Version: 0.0.16 | Published: 22 Sep 2026 | Updated: 12 days ago
ind-dataset-logo

Open Referral UK

Dataset

Summary

Publication Version:
3.0.0
Type:
  • Information standards
  • Technical standards and specifications
Applies To:
  • Government organisations
  • Public sector bodies
  • NHS trusts
  • NHS foundation trusts
  • Integrated care boards
  • Vendors
  • Digital Health Agencies and NGOs
Impacts On:
Local authority service directories, public-service discovery and service integration.
Topics:
  • Data
  • Data definitions and terminologies
  • Form
  • Open
  • Referrals
  • Service
Care Settings:
  • Community health
  • Social care
Alternate Name:
  • Record and share information about public services in local authorities
  • ORUK
  • Human Services Data Specification (HSDS)
Publication Date:
01 September 2023

Contact Point

Documentation

Description:
The OpenReferral schema defines a structure for human services data - that is, a directory of services that meet human needs. Open Referral UK extends Open Referral to support richer data where needed. It then constrains the resultant schema by means of an application profile which says what fields are recommended for English use and what external vocabularies to reference.

Data Model Diagram for the Open Referral UK data model v3.0

///mermaid erDiagram accTitle: Data Model Diagram for the Open Referral UK data model v3.0 accDescr: Entity relationship diagram illustrating the Open Referral UK v3.0 data standard schema. ORGANIZATION { string id PK string name string description string email string url string logo string uri } SERVICE { string id PK string organization_id FK string name string description string url string email string status } LOCATION { string id PK string location_type string name string description float latitude float longitude string external_identifier } SERVICE_LOCATION { string service_id PK,FK string location_id PK,FK } ADDRESS { string id PK string location_id FK string address_1 string city string state_province string postal_code string country string address_type } CONTACT { string id PK string organization_id FK string service_id FK string location_id FK string name string title } PHONE { string id PK string contact_id FK string service_id FK string location_id FK string number string description } SCHEDULE { string id PK string service_id FK string location_id FK string service_at_location_id FK int opens_at int closes_at string valid_from string valid_to } TAXONOMY { string id PK string name string vocabulary string description } TAXONOMY_TERM { string id PK string taxonomy_id FK string name string description string parent_id FK } ORGANIZATION ||--o{ SERVICE : provides ORGANIZATION ||--o{ CONTACT : has SERVICE ||--o{ SERVICE_LOCATION : delivered_at LOCATION ||--o{ SERVICE_LOCATION : hosts LOCATION ||--o{ ADDRESS : has LOCATION ||--o{ CONTACT : has SERVICE ||--o{ CONTACT : has CONTACT ||--o{ PHONE : has SERVICE ||--o{ PHONE : has LOCATION ||--o{ PHONE : has SERVICE ||--o{ SCHEDULE : has LOCATION ||--o{ SCHEDULE : has TAXONOMY ||--o{ TAXONOMY_TERM : contains TAXONOMY_TERM ||--o{ TAXONOMY_TERM : parent_of

  • Explain the Open Referral UK v3.0 Entity Relationship Diagram

    Overview

    This entity relationship diagram illustrates the Open Referral UK version 3.0 standard schema. It specifies 10 core entities and 14 directed one-to-many relationships connecting organizations, services, locations, contacts, schedules, and taxonomies.


    Entities and Attributes

    Organization

    Represents an umbrella body or provider offering community services.

    • id: string (Primary Key)
    • name: string
    • description: string
    • email: string
    • url: string
    • logo: string
    • uri: string

    Service

    Represents a specific service delivered by an organization.

    • id: string (Primary Key)
    • organization_id: string (Foreign Key referencing Organization)
    • name: string
    • description: string
    • url: string
    • email: string
    • status: string

    Location

    Represents a physical place where services are hosted or administered.

    • id: string (Primary Key)
    • location_type: string
    • name: string
    • description: string
    • latitude: float
    • longitude: float
    • external_identifier: string

    Service Location

    A join entity linking services to the physical locations where they are delivered.

    • service_id: string (Composite Primary Key, Foreign Key referencing Service)
    • location_id: string (Composite Primary Key, Foreign Key referencing Location)

    Address

    Represents the postal address for a specific location.

    • id: string (Primary Key)
    • location_id: string (Foreign Key referencing Location)
    • address_1: string
    • city: string
    • state_province: string
    • postal_code: string
    • country: string
    • address_type: string

    Contact

    Represents an individual point of contact tied to an organization, service, or location.

    • id: string (Primary Key)
    • organization_id: string (Foreign Key referencing Organization)
    • service_id: string (Foreign Key referencing Service)
    • location_id: string (Foreign Key referencing Location)
    • name: string
    • title: string

    Phone

    Represents phone numbers associated with contacts, services, or locations.

    • id: string (Primary Key)
    • contact_id: string (Foreign Key referencing Contact)
    • service_id: string (Foreign Key referencing Service)
    • location_id: string (Foreign Key referencing Location)
    • number: string
    • description: string

    Schedule

    Represents opening hours, operating times, or validity dates.

    • id: string (Primary Key)
    • service_id: string (Foreign Key referencing Service)
    • location_id: string (Foreign Key referencing Location)
    • service_at_location_id: string (Foreign Key)
    • opens_at: integer
    • closes_at: integer
    • valid_from: string
    • valid_to: string

    Taxonomy

    Represents a categorization system or controlled vocabulary.

    • id: string (Primary Key)
    • name: string
    • vocabulary: string
    • description: string

    Taxonomy Term

    Represents individual tags or categories within a taxonomy, supporting hierarchical trees.

    • id: string (Primary Key)
    • taxonomy_id: string (Foreign Key referencing Taxonomy)
    • name: string
    • description: string
    • parent_id: string (Foreign Key referencing Taxonomy Term for parent hierarchy)

    Entity Relationships

    • Organization to Service: One Organization provides one or more Services (provides).
    • Organization to Contact: One Organization has one or more Contacts (has).
    • Service to Service Location: One Service connects to one or more Service Locations (delivered_at).
    • Location to Service Location: One Location hosts one or more Service Locations (hosts).
    • Location to Address: One Location has one or more Addresses (has).
    • Location to Contact: One Location has one or more Contacts (has).
    • Service to Contact: One Service has one or more Contacts (has).
    • Contact to Phone: One Contact has one or more Phone numbers (has).
    • Service to Phone: One Service has one or more Phone numbers (has).
    • Location to Phone: One Location has one or more Phone numbers (has).
    • Service to Schedule: One Service has one or more Schedules (has).
    • Location to Schedule: One Location has one or more Schedules (has).
    • Taxonomy to Taxonomy Term: One Taxonomy contains one or more Taxonomy Terms (contains).
    • Taxonomy Term to Taxonomy Term: One Taxonomy Term acts as the parent of one or more sub-terms (parent_of, recursive self-reference).
