Quick answer
Start with the requesting contractor’s letter, claim and service dates. Map every requested item to an existing source record, check identity and chronology, and preserve a manifest of the version actually submitted. Resolve missing or conflicting material through the responsible record owner without inventing documentation. Retain delivery evidence and track the contractor’s response separately from upload completion.
Treat the request as a claim-specific evidence problem
An additional documentation request arrives for a fictional SNF claim covering September 8–21. The records team exports 240 pages. Billing sees a hospital discharge summary and marks the qualifying-stay evidence complete. A second reviewer notices that the summary concerns an August hospitalization, while the claim file identifies a September qualifying stay.
The number of pages was never the useful control. The useful control is whether the right evidence answers the request for the right person, claim and period. First Coast's April 30, 2026 SNF documentation aid identifies physician, nursing, assessment, therapy and hospital record families. The MAC expressly describes the aid as a reference, not a replacement for governing requirements. The actual request and applicable policies determine the response.
Translate the letter into a manifest
Record the request identifier, contractor, claim reference, requested dates, response deadline and accepted delivery route. The deadline comes from the actual letter and applicable review instructions; do not substitute a deadline from an unrelated review program. Assign one packet owner even when several departments supply records.
The following original manifest groups eight work items for the fictional request. It is not an official checklist and does not imply every request requires exactly these groups.
| Evidence group | First-pass finding | Disposition before submission |
|---|---|---|
| Claim and beneficiary match | Claim reference matches | Retain identity check and requested dates |
| Hospital stay evidence | August summary conflicts with September chronology | Obtain the identified September record; document the correction |
| Orders and admission assessment | Present for the requested admission | Confirm signatures, dates and legibility |
| Certification and recertification | Expected certification not found | Escalate to authorized owner; preserve the absence and response |
| Nursing and treatment records | One requested date omitted from export | Retrieve the existing record and rerun completeness check |
| MDS and supporting records | Assessment present; supporting source filed elsewhere | Link the relevant source pages to the assessment period |
| Therapy records | Evaluation and progress records present | Check requested service dates and practitioner identification |
| Notices and other specifically requested material | Notice identified in separate billing folder | Include if applicable to this request and retain its context |
The manifest contains source location, document date, version and final packet page range. Those fields allow the reviewer to find the supporting material without guessing which of several exports was used. Keep sensitive information within approved access and submission channels.
Resolve an absence without rewriting history
The missing certification is not a document-format problem. The packet owner asks the responsible clinical and compliance reviewers whether a valid record exists elsewhere and what the applicable certification rules permit. If the record exists, retrieve it with its authentic signature and dates. If it does not, do not backdate a replacement or relabel another note as a certification.
The response may need a factual explanation or another permitted action under the actual review instructions. Document what was found, what remains absent and who made the substantive determination. A completed manifest can truthfully show an unresolved evidence limitation; marking an item green does not cure it.
The wrong hospital summary is a different problem. Here the correct record exists, so the team replaces the mistaken attachment before submission and retains the internal correction history. It verifies that the replacement supports the relevant chronology rather than merely sharing the beneficiary's name.
Freeze the submitted version and prove delivery
After review, the final packet contains 228 pages. The smaller count reflects removal of unrelated material and inclusion of the omitted requested records. The reviewer reconciles all eight manifest groups to that exact file, checks page readability and confirms that the electronic submission identifies the correct request.
Retain the submitted file, final manifest, submission timestamp and receiving-system evidence. If a transmission fails, record the failure and successful retry rather than overwriting the first event. If the contractor requests more information, link that request to the initial packet and identify precisely what the supplemental submission adds.
A submitted packet, a received packet and a favorable determination are separate statuses. Billing should not release an assumed recovery or close the review solely because someone clicked upload. When a determination arrives, reconcile it to the reviewed claim and route an unfavorable result through the appropriate correction or appeal process.
Evaluate the handoff with the actual exception
A useful platform demonstration follows this fictional file from request receipt through the misdated hospital document, missing certification escalation and final delivery evidence. The buyer should be able to trace each item to its owner and the version submitted. A generic document count or shared folder does not show whether the system supports that work.
The finished artifact is a reproducible response file: another authorized reviewer can identify what was requested, what was supplied, what was unresolved and what the contractor subsequently decided. It supports a medical-review response; it does not itself establish coverage or payment.
Questions & answers
Does a large chart export prove an ADR response is complete?
No. Completeness depends on the request, claim and period. A large export can omit a certification or include another stay’s records. Use a claim-specific manifest.
Can the billing team create a missing certification?
No. Escalate the absence to the authorized clinical and compliance owners. Preserve the actual record and apply the relevant rules for any permissible clarification or delayed documentation.
Does an upload receipt mean the claim will be paid?
No. It proves a transmission event, subject to the receiving system’s status. Medical review and the payment determination remain separate.
Primary sources
Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.