Latest news

A number of new features are due to be released in August 2026 (subject to testing), including both entirely new functionality and improvements to existing capabilities. Further information is available.

As a result of user feedback, the deprecation timescales for the ORD API has been pushed back until September 2027.Retirement of this API remains under review.

We continue to encourage all ORD API users to migrate to the Organisation Data Terminology FHIR R4 API, the key benefits/drivers being: -

• FHIR R4 includes key health and care geographies; mapping each organisation and site to the Region/ICB/Sub
• ICB Location it sits within geographically, as well as to Local Authority boundaries, for example
• due to the above, ODS plan to close all current RE5 “in the geography of” relationships as these are static and limited to certain org types (see  our February 2026 update below). FHIR R4 geography data provides dynamic mappings for all entities to multiple geographies, better meeting user need
• FHIR R4 API aligns with other data models/NHS APIs increasing interoperability and standardisation of data
• FHIR R4 includes the practitioner data that ODS publish (GP, consultants, nurse prescribers and private controlled drug prescribers)

To assist with the migration, we have created:

• implementation guidance and an open API specification
• a sandbox to explore the API prior to onboarding and a postman collection to provide examples of how to request data 

To use the API in production you will need to:

• follow the onboarding process
• use API key authentication, for more information on how to get started and how to generate your key, please refer to step 1. register your application on the platform

We recommend beginning migration as soon as possible to avoid any potential disruptions. Submit an organisation data request if you have any queries.

Over the coming months, ODS plan to refresh/uplift the documentation associated with the published Health and Social Care Organisation Reference Data Information Standard (HSCOrgRefData 0090).

Current documentation focusses on the 2019 implementation of the ANANA code frame, the previous move to the publication of data via XML files and API, and the planned deprecation of legacy csv files published via our website on a fixed schedule.

Much of the documentation is out of date given the above changes are now fully embedded. We also need to ensure that the Standard does not refer to legacy products that have been replaced (i.e. ODS Portal and DataPoint which have been replaced by ODS Data Search and Export).

The uplift will ensure that the supporting documentation is accessible, accurate and meaningful to those seeking to utilise Organisation Reference Data, but it does not fundamentally change the information standard or data model.

We will publish further news items to inform you of progress but please get in touch if you have any queries.

Following the 2026 split of Frimley ICB, the following sub ICB locations and their respective LSOAs, no longer map to Surrey and Sussex Cancer Alliance. This will be published in the NHS Postcode Directory May 26 release.

In response to user feedback, ODS will be adding the following relationships to our data model:

We are also liaising with finance colleagues and plan to create a new named relationship (type) of 'Is Financially Apportioned to' (exact relationship name tbc) so that we can also publish:

This will mean that instances of these relationships are available via the APIs and Data Search and Export, and so ODS will be able to retire the standalone excel spreadsheet. This will improve data accuracy, consistency and will be in line with our 'single source of truth' ambition for organisation data.

Timings are to be confirmed; this is early notification of planned work. Further updates will be shared but if you have any queries or concerns, contact us.

In response to user requirements, the following new non-primary roles are currently under development:

• lung cancer screening provider (non-primary role for NHS trust sites and independent sector healthcare provider sites)
• admin only (non-primary role for branch surgery codes, to make the distinction between patient facing branch surgeries and those only used for admin purposes)

We will publish the new non-primary role IDs in our next newsletter and via the Reference Data Catalogue as soon as they are confirmed.

ODS have published a new NHS Trust code for The Online NHS Trust (K0N6A) which can be viewed via ODS Data Search and Export.

Users will note the future legal start date of 1 June 2026, which reflects the legal establishment date.

Despite it being a virtual service/trust, to create the code we had to assign the trust a nominal address/postcode. In ODS data, Trust codes have a geographic relationship to an ICB, based on their postcode, so the same has been applied to The Online NHS Trust.  There is no 'partner to' relationship as this is not applicable as it is a national service. ODS continue to work with the programme team to confirm trust site and other reference data requirements.

Further information about the new trust is available.

Phase 1 of ICB mergers/new footprints came into effect on 1 April 2026.  For more information see ODS Implementation of ICB Mergers Phase 1.

On 12 January 2026, ODS published 6 new codes for the integrated care boards (ICBs) that will be formed on 1 April 2026. These codes have been published in advance of the legal start date to enable system testing and configuration in readiness for 1 April. The codes are available via Data Search and Export and the ODS APIs. 

A 'forward view' version of the NHS Postcode Directory was published on 4 March 2026 and contains postcode data for February 2026 but with the new ICB boundaries from 1 April 2026 included. Please refer to our 'Upcoming code changes' webpage for further information regarding ICB Reconfiguration.

RE5 'in the geography of' relationships were created and stored against an ODS record to indicate a given boundary that organisation was located within geographically (for example, X NHS Trust is located within the boundary of Y integrated care board based on its postcode). To improve data quality, we no longer want to store static 'in the geography of' relationships and instead use dynamic geographic relationships that are mapped from the postcode to the latest boundaries within the NHS Postcode Directory.

This functionality has been enabled in the data that feeds ODS Data Search & Export and the Organisation Data Terminology FHIR R4 ODS API. To implement fully, ODS will need to close all legacy 'in the geography of' relationships and support users to migrate to the new dynamic geography data (and therefore the FHIR R4 API rather than ORD API).

Benefits of this new approach are:

• fewer 'stored' relationships forming part of an organisation record, meaning that the impact of any future reconfiguration is reduced (fewer relationships to manually update as geographic relationships will dynamically update from NHS Postcode Directory data)
• better data quality - at present, the 'in the geography of' relationships are created in the ODS database at the point of code creation and must be manually checked and updated if the organisation address changes

