EMPI Implementation / Conversion

NextGate is a pioneer and respected leader in the EMPI industry. For nearly 2 decades we have designed, implemented, and optimized EMPIs across a variety of healthcare environments. Our deep experience, technical ability, and innovative products are unmatched in the industry.

We specialize in implementing and tuning the NextGate registry products as well as Oracle (Sun/SeeBeyond) eIndex, eView, and Mural products. Our EMPI services cover all aspects of an implementation:

8 Week Implementation

NextGate has perfected the EMPI implementation process.  We’ve pre-built project plans, data extract formats, data analysis phases, weighting and threshold reports, and interface questionnaires.  Since we’ve done this work so many times before, we can expertly guide you through tasks, issues, decision points, and their implications. Our consolidated experience means your EMPI moves into production, fast!

The major elements of the Technical implementation are:

• Data Investigation: Analyze a representative set of patient records from each EMPI data source to identify patterns, frequencies, weights, and exclusions
• Algorithm Customization: Configure and tune the matching algorithm according to the results of the analysis
• Data Loading: Load data into the EMPI database
• Integration Interface Setup: Deploy interfaces required to connect the EMPI to its various constituent systems
• Application Configuration: Tailor the data stewardship GUI to the implementation’s requirements.
• Operations and Support: Data quality management and application support training

Passive and Active Mode

Typically, an EMPI is deployed in two distinct phases commonly referred to as Passive Mode and Active Mode.

Passive Mode creates the foundations of a working EMPI.  It loads the database, performs automatic matching, identifies potential duplicates, deploys interface connections, and continues to receive and analyze patient data after it has been entered into the  system — thus, “passive”.

Active Mode makes the EMPI’s matching process available to front-end users for real-time record comparisons. For example, a registrar can query the EMPI at the point of registration to determine if the patient already has a record anywhere in the system, which aids in the prevention of duplicate or overlay records.

This Active process can be deployed across most any system in an enterprise, not just the HIS. The user will see screen views that resemble their current system and experience efficient response times. Now, any point of entry can be enlisted to help improve the quality of data.