Q-Cyber Magazine

Healthcare · 21 August 2026 · 3 min read

Telemedicine is a clinical system, not a consumer video call

Remote consultation platforms process personal health data and create clinical records; they should meet DPDP duties, a resource-level access model, and, where records are shared, the national digital health consent design.

Abstract graphic of layered document sheets in Knowlcom blue

A remote consultation produces, or should produce, a record: who was seen, what was said, what was prescribed, and often an image, a chat log or a recording. That record is personal data. The platform that carries it is a clinical system, and should be designed as one.

The session and the record

Two layers need to be designed together. The first is the session: how the clinician and the patient are identified, how the path is protected, and whether a third party on the path can read or alter the consultation. A consumer calling app that was not built for this purpose will usually fail that test, because identity is weak, recordings may be stored in the wrong place, and the path is not under the provider's control. This article will not prescribe a particular product. It will say that keys and identities should belong to the parties, and that the path should not be treated as trusted merely because the call connected.

The second layer is the record. A consultation that leaves no accountable record is a clinical failure. A consultation that leaves an identifiable record in an unmanaged chat history, a personal mailbox or an unnamed cloud folder is a DPDP failure. Notices should say whether sessions may be recorded, how long records are kept, and who may see them. If the record is later shared with a specialist or into the national digital health exchange, a scoped consent artefact, not a forwarded attachment, is the design the national policy already describes.

Exhibit 1

A telemedicine control set drawn from published duties

LayerWhat should be truePublic hook
Lawful basis and noticeStandalone, purpose-specific notice for consultation, recording, prescribing and any secondary useDPDP Rules, as described by PIB on 14 November 2025
Session pathNo implicit trust in the bearer; authentication of the parties before access to the clinical resourceNIST SP 800-207
Record sharingA consent artefact defining the scope of each share, consistent with federated exchangeHealth Data Management Policy
Incident and evidenceSpecified cyber incidents reported within six hours; logs retained 180 days in IndiaCERT-In directions, 28 April 2022
Breach affecting patientsPrompt, plain-language notice of nature, consequences, steps and a contact pointDPDP Rules

Source: Press Information Bureau, 14 November 2025; Health Data Management Policy on abdm.gov.in; NIST SP 800-207, August 2020; CERT-In, 28 April 2022.

Implications

  1. Classify the platform as a clinical system, with an owner, a record policy and a processor list.
  2. Protect the session as an untrusted path, with identifiable parties and keys that do not belong to the bearer.
  3. Share records through consented exchange, not through unmanaged copies.
  4. Rehearse CERT-In and DPDP notice for a compromised or leaked clinic.

What this means for healthcare

Remote care is now ordinary. It will be trustworthy only if the session and the record are designed with the same seriousness as a consulting room and a paper file, under a law that already requires purpose, safeguards and an answer to the patient within 90 days.

Sources

  1. PIB notification of the DPDP Rules, 2025
  2. National Digital Health Mission: Health Data Management Policy
  3. NIST SP 800-207, Zero Trust Architecture
  4. CERT-In Directions, 28 April 2022