PractitionerRole.fullURL missing `/`

Healthcare Worker API
1

Hi,

More of an FYI, than a question.

The response bundle for a PractitionerRole search has a malformed URL.

"fullUrl": "https://int.api.service.nhs.uk/healthcare-workerPractitionerRole/555085026102"

The above PractitionerRole.fullUrl appears to be missing a / between healthcare-worker and PractitionerRole.

The abridged response:

{
    "resourceType": "Bundle",
    ...
    "entry": [
      ...
      {
        "search": {
          "mode": "match"
        },
        "resource": {
          "resourceType": "PractitionerRole",
          "id": "555085026102",
          "identifier": [
            {
              "system": "https://fhir.nhs.uk/Id/sds-role-profile-id",
              "value": "555085026102"
            }
          ],
          ...
        "fullUrl": "https://int.api.service.nhs.uk/healthcare-workerPractitionerRole/555085026102"
      },
      {
        "search": {
          "mode": "match"
        },
        "resource": {
          "resourceType": "PractitionerRole",
          "id": "555083478104",
          "identifier": [
            {
              "system": "https://fhir.nhs.uk/Id/sds-role-profile-id",
              "value": "555083478104"
            }
          ],
          ...
        "fullUrl": "https://int.api.service.nhs.uk/healthcare-workerPractitionerRole/555083478104"
      },
      ...
    ]
  }

Thanks,

David

2

@david.hamill1

Thank you so much for taking the time to highlight this - we’ll get someone to check it over and address the issue.

Really appreciated, and hope it didn’t cause you too many issues.

3

Hi David,

Thanks for reporting this. I have investigated the malformed fullURL response and the data doesn’t match what our API produces. The ID format, identifier system and base URL path are all different from our expected output.

To help us trace where the problem is occuring, could you confirm the following:

  1. The exact request URL you’re calling ( full url including host and path e.g. https://int.api.service.nhs.uk/referrals/FHIR/R4/PractitionerRole).

  2. The request headers you’re sending, particularly Host, Authorization, NHSD-eRS-Business-Function and NHSD-End-User-Organisation-ODS.

  3. Are you calling the eRS API directly or is there bridge between your system and the API?

Thanks,

George

4

Hi George.

Thanks for your reply. Apologies, this isn’t an e-RS issue.

I thought I put this under the Healthcare Worker API category; for some reason this has ended up under the eRS category. “system” seems to have moved it across. :man_shrugging:

I’ll move it across and continue the conversation with that team.

David

5

Hi David - thanks for the letting us know about this.

To confirm - this is a known issue and will be fixed as part of the next planned Healthcare Worker API release. If you spot anything else - let us know, Sarah