Why is data processing standardization in healthcare important?

In the healthcare industry, system interoperability is the cornerstone of modern technological solutions. The variety of formats and the lack of consistent standards hinder data exchange between healthcare providers. Standards developed by the HL7 organization—such as HL7 v2, HL7 v3, and FHIR—help overcome these challenges by enabling fast and secure data processing.

HL7 standards: The evolution of interoperability

HL7 v2 – messaging in ASCII

The HL7 v2 standard, developed in 1989, facilitates message exchange between systems. While these messages are widely used, they rely on textual ASCII structures, making interpretation and integration challenging in complex environments.

Example of an HL7 v2 message:

MSH|^~\&|SENDING_APP|SENDING_FACILITY|RECEIVING_APP|RECEIVING_FACILITY|202306180930||ORU^R01|123456789|P|2.5\r

PID|||12345||Doe^John^J||19700101|M|||123 Main St^^Anytown^CA^12345||(555)555-5555||S||N\r

OBX|1|NM|100779^eGFR^L||84|mL/min/1.73||N|F

HL7 v3 – complexity that failed to gain popularity

The attempt to introduce semantic interoperability in HL7 v3 (based on XML) was unsuccessful due to the complexity of its specifications and the high implementation costs.

FHIR – A next-generation standard

FHIR (Fast Healthcare Interoperability Resources) combines the simplicity of HL7 v2 with the semantic interoperability of HL7 v3. It is based on RESTful APIs and supports data in JSON and XML formats. FHIR shifts the focus from healthcare institutions to the patient, enabling better management and data processing throughout the care cycle.

FHIR in practice: a project for 9amHealth

9amHealth is a U.S.-based startup offering online healthcare services for patients with diabetes, obesity, and high blood pressure. The project’s goal was to develop a system that integrates medical data from multiple sources, including laboratories and medical devices, while ensuring compliance with regulations such as HIPAA.

Scope of work carried out by fireup.pro:

✔️ Backend and Frontend Implementation

Developed a scalable architecture enabling real-time processing of large volumes of medical data.

✔️ Integration with Laboratory Providers

Leveraged HL7 v2 and FHIR standards to automate the exchange of laboratory test results in compliant formats.

✔️ Data Storage

Implemented a dual approach where data in HL7 v2 format was converted to FHIR R4, allowing for reuse in other contexts.

Technical aspects of implementing FHIR

Treatment, patient data processing, test results, and sensitive data management in the healthcare industry.

HAPI FHIR – Tool Ecosystem

fireup.pro, in collaboration with the client, utilized the HAPI FHIR library, which supports both HL7 v2 and FHIR. This enabled the following:

  • Parsing HL7 v2 messages into Java objects.
  • Creating and processing FHIR resources in JSON and XML formats.
  • Exposing a RESTful server for FHIR resources.

Code Example:

FhirContext ctx = FhirContext.forR4();

Observation observation = new Observation();

observation.setCode(new CodeableConcept().setText(„Blood Glucose Level”));

observation.setValue(new Quantity(5.5).setUnit(„mmol/L”));

Converting HL7 v2 to FHIR

Using the HL7ToFHIRConverter, data from HL7 v2 messages were transformed into FHIR resources, ensuring compatibility and enhanced reusability.

HL7ToFHIRConverter converter = new HL7ToFHIRConverter();

Bundle fhirBundle = converter.convert(hl7Message);

Data Storage and Processing

FHIR data was stored in JSON format across databases such as PostgreSQL and MySQL, as well as in NoSQL systems like MongoDB to handle larger data volumes effectively.

Standardized Coding

SNOMED CT (Systematized Nomenclature of Medicine – Clinical Terms)

  • Used for coding clinical symptoms, such as high blood pressure.
  • Ensures consistency and interoperability in describing medical conditions and procedures.

LOINC (Logical Observation Identifiers Names and Codes)

  • Focused on defining laboratory test results and observations.
  • Facilitates standardized reporting and sharing of lab data across systems.

UCUM (Unified Code for Units of Measure)

  • Provides a standard for representing units of measurement, ensuring accuracy in data interpretation.
  • Example: Standardizing units like „mmHg” for blood pressure or „mL/min” for lab results.
Modern technologies and data processing in the world of healthcare – 21st-century healthcare.

Why FHIR?

➡️ Interoperability
FHIR enables integration with various healthcare systems worldwide, ensuring seamless data exchange between solutions.

➡️ Data Flexibility
Support for JSON and XML formats allows data adaptation to diverse IT environments.

➡️ Performance and Scalability
With RESTful API and tools like HAPI FHIR, systems can efficiently process data and integrate with other solutions, facilitating scalability under increasing workloads.

➡️ Security
FHIR complies with international standards like HIPAA, ensuring the protection of patient data.

Technical Summary


The implementation of FHIR in the 9am.Health project demonstrates that this standard is the future of healthcare. Fireup.pro successfully integrated legacy HL7 v2 standards with modern FHIR, providing the client with scalability, interoperability, and regulatory compliance.

🚀 If your company needs a technological partner to implement modern IT solutions in the healthcare industry, contact fireup.pro – experts in medical data processing.