Medicus Standards
- Supplier name
- Medicus Health Limited
- Solution ID
-
10124-001
- Contracting vehicle
-
Tech Innovation
Standards and solution categories
Standards describe the technical specifications or operating conditions required for a solution to be published on the Buying Catalogue.
Solution categories are assigned to supplier solutions based on risk and determine the level of assurance that suppliers complete.
More information about solution categories (opens in a new tab)
This is how Medicus has performed against the relevant Standards:
Standards not fully met
Any Standard that has not been fully met will have a status of ‘in progress’ and the catalogue solution will be subject to a Compliance Work-off Plan.
This means the supplier has agreed to complete any outstanding work to meet the Standard within an agreed timeframe.
Use the ‘view details’ link to find more information about any outstanding Work-off Plans.
Overarching Standards
These Standards must be fully met by all catalogue solutions within an agreed timeframe
| Standard | Description | Status | |
|---|---|---|---|
| Baseline Assurance Standard | A minimum set of essential requirements from the Overarching Standards. Following assurance of the BAS, Solutions are required to become fully compliant with all Overarching Standards to remain published on the Buying Catalogue. | StatusFully met | |
| Business Continuity & Disaster Recovery | Ensures that Suppliers Solutions are supported by robust business continuity plans and disaster recovery measures. | StatusFully met | |
| Clinical Safety | Supports the management of clinical risk and Patient safety. | StatusFully met | |
| Commercial | This Standard underpins all commercial activity relating to the Catalogue. It does this by defining a number of rules governing the commercial relationship of relevant parties and by setting out standards of behaviour and principles of access to data and services charges. | StatusFully met | |
| Data Migration | Supports the secure migration of Practice data between Solutions. | StatusFully met | |
| Data Standards | Defines detailed technical standards for the storage, management and organisation of data and specifies standardised reference data, terminology and codes. | StatusFully met | |
| Hosting & Infrastructure | Supports best practices for infrastructure and hosting of systems. For example, ensuring that systems are cost effective, secure, reliable, resilient, safe, manageable and energy efficient. | StatusFully met | |
| Information Governance | Supports the controls needed to ensure that Special Category Data is kept confidential, is accurate and is available to authorised users when required. | StatusFully met | |
| Interoperability Standard | Defines a comprehensive set of standards, interfaces and protocols that Solutions and systems will use when interoperating. | StatusFully met | |
| Non-Functional Questions | Enables the Authority to assess the risk associated with the Compliance Assessment of the Solution against appropriate Overarching Standards. | StatusFully met | |
| Primary Care Technology Innovation Standard | As part of our move to modernise core clinical systems for Primary Care, NHS Digital have been engaging Suppliers around our Modern Technology Standards. These standards and the NHS Architecture Principles lay out the future ways of working and technology we want to see developing to serve the needs of Primary Care and simplify the complexity of healthcare systems provision. | StatusFully met | |
| Service Management | Supports suppliers in the delivery and management of services that support and provide their Solutions. | StatusFully met | |
| Testing | Ensures that Suppliers' software delivery test processes are of sufficient quality and rigour. | StatusFully met | |
| Training | Defines the training activities and collateral expected from Suppliers to support the buyers and users of their Solutions. | StatusFully met |
Other Standards
These Standards are relevant to solutions that meet particular Capabilities
| Standard | Description | Status | Action |
|---|---|---|---|
| 111 | Supports receipt and consumption of data sent by 111 provider systems for transfer of care to the GP Practice. | StatusFully met | |
| Authentication and Access | Supports user authentication and access controls to NHS systems and national services. | StatusFully met | |
| Booking and Referral Standard (BaRS) | Supports the System Supplier with a set of instructions, rules and guidance on how to use the building blocks of FHIR to digitise workflows. BaRS offers a universal standard way to digitise workflows that support all cross service Patient journeys in the NHS. | StatusIn progress | View details |
| Clinical Document Architecture (CDA) | Defines the standard for exchange of clinical information between systems. | StatusFully met | |
| Digital Medicines and Pharmacy FHIR Payload | Supports transmission of medicines information between care settings. | StatusIn progress | View details |
| e-Referrals Service (eRS) | Supports electronic booking with a choice of place, date and time for hospital or clinic appointments. | StatusFully met | |
| Electronic Prescription Service (EPS) - Prescribing | Supports sending prescriptions electronically to a dispenser (such as a pharmacy) of the Patient's choice. | StatusFully met | |
| Electronic Yellow Card Reporting | Supports electronic reporting of suspected adverse drug reactions (ADRs). | StatusFully met | |
| Ensures that email services within solutions are securely configured. | StatusFully met | ||
| eMED3 (Fit Notes) | Supports the creation of eMED3 data, its integration into the Patient Record, printing or issuing of MED3 fit note certificates and extraction of data to NHS Digital. | StatusFully met | |
| General Practice Appointments Data Reporting | Supports the collection and submission to the Authority of Appointment data to support capacity planning and management. | StatusFully met | |
| Generic FHIR Receiver | Supports the receipt of incoming ITK3 FHIR messages | StatusFully met | |
| GP Connect (Patient Facing) Access Record | The GP Connect (Patient Facing) Access Record - FHIR API is used to access structured and coded information from a Patient's GP Practice Electronic Patient Record (EPR) to be used in a Patient facing Solution. The API accesses GP Foundation Supplier Solutions and provides a consistent interface and data model. | StatusFully met | |
| GP Connect (Patient Facing) Prescriptions | The GP Connect (Patient Facing) Prescriptions - FHIR API is used to enable Patients to view all their current medication and manage requests for a new instance of a Repeat Prescription using a Patient facing Solution. | StatusFully met | |
| GP Connect (Patient Facing) User Permissions | The GP Connect (Patient Facing) User Permissions API is used to enable Patient Facing Solutions to access the permissions held within the GP Foundation Supplier Solution for Patients relating to the Prescription Ordering and View Record Citizen Services. | StatusFully met | |
| GP Connect Access Record HTML | The GP Connect Access Record HTML API provides Health and Care Professionals with read only access to a Patient’s GP Practice Electronic Patient Record (EPR) by requesting sections or headings. | StatusFully met | |
| GP Connect Access Record Structured | The GP Connect Access Record Structured API enables a Solution to request and consume a Patient’s GP Practice Electronic Patient Record (EPR) in a structured and coded format that is machine readable. | StatusFully met | |
| GP Connect Send Document | GP Connect Send Document provides a simple and standardised means of sending a document, such as a PDF, an image, or HTML file to a GP Practice Receiver Solution. | StatusFully met | |
| GP Connect Update Record | GP Connect Update Record provides a simple and standardised means for a Sender Solution to send structured data to a GP Practice Receiver Solution so that it can be added to a Patient’s GP Practice Electronic Patient Record (EPR). | StatusIn progress | View details |
| GP2GP | The GP2GP record transfer mechanism enables an Electronic Patient's Record (EPR) to be electronically transferred directly and securely when they move from one Practice to another. | StatusIn progress | |
| GPES Data Extraction | Supports secure collection of information from General Practices and its delivery to approved organisations. | StatusFully met | |
| IM1 - Interface Mechanism | IM1 is a mechanism for accessing data held in GP Systems | StatusIn progress | View details |
| Interoperability Toolkit (ITK) | Supports interoperability within and between solutions with common specifications, frameworks and implementation guides. | StatusFully met | |
| Messaging Exchange for Social Care and Health (MESH) | Supports the secure transfer of clinical and non clinical data across health and social care. | StatusFully met | |
| Multicast Notification Service (MNS) | The Multicast Notification Service (MNS) allows digital health and care services to publish and receive Patient-related state changes from a single centralised system. | StatusFully met | |
| National Data Opt-Out | The National Data Opt-Out Service has been established to ensure that a mechanism is developed and available for Health and Social Care organisations to use that will enable a Patient’s preference to be honoured accordingly. | StatusFully met | |
| National Events Management Service (NEMS) | The National Events Management Service (NEMS) allows digital health and care services to notify other digital services that an ‘event’ has occurred, using ‘publish-subscribe’ messages. | StatusFully met | |
| NHAIS HA/GP Links | Supports the management of Patient registration and demographic information with National Health Application and Infrastructure Services. | StatusFully met | |
| NHS Login Service | Supports the verification of Citizens and services requesting access to digital health records. | StatusFully met | |
| Personal Demographics Service (PDS) | Supports Solution integration with the Personal Demographics Service which stores Patient details. | StatusFully met | |
| Primary Care Clinical Terminology Usage Report | Supports the collection and submission to NHS digital of information about usage of clinical coded terms. | StatusFully met | |
| Register with a GP Surgery Service | The Register with a GP Surgery Service allows Patients to submit registration application information and for digital health and care services to retrieve this information submitted by Patients. | StatusIn progress | View details |
| Summary Care Record (SCR) | Supports the management of Summary Care Record data and staff access to those data. | StatusFully met | |
| Transfer of Care FHIR Payload | Introduction of MVP FHIR messaging for Transfer of Care. Specification v0.7 | StatusIn progress | |
| Vacination Extract | The Vaccination Extract specifies the flow of vaccination-related information from healthcare settings to the Authority. | StatusFully met | |
| Validated Relationship Service | The Validated Relationship Service - FHIR API enables a Solution to access the Validated Relationship Service. This is the national electronic database of relationships that have been verified for the purpose of enabling individuals to access healthcare services on behalf of those they care for. The relationships held by this service are strictly for the purpose of enabling access to healthcare services. | StatusFully met |
Solution information last reviewed: 14 May 2025