Two weeks before ExaltHealth's first hospital was supposed to open in Houston, Farzad Vahid picked up the phone. "Ricky, this hospital is opening in two weeks, what's going on?" Ricky's plan was to fly down on opening day and check that everything was connected. Fornida sent Steven on-site instead, for almost two weeks, twelve hours a day, to wire the building before the first patient walked in. The hospital opened on time. Five hospitals later, that crisis became a playbook. It's a clean example of what managed IT services for healthcare are supposed to buy: operational readiness before patient care starts.
The 60-second version
- Client: ExaltHealth, a multi-state rehabilitation hospital chain. Ricky is the CTO, and also the entire IT department, compliance function, and technical-operations function for every facility.
- The trigger: ExaltHealth's first hospital was opening in Houston in 2024. Their previous MSP had gone silent. With two weeks until opening day, nothing was connected.
- What we did: Fornida sent an engineer on-site for nearly two weeks to install firewalls, networking, EDR, and email security in time. The hospital opened.
- What we built after: A standardized equipment list and pre-opening checklist that turned each subsequent hospital from a fire drill into a routine project. Confirm the order, ship pre-configured, deploy.
- Where they are now: Five hospitals operating. Eight more planned. SonicWall CSE rolling in at hospital #3+ to retire legacy SSL-VPN.
The Houston crisis
The handoff began with a phone call.
When we were gonna open the first hospital for Ricky, I said, Ricky, this hospital is opening in two weeks, what's going on? He said, well, I feel like I'm gonna go down there on the day of to make sure everything's connected. I was like, I would really encourage you to get your upper management to allow Steven and the team to go down there tomorrow and get everything connected before that first day, because you don't wanna show up on your first day and have patients and things not working.
— Farzad Vahid, Founder & CEO, Fornida
The previous MSP wasn't anywhere on the project. Fornida wasn't even contracted to do the buildout. Ricky kept calling with questions because his existing team wasn't picking up. That's the moment the relationship shifted.
His MSP was nowhere to be found. They weren't... well, in all fairness, their job wasn't to connect everything, but their job was to manage it. I don't see how they were gonna manage it if it wasn't all connected.
— Farzad Vahid
He would pick up the phone and he stopped calling them. He started calling us. So it got to a point where, Ricky, we can't continue to answer all these questions for you because, I understand the other team's not responding, but we're not being paid for this. So at some point, you guys gotta make a decision internally. And that's what happened.
— Farzad Vahid
Steven went down to Houston the next day. He stayed for almost two weeks, twelve hours a day. The hospital opened on schedule.
What we found when we looked at the bigger picture
Brian Smith, Fornida's System Architect, joined the engagement after the Houston open. The first thing he mapped was the shape of Ricky's job.
Ricky is their primary IT, technical operations, compliance, all that kind of stuff. Like the full every single thing. He's the full officer there in the corporate. So he is overtop every single place. The issue being he is one person for all of these locations.
— Brian Smith, System Architect, Fornida
That's the buyer profile every multi-location healthcare operator recognizes: one technical officer covering five-plus facilities, every vendor, every audit, every nurse ticket. The problem isn't headcount. It's the lack of a system that takes routine work off the desk.
The next thing Brian mapped was the vendor density inside a single nurse ticket.
The vast majority of their work is going to be done in vendor software. They use software called Well Sky... it connects to insurance, which is a different person. It connects to the software that sends pills out, it sends it to the heart rate monitor. There's a lot of different pieces there, and we were able to go in and work with them and really map that out. So when we have an issue, we're able to assist directly... if something doesn't work, we can contact the people immediately so they don't have to sit there spinning.
— Brian Smith
In a normal small business, an IT ticket usually touches one or two systems. In a rehab hospital, a single ticket can touch the EMR, the insurance gateway, the medication dispenser, and the heart-rate monitor. Four vendors, four contracts, four support queues. Full-stack MSP in this context means triage across all of them, not just patching Windows.
The cyber gaps we found inside the IT work
This was an IT engagement first. Two cybersecurity issues surfaced inside the IT scope that needed fixing before the next hospital opened.
The first was an EDR coverage gap nobody knew existed.
When we deployed Sentinel One, they had a different software before. But even with that software, we discovered that if they had, let's say, a hundred machines, only about 60 of them had that software deployed, and they didn't even know that. So it doesn't matter if you pay for this really expensive, nice EDR if it's not even deployed.
— Brian Smith
That's the most common gap we find inside a healthcare IT environment. The EDR isn't broken. It isn't deployed. Inventory and monitoring catch it. Trust alone doesn't.
The second was an email flow that was treating PHI like generic mail.
At a normal company, you email basically anybody. But with medical, it's a lot more crucial. Every document you work with is PII level. So we helped them make sure emails were encrypted. If you're a regular nurse, you don't need to email a random person at Gmail. So we were able to go in and work out email flow rules. That required us to really understand what are the nurses doing, which are the roles who need that? A receptionist or admissions person is going to be emailing insurance. But this nurse, this is all internal.
— Brian Smith
Email flow rules tied to roles, not individuals. Nurses internal-only by default. Receptionists and admissions cleared to email insurance carriers. Encryption on outbound PHI. The rules came from sitting with the team and walking through what each role actually does, not from a generic HIPAA template.
The playbook that emerged
Hospital #1 was a fire drill. Hospital #2 was less of one. By hospital #3, ExaltHealth and Fornida had built the playbook that turned openings into routine.
One of the main things which helps is that they also standardized. Most of their locations are roughly the same size. Now we're able to look at things as, okay, your estimated start date is in three months or four. Because we've done this, we now know. Okay, here's all the equipment they need. Here's the firewall, here's the networking equipment, here's the workstations, printers, all that kind of stuff. We have this standard package. They confirm it, place the order, and we're able to fully configure it, get it done, and we don't even have to bother them for 99% of this.
— Brian Smith
That last clause is the win: we don't even have to bother them for 99% of this. The whole point of an opening playbook is that the CTO of a multi-location operator stops being the bottleneck for every facility's buildout. Order placed. Equipment configured. Pre-staged. Site visits scheduled. Hospital opens.
The discipline that makes the playbook work is showing up early, before there's anything to install.
Nothing goes on schedule when it comes to construction or raw hardware implementation. What's really important is to be able to check early. We take multiple trips out where the first time we visit, we might not be installing anything, but the whole point is we're evaluating. If they got 30 access points and we're walking around and we're like, okay, well shoot, these are supposed to go on the wall there and there's nothing there. There's no ports, there's nothing. So we are able to spot that kind of stuff pretty early.
— Brian Smith
The cautionary version of skipping that step is the Florida coordination story.
One of their locations in Florida, they hire a CEO who's supposed to be visiting the site and do things, but it wasn't well communicated. The ISP, the internet provider, showed up to turn on the internet. There was no power, no walls. And that was never communicated from the contractors. The CEO, the owner doesn't know every single person who needs to be involved. There's a lot of chefs, right?
— Brian Smith
The ISP showed up to wire a building that had no power and no walls. Nobody was wrong individually. The coordination across contractors, ISP, CEO, owner, and IT just didn't happen. That's what the playbook now prevents.
What this means for any growing healthcare operator
Three things this engagement proves about the shape of multi-location healthcare IT right now:
- Hospital openings are project-management problems, not technology problems. The win isn't the firewall or the EDR. It's the coordination across contractors, ISP, construction, compliance, and IT before opening day. The Florida ISP-shows-up-to-no-power story is what happens when that coordination fails.
- One-person IT departments need a partner that takes 99% of the buildout off the desk. Standardized equipment lists, pre-configured packages, and scheduled site visits are how a CTO covers five facilities without burning out.
- EDR coverage gaps are common and invisible. "100 machines, 60 had it deployed, they didn't even know" is the pattern, not the exception. An IT engagement that doesn't audit the security stack is half a job.
About ExaltHealth
ExaltHealth is a rehabilitation hospital chain operating across Texas and Florida. Their first hospital opened in Houston in 2024. Five facilities are operating now, with eight more in planning. Ricky is the CTO, and also the IT, compliance, and technical-operations function for every location. Most of ExaltHealth's clinical work runs through Well Sky and a tightly integrated stack of insurance, pharmacy, and patient-monitoring vendors, which is why Fornida's job is as much vendor triage as endpoint management.
Tools deployed
- SonicWall — perimeter firewall at every hospital. Standardized configuration across facilities.
- SonicWall CSE — ZTNA, planned for hospital #3+, replacing legacy SSL-VPN.
- SentinelOne EDR — replaced the previous under-deployed EDR. Now covers every endpoint, every facility, with monitoring.
- Checkpoint Harmony + Coral — email security. Harmony at the newer hospitals after Coral at the early ones.
- Aruba — wireless access points and switching across the hospital networks.
- Veeam — backup, run against the standardized infrastructure footprint.
- ConnectWise Automate — RMM across the multi-site environment.
- Microsoft 365 + Azure — with role-based email flow rules tuned for HIPAA (nurses internal-only by default; receptionists / admissions cleared to email insurance).
What managed IT services for healthcare look like at multi-location scale
Small-business managed IT isn't only about the help desk. It's about whether your single technical officer can open the next location without it becoming a crisis. The work that gets you there is unglamorous: standard equipment lists, pre-staged configurations, early site evaluations, monitored EDR coverage, role-based email rules. It's the difference between hospital openings that consume your CTO and hospital openings that don't.
If you're running multi-location operations on one technical officer's calendar and the next opening is on the books, schedule a 30-minute call. We'll walk through what the buildout actually looks like and where the coordination gaps usually live. No urgency, no pressure. Just a working conversation about whether a playbook makes sense for what you're building.
