What a compliant teleconsultation workflow actually requires
A teleconsultation workflow in an Indian hospital has five obligations that exist whether or not the software enforces them: the practitioner must be a registered medical practitioner acting within their competence, both parties must know who they are speaking to, consent must be established, the consultation must be documented as thoroughly as an in-person visit, and any prescription must respect the limits that apply to remote consultation. Everything else — the video quality, the waiting room, the payment link — is convenience layered on top of those five. Hospitals that build the convenience first and retrofit the obligations later usually end up with a service their medical committee quietly stops trusting.
The governing reference in India is the Telemedicine Practice Guidelines, which set out how registered medical practitioners may consult remotely, what modes are permitted, and how medicines are grouped for remote prescribing. The guidelines are deliberately mode-agnostic: video, audio, and text-based consultations are all recognised, but the practitioner is expected to exercise judgement about whether the chosen mode is adequate for the clinical question in front of them. That judgement is the part no configuration screen can make for you.
The practical consequence is that teleconsultation should be designed as a variant of your existing OPD workflow, not as a separate product bolted to the side of the hospital. Same patient record, same identifiers, same prescription numbering, same billing ledger. When teleconsultation runs on a parallel system, the first time a tele patient walks into the physical OPD you discover you have two records for one person.

Identity verification on both sides of the call
The practitioner must be satisfied that the patient is who they claim to be, and the patient is entitled to know the practitioner's name and registration status. In practice this means the consultation screen should display the doctor's name and registration number to the patient without the doctor having to recite it, and the booking flow should capture enough identifying information that the doctor is not starting the encounter with a guess. Age and identity matter more here than in a physical OPD, because there is no reception desk that saw the person.
For an existing patient, identity is largely solved by linking the teleconsultation to the existing MRN and confirming a known detail at the start of the call. For a new patient, hospitals typically capture a government identifier or ABHA number at registration and confirm the name and year of birth verbally. ABHA linkage is worth doing at this point rather than later, because a tele patient who never visits the campus may otherwise never get linked at all.
Consent deserves an explicit position in your workflow even though the guidelines treat a patient-initiated consultation as carrying implied consent. Record who initiated the encounter, and where the hospital or a health worker initiated it, capture consent explicitly and store it against the encounter. If the consultation is recorded — which is a separate decision with its own retention and DPDP implications — consent for recording must be separate from consent for the consultation itself.
Identity and consent checks to build into the flow
- Practitioner name and registration number visible to the patient
- Patient linked to an existing MRN, or a new MRN created with verified details
- Age confirmed, with an adult present where the patient is a minor
- Who initiated the consultation, recorded against the encounter
- Separate, explicit consent captured if the session is recorded
What may be prescribed remotely, and what may not
The Telemedicine Practice Guidelines group medicines for remote prescribing rather than allowing a blanket permission. Broadly, there is a category of relatively safe over-the-counter medicines that may be prescribed in any teleconsultation, a category permitted on a first video consultation, a category intended as add-on medication in a follow-up for a condition already assessed in person, and a prohibited list that must not be prescribed remotely at all. Narcotic and psychotropic substances sit firmly outside remote prescribing.
The mistake hospitals make is treating this as a training problem. It is a configuration problem. Your formulary should carry a remote-prescribing attribute per medicine, and the e-prescription screen in a teleconsultation encounter should behave differently from the same screen in a physical OPD encounter — surfacing the permitted set, warning on the restricted set, and blocking the prohibited set outright. A platform such as HealUDoc can drive this from the encounter type, so the same prescriber sees different constraints depending on how the patient is in front of them.
Pharmacy needs a matching rule. A prescription generated from a teleconsultation should be identifiable as such at the dispensing counter, so the pharmacist is not asked to interpret a remote prescription with the same latitude as a written one. This also gives your medical committee something concrete to audit each quarter: pull the teleconsultation prescriptions, check the category mix, and look for prescribers who are consistently at the edge.

