Enterprise master patient index

Last updated

An enterprise master patient index or enterprise-wide master patient index (EMPI) is a patient database used by healthcare organizations to maintain accurate medical data across its various departments. Patients are assigned a unique identifier, so they are represented only once across all the organization's systems. [1] Patient data can include name; gender; date of birth; race and ethnicity; social security number; current address and contact information; insurance information; current diagnoses; and most recent date of hospital admission and discharge (if applicable).

Contents

EMPIs are intended to ensure patient data is correct and consistent throughout the organization regardless of which system is being updated. Non-healthcare organizations also face similar issues maintaining customer records across different departments.

Many software vendors use EMPI and MPI (master patient index) synonymously, because an MPI is only workable if it is used by all software applications across an entire enterprise; that is, "master" implies enterprise-wide scope. [2]

EMPIs use match engines along with the technique of referential matching to more easily identify duplicate patient records.

Overview

In computing, an enterprise[-wide] master patient index is a form of customer data integration (CDI) specific to the healthcare industry. Healthcare organizations and groups use EMPI to identify, match, merge, de-duplicate, and cleanse patient records to create a master index that may be used to obtain a complete and single view of a patient. The EMPI will create a unique identifier for each patient and maintain a mapping to the identifiers used in each records' respective system.

An EMPI will typically provide an application programming interface (API) for searching and querying the index to find patients and the pointers to their identifiers and records in the respective systems. It may also store some subset of the attributes for the patient so that it may be queried as an authoritative source of the "single most accurate record" or "source of truth" for the patient. Registration or other practice management applications may interact with the index when admitting new patients to have the single best record from the start, or may have the records indexed at a later time.

An EMPI may additionally work with or include enterprise application integration (EAI) capabilities to update the originating source systems of the patient records with the cleansed and authoritative data.

Even the best tuned EMPI will not be 100% accurate. Thus an EMPI will provide a data stewardship interface for reviewing the match engine results, handling records for which the engine does not definitively determine a match or not. This interface will provide for performing search, merge, unmerge, edit and numerous other operations. This interface may also be used to monitor the performance of the match engine and perform periodic audits on the quality of the data.

EMPI can be used by organizations such as hospitals, medical centers, outpatient clinics, physician offices and rehabilitation facilities.

Match engine

A component of an EMPI is the match engine, the method by which different records can be identified as being for the same patient. [3] A match engine may be deterministic, probabilistic, or naturalistic. [4] [5] The match engine must be configured and tuned for each implementation to minimize false matches and unmatches. The accuracy and performance of the match engine are a big factor in determining the value and ROI for an EMPI solution.

The attributes a match engine is configured to use can typically include name, date of birth, sex, social security number, and address. The match engine must be able to give consideration to data challenges such as typos, misspellings, transpositions and aliases. [6]

Referential matching

Referential matching involves taking third party patient demographic data containing unique identifiers and using it to better match patient records. Rather than compare incomplete records with each other to try to match them, the organization would compare each incomplete record with a more comprehensive referential database. This works across multiple organizations as long as they all use the same referential list of demographic data formatted the same way. Putting the EMPI on the cloud is one technique to ensure uniformity of the match engine. [7] In 2018, Pennsylvania-based NGO The Pew Charitable Trusts identified referential matching using third party patient data as a good way to improve patient matching. [8]

Key benefits

Correctly matching patient records from disparate systems and different organizations provides a more complete view of a patient. Additional benefits include:

Related Research Articles

Health informatics Applications of information processing concepts and machinery in medicine

Health informatics is the field of science and engineering that aims at developing methods and technologies for the acquisition, processing, and study of patient data, which can come from different sources and modalities, such as electronic health records, diagnostic test results, medical scans. The health domain provides an extremely wide variety of problems that can be tackled using computational techniques.

Health Level Seven or HL7 refers to a set of international standards for transfer of clinical and administrative data between software applications used by various healthcare providers. These standards focus on the application layer, which is "layer 7" in the OSI model. The HL7 standards are produced by Health Level Seven International, an international standards organization, and are adopted by other standards issuing bodies such as American National Standards Institute and International Organization for Standardization.

Record linkage is the task of finding records in a data set that refer to the same entity across different data sources. Record linkage is necessary when joining different data sets based on entities that may or may not share a common identifier, which may be due to differences in record shape, storage location, or curator style or preference. A data set that has undergone RL-oriented reconciliation may be referred to as being cross-linked. Record linkage is referred to as data linkage in many jurisdictions, but the two are the same process.

Electronic health record Digital collection of patient and population electronically stored health information

