RADV Medical Record Retrieval: Helping Your Practice Respond Within the Five-Month Submission Window
A practical guide for physician practices and health systems on retrieving and delivering medical records for Medicare Advantage RADV audits within CMS's five-month submission window, including workflows, quality checks, staffing, vendors, and common pitfalls.
KNOWLEDGE CENTER
11/15/202611 min read
When CMS audits a Medicare Advantage (MA) contract through Risk Adjustment Data Validation (RADV), the plan has a fixed period to submit medical records that support the diagnoses it reported for each sampled enrollee. CMS restored a five-month medical record submission window in 2026, after briefly shortening it to three months in 2025, and stated that the five-month window will apply to payment year 2020 and later audits. For payment year 2020, the window ran from April 13 to August 28, 2026. For payment year 2021, it ran from June 22 to November 6, 2026.
Five months sounds generous, but most of that time belongs to the plan. Plans must identify which providers saw each sampled enrollee, request records, wait for them to arrive, review them, select the strongest record for each audited condition, request additional records when the first ones fall short, and upload everything to CMS before the deadline. Every week a record sits in a provider's request queue is a week the plan cannot use. With CMS now auditing every RADV-eligible contract roughly every three months, practices and health systems that serve MA enrollees can expect a steady and growing flow of requests from multiple plans and retrieval vendors.
This article offers a practical playbook for providers: how the five-month window translates into provider deadlines, how to build an efficient retrieval workflow, what quality checks matter, how to work with retrieval vendors, and how to avoid common mistakes. It is educational and not legal advice.
How the Five-Month Window Works for Providers
The Plan's Timeline
A typical plan timeline within a five-month window looks something like this:
• Weeks 1 to 2: CMS provides the list of sampled enrollees and audited conditions. The plan identifies the providers and dates of service most likely to support each condition.
• Weeks 2 to 8: The plan and its retrieval vendors request records from providers.
• Weeks 4 to 14: Records arrive and are reviewed by the plan's coders. Records that do not support the condition trigger requests for additional dates of service or other providers.
• Weeks 12 to 20: The plan selects up to two records per audited condition, prepares submissions, and uploads them to CMS before the deadline.
Because of this sequence, plans usually ask providers to respond within a few weeks, and second-round requests late in the window may come with very short deadlines.
Why Speed Matters
A plan can submit only two records per audited condition, and CMS needs only one valid record to support payment. If the first record a provider sends is incomplete, unsigned, or from the wrong year, the plan may need a second record from the same or another provider, and time may run out. Fast, complete, accurate responses make it more likely the plan can support legitimate diagnoses, which protects revenue in provider risk-sharing arrangements and reduces follow-up audits of the provider's coding.
Building a RADV Retrieval Workflow
Centralize Intake
Designate one team, whether health information management, release of information, a risk adjustment department, or a contracted vendor, to receive all MA record requests. Publish a single intake channel, such as a dedicated fax line, secure email address, or portal, and ask plans to use it. Scattered requests to individual clinics lead to missed deadlines.
Log Every Request
Track each request in a log or workflow system with:
• The requesting plan and vendor.
• The date received and the due date.
• The enrollee identifiers and requested dates of service.
• The staff member assigned.
• The date records were sent and the method.
• Any follow-up requests.
The log lets leadership monitor volume and turnaround and gives the organization proof of timely response.
Verify the Requester
Confirm that the requester is the MA plan or an authorized vendor. Maintain a list of verified plan contacts and vendors, and call the plan to verify any unfamiliar vendor. Verification protects patients and the organization from fraudulent requests.
Prioritize by Deadline
Sort requests by due date, and flag rush or second-round requests. Set an internal turnaround target that is shorter than the plan's deadline, such as five to ten business days.
Retrieve Complete Records
For each requested date of service, retrieve the complete encounter documentation, typically including:
• The progress note or visit note, with history, examination, assessment, and plan.
• Problem list and medication list, where they show conditions were addressed.
• For inpatient stays, the discharge summary, history and physical, and consultation notes.
• For outpatient hospital services, the relevant visit documentation.
• Any addenda made at the time of care according to organizational policy.
Avoid sending only claim forms, superbills, or summaries, which generally do not meet RADV standards.
Run Quality Checks Before Sending
Before release, check each record for the elements that commonly cause RADV records to fail:
• Correct patient: name and identifiers match the request.
• Correct date of service: the encounter falls within the requested date and the payment year's data collection period, generally the prior calendar year.
• Acceptable encounter type: a face-to-face visit or qualifying telehealth encounter with an acceptable provider type, or a hospital inpatient or outpatient record.
• Signature and credentials: the note is signed and dated by the treating provider, with credentials shown.
• Legibility: scanned and printed records are readable.
• Completeness: all pages are included, including the assessment and plan.
If a record lacks a signature, follow the plan's instructions and CMS guidance on signature attestations. Do not add signatures or alter old records.
Deliver Securely
Use the plan's secure portal, secure file transfer, encrypted delivery, or other approved methods. Confirm receipt where possible. Record the delivery in the request log.
Handle Follow-Up Quickly
Second-round requests often come late in the window with short deadlines. Treat them as high priority.
Electronic Health Record Access
Many plans offer providers the option of granting their coders remote, read-only access to the electronic health record, or of using EHR integrations that let plans retrieve records directly. These arrangements can speed retrieval dramatically and reduce staff workload. Before granting access, providers should:
• Execute appropriate agreements addressing permitted uses, minimum necessary access, security, and audit trails.
• Limit access to the enrollees and dates of service needed.
• Monitor access logs.
• Confirm that the arrangement complies with HIPAA and the organization's policies.
Working With Retrieval Vendors
Plans often use third-party retrieval vendors, and providers may use their own release-of-information vendors. To make vendor relationships work:
• Confirm each vendor's authorization from the plan.
• Agree on delivery methods, formats, and turnaround times.
• Clarify whether copy fees apply. Provider contracts with MA plans often address record copying, and some contracts prohibit charging plans for records needed for audits.
• Monitor vendor performance and escalate problems early.
Onsite retrieval, in which vendor staff come to the practice to scan or print records, may be offered for high-volume requests. Supervise onsite vendors and limit access to the records requested.
Staffing for Higher Volume
With CMS auditing every eligible contract on a rolling schedule, request volume can rise sharply and arrive in waves. Organizations should:
• Forecast volume based on MA enrollment and the number of plans.
• Cross-train staff to handle peaks.
• Consider temporary staff or vendor support during heavy periods.
• Track turnaround times and adjust staffing when targets are missed.
Legal and Contractual Considerations
HIPAA
HIPAA permits disclosures for payment, health care operations, and health oversight without patient authorization, subject to the minimum necessary standard. Disclosures to an MA plan for RADV generally fall within these permissions. Providers should follow their release-of-information policies, verify requesters, and document disclosures.
Contract Obligations
MA plans must include in their contracts with network providers provisions giving HHS and its designees the right to audit and inspect records relating to the MA contract, and records generally must be retained for 10 years. Provider agreements typically require providers to furnish records on request within specified timeframes. Failing to respond can breach the contract.
Do Not Alter Records
Never create, amend, or supplement documentation in response to a RADV request. Late entries designed to support diagnoses can expose the provider to serious legal risk, including potential False Claims Act liability.
Risk-Sharing Arrangements
Providers in capitated, value-based, or risk-sharing arrangements may share in revenue affected by RADV findings. Review contracts to understand how RADV results flow through to the provider and whether the provider has any rights to review or dispute findings.
Improving Documentation for Future Audits
Retrieval efficiency matters, but the best protection is documentation that clearly supports each diagnosis. Practices should:
• Train clinicians to document the status, assessment, and plan for each chronic condition addressed.
• Avoid carrying forward inactive diagnoses.
• Make sure every note is signed and dated promptly.
• Use EHR templates that prompt complete assessment and plan documentation.
• Conduct periodic internal risk adjustment audits and share results with clinicians.
When internal audits find that unsupported diagnoses were submitted, providers should work with the plan and counsel on corrections and evaluate any obligations under the 60-day overpayment rule.
Measuring Performance
Track metrics such as:
• Number of requests received per month, by plan.
• Average and maximum turnaround time.
• Percentage of requests completed by the plan's deadline.
• Percentage of records returned for missing signatures or incomplete pages.
• Number of second-round requests.
Share results with leadership and plans, and use them to improve processes.
A Sample Internal Timeline
Practices can translate the plan's needs into a simple internal standard:
• Day 1: Receive and log the request, verify the requester, and assign staff.
• Days 2 to 5: Retrieve records, including from archives or offsite storage if needed.
• Days 5 to 7: Run quality checks and resolve issues such as missing pages.
• Days 7 to 10: Deliver securely and confirm receipt.
• Ongoing: Respond to follow-up requests within two to three business days.
A ten-business-day standard for initial requests generally leaves plans enough time within their own deadlines. Rush requests late in the window may need same-week turnaround.
Special Situations
Records in Archives or Offsite Storage
Payment year 2020 audits involve dates of service in 2019, and later audits involve records several years old. Records may be in legacy EHR systems, archived databases, or offsite paper storage. Practices should know where older records are kept, how long retrieval takes, and who has access, and should plan for longer retrieval times for archived records.
Practice Acquisitions and EHR Conversions
When practices are acquired or change EHR systems, older records may be held by the prior owner or in a legacy system. Make sure agreements from acquisitions address access to historical records for audits, and maintain read-only access to legacy systems for at least the 10-year retention period.
Departed Clinicians
Records signed by clinicians who have left the organization are still valid if properly signed at the time. If a note was never signed, follow plan instructions and CMS guidance on signature attestations, which may not be available for every record type. Practices should strengthen signature monitoring so notes are signed promptly in the future.
Closed Practices
When a practice closes, its records must still be retained and made available. Designate a custodian and make sure plans know how to reach them.
Preparing Records for Delivery
How records are packaged affects how quickly plans can use them:
• Deliver records as clear, legible PDF files or in the format the plan requests.
• Include the complete encounter, in order, with the assessment and plan.
• Label files with the enrollee identifier and date of service as the plan requests.
• Avoid including unrelated encounters or large volumes of unrequested documents, which slow review.
• Confirm that scanned pages are complete and not cut off.
Coordinating Across Multiple Plans
Providers that serve enrollees in several MA plans may receive overlapping requests from different plans and vendors at the same time, sometimes for the same patients. A centralized log helps avoid duplicate work and missed deadlines. When volume from a single plan is high, ask the plan about batching requests, secure EHR access, or onsite retrieval. Share contact information for the organization's intake team with each plan's provider relations staff so requests go to the right place from the start.
Training Staff
Release-of-information staff need specific training for RADV requests, which differ from routine requests for continuity of care or legal purposes. Training should cover:
• How to verify plans and vendors.
• How to identify the correct date of service and encounter type.
• What a complete encounter record includes.
• How to check for signatures, dates, credentials, and legibility.
• How to use secure delivery methods.
• How to log requests and escalate problems.
• Why records must never be altered.
Refresh training as CMS guidance and plan processes change, and include RADV scenarios in onboarding for new staff.
Escalation and Communication With Plans
Problems are inevitable during audit waves. Establish escalation paths for requests that cannot be met on time, records that cannot be located, and questions about scope. Contact the plan early when a deadline is at risk, explain the issue, and propose a solution, such as partial delivery or remote access. Plans generally prefer early notice to missed deadlines. Keep a record of each escalation and its resolution.
Protecting Patient Privacy
Efficiency should never come at the expense of privacy. Send only the records requested for the specified enrollees and dates of service, apply the minimum necessary standard, and avoid sending records for the wrong patient, which is a reportable privacy incident in many cases. Double-check patient identifiers before release, especially for patients with common names. Use secure delivery for every transmission, and avoid unencrypted email. If a misdirected disclosure occurs, follow the organization's breach assessment procedures promptly.
Using Technology
Workflow tools can track requests, assign tasks, send reminders before deadlines, and report turnaround metrics. Some EHR systems can generate complete encounter packets automatically for a specified date of service. Where request volume is high, these tools can significantly reduce manual effort. Whatever tools are used, keep a human quality check before release, because automated packets may omit addenda, include unrelated documents, or capture the wrong encounter.
Reviewing Results
When plans share results, such as records that did not support a condition or were rejected for technical reasons, review them with the retrieval team and clinical leaders. Technical failures, such as missing signatures or wrong dates, point to retrieval or documentation process fixes. Clinical support failures point to documentation training needs. Tracking these results over time helps the organization measure improvement and reduces the number of second-round requests in future audits. Share summary results with leadership at least quarterly, along with planned improvements.
Common Mistakes
• Letting requests sit in individual clinics without central tracking.
• Sending summaries or claim forms instead of complete notes.
• Sending records from the wrong year or wrong patient.
• Sending unsigned or illegible notes.
• Releasing records to unverified requesters.
• Charging copy fees that the contract prohibits.
• Altering records to support diagnoses.
• Understaffing during audit waves.
Myths About RADV Record Retrieval
Myth: Providers Have Five Months to Respond
The five-month window belongs to the plan, which typically needs records from providers within a few weeks.
Myth: More Records Are Better
Plans can submit only two records per audited condition, so they need the strongest single record, not a stack of documents.
Myth: Remote EHR Access Is Always Risky
With appropriate agreements, access limits, and monitoring, remote access can be secure and efficient.
Myth: Retrieval Is an Administrative Task Only
The quality of what is sent determines whether diagnoses are supported, which can affect provider revenue and compliance exposure.
Questions Leadership Should Ask
• Do we have one intake channel and log for all MA record requests?
• What is our average turnaround, and do we meet plan deadlines?
• Do we quality-check records for signatures, dates, and completeness before sending?
• Have we evaluated secure EHR access for high-volume plans?
• Are we staffed for audit waves as CMS audits every contract?
• Do our clinicians document chronic conditions in a way that will hold up in RADV?
Key Takeaways
• CMS restored a five-month RADV medical record submission window for payment year 2020 and later audits, but plans need provider records within weeks to meet it.
• Plans can submit only two records per audited condition, so complete, signed, correctly dated records matter more than volume.
• A centralized intake, request log, verification step, quality checks, and secure delivery form the core of an efficient retrieval workflow.
• HIPAA generally permits RADV disclosures without authorization, and MA contracts typically require providers to furnish records and retain them for 10 years.
• Strong documentation at the point of care is the best long-term protection, and records must never be altered in response to a request.
How HealthBridge Can Help
HealthBridge helps physician practices and health systems respond efficiently to Medicare Advantage RADV record requests. Our team can design centralized intake and tracking workflows, set turnaround targets, build quality checklists for signatures, dates, and completeness, and help evaluate secure EHR access arrangements with plans. We also conduct risk adjustment documentation and coding audits and train clinicians on documenting chronic conditions. If your organization is receiving RADV record requests or wants to prepare for higher volume, please get in touch with us. We will be happy to help you with this topic.
References
• Centers for Medicare & Medicaid Services. Memorandum, Update on the Status of Medicare Advantage Risk Adjustment Data Validation Audits (January 27, 2026). https://www.cms.gov/medicare/coding-billing/risk-adjustment-data-validation-program
• Centers for Medicare & Medicaid Services. Medicare Advantage Risk Adjustment Data Validation Program. https://www.cms.gov/data-research/monitoring-programs/medicare-risk-adjustment-data-validation-program
• Centers for Medicare & Medicaid Services. CMS Rolls Out Aggressive Strategy to Enhance and Accelerate Medicare Advantage Audits (May 21, 2025). https://www.cms.gov/newsroom/press-releases/cms-rolls-out-aggressive-strategy-enhance-and-accelerate-medicare-advantage-audits
• Centers for Medicare & Medicaid Services. Medicare Managed Care Manual, Chapter 7, Risk Adjustment. https://www.cms.gov/regulations-and-guidance/guidance/manuals/downloads/mc86c07.pdf
• Electronic Code of Federal Regulations. 42 CFR 422.310, Risk adjustment data. https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-422/subpart-G/section-422.310
• Electronic Code of Federal Regulations. 42 CFR 422.311, Risk adjustment data validation audits. https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-422/subpart-G/section-422.311
• Electronic Code of Federal Regulations. 42 CFR 422.504, Contract provisions. https://www.ecfr.gov/current/title-42/chapter-IV/subchapter-B/part-422/subpart-K/section-422.504
• Electronic Code of Federal Regulations. 45 CFR Part 164, Subpart E, Privacy of Individually Identifiable Health Information. https://www.ecfr.gov/current/title-45/subtitle-A/subchapter-C/part-164/subpart-E
• U.S. Department of Health and Human Services. HIPAA Guidance on Uses and Disclosures for Treatment, Payment, and Health Care Operations. https://www.hhs.gov/hipaa/for-professionals/privacy/guidance/disclosures-treatment-payment-health-care-operations/index.html
• U.S. Code. 42 U.S.C. 1320a-7k(d), Reporting and returning of overpayments. https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title42-section1320a-7k

