Ambulance Domain Message Specification

This specification contains details of message definitions and interactions required to support Ambulance messaging.

Child Health Data Sharing Domain Message Specification

This specification supports the sharing of child health records, for example to support the eRedbook initiative.

Child Protection Information Sharing Domain Message Specification

This specification contains details of message definitions and interactions required to support the rollout of the Child Protection Information Sharing (CP-IS) system.

A Release Candidate (RC) designates the document as being available for production build purposes, and available for First of Type deployment. Accreditation to this specification is available, but it should be noted that there may be a need to incorporate minor amendments when the specification reaches Final status.

Child Screening Domain Message Specification Pack

This specification details the message definitions and interactions required to support the Child Screening work stream.

Crisis Care Extract Domain Message Specification

This specification contains details of message definitions and interactions required for Crisis Care Extract messaging to support the sharing of care plans for urgent and emergency care.

Discharge Domain Message Specification

Please contact the Interoperability Standards Service for the latest information about this.

Electronic Prescription Service Domain Message Specification

Electronic Prescription Service enables prescribers - such as GPs and practice nurses - to send prescriptions electronically to a dispenser (such as a pharmacy) of the patient's choice. This makes the prescribing and dispensing process more efficient and convenient for patients and staff.

Emergency Department Domain Message Specification

Please contact the Interoperability Standards Service for the latest information about this.

End of Life Domain Message Specification

This specification contains details of message definitions and interactions required to support the End of Life QIPP work stream.

FGM RIS - Domain Message Specification

The FGM RIS Domain Message Specification contains details of FHIR message definitions and interactions required to support the rollout of the FGM Risk Indication System NHS Spine 2 National Service interface.

Health Protection Electronic Notification (HPEN) Domain Message Specification

This specification enables the electronic notification of notifiable diseases from primary care to Public Health England.

Interoperability Toolkit - TMS Transport

This document provides the requirements for ITK Accredited Systems to nationally exchange messages via the National Spine Transaction Messaging System.

Interoperability Toolkit XDS Adapter

ITK Cross Enterprise Document Sharing (XDS) Adapter - provides the requirements for ITK Accredited Systems to interact with an IHE Registry/Repository.

Should you wish to comment on this specification or for any content enquiries, please email HSCIC Interoperability Team

ITK Accreditation

Please note that content for this pack is no longer published on this website. ITK Accreditation information can now be found on the NHS Developer Network

The Interoperability Toolkit (ITK) Accreditation pack contains tools and guidance for attaining accreditation to the ITK Standard. It is applicable to all System Suppliers wishing to seek accreditation.

In order to attain ITK Accreditation, a vendor must demonstrate the technical conformance of their product with respect to the ITK requirements specifications by submitting evidences of this conformance to HSCIC for review. This will be achieved through use of the ITK Toolkit Workbench, along with completion of the Supplier Certified Requirements Coverage check list and by providing supporting evidence. All successful Accreditations are listed within the ITK Accreditation Catalogue.

ITK Architecture

These documents are intended for a mixed technical audience, specifically those intending to develop ITK Accredited Systems, as well as those in the Health and Social Care Architecture communities.

There are eight documents in two categories. The first part provides an overview of both the ITK and ITK Accreditation. The second part consists of six documents and covers the architectural requirements for building ITK Clients, Hosts and Middleware the Distribution Envelope, Transports and Addressing and the three different types of ITK transport: Web Service (WS), Data Transfer Service (DTS) and Transaction Messaging Service (TMS).

ITK Core

The Core contains help and guidance on the artefacts and concepts that are shared across ITK implementations. This pack contains service definitions that are used with all ITK transport options. For Web Services, the Core also contains technical artefacts such as WSDL files.

The Distribution Envelop is explained in detail in terms of its elements and attributes, with a schema file and several examples also included. The acknowledgement framework is outlined, with examples and schema for the ITK infrastructure Acknowledgement and ITK Business Acknowledgement.

Finally, the Core explains ITK correspondence metadata, including schema and examples.

ITK Spine Mini Service

The technical implementation to connect to SPINE is relatively intricate. The ITK Spine Mini Services have been created to provide a simpler route to access national services.

The Spine Mini Services specifications define how to connect to NHS National Services, commonly known as the Spine. Essentially these are a set of specifications to enable suppliers of third party software to provide solutions for a greatly simplified interface for accessing a subset of the SPINE services e.g. PDS, SCR. The intent is to lower the “barrier to entry” to the SPINE.

The Spine Mini Service Provider pack contains: Common Client Requirements, Common Provider Requirements along with specific requirements associated with the particular National Service being accessed. Currently this pack contains specific requirements for accessing Patient Demographics Service (PDS) and is being enriched to contain additional specifications for accessing other National Services e.g. Summary Care Record (SCR).

ITK Trust Operating Model

The Trust Operating Model is an integral part of the Interoperability Toolkit. It details the Trusts’ responsibilities for Locally Assured Systems and Spine Mini Service compliant systems.

The primary audience for the Trust Operating Model are project teams working for a deploying organisation who are responsible for the runtime requirements of the implementation. Suppliers are envisaged as a secondary audience for the Trust Operating Model documentation.

