/
e-Referrals Service (e-RS)

e-Referrals Service (e-RS)

Owned by Imran Majid (Deactivated)
Last updated: 04-02-2025 by Victoria BusseyVersion comment
3 min read

ID

S35

Version

2.0.1

Type

Standard

Status

Effective

Effective Date

Jul 29, 2022Ā 

Contracting Vehicle(s)

Ā 

Introduction

The NHS e-Referral Service (NHS e-RS) combines electronic booking with a choice of place, date and time for first hospital or clinic Appointments. Patients can choose their initial hospital or clinic Appointment, book it in the GP surgery at the point of referral, or later at home on the phone or online.

RequirementsĀ 

Applicable Suppliers

ID

Requirement

Level

Suppliers of new services or applications (i.e. those which are NOT currently deployed into an operational environment with existing e-Referral Service (e-RS) compliance).

ERS01

Implement and maintain theĀ e-Referral Service FHIR API - Primary Care ReferrerĀ inline with the latest specification version.

MUST

Suppliers of services which ARE currently deployed into an operational environment, and have existing e-Referral Service (e-RS)Ā compliance.

ERS02

NHS e-Referrals Service - Referrer Compliance Document v1.1.docxĀ or a later version (e.g.Ā e-Referral Service FHIR API)

Service integration is supported through the Health and Social Care Network (HSCN) -based HL7 message interactions from theĀ NHS Message Implementation Manual (MiM).

MUST

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

Compliance, Assurance and TestingĀ 

e-Referral Service FHIR API -Ā Primary Care Referrer

For Suppliers of new services or applications, seeĀ the e-Referral Service (e-RS) section onĀ Onboarding Overview of the Digital Services for Integrated Care (DSIC) Interoperability Standards and Requirements

NHS e-Referrals Service - Referrer Compliance Document v1

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

To gain access to e-RS 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 contactĀ businesspartners@nhs.netĀ or visitĀ https://digital.nhs.uk/services/nhs-business-partners

The design and testing of Supplier Solutions are based upon the NHS Connecting for Health MIM version 2.3 and 3.1.09.

System Suppliers can access the updated data dictionary for the NHS e-RS. Other technical messaging documents can be found on the archivedĀ Choose and Book site.

Documentation

e-Referral Service FHIR API -Ā Primary Care Referrer

For Suppliers of new services or applications:

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

NHS e-Referrals Service - Referrer Compliance Document v1

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

Developer resources are available on the officialĀ e-Referral Service landing pageĀ on NHS Digital's website; theĀ Document LibraryĀ is a component part of e-RS' requirements for Suppliers seeking guidance and any implementation documentation.Ā 

If you are interested in learning more about the NHS e-RS APIs, please visit theĀ NHS Digital Developer Network website.

Dependencies

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

e-Referral Service FHIR API -Ā Primary Care Referrer

For Suppliers of new services or applications:

NHS e-Referrals Service - Referrer Compliance Document v1

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

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

Items on the Roadmap which impact or relate to this Standard