New codes should inherit old rules

A new code is not automatically a new rule.

Sometimes the code only gives an existing service a more precise label. The business still has to follow the same counter, exclusion, clinical rationale, authorization path, and source obligation that governed the older code.

Connecticut DSS Provider Bulletin 2022-101 / Policy Transmittal 2022-69 is a clean example. The bulletin adds three tomosynthesis dental CDT codes to the diagnostic radiology section: D0372 for a full series, D0373 for bitewing imaging, and D0374 for periapical imaging. Those codes are new to the fee schedule, but the bulletin does not treat them as new operating concepts. It maps them onto the same policies and regulations used for conventional radiography and digital imaging.

The operating move is inheritance.

The counter is shared

D0372 is a tomosynthesis full series. D0210 is a conventional complete mouth series. A weak billing model would give each code its own local rule because the labels differ.

The Connecticut rule does the opposite. D0210 and D0372 share one complete-mouth-series counter. Only one complete mouth series, whether conventional or tomosynthesis, is payable for a HUSKY Health member every three years.

The business record should therefore model the counter as the durable object. The code is one way of using the counter. It is not the counter itself.

A standalone note that says “D0372 allowed every three years” can miss the prior D0210 claim. A shared-counter record that says “complete mouth series counter, D0210 or D0372, one per member every three years” makes the inheritance visible. The future operator can see the shared limit before the claim is submitted.

The exclusion travels too

D0373 is tomosynthesis bitewing imaging. The bulletin permits up to four D0373 images per year for a HUSKY Health member only when no conventional bitewing claims were submitted for that member under D0270 through D0274.

The rule is more than a frequency limit. It is also an exclusion group.

The record needs to ask whether a conventional bitewing code already used the bitewing allowance. It should not merely count D0373 instances. A new modality code can still be blocked by older modality claims because the payer is governing the underlying bitewing imaging work, not only the code string.

Local lore becomes dangerous here. A biller may remember that tomosynthesis bitewings are “new” and think the year starts fresh. The source rule says otherwise. A usable operating record should teach that D0373 inherits the bitewing policy boundary and has to be checked against D0270, D0271, D0272, D0273, and D0274.

Periapicals share one annual limit

D0374 follows the periapical policy used for D0220 and D0230. The combined payable maximum is four periapical images per year per patient across D0374, D0220, and D0230.

Again, the durable rule is not “D0374 has a limit.” The durable rule is “periapical imaging has one combined annual limit across these codes.”

The bulletin also preserves the medical-necessity path. Additional imaging can go through prior authorization or post-procedure review when medically necessary. That detail matters because the rule is not a hard clinical prohibition. It is a payable-limit rule with an escalation route.

An owner-ready record should preserve both halves: the combined annual counter and the PA or PPR route for exceptions. Otherwise a trainee learns only “stop at four,” while an experienced owner knows the real work is “stop at four unless the case has source-backed medical necessity and someone owns the review path.”

Code inheritance should be explicit

The practical lesson is small but important. New codes should inherit old rules unless the source says the underlying business concept changed.

Hadto’s concern is not just the dental billing detail. Hadto’s thesis is converting employees into owners. That requires records that teach how rules carry forward. A future owner/operator should not have to ask the founder whether a new payer code changed the business logic or only changed the transport label.

The record should make the inheritance inspectable:

• Which new code was added?
• Which older code, counter, exclusion group, or medical-necessity path does it inherit?
• Which source rule created that inheritance?
• Which patient, member, payer, date, and claim facts are needed before the code can be used safely?
• What escalation route remains when the limit is reached but the service is medically necessary?

Those questions prevent duplicate local lore. They also keep the model from pretending every code addition deserves a new concept.

Sometimes a new code means a new service. Sometimes it means a more specific label for work the payer already knows how to govern. The only safe way to tell the difference is to keep the source attached and make the inherited rule visible in the operating record.

That is how a business learns without making the owner remember every edge case.

---

Source evidence used in this note: internal Hadto ontology research-cycle manifest captured 2026-05-06 and Connecticut DSS Provider Bulletin 2022-101 / Policy Transmittal 2022-69.