Background
1. A pediatric dental practice in Texas participates in Medicaid and DentaQuest.
2. Qlarant, the UPIC for the South Western Jurisdiction, issues a Request for Information covering sampled claims from 2022 to 2024 for this practice (NPI and plan identified).
3. The letter cites the practice’s obligation to provide timely access to all documents relating to Medicaid claims and warns of possible sanctions and recoupments if records are not produced.
Triggering event
1. As part of preparing the response, the practice conducts an internal review of each sampled claim.
2. On one claim line involving an extraction of a supernumerary tooth, staff notice that the tooth designation on the claim does not match the supernumerary tooth designation in the clinical documentation.
Key facts
1. The patient’s clinical records, treatment planning documentation, radiographs, and prior authorization all consistently identify the treated tooth as supernumerary tooth #57.
2. The prior authorization submitted to and approved by the managed care organization explicitly reflects treatment of supernumerary tooth #57.
3. The discrepancy is limited to the tooth designation on the claim; the clinical documentation, radiographic support, and authorization are aligned and contemporaneous.
4. The practice’s PM software (Eaglesoft) does not support direct entry of supernumerary tooth designations in the charting system, as confirmed by Patterson Dental Technology.
5. Vendor documentation explains that this limitation can create administrative discrepancies between software‑generated claim data and the underlying clinical documentation when supernumerary teeth are involved.
Practice’s response
The practice prepares a cover letter that:
• References the UPIC case and sample numbers and states that records are enclosed in response to the Request for Information.
• Discloses the tooth‑designation discrepancy on one claim line and describes it as administrative in nature.
• Emphasizes that the discrepancy did not affect services rendered, medical necessity, radiographic findings, or prior authorization; all documentation consistently supports treatment of supernumerary tooth #57.
• Explains the Eaglesoft charting limitation and includes the correspondence from Patterson Dental Technology confirming inability to chart supernumerary teeth directly.
• Lists the enclosed documentation: complete dental records, clinical notes, questionnaires, radiographs, treatment plans, caries charting, prior auth records, vendor correspondence, and other responsive documents.
Training objectives and teaching points
1. Recognize the importance of aligning claim data with clinical documentation and prior authorization, especially for non‑standard tooth designations like supernumerary teeth.
2. Identify risks when practice management software cannot represent clinical reality (e.g., supernumerary tooth numbering) and how to mitigate those risks.
3. Demonstrate how to construct an effective response to a UPIC/Medicaid record request, including transparent self‑disclosure of administrative errors backed by documentation.
Discussion Questions
1. What specific discrepancy did the practice identify during its internal review, and where did the documentation still align?
2. How can a software limitation contribute to apparent claim discrepancies, and what documentation should a practice obtain to explain this?
3. In your practice, what additional safeguards could you implement when billing for supernumerary teeth to ensure that claim data matches clinical documentation and authorizations?
4. The prior authorization did not explicitly reference tooth #57, but clinical notes and radiographs did. What would you do?
5. The software limitation was known but not previously documented with vendor correspondence. What would you do?
Case vignette: “The Supernumerary Tooth That Triggered an Audit”
Setting
A pediatric dental practice participating in Texas Medicaid and managed care receives a formal Request for Information from a federal contractor conducting a program‑integrity review of sampled Medicaid claims over a two‑year period.
The trigger
As part of preparing the response, the practice conducts an internal review of each sampled claim and discovers a discrepancy on one claim line for an extraction of a supernumerary tooth.
• Clinical records, treatment planning notes, radiographs, and prior authorization all consistently identify the treated tooth as a specific supernumerary tooth (e.g., “supernumerary tooth #57”).
• The prior authorization submitted to and approved by the managed care organization also specifies that same supernumerary tooth.
• However, the tooth designation on the submitted claim does not match the supernumerary designation documented in the chart and prior auth.
‘Root’ cause
During the internal review, the team contacts their practice management software vendor to understand how the tooth ended up mis‑designated.
• The vendor confirms that the software does not support direct entry of supernumerary tooth designations in the charting system.
• Because of this limitation, supernumerary teeth cannot be charted using standard supernumerary numbering conventions, which can cause administrative discrepancies between software‑generated claim data and the underlying clinical documentation when supernumerary teeth are treated.
Practice’s response
The practice decides to be proactive and transparent in its audit response.
In its cover letter, the practice:
• Acknowledges the Request for Information and confirms that complete records are enclosed.
• Discloses the single discrepancy involving the tooth designation on one claim line for a supernumerary tooth extraction.
• Explains that the discrepancy is administrative only and limited to the claim’s tooth designation.
• The letter emphasizes that the patient’s contemporaneous clinical documentation, radiographic findings, treatment records, and prior authorization materials all consistently support treatment of the same supernumerary tooth.
• The practice includes the vendor’s written confirmation that the practice management software cannot directly chart supernumerary tooth numbers, documenting the system limitation that contributed to the error.
• To make it easy for the reviewer, the practice encloses and clearly labels:
• Complete dental records
• Clinical notes and treatment planning documents
• Patient questionnaires
• Diagnostic radiographs and treatment plans, including caries charting
• Prior authorization records reflecting the supernumerary tooth
• Vendor correspondence explaining the software’s supernumerary‑tooth charting limitation
• Any additional documentation responsive to the Request for Information
Key teaching points
For dentists and office managers:
• Even when care is appropriate and well‑documented, mismatches between claim data and clinical records (especially tooth numbers) are low‑hanging fruit for auditors.
• Practice management software limitations (like inability to chart supernumerary teeth correctly) are not a defense by themselves; you need contemporaneous documentation plus vendor confirmation and a clear explanation in your response.
• When you find a problem during an audit, a calm, factual letter that:
• Identifies the issue,
• Shows that clinical documentation and authorizations are consistent, and
• Demonstrates that the issue is administrative in nature
• can help keep an error from being framed as something more serious.
Discussion questions for training
1. Where in your own workflow are you most likely to see discrepancies between tooth numbers on claims and tooth numbers in the chart?
2. If your software cannot represent supernumerary teeth correctly, what manual safeguards and documentation would you put in place?
3. How would your practice’s response letter look different if you discovered that several claims—not just one—had similar tooth‑designation issues?
Responding to UPIC/Medicaid Record Requests
PURPOSE
Define a standardized process for responding to UPIC/Medicaid records requests (e.g., Qlarant) to ensure timely, complete, and defensible submissions.
SCOPE
Applies to all Medicaid claims and managed care plans for the practice, including DentaQuest and other Texas Medicaid MCOs.
1. Receipt and logging of request
• Upon receipt of a records request letter, immediately date‑stamp and scan the letter into the compliance or audit folder.
• Log key details in the Audit/Review Log: issuing entity (e.g., Qlarant UPICSW), plan (e.g., DentaQuest), case number, sample ID, internal tracking number, date of letter, and deadline (usually 30 days).
• Notify the compliance lead and practice owner within the same business day.
2. Deadline and submission method
• Confirm the required submission method (e.g., Kiteworks Secure File Transfer) and note any explicit prohibitions (e.g., no PHI via email).
• Add reminders: one for 10 days before due date, one for 3 days before due date, and one on the due date.
3. Identify claims and required documents
• From the enclosed claims listing, create a working table that includes for each claim: patient ID, DOS, tooth/quad, procedure code(s), and amount paid.
• From the records request list, build a document checklist for each claim (e.g., complete chart, radiographs, treatment plan, consent, anesthesia/sedation record, prior authorizations, claim form/EOB).
4. Gather and organize documentation
For each sampled claim:
• Pull all clinical documentation: progress notes, treatment planning records, questionnaires, consents, sedation/anesthesia records (if applicable).
• Pull diagnostic records: radiographs, imaging, photos as requested.
• Pull billing records: claim forms, EOBs, ledger entries, scheduling logs.
• Pull authorization records: prior authorizations/approvals, correspondence with the plan.
• Save documents into a structured folder system (e.g., UPIC Case CSE-XXXX/Patient ID – DOS) to mirror the claims listing.
5. Internal compliance review before submission
For each claim:
• Compare billed procedure codes, tooth/quad designations, and DOS against clinical notes, radiographs, and prior authorizations.
• Specifically confirm:
• Tooth number/designation (including supernumerary teeth)
• Consistency between chart, radiograph, and authorization (same tooth, same procedure)
• Medical necessity documented contemporaneously with services.
• Identify and document any discrepancies (e.g., mis‑numbered tooth, code mismatch, missing signature) in a Discrepancy Log.
6. Handling discrepancies (including software limitations)
When discrepancies are found:
• Determine whether the issue is:
• Administrative (e.g., tooth designation on claim vs. chart)
• Documentation gap
• Potential overpayment or non‑covered service.
• If administrative and clinically aligned (as in the supernumerary tooth #57 example), prepare a concise explanation in the cover letter that:
• Identifies the specific claim line and nature of the discrepancy.
• Explains that clinical records, radiographs, and prior auth consistently support the same tooth and procedure.
• Clarifies that the issue did not affect services rendered or medical necessity.
• If the discrepancy relates to software limitations (e.g., inability to chart supernumerary teeth):
• Obtain documentation from the software vendor confirming the limitation (e.g., Eaglesoft cannot directly chart supernumerary tooth designations).
• Include that vendor documentation in the submission package.
• Document internal mitigation steps (e.g., manual cross‑checks, supplemental notes).
7. Drafting the response letter
The response letter should:
• Reference the requesting entity, case number, sample ID, NPI, and date of the request.
• State that the practice is submitting complete records responsive to the Request for Information.
• Summarize any self‑identified discrepancy succinctly, describing:
• What the discrepancy is (e.g., tooth designation on a claim line for a supernumerary tooth).
• That it is administrative in nature and did not impact clinical services, medical necessity, radiographic support, or prior authorization.
• Note any relevant system limitations confirmed by third parties (e.g., vendor correspondence regarding charting supernumerary teeth).
• Provide a clear list of enclosed materials (e.g., complete dental records, clinical notes, radiographs, prior auth, vendor correspondence).
• Provide contact information for follow‑up.
8. Final QA and submission
• Confirm that all claims listed in the request are accounted for and that documents are legible and logically ordered.
• Confirm that no PHI is sent via prohibited channels (e.g., email) and that the designated secure portal is used (e.g., Kiteworks).
• Upload records, retaining proof of upload (dated screenshots, confirmation emails from the portal).
• File a final copy of the letter and all submitted materials in the audit folder.
9. Post‑submission follow‑up
• Document date of submission and any subsequent correspondence from Qlarant or the plan.
• If findings or overpayments are issued, route them through the practice’s refund/appeals SOP for evaluation and possible appeal.
• Use lessons learned to update training and local documentation/billing procedures.
Simple response‑letter template
Below is a flexible template adapted from this case that you can standardize and tweak for each client.
[Practice Name]
[Practice Address]
[Date]
[Contractor Name]
[Jurisdiction/Department]
RE: Request for Information
Case Number: [Case Number]
Sample Identification Number: [Sample ID]
NPI: [NPI]
To Whom It May Concern:
[Practice Name] respectfully submits the enclosed records in response to the above‑referenced Request for Information.
As part of our internal review of the sampled claims and supporting documentation, we identified [brief description of discrepancy, e.g., a discrepancy involving the tooth designation reported on one claim line associated with a supernumerary tooth extraction]. The patient’s clinical records, treatment planning documentation, radiographs, and prior authorization records consistently identify the tooth as [correct designation].
We determined that the discrepancy is administrative in nature and relates solely to [describe claim‑level issue]. The contemporaneous clinical documentation, radiographic findings, treatment records, and authorization materials consistently document and support treatment of [correct designation], and the discrepancy did not affect the clinical services rendered, the underlying medical necessity for treatment, or the authorization obtained for the procedure.
We further confirmed that our practice management software, [Software Name], does not currently support direct entry of [describe limitation, e.g., supernumerary tooth designations] within the charting system. Documentation from [Vendor Name] confirming this software limitation is included with this submission. This limitation can create the potential for administrative discrepancies between software‑generated claim data and the underlying clinical documentation when such cases are processed.
For ease of review, the enclosed documentation includes:
• Complete dental records
• Clinical notes and treatment planning documentation, patient questionnaires
• Diagnostic radiographs and treatment plan(s)
• [Caries charting and/or sedation/anesthesia records, as applicable]
• Prior authorization records reflecting [correct tooth/procedure]
• [Vendor] correspondence regarding [software limitation]
• Additional supporting documentation responsive to the Request for Information
[Practice Name] appreciates the opportunity to provide clarification and supporting documentation regarding this matter. Should additional information or clarification be required, please contact our office at [phone/email].
Sincerely,
[Provider Name, Credentials]
[Title]
[Practice Name]