<p>Managing patient records efficiently is crucial in providing high-quality healthcare services. This guide will walk you through the process of merging duplicate records when registering a patient with an existing EMIS ID, ensuring a unified and accurate patient database.</p><h1><strong>Identifying duplicate patients</strong></h1><ul class="accent-bullets"><li><p><strong>Notification:</strong> Upon adding an EMIS ID to a patient's profile, the system may alert you to the existence of a duplicate EMIS ID already in the system.</p></li><li><p><strong>Option to merge:</strong> In the event of such an alert, you will be presented with the option to merge the new patient record with the existing duplicate record.</p></li></ul><h1><strong>Merging duplicate patients</strong></h1><p>On some occasions we will not be able to match the patient as their EMIS ID will be assigned to another patient already in Hero. This is when you will be asked to merge the two patients. Hero will display the two patient details side by side side for you to review before confirming the merge.</p><blockquote><p><strong>⚠️ Be aware that any patient details not associated with the patient holding an EMIS ID will be lost during the merge. If there are specific details you wish to retain, ensure they are manually copied into the patient's EMIS record before completing the merge.</strong></p></blockquote><h1><strong>Which patient is preserved after the merge</strong></h1><p>When the merge is successful, the patient with the existing EMIS (or PDS in an NHS practice) will be preserved.</p><h1><strong>Information that is merged</strong></h1><p>The merge will include appointments, messages, questionnaires, invoices, prescriptions, and any approved connections to the patient holding the EMIS ID, ensuring a complete and updated patient profile.</p><h1><strong>When is a patient determined as a duplicate?</strong></h1><p>For a merge scenario to occur, both patient records must share the same date of birth and EMIS ID. This ensures that conflicting information are against a unique identifier (EMIS ID) and patient identifiable information (Date of birth) to verify that the conflict is a patient that has two records therefore prevents the merging of records for different patients.</p>

Patients

Learn how to merge duplicate Hero patient records.

Patient merging

Invite admins

Practitioners

Locations

Multi-tenancy

API keys

Introducing NHS patients to Hero

Introducing private patients to Hero

Onboarding

Send a message

View sent messages

Contact methods

Questionnaires

Questionnaire links

Questionnaire responses

Patient replies

Send an attachment

Self-booking links

Message templates

SMS fragments

What patients see

EMIS-X

Individual messaging

Send a batch message

Uploading patients

Batch messaging

Online booking

Appointment restrictions

Networks

Cross-org booking

Cross-org self-booking links

Intake forms

Video appointments

Diary view

Book an appointment

Reporting

Reminders mailers

Cancellation policy

Appointment types

Appointments

Patient submissions

Assigning admins

Teams

Respond to a patient

Inbox

Get started

Pathways

Request templates

Patient access

Schedule access

Daily limits

Page messaging

Medical device status

Testing pathways

Submit a request

Auto-assign requests

Care navigation

SMS (Firetext)

Stripe: Get started

Stripe: Invoicing

Stripe: Take payments

Stripe: Products

Stripe: Reporting

Stripe: Patient details

Stripe: Customers

Stripe: Branding

Stripe: Patients payments

Apps

Get Started

Troubleshooting

EMAS Manager

Multiple instances of EMIS Web running on the PC

.Net 3.5 required for Sidekick to function

Hero Sidekick

Getting started

Gateway PC setup

Booking configuration

Unregistered patients

Retrieve patient records

Hero hosted integration guide

SystmOne

EMIS

Submit a quick consult

Feature requests

Sub-processors

Multi-Factor Authentication (MFA)

About the Hero platform

Docs

Hero Health