Topic

FHIR & HL7 Standards

HL7 v2 and FHIR are the two standards most NHS integration traffic runs on. v2 announces events with context left implicit; FHIR states resources with everything explicit. These articles cover both, plus UK Core, the NHS profile set that turns deliberately permissive base FHIR into something two Trust systems can actually agree on.

FHIR & HL7 Standards
Latest first

All posts

Preview card for the article: HL7 v2 to UK Core FHIR: mapping the messages NHS systems actually send
Preview card for the article: UK Core conformance in practice: what it means for your NHS integrations
Preview card for the article: FHIR resources explained: Patient, Encounter, Observation and the ones you'll use most
Preview card for the article: HL7 v2 for NHS teams: the message types you'll actually meet (ADT, ORU and friends)
Preview card for the article: What Is FHIR and Why It Is Transforming Healthcare Integration
Preview card for the article: HL7 vs FHIR: What's the Difference and Why It Matters

Common questions

What is the difference between HL7 v2 and FHIR?
HL7 v2 is a message format: an event announcement built from segments, with much of its meaning carried by local convention. FHIR is a resource model: discrete records with explicit structure, references and statuses, exchanged over web APIs. Converting between them is a translation exercise, not a format change.
What is UK Core?
UK Core is the NHS's set of FHIR R4 profiles: nationally maintained constraints defining which elements are mandatory, how the NHS number is carried, and which value sets each coded element must draw from. Conformance means validating against a named profile at a pinned guide version, terminology included.

Ready when you are

Turn healthcare workflow ideas into production-ready delivery.

Pick the products you need and an integration specialist will get you set up. No call centre, no hard sell just a straight conversation about your integration.

Talk to sales