|
| 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 | +## 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 the person's 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 still confidently conveys that the user does not need the vaccine, but allows them to flag concerns and proceed with getting the vaccination, if needed. |
| 34 | + |
| 35 | +We're also developing a 'Help and Support' page to guide users who suspect something might be wrong. One place we link to this is from the 'vaccination given' screen. It will explain why vaccination information may not appear correctly and what steps they can take. |
| 36 | + |
| 37 | +**Appointment booked** |
| 38 | + |
| 39 | + |
| 40 | + |
| 41 | +**Vaccination given** |
| 42 | + |
| 43 | + |
| 44 | + |
| 45 | +## Telling people they cannot have it |
| 46 | + |
| 47 | +Even when the data is right, it’s hard telling people they are not eligible. We currently say: |
| 48 | + |
| 49 | +>“We do not believe you can have it. This is because you: |
| 50 | +> |
| 51 | +>* are not aged 75 to 79” |
| 52 | +
|
| 53 | +This is not landing well for everyone. People who are proactive about their health often don’t feel that’s a good enough reason. |
| 54 | + |
| 55 | +One user, aged 80, asked: “Why does it stop at 79? That doesn’t seem fair.” |
| 56 | + |
| 57 | +Another, with a weakened immune system, said they planned to check with their GP in case they still qualified. |
| 58 | + |
| 59 | +They have a point. Clinicians reminded us that the vaccine is available privately – so technically, anyone could choose to have it. |
| 60 | + |
| 61 | +Perhaps the 'Help and Support' page can help here too. If we had empathetic content on that page for people who are unsure why they're not being offered a vaccine, might this reassure them? |
| 62 | + |
| 63 | + |
| 64 | + |
| 65 | +One last point: you'll notice we've deliberately avoided using the word 'eligible'. It's a policy word that can be confusing — especially for users who are not fluent in English or with low digital literacy. |
| 66 | + |
| 67 | + |
0 commit comments