Every ECHS claim that comes back with a query is money that has already been earned but not yet received. The treatment is done, the patient has gone home, and the file is now sitting in a queue — sometimes on the portal, sometimes on someone's desk in your billing office. The longer it sits, the longer your receivables age.
Most hospitals cannot fully control how quickly a claim is processed on the other side. What they can control is how often claims get queried in the first place, and how fast they respond when a query does arrive. This guide covers both.
Why ECHS claims get queried
Queries are rarely random. When billing teams go back through a few months of queried files, the same handful of reasons tend to come up again and again.
1. Missing or incomplete documents
The most common cause is simple: something the processing team expected is not in the file. Typical gaps include a missing referral, an unsigned or undated discharge summary, investigation reports that are mentioned in the notes but not attached, missing implant stickers or invoices, and incomplete beneficiary identity documents. Each gap on its own looks minor. Together they account for a large share of back-and-forth.
2. Bills that do not match the clinical record
A bill that lists a procedure, a room category or a number of ICU days that the case sheet does not support will almost always draw a query. The same applies when dates do not line up — admission time on the bill differs from the admission note, or the discharge date on the summary differs from the final bill.
3. Late uploads
Files uploaded well after discharge are harder to defend. Documents get misplaced, the treating doctor has moved on to other cases, and the billing executive who handled the admission may not be the one answering the query. Delay at the upload stage tends to create delay at every later stage.
4. Coding and package issues
Choosing the wrong package, billing items that are already included in a package, or charging separately for something the rate list treats as bundled are frequent triggers for queries and deductions. These are not always errors of intent — they are often a result of the rate list and package rules being interpreted differently by different people on your team.
5. Poor-quality scans
Blurred pages, cropped signatures, sideways scans and multi-document PDFs where the reviewer cannot find the relevant page all slow processing. A document that exists but cannot be read is, in practice, a missing document.
The exact documentation and timelines required depend on the current ECHS guidelines and the terms of your empanelment. These change from time to time, so your billing head should keep a copy of the latest circulars and review the internal checklist whenever a new one is issued.
How to measure query TAT properly
You cannot reduce what you do not measure, and many hospitals do not have a clear number for query turnaround time. "We reply to queries quickly" is not a metric.
Start by defining two separate clocks:
- Internal response time — from the moment a query is raised on the portal to the moment your hospital submits a reply. This is fully within your control.
- Total query cycle time — from the first query to final settlement of that claim, including any repeat queries. This shows whether your replies actually resolve the issue or just trigger another round.
Then track, at minimum, for every claim:
- Date of discharge and date of final bill upload
- Date each query was raised and date it was answered
- Query reason, in a fixed set of categories (document missing, bill mismatch, package/coding, scan quality, other)
- Who in your team owned the reply
- Number of query rounds before settlement
- Amount claimed versus amount approved, and the stated reason for any deduction
With this data you can see the average and the worst cases, not just the overall feel. The long tail matters most: a small number of files stuck for months usually hold a disproportionate share of your blocked money.
Most hospitals start this in a spreadsheet. That works for a few weeks, but manual logging slips as soon as the team gets busy, which is exactly when you need the data most. Pulling status directly from the portal into a dashboard removes that dependency.
Process fixes that prevent queries
Automation helps, but most query reduction comes from disciplined process. These are the fixes that hospitals find most effective.
Start the document checklist at admission, not at discharge
The discharge counter is the worst place to discover a missing referral. Build a checklist for every ECHS admission that starts at the admission desk: referral, beneficiary card, identity documents, and any other entitlement papers required under your empanelment terms. Mark each item as received, pending or not applicable. Anything still pending after the first day should be escalated, while the patient and family are still in the hospital.
A structured billing KYC module makes this practical: documents are uploaded against the admission, completeness is visible at a glance, and the billing team can download the full set in one go when preparing the claim.
Make sure geo-tagged patient photographs are taken on time
Where patient photographs are part of the documentation requirement, they need to be taken at the right stage of the stay and be clearly attributable to the patient, date and location. Relying on staff phones and WhatsApp forwards leads to missing, mislabelled or undated images.
The photo itself is taken in the geo-tagging app the hospital uses. What usually fails is the reminder. A geo-tag notification app alerts the right staff member at admission, during the stay and at discharge, and keeps reminding — then escalates to a supervisor — until each stage is marked done. At billing time, the team already knows every photo has been taken.
Reconcile the bill against the case sheet before upload
Before any final bill goes out, a second person should check it against the clinical record: dates, room category, ICU days, procedures, implants and the package selected. This takes a few minutes per file and catches the mismatches that otherwise come back as queries weeks later. Keep a short written guide on common package inclusions so that the check is consistent across billing executives.
Set a target for upload after discharge
Agree internally on how soon after discharge a file must be uploaded — within the timelines your empanelment requires, and ideally well inside them. Track this as a number every week. A discharge tracker helps here, because a file cannot be uploaded quickly if the discharge summary and final bill lock themselves were late.
Give the query queue a daily owner
Queries often sit unanswered not because they are hard, but because nobody was looking. Assign one person to check the portal for new queries every working day, log them, and route each one to the right team — billing for bill corrections, medical records for missing notes, the treating department for clinical clarifications. Review the open query list in a short daily huddle, oldest first.
Standardise scan quality
Agree on basic scanning rules: one document per file where possible, correct orientation, readable resolution, all pages included and named consistently. It sounds basic, and it removes an entire category of avoidable queries.
Key takeaways
- Most ECHS queries come from a few repeat causes: missing documents, bill–record mismatches, late uploads, package/coding issues and poor scans.
- Measure internal response time and total query cycle time separately, and categorise every query by reason.
- Start the document checklist at admission, make sure geo-tagged photos are taken on schedule, and reconcile bills before upload.
- Give the query queue a named daily owner and review the oldest items first.
- Use automation for repetitive portal work and pattern analysis — not as a substitute for a clean file.
Where automation actually helps
Once the process is in place, automation removes the repetitive work that eats your billing team's day and gives managers visibility they cannot get from spreadsheets.
Automation agents for final bill uploads
Uploading final bills to the ECHS portal is repetitive: log in, search the case, fill fields, attach documents in the correct slots, submit, note the reference. An automation agent can do this from a prepared file set, consistently and without fatigue, while logging what was uploaded and when. Your executives spend their time checking files and answering queries instead of clicking through portal screens.
Portal-to-dashboard data pulls
Instead of someone manually checking claim status one by one, an automation agent can download claim and query status from the portal into a central dashboard. New queries show up the same day with their age, and nothing depends on a person remembering to look.
Query TAT and QC dashboards
With portal data flowing in automatically, you can calculate query TAT for every claim and see it by reason, by billing executive and by department. Quality-check metrics show which files went out incomplete and why. This turns a weekly argument about "why are payments slow" into a specific list of files and causes.
Deduction and arbitration pattern analysis
Individual deductions look like one-off disputes. Analysed together, they often reveal patterns — a particular package that is repeatedly disallowed, a specific item consistently deducted, or a type of case that frequently goes to arbitration. Once you can see the pattern, you can fix it upstream: update the billing guide, retrain the team or change how that case type is documented.
COPPERJAM's Billing Desk Automation cover these areas — final bill upload, portal-to-dashboard download, query TAT and QC calculation, and arbitration analysis — and work alongside your existing HIS and billing team rather than replacing them.
A practical starting plan
- Week 1: Pull the list of currently queried ECHS claims. Categorise each by reason and age.
- Week 2: Introduce the admission-stage document checklist and a named daily query owner.
- Week 3: Add pre-upload reconciliation of bill versus case sheet, and a written package guide.
- Week 4 onwards: Track internal response time and upload-after-discharge weekly. Bring in automation for uploads and status tracking once the process is stable.
Query TAT is not one problem — it is the sum of many small delays. Fix the causes you control, measure honestly, and let automation agents take over the repetitive portal work so your team can focus on the files that need judgement.