Add RAVS post: Finding the patient first#435
Open
frankieroberto wants to merge 3 commits intomainfrom
Open
Conversation
This is aimed to make it quicker to get started, by giving you a template you can copy with all the relevant fields.
Anna-Sutton
reviewed
Mar 27, 2026
Collaborator
Anna-Sutton
left a comment
Anna-Sutton
left a comment
There was a problem hiding this comment.
I've made a few suggestions - feel free to ignore any that don't work for you. Well done for doing this one - it's really quite difficult to explain. Probably of most use to future RAVS designers - when someone next thinks of reordering the journey!
|
|
||
| We’ve since learnt from our [customer experience survey](/record-a-vaccination/2025/03/asking-fewer-better-questions/) and from [visiting London pharmacies](/record-a-vaccination/2025/12/london-pharmacy-research/) that some users have found one aspect of the new order to be frustrating. | ||
|
|
||
| To address this, we have now reordered the new interface, so that the patient search and vaccination now come first. |
Collaborator
There was a problem hiding this comment.
Maybe 'so that the patient's details and vaccination history are shown earlier'
|
|
||
| ## Feedback | ||
|
|
||
| We tested the redesigned journey in user research sessions. Whilst we gained valuable feedback on some of the details, we did not observe any issues or hear any feedback on the order. |
Collaborator
There was a problem hiding this comment.
Suggested change
| We tested the redesigned journey in user research sessions. Whilst we gained valuable feedback on some of the details, we did not observe any issues or hear any feedback on the order. | |
| When we tested the redesigned journey, we did not observe any issues or hear any feedback on the order. |
|
|
||
| We tested the redesigned journey in user research sessions. Whilst we gained valuable feedback on some of the details, we did not observe any issues or hear any feedback on the order. | ||
|
|
||
| However, after launching the new interface and during [a period of dual running it with the old interface](/record-a-vaccination/2025/10/how-we-told-users-about-a-change-to-the-interface/), we started to receive feedback and user needs not previously discovered. |
Collaborator
There was a problem hiding this comment.
Suggested change
| However, after launching the new interface and during [a period of dual running it with the old interface](/record-a-vaccination/2025/10/how-we-told-users-about-a-change-to-the-interface/), we started to receive feedback and user needs not previously discovered. | |
| However, after launching the new interface and during [a period of dual running it with the old interface](/record-a-vaccination/2025/10/how-we-told-users-about-a-change-to-the-interface/), we discovered some new user needs. |
|
|
||
| However, after launching the new interface and during [a period of dual running it with the old interface](/record-a-vaccination/2025/10/how-we-told-users-about-a-change-to-the-interface/), we started to receive feedback and user needs not previously discovered. | ||
|
|
||
| In particularly, some users mentioned that it was useful to check the patient details in order to make sure they are eligible for the vaccination. For example, one user said: |
Collaborator
There was a problem hiding this comment.
Suggested change
| In particularly, some users mentioned that it was useful to check the patient details in order to make sure they are eligible for the vaccination. For example, one user said: | |
| In particular, some users mentioned that it is useful to check the patient's details in order to make sure they are eligible for the vaccination. For example, one user said: |
|
|
||
| ## Background | ||
|
|
||
| When we set out to redesign the recording interface back in late 2024, a lot of our thinking was about optimising for vaccination clinics for COVID-19, flu or pertussis, where a lot of patients would all be given the same vaccine by the same vaccinator in the same location. |
Collaborator
There was a problem hiding this comment.
Suggested change
| When we set out to redesign the recording interface back in late 2024, a lot of our thinking was about optimising for vaccination clinics for COVID-19, flu or pertussis, where a lot of patients would all be given the same vaccine by the same vaccinator in the same location. | |
| When we set out to redesign the recording interface back in late 2024, our initial focus was on optimising the user journey for vaccination clinics, for example for flu, where several patients would all be given the same vaccine by the same vaccinator in the same location. |
|
|
||
| In addition, we’ve heard that some clinicians prefer to check the patient’s age electronically rather than directly ask the patient. | ||
|
|
||
| There was also a separate need we’ve uncovered: some users are using RAVS to proactively check whether an eligible patient had had their vaccination yet, in order to be able to offer it to them if they have not. This is not something RAVS was specifically designed for, however opportunistic vaccination is part of the overall public health strategy, and we are keen to support this. |
Collaborator
There was a problem hiding this comment.
Suggested change
| There was also a separate need we’ve uncovered: some users are using RAVS to proactively check whether an eligible patient had had their vaccination yet, in order to be able to offer it to them if they have not. This is not something RAVS was specifically designed for, however opportunistic vaccination is part of the overall public health strategy, and we are keen to support this. | |
| We also discovered that some users are using RAVS to proactively check whether an eligible patient has already had a vaccination, in order to offer it to them if they have not. This is not something RAVS was specifically designed for, however opportunistic vaccination is part of the overall public health strategy, and we are keen to support this. |
|
|
||
| ## What we changed | ||
|
|
||
| In response to the feedback, we’ve now changed the order so that the step of finding the patient and seeing their details now comes first, followed by the other questions. |
Collaborator
There was a problem hiding this comment.
Suggested change
| In response to the feedback, we’ve now changed the order so that the step of finding the patient and seeing their details now comes first, followed by the other questions. | |
| In response to the feedback, we’ve changed the order so that the step of finding the patient and seeing their details now comes first, followed by the other questions. |
|
|
||
|  | ||
|
|
||
| When a vaccination has been recorded, if the user selects the option to record the same vaccination for the next patient, they still skip the common questions (date, location, vaccinator, vaccine type and batch) in order to save time. |
Collaborator
There was a problem hiding this comment.
Suggested change
| When a vaccination has been recorded, if the user selects the option to record the same vaccination for the next patient, they still skip the common questions (date, location, vaccinator, vaccine type and batch) in order to save time. | |
| When a vaccination has been recorded, if the user selects the option to record the same vaccination for the next patient, they still skip the questions that are less likely to differ from one patient to the next (date, location, vaccinator, vaccine type and batch) in order to save time. |
|
|
||
| ## Future considerations | ||
|
|
||
| We’ll monitor feedback on the re-ordered flow to check that it hasn’t introduced any new issues. |
Collaborator
There was a problem hiding this comment.
Suggested change
| We’ll monitor feedback on the re-ordered flow to check that it hasn’t introduced any new issues. | |
| We’ll monitor feedback on the reordered flow to check that it hasn’t introduced any new issues. |
|
|
||
| We’ll monitor feedback on the re-ordered flow to check that it hasn’t introduced any new issues. | ||
|
|
||
| Moving the patient finding to the beginning also now makes it possible to display the patient’s name and details on more of the subsequent screens. This might be something we look at in future. |
Collaborator
There was a problem hiding this comment.
Suggested change
| Moving the patient finding to the beginning also now makes it possible to display the patient’s name and details on more of the subsequent screens. This might be something we look at in future. | |
| Now that we begin with the patient, it makes it possible to display the patient’s name and details on more of the subsequent screens. This might be something we look at in future. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.