Hadto note
Zero-dollar rows can still be instructions
MaineCare's 2026 Section 25 dental fee schedule shows why D9995/D9996 should be modeled as teledentistry modality and tracking companion lines, not paid benefits or simple noncoverage.
Why this matters
This post shows how explicit models, workflow controls, and evidence trails make the business easier to inspect, teach, and run.
Why this note is here
Operating rule: Turns an idea into a rule an owner or operator can use.
What supports it: Uses evidence, definitions, and cause-and-effect.
A zero-dollar teledentistry row can still carry a claim instruction when payment belongs to an underlying diagnostic service.
A zero-dollar fee-schedule row can still tell the operator what to do.
MaineCare’s 2026 Section 25 dental fee schedule lists D9995 and D9996 with a maximum allowance of $0. The easy reading is that the codes are dead rows. The other easy reading is that the rows are covered because they appear in the fee schedule.
Both shortcuts lose the rule.
D9995 records synchronous teledentistry. D9996 records asynchronous store-and-forward teledentistry. MaineCare’s Section 25.03 rule context says diagnostic services may be delivered by telehealth, the provider bills the underlying service, and the teledentistry CDT code is included for tracking.
That makes the teledentistry row a companion line.
Payment lives somewhere else
The payable service is the underlying diagnostic work. A limited oral evaluation, a screening, or another diagnostic service has its own coverage and rate question. D9995 and D9996 do a different job. They mark how the encounter happened.
That difference matters at the desk.
If a system treats D9995 as a standalone payable benefit, it can train a biller to expect money on a line that exists for tracking. If it treats $0 as flat noncoverage, it can suppress the line and erase the modality evidence MaineCare asked the provider to include.
The operating record needs both facts at once:
- the diagnostic service line that carries the reimbursement question
- the teledentistry companion line that carries modality and tracking evidence
Those two lines answer different questions. Collapsing them into one covered/not-covered flag creates a cleaner table and a weaker business.
The row still teaches the workflow
The companion line tells the next operator what happened without relying on private memory.
D9995 says the diagnostic service used a real-time teledentistry encounter. D9996 says information was stored and forwarded for later dentist review. The $0 allowance says the tracking line itself is not separately paid. The underlying service line still has to be checked under the ordinary Section 25 diagnostic rules.
That is enough structure to teach the workflow.
A trainee can learn that the teledentistry code is not the benefit being sold to the payer. The line is also not noise. It is a claim-line instruction: keep the modality visible, attach it to the diagnostic service, and do not move the payment expectation onto the tracking row.
An owner can audit the same record. Were diagnostic telehealth rules in scope? Was the underlying service billed? Was the modality line present? Did the system keep zero maximum allowance separate from noncoverage? Those are operator questions, not vocabulary trivia.
Companion lines are infrastructure
Hadto’s thesis is that domain expertise should become records a trainee can use.
Dental billing expertise often appears as a short correction from the experienced person in the room: “use the tele code too,” “that line pays zero,” or “bill the exam, not the telehealth code.” Those corrections are useful, but they are still trapped in a person.
The infrastructure version preserves the reason.
The record says D9995 and D9996 belong to a MaineCare-specific companion rule family. It separates synchronous and asynchronous modality, stores zero maximum allowance as a payment-disposition fact, and links the companion row to the underlying diagnostic service instead of leaving the relationship to memory.
That record is slower to fake and easier to teach. It lets a new operator see why the $0 row should still appear, why the claim should not expect separate payment from it, and why the business cannot throw it away as simple noncoverage.
The rule is small, but the pattern is general. Owner-ready systems do not only preserve what gets paid. They preserve the instructions that make payment, tracking, evidence, and handoff legible.
A zero-dollar row is not always a dead row. Sometimes it is the line that tells the next operator how the real service moved.
Source evidence used in this note: public MaineCare Section 25 Dental Services 2026 fee schedule and public MaineCare Section 25.03 rule context, accessed 2026-06-04. Internal Hadto research notes and merged companion-line proof are on file as non-public evidence.
Follow this concept
- Compare services that make the work inspectable
Use the services page when the note points to workflow, source-of-truth, or handoff repair.
- Read the operator path that depends on visible work
See how explicit methods become the basis for authority, accountability, and ownership.
Read next
- A research pipeline has to keep its evidence attached
Main point: States a point Hadto should prove with examples, sources, or customer work.
- An agent brain still needs an ontology overlay
Evidence: Adds facts or examples behind an existing point.
- From Consumer-Generated Content to Consumer-Generated Companies
Evidence: Adds facts or examples behind an existing point.