Risk adjustment converts documented diagnoses into payment. Validation audits test the documentation. The question is narrow and unforgiving: for this member, in this year, does the medical record support the condition that was submitted. If it does not, the associated payment is recoverable, and recovery can be applied at scale.
Almost no plan does this work alone. Coding vendors review charts and identify conditions. Retrieval vendors chase records from provider offices. Assessment vendors conduct in-home visits that generate diagnoses. Analytics vendors identify suspected gaps. Each of these contributes to what gets submitted, and each holds part of the evidence that would explain why.
The timing is the problem. Validation reaches back across payment years. By the time a request arrives, a coding vendor may have been replaced, a retrieval vendor's audit trail may have been purged on its own schedule, and the provider group that generated the record may no longer be contracted. The plan carries the repayment exposure regardless of who did the work, which makes the vendor agreement the only place to secure what the plan will need.
Where validation readiness fails
Failures are evidentiary rather than clinical. The diagnoses were often defensible; the documentation supporting them could not be produced in the form the audit required.
- Coder rationale not retained, the vendor's internal basis for a code, including the chart location relied on, is treated as working material and discarded, leaving no explanation of the submission.
- Retrieval trail incomplete, there is no record of which chart was obtained, from which provider, covering which dates, so the submitted code cannot be tied to a specific document.
- Retention shorter than the audit window, vendor retention policies run shorter than the lookback period, and records are destroyed legitimately but inconveniently.
- Cooperation ends with the contract, a replaced vendor has no obligation to assist, and assistance depends on commercial goodwill it has no reason to extend.
- Exposure unallocated, the agreement is silent on repayment risk arising from unsupported coding, so the plan absorbs the full amount while the vendor keeps its fee.
The pattern is that the plan buys an activity and not the evidence the activity produced. Coding, retrieval and assessment are delivered as services with a throughput measure, and the artefacts that would later justify each submission are not specified as deliverables at all.
Validation reaches back across payment years, and plans frequently change coding or retrieval vendors inside that period. A retention and cooperation obligation that terminates with the agreement leaves the plan asking a former supplier for help with a liability the supplier no longer shares. Both duties need stated periods measured from the payment year and express survival of termination.
The five terms to secure
Each term below should sit in the vendor agreement and be tracked as an obligation on the vendor record, with the evidence requirement treated as a deliverable rather than as an administrative by-product.
- Documentation standard per submission. a requirement that each code identified by the vendor is accompanied by the supporting chart reference, date of service, provider and coder rationale, delivered as part of the work product.
- Work product retention. retention of coder rationale, review notes and retrieval audit trails for a period measured from the payment year, stated explicitly and surviving termination.
- Audit cooperation with response times. an obligation to respond to validation support requests within a defined number of business days, including after the agreement ends, with a named contact maintained.
- Quality and accuracy standards with measurement. defined accuracy expectations, a sampling methodology and a remediation process, so coding quality is measured continuously rather than discovered during an audit.
- Allocation of repayment exposure. an express allocation of liability where submissions traceable to the vendor's work are found unsupported, proportionate to the vendor's role and fee.
A five-step roadmap for plans
Step 1, Map the submission chain
For each submission source, identify which vendor contributed, what evidence that vendor generates and where the evidence resides. The exercise usually shows that evidence for the highest-volume source is the least well specified, because volume drove the commercial conversation.
Step 2, Specify evidence as a deliverable
Rewrite the statement of work so the supporting chart reference, service date, provider identity and coder rationale are part of what the plan receives, not internal vendor material. This is the single change that most improves validation readiness, and it is usually accepted because the vendor already produces the information, in the same way physician and provider agreement tracking works from records the organization already holds.
Step 3, Set retention to the payment year
Anchor retention to the payment year rather than the contract term, with express survival. Confirm the vendor's records management can implement the period, since an obligation its systems cannot meet will fail silently and only surface when records are requested.
Step 4, Build cooperation into exit
Include transition and cooperation terms that operate after termination, with defined response periods and a maintained contact. Where possible, take delivery of the work product and audit trails at exit rather than relying on a former vendor to hold them.
Step 5, Sample continuously, not at audit
Run ongoing internal validation sampling against the vendor's output using the agreed accuracy standard. Finding a systematic documentation weakness in the current year is a remediation exercise; finding it during a validation audit covering three prior years is a repayment exercise, which is the argument for obligation management in healthcare.
Hold vendor evidence duties on the contract
Aavenir tracks documentation deliverables, retention periods and audit cooperation duties as monitored obligations that survive vendor termination.
Why continuous sampling changes the economics
The terms above make validation survivable, but the measure that most reduces exposure is internal sampling against the same standard an auditor would apply, performed while the payment year is current. A documentation weakness found early can be corrected through provider education, vendor remediation and in some cases resubmission. The same weakness found during validation applies across every affected member for every year it persisted. Contractual accuracy standards and a defined sampling methodology are what make that early detection a vendor obligation rather than an internal aspiration nobody has time for.
Source, evidence and contractual control
The table maps each submission source to the evidence validation requires and the term that secures it.
| Submission source | Evidence required | Contractual control | Retention anchor |
|---|---|---|---|
| Retrospective chart review | Chart reference, coder rationale | Evidence as deliverable | Payment year |
| Chart retrieval | Retrieval trail, provider, dates | Audit trail retention | Payment year |
| In-home assessment | Assessment record, clinician | Documentation standard | Payment year |
| Provider-submitted claims | Medical record at provider | Provider record access terms | Payment year |
| Analytics gap identification | Basis for suspected condition | Rationale retention | Payment year |
Risk adjustment validation is a documentation test applied years after the fact, to work performed largely by vendors who may no longer be engaged. Plans that come through it well are not the ones with better coders; they are the ones whose agreements treated supporting evidence as a deliverable, anchored retention to the payment year rather than the contract term, secured cooperation that survives termination with defined response times, and allocated repayment exposure explicitly. Adding continuous sampling against the contractual accuracy standard turns the whole arrangement from a backward-looking liability into something the plan can manage while the year is still open. The terms cost nothing to include at negotiation and are close to impossible to obtain once a validation request for a prior year has already landed on the desk.
For related guidance, see Value-based care contract administration, simplified, The compliance guide to BAA tracking across vendors and The health system guide to physician agreement controls.
