Four health system technology executives explain how they decide which workflows every hospital shares after an acquisition and which ones stay local. Watch below or on YouTube.
Health systems that bring acquired hospitals onto one platform should build on a shared technology foundation and keep only the local workflows that deliver value, four technology executives said during a recent healthsystemCIO Webinar. The panel included Ash Goel, MD, SVP and CIO at Bronson Healthcare; Craig Richardville, SVP and Chief Digital & Information Officer at UF Health; Lisa Stump, SVP, Chief Digital Information Officer and Dean for Information Technology at Mount Sinai Health System; and Tinu Tadese, MD, former System VP and CMIO at Boston Medical Center Health System. All four described systemness, a health system operating as one organization, as a different goal from sameness. They also agreed that governance should decide which local differences stay. Clinical, operational and financial leaders sit at that table alongside IT.
The discussion opened with Goel separating shared technology from identical operations. “Systemness is like the plumbing codes: the plumbing has to be right and work everywhere, and the fixtures can be different,” he said. Patients want a consistent experience, and clinicians want the same workflows so they do not have to do 10 things differently. In other words, a gold, silver or bronze fixture should not change how the system runs.
For Richardville, systemness is an ongoing process. He starts with the enterprise standard and then looks for warranted variances, whether clinical, operational, regulatory or driven by a local market.
Source link







