Solutions

Many-to-many connectivity, without a bespoke interface per participant.

An exchange is a fan-out problem with a compliance obligation attached. IntuCloud gives you IHE transactions, Direct, and FHIR as connector types, per-destination transformers so no participant forces a fork, and the capacity to run it at network volume.

Get started free Talk to sales

What makes this hard today

Every participating facility wants the payload shaped slightly differently, and each variation becomes a new channel.
IHE conformance is table stakes, but the transactions are fiddly and easy to get subtly wrong.
Fan-out multiplies volume: one inbound message can mean a dozen outbound deliveries.
When one participant is down, you need to know exactly what they missed — and be able to send it again.

What changes with IntuCloud

One channel, many destinations, each with its own filter, transformer and response transformer.
XDS.b, PIX and PDQ transactions are connector types with the ITI semantics built in.
Enterprise capacity covers 5,000,000 messages a month at 50 messages per second.
Filter the message browser to the outage window and batch reprocess when they come back.

Capabilities

What an exchange needs.

IHE profiles, not approximations

XDS.b document sharing (ITI-41 provide and register, ITI-42 register, ITI-43 retrieve), PIX (ITI-8 feed, ITI-9 query) and PDQ (ITI-21, ITI-22) as first-class connector types.

Connector catalog

Fan-out with per-destination logic

One inbound message, many participating systems — each destination gets its own filter, transformer and response transformer, so a participant that needs a different payload gets one.

Visual designer

Addresses participants can allowlist

Gateway addresses at *.gw.intucloud.ai with TLS 1.2+, mTLS where required, and dedicated ingress or egress address sets so each participant has a stable IP to trust.

Environments & networking

Operations at network scale

When one participant goes dark, find the affected window in the message browser and batch reprocess once they are back. Alert rules cover queue depth and error rate per channel.

Observability

Standards

The transactions, spelled out.

Profile / standard

IHE XDS.b

Transactions

ITI-41, ITI-42, ITI-43

Use

Provide and register, register, and retrieve document sets.
Profile / standard

IHE PIX

Transactions

ITI-8, ITI-9

Use

Patient identity feed and cross-reference query.
Profile / standard

IHE PDQ

Transactions

ITI-21, ITI-22

Use

Patient demographics query, including the HL7 v3 variant.
Profile / standard

Direct

Transactions

—

Use

Direct secure messaging to a Direct address through a configured HISP.
Profile / standard

FHIR R4 / R4B

Transactions

—

Use

Server listener, scheduled poll, and R4B subscription notifications.
Profile / standard

HL7 v2

Transactions

—

Use

MLLP listeners and destinations with ACK and NACK handling.

Scroll the table sideways to see every column.

IHE and exchange-oriented standards supported by IntuCloud
Profile / standard	Transactions	Use
IHE XDS.b	ITI-41, ITI-42, ITI-43	Provide and register, register, and retrieve document sets.
IHE PIX	ITI-8, ITI-9	Patient identity feed and cross-reference query.
IHE PDQ	ITI-21, ITI-22	Patient demographics query, including the HL7 v3 variant.
Direct	—	Direct secure messaging to a Direct address through a configured HISP.
FHIR R4 / R4B	—	Server listener, scheduled poll, and R4B subscription notifications.
HL7 v2	—	MLLP listeners and destinations with ACK and NACK handling.

Capacity

What the plans carry.

Exchange traffic usually lands on Enterprise. These are the numbers, not an estimate.

Messages included per month

Team

250,000

Enterprise

5,000,000
Throughput

Team

5 messages/sec

Enterprise

50 messages/sec
Long-running environments

Team

2

Enterprise

20, plus 10 custom
Dedicated gateway IPs

Team

$40/mo add-on

Enterprise

Included
Retention

Team

30 days

Enterprise

365 days
Single sign-on

Team

Google, Microsoft

Enterprise

OIDC, SAML