Additional Documentation Requests From Payors: ADRs and Denial Prevention

Because records are the visible deliverable, a Medicare additional documentation request can look like a straightforward chart pull. Operationally, it is a release of information workflow with a direct revenue consequence.

Clinical documentation remains the foundation. Yet a complete chart cannot compensate for late routing, incorrect scope, or delivery evidence stored outside the claim record. Many avoidable ADR denials begin in those handoffs.

The ADR control chain connects five responsibilities: intake, scope, packet integrity, delivery evidence, and outcome tracking. A delay at one point creates pressure at the next. Late routing shortens review time and increases the chance that staff miss an order, signature, report, or related note.

In this article, we examine how breakdowns across the ADR control chain can turn complete documentation into an avoidable denial, and what practices can do to keep each response on track.

What Is a Medicare Additional Documentation Request?

An additional documentation request, or ADR, is a Medicare contractor’s request for records or related information during medical review. The contractor uses the documentation to evaluate whether a claim meets Medicare coverage, coding, billing, payment, and medical necessity requirements.

An ADR may support a prepayment or post-payment review. It differs from prior authorization because it occurs during claim review rather than before the service. A routine claim edit may require a billing correction without a supporting record packet.

Commercial payors can send similar post-claim documentation requests under different names. Their request letters, contracts, and program rules govern the response. Medicare terminology and deadlines should remain within the Medicare context. The same operating controls can still help practices manage other payor requests.

Why Can a Complete Chart Still Lead to an ADR Denial?

A complete chart does not prove that the practice submitted the right records on time or retained delivery evidence. ADR risk develops in the space between the clinical record and the contractor’s review.

A request may sit in an unmonitored fax folder, or staff may send a progress note without its related order. Even a complete packet can go to the wrong destination, and a confirmation left in one employee’s inbox can make the response hard to prove.

Federal response windows make early control essential. For prepayment review, 42 CFR 405.903 generally allows 45 days for a contractor request and 30 days for a UPIC request. The same general response windows appear in 42 CFR 405.929 for post-payment review. Good cause exceptions may apply, but staff should still treat the request letter as the working source for deadlines and submission instructions.

These handoff failures create operational and financial consequences. Late routing reduces review time, incomplete packets create rework, and missing delivery evidence weakens a nonreceipt dispute. By the time leaders see the denial, the original process failure may be weeks old.

What Does the ADR Control Chain Include?

The ADR control chain helps leaders evaluate the response as one connected process. A practice can perform every task and still lack control when ownership, status, packet history, and evidence are disconnected.

Intake Control

Every additional documentation request should enter one accountable workflow. That rule applies to mail, fax, portal notices, electronic notifications, billing notices, and front desk handoffs.

Log the contractor, patient, claim number, date of service, date received, response deadline, submission instructions, owner, and current status. Staff should immediately escalate any request without a named owner or documented due date.

Scope Control

Confirm exactly what the reviewer requested before staff begin pulling records. Check the patient identifiers, claim, dates of service, record types, review reason, submission method, and deadline.

Scope review should also identify requests that need authority or disclosure review. A controlled release of information process helps staff verify authority, apply the right disclosure standard, and preserve a request-specific activity history.

Packet Integrity

Build the packet around the reviewed claim and the contractor’s instructions. Supporting documentation can come from outside the billed date when it helps establish coverage, coding, payment, or medical necessity.

Organize the response so the reviewer can follow the connection between the billed service and its support. Excess material can obscure that connection, while missing context can leave the claim unsupported.

Delivery Evidence

The practice should be able to show what it sent, when and where it sent it, and which confirmation proves delivery.

Under 42 CFR 405.930, a contractor may deny a claim when requested documentation does not arrive on time. Store the confirmation with the request and final packet version so staff do not have to search personal inboxes or local folders later.

Outcome Tracking

Continue tracking after the packet leaves the practice. Record whether the claim is paid, denied, reopened, appealed, or still pending.

Outcome data can reveal recurring issues by location, service line, contractor, record type, and submission method. Leaders can then direct training or workflow changes to the point of failure instead of treating all denials alike.

What Records May a Medicare ADR Require?

The ADR letter controls the response. Record requirements vary by claim type, service, review issue, and contractor instructions. These examples illustrate common support categories rather than a universal packet.

Claim Type	Records Often Requested	Review Risk If Missing
Evaluation and management	Visit note, history, exam, medical decision making, related prior notes	The reviewer may be unable to validate the billed level or clinical rationale.
Procedure or surgery	Operative report, orders, preoperative note, anesthesia record, pathology report	The packet may not connect the procedure code to the documented service or medical necessity.
Diagnostic imaging	Imaging report, order, indication, related clinical notes	The reviewer may be unable to confirm the order, indication, or need for the study.
Therapy or ongoing treatment	Plan of care, progress notes, treatment logs, reassessments	The record may not support the frequency, duration, or continued need for treatment.
Modifier-supported claims	Same-day notes, distinct service documentation, procedure note	The packet may not establish that the separately billed service was distinct.

For CERT reviews, CMS instructs medical record staff and third-party record services to provide records that support payment. Those records may include relevant documentation from before the date listed in the request. The CERT guidance also directs responders to follow the ADR instructions when submitting those records.

How Can Practice Leaders Find Weak ADR Controls?

Practice administrators can test the workflow before denial volume rises. Sample recent requests and trace each one from receipt through claim outcome.

Control Question	Warning Sign
Where did the request enter the organization?	Requests arrive through several channels without one queue or routing rule.
Who owned the response?	Ownership changed informally or was never recorded.
How was the deadline established?	Staff relied on memory or counted from the wrong date.
How was packet completeness confirmed?	No request-specific checklist or second review exists.
Where is delivery proof stored?	The confirmation remains in email, a fax device, or a local folder.
What happened to the claim?	The ROI or medical records team cannot see the outcome.

Turnaround time alone will not explain the workflow. Leaders should also track on-time submissions, completed quality checks, rework, nonreceipt disputes, denials, and repeat issues by location or service line.

These measures connect release work to healthcare revenue cycle management without shifting billing or clinical decisions to the ROI team. The request history supplies operational evidence that revenue cycle leaders can use to evaluate the result.

How Should Practices Handle Electronic ADR Exchange?

CMS’s Electronic Submission of Medical Documentation system lets Medicare review contractors send electronic requests and exchange supporting medical documentation. Electronic exchange reduces dependence on mailed or faxed paper, but practices still need consistent routing, ownership, packet review, and evidence retention.

Every intake and delivery channel should feed the same operating record. This approach also strengthens broader healthcare audit readiness by creating a repeatable record of what the organization received, released, and carried through final disposition.

Where Does ChartRequest Fit in the ADR Workflow?

ChartRequest centralizes the medical records release workflow that supports ADR fulfillment, giving practices one place to manage request intake, ownership, packet status, fulfillment activity, and delivery evidence.

ChartRequest release of information software helps teams see where each request stands, what still needs attention, and which activity supports the completed response. That visibility reduces reliance on scattered inboxes, spreadsheets, and local files.

Through ChartRequest’s provider solutions, practices can standardize medical records release across billing, clinical, medical records, and compliance teams while gaining clearer visibility into each request from intake through fulfillment.

ChartRequest supports the medical records request and release process. Clinical, coding, and billing teams remain responsible for coding, medical necessity, clinical sufficiency, appeals, and record retention.

Schedule a personalized consultation to see how ChartRequest can centralize ADR-related medical records release, strengthen handoff control, and preserve the evidence behind each response before a deadline becomes a denial.

Frequently Asked Questions