HL7 & FHIR CourseFOR HEALTH IT PROS$45 · one paymentJoin the list

New course

HL7 & FHIR

Hospital data moves in two formats. Pipe-delimited HL7 v2 feeds carry most of it today, and FHIR REST APIs carry the new work. Learn both on real integration projects.

  • 21lessons planned
  • 2chapters
  • 13projects
  • 0out now

What is FHIR?

Fast Healthcare Interoperability Resources: a standard from HL7 International for exchanging health data over web APIs, with published mappings from HL7 v2.

Resources, not segments

Data lives in resources such as Patient, Observation, and Appointment, in JSON or XML, read and written over REST.

Your HL7 v2 skills carry over

The clinical events stay the same. A registration is still a registration. The syntax and the transport change.

Profiles and extensions

Profiles constrain the base resources for a use case. Extensions add what the base spec leaves out.

Where new interfaces go

Major EHR vendors expose FHIR APIs today, and US interoperability rules point the same way.

One event. Two formats.

Each project in the course works with both sides: the HL7 v2 message your engine receives and the FHIR resource your API serves.

FeedHL7 v2.5.1ADT^A04 (excerpt)
MSH|^~\&|HOSTEHR|MAIN|ARIA|RADONC|20261003091500||ADT^A04^ADT_A01|MSG00001|P|2.5.1
EVN|A04|20261003091500
PID|1||MRN0042^^^MAIN^MR||DOE^JANE^Q||19620314|F
PV1|1|O|RADONC^LINAC2^^MAIN
APIFHIR R4Patient
{
  "resourceType": "Patient",
  "identifier": [
    {
      "type": {
        "coding": [{"system": "http://terminology.hl7.org/CodeSystem/v2-0203", "code": "MR"}]
      },
      "value": "MRN0042"
    }
  ],
  "name": [{"family": "DOE", "given": ["JANE", "Q"]}],
  "gender": "female",
  "birthDate": "1962-03-14"
}
PID-3Patient.identifier
PID-5Patient.name
PID-7Patient.birthDate
PID-8Patient.gender

Watch for: PV1 becomes a separate Encounter resource. Decide early which system owns it.

21 lessons in 2 chapters Lessons in production

From your first segment to a working integration hub. Lessons release in order as each one is finished.

Chapter 01

Fundamentals

The vocabulary. Eight lessons of short, practical exercises.

01The healthcare data landscapeIn production
02HL7 v2 anatomy: segments, fields, messagesIn production
03Parsing pipe-delimited messagesIn production
04Patient identity and ADT workflowsIn production
05FHIR resources 101In production
06REST and search: reading dataIn production
07Writing data: create, update, transactionsIn production
08Terminologies: SNOMED CT, LOINC, ICD-10In production

Chapter 02

Projects

Thirteen builds where the fundamentals turn into working integrations.

09Real-time ADT feed listenerIn production
10Lab results dashboardIn production
11Scheduling: appointments and slotsIn production
12Medication orders and dispenseIn production
13Clinical documents: CDA to FHIRIn production
14SMART on FHIR appIn production
15Terminology service integrationIn production
16Bulk data exportIn production
17Audit events and provenanceIn production
18Subscriptions and notificationsIn production
19Consent managementIn production
20EHR sandbox integrationIn production
21Capstone: hospital integration hubIn production

Join the list. Pay once.

Get a short note each time a new lesson is out. The full course is one payment, with lifetime access.

Built for interface work

Written by an integration engineer with 18 years of HL7 work in live hospital environments.

Real message shapes

Examples follow HL7 v2.5.1 and FHIR R4 as interfaces send them.

Both sides of the engine

Every project covers the v2 feed and the FHIR API.

Projects, not slides

Thirteen builds, from an ADT listener to a capstone hub.

Access for life

One payment. Come back when you need a refresher.

Updates included

New lessons and fixes at no extra charge.

Questions before you start

Anything else? Email hello@radoncplaybooks.com.

You need to know what an EHR does day to day. The project lessons use JavaScript, and each one explains the code it uses.

No. Most of the patterns carry over. Knowing what sits under a FHIR API is what lets you debug the failures it hides.

Most do. The course teaches both formats, and how an integration engine translates between them. You will work with both for years.

FHIR R4. It is the version most EHR vendors run in production, and core resources such as Patient and Observation are normative in R4.

No. No lesson is out. The rest release one at a time as each one is finished. Join the list and you get a note for each release.

Learn the formats your interfaces speak

Lessons release one at a time. The full course is $45, one payment.