iris-fhir-bridge

🧾 Summary

IRIS-FHIR-Bridge is a robust interoperability engine built on InterSystems IRIS for Health, designed to transform healthcare data across multiple formats into FHIR and vice versa. It leverages the InterSystems FHIR Object Model (HS.FHIRModel.R4.*) to enable smooth data standardization and exchange across modern and legacy healthcare systems.

🚀 Key Features

• 🧾 CSV → FHIR Transformation

Convert structured legacy data in CSV format into FHIR resources using InterSystems’ native FHIR object model.

Currently supported FHIR resources:

• Patient
• Encounter
• Observation
• Practitioner
• Organization

✅ Can be easily extended to support other FHIR resource types.

• 🔁 HL7 v2 → FHIR Conversion

• 📝 CCDA → FHIR Conversion

• 🔄 FHIR → HL7 v2 Conversion

📦 Repo Highlights

✅ Sample data files
HL7, CDA, FHIR, CSV sample data files provided in the src/data folder.

✅ Postman Collection Included
Test all REST endpoints using the ready-to-import Postman collection provided in the src/collection folder.

✅ Prerequisites

Make sure you have git and Docker desktop installed.

⚙️ Installation

🐳 Docker (e.g. for dev purposes)

Clone/git pull the repo into any local directory

$ git clone https://github.com/mwaseem75/iris-fhir-bridge.git

Open the terminal in this directory and run:

$ docker-compose up -d

🧰 IPM

Open IRIS for Health installation with IPM client installed. Call in any namespace:

USER>zpm "install iris-fhir-bridge"

🖥️ View Production

Navigate to http://localhost:32783/csp/healthshare/fhirbridge/EnsPortal.ProductionConfig.zen?$NAMESPACE=FHIRBRIDGE& to view the production by using SuperUser | SYS

🔧 Conversion Workflows

🧾 CSV to FHIR (Using FHIR Object Model)

File-Based Service
Parses structured CSV data and transforms it into valid FHIR resources using the InterSystems FHIR Object Model (HS.FHIRModel.R4.). Designed for production environments, this service reads structured CSV files, maps each row to corresponding FHIR resources (e.g., Patient, Encounter, Observation, etc.), and assembles them into a fully compliant FHIR Bundle.
The generated FHIR Bundle is ready to be posted directly to a FHIR server, enabling seamless integration and automated ingestion of legacy tabular data into modern healthcare systems.

Patient synthetic data (CSV format) and generated FHIR bundle resource

The related Business Operation generates a JSON file containing the FHIR Bundle, which can be directly posted to any FHIR-compliant server.

Observation synthetic data (CSV format) and generated FHIR bundle resource

Encounter synthetic data (CSV format) and generated FHIR bundle resource

Practitioner synthetic data (CSV format) and generated FHIR bundle resource

Organization synthetic data (CSV format) and generated FHIR bundle resource

HL7 v2 to FHIR

Transform inbound HL7 v2 messages into FHIR resources
REST API: HL7_Http_Service
Exposed via HTTP and testable with Postman

File-Based Service: HL7_File_Service
Monitors folder and auto-processes HL7 v2 files

CCDA to FHIR

Convert structured clinical documents (CCDA) to FHIR resources using predefined mappings. This allows integration of rich clinical narratives into modern systems.
REST API: CDA_Http_Service
Accepts CCDA XML and converts to FHIR JSON format

FHIR to HL7 v2

Convert FHIR resources back into HL7 v2 message formats, enabling backward compatibility with legacy systems and seamless data round-tripping.
Interop Service: HS.FHIRServer.Interop.Service
Converts FHIR resources back to HL7 v2 messages for legacy system compatibility

Special Thanks to:

Guillaume Rongier for: iris-healthtoolkit-service template for guidance

Thanks