Electronic eligibility answers whether a patient is covered, and then somebody opens the payer portal anyway to find out what is actually payable.
There is a mandated electronic standard for eligibility, and it works. It confirms that a plan is active. What it routinely omits is the detail the front desk actually needs: frequency limitations, waiting periods, alternate benefit provisions and remaining annual maximum. That gap is the origin of most manual verification in this sector.
So the work becomes portal work. Each payer has its own login, its own layout and its own vocabulary, and the session times out partway through a lookup. The result is transcribed into the practice management system as free text, where it cannot be queried later.
Denials arrive as standardised reason codes that are vague by design, and interpreting one against a specific plan is judgment work. The assembly around it is not: pulling the radiograph out of the imaging application, attaching it to the claim, and resubmitting after a single field was corrected.
Coverage is confirmed. Whether a specific procedure is payable this year, at what rate, after what waiting period, is frequently absent, which is why practices treat the electronic check as a first pass only.
No published interface, multi-factor login, per-office credentials that expire, lockout after failed attempts, and a session that times out midway. These are not incidental obstacles.
The practice system launches the imaging application with a patient identifier. There is often no programmatic route to list or export the images a claim needs, so a person exports them by hand.
Where a practice system has no supported interface, vendors reach into the database directly. Those integrations break on version upgrades and are unsupported when they do.
A 270 goes out and a 271 comes back reporting the patient active, which answers none of what the treatment plan needs: how much of the annual maximum remains, whether frequencies allow another prophy this cycle, whether a crown sits behind a waiting period or pays an alternate benefit instead.
The clearinghouse report splits into two very different piles.
The overdue list and the schedule disagree constantly, because a patient who booked online yesterday still sits on the list that was generated last week, and the communications tool cannot see the practice system where the appointment now lives.
The claim carries a PWK segment and an attachment control number, while the packet itself travels through an attachment service rather than inside the 837D.
The amount in the bank rarely equals the amount on the file.
Deposits keep landing.
A 999 confirms the envelope opened.
Most first pass rejections come down to a single absent field.
Submitted for a crown, then silence.
Diagnosed, presented, agreed to in the chair, and still sitting on the unscheduled list eleven months later.
A request comes in by fax, and the chart it asks for sits in four places at once: notes in the practice system, radiographs in the imaging application, a cone beam volume that exports only as DICOM, and consent forms scanned in flat.
Nothing announces this one.
Two photographs arrive with the new patient form.
The schedule turns up as a spreadsheet or a PDF keyed by procedure code, and it has to become fee rows against the right plan before the next estimate is quoted at the desk.
This one leaves dentistry altogether.
A denial at least proves something went out.
Somebody leaves on a Friday.
A practice is a covered entity, and any vendor that creates, receives, maintains or transmits protected health information on its behalf is a business associate, which requires a written agreement in place before any disclosure. That agreement has to describe permitted uses, require safeguards, bind subcontractors on the same terms, and require return or destruction at termination. This is why putting a model provider in the path is a decision rather than a formality: a business associate has no independent authority to use protected information for its own product development or model training, and if a vendor will not sign, the information cannot go to it. The minimum necessary principle separately limits how much data a workflow should move even under an agreement. Coding and anything submitted to a payer under a provider identifier carries liability for that provider, so a person attests even where a system assembles.
Related: Insurance agencies Field services. Or start from the four shapes of work instead of from an industry.