Eligibility, authorisation, and claim edit checks before submission
Deterministic checks at registration, scheduling, and claim release that confirm active coverage, match each service to the prior authorisation its insurer requires, and stop claims with missing or invalid data before they reach the insurer.
Part of the recommended approachTechnique: Rules Engine
These checks run at three points: when the patient is scheduled or registered, before the service is delivered, and when the claim is released to the insurer.
At registration they confirm the patient’s plan is active, establish which insurer pays first when the patient has more than one, and check remaining benefits for services with a benefit maximum, since coordination of benefits and benefit maximums account for most eligibility denials in one vendor’s hospital data.
Before the service they check whether the insurer requires prior authorisation and whether the authorisation on file matches the procedure, units, and dates being delivered, because invalid and mismatched authorisations cause far more authorisation denials than a missing one.
At claim release they apply edits for missing fields, invalid code combinations, and insurer-specific rules, and hold any claim that fails so a biller can correct it.
This is the right place to start for every provider, because one vendor’s analyses of hospital claims put registration, eligibility, authorisation, and claim data among the largest categories of denials, and medical group leaders describe strengthening these edits as one of their remedies.
A pediatric hospital that redesigned its emergency department registration form cut missing or incomplete insurance fields by 67%, and reports that this helped reduce its denials.
It is the wrong tool for denials driven by an insurer’s clinical review of medical necessity or documentation, which no field check can predict, and those belong to clinical documentation staff and the root-cause work queues.
Strengths for this problem
- Targets registration and eligibility, authorisation, and missing or invalid claim data denials, which one vendor's analyses of hospital claims rank among the largest categories.
- Every hold can be explained to a registrar or biller in plain terms, such as an inactive plan, a service on the insurer's authorisation list with no authorisation number, or an invalid diagnosis code.
- Works on day one with no denial history, so it suits a small practice as well as a health system.
- A new insurer rule takes effect as soon as the edit is changed, without waiting for enough denials to retrain a model.
Limitations for this problem
- Only catches what the edits encode, so it misses denials driven by clinical documentation or medical necessity judgements made by the insurer.
- Insurer authorisation lists and coverage policies change often, and an edit library that is not maintained starts letting through exactly the claims it was built to stop.
- Too many low-value holds slow claim release and teach billers to override edits without reading them.
Data needed
- Registration record per encounter: primary and any secondary insurer, plan, member ID, subscriber relationship, and the eligibility response received, with the date it was checked and any remaining benefit for services with a maximum.
- Each insurer's current list of services that require prior authorisation, by plan and procedure code.
- Authorisation records: authorisation number, approved service, units, and date range, matched to the scheduled and delivered service.
- Claim fields as they will be submitted, including procedure and diagnosis codes, modifiers, place of service, rendering provider, and the authorisation number.
How it is measured
- Initial denial rate for eligibility, authorisation, and missing or invalid claim data, per insurer, before and after each edit is introduced.
- Share of claims held by an edit that turned out to need a correction, which shows whether the edit is worth the delay.
- Edit override rate per edit, and the denial rate on claims released through an override.
- Days from service to claim submission, so holds do not create a filing deadline problem of their own.
Pitfalls
- Checking eligibility once at scheduling and never again, so a plan that lapses before the visit is not caught.
- Copying a generic edit library and never adding the insurer-specific rules that drive this organisation's own denials.
- Treating an authorisation number on the claim as proof the service matches the authorisation, when the approved units, dates, or procedure code differ.
- Adding edits after every denial without retiring stale ones, until billers override holds by habit.
Human oversight
Registrars and patient access staff resolve eligibility and authorisation holds before the service where possible, and billers decide how each held claim is corrected. The revenue cycle manager owns the edit library and approves each new or retired edit. No edit changes a diagnosis or procedure code on its own, because code changes belong to coders working from the documentation.