I still pick up relief house supervisor shifts. I do it because it keeps me honest.
On a busy night, the house supervisor knows exactly where the beds are. They know which unit is short a nurse, which discharge is stuck waiting on a ride, and which ICU bed will open in two hours. That person is the command center for the building, whether or not anyone calls it that.
But here is what I notice every time. The hardest calls of the night almost never start inside our walls. They start with a phone ringing from a hospital 90 miles away that has a patient who needs something they can't provide. And the answer to whether we can help depends on things I can't see from my desk.
That's the idea behind the talk I gave at WC Forum in Nashville this month, and I want to unpack it a bit here.
Capacity doesn't respect property lines
Most hospital command centers were built to look inward. Big screens, bed boards, throughput metrics, a team watching the house. That work matters. Plenty of hospitals have made real gains by getting their own flow under control.
The trouble is that patients don't live inside one hospital. They live in a region. When a rural hospital can't find a bed, when a community hospital is full, when a tertiary center is turning away transfers, those are not separate problems. They are one problem showing up in different buildings.
A command center that only sees its own house is a bit like a pilot who only watches their own instruments and never talks to air traffic control. You can fly the plane well and still end up circling.
What we learned when the whole state was full
In 2020, our team helped stand up the Arizona Surge Line with the Arizona Department of Health Services and the University of Arizona. It was built for a crisis. Hospitals across the state needed one place to call when they couldn't find a bed for a COVID patient.
Between 2020 and 2022, the Surge Line handled about 12,000 patient transfers. Roughly 85 percent of them came from rural, critical access, Indian Health Service and tribal hospitals.
Sit with that number for a second. The hospitals with the fewest resources were the ones who needed coordination the most. And no single command center, no matter how good, could have solved that alone. It took a layer that sat above any one system and could see the whole board.
Since December 2022, Blackbox has partnered with the University of Arizona to staff AZ REACH, the university's statewide transfer coordination program, carrying that work forward from crisis mode into everyday transfers. The lesson stuck with us. Regional coordination isn't only an emergency tool. It's how patients get to the right place on an ordinary Tuesday.
What a regional layer actually means
When I say regional layer, I don't mean one big system running everyone else's beds. I mean a few practical things.
Regional visibility. Knowing, in close to real time, who can take what kind of patient. Not a perfect count. A useful picture, plus people willing to pick up the phone and confirm it.
Two-way transfers. Most transfer centers are built to pull patients up to a higher level of care. Far fewer are built to send them back home once the acute need is over. Repatriation is the forgotten half of transfer work. When it works, tertiary beds open up, families get their loved ones closer to home, and rural hospitals keep the patients and volume they need to stay open.
Shared governance. If community and rural hospitals are only ever on the receiving end of decisions, they stop trusting the process. The regional layer works when they have a real seat at the table, agreed rules for how requests are handled, and a clear path to raise a problem.
Governance and roles come first
This is the part that surprises people. When leaders ask me what technology they need for a regional command center, my honest answer is: not yet.
Before software, you need answers to some plain questions.
Who decides whether a patient is medically appropriate to accept? Who owns finding the bed? Who calls the sending hospital back, and how fast? What happens when the answer is no? Who do you escalate to at 3 a.m.? How do repatriation requests get handled, and who is accountable for them?
If those answers are fuzzy, a new dashboard just shows you the confusion in higher resolution. If they are clear, even a simple setup with good people and a shared phone line can move patients well. Then technology can make good work faster.
I say this a lot: we can only operate at the speed of trust. That's true inside one hospital, and it's even more true across a region. Hospitals that compete for patients and staff have to believe the coordination layer treats them fairly. That trust is built through governance, consistency and showing up, call after call.
Where to start
If you run a command center today and you're wondering what's next, here are a few questions worth asking your team:
- How many of your hardest capacity problems start outside your walls?
- Do you know how your transfer partners experience calling you?
- Do you have a defined process for sending patients back home, or only for bringing them in?
- If a regional partner wanted a voice in how transfers work, where would they go?
You don't need to answer all of these at once. But the next generation of command centers will be judged less by how well they run one building and more by how well they connect to everyone around them.
The patient doesn't care whose bed it is. They care that someone answered, someone decided, and they got where they needed to go.
That's the work. If you want to talk through what a regional layer could look like for your system, we'd love to hear from you.