Product Backlog
This product backlog contains the features we're delivering to realise our API management vision. You can comment on features, upvote features, and suggest new features.
If your suggestion relates to our e-Referral service then please complete this form instead. To view e-Referral service requests, see here.
National RBAC role selection UI
Currently, for smartcard users, the Identity Agent will ask the end user to select a role to use for the current session (using the list of nationally-defined roles ...
API producer analytics
Ability for API producer teams to see analytics on the use of their API.
Help and support - response time SLAs
Define and implement response time service level agreements for responding to support requests.
Test data tool refresh / single sign-on
The test data tool is a little long in the tooth, and also requires a separate account from the developer account, which we have to set up for you (not self service). ...
Developer portal - role specific user journeys
Enhance the developer portal with user journeys for user journeys for specific roles e.g. coder / architect, tester, product owner / BA, security officer, clinical ...
API catalogue - remove obsolete API portals and specifications
Remove obsolete API portals such as those on TRUD and Health Developer Network and redirect them to the new API catalogue. Remove specifications for retired APIs.
Domain model
Build and publish a domain model for NHS Digital APIs that defines a taxonomy for domains and consider how that impacts our API URL namespace. Ties in with feature to ...
Online developer portal
Internet-facing web pages with single starting point and general info on getting started with NHS Digital APIs.
App store / marketplace (FHIR?)
Create a place where external developers can publish their apps for all to see, for example like Smart on FHIR (https://apps.smarthealthit.org/)
API platform in the cloud
Implement "cloud first" policy by hosting the API platform in the cloud, including sandboxes.
Developer-facing analytics
Ability for developers to view analytic data for API traffic from their applications.
Please review page styling
Please look at styling of page/scaling and minimizing the Try API panel
Not planned
platform
My developer account - strong authentication
Improve the authentication on the developer account to make it stronger e.g. 2-factor authentication, possibly selectively (e.g. to access production credentials).
Tech stack for APIs
Define a standard tech stack for APIs, so API producers don't have to figure it out for themselves.
Sample code for encode and sign a jwt with rsa512 in c#
please provide a sample code for encode and sign a jwt with rsa512 in c#
Consistent endpoint discovery
A consistent method for discovering endpoints across all our API technologies - MESH, SSP etc
Help and support - process / training / culture
Work to instil a greater sense of a developer-centric support ethic within delivery teams.
Help and support - service desk tool integration
Ability for developers to raise service desk tickets online via their developer account and view the status of those tickets.
Help and support - self-service guidance
On the help and support page, include details of how developers can help themselves, for example links to tutorials.
Search engine optimisation
Ensure that our API documentation can be found by external and internal search engines.
Calling application version management
Add an optional field in API requests specifying the software version of the Connecting System. This could be descriptive, such as 'v1.0.5', or an ID such as a GUID ...
Merge the two oath2 endpoints in the API-M INT environment into a single endpoint
Description:
There are two identity services in INT, both using Oauth2:
• One identity service “/oauth2” needs to use a smartcard/OIDC and uses NHS Identity to ...
FHIR policy update
Our FHIR policy hasn't been looked at in a while. The scope of this feature is to revisit it and refresh it, maybe adding further details.
Developer / integration guide - Urgent and Emergency care and 111
An online guide containing best practice guidance for integrating urgent and emergency care software with NHS Digital APIs
Other developer guides
As part of our vision to make learning easier, we want to produce a number of "developer guides" - on this page: ...
OAuth support for installed apps
Some of our APIs require the end user to authenticate themselves and/or authorise their software to access them, using the OAuth 2.0 standard. OAuth 2.0 uses ...
API producer guidance
Provide guidance for API producer teams on how to come onboard, how the tech works, how to do documentation, what path-to-live environments are available etc.
Developer portal - improve information architecture
There are numerous dead-ends on the NHS Digital website, for example if I find a service in the "services" area, it doesn't always link through to the relevant API ...