Some or all of the services described herein may not be permissible for HealthBridge US clients and their affiliates or related entities.
The information provided is general in nature and is not intended to address the specific circumstances of any individual or entity. While we strive to offer accurate and timely information, we cannot guarantee that such information remains accurate after it is received or that it will continue to be accurate over time. Anyone seeking to act on such information should first seek professional advice tailored to their specific situation. HealthBridge US does not offer legal services.
HealthBridge US is not affiliated with any department of public health agencies in any state, nor with the Centers for Medicare & Medicaid Services (CMS). We offer healthcare consulting services exclusively and are an independent consulting firm not affiliated with any regulatory organizations, including but not limited to the Accrediting Organizations, the Centers for Medicare & Medicaid Services (CMS), and state departments. HealthBridge is an anti-fraud company in full compliance with all applicable federal and state regulations for CMS, as well as other relevant business and healthcare laws. The badges, icons, and achievement graphics displayed on this website represent proprietary performance metrics, volume milestones, and internal corporate recognition issued exclusively by our corporate affiliate network at SummitRidge. These visual markers are utilized solely as historical indicators of enterprise growth, operational longevity, and volume-based milestones cleared within our shared corporate ecosystem.
© 2026 HealthBridge US, a California corporation. All rights reserved.
For more information about the structure of HealthBridge, visit www.myhbconsulting.com/governance
