Study guide

2.2 Provider Signatures, Dates, and Acceptable Records

AAPC Certified Risk Adjustment Coder CRC

Track your progress as you read

Finished sections get a check mark.

1 CRC Exam and Risk Adjustment Foundations

1.1 CRC Exam Format, Open-Book Rules, and Timing 1.2 What Risk Adjustment Tries to Measure 1.3 CMS-HCC, HHS-HCC, CDPS, and Commercial Models 1.4 Value-Based Care, Capitation, and Why RAF Matters 1.5 Model Versions, Code Years, and Source Control

2 Documentation Validation and MEAT

2.1 MEAT, TAMPER, and Supported Diagnosis Capture 2.2 Provider Signatures, Dates, and Acceptable Records 2.3 Annual Recapture and Chronic Condition Review 2.4 Problem Lists, Medication Lists, and Diagnostic Test Evidence 2.5 Provider Queries and Documentation Improvement

3 ICD-10-CM Coding for Risk Adjustment

3.1 ICD-10-CM Guidelines and Code Book Navigation 3.2 Diabetes, CKD, and Common Combination Coding 3.3 Cardiovascular and Pulmonary HCC Conditions 3.4 Neoplasms, Neurology, Mental Health, and Substance Use 3.5 Infectious, Immune, Liver, and Gastrointestinal Conditions 3.6 Symptoms, Abnormal Findings, History Codes, and Status Codes

4 HCC Hierarchies and RAF Logic

4.1 HCC Mapping, Hierarchies, and Disease Interactions 4.2 Demographics, Coefficients, and Payment-Year Thinking 4.3 Prospective, Concurrent, and Retrospective Reviews 4.4 CMS-HCC Version Changes and Hierarchy Awareness 4.5 RAF Calculation Examples and Interpretation

5 Compliance, Audits, and Quality

5.1 RADV Audits, Overpayments, and Validation Risk 5.2 Compliance, Ethics, and Coding Quality Controls 5.3 Risk Adjustment Operations and Team Workflow 5.4 Quality Measures Versus Risk Adjustment 5.5 Payer Policies, Encounter Data, and Submission Errors

6 Final CRC Review

6.1 Open-Book Speed, Tab Strategy, and Timed Practice 6.2 Final Model, Coding, and Compliance Checklist 6.3 Body-System Cram Sheet for High-Yield HCCs 6.4 Exam-Day Workflow and Confidence Under Ambiguity

2.2 Provider Signatures, Dates, and Acceptable Records

Key Takeaways Explain This Topic AI

Provider Signatures, Dates, and Acceptable Records: match Date of service to the clue "record year or encounter date appears" before choosing an answer.

Do not swap Provider authentication and Acceptable source; each row points to a different AAPC risk-adjustment coding action.

Use mixed practice until Face-to-face or allowable encounter and Legibility and linkage still trigger the right move under CRC risk adjustment exam timing.

Last updated: June 2026

Provider Signatures, Dates, and Acceptable Records

Quick answer: A diagnosis must be tied to an acceptable face-to-face or allowable encounter, date of service, and provider documentation.

Risk adjustment validation is record-based. CRC candidates need to know when a document supports coding and when it is administrative noise. This section is strongest when studied as clue recognition. Compare Date of service, Provider authentication, and Acceptable source; each may sound nearby, but each sends you to a different documentation, code, or HCC rule.

Core Map

  • Exam clue What it tells you Best next move
  • Date of service record year or encounter date appears capture only diagnoses supported in the relevant year

Provider authentication signature or credential appears verify the record is authenticated by an acceptable provider

Acceptable source lab, radiology, problem list, or provider note appears use sources according to model and payer rules

  • Face-to-face or allowable encounter encounter type appears confirm the visit type supports risk adjustment
  • Legibility and linkage unclear diagnosis or note appears do not infer beyond documentation
  • How This Shows Up on the Exam

Provider Signatures, Dates, and Acceptable Records should be reviewed with the answer choices covered. Predict the row first: Date of service if the item gives record year or encounter date appears, Provider authentication if the item gives signature or credential appears. Then uncover the Provider Signatures, Dates, and Acceptable Records choices and reject anything that does not serve the predicted row.

Date of service and Provider authentication are easy to confuse because both belong to Provider Signatures, Dates, and Acceptable Records. Keep them separate by attaching each one to its trigger. Date of service calls for: capture only diagnoses supported in the relevant year. Provider authentication calls for: verify the record is authenticated by an acceptable provider.

For Acceptable source, focus on what the clue makes necessary: use sources according to model and payer rules. For Face-to-face or allowable encounter, the necessary action is different: confirm the visit type supports risk adjustment. A correct Provider Signatures, Dates, and Acceptable Records answer should make that difference visible, not hide it behind a general statement.

When the item feels ambiguous, compare the remaining choices to Acceptable source, Face-to-face or allowable encounter, and Legibility and linkage. A strong Provider Signatures, Dates, and Acceptable Records answer should still tell you which signal it is using and which action it is taking. If the Provider Signatures, Dates, and Acceptable Records choice cannot do both, it is probably recognition rather than decision-making.

Decision Notes

Use Provider Signatures, Dates, and Acceptable Records as a precision drill. The best answer should not merely mention Date of service; it should explain why record year or encounter date appears leads to this action: capture only diagnoses supported in the relevant year. If the question adds signature or credential appears, pause before committing, because Provider authentication changes the next move.

For Provider Signatures, Dates, and Acceptable Records practice, write one wrong answer that overuses Acceptable source and one correct answer that applies Face-to-face or allowable encounter. In Provider Signatures, Dates, and Acceptable Records, 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 Legibility and linkage in the Provider Signatures, Dates, and Acceptable Records check because scoring, safety, administrative, or compliance details can change an otherwise plausible response.

Worked Exam Scenario

A lab result suggests diabetes, but the provider note never diagnoses, assesses, or treats diabetes. Before reading the choices, decide whether the scenario is controlled by Date of service or Provider authentication. If record year or encounter date appears, the answer needs to do this: capture only diagnoses supported in the relevant year. If the decisive wording is signature or credential appears, switch to verify the record is authenticated by an acceptable provider.

Common Traps

In Provider Signatures, Dates, and Acceptable Records, the most expensive miss is choosing the answer that sounds familiar but does not answer the row. Watch for choices that treat Date of service as interchangeable with Provider authentication, skip the condition behind Acceptable source, or mention Face-to-face or allowable encounter without doing confirm the visit type supports risk adjustment. Your review note should state the clue the option ignored.

Study Routine

Cover the action column and recreate the moves for Date of service through Legibility and linkage.

Practice one easy Provider Signatures, Dates, and Acceptable Records item, one medium item, and one item where two choices feel plausible.

Track whether the Provider Signatures, Dates, and Acceptable Records miss came from weak content or from choosing before the clue was clear.

Return to Provider Signatures, Dates, and Acceptable Records only after a mixed question confirms the repair.

For Provider Signatures, Dates, and Acceptable Records, study time should produce a reusable CRC risk adjustment exam behavior, not just a familiar page. If the Provider Signatures, Dates, and Acceptable Records 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 record year or encounter date appears, and one that clearly gives signature or credential appears. Answer both without looking at the table, then explain why the action for Date of service does not fit Provider authentication. Finish by adding a third stem for Acceptable source.

Final Check

Before moving on from Provider Signatures, Dates, and Acceptable Records, cover the table and predict the action for record year or encounter date appears, lab, radiology, problem list, or provider note appears, and unclear diagnosis or note appears. The Provider Signatures, Dates, and Acceptable Records 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.