OperationsLive · in the productQueue & board

eSanjeevaniLink

The national teleconsult, typed in once and attached to the right visit.

Offered in: India only.

Get eSanjeevaniLink Open the appAvailable nowHow pricing works →

What it is

A person reads the consult on e-Sanjeevani and records it here, against the reference the national platform gave it — and that reference is a unique index, so recording the same consult twice is the same row rather than a second history. Once somebody decides which local visit it belongs to, it attaches to that visit. MedAppz holds no e-Sanjeevani credential: nothing is fetched and nothing is sent, and the first card on the screen says so rather than leaving a person waiting for a sync.

Who uses it: Built for: Every specialty
Reads: Encounters, patient record
Writes: Linked consults
Never: It does not connect to e-Sanjeevani.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record; operational history stays queryable.

How it works

Read the first card before anything elseWhat this bridge does, and does not says that this deployment holds no e-Sanjeevani credential, and lists what connecting one would need; nothing here is fetched or sent.
Record the consult you read on the national platformThe e-Sanjeevani reference, whether it was OPD, specialist or follow-up, the date, the doctor, the hub facility, and what was said, advised and prescribed.
The reference is what stops a parallel historyOne national reference is one row: a unique index on it means recording the same consult twice is the same row, which is the property a link table actually owes anybody.
Attach it to the local visitAttach to a visit asks for the visit id, and a visit belonging to a different patient, or a consult already attached, is refused.
Work the ones still looseNot yet attached filters the list down to the consults with no local visit against them, and Show all puts them back.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It does not connect to e-Sanjeevani.

There is no credential, no endpoint and no sync in this product — a person copies what the national platform shows, and the app’s own connection screen answers “not configured” in every deployment there is.

It does not attach a consult to a visit belonging to somebody else: the link is written by a statement that joins the visit to the same patient, so a stranger’s visit updates nothing.

AI in eSanjeevaniLink

AskQuestions about what is on screen — “What needs attention in eSanjeevaniLink today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

eSanjeevaniLink — e-Sanjeevani — Type a national telemedicine consult into the local record, once — 01e-Sanjeevani — Type a national telemedicine consult into the local record, onceCaptured from the running demo clinic

01e-Sanjeevani — Type a national telemedicine consult into the local record, onceCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 2

CaseNotes Patient Registry

See the whole clinic →

Questions clinics ask

What does eSanjeevaniLink do?

The national teleconsult, typed in once and attached to the right visit. A person reads the consult on e-Sanjeevani and records it here, against the reference the national platform gave it — and that reference is a unique index, so recording the same consult twice is the same row rather than a second history. Once somebody decides which local visit it belongs to, it attaches to that visit. MedAppz holds no e-Sanjeevani credential: nothing is fetched and nothing is sent, and the first card on the screen says so rather than leaving a person waiting for a sync.

What data does eSanjeevaniLink read and write?

eSanjeevaniLink reads encounters, patient record and writes linked consults. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does eSanjeevaniLink deliberately not do?

It does not connect to e-Sanjeevani. There is no credential, no endpoint and no sync in this product — a person copies what the national platform shows, and the app’s own connection screen answers “not configured” in every deployment there is. It does not attach a consult to a visit belonging to somebody else: the link is written by a statement that joins the visit to the same patient, so a stranger’s visit updates nothing.

What happens to our data if we uninstall eSanjeevaniLink?

All clinical data stays in the record; operational history stays queryable.

Is eSanjeevaniLink available today?

Yes — eSanjeevaniLink is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Where is eSanjeevaniLink offered?

eSanjeevaniLink is offered in India only: it is built on that market's own systems and rules.

Want to see eSanjeevaniLink running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Operations

All 143 →