Network assurance is not appointment availability

A dental access report is not the appointment.

That sounds obvious until a system has to act. A spreadsheet says a plan is subject to network adequacy review. A directory is reviewed monthly. Secret shoppers test participation and appointment availability. Grievances are reviewed. Encounter data is analyzed. Payment analysis is named as a future requirement.

Those are all useful facts. They are not the same fact.

California’s dental managed-care reporting makes the distinction concrete. The Department of Health Care Services publishes a Network Adequacy and Access Assurances page that places the dental report inside Annual Network Certification. The linked 2024 Dental Managed Care workbook identifies the reporting period, plan context, and dental provider-category scope. The separate 2024 ANC Analysis Methods document explains the broader methods for network validation, timely-access review, alternative access standards, grievances, and encounter-data analysis.

An operator system should not turn that whole bundle into one green access light.

If you run a business: When several different checks feed one status light, the light hides which check actually ran. Keep each verification method as its own fact, with what it proved and what it left unproven, so the next person can tell a reviewed listing from a confirmed appointment.

Assurance is a set of methods

A directory review asks whether the listed network can be inspected. A secret-shopper network-participation test asks whether provider participation can be verified. A secret-shopper appointment-availability test asks whether a member can move from directory to scheduled care.

The other methods see different failures. An access grievance asks whether members are reporting problems through a complaint path. Encounter-data analysis asks whether services are showing up after care is delivered. Future payment analysis asks whether payment and network assurance need to be reported together later.

Each method sees a different part of the access problem. If the business collapses them into one field called network adequacy, the next operator cannot tell what was actually proven.

The guardrail matters

The same report should also say what it does not prove.

Network-assurance evidence is not a CDT reimbursement schedule. It does not set coverage. It does not create a D9995, D9996, Q3014, sedation, or procedure-payment rule. A listed provider is not automatically available. The next patient still needs separate appointment evidence before anyone can claim care is reachable within a clinically useful window.

Those conclusions need their own sources: fee schedules, manuals, contract rules, provider directories, appointment-availability results, grievance records, encounter data, or plan-specific comparators.

This is the work Hadto is trying to make durable. The point is not to collect more reports. The point is to keep the report from being overread.

Owners need the proof trail, not the headline

A dental practice, plan, or operating company does not need a vague answer that says access looks acceptable. It needs the proof trail:

• which reporting period was reviewed
• which plan and provider category were in scope
• which assurance method produced the evidence
• whether the evidence came from geomapping, a directory review, a secret shopper, a grievance review, or encounter data
• which claims remain barred until a comparator source is checked

That record lets the next operator ask the right follow-up question. Is the directory current? Did the secret shopper reach a participating dentist? Was an appointment actually available? Grievance patterns may point to the same failure. Encounter data can show whether care happened. Payment analysis still needs its own source when that requirement arrives.

A domain expert can train an apprentice or hand off an operating lane only when the work keeps its source, method, and boundary visible. Otherwise the owner stays trapped as the person who remembers what the report really meant.

Network assurance is useful because it shows what the system is watching. It becomes operator-ready only when it also says what remains unproven.

---

Source evidence used in this note: public California DHCS Network Adequacy and Access Assurances materials, the public DHCS 2024 Network Adequacy and Access Assurances Report, Dental Managed Care workbook, and the public DHCS 2024 ANC Analysis Methods document. Hadto internal evidence ID: HAD-1770. Source-candidate notes are on file from the 2026-06-29 ontology research cycle.