Immunisation Consent: Part 4
We’ve spent the last couple of sprints in the Define stage, following the Discovery and are currently in the first sprint of the Develop stage. This is what we’ve been doing.
User needs
Our analysis of the user research helped us identify around 20 user needs for the service. These are statements describing what different users need from the service. Our first attempts are broader statements than we might usually want, but they are a good basis to develop from. Here are a couple of examples:
“As the Head of Children's Health Provision I want to ensure that all parties with parental responsibility have access to the correct information, advice and guidance so that they can make an informed decision about consent, without being excluded”
“ As the Business Support Officer I want to free up my time from scanning in forms and inputting data into SystmOne so that I can support the team more widely in my role”
Problem statements
After looking at the research outputs and user needs identified, we needed to write some problem statements, describing the main areas of focus for prototyping. We came up with 6 statements that we felt covered the main opportunities for improvement.
- Contract — The NHS England contract requires a paperless approach to gaining consent, but research suggests wholesale change can lead to reduction in take-up
- Information and Guidance — Many of the parents we spoke to are happy with the information provided, but there are users with non-standard needs who need access to more detailed information
- Roles and Responsibilities — There is a lack of consistency in the approach of schools to roles, responsibilities and data ownership that increases the workload for school staff
- Digital Exclusion — Digital skills and access to the internet are not universal
- Service demand — Expansion of the number of children eligible for immunisations will lead to increased demand for services, which will have an impact on resilience, costs and workload
- Data security — While currently well managed and successful, the current process does carry a risk to data security from loss or theft of paper forms
“How might we..?” workshop
We really wanted to involve the service team as much as possible in coming up with ideas, as they are the experts in how things work and can do a great job in identifying ways things could be better.
We ran a workshop with the team, discussing the problem statements and potential ways to approach them, using the “How might we..?” question format to stimulate the conversation. The end result was lots of post-it note ideas clustered around each of the statements.
We focused on the problem statements that didn’t involve a digital consent solution in the session, as the requirements for this need to be looked at in more detail than time allowed. We intend to create a list of requirements based on the user needs mentioned earlier, that might need breaking down further into user stories to be more useful.
Presentation to Clinical Update Group
We were guest speakers at a Clinical Update group meeting as part of our ongoing commitment to working in the open and keeping stakeholders engaged.
Very few of the attendees had been at the Show and Tells or the workshop, so they got the full story so far, from kick-off meeting to the ideas workshop. We forget how much we’ve done, until we talk about it all!
Prototyping
Given the amount of showing and telling we’ve been doing lately, I’m looking forward to getting into the hands-on design work. We looked at the ideas we got from the workshop and distilled them down to around 10 that we thought we should look further into. We decided to use the next show and tell slot for developing some of the ideas into testable prototypes.
We had a go at a couple of paper prototypes in advance, to give the service team an idea of the approach. We’ll see what feedback they give us too — always be testing!
This one is from the Information and Guidance problem statement. Not all schools publicise the immunisation session date to the parents. We do already publish the schedule on one of our web pages, but it’s a pdf document. We’ll be prototyping a new content design for our web pages too, but we had a think about how we could create a way to have it searchable, dynamic and up-to-date.
Next steps
We’ll be creating and testing more prototypes over the next couple of sprints, as well as starting the process of procuring or developing an online consent system.
It will be pretty fast paced, but a lot of fun!
Attribution
Contract icon — Designed by wanicon from www.flaticon.com
Information icon — Designed by Freepik from www.flaticon.com
Meeting icon — Designed by Prosymbols from www.flaticon.com
Digital exclusion icon — Designed by Freepik from www.flaticon.com
Syringe icon — Designed by surang from www.flaticon.com
Data protection icon — Designed by Eucalyp from www.flaticon.com
