The Clinical Frontier · 2 October 2026 · Issue 016 India discharges tens of millions of patients from hospitals each year. The summary is the last bottleneck before the door.
In this issue
- Claude Sonnet 5.5, released September 28, generates output more than 30% faster and costs up to 30% less per task than Sonnet 5, at identical per-token pricing ($2 input, $10 output per million tokens). Anthropic explicitly positions it for “polished documents, slides, and spreadsheets.”
- Discharge summaries are one of the highest-volume, legally mandated clinical documents in any hospital. In India, they are also the primary record that Health Information Providers must share on ABDM for patient-consented record access.
- Speed and cost matter here in ways they do not for rare, specialist documents: a single secondary-care hospital may generate 200 to 500 discharge summaries on a busy day, and the bottleneck is almost always the junior resident writing them after the attending has already left the ward.
- Prompt caching changes the cost structure for template-heavy documents: a cached ABDM section-heading schema and standard discharge template costs $0.20 per million tokens on cache reads, a 90% reduction from the uncached input price.
What shipped
Claude Sonnet 5.5, released September 28, 2026, is Anthropic’s second model in the Claude 5.5 family. Anthropic positions it as a faster, more cost-efficient complement to Claude Opus 5.5 for everyday tasks, document creation, and agentic workflows.
Key specifications verified from the Anthropic model page:
- Output speed: 30%+ faster than Sonnet 5
- Per-task cost: Up to 30% less than Sonnet 5 (token efficiency; per-token pricing unchanged)
- Per-token pricing: $2 per million input tokens, $10 per million output tokens
- Prompt cache read price: $0.20 per million tokens
- Context window: 1 million tokens
- Computer use (OSWorld 2.1): 80.1%
- Agentic coding (Terminal-Bench 4.0): 70.6%
- Knowledge work (GDPval-AA v2.1): 1,844 Elo
The model page states it directly: “Sonnet 5.5 is strongest at well-scoped everyday tasks, fixing bugs, and creating polished documents, slides, and spreadsheets.” In healthcare, the discharge summary is exactly this class of task: well-scoped inputs (admission notes, lab values, imaging summary, medication reconciliation), a fixed output schema, and a tight window to produce it.
Healthcare organizations can access Sonnet 5.5 through the Anthropic API. Organizations working in clinical or life sciences contexts can apply to Anthropic’s Life Sciences Verification Program for access to expanded capabilities.
The discharge summary problem in India
India’s secondary and tertiary hospital sector is large and growing fast. India has approximately 1.3 hospital beds per 1,000 population, well below the global median, which means the hospitals that exist run at high occupancy, with bed turnover a critical efficiency metric.
Every inpatient discharge legally requires a discharge summary under the Clinical Establishments (Registration and Regulation) Act. The summary must cover: admission diagnosis, clinical course, investigations, final diagnosis (with ICD codes), procedures performed, discharge medications, follow-up instructions, and advice on return for emergency care.
Under the Ayushman Bharat Digital Mission, hospitals that are Health Information Providers must push a structured FHIR-compliant DischargeSummaryRecord to the patient’s ABHA-linked Health Information Exchange following discharge, when the patient provides consent. This requires the summary to be not just legible prose but machine-readable structured data: ICD-11 for diagnoses, SNOMED-CT for procedures, LOINC for lab observations, and the ABDM FHIR R4 profile section structure.
The gap in most Indian hospitals today:
- The production gap: Summaries are written by junior residents, often after the patient has already left the ward. Errors and omissions are common.
- The structure gap: Plain-text summaries in a hospital’s own format are not the same as ABDM-compliant FHIR records. The mapping step is usually manual.
- The language gap: The clinician writes in English; the patient needs instructions in Hindi, Marathi, Tamil, or Kannada. Translation is rarely done systematically.
- The volume gap: A tertiary hospital discharging 400 patients a day has no staffing model that allows every summary to get 20 minutes of a senior clinician’s attention.
How Sonnet 5.5 fits the workflow
A Sonnet 5.5-powered discharge summary module fits into the existing EMR at two points.
At summary generation, the model takes structured inputs already in the EMR: admission notes, progress notes, final diagnosis codes, procedure log, medication list, and lab summary. It produces a structured draft that:
- Fills the ABDM FHIR DischargeSummaryRecord section headings (Reason for Admission, Clinical Findings, Discharge Diagnosis, Medications on Discharge, Follow-Up Plan, Emergency Instructions)
- Applies ICD-11 to diagnoses and SNOMED-CT to procedures from the EMR code lists, so the ABDM push is ready without a separate coding step
- Flags gaps (missing post-discharge medication duration, absent follow-up date) as inline prompts for the treating physician to resolve before signing
The physician reviews and signs, not generates from scratch. Time at the ward drops from 15 to 20 minutes per summary to a 3 to 5 minute review and sign. At 400 discharges per day, saving even 10 minutes per summary frees 4,000 minutes (66 hours) of physician documentation time daily, which can be redirected to clinical care.
At patient communication, the model takes the signed summary and produces:
- A plain-language explanation of the diagnosis in English and one or more Indic languages (Hindi, Kannada, Tamil, Marathi), matched to the patient’s registered language preference in the ABHA profile
- A structured follow-up reminder formatted for WhatsApp or SMS: next appointment, medications with timings, red-flag symptoms to return for immediately
- A FAQ block for the most common patient questions about their condition, grounded in the discharge instructions
The 1-million-token context window means all of this can happen in a single call: the full EMR extract, the ABDM section schema, the ICD and SNOMED code lists, the hospital’s standard boilerplate, and the language-specific term glossary, all held in context at once.
The cost math for ABDM-scale
At $2 per million input tokens and $10 per million output tokens, a single discharge summary generation call (50,000 token context: EMR notes, code lists, schema template; 2,000 token output) costs approximately $0.12 with no caching.
With prompt caching, the hospital loads its standard ABDM template, ICD-11 excerpt, and SNOMED-CT procedure list once as a cached prefix. At $0.20 per million cached input tokens, the same 40,000 template tokens cost $0.008 per call instead of $0.08. Variable patient data (10,000 tokens) is the only uncached input: $0.02 per call. Output remains $0.02. Total per-discharge cost with caching: approximately $0.048, or roughly Rs 4.
A 400-bed hospital generating 400 discharge summaries per day spends approximately Rs 1,600 per day on generation API costs. Monthly: approximately Rs 48,000, well within the operational budget of any hospital that currently employs a ward clerk for documentation.
The 30% per-task cost improvement in Sonnet 5.5 versus Sonnet 5 means this monthly figure is approximately 30% lower than the previous generation, before any caching optimization.
The DPDP and data governance layer
Every discharge summary generation call processes personal data as defined under the Digital Personal Data Protection Act 2023: name, ABHA ID, diagnosis, medication, and clinical history. Before building this workflow:
- Consent: ABDM’s consent artefact must be in place before pushing a DischargeSummaryRecord to the HIE. The same consent governs whether the patient’s data can be processed for AI-assisted generation.
- Data residency: Calls to the Anthropic API route through cloud infrastructure. A hospital subject to data localisation requirements under DPDP must confirm the API routing and retain a Data Processing Agreement with Anthropic.
- Data minimisation: Only the fields needed for the summary (not the full longitudinal EMR) should be in the generation call. Progress notes from prior admissions are not needed; structured final diagnosis and medication data are.
- Audit logging: Every generation call should be logged with a timestamp, summary ID, and clinician-sign-off record so any dispute about what the AI produced versus what the physician signed can be resolved.
Anthropic’s healthcare page notes that Claude is being used by health system partners for “clinical documentation at scale, saving clinicians millions of hours annually.” The Life Sciences Verification Program gives healthcare organisations access to expanded capabilities and Anthropic’s safety review for clinical contexts.
The takeaway
Claude Sonnet 5.5 is not a new model category for discharge summaries. It is a cost and speed improvement on a model that was already capable. That distinction matters because the case for AI-assisted discharge documentation in India was always economically marginal: too expensive for routine use at high volume.
The 30% speed increase addresses the ward bottleneck: the summary must be ready before the patient leaves, not hours later. The 30% per-task cost reduction with prompt caching addresses the volume economics: hundreds of summaries per day at a cost comparable to existing documentation staff.
The ABDM FHIR requirement turns this from a convenience into an infrastructure question. Every hospital that wants to be a compliant HIP eventually needs a pathway from structured EMR data to a FHIR-compliant DischargeSummaryRecord. A model that generates the structured draft and flags ICD-11 gaps in the same step as writing the narrative is the right architectural choice for that pipeline.
The next issue will cover the latest from the frontier model companies. Follow along at hcitexpert.com.