Product Backlog

I think it would be useful to add the usage pattern to entries in the API catalogue pages - "open access", "application restricted" and "user restricted" as a ...

An addition to the API catalogue that allows you to find the API you need based on the user case you're trying to achieve. For example, you might type "search for a ...

Create a place where external developers can publish their apps for all to see, for example like Smart on FHIR (https://apps.smarthealthit.org/)

Implement "cloud first" policy by hosting the API platform in the cloud, including sandboxes.

Ability for developers to view analytic data for API traffic from their applications.

Enhance the developer portal with user journeys for user journeys for specific roles e.g. coder / architect, tester, product owner / BA, security officer, clinical ...

Please look at styling of page/scaling and minimizing the Try API panel

Define a standard tech stack for APIs, so API producers don't have to figure it out for themselves.

please provide a sample code for encode and sign a jwt with rsa512 in c#

Improve the authentication on the developer account to make it stronger e.g. 2-factor authentication, possibly selectively (e.g. to access production credentials).

A consistent method for discovering endpoints across all our API technologies - MESH, SSP etc

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 ...

Ensure that our API documentation can be found by external and internal search engines.

Create a non-technical guide to building software that deals with the workforce within the NHS in England.

Create a non-technical guide to building software that deals with vaccinations within the NHS in England.

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 ...

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 ...

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.

An online guide containing best practice guidance for integrating urgent and emergency care software with NHS Digital APIs

As part of our vision to make learning easier, we want to produce a number of "developer guides" - on this page: ...

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 ...

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.

Define and implement response time service level agreements for responding to support requests.

Work to instil a greater sense of a developer-centric support ethic within delivery teams.

Ability for developers to raise service desk tickets online via their developer account and view the status of those tickets.

On the help and support page, include details of how developers can help themselves, for example links to tutorials.

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 ...