Software
Clinic data backup and recovery: what to back up, how often, and who holds the key A routine for a small OPD, whether the records live on a desk computer or in a vendor's cloud.
A clinic's records are the patient list, the visits and prescriptions, the bills and the day book, and the clinic is expected to keep them for years. This post gives a backup routine for a 1 to 3 doctor OPD: what to copy, how often, where the copy lives, who holds the password, and the one test that proves a backup is real. It applies whether your software runs on a desk computer or in a vendor's cloud.
Published · Last reviewed · 7 min read
- Back up what you could not re-create: the patient master, visits and prescriptions, bills and receipts, the fee list and templates, and the scanned paper.
- The DPDP Rules, 2025 list data backups among the minimum security safeguards and ask a Data Fiduciary to keep personal data and processing logs for at least one year. The 2002 conduct regulations ask for indoor records for three years and for records to be supplied within 72 hours of a request.
- A backup you have never restored is a hope. Once a month, open the copy and find last Tuesday's visit in it. For cloud software, the real backup is a full export the clinic admin can run alone.
Back up the patient master, every visit and prescription, every bill and receipt, your fee list and templates, and the scanned paper, every working day, to a copy that lives outside the clinic computer, under a password that two named people hold. Then restore it once a month and look for a real visit. That is the whole routine; the rest of this post explains each part and how it changes when a vendor's cloud holds the data.
What should a clinic back up?
Back up whatever you could not rebuild from memory or paper. For an OPD that is a short list, and it is worth writing it on the wall by the desk computer.
| Data | Why it matters | Where it usually lives |
|---|---|---|
| Patient master | Names, phone numbers, ages, UHIDs; the key to every other record | Software database |
| Visits, notes and prescriptions | The medical record; the thing a patient or a court may ask for | Software database |
| Bills and receipts | Collections, GST position, insurance reimbursement, the CA's year end | Software database, day book |
| Fee list, doctor timings, templates, favourites | Hours of setup you do not want to repeat | Software settings |
| Letterhead and certificate formats | The print the patient carries | Software settings or a folder on the PC |
| Scanned reports and consent forms | Outside lab reports, consent, MLC paperwork | A folder on the PC or in the software |
| Registers kept on paper | OPD register, certificate register, MLC register | The cupboard; photograph or scan them monthly |
The retention rules decide how long the copies must survive. Clause 1.3.1 of the Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002 asks every physician to keep the records of indoor patients for three years from the start of treatment, and clause 1.3.2 says that when a patient, an authorised attendant or a legal authority asks for records, they "shall be issued within the period of 72 hours". You cannot meet a 72-hour request from a backup you cannot open. Our post on how long to keep medical records covers OPD retention and the state rules.
How often should the backup run?
Every working day, at closing, for anything stored on a computer in the clinic. The question to ask is how many days of work you could afford to type in again from the parchis; for most OPDs the answer is one. Weekly is enough for the settings and formats, which change rarely. Paper registers can be photographed or scanned monthly.
The DPDP Rules, 2025 make the backup a legal expectation rather than good practice. Rule 6(1) lists the minimum security safeguards a Data Fiduciary must take, and clause (d) names "reasonable measures for continued processing in the event of confidentiality, integrity or availability of such personal data being compromised as a result of destruction or loss of access to personal data or otherwise, such as by way of data-backups". Rule 8(3) asks the fiduciary to keep personal data and the logs of its processing "for a minimum period of one year". Those rules come into force eighteen months after the Rules' publication on 13 November 2025; our DPDP guide for clinics has the timeline.
Where should the copy live?
- Not on the same disk. A copy on the same computer dies with it.
- Not only in the building. Fire, theft and a flooded ground floor take the computer and the drawer next to it. Keep one copy outside: an online drive, or an external disk that goes home with a named person.
- Two copies on different schedules. A daily copy that is overwritten and a monthly copy that is kept. If a mistake or a virus corrupts the database on Monday, the daily copy is corrupt by Tuesday; the monthly copy is not.
- Readable without the software. A database file only the vendor's program can open is a backup only for as long as you have that program and that vendor. Keep at least one export in a format a spreadsheet opens.
Who holds the key?
A backup with an encryption password or an online-drive login is only as recoverable as the password. At most small clinics the password lives in one person's head or on a sticky note. Write it in a sealed envelope in the clinic's own safe, and give a second copy to the owner. Two named people, both written down. When one of them leaves the clinic, change the password that week and update both envelopes.
Treat the backup copy as patient data, because it is. The same DPDP duties that apply to the live records apply to the copy, including rule 6(1)(a)'s minimum of encryption, obfuscation, masking or virtual tokens, and rule 6(1)(b)'s access control. An unencrypted external disk in a handbag is a personal data breach waiting for a lost bag.
What changes when the software is in the cloud?
The vendor takes the server backups, and the clinic cannot see them. So the clinic's backup becomes the export. Ask the vendor three things in writing: how often their backups run and where they are kept; how long a restore takes if they lose data; and whether the clinic admin can export all data, in a file you can open, without asking support. Then run that export yourself, on a schedule, and keep the files exactly as you would keep the daily copy from a local system.
The DPDP Rules keep the clinic responsible here too. Rule 6(1)(f) asks for an "appropriate provision in the contract" between the fiduciary and the processor on security safeguards, and the illustration under rule 8(3) is a company that engages a cloud provider to host customer records and must ensure the provider keeps the data and logs for at least one year. Our page on clinic data ownership sets out what to expect from a vendor on export and deletion, and our post on switching clinic software shows what a good export looks like when you need it.
How do you know the backup works?
- Once a month, take the latest copy to a different computer or a clean folder.
- Open it. For a local system, restore it into a test copy of the software or open the export file. For a cloud system, open the export file in a spreadsheet.
- Find a visit from the previous week: the patient, the prescription, the bill amount. If any of the three is missing, the backup is not covering that table.
- Write the date and the result in a notebook kept with the backup envelope. A page of dates is the evidence that the clinic took reasonable measures, and the first thing you will want after a loss.
- Time the restore. If it took three hours on a quiet Sunday, that is what it will take on a Monday morning with the waiting room full.
What does recovery look like on the day?
When the computer dies or the data is gone, the sequence is: keep the OPD running on paper slips and the token board, then restore. Our post on running the OPD when the internet is down has the paper kit, and it works for a dead computer as well. After the restore, type in the slips from the gap, starting with bills, then prescriptions. If the backup was taken last night, the gap is one morning. If it was taken last month, the gap is the reason this post exists.
Questions
Is a clinic legally required to back up patient data?
Rule 6(1)(d) of the DPDP Rules, 2025 lists measures for continued processing after loss of access, "such as by way of data-backups", among the minimum security safeguards a Data Fiduciary must take, and rule 8(3) asks for data and logs to be kept for at least one year. These rules come into force eighteen months after 13 November 2025. The conduct regulations' retention and 72-hour rules apply now.
Is the vendor's cloud backup enough?
It protects the vendor's servers; it does not give the clinic a copy it can open without the vendor. Run the clinic's own export on a schedule and keep it as you would a local backup.
What format should a clinic backup be in?
At least one copy should open without the clinic software: CSV or spreadsheet files for the data, PDFs or images for scanned paper. A database file only the vendor's program reads is tied to that vendor.
Sources
- Ministry of Electronics and Information Technology, Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), 13 November 2025, rules 1, 6 and 8 (accessed 30 Oct 2026)
- The Digital Personal Data Protection Act, 2023 (No. 22 of 2023), Gazette of India, 11 August 2023, sections 2(i), 2(k) and 8 (accessed 30 Oct 2026)
- National Medical Commission, Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002, amended up to 8 October 2016, clauses 1.3.1 and 1.3.2 (accessed 30 Oct 2026)
- MoHFW e-Health Division, Electronic Health Record (EHR) Standards for India 2016, Standards Set Recommendations v2.0, hardware section (accessed 30 Oct 2026)
This is operational guidance for clinics, not legal or tax advice. Confirm with your state authority, council or CA.
Drafted with AI assistance; every fact checked against the sources listed; reviewed by the Vitels team.