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 and integration catalogue.

Search A-Z

Search A-Z

E

EPS onboarding guidance for suppliers

Find our onboarding and assurance requirements, developer guidance and instructions on how to integrate the Electronic Prescription Service (EPS) and the national patient prescription tracking service.

F

Falsified Medicines Directive implementation toolkits

Guidance toolkits developed for healthcare providers to help prepare for the implementation of the Falsified Medicines Directive.

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 was an agreed set of standards for sending information between providers.  It was 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.

K

Keep your software secure

Learn about key concepts and practices you need to secure your application (or software)

M

Message Implementation Manuals (MiMs)

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

N

NHS Data Standards Directory

A directory of nationally recognised standards for use in health and adult social care

NHSmail applications guide

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

P

Pathology standards implementation

Learn about the terminology and message specification required to meet the DAPB 4101 Pathology and Laboratory Medicine Reporting Information Standard and the benefits its implementation will bring.

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.

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.