FilePreserveA RADV request rarely maps to a single record.
Scope expanded, deadlines didn't get looser
CMS's May 2025 RADV scope expansion increased the compliance burden on health plans specifically — a named, dated forcing function, not a hypothetical. Audit-response teams need a faster, more reliable way to produce complete documentation, not just more storage.
No single "submission packet" view
Health Cloud Case plus whatever custom objects track the audit request and each medical-record submission — none of it was built to render as one file. Someone opens several tabs and manually compiles attachments into whatever format the submission requires.
Archiving shouldn't mean losing access
Storage costs push toward archiving older files off active Salesforce storage, but most archive vendors make that file unreachable via standard APIs until it's manually restored through their own separate console — exactly the wrong moment for that friction to show up.
Every supporting document, in one packet, without a console switch.
- Supporting documents assembled by hand across several related objects
- Any file already archived needs a manual restore before it can be used
- A RADV request means racing the clock across multiple tools
- Pick whichever documents you need across a member or claim's related lists
- Archived files are pulled back in automatically the moment they're selected
- One audit-ready PDF, without a manual restore detour
Point FilePreserve at your own RADV workflow.
Archive jobs are config-driven — pick the object, set your filter criteria, done. The setup guide walks through exactly how.