4.3 Prospective, Concurrent, and Retrospective Reviews

Prospective, Concurrent, and Retrospective Reviews

Quick answer: CRC work includes prospective gap closure, concurrent documentation improvement, and retrospective chart review.

The exam may describe when the review happens and ask what the coder can do. Timing affects whether the solution is provider education, query, or validated capture. This section is strongest when studied as clue recognition. Compare Prospective review, Concurrent review, and Retrospective review; each may sound nearby, but each sends you to a different documentation, code, or HCC rule.

Core Map

How This Shows Up on the Exam

Treat Prospective, Concurrent, and Retrospective Reviews as a small decision tree. A clue such as before or early in care year appears should send you toward Prospective review, while during current encounter workflow appears asks for Concurrent review. In Prospective, Concurrent, and Retrospective Reviews, the answer is not better because it sounds broader; it is better when it solves the controlling fact.

Prospective review and Concurrent review are easy to confuse because both belong to Prospective, Concurrent, and Retrospective Reviews. Keep them separate by attaching each one to its trigger. Prospective review calls for: identify suspected conditions needing provider assessment. Concurrent review calls for: support documentation while care is happening.

For Retrospective review, focus on what the clue makes necessary: code only what existing documentation supports. For Provider query, the necessary action is different: ask compliant clarification when allowed. A correct Prospective, Concurrent, and Retrospective Reviews answer should make that difference visible, not hide it behind a general statement.

When the item feels ambiguous, compare the remaining choices to Retrospective review, Provider query, and Gap closure. A strong Prospective, Concurrent, and Retrospective Reviews answer should still tell you which signal it is using and which action it is taking. If the Prospective, Concurrent, and Retrospective Reviews choice cannot do both, it is probably recognition rather than decision-making.

Decision Notes

Use Prospective, Concurrent, and Retrospective Reviews as a precision drill. The best answer should not merely mention Prospective review; it should explain why before or early in care year appears leads to this action: identify suspected conditions needing provider assessment. If the question adds during current encounter workflow appears, pause before committing, because Concurrent review changes the next move.

For Prospective, Concurrent, and Retrospective Reviews practice, write one wrong answer that overuses Retrospective review and one correct answer that applies Provider query. In Prospective, Concurrent, and Retrospective Reviews, a memorized answer usually survives only in the original row, while a real CRC risk adjustment exam decision survives paraphrased stems and mixed practice. Keep Gap closure in the Prospective, Concurrent, and Retrospective Reviews check because scoring, safety, administrative, or compliance details can change an otherwise plausible response.

Worked Exam Scenario

A coder finds medication evidence suggesting CHF, but the provider note does not mention CHF this year. Before reading the choices, decide whether the scenario is controlled by Prospective review or Concurrent review. If before or early in care year appears, the answer needs to do this: identify suspected conditions needing provider assessment. If the decisive wording is during current encounter workflow appears, switch to support documentation while care is happening.

Common Traps

In Prospective, Concurrent, and Retrospective Reviews, the most expensive miss is choosing the answer that sounds familiar but does not answer the row. Watch for choices that treat Prospective review as interchangeable with Concurrent review, skip the condition behind Retrospective review, or mention Provider query without doing ask compliant clarification when allowed. Your review note should state the clue the option ignored.

Study Routine

• Cover the action column and recreate the moves for Prospective review through Gap closure.
• Practice one easy Prospective, Concurrent, and Retrospective Reviews item, one medium item, and one item where two choices feel plausible.
• Track whether the Prospective, Concurrent, and Retrospective Reviews miss came from weak content or from choosing before the clue was clear.
• Return to Prospective, Concurrent, and Retrospective Reviews only after a mixed question confirms the repair.

For Prospective, Concurrent, and Retrospective Reviews, study time should produce a reusable CRC risk adjustment exam behavior, not just a familiar page. If the Prospective, Concurrent, and Retrospective Reviews miss log shows the same row twice, reread only that row, write a new example, and test it inside a coding, model, documentation, or compliance item from another CRC domain.

Mini-Drill

Create two one-sentence stems: one that clearly gives before or early in care year appears, and one that clearly gives during current encounter workflow appears. Answer both without looking at the table, then explain why the action for Prospective review does not fit Concurrent review. Finish by adding a third stem for Retrospective review.

Final Check

Before moving on from Prospective, Concurrent, and Retrospective Reviews, cover the table and predict the action for before or early in care year appears, after encounter or after year appears, and suspected chronic condition lacks current evidence. The Prospective, Concurrent, and Retrospective Reviews section is ready when the prediction comes before the answer choices and when the reasoning supports proving the diagnosis is current, supported, specific, and model-relevant.