The Enamel Review · Industry
ADA asks CMS to include dental data in Medicaid IT
The ADA is asking federal regulators to build dental information into the next generation of state Medicaid technology standards — a quiet decision with long consequences for patients.
In a natural, human-quality voice · about 4 min · free when you register
Read aloud · 0:00 / 4:00 · the text follows along
Most of the decisions that shape a patient’s experience of care are made in an operatory. A few are made in a comment letter. The American Dental Association has urged the Centers for Medicare & Medicaid Services to make sure that dental data and dental technology are accounted for in the standards now being developed for state Medicaid systems, according to reporting in ADA News. It is the kind of item that rarely travels beyond trade press, and it deserves better, because the plumbing of Medicaid data determines what a state can see, what it can pay for promptly, and how easily a dental office can participate at all.
What CMS is actually standardizing
State Medicaid programs do not run on a single federal computer. Each state builds or buys its own enterprise systems — eligibility, claims processing, provider enrollment, encounter reporting — against federal architecture and certification expectations, and each state feeds data upward into national reporting. CMS periodically refreshes those expectations: what modules must do, which code sets and interoperability standards apply, how data must be structured so that one state’s records can be compared with another’s. The direction of travel across the last decade has been toward modular systems, application programming interfaces, and standardized clinical and administrative data exchange.
Dental has a habit of sitting slightly outside that frame. Dentistry uses its own HIPAA-named code set, CDT, maintained by the ADA. It has its own diagnostic terminology work. Its claims routinely depend on attachments — radiographs, periodontal charting, narratives — in a way that most medical claims do not. When a standards effort is drafted primarily around medical encounters, dental requirements tend to be handled as an exception, added late or not at all. The ADA’s argument, as reported, is a structural one: build the dental case in from the start rather than retrofitting it.
Why the distinction matters more than it sounds
Consider what happens when dental data is poorly captured in a state’s system. Utilization figures for children’s preventive visits become unreliable, which weakens the state’s ability to evaluate its own program. Provider directories drift, which frustrates families trying to find a participating office. Prior authorization and attachment workflows stay manual, which adds staff hours that a small practice absorbs unhappily. Over time, administrative friction is associated with lower dental participation in Medicaid — an association that policy researchers and state programs have documented for years, even if causation is layered and local.
The reverse is also true and less often discussed. Clean, standardized dental data is what makes it possible to ask serious questions: whether sealant programs reach the children they were designed for, whether emergency department visits for dental pain decline when access improves, whether teledentistry encounters in underserved neighborhoods produce follow-through on definitive care. Those questions cannot be answered with data that was never structured to hold the answer. Technology standards are, in that sense, research infrastructure.
The advocacy pattern behind the letter
This comment sits inside a broader pattern of organized dentistry engaging with federal and state rulemaking rather than reacting to it. Readers who follow that work will recognize the rhythm from our earlier coverage of state-level dental advocacy and the volume of laws it has shaped, and from the profession’s attention to leadership and research direction at the federal level, including the new NIDCR director. None of it is glamorous. Comment letters, certification criteria, code set maintenance and interoperability specifications are the unlovely substrate on which access rests.
It is worth being precise about what a comment letter is and is not. It is a formal request for consideration during a rulemaking or standards development process. It does not bind the agency. CMS may adopt some recommendations, decline others, or address them in subsequent guidance. Anyone reading a headline of this kind should treat it as a position being registered, not a policy being enacted. The documents to watch are the eventual CMS guidance and certification materials themselves, which are published publicly.
How does any of this reach a South Florida patient or practice?
For a Florida family covered by Medicaid, none of this changes anything this week. Over a longer horizon, better dental data standards tend to show up as small mercies: an accurate list of participating offices, fewer claims returned for missing attachments, shorter waits for authorization on a child’s care. For a practice weighing whether to enroll, the administrative burden of a state program is often the deciding variable, and that burden is largely a function of the systems the state bought.
The practical takeaway is modest and real. If you are a patient, verify coverage and participation directly with the plan and with the office before scheduling, because directories lag reality. If you are a clinician, the comment periods on Medicaid systems guidance are open to the profession, and the documents are free to read. Standards written without dental at the table are not usually hostile. They are simply written by people who were thinking about something else.
Comments
Comments publish after a one-click email verification — every voice here is a real one. Comments are reviewed before they appear.
Loading comments…