Skip to main content

Organisation Reference Data: how changes affect your service

This page highlights the most relevant changes to the Organisation Reference Data (ORD). Please refer to the ISN DCB0090 which mandates and outlines the changes fully.

ORD users should explore their own systems and processes to identify specific effects on their own organisation.

Organisation code Site code
R0C R0C01
R0C R0C02
R0C R0C03
R0C A1T5Y
R0C C0H8P
R0C H8U4F

This table contains example site codes. The first three rows are in the current format; the bottom three are the new alpha-numeric-alpha (ANANA) format.

Codes in ANANA format were originally scheduled to be allocated to organisations types within scope of ANANA from 1 April 2020 but due to COVID-19 this has been postponed until at least 1 September 2020.


This revised date is provisional and will remain under review. Further updates will be released as we approach it.


Older organisation code formats will not be converted

When a new transition date is confirmed all new organisation identifiers allocated by the Organisation Data Service (ODS) will be issued using the new code structure (ANANA). Codes issued prior to this date will not be converted meaning there will be a mix of code formats in organisation reference data.


Codes in scope of ANANA

Both organisation and site codes are within the scope of ANANA, but not all organisation types. For a definitive list of organisation types adopting the ANANA format see our ORD scope definition.

All organisation types are within scope of the ODS XML file and ODS API Suite. The same meta data will need to be used within these products to query all organisation data, regardless of what format the codes are in.


All ANANA codes will be 5 characters in length

You’ll need to ensure your systems and processes can accept 5 character ANANA codes. This includes any automated or manual validation that depends on code format.

If this is a problem you may need to use the XML meta data to continue this validation – for example, query the Primary Role to determine organisation type.


Consume ORD via monthly ODS XML file or ODS API Suite

Regardless of code format, all users will need to consume organisation reference data via the monthly ODS XML file or ODS API Suite from Nov 2021 at the very latest. Organisation reference data in CSV format will be withdrawn from Nov 2021. The ODS XML file and ODS API Suite are live now.

You can use the membership search function in the ODS API Suite to identify both:

  • all organisations within in a particular geographical boundary
  • all site codes under a specific organisation

Identify parent organisation codes

Sites under a parent organisation code can be identified by querying the relationship metadata, using relationship ID: RE6 “Is operated by by”.


Identify hierarchical information about an organisation

To identify NHS hierarchy information (High Level Health Authority and National Grouping) about a specific organisation in the XML file/ODS API Suite, the relationship meta data must be used. There are various ‘named relationships’ in ORD which describe how one organisation entity is linked to another.

See How to derive NHS hierarchy from ORD.

Last edited: 14 September 2021 3:19 pm