Electronic Prescription Service (EPS) - Prescribing

Owned by Jonathan Telfer (Unlicensed)
Last updated: 09-08-2023 by Michael France
3 min read
IDS36
Version3.0.1
TypeInteroperability Standard
StatusEffective
Effective Date 
Framework(s)

Introduction

Electronic Prescription Service (EPS) allows prescribers (like those using GP Systems) 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. Please access the EPS landing page on NHS Digital's website for further information. 

Requirements

 Applicable Suppliers RequirementLevel
Suppliers of new services or applications (i.e. those which are NOT currently deployed into an operational environment with existing Electronic Prescription Service (EPS) compliance).Implement and maintain the Electronic Prescription Service (EPS) FHIR API - Prescribing API inline with the latest specification version.
MUST
Suppliers of services which ARE currently deployed into an operational environment, and have existing Electronic Prescription Service (EPS) compliance.GPSoC CCN057 and EPS Prescribing Systems Compliance Specification v6.0, or a later version.MUST
EPS Prescribing Systems Compliance Specification v6.11 (Document reference NPFIT-ETP-EDB-0025) Requirement 6.4.4 onlyMUST
EPS Prescribing Systems Compliance Specification v6.11 (Document reference NPFIT-ETP-EDB-0025) Requirement 5.2.1, 5.2.5, 5.2.7, 6.7.7, 6.7.8, 6.9.10 onlyMUST

All suppliers are encouraged to work towards compliance with the latest version as above.

Compliance, Assurance and Testing

EPS FHIR API - Prescribing API

For Suppliers of new services or applications, see the Electronic Prescription Service (EPS) section on Onboarding Overview of the Digital Services for Integrated Care (DSIC) Interoperability Standards and Requirements.

EPS Prescribing Systems Compliance Specification v6.11 or older

For Suppliers of services which ARE currently deployed into an operational environment:

 Click here to view historical assurance approach

To gain access to EPS suppliers previously followed the Common Assurance Process (CAP). CAP is an end-to-end assurance process, which involves a tailored (CAP) approach being developed which states what deliverable and activities are conducted.

As part of the CAP suppliers will be asked to demonstrate adherence to the following specifications:

These specifications contain a set of generic requirements applicable to all systems seeking compliance to a business domain. Compliance with these specifications is mandatory and established through the CAP.

For advice, access to the documentation, and support from the NHS Business Partners programme, please contactbusinesspartners@nhs.netor visithttps://digital.nhs.uk/services/nhs-business-partners

Testing services can be accessed via the NHS Digital Solutions Assurance Team.

EPS is a national service provided by NHS Digital as part of the Spine infrastructure. It therefore is supported on all of the Path to Live (PTL) environments.

Documentation

EPS FHIR API - Prescribing API

For Suppliers of new services or applications:

It is recommended to read GP software developer guide in conjunction with the API documentation.

EPS Prescribing Systems Compliance Specification v6.11 or older

For Suppliers of services which ARE currently deployed into an operational environment:

 Click here to view previous EPS requirements documentation

Developer resources are available at the Developer resources for the Electronic Prescription Service.

Dependencies

EPS FHIR API - Prescribing API

For Suppliers of new services or applications:

Creating a compliant implementation requires implementing the following dependent interface standards:

EPS Prescribing Systems Compliance Specification v6.11 or older

For Suppliers of services which ARE currently deployed into an operational environment:

 Click here to view historical dependencies

Creating a compliant implementation previously required implementing the following dependent interface standards:

*May be sourced indirectly by existing PDS interface provided by PIM Solution, either via API to PIM Solution, or as a shared application resource if delivered as part of the same Solution.

Roadmap

Generating page properties report...