Skip to content
All case studiesHealthcare IT

FHIR R4 Bundle Generator for Healthcare Systems

A Java service that turns hospital data — HL7 v2, CSV, JSON — into validated FHIR R4 bundles (Patient, Encounter, Observation, Practitioner), later repackaged as a Spring Boot microservice.

JavaHAPI FHIRSpring BootHL7 v2 → FHIR R4
99%
FHIR profile conformance
3
Input formats (HL7 v2, CSV, JSON)

The challenge

Downstream analytics and partner systems needed data in FHIR R4, but the source hospital data arrived as HL7 v2 messages, CSV extracts and JSON — each with its own quirks. Hand-mapping was slow and error-prone, and non-conformant bundles were rejected further down the line.

Approach

  • Built a Java conversion engine on HAPI FHIR that maps each input format to FHIR R4 resources — Patient, Encounter, Observation, Practitioner — and validates every bundle against the target FHIR profiles before it leaves.
  • Refactored the engine into a standalone Spring Boot microservice so it can be deployed, scaled and versioned on its own rather than baked into one app.

Result

Bundles now pass profile validation at 99% conformance, three input formats are handled by one service, and the FHIR layer can evolve without touching the systems around it.

Add volume (bundles/day), the systems it feeds, and the delivery timeline via the admin panel.

Want an outcome like this?

99% conformance to FHIR profiles and a clean, independently deployable service that analytics and partner platforms can consume.

Book a call
Next case study →

Victoria — reliable email-triage agent