As of this morning I have been receiving the following error in the e-RS INT environment on all endpoints, despite correctly passing through the ‘missing’ header with the value of our organisation (OE05Z)
Missing or Empty NHSD-End-User-Organisation-ODS header.
'response_body': '{ "resourceType": "OperationOutcome", "meta": { "lastUpdated": "2026-04-08T08:35:14.637Z", "profile" : [ "https://fhir.nhs.uk/STU3/StructureDefinition/eRS-OperationOutcome-1" ] }, "issue": [ { "severity": "error", "code": "required", "details": { "coding": [ { "system": "https://fhir.nhs.uk/STU3/CodeSystem/eRS-APIErrorCode-1", "code": "MISSING_HEADER" } ] }, "diagnostics": "Missing or Empty NHSD-End-User-Organisation-ODS header." } ] }', 'method': 'POST', 'url': 'https://int.api.service.nhs.uk/referrals/FHIR/STU3/CommunicationRequest/$ers.fetchworklist', 'http_status_code': 400, 'X_Correlation_ID': 'ca10d548-62b2-428c-a5b7-1bfbd7aa40df',
Here are the headers from this request
{'User-Agent': 'external-systems', 'Accept-Encoding': 'gzip, deflate, br, zstd', 'Accept': 'application/fhir+json', 'Connection': 'keep-alive', 'Authorization': 'Bearer <TOKEN>', 'Content-Type': 'application/fhir+json', 'X-Correlation-ID': 'ca10d548-62b2-428c-a5b7-1bfbd7aa40df', 'NHSD-End-User-Organisation-ODS': 'O0E5Z', 'NHSD-eRS-Business-Function': 'SERVICE_PROVIDER_CLINICIAN', 'Content-Length': '330'}
Let me know if you need more details / can hop on Teams.
1 Like
Good Morning mungles,
Whilst I don’t have access to confirm the ODS, from an initial glance I can see that the code you reference in your explanation (OE05Z) is slightly different from the one you demonstrate in the headers (O0E5Z). Please can you confirm which one of these is the correct code and if that code works.
Kind regards,
George Craft
That was a typo. The correct one is the one in the headers!
Thanks for the confirmation, I will have a deeper look into this now.
1 Like
We are now experiencing an identical issue in the eRS production environment. Please let me know if you would like to get on a call.
FYI @tony.marsh1
@mungles2025 If you have seen a production error, please also raise this via the national service desk so the production service teams can become involved and prioritise resolving it
1 Like
We’ve raised it. Thank you
1 Like
We’re also seeing this affecting PROD and INT
I’ve raised this with NHSE Service Bridge as a major incident, ref: INC0385207
We have raised this incident with the following ticket: CS1393750
The priority of this ticket has been set to Medium, I would advise for us it is higher priority as currently no users can triage using our platform.
Please let us know if any further information is needed.
Best, Jack
We are also seeing this in production; ticket CS1393992 raised.
Has there been any update on any of the major incident tickets above? I have not yet heard back on any of my threads.
I’ve had the below response, and the priority has been set to ‘moderate’. I agree with your earlier point that a complete outage of the e-RS APIs should be considered higher priority given the impact on clinicians.
The issue is also not reflected on the status pages for e-RS at Customer Service Portal - Customer Support
”Thank you for raising this incident. We are aware of the issue and are actively investigating. Further updates will be provided as soon as more information becomes available.”
Hi Everyone, apologies if individual comms haven’t gone back to you - I know the service teams are definitlely looking at the incident - I will make them aware of this post
Hi all, the current position is that the issue has been caused by a recent APIM release, and this release is going to be rolled back in production and int environments today
1 Like
Just to close the loop I can confirm we are no longer seeing this issue in INT or Production. Thank you!
1 Like
@Jack_Calladine /All
Thank you for confirming, and of course our apologies for the issues this caused.
We’ll be doing a retro on the issue and feeding back any comments you made during the time period.