![\"\"](\"https:\/\/training.nuth-itt.co.uk\/wp-content\/uploads\/2025\/04\/Picture36-300x71.png\")
<\/p>\n<\/p>\n
Patients will sometimes end up with duplicate records.\u00a0 It is important to ensure that these are merged promptly and accurately when found.\u00a0 \u00a0This guide provides the information regarding the process for patient records identified as duplicates in mediSIGHT.<\/p>\n
Throughout this guide, and when raising tickets to NUTH IT and Medisoft Support, it is critical to use the following terms:<\/p>\n
<\/p>\n
A change was made on 19 June 2025 (CHG87463) to the system that manages patient details between systems (HL7).\u00a0 This resolved an issue where patient details were not updated in mediSIGHT following a merge of duplicate records.<\/p>\n
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.<\/p>\n
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.<\/p>\n<\/div>\n
<\/div>\n
<\/p>\n
A change was made on 17 July 2025 (CHG87802) to the interface system from mediSIGHT to DocStore and Synertec.\u00a0 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.<\/p>\n
Following the change, all documentation is placed into the Primary MRN, regardless of the MRN (Primary or Secondary) used.\u00a0 The letters are sent to Synertec using the MRN on which they were recorded (Primary or Secondary).\u00a0 If a Secondary MRN is used then an automatic alert is generated to Service Desk to request merging of the records in mediSIGHT<\/p>\n<\/div>\n
<\/div>\n
<\/p>\n