Solutions
Modernize the interface engine without a rip-and-replace project.
ADT, ORM and ORU feeds keep multiplying, the people who understand them keep retiring, and the engine underneath was chosen a decade ago. IntuCloud lets you move one channel at a time, with the change control and audit trail a hospital actually has to produce.
What makes this hard today
- An interface engine chosen a decade ago, on a JVM, with configuration locked in a GUI and a database.
- A very small number of people who can safely change an ADT feed, and no good way to review their work.
- Every new downstream system means another channel, another transformer, another thing to operate.
- Compliance obligations that grow faster than the team — audit trails, access reviews, retention.
What changes with IntuCloud
- Import existing Mirth Connect channels as editable pipelines and cut over one at a time.
- Channels are YAML and TypeScript files — reviewable in a pull request, revertible in one click.
- Deployment gates and named approvals give you a documented change process, not a tribal one.
- PHI under a BAA, audit logs on all mutating APIs, and retention configured per plan.
Capabilities
What you get on day one.
HL7 v2 over MLLP at the core
TCP listeners in MLLP mode with ACK and NACK handling, plus FHIR R4, CDA, X12, DICOM and IHE when the next project needs them. 27 connector types in all.
Connector catalogChange control your CAB will sign off
Promotion gates run connector preflight against the target environment, soak the channel for a configured window, and require a named approval — all recorded as audit events.
Environments & deploymentsPHI under BAA, isolated per tenant
Encrypted at rest and in transit, no shared filesystem between tenants, a dedicated task per production channel, audit logs on every mutating API.
Security & complianceOperations for a small interface team
Queue depth and lifecycle in the monitor, an HL7 segment viewer on every message, and batch reprocess when the lab system comes back after an outage.
ObservabilityIf PHI cannot leave the building, it doesn't have to.
Plenty of hospitals will not move clinical data to a cloud platform, and that is a legitimate position rather than an objection to be handled. The engine underneath IntuCloud is open source: run intu-dev in your own data centre, keep the data inside your compliance boundary, and buy a support subscription so you are not on your own with it.
The same channel files run in both places, so the decision is reversible.
Start building today.
Free plan, no credit card — design and test unlimited channels.