Duplicate MRN created during registration — patient demographics mismatch
Issue Description
Front desk staff reported that a returning patient was registered with a new MRN instead of their existing one. The system created a duplicate record. Patient has two active MRNs in the system causing billing and clinical documentation issues.
Troubleshooting Checklist
Work through each step. Check off as you complete them.
Verify patient demographics in MRN lookup
Confirm patient name, DOB, SSN, and address match source documents. Check for duplicate MRNs.
Check registration workflow configuration
Review the registration workflow in Cerner PowerChart — confirm required fields, mandatory sections, and facility-specific rules.
Validate insurance/guarantor setup
Confirm payer plan, subscriber ID, group number, and eligibility status are correctly mapped.
Review user role & security access
Confirm the reporting user has the correct Cerner security role for the registration domain.
Check facility/location configuration
Verify the facility node, encounter type, and location codes are correctly set in the domain.
Test in non-production environment
Replicate the issue in the Cerner test/cert environment to isolate configuration vs. data issue.
Document findings and resolution
Record root cause, steps taken, and resolution in the ticket. Notify facility POC.
Root Cause
The patient's name was entered with a nickname ('Liz' vs 'Elizabeth') causing the MPI matching algorithm to fail. Duplicate detection threshold was set too low for partial name matches.
Resolution
Merged duplicate MRNs using the MPI merge utility. Updated the MPI matching threshold for nickname/alias matching. Trained registration staff on proper name entry standards.