Transferring Patients Between Clinic Branches Safely
How a clinic group in India hands a patient from one branch to another: consent, clinical handover note, records, appointments, follow-up and patient choice.
How Indian clinic groups can share patient records across branches safely: one record, unique patient IDs, role-based access, consent, ABDM, duplicates and audit logs.
A clinic group should keep one record for each patient that any branch can open when the patient visits, with a unique patient ID, careful duplicate checks, role-based access so staff see only what they need, audit logs of who opened what, and clear consent and privacy notices under the DPDP Act. Link records with outside facilities through consent-based sharing such as ABDM where available. Make sure records stay available during internet outages and that you can export them if you change systems.
On a narrow screen, scroll the table sideways to see every column.
| Principle | What it means |
|---|---|
| Unique patient ID | Each patient has one ID across the group |
| Single history | Visits, prescriptions, tests and notes from all branches in one record |
| Same templates | Notes look the same everywhere |
| Real-time access | A visit at one branch is visible at another immediately |
| Clear authorship | Each entry shows the doctor, branch, date and time |
Duplicates happen when a patient registers at a new branch with a different spelling or phone number. Prevent them by:
Not everyone needs everything:
On a narrow screen, scroll the table sideways to see every column.
| Role | Access |
|---|---|
| Doctors | Full clinical record of patients they treat |
| Nurses | Clinical details needed for their tasks |
| Reception | Demographics, appointments, billing |
| Branch managers | Operational reports, not clinical notes |
| Owners | Group reports; clinical access only if they treat patients |
Restrict sensitive notes, such as mental health, sexual health or termination, further.
Record who opened which record, when and from which branch. Review logs for unusual access, such as staff opening records of patients they did not see. Logs protect patients and help investigate complaints.
Under the Digital Personal Data Protection Act, 2023, tell patients how their data is used and shared. A simple notice at registration can explain that records are shared across the group's branches for their care, who can see them and how to ask questions. Do not use the shared record for marketing without separate consent.
Patients also visit hospitals, labs and other doctors. The Ayushman Bharat Digital Mission provides health facility registration, ABHA numbers and consent-based sharing of records between facilities. Where your software supports it, this lets you receive and share records with the patient's consent.
Internet and power cuts happen. Check that branches can continue to see and record patient information during an outage and that the system shows clearly what has been saved and synced. Keep a paper fallback for emergencies and enter it later.
If you change software, you must be able to export all records in a usable format, including notes, prescriptions, attachments and audit trails. Check this before you choose a system. See clinic software data ownership.
Occasionally a patient asks that a visit to one branch, for example for a sensitive concern, not be visible to staff at another. Discuss what this means for their safety, record the request, and use the software's restricted access features where available. Respect the request as far as safe care allows.
At every visit, reception should confirm the patient's identity with two details, such as name and phone number or date of birth, before opening the record. Doctors should glance at allergies, current medicines and recent visits at other branches before prescribing. These small habits make the shared record useful rather than just available.
A four-branch clinic group in Lucknow had separate records at each branch. A patient with a penicillin allergy recorded at one branch was prescribed amoxicillin at another. After this near miss, the group moved to one shared record with a unique patient ID, trained reception to search by phone and name before registering, and reviewed duplicates weekly. Allergies and long-term medicines now appear at every branch, and repeat tests ordered within a month fell noticeably.
Bractis supports clinics with more than one location, with roles that limit access and supported local work that shows save and sync status. Caregiver access is explicit and purpose-limited. ABDM support is in development. Bractis does not sell health data or use it for advertising. Ask the team what is supported today for shared records and duplicate handling, and test it. Plans start at ₹999 a month plus GST.
By searching before registering, training reception, reviewing possible duplicates and merging carefully with a way to reverse mistakes.
Tell patients clearly how records are shared within the group for their care, as the DPDP Act requires. Separate consent is needed for other uses.
ABDM supports consent-based sharing of records between registered facilities using the patient's ABHA.
Bractis is clinic management software built for Indian OPDs: appointments, patient records, prescriptions, billing and follow-up in one place. You can try it in your own clinic before you decide.
Written by the Bractis editorial team for doctors and clinic owners in India. Rules, fees and prices change: check the linked primary sources before acting, and ask your CA or lawyer about your own case.
Duties of data fiduciaries, including security safeguards, purpose limits and breach reporting.
Health facility registry, ABHA and consent-based sharing of health records between facilities.
Professional conduct for doctors, including no fee-splitting, records and limits on use of a doctor's name for commercial promotion.
Each clinical establishment, including each branch, needs registration where the Act or a state law applies.
Rules for consultations by video, audio and text, including with a health worker present.
How a clinic group in India hands a patient from one branch to another: consent, clinical handover note, records, appointments, follow-up and patient choice.
How clinic groups in India govern patient data: who is responsible, access roles, consent, retention, vendor contracts, breach response and regular access reviews.
How to run two or more clinic branches in one software in India: shared patient records, branch-wise billing and reports, staff access by branch, and setup steps.
How the hub-and-spoke model works for Indian clinic groups: a central specialist hub, nearby GP or satellite clinics, referral pathways, shared records and economics.