Hadto note
The child plan is not the adult plan
Michigan Healthy Kids Dental sources show why owner-ready automation must preserve the child plan lane and pre-treatment proof route before acting on a dental rule.
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 child dental plan lane cannot be safely collapsed into adult Medicaid, HIDE SNP, or generic state authority.
Healthy Kids Dental is not just “Medicaid dental.”
That label is too flat for daily work. It hides the question an operator has to answer before treatment: which child dental plan lane is live for this member, on this date, under which administrator, with which proof route?
The Michigan evidence makes the problem useful. Delta Dental Michigan publishes a Healthy Kids Dental provider-information surface. BCBSM’s Healthy Kids Dental lane uses a DentaQuest office reference manual. Both are Michigan child dental benefit surfaces. Neither should be treated as adult Medicaid, MI Integrated HIDE SNP, or a generic state-authority answer.
The business risk is not only a wrong claim. It is training the office to start from the wrong rule.
The child lane chooses the proof
Delta Dental’s Healthy Kids Dental provider information is an administrator surface for a child plan lane.
It tells the provider to prove participation and eligibility at the date of service. It ties reimbursement to submitted fees and the Healthy Kids Dental fee schedule. It makes fee-schedule absence matter, because a service missing from the schedule is not treated as a normal covered service. It also carries the practical guardrails around noncovered or alternate procedures: advance consent, record notation, and limits on when a member can be billed.
The provider record needs those facts before treatment can move cleanly from chairside recommendation to claim, patient communication, and record retention.
The same source also brings operating constraints that a generic “Medicaid dental” record will miss. Appointment-access expectations matter. Third-molar and radiograph documentation criteria matter. The front desk, clinical team, and billing team each need a different part of the same lane record.
An owner-ready system should therefore store the Delta HKD lane as more than a payer name. It should preserve child-DHP administrator, date-of-service eligibility proof, provider participation, fee-schedule presence, reimbursement cap, noncovered or alternate-service consent, record notation, member-billing guardrails, access expectations, and documentation criteria.
If those facts collapse into “Delta Dental covers HKD,” the automation has already skipped the work that protects the operator.
The same child benefit can use another surface
BCBSM Healthy Kids Dental proves the second half of the problem. The child benefit lane can sit under a different administrator and carry a different evidence shape.
In the BCBSM/DentaQuest Healthy Kids Dental Office Reference Manual, DentaQuest appears as the network and vendor administrator. The manual exposes code-level radiograph and tomosynthesis handling for the child lane:
- D0372 is covered for ages 5 through 20 in the D0210, D0330, and D0372 comprehensive-series group, one per 60 months per patient.
- D0373 is covered for ages 0 through 20 in the D0270, D0272, D0273, D0274, and D0373 bitewing group, one per 12 months per patient.
- D0374 is covered for ages 0 through 20 in the D0230 and D0374 periapical group, twelve per calendar year per patient.
Those rows are not interchangeable with the Delta provider-information surface. The BCBSM/DentaQuest manual adds its own duties around radiograph quality, mounting, dating, patient identification, authorization documentation, same-access and member-rights language, no missed-appointment charge, and noncovered-service private arrangements.
That does not make BCBSM/DentaQuest “more authoritative” than Delta. It means the plan lane selected a different operating surface.
A useful model does not store one Michigan child dental rule. It stores a rule path: member, child plan lane, administrator or vendor route, source surface, eligibility proof, age band, frequency group, documentation package, consent requirement, member-billing boundary, and access right.
Adult lanes cannot inherit child proof
The tempting shortcut is to let one Michigan Medicaid dental record stand in for all of this.
That shortcut fails because adult Medicaid lanes, HIDE SNP lanes, state lookup surfaces, and Healthy Kids Dental lanes answer different operating questions. A UHC adult MHP or HIDE SNP grid may expose portal checks, adult benefit rows, required-document packages, or federal alignment disclaimers. A state lookup surface may tell the provider where to verify code, rate, frequency, and eligibility facts. A Healthy Kids Dental administrator surface may tell the office how to prove a child member’s eligibility, what consent must exist before noncovered treatment, which fee schedule matters, or which radiograph group has spent the allowance.
The CDT code family can look familiar across those lanes. The business rule is not familiar until the lane is known.
Many AI systems become dangerous in ordinary office work at exactly this point. They retrieve a true sentence from the wrong surface and make it sound ready for action. “D0373 is annual” is not enough. Annual under which child lane, for which ages, grouped with which bitewing codes, after which eligibility proof, with which documentation and billing guardrails?
Experienced billers already ask those questions. The owner-ready system has to preserve them as structure.
Automation starts after the route is preserved
Hadto’s thesis is that domain experts become operators when their judgment survives handoff.
For Healthy Kids Dental, the system should not begin by automating a coverage answer. It should first require the pre-treatment route. The member has to be identified as a child HKD member for the date of service. The office has to know whether the lane is Delta Dental HKD or BCBSM/DentaQuest HKD. Provider participation, eligibility, and the controlling source surface have to be verified before the service is treated as a live rule. The fee-schedule or frequency-group answer should travel with the case, along with documentation, consent, access, and member-billing guardrails.
After that, automation can help. It can route the next task, check the age band, warn when a frequency group may be spent, prompt for radiograph documentation, or block a member-billing path that has not met the source’s consent rule.
Before that route is preserved, automation is only guessing from a code row.
The child plan is not the adult plan. It is not the HIDE SNP plan. It is not the state manual by another name. It is a live operating lane with its own administrator surfaces and proof duties.
A business that records that lane can train more people to make the right decision. Flattening it still leaves the same expert nearby to remember which “Medicaid dental” answer was safe this time.
Source evidence used in this note: public source Delta Dental Michigan Healthy Kids Dental provider information, reviewed through Hadto’s 2026-05-12 ontology research cycle; public source BCBSM/DentaQuest Healthy Kids Dental Office Reference Manual, reviewed through Hadto’s 2026-05-12 ontology research cycle. Internal research notes, not public evidence: 2026-05-12 ontology research-cycle notes on file, including preserved manifest references research/manifests/dental/2026-05-12-delta-dental-michigan-healthy-kids-dental-provider-info.yaml and research/manifests/dental/2026-05-12-bcbsm-dentaquest-healthy-kids-dental-office-reference-manual.yaml.
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.