Latest posts by Khal Rai (see all)
- The Year’s Innovations – Wrap-up & What’s to Come! - January 11, 2017
- Data Done Differently - October 11, 2016
- Frictionless Product Delivery - August 18, 2016
As I mentioned in my previous post, The Truth Is Stranger Than Friction, some physicians are so dissatisfied with their EHRs that they wish they could return to the days of paper charts. The main culprit is the data collection process, which causes friction between doctors and patients. I argued that workflows should, first of all, adapt to each doctor’s style so that doctors can concentrate on patients rather than technology, and, second, enable seamless data collection during patient interactions so that doctors don’t waste time recording data later. Traditionally, EHRs have been vendor-led in how they were built rather than being designed around how clients wanted to use them.
The role of an HCIT vendor is to understand its clients’ and prospects’ requirements. This step is often overlooked. We are seeing huge dissatisfaction in practices’ experiences with their current EHR solution. This can be seen with the impact these solutions have on the doctor-patient relationship; many practices have seen a reduction in the amount of face-to-face time with patients, as well as a decrease in the number of patients they can see.
According to a recent Medscape study, 45% of patients made complaints either occasionally or frequently about lack of eye contact, excessive questions, or providers focusing more on the equipment than the exam. On top of that, a recent article on Healthcare Scene reinforces that doctors are frustrated by using EHRs because they don’t match their workflows, feel clunky, and require too much time for documentation. The article goes on to say that these frustrations lead to both physician burnout and a decrease in EHR use.
However, is technology the culprit? No. I believe these problems are not a reflection on the technology. We see in other industries how technology has been optimized to improve business operations and improve customer satisfaction. I would argue that the fundamental problem with EHRs is a lack of understanding of what challenges practices face, and how to accommodate and plan for both today and tomorrow’s needs. This lack of understanding usually results in a poor implementation plan that is set up to fail from day one. Unfortunately, with the move toward a valued-based model, this misunderstanding is likely to cause even more problems.
What is needed is not only a way to capture and share relevant data, but a way to do this without disrupting the physician’s workflow. This is especially important for specialty practices with a high-volume of patients. Workflows should be personalized so they fit around the physician’s way of working rather than interfering with it, and a crucial part of this is cutting out the clutter and showing only relevant information as defined by the physician and practice.
Our team’s philosophy has always been to put the clients’ requirements first in everything we do. We work closely with clients to understand their workflow, and then we provide a solution that improves their operations in a way that makes sense to them. Our years of experience in providing best-of-breed specialty solutions to ambulatory practices has given us a strong appreciation of the importance of designing an agile solution that effectively handles a high-volume patient intake and put through while improving practices’ bottom line.
When it comes to data, we feel just as strongly, if not more so! We want to enable seamless data collection during patient interactions, so that doctors are not spending hours recording data later. We want to empower practices to determine who should capture the data they want, when and how they want, in the context of patient encounter. This means providing a flexible solution that is future-proof, leveraging mobile platforms and predictive technologies, while incorporating Outcomes and Analytics that not only keep up with busy specialists, but actually help move them forward.
That is what we mean by data done differently.