The Ayushman Bharat PM-JAY Claim Workflow for Hospitals

Verification establishes that the patient in front of you is an entitled beneficiary and that the entitlement is active. This is done against the scheme's beneficiary identification process, using the identifiers the scheme accepts, and it produces a record that anchors everything downstream. If verification is skipped or deferred because the ward is busy, the hospital has effectively started an unfunded admission.

The failure mode here is rarely fraud. It is a family arriving at night with partial documents, a front-desk clerk who admits on good faith, and a verification attempt made two days later when the identifiers do not resolve. Build the escalation path explicitly: who is called at 2 a.m., what provisional status the case carries, and at what point a clinical decision to proceed becomes a documented financial decision to proceed.

Record the verification outcome in the hospital system, not only in the scheme portal. When the two systems hold the same case reference, reconciliation at month end is a lookup rather than an investigation.

Pre-authorisation is where the hospital states what it intends to do and the payer agrees to fund it. The request carries the clinical justification, the proposed package, and supporting evidence — investigation reports, imaging, clinical notes, and photographs where the case type calls for them. The quality of this submission determines whether the case sails through or enters a query loop that costs days.

The most common cause of a weak pre-authorisation is a treating doctor who writes for a clinical audience and an administrator who submits it unchanged. The reviewer on the other side is checking whether the documented findings support the package claimed. A note that says the patient was managed conservatively and then improved does not, on its face, justify an interventional package — even when the intervention plainly happened.

Give the scheme desk permission to send a pre-authorisation back to the consultant before submission. A two-hour internal round trip is cheaper than a four-day query cycle, and it teaches the clinical team what the payer actually reads.

PM-JAY funds treatment through defined packages. Choosing one is not a billing formality; it fixes what the hospital may claim, what is deemed included, and in many cases whether the patient can be charged separately for anything at all. Packages typically bundle the procedure with associated stay, routine consumables, and standard investigations, which means an item you consider extra may already be inside the price you accepted.

Two constraints deserve standing attention. First, package specifications carry conditions — some are reserved for particular facility levels or specialist availability, and claiming one you are not eligible for invites rejection and audit exposure. Second, the beneficiary is entitled to cashless treatment within the covered scope, so informal collection from the family for included items is both a contractual and a reputational problem.

Where a case genuinely exceeds what a single package contemplates, the correct route is the scheme's own provision for that situation, not a quiet side bill. Document the clinical reasoning at the time, not retrospectively when a claim is queried. Rates, package definitions, and eligibility conditions are revised periodically by the National Health Authority and state agencies, so read the current master rather than relying on what the desk learned two years ago.

Once the case is running, the hospital accumulates the evidence the claim will stand on: operative notes, investigation reports, discharge summary, and the case-specific artefacts the scheme requires. The practical discipline is to collect these as the case progresses rather than assembling them after discharge, when the surgeon has moved on and the ward file has gone to records.

Queries are the scheme's request for something missing or unconvincing, and they run against a response window. A query that lapses is functionally a rejection the hospital chose. The organisational fix is boring and effective: a named owner, a shared queue visible to more than one person, and a daily check that no query is aging. Hospitals that route queries to a single individual's login discover the weakness the week that person takes leave.

A platform such as HealUDoc can hold the scheme case reference against the encounter so that discharge summaries, reports, and consumable records are retrievable by case rather than hunted across departments. The portal remains the system of record for the claim; the hospital system's job is to make sure nothing needed is missing when the query arrives.

Submission converts a treated case into a receivable. From that moment the hospital needs to know, for every submitted claim, its current state: submitted, queried, approved, partially approved, rejected, or settled. Hospitals that track only submitted-versus-received cannot tell the difference between a slow payer and a claim that quietly died in a query three weeks ago.

Partial approvals deserve their own bucket. A claim settled at less than the amount claimed is either a legitimate package correction the hospital should learn from, or a deduction worth contesting — and you cannot tell which if partial settlements are absorbed into the general receipt line. Reconcile settlement advice against submitted claims at the case level, not the batch level.

Settlement cycles for government schemes are structurally longer than cash and often longer than private insurance. Plan for that in the working-capital view rather than being surprised by it quarterly. The scheme portfolio should carry its own aging analysis because blending it with corporate receivables hides both problems.

The single biggest structural risk in PM-JAY claim management is concentration. One capable coordinator learns the portal, the state agency contacts, and the unwritten conventions, and the hospital's scheme revenue quietly becomes a function of that person's attendance. Cross-train at least two people, document the conventions as they are learned, and rotate the daily query check.

Give the desk a weekly review with finance rather than an annual one. Fifteen minutes covering aged queries, rejections by reason, and partial approvals will surface the recurring documentation gap long before it becomes a lakh-scale pattern. HealUDoc dashboards can put scheme cases alongside the rest of the receivables picture so scheme performance is reviewed with the same seriousness as corporate and TPA accounts.

Finally, close the loop with the clinical team. When a rejection traces to a missing operative detail or an unsupported package, the correction belongs in the consultant's documentation habit, not in the desk's workaround list. Scheme revenue improves when the ward changes, not when the desk works later.