You own the data
You are the data fiduciary under the DPDP Act. Zyanta is a processor with no standing access to production.
Claims Ignite · cashless pre-authorisation
Today a pre-authorisation can take a family from six hours to two days. Claims Ignite is built to get a complete file to the insurer in minutes: one reference, three photos, and the claim on the patient's own phone.
The problem
Both middle numbers are true at once. Everything before a complete file reaches the insurer happens on the hospital's side: the walk to the desk, the search for documents, the doctor's form, the typing, the queries. Nobody times those hours.
The patient first
The flow
The patient gets a reference number straight away. The doctor sees them appear in their own queue.
Policy, Aadhaar and PAN are read, cross-checked and prefilled. A mismatch is shown, never silently accepted.
Typed or photographed. The procedure master names the procedure, the evidence the insurer expects and the likely query.
Only the bed, the estimate and what the hospital alone knows remain. Room advisor and sum-insured checks run as they type.
The notes reader proposes each field with its source. Sign-off generates the pre-auth form itself.
The payer's own validators pass before filing. Submitting starts the IRDAI hour, counted live.
A query pauses the clock. The reply is drafted from the record, attested by the doctor, and the clock resumes.
Stage, clock, approved amount and what they may pay, in English or Telugu.
In your cloud
You are the data fiduciary under the DPDP Act. Zyanta is a processor with no standing access to production.
Source mirrored into your Git organisation. Your CI/CD builds, scans and deploys it behind your approval gate.
Your name, domain, logo and colours on every patient screen, set in one configuration file.
Channel adapters file with the TPA portal, NHCX or the insurer's API, and bring every query and decision back to the desk board and the patient's phone.
If your desk runs ClaimBook, IHX or another claims platform, Claims Ignite delivers the complete file into it, and status flows back to the patient's page.
Your hospital system
Claims Ignite connects through HL7 v2 ADT messages, FHIR R4, read-only database views or a scheduled file, whichever your system offers.
Integration is never a precondition for the pilot. On day one the doctor master and tariff load from a spreadsheet, and the desk enters the UHID and IP number.
What is live today
Doctor's QR, reference at first tap, document reading and identity cross-checks, notes reader, procedure master, desk board with the payer's validators, room advisor, generated pre-auth form, query loop, patient status page, and a simulated payer with the real state machine.
Deployment in your cloud with SSO, HIS connectors, live TPA portal and NHCX filing, hand-off to ClaimBook, IHX or your platform, desk lead and auditor roles.
Patient rating, trips to the counter, minutes from advice to a complete file, queries per file. None of these has been measured on a live unit yet.
Next steps
With your IT and cyber security leads: the architecture, the security review, and how it sits in your cloud.
We observe the current flow and agree the baseline: counter trips, minutes to a complete file, queries, patient rating.
One unit, the payers it files with most, Option A or B, and the integrations in scope.
Set-up, go-live, hypercare, and a joint review of the numbers against the baseline.
Read it for your role
CEO · COO · medical director
What changes for patients, what a pilot asks of you, and the four numbers it measures.
OpenDesk head · TPA coordinators
What changes in the day, after-submit options with ClaimBook or IHX, and what you configure.
OpenCIO · CISO · IT lead
Your cloud and keys, DPDP data ownership, HIS integration, roles and service levels.
OpenOur ask
Name one unit and a desk lead, and give us an hour with your IT team. We bring the security review, a draft pilot plan and the baseline method.