The following is a guest article by Alisha Moopen, Managing Director and Group CEO at Aster DM Healthcare
Every health system leader I speak with has a smart hospital pilot they’re proud of. A connected room that reduced response times. A virtual monitoring tool that caught deterioration early. An AI-assisted workflow that impressed the clinical team and made it onto a conference slide. What far fewer of them have is a second floor that looks like the first.
That gap — between a successful pilot and genuine enterprise-wide transformation — is the defining challenge of healthcare’s digital moment. And after years of scaling connected care across one of the Middle East and South Asia’s largest integrated healthcare networks, I can tell you: it is almost never a technology problem. The technology works. The scaling doesn’t — because scaling requires something harder than a good proof of concept. It requires a fundamental rethink of how care is designed, delivered, and coordinated.
The Pilot Trap
Pilots succeed in controlled conditions. They have dedicated champions, focused resources, and the benefit of novelty. Enterprise rollouts inherit none of those advantages. Different units have different workflows, different cultures, different patient mixes — and technology that was shaped around one environment rarely transplants cleanly into another. I’ve watched health systems deploy the same platform across ten facilities and get ten different results, not because the platform failed, but because the implementation assumed uniformity that didn’t exist.
The workforce dimension compounds this significantly. When digital tools are added to clinical workflows rather than integrated into them, they don’t save time — they consume it. Clinicians already managing documentation burden, alert fatigue, and staffing pressures don’t need another system to check. They need technology that works the way care works: continuously, collaboratively, and without friction. Getting that right requires involving clinical teams not as end-users of technology decisions, but as co-designers of them. In my experience, that shift — from deploying technology to co-designing it with clinical teams — is consistently where adoption outcomes diverge.
Technology as Infrastructure, Not Addition
The framing I keep returning to is this: smart hospital technology should be infrastructure, not an addition. When a virtual monitoring system’s data doesn’t flow directly into a clinician’s existing decision workflow, it becomes noise. When a connected room operates independently of the EHR, its value is isolated. When digital and physical care pathways are designed separately, you don’t have a smart hospital — you have a regular hospital with expensive equipment in it.
At Aster Hospital Al Qusais — recognized on Newsweek’s World’s Best Smart Hospitals 2025 list, and a two-time recipient of the Best Technology Use Case Award from the Healthcare Management Awards — we approached this from the outset, differently. Generative AI was embedded into patient treatment workflows to streamline and error-proof clinical processes, not bolted on as an afterthought. And rather than deploying point solutions, we built connectivity into the patient room itself: Talab, our inpatient interactive communication tool, links caregivers, clinical teams, administration, and housekeeping in a single seamless interface — so that the room itself becomes a coordination hub rather than a passive space. None of these were standalone deployments. They were designed as a connected ecosystem, each capability reinforcing the others, so that digital coordination became the default mode of care rather than a parallel track running alongside it.
Build for Integration from the Start
The health systems I see scaling fastest made one decision early that others didn’t: they treated integration as a design constraint from the beginning, not a problem to solve later. Retrofitting digital systems into physical and operational infrastructure that wasn’t built to receive them is expensive, slow, and organizationally punishing. Every new technology requires its own bespoke implementation effort. Every workflow redesign happens after the fact. The compounding advantage goes to systems that are built with integration in mind — where each new capability layers onto a foundation designed to support it.
This matters practically as well as philosophically. Implementation costs for enterprise-scale health IT are significant, and organizations that absorb them repeatedly — because each deployment is effectively a standalone project — are not building smart hospitals. They are building costly patchworks that will eventually need to be rebuilt anyway.
The question I’d encourage health system leaders to ask isn’t “does this technology work?” The evidence that it works is abundant. The harder, more useful question is: “Does our infrastructure — physical, operational, and cultural — allow this technology to become the way we deliver care?” Systems that can answer yes to that question are the ones that move from pilots that impress to a transformation that sticks. That’s the difference that matters, and it starts well before the technology is ever switched on.
Alisha Moopen is Managing Director and Group CEO at Aster DM Healthcare, one of the largest integrated healthcare networks in the Middle East, operating 15 hospitals, 117 clinics, and 285 pharmacies across the UAE, Saudi Arabia, Oman, Kuwait, Bahrain, and Qatar.
