We have detected that you are using Internet Explorer to visit this website. Internet Explorer is now being phased out by Microsoft. As a result, NHS Digital no longer supports any version of Internet Explorer for our web-based products, as it involves considerable extra effort and expense, which cannot be justified from public funds. Some features on this site will not work. You should use a modern browser such as Edge, Chrome, Firefox, or Safari. If you have difficulty installing or accessing a different browser, contact your IT support team.
Creating a new NHS England: Health Education England, NHS Digital and NHS England have merged. More about the merger.
Personal Demographics Service - SMSP API - use this if you want to get PDS data without an authenticated end user (no smartcard required). It is, however, read-only and searches are limited to a single result.
Spine Directory Service - LDAP API - use this to access data in the Spine using Directory Service (SDS), our LDAP API, which provides details of organisations, people and systems registered with the Spine.
To remove the complexity of building your own Message Handling System, we offer a pre-assured, client side MHS adaptor that you can integrate into your own infrastructure.
It makes it easier to connect to the NHS Spine and perform business operations by exposing a RESTful API that conforms to the HL7 V3 standard.
GP2GP Sending Adaptor (In Development)
If you are building a system that receives EHR (Electronic Health Record) requests and responds with HL7 V3 EHR messages, you can use our GP2GP Sending Adaptor to handle the requests and map FHIR records to the desired HL7 V3 output. This is also compatible with the Message Handling System (MHS).
GP2GP Receiving Adaptor (In Development)
If you are building a system that creates EHR requests and needs to convert the responses to FHIR from HL7 V3, you can use our GP2GP Receiving Adaptor to the generate the requests and convert the response to the desired FHIR output. This is also compatible with the Message Handling System (MHS).
For some activities, the end user must be authorised to perform that activity.
The integration itself does not perform any authorisation checks. Rather, the calling system is expected to perform them. The authorisation rules are specified in our national Role Based Access Control (RBAC) database.