Formulary attributes worth maintaining for remote prescribing
- Remote-prescribing category assigned per medicine, owned by pharmacy
- Encounter-type-aware prescribing rules rather than prescriber-level trust
- Hard block on prohibited categories, with no override path
- Teleconsultation prescriptions flagged for the dispensing pharmacist
- Quarterly audit of category mix by prescriber and specialty
Documentation parity with the in-person visit
A teleconsultation note is a medical record with exactly the same status as an OPD note, and it should look like one. History, the findings that were obtainable remotely, the limitations of the assessment, the working impression, the plan, and the safety-netting advice given to the patient. The limitations line is the one most often skipped and the one most valuable in retrospect — it is what documents that the practitioner knew a remote assessment could not exclude something and told the patient what to watch for.
Build the tele note as a template variant rather than a free-text box. The fields are mostly the same as an in-person note, with additions for the mode used, the reason the mode was adequate, and the advice given about when to attend in person. If your EHR supports encounter-type templates, this is a fifteen-minute configuration that permanently raises the floor on note quality.
Attachments deserve a deliberate policy. Patients will send photographs of rashes, wound sites, reports, and old prescriptions over whatever channel is easiest for them, which is frequently a personal WhatsApp number. Give them a supported upload path attached to the encounter, and make clear to clinicians that images received on a personal device are not part of the record until they are attached to it.

Payment, refunds and the tele-specific no-show
Teleconsultation almost always requires payment before the encounter, because there is no physical counter to collect at. That single fact changes your operational risk profile: you are now holding money for a service that may not happen, and every failure mode — the doctor running late, the patient's network dropping, the wrong number dialled — becomes a refund conversation. Decide the refund rules before launch and publish them at the point of booking, not in a policy page nobody opens.
The tele no-show is different from an OPD no-show and should be counted separately. A patient who does not answer is not the same as a patient who answered but could not be heard, and neither is the same as a consultation the doctor could not start on time. Define the attempt protocol — how many call attempts, over what window, on which channels — and record the outcome as a coded reason rather than a free-text comment. Without coded reasons you cannot tell whether your no-show rate is a patient problem or a connectivity problem.
Partial-service situations are the hardest to write rules for. If the doctor spoke to the patient for four minutes, determined that the complaint needs a physical examination, and advised an OPD visit, was that a consultation? Most hospitals settle on treating it as a completed consultation with a credit toward the in-person visit, which is defensible to both the patient and the finance team. Whatever you decide, decide it once and encode it, or your front-desk staff will improvise ten different answers.
“We stopped arguing about refunds the week we started recording why a tele consult failed. Half of what we had been calling no-shows turned out to be patients on a call we never successfully dialled.”
Where teleconsultation quietly breaks
The most common structural failure is scheduling teleconsultations into the same session as physical patients without protecting the time. A doctor with a full waiting room will not step away to take a video call, so the tele patient waits, gets a hurried encounter, and does not come back. Either block dedicated tele sessions, or place tele slots at the start or end of a session where the physical queue is not applying pressure.
The second failure is the handover gap. A teleconsultation that ends with an investigation order, a referral, or an advice to attend in person creates work that must land somewhere. If the order does not flow into the lab and the follow-up does not appear on a recall list, the encounter ends in a dead end and the patient is left to organise their own care. Every tele encounter should end with an explicit disposition, and each disposition should have a downstream owner.
The third is the technology floor. Teleconsultation depends on the weaker of two connections, and the hospital only controls one of them. Test the practitioner side properly — wired connection, decent microphone, a room that is quiet and private, a backup device — and accept that the patient side will vary. Give clinicians a documented fallback to an audio-only consultation, and record when it was used.
Launching without fragmenting the schedule
Start with the specialties where remote assessment is genuinely adequate for a meaningful share of the caseload: follow-up-heavy chronic care, report reviews, medication titration, psychiatry, and dermatology with good photographs. Trying to launch across every department at once produces a thin service in each and a lot of clinicians whose first tele experience was a bad one. Two departments running well are a better foundation than ten running badly.
Keep one appointment book. Teleconsultation slots should live in the same schedule as physical slots, marked by type, so that leave, session changes, and capacity reporting all work without a second system to maintain. HealUDoc dashboards can then show tele and physical volumes side by side, which is the comparison your medical superintendent will actually ask for.
Review the service at ninety days on clinical grounds rather than volume. What proportion of tele encounters ended in an advice to attend in person, and was that appropriate? Were prescriptions within the permitted categories? Did follow-ups close? A teleconsultation service that answers those three questions well is one you can safely expand.


