Non-NHS Digital API producer teams

7 votes

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

Done make-building-apis-easier platform platform-phase-3 Suggested by: Tony Heap (11 Jul, '20) • Upvoted: 14 Feb, '21 • Comments: 6

Comments: 6

13 Jul, '20
Kate Gill
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
29 Jan, '21
Mike Smith
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.
05 Feb, '21
Bill Swire
@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).
05 Feb, '21
Bill Swire
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.
05 Feb, '21
Tony Heap Admin
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.
01 Dec, '22
Tony Heap Admin
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 .