Examples

The intu-dev-examples repository contains 13 self-contained projects covering 39 channels across every major healthcare integration vertical. Each example includes its own configuration, Docker Compose stack, sample test data, and step-by-step instructions.

git clone https://github.com/intuware/intu-dev-examples.git
cd intu-dev-examples

Prerequisites

Docker and Docker Compose are required. Node.js 18+ and intu-dev are optional if running outside Docker. Every example includes PostgreSQL-backed message storage so you can explore processed messages in the dashboard at http://localhost:3000 (admin / admin).

Quick Reference

Example	Channels	Sources	Destinations	Standards
Laboratory	4	TCP, SFTP	TCP, HTTP, File, SFTP	ORM, ORU
Pharmacy	3	TCP, FHIR	TCP, HTTP	RDE, RDS, MedicationRequest
Radiology	4	TCP, DICOM	TCP, HTTP, DICOM, FHIR	ORM, ORU, DICOM, ImagingStudy
Patient Admin / ADT	5	TCP	HTTP, FHIR, Kafka, SFTP	ADT A01/A03/A04/A08/A40
Insurance / Payer	4	HTTP, SFTP	HTTP, Database	X12 270/271/837/835/278
Public Health	4	TCP, SFTP, File	SFTP, HTTP	ORU, VXU, ADT
Scheduling	3	SFTP, Database	HTTP, SMTP	SIU, CSV
HIE	3	HTTP, TCP	FHIR, HTTP, Direct	CCDA, ADT, FHIR Bundle
Billing	2	TCP, HTTP	Database, File	DFT, X12 837P
Document Exchange	2	HTTP, IHE	SFTP, File	CCDA, IHE XDS.b
Blood Bank	2	TCP, SFTP	TCP, HTTP	ORM, ORU
Medical Devices	2	TCP	HTTP, SMTP	ORU
FHIR-to-HL7	1	FHIR	File	12 FHIR resources to HL7v2

Laboratory

4 channels — TCP/MLLP, SFTP — ORM, ORU

Lab integrations are the most common interface in healthcare IT. Hospitals send ORM^O01 lab orders from the EHR to the Laboratory Information System (LIS) and receive ORU^R01 results back. Intra-facility flows use real-time TCP/MLLP, while reference labs exchange HL7 files via SFTP. This example covers both patterns: real-time order entry, SFTP result pickup from reference labs, result archival, and outbound SFTP order routing.

cd laboratory && docker-compose up --build

Pharmacy

3 channels — TCP/MLLP, FHIR — RDE, RDS, MedicationRequest

Pharmacy integrations connect the EHR’s CPOE to pharmacy dispensing systems. Medication orders flow as RDE^O11 messages, and dispense confirmations return as RDS^O13. This example also demonstrates the FHIR-to-legacy bridge pattern: accepting a FHIR R4 MedicationRequest and converting it to an HL7v2 RDE message for pharmacies that only speak HL7v2.

cd pharmacy && docker-compose up --build

Radiology

4 channels — TCP/MLLP, DICOM, FHIR — ORM, ORU, DICOM C-STORE, ImagingStudy

Radiology integrations span two worlds: HL7v2 for orders and reports, and DICOM for imaging. This example shows EHR imaging orders routed to the RIS, radiology reports returned to the EHR, DICOM image routing between PACS systems, and a DICOM-to-FHIR bridge that converts DICOM metadata into FHIR ImagingStudy resources. The Docker stack includes Orthanc (open-source PACS) and HAPI FHIR Server for end-to-end testing.

cd radiology && docker-compose up --build

Patient Administration / ADT

5 channels — TCP/MLLP, FHIR, Kafka, SFTP — ADT A01/A03/A04/A08/A40

ADT messages are the backbone of every hospital’s integration engine. Every downstream system — pharmacy, lab, radiology, billing, scheduling — needs to know when a patient is admitted, updated, discharged, or merged. This example demonstrates registration broadcast, admit-to-FHIR Encounter conversion, demographics streaming to Kafka, discharge summaries via SFTP, and patient merge notifications.