An electronic health record (EHR) is the systematized collection of patient and population electronically stored health information in a digital format. These records can be shared across different health care settings. Records are shared through network-connected, enterprise-wide information systems or other information networks and exchanges. EHRs may include a range of data, including demographics, medical history, medication and allergies, immunization status, laboratory test results, radiology images, vital signs, personal statistics like age and weight, and billing information.

Entity–attribute–value model (EAV) is a data model to encode, in a space-efficient manner, entities where the number of attributes that can be used to describe them is potentially vast, but the number that will actually apply to a given entity is relatively modest. Such entities correspond to the mathematical notion of a sparse matrix.

Health information management (HIM) is information management applied to health and health care. It is the practice of analyzing and protecting digital and traditional medical information vital to providing quality patient care. With the widespread computerization of health records, traditional (paper-based) records are being replaced with electronic health records (EHRs). The tools of health informatics and health information technology are continually improving to bring greater efficiency to information management in the health care sector. Both hospital information systems and Human Resource for Health Information Systems (HRHISs) are common implementations of HIM.

In information science and information technology, single source of truth (SSOT) architecture, or single point of truth (SPOT) architecture, for information systems is the practice of structuring information models and associated data schemas such that every data element is mastered in only one place, providing data normalization to a canonical form. Any possible linkages to this data element are by reference only. Because all other locations of the data just refer back to the primary "source of truth" location, updates to the data element in the primary location propagate to the entire system, providing multiple advantages simultaneously: greater efficiency/productivity, easy prevention of mistaken inconsistencies, and greatly simplified version control. Without SSOT architecture, rampant forking impairs clarity and productivity, imposing laborious maintenance needs.

MEDCIN, a system of standardized medical terminology, is a proprietary medical vocabulary and was developed by Medicomp Systems, Inc. MEDCIN is a point-of-care terminology, intended for use in Electronic Health Record (EHR) systems, and it includes over 280,000 clinical data elements encompassing symptoms, history, physical examination, tests, diagnoses and therapy. This clinical vocabulary contains over 38 years of research and development as well as the capability to cross map to leading codification systems such as SNOMED CT, CPT, ICD-9-CM/ICD-10-CM, DSM, LOINC, CDT, CVX, and the Clinical Care Classification (CCC) System for nursing and allied health.

Enterprise search is the practice of making content from multiple enterprise-type sources, such as databases and intranets, searchable to a defined audience.

Microsoft SQL Server is a relational database management system developed by Microsoft. As a database server, it is a software product with the primary function of storing and retrieving data as requested by other software applications—which may run either on the same computer or on another computer across a network. Microsoft markets at least a dozen different editions of Microsoft SQL Server, aimed at different audiences and for workloads ranging from small single-machine applications to large Internet-facing applications with many concurrent users.

Patient portals are healthcare-related online applications that allow patients to interact and communicate with their healthcare providers, such as physicians and hospitals. Typically, portal services are available on the Internet at all hours of the day and night. Some patient portal applications exist as stand-alone web sites and sell their services to healthcare providers. Other portal applications are integrated into the existing web site of a healthcare provider. Still others are modules added onto an existing electronic medical record (EMR) system. What all of these services share is the ability of patients to interact with their medical information via the Internet. Currently, the lines between an EMR, a personal health record, and a patient portal are blurring. For example, Intuit Health and Microsoft HealthVault describe themselves as personal health records (PHRs), but they can interface with EMRs and communicate through the Continuity of Care Record standard, displaying patient data on the Internet so it can be viewed through a patient portal.

Health information technology (HIT) is health technology, particularly information technology, applied to health and health care. It supports health information management across computerized systems and the secure exchange of health information between consumers, providers, payers, and quality monitors. Based on an often-cited 2008 report on a small series of studies conducted at four sites that provide ambulatory care – three U.S. medical centers and one in the Netherlands – the use of electronic health records (EHRs) was viewed as the most promising tool for improving the overall quality, safety and efficiency of the health delivery system. According to a 2006 report by the Agency for Healthcare Research and Quality, in an ideal world, broad and consistent utilization of HIT would:

VistA

The Veterans Health Information Systems and Technology Architecture (VISTA) is a health information system deployed across all veteran care sites in the United States. VISTA provides clinical, administrative, and financial functions for all of the 1700+ hospitals and clinics of the Veterans Health Administration VISTA consists of 180 clinical, financial, and administrative applications integrated within a single transactional database.

