At this year’s HIMSS conference in Orlando, the University of Maryland’s Center for Health Information and Decision Systems released and presented a framework to assist folks in developing and assessing sustainable health information exchange networks, the “CHIDS Evaluation Framework for Sustainable Health Information Exchange”.
The framework is based on interviews, environmental scans, user surveys, and benchmarking. Interestingly, they benchmarked HealthBridge, Michiana Health Information Network (MHIN), and Delaware’s network, DHIN - these HIEs are supported by either participant subscription fees or “legislated contribution”, in DHIN’s case. I like a couple of success factors they pointed out about the benchmarked networks:
- Look for quick wins
- Align incentives with the community and avoid competing with it
- Be flexible and offer access mechanisms for everyone, regardless of their technical prowess
- “Push system has a clearer value proposition than a pull system”
- No matter what folks think, don’t count on payors for operational funding
- Assemble a broad stakeholder group
They go on to define what I would call a Golden Rule for HIE sustainability: a RHIO should work with stakeholders to identify valuable services, deliver those services, and charge a fair fee for those who use the services; sustainability is reached when folks receive value, pay for that value, and the fees cover HIE costs.
That seems really simple, but it is something missing from far too many public HIE efforts.
Whether you look at a region, a state, or even some of the nationwide exchanges as examples, the perceived value delivered does not add up to the cost to deliver those services. So where are things going wrong?
I’ll describe two issues that I think effect why public HIEs cannot generate enough demand for their service or their service doesn’t yield value, and thus they care unable to generate the revenue to achieve sustainability: Collaboration and Generating Real Value.
Collaboration is hard. In healthcare we are all driven by elements of the Hippocratic oath, whether we are physicians or not. We need to do the right thing for patients, improve health and the delivery of healthcare, and help control healthcare spending for the health of our economy. Many folks get around the table as “RHIO Stakeholders” with these holistic thoughts in mind and devise ways to share data, share services, and setup structures for the common good. But then all too often people go back to their “day jobs”, where they run their healthcare businesses, compete in their local market, and make tough decisions. When these worlds collide and can lead to Clobber-ation, not collaboration. These undercurrents undermine progress at the community level, maybe deliberately or through indecision, absence, or some other indirect action, whether motivated by politics, competition, or plain old money.
Sounds evil and sinister, right? But as providers of all sizes jockey for their piece of the pie, these things do happen. “Should I share data with my competitor, when in my day job I’m figuring out how to set up an accountable care organization?”
Generating Real Value is another problem. Real Value can’t be determined in a RHIO Board meeting. Real Value depends on things like end-user experience, service quality, data availability, and education. The DC RHIO report mentions the classic emergency department use case: the ED doc who expends precious moments during her work routine, logging into a RHIO application, looking for patient records, only to find that most of the time there are no records in the system – a catch-22 for HIEs that struggle with limited investment, limited participation, or who take the overly cautious path of phased implementations that choke the flow of useful data (clobber-ation in action!).
I encourage you to check out the framework. It was immediately put to work assessing our Capitol’s DC Regional Health Information Organization (RHIO).
DC’s RHIO started in 2007 and has been focused on hospitals and safety net providers. According to the report, after 3 years and $6M in public funds, only two hospitals and six clinics have gone live on their Microsoft Amalga platform. It faces staggering operational expense, with costs running between $3.4M and nearly $5M per year to run it.
What about Private HIEs?
The CHID HIE assessment framework is 100% oriented towards public HIEs. They focus on Governance, Community Engagement, Public Trust, and Technology.
Given MobileMD’s near-exclusive focus on the private/enterprise HIE market, I don’t believe Governance, Community Engagement or to a large degree Public Trust are relevant to our space. It is the fact that we have simplified, single-party Governance that makes our sustainability and adoption seemingly “natural” in our implementations. Public Trust in our world is driven by the discrete patient-provider relationship that we understand and manage to; again, not a factor that impacts adoption in an enterprise-focused network.
As for Technology, our cloud-based deployment, zero footprint, and “100% service” approach means nobody on the client side needs to know about or implement our technology. So again, we’ve removed the roadblocks and stumbling points.
So, I guess we validate that the framework correctly targets the key points that cause community HIEs to falter. We firmly agree that they bring to light the underlying issues impacting both adoption and sustainability of an HIE. MobileMD has built our 4D HIE solution, established our deployment approach, and selected our target market in such a way as to naturally mitigate most of these concerns.
What To Do?
Here’s our take: Rather that build public community HIEs in phases or baby steps that constrain data, limit participation, and suffer from clobber-ation, start the effort with privately focused enterprise HIEs. Deployed in alignment with health system or practice group business lines, these HIEs thrive given their close alignment with a business-oriented community of physicians, a natural patient flow, and in the spirit of competition. Connect these private HIEs by weaving an HIE fabric that spans an entire geography; use NwHIN CONNECT and Direct as the thread that pulls them together. This fabric accomplishes two things at once: it meets the internal business needs of an enterprise (think ACO, quality programs, and management of payment bundling and re-admit rates), and it provides information exchange across the community to improve outcomes and population health. Truly Competition Before Cooperation.
What do you think? Leave a comment!
Posted by Chris Voigt 
