Solutions
Every hospital wants a different interface. Build one.
Integration work has a way of quietly becoming the roadmap. IntuCloud gives you a single canonical pipeline into your product and a place to absorb each customer's variations — without a fork, a spreadsheet of one-off scripts, or a dedicated integration team.
What makes this hard today
- Every hospital customer has a different EHR, a different HL7 dialect, and a different opinion about FHIR.
- Each new implementation adds bespoke integration code that only one engineer understands.
- Integration engineering competes directly with product roadmap for the same people.
- Prospects ask for security and compliance answers your team has to assemble from scratch each time.
What changes with IntuCloud
- One canonical channel, with per-destination transformers absorbing each customer’s variations.
- Channels are TypeScript and YAML in Git — reviewable by the whole team, not one specialist.
- A free sandbox per project means prototyping the next interface costs nothing.
- A documented security posture, PHI under BAA, SSO and audit logs you can point at.
Capabilities
What changes for your team.
Standardize once, connect many
Build one canonical channel into your product, then handle each hospital’s quirks in a per-customer transformer rather than a per-customer fork of your integration code.
Visual designerA sandbox per implementation
Every project gets an isolated sandbox. Prototype the next customer’s interface against synthetic messages without touching a production environment or spending a seat.
EnvironmentsDeveloper experience your team will accept
TypeScript stages, YAML channels in Git, a CLI, and an export path to the open-source engine. Integration work stops being a separate discipline from the rest of your codebase.
The intu-dev enginePricing that follows the deal
Build the demo on Free. Land the first hospital with PHI on Team. Move to Enterprise when contracted volume and SLAs enter the conversation.
PricingGrowth path
Start free. Pay when a customer goes live.
The commercial model matches how a vendor actually grows: design is free, production is paid.
- Free 01
Building the demo
Unlimited projects and channels, sandbox testing, Mirth import, 10,000 messages a month. Synthetic data only — which is exactly what a demo should use.
- Team 02
First hospital customer
A production environment, PHI under a BAA, 250,000 messages a month, Google and Microsoft SSO, business-hours support. $499/mo.
- Enterprise 03
Contracted volume and SLAs
5,000,000 messages a month at 50 messages/sec, 20 long-running plus 10 custom environments, dedicated gateway addresses, SAML, named technical contact.
API-first, and portable by construction.
The projects you build here are intu-dev projects. If a customer insists the integration runs inside their own network, export it and run the open-source engine there — same channel files, same behaviour, no rewrite. That is a useful answer to have in a procurement conversation.
Start building today.
Free plan, no credit card — design and test unlimited channels.