The Delhi son and the AIIMS PMJAY claim his father's cardiac surgery overlapped
Anmol's father complained of chest pain one June morning in 2024, standing in the kitchen of their Dwarka flat. By Wednesday, he was in AIIMS Delhi's cardiology ward. By Thursday, the surgeon said CABG—coronary artery bypass, quintuple. The surgery slot was sixteen days away. The cost was ₹2,18,000.
Anmol was 42, a supervisor at a municipal water-department depot, earning ₹38,000 monthly. His father was a retired railway employee on ₹19,500 monthly pension. Together they fell into a category that should have meant free surgery—they had coverage, in fact two coverages. But the two schemes were not designed to speak to each other.
Anmol discovered he could file under Ayushman Bharat PMJAY, the central scheme covering hospitalization up to ₹5 lakh. But because his father was a Delhi resident with income below ₹3 lakh, he also qualified for the Delhi Arogya Kosh, a separate territorial scheme with its own reimbursement promise. Both covered the surgery. Both had overlapping documents. Neither official he called could explain how to access both. One told him to pick. Another said the choice did not exist.
🗓️ The dual-scheme Delhi calendar
Ayushman Bharat was launched nationally in 2018, covering the country's poorest households. Delhi's AIIMS, Safdarjung, and Government Medical College all joined the network. A poor person could walk in with Aadhaar and walk out with a zero bill.
In 2020, Delhi launched its own scheme, the Delhi Arogya Kosh, to catch cases PMJAY might miss. DAK covered anyone in Delhi with income below ₹3 lakh and eligible diagnoses—including cardiac surgery. Same income-ceiling, different reimbursement track.
No AIIMS material explained how two schemes managed people eligible for both. The social-welfare desk said: file PMJAY first, then DAK if anything remained unpaid. But processing timelines were vague—eight to twelve weeks for PMJAY, twelve weeks for DAK through a separate online portal at health.delhi.gov.in. The DAK deadline was seventy-two days after discharge.
- 🏥
Day 0 — Discharge
AIIMS social-welfare begins PMJAY file preparation.
- 📨
Days 1–7 — PMJAY filed
AIIMS submits PMJAY claim; processing window begins.
- ⏰
Day 72 — DAK deadline
Last day to submit DAK through health.delhi.gov.in. Miss this, and DAK eligibility is forfeited.
- ₹
Weeks 8–12 — Reimbursement
PMJAY funds reach hospital; any gap covered by DAK.
Within this calendar, Anmol's uncertainty was not abstract. The AIIMS desk could only process one scheme at a time, meaning two separate visits, two separate queues, two separate document verifications. PMJAY might reimburse the full ₹2,18,000 and leave nothing. It might reimburse ₹1,80,000 and leave ₹38,000 as Anmol's debt. If it was the latter, the DAK claim would catch it—but only if Anmol filed before day 72.
The hospital had no obligation to wait. They could demand payment within thirty days of discharge.
⚠️ The thirty-day wall
AIIMS issued a bill notice on day 11: full charges due by day 30 of discharge. The notice said PMJAY and DAK could be filed separately, the hospital would cooperate once approved, but the patient remained liable until reimbursement arrived.
Anmol could not find forty-five hours to manage two separate filings—one with AIIMS (up to four visits if documents were rejected), one with the Delhi Health Department online portal (requiring registration, file upload, and income proof matching a tax return, even though his father was a pensioner who did not file).
His sister called on day 16. She had heard of a tool, the agent, helping people navigate scheme overlaps. A relative with a similar cardiac case had used it, filed both claims within a week, and was now waiting for DAK. "It's a chatbot," Anmol said, skeptical. His sister said it was not. "It asks you things. You upload documents. It tells you which scheme to file first."
That evening, Anmol opened the agent on his phone and described his situation. The response arrived in a minute.
🌗 The pivot: specific instruction
The agent asked for specifics: his father's age, pension amount, PMJAY enrollment date, PMJAY card number, hospital bill, pension structure (state or central), Delhi residence proof, and whether his father had claimed any government health scheme before.
Anmol answered from the living room, his father sleeping nearby. After twelve minutes and nine responses, the agent produced a single-page output titled "Two-Scheme Sequence for Your Case."
It said:
- File PMJAY first. Processing: 9–11 weeks. Expected reimbursement: ₹2,18,000 (full).
- File DAK on day 45. Do not file immediately. Wait until day 45, when PMJAY's trajectory is clear. Filing both immediately triggers duplicate-claim flagging, delaying both.
- Deadline buffer: Seventy-two days. Filing on day 45 left a twenty-seven-day safety margin.
The agent then listed documents for each scheme. PMJAY: Aadhaar, PMJAY card, discharge summary, itemized bill, bank proof. DAK: Aadhaar, Delhi residence proof (electricity bill), income proof (pension certificate), discharge summary, itemized bill, bank details.
"You're missing one," the agent typed. "Your father's income proof. PMJAY usually verifies income automatically, but if his registration is old, the AIIMS desk might ask for a pension certificate. Get it from the Railway Pension office now. Do not wait."
The agent noted: "It is day 16. Visit AIIMS on day 17, opening time. Tell them you are filing PMJAY only, DAK later. Do not mention both schemes now—it will add processing steps."
"मुझे डर था कि मैं कुछ गलत कर दूँगा, या कि दोनों स्कीमें एक दूसरे को रद्द कर देंगी। लेकिन जब एजेंट ने कहा कि पहले PMJAY करो, बाद में DAK, तो समझ में आ गया कि ये एक क्रम है, गलतफहमी नहीं।"— I was terrified I would do something wrong, or that the two schemes would cancel each other out. But when the agent explained PMJAY first, then DAK, it clicked—there was a sequence, not a mess.
On day 17, Anmol visited the AIIMS desk with the PMJAY documents. He did not mention Delhi Arogya Kosh. The desk verified his father's Aadhaar, cross-referenced the PMJAY card, and scanned the discharge summary and itemized bill. They noted that the pension certificate was pending. "Bring it when you have it," the desk officer said. "We will email it to PMJAY headquarters. Processing starts when the file is complete."
On day 22, Anmol received the pension certificate by email from the railway office. On day 23, he walked back to the AIIMS desk with the printed certificate. They scanned it, updated the PMJAY file status online, and told him to expect communication from PMJAY headquarters within ten business days. A reference number was issued. The PMJAY claim was now live.
On day 45, Anmol returned. No rejection letter had arrived from PMJAY—which meant it was still processing, not approved yet. But day 45 was the date the agent had specified for filing DAK. Anmol sat down at home, opened the Delhi Health Department portal, and registered his father's details. The portal asked for income proof, residence proof, and the discharge documents. He uploaded the pension certificate, the electricity bill, and the itemized hospital bill. A submission receipt was generated with a date: day 45 of discharge.
The receipt noted that the Delhi Arogya Kosh team would contact him within seven business days if any documents were incomplete.
No one contacted him.
🧭 Why the sequence matters: the burden of choice
The overlap between PMJAY and DAK is not a bug; it is the residue of two systems designed separately, now coexisting. Ayushman Bharat is national, designed to be comprehensive. Delhi Arogya Kosh is territorial, designed to catch what PMJAY might miss. Both schemes are blocked from reimbursing simultaneously—if they paid together, the hospital would be overpaid. So only one reimbursement processes at a time.
But the order matters. If PMJAY approves and pays the full amount, DAK never triggers. If PMJAY pays partial, DAK covers the gap and two agencies split the bill. If PMJAY rejects, DAK is the fallback. The timing of filing shapes which scheme responds to the actual need.
Through the agent's guidance, Anmol learned that the "one at a time" constraint could be managed by sequence and patience. File PMJAY immediately (the hospital is processing it), then file DAK at day 45, when PMJAY's trajectory is clear. Filing both immediately triggers duplicate-claim flagging, adding eight weeks to processing. Filing DAK first can cause PMJAY to refuse, citing an overlapping claim. The sequence is not optional—it is the only way both schemes can work together on behalf of a poor person earning ₹3 lakh annually.
"PMJAY पहले फाइल करो, फिर इंतज़ार करो। 45 दिन बाद DAK फाइल करो। यह क्रम है, क्योंकि दोनों एक साथ काम नहीं कर सकते, लेकिन एक के बाद एक काम कर सकते हैं। तुम 72 दिन के अंदर DAK फाइल करो, तो बैकअप रहेगा।"
(File PMJAY first, then wait. File DAK on day 45. This is the sequence, because both cannot work together, but they can work one after the other. If you file DAK within seventy-two days, you have a backup.)
What it does
- 🔍Verifies the eligibility criteria of each scheme and flags conflicts before you file.
- 🗂️Surfaces the exact document requirements for each scheme and tells you which are missing.
- 📞Recommends a filing sequence that minimizes duplicate-claim flagging and processing delays.
- ⏰Alerts you to deadlines and tells you when to file the second scheme to avoid forfeiture.
What it does not do
- 🔒Never submits claims on your behalf; you file every document yourself at the hospital desk or online portal.
- 💳Never enters your financial details into government systems; you provide the data, it verifies the logic.
- ✅Never decides which scheme to prioritize; it surfaces the consequence of each choice and leaves the decision to you.
For people like Anmol, clarity on sequence is clarity on survival. When he was sitting in the AIIMS waiting room on day 16, facing a thirty-day bill deadline, the choice between PMJAY and DAK felt like a binary—pick one, hope it works, and if it does not, you are sunk. The agent reframed it as a sequence: neither scheme replaces the other; they are designed to be tried in order, each one to catch what the previous one missed. That reframing is not trivial. It means the debt is not unavoidable. It means there is a legal mechanism to answer it. It means Anmol does not have to choose.
🌱 The small grace of knowing
By day 63, PMJAY headquarters approved the claim: ₹2,18,000 in full. The funds transferred to AIIMS Delhi's account the next day. The entire outstanding bill was credited. Anmol's liability became zero.
On day 68, the Delhi Arogya Kosh office emailed: his father's application was approved but would not reimburse further, as PMJAY had covered everything. The DAK approval letter came anyway—a backup that would not be needed.
Anmol's father recovered in the Dwarka flat, sitting on the living-room chair, walking to the balcony by month three, to the corner shop by month four. Cardiac follow-ups showed good graft function.
What Anmol carried from that summer was not medical relief—that came later. It was a smaller grace: the knowledge that the system had not been malicious, only disorganized. The two schemes were not designed to trap him; they were designed to keep each other in check. The choice that had felt forced upon him was no choice at all, once he understood the sequence. And the sequence, once named, was simple enough that a water-department supervisor with a phone and forty-five minutes could execute it alone. That simplicity—the reduction of chaos to clear steps—did not happen by accident. It came because someone asked the right questions, understood the risk, and told him what to do next.