Like most states, Arizona is in a transition period in terms of health IT initiatives. It has made great progress in EHR adoption (80 percent) and has a statewide health information exchange with a sustainable business model that includes funding from both hospitals and payers. But as federal grant funding for HIE and regional extension center outreach work subsides, Arizona is shifting gears to focus on reaching more providers and expanding the types of services the HIE offers.
The Arizona Strategic Enterprise Technology Office funded the creation of the recently published Health IT Roadmap 2.0, which received input from more than 300 stakeholders and describes 19 key initiatives to advance HIT/HIE in Arizona. This morning I had the chance to speak with Arizona Health-e Connection CEO Melissa Kotrys about a few of those initiatives.
The first one that caught my eye was the study of a statewide unique patient identifier. Last fall I saw a debate at the AMIA conference in Washington, D.C., about whether AMIA should advocate for a unique health identifier for care and research purposes and if so, what kind of standard should it support under what conditions? There were strong feelings on both sides. An audience poll following the debate seemed to suggest that a majority wanted AMIA to advocate a unique health identifier, but there was widespread recognition that political headwinds continue to make consensus on the right direction unlikely.
I mentioned that meeting to Kotyrs, and she agreed with my description of it as a political hot potato. “It is a controversial issue,” she said, “but when we convened stakeholders to talk about key issues, this topic of the difficulty of patient identification came up, even with master patient index solutions. So there was enough interest to explore this topic further.”
According to the Arizona Health IT Roadmap 2.0 document, the lack of a unique identifier for every patient causes difficulty in ensuring that: 1) patient records are always matched to the correct patient and 2) all records belonging to a patient are identified and associated with the patient. As the number of patients and the number of organizations participating in HIE grows, the complexity of correct patient record matching is magnified.”
Arizona plans to explore best practices and identify alternative approaches it can use to address the increasing complexity of correctly matching patients to all of their available records across multiple organizations.
Another change Kotrys mentioned was that during the course of developing the roadmap, AzHeC tightened its affiliation with the statewide HIE organization, the Health Information Network of Arizona (HINAz). AzHeC will continue to serve as the multi-stakeholder organization that handles policy development, education, stakeholder engagement and various HIT/HIE programs such as the Arizona Regional Extension Center, while HINAz will serve as the “network” under the AzHeC umbrella that connects providers through the statewide HIE.
Here are a few other interesting initiatives on Arizona’s to-do list:
An HIE Consent Management Engine: This would develop a technical infrastructure to support the common statewide patient consent approach and processes. The consent management engine should be able to:
• Manage consent from multiple sources (providers, HIEs, and patient-generated sources)
Also On Healthcare-Informatics...
Get the latest information on Meaningful Use, and attend other valuable sessions at this two-day, intimate event bringing together C-level, physician, practice management and IT decision makers for strategy discussions, knowledge exchange, and one-on-one meetings.