The ration card wasn't in the database. She paid ₹46,000 out of pocket.
🧑⚕️ Swati, 38, Mumbai. Mother needed cataract surgery, ₹46,000 cost. MJPJAY card valid. Hospital desk said "ration card not in current database." Denial. Swati paid privately. Fourteen weeks later, reapplication approved. Mother was eligible all along. Regional databases weren't synced.
🚨 The problem
Eligibility databases don't sync across regional MJPJAY offices. Ration cards valid in one district may be "not found" in another office's database. The same family is eligible and ineligible depending on which office checks. Payment is demanded. Refund takes weeks.
🚀 How GabFORGE helped
Swati photographed the denial letter, the ration card, and the reapplication approval.
- 🔍 Found the database-mismatch clause. Read MJPJAY protocols and found: eligibility can be manually verified across all district offices if one office's database shows missing record. Manual verification form exists.
- 💬 Named the reapplication pathway. MJPJAY State Health Assurance Society, manual verification request. Provides eligibility confirmation. Hospital then processes retroactive cashless claim.
- 📞 Provided the appeal process and expected timeline. 10–14 days for manual verification, then 5–7 days for hospital reprocessing.
Swati filed manual verification. Approved. Hospital reprocessed claim. ₹46,000 refunded.
🇮🇳 Why this matters
Regional databases have synchronization gaps. The same person is eligible in one database, invisible in another. Manual verification pathways exist to bridge these gaps—they're just not offered unless someone asks.
The long version has the denial, the out-of-pocket payment, the reapplication approval, and the moment Swati realized database gaps cost money.