cd patient-admin && docker-compose up --build

Insurance / Payer

4 channels — HTTP, SFTP, Database — X12 270/271, 837, 835, 278

Insurance integrations handle the financial side of healthcare using the X12 EDI standard. This example covers real-time eligibility inquiry (270/271), batch claims submission from SFTP to a clearinghouse API (837), ERA remittance processing into a billing database (835), and prior authorization requests (278).

cd insurance && docker-compose up --build

Public Health Reporting

4 channels — TCP/MLLP, SFTP, File — ORU, VXU, ADT

Public health reporting is mandated by law in every US state. This example covers all four mandatory reporting channels: Electronic Lab Reporting, immunization reporting to the IIS, syndromic surveillance from emergency departments, and cancer case reporting to tumor registries. Most state health departments accept data via SFTP file drops.

cd public-health && docker-compose up --build

Scheduling

3 channels — SFTP, Database, SMTP — SIU, CSV

Scheduling integrations synchronize appointment data between systems. External clinics send SIU^S12 appointment files via SFTP, bulk imports arrive as CSV, and the system generates appointment reminder emails by polling a database. Includes a Mailpit container so you can see the reminder emails in a web inbox.

cd scheduling && docker-compose up --build

Health Information Exchange / HIE

3 channels — HTTP, TCP/MLLP, FHIR, Direct — CCDA, ADT, FHIR Bundle

Health Information Exchanges enable clinical data sharing across organizations. This example demonstrates CCD/CCDA-to-FHIR Bundle conversion, ADT admission notification broadcasting to HIE participants, and patient referrals via Direct secure messaging. Includes a HAPI FHIR Server to simulate the FHIR-based HIE repository.

cd hie && docker-compose up --build

Billing / Revenue Cycle

2 channels — TCP/MLLP, HTTP — DFT, X12 837P

Billing integrations bridge clinical systems and revenue cycle management. DFT^P03 charge messages post charges to the billing database, and the superbill channel converts a JSON superbill into an X12 837P professional claim file.

cd billing && docker-compose up --build

Document Exchange

2 channels — HTTP, IHE — CCDA, IHE XDS.b

Clinical document exchange for care transitions and regulatory compliance (Meaningful Use, 21st Century Cures Act). Receives CCDA documents via HTTP and forwards them to a partner organization’s SFTP server, and ingests documents from an IHE XDS.b repository for local archival.

cd document-exchange && docker-compose up --build

Blood Bank

2 channels — TCP/MLLP, SFTP — ORM, ORU

Blood bank integrations manage the transfusion medicine workflow: ordering blood products and receiving crossmatch/typing results. Real-time orders flow via TCP/MLLP within the hospital, while external regional blood banks deliver results via SFTP file drops.

cd blood-bank && docker-compose up --build

Medical Devices / IoT

2 channels — TCP/MLLP, SMTP — ORU

Medical device integration feeds data from bedside monitors, ventilators, and infusion pumps into the EHR. Vital signs arrive as ORU^R01 messages over TCP and are forwarded to the EHR’s REST API. Critical alarms are routed to clinical staff via email. Includes Mailpit for viewing alarm notification emails.

cd medical-devices && docker-compose up --build

FHIR-to-HL7 Comprehensive

1 channel, 12 FHIR resources — FHIR R4 Listener — ADT, ORU, ORM, RDE, VXU, SIU

A single FHIR R4 gateway channel that accepts 12 resource types and routes each to the appropriate HL7v2 transformation. The transformer dispatches by resourceType: Patient to ADT^A08, Encounter to ADT^A01, Observation to ORU^R01, DiagnosticReport to ORU^R01, MedicationRequest to RDE^O11, AllergyIntolerance to ADT^A08 with AL1, ServiceRequest to ORM^O01, Condition to ADT^A08 with DG1, Immunization to VXU^V04, Appointment to SIU^S12, Coverage to ADT^A08 with IN1, and Procedure to ORU^R01 with PR1. Use this as a mapping reference when building FHIR-to-legacy bridges.

cd fhir-to-hl7-comprehensive && docker-compose up --build