Medical Record Retention in India: Build a Clinic Schedule
Build a clinic retention schedule with scoped NMC guidance, a worked date review, hold instructions and an archive retrieval test before EMR exit.
As of 28 October 2026, DPDP implementation is phased: the notified one-year and eighteen-month stages are still ahead. The October 2026 wording order does not change that schedule. An Indian clinic should map each patient-data use, resolve provider roles and applicable requirements, and rehearse requests and incidents. A privacy notice or “DPDP-ready” software label alone does not establish compliance.
For Indian clinic owners planning digital patient-data governance and evaluating software providers during the DPDP transition.
G.S.R. 843(E), dated 13 November 2025, commences the Act in groups: specified provisions on publication, another group after one year and the main processing-obligation and individual-rights provisions after eighteen months. Rule 1 of the final Rules also uses staged commencement. The December 2025 corrigendum corrects wording in that rule.
On this article’s review date, 28 October 2026, the one-year and eighteen-month stages of those November 2025 notifications are still ahead. The table is a reading aid, not a substitute for checking the exact provision and any subsequent notification when making a legal decision.
Use two separate planning columns: obligations applicable to the clinic now, and preparation for provisions due to commence later. A future DPDP stage does not answer every current confidentiality, record-handling or security question. Nor should a vendor imply that buying a feature today completes the clinic’s future obligations.
On a narrow screen, scroll the table horizontally to read all columns.
| Stage in the notifications | Selected scope | Position at 28 October 2026 |
|---|---|---|
| Publication stage | Specified Act provisions; Rules 1, 2 and 17–21. | This stage has commenced. |
| One year after publication | Act section 6(9) and section 27(1)(d); Rule 4. | The notified one-year stage is still ahead. |
| Eighteen months after publication | The principal processing and rights provisions listed in G.S.R. 843(E); Rules 3, 5–16, 22 and 23. | Prepare for the later stage; do not label it fully operative today. |
Source: MeitY: G.S.R. 843(E), commencement notification
S.O. 5458(E), dated 5 October 2026, is the Digital Personal Data Protection (Removal of Difficulties) Order, 2026. It changes wording in section 9(1) about children and persons with disability who have a lawful guardian, and clarifies the data-audit wording in section 10(2)(c)(ii). The order describes these as textual and editorial corrections. It does not revise the staged commencement notification.
For the clinic’s working file, record the instrument, affected provision and consequence separately. A new publication date does not mean every processing duty started on that date. Equally, an older downloaded copy of the Act may omit later wording changes. Keep the order alongside that copy so an adviser does not unknowingly assess superseded wording.
A family member providing a phone number is also not, by that fact alone, established as a lawful guardian. Record the actual relationship and authority relevant to the activity; do not turn a convenient reception contact into authority for every record request, recording or secondary use. Any child-specific or guardianship process needs its own applicable assessment.
Source: Gazette of India: DPDP Removal of Difficulties Order, 2026
The Act’s enacted scope includes personal data collected digitally and paper information later digitised. It distinguishes a Data Fiduciary, which determines processing purpose and means, from a processor acting on its behalf. It provides for consent and certain legitimate uses; a checkbox is not the only question in choosing an applicable processing ground.
Map roles by activity and agreement. A clinic may choose why it records an encounter, while a software provider handles storage under the agreed service. A separate use of information by that provider needs its own scrutiny. Do not assume every vendor activity has the same role simply because one contract calls the vendor a processor.
Separate the treatment decision, the record-keeping activity, optional messaging and any secondary use such as model training. The fact that they involve the same patient does not make their purposes identical. Ask the responsible adviser to assess applicability and grounds against the actual flow.
Source: India Code: Digital Personal Data Protection Act, 2023
Begin with the path a patient’s information takes through an ordinary visit. Include registration, paper documents scanned at reception, consultation notes, billing, messages, exports and support interactions. Identify the locations outside the central EMR: a downloads folder, an email attachment or a staff phone can become an unplanned copy.
For each flow, name a responsible clinic person and the provider involved. Record what is collected, why, who can access it, where copies go and what event triggers review or disposal under the applicable policy. This is a practical inventory, not a claim that one spreadsheet fulfils the law.
On a narrow screen, scroll the table horizontally to read all columns.
| Activity | Information and destinations to identify | Question the owner must resolve |
|---|---|---|
| Registration | Patient identifiers, contact details, booking form and reception screen. | Which fields are necessary, and how are shared contacts represented? |
| Clinical record | Notes, prescriptions, reports, attachments and retained versions. | Who may view, amend, export and authorize release? |
| Patient communication | Recipient, purpose, channel/provider and queued messages. | How does a changed contact arrangement reach the next send? |
| AI or document processing | Audio/images, generated text, external processors and retained copies. | What is processed, retained or reused under the actual agreement? |
| Support and recovery | Screenshots, logs, support sessions, backups and restored environments. | Who authorizes access and verifies closure or recovery? |
In this fictional example, adult patient P-62 has an appointment booked using a family phone. She tells reception, in her preferred language, that she wants a paper visit summary, no promotional messages and no audio recording. An appointment reminder is already queued. The EMR stores typed notes, a separate provider sends messages, and an optional scribe service has not yet been activated for this visit.
Reception confirms which patient and communication arrangement the request concerns without announcing clinical information at a crowded desk. It records the request and routes decisions to the responsible people. The words “no messages” need clarification: refusing promotions, changing the reminder channel and requesting erasure are different instructions. The clinic should capture the patient’s meaning, rather than make her choose an unexplained software setting.
The following decisions are an operational rehearsal, not a determination of a legal processing ground. They show why four activities sharing a name and phone number still need separate ownership. The same exercise should be repeated after a provider change, because a preference stored in the EMR may not automatically reach another service.
On a narrow screen, scroll the table horizontally to read all columns.
| Activity | Decision and responsible role | Evidence that closes this part |
|---|---|---|
| Typed clinical record and paper summary | Doctor continues the agreed documentation workflow; records staff assess any separate retention or access question. | The visit record remains attributable and the requested paper output is handled through the clinic’s release process. |
| Queued appointment reminder | Reception checks the exact recipient and asks the messaging owner to cancel or change this queued send through the supported process. | Queue status and provider response are recorded; an already transmitted message is not described as recalled. |
| Promotional communication | The marketing owner applies the refusal to the relevant audience/list and checks future scheduled campaigns. | The patient is excluded from the intended promotional use without silently deleting the clinical chart. |
| Optional audio processing | The doctor uses manual documentation for this fictional visit; the scribe remains off. | No recording starts; a screen label alone is not treated as proof about an earlier recording or a provider’s retained copies. |
At the next shift, another receptionist should be able to see what changed and what remains unresolved. A global “consent withdrawn” label is too vague to tell them whether a reminder may be sent or whether the chart is still needed for care. Use the request reference, affected purpose, effective instruction and confirmed completion state.
For P-62, suppose the marketing exclusion is confirmed but the messaging provider has not yet answered about the queued reminder. The request is partly actioned. Do not mark every task complete or promise that no message can arrive. Assign follow-up to a person, use the agreed alternative contact route where necessary, and update the patient with what is known.
An internal handover should contain enough detail to act without copying an entire consultation into a privacy task. If identity or representative authority is uncertain, record what needs resolution and route it appropriately. Do not collect a fresh identity-document scan automatically for every routine preference change; establish a proportionate verification process for the actual request.
Rule 3 describes an understandable notice with an itemised account of personal data and purposes, and ways to withdraw consent, exercise rights and complain. Rule 6 addresses safeguards, including access visibility, continuity and processor-contract provisions. These belong to the later commencement group; use the final text for preparation rather than presenting draft rules as current law.
An operational draft should reflect what the clinic actually does. If appointment coordination uses a provider, the internal implementation record should identify that arrangement. If the clinic does not use audio recording, do not copy a generic notice that suggests it does. Remove vague catch-all language that the team cannot explain.
Test whether a patient can understand the purpose and find a working contact route in a language and format suitable for the clinic’s audience. Then test the other end: someone must receive and act on a request. A carefully written notice pointing to an unattended inbox is an incomplete operational process.
Version the approved wording and record when and where it was used. Updating a web page does not establish what a patient saw on a paper form last month. Keep the evidence needed to explain that history without inventing consent that was never captured.
Ask for the data-flow and service scope that applies to your clinic, including subprocessors, hosting, support access, retention and deletion handling, incident cooperation and exit. The answer should describe the configured product, not a generic security brochure for a different service.
Distinguish a contract promise from observable behaviour. The agreement may describe role-based access; a demonstration should show what reception and a doctor can actually see. A statement about deletion needs to explain retained copies and recovery environments. A support promise needs a working contact and escalation process.
Keep the unresolved questions visible in procurement. “DPDP-ready” is not a substitute for a named feature, contractual obligation or clinic procedure. Conversely, a missing answer should become a specific gap to resolve rather than a sweeping allegation that the product is unlawful.
Use fictional cases: a patient changes a shared contact number, asks for records, questions an entry or reports an unexpected message. Trace how the request arrives, how authority and scope are checked, who decides and how the outcome is communicated. Different requests can require different clinical or legal review.
For an incident exercise, start with a specific event such as a record package sent to an unintended recipient. Identify who contains the problem, preserves the facts and assesses affected data and applicable notification duties. Do not apply one copied deadline to every incident without checking the relevant regime and commencement status.
A deletion request also needs a reasoned process. Record-retention obligations, unresolved proceedings and different copies can matter. Do not promise immediate erasure of every clinical record merely because a communication preference changes.
An unexpected patient-file disclosure needs prompt containment and assessment under the requirements that actually apply. Future DPDP commencement is not permission to ignore current duties. CERT-In’s 28 April 2022 directions require the named entity categories to report specified cyber incidents within six hours of noticing them or being informed. Assess entity and incident scope, including the clinic’s provider arrangements, rather than assuming that every event has one universal deadline.
In a rehearsal, write down when the clinic learned of the event, who controls the affected system, what was exposed and who owns the notification assessment. Keep those facts separate from when a support ticket was opened. Waiting for a vendor to close its investigation can consume the time available for a duty that starts earlier.
A practical first decision is whether the recipient link or access can be restricted through the supported process while preserving evidence. Record containment, uncertainty and escalation as separate steps. A patient-record response period, a future DPDP reporting provision and a provider’s service-response promise are not interchangeable incident clocks.
Start with unknown destinations and unowned access, because they make every later assurance difficult to support. Then resolve purpose and notice mismatches, provider responsibilities and the request-handling path. Test recovery and incident coordination against the same map.
For a small clinic, one maintained register with named owners is often more useful than a large policy pack nobody can operate. Review it when a new service, provider or data use is introduced. The next decision should be tied to evidence, not the number of pages in the folder.
This article’s preparation sequence is original operational guidance. It is not a statutory checklist or a determination that a particular clinic has met every applicable requirement.
A fictional clinic adds an AI note-drafting service to an existing EMR. Its old map covers typed records and appointment messages, but not audio sent to another processor. Before using patient recordings, the owner identifies the new flow, obtains the actual provider terms, resolves retention and reuse questions and updates the relevant procedure and patient information. A generic privacy checkbox is not treated as evidence that those decisions have already been made.
Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.
No. S.O. 5458(E) changes wording in sections 9 and 10. It does not change the phased commencement schedule. As of 28 October 2026, the notified one-year and eighteen-month stages are still ahead.
Record the purpose-specific instruction and apply it to the relevant messaging lists and queued work. Continue the separately assessed care-record process. Do not infer a request to erase the chart or authority for a family contact from a promotional opt-out.
No. The notified scheme has publication, one-year and eighteen-month stages. Check the specific provision and current notifications rather than treating an announcement of the Rules as one universal commencement date.
The enacted scope expressly includes non-digital personal data that is later digitised, subject to the Act’s applicability and commencement. Include scanned files in the clinic’s assessment.
No. The clinic still needs to understand purposes, applicable grounds, recipients, access, provider responsibilities and how requests are handled. The checkbox is only one possible piece of evidence.
A label cannot establish the clinic’s actual practices. Verify specific controls and contractual scope, and connect them to the clinic’s applicable obligations and responsibilities.
Map the real patient-data journey and assign owners to unknown destinations or access. Use that map to review the relevant legal position, provider terms, notices and request process.
Updated on . Status is scoped to 28 October 2026 and the linked instruments. Clinic-specific applicability, existing duties and later changes need appropriate legal assessment. P-62 is fictional; the readiness examples are not a certification or a complete patient notice. No independent clinical or legal review is claimed.
Scope, definitions and grounds; this copy is dated as of 19 November 2025. Read with later instruments below. Checked 28 October 2026.
Primary staged-commencement notification dated 13 November 2025; checked 28 October 2026.
Rules 1, 3 and 6 for the narrowly discussed preparation topics; final text distinct from the January draft. Checked 28 October 2026.
December 2025 correction, including publication wording in Rule 1; checked 28 October 2026.
S.O. 5458(E), dated 5 October 2026; clauses 1–2 and the stated textual/editorial purpose. Official PDF retrieved and read 28 October 2026.
Direction (ii) and Annexure I; specified entities and cyber incidents, not a universal response clock. Checked 28 October 2026.
Build a clinic retention schedule with scoped NMC guidance, a worked date review, hold instructions and an archive retrieval test before EMR exit.
Evaluate vendor support access with a timed session case, repair approvals, open-session expiry tests and separate checks for remote control and retained files.
Separate clinic care messages from promotions with English and Hindi reminder examples, permission checks and a worked opt-out timeline.
Bring a fictional data-flow map and the provider questions you need answered. Inspect role access, record requests and support handling against the actual configured scope.
Request a clinic demo