Environment: e-RS INT (integration)
Summary:
We’ve recently configured our ASID for e-RS INT and are getting HTTP 500 on every endpoint we’ve tried. The response is a generic plain-text error (not
a FHIR OperationOutcome), which suggests the request isn’t reaching the e-RS application layer.
Endpoints tested:
- GET /STU3/ReferralRequest/$ers.fetchWorklist (A005)
- GET /STU3/HealthcareService?patient={nhsNumber} (A008)
ODS codes tried: A20047, D82028 — both return 500
Business functions tried: REFERRING_CLINICIAN, REFERRING_CLINICIAN_ADMIN, REFERRING_ADMIN, SERVICE_PROVIDER_CLINICIAN — all return 500
Request headers:
Authorization: Bearer
Accept: application/fhir+json
Content-Type: application/fhir+json
NHSD-End-User-Organisation-ODS:
NHSD-eRS-Business-Function:
X-Correlation-ID:
Response (identical for all requests):
HTTP 500
Body: " - The server encountered an unexpected condition that prevented it from fulfilling the request."
What we’ve ruled out:
- CIS2 authentication is working (we get a valid Bearer token and can re-authenticate successfully)
- Multiple ODS codes and all business functions produce the same error
- The response is not a FHIR OperationOutcome — it’s a plain-text string, suggesting it fails at the Spine/gateway level before reaching e-RS
Question: Is there a known delay between ASID configuration and it becoming active in INT? Or is there an additional Spine registration step we may be
missing? Any guidance appreciated.
X-Correlation-IDs for investigation:
- 1fda23b7-1e0d-45d2-8053-fdd947bd59d2 (worklist, D82028, 2026-04-02 ~10:10 UTC)
- 278c7230-6e72-4fad-b5d8-aa9da6a286db (service search, A20047, 2026-04-02 ~09:35 UTC)
Thank you!