TGS


DHSC Search Medical Product Evidence Alpha Reassessment

From: DHSCAssessment date: 19/02/2026 Reassessment date: 04/11/2026Stage: Alpha Result: Green at reassessmentService provider:  DHSC

Service description  Project Compass will present clinical evaluations and procurement artefacts from a variety of trusted sources such as NICE, NHS Supply Chain, Orthopaedic Data Evaluation Panel (ODEP), National Joint Registry (NJR) and other users in NHS Trusts to help procurement professionals and clinicians to make informed procurement decisions.   The availability of this evaluative documentation will promote the adoption of high-value innovations across the system and promote value-based procurement best practice.   The focus of the alpha phase has been to validate the need for the service, understand and articulate user needs, and provide a technical specification for the Beta phase.  Service information goes all the way down to individual items and services from a variety of suppliers. “Reviews” from previous users of the suppliers are included.  Service users 

This service is for DHSC/NHSE employees, those mainly focussed on procurement. 

Anticipated users of the service are: 

Procurement Professionals  Clinicians  Suppliers  

Procurement Professionals will access the service to review evaluations, to gain insight into the best products available, compare products based on clinical outcomes, understand long-term value, rather than price alone to make informed value-based procurement decisions.  Procurement Professionals are also expected to provide their own procurement documentation and contact information to help foster collaboration within their profession and assist clinicians. 

Clinicians will access the service to review evaluations to gain an insight into products that are used by other NHS Trusts, understand the efficiency of products and compare products to assist Procurement Professionals with the choice of devices. Clinicians will also be expected to upload clinical evaluations and provide contact information to foster collaboration. 

Suppliers will access the service to review evaluative documents relating to their products. 

Things the service team has done well:   The service team has all the skills needed to carry out the Alpha phase and has produced a prototype, extensive documentation and information.  The panel was impressed that the service team has carried out extensive engagement with colleagues within DHSC, NHSE, and the wider NHS organisation.   User Research: the team has carried out comprehensive and inclusive user research, validating and evidencing user needs, pain points and behaviours.   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  Decision 

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

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

Monitor the response rate to the impact and satisfaction surveys and respond proactively to low response rate if necessary  Continue to include users with access needs and varied digital confidence in future user research  2. Solve a whole problem for users  Decision 

The service was rated green for point 2 of the Standard.  The team demonstrated a strong understanding of how Project Compass fits into the broader ecosystem of NHS procurement and the "whole problem" of value-based decision-making. Rather than acting as an isolated tool, the service is designed to bridge the gap between high-level clinical evidence and real-world Trust experience.  

Integration and Resilience The team has carefully considered the technical dependencies on external systems, such as the DHSC Product Information Management (PIM) Service and the Orthopaedic Data Evaluation Panel (ODEP). They confirmed that the service does not rely on these data sources at runtime; instead, data is batched into the system.  Data Continuity A key strength of the design is how it handles data decay or the removal of external products from catalogues. Because NHS users "enrich" product records with their own evaluations and trials, the team maintains a record of the data even if the original source disappears. This ensures that past procurement expertise is not lost when products are discontinued.  Addressing the Information Gap Research confirmed that users struggle with interpreting "highly clinical" central evidence. The service solves this by facilitating peer-to-peer conversations and hosting a directory of who has procured specific products, effectively joining up two key aspects of this ecosystem.   

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

Formalise the Support Model While the technical resilience is high, the "human" support model for when data is inaccurate or missing from upstream sources needs to be fully mapped to ensure users aren't left at a dead end.  Test the Full Lifecycle In Private Beta, focus research on how the service handles the "Monitor" phase of the journey, ensuring that data being batched in remains relevant for long-term clinical outcome tracking.  3. Provide a joined-up experience across all channels  Decision 

The service was rated green for point 3 of the Standard.  The team has established clear entry points for the service through policy initiatives, digital service signposting (such as NHS Supply Chain), and community engagement. However, the automated communication journey remains largely untested. 

