Skip to main content

A to Z of developer resources

Find guidance and resources for developers integrating NHS services. You might also be interested in our API catalogue.

Search A-Z

Search A-Z


D

Diagnostic Data Service: Guidance for developers

Diagnostic Data Service developer resources


Document header - Clinical Document Architecture on FHIR

DEPRECATED: Generic document header FHIR specification


E

EPS: Guidance for developers

We've published a range of developer guides and materials for the Electronic Prescription Service, including information on apps, identifiers, APIs and service integration.


F

Falsified Medicines Directive implementation toolkits

The Falsified Medicines Directive (FMD) is a set of rules to protect people from fake medicines in the European Union (EU). It includes additional anti-tampering security on packaging, and tracking of medicines using a unique identifier, like a barcode.


FHIR policy introduction

Policies for the use of HL7 FHIR standards in the NHS in England.


FHIR vital signs profiles

View a table mapping "magic values" (LOINC codes) to SNOMED CT values used in FHIR STU3 in the UK.


G

Glossary of developer terms

Find a list of NHS developer terms and abbreviations, along with their definitions. 


I

Integrated Urgent Care Domain Message Specification

The Integrated Urgent Care Domain Message Specification is an agreed set of standards for sending information between providers.  It is designed to support services such as NHS 111, NHS 111 online, and the repeat caller service.


Interoperability Toolkit: Guidance for developers

A collection of software developer resources.


M

Message Implementation Manuals (MiMs)

The Message Implementation Manual (MiM) is the formal specification of the HL7 V3 messaging on the Spine.


N

NHSmail applications guide

Guidance on how to configure local mail-enabled applications to work with NHSmail.


NHS Number client

Find out about our simple client and java code library, designed to make it easier to model NHS Numbers in software.


S

Signatures and public keys

How to use signature and the public key to check a checksum release.


Spine Core FHIR API Framework

The Spine Core FHIR API Framework provides common behaviours and services used across FHIR APIs delivered on Spine. This specification also covers other Spine services that complement or are used alongside Spine FHIR APIs.


Spine Mini Services APIs

A brief introduction to getting started with the Spine mini services APIs.


Structured headings - Clinical Document Architecture

The generic Structured Headings Clinical Document Architecture (CDA) model is a large “CDA Refined Message Information Model (RMIM)” that can be used as the basis to create specific profiles. It consists of a Common CDA Header, Common Library of CDA Sections (PRSB, plus others) and a Common Library of CDA Coded Entries (PRSB assured plus other legacy ones). The generic Structured Headings CDA model itself is not meant for implementation, but is constrained by a profile specification that allows the model to be constrained to specific use cases. This profile specification is rule based and consists of a series of assertions against the base model, for example, this details which section can or cannot be present, which coded entries can or cannot be present, and so on.


T

Transaction Messaging Service Java implementation

TMS Java implementation contains a set of tools for network operations on Spine.


Transaction Messaging Service Microsoft .NET implementation

This package contains an implementation of a Spine message handler written in C# for the Microsoft .Net 4.0 platform, provided under the Apache 2.0 licence.