Spine Directory Service (SDS) FHIR API

Comments: 8

• 13 Jul, '20
  Kate Gill

  Is there a suggestion related to this to remove SSP as a proxy as well, and so support direct point to point APIs with a model for authentication/authorisation?

• 23 Jul, '20
  Kevin Mayfield

  Upvote for Kate Gill's comment. Can we remove SSP?

• 05 Oct, '20
  Tony Heap Admin

  This API is now available for testing in alpha. Specifically you can get endpoint details for an accredited system. If you are interested in other capabilities, please add a comment to this feature or suggest a new feature.

• 05 Oct, '20
  Tony Heap Admin

  Removing Spine Security Proxy (SSP) is a separate thing to building a new SDS FHIR API. I have created a separate feature suggestion: https://nhs-digital-api-management.featureupvote.com/suggestions/124432/remove-spine-security-proxy-ssp.

• 13 Apr, '21
  Brian Diggle

  The SDS FHIR API will shortly go into production, but is already available in sandbox and integration testing environments.
  
  The API allows you to search for Spine endpoints and spine accredited system information, and at this stage is limited to consumers from a Primary Care context.

• 27 Oct, '21
  Tony Heap Admin

  This API is now available for use in production. See https://digital.nhs.uk/developer/api-catalogue/spine-directory-service-fhir for details.

• 25 Oct, '22
  Christopher Morris

  Is there a way of extracting nhsdhsccode using the Spine FHIR API for a given ODS Code? This is the National Grouping / NHS England Region. For example, for ODS Code M82024, it is Y60 MIDLANDS COMMISSIONING REGION.

• 31 Oct, '22
  Brian Diggle

  The SDS FHIR API exposes only the services tree of SDS - details of spine accredited systems and their associated endpoints. The ODS API suite provides querying capabilities on organisation data and includes hierarchical organisation associations. This seems a better place to query organisation data as the ODS service masters this data.