A008 – Fetch Worklist ($ers.fetchworklist) error

e-Referral Service (e-RS)
,
1

Hi @BalalSaleh could you please look into this for our partner please.

“We have now successfully validated our integration with the e-RS INT environment for the following endpoints using our registered application (Mid Yorkshire – ERS to CITO RPA – INT – e-Referral Service – Application-Restricted):

  • A005 – Retrieve Referral Request

  • A006/A042 – Retrieve Attachments

  • A007 – Generate Clinical Information Summary (CRI)

All these endpoints are working correctly when using known UBRNs — the system successfully retrieves the referral details, CRI PDFs, and all related attachments.

However, the A008 – Fetch Worklist ($ers.fetchworklist) endpoint still does not return any referrals.

  • The call connects successfully and responds with status 200 (or 422 when the service parameter is missing),

  • but when we specify valid Service IDs (6710999 and 6711006), the response payload is always an empty list.

We have verified that both of these services are configured correctly in the INT environment and can see active referrals listed under both Referrals for Review and Appointment Slot Issues directly in the e-RS UI. This confirms that the Service IDs are valid and populated with referrals, but the API endpoint is not returning them via the worklist operation.

Summary of validation so far:

  • Environment: INT

  • App ID: 8a3183e6-ab4e-4538-9beb-733cecffaa64

  • Key ID (kid): midyorks-int-test-shashi

  • Authentication: Application-restricted (OAuth2 client_credentials, RS512 JWT)

  • JWKS registered and verified

  • Token generation and resource access: Successful

  • Referrals, CRI, and attachments retrievable via A005/A006/A007

  • A008 (fetchworklist) executes successfully but returns 0 results despite visible referrals in the INT UI”

2

Hi Hannah,

There are a couple of asks to help us resolve the issue which is being faced.

Can we please have the correlation ID used.

Can we also please have the request and body which is being made including all parameters.

Thanks,
Balal

3

Hi @BalalSaleh

Please find below information. Kindly note that I have segregated my response into 3 parts as the editor doesn’t allow me to paste more than 2 links at a time and the unlink option doesn’t work as well.

Request Summary :

Endpoint: https://int.api.service.nhs.uk/referrals/FHIR/STU3/ReferralRequest/$ers.fetchworklist
HTTP Method: POST
Date/Time (BST): 2025-10-22 14:16
Service ID: 6710999
List Type: REFERRALS_FOR_REVIEW
Headers:
X-Correlation-ID: 6e2f43c1-bb5e-43c1-bb0e-736c4c7a3a2a
X-Request-ID: (from response header)
Authorization: Bearer [token redacted]
Content-Type: application/fhir+json

4

Request Body :

{
“resourceType”: “Parameters”,
“meta”: {
“profile”: [
“https://fhir.nhs.uk/STU3/StructureDefinition/eRS-FetchWorklist-Parameters-1”
]
},
“parameter”: [
{
“name”: “listType”,
“valueCodeableConcept”: {
“coding”: [
{
“system”: “https://fhir.nhs.uk/STU3/CodeSystem/eRS-ReferralListSelector-1”,
“code”: “REFERRALS_FOR_REVIEW”
}
]
}
},

5

{
“name”: “service”,
“valueIdentifier”: {
“system”: “http://fhir.nhs.net/Id/ers-service”,
“value”: “6710999”
}
}
]
}

Response Detail :

HTTP Status: 200 (empty list)
x-request-id: c856411a-ba3d-4968-af8a-3ac1d3ecd657-1
Response body:
{
“resourceType”: “List”,
“status”: “current”,
“mode”: “snapshot”,
“entry
}

Kindly let me know if you require further information.

Best Regards,

Shashi

6

Hello Shashi,

Thanks for the information.

Please bear with us whilst we investigate this.

Thanks,
Balal

7

Hello Shashi,

We have been trying to investigate the issue you are facing. But this is working as required.

We need to know if the referrals for review that are being seen in the UI are linked to the service ID being used. On the UI are you filtering using that specific service?

thanks,
Balal