Search loading...


Explore and Make use of Nationally Defined Messaging APIs



NHS Digital can provide conformance certification for sending and receiving systems processing FHIR Documents.

Verification and Validation

Sending and receiving systems are required to validate documents conform to their Message Specifications.

ID Description Sender Receiver
FHIR-V&V-01 Sending and Receiving systems MUST provide a means to assure the validity of the FHIR document. Y Y
1. If this validation fails, the system MUST log the fault in the application or system logs as appropriate.
ID Description Sender Receiver
FHIR-V&V-02 Sending systems SHOULD provide facilities (e.g. a ‘verification’ step) to ensure the content of the FHIR Document is checked/verified by the document author, or other approved user, prior to the sending of the Document. Y N

Use of Coded Clinical Content

Coded entries are the mechanism used to exchange structured clinical information between systems. These are common, agreed structures for clinical data representation, and are the cornerstone of clinical data interoperability. A Coded entry is one or more Resources that are referenced from the FHIR element Composition.section.entry.Reference.

ID Description Sender Receiver
FHIR-CC-01 If a local system is not able to construct a coded entry to represent coded clinical information in a document, then the Payload Implementation Guidance will define the processing rules. Y N
ID Description Sender Receiver
FHIR-CC-02 Coded clinical content within documents MUST validate against the Payload Implementation Guidance and specified profiles. Y N
ID Description Sender Receiver
FHIR-CC-03 All clinical content within coded entries of a document MUST also be represented within the text sections of that document. Y N
ID Description Sender Receiver
FHIR-CC-04 References to coded entries within a document MUST be to resources within the same document. Y N
Tags: fhir

All content is available under the Open Government Licence v3.0, except where otherwise stated