CRC study materials
CRC study resources

CRC (Court Reporting Certifications): Auditing and Data Accuracy: Chart Reviews, Risk Score Capture, and Quality Reporting

CRC · Work through your exam, one topic at a time.

All guide sections

Auditing and Data Accuracy: Chart Reviews, Risk Score Capture, and Quality Reporting

This domain tests how risk-adjustment data is validated and where accuracy breaks down. You must be able to audit a chart, confirm that documentation supports a reported HCC, recalculate the effect on the risk score, and connect coding accuracy to quality and value-based programs.

The audit workflow

  • Confirm the encounter falls in the audit year and in an eligible setting, and that the provider type and signature are valid.
  • Verify the diagnosis is documented with MEAT support and is not merely historical or suspected.
  • Validate code specificity and linkage, then confirm the correct HCC mapping and hierarchy effect.
  • Recalculate the risk score with and without the finding. An unsupported HCC removed from a sample may produce an error rate that is extrapolated across the population.

Risk score capture and documentation gaps

  • Common gaps are missed chronic conditions, unspecified codes, and unlinked complications. Each can lower a score legitimately or inflate it improperly.
  • Over-capture is equally an audit finding: a diagnosis added without support is an overpayment risk.

Quality and value-based overlap

  • HEDIS and Star Ratings measures depend on the same documentation. A diabetic member needs A1c testing, retinal exam, and nephropathy assessment; accurate complication coding supports both risk adjustment and quality performance.
  • MIPS and other value-based programs reward accurate, complete problem documentation, not maximal coding.

Worked example

A chart review finds the assessment "chronic systolic heart failure, EF 30%" but the claim reports I50.9. The reviewer changes the code to I50.2. Reasoning: the documentation supports systolic type, so I50.2 is correct. In many model versions both map to the same HCC, so the payment effect may be zero, but specificity still matters for quality measures, future audits, and clinical accuracy. If the note had said only "CHF" in the problem list with no assessment, no code would be supported.

Traps that cost marks

  • Accepting a provider attestation without underlying documentation.
  • Reviewing a chart from the wrong year or an ineligible encounter type.
  • Assuming every chart review increases the risk score; reviews legitimately remove unsupported HCCs.
  • Ignoring hierarchies when recalculating the score after a chart change.