The pandemic normalised the video consultation. What followed was less dramatic and more interesting: telemedicine settled into the parts of care where it genuinely fits, which turned out to be follow-ups, chronic disease management, mental health, dermatology, and second opinions. First-time diagnostic consults for undifferentiated symptoms largely went back to the clinic, and reasonably so.
For anyone building in this space, the useful question is no longer whether remote care works. It is which parts of the care pathway it serves, and what the platform has to do around the call to make those work.
The Call Is the Easy Part
A working video layer is close to a commodity now. The hard requirements sit at the edges.
- Bandwidth resilience. A meaningful share of Indian consultations run on a mobile connection with variable throughput. Platforms need adaptive bitrate, graceful degradation to audio-only without dropping the session, and a reconnect that restores state rather than restarting the consult.
- Low-friction entry. Requiring a patient to install an app before their first consult loses a measurable fraction of them. A browser-based join from a link works better, particularly for older patients being helped by a family member.
- Pre-consult capture. Symptoms, current medications, vitals from a home device, and uploaded reports collected before the call turn a 12 minute consult into 12 minutes of clinical time rather than eight minutes of history taking.
- Prescription at the end of the call. Under the Telemedicine Practice Guidelines, prescribing is permitted with defined limits by drug category, and the prescription must be issued in a form the patient can present at a pharmacy. If that step lives outside the platform, adoption suffers.
- Records that persist. The consultation note, prescription and any shared reports need to land in the same record as the patient’s in-person visits, ideally as FHIR resources linked to their ABHA address.
Regulation Sets Real Boundaries
India’s Telemedicine Practice Guidelines, issued in 2020 and now part of professional conduct expectations, define what a registered medical practitioner may and may not do remotely. Drugs are grouped into lists, with an over-the-counter and low-risk category prescribable in a first consult, and restricted categories excluded entirely from teleconsultation. Practitioners must identify themselves and verify the patient’s identity, and they may refuse to consult remotely where an in-person examination is clinically necessary.
Platform design should make the compliant path the easy path. Restricted drugs should not appear in a first-consult prescribing interface at all. Identity verification should be part of the join flow. Consent to teleconsult should be captured and stored, and under the DPDP Act, that consent record needs to be specific and withdrawable.
Continuity Is the Differentiator
The telemedicine products that retain users are the ones that treat a consult as one event in an ongoing relationship. That means scheduled follow-ups created automatically from the clinical plan, medication adherence prompts between visits, remote monitoring data flowing in from glucometers or blood pressure cuffs, and an asynchronous message channel so a patient with one small question does not need a whole new appointment.
Asynchronous care is underused. For a stable hypertensive patient, a structured check-in with a reading and three questions is often better medicine than a video call neither party particularly wanted.
At Invexa, remote care platforms are built as part of a continuous record rather than as a standalone video product, since the value shows up between consultations more than during them.