Healthcare // Analytics
News
9/12/2013
09:49 AM
Connect Directly
RSS
E-Mail
50%
50%

ONC Partners Tackle Patient-Data Matching Problem

ONC leads public-private coalition working on a key interoperability challenge: how to match unique patients to their personal data as it moves across the healthcare system.

10 Mobile Health Apps From Uncle Sam
10 Mobile Health Apps From Uncle Sam
(click image for larger view and for slideshow)
The Office of the National Coordinator for Health IT (ONC) has launched a national, public-private initiative to tackle one of the most serious barriers to the advancement of health information exchange (HIE): uniquely matching a patient to the healthcare data about that patient.

"By identifying and recommending standardization of the basic attributes most commonly used for patient matching, we are looking to improve patient safety, care coordination and efficiency," wrote Lee Stevens, policy director of ONC's State HIE program, on the office's HealthIT Buzz blog. ONC is part of the Department of Health and Human Services (HHS).

According to Stevens, the new project will focus on two specific objectives:

-- Identifying the common attributes that achieve high positive match rates across disparate systems. The attributes may include common fields such as name, date of birth, address, sex, cellphone number and new criteria such as emergency contact and insurer.

-- Defining the processes and best practices that are most effective to support high positive patient matching rates utilizing these attributes.

[ What steps should hospitals take to more effectively share data with other healthcare organizations? See Most Hospitals Exchange Data, But Scope Too Limited. ]

Among ONC's partners in the patient matching initiative are the Federal Health Architecture, which includes more than 20 federal agencies; the College of Health Information Management Executives (CHIME); the Health Information Management and Systems Society (HIMSS); the Bipartisan Policy Center; Healtheway, which manages the eHealth Exchange, the successor to the National Health Information Network; the EHR/HIE Interoperability Work Group, which includes 19 states as well as electronic health record and HIE vendors; many large integrated delivery networks; and statewide and local HIEs.

After conducting "environmental scans and literature reviews," the participants will submit a report to the National Coordinator of Health IT by the end of the year.

CHIME applauded ONC's action to improve patient-data matching. "Despite years of development, no clear strategy has emerged to accurately and consistently match patient data," said CHIME president and CEO Russell Branzell in a statement. "As we advance interoperability and health information exchange, we are delighted to see ONC take action to ensure the right data is matched with the right patient. This is a necessary, concrete step to bolster patient safety."

It can also help healthcare organizations show Meaningful Use. As CHIME pointed out, the government has required health information exchange in its EHR incentive program, "but has not provided ... guidance on how organizations ought to approach patient-data matching."

In an interview with InformationWeek Healthcare, Branzell said that CHIME told ONC and the Centers for Medicare and Medicaid Services (CMS) several months ago that the most important thing the government could do to accelerate the impact of health IT on improving outcomes was to improve the accuracy of patient matching.

"We feel good that they listened and we commend ONC and CMS for that. But that just means we've come to the starting line, and we have a lot of work ahead of us."

The biggest obstacle, he said, is that "there are no clear accepted standards" for patient matching. Every statewide and regional HIE, every healthcare organization, and every physician practice has different patient identifiers and methods for documenting demographic information, he said.

He attributed part of this problem to the multiplicity of EHRs, which have different systems for identifying patients. The EHR vendors view this as an "outside issue" that is up to each organization to solve when they try to exchange data with providers that use different systems, he said.

National standards that all vendors would have to adopt -- such as a universal method for recording date of birth or a way to correct wrong addresses -- could go a long way toward solving this problem, he said.

CHIME doesn't have a position on a national patient identifier, Branzell said, but this is a dead issue because Congress has consistently blocked it. Government agencies such as Medicare and Tricare use Social Security numbers as identifiers, but that would be unacceptable in the rest of healthcare, he said. Still, he added, a consistent method must be found to match patients across public and private entities.

A basic assumption of ONC's approach is that healthcare providers can apply best practices that are already being used elsewhere to improve patient matching. "We hope there are standards and best practices out there that we can replicate in a meaningful way," Branzell said.

There are some organizations, including the Indiana and Delaware HIEs, that have found ways to match patients with great accuracy, he noted. In addition, the Care Connectivity Consortium, which includes Geisinger Health System, Kaiser Permanente, Mayo Clinic, Intermountain Healthcare and Group Health Cooperative, has spent a lot of time and money on the patient matching issue, he pointed out.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
jaysimmons
50%
50%
jaysimmons,
User Rank: Apprentice
9/17/2013 | 8:57:36 PM
re: ONC Partners Tackle Patient-Data Matching Problem
I think its more the taboo associated with using the SSN for any other identification purposes other than government based. I dont really see what the big deal is as the SSN would be present in the demographic information anyways. I just dont see the general public agreeing with using their SSN.

Jay Simmons
Information Week Contributor
David F. Carr
50%
50%
David F. Carr,
User Rank: Author
9/13/2013 | 12:49:09 AM
re: ONC Partners Tackle Patient-Data Matching Problem
Is there really a good reason for not using the SSN, or maybe some hash based on the SSN? Don't all the source systems contain that data point anyway? Seems like we go to irrational lengths to avoid using the obvious choice. In the era of identity theft, we're all sensitive to the protection of that number, but it seems to me the problem lies in other systems that treat SSN as a reliable proxy for identity in ways that they shouldn't. This is an example of where it ought to be able to serve its purpose as a unique key.
Big Love for Big Data? The Remedy for Healthcare Quality Improvements
Big Love for Big Data? The Remedy for Healthcare Quality Improvements
Healthcare data is nothing new, but yet, why do healthcare improvements from quantifiable data seem almost rare today? Healthcare administrators have a wealth of data accessible to them but aren't sure how much of that data is usable or even correct.
Register for InformationWeek Newsletters
White Papers
Current Issue
InformationWeek Must Reads Oct. 21, 2014
InformationWeek's new Must Reads is a compendium of our best recent coverage of digital strategy. Learn why you should learn to embrace DevOps, how to avoid roadblocks for digital projects, what the five steps to API management are, and more.
Video
Slideshows
Twitter Feed
InformationWeek Radio
Archived InformationWeek Radio
A roundup of the top stories and trends on InformationWeek.com
Sponsored Live Streaming Video
Everything You've Been Told About Mobility Is Wrong
Attend this video symposium with Sean Wisdom, Global Director of Mobility Solutions, and learn about how you can harness powerful new products to mobilize your business potential.