The plan rule comes before the payer rule

A payer rule is not the plan rule.

That sounds small until a billing system has to teach the next operator what to do with the same dental code family under two Arkansas sources.

The weak question is, “What does this payer do with D0372, D0373, and D0374?” That question starts too late. The better question is, “Which contract, product line, and benefit lane is active for this patient on this date?”

Adjudication logic belongs after that answer. A system that skips the plan lane makes the code table look more stable than the business rule really is.

Start With The Contract Gate

The Delta Dental of Arkansas 2025 Dentist Handbook treats D0372, D0373, and D0374 as denied unless a group or individual contract covers them.

The handbook is creating a contract gate, not a normal code-level denial.

The office cannot reason from the CDT family alone. It has to know whether the patient’s group contract or individual contract has made the tomosynthesis service a covered benefit. Only then does the next layer matter.

When the service is covered, the handbook adds same-office rules around conventional comparator codes and capture-only codes. The relevant conventional radiograph line, the tomosynthesis interpretation line, and the capture-only line can no longer be treated as three separately billable facts just because they are three different CDT codes. Some of those lines become not billable to the patient when the same-office bundling rule applies.

The owner-ready record has to preserve that order. Contract coverage says whether the benefit exists. Payer processing says which line can be recognized. Same-office bundling says which related lines lose separate patient-billing status. The claim record says what happened for this patient.

If those steps collapse into “Delta denies tomosynthesis,” the business loses the useful distinction. A denied-by-default code is not the same thing as a denied-under-this-plan code. A covered-by-contract line is not the same thing as a separately billable patient balance.

L.E.A.T. Is Another Lane

The Arkansas Blue Cross CDT 2025 Dental Procedure Guidelines takes a different route.

D0372 maps by L.E.A.T. alternate benefit to D0210. D0373 maps by L.E.A.T. to D0270. D0374 maps by L.E.A.T. to D0220. The same guide treats D0387, D0388, and D0389, the image-capture-only tomosynthesis codes, as not-covered benefits. It also says subscriber plan details vary and eligibility or individual plan benefits must be verified.

That last sentence is doing real operating work.

L.E.A.T. does not erase the plan lane. It is an adjudication transformation that still depends on whether the patient is eligible and what the active plan covers. The system should not store “Arkansas Blue Cross covers D0372 as D0210” as a universal payer fact. It should store the narrower rule: under this source, in this benefit lane, D0372 can be processed as the least expensive professionally acceptable conventional comparator D0210, subject to plan verification.

The same family now has a different shape from Delta Arkansas.

Under Delta Arkansas, the first question is whether a group or individual contract covers the tomosynthesis code at all. Under Arkansas Blue Cross, the first visible adjudication move is L.E.A.T. substitution to a conventional comparator, while capture-only tomosynthesis codes stay not covered. Both still require plan context before the office can treat the answer as live. The payer name is not enough.

Do Not Store One Payer Answer

Most local billing knowledge gets compressed for speed: “Delta denies it unless the contract has it,” “Arkansas Blue Cross downgrades it to the regular X-ray,” or “capture-only is not covered.”

Those shortcuts can work while the expert is nearby. They are not owner-ready systems. They hide which lane made the answer true.

A transferable record needs separate fields for payer, plan family, group or individual contract, product line, eligibility check, CDT code, interpretation-bearing service, capture-only service, conventional comparator, alternate-benefit method, same-office scope, not-covered status, and patient-billing consequence.

The field list sounds long only because the business has been letting one person remember it. The payer sources already make the distinctions. The system’s job is to keep them from being flattened.

The failure mode is predictable. A future operator sees D0372 and reaches for the payer rule. The claim then follows the wrong branch because the contract gate was never checked, the product-line context was stale, or the L.E.A.T. mapping was treated as coverage instead of substitute processing.

The rework is not just claim cleanup. It is training debt. Every hidden lane has to be explained again to the next biller, manager, buyer, or successor.

The Plan Lane Has To Be First-Class

Hadto’s operating standard is simple: put the plan lane before adjudication.

A dental billing workflow should not begin with a code table. It should begin with the live benefit context:

• Who is the payer?
• Which group, individual, or product-line contract is active?
• Was eligibility verified for the date of service?
• Does the plan cover the submitted service, deny it by default, or route it through alternate benefit processing?
• Which comparator, capture-only, same-office, or patient-billing rule applies only after that plan answer?

Those questions keep payer policy from becoming local folklore.

The same code family can be a denied default, a contract-covered benefit, an L.E.A.T. alternate benefit, a conventional comparator, or a capture-only non-benefit depending on the lane. The owner does not need every edge case in memory. The record should show the lane that selected the rule.

A billing note says what happened last time. An operating system tells the next person which rule is allowed to happen now.

The payer rule still matters. It just does not get to go first.

---

Source evidence used in this note: Delta Dental of Arkansas Dentist Handbook January 1, 2025 and Arkansas Blue Cross CDT 2025 Dental Procedure Guidelines, both reviewed through the 2026-05-07 Hadto ontology research cycle.