Discharge Summary Format India: Cleaner, Faster Cashless

A discharge summary is the one document everyone reads after the patient goes home. The next doctor reads it to continue care. The patient reads it to know what changed. And the cashless desk reads it to close the claim. When it is clear and complete, all three of those happen fast. When it is thin, contradictory, or copied from the last patient, every one of them stalls.

This guide covers what a complete discharge summary actually contains in India, the format that holds up under a TPA's eye, and the part most people get wrong about what a good summary can and can't do for a cashless claim.

Key takeaways

• A complete discharge summary carries identifiers, admitting and final diagnoses, course of stay, procedures with dates, discharge medications, and follow-up. Completeness beats any particular template.
• The IRDAI Master Circular (29 May 2024) sets a three-hour clock for final discharge authorisation. The summary is the document that request rides on.
• A clean summary does not stop a claim being rejected for paperwork, because IRDAI bars rejecting claims for "want of documents." The real benefit is speed: an approvable-on-first-read request that clears the clock without queries.
• The summary is only as good as what got written during the stay. Capturing the encounter well is upstream of writing the summary well.

Sources: IRDAI Master Circular on Health Insurance Business, 29 May 2024 (IRDAI/HLT/CIR/MISC/77/05/2024); MoHFW EHR Standards for India, 2016.

What a complete discharge summary contains

Strip away the house style and every good discharge summary answers the same five questions: who, why, what was found, what was done, and what next. The fields below are the ones that make those answers verifiable. NABH accreditation guidance, the MoHFW EHR Standards 2016, and day-to-day TPA practice all converge on roughly this set.

• Patient and admission identifiers. Name, age, sex, hospital number, admission and discharge dates, treating consultant. This is what ties the summary to the rest of the record and to the pre-auth already on file.
• Diagnoses. Both the admitting diagnosis and the final diagnosis at discharge. If they differ, the summary should make sense of why; a final diagnosis that appears from nowhere is the kind of gap that triggers a query.
• Course of stay. A short, honest narrative of what happened between admission and discharge. Key events, the response to treatment, any complications. Not a transcript, a clinical story.
• Procedures and investigations. What was done, with dates, and the findings that mattered. A procedure billed but absent from the summary is a classic diagnosis-treatment mismatch.
• Discharge medications. Drug, dose, route, frequency, and duration. This is the part the patient and the next prescriber actually act on, so vagueness here has real downstream cost.
• Condition at discharge and follow-up. How the patient is leaving, what to watch for, when and where to come back. The instruction that closes the loop on care.
• Authentication. The treating doctor's name and signature. An unsigned summary is, for medico-legal purposes, an unfinished one.

The order can vary. The completeness cannot. A summary missing the indication or the final diagnosis is not a formatting problem, it is a hole in the clinical record, and it reads as one to anyone who has to rely on it later.

Is there a standard discharge summary template in India?

People search for a blank template, paste it in, and assume the job is done. The template is the easy part. There is no single statutory discharge summary format mandated nationally, but the expected fields are remarkably stable across NABH guidance, the EHR Standards 2016, and what TPAs actually look for. The hard part is what goes inside the fields.

A template gives you headings. It does not give you a final diagnosis that matches the procedure, or a course of stay that explains the findings, or discharge medications that line up with what was prescribed during the admission. Those come from the clinical record being complete in the first place. A beautiful template wrapped around a thin record is still a thin summary. So treat the format as table stakes and put the effort where it counts: making sure the content is complete and internally consistent before the patient walks out.

Why the discharge summary decides how fast cashless clears

Here is the chain, because it is worth seeing literally. At discharge, the hospital's insurance or TPA desk requests final authorisation. That request is built from the discharge summary: the final diagnosis, the procedures done, the course of stay. The insurer or TPA reads it and decides. Approve, query, or hold.

The IRDAI Master Circular on Health Insurance Business, dated 29 May 2024, put a hard clock on that decision. Final discharge authorisation has to be granted within three hours of the hospital's request, and if the insurer drags past three hours, it bears any extra hospital charges from the delay. Three hours sounds generous until a query lands in it. A summary that prompts "please clarify the indication" or "diagnosis does not match the procedure billed" spends that window in back-and-forth, and the patient sits in the bed waiting to leave.

