# Four software renewal questions to help get HbA1c to the dental chair

By MarketScale Newsroom · Published 2026-11-18 · Healthcare on MarketScale
Canonical: https://www.marketscale.com/industries/healthcare/four-software-questions-that-could-bring-a-patients-hba1c-to-the-dental-chair

> A dentist turned hospital data developer lists four vendor questions on FHIR, health information exchange, SNODENT and e-referrals for dental renewals.

## Key points

- The HbA1c a dentist asks a patient to remember already sits as a structured field in a hospital data warehouse; getting it to the chair starts with what a practice asks its software vendor.
- Two of the five FHIR resources most relevant to dentistry, Patient and Observation, belong to the normative core of FHIR Release 4, where future changes are meant to stay backward compatible.
- At renewal, ask vendors specifics: which FHIR resources they expose, whether they can query the regional HIE, whether they code in SNODENT, and whether they support structured referrals.

Around 2019, in a clinic in Coimbatore, India, a woman in her late forties with long-standing type 2 diabetes came in for a routine extraction. She described her diabetes as managed. Her dentist, Dr. Deepashree Rajendraprasad, asked when she had last seen her physician and what her most recent HbA1c was. She had no printout with her, and the lab was across town. Rajendraprasad went ahead on clinical judgment, and the patient healed more slowly than expected. She recovered in the end. Rajendraprasad says she has thought about that patient many times since.

Rajendraprasad now works as a business intelligence developer at a large US health system, building reports and dashboards for its quality and patient safety team. In a Nov. 17 piece for Dental Economics, she describes that same lab value from the other side. In her current job, HbA1c is a structured data element, refreshed in the business data warehouse and available at the point of care. The HbA1c a dentist asks a patient to remember already sits as a structured field in a hospital data warehouse; getting it to the chair starts with what a practice asks its software vendor.

The most practical part of her article is a short list: four questions she says every practice should put to its practice management software vendor at the next contract renewal. For a practice owner or the operations lead at a dental group, that turns interoperability from an aspiration into something specific enough to go in a renewal checklist.

> Many of the most consequential judgments I made as a dentist were based on knowledge I did not possess., Dr. Deepashree Rajendraprasad, Dental Economics

## Why medical history stops at the front desk

Most US dentistry, Rajendraprasad writes, happens in small independent offices running practice management software that was never designed to exchange data with medical records. The medical history taken at the front desk is mostly what the patient reports. The office records it accurately, but it is often incomplete or out of date, and it depends entirely on what the patient remembers and chooses to share.

She gives three cases where that gap changes treatment. A patient on a direct oral anticoagulant forgets to mention it. A patient on intravenous bisphosphonates has an oncology team that would have flagged the risk of medication-related osteonecrosis if the dentist had been part of the conversation. A patient's poorly controlled diabetes would show up in a recent HbA1c that should shape how aggressive periodontal therapy is. In each case the information exists somewhere in the wider health system. It just never reaches the operatory.

Medicine spent the past decade building the plumbing to move that data. The 21st Century Cures Act and the ONC Final Rule on interoperability and information blocking, finalized in 2020, require certified health IT systems to make patient data available through standardized application programming interfaces, especially HL7's Fast Healthcare Interoperability Resources (FHIR) standard. Dentistry has been slow to adopt those principles, she notes, but the framework is already in place.

Her day job shows what connected data looks like when it's working. She works in Epic Clarity and Caboodle, the relational data warehouse and dimensional analytics platform behind the Epic electronic health record. Clinical events are documented in real time, then loaded into organized tables the analytics team can query.

Her team tracks Agency for Healthcare Research and Quality Patient Safety Indicators, CMS Core Measures, hospital-acquired infection rates, 30-day readmissions, length of stay and mortality on dashboards that refresh on a schedule. These aren't reports assembled by hand months after the fact. A clinician can drill down from a unit-level rate to a single encounter in seconds.

When the hospital reports to CMS's Hospital Inpatient Quality Reporting program or to the Joint Commission, the underlying data has already been validated, reconciled and governed. The same data feeds clinical decision support, population health stratification and value-based contracts. She describes "connected" as that whole loop: data acquisition, standardization, governance, reporting and feedback into care.

That loop is a handy way to read what follows. FHIR and exchange access concern getting data in, standardized terminology concerns making it comparable, and structured referrals concern sending it back into care, so the checklist could be seen as dentistry's entry ramp to the same cycle.

Her verdict on dentistry is blunt. The technical capability to join that stack exists, she argues, and what has often been missing is the willingness to ask for it. That puts the first move with whoever signs the software contract, not with the IT department.

## The renewal checklist, question by question

Rajendraprasad says none of these requests are unusual. All of them are routine expectations in medical IT.

1. Does the product support HL7 FHIR APIs, and which FHIR resources does it expose?
2. Can the practice connect to the regional health information exchange?
3. Does the software use standardized medical terminology for diagnoses and procedures?
4. Can it send and receive structured electronic referrals to and from medical providers?

### FHIR: ask for resources by name

On the first question, she names the resources that matter for dental care: Patient, Condition, MedicationStatement, AllergyIntolerance and Observation. A vendor that can't answer, she writes, hasn't yet engaged with modern interoperability standards. HL7's own account of FHIR Release 4 adds useful context. The release's base passed a normative ballot, meaning future changes to those sections are intended to be backward compatible.