The documentation has two categories (i) Guidance and (ii) Governance and these are more relevant to the Project Manager and technical team within a deploying organisation. Senior Management may find the overview document relevant, and may also wish to familiarise themselves with the information on Governance and Stakeholders.

NHS 111 Domain Message Specification

NHS 111 Domain Message Specification contains details of message definitions and interactions required to support the national rollout of NHS 111.

NHS CP-IS Spine Mini Service Domain Message Specification

This specification contains details of message definitions and interactions required to support the rollout of the Child Protection Information Sharing (CP-IS) Spine Mini Service.

NHS Interoperability Toolkit CDA Functional Requirements

NHS Interoperability Toolkit CDA Functional Requirements This contains the requirements for systems sending or receiving messages containing NHS Connecting for Health published message specifications for CDA Documents (e.g. Discharge, Out Patient, A&E, OOH and Ambulance Reports). It covers the handling of CDA Documents by clinical applications and the processing and transmission of these by Message Handling Systems between parties over a variety of transports.

*This pack must be used in conjunction with the contents of the NHS Interoperability Toolkit Core pack and the NHS Interoperability Toolkit Correspondence pack.

For all content enquires, please email ITK team.

NHS Interoperability Toolkit Dashboards

The release for this specification has been removed from TRUD. Please contact the Interoperability Standards Service for the latest information about this, and ensure the email's subject field contains the following:

1. For the "Interoperability Standards Service".
2. Mentions the type of interoperability standard, e.g. HL7 FHIR, HL7 v2, HL7 v3, CDA etc...
3. The domain, for example, PDS, ETP, ODS, Transfer of Care, etc...

NHS Interoperability Toolkit HL7 v2

The release for this specification has been removed from TRUD. Please contact the Interoperability Standards Service for the latest information about this, and ensure the email's subject field contains the following:

1. For the "Interoperability Standards Service".
2. Mentions the type of interoperability standard, e.g. HL7 FHIR, HL7 v2, HL7 v3, CDA etc...
3. The domain, for example, PDS, ETP, ODS, Transfer of Care, etc...

NHS Interoperability Toolkit HL7V2 Supplementary Pack

HL7 v2 Supplementary Pack contains artefacts supporting ITK HL7 v2 ADT Specifications. This pack contains tighter message schemas with vocabulary binding which can be used for conformance purposes. This pack also contains example HL7 v2 messages along with HTML representation of specifications derived from XML profiles of the HL7 v2 messages.

The artefacts contained in this pack are for information only and are not 'Normative'.

Please Note: The HL7 v2 supplementary pack has been made redundant and it is not available for download. If you are interested in the content of this release pack, you can subscribe and download it from here

For all content enquires, please email CFH Interoperability Team

NHS Interoperability Toolkit Security Requirements Accreditation and Concessions

As part of an extensive review of the ITK Architecture Specifications - during Q3/Q4 2012, a team comprising representatives from the Centre and the suppliers agreed a number of changes to the way ITK messages are authenticated. The changes reflected implementation difficulties presented by the nature of the WS-Security header signing specification given current development platforms, and addressed the inclusion in ITK, of multi-hop and non-SOAP transports. Technical details on the reasons for these changes are given in ITK Security Briefing Paper – Strawman Proposals.

The concessions discussed here will form part of the intended refresh and update to the ITK Architecture Specifications planned for completion by 3Q2013.

If you have any questions or queries on these changes to the documentation please direct them to Toolkit Enquiries

* This pack must be used in conjunction with the ITK Web Services Transport Specification which can be located within the related documents section of the NHS Interoperability Toolkit Core Pack

NHS Messaging Implementation Manual

The Messaging Implementation Manual for the HL7v3 messages defined by CFH. Details the messaging interfaces for the HL7v3 messages intended for use on the SPINE.
Please note: These messaging specifications are provided as one part of the implementation information required to implement the CFH defined messages. Suppliers should consult with their relevant CFH implementation team, before embarking on any development utilising these specifications.

Non-coded CDA Document Domain Message Specification

This specification contains details of message definitions and interactions required to support the national rollout of Non-coded CDA Document.

Out of Hours Domain Message Specification

Please contact the Interoperability Standards Service for the latest information about this.

Outpatients Domain Message Specification

This specification contains details of message definitions and interactions required to support Outpatients messaging.

PDS Mini Services Domain Message Specification

The PDS Mini Services domain message specifications contain details of message definitions and interactions to connect to NHS National Services, commonly known as the PDS (Person Demographic Services) on Spine. Essentially these are a set of specifications to enable suppliers of third party software to provide solutions for a greatly simplified interface for accessing a subset of the SPINE services i.e. PDS.

Telehealth Domain Message Specification

The release for this specification has been removed from TRUD. Please contact the Interoperability Standards Service for the latest information about this, and ensure the email's subject field contains the following:

1. For the "Interoperability Standards Service".
2. Mentions the type of interoperability standard, e.g. HL7 FHIR, HL7 v2, HL7 v3, CDA etc...
3. The domain, for example, PDS, ETP, ODS, Transfer of Care, etc...

Transfer of Care Domain Message Specification

Please contact the Interoperability Standards Service for the latest information about this.