FHIR UK Core R4 — Interoperability
Version 1.0 — Effective 6 April 2026 — Clarifia Ltd
Clarifia 1.0 conforms to FHIR UK Core R4 (STU3) as published by NHS England. Our API implementation follows the NHS England Interoperability Framework to enable seamless, standards-based data transfer between SDEC clinical workflows and GP clinical systems.
Clarifia’s API design adheres to the NHS England Interoperability Framework, which mandates the use of nationally agreed standards for health data exchange to eliminate proprietary integration barriers across the NHS estate. Our implementation aligns with the following framework pillars:
AuditEvent resource providing end-to-end traceability from referral origin to SDEC disposition.The following FHIR resources are implemented by the Clarifia API, profiled against the relevant UK Core Implementation Guide profiles. All resources are validated against the HAPI FHIR Validator with the UK Core IG loaded prior to storage.
| Resource | UK Core Profile | Interactions | Clinical Purpose |
|---|---|---|---|
| Patient | UKCore-Patient | readsearch | Retrieve patient demographics for SDEC triage context |
| Encounter | UKCore-Encounter | createreadupdatesearch | Record SDEC triage encounter and disposition outcome |
| ServiceRequest | UKCore-ServiceRequest | createreadupdate | SDEC referral request from GP or 111 to acute trust |
| Observation | UKCore-Observation | createreadsearch | NEWS2 vital signs and clinical observations used in Double-String validation |
| Condition | UKCore-Condition | readsearch | Primary presenting diagnosis and exclusion codes for pathway logic |
| Composition | UKCore-Composition | createread | SDEC discharge summary transmitted to GP clinical system |
| AuditEvent | UKCore-AuditEvent | createsearch | Immutable audit trail for Double-String decisions and clinician overrides (DCB0129) |
| Practitioner | UKCore-Practitioner | readsearch | Clinician identity and GMC/NMC registration verification |
A core use case of Clarifia is ensuring that the outcome of an SDEC encounter is communicated back to the patient’s registered GP practice in a structured, coded, and interoperable format — eliminating the legacy reliance on unstructured discharge letters.
ServiceRequest resource is created by the referring system (GP clinical system or NHS 111) and transmitted to the acute trust’s SDEC endpoint via the Clarifia API.Observation (NEWS2) and Condition resources to compute the recommendation.Encounter resource is created capturing admission, triage outcome, and disposition.Composition (structured discharge summary) is created using SNOMED CT UK Edition coded entries and transmitted to the GP’s system via the GP Connect Send Document API.AuditEvent is created at each state transition, providing a complete, immutable audit trail from referral to discharge to the GP communication.Clarifia uses the following nationally mandated coding systems, consistent with the NHS England Interoperability Framework:
| System | OID / URL | Used For |
|---|---|---|
| SNOMED CT UK Edition | http://snomed.info/sct | Clinical findings, procedures, diagnoses |
| NHS Number | https://fhir.nhs.uk/Id/nhs-number | Patient identifier |
| ODS Code | https://fhir.nhs.uk/Id/ods-organization-code | Organisation identifier |
| dm+d | https://dmd.nhs.uk | Medicines and devices |
| ICD-10 | http://hl7.org/fhir/sid/icd-10 | Secondary diagnostic coding |
| LOINC | http://loinc.org | Observation coding (NEWS2 components) |
| CIS2 / NHS Login | https://identity.nhs.uk | Workforce identity (SMART on FHIR) |
The full machine-readable FHIR CapabilityStatement is available at the following endpoints:
GET /fhir/metadata — FHIR CapabilityStatement (JSON)GET /fhir/.well-known/smart-configuration — SMART on FHIR configurationTo request API access credentials, integration documentation, or a connection test against our sandbox environment, contact:
Email: governance@clarifia.ai