Isn't a hub a single point of failure?

It's a concentration of risk you engineer around — high availability, message queuing, retries, and monitoring. In exchange you get centralized governance and linear scaling. For most healthcare integration estates that trade is clearly worth it.

Can I start point-to-point and move to a hub later?

You can, but migrating a tangle of bespoke interfaces into a hub is real work. If you can see growth coming, it's usually cheaper to start with an aggregator than to unwind point-to-point sprawl later.

What is hub-and-spoke integration?

Hub-and-spoke is the aggregator pattern: a central hub connects to each system once (the spokes) and normalizes data to a canonical model, so every consumer reads one contract instead of building a link to every source. Adding a system is one new spoke rather than a new interface for each consumer — which is what keeps complexity linear.

How many connections before an aggregator is worth it?

There's no hard threshold, but the economics usually tip once you're past roughly three to five systems, or you expect to keep adding them. Below that, a couple of direct links can be simpler than running a hub. Above it, point-to-point's N-squared interface growth makes an aggregator the cheaper and more maintainable choice.

Is an integration aggregator the same as an interface engine?

They overlap but aren't identical. An interface engine like Mirth is a tool that can implement a hub; "aggregator" and "hub-and-spoke" describe the architecture — one central point that normalizes and serves many consumers. You can build an aggregator on an interface engine, an integration platform, or custom services. The pattern is the point, not the product.

Decision Guide

Integration Aggregator vs Point-to-Point

Use an aggregator (hub-and-spoke) when you'll connect to more than a handful of systems — a central hub normalizes data once and every consumer reads one contract, so complexity grows linearly instead of exploding. Use point-to-point only for a small, stable number of interfaces where a direct link is simpler than standing up a hub. The trap is starting point-to-point "because it's quick" and drowning in an N-squared web of bespoke interfaces as you grow.

15-Minute Scoping Call All Comparisons

Quick answer

More than a few connections, or growing → aggregator (hub-and-spoke). A couple of fixed interfaces → point-to-point. Point-to-point scales as N², and that's the whole story.

Decision table at a glance

Criterion	Aggregator	Point-to-Point
Complexity growth	Linear (one spoke per system)	~N² (interface per pair)
Upfront effort	Higher (build the hub)	Lower (one link)
Adding a new system	One new spoke	New interface to each consumer
Governance & monitoring	Centralized	Scattered per interface
Single point of failure	Hub (mitigate with HA)	None central (many small)
Best for	Many / growing connections	Few, fixed connections

What they are

What is Aggregator

An aggregator (hub-and-spoke / integration layer) is a central component that connects to each system once, normalizes to a canonical model (e.g. FHIR), and serves all consumers through one contract. Adding a system means one new spoke, not a new interface for every consumer.

What is Point-to-Point

Point-to-point wires each system directly to each other system that needs it — a dedicated interface per pair. Simple and fast for one or two links, with no hub to build or run, but the number of interfaces grows roughly as the square of the systems involved.

Key differences

The N-squared problem

Point-to-point is seductive because the first interface is quick. But with M systems each needing to talk to the others, you trend toward M×(M-1)/2 interfaces — every new system multiplies the work and the maintenance surface. An aggregator collapses that to one connection per system, so growth stays linear and predictable.

Centralized governance vs scattered logic

A hub gives you one place for transformation rules, mapping, security, audit logging, and monitoring. Point-to-point scatters that logic across many interfaces, so a change to a data model or a compliance control means touching every affected link. For regulated healthcare data, centralization is a real operational and audit advantage.

Upfront cost vs long-run cost

The aggregator costs more to stand up — you're building shared infrastructure before it pays off. Point-to-point is cheaper on day one and more expensive on every day after, once you pass a few connections. Decide based on your trajectory, not just the first interface.

Resilience trade-offs

A hub is a single point of failure you must engineer around (high availability, queuing, back-pressure). Point-to-point has no central chokepoint, but failures and changes are handled per-interface with no shared observability. Most teams accept the hub and invest in its resilience because the operational clarity is worth it.

When to use each

When to use Integration Aggregator

You connect to more than a handful of systems, or expect to grow.
Multiple consumers need the same data and you don't want to duplicate interfaces.
You want one place for transformation, monitoring, security, and governance.
You're building a product that onboards new health systems over time.

When to use Point-to-Point

You have a small, stable set of interfaces (two or three) with no growth planned.
A single direct link is genuinely simpler than standing up and running a hub.
The integration is a one-off or short-lived and doesn't warrant shared infrastructure.
Latency or contractual reasons demand a dedicated, unmediated connection.

Healthcare Interoperability Solutions EHR/EMR Integration Services FHIR Integration & API Development Redox vs Direct EHR Integration

Frequently Asked Questions

When you have a genuinely small and stable number of interfaces — two or three — with no expected growth, and standing up a hub would be more infrastructure than the problem warrants. Beyond a handful of connections, an aggregator almost always wins.

Not sure which fits your build?

Tell us about your product, integration targets, and timeline. We'll map the trade-offs to your context and recommend the path that gets you to a compliant launch fastest.

15-Minute Scoping Call Explore Solutions