What is Concurrent Risk Adjustment? Definition, Formula, and Benchmark

Concurrent risk adjustment occupies the middle ground between prospective and retrospective workflows. Prospective review happens before the visit; retrospective happens after claim submission. Concurrent review happens during the post-visit charting window — after the encounter but before claim submission — and catches documentation gaps while the provider's memory of the visit is still fresh and clarification is feasible without addenda.

A concurrent program typically operates through EHR integration. An NLP engine or coder reviews the provider's progress note within hours of the encounter. If the note references a condition without supplying MEAT, or codes a generic condition where a more specific one is documented, the system generates a coder query or flags the note for provider review. The provider amends the note, the coder finalizes the claim, and the encounter is submitted with accurate MEAT-compliant coding. The entire loop closes within 24–72 hours of the visit.

Concurrent review captures most of the compliance benefits of prospective review — contemporaneous clinical context, provider memory of the visit, no retroactive addenda — with lower operational lift than full prospective planning. It does not require pre-visit suspect-condition lists or care-team huddles; it simply inspects what the provider already produced and flags gaps. This makes concurrent programs easier to deploy in specialty settings and in high-volume primary care where pre-visit planning at the annual-wellness-visit scale is not practical.

Operationally, concurrent review works best when coupled with computer-assisted coding (CAC) and computer-assisted physician documentation (CAPD) tools. CAC pre-populates probable ICD-10-CM codes from the note; CAPD flags specificity gaps for the physician during documentation. A concurrent review layer on top of CAC/CAPD provides a final coder validation before claim submission.

Compliance posture is favorable. Because documentation corrections happen before claim submission, concurrent review avoids the retrospective-review compliance concerns around retroactive diagnosis addition. RADV error rates for concurrent-heavy programs closely approximate prospective-program error rates because the underlying documentation quality is similar.

Large ACOs and MA plans increasingly deploy concurrent review as the primary workflow, with prospective review retained for annual wellness visits and retrospective review reserved for specialty and hospital encounters outside the concurrent program's scope. The combination yields the highest overall capture accuracy with the lowest audit exposure, though at higher combined operating cost than single-modality approaches.

Coders working with Concurrent Risk Adjustment see the edge cases most often at the coding-documentation boundary. Payer-specific coverage policies, LCDs, NCDs, and local guidance on Concurrent Risk Adjustment change more often than the underlying clinical text implies, so a reviewer-authored crosswalk between the coding convention and the associated prospective risk adjustment workflow is one of the cheapest CDI interventions available. Concurrent Risk Adjustment is also where a well-maintained claim scrubber earns its keep — the cost of a single mis-coded claim downstream is usually 5–10× the cost of the scrub rule that would have caught it.