Claims Ignite · cashless pre-authorisation

A cashless admission your patient never has to chase.

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.

Published6 to 48 hour waits, LocalCircles, January 2025 Design targetminutes; measured in pilot

The problem

The insurer's hour starts only when the file is complete. The patient's wait starts much earlier.

1 hr
For the insurer to decide a pre-auth
IRDAI Master Circular, May 2024
96.7%
Insurers' reported compliance
Stated in Parliament, December 2025
6 in 10
Patients who waited 6 to 48 hours
LocalCircles survey, January 2025
179
Fields on one TPA's pre-auth form
From our field-by-field teardown

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.

PublishedIRDAI, Parliament, LocalCircles Real179 fields, from the portal teardown
How the IRDAI one-hour rule works, and when the clock starts

The patient first

Five promises to a family that has just been told "you need to be admitted".

1A reference number at the first tap, in the doctor's room
3Photos instead of photocopies: policy, Aadhaar, PAN
0Times asked for the same fact twice
24×7Status on their own phone, with the insurer's clock
₹What it may cost them, before the bed is chosen
Designedpatient rating is measured in the pilot, at approval and at discharge

The flow

One record, filled once, by the person who knows each part.

  1. Doctor's room

    Scan the doctor's QR

    The patient gets a reference number straight away. The doctor sees them appear in their own queue.

  2. Patient's phone

    Three photos

    Policy, Aadhaar and PAN are read, cross-checked and prefilled. A mismatch is shown, never silently accepted.

  3. Doctor

    Advice in their own words

    Typed or photographed. The procedure master names the procedure, the evidence the insurer expects and the likely query.

  4. Insurance desk

    Already on the board

    Only the bed, the estimate and what the hospital alone knows remain. Room advisor and sum-insured checks run as they type.

  5. Doctor

    Accept and sign once

    The notes reader proposes each field with its source. Sign-off generates the pre-auth form itself.

  6. Insurance desk

    Nothing missing, submit

    The payer's own validators pass before filing. Submitting starts the IRDAI hour, counted live.

  7. Payer

    Query or decision

    A query pauses the clock. The reply is drafted from the record, attested by the doctor, and the clock resumes.

  8. Patient's phone

    Always knows where it is

    Stage, clock, approved amount and what they may pay, in English or Telugu.

Liveevery step above runs in demonstration, against a simulated payer

In your cloud

It runs in your cloud account, from your repository, under your brand and your keys.

Data

You own the data

You are the data fiduciary under the DPDP Act. Zyanta is a processor with no standing access to production.

Pipeline

Your pipeline

Source mirrored into your Git organisation. Your CI/CD builds, scans and deploys it behind your approval gate.

Brand

Your brand

Your name, domain, logo and colours on every patient screen, set in one configuration file.

After submit, you choose where the file goes.

Option A · included

Claims Ignite files and tracks it

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.

Option B · keep your platform

Hand the file to the system you already use

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.

Designedhand-off routes are confirmed with each vendor and your team during pilot set-up

Your hospital system

We read what your HIS already knows, so nobody types it again.

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.

LivestandaloneDesignedHIS connectors

What is live today

A short true list, rather than a long one.

Running 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.

Designed, built during set-up

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.

What a pilot measures

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

Four steps from here to a measured pilot.

  1. A 60-minute technical session

    With your IT and cyber security leads: the architecture, the security review, and how it sits in your cloud.

  2. Half a day at one insurance desk

    We observe the current flow and agree the baseline: counter trips, minutes to a complete file, queries, patient rating.

  3. Agree pilot scope and success measures

    One unit, the payers it files with most, Option A or B, and the integrations in scope.

  4. Ninety days, measured

    Set-up, go-live, hypercare, and a joint review of the numbers against the baseline.

Our ask

Let the family stop worrying about the paperwork.

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.