Platform
Know what happened to every message.
Interface work is judged on the bad day, not the good one. IntuCloud gives you the monitor, the message history, the reprocess button and the alert rules you need when a downstream system was down for forty minutes and nobody noticed.
Surfaces
Four places to look.
Monitor
Channel health at a glance: queue depth, in-flight counts, lifecycle state, and start/stop control for each deployed channel.
Messages
Browse everything that came through, with format-aware viewers — an HL7 segment viewer, a FHIR resource tree, a CDA document view.
Alerts
Metric and condition rules with severities, acknowledgement, muting, notification templates and rule history.
Events
An audit-style stream of platform activity — who deployed what, who approved a promotion, what changed and when.
Reprocess
Replay what the downstream system missed.
When a receiving system comes back after an outage, the question is always the same: what did we lose, and can we send it again? Filter the message browser to the window in question and reprocess the batch.
The message detail view shows the payload at each stage, so you can tell the difference between "we never received it" and "we transformed it wrong".
- Open any message and reprocess it on its own.
- Select a range and reprocess in bulk after an outage.
- Reprocessing is available on every plan, including Free.
- Each reprocess is recorded in the event stream with who ran it.
Alerts
Rules that page the right person.
Alert rules are per workspace and versioned like everything else. Alert history shows what fired, when, who acknowledged it and how long it stayed open.
- Build rules on metrics and conditions — error rate, queue depth, channel state.
- Assign severities, acknowledge an active alert, or mute a known-noisy rule.
- Notification templates keep the message readable at 3am.
- 5 rules on Free, 25 on Team, 500 on Enterprise.
Reliability
Clinical traffic is never dropped.
The behaviours below are properties of the platform, not settings you have to remember to turn on.
Backpressure, not data loss
When a channel is saturated, HTTP listeners respond 503 with Retry-After and MLLP listeners return a retryable NACK. The sender is told to slow down; nothing is silently discarded.
Drain on undeploy
Taking a channel down lets in-flight messages finish rather than cutting them off mid-pipeline.
Soft overage
Exceeding your included message volume does not stop clinical traffic. You are notified at 80% and again at 100%, and can add message blocks from the billing page.
Explore the platform
Start building today.
Free plan, no credit card — design and test unlimited channels.