No Relationship error in fetch worklist Retrieve referral worklist (A008, FHIR STU3)

e-Referral Service (e-RS)
1

I’m working on integrating with the e-RS API (https://int.api.service.nhs.uk/referrals/FHIR/STU3/ReferralRequest/$ers.fetchworklist) and have come across the following OperationOutcome error when trying to access a referral, I’m aware of a similar error in a previous post although I’m not sure what the resolution is, Thanks in advance for any pointers.:

"resourceType": "OperationOutcome",
"issue": [
    {
        "severity": "error",
        "code": "business-rule",
        "details": {
            "coding": [
                {
                    "code": "NO_RELATIONSHIP",
                    "system": "https://fhir.nhs.uk/STU3/CodeSystem/eRS-APIErrorCode-1",
                    "display": "No relationship"
                }
            ]
        }
    }
]

}

2

I ran into issues calling $ers.fetchworklist in the INT environment using application-restricted access, specifically:

  • "NO_RELATIONSHIP" and
  • "INVALID_CODE" for specialty.

After some testing, I resolved it by adjusting the request body to match the correct Parameters format for application-restricted mode. Here’s the structure that worked:

{
“resourceType”: “Parameters”,
“meta”: {
“profile”: [
“https://fhir.nhs.uk/STU3/StructureDefinition/eRS-FetchWorklist-Parameters-1”
]
},
“parameter”: [
{
“name”: “listType”,
“valueCodeableConcept”: {
“coding”: [
{
“system”: “”,
“code”: “REFERRALS_FOR_REVIEW”
}
]
}
},
{
“name”: “service”,
“valueIdentifier”: {
“system”: “http://fhir.nhs.net/Id/ers-service”,
“value”: “<your_service_id_here>”
}
}
]
}

3

Hi @Stuart_Dovey,

Do you still require support or have you managed to resolve the issues yourself, your follow up message suggests you may have?

If you still require support please provide your Application ID and related X-Correlation-ID/X-Request-IDs.

Regards,

Adam.