Uncategorized

Letting the Data Flow, Part One

Making clinical data liquid permeated a series of events I attended last week during Health Innovation Week in San Francisco.  Monday and Tuesday found me at the HIE/REC conference. Wednesday was HealthCamp at Kaiser-Permanente’s Garfield Research Center (KP was extremely gracious in hosting this event and the opportunity to get a tour of the facilities prior to event kick-off was great). The week concluded with the annual and well-orchestrated Health 2.0 conference.

This first post will focus on the HIE/REC event as it was quite distinct from the other events: smaller audience, more staid, dominated by government officials and tied at the hip, for good and bad, to the existing healthcare system infrastructure.

The HIE/REC conference was an odd event with attendance hovering around 200 or so attendees.  The event was focused almost entirely on what the States are doing with the federal funds coming their way to establish Regional Extension Centers (RECs) whose main objective is to get priority primary care physicians (PPCPs) to adopt and meaningfully use a certified EHR. Now, having been to this event and heard many of the State REC initiatives that are now underway via this program, sad to say that my original opinion has not changed. Rather than picking preferred EHRs and assisting with deployment, these RECs may be better off just helping to these PPCPs understand exactly what the HITECH Act is, what are their options, what questions to ask of a vendor or service provider and leave it to EHR consultants and vendors to take it from there.

On the HIE front, there was the usual talk of building the HIE (this time on a Statewide level), soliciting community involvement and last but certainly not least, building a model for sustainability.  When one listens to these presentations from what are typically non-profit organizations, one can not help but be struck by the acute lack of just basic business sense with far too many messages that go along the lines of…

Think like a business, what is the value to end user and charge appropriately.

Yikes, if that is the best they can come up with, we’re in trouble.

In listening to the multitude of presentations over the course of those two days, one thing became abundantly clear, CMS and more broadly the feds want access to clinical data and they see HIEs as playing a critical role in getting that data to flow.  Tony Rodgers, Deputy Administrator at CMS said as much in his talk which outlined the current CMS strategy:

  1. ACOs are what CMS is backing long-term as CMS does not have much hope for broad adoption of EHRs by small practices/providers under MU.
  2. HIEs are seen as the aggregator of data for future quality assessments and gain insight on what is truly effective.
  3. CMS strongly believes we can not bring down costs with current organizational structure of the healthcare system – thus their support of new models, particularly ACOs and Patient-Centered Medical Home. Thus, CMS is looking to map payment reform to HIT adoption in such a way that it logically force the needed organizational changes in the healthcare system to bend the ever elusive cost curve.
  4. Ideal: Create what he Tony called the “Medical Home 3.0″ wherein the physician is fully connected at local, regional and national levels to those organizations and institutions that can deliver information at the point of care leading to better, more accurate diagnosis, treatment and ultimately lower costs.

These are fine ideals but how we get there is another story altogether.

The biggest concern may be the nearly complete and total lack of those from the business side of the healthcare spectrum present at this event. Sure, there were your sponsors, the usual mish-mash of HIT vendors, but nowhere did I see or hear presentations from organizations that have already established private, enterprise HIEs in their communities. This takes me back to a conversation I had with a large IDN in the midwest that had already worked with competing IDNs and community hospitals to establish a local, albeit private, HIE.  She had absolutely no desire to be a part of a statewide initiative that planned to charge her organization ~$50K/yr for something they already had (and likely far better than the one the State was planning).

And therein lies the rub: The need for data liquidity is apparent but if we do not address the core needs and issues at the community level and engaged healthcare business in the discussion, meetings such as this will be a lot of talk, but talk that is disconnected from the business of healthcare and thus of little relevance.

John Moore is an IT Analyst at Chilmark Research, where this post was first published.

Categories: Uncategorized

Tagged as: , , , ,

3 replies »

  1. this stuff is all so stupid. no one is making a difference in healthcare from this blog site – let alone john “i schill for cash and not knowledge” moore.
    please. get some real thoughts here and stop wasting storage space.

  2. I know others have said this before, but we should probably think of the NHIN and HIEs like the interstate system. It is in the public interest to keep the data flowing, but it is not sufficiently in the interest of the players who have the data to pay for the flow (they have done a great job gobbling up 17% of GDP without it).
    So, at least for now, massively subsidize the data flow and put CMS carrots and sticks in place to get parties to get their data flowing. Once that is done, and organizations have been rebuilt to rely on this data exchange to enhance care and improve efficiency, then you can look at charging for it.

  3. Medical Home 3.0 should have the patient (with their own data) at the center. Everyone who generates and uses the data (including physician PCMH providers) should be in the periphery.
    Any single provider or group will never be the sole “medical home” for a patient over the course of their life, there will be many providers/groups assuming this role from time to time.
    The patient and their data (under the patient’s control) should be at the center.