Screening messaging V1.0.0
Introduction
Some screening programmes use the Digital Diagnostics & Pathology Messaging standards to return results to GP systems. Variant NHS004 of the Medical Service Report (MEDRPT) message was created to enable it to carry screening results.
In addition to the minor changes to the message definition, the system is required to identify NHS004 messages as ‘screening messages’ rather than pathology messages and to present them as such to users for processing.
Compliance and Assurance
For advice and support on assurance please contact businesspartners@nhs.net or visit https://digital.nhs.uk/services/nhs-business-partners
Requirements
Req ID | Requirement | Level |
|---|---|---|
| SRN1 | The system MUST support MIG variant NHS004 of the EDIFACT Laboratory Service Report (MEDRPT) message. | MUST |
| SRN2 | The system MUST perform the same validation checks (e.g. EDIFACT constructs, Patient, Receiving Organisation, sender/recipient identifiers, etc) on a NHS004 message as a NHS003 message with the exception of the clinical code validation check. | MUST |
| SRN3 | The system MUST comply with the requirements contained in the following document: Cancer Screening - eGP-Comms GP Software Supplier Requirements v4.1.doc | MUST |
| SRN4 | From time to time the authority will provide updates to terminology code list and associated terminology mapping tables contained in the ‘Cancer Screening - eGP-Comms GP Software Supplier Requirements v4.1.doc’ requirement document (see SRN3 above) Updates will be published as an addendum to the issued document and will additionally provide a schedule for implementation. Suppliers MUST be compliant with the updated code list aligned to the published schedule. The schedule will allow at least 3 months for implementation. | MUST |
Documentation
Dependencies
Creating a compliant implementation requires implementing the following dependent interface standards:
Messaging Exchange for Social Care and Health (MESH)