From: DHSCAssessment date: 04/09/2025Reassessment date: 21/01/2026Stage: Alpha reassessmentResult: Green at reassessmentService provider: DHSC
Service descriptionFPHD aims to improve and protect health and reduce inequalities through high-quality public health intelligence, available to all.
FPHD enables users to find, access and use public health data about England, via a single, trustworthy and accessible platform, so that they can make informed decisions and get the information they need, whether that's updating a JSNA (Joint Strategic Needs Assessment), building a policy case, evaluating a public health intervention, conducting research, or understanding the health landscape of their local area.
Service users Data publishers Internal DHSC users: DHSC, NHSE and UKHSA analysts Data consumers Public Health Analysts Public Health Specialists Policy Professionals Academics Elected Representatives Members of the Public Things the service team has done well: Given short timescales, the team built effectively on previous user research to identify, prioritise and fill gaps in their alpha research, in particular around users who will publish data. The team used a mix of methods, and began planning for further research by creating a user panel and identifying potential participants with access needs The team have demonstrated a strong understanding of the Key Performance Indicators (KPIs) for their project and established appropriate metrics for monitoring them Report contents Understand users and their needs Solve a whole problem for users Provide a joined-up experience across all channels Make the service simple to use Make sure everyone can use the service Have a multidisciplinary team Use agile ways of working Iterate and improve frequently Create a secure service which protects users’ privacy Define what success looks like and publish performance data Choose the right tools and technology Make new source code open Use and contribute to open standards, common components and patterns Operate a reliable service 1. Understand users and their needs DecisionThe service was rated green for point 1 of the Standard.
Advice to help the service team continually improve the service:
the team has a large amount of user research work to do with diverse user groups and limited UR resource, moving into beta. They would benefit from working with DHSC stakeholders to review their evidence base and prioritise their project and research goals - recognising that whilst they have clearer evidence of needs for some well researched groups, such as Local Authority public health analysts, there are user groups where their research is at a much earlier stage. For example they have only spoken to a few members of the public. Given their limited understanding of this user group at this early stage, and recognising that their needs are likely to differ significantly from those of public health analysts, the team should carry out further work to understand the needs of members of the public. 2. Solve a whole problem for users DecisionThe service was rated amber for point 2 of the Standard.
This is amber because:
The service is aiming to make public health intelligence accessible and useful for everyone from analysts to members of the public, however, no riskiest assumptions have been identified, nor tested in relation to the problem statement. Assumptions the team validated during the Alpha treated ‘Data Consumers’ as a single group, which meant that the hardest question ‘How might we serve both audiences’ that the service faces was not treated as a risk The exploration during the Alpha was heavily focused on professional users and the service has been developed around analyst behaviours and mental models rather than a concept development for the public users. The team’s research had pointed out a simpler and more narrative-led way in for less technical users, but those needs were not taken forward The treatment of data interpretation is unresolved. The team explained that detailed narrative already has a home on GOV.UK and the service should not become a dumping ground for commentary. They also acknowledged that some light-touch interpretation needs to remain so that people can make sense of what they are looking at, and this is difficult when data is multidimensional and drillable, and publishers cannot write commentary for every combination. The panel agree this is hard, however, what’s missing is user insight to resolve it, particularly for members of the public who are the group most likely to need help reading dataAdvice to help the service team continually improve the service:
Consider the question of whether one service can meet both expert and public users' needs as a risk to be validated rather than a design intention Map out how different users navigate and search in different situations and for different tasks, and use that to explore ways into the data beyond search and a list view Design and test the plain language summaries that members of the public asked for during the Alpha, so that someone without statistical training can understand what the figures for their area are telling them Revisit whether the current scope boundary reflects how users understand the whole journey, or whether it reflects how the work is currently divided between organisations Updated DecisionThe service was rated green for point 2 of the Standard.
3. Provide a joined-up experience across all channels DecisionThe service was rated amber for point 3 of the Standard.
This is amber because:
Although the team identified the entry points to the service, the panel did not see how and where those arrivals lead to or what the experience looks like once someone lands from different routes. For example, when someone asked AI, would they be able to access the data searched and filtered already by AI or to the service landing screen The seamless journey between the service and GOV.UK is the part that matters most for the joined-up experience and is not yet designed. The team has started to address this by signposting to GOV.UK publications within the service, which is a good first step, but the return leg does not exist, and the interaction flows between the two have not been observed The assumption underlying the whole approach that separates the data from its interpretation will not break the experience remains largely untestedAdvice to help the service team continually improve the service:
Map out cross-channel journeys starting from a specific persona’s entry point and show what their experience looks like, identify any pain points or assumptions to achieve their goals, making sure users do not feel they are dropped between separate services Develop and test scenarios for both expert and members of the public from identifying what motivates them to use the service to the onwards journey. Validate or invalidate whether the signposting sufficiently meets user needs Shift your design focus from interactions to end to end flows, especially around unhappy paths and escalation routes for users when they face the dead-end Updated DecisionThe service was rated green for point 3 of the Standard.
4. Make the service simple to use DecisionThe service was rated amber for point 4 of the Standard.
This is amber because:
While the panel saw strong evidence of iterative improvements at the component level, including several refinements to the geography selection based on user feedback, there was less evidence of the same level of iteration across the end-to-end journey. The panel is not convinced that sufficient attention had been given to simplifying the overall user task over time Content design is a gap in developing this a simple to use service, which the team acknowledge. Specialist language remains a barrier for people who are not analysts. There is no record of how content has been iterated, and the examples offered in the session were given to show awareness of the problem rather than to demonstrate what work has been done to resolve the problemOptional advice to help the service team continually improve the service:
Look at how other government teams have approached similar data services and bring that back into your own design thinking Demonstrate how a whole task has been made simpler over rounds of testing, not only how individual components have improved Bring content design in Beta and test plain language alternatives and in-context explanations with people who are not analysts Keep a record of content decisions and how wording has changed in response to what users struggling with Updated DecisionThe service was rated green for point 4 of the Standard.
5. Make sure everyone can use the service DecisionThe service was rated amber for point 5 of the Standard.
This is amber because:
Issues already found have not been resolved. For example, the colour contrast in the charts and the underlying concern about the use of colour that was inherited from earlier design work have not been resolved Research with people who have access needs concentrated on cognitive needs and no one using assistive technology has yet to test the serviceAdvice to help the service team continually improve the service:
Build on the work done in alpha to identify potential users with access needs, and test with people using assistive technology Develop the assisted digital approach and make it clear how support will be offered Resolve the outstanding issues with colour in data visualisations and test the iterated version with users Arrange accessibility testing early in beta and act on what it finds Consider testing the service on different digital devices and off-line journeys if needed particularly by members of the public Updated DecisionThe service was rated green for point 5 of the Standard.
6. Have a multidisciplinary team DecisionThe service was rated green for point 6 of the Standard.
7. Use agile ways of working DecisionThe service was rated green for point 7 of the Standard.
8. Iterate and improve frequently DecisionThe service was rated green for point 8 of the Standard.
Optional advice to help the service team continually improve the service:
continue to adopt agile methodologies to highlight opportunities for improvements in the service a clear ‘owner’ for monitoring KPIs should be established going into beta. Though the team has a robust list of Key Performance Indicators (KPIs) with appropriate metrics for monitoring respond to feedback given in assessment and this report on user needs so they can better understand the needs of users and respond to changing them, going into beta. The beta team should reflect on the current scope of the project and the assumptions they have on the user needs, making sure their approach reflects the current needs of users of the service Review and re-write the riskiest assumptions regularly, not just once at the beginning of the project, be clear with what can validate or invalidate the assumptions, and share findings against the risks, so that the team and stakeholders can make informed decisions moving forward 9. Create a secure service which protects users’ privacy DecisionThe service was rated green for point 9 of the Standard.
The Find Public Health Data technical project team reviewed the current architecture and then provided a target technical architecture, software options analysis, authentication options (Public & Publisher), hosting options, API framework/design pattern and UI framework.
The team demonstrated that they understand how to manage risks at this stage of the project life cycle:
A threat modelling exercise has been conducted with known risks (41). These have been mitigated and 2 residual risks currently pending Security and privacy considerations for software options The security posture for the solution architecture considers Global and Regional Web Application Firewall (WAF) components The Transport Layer Security (TLS) is version 1.2 and above Protection against Open Worldwide Application Security Project (OWASP) Top 10 vulnerabilities Identity and access management for Publisher (Entra ID) and Public users (One Login) The service team is aware that a stable and supportable version of PostgreSQL should be provisioned for the project by the platform at Beta phase A multi-level access management to include MFA should be persisted to PostgreSQL database for Publisher teams accessing the data Data encryption at rest and in transit The application and infrastructure code should be scanned for vulnerabilities and consequent fixes where required prior to deploymentAt the Beta Phase, evidence for the above should be readily available for review.
10. Define what success looks like and publish performance data DecisionThe service was rated green for point 10 of the Standard.
Optional advice to help the service team continually improve the service:
The team has established a comprehensive set of key performance indicators (KPIs) and appropriate monitoring approaches for the private beta phase. While the team does not currently plan to employ or contract a dedicated performance analyst, instead distributing performance analysis responsibilities across suitably skilled members of the blended team, this approach should be kept under review as the service scales It is recommended that the team closely monitors the additional workload associated with KPI tracking, analysis and reporting during beta. Responsibility for which team member owns the monitoring of KPIs should be clearly established. This will help ensure that performance management responsibilities remain sustainable and do not adversely affect delivery capacity or the quality of insight generated. Should these responsibilities begin to place undue pressure on team members, the team should consider securing dedicated performance analysis resource to provide robust and consistent monitoring, support continuous improvement, and enable data-driven decision-making 11. Choose the right tools and technology DecisionThe service was rated green for point 11 of the Standard.
Advice to help the service team continually improve the service:
The service team demonstrated that they have reviewed and chosen tools driven mostly by baseline standards, namely, TCoP, Service Standards, Secure by Design and key non-functional requirements. They used these as guides for the technical requirements template The spikes that will be conducted in Beta will validate some of the choices made at Alpha phase 12. Make new source code open DecisionThe service was rated green for point 12 of the Standard.
Advice to help the service team continually improve the service:
For this phase of the project, there were no technical implementations with codebases for deployment. However, a GitHub repository has been provisioned for the project. At the Beta phase, it must be evident that the repository has been used for active development and deployment of the solution, with best practices maintained to ensure that there is parametrisation, with keys, secrets and certificates stored appropriately referenced in the scripts for example, not included in the codebase. 13. Use and contribute to open standards, common components and patterns DecisionThe service was rated green for point 13 of the Standard.
Advice to help the service team continually improve the service:
The Service team considered the use of open standards, common components and patterns for the next phase of the work. These considerations include:
The proposal to use One Login, which is a common component for authentication for public projects The use of Git as an Open-Source tool for GitHub The use of Open API specification – Open Source.For the Beta phase, the team should continually explore the use of open sources, common components and patterns. Where third-party software choices are made, it should be evident that there has been consideration of avoiding lock in with specific technologies. Finally, the technology governance should be robust, to include SMEs from architecture, including data, technical & security service management. As well as engineering and others. This is to ensure all aspects of governance have good coverage
14. Operate a reliable service DecisionThe service was rated green for point 14 of the Standard.
Advice to help the service team continually improve the service:
The team has demonstrated a good understanding of this assessment standard by carefully setting out the requirements and process of the selection of tools and technology for the project. For the beta phase, evidence to support the reliability of the tools and components selection should be available for review. This could be key metrics, graphs and outputs. Where initially selected tools are inadequate, metrics to support these findings should be available and pivoting to more appropriate tools. The observability solution should include monitoring and alerting capabilities and protective monitoring The team has set out the service performance KPI to include: cost per transaction, user satisfaction, completion rate, service take-up, usability, publisher satisfaction, accessibility and reliability. These performance KPIs for the service should be available for review at beta.https://digitalhealth.blog.gov.uk/2026/11/18/dhsc-find-public-health-data-alpha-reassessment/
seen at 14:52, 18 November in Digital health and social care.