# NHSD-End-User-Organisation-ODS in Request Header

**URL:** <https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468>\
**Category:** Personal Demographics Service FHIR API\
**Tags:** pds, fhir, spine\
**Created:** [3 February 2026 16:09 UTC](https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468 "2026-02-03T16:09:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![simon.hitchman1](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@simon.hitchman1](https://developer.community.nhs.uk/u/simon.hitchman1)\
**Post date:** [3 February 2026 16:09 UTC](https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468/1 "2026-02-03T16:09:39Z")

</div>

Hi there,

We have noticed that in our ‘Search for a patient’ and ‘Get patient details’ requests, a potentially incorrect code has been populated in the NHSD-End-User-Organisation-ODS parameter.

The Org Code in question is for an NHSE screening system and the calling application will pass this single code only for every request. The schema documentation suggests that this is ‘_Mandatory for client applications which service multiple end user organisations (EUO)_’. Given that this is not the case, is this ignored?

The reason for the question is that the API is behaving as expected even when the incorrect code is being passed.

If this is corrected in the calling application, will this change have any impact i.e. will the PDS API notice the change and object?

Many thanks for your help.

---

<div class="post-metadata">

**Author:** ![Adrian\_Hall](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/adrian_hall/32/587_2.png) [@Adrian\_Hall](https://developer.community.nhs.uk/u/Adrian_Hall)\
**Post date:** [5 February 2026 09:34 UTC](https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468/2 "2026-02-05T09:34:28Z")

</div>

This is currently _mostly_ for audit purposes. So changing the ODS code should not matter at this time.  
It is used for applications that have multiple different organisations calling via the same installation.

PDS FHIR API v2 might be more discerning about that. Watch this space.

---

<div class="post-metadata">

**Author:** ![simon.hitchman1](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@simon.hitchman1](https://developer.community.nhs.uk/u/simon.hitchman1)\
**Post date:** [5 February 2026 11:42 UTC](https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468/3 "2026-02-05T11:42:57Z")

</div>

Thanks @Adrian_Hall appreciate the update.

---

<div class="post-metadata">

**Author:** ![simon.hitchman1](https://avatars.discourse-cdn.com/v4/letter/s/ecb155/32.png) [@simon.hitchman1](https://developer.community.nhs.uk/u/simon.hitchman1)\
**Post date:** [24 August 2026 14:10 UTC](https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468/4 "2026-08-24T14:10:53Z")

</div>

Hi Adrian. Going back to this thread earlier in the year, you mentioned v2 of the PDS FHIR API may be more discerning about the incorrect ODS code being passed in by a calling application. Is there any update on the release of v2? We are just planning work for the remainder of this year and although this is a very small change, we do want to prioritise before a v2 release necessitates an urgent fix. Thank you.

---

<div class="post-metadata">

**Author:** ![Adrian\_Hall](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/adrian_hall/32/587_2.png) [@Adrian\_Hall](https://developer.community.nhs.uk/u/Adrian_Hall)\
**Post date:** [24 August 2026 15:46 UTC](https://developer.community.nhs.uk/t/nhsd-end-user-organisation-ods-in-request-header/10468/5 "2026-08-24T15:46:10Z")

</div>

I’ll seek confirmation, but v2 is likely to be next year.