April 15, 2017 Leave a comment
March 13, 2016 1 Comment
Farhad Manjoo, the NYTimes tech reviewer, wrote a story this week about the Amazon Echo, a device for the home using the Amazon Alexa voice recognition service to allow natural-feeling interactions with web searches and web-connected home devices. My immediate reaction was that this will be the human-computer interaction with the future EHR.
Where we now use the mouse and keyboard to search endlessly through complicated menus, in 5-10 years, we will instead be able to say aloud, “Order Mrs. Jones a metabolic panel, lipid panel, and A1C to be done today and again in 6 months. Send the order to the Quest lab. She also needs a bone density scan ordered to screen for osteoporosis. Make sure she has this scheduled and completed by the end of the year. Make a referral to Dr. Smithson in Cardiology for management of coronary artery disease. Send in a one-year refill of her metformin. At the end of our visit today, please send a letter with my full note from today’s visit to her primary care physician.”
As a physician speaks these orders, his shopping cart menu will build on-screen, allowing for verification that the system selected the right items. What now takes several minutes and immense cognitive effort could instead be completed with natural speech and minimal effort in far less time.
I hear from colleagues all the time that they are overwhelmed when using EHRs with too many buttons, menus, and too much clicking around. They feel disconnected from the patient sitting in their office, and that the computer screen has intruded in that relationship. Perhaps a natural language voice recognition system like Alexa is one step closer toward a more satisfying and connected experience for everyone.
January 23, 2015 2 Comments
A rapidly growing number of health innovations such as mobile apps, diagnostic tools, and sensors are being developed with a focus on enabling health and wellness outside of the traditional medical office visit. As Eric Topol points out in his new book, The Patient Will See You Now, many of these tools will help people independently understand and manage their health. A long history of medical paternalism will be overturned as health information is returned to the individual and autonomy restored. This is a great trend.
However, we do not have to create an “either-or” dynamic where some health information is held by the healthcare system and other information by the individual. These new technologies will be maximally useful when they enable and facilitate a deeper, richer dialogue within the context of existing doctor-patient relationships. To achieve this more coherent and comprehensive healthcare, we need to bring together the patient, her digital health information from new sources, the doctor, and the EHR.
These concepts of interoperability and EHR integration are being widely recognized as crucial over the next few years in healthcare, as evidenced by the JASON Task Force’s recommendations and the formation of the Argonaut Project.
What concerns me as a practicing physician and informaticist is when I hear people discuss EHR integration as if it means only this:
This represents the idea of taking every single data point collected by mobile apps, sensors, and other tools and passing it all straight through into the EHR. I am always reminded of one of my favorite scenes from I Love Lucy, but instead of desperately trying to stuff chocolates into my cheeks and clothing, the medical conveyer belt could make physicians unable to keep up with massive quantities of inbound data from patients.
I think it is this sentiment that has led to articles like this one posted in August 2014, saying that “doctors don’t care about your FitBit data.”
I disagree. The truth is that I might care about your FitBit data, depending on the clinical situation, the context of that data, and the way in which it is presented to me. I just don’t know yet. I think it is very likely that there will be many of these situations where your activity tracker data matters a lot! We can do better. We can use new information sources when they are helpful and add value by weaving together a comprehensive view of a patient’s health information that facilitates better conversations between individuals and their doctors, and thus better care. This means that patient-generated data cannot be siloed off from the EHR. It instead must be incorporated into clinical workflows as part of the EHR. To achieve this vision of a more complete EHR integration, I think we need the following:
Four Key Features of EHR Integration
1: Discrete data points: I know, I know. Didn’t I just say we don’t want this? I actually believe we still do want access to discrete data. It just cannot be the beginning and then end of integration. Also, this refers not just to data coming in to an EHR from outside, but clinical data flowing out from an EHR to an app or analytic tool, such as your medication list, medical history, or recent hemoglobin A1c values.
2: Analytics and decision support: We need intelligent rules, filters, and analytics to help route information at the right time to the right person and right place. These rules will work best if they can use data from inside the EHR along with these new, patient-generated data sources.
3: App and workflow integration: Talented and innovative software developers and others are creating new ways of presenting information, such as disease-specific data visualizations. We need to make it easy for physicians to access these within the context of their daily work in the EHR. Physicians are not going to launch and log-on to their EHR and three different applications to compare data, no matter how snazzy and how much media buzz your new app has. Moreover, we should be able to do clinical documentation, make a therapy change, or order further diagnostic testing from within the confines of a new tool and have that documentation, prescription, or lab “order” feed back into our EHR for action. This will keep your medical chart and health record more comprehensive and easier to follow, with less information scattered around different places.
4: Communications integration: Finally, with all of this information passing back and forth, each system is going to be capable of sending and receiving messages between the doctor, patient, family members, and other care team members. Nobody will want to log-on to every individual account to check messages. So, we need to be able to intelligently integrate and route messages so that each person can send and receive messages from the “hub” application that makes most sense to them.
At the UCSF Center for Digital Health Innovation, we are excited to be working toward this vision of comprehensive, workflow-driven EHR integration.
(This post is based on a talk I gave at the Diabetes Technology Meeting in Bethesda, Maryland in November 2014.)
“But who is going to pay for it?!” — New Medicare Billing Codes for 2015 Include Remote Chronic Disease Management
November 5, 2014 Leave a comment
September 19, 2014 Leave a comment
Epic’s User Group Meeting (UGM) is a Healthcare Conference
The Epic EHR is so ingrained in healthcare now that the UGM conference is really a healthcare conference, not an IT conference. This was a conference where more than 10,000 healthcare professionals met to share best practices about how to run a healthcare organization and deliver care, and oh by the way, the tool you’re using is this software called Epic.
There were clearly dominant themes this year among the priorities of the healthcare organizations in attendance:
1— Population health and ACOs
2— Patient-______: patient-engagement, patient-centeredness, patient reported outcomes, patient collected data, patient portal, etc
3— Health information exchange
4— Capture and use of discrete data by physicians
5— E-visits and video visits to improve access (and maybe end the long reign of the office visit)
6— Algorithms and analytics, especially with combining of multiple data sources
7— Personalized medicine using genomic data and home-collected data alongside traditional clinical data
Epic Should Do SaaS
If I were Epic, I would develop a SaaS (Software as a Service) version (call it “EpicLite”) and cannibalize my own business from the bottom up. Epic is making some fantastic improvements to their software, but a major complaint you hear around the lunch tables at UGM is that no organization has the resources to implement all of Epic’s features and functions. Epic has made their software endlessly customizable in an attempt to please customers who asked them for such customization. But the end result is that we all bog ourselves down. I’d like to see Epic push back a bit more against what we all tell them we want, be bolder, and push out software to us all that just works out of the box. They can start with the “EpicLite” version and sell it to organizations less complex than the very large customers they most frequently serve now. Follow the 80/20 rule, pick the things that work best, and give it to people. I promise that we will complain, but then we will deal with it and save a lot of money and effort. They could then slowly move up-market with this SaaS version to sell it to the more complex and large customers in true Clayton Christiansen-esque disruptive innovation to disrupt their own core business. To analogize based on one of Christiansen’s examples, they won’t want to be selling mainframes in ten years when everyone wants PCs.
Open.Epic and Apple HealthKit Integration
I’ve heard a lot of skepticism about this effort over the past year because Epic has always had the reputation of being a very closed system, but Open.Epic should change that perception. I think that this is going to be a big deal. I believe that a major reason for the lack of success of many digital health apps is that they are silos and built in standalone fashion. Let’s face it: the EHR is the hub of clinical workflows and no matter how cool and important your app is, it is still just an add-on. Apps cannot be successful if they don’t fit into clinical workflows. Therefore, to be successful, the workflow of using an app needs to blend in with the use of the EHR. Epic publishing APIs through Open.Epic for people to connect apps in is a game-changer and will enable an entirely new generation of apps that bolt on alongside the EHR.
Similarly, I think the Epic and Apple Healthkit integration will catalyze many of the currently stagnant use cases for sensor and device data, as it will now easily feed into the clinical environment.
Random Thoughts and Impressive Numbers
I found myself wondering what Epic would be like if it were in Silicon Valley instead of Wisconsin. I don’t think it would be very Epic-like. You probably wouldn’t see them announcing next year’s product releases in the form of a musical.
It is hard to tell how much the healthcare system is shaping Epic’s software development plan versus the other way around. I’m sure it is some of both.
Epic is incredibly successful at energizing its customers and getting them to evangelize and espouse the virtues of their product for them. And we all pay to fly out to Wisconsin to do it! When I walked by it, their usability testing lab had a more than half-hour wait to get in and a line down the hallway.
54% of the US and 2.5% of the global population have an EpicCare chart. There were 5,000,000 Epic<—>Epic information exchanges in Aug 2014.
January 23, 2014 Leave a comment
The Most Important Digital Health App of 2013: Bugs and Drugs
In a year that saw consumer-facing digital health app after consumer-facing digital health app, the app that impressed me most was actually clinician-facing, not consumer-facing. In 2012, the digital health apps that stood out to me most were Kinsa, a smartphone-connected thermometer enabling real-time community maps of infectious disease, and GeckoCap, a wireless sensor-in-a-smartcap for asthma inhalers enabling parents to track their kids’ asthma. (Of course, for fairness sake, I’m leaving out Tidepool, the open platform for type 1 diabetes for which I’m medical advisor, and about which I am incredibly enthusiastic.)
When seeing new digital health devices and apps, I usually have one of three reactions, either: a) “Nope, next!”; b) “This has potential, I want to hear more about it”; or c) “I need to immediately call everyone I know and tell them about what I just saw”. This year, reaction C came from the AthenaHealth/ePocrates Bugs and Drugs app. This app makes me feel optimistic about real progress happening in healthcare. This app makes me feel like the promise of the Learning Healthcare System is either upon us, or truly just around the corner.
If you’ve not seen this app yet, stop reading this article for a moment (come back to finish it, of course!) and go download it from the App Store. The Bugs and Drugs app is a real-time, aggregated, cloud antibiogram.
What’s an antibiogram?
Here is an example of the 2011 UCSF adult antibiogram. First, a quick explanation for the non-clinician. To test a patient for urine or bloodstream infections, clinicians order cultures to see if bacteria will grow (literally) out of the respective collection sites from a patient. If bacteria grows from a culture and the patient is thus deemed infected, tests are done to see which bacteria is the specific cause. Additional tests are then done to see which antibiotics will be effective at killing this particular bacteria strain. This is known as sensitivity or susceptibility data. This information can make the difference between giving a patient an ineffective antibiotic and an effective one. Without it, we as clinicians are guessing about which bacterial strain we think the patient might have and which antibiotic to use. We base this on our knowledge about which bacteria are most commonly pathogenic and which antibiotics are designed to kill which bacteria. We also use available past data about cultured bacteria and antibiotic susceptibilities. This last piece of data comes from antibiograms. Many hospitals regularly publish an antibiogram, a handout that aggregates all of the culture and susceptibility data from each culture site (e.g. blood or urine) from the past year. It shows the relative frequency of the occurrence of each bacterial strain and the frequency of each particular bacteria being sensitive or resistant to each common antibiotic. For example, in the example UCSF antibiogram linked to above, there were 810 E. coli isolates (the most common bacteria isolated), and 85% of these were susceptible to ceftriaxone, a common antibiotic. You might find that in another hospital in another region of the country, say North Carolina, that the sensitivity rate of E. coli to ceftriaxone is 35%. Thus in the first hospital, the treating doctor would be likely to use ceftriaxone to treat the next patient with an E coli urinary tract infection, whereas in Texas, the doctor would certainly want to choose something else, knowing that ceftriaxone is unlikely to be effective.
So, this information can truly be life or death information. It also contributes greatly to the concept of antibiotic stewardship and appropriate use of antibiotics to maintain their effectiveness for future use. Traditionally, antibiograms are published regularly with an aggregation of the previous year’s data for each particular hospital. But, that is static data, a collection of one year at a time. It is also data bound within the physical or virtual walls of each healthcare organization or medical center.
Bugs and Drugs: An Antibiogram for the Learning Healthcare System
The Bugs and Drugs app has taken this concept and moved it into the cloud era. The app capitalizes on the fact that AthenaHealth, as a cloud EHR provider, is able to aggregate all of the clinical data from their EHR, in real-time. They have aggregated together all of the bacterial culture and antibiotic susceptibility data from all of their users and display it in real time in this app. You are a doctor in Wichita and your patient has a urinary tract infection? Pull open the Bugs and Drugs app and you can actually see what the most common bacteria are in the Wichita area right now that are causing urinary tract infections. You can see which antibiotics are effective against those bacteria in the Wichita area right now. This data is not from last year, it is from the last few weeks. This data is not just from your hospital’s lab, it is from all of the hospitals’ labs in the area.
The catch of course is that this still lacks true health information exchange. While the data does cross boundaries between health systems, it does not cross EHR vendor boundaries, coming only from AthenaHealth locations. So, in the example above, you would not be getting data from every location in Wichita, just those that use AthenaHealth.
However, the really important thing about this app is that it shows on a nuts-and-bolts clinical level what we can do with aggregated real-time clinical data when it is put into a useful format in the hands of a clinician. This information can influence care right now, for the patient sitting right in front of you. This is the realization of the possibilities of the Learning Healthcare System, moving valuable information much more efficiently into the hands of the treating physician. I predict (and hope) that we’ll see many more innovations like this in the coming year.
December 16, 2013 Leave a comment
The current paradigm of office visits every three months for PWDs (people with diabetes) is not the right model (nor is it for other similar chronic conditions). The management of diabetes requires a patient to make dozens of daily self-management decisions. “How much insulin should I give for this slice of pizza? Do I need to eat a snack to prevent my blood sugar from going low before I go for a jog?” Diabetes related questions and issues do not occur on an every-three month basis in synch with this current model for office visits. They are predictably unpredictable. Accordingly, to best serve our patients, our system must be flexible and nimble.
In the current model, I see a PWD in my office and let’s say, for example, that we decide together to make a change to his insulin to carbohydrate dosing ratio. He then leaves my office and we wait three months to reconvene and see if that dosing plan change is working or not. It’s not that it takes three months to decide. We could probably know within a week or two if the change is working. It’s just that healthcare isn’t set up that way. Our entire world now, in every industry and facet of life, is about data, analytics, and metrics. Other industries have learned that rapid feedback loops are effective. Adjusting a PWD’s insulin to carbohydrate dosing ratio should be no different. By the time he comes back to my office three months later, the opportunity for learning may already have been lost. Neither one of us has gotten timely and relevant feedback about our decisions. We may have lost the opportunity for a teachable moment. Healthcare needs to develop a new model where these feedback loops are much tighter and much faster, actually capitalizing on opportunities for teachable moments. (Sidebar: One doctor who realized this years ago was Dr. Jordan Shlain, who founded HealthLoop) Research studies show that PWDs are more successful and confident with managing their diabetes when they feel like they have the backup and support of their clinical providers looking over their shoulders to make sure things are going ok. If we were to design the system from scratch to accomplish these goals, we probably would not have built it to rest on the concept of office visits every three months.
So, what should be the future model of a Diabetes and Endocrinology clinical practice? Here’s what I imagine my practice looking like in the (hopefully near) future. Instead of having 16 office visit slots per day of 30 minutes each, I imagine myself seeing 5 patients a day for 45-60 minutes each, allowing us to take our time working together in person and truly addressing the needs and goals of the patient. These longer visits are essential for a patient new to my practice, a patient with a complicated or unknown diagnosis, a patient with complications or a major change in their disease state, or for discussing major changes in therapeutic course or strategy. The rest of my day will be spent using a dashboard to do remote population management, looking for trouble spots among my patient population and focusing in on those, and doing telemedicine, connecting with patients through video-chats to make more minor adjustments and to do brief “check ins.” Ten minutes spent with a patient at the point where there is a teachable moment like a low blood sugar from walking the dog might be more effective than a standard 30 minute office visit every three months. We’ll have to test this hypothesis, of course, but we must try it.
This is why I’m brimming with so much enthusiasm and excitement about working with the non-profit, Tidepool, who is building an open data platform and a new generation of software applications for the management of type 1 diabetes. Tidepool will provide us with the technology infrastructure to reach this vision of more frequent feedback loops and teachable moments. I’m also very excited about the work that my UCSF colleagues, Drs. Ralph Gonzales and Nat Gleason, are doing to pilot the use of telephone visits and e-visits with patients in place of office visits. Their work is paving the way toward demonstrating efficacy of e-visits, helping to achieve payer reimbursement so that such a model can take root.