EPS requirements

These are the requirements for the EPS components only. Systems will also need to meet wider NHS Spine integration requirements including Spine Demographics, Spine Messaging, Spine Directory Service and Spine Security Broker.

Systems may also need to meet non-functional requirements listed in any NHS Digital agreements.

The Electronic Prescription Service - HL7 V3 API is deprecated, and a retriement date will be announced soon.

If you are developing a new integration, you must use the Electronic Prescription Service - FHIR API instead.

If you have any concerns, contact us.

You may find it useful to read the EPS integration walk through to understand how to use these documents.

Some of the documents only relate to prescribing or dispensing systems, others are common to both.

• EPS domain message specification
• EPS schedule 2 & 3 controlled drugs requirements [Archive Content]
• NHS dictionary of medicines and devices compliance requirement [Archive Content]
• RBAC implementation guidance for the EPS R2 [Archive Content]
• IG RBAC control names and codes database V27.2 2012_11_13 [Archive Content]
• Guidance for endorsement
• Electronic Prescription service release 2 clinical assurance [Archive Content]
• dm+d implementation guide (primary care)
• Nomination requirements for system suppliers [Archive Content]
• Digital signature toolkit guidance [Archive Content]
• ETP web services client source code [Archive Content]
• MiM 3.1.07 & 4.2.00 compatibility guidance [Archive Content]
• EPS infrastructure specification [Archive Content]
• Message Implementation Manual
• Native use of dm+d definition 
• EPS prescribing systems compliance specification [Archive Content]
• ETP message signing requirements [Archive Content]
• Digital signature and non repudiation [Archive Content]
• Dispensing systems compliance specification [Archive Content]
• EPS digital prescription token specification 
• EPS paper token overprint specification September 2021