Q-Cyber Magazine
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.

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
| Layer | What should be true | Public hook |
|---|---|---|
| Lawful basis and notice | Standalone, purpose-specific notice for consultation, recording, prescribing and any secondary use | DPDP Rules, as described by PIB on 14 November 2025 |
| Session path | No implicit trust in the bearer; authentication of the parties before access to the clinical resource | NIST SP 800-207 |
| Record sharing | A consent artefact defining the scope of each share, consistent with federated exchange | Health Data Management Policy |
| Incident and evidence | Specified cyber incidents reported within six hours; logs retained 180 days in India | CERT-In directions, 28 April 2022 |
| Breach affecting patients | Prompt, plain-language notice of nature, consequences, steps and a contact point | DPDP 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
- Classify the platform as a clinical system, with an owner, a record policy and a processor list.
- Protect the session as an untrusted path, with identifiable parties and keys that do not belong to the bearer.
- Share records through consented exchange, not through unmanaged copies.
- 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.


