Hospital Neutral Host Contracts Decide Whether Private 5G Needs a Rebuild

Quick Answer: A hospital neutral host project in 2026 is often built around one anchor carrier and its licensed spectrum, because T-Mobile and Verizon are reluctant to support multi-operator networks on shared Citizens Broadband Radio Service (CBRS) spectrum. The neutral host contract settles three things a future private clinical layer inherits: whose core holds the subscriber records for hospital-owned devices, which SIM or eSIM credentials they carry, and which spectrum bands the installed radios can serve. If all three favor the hospital, the private layer can be switched on later; if any one does not, it becomes a second project. AI-driven virtual patient observation is one workload likely to make that layer necessary sooner than planned.

SNS Telecom & IT counts more than 100 U.S. neutral host networks built on CBRS small cells, with hospitals among the sites. In its June 2026 market report, SNS adds that reluctance from T-Mobile and Verizon has largely limited recent multi-operator projects to high-profile customers, such as the U.S. military and retail giants.

At the steering meeting that approves a hospital neutral host, the facilities lead wants the failing distributed antenna system (DAS) gone before the new tower opens. Physicians want calls that survive the elevator ride. The anchor carrier’s proposal covers both, and near the bottom of the roadmap slide sits a single line: private 5G, phase two.

Tampa General Hospital signed a version of this deal in 2025. Verizon says the new neutral host serves the main hospital, where an outdated DAS had proved unreliable, and includes a latent private 5G core the hospital can turn on later for the medical, academic, and research work planned for a new tower.

The room treats the private layer as a phase-two question, though the contract on the table will settle most of its terms.

AI Observation Is a Likely First Tenant for the Private Layer

In virtual observation, a remote sitter or nurse watches several high-risk patients over video while software flags movement that suggests a fall.

Black Book Research surveyed 554 clinical, finance, and IT leaders in August 2025 and describes hospitals building AI-powered observation into core operations. Of those respondents, 73% expected their organizations to expand virtual care by 2026. Among mature programs that reported results, high-risk units averaged a 20% drop in patient falls within 12 months of adopting virtual monitoring.

Bedside nurses are less convinced by the wider virtual nursing model. In a December 2025 study in JAMA Network Open, Penn Nursing researchers found that 57% of 880 hospital nurses who work alongside virtual nurses said those programs did not reduce their workload. The clinical evidence is mixed, and the video traffic reaches the network either way.

For the wireless design, three properties of this traffic matter more than the clinical debate:

•       Continuous video moving up from the room to a monitoring hub, which loads the uplink of a network usually sized for phones pulling data down.

•       Alerts that depend on a short, predictable path between the camera, the inference software and the person who responds.

•       Protected health information (PHI) in every frame, which many hospital security teams prefer to keep and process on site.

Neither survey looked at network design, but these properties make AI observation a likely first tenant for a private layer.

Celona says Stanford Health Care’s neutral host network leaves room to move mobile carts and biomedical monitoring devices from Wi-Fi to private 5G. Celona supplied the system, so this is the vendor’s account.

Carrier Positions Have Reshaped the Hospital Neutral Host Deal

Since CBRS opened, many U.S. venues have funded their own neutral host as small cells shared with each carrier through a multi-operator core network (MOCN). The alternative, a multi-operator radio access network (MORAN), shares the radio hardware while each carrier brings its own licensed spectrum.

Each national carrier now takes a different line on the CBRS design:

•       T-Mobile told RCR Wireless in August 2025 that it still supports CBRS MOCN but is encouraging partners to prioritize licensed mid-band spectrum. RCR reported that the request went to neutral host vendors including Celona and InfiniG and focuses mostly on 2.5 GHz, with some 1.9 GHz. RCR understood that existing CBRS sites would keep support if they met performance targets, while new venues would be required as a rule to use T-Mobile spectrum, leased for MOCN or in MORAN setups.

•       Verizon told RCR that its neutral host networks use its own licensed spectrum, sometimes with an active or dormant private 5G core, and that either layer can run on its spectrum or CBRS. RCR adds that Verizon has always controlled those sales itself and, while it works with Celona, has never certified Celona’s system for third-party CBRS deployments. Under Verizon’s product terms, customers must sign separate spectrum redistribution agreements with non-Verizon carriers.

•       AT&T was, in RCR Wireless’s account from September 2025, the only U.S. operator still offering full support to third parties that fund CBRS neutral host systems in enterprise venues.

