Search for additional instance and reference data

Overview

Use this endpoint to access a range of information contained in CodeSystems to meet your needs. We have CodeSystems that contain regularly changing data such as organisations, practitioners and relationships plus more traditional reference based CodeSystems.

CodeSystem names include the date when they were last updated i.e. ods-organization-code-2024-03-07 so when searching for individual concepts (records within the CodeSystem) it is necessary to perform a search using a $lookup providing the system and code required in addition to any properties you wish to return.

For example:

/CodeSystem/$lookup?system=https://fhir.nhs.uk/Id/ods-organization-code&code=G81086&property=*

Summary information

A summary of each codeSystem can be returned to see which properties are available and which search operations are supported, without attempting to return the data. organisation, role, relationship, postcode and geography information will all generate errors as they are too large to be returned.

Performing a search will default to summary mode and list each instance of the CodeSystem currently stored on the Server. it is expected that we will retain 2-3 versions at any given point.

For example: /CodeSystem?url=https://fhir.nhs.uk/Id/ods-organization-code

The smaller reference based CodeSystems these can be retrieved in full using _summary=false which will return all versions stored on the server in full.

For example: /CodeSystem?system=https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-role&_summary=false

Code Validation

Using the $validate operation you can check whether a code is present within any given ValueSet and you can also provide additional properties to validate their values.

For example: CodeSystem/$validate-code?url=https://fhir.nhs.uk/Id/ods-organization-code&code=RH8&status=active

Organisation Data

ods-organization-code

https://fhir.nhs.uk/Id/ods-organization-code

In addition to the data available through the FHIR Organization resource we also have the following properties:

• related organisations using a Relationship ID such as RE4 (commissioned by), RE6 (operated by), RE8 is Partner to and Nomonated Payee for (RE10)
• presence of successor or predecessor information
• indicator for onward succession
• geographic values such as Local Authority boundary, Integrated Care Board boundary or Lower Super Output Area (LSOA)

organisation-relationship-instance

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/organization-relationship-instance Contains relationship history

organisation-role-instance

Contains role history

Practitioner Data

practitioner

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner

Contains the prescribing practitioner and consultants in a single CodeSystem to enable lookup and validation of Practitioner codes. Practitioners are categorised with a type and role. roles and types can be validated against the practitioner-role CodeSystem.

Types include PGP (General Practitioner), PNURSE - Prescribing Nurse and PDENTCON Dental Consultants.

Roles include PHOSPCON120 (ear nose and throat), PGP1 (principal GP), PNURSE1 (district nurse / health visitor)

Where practitioners are associated to an organisation, the current/latest values is held in a membership property, these include ME1 Parent Practice for GPs and ME4 Parent Trust for a Dental Consultant. More information about the associations can be found in the practitioner-relationship-instance CodeSystem.

This CodeSystem has been designed to enable pracitioners with multiple codes, i.e a Prescribing Code and a General Medical Council (GMC) code to be returned or validated.

Properties numbered from 1 to 8 contain a specific identifier issued by a range of authorities, more information about each assigned identifier including start date and issuing Authority can be found in the practitioner-additional-attribute CodeSystem

practitioner-relationship-instance

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-relationship-instance

Contains relationship history where practitioners are associated with an organisation.

practitioner-additional-attribute

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-additional-attribute

Contains additional information about the identifier issued to a practitioner, in addition to the identifier, the name and ODS code of the Issing authority, start and end dates for the identifier are included.

Geographic Data

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/geography-name

Supports the identification of Office for National Statistics (ONS) identifiers for geographic boundaries used within the ods-organization-code CodeSytem. ODS identifiers for geographic organisations such as ICB and Local Authority can be retreived from the Organization Endpoint.

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/postcode

Contains every postcode within the NHS Postcode Directory and a selection of their geographic boundaries.

More information about how this data is compiled can be found in the NHSPD user guide.

the following Geographic boundaries are included:

• CA cancer alliance
• EW electoral ward
• GOR government office region
• ICB integrated care board
• LA local authority
• LSOA11 2011 lower super output areas
• NHSER NHS England region
• PC parliamentary constituency
• PCO primary care organisation
• SMHPC AED strategic mental health provider collaborative - adult eating disorder
• SMHPC AS strategic mental health provider collaborative - adult secure
• SMHPC CT4 strategic mental health provider collaborative - CYPMH tier 4

Reference Data

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSOrganisationRole

Every organisation has at least one role; a primary role. It may also have additional roles which provide more information about the organisation's function or purpose.

The full list of role codes is contained in this CodeSystem and can be retreived in full or individual role codes can be returned or validated.

This CodeSystem has 1 additional Property: primaryRole which contains a true/false value if the role is a primary role or not.

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/ODSRelationship

Every relationship has a type to describe the nature of the relationship, which includes: is Commissioned by, is operated by and is partner to.

https://digital.nhs.uk/services/organisation-data-service/CodeSystem/practitioner-role

Within the former CSV publications for practitioners, any classifications against a practitioner such as consultant speciality code or nurse prescriber type have been converted to roles and can be returned or validated with this CodeSystem.