How to Respond to UPIC Record Requests Safely

How to Respond to UPIC Record Requests Safely

A UPIC record request can place a practice under immediate operational and financial pressure. The request may appear routine, but the records you submit can shape an extrapolated overpayment finding, a referral decision, or the scope of future scrutiny. Your response should be timely, complete, organized, and strategically reviewed before it leaves the practice.

Unified Program Integrity Contractors, or UPICs, support the Centers for Medicare & Medicaid Services in identifying and investigating potential fraud, waste, and abuse in Medicare and Medicaid. They may request medical records, claims information, billing documentation, ordering records, proof of delivery, and other materials tied to a defined universe of services. For providers, the central issue is not simply producing documents. It is producing a defensible record that accurately reflects the care delivered and the basis for reimbursement.

What UPIC Record Requests Signal

A request for records does not, by itself, establish wrongdoing. UPICs conduct reviews for many reasons, including data analysis, complaint-driven inquiries, provider comparisons, referral activity, prior audit results, and concerns identified through claims patterns. Still, the request deserves prompt leadership attention because the process can move quickly and the consequences can expand.

The initial letter should be treated as a controlled compliance event. It may identify the beneficiary, date of service, claim number, requested documentation, submission instructions, and due date. It may also contain language that reveals whether the review is focused on medical necessity, documentation requirements, coding, ordering or certifying provider involvement, coverage criteria, or potential billing irregularities.

That distinction matters. A missing signature presents a different response challenge than a pattern of unsupported high-level evaluation and management services, questionable ancillary testing, or services billed without adequate evidence of performance. Before records are assembled, the practice should understand what the request actually seeks and what the requested claims have in common.

The First 48 Hours Matter

The most common early mistake is allowing a record request to move informally through the organization. A front-desk employee, records clerk, or billing team member may begin gathering documents without a centralized process. That can lead to missed deadlines, incomplete production, duplicate submissions, or records that are altered after the request is received without a reliable explanation of what changed and why.

Assign one accountable response lead and immediately preserve the relevant materials. The lead should coordinate clinical, billing, revenue cycle, compliance, and information technology personnel as needed. Preserve the original request, the envelope or electronic transmission details, correspondence, audit logs, and all versions of documents that may be responsive.

At this stage, confirm the deadline and the permitted submission method. Do not assume an extension will be granted, but do not wait until the deadline has passed to request one if the volume, system access issues, or other circumstances make timely production unrealistic. Any communication with the UPIC should be professional, documented, and limited to what is necessary.

A disciplined initial review should answer four questions:

  • Which claims, beneficiaries, and dates of service are at issue?
  • What documents are specifically requested, and which systems hold them?
  • Is the request tied to a stated review concern or coverage requirement?
  • Who will validate completeness, clinical support, and transmission before submission?

How to Prepare UPIC Record Requests for Submission

Producing every available document is not the same as producing a strong response. The practice should identify responsive records, reconcile them against the request, and conduct a substantive review before release. That review should examine whether the documentation supports the service as billed and whether the record is internally consistent.

For example, a claim may include a procedure code that appears correctly entered in the billing system, while the clinical note does not support the procedure’s indication, performance, interpretation, or required supervision. A record may show that an order exists but fail to establish the required certifying relationship. In other cases, documentation may support care but contain conflicting dates, cloned language, unsigned entries, or amendments that create avoidable credibility concerns.

The objective is not to rewrite history or conceal weaknesses. Records must never be altered to create support that did not exist at the time of service. If a legitimate late entry, addendum, or correction is appropriate under the organization’s policies and applicable requirements, it should be clearly dated, attributed, and distinguished from the original documentation. The response team should understand that a late-created document can draw attention if it is presented without context.

Create a production inventory that identifies every requested item, its source, the person who verified it, and whether it was submitted. A simple index can reduce confusion and help demonstrate that the practice responded in an organized manner. Keep an exact copy of everything transmitted, including the final file set, cover letter, delivery confirmation, and any communications concerning the request.

Review the Claim and the Record Together

A medical record review should not occur in isolation from the claim. Compare the submitted claim data against the documentation, including diagnosis codes, procedure codes, modifiers, units, place of service, rendering provider, ordering provider, and dates. When applicable, evaluate whether the service meets payer coverage criteria and documentation standards.

This is where provider organizations often discover that the risk is broader than a single chart. If several requested claims reflect the same documentation failure, billing workflow gap, template problem, or staff training issue, the practice may face a pattern concern. Early identification allows leadership to assess the exposure and begin targeted corrective action without waiting for findings.

Avoid Reactive and Overbroad Responses

Pressure can produce poor decisions. Some practices submit records quickly without review because they fear appearing uncooperative. Others send large volumes of unrelated material in the hope that more documentation will help. Neither approach is reliably protective.

An incomplete submission can invite adverse assumptions. An overbroad submission can introduce inconsistencies, disclose records not requested, and complicate the review. The appropriate approach depends on the request language, the type of records involved, and the provider’s actual documentation posture. Precision is generally more defensible than volume.

Practices should also avoid informal explanations that are unsupported by the record. A phone call or cover letter should not speculate about why documentation is missing, characterize a billing error before it has been fully assessed, or make admissions that exceed the known facts. If significant potential overpayment, exclusion, referral, or enforcement exposure is present, the practice should consider involving experienced compliance and legal advisors early in the process.

Prepare for What May Follow

Submission is often the beginning of the matter, not the end. A UPIC may issue additional documentation requests, seek interviews, request clarification, expand the sample, refer matters to another agency, or issue findings that require a response. Maintain a controlled audit file throughout the process and track every deadline.

If the review identifies weaknesses, use the information to assess root causes. Was the issue caused by documentation habits, unclear policies, template design, coding edits, credentialing processes, charge capture, or inadequate oversight? A credible corrective action plan addresses the operational cause, identifies accountable owners, establishes monitoring, and documents measurable improvement. Generic retraining alone rarely resolves a recurring control failure.

For organizations facing a significant audit, an independent pre-submission review can provide a clearer view of the records through an enforcement and payer-integrity lens. Praevera Risk Associates helps providers evaluate documentation and claims exposure, organize defensible audit responses, and develop corrective actions that protect both reimbursement and regulatory standing.

The strongest response to a UPIC request is built before the letter arrives: records that reflect the care provided, claims that match the record, clear ownership of audit communications, and quality assurance processes that identify vulnerabilities early. When a request does arrive, disciplined action gives your practice the best opportunity to respond with confidence and preserve its integrity.