On Nov 14, the HIT Policy Committee sent recommendations to the HIT Standards Committee on three key areas for future EHR capability: query for a patient record, provider directory management, and data portability and migration. An article on the recommendations can be found here.
These recommendations were the result of many months of deliberation by the Information Exchange Working Group, of which I have the privilege of being Chair. These three functional capabilities are very important because they address key needs important to health care delivery but that won't be adequately met by the market on its own.
query for a patient record
Meaningful use has approached interoperability in a deliberate and methodical fashion. Stage 1 focused on adoption of EHRs, and routinizing use of HIE capabilities that already existed in the market (primarily eprescribing and lab results delivery). Stage 2 took it one step further to move the market to adoption of "push" capabilities among providers and between providers and patients. The new recommendation on "query" takes the final step to enabling "pull" or "query" functions among providers. While it will still take many years for the market to create business practices and infrastructure to support seamless inter-connectivity among all providers and patients, the "query" requirement will make EHRs finally fully capable of being the building blocks of that larger interoperability vision.
This is mostly a "clean-up" recommendation from Stage 2. As the HISP market starts to take shape based on the Direct requirements of Stage 2 MU, a clear obstacle to more seamless integration of HISPs is the lack of standards for provider directory transactions -- being able to look up a provider and his/her security credentials from one system to another. This recommendation will enable one EHR system to discover a provider, their routing address, and their security credentials, and will also enable EHR systems (or standalone provider directories) to respond to such electronic provider directory searches.
data portability and migration
I personally know of someone whose doctor changed EHR systems only to
find that the medical records got matched to the wrong patients during
the migration. Imagine the disastrous consequences that could result from such errors! Current market predictions are that 20-30% of providers will be changing their EHR systems in the next few years, for a variety of reasons. Data migration -- the ability to transfer data from one EHR to another -- will thus become an increasingly important issue in the market. As EHR systems and EHR users enhance their ability to apply quality and decision support tools to clinical data, there are important safety and quality risks to having incomplete and/or error-filled data migrations from one system to another. Data portability refers to the transfer of data from one EHR system to another to support a patient's desire to change physicians, for example. It is similar in many ways to the data migration need which is why we included this use case in our recommendation.
There is a balance that needs to be struck between the scope and specificity of government regulation, on the one hand, and the strong desire and need for market flexibility and innovation. We already have examples of where this can go awry. I believe that these recommendations are judicious in covering only areas that are important to society and that also won't get fixed by the market on its own.