Where appropriate, our RESTful APIs follow the HL7 FHIR standard (pronounced 'fire').
FHIR (Fast Healthcare Interoperability Resources) is a global standard for health care data exchange. It is the successor to the HL7 V3 standard.
- includes specific resources for the health care domain, such as Patient and Observation, and also defines common data items for those resources
- can be adapted for local requirements using profiles, extensions, terminologies and more
- defines rules for how to access resources via RESTful APIs
- can also be used for messaging and document solutions
FHIR has been adapted for use in England as follows:
- CareConnect is a set of England-centric FHIR profiles built on FHIR Release 3
- FHIR UK Core is a set of UK-centric FHIR profiles built on FHIR Release 4
You don’t need to know much about FHIR to use our APIs - FHIR APIs are just RESTful APIs that follow specific rules. In particular:
- resource names are capitalised and singular, for example /Patient not /patients
- array names are singular, for example line not lines for address lines
- data items that are country-specific and thus not included in the FHIR global base resources are usually wrapped in an extension object
Some of our older APIs conform to the HL7 Version 3 standard.
HL7 V3 is a global standard for health care data exchange. It is the predecessor to the FHIR standard.
- synchronous APIs, using SOAP and XML
- asynchronous APIs, using ebXML
Be aware that using our HL7 V3 APIs can be hard work because:
- the documentation is quite hard to navigate
- the message structure is complex
- for asynchronous APIs you need to build a Message Handling System to receive inbound messages
If there is a suitable RESTful API available, we recommend you use that instead.
Learn how to integrate with our HL7 V3 APIs by reading:
Message Handling Service adaptor
To remove the complexity of building your own Message Handling System, we offer a pre-assured, client side Message Handling Service adaptor that you can integrate into your own infrastructure.
Spine Security Proxy (SSP)
Some of our synchronous APIs are available via the Spine Security Proxy (SSP). We use SSP where the responding system is another local system. Requests and responses go via SSP instead because this makes it easier for responding systems - they only have to deal with requests from a single place.
To make sure all systems can talk to one another, we (NHS Digital) write the API specifications for SSP APIs, even though we don’t own the responding systems.
SSP APIs are generally FHIR APIs, the only difference being that SSP sits in the middle, routing traffic and making security easier.
Some of our asynchronous APIs use MESH (Message Exchange for Social care and Health). MESH is an NHS Digital messaging hub that allows systems to send and receive asynchronous messages. MESH replaced an older system called DTS.
With MESH, sending systems send messages to a messaging hub and the messages are placed on the recipient’s “queue”. Receiving systems must constantly check the messaging hub for incoming messages on their queue. This is known as a “push” or “polling” mechanism.
MESH is built as a RESTful API with endpoints for sending messages and for polling for received messages.
The message payload format depends on the specific API. For example, pathology messages use HL7 v2 EDIFACT, whereas transfer of care messages use FHIR.
Last edited: 16 September 2021 11:35 am