D9310 is commonly used in US CDT reporting for a consultation involving a diagnostic service by a practitioner other than the requesting practitioner. It is not a substitute for every new-patient or specialist evaluation. Use the current ADA nomenclature and descriptor, document the requesting source and communicate the opinion.
Important: US educational guidance only. CDT is updated annually and is ADA intellectual property; verify the licensed current edition and each payer contract.
Consultation elements
A defensible consultation usually includes a request for an opinion or advice, a clinically appropriate assessment and communication of findings back to the requesting practitioner.
Consultation versus evaluation
An evaluation may establish care and lead directly to treatment; a consultation answers a defined question. The patient's route to the office, treatment responsibility and current CDT descriptor matter.
Referral documentation
Record requesting practitioner, date, question, records supplied and urgency. If the patient self-refers, verify whether the consultation code remains appropriate.
Clinical record
Document history, examination, tests, imaging reviewed, diagnosis/differential, prognosis, options, risk and recommendation. A brief courtesy conversation is not automatically a reportable consultation.
Communication back
Send a dated written report or documented communication to the requester, including findings and recommended next steps. Preserve proof of transmission consistent with privacy law.
Same-day treatment
If treatment is performed at the consultation visit, payer bundling or code rules may apply. Report actual services and check the current descriptor and plan policy.
Imaging
Do not repeat images merely for claim support. Review provided diagnostic images and order additional imaging only when justified; document why.
Coverage
Plans may limit consultations by specialty, referral, frequency or same provider. Coverage does not redefine the clinical service.
Examples
Appropriate scenarios may include a general dentist requesting an endodontic, surgical, oral-medicine or prosthodontic opinion. Routine periodic evaluation or an unsolicited second opinion may require different reporting.
Denials
Common reasons include absent referral, no report, duplicate evaluation, frequency limit or non-covered consultation. Appeal only with documentation matching the service.
Audit checklist
Requester and question present; assessment complete; opinion recorded; communication returned; codes current; privacy protected.
Core US claim workflow
- Verify patient identity, eligibility and plan details.
- Diagnose and treatment-plan without allowing benefits to dictate care.
- Perform and document the actual service.
- Select the current code whose full nomenclature and descriptor match.
- Complete tooth, surface, arch, date, provider and fee fields accurately.
- Attach only relevant requested evidence.
- Reconcile acceptance, payment, adjustment and patient balance.
Coverage is not coding
A code describes a service; the plan decides benefits under its contract. A denial does not prove miscoding, and available benefits do not justify selecting an inaccurate code. ADA guidance emphasises coding for what was done and reporting the full fee.
Documentation template
| Field | Record |
|---|---|
| Reason | Symptoms, diagnosis or treatment objective |
| Findings | Objective examination and imaging |
| Service | Site, material, components and technique |
| Necessity | Why this service was clinically appropriate |
| Alternatives | Options discussed and patient decision |
| Outcome | Completion, instructions and follow-up |
Narrative-writing principles
Write concise patient-specific facts. Link diagnosis, findings and procedure. State dates and sites consistently. Avoid copied superlatives, unsupported “medical necessity” language and a long chronology unrelated to the payer question.
Attachments checklist
Confirm images are diagnostic, dated, oriented and labelled; photographs have consent; periodontal charting is current; operative or laboratory records match the claim; and no unnecessary protected information is disclosed.
Predetermination and authorisation
Explain that predetermination, pre-estimate or prior authorisation is not a payment guarantee. Eligibility, maximums, exclusions, coordination of benefits and plan status can change before claim adjudication.
Denial triage
Classify the response: missing information, coding mismatch, contractual exclusion, frequency, alternate benefit, eligibility, duplicate or payer processing error. Correct a claim only when it was inaccurate; otherwise appeal with focused evidence and cite the plan document.
Compliance risks
- Upcoding or downcoding to obtain a benefit
- Billing a service not completed
- Changing dates or sites
- Waiving copayments inconsistently or deceptively
- Unbundling contrary to the performed service
- Using another provider’s credentials
- Copying narratives that conflict with the chart
Annual update process
At each CDT release, review added, revised and deleted codes, errata, practice-management mappings, templates and staff training. Preserve the code set applicable to each date of service.
Frequently asked questions
Does a code guarantee reimbursement?
No. Payment depends on the benefit contract, eligibility and payer adjudication.
Should a code be changed after denial?
Only if the original claim did not accurately represent the record. Never change the code solely to trigger payment.
Can this article replace the CDT manual?
No. Use the licensed current ADA CDT source for complete nomenclature and descriptors.
Conclusion
Accurate reporting follows the clinical record, current official code source and transparent patient communication.
Operational review before submission
A reliable review separates four layers that are often mixed together: the clinical decision, the clinical record, code selection, and benefit adjudication. The clinician owns the accuracy of the diagnosis and service record. The coding team translates that record using the current authoritative code set. The benefits team verifies administrative requirements. A payer then applies the contract. Keeping these layers distinct prevents coverage rules from rewriting the chart.
Eight-point preflight
- Identity: confirm patient, provider, location and date.
- Diagnosis: confirm the assessment appears before or contemporaneously with treatment.
- Specificity: identify tooth, site, arch, quadrant, material or time detail when relevant.
- Completion: confirm the reported service reached the code’s reportable endpoint.
- Consistency: compare note, claim, images, laboratory record and ledger.
- Authority: check the current official code source rather than an old cheat sheet.
- Benefits: verify administrative rules without allowing them to change the code.
- Communication: present patient responsibility as an estimate, not a promise.
Decision matrix for documentation quality
| Finding | Action before claim | Do not do |
|---|---|---|
| Service is clear; coverage uncertain | Report accurately and verify benefits | Replace it with a “covered” code |
| Record lacks a required clinical fact | Ask the treating clinician for a compliant clarification | Infer or invent the fact |
| Attachment and note conflict | Resolve the discrepancy and preserve amendments | Submit whichever version looks favorable |
| Current code changed | Apply the code set effective for the service date | Use a familiar obsolete entry |
| Payer requests more information | Answer the precise request with relevant records | Send an uncontrolled chart dump |
| Denial cites frequency or exclusion | Review eligibility, history and contract language | Assume the procedure was miscoded |
How to write a useful narrative
A good narrative is brief enough to review and specific enough to connect evidence with the service. Start with the diagnosis and objective findings, identify anatomy, explain the decision, state what was completed and point to dated attachments. Avoid adjectives such as “severe” unless the clinical measurements support them.
Narrative formula
On [date], examination of [anatomy] identified [diagnosis] supported by [objective findings]. Because [patient-specific clinical rationale], [service] was performed/completed on [date] by [provider]. The record includes [relevant attachments]. Outcome and follow-up: [facts].
What weak narratives look like
- They repeat the procedure name without explaining need.
- They use payer language instead of clinical language.
- They contain copied measurements that do not match attached records.
- They add unrelated history and obscure the relevant facts.
- They state that authorization “guarantees” payment.
Attachment governance
Establish an office protocol for naming, dating, orienting and exporting attachments. Before transmission, verify that every image belongs to the correct patient and that no unrelated protected information is included. Maintain the original diagnostic-quality record even if the payer portal compresses the submitted copy.
| Attachment risk | Control |
|---|---|
| Wrong patient or side | Two-identifier and orientation check |
| Undated image | Verify acquisition date in source system |
| Illegible export | Review the exact transmitted file |
| Excess information | Send the minimum relevant record requested |
| Missing audit trail | Retain submission confirmation and contents |
Predetermination and patient estimates
Predetermination can reveal exclusions, frequency limits, alternate benefits and documentation requests, but it is not a contract for payment. Eligibility may change before treatment, and adjudication may depend on the final service. Written estimates should state assumptions, expected plan payment, possible patient balance and the fact that clinical recommendations do not depend on benefit design.
Denial response workflow
- Read the explanation of benefits and exact adjustment reason.
- Determine whether the issue is eligibility, coverage, coding, missing information, authorization, coordination or processing.
- Compare the submitted claim with the original chart and current authoritative sources.
- Correct a clerical error transparently or appeal a supportable decision with focused evidence.
- Never modify the underlying clinical facts to fit a payer criterion.
- Track the outcome so recurring workflow failures can be corrected.
Audit sampling plan
Each quarter, select a small sample across providers, locations and payers. Compare the service date, code, anatomy, narrative, attachments, ledger and remittance. Classify defects as clinical-record, coding, administrative or communication failures. Assign an owner and completion date; education without follow-through is not a control.
Team roles and handoffs
| Role | Primary responsibility | Escalation trigger |
|---|---|---|
| Clinician | Diagnosis, findings, service and outcome | Missing or contradictory clinical fact |
| Assistant/hygienist | Permitted contemporaneous observations and records | Scope or authentication uncertainty |
| Coder/biller | Current code selection and clean claim | Ambiguous service or code-set conflict |
| Benefits coordinator | Eligibility, authorization and estimate | Plan language conflicts with claim facts |
| Compliance lead | Policy, audit and corrective action | Pattern, repayment or legal concern |
Frequently asked questions
Can a payer tell the practice which code to use?
A payer can explain how it adjudicates a submitted code, but the claim must accurately report the documented service. Ask for policy language when coverage is unclear.
Should every claim include a narrative?
No. Follow the payer’s requirements and use a narrative when it adds necessary context. Unrequested, repetitive text may slow review.
Can a note be completed after the visit?
Records should be contemporaneous. A legitimate late entry or amendment should be identified, dated, attributed and preserve the original according to office policy and applicable rules.
What if the patient asks the office to change a code?
Explain that codes report services actually provided. The team may correct an error, but cannot change accurate reporting to produce a preferred benefit.
How often should code references be updated?
At least for every annual code-set release, with targeted training and updates to templates, software favorites, fee schedules and payer rules.
Editorial and clinical-use disclaimer
This educational material supports workflow design. It does not replace the current codebook, a payer contract, professional clinical guidance, state law, legal advice or a patient-specific decision. Practices should obtain qualified guidance for ambiguous or high-risk cases.