Informatics Corporation of America (ICA) is a privately held health information technology organization headquartered in Nashville, Tennessee. It serves integrated delivery systems (IDNs), health information exchanges (HIEs), individual hospitals, Independent Practice Associations (IPAs) and Regional Health Information Systems (RHIOs). In 2000, some of Vanderbilt University Medical Center's (VUMC) practicing physicians teamed with informatics professionals to develop two complementary software applications—dubbed StarChart and StarPanel—to aggregate and organize medical data, and to improve communication and clinical decision-making within a single interface. This technology has allowed VUMC to improve efficiency and communication processes in order to deliver cohesive care across the medical center and its affiliated clinics and physicians' practices.

AHLTA is a global Electronic Health Record (EHR) system used by U.S. Department of Defense (DoD). It was implemented at Army, Navy and Air Force Military Treatment Facilities (MTF) around the world between January 2003 and January 2006. It is a services-wide medical and dental information management system. What made AHLTA unique was its implementation date, its Central Data Repository, its use in operational medicine and its global implementation. There is nothing like it in the private sector.

Body area network Small-scale computer network to connect devices around a human body, typically wearables

A body area network (BAN), also referred to as a wireless body area network (WBAN) or a body sensor network (BSN) or a medical body area network (MBAN), is a wireless network of wearable computing devices. BAN devices may be embedded inside the body as implants, may be surface-mounted on the body in a fixed position, or may be accompanied devices which humans can carry in different positions, such as in clothes pockets, by hand, or in various bags. While there is a trend towards the miniaturization of devices, in particular, body area networks consist of several miniaturized body sensor units (BSUs) together with a single body central unit (BCU), larger decimeter sized smart devices still play an important role in terms of acting as a data hub or data gateway and providing a user interface to view and manage BAN applications, in-situ. The development of WBAN technology started around 1995 around the idea of using wireless personal area network (WPAN) technologies to implement communications on, near, and around the human body. About six years later, the term "BAN" came to refer to systems where communication is entirely within, on, and in the immediate proximity of a human body. A WBAN system can use WPAN wireless technologies as gateways to reach longer ranges. Through gateway devices, it is possible to connect the wearable devices on the human body to the internet. This way, medical professionals can access patient data online using the internet independent of the patient location.

Fast Healthcare Interoperability Resources is a standard describing data formats and elements and an application programming interface (API) for exchanging electronic health records (EHR). The standard was created by the Health Level Seven International (HL7) health-care standards organization.

Medical device connectivity is the establishment and maintenance of a connection through which data is transferred between a medical device, such as a patient monitor, and an information system. The term is used interchangeably with biomedical device connectivity or biomedical device integration. By eliminating the need for manual data entry, potential benefits include faster and more frequent data updates, diminished human error, and improved workflow efficiency.

Medical image sharing Electronic exchange of medical images

Medical image sharing is the electronic exchange of medical images between hospitals, physicians and patients. Rather than using traditional media, such as a CD or DVD, and either shipping it out or having patients carry it with them, technology now allows for the sharing of these images using the cloud. The primary format for images is DICOM. Typically, non-image data such as reports may be attached in standard formats like PDF during the sending process. Additionally, there are standards in the industry, such as IHE Cross Enterprise Document Sharing for Imaging (XDS-I), for managing the sharing of documents between healthcare enterprises. A typical architecture involved in setup is a locally installed server, which sits behind the firewall, allowing secure transmissions with outside facilities. In 2009, the Radiological Society of North America launched the "Image Share" project, with the goal of giving patients control of their imaging histories by allowing them to manage these records as they would online banking or shopping.

Artificial intelligence in healthcare Overview of the use of artificial intelligence in healthcare

Artificial intelligence in healthcare is an overarching term used to describe the use of machine-learning algorithms and software, or artificial intelligence (AI), to mimic human cognition in the analysis, presentation, and comprehension of complex medical and health care data. Specifically, AI is the ability of computer algorithms to approximate conclusions based solely on input data.

References

  1. "enterprise master patient index (EMPI)". searchhealthit.techtarget.com. 2017-08-01. Retrieved 2019-02-08.
  2. "iREACH | Enterprise Master Patient Index by Infocom System". Archived from the original on 2006-10-20. Retrieved 2006-10-31.
  3. "Can Smart Cards Reduce the Risk of Medical Identity Theft?". healthitsecurity.com. 2014-12-19. Retrieved 2019-02-08.
  4. Probabilistic Versus Deterministic Data Matching: Making an Accurate Decision
  5. A naturalistic patient matching algorithm: Derivation and validation
  6. "Match Engine Theory and Configuration". Archived from the original on 2011-07-14. Retrieved 2010-08-28.
  7. "Cloud-based master patient index could offer patient-matching relief". healthcareitnews.com. 2017-05-03. Retrieved 2018-02-08.
  8. "Patient Matching Strategy Should Leverage Smartphones, Biometrics". ehrintelligence.com. 2018-10-02. Retrieved 2019-02-08.