The modern hospital relies on three enterprise platforms: the electronic medical record (EMR), the Picture Archiving and Communication System (PACS), and a clinical collaboration platform that connects clinicians, patients, and families.
While the EMR and PACS are well established, the collaboration layer is still taking shape. As virtual care becomes a permanent part of healthcare delivery, hospitals that treat collaboration as enterprise infrastructure, not another departmental application, will be better positioned for the future.
Key Takeaways
- The modern hospital doesn't run on one platform. It runs on three, each solving a fundamentally different problem.
- Early EMR adoption was department by department, and the resulting fragmentation forced enterprise consolidation.
- Virtual care is following the same pattern: many health systems now run four or more telehealth vendors under one roof.
- That isn't a telehealth problem. It's an enterprise architecture problem.
- Clinical collaboration belongs alongside the EMR and PACS, not beneath them.
Every enterprise platform has strengths and limitations. The mistake isn't choosing the wrong one — it's asking one platform to be all three.
Why Did Hospitals Consolidate Around the EMR?
I started my career on paper.
When I needed to analyze patient data, I'd walk down to medical records and pull charts by hand. The charts were so heavy that I'd load them into a shopping cart, wheel them over to a table, and spend hours flipping through stacks of paper. Anyone who trained in that era remembers it.
Then came the promise: we're going to digitize all of this and make it easy to find what you need.
It was a good promise. It just didn't unfold the way anyone expected.
In the early days, every department selected its own electronic medical record. Medicine wanted one system. Surgery wanted another. Anesthesia chose a third. Each department made a decision that made sense for its own workflow.
Collectively, though, those decisions created an operational nightmare.
IT teams were left supporting multiple vendors, maintaining different infrastructures, and managing systems that couldn't communicate with one another. Eventually, hospitals realized that fragmentation wasn't sustainable. They consolidated, first to a handful of vendors, and eventually, for many organizations, onto Epic as federal incentives accelerated widespread adoption.
The lesson wasn't about records
It was about what happens when enterprise technology evolves one department at a time.
Is Telehealth Following the Same Pattern?
I've watched this movie before. Today, I believe we're watching it happen again with virtual care.
Telehealth began with carts, expensive ones, often built on Cisco or Polycom hardware. As the market evolved, specialized vendors emerged for nearly every clinical use case. Stroke programs adopted one platform. Behavioral health selected another. ICUs chose something different.
Every clinical champion found a solution that worked exceptionally well for their department. None of those decisions were wrong.
But over time, they produced the same outcome hospitals experienced during the early EMR era: multiple platforms performing similar functions, each requiring its own support model, maintenance schedule, contracts, and training. Walk through many health systems today and you'll find four or more virtual care vendors operating under the same roof.
That isn't a telehealth problem. It's an enterprise architecture problem.
Alan Pitt, MDChief Strategy Officer and Co-Founder, VitalchatWhat Are the Three Enterprise Platforms Every Modern Hospital Needs?
Many people assume the goal is to find one platform that does everything. I don't think that's realistic.
The modern hospital doesn't run on one platform. It runs on three. Each exists because it solves a fundamentally different problem.
The third platform is the one still evolving. As virtual care continues to mature, I believe this collaboration layer will become just as essential to hospital operations as the EMR and PACS are today.
Why Can't One Platform Do Everything?
Every enterprise platform has strengths and limitations.
| Platform | Excels at | Not designed for |
|---|---|---|
| EMR | Managing clinical documentation | Imaging storage, real-time connection |
| PACS | Managing medical imaging | Documentation, connecting people |
| Clinical collaboration | Connecting people | Documentation, imaging storage |
None of them excels at the others' primary function. Trying to force one platform to perform every role often leads to expensive technology that satisfies no one. Hospitals generate more value when these platforms work together rather than compete to become everything.
What Should Health Systems Do Next?
If history teaches us anything, it's that fragmented technology doesn't stay fragmented forever. Department-level purchasing eventually becomes an enterprise conversation. That's exactly what happened with electronic medical records.
I believe the same consolidation is coming for virtual care. The organizations that get ahead of it won't continue buying telehealth one department at a time. They'll recognize clinical collaboration as enterprise infrastructure, something that belongs alongside the EMR and PACS, not beneath them.
I'm pragmatic about these decisions. Hospitals have limited budgets, limited staff, and limited bandwidth for innovation they only half believe in. The goal isn't to replace every existing system overnight, it's to recognize the pattern before history repeats itself.
Complexity only gets harder to unwind
Because once you've lived through pushing shopping carts full of paper charts, or managing shopping carts full of disconnected vendors, you learn that complexity only gets harder to unwind.
FAQ
Why isn't the EMR enough for virtual care?
Electronic medical records are designed to manage clinical documentation and patient information. They are not built to support the real-time communication and collaboration required for virtual nursing, telehealth, patient engagement, and multidisciplinary care coordination.
Why do hospitals consolidate technology vendors?
As organizations grow, maintaining multiple systems that perform similar functions increases operational complexity, support costs, and training requirements. Enterprise standardization improves interoperability, simplifies IT management, and creates a more consistent user experience.
What is a clinical collaboration platform?
A clinical collaboration platform enables clinicians, patients, and families to connect virtually across the care continuum. It serves as the enterprise layer for communication and virtual care workflows while integrating with systems like the EMR and PACS.