The summary that clears the clock is the one that was complete and consistent the first time. Speed rewards clean summaries and punishes muddled ones. That is the whole mechanism, and the next section is about being exact on what it does and does not mean.

The part everyone gets wrong about documents and denials

This is where vendors oversell and clinic staff get a rule backwards, so read it carefully. A clean discharge summary does not stop your cashless claim from being rejected for paperwork. It cannot, because the rule does not allow rejection for paperwork in the first place.

The IRDAI Master Circular bars insurers from rejecting a claim for "want of documents." Required documents are meant to be sorted at the proposal stage, and where something is missing for a claim, the insurer or TPA is expected to collect it from the hospital, not bounce the claim back at the patient. So "complete your discharge summary and your claims stop getting rejected for missing papers" describes a problem the rules already forbid. It is not the benefit on offer.

The real, narrow, honest benefit is speed. Because a complete and internally consistent summary gives the pre-auth desk a request that is approvable on first read, it is what lets that request clear the three-hour clock without a round of queries. Faster discharge authorisation. Fewer documentation back-and-forths at the bedside. That is the mechanism, and it is worth being precise about, because the loose version of the claim is both wrong and easy to disprove.

For the wider picture of how clinical notes feed cashless approvals and where they break, see how notes affect cashless approvals. For who actually sits at the cashless desk and why a TPA cannot reject a claim on its own, see the TPA full form explained.

The summary is only as good as what got written during the stay

Here is the upstream truth a template will never fix. A discharge summary is assembled from the clinical record of the admission. If the daily notes were thin, if the indication was never clearly documented, if the procedure findings live only in someone's memory, then the summary gets reconstructed at discharge from fragments. That reconstruction is where mismatches and gaps creep in, and it usually happens under time pressure with the next patient already waiting.

So the best place to improve discharge summaries is not the discharge desk. It is the encounter itself. A record that was captured completely and consistently during the stay produces a summary that practically writes itself, and one that holds together when the TPA reads it. A record that was captured in scraps produces a summary held together with assumptions.

Where ambient documentation fits

AI Scribe by Patient Square is an ambient AI medical scribe that listens during the visit and hands back a structured SOAP note, ICD-10 suggestions, and a prescription draft — ready to review and sign about two minutes after the visit. It does not write the discharge summary for you, and it does not touch any TPA, insurer, or claims system. There is no claims integration, on the roadmap or off it. What it does is make the clinical record underneath the summary more complete, because the diagnoses, findings, and plan get captured while the encounter is happening instead of being reconstructed afterward.

It works alongside your existing EHR. The record still lives where it already lives; the scribe fills the gap between what was said in the room and what ends up written down. A few things matter for an Indian setting specifically. The scribe captures English, Hindi, and 20+ Indian languages, including the mid-sentence Hindi-English mixing of a real consult, and the note always comes back in clean clinical English. The prescription draft passes a deterministic safety screen: drug-interaction, renal, and pregnancy checks that re-run at sign time and hard-block unsafe combinations unless you override with an attestation. Visit audio is processed in memory and discarded the moment the note drafts; there is no recording sitting on a server, which is the cleaner answer under the DPDP Act 2023.

On pricing, Solo is ₹1,199 per clinician per month on launch annual billing, ex-GST; add 18% GST and the invoice lands at about ₹1,415 a month. Group tier is ₹999. Same product across tiers, no feature gating, with a 7-day full-featured trial and no card required. The full breakdown is on the pricing page.

In short

A discharge summary does three jobs at once. It carries care forward to the next doctor, it tells the patient what changed, and it closes the cashless claim. The format is the easy part. Completeness and internal consistency are what actually carry it. The IRDAI clock rewards a summary that is approvable on first read and punishes one that prompts a query. Be precise about why, though. The benefit is speed, not protection from a paperwork rejection that the rules already forbid.

And the real fix sits upstream. A summary is only as good as the record it is built from, and the record is only as good as what got captured during the encounter. If your summaries arrive thin because there was no time to write them properly during the stay, the fix is better capture at the point of care, not a nicer template. Book a short demo and watch a real consult turn into a structured note, or read the pricing first. Either way, fix the layer that actually feeds the summary.