The normative portions include the RESTful API, the JSON and XML formats and basic datatypes, the terminology layer, the conformance framework (StructureDefinition and CapabilityStatement), and two key resources: Patient and Observation. HL7, which has affiliates in 35 countries, said the R4 base would go to the American National Standards Institute as a normative standard, and that applications implementing those sections no longer risk falling out of conformance.

So two of the five resources on her list sit in the most stable part of the standard. That suggests a practice can reasonably expect a clear yes or no on those two. For the other three, it's worth asking the vendor to state in writing which FHIR release it supports.

HL7 said its priority after R4 was to bring more sections of the standard to normative status, and it points implementers to its FHIR Maturity Model to see how each part is advancing. That gives a practice an outside reference for where Condition, MedicationStatement and AllergyIntolerance stand, so the vendor's answer can be checked against the standard's own record.

Block Field

### Exchange access, terminology and referrals

The second question is about local reach. Most states have at least one health information exchange, Rajendraprasad writes, and many offer a query interface that lets authorized clinicians see a patient's recent medications, problem list and lab results. Read-only access alone would change the history conversation at the chair: the current medication list plus the latest HbA1c, international normalized ratio (INR) or basic metabolic panel.

The third question turns on SNODENT, the clinical terminology the American Dental Association maintains to work alongside SNOMED CT, the vocabulary most of medicine uses. The ADA describes SNODENT as an ANSI-recognized standard that is harmonized with SNOMED CT and aligned with ICD-10-CM for billing. SNODENT codes, it says, work the same way SNOMED codes do, and many oral health conditions and specific anatomical sites exist only in SNODENT. SNOMED CT is approved for use with HL7 documents, including FHIR.

The association also maintains SNO-DDS GD, a smaller subset built from the conditions general dentists record most often, plus an orthodontic subset, with other specialty subsets in development. One entry in the ADA's change history ties straight back to the front desk: since 2007 it has added terms from the ADA Patient Dental and Medical Health History Information Form and built a cross-walk from SNODENT to ICD-10-CM. The vocabulary for coding the intake history already exists, which makes the software the deciding factor.

Rajendraprasad's point is that practices coding in standardized terms can be counted in community health and accountable care reporting. Practices that record findings only as free text can't.

The fourth question replaces paper. A structured digital referral carries a clinical note, a radiograph and a stated reason for the consult. That closes the gaps paper referrals leave behind and creates a record that supports both clinical care and medicolegal protection.

## Who gains most at the chair

The clinical payoff, as Rajendraprasad describes it, is concrete. Screening patients on anticoagulants before surgery becomes a standing protocol instead of a conversation that depends on memory. Periodontal plans for patients with diabetes can be sorted by the latest HbA1c rather than by how well the patient says they're doing. Surgical planning for patients with a history of bisphosphonate or antiresorptive therapy can draw on the actual medication record, including how long the patient took the drug and how it was given.

The checklist has limits, and they follow from her own description. Exchange access depends on what the regional exchange offers: many have query interfaces, not all. A small independent office whose current software wasn't built for interoperability may find the realistic first step is read-only lookups through an exchange, with FHIR integration and structured referrals coming later.

The checklist matters most for practices that see many medically complex patients, where one missing anticoagulant or HbA1c value changes the treatment plan. A practice with a mostly healthy patient base will get less out of it.

Block Field

## Quality measures dentistry could help write

Rajendraprasad's broader argument looks past the single patient. Hospital quality teams can report to CMS and the Joint Commission without a scramble because their data is already structured and governed. Dentists who push for structured data now, she writes, can help shape how oral health quality is measured as value-based care spreads. Practices that keep free-text records will be left out of that conversation by default.

The ADA makes a similar case for its terminology, listing more granular data for oral health research and accurate public health reporting among SNODENT's uses. There is also a direct route into the vocabulary itself. A SNODENT Maintenance Committee within the ADA's Center of Excellence on Dental Care and Financing reviews changes, including requests submitted by users, and the ADA Standards Program Consensus Body 3 Terminology & SNODENT, which ballots revisions, is open to all interested parties. For a dentist who wants a say in how oral health gets measured, that is a concrete place to start.

Two dates are worth watching. The ADA releases SNODENT updates every fall, and each release may refine relationships between concepts, retire ones no longer in use and introduce new ones, so terminology support belongs in any contract being negotiated this season, along with a question about how quickly the vendor loads each new release. The second date is the practice's own renewal, which is when all four questions are cheapest to ask.

## Sources

- [Insights gained from transitioning from the dental chair to the hospital data warehouse](https://www.dentaleconomics.com/science-tech/article/55403882/insights-gained-from-transitioning-from-the-dental-chair-to-the-hospital-data-warehouse) (Dental Economics)
- [HL7 Publishes FHIR® Release 4](https://blog.hl7.org/hl7-publishes-fhir-release-4)
- [Systematized Nomenclature of Dentistry (SNODENT) | American Dental Association](https://www.ada.org/resources/practice/dental-standards/snodent)

Tags: Deepashree Rajendraprasad, HL7 FHIR, SNODENT, Health information exchange, Dental practice management software, Epic Caboodle

---
Source: MarketScale, https://www.marketscale.com/industries/healthcare/four-software-questions-that-could-bring-a-patients-hba1c-to-the-dental-chair. Published for AI indexing and citation; cite the canonical URL. Site guide for agents: https://www.marketscale.com/llms.txt
