Data Description
NHS England and Regions in England, plus codes for Government Office Regions in England and Wales. It also lists a number of high-level Welsh organisations.
How Data is Maintained
NHS England and Regions are not legal entities; they are sub-divisions of NHS England. Information on these entities is supplied directly to ODS by NHS England.
Requirements/updates for Welsh Regions are provided to ODS by Digital Health and Care Wales. Welsh Regions were created to facilitate the commissioning and reporting of health and care services at varying geographies across Wales. Welsh Region boundaries have not been added to the NHS Postcode Directory as there is not a one to one relationship between Local Health Boards and Regions - LHBs will sit within more that one Welsh Region. These were the requirements of DHCW and Welsh Government.
Data Quality Assessment
For further information re the: ODS Data Quality Assessment Framework
| Data Quality Dimension | |||||||||||
| Last updated: |
| 1 | 2 | 3 | 4 | 5 | ODS mastered or 3rd party data | 6 | 7 | 8 | 9 |
| OVERALL | Frequency of Update | Data Collection Method | Fit for Purpose | Coverage / Completeness | Reliability / Accuracy | Data Agreement | 3rd Party Escalation Routes | System Application / Downstream System Feedback | Future Refinement / Improvement Plan | ||
| NHS England and Regions | GREEN | Green | Green | Green | Green | Green | ODS | n/a | n/a | Green | Green |
| Ad Hoc, driven by NHS/DHSC policy changes | ODS mastered as part of a national reconfiguration project. Minor amendments to addresses etc may be received via customer logs to helpdesk. | Codes created to meet demand | Complete | Essential that these codes are reliable / reflect NHS structures | n/a | n/a | No known issues | Not required | |||
Key Information - Roles, Code Formats and Data Source
| Key Information | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Geographic coverage |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Primary Role ID | RO185 | Primary Role Name | REGIONAL OFFICE (RO) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RO209 | NHS ENGLAND (REGION) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RO210 | NHS ENGLAND (REGION, LOCAL OFFICE) | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RO212 | NHS ENGLAND (REGION, LOCAL OFFICE) SITE | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RO200 | WELSH ASSEMBLY | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RO128 | GOVERNMENT OFFICE REGION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| RO328 | WELSH REGION | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Non Primary Role ID | RO211 | Non Primary Role Name | SPECIALISED COMMISSIONING HUB | Linked to RO210 Primary Role only | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Raw Data Source | NHS England / Digital Health and Care Wales | Update Frequency | Ad-hoc basis | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Code Format |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Permitted Relationships
Permitted Relationships: Regions/Gov Depts can be linked to (upward): | ||||
Source Primary Role ID | Relationship Type Id | Relationship Type Name | Target Primary Role ID | Target Primary Role Name |
| RO185 | RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO128 | GOVERNMENT OFFICE REGION |
RO210 | RE2 | IS A SUB-DIVISION OF | RO209 | NHS ENGLAND (REGION) |
| RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO128 | GOVERNMENT OFFICE REGION | |
RO212 | RE6 | IS OPERATED BY | RO210 | NHS ENGLAND (REGION, LOCAL OFFICE) |
| RE6 | IS OPERATED BY | RO261 | STRATEGIC PARTNERSHIP | |
| RO200 | RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO185 | REGIONAL OFFICE (RO) |
| RO328 | RE5 | IS LOCATED IN THE GEOGRAPHY OF | RO189 | SPECIAL HEALTH AUTHORITY |
Legacy 'Parent' Mapping
Traditionally, some systems have referred to a 'parent' relationship between organisation/site records. Although 'parent' is not one of the named relationship types that ODS publish, there has previously been mappings that indicate which relationship types between specific organisation types, could be interpreted as 'parent' relationships.
The legacy parent mapping (for active org types) is shared below for information but should be used with caution. Please note that ODS intend to move away from RE5 'in the geography of' relationships. The modern equivalent is a dynamic mapping from the org/site postcode to the Postcode CodeSystem. The equivalent values in Data Search and Export and the Organisation Data Terminology FHIR R4 API are shown below where relevant. It is recommended to use these new dynamic postcode based values, rather than legacy RE5 'in the geography of' relationships.
| CIM Organisation Type Code | ODS Primary Role ID | ODS Primary Role Name | Country | Country Legacy Code | Relationship Type ID | Relationship Type Name | Parent Org Type Code | Parent Primary Role ID | Parent Primary Role Name | Modern Equivalent: Data Search and Export | Modern Equivalent: Org Data Terminology FHIR R4 API - Postcode CodeSystem |
| WW | RO328 | WELSH REGION | WALES | W | RE5 | IS LOCATED IN THE GEOGRAPHY OF | SA | RO189 | SPECIAL HEALTH AUTHORITY | n/a (a solution will be provided before end dating the current RE5 relationship). | n/a (a solution will be provided before end dating the current RE5 relationship). |
Legacy .csv File Mapping
Click here for an explanation of the baseline data differences between legacy csv files and ODS Data Search and Export and the ODS APIs.
eauth.csv
Authoritative Organisations including NHS England (Region), Government Office Regions and NHS England (Region, Local Office).
Primary Role ID = RO128, RO209, RO185, RO200
Col | Data Item | Report Alias (Legacy csv) | Notes |
1 | [OrganisationCode] | Organisation Code | |
2 | [OrgName] | Name | |
3 | NULL | National Grouping | Change from legacy csv: Not populated as the organisations in question are of this tier or higher, therefore this value is not applicable for these entities. |
4 | NULL | Column 4 | |
5 | [Address1] | Address Line 1 | |
6 | [Address2] | Address Line 2 | |
7 | [Address3] | Address Line 3 | |
8 | [Town] | Address Line 4 | |
9 | [County] | Address Line 5 | Change from legacy csv: As this is a legacy field, not populated for new addresses since 2018, this field within the ODS Data Search & Export tool (including pre defined reports) will not be populated. Note that the value (where populated) is available via the FHIR Organization Resource in the address.district property. |
10 | [Postcode] | Postcode | |
11 | [LegalStartDate] | Open Date | |
12 | [LegalEndDate] | Close Date | |
13 | NULL | Column 13 | |
14 | RoleID | Organisation Sub-Type Code | Only populated where there is a role (PrimaryRole = 0) that is active or has a legal end date as equal to the organisation’s end date. |
15 | NULL | Column 15 | |
16 | NULL | Column 16 | |
17 | NULL | Column 17 | |
18 | [TelephoneNumber] | Contact Telephone Number | |
19 | NULL | Column 19 | |
20 | NULL | Column 20 | |
21 | NULL | Column 21 | |
22 | ‘1’ | Amended Record Indicator | Set to 1 for Report |
23 | NULL | Column 23 | |
24 | NULL | Column 24 | |
25 | NULL | Column 25 | |
26 | NULL | Column 26 | |
27 | NULL | Column 27 |