Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Paul Cerrato

Paul Cerrato

Editor, InformationWeek Healthcare

Grow Your Own Health Information Exchange

While many healthcare organizations turn to private vendors to set up HIEs, others get good results by building their own.

Telemedicine Tools That Are Transforming Healthcare
Telemedicine Tools That Are Transforming Healthcare
(click image for larger view and for slideshow)
Once upon a time, many health IT stakeholders hoped to develop a massive, public health information exchange (HIE) that would eventually let hospitals and practices share patient data nationwide. That hope is beginning to look more like a pipe dream.

A recent report from Chilmark Research for instance, shows that while the HIE market grew more than 40% in the past year, most of that growth came in privately sponsored, enterprise health information exchanges, rather than in public health information exchanges that seek to connect providers across regions and states.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Chilmark CEO John Moore offered his take on the growth in private HIEs in a recent InformationWeek Healthcare interview: "Everybody realizes they're going to have to tie their systems together with their affiliates if they're going to have any hope of surviving payment reform."

The main reasons for the rapid health information exchange growth, according to Chilmark, are the Meaningful Use criteria that will require interoperability between systems as patients are moved from one care setting to another, and the impending changes in reimbursement methods that will necessitate greater care coordination.

[ Most of the largest healthcare data security and privacy breaches have involved lost or stolen mobile computing devices. For possible solutions, see 7 Tools To Tighten Healthcare Data Security. ]

While public health information exchanges could help providers meet these challenges, healthcare organizations tend to approach information exchange in the context of their own positions in the marketplace. In addition, many don't want to wait for public health information exchanges to reach their areas. So it's not surprising that the bulk of health information exchange growth is now in the private sector.

However while many providers are turning to HIE vendors, some are taking a grassroots approach, cooking up their own brands of information exchange. One example of this build-your-own model is Huntington Memorial Hospital in Pasadena, Calif., a 625-bed facility that works with about 3,000 physicians in 1,500 practices.

Most of the physicians affiliated with the hospital have electronic health record (EHR) systems, but few have fully optimized their use. Rebecca Armato, executive director of physician and interoperability services at Huntington, says her goal is to help them fully use these systems by creating what she calls a "connected, collaborative care community."

The Huntington HIE connects the hospital and the community of private medical practices. It selectively pushes patient data back and forth among providers. It sends data about a patient's hospital stay or hospital-based outpatient clinic visit, for instance, into a physician portal, and to a community physician's EHR system, depending on each clinician's needs.

One of the keys to convincing community physicians of the value of the HIE is to show them that the exchange won't disrupt their workflow or overwhelm them with a barrage of data, said Joel Diamond, MD, at this year's HIMSS national conference in Las Vegas. Diamond is a partner at Handelsman Family Practice and chief medical officer for dbMotion, a vendor that provides an interoperability platform capable of integrating patient data across various IT applications.

That education process involved seven seminars in 2010 and 2011, hands-on training at the hospital's "physician innovation center," and training in individual physician's offices to explain how to use various software and hardware tools.

As Armato and Diamond explained in their HIMSS12 presentation, the HIE generates four interacting screens for clinicians to work with.

First there's a virtual patient record, which contains vital data on each patient. Second, it's viewable within the hospital's EHR (Huntington is currently a Meditech shop but will soon switch to Cerner). The third component in the HIE is the community doctor's office EMR, and finally there's the collaborative care portal.

The portal is the "game changer" for doctors, said Diamond, because it lets clinicians in diverse practice settings see summaries of all their patients' hospital care by date and then drill down to see, in real time, the specific care they're getting.

So if Dr. Jones is about to see Mr. Smith in her office, she can log onto the collaborative care portal to find out that he had a CT scan while he was in the hospital a week ago and that he was referred to Dr. Silver for a pulmonary consult that took place two days earlier. The portal also serves as a communication tool among physicians, giving them the ability to create new referrals or send quick notes to other members of the care team without disrupting their workflows.

Armato said she's received lots of positive feedback from physicians using this homegrown HIE, including comments about how it's saving them time and money normally expended on mail and faxes to other providers. Others appreciate the fact that the system has sped up the admission process, improved communication among clinicians, and made billing quicker.

While many policymakers continue to work toward that holy grail of a national HIE, hospitals like Huntington Memorial deserve a round of applause for making information exchange a reality in their communities.

Get the new, all-digital Healthcare CIO 25 issue of InformationWeek Healthcare. It's our second annual honor roll of the health IT leaders driving healthcare's transformation. (Free registration required.)



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.