Skip to content

Docs: [AEA-6528] - Update the OAS file to say the PSU is in Beta #2968

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
wildjames merged 4 commits into from
Apr 16, 2026
Merged

Docs: [AEA-6528] - Update the OAS file to say the PSU is in Beta #2968

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
62f6c96
Update the OAS file for the main PSU
wildjames Apr 14, 2026
61ac0b0
Also update the CPSU OAS
wildjames Apr 14, 2026
fe40959
revert cPSU change
wildjames Apr 16, 2026
7b577db
Update eps-custom-prescription-status-update-api.yaml
wildjames Apr 16, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions packages/specification/eps-custom-prescription-status-update-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,15 +12,15 @@ info:
email: api.management@nhs.net
description: |
## Overview
The Custom Prescription Status Update API is restricted to dispensing suppliers with an existing prescription
status update solution, who can onboard to provide updates to patients on a national scale via the NHS App
The Custom Prescription Status Update API is restricted to dispensing suppliers with an existing prescription
status update solution, who can onboard to provide updates to patients on a national scale via the NHS App
(and other third parties in the future) by September 2024.

You can:
* enable patients to know when their prescription is ready
* enable dispensing suppliers to push status information about electronic prescriptions
## Who can use this API
The Custom Prescription Status Update API is intended for those dispensing suppliers who have signed the MOU to
The Custom Prescription Status Update API is intended for those dispensing suppliers who have signed the MOU to
supply status updates by September 2024, so they can provide and push the information required to a central NHS data store.
## Related APIs
The following APIs are related to the "Custom Prescription Status Update" API:
Expand Down
2 changes: 1 addition & 1 deletion packages/specification/eps-prescription-status-update-api.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ info:
* [Electronic Prescriptions Service Dispensing](https://digital.nhs.uk/developer/api-catalogue/eps-fhir-dispensing-api): the national service for dispensing prescriptions across health and social care.
* [Prescriptions for Patients](https://digital.nhs.uk/developer/api-catalogue/prescriptions-for-patients-fhir-api-v2): the national service to retrieve prescriptions data for individual patients from the Electronic Prescription Service (EPS), for use in patient-facing applications.
## API Status and Roadmap
This API is [in development](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses), meaning the API will soon be available for testing via a sandbox service or an integration environment - but we expect to make breaking changes based on developer feedback.
This API is [in beta](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#statuses), which means it is being used by a small number of suppliers and could still be subject to breaking changes.
## Service Level
This API is a silver service, meaning it is operational and supported between 8am and 6pm, Monday to Friday, but not bank holidays.
For more details see [service levels](https://digital.nhs.uk/developer/guides-and-documentation/reference-guide#service-levels).
Expand Down
Loading