The honest answer: not yet, and for most clinics, not as a goal either. The right question isn't whether AI can submit a claim end-to-end (technically it can) but where human judgment adds safety and where it adds only friction. Human-in-the-loop claims automation is a design where AI drafts every claim (extracting data from documents, applying codes, filling the payer's form) but a staff member reviews and approves it before anything is submitted to an insurer. We build for that specific division of labour, and this post explains it.
What AI Should Do: The Drafting
Reading a photographed referral letter, extracting the patient, procedures, and clinical details, mapping them to the payer's accepted codes, checking the claim against that insurer's known requirements (the source of most administrative denials), and filling the form: this is high-volume pattern work where modern document AI is fast and, importantly, consistent. A tired human transposes digits at 4pm on a Friday; the model doesn't. In our production deployment inside a Hong Kong hospital radiology department, staff rate the AI's document-processing accuracy at over 99%. But note what that deployment still includes: staff.
What Humans Should Do: The Judgment
Approval before submission is not a ceremonial click. It catches the cases pattern-matching can't be trusted with: ambiguous referrals, unusual procedure combinations, a price that's technically correct but clinically implausible, a patient whose situation the front desk knows and the document doesn't show. It also keeps accountability where regulators, insurers, and patients expect it: with the provider. A claim is a representation the clinic makes to an insurer; the clinic should be the one making it.
The Part Most People Miss: Corrections Are the Product
Every time a staff member fixes a drafted claim (corrects a code, swaps a document, adjusts a price tier) that correction is captured. It becomes a rule, a template fix, an example the system learns from. This is why human-in-the-loop isn't a transitional compromise on the way to full autonomy; it's the mechanism by which the automation gets safe enough to earn more autonomy, payer by payer, claim type by claim type. Systems that skip the human skip the feedback.
Where Autonomy Is Appropriate
Graduated, and by risk class. Status checks, remittance parsing, and payment matching are read-only: full automation is fine from day one. Routine, repeated claim types with months of perfect approval history can move to spot-check review. New payers, new claim types, high-value claims, and anything the model flags as low-confidence stay at full review. The dial moves based on evidence, not enthusiasm.
What to Ask Any AI Billing Vendor
Does a human approve claims before submission, and can I set that policy per payer and claim type? What happens to my staff's corrections? Are they captured and applied, or discarded? Can I see why the AI drafted what it drafted (the source document, the extracted fields, the rule applied)? And where does patient data go? Is it de-identified before any hosted model sees it? (Our answer to the last one is architectural: PII is masked on our own infrastructure before any external model is involved, the same privacy-first design we've written about for our hospital deployment.)
FAQ
Is fully autonomous claim submission legal? Legality varies by market, but the practical standard is accountability: the provider is responsible for what's submitted in its name, which is a strong argument for provider approval regardless of jurisdiction.
Doesn't human review defeat the point of automation? No. Drafting is 80 to 90 percent of the work. Reviewing a complete, pre-checked claim takes seconds; assembling one takes many minutes.
Does the AI get better over time? Only if corrections are captured. That feedback loop is the difference between automation that plateaus and automation that compounds.
How does Vascue implement this? AI drafts every claim from the source documents; clinic staff approve in a review queue before submission; every correction is stored and applied to future drafts; and autonomy is expanded gradually per payer based on track record. See how the claim workflow runs end to end.
Book a demo and we will walk through the review queue and what the AI drafts on your own claims.