Add previous RAVS design history entries

app/_layouts/product.njk

@@ -36,6 +36,9 @@
           "Bowel screening",
           "Explore team",
           "Manage breast screening"
+        ] },
+        { title: "Vaccinations", services: [
+          "Record a vaccination"
         ] }
       ] %}
 

app/posts/record-a-vaccination/2023/03/2023-03-24-what-is-the-record-a-vaccination-service.md

@@ -0,0 +1,38 @@
+---
+title: "What is the record a vaccination service? "
+date: 2023-03-24
+---
+### The service will enable healthcare professionals to record vaccination data safely and efficiently.
+
+Over the last eight months, we have been working to understand what the future of [point of care (PoC)] (https://digital.nhs.uk/coronavirus/vaccinations/training-and-onboarding/point-of-care) should look like and how we can transform the current PoC market to deliver key NHS outcomes better and meet the needs of clinicians and patients.
+
+### Current challenges
+
+Throughout our work, we've found reoccurring challenges faced by users of services within the current PoC market.
+
+- Users who record data when administering Covid-19 and Flu vaccinations together often find the process complicated and time-consuming.
+- Clinicians typically have to navigate multiple systems to join up and record patient booking and demographic data into their POC systems
+- Poor service usability is leading to data errors and clinical risk for patients
+
+We've also found that the PoC services do not enable the delivery of strategic NHS outcomes such as improving the timeliness of data across [section 7a vaccinations] (https://www.gov.uk/government/publications/public-health-commissioning-in-the-nhs-2021-to-2022/annex-a-public-health-functions-section-7a-agreement-2021-to-2022-services-to-be-provided) and driving more effective patient intervention and vaccine uptake.
+
+And we know that adding new types of vaccine, eligibility questions and making PoC changes can often be time-consuming and burdensome and removes the agility needed to respond rapidly to developing situations.
+
+### Strategic priorities
+The future of PoC provision will need to enable the delivery of strategic outcomes such as increasing vaccine uptake and improving the timeliness of patient interventions. The services within the market will need to be able to fulfil these organisational priorities and respond to outbreak or surge situations.
+
+### Record a vaccination
+One of the key recommendations was to develop an in-house PoC service. We've called it 'Record a vaccination'. The service will support healthcare settings to safely and efficiently record current vaccinations.
+
+We aim to:
+
+- Deliver an exceptional user experience
+- Improve data quality and reduce clinical risk
+- Integrate with other systems for more consistent data and an efficient process
+- Support the administration and recording section 7a vaccinations
+- Drive an increase in PoC service standards throughout the market
+
+### We’re starting to build the service
+As we begin our beta (or build) phase, we want to document and share the learnings we have had throughout our work and the progress we will make going forward.
+
+Our design history will show how the service we are developing has been validated through user research across delivery models and will lead to a better point-of-care experience for all users.

app/posts/record-a-vaccination/2023/03/2023-03-31-making-sure-everyone-can-use-the-service.md

@@ -0,0 +1,22 @@
+---
+title: "Making sure everyone can use the service "
+date: 2023-03-31
+---
+To design and build a record a vaccination service that works across different healthcare settings, we must meet the needs of various user groups and staff with diverse roles or permissions, like system administrators and vaccinators.  
+
+Throughout our prototyping, we plan to invite research participants from: 
+
+- Community pharmacies   
+- GP practices   
+- Hospitals (including maternity services) 
+- Large vaccination centres   
+- Primary care networks  
+
+
+We'll consider: 
+
+- What vaccine delivery settings do they work in?  
+- What point-of-care systems do they currently use?  
+- What is the level of their digital literacy?  
+
+The aim is to recruit two users across each setting, ideally, one participant representing maternity services in hospital hubs to get a good mix of users familiar with different point-of-care systems. 

app/posts/record-a-vaccination/2023/04/2023-04-10-sprint-one-managing-vaccines.md

@@ -0,0 +1,67 @@
+---
+title: "Sprint one: managing vaccines"
+date: 2023-04-10
+---
+### Designing a new service to manage vaccines
+Managing vaccines is a new service area we’re exploring in alpha. Our initial research highlighted users need to add vaccines and batches in their point-of-care (POC) systems, so they are ready to select and record data. 
+
+However, some systems do not allow users to track vaccine usage and stock levels easily.  
+
+### Building to learn
+With limited knowledge of this service area, we considered what stock-related tasks users would want to perform, built prototypes, and tested different ideas — learning more and learning faster this way.  
+
+To manage vaccines, we assume or know from other POC systems, staff typically: 
+
+- Order vaccines from one or multiple stock ordering systems 
+- Check-in delivered vaccine stock batches into their POC system 
+- Choose and record the type of vaccines, batches and doses they give to patients within their POC system 
+- Track and monitor the use of stock outside of a POC system 
+
+During the sprint, we aimed to understand how users: 
+
+- Navigate the main tasks to check in and manage vaccines 
+- Use language to describe stock management tasks and units of stock 
+- Could track stock more effectively using the system 
+
+### Getting the scope of our service right 
+We explored how users order and manage stock using different structures, systems, and processes — mindful that our POC system should join up with, or point to what’s already in place (not replicate or replace it). 
+
+We specifically looked at:
+
+- How is stock currently ordered? What systems, processes or people are involved? What can we do to simplify this? 
+- When and how frequently is stock delivered? How is stock checked in and entered within POC systems? What can we do to make this easier? 
+- How is used stock recorded within a POC system and tracked by staff? How do staff know they have enough left to cover their planned appointments or when to order more? How can we make this more visible? 
+
+### Prototyping without designers  
+
+At the start of alpha, we had not yet onboarded our designers, so we worked as a team to process our ideas and develop some basic wireframes. This gave us a good starting point for our user research sessions. In future, we'll build prototypes in Figma and make design iterations based on what we learn. Our prototypes supported the following scenarios:
+
+**Users set up their systems to record the vaccines they administer**.
+
+![Manage your settings prototype](n2o41zl3ml3fctfv5mtjfn9t7jra.png)
+
+
+**Users view their order history and check in a new stock delivery**.  
+
+![Vaccine order history prototype](gmmfe4za4z1wlf1hqk281g0xlg2h.png)
+
+
+**Users view vaccine stock levels and future delivery dates**.  
+
+![View vaccine stock levels prototype](8mqb0e4dfc97czphhquosc3jtaup.png)
+
+
+**Users are notified when stock is low**.  
+
+![Low stock alert prototype](jrpwwdnlyl47f5k86q4kb0abn44q.png)
+
+
+### What we learnt 
+
+Following testing, we found: 
+
+- Setting the minimum value for stock is helpful to users monitoring stock levels and alerts. The max stock level is of far less value to them.  
+- Users order vaccines from several sources like a central team, pharmacy, or network of suppliers, so identifying a single ordering system or allowing users to order through their point-of-care system would be challenging. As such, we agreed supporting users to order directly through a point-of-care system was out of scope. 
+- Users expect to manage vaccine stock settings when setting up the system. 
+- System administrators should be alerted to low stock, as early in the journey as possible, ideally from the home page.  
+- The system would need to be able to track stock donations from other organisations with excess stock close to expiring and split orders.  

app/posts/record-a-vaccination/2023/04/2023-04-17-sprint-one-managing-clinics.md

@@ -0,0 +1,77 @@
+---
+title: "Sprint one: managing clinics"
+date: 2023-04-17
+---
+### Designing a new service to manage clinics 
+We are exploring what users would expect from a new service area ‘manage clinics’ in alpha. We’ve considered what tasks users would want to perform, built prototypes, and tested different ideas — learning more and learning faster this way. 
+
+Our main goals are to address known user pain points of finding patients in a clinic, which can cause significant delays and address the lack of integration between other booking and point-of-care systems. 
+
+To manage clinics, staff typically: 
+
+- set up calendars of patient appointments into booking or calendar systems 
+- manually transfer appointment information into their point-of-care (POC) system to record vaccination data, though some point of care systems integrate booking  
+- assign teams of clinical staff to administer and record vaccinations 
+- arrange additional support or longer appointments for patients with specific needs 
+
+During the sprint, our goal was to:  
+
+- verify the main tasks users perform to manage clinics based on our assumptions 
+- identify the language used to describe clinic management tasks 
+- understand how users could manage clinics more effectively using the system 
+
+### Exploring new approaches  
+
+We explored: 
+
+- where appointment information is captured, and how it’s entered in current POC systems. And how we can leverage technology to simplify this. 
+- how we can accommodate appointment bookings and walk-in patients. 
+- how we can help users find and allocate the right staff to administer vaccinations. 
+- where we can show patient information in the system to support the planning of appointments. 
+
+### Getting the scope of our service right 
+We explored how users manage appointments and calendars using different structures, systems, and processes — mindful that our POC system should join up or point to with what’s already in place (not replicate or replace it).  
+
+### Prototyping without designers  
+
+At the start of alpha, we had not yet onboarded our designers, so we worked as a team to process our ideas and develop some basic wireframes. This gave us a good starting point for our user research sessions. In future, we’ll build prototypes in Figma and make design iterations based on what we learn. Our prototypes supported the following scenarios:
+
+**Users set up their clinics to deliver and record vaccinations**.
+
+![Plan your clinic homepage](eccyyd9xahdqn16pv7hrc8qhkzor.png)
+
+![Set up clinic screen](u8cu2anf2uymycq20zr6jqvo1w7o.png)
+
+#### We learnt:
+
+- Users expect to see a list of sites with corresponding calendars. 
+- Maternity settings operate differently: patients drop in for a vaccine when they attend a maternity appointment. 
+- Users in large vaccination centres see no value in allocating staff to a scheduled clinic because they may only find out who is working on the day.  
+- Current point-of-care systems record the vaccinator's details, which users view as an administrative burden.   
+- Users view the ability to ‘check how many vaccines are available’ as positive and expect to see the clinic’s capacity to accommodate walk-in patients.   
+
+**Users identify and arrange support for patients who need reasonable adjustments or assistance**. 
+
+![Arrange patient support screen](9a6eux4vy6zzjzc3uvxpln4pjguo.png)
+
+![Arrange patient support options screen](uf9ejlrjuk5huxmnwtr2w66j6ftl.png)
+
+#### We learnt:
+
+- Users need to know if patients have specific requirements or need reasonable adjustments in advance because it could lengthen the duration of their appointment or require a particular staff member.   
+- The national booking service (NBS) captures some (but not all) patient access needs. For example, we learnt there is a need for staff to prepare clinics in advance for stem cell patients or patients who cannot show their arms for religious reasons, which NBS does not capture.  
+- If patients book their appointments through a booking system like the national booking service (NBS), users need the ability to change the location of the appointment in their point-of-care system. Currently, users must cancel the appointment in their system, manually reschedule it (at a new site) and notify the patient. 
+
+**Users find patients with or without appointments**.
+
+![Find patients in appointment list screen](jfqt16o4cle8ima0feq29c611u9d.png)
+
+![Search to find patients screen](5ucliwzr5ykutzzsxdylf3tqwmc4.png)
+
+#### We learnt:
+
+- Users expect to see the appointment list and patients before arranging support. 
+- Users expect to see (at a glance) in the appointment list patients who need additional support. While maternity setting users can already view this information in the patient record, which is of less value to them.     
+- The list is a good starting point for viewing all patients. For example, users are likely to click on the patient’s name and start recording their vaccination data, removing the need to search for them.   
+- Users expect to extract an appointment list from other systems in an appropriate format, like a CSV file.  
+- Users expect to search and filter the appointment list in one view.