Is Part Of:
[object Object]

Benefit 1

Benefit statement:
Open Referral UK provides a consistent way of structuring and sharing data about services, so that information can be recorded once and shared across multiple directories.

Benefit 2

Benefit statement:
By adopting Open Referral UK, organisations can reduce the cost and effort of maintaining duplicate directory entries, improve data quality, and make it easier for people to find community help and support.

Benefit 3

Benefit statement:
Councils currently spend significant time and money maintaining multiple overlapping service directories across adult social care, children’s services, SEND, and community support.
Benefit topic:
Local

Benefit 4

Benefit statement:
Adopting an open data standard allows local authorities to break down directory silos, procure software without vendor lock-in, and share data seamlessly with health partners and the voluntary sector.
Benefit topic:
Local

Benefit 5

Benefit statement:
Voluntary and community groups often have to submit and update their service details across dozens of different council, NHS, and independent directories.
Benefit care setting:
Community health
Benefit topic:
Accessibility

Benefit 6

Benefit statement:
With Open Referral UK, the goal is 'enter once, publish anywhere' — reducing the administrative burden on front-line charities and making their services visible to wider audiences, including social prescribing systems.
Benefit care setting:
Community health

Benefit 7

Benefit statement:
Easy to access, accurate and local information on services.

Benefit 8

Benefit statement:
Collaborate and share knowledge with local authorities, organisations, and stakeholders.

Benefit 9

Benefit statement:
Save money and resources by capturing data once, giving frontline workers and advocates easy access to essential information.

Benefit 10

Benefit statement:
Avoid duplicating information and creating new directories from scratch.

Benefit 11

Benefit statement:
Provide users with services they need through a holistic, cross-organisation approach rather than working in silos.

Benefit 12

Benefit statement:
Central Digital and Data Office endorsement offers confidence in the reliability and long-term viability of the standard.

Requirement 1

Must/Should/Could:
Must
Requirement description:
Entities require an id property.

Requirement 2

Must/Should/Could:
Must
Requirement description:
organization.name, service.name, and service.status are mandatory.

Requirement 3

Must/Should/Could:
Must
Requirement description:
Relational links require foreign key pairings (e.g., service_at_location linking service_id and location_id).

Requirement 4

Must/Should/Could:
Should
Requirement description:
Regular opening hours via schedule (opens_at, closes_at).
Conditional Topic:
Data

Requirement 5

Must/Should/Could:
Should
Requirement description:
Contact mechanisms (phone, email, url).
Conditional Topic:
Data

Requirement 6

Must/Should/Could:
Should
Requirement description:
Categorization via external or local taxonomy / taxonomy_term codes.
Conditional Topic:
Data

Review & Status

Contributor:
  • Ministry of Housing, Communities and Local Government (MHCLG)
  • iStand UK
Scope:
Government technology open standard for consistent data exchange, formatting, describing or publishing across public-sector organisations.
Technical Committee:
Cross Government Steering Group for Open Referral UK
Licenced Title:
BSD 3-Clause License
Mandated:
No
Status:
active

Registration

Registration Status:
DSAS - Review Live/In progress
Registration Authority:
Central Digital and Data Office’s (CDDO) Data Standards Authority