The Clinical Frontier · 29 September 2026 · Issue 013 A context window large enough to hold an entire patient record changes what AI can do at the moment a coder reads a discharge summary.
In this issue
- GPT-6 Astra, the most capable model OpenAI has broadly deployed, is now available to Healthcare users. Its 1,050,000-token context window is large enough to ingest a complete inpatient record in a single call.
- The OpenAI Agents API, launched September 10, 2026, provides the orchestration layer to turn a frontier model into a repeatable, auditable ICD-10 coding pipeline.
- PM-JAY covers approximately 55 crore beneficiaries across roughly 29,648 empanelled hospitals. Coding errors that cause NHCX claim denials are a measurable, addressable revenue problem at every empanelled facility.
- India has a structural shortage of certified ICD-10 coders. AI-assisted coding is one of the highest-value, lowest-controversy automation targets in Indian health IT.
What shipped
GPT-6 Astra is the most capable model OpenAI has broadly deployed. OpenAI describes it as state-of-the-art for computer use, browsing, software engineering, cybersecurity, science, and professional work. The model carries a 1,050,000-token context window with up to 128,000 output tokens and a knowledge cutoff of April 30, 2026. Access is rolling out to Plus, Pro, Business, Enterprise, Healthcare, and Edu users in addition to the OpenAI API.
The Agents API, launched September 10, 2026, provides a managed cloud harness for building agents that can plan work, use tools, coordinate subagents, and run reliably over long periods. OpenAI built the Agents API to give developers the same infrastructure that powers its own Codex system: context compaction to let agents work across multiple context windows without losing state, file and code environments, and subagent routing for parallelising work.
Together, the two products give Healthcare-tier customers a frontier intelligence layer and a production-ready orchestration framework in one vendor platform. For workflows that involve reading long unstructured documents and producing structured coded outputs, this combination is directly applicable.
The India coding problem
PM-JAY, India’s government health insurance scheme, covers approximately 55 crore beneficiaries across 12.37 crore families, the bottom 40 percent of India’s population by income. As of September 2024, the National Health Authority has empanelled roughly 29,648 hospitals, including 12,696 private hospitals, to provide cashless secondary and tertiary care under the scheme.
Every inpatient claim flowing through NHCX, the National Health Claims Exchange, requires:
- ICD-10 diagnosis codes for the principal diagnosis and all significant comorbidities
- Health Benefit Package (HBP) codes from the NHA’s defined package list for the primary procedure
- Supporting clinical documentation that matches the codes submitted
NHCX processes claims through automated adjudication. A claim that presents an unspecified ICD-10 code (one that ends in a non-specific digit because the coder could not locate the precise code), sequences the principal diagnosis incorrectly, or mismatches the procedure HBP code with the diagnosis is flagged for review or denied before a human adjudicator sees it.
The underlying cause is structural: India has a significant shortage of certified medical coders for ICD-10. ICD-10 coding is skilled work. Mapping a clinician’s free-text discharge summary, which may span multiple pages and include abbreviated terminology, brand-name drugs, conflicting entries from different treating physicians, and varying levels of documentation specificity, to a precise ICD-10 code set requires clinical knowledge, coding guideline familiarity, and case-specific judgment. India’s health IT workforce pipeline has not scaled fast enough to meet the demand generated by PM-JAY’s expansion.
The consequence is straightforward: a share of PM-JAY claims reach NHCX with under-specified or incorrect codes and are denied or suspended. Each denied claim requires re-work: re-coding, re-submission, re-adjudication. For a district hospital processing several hundred PM-JAY cases per month, this is a real operating cost and a cash-flow problem.
Why the context window is the key variable
Medical coding errors frequently arise not from ignorance of the code but from incomplete reading of the record. A coder working under time pressure may code from the discharge summary alone and miss:
- A complication documented in the operation notes but not carried forward to the summary
- A comorbidity mentioned in nursing notes that upgrades the principal diagnosis to a more specific code
- A laboratory value in the reports that changes the coding of a metabolic condition
At 1,050,000 tokens, GPT-6 Astra can receive the complete hospitalization record in a single API call. A typical inpatient record, including the discharge summary, daily progress notes, operation notes, anaesthesia record, nursing notes, lab reports, and imaging reports, fits comfortably within this window. The model processes the complete record, not a truncated version, before suggesting codes.
This matters because ICD-10 coding guidelines specifically require coding to the highest level of specificity supported by the documentation. A coder who misses a comorbidity because they did not read the full record is not making a judgment error. They are making an information access error. A model with a 1-million-token context window does not make the same error.
Building the pipeline with the Agents API
The Agents API adds the orchestration layer that turns a single model call into a repeatable coding workflow:
Step 1: Ingest. Pull the full patient record from the hospital information system or EMR. Strip identifying fields (name, ABHA ID, phone number) before sending to the API, keeping only the clinical text. This is the key DPDP Act data minimisation step.
Step 2: Extract. A first GPT-6 Astra call extracts all diagnoses, procedures, complications, and comorbidities as structured clinical concepts, with the supporting text passage for each.
Step 3: Code. A second call maps each extracted concept to its ICD-10 code, the relevant coding guideline that applies, and the supporting phrase in the documentation. For PM-JAY cases, a third call maps the primary procedure to the relevant NHA Health Benefit Package code.
Step 4: Check. A verification step confirms that every code is traceable to explicit supporting documentation and that principal diagnosis sequencing follows ICD-10 guidelines.
Step 5: Route. Cases where confidence is high go to the coder’s review queue as pre-coded suggestions. Cases with low confidence, ambiguous documentation, or conflicting entries in different sections of the record go to the expert coder queue for full manual review.
Each step is logged with inputs, outputs, and the specific text evidence used. This creates the audit trail that NABH accreditation processes require and satisfies the DPDP Act’s accountability obligations.
The DPDP Act constraint
A complete patient record sent to an external API is sensitive personal data under India’s Digital Personal Data Protection Act 2023. Any platform deploying GPT-6 Astra for coding automation must address three obligations before the first API call:
- Data minimisation. Send only the clinical text required for coding. Strip the ABHA ID, patient name, phone number, and other identifiers from the document before it leaves the hospital network. Coding does not require the patient’s identity; it requires the clinical facts.
- Data processing agreement. Under DPDP, the hospital is the Data Fiduciary and the API provider is a Data Processor. A documented data processing agreement covering purpose limitation (coding only), retention limits, sub-processing controls, and security standards is mandatory.
- Audit logging. Log every API call with the case reference (not the patient name), the operator ID, the timestamp, and the output. These logs support both DPDP accountability audits and clinical quality reviews.
These obligations are not specific to AI or to OpenAI. Any system that sends patient records to an external service for processing carries the same obligations. The difference with a frontier model integration is scale: a system that codes thousands of records per day generates a corresponding volume of data processing events, and the DPA structure must accommodate that scale from the design phase.
The takeaway
GPT-6 Astra is now available to Healthcare-tier customers through the OpenAI API. A 1,050,000-token context window addresses the core failure mode of coding from incomplete record review. The Agents API provides the orchestration layer to build a step-by-step, auditable coding pipeline rather than a single monolithic model call.
For Indian health IT teams at PM-JAY empanelled hospitals, AI-assisted ICD-10 coding is one of the clearest immediate ROI cases in the stack: the problem is measurable (coding-related denial rate), the workflow is structured (read record, produce codes, verify, submit), and the outcome is auditable (re-submission rate before and after). A 30-day pilot at a single facility, with coding-related denials as the primary metric, is a practical starting point.
The technical implementation is the easy part. The DPDP data handling design and the human review workflow for low-confidence cases are what the pilot needs to validate first.
The Clinical Frontier is a daily briefing from HCITExperts. More tomorrow.