intu

Integration as Code for Healthcare
Build, version, and deploy healthcare integration pipelines using YAML and TypeScript.

Website · Docs · npm · Issues

intu is a Git-native, AI-friendly healthcare interoperability framework. Define channels as YAML config and TypeScript transformers, store everything in Git, and run a production-grade engine with a single command.

Why intu?

• Integration as Code — Pipelines are YAML + TypeScript files in Git. No GUI, no database config, no vendor lock-in.
• Healthcare-native — HL7v2, FHIR R4, X12, CCDA, DICOM parsers and connectors built in.
• Fast — Go binary + Node.js worker pool. Sub-millisecond transforms. Hot-reload on file change.
• AI-friendly — Declarative config means LLMs can generate, modify, and review pipelines.
• Full pipeline — Preprocessor → Validator → Source Filter → Transformer → Destination Filter → Destination Transformer → Response Transformer → Postprocessor.
• 12 source connectors, 13 destination connectors — HTTP, TCP/MLLP, FHIR, Kafka, Database, File, SFTP, Email, DICOM, SOAP, IHE, Channel, SMTP, JMS, Direct, Log.

Install

Via npm (recommended):

npm i -g intu-dev

This installs the Go binary for your platform automatically.

From source:

go build -o intu .

Quick Start

intu init my-project
cd my-project
npm run dev

intu init scaffolds the project and runs npm install. npm run dev starts the engine with auto-compile and hot-reload.

Add a channel:

intu c my-channel

Dashboard

intu ships with a built-in web dashboard for monitoring channels, browsing messages, and triggering reprocessing.

Project Structure

.
├── intu.yaml              # Root config + named destinations
├── intu.dev.yaml          # Dev profile overlay
├── intu.prod.yaml         # Prod profile overlay
├── .env                   # Environment variables
├── src/
│   ├── channels/
│   │   └── sample-channel/
│   │       ├── channel.yaml   # Channel config (source, destinations, pipeline)
│   │       ├── transformer.ts # TypeScript transformer (IntuMessage in, IntuMessage out)
│   │       └── validator.ts   # Optional validator
│   ├── types/
│   │   └── intu.d.ts          # IntuMessage & IntuContext type declarations
│   └── lib/
│       └── index.ts           # Shared utilities
├── package.json
├── tsconfig.json
└── README.md

CLI Reference

All commands accept --log-level (debug|info|warn|error) (default: info).

Project & Build

Channel Management

Operations

IntuMessage

Every byte flowing through intu is wrapped in an IntuMessage — a universal envelope carrying the raw body, transport protocol, and protocol-specific metadata. IntuMessage is created in Go the moment a source connector finishes receiving data and flows unchanged through every pipeline stage.

┌─────────────────────────────────────────────────────┐
│ IntuMessage                                         │
│                                                     │
│  body          raw payload (string or base64)       │
│  transport     "http" | "kafka" | "file" | ...      │
│  contentType   "json" | "hl7v2" | "fhir_r4" | ...  │
│  http/kafka/   transport-specific metadata          │
│  file/tcp/...  (only matching transport populated)  │
│  sourceCharset original encoding (empty = UTF-8)    │
│  metadata      arbitrary key-value pairs            │
└─────────────────────────────────────────────────────┘

TypeScript transformers receive IntuMessage as their first argument and return a (possibly modified) IntuMessage. The contract is the same for validators, filters, preprocessors, and postprocessors. See the full IntuMessage specification for the Go struct, TypeScript interface, serialization formats, and design principles.

Sources & Destinations

Sources

Destinations

Data Types

raw · json · xml · csv · hl7v2 · hl7v3/ccda · fhir_r4 · x12 · binary

Destinations Config

Define named destinations in intu.yaml:

destinations:
  kafka-output:
    type: kafka
    kafka:
      brokers: [${INTU_KAFKA_BROKER}]
      topic: output-topic
    retry:
      max_attempts: 3
      backoff: exponential
      initial_delay_ms: 500

Channels reference them by name (multi-destination supported):

destinations:
  - kafka-output
  - name: audit-http
    type: http
    http:
      url: https://audit.example.com/events

Contributing

Contributions are welcome — bug reports, docs, and code.

• Issues & PRs: github.com/intuware/intu-dev
• Contact: ramnish@intuware.com

License

intu is licensed under the Mozilla Public License 2.0 (MPL-2.0).