Mickiesoft

Este artículo solo está disponible en inglés por el momento.

Healthcare

HL7 FHIR Explained: A Developer's Guide to Healthcare Interoperability

Nov 6, 2026
3 min de lectura
HL7 FHIR Explained: A Developer's Guide to Healthcare Interoperability

A patient's information is usually spread across several systems: the hospital record, the lab, the pharmacy, an insurer and increasingly a mobile app. Each one was built by a different vendor with its own data model. Interoperability is the work of getting those systems to exchange data reliably and with the same meaning on both sides. HL7 FHIR has become the main standard for doing that in new projects.

HL7 v2 and FHIR: what is the difference?

HL7 version 2 has been used inside hospitals for decades. It sends pipe-delimited messages such as admissions, discharges and transfers (ADT), lab orders and results. It is everywhere, but each installation tends to have its own local variations, and it was designed for messaging inside a hospital network rather than for web and mobile apps.

FHIR (Fast Healthcare Interoperability Resources) takes a web-first approach. Data is organised into small, well-defined resources exchanged over REST using JSON or XML. Release 4 (R4) is the version most implementations and national guides are built on today, with R5 published as the next step.

HL7 v2FHIR
FormatPipe-delimited segmentsJSON or XML resources
TransportUsually MLLP over TCP inside the networkHTTPS REST APIs, plus messaging and documents
Best forExisting in-hospital feedsApps, partner APIs, cloud and mobile
Developer experienceSpecialist knowledge neededFamiliar to any web developer

FHIR building blocks

  • Resources such as Patient, Practitioner, Encounter, Observation, Condition, MedicationRequest, DiagnosticReport and Appointment.
  • REST interactions: read, search, create, update and history, for example GET /Patient?identifier=....
  • Terminologies such as LOINC for lab tests, SNOMED CT for clinical terms and ICD-10 for diagnoses, so a code means the same thing on both sides.
  • Profiles and implementation guides that narrow the base standard for a country or use case, specifying which fields are required and which code systems to use.
  • Bundles to send several related resources together, for example a lab report with its observations.

SMART on FHIR for apps

When a third-party app needs to read or write data in a health record system, SMART on FHIR provides the security layer. It uses OAuth 2.0 and OpenID Connect so the app gets only the scopes it needs, such as reading a single patient's observations, and the patient or clinician grants that access explicitly. If you are building an app that will plug into existing EHR platforms, design around SMART launch flows from the start.

A practical integration architecture

Few organisations can replace their HL7 v2 feeds overnight. A pattern that works well is:

  1. Keep v2 inside, expose FHIR outside. An integration engine receives existing HL7 v2 messages from lab and admission systems and maps them to FHIR resources.
  2. Run a FHIR server as the shared layer. Open-source servers are mature, and managed FHIR services are offered by the major cloud providers.
  3. Put an API gateway in front for authentication, rate limiting and logging.
  4. Publish events when key resources change, so downstream systems such as billing or notifications react without polling.
  5. Validate everything against your profiles in CI, so a bad mapping is caught before it reaches a partner.

Common pitfalls

  • Patient matching. Different systems use different identifiers. Agree on a master patient index or matching rules early.
  • Free-text codes. Mapping local lab test names to LOINC is slow, manual work. Budget for it.
  • Assuming "FHIR-compliant" means compatible. Two FHIR systems can still disagree on profiles and code systems. Always check the implementation guide each side follows.
  • Ignoring audit. Every read of patient data through an API should be logged with who, what and why.

How Mickiesoft can help

Mickiesoft builds APIs, integration layers and the web and mobile apps on top of them. If you need a FHIR API for your product, an HL7 interface to a lab or hospital, or a plan for moving off point-to-point integrations, our healthcare app development team can help.

Need two health systems to talk to each other?

Mickiesoft designs and builds FHIR APIs, HL7 interfaces and integration layers for clinics, labs and health-tech products.

Talk to an Engineer

Preguntas frecuentes

Encuentre respuestas a las preguntas más habituales sobre nuestros servicios, nuestro proceso y nuestras capacidades.

Etiquetas:HL7 FHIRhealthcare interoperabilityFHIR API developmentSMART on FHIRHL7 v2 integrationhealthcare software developmentelectronic health records