The benefit guide is part of the rule

The code row is not the whole rule.

Dental benefits work keeps proving the same operating failure from different directions. A biller sees a CDT code, remembers a payer shortcut, and treats the row as if it owns the decision. The actual source often says something narrower.

The Solis and Solstice dental materials make the source problem visible. Both mention tomosynthesis codes. Both can affect how an office thinks about D0372, D0373, and D0374. They do not have the same authority.

An owner-ready system has to know which surface is speaking before it trains a person or automates a claim decision.

A benefit guide can define the benefit

The Solis Health Plans dental guide is member-facing and bilingual. It tells the member the guide is a complete list of procedures covered by the Solis Wellness Giveback Plan HMO C-SNP. Missing procedures are outside this plan’s coverage. The guide also tells members to use in-network providers and marks comprehensive services that need prior authorization with an asterisk.

Member copy is doing rule work.

For this plan, the guide is part of the operating rule. It names the covered-code universe, the network lane, the prior-authorization marker, and the frequency counters a practice has to respect.

D0372 appears inside a three-calendar-year group with D0210, D0330, and D0277. The operating fact is not simply “D0372 is covered.” A tomosynthesis comprehensive series shares a counter with the complete series, panoramic image, and vertical bitewing group named by this plan guide.

D0373 sits in a different group. It shares an annual bitewing counter with D0270, D0272, D0273, and D0274. D0374 appears with its own annual limit.

Those distinctions matter at the desk. A trainee should not learn one generic tomosynthesis policy. The trainee needs to know which guide, which plan, which member network, which prior-auth marker, and which frequency group made the answer true.

An advisory cannot replace the contract

The Solstice Public Advisory has a different job.

It is a clinical-review advisory. It lists procedure codes, benefit-guideline summaries, and documentation expectations. At the front, it warns that a listed code may still be outside a subscriber’s contract, because the group or subscriber account chooses benefit coverage. It also says specific plan coverage, exclusions, and limitations can supersede the advisory criteria.

The warning draws an authority boundary.

For D0372 and D0387, the advisory says benefits are allowed if covered under the plan and not allowed if not covered under the plan. For D0373, D0374, D0388, and D0389, it repeats that plan gate and adds another rule: if individual X-ray codes are submitted on the same date as a comprehensive series of X-rays, the individual codes are considered inclusive to the comprehensive series.

The advisory is still useful. It tells the office how clinical review sees the code family and how same-date X-ray submission can affect processing. But it does not make coverage live on its own.

A system that stores “Solstice allows D0373” has already lost the rule. The more accurate record says the advisory allows review only when the active plan covers the service, and the contract or schedule of benefits can override the advisory lane.

Store the source role with the fact

The same CDT row can be attached to several source roles.

A member benefit guide can be a covered-code list for a named plan. A clinical-review advisory can describe when a listed procedure is allowed for review. A subscriber contract can decide whether the benefit exists. A prior-auth flag can decide whether the office has to get permission before treatment. A frequency group can decide whether a past claim consumed the current allowance.

The roles cannot be merged.

A record with only code, payer, and summary forces the next person to guess which source had authority. The resulting guess becomes training debt and automation risk. Even a model that retrieves the right code row can still select the wrong rule source.

The owner-ready record needs a field for source role. It should say when a row came from a member-facing covered-code guide, which named plan that guide applies to, whether the code is absent or present in the covered list, whether in-network use or prior authorization is required, which frequency counter groups the code, and whether a separate advisory is only clinical-review guidance subject to contract coverage.

A reference table holds rows. An operating system preserves authority.

Apprentices need the rule surface

Hadto’s thesis is that expert billing judgment should become inspectable operating infrastructure. That is how apprentices become owner/operators instead of people who copy the expert’s latest shortcut.

The apprentice does not only need to know whether D0372 is covered. They need to learn the order of authority.

First, identify the member and active plan. Then identify the source surface that speaks for that plan. For a member guide, ask whether it is the covered-code list and whether absence means no coverage. For an advisory, ask what contract or schedule of benefits controls coverage. Then look at prior authorization, network, same-date inclusion, and frequency counters.

Only after those steps should the code row drive the claim workflow.

That order prevents two bad shortcuts. The first shortcut treats a clinical-review advisory as if it created coverage. The second treats a member-facing benefit guide as if it were loose marketing copy instead of a plan rule surface.

Both shortcuts make the business dependent on the person who remembers the difference.

Preserve document authority before modeling the code row.

A billing AI should not answer from D0372 alone. It should show the source role, plan scope, contract gate, network requirement, prior-auth marker, frequency group, and same-date inclusion rule that made its answer reviewable.

A reviewable source trace makes the decision slower to fake and easier to teach.

The goal is not to build a larger pile of dental facts. The goal is to turn source judgment into a record a future operator can inspect. When the business preserves the source surface, the next person can see why a guide controls one decision, why an advisory only qualifies another, and why the contract still has the final word.

The benefit guide is not background reading. In the right plan lane, it is part of the rule.

---

Source evidence used in this note: Solis Health Plans Dental Guide for Solis Wellness Giveback Plan HMO C-SNP, accessed and reviewed 2026-05-09; and Solstice Benefits 2026 Public Advisory, accessed and reviewed 2026-05-09.