Every document a RADV request asks for, with no manual restore.
Health plans commonly run RADV response on Health Cloud Case plus custom objects. A member's supporting documents span several related objects, not one record.
Assembled for a record request. Names and files are made up.
- Exh. 1Encounter_Note.pdf
- Exh. 2Discharge_Summary.pdf
- Exh. 3Lab_Results.pdf
- Exh. 4Referral_Letter.pdf
A RADV request rarely maps to a single record
On May 21, 2025, CMS announced it will audit all eligible Medicare Advantage contracts for each payment year in newly initiated audits. Audit response teams need a faster, more reliable way to produce complete documentation, not only more storage.
No single submission packet view
Health Cloud Case plus whatever custom objects track the request and each medical-record submission were not built to render as one file. Someone opens several tabs and compiles attachments by hand into the format the submission needs.
Archiving should not mean losing access
Storage costs push toward archiving older files. Some archive tools leave a file unreachable by your other Salesforce tools until it is restored through their own console, which is the wrong moment for that friction.
Every supporting document, in one packet, without a console switch
| Step | Without FilePreserve | With FilePreserve |
|---|---|---|
| Assembling | Documents gathered by hand across several related objects | Pick the documents you need across a member's or claim's related lists |
| Archived files | An archived file may need a manual restore before it can be used | Pulled back in automatically when selected |
| During the request | Racing the clock across multiple tools | One audit-ready PDF, with no manual restore detour |
Point FilePreserve at your own RADV workflow.
Pick the object, set your filters, done. The setup guide walks through it.