Update went-for-an-appointment-came-back-with-a-list.md

Author: johnrimmer2

app/posts/record-a-vaccination/2025/07/went-for-an-appointment-came-back-with-a-list.md

@@ -11,33 +11,36 @@ But there are a huge number of appointment systems out there, so integrating wit
 
 We thought about what was useful about appointments and how we could deliver the benefits without integrations or duplicating what appointment systems already do and so... ‘Lists’ were born!
 
-## What are the benefits?
+## The benefits of appointments
 
 When we reflected on what we'd heard from users in terms of ’what’s so good about appointments?’, the mosts compelling reason was being able to see a list of everyone they had to see, how many they had left and who had been vaccinated.
 
-And we could do that, allow them to have structured lists of patients. Maternity clinics & Staff vaccinations (where the patients are already known & there isn’t always a specified time for the appointment) make up 40% of RAVS activity.
+And we could do that, allow them to have structured lists of patients. Maternity clinics & Staff vaccinations (where the patients are already known and there isn’t always a specified time for the appointment) make up 40% of RAVS activity.
 
-Today RAVS works liek so - a vaccinator looks up a patient, vaccinates them, and then looks up the next one and so on.
+Today RAVS works like so, a vaccinator looks up a patient, vaccinates them, and then looks up the next one and so on.
+
+
+## So how's it different?
 
 Lists would be different - the vaccinator is choosing the patient from a much smaller list of known users they’ve input themselves, and RAVS is ready to provide the details.
 
 But how to get the patient NHS numbers into RAVS was the challenge - by template or free text boxes, individually or by the 100s? Every option’s got shortcomings.
 
 And it’s not only a completely new concept for RAVS; adding large sets of data doesn’t have a lot of precedent in NHS or GOV design patterns, so we were designing new ground.
 
-In the end we decided a template would be too fiddly/fraught and instead designed a journey which asks vaccinators a few questions about when & where the vaccinations will be done, before they cut&paste NHS numbers from their booking system into a box in RAVS.
+In the end we decided a template would be too fiddly and instead designed a journey which asks vaccinators a few questions about when and where the vaccinations will be done, before they copy and paste NHS numbers from their booking system into a box in RAVS.
 
 ## How to make a List
 
-So far so simple, but we crave simplicity, so we also simplified the design by:
-- Removing a ‘check/confirm’ screen in favour of in-page error messages for non-existant NHS numbers
+So far so simple, but we wanted to go further and simplified the design by:
+- Removing a 'check' page in favour of in-page error messages for non-existant NHS numbers
 - Showing everything in one list, rather than separate lists for Awaiting and Recorded
-- Applying Search to one list at a time
-- Moving ‘delete list’ to the bottom of the page to simplify the top
-- Reviewing and iterating the content, particularly on the add NHS numbers page
+- Applying search to one list at a time
+- Moving ‘delete list’ to the bottom of the page help visual clutter
+- Iterating the content, with particular focus to the add NHS numbers page
 Finally, we re-named the section to better describe a list of patients, their NHS numbers, a date and a location
 
-We didn’t set out to do this - remember we thought we wanted appointments(!). But Lists keeps things simple & achieves the vast majority of Appointments benefits.
+We didn’t set out to do this - remember we thought we wanted appointments. But Lists keeps things simple and achieves the vast majority of what an appointment does.
 
 ![Lists Home](lists-home.png)