Home/Platform/Overview
A clean-sheet integration engine. Every message becomes a typed object, every transform is real code, every hop is durable, and everything can be replayed. Run it on premise, on Kubernetes, on a single VM or across multiple VM deployments. The artifact is the same in every case.
HL7 v2, FHIR R4/R5, X12 (full 5010) and XML parse into typed objects you can inspect, map and validate, rather than strings you have to split.
On premise, Kubernetes, a single VM or multiple VMs. Message queuing, structured logging, archive and replay are built in, not bolted on with a cron job.
Role-based access, immutable audit logs, encryption in transit and at rest, BAA-ready, and a support model that never requires us to see patient data.
The console, the builder and a message going all the way through, without a slide in sight.
A project groups the workflows, variables, templates, libraries and collaborators for one integration programme: a hospital, a customer, a migration. Each one is Git-backed, so interfaces get branches and review like the rest of your code.
Linkiir Grid: Projects
Per-environment values, resolved at deploy. No more if hostname == 'prod'.
Clone a proven interface shape into a new site in one action.
Shared Lua modules, versioned, required by any workflow in the project.
Branch, review, roll back. Access scoped per project, per role.
Drag the nodes, wire them, and configure the one that matters. Every parameter you'd hunt through a config file for is on the panel, with the documentation next to it rather than in a PDF from 2014.
Linkiir Grid: Workflow Builder, node parameters
| Type | Ref | Segment | Identity | Description | Min | Max | Req | Rep |
|---|---|---|---|---|---|---|---|---|
| Segment ⌄ | 1 | MSH | None | Message Header | 1 | 1 | ✓ | |
| Segment ⌄ | 2 | SFT | None | Software Segment | 0 | −1 | ✓ | |
| Segment ⌄ | 3 | UAC | None | User Authentication Credential | 0 | 1 | ||
| Segment ⌄ | 4 | MSA | None | Message Acknowledgment | 1 | 1 | ✓ | |
| Segment ⌄ | 5 | ERR | None | Error | 0 | −1 | ✓ |
Linkiir Grid: Schema Editor
The Schema Builder was written from scratch for this job. Message definitions, segments, composites and primitives, all editable, versionable and validated as you go. Because the standard is a suggestion and every site interprets it differently.
Ships with grammars for HL7 v2.3 through v2.9, FHIR R4 and R5, X12 5010 (837P/I/D, 835, 270/271, 276/277, 278, 834, 820), plus CDA and arbitrary XML.
The editor embedded in Grid is VS Code, so there is nothing new to learn. File explorer, shared libraries, pinned samples, a debugger and a run-test button, all where you expect them. Copy the whole tree with mapTree, then override the fields that differ.
Linkiir Grid: Node Script Editor
Pin a de-identified production message, run the transform, read the output and variables. Iterate in seconds, not deploys.
Write mapping.lua once and require it everywhere. Fix a mapping bug in one place, not nineteen channels.
Describe the target message and get a first-pass transform in readable Lua, one you can review, correct and own.
Throughput, queue depth, CPU, memory and the health of every workflow, on one screen, with the services behind it listed honestly. When something breaks you find the message, not the haystack.
Linkiir Grid: Dashboard
Agent is in development and launches in March 2027. It will watch the estate, propose the fix instead of the ticket, and execute through Grid, or through the engine you already have. Every action a signed record: who saw it, what Agent proposed, what a human approved, when it ran, what changed. Here's what we're building.
Duplicate ADT detection, patient-match confidence, rejection clustering, quiet-endpoint alarms.
Agent explains what it saw and what it wants to do: merge, resubmit, re-route, hold.
Resubmissions, merges, re-routes and callbacks execute through Grid or your incumbent engine.
Policies define what Agent may do alone and what it must escalate, with a full record of proposal, approval and outcome.
| Transports | |
| Inbound | MLLP · TCP · HTTPS/REST · SFTP · FTPS · file watchers · database polling · Kafka · Redpanda · AMQP · webhook receivers · DICOM C-STORE |
| Outbound | MLLP · HTTPS/REST · FHIR REST · SFTP · FTPS · file write · database write · Kafka · Redpanda · cloud object storage · warehouse loaders |
| Formats | |
| Healthcare | HL7 v2.3–v2.9 · FHIR R4 / R5 (JSON + XML) · CDA / C-CDA · DICOM metadata |
| EDI & B2B | X12 5010 full set: 837P/I/D, 835, 270/271, 276/277, 278, 834, 820, 275, 277CA · EDIFACT · delimited and fixed-width flat files |
| General | JSON · XML · CSV/TSV · Protobuf · custom binary via Lua |
| Runtime | |
| Deployment | On premise · Kubernetes (Helm chart) · Docker Compose · single VM (Linux, Windows) · multiple VM deployments · air-gapped install supported · Linkiir Cloud Coming soon |
| Broker | Bundled, or bring your own Kafka / Redpanda |
| Databases | PostgreSQL, SQL Server, Oracle or MySQL for log archive and configuration store |
| Availability | Active/active high-availability topology, automatic failover, message-level durability with replay |
| Scripting | Lua 5.4 with the Linkiir standard library, shared project libraries, run-test and step debugger |
| Pre-tested endpoints | |
| Vendors | Epic, Oracle Health (Cerner), MEDITECH, athenahealth, eClinicalWorks, Veradigm, NextGen, PointClickCare, Availity, LabCorp, Quest, Surescripts and the rest of the Integration Network |
We'll shadow your live traffic through Grid and diff the output against your incumbent engine, byte for byte. You see the report before you decide anything.