Skip to main content

Sunsetting policy

Learn about our sunsetting policy including deprecation and retirement of NHS e-Referral Service endpoints

Introduction

The NHS e-Referral Service (e-RS) is an evolving, publicly-funded national system, critical to the NHS.

The API we offer must be maintained and managed cost-effectively. This means that API endpoints will be deprecated and retired over time.

Partners must migrate away from deprecated API endpoints. In exceptional circumstances you will also be expected to respond to breaking changes.

This policy builds upon the general NHS API deprecation and retirement policy.


Deprecation and retirement

An API endpoint may be deprecated if it is:

  • redundant with the introduction of a new endpoint which provides equivalent or enhanced capabilities

  • not fit for purpose, for example because it doesn't include important use-cases

  • insecure or a security risk

  • not being used or has limited usage

When an API endpoint is deprecated:

  • we will publish a deprecation notice which includes a deprecation and retirement date
  • a migration guide will be produced
  • the endpoint will still be available for use
  • normal service levels will still apply
  • further updates to the endpoint are unlikely to be made
  • new integrations will not be permitted - partners already in the latter stages of onboarding will be allowed to complete integration

For details on endpoints that are currently being considered for deprecation or retirement, see our deprecation notices.


Sunsetting timeline

The deprecation period is 12 months.

The retirement date is the date at the end of this period at which the API endpoints will reach end-of-life and be taken out of service.  At this point, the API endpoint will no longer be available for use.

Deprecation
notice
Deprecation...
Deprecation
date
Deprecation...
Retirement
date
Retirement...
1st June 2020
1st June 2020
1st June 2021
1st June 2021
18th May 2020
18th May 2020
+ variable
+ variable
+ 1 year
+ 1 year
Variable notice period
Variable notice period
Deprecation period
Deprecation period
Available for use
No new integrations
Available for use...
Available for use
No new integrations
Available for use...
Available for use
 
Available for use...
No longer available for use
No longer availabl...
Retired
Retired
Text is not SVG - cannot display NHS e-Referral Service - API Sunsetting timeline
Accessibility description

NHS e-Referral Service API - Sunsetting timeline

The diagram illustrates an example sunsetting timeline with three key touchpoints.

1. Deprecation notice

At this point, a decision has been taken to deprecate an endpoint. A deprecation notice is issued with a deprecation and retirement date. The example deprecation notice date is 18th May 2022.

The endpoint remains available for use. However, no new integrations are allowed.

2. Deprecation date

This is the deprecation date and is a variable period from the deprecation notice being issued. The example deprecation date is 1st June 2022.

The endpoint remains available for use. However, no new integrations are allowed.

3. Retirement date

The retirement date is the date at the end of this period at which the endpoint will be taken out of service. The example retirement date is 1st June 2023.

The endpoint is no longer available for use after this point.

During the deprecation period partners are expected to follow the migration guide and onboard with the new API endpoint. A lighter weight assurance policy will be available for migrations, provided no new functionality is to be adopted.

The aim is for partners to have migrated away from the deprecated API endpoints before the retirement date. 

Partners unable to migrate away from an API endpoint before its retirement date should contact the API partners team within 6 weeks of the deprecation notice: [email protected].


Breaking changes

The e-RS is an evolving system. Functionality is being added and updated to meet the demands of the NHS. As such, the e-RS API will need to adapt to meet these needs.

When a proposed change is not backwards compatible, we will look to introduce a new version of the endpoint. This will maintain the behaviour of the existing endpoint version. The deprecation and retirement policy will be followed to prompt the migration of partners to the new endpoint version.

In exceptional cases, it may be necessary to make a breaking change to an existing endpoint.

This could be because:

  • an immediate privacy or security risk has been identified
  • a critical functional change to the e-RS has been identified that cannot reasonably be accommodated in any other way

The deprecation period length will be assessed on a case-by-case basis when this occurs. At the end of this period the changes will be applied to the existing endpoint. Other aspects will follow the standard deprecation and retirement process.

Partners unable to update their integration before the changes are applied should email the API partners team within 6 weeks of the deprecation notice: [email protected]

Last edited: 1 August 2023 3:53 pm