End-to-End Journey While the service triggers automated emails for sign-up verifications and peer-to-peer contact alerts, the team acknowledged that the content, timing, and frequency of these notifications have not yet been validated with users. 

Offline Integration There is a clear "Contact support" call-to-action, but the specific design of the offline support journey and how user feedback from support tickets will iterate the service design is not yet fully defined.  

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

Conduct dedicated user research on the end-to-end notification journey to ensure "Impact" summaries (using the team’s performance framework) provide value without contributing to notification fatigue.  Map the "human" help desk journey to ensure seamless integration between digital friction and offline resolution.  4. Make the service simple to use  Decision 

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

The team demonstrated strong evidence of iterative design on the homepage to reduce cognitive load and define a clearer service proposition. 

Homepage Iteration The team moved from an initial content-heavy approach to a leaner, modular design that prioritised key unmet needs, such as peer contact support alongside formal evidence.   Design Consistency The service utilises the NHS design system throughout, including standard text boxes and NHS Cards, ensuring a familiar interface for users.  Search and Filters User testing showed that filters are generally well-understood. The team intentionally used standard components for category-level filtering originally, prioritising accurate results over complex interaction functionality in Alpha. This aligned to current known mental models and design best practice of progressive enhancement.  

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

The team acknowledge that product pages remain information dense. Prioritise research into the hierarchy of these pages for example, cost vs. technical details) to ensure they meet specific user needs during procurement.   Tree testing and card sorting to validate the Information Architecture (IA) and navigation labels.  5. Make sure everyone can use the service   Decision 

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

The team has been transparent regarding the significant accessibility barriers identified in research, specifically the challenges legacy document formats (PDFs, Excel) pose for users with screen readers or voice control software. 

This is amber because:  

Document-Centric Risk The team is operating within a challenging landscape where much of the service's primary value is currently held in unstandardised document formats provided by external partners. While the team does not have direct control over how these documents are authored at the source, they have been proactive in identifying the resulting accessibility risks for users of assistive technology  Navigation Assistant Anchor links have been added to long product pages as navigation assistants, though the team recognises these can create separate accessibility issues if not implemented carefully 

Advice to help the service team continually improve the service: 

Strategic Influence Rather than the team carrying the full weight of this risk, they plan to and should continue to work with policy leads to influence the standardisation of MedTech evaluations across the NHS at the source  Exploration of AI The panel encourage the team to explore ways they might use AI in the service, for example to extract key metadata into accessible HTML summaries at scale. The team acknowledged this will require SME knowledge and critical governance exploration - but may help to reduce time burdens across the ecosystem if implemented carefully.  Accessibility review and external expertise The team have taken steps to strengthen accessibility, consulting an external provider after initial challenges in locating suitable support. Lead Assessor from the NHS England accessibility team has been identified as a key contact. The Service Team Delivery Manager will follow up with him to secure a formal review and further guidance.  Updated Decision 04/11/2026 

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

Advice to help the service team continually improve the service: 

Continue to monitor the volume and range of documentation contributed by users throughout private beta. Use appropriate performance measures to understand whether these features and the proposed incentives are delivering value, encouraging ongoing engagement and meeting user needs.  Continue to test the finding that users need to review the full document, rather than a consistent set of extracted facts. Explore alternative ways of helping users understand the key information and wider context of the evidence. Assess whether this is impacted with more participants, different user groups, or with different jobs to be done.  As research continues through beta, test whether information needs and behaviours remain consistent across a broader range of participants, user groups and jobs to be done. Continue to research with the academic user group during private beta to further test the proposition, including how they contribute to and benefit from the service. Consider how best to onboard and incentivise academic partners during private beta and use these findings to inform the service’s development.  Continue to measure the value the service provides to users and how this develops over time. Use the evidence to understand what drives adoption and repeat engagement, rather than assuming that bringing information together in one place will be sufficient to attract and retain users.  6. Have a multidisciplinary team  Decision 

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

