|
| 1 | +--- |
| 2 | +title: "Designing eligibility for vaccinations in the NHS App" |
| 3 | +date: 2025-07-02 |
| 4 | +--- |
| 5 | + |
| 6 | +We’re working on a new vaccination feature in the NHS App to help people of any age: |
| 7 | + |
| 8 | +* understand which vaccines they should get |
| 9 | +* check if they’ve already had them |
| 10 | +* get a convenient appointment |
| 11 | + |
| 12 | +Our aim is to make vaccination information more relevant and personal, based on what we know about them. We’re doing that using a new Eligibility API that brings together things like age and vaccine history. |
| 13 | + |
| 14 | +By tailoring the experience, we hope to make it easier for people to take action, reduce pressure on frontline services, and ultimately improve uptake. |
| 15 | + |
| 16 | +We’re starting with the RSV vaccine, and one of the key groups it's offered to is older adults within a specific age range. By using age and vaccine appointment data, we can give adults checking their eligibility a more tailored experience. |
| 17 | + |
| 18 | +But it’s not straightforward. Here’s how we’re tackling two of the biggest content challenges. |
| 19 | + |
| 20 | + |
| 21 | +## 1. Designing for uncertainty |
| 22 | + |
| 23 | +One way we’re personalising the experience is by showing in the App: |
| 24 | + |
| 25 | +* any vaccination appointment we believe they've already booked |
| 26 | +* any vaccination we believe they’ve already had (and the date) |
| 27 | + |
| 28 | + |
| 29 | +But what if we’ve got these events, or their age, wrong? |
| 30 | + |
| 31 | +To avoid shutting out people who should get the vaccine, we’re designing ways for them to challenge what they see and take action if something doesn’t look right. |
| 32 | + |
| 33 | +We’re testing designs where the personalised message is still clear and confident, but we allow users to flag concerns and proceed to booking, if needed. |
| 34 | + |
| 35 | +**Appointment booked** |
| 36 | + |
| 37 | + |
| 38 | + |
| 39 | +**Vaccination given** |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | +## 2. Telling people they cannot have it |
| 44 | + |
| 45 | +Even when the data is right, it’s hard telling people they are not eligible. We currently say: |
| 46 | + |
| 47 | +“We do not believe you can have it. This is because you: |
| 48 | + |
| 49 | +* are not aged 75 to 79” |
| 50 | + |
| 51 | +This is not landing well for everyone. People who are proactive about their health often don’t feel that’s a good enough reason. |
| 52 | + |
| 53 | +One user, aged 80, asked: “Why does it stop at 79? That doesn’t seem fair.” |
| 54 | + |
| 55 | +Another, with a weakened immune system, said they planned to check with their GP in case they still qualified. |
| 56 | + |
| 57 | +They have a point. Clinicians reminded us that the vaccine is available privately – so technically, anyone could choose to have it. |
| 58 | + |
| 59 | +We’re wondering if removing specific mentions of ages: “It’s not currently available on the NHS for your age group” might be clearer and a more helpful starting point. We might also explore tone: can we make it more empathetic? |
| 60 | + |
| 61 | + |
| 62 | + |
| 63 | +We’ll be back with another Design History soon, once we’ve tested and refined these ideas. |
| 64 | + |
| 65 | + |
0 commit comments