SNS says some radio vendors and service providers now offer MORAN as an alternative to CBRS MOCN, and names AdventHealth and Tampa General Hospital among the customers using it.

My reading is that a hospital buying neutral host in 2026 is often choosing an anchor carrier too, and that choice reaches into its private network plans. The three models in Table 1 differ in what each leaves for future clinical use.

Table 1: Neutral host models a hospital is likely to be offered in 2026

Model	Spectrum	Carrier support as reported in 2025	What a later private layer can reuse
CBRS MOCN	Shared CBRS, coordinated through a Spectrum Access System	AT&T full support; T-Mobile for existing sites that meet its targets; Verizon has never publicly supported it	Radios and spectrum, if the core can host a private network identity alongside the carriers’
Anchor-carrier MORAN	Each carrier’s own licensed bands	The anchor carrier, with others joining through separate agreements	Radio hardware, if it also carries the band the private layer will use
MOCN on leased carrier spectrum	One carrier’s licensed band, shared through a lease	Set by the lease terms	Depends on the lease and on whose core is installed

Carrier terms for neutral host changed in 2025 and can change again before a hospital contract is signed. Subscribe to PrivateLTEand5G for analysis when they do.

Decision One: Whose Core Sits in the Rack

Verizon markets the latent core as a feature: neutral host now, with a pre-installed private 5G core to switch on when needed. The company said in October 2025 that AdventHealth uses both layers, with the private network covering smart beds, real-time location services and asset tracking, and that Tampa General’s core is installed but not yet switched on. Both descriptions are Verizon’s own, since it sells the combination.

Four details decide whether switching a dormant core on is a configuration change or a new negotiation:

•       Ownership of the subscriber database and the private network identity, which determines whether the hospital can move its devices if it changes carriers or platforms.

•       Placement of the user plane function: on site for AI video and PHI, or inside the carrier’s network.

•       The price and lead time for activation, written into the contract at signing.

•       Support for the core software across the full contract term, including what happens if the platform changes owner.

Local breakout matters for AI observation traffic in particular. In an earlier piece on private wireless in healthcare, I argued that keeping patient data on premises is a strong reason to build private. The case holds only when the user plane sits inside the hospital.

Platform ownership can also change mid-contract. On October 13, 2026, Nokia announced an agreement to sell its Enterprise Campus Edge private wireless business to AURELIUS, with closing expected in the first half of 2027, and says continuity for existing customers is among its priorities. Neutral host contracts run for years, so support terms belong in them.

PRO TIP: Activation Terms Belong in the First ContractBefore the neutral host contract is signed, the hospital still has leverage over the terms of the latent core. Integrators who write the activation price, lead time, breakout location and support term into that contract turn the private layer into a configuration change. When those terms wait for phase two, the price gets negotiated after the hospital has already committed to the carrier and the platform.

Decision Two: Which SIM the Clinical Devices Carry

Personal phones stay on each carrier’s public network through the neutral host. Hospital-owned devices that join the private layer need credentials the private core recognizes, and the hospital has two broad ways to issue them.

Carrier-issued private SIMs can keep provisioning simple, but they tie every device to the anchor carrier’s core. Hospital-managed eSIM profiles, pushed through the existing mobile device management (MDM) platform, let the hospital move the fleet between cores. For CBRS, the OnGo Alliance publishes device requirements for joining 5G standalone (SA) private networks that broadcast its Shared Home Network Identifier.

Some biomedical devices ship with fixed wireless configurations and are likely to stay on Wi-Fi; others depend on what the manufacturer supports. Clinical handhelds, mobile carts and AI observation endpoints are easier first candidates.

A device inventory for the private layer needs four fields for each model:

•       Supported cellular bands, including whether CBRS band 48 or n48 is on the list.

•       eSIM support, and whether profiles can be pushed through MDM.

•       5G SA support.

•       The management platform the device already reports to.

PRO TIP: A Device Inventory Before Design FreezeA neutral host design often fixes radio bands and core choices months before anyone asks which clinical devices will join the private layer. An inventory taken before design freeze, covering band, eSIM and SA support for each model, shows whether those devices could connect at all. Without it, a well-specified core can end up with no compatible devices to serve.

Decision Three: Which Spectrum the Private Layer Runs On

A hospital has two spectrum options here: CBRS, where a Spectrum Access System coordinates access, or the anchor carrier’s licensed spectrum, which Verizon says can carry either layer. Three constraints shape the choice:

