NHSE Share blood pressure readings with your GP Alpha assessment

From: DHSC
Assessment date: 02/07/2026
Stage: Alpha assessment
Result: Green
Service provider: NHS England

Service description 

This service aims to solve the problem of… 

• GPs to request, view and manage recurring blood pressure readings so that they can efficiently receive more, higher quality blood pressure data from their patients on a schedule that they choose, leading to better managed hypertension for the patients

• Patients to send blood pressure readings to their GP through the NHS App, either manually or automatically via a smart bluetooth blood pressure cuff so that they can send blood pressure readings within the high-trust NHS App, either manually or automatically, leading to better managed hypertension by providing key info to GPs

Service users 

This service is for… 

• General practitioners (GPs) 

• GP admin staff 

• People diagnosed with hypertension who have agreed with their GP to record their blood pressure via the NHS App 

Report contents

1. Understand users and their needs
2. Solve a whole problem for users
3. Provide a joined-up experience across all channels
4. Make the service simple to use
5. Make sure everyone can use the service
6. Have a multidisciplinary team
7. Use agile ways of working
8. Iterate and improve frequently
9. Create a secure service which protects users’ privacy
10. Define what success looks like and publish performance data
11. Choose the right tools and technology
12. Make new source code open
13. Use and contribute to open standards, common components and patterns
14. Operate a reliable service

1. Understand users and their needs 

Decision 

The service was rated green for point 1 of the Standard 

• It was clear from the assessment that users are at the forefront of the design of the service and that the whole team regularly engage with research and the findings. 

Optional advice to help the service team continually improve the service: 

• Private beta will need to look to extend the representation of users in UR. Although the sample was not particularly diverse in alpha, it was great to see the future plans talked about and this will need to be a priority to ensure the service gain a comprehensive understanding of the full spectrum of service users. 

• Employing a diverse range of UR methods to avoid reliance on qualitative or quantitative evidence alone. 

2. Solve a whole problem for users 

Decision 

The service was rated green for point 2 of the Standard. 

Optional advice to help the service team continually improve the service: 

• The team demonstrated early consideration about the importance of people using the right cuff, opting for a simple and practical approach to connect users with 3^rd party society advice on an external website. Further consideration should ideally be given to the usability and accessibility of that advice and how essential it is that patients follow it. 

• Private beta will need to look at whether the service is successfully solving the whole monitoring journey from "GP asks for readings" through to "patient receives reassurance or clinical follow-up", in particular: 
  • how patients know their readings have been seen
  • what feedback patients receive after submission
  • how opt-outs, missed readings and rescheduled readings are handled

3. Provide a joined-up experience across all channels 

Decision 

The service was rated green for point 3 of the Standard. 

Optional advice to help the service team continually improve the service: 

• The team made it clear that the majority of operational work would sit with GP admin staff. It will be important in private beta to look at the work still to do around flagging and workflow integration to ensure the service does not increase burden. Specifically: 
  • how GP admin staff would flag readings needing clinician review
  • how alerts and notifications should work
  • how the workflow should fit with existing practice processes
  • ensuring the service integrates with current GP workflows rather than creating extra work

• The team noted their intent to look at the role of pharmacists – it will be important to test this and other touchpoints that patients have in the management of hypertension.

4. Make the service simple to use 

Decision 

The service was rated green for point 4 of the Standard. 

Optional advice to help the service team continually improve the service: 

• The team made it clear that they are aware that notification design will be a focus for private beta. Success depends on making blood pressure sharing feel effortless and fit into everyday life, particularly for users who are disengaged or highly sensitive to friction. It will be important to test: 
  • how many reminders are acceptable 
  • whether reminder messages should also create NHS App inbox messages 
  • how to support patients who miss readings 
  • how to handle repeated rescheduling 
  • whether notifications drive completion without creating fatigue 

5. Make sure everyone can use the service  

Decision 

The service was rated green for point 5 of the Standard. 

Optional advice to help the service team continually improve the service: 

• The team noted that more accessibility testing is planned. It will be important to expand accessibility and inclusion research to cover carers, lower digital literacy users, diverse demographic groups and people using assisted digital support. Private beta needs to demonstrate that the service works for people who do not fit the "confident NHS App user" profile as well as it works for those who do. 

6. Have a multidisciplinary team 

Decision 

The service was rated green for point 6 of the Standard. 

7. Use agile ways of working 

Decision 

The service was rated green for point 7 of the Standard. 

8. Iterate and improve frequently 

Decision 

The service was rated green for point 8 of the Standard. 

Optional advice to help the service team continually improve the service: 

• The team already has a mature approach to iteration through risky-assumption mapping, user research, prototype testing and regular retrospectives. In private beta, it will be necessary to test real-world behaviour. 

9. Create a secure service which protects users’ privacy 

Decision 

The service was rated green for point 9 of the Standard. 

Optional advice to help the service team continually improve the service: 

• Ensure the service is added to the relevant DPIAs in beta to ensure compliance to secure by design principles.

10. Define what success looks like and publish performance data 

Decision 

The service was rated green for point 10 of the Standard. 

Optional advice to help the service team continually improve the service: 

• The team should continue the work already begun in defining and quantifying OKRs and KPIs, including Cost Per Transaction for this service. 

• The team should engage a health economist or academic to help evaluate long-term health outcomes and cost savings associated with the service rollout. 

11. Choose the right tools and technology 

Decision 

The service was rated green for point 11 of the Standard. 

12. Make new source code open 

Decision 

The service was rated green for point 12 of the Standard. 

Optional advice to help the service team continually improve the service: 

• For beta create and link to a repository to evidence this.

13. Use and contribute to open standards, common components and patterns 

Decision 

The service was rated green for point 13 of the Standard. 

Optional advice to help the service team continually improve the service: 

• There were impressive points related to this service that would be good to make sure you are highlighting and celebrating (for example the PDM adapter that had been shared and used by another team).

14. Operate a reliable service 

Decision 

The service was rated green for point 14 of the Standard.