Skip to content

Commit 7a2bd04

Browse files
Update 2025-07-02-designing-eligibility-in-the-app.md
1 parent 5bad677 commit 7a2bd04

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

app/posts/vaccinations-in-the-app/2025/07/2025-07-02-designing-eligibility-in-the-app.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,10 @@ One way we’re personalising the experience is by showing in the App:
2525
* any vaccination appointment we believe they've already booked
2626
* any vaccination we believe they’ve already had (and the date)
2727

28-
28+
**Appointment booked**
29+
30+
![Screenshot of a page titled 'RSV for older adults', playing back to the user that they have an appointment booked](already-booked.png)
31+
2932
But what if we’ve got these events, or the person's age, wrong?
3033

3134
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.
@@ -34,10 +37,6 @@ We’re testing designs where the personalised message still confidently conveys
3437

3538
Part of this involves a 'Help and Support' page to guide users who think something might be wrong. One place we link to this is from the 'Vaccination given' screen. The page will explain why, on occasion, vaccination information may not appear correctly and what steps they can take.
3639

37-
**Appointment booked**
38-
39-
![Screenshot of a page titled 'RSV for older adults', playing back to the user that they have an appointment booked](already-booked.png)
40-
4140
**Vaccination given**
4241

4342
![Screenshot of a page titled 'RSV for older adults', playing back to the user that they've already been vaccinated, with a help and support link](already-vaccd.png)

0 commit comments

Comments
 (0)