How should a district set up teleconsultation at primary health centres?
Teleconsultation products are commonly designed around a person holding their own smartphone, choosing a doctor, and paying a private pharmacy for whatever is prescribed. A Primary Health Centre in a rural block is a different setting, and a district that procures on urban assumptions can end up with a service its own patients cannot use.
The decisions that determine whether a PHC teleconsultation service survives are rarely about video quality. They are about who books, who operates the device, what the pharmacy can dispense, what language the household reads, where a referral goes, and who holds the record.
Why urban telemedicine assumptions break at a PHC counter
Direct-to-consumer telemedicine assumes the patient is the device operator: they open the app, join the video call, read the summary, and choose a pharmacy. At a PHC, the person in front of the screen is often an ANM, a staff nurse, or a multipurpose worker rather than the patient. The patient may be elderly, may not read English, and may have arrived with a family member or an ASHA rather than by booking anything.
The prescribing model breaks too. An open drug database lets a consumer app suggest any registered molecule, because the patient is expected to buy it. A PHC dispenses from fixed public stock. If the e-prescription names something the pharmacy does not carry, the visit ends with a slip of paper and no medicine. An English-only prescription, however clinically correct, is also of limited use to a household that reads Telugu or another local language and has nobody nearby to translate dosage instructions reliably.
Who books the consultation, and why an assisted route matters
Self-service booking assumes smartphone ownership at the individual level. In a rural catchment the household phone may belong to a member who has migrated for work, and the person who needs the consultation may not be the person who can operate an app. Treating ASHA-assisted or ANM-assisted booking as a fallback, rather than a first-class access route alongside walk-in registration at the PHC, quietly excludes the patients the service is meant to reach.
An assisted booking route means a frontline worker who already knows the household can register the patient, explain what the consultation is for, prepare them with any records or medicine strips they hold, and be contactable if a home follow-up is needed. It also gives the PHC a named person to call when a patient does not arrive for a slot. This is a workflow decision to make before procurement, not a training add-on afterwards.
A bounded formulary versus an open drug database
An open, unbounded drug list is a reasonable design for a consumer service operating against retail pharmacies. It is a poor fit for a PHC, where the pharmacy stocks a defined, budgeted set of essential medicines. A service built around a verified, bounded formulary that maps to what PHCs actually stock gives the district two things an open list cannot. The first is procurement predictability, because the pharmacy officer can forecast demand from what consulting clinicians are permitted to prescribe. The second is prescribing consistency, because clinicians rotating through the same PHC work from one constrained list rather than each defaulting to their own preferred brand names.
Put the question to any vendor directly: is the formulary a fixed, verified list matched to public-sector stock, or an open database assuming retail pharmacy access? A follow-up matters as much: who updates the list, on what authority, and how quickly a district-specific change is reflected.
Prescription language and legibility
A prescription that is clinically accurate but unreadable to the household is a safety gap, not a paperwork detail. Bilingual e-prescriptions, in English and the local language, mean the household does not depend on finding someone to translate dose and duration before the first tablet is taken. Legibility matters in the plain sense too: an output a PHC pharmacist and a household member can both read without needing the prescribing clinician on the phone again.
Districts should also look at what the prescription carries beyond the drug name. Duration, review date, and whether the patient is expected back at the PHC are read later, at home, without a clinician present.
Referral workflow: the PHC medical officer stays the coordinating point of care
A service that lets a clinician refer a patient onward without looping back through the PHC medical officer creates a second, parallel record of that patient's care, one the PHC cannot see or act on. The safer design keeps the PHC medical officer as the coordinating point of care: referrals generated during a teleconsultation are visible to the PHC, and the PHC remains where the patient's overall record lives.
Referral is also incomplete without closure. A referral that is opened but never checked back on is not meaningfully different from no referral at all. The district should expect any workflow to record not just that a referral was made, but whether the patient reached the referral point, and who checks. The return leg matters too: the PHC needs a structured place to enter what the higher facility did and what follow-up is expected locally.
Connectivity, devices and the consultation space
Facility connectivity is the more controllable of the two ends. A design that assumes the patient will take a video call from home, on their own data plan, is exposed to a variable the district cannot manage. Treating the PHC itself as the consultation point uses a facility-owned device on a connection the facility already maintains, and removes the assumption that the patient can afford data.
A plan for connectivity failure matters as much as the connection: what happens when the call drops, whether the workflow can fall back to audio, whether it resumes with the same clinician, and whether the patient waits or is rescheduled. A district should ask to see that fallback demonstrated rather than described.
The physical space is part of the design. A consultation held at a shared counter within earshot of a waiting queue is a privacy problem regardless of how the software behaves, so districts should specify where the session takes place and who else is in the room.
Staffing and the assisting worker
Every teleconsultation slot involves at least three roles: the patient, the assisting worker at the facility, and the consulting clinician. Districts routinely specify the third and forget the second. The assisting worker's tasks need writing down, because they compete with everything else that person does: preparing the patient, entering identifiers correctly, holding the device, printing the prescription, explaining what happens next. The role needs a named backup, because a rota depending on one trained person stops when that person is transferred or on leave.
What a teleconsultation slot is not for
Scope needs stating in the district's own documents rather than left to the vendor. A teleconsultation slot is not an emergency channel, and the workflow should make that obvious to the assisting worker, so a patient needing immediate attention is moved to the emergency pathway rather than held for a scheduled call. It is also not a replacement for the PHC medical officer's judgement about who should be seen in person. Stating what is out of scope protects staff as much as patients, because a worker who knows a presentation is not for teleconsultation need not argue it at the counter.
What a district should decide before procurement
Several operational questions need answers before a contract is signed, not after the service goes live. Who owns the slot calendar for a PHC or block, and who resolves double-booking or clinician unavailability. What the protocol is when a consultation cannot be completed, and whether the patient is asked to wait, return, or be seen by the PHC medical officer instead. How a referral is recorded, and who confirms and logs its closure. Who owns the record afterwards, and for how long it is retained.
Two further questions are worth adding. What the district receives if the contract ends, in a form it can read without the vendor's software. And what the district itself will review to judge whether the service is working, agreed in advance rather than inherited from the platform.
These questions apply to any digital health procurement a district runs. The same discipline of specifying scope, evidence status and operational ownership before signing applies whether the tool is a teleconsultation platform or, for example, an AI-assisted chest X-ray screening tool being considered for a district TB programme.
A vendor-neutral decision checklist
The table below applies to any teleconsultation vendor a district is evaluating, independent of the platform under discussion.
| Decision point | Question to put to the vendor | Why it matters |
|---|---|---|
| Booking route | Is ASHA- or ANM-assisted booking a first-class workflow, or only a self-service app? | Determines whether patients without a personal smartphone can access the service |
| Formulary scope | Is prescribing limited to a verified list matched to public stock, or an open drug database? | Affects whether prescriptions can be filled at the PHC pharmacy |
| Prescription language | Is the e-prescription produced in the local language as well as English? | Affects whether the household can follow dose and duration unaided |
| Referral routing | Does a referral route back through the PHC medical officer? | Prevents a parallel record the PHC cannot see or act on |
| Referral closure | Is there an explicit step recording whether the referral was completed? | An open referral with no closure step is easy to lose track of |
| Slot ownership | Who controls the calendar, and who resolves clashes or no-shows? | Unclear ownership wastes clinician time |
| Connectivity fallback | What happens when the call drops or the clinician is unavailable? | Determines whether the patient waits, is rescheduled, or sees the medical officer instead |
| Assisting staff | How many staff per facility are trained, and who covers absence? | A single trained operator makes the service fragile |
| Out-of-scope cases | How does the workflow handle a patient who should not wait? | Keeps the emergency pathway separate from the teleconsultation queue |
| Record ownership | Who retains the consultation record, and for how long? | Affects continuity of care and later audit |
Phasing a district rollout
A block-level start is easier to correct than a district-wide launch. Beginning at a few facilities surfaces problems that only appear in use: identifiers entered inconsistently, prescriptions printed but not handed over, slots booked for patients nobody told, referrals opened with nobody assigned to close. What the district watches should be agreed before that phase starts and framed as operational review, not a claim about clinical benefit: whether booked slots are used, whether prescriptions are dispensed on site, and whether referrals are closed.
Records, consent and local governance
A teleconsultation generates a record that must sit somewhere defensible. The district should be clear about what is captured, where it is stored, who can see it, how consent is taken and documented at the facility, and what the retention arrangement is. These are governance decisions for the district and its legal advisors rather than defaults inherited from a product. Access control deserves attention, because shared logins at a counter make later audit meaningless.
Scope limits: who actually sets the rules
Telemedicine practice standards, prescribing rules for remote consultations and record-keeping requirements in India are set by the relevant national professional and regulatory authorities, and applied locally through state health department orders and programme guidance. These rules change over time, and their interpretation for a specific district or block is a matter for the district's own health administration and legal advisors, not for a software vendor. Clinoble does not set, certify or interpret telemedicine practice rules, prescribing regulations or record-keeping requirements, and nothing here should be read as legal or regulatory guidance. A district should confirm current requirements with the appropriate state and national authorities before finalising any design.
Where Clinoble fits
TeleVaidyam is Clinoble's teleconsultation product for rural Telangana primary care, currently in pilot deployment rather than wide-scale rollout. It is built around a verified formulary of 257 molecules rather than an open drug list, produces bilingual e-prescriptions, treats ASHA-assisted booking as a first-class access route alongside walk-in registration, and routes referrals through a workflow that keeps the PHC medical officer as the coordinating point of care. It is designed for PHC-anchored primary care, not urban direct-to-consumer telemedicine and not a disease-programme management system. More detail is on the TeleVaidyam page.
Clinoble Innovations Private Limited is based in Hyderabad, Telangana; its founder and director is Dr. Jaideep Rao M., MBBS, MD Community Medicine.
Clinoble also builds Aarogyam365, a live bilingual English and Telugu family preventive-health platform organised around monthly actions, and TB F.I.R.S.T, a bilingual tuberculosis cascade tool. See the Aarogyam365 page and the TB F.I.R.S.T page.
Founder and director: Dr. Jaideep Rao M., MBBS, MD Community Medicine.