Hi Joseph! I would be interested in this information if you still have and are willing to share!!Becky
I would also be interested in anything you are willing to share.
Carol L. Rich, CPC
Health Information Supervisor
Health Information Management
1100 Lakeview Drive
Wausau, WI 54403
"Try not. Do, or do not. There is no Try!" ~ Yoda
P Please consider the environment before printing this email.
Statement of Confidentiality
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient of this email, any use, dissemination, forwarding, printing, or copying of this email is prohibited. Please notify the sender of this email of the error and delete the email.
I am also interested in what insights you can share as I responsible for my health systems EMPI.
Laritha Boone, MBA-HCM, RHIA
Manager, HIM Data Integrity and eHealth
251 South Claybrook
Memphis, TN 38104
direct 901-516-2332 | fax 901-937-3347
I'd be interested in this information as well. Thanks for sharing.
Leah Beck, RHIA
Health Information Management
Hi, I am interested also please. If you have any information on any MPI clean up that was done and what vendor you used, if any, would be greatly appreciated. My email address is kviruet@valleyehealth.
I'm interested in this information as well. My email is firstname.lastname@example.org.
This seems to be a hot topic. I would really appreciate any information you have on Master Patient Index Specialist too. Please email it to me at email@example.com
I am also interested in receiving this information. Please send it to Maryjo.firstname.lastname@example.org.
Mary Jo Laufenberg RHIA
HIMS EHR Director
MPI Cleanup Projects - Pre-EHR Go-Live
MPIs must be duplicate patient free before considering load into EHR.
Cleanup should begin as soon as possible.
Once cleanup has been completed, a new MPI extract is completed and loaded into the EHR at least one week prior to go-live (requires dual registration in legacy system and EHR for one week).
Considered several options for the initial pre-EHR load MPI cleanup projects.
HIM - Some departments were staffed and some were not staffed for large cleanups such as this. We now exclusively rely on HIM to complete MPI cleanups since we do not operate with tight timelines as we have in the past.
Vendor -Not very cost effective and did not allow us to retain those folks beyond the cleanup project for maintenance.
Temp employees - We went the route of hiring temp employees during our initial MPI/ EMPI cleanup projects. Some were assigned to HIM departments that were not staffed to handle an MPI cleanup and the remaining were staffed to work the EMPI cleanup projects once each MPI was loaded into our EHR. Once the large cleanups were complete and our EHR went live we retained several temp employees to become permanent employees to maintain the EMPI.
Determine process for cleanup.
MPI duplicate patient analysis was completed in our EHR cleanup/ Test environment to ensure that the logic (probabilistic, deterministic, fuzzy) in what will become our source system was used. If you use any other system's logic it may not equal the EHR logic and you may end up with many more potential duplicates once loaded into the EHR.
Duplicate patient analysis was exported to an Excel spreadsheet that can be easily worked by HIM/ temp staff at the sites.
Decision was made to only complete the electronic merge of medical record numbers and not change labels on paper records. This decision was made based on the fact that the merged away MRN is always retained in the MPI as a previous MRN and could be imported into the EHR. Additional training was necessary to ensure staff always checked the systems for a previous MRN.
I required weekly updates from the sites to ensure they were on track to meet our EHR MPI go-live deadlines.
MPI/ EMPI Maintenance - Post-MPI EHR Loads
Initial cross-facility duplicate patient cleanup. (Duplicates created between different facilities)
EMPI staff is responsible for remediating duplicate patients that are created due to MPI loads into the EHR.
Initial internal duplicate patient cleanup. (Duplicates within the same facility)
Occasionally we will be required to work down internal duplicates in the EHR after an MPI load is completed.
If merge messages are not sent to downstream systems, HIM and ancillary departments are responsible for running their merged patient reports in the EHR daily in order to ensure that their MRNs remain in sync with merges completed in the EHR.
Ongoing cross-facility and internal duplicate patient maintenance. (24 hours x 5 days and on call weekends)
EMPI staff is responsible for running, researching and working down hourly cross-facility duplicate patient reports and daily internal duplicate patient reports (broken out by facility).
EMPI staff responsible for responding to end user duplicate patient reports via our Remedy system.
Ongoing patient overlay monitoring and reporting. (24 hours x 5 days)
EMPI staff is responsible for working two patient overlay work queues hourly that report out all patients in real time that have had either a single date of birth change or a change to two or more demographics done at the same time.
EMPI staff researches to determine if it was a demographic correction, error or if it was truly a patient overlay in which the wrong patient record was used for treatment.
EMPI Manager responsible for confirming the patient overlay and coordinating the remediation process.
Requires assistance from HIM, reg, rad, lab, billing, risk, pharm
Ongoing incoming message report management. (24 hours x 5 days)
This task requires EMPI staff to work a report hourly that reports out incoming continuity of care documents, (Transitions of Care "CCD"), that failed to route to our SSM providers due to missing provider name, no EHR record to link to or slight demographic discrepancies between the incoming message and EHR record.
MyChart Proxy Setup (Patient portal). (24 hours x 5 days)
One EMPI staff member is responsible for accepting and setting up access requests to our patient portal for parents/ guardians requesting access to patient records.
ID theft investigations. (As needed)
EMPI Manager plays a role in investigating ID theft reports since I have access to all patient records in the EHR. This allows me to compare signatures and locate, identify and flag any other records that may be the victim or perpetrator of the ID theft.
Stats tracking and reporting. (Daily and report out monthly; see EMPI Dashboard template attachment)
EMPI Manager responsible for reporting out monthly stats related to:
EHR testing. (As needed)
EMPI Manager completes all testing as it relates to EMPI EHR enhancements, fixes and upgrades.
This Practice Brief contains a model MPI Coordinator Job Description.
AHIMA. "Fundamentals for Building a Master Patient Index/Enterprise Master Patient Index (Updated)." Journal of AHIMA (Updated September 2010).
Read your post and I would be very interesting in your support information if you are willing to share.
Sue Foster, RHIT, CPC, CMT
Financial Software Services