One Network Standard, Every Site: How a Major Healthcare Provider Got Its Multi-Site IT Under Control

The situation

A major healthcare provider had grown its network of clinic offices the way most successful multi-site healthcare businesses grow: one location at a time, each opened or acquired under deadline pressure. Every site arrived with its own internet contract, its own firewall brand, its own wiring-closet habits, and the phone number of whichever local technician had set it up.

The clinical work never stopped. Couriers moved specimens on fixed schedules, and results had to reach ordering physicians without interruption. A clinic office that lost connectivity stopped serving patients the moment the link dropped, and the phone calls started minutes later.

Adaptive IP Services was engaged to take over IT operations across the footprint. Our founder had been working in enterprise infrastructure since 1997, and this engagement became one of the proving grounds for how Adaptive still operates today.

The challenge

Three constraints shaped the whole engagement.

No downtime windows worth the name. Clinic offices opened early and clinical operations ran around the clock. Cutover work had to be staged, rehearsed, and reversible, because "we'll fix it in the morning" was never an acceptable plan.

A regulated environment. Clinical operations answer to inspectors and auditors. Documentation could not be aspirational. If the binder said a site was configured a certain way, the site had to actually be configured that way, and someone had to be able to prove it.

Sprawl without staff. The company had far more locations than IT people. Whatever we built had to be supportable by a small team, remotely, without a technician on a plane every time a site misbehaved.

What Adaptive did

We audited before we touched anything. Site by site, we documented what was actually installed: circuits, hardware, configurations, contracts, and the undocumented local workarounds holding it all together. You cannot standardize what you have not honestly inventoried.

We wrote one network standard and rolled it out location by location. Same firewall platform and configuration baseline, same addressing scheme, same wiring and labeling conventions at every site. The test we held ourselves to: a technician who had never set foot in a location should be able to support it from the standard documentation alone.

We consolidated vendors. Dozens of local ISP contracts, hardware suppliers, and support arrangements collapsed into a short list with one accountable party in front of them: us. When something broke, the client made one call and we owned the outcome, including the finger-pointing between carriers.

We built a centrally managed digital signage network for the patient-facing locations. At the time, nothing on the market fit a multi-site healthcare operation the way this needed to work, so we developed our own signage solution. We made it deliberately simple for the client to run: staff dropped their content into a shared Dropbox folder, and the right screens updated on their own, with no site visit and no per-location fiddling. Before that, updating patient messaging meant emailing files to site managers and hoping.

We put process behind the technology. Documented runbooks, change control, and a tiered disaster-recovery process defining what got restored, in what order, and who decided. Our founder later formalized that thinking into documented process frameworks (ITIL/ITSP process design and a four-tier DR model) and the forthcoming book CIO: From Service Provider to Partner. This engagement is part of where that material was earned.

What changed

We won't invent numbers for a client we're not naming, so here is what changed and why it changed.

After-hours pages went down because failures became predictable. When every site runs the same baseline, a failure at one site looks like a failure you have already seen. Most issues moved from "drive out and investigate" to "diagnose remotely against a known configuration."

New sites became checklist work. Opening a location shifted from a bespoke project to a repeatable turn-up: order the standard circuit, ship the standard stack, apply the standard configuration, verify against the standard test plan.

Audits got quieter. Documentation described the deployed reality because the deployed reality came from the documentation. Inspectors ask harder questions when the answers are improvised. Ours weren't.

Leadership got one accountable partner. Vendor disputes, carrier escalations, and hardware lifecycle decisions landed on our desk instead of the client's.

What this means for your business

That engagement ran on discipline: inventory honestly, standardize deliberately, document what you deploy, and put a process behind every promise. None of that has changed. What has changed is the packaging.

The same operating discipline now ships as defined SOC, NOC, and consulting packages with published pricing, for organizations that want the multi-site rigor without a multi-site price of entry. If your situation needs architecture and process work before anything gets managed, that is what our consulting practice does, and it draws on the same playbook described above.

If you run more than one location and your IT knowledge lives in the heads of whoever installed things, you already know how this story starts. You get to choose how it ends.