Saint Luke’s Health System is a Kansas City-based integrated health system that encompasses 10 hospitals, 918 staffed beds, 9,000 employees, 450 employed physicians, and 2,440 affiliated physicians, delivering patient to care to patients in a 67-county service area surrounding the Kansas City, Missouri/Kansas metropolitan area; it is a health system with $2.8 billion in annual revenues.
In a presentation that was presented on July 16 in a webinar sponsored by the Institute for Health Technology Transformation (iHT2-a sister organization to Healthcare Informatics under the Vendome Group, LLC corporate umbrella, Deborah Gash, vice president and CIO of the St. Luke’s Health System, shared with webinar attendees the story of her organization’s implementation of a cloud-based information exchange system for diagnostic images.
Like many hospital-based organizations, Saint Luke’s had been struggling with a complex, disjointed system of diagnostic image management, with diagnostic images not readily available, or difficult to share between and among clinicians and care sites; access to studies not timely; and with complicated, awkward practical challenges around the fact of diagnostic images constantly being moved around from one location to another, being lost, not capable of being read, and so on.
“As CIO, I try to get out and meet with our various stakeholder groups and talk with them about their technology and really hear first-hand from them about what’s working well and not,” Gash told her audience. “And it has always come up that the access to information and in particular images, has been problematic. Our previous state was reliant on people, had lots of points of failure, and was a particularly challenging area for us. Although we had an enterprise PACS [picture archiving and communications system], we were really struggling with making those images from outside the organization available to our providers. Images might come via CDs from patients, or via ambulance service. So the only time we could view those studies was when a patient physically arrived and we physically had the studies with us. So being able to understand what was happening with the patients before that was very challenging for physicians.”
Meanwhile, Gash noted, “Patients would also bring CDs with them to physician appointments, and we’d have to process those images, when they were from imaging centers or other hospitals. Or we would have surgical specialists performing procedures in our organization, who might perform studies in their clinics, and would want those available during those surgical procedures, so they would be bringing media in for use during surgeries.”
As a result, Gash said, “Getting those CDs where they needed to be, and getting them loaded, and so on, required a lot of manual processes; and many of the CDs weren’t viewable if they didn’t have the right viewer; or even they had a viewer embedded, the viewer wouldn’t load; or CDs would get lost along the way. It created a lot of dissatisfaction, and I would hear about it from physicians all the time. And my security team would want to prevent the loading of CDs onto devices to block viruses and malware.” In sum, she said, “Overall, this whole process of handling images was very inefficient and a constant source of frustration.”
In fact, Gash said, the average cost of $7.00 to produce a single CD carrying diagnostic images, and the costs and hassles of having so many CDs going lost or not being able to be read, were mounting for the organization, which has been generating a half-million diagnostic imaging studies every year. “So this was very costly for us,” she said.
As a result, beginning in 2011, Gash told her webinar audience, “We ended up with a pretty aggressive requirements list” for some sort of new IT-based system that could solve all of the above problems. “I began by inquiring and looking and seeing what I could find in the market. And at that particular time, there really weren’t a lot of options available. I spent a whole day in the exhibit hall at the HIMSS Conference [sponsored by the Chicago-based Healthcare Information & Management Systems Society], and found some there.” Meanwhile, she said, I went to our PACS vendors first and explained the challenge. We focused on the methods that referring physicians used to access studies. This didn’t affect the radiologists as much because their expectation was that they would see the studies through their PACS, so we focused on the referring physicians. We looked at distributed architecture. And cloud-based architecture was very favorable to me as CIO, because the technical requirements were low and the speed at which I could deploy was much faster.”
Gash made it clear that moving forward with a cloud-based solution did mean engaging in a lot of provider and staff education. “I did have to spend a lot of time talking with people about cloud-based technology and security,” she said. “People weren’t very knowledgeable about it at the time. And we still have lots of conversations about whether it’s secure or not and whether we’ll get into privacy issues. So this is key: you have to spend a lot of time educating on security, etc. I even had to spend a lot of time meeting with risk management and others. It required a lot of socialization to get people comfortable.”