This is amber because:  

The team have highlighted most of the team will roll of at the end of Alpha. The team must ensure continuity of build standards and a robust handover should the tender result in a new supplier to avoid minimal impact to the service  Updated Decision 04/11/2026 

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. 

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

Continue with Agile approach, perhaps include refinement sessions if not already in place  Recommend a new sprint 0 for the beta phase and include training for new contract team members if applies  8. Iterate and improve frequently  Decision 

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

User-Led Changes Page headings and content were revised based on direct feedback to ensure the service proposition was immediately graspable.   Future Planning The team has a clear research plan for Private Beta to address outstanding risks, including filter interactions and naming consistency.   Service Naming The team is actively testing task-oriented names to resolve existing ambiguity between "Compass" and descriptive titles like "Search medical technology evaluations". 

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

Address Innovation Bias Test design iterations that provide confidence in new products without over-relying on volume metrics (like number of documents) that may potentially naturally favour incumbent suppliers.   Finalise Service Name: Formalise the service name based on Beta testing results to ensure discoverability and clarity for newer users.  9. Create a secure service which protects users’ privacy  Decision 

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

Advice to help the service team improve the service: 

The service did confirm that Personal Identifiable Information (PII) is collected at minimal levels. There is also commercial information that can be managed by a Role Based Access Control (RBAC). However, not having any technical controls for managing PIIs is a risk to the project irrespective of the minimal levels of collection. In Beta, there should be technical controls to manage PII e.g. Anonymisation – masking policies, full redaction or native Data Loss Prevention (DLP) functionality   Login access for non-NHS & DHSC users should be finalised in the Beta phase  Consider both infrastructure and application vulnerability scan solutions to improve the security posture of the service. Pipeline scans for infrastructure build such as Checkov and Application scan e.g. SonarQube or alternatives should be considered and implemented in the Private Beta phase  A detailed threat modelling and controls implemented in the next phase  10. Define what success looks like and publish performance data  Decision 

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

Advice to help the service team improve the service: 

The test strategy should include performance tests to ensure the service is performant and identify areas of improvements. In addition, the metrics should guide the service through put, scalability and response times  The performance metrics should be available for review at the Private Beta phase  11. Choose the right tools and technology  Decision 

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

Advice to help the service team continually improve the service:  

The team presented a selection of tools that possesses known capabilities and used widely with NHS & DHSC projects. These include NHS Login, NHS Notifications, NHS Design Systems etc. However, integrating these technologies successfully is key to the success of the project  It is imperative that both PIM data source and DAC hosting are ready in-time for the next phase of the project  The integration of PIM Data with the Compass PostgreSQL is also key to the success of the project. The integration should be carefully planned and implemented in the next phase  The tool for service monitoring and alerting should be identified and implemented in the Private Beta. There are several options to include platform native solutions  The data matching through fuzzy logic should be evidenced in the next phase  12. Make new source code open  Decision 

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

Advice to help the service team continually improve the service: 

The project team provided a link and access to the project GitHub/Lab repository. In the next phase, it should be evidence that the repository has been actively used for the development and deployment of the Beta solution  13. Use and contribute to open standards, common components and patterns  Decision 

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

Advice to help the service team improve the service: 

The service team should explore the use of open standards and common components pattern in the Beta Phase Manufacture Product Code (MPC) is a proprietary identifier used by supply chains and companies Unique Device Identification (UDI) is a regulatory driven framework 14. Operate a reliable service  Decision 

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

Advice to help the service team continually improve the service: 

The reliable service considerations for the Beta phase should be implemented and evidenced in the next phase.

https://digitalhealth.blog.gov.uk/2026/11/18/dhsc-search-medical-product-evidence-alpha-reassessment/

seen at 18:39, 18 November in Digital health and social care.