Organisation Data Service
Organisation Data Service (ODS) provides organisation identifiers used across health and social care systems.
Role in NHS App Architecture
ODS provides organisation identity. In this wiki it is the bridge between patient registration, provider identity, endpoint lookup, supplier configuration, and service-route assumptions.
Route Placement
ODS appears in registered-GP and endpoint lookup patterns, GP Connect route analysis, Patient Care Aggregator / Wayfinder specialty validation, and organisation-level onboarding or provider configuration.
DPHC Relevance
ODS identifiers are likely needed to determine whether Defence Primary Healthcare (DPHC) organisations are represented in NHS systems in a way that NHS App, GP Connect, Personal Demographics Service (PDS), and supplier onboarding can use.
The current ODS pass confirms relevant MOD / Defence Medical Services (DMS) records, including DDG Defence Medical Services, related DMS sites, XDM Ministry of Defence, and S22029 Ministry of Defence as a Scottish GP Practice. A DGP boundary check also found active prescribing-cost-centre records at the DGP guide postcode WS14 9PY, while simple active ORD name searches did not return a directly named Defence Global Practice or Central European Practice record. ODS GP-practice reference data shows that commonly named GP Practice ODS codes are Prescribing Cost Centre codes and that GP Practice is a role-based subset. This narrows the organisation-identity question but does not prove DPHC Firmbase or DPHC(O) PDS registered-GP state, practice-level GP Practice role, supplier enablement, or NHS App GP-linked feature availability.
Dependencies
| Dependency | Why it matters |
|---|---|
| Organisation code | Identifies the DPHC or ordinary NHS organisation. |
| Organisation type | May determine whether the organisation is treated as a GP practice, MOD healthcare organisation, or another body. |
| Endpoint / directory linkage | May connect to Spine Directory Service (SDS) or provider endpoint lookup. |
| Supplier / practice enablement | May determine GP Connect PFS, Interface Mechanism 1 (IM1), or other route availability. |
What This Does Not Prove
An ODS code alone does not prove that an NHS App feature works, that a GP clinical-system endpoint exists, or that DPHC is onboarded for GP Connect, IM1, NHS Notify, Patient Care Aggregator / Wayfinder, or direct NHS App integration.
Evidence Needed
- ODS codes for DPHC Firmbase practices, Defence Global Practice, Central European Practice, and any DGP-postcode candidate records that are actually used for patient registration.
- Organisation type, GP Practice role status, and relationship to ordinary NHS GP practices.
- Whether NHS App GP-linked services check ODS type, GP supplier, GP Connect PFS onboarding, or other metadata.
- Whether Programme Cortisone changes ODS relationships or supplier registration.
Related Routes
Current Source Confidence
High for ODS component role. Not evidenced for DPHC organisation configuration or feature availability.