Everywhere we turn these days it seems “Big Data” is being touted as a solution for physicians and physician groups who want to participate in Accountable Care Organizations, (ACOs) and/or accountable care-like contracts with payers.
We disagree, and think the accumulated experience about what works and what doesn’t work for care management suggests that a “Small Data” approach might be good enough for many medical groups, while being more immediately implementable and a lot less costly. We’re not convinced, in other words, that the problem for ACOs is a scarcity of data or second rate analytics. Rather, the problem is that we are not taking advantage of, and using more intelligently, the data and analytics already in place, or nearly in place.
For those of you who are interested in the concept of Big Data, Steve Lohr recently wrote a good overview in his column in the New York Times, in which he said:
“Big Data is a shorthand label that typically means applying the tools of artificial intelligence, like machine learning, to vast new troves of data beyond that captured in standard databases. The new data sources include Web-browsing data trails, social network communications, sensor data and surveillance data.”
Applied to health care and ACOs, the proponents of Big Data suggest that some version of IBM’s now-famous Watson, teamed up with arrays of sensors and a very large clinical data repository containing virtually every known fact about all of the patients seen by the medical group, is a needed investment. Of course, many of these data are not currently available in structured, that is computable, format. So one of the costly requirements that Big Data may impose on us results from the need to convert large amounts of unstructured or poorly structured data to structured data. But when that is accomplished, so advocates tell us, Big Data is not only good for quality care, but is “absolutely essential” for attaining the cost efficiency needed by doctors and nurses to have a positive and money-making experience with accountable care shared-savings, gain-share, or risk contracts.
For the record: I am a geek. I love technology. I adopted EMR when all the cool kids were using paper. Instead of loitering in the “in” doctors lounge making eyes at the nurses, I was writing clinical content and making my care more efficient. I was getting “meaningful use” out of my EMR even when nobody paid me to do it.
But now who’s laughing? While they are slaving away trying to get their “meaningful use” checks, I’ve moved on to greener pastures, laughing at their sorry butts! It’s just like my mom promised it would be. Thanks mom.
Really, for the record, I am not so much a technology fan as a “systems” guy. I like finding the right tool for the job, building systems that make it easier to do what I want, and technology is perfect for that job. I am not so much a fan of technology, but what technology can do. Technology is not the goal, it is the best tool to reach many of my goals. There are two things that measure the effectiveness of a tool:
1. Is the tool the right one for the job?
2. Is the person using the tool properly?
So, when answering the question I posed at the end of my last post, what constitutes a “good” EMR, I have to use these criteria.
Every day CIOs are inundated with buzzword-compliant products – BYOD, Cloud, Instant Messaging, Software as a Service, and Social Networking.
In yesterday’s blog post, I suggested that we are about to enter the “post EHR” era in which the management of data gathered via EHRs will become more important than the clinical-facing functions within EHRs.
Today, I’ll add that we do need to a better job gathering data inside EHRs while at the same time reducing the burden on individual clinicians.
I suggest that BYOD, Cloud, Instant Messaging, Software as a Service and Social Networking can be combined to create “Social Documentation” for Healthcare.
In previous blogs, I’ve developed the core concepts of improving the structured and unstructured documentation we create in ambulatory and inpatient environments.
I define “social documentation” as team authored care plans, annotated event descriptions (ranging from acknowledging a test result to writing about the patient’s treatment progress), and process documentation (orders, alerts/reminders) sufficient to support care coordination, compliance/regulatory requirements, and billing.