We have detected that you are using Internet Explorer to visit this website. Internet Explorer is now being phased out by Microsoft. As a result, NHS Digital no longer supports any version of Internet Explorer for our web-based products, as it involves considerable extra effort and expense, which cannot be justified from public funds. Some features on this site will not work. You should use a modern browser such as Edge, Chrome, Firefox, or Safari. If you have difficulty installing or accessing a different browser, contact your IT support team.
How to understand relationship meta data – how it works, names and definitions
Find out how to understand relationship meta data, including how it works, along with information about names and definitions.
Published: 27 April 2018
Relationships are used to link organisation entities together. These can imply genuine operational links, indicating commissioning or provision, lines of authority or virtual geographical associations.
Relationships – how it works
Any organisation record can be linked to one or more others via relationships.
There is no rigid hierarchy within the model (i.e. any record may be linked to any other record).
The different sides of a Relationship are termed ‘Subject’ (the record that holds the relationship reference) and ‘Target’ (the related Organisation that is referenced)
Relationships are ‘one-way’ – that is, they are only hosted by one of the entities in the pairing
There is no restriction on the number of times a record may be referenced as a Target from other Subject records.
Relationship information is contained in an element tagged ‘Rels’ in the Organisation component of the XML file. Within this element will be one or more elements tagged ‘Rel’, each of which contain the details of one of the Relationships for the Subject entity. Each of these Relationships will include a unique identifier, a name to give context, status and a timespan, as well as a range of information about the target entity including its own identifier.
Relationships are categorised with a Named Relationship value that indicates a context for the Relationship. There are 6 at present but more may be added in future.
Named Relationship: HAS A LEGACY RELATIONSHIP TO
Short Description: Historic data.
Definition: A relationship existing in the data for which the original context is unknown.
Named Relationship: IS A SUB-DIVISION OF
Short Description: Department/Programme-toOrganisation/Site
Definition: The Organisation of which the subject entity forms a sub-division or component (such as a department or programme of work).
NHS ENGLAND (REGION, LOCAL OFFICE)
IS A SUB-DIVISION OF
NHS ENGLAND (REGION)
Named Relationship: IS DIRECTED BY
Short Description: Influenced or directed through policy.
Definition: The primary Organisation by which the subject entity is influenced or directed, through policy, legal authority or contractual agreements
IS DIRECTED BY
Named Relationship: IS COMMISSIONED BY
Short Description: Provider-to-Commissioner
Definition: An Organisation commissioning health care or related services from the subject entity
PRESCRIBING COST CENTRE
IS COMMISSIONED BY
CLINICAL COMMISSIONING GROUP
Named Relationship: IS LOCATED IN THE GEOGRAPHY OF
Short Description: Geographical aggregator.
Definition: An administrative geography, organisation or subdivision of an organisation, within the boundary of which the subject entity is physically located. Supplied for aggregation purposes only. e.g. Fields 3 and 4 in current files.
INDEPENDENT SECTOR HEALTHCARE PROVIDER
IS LOCATED IN THE GEOGRAPHY OF
NHS ENGLAND (REGION, LOCAL OFFICE)
Named Relationship: IS OPERATED BY Short Description: Site-to-Organisation Definition: The Organisation that is responsible for operating and managing services within the subject entity.Does not necessarily denote ownership.
CARE HOME SITE
IS OPERATED BY
CARE HOME HQ
Relationship names are defined and maintained within the Data Item Catalogue and further information regarding how the Relationships Component works within the XML can be found within section 9 of the Technical Specification.
Both the Technical Specification and the Data Item Catalogue are published on our website or within the XML Supporting Products pack on TRUD.