{"type":"data","nodes":[{"type":"data","data":[{"mainNavPagesCollection":1,"subnavPagesCollection":26},{"currentSlug":2,"topLevelSlug":-1,"total":3,"items":4},"unique-patient-identifier-is-critical-to-improve-patient-matching",6,[5,8,11,14,17,20,23],{"title":6,"slug":7},"Home","",{"title":9,"slug":10},"About GPII","about-gpii",{"title":12,"slug":13},"Why the Need?","why-the-need",{"title":15,"slug":16},"Our Services ","our-services",{"title":18,"slug":19},"Privacy Protection","privacy-protection",{"title":21,"slug":22},"Contact Us","contact-us",{"title":24,"slug":25},"Articles","articles",{"currentSlug":2,"total":27,"items":28},0,[]],"uses":{"params":["slug"]}},{"type":"data","data":[{"title":1,"sanitizedBodyMarkup":2,"published":3,"author":4,"category":7,"tagsCollection":10,"pdf":20,"link":22}," Unique Patient Identifier is Critical to Improve Patient Matching","\u003Cp>In a recent HIStalk article entitled “National Patient Identifier: Why Patient Matching Technology May Be\na Better Solution,” Vicki Wheatley argues that, “… healthcare organizations should instead focus on\nstrengthening their existing enterprise matching strategies” rather than work to implement a national\npatient identifier (NPI). The article makes several valid points that contribute to the ongoing debate\nabout an NPI:\u003C/p>\u003Cul>\u003Cli>\u003Cp>No solution, including an NPI, can solve all patient matching problems.\u003C/p>\u003C/li>\u003Cli>\u003Cp>Patient matching errors and healthcare fraud will continue to require special attention.\u003C/p>\u003C/li>\u003Cli>\u003Cp>Accurate tracking of an individual’s information across healthcare silos is becoming increasingly\nimportant.\u003C/p>\u003C/li>\u003Cli>\u003Cp>Any proposed patient matching solutions must not negatively influence privacy, security, or\nclinical outcomes.\u003C/p>\u003C/li>\u003Cli>\u003Cp>Accurate patient matching is essential for activities ranging from clinical care to healthcare\nanalytics to population health management.\u003C/p>\u003C/li>\u003C/ul>\u003Cp>In these and several other areas, Ms. Wheatley’s article makes a valid contribution to the ongoing\ndebate concerning a national unique patient identifier.\n\u003C/p>\u003Cp>There were a few areas, however, where we have a somewhat different viewpoint. The first of these is\nthe implied assumption that healthcare organizations must make a choice between having an EMPI and\nhaving a national patient identifier. We believe that this is a false dichotomy.\u003C/p>\u003Cp>Clearly, healthcare organizations must continue to improve their existing EMPI systems as much as\npossible. However, years of analysis and experience indicate that this will not allow them to achieve the\nlevels of patient matching accuracy that are being required going forward. Those requirements include\nidentification of individuals across disparate healthcare systems, the need for matching against ever-\nincreasing patient populations, and the fact that patient demographic data has known variability and\nambiguities.\u003C/p>\u003Cp>These represent just three of the reasons why unassisted EMPI demographic matching cannot represent\nthe sole patient matching strategy. Rather, the EMPI approach will need to be supplemented by\ntechniques such as the use of an NPI, biometrics, digital certificates, and other technologies.\nVirtually every EMPI system uses a patient’s Social Security number as a data element to improve the\nperformance of their demographic matching algorithm. I was puzzled by the statement, “… even in\ntheory, every single potential patient in the country would need to be assigned one…” as a condition for\nan NPI to work. Ms. Wheatley acknowledges that there are many people in the US who require\nhealthcare but do not have an SSN. Despite this deficiency, the use of the SSN clearly adds value in those\nsituations where it is accurately available. Similarly, an NPI would benefit each patient who chooses to\nuse one.\u003C/p>\u003Cp>An important point to keep in mind is that there is no mechanism to check for data entry errors in most\nof the data elements currently used for demographic matching. This includes the SSN, names, and\naddresses. For example, there is no reliable way to detect transposition of digits when a SSN is manually\nentered. Nor is there an easy way to automate the capture of a patient’s SSN.\u003C/p>\u003Cp>Contrast that with a well-designed national patient identifier system. In most situations, the NPI would\nbe read using automated technology such as a barcode reader or a smart chip that would virtually\neliminate errors. Even when the NPI is manually entered, embedded check digits can ensure that any\ndata entry errors are immediately detected and the operator is prompted to re-enter the NPI. When\nadded to a person’s demographic profile, the NPI thus becomes the single demographic element that\ncan lead to accurate patient identification on its own. These proposals represent a major advance from\nthe current situation – i.e., an 8 percent or more error rate in EMPI matches.\u003C/p>\u003Cp>It is very clear that healthcare organizations will continue their use of EMPI systems for the foreseeable\nfuture. That fact, however, should not blind us to the reality that these EMPI systems need to be\naugmented by additional capabilities going forward if they are going to meet the patient matching\naccuracy needs that are emerging in healthcare.\u003C/p>\u003Cp>The use of a national patient identifier, even if it is initially only chosen by a subset of providers (or\npatients, on a voluntary basis), will enhance the patient matching accuracy for those patients and help\navoid the medical errors that are associated with patient matching errors.\u003C/p>","2014-03-12T00:00:00.000Z",{"firstName":5,"lastName":6},"Barry","Hieb",{"slug":8,"title":9},"patient-matching","Patient Matching",{"total":11,"items":12},3,[13,15,17],{"slug":8,"title":14},"patient matching",{"slug":16,"title":16},"identifier",{"slug":18,"title":19},"unique-identifier","unique identifier",{"title":21,"url":21},"",{"title":21,"url":21}],"uses":{"params":["slug"]}}]}
