Designers begin by understanding how people work in the real world, and then create the best IT system that's technically feasible.
The one given across all sectors of healthcare today is that change is coming, and not the gradual kind. This is multi-billion-dollar, build-up while tearing down kind of change. If that change is to lead to dramatic improvements in the effective and efficient care of patients, our systems must be redesigned, not re-engineered. Here's why: It's a matter of life and death.
On Sept. 25, 2014, Eric Duncan reported to the emergency department of the Texas Health Presbyterian Hospital Dallas with a low-grade fever, abdominal pain, dizziness, and headaches. When he returned to the hospital on Sept. 30 and was diagnosed with Ebola, the question asked by nearly everyone paying attention (and we all were) was, "How could the doctors and nurses have missed the telltale signs of Ebola presenting in a man just returned from west Africa?"
The hospital's first response was to blame a design flaw in its electronic health record (EHR) system that prevented travel history data entered by nurses from presenting itself to doctors. It later retracted that claim, stating, "There was no flaw in the EHR in the way the physician and nursing portions interacted related to this event." The system behaved exactly as it was intended to.
So was there a flaw? Absolutely. The system was built with the assumption that the people using it should conform the way they work to the way the EHR was built, rather than the other way around. In other words, like most healthcare systems, their EHR was engineered.
Design, on the other hand, begins by gaining an understanding of how a system is likely to be used within a given environment and creating that system accordingly.
For those on the delivery side of healthcare, it is not news that very few of our systems are created with consideration of how they'll actually be used.
First, learn how they work, then figure out what they need.
Our methods of "handing off" patients from one clinician to another create deadly information black holes and miscommunications. The devices in our incredibly sophisticated Intensive Care Units emit a cacophony of competing sounds, causing nurses and doctors to ignore the occasional deadly warning. Clinicians cut and paste pages of text into the notes sections of electronic medical records, ensuring adequate documentation for billing, but burying potentially critical details. In fact, health services researchers have filled medical libraries with details of poorly designed systems that contribute to the accidental deaths of hundreds of thousands of patients globally each year.
So why the urgent need for design in healthcare now? There are three macro-level developments that are combining to create a perfect storm of change in healthcare.
Payment reform. The shift from "fee for service" toward a "fee for value" reimbursement will affect nearly every aspect of care, from who pays, to where and how care is provided.
Healthcare goes digital. Significant government investments, including up to $44,000 per adopting clinician, have driven electronic medical record adoption from 11% in 2007 to 78% in 2014. In turn, healthcare is increasingly awash in data that has yet to be widely employed to improve care.
Affordable high throughput sequencing. The dropping cost of reading a human's DNA is leading to a fundamental rethinking of disease and biology, and to new classes of drugs and diagnostics. The implications of what is sometimes called "personalized medicine" will affect everything from how clinicians will make sense of mountains of new data, to how IT departments will store it, and how payers will reimburse for it.
Each of these impending changes represents fundamentalchange to existing processes, systems, and structures. Success in transforming these systems will be dictated by good or bad design -- regardless of whether designers are involved (they are usually not) or even if it's recognized that "design" is actually what is taking place (it usually isn't).
What Exactly Is "Design?"
Most of the healthcare industry views designers as a luxury afforded to consumer product companies. They are the more-stylish-than-thou gurus who use words like "metaphor" and "user experience." Sure, one or two wander into healthcare now and then, adding a bit of contrast to our drab lab coats and beige walls.
But the need for design is popping up in more industries these days. The notion of involving designers in improving healthcare pinged twice for me in a couple weeks -- once at a meeting and once during lunch with a colleague. That's enough of a sign that I had some homework to do in order to figure out what exactly they were talking about. I had heard one or two interesting talks from designers about their work in re-orienting the architecture of hospitals to "promote" health, and of wheelchairs designed to climb stairs. But what design had to do with the type of health-system-improvement work we do at Ariadne Labs wasn't obvious to me.
So, I started knocking on the doors of designers. I met with the founders of the design firm Invivia, the co-founder of the strategy firm Jump Associates, and spoke with the lead designer at the HELIX Center. I watched videos, read the books they suggested, and asked questions.
In short, I learned just enough to be dangerous, so let me offer a disclaimer. There is an enormous difference between the abilities and approaches of those that have mastered their fields and those of people just learning them. Unlike the novice musician or chef, the masters are so proficient with the tools of their trade that they are no longer restricted to sheet music or recipes. My intent isn't to make master designers out of clinicians or health IT professionals (nor of me) but to show just how important and accessible the basics of design truly are. While I'll surely misrepresent aspects of this field, I am convinced that
Page 2: Get a handle on design.
Leonard D'Avolio, PhD, is the Director of Informatics at Ariadne Labs, a joint venture of Brigham and Women's Hospital and the Harvard School of Public Health. He is co-creator of the healthcare prediction platform Cyft, an assistant professor at Harvard Medical School, and a ... View Full Bio
[Interop ITX 2017] State Of DevOps ReportThe DevOps movement brings application development and infrastructure operations together to increase efficiency and deploy applications more quickly. But embracing DevOps means making significant cultural, organizational, and technological changes. This research report will examine how and why IT organizations are adopting DevOps methodologies, the effects on their staff and processes, and the tools they are utilizing for the best results.
IT Strategies to Conquer the CloudChances are your organization is adopting cloud computing in one way or another -- or in multiple ways. Understanding the skills you need and how cloud affects IT operations and networking will help you adapt.