The future of patient identification
We believe that healthcare needs a major shift to solve the problem of misidentification
GPII is an active member of the Patient ID Now coalition and has participated in the working group that helped develop the "Framework for a National Strategy on Patient Identity". The primary goal of that exercise is to eliminate errors in patient matching. You can access the framework at this link: Patient ID Now Framework (ahima.org).
Currently, the Patient ID Now coalition is focused on work needed to convince Congress to repeal the federal prohibition contained in section 510 of the labor - HHS appropriations bill. GPII is looking beyond that to a plan for the future; see our summary paper, Solving the Patient ID Now Puzzle.
GPII has started a blog to engage the industry in a discussion about patient identification. We believe the problem and cost of patient misidentification is not well understood and the complexity of the solution is generally underestimated. Join us in this discussion and add your comments at Patient Identification at Wordpress
See also the first in a series of papers on patient identification: Designing a Durable Patient Identification Solution for Healthcare
Our sole focus is to provide cloud-based services to the healthcare industry to accurately link healthcare records. This is absolutely essential if we are to achieve the benefits of interoperability. GPII makes available a unique data element, a <prTag> that offers the following benefits:
We contend that enabling accurate sharing of clinical information will result in improved patient care and reduced costs. The simplicity of the <prTag> approach ensures that interoperability is both safe and cost effective.
Any solution to accurately match healthcare records must respect the privacy rights of the patient. <prTags> are designed specifically to address all of the requirements noted above.
Each of the requirements described in this document must be considered in the design of a national healthcare identification system. We maintain that these requirements must be addressed regardless of what implementation strategy is cho