This article is early warning of planned changes, as we are aware of the significant impact on users. The implementation plan and timescales for the closure of RE5 'in the geography of' relationships will be communicated as soon as possible. Further information regarding migration to the new dynamic geography mappings is available within the ODS Reference Data Catalogue: see Organisation Data Service : Relationships.

On Sunday 22 February 2026 the following service will be unavailable due to planned maintenance:

• Data Search and Export (DSE)
• ODS ORD API
• ODS FHIR R4 API

The downtime will occur from 10am - 11am (British Standard Time).

We recommend scheduling any integrations or API calls outside these times to avoid disruption.

The way in which pharmacy system suppliers  request EPS Pharmacy Nominations or Consolidations has changed. These requests are now accessed via the NHS National IT Customer Support Portal.

To submit a request to ODS you will need to:

1. Log into NHS National IT Customer Support Portal.
2. Select 'Submit a Case'.
3. From the categorises listed on the left-hand side of the screen, select ‘Medications and Prescriptions’.
4. Select the subcategory ‘Electronic Prescription Service'.
5. Select the ‘EPS Pharmacy Nomination or Consolidation’ webform.

New portal users will be prompted to create an account.

We have introduced these changes to: 

• simplify the request process - this has been achieved by replacing the old process of contacting the Service Desk via email with a simple and clear webform on the portal 
• decrease request processing times - our new portal webforms allow you to provide the necessary information, in the correct format at the start of your request 
• improve visibility - you are able to view and update your requests within the NHS National IT Customer Support Portal 

From 1 March 2026, we will only accept requests from pharmacy system suppliers submitted via the NHS National IT Customer Support Portal. Email requests sent to the National Service Desk will no longer be accepted.

On Thursday 4 December 2025 the following services will be unavailable due to planned maintenance:

• ODS ORD API
• ODS STU3 API
• ODS FHIR R4 API
• Data Search and Export (DSE)

The downtime will occur from 8-9pm and 10-11pm (British Standard Time).

We recommend scheduling any integrations or API calls outside these times to avoid disruption.

The csv legacy files have now been withdrawn from the ODS data download webpages. These have been replaced by automatic csv download links to the relevant Data Search and Export Predefined Reports. Reference Data Catalogue links have been provided against each report. These include the report specification as well as an explanation of any changes between the legacy csv and DSE reports.

Key differences between legacy csv and DSE Predefined Reports:

• DSE predefined reports are dynamic – the source data updates nightly. ODS have moved away from ‘snapshot’ full files produced on a monthly/quarterly basis, and we will no longer publish amendment-only files. Users can create their own amendment files if required via DSE.
• As DSE reports are dynamic, all ‘amendment indicators’ (field 22) have been set to ‘1’ by default.
• It is also possible to automate the download of multiple reports (packs) using the DSE API endpoint. Please refer to DSE ‘Help and guidance’ for further information.
• DSE has a baseline cut-off date of 31 March 2017, so searches and reports will include all open records and records that have closed since this cut-off date. This is a change from the legacy csv reports, particularly for third party data where you will see less records in the predefined reports as they closed before the DSE baseline (such as ecarehomehq, ecarehomesite, edispensary, egpcur, epharmacyhq, epraccur, eschools and niorg). For ODS mastered data (that is, NHS trusts, integrated care boards and independent sector healthcare providers) there will be an increase in records returned in predefined reports as the previous baseline for these data types was a rolling cut off date of the previous financial year.
• Fields with a geographic hierarchical value, particularly fields 3 and 4 of most reports (National Grouping / High Level Health Geography), are now derived as an extension of the record’s postcode, rather than via relationships or inherited from the parent. This means they are dynamic and will change if the org postcode changes or the boundary they sit within changes.
• Note that default values are not currently provided in hierarchy fields – for example, ‘W00’ where a Welsh geographic equivalent is not applicable/available.
• The data item ‘County’ is no longer provided in any reports/searches.

The Weekly Prescribing Data pack has now been retired. Historic packs remain available (12-month period, up to October 2025). A migration notice has been issued to all users who are signed up to receive this data pack.

The TRUD Organisation Reference Data pack has been rebranded. It will now be released on a quarterly basis and will only contain the postcode files (from November 2025). Historic monthly/quarterly packs containing csv org/site data will remain available. A migration notice has been issued to all users signed up to receive this data pack.

On 23 December 2024 we sent out communications announcing the deprecation of the ODS STU3 API. This decision aligns with our efforts to enhance the performance, security, and functionality of our services. While the STU3 API will remain available until 31 December 2025 (supported and maintained), it will become obsolete and retired after this date. No further development work will take place on this API after 31 December 2025.

To provide a better experience, we encourage all users to migrate to the Organisation Data Terminology - FHIR API, which offers increased ODS data, combining content found within both the ODS ORD API and the ODS STU3 API. The Organisation Data Terminology FHIR R4 API brings the benefit of a single data source (improving reliability and consistency of data), as well as offering extended support. Publishing ODS data via a FHIR compliant API is a modernisation of the service, allowing for future uplift in line with the FHIR standard and supports interoperability across the health and social care system. 

We understand that transitions require effort, and we are committed to supporting you during this period. To assist with the migration, we have created:

• implementation guidance and an open API specification as well as a free to access sandbox which gives you a chance to explore the API prior to onboarding  
• a postman collection to provide examples of how to request data 

To use the API in production you will need to:

• follow the onboarding process
• use API key authentication, for more information on how to get started and how to generate your key, please refer to step 1. register your application on the platform

We have also published the ODS data model within a new Reference Data Catalogue. The Data Model pages include a mapping between STU3 data attributes and R4 attributes which we hope will support migration.

We recommend beginning migration as soon as possible to avoid any potential disruptions. Please submit an organisation data request if you have any questions or need guidance.