Make the API platform available to non-NHS Digital API producer teams. It's not clear what specific use cases this might be for.
These could be any point to point APIs that are between local services (third party systems) and not to a national Spine service- can the API platform be a broker, or at least provide a standardised approach for endpoint discover and authoristation/authentication in APIs between systems
This would be a helpful to support Local Health and Record Exemplars and the Share Care Record systems in linking up so think this is worth considering.
@mike Smith, local services providing access to locally/regionally held data (data islands such as LHCREs, ICSs) are essential building blocks of a federated data architecture (LHCREs, ICSs).
Any plans to move GP Connect APIs onto APIm (local API calls are currently brokered using the Spine Proxy service). I would assume these would benefit from the additional controls, visibility/transparency, lifecycle and lowered barriers to entry provided by APIm.
Bill, discussions are happening internally about moving GP Connect onto our new API platform. If you want to suggest it, please feel free to suggest a new feature for it.
This capability is now available (and has been for some time, I forgot to update this, sorry). For more details, see https://digital.nhs.uk/services/api-platform .
This feedback board is powered by Feature Upvote.
When submitting your email with a suggestion or comment, Feature Upvote uses your email to
Your email is never displayed to other users. NHS Digital API Management staff will be able to see your email address.
Feature Upvote's Acceptable Use Policy can be summarized as:
Read the full Acceptable Use Policy (in English)
We’ll email you when the status of the suggestion changes. You can unsubscribe at any time with a single click.