mediSIGHT – How to merge patients

Background

Patients will sometimes end up with duplicate records.  It is important to ensure that these are merged promptly and accurately when found.   This guide provides the information regarding the process for patient records identified as duplicates in mediSIGHT.

Throughout this guide, and when raising tickets to NUTH IT and Medisoft Support, it is critical to use the following terms:

  • Primary MRN – The MRN of the patient which should be kept.  In Powerchart, when searching for a patient, this is the MRN that is not shown in brackets.
  • Secondary MRN(s) – This is the Duplicate MRN(s).  In Powerchart these numbers are included in brackets when searching for a patient.  When opening the patient from a secondary MRN in Powerchart the Primary MRN will be loaded.

 

A change was made on 19 June 2025 (CHG87463) to the system that manages patient details between systems (HL7).  This resolved an issue where patient details were not updated in mediSIGHT following a merge of duplicate records.

Prior to this, if the patient was seen in Ophthalmology under the Secondary MRN, then no updates would be sent from the Patient Administration System (PAS) to mediSIGHT once the records were merged into the Primary MRN, as the Primary MRN was not registered to be active in Ophthalmology.

Any patients still affected by this issue (affecting patients merged between 17 March 2025 and 19 June 2025), will need their Primary MRN adding to the Preseen table by the Interface team.

 

A change was made on 17 July 2025 (CHG87802) to the interface system from mediSIGHT to DocStore and Synertec.  This resolved an issue where clinical documentation made in a Secondary MRN would be loaded into DocStore, but any associated letters were filtered out for manual review.

Following the change, all documentation is placed into the Primary MRN, regardless of the MRN (Primary or Secondary) used.  The letters are sent to Synertec using the MRN on which they were recorded (Primary or Secondary).  If a Secondary MRN is used then an automatic alert is generated to Service Desk to request merging of the records in mediSIGHT

 

Process
Patient records should be merged in Cerner, which can be requested on Service Now.  The merge will then be automatically carried out in mediSIGHT.  This guide details how to resolve patient records which have failed to automatically merge.
  1. Open mediSIGHT and Find the patient record(s)
  2. Confirm whether both the Primary and Secondary MRN exist in mediSIGHT
  3. Follow the relevant section below
    1. Only Secondary MRN exists in mediSIGHT
    2. Multiple Secondary MRNs exist in mediSIGHT (but no Primary MRN)
    3. Primary MRN and any number of secondary MRNs exist in mediSIGHT
Only Secondary MRN exists in mediSIGHT

Note: Only system administrators are able to edit patient details using this method.  Details should only be edited in this way for this designated purpose.  All other patient detail changes should be actioned through Cerner eRecord.

  1. Open the patient
  2. Click Patient details in the Navigation menu
  3. Click Add or edit details in the top right
  4. Enter the Primary MRN in the Hospital number field
  5. Click Done
  6. Place a Service Now request for the Primary MRN to be added to the Preseen table for mediSIGHT with the Interface Team (Chris Rouse / Anth Todhunter).
Multiple Secondary MRNs exist in mediSIGHT (but no Primary MRN)
  1. Perform steps 1-6 in the section above on the MRN used to make the most recent documentation.
  2. Log a ticket with Medisoft Support detailing the Primary MRN and all the secondary MRNs remaining in mediSIGHT
  3. The NUTH Service Now ticket must only be closed once a successful merge has been confirmed.  This includes confirming that the secondary MRNs are no longer accessible in mediSIGHT.
Primary MRN and any number of secondary MRNs exist in mediSIGHT
  1. Log a ticket with Medisoft Support detailing the Primary MRN and all the secondary MRNs remaining in mediSIGHT. (No action is possible from NUTH staff).
  2. The NUTH Service Now ticket must only be closed once a successful merge has been confirmed.  This includes confirming that the secondary MRNs are no longer accessible in mediSIGHT.


Updated: 9 September 2025