•       Radio band support. MORAN needs separate radio chains and multi-band support for each operator’s licensed bands, as noted in an RCR Wireless explainer. Radios ordered for carrier bands may not carry CBRS, in which case a CBRS private layer means a new radio purchase.

•       CBRS policy exposure. The 2025 budget law gave CBRS no formal protection from auction or power-level changes. Proposals still open for comment at the Federal Communications Commission (FCC) when Fierce Network reported on them in 2026 would add Category C base stations at 1,585 watts and Category D at 15,849 watts per channel, against the current 50-watt Category B maximum.

•       Shared timing on shared radios. In a voluntary coexistence specification, the OnGo Alliance has neighboring CBRS radios use the same or an equivalent time division duplex (TDD) configuration, with more freedom for indoor radios to opt out. A cell serving public and private devices on one channel runs one TDD pattern, which on a neutral host is likely to favor phone downloads, so uplink-heavy AI video competes in a frame built for the opposite direction unless the private network gets its own channel.

Licensed spectrum trades that policy exposure for dependence on one carrier. Table 2 shows what each of the three decisions means once the hospital wants the private layer live.

Table 2: How each neutral host decision plays out later

Decision made in the neutral host contract	Private layer is an activation when	Private layer is a second project when
Core	The hospital controls the private network identity, the user plane sits on site, and activation price and lead time are in the contract	The core is carrier-held and activation is priced later
SIM and identity	Hospital-managed eSIM profiles sit on devices already checked for band and SA support	Devices lack the band or SA support, or carry SIMs tied to a core the hospital cannot reuse
Spectrum and radios	Installed radios already carry the band the private layer will use	The private layer’s band needs new radios

PRO TIP: Spectrum Agreements Before Radio OrdersRadio orders often lock in band support well ahead of any decision about the private layer. Integrators who settle spectrum terms first, including the separate agreements non-anchor carriers need, can confirm in writing that the ordered radios carry the private layer’s band as well as the carriers’. Reversing that order leaves band support to be checked after the hardware has shipped.

Where Does This Leave You?

If you are a systems integrator or solution vendor selling hospital neutral host this year, the private network is part of the sale whether or not the hospital mentions it. Measure the result by whether the private network goes live without new radios or core hardware, whether every carrier agreement was signed before the radio order, and whether activation to first clinical device is measured in weeks. Getting there means settling the device inventory and core terms before design freeze, at a presales cost on deals whose private network may stay dormant for a long while. If your team already designs hospital neutral host this way, the Executive Voice Program and Partner With Us are ways to show hospital IT leaders how your design holds up.

If you run hospital IT or clinical engineering, give the neutral host proposal the scrutiny of a private network RFP. Two checks tell you where you stand: the share of hospital-owned devices that could move to the private layer without replacement, and whether the contract states a price for switching on the dormant core. Neither comes easily. The first needs clinical engineering and IT to agree on one device inventory, and the second needs the carrier to commit before you have a firm use case. A wireless self-audit before signing is a practical place to start mapping those gaps.

Frequently Asked Questions

These questions tend to surface once a neutral host proposal reaches procurement.

Can a hospital neutral host still carry all three carriers on CBRS?

It has been done, mostly for very large customers. RCR Wireless reported in 2025 that all three national carriers joined Meta’s CBRS neutral host. A hospital proposal promising three carriers on CBRS should come with written confirmation from each carrier for that building.

Does the patient data case for private wireless cover the neutral host layer?

No. Neutral host traffic leaves through each carrier’s core, like traffic from a phone outside. For staff on personal phones, patient data protection depends on the clinical apps’ encryption and the hospital’s mobile device policies. The on-premises argument covers the private layer only.

Who is responsible for 911 calls on a hospital neutral host?

Emergency calls on a neutral host must meet the same routing and location standards as calls on each carrier’s own network. Carriers check this before approving a site, but buildings change after go-live. The contract should name who monitors emergency call routing from then on.

Should biomedical devices move to the private layer first?

Fixed-configuration biomedical devices are a poor place to start, since moving them can mean new validation work with the manufacturer. Devices the hospital configures itself make a better pilot group, giving clinical engineering evidence before regulated equipment moves.

What happens to a CBRS private layer if the FCC raises power limits?

A study for a cable-led CBRS group found that converting even a small share of base stations to higher power would sharply cut throughput across the band. A hospital on CBRS is safer with a documented licensed fallback its installed radios can support.