Why SuperBroadband changes the multi-site healthcare conversation.

Multi-site healthcare has been quietly papered over with bad answers to the same question for fifteen years. The question: where does your secondary path actually come from?

You can read it in a hundred different IT audit findings, all phrased nearly the same way. Primary fiber from Vendor A. Secondary "broadband" from Vendor B. Last failover test: unverified, six months ago. Sometimes worse — the secondary path is the same vendor's metro fiber on a different conduit, which everyone knows isn't actually diverse the moment a backhoe finds the wrong duct bank.

The reason this persists isn't engineering stubbornness. It's economics. Provisioning two truly diverse wireline circuits to a 20-clinic ambulatory network is expensive, takes nine to eighteen months, and locks the architecture to whoever happens to have last-mile presence at each address. So the project gets descoped. The audit finding stays open. Everyone moves on.

What changed

T-Mobile's SuperBroadband product, by their own description, combines enterprise 5G with Starlink satellite in a single managed service — one contract, one bill, one box, two paths. Two operational modes: automatic failover, or load-balance for resilience by construction.

"Speeds vary due to local network characteristics and management." That's the honest line buried in the marketing. It matters because it tells you what you actually got.

From the architecture side, what you got is this: a single CPE that simultaneously holds a 5G PDP session and a Starlink LEO session. The two paths are physically uncorrelated in a way that two wireline paths never are. A backhoe doesn't take out a satellite constellation. A regional cellular tower outage doesn't dim the sky overhead. For the first time, the "real diverse second leg" line on the architecture diagram corresponds to two actually-independent failure domains.

For a single large hospital, that's nice but not transformative — most large hospitals already have engineering budget for proper carrier diversity. For an ambulatory network with 30 to 60 clinics, or a long-term care operator with 15 facilities across three states, or a behavioral health practice running telehealth-first intake from 22 sites, this is the first economically rational answer the industry has produced.

The reason it took this long

Two underlying things had to be true before this was possible.

First, 5G fixed wireless had to actually deliver enterprise-grade performance. Five years ago, "5G fixed wireless" meant a high-mounted modem that sometimes did 50 Mbps if the weather was right. Today, on T-Mobile's published numbers, you can plan a multi-site rollout around it as a primary path with confidence — not a "backup" path you hope never to need.

Second, Starlink had to mature to managed-service grade. The early Starlink RV / residential offering wasn't something you'd put under a healthcare SLA. The current Business and Enterprise tiers — and now, importantly, the wholesale relationship that lets T-Mobile bundle Starlink into a single contract — are.

The technology was incremental on both sides. The packaging is what changed. A single managed contract, with one carrier holding both sides of the diversity story, eliminates the procurement friction that kept this option off the table.

What it changes about an SD-WAN design

Healthcare SD-WAN architectures over the last decade have been heavily shaped by underlay economics. Three patterns dominated:

1. MPLS-with-broadband-failover

The default for hospital systems with the budget. Reliable, expensive, slow to change. Provisioning lead times in months. Often locks the architecture to the MPLS carrier's coverage map.

2. Dual broadband from different carriers

The ambulatory default. Cheaper, but secondary "diversity" depends on whether the two carriers actually have separate physical paths. They often don't. Audit findings live here.

3. 4G/LTE failover

The pragmatic compromise. Works for keeping a clinic alive during a wireline outage, but throughput drops to a level that's noticeable in clinical workflow — and in many practice environments, audit posture isn't satisfied by a "best effort" backup.

SuperBroadband is the first option that genuinely improves on all three at once. The 5G side is good enough to be a primary path. The Starlink side is uncorrelated enough to be a real secondary. The single-contract packaging removes the procurement reason these conversations stalled. And the per-site cost — T-Mobile's published starting price is $250/mo on a 36-month commitment — is in the same neighborhood as a single wireline circuit, while delivering the diversity of two.

Where it doesn't fit

Honest caveats, because this isn't a press release.

If your site has line-of-sight obstructions to the satellite arc — heavy tree canopy in the right direction, an adjacent tall building, certain rural mountain valleys — Starlink's contribution drops. The 5G side carries proportionally more, which is fine but is no longer truly hybrid.

If you need symmetric, deterministic latency to a specific cloud region — say, for a contact-center workload sensitive to one-way latency to a US-East PoP — the satellite path's variable jitter shows up. Load-balance mode is less appealing; automatic-failover mode is the right configuration.

If your security posture requires private MPLS endpoints all the way into a specific cloud — most healthcare environments don't, but some do — SuperBroadband sits at the public-internet edge. You'd still need a separate connectivity story for the deep-private case.

And finally: this is a relatively new product. T-Mobile's published reference list of healthcare deployments is short. The Boston Children's 5G ANS work is well-documented and adjacent; SuperBroadband-specific multi-site references are still being built. The conservative read is "promising, validate at one site before committing the fleet." That's the read we'd give a client.

The honest summary

For the first time in fifteen years of multi-site healthcare networking, the "real diverse second leg" line on the architecture diagram has a managed, contractable, financially reasonable answer behind it. That doesn't mean SuperBroadband is the answer for every site. It means the conversation finally moves from "we can't afford to do it right" to "let's pick which sites this fits and pilot." That's a substantial change in what's available to design with.

If you're running a multi-site healthcare network and the secondary-path question keeps coming up in audits or steering meetings, this is the option to evaluate. Anchor on a single-site pilot. Validate the failover behavior with the workloads that actually matter to clinical operations. Then decide whether to roll it across the rest.

That's the kind of engagement Medical ANS is built for. If you want to walk through it against your environment, the first call is a 30-minute working session.

---

Sources & references: T-Mobile SuperBroadband product page — t-mobile.com/business/business-internet/superbroadband. T-Mobile 5G ANS / Boston Children's deployment story — t-mobile.com, Sept 2023. Cato Networks customer story (Fullerton Health) referenced on our industry references page.