Unexpected response from SDS FHIR API

Other services Spine Directory Service (SDS)
,
1

We are using SDS FHIR API. Our regression tests have recently started failing in the INT environment.

When requesting Device resources for organisation YES:

GET Device?organization=https://fhir.nhs.uk/Id/ods-organization-code|YES&identifier=https://fhir.nhs.uk/Id/nhsServiceInteractionId|urn:nhs:names:services:nrl:DocumentReference.content.read

The response includes 3 resources.

2 have owner.identifier.value of YES, as expected.

The response also includes a resource where owner.identifier.value of YEA, which doesn’t meet the expectation in the FHIR specification which defines a match against Device.owner. We note that this resource has an identifier using the same MHS Party Key as the resources owned by YES:

{
  "system": "https://fhir.nhs.uk/Id/nhsMhsPartyKey",
  "value": "YES-0000806"
}

Is this an expected behaviour of the SDS FHIR API?

2

Hi @dunmail, thanks for posting on the Community. This has been flagged to the SDS team and they should respond shortly.

3

Do you know when the SDS team are likely to respond?

1 Like