Product Backlog

Enhance the PDS FHIR API so it can be accessed without an authenticated end user present (i.e. without the need for a smartcard) - similar to the way PDS Spine Mini ...

Make it possible to authenticate with a smartcard using NHS Identity on the internet i.e. without needing an HSCN connection.

Allow Hospital Patient appointments to be sent to NHS App. Most hospitals have extensive support for appointment messages (in HL7v2) these can easily be transformed ...

Ability for developers to register applications on the API platform and get their credentials - self-service (although manual approval will be required for production ...

Ability to access EPS as a dispenser, including getting prescriptions and updating prescription status.

Allow the PDS FHIR API to be accessed by patients. This would require the citizen to have an NHS login account (so they are strongly authenticated) and allow them to ...

FHIR-conformant API for creating, adding to, or accessing a patient's Summary Care Record. The first version of this will be for primary care use.

Ability to register a birth using the PDS FHIR API.

As a trust with local demographic records which are not synchronised with PDS I want to be able to see the system effective date of attributes in the PDS record So ...

FHIR-compliant API for accessing the Spine Directory Service (SDS), for example to retrieve details of endpoints for messaging other healthcare systems.

Prescription State AWAITING_RELEASE_READY = '0000' TO_BE_DISPENSED = '0001' WITH_DISPENSER = '0002' WITH_DISPENSER_ACTIVE = '0003' EXPIRED = ...

The first version of our SCR FHIR API is for primary care. If you are interested in other use cases, please let us know your use case by adding a comment to this feature.

Currently, the only way to complete authorisation for a user-restricted API is using "combined authentication and authorisation" - authentication with NHS Identity ...

Currently we use OAuth 2.0 to authorise external software to access APIs for healthcare workers. There is no standard way for external software to get the end user's ...

A number of data fields in the PDS FHIR API include a "period" during which the data is effective (in HL7 V3 these were referred to as "business effective dates"). ...

When testing integration across multiple APIs, it would be really helpful to have standardised test patients (NHS numbers) across the APIs.

Identify process pain points in the onboarding process and re-engineer the process to remove those pain points.

Currently, to set up a public key for signed JWT auth, API consumers need to email API management and ask them to do it. This feature would make it self service, just ...

An API standard for eyecare referrals. This API standard supports auto-population of digital referral platforms used when referring patients to NHS services from a ...

Make our API platform available on the internet, rather than being only available on the HSCN network.

For the PDS FHIR API, ability to update nominated pharmacy element in application restricted access mode. Being a fully online pharmacy 24/7 & having a large number ...

Provide something to help API consumers do performance testing. This might be a hosted service or a set of ready-to-go stubs.

It would be amazing if you could query a tree of data, then have role based access control to limit what data is returned based on your identity. This means data can ...

Improved, easier-to-use API for accessing organisation data in ODS via the API platform. Possibly FHIR-compliant.

Person data on Spine includes ethnicity. This is not available through PDS FHIR API (or the PDS HL7 v3 API). It is sensitive data and so may be excluded for IG ...

Ability to access EPS as a prescriber, including creating prescriptions and cancelling prescriptions.

Currently, all API deployments have to be done by the API Management central team. This change would allow API producer teams to do their own API deployments at a ...

API to allow citizens to get (prove) details of immunisations they have received, such as for COVID-19. For third party apps using NHS login to prove the citizen's ...

Make the API platform available to non-NHS Digital API producer teams. It's not clear what specific use cases this might be for.

An addition to the PDS API that indicates if (spine) flags (or other spine information) exists for the current patient. This would allow an organisation to know if ...

A number of NHS Digital publications are made as CSV, Excel and Power BI dashboards. An examples of the types of publications in question: ...

Consolidate the numerous directory of service API's into a single service. At present we have DoS for specific areas such as UEC, EPS, eRS, etc.

Healthcare professional information in England can currently be obtained from a number of different sources such as sds ldap API, publicly available csv file and ...

IMHO it would be good to provide developers with open-api/swagger.json documentation to allow the generation of http restful clients using open-api tooling for the ...

API for signing things remotely, removing the need to developers to build their own signing logic. Primary use case is signing prescriptions. To be used in ...

An API that, given an ASID, provides the corresponding ODS code.

Ability to register a new patient (not a birth) in PDS through the PDS FHIR API.

At the moment it's possible to manually download an EBSX02 (daily) spreadsheet, then ingest that into whatever systems. Can you help to cut out the manual ...

EPS has a store of accurate primary issues and dispensing history. This is currently only exposed via a prescription tracker API, a more general API would enable ...

Currently, national APIs such as PDS rely on the calling system to implement role-based access controls (RBAC). This in turn increases the assurance burden on ...

Ability to access test environments without needing our help.

Provide APIs that allow API producers and/or API consumers to perform "platform" functions through an API. This might include API deployment, monitoring, analytics, ...

Addition to the e-RS APIs suite to allow an existing booking to be rescheduled from the provider system. This would need to book the new slot and then release the ...

Enhance the PDS FHIR API to allow retrieval and update of consent to share information.

NHS Digital has two distinct categories of APIs - API services (an actual callable national service) and API standards (a specification that is intended to aid ...

The MESH API is a relatively high volume onboarding journey. We should digitise the onboarding process.

It has been noticed that both the retrieve and search PDS FHIR APIs expect the search parameters as a query string. This means that private data like name, date of ...

Ability to include contact details such as phone numbers and email addresses in PDS searches

In-App messages that are sent containing links to onboarded "silver"/"web" integrated features should be rendered in such a manner that clicking upon them will ...

The current Electronic Prescription Service (EPS) Tracker API supports a basic search on the status of the prescription. The proposal is to develop the facility to ...