More musings from the Healthtech meeting. Given that this is a somewhat private meeting, and I’m an invited guest, I’m not going to name names, but suffice it to say that the health systems here include many of the largest (predominantly non-profit) regional hospital systems in the US.

So from my non-scientific surveillance, where are they and what are the challenges they are facing? In general the last few years have been about automating their laboratory, pharmacy and PACS (radiology) systems. At least in some hospitals, this has led to reducing costs in testing , and getting results back much faster (in 6 minutes in one case). This of course promotes quicker decisions which filters into lower ALOS and increases ROI. The rest of the effort in the last few years has been about creating the wired and wireless infrastructure that’s needed to support the next stage of their plans–in fact wireless is a major focus.

The new challenge is CPOE and bedside medication records. Now they are starting at varying rates to move to clinical documentation at the bedside and also at the nurses station. CPOE (i.e. getting the physician ordering, particularly medication ordering, in the loop) is the major push many of the systems are working on now. This somewhat tracks with various studies showing that CPOE use is pretty low (of course it’s existed at some hospitals such as Brigham & Womens and Intermountain for several years).

Some of these systems are creating big time process improvements (so long as the medical team is bought into the decision process). But by no means do the medical staff appear to be so compliant in all cases–in one case there was no improvement in several basic process measures. So putting the system in is only part of the battle, and the medical culture still seems to be the biggest hurdle.

One big system (which has introduced a lot of new technologies) is very rigorous about incubating a test-lab learning environment before any new technology is moved into different facilities. This is part of an extremely detailed planning process, which needs exceedingly high levels of buy-in from clinical and operational staff, and rigorous assessment at all levels of every roll out. In other words there’s no organic growth of IT use, its all carefully designed. Nor are new or innovative, but untried, technologies allowed into the system. Instead the IT group makes sure that any devices or applications they introduce does not distract them from their total focus with keeping the network up for Five Nines reliability (99.999% up time). So their priority is keeping the mission critical network up. Their system hasn’t gone done unscheduled in 2 years. Some time ago Paul Saffo at IFTF said that eventually computer downtime (like phone downtime) would start killing people. Plenty of these hospital CIOs seem to believe it. So as IT becomes more integral to other parts of the hospital (ie. lab/pharmacy first, nursing next, then physicians) many hospital systems are looking for incredibly (and justifiably) high levels of network/application uptime and reliability.

And don’t mistake that putting this all in is anything other than damn hard work. The words Six Sigma and Process Improvement were heard alot. All in all they are probably not having as much fun as we technology futurists have looking at all the new toys. But in terms of creating the environment for process-driven hospital-based care, at least some of the leading systems in America are making progress.