Work through these ten groups in order, because later concepts assume the foundations built earlier. Each concept pairs a rule with a resolved example and a common pitfall, so read actively: decide the answer before reading the resolution. Use the citations to revisit the underlying guideline texts when a distinction remains fuzzy. These are teaching concepts for study support, not an official syllabus or a substitute for the credentialing body's own materials.
Risk Adjustment Foundations and the Coder's Role
1. Purpose of Risk Adjustment Payment
Risk adjustment is a payment methodology that levels financial comparisons among health plans by accounting for each enrolled patient's documented health status. It compensates plans that enroll high-cost, chronically ill members so plans compete on care quality rather than on attracting the healthiest enrollees.
Example: A plan enrolls many members with diabetes and heart failure while a competitor attracts healthier members. Risk adjustment raises the first plan's payment to reflect its costlier population, so neither plan gains by avoiding sick enrollees.
Mistake to avoid: Assuming risk adjustment is a bonus program for plans rather than a neutralizing mechanism that reflects true population health costs.
Reference: AAPC CRC study guide sample
2. Where Risk Adjustment Coders Work
Most risk adjustment coders work for health plans or vendors serving plans; others work in provider offices holding risk-based contracts. Knowing your employer's position clarifies whether you code from submitted claims, audit provider selections, or educate clinicians on capturing complete, specific diagnoses.
Example: A coder reviews prior-year encounter records for a Medicare Advantage plan, checking that each submitted diagnosis is supported. She works for the plan itself, not the treating clinic, and codes from claims plus record documentation.
Mistake to avoid: Applying provider-office coding workflows to plan-side review work, where the record, not the claim, is the primary evidence source.
Reference: AAPC CRC study guide sample
3. Risk Adjustment Coding Scope Versus Other Settings
Outpatient coders emphasize CPT, HCPCS Level II, and ICD-10-CM with APCs; inpatient coders add ICD-10-PCS and MS-DRGs. Risk adjustment coding uses ICD-10-CM only, drawing diagnoses from claims and record documentation across all settings to build an accurate patient risk profile.
Example: An outpatient coder assigns CPT and ICD-10-CM for a clinic visit, while a risk adjustment coder reviewing the same encounter focuses only on whether every documented chronic diagnosis is captured and specific enough for the model.
Mistake to avoid: Spending effort on procedure code selection when the risk adjustment task requires only complete, guideline-compliant diagnosis capture.
Reference: AAPC CRC study guide sample
4. Code All Documented Diagnoses Rule
Unless instructions specify otherwise, every documented diagnosis meeting coding guidelines is reported, whether or not it maps to a risk-adjusted condition. Selectively coding only HCC-valued conditions creates incomplete data, undermines quality measures, and misrepresents the patient's true health status.
Example: A visit documents current COPD alongside a personal history of breast cancer that prompts today's surveillance imaging order. The coder reports both the COPD and the history code as a secondary diagnosis, even though the history code does not risk adjust for CMS HCC purposes, because all documented diagnoses affecting care are coded regardless of risk adjustment value.
Mistake to avoid: Filtering out documented diagnoses simply because they carry no risk adjustment value in the current model.
Reference: AAPC CRC study guide sample
5. Using Medications to Detect Documentation Gaps
Risk adjustment coders need working knowledge of medications, treatments, and diagnostics to spot documentation gaps. A patient taking insulin without documented diabetes signals a missing diagnosis, but the coder's role is to educate and query, never to infer a diagnosis the provider has not documented.
Example: A record lists insulin and metformin among current medications, but the assessment never mentions diabetes. The coder flags this as an educational opportunity and queries the provider rather than coding diabetes from the drug list alone.
Mistake to avoid: Assigning a diagnosis code directly from a medication list instead of querying the provider for documentation.
Reference: AAPC CRC study guide sample
6. Coder as Auditor Versus Coder as Assigner
When physicians select their own codes, the coder often serves as auditor, verifying documentation supports the selections and giving feedback on discrepancies. When coders assign codes, they work from what the record documents. Both paths require the same guideline knowledge but different daily workflows.
Example: A physician selects his own codes at checkout; the coder then audits several charts monthly, finds an unsupported COPD code, and provides feedback plus a documentation tip sheet instead of silently changing the claim.
Mistake to avoid: Treating physician-selected codes as untouchable, or changing them without communicating the documentation reason for the change.
Reference: AAPC CRC study guide sample
Payers, Payment Models, and Compliance Context
7. Fee-for-Service Versus Value-Based Diagnosis Focus
In fee-for-service, ICD-10-CM codes mainly support medical necessity for billed procedures; CPT drives payment. In value-based arrangements, diagnoses themselves determine revenue through risk scores, so complete, specific diagnosis capture becomes financially and clinically central rather than incidental.
Example: A practice built around fee-for-service submits an unspecified diabetes code merely to justify an A1c lab. Under a risk contract, the coder educates the provider to document diabetes type and complications so the full condition is captured.
Mistake to avoid: Carrying the fee-for-service habit of treating diagnosis codes as mere medical-necessity support into risk-adjusted work.
Reference: AAPC CRC study guide sample
8. Two Constant Purposes Across Changing Programs
The Affordable Care Act moved risk adjustment into mainstream use. Although program details change annually, two purposes persist: protecting plans that attract disproportionately unhealthy enrollees, and discouraging plans from marketing only to healthier, less costly potential members.
Example: A new exchange plan worries that sicker enrollees will make it uncompetitive. Risk adjustment transfers funds so its higher-cost members are financially recognized, removing the incentive to market only to healthy applicants.
Mistake to avoid: Memorizing yearly program mechanics while missing the two enduring purposes that explain why every rule exists.
Reference: AAPC CRC study guide sample
9. Health Plan Responsibility for HCC Support
CMS holds health plans responsible for gathering diagnosis codes that support specific HCCs, identifying over-coded conditions, and driving correct payment. Increased audit scrutiny means plans rely on coders to verify that claims match documentation and to catch both under-coding and unsupported over-coding.
Example: A plan discovers submitted HCCs lacking record support and over-coded conditions inflating scores. It launches internal review, provider education, and corrected submissions before CMS audit findings impose financial recoupment.
Mistake to avoid: Assuming the treating provider alone bears responsibility for the accuracy of diagnoses a plan submits for payment.
Reference: AAPC CRC study guide sample
10. Compliance, Audits, and the OIG Work Plan
Compliance programs, internal audits, and the OIG Work Plan exist because coding errors can constitute fraud or abuse when intentional or reckless. Coders serve as a first line of defense by auditing diagnosis assignment, reporting discrepancies, and helping build policies that support accurate submission.
Example: A coder performing prepayment review notices a claim with an unsupported severe diagnosis and holds it for documentation before submission, preventing a false claim from reaching the payer.
Mistake to avoid: Viewing audit findings as administrative nuisances rather than fraud-prevention tools that protect the organization.
Reference: AAPC CRC study guide sample
11. Coder Role in Gap-in-Care Identification
Coders can review insurer-supplied reports, usually monthly or quarterly, to identify patients with care gaps under practice policies. Presenting a concise note or task on the provider's screen lets the clinician act with minimal distraction, making the coder valuable in pre-visit planning and prepayment review.
Example: A coder flags a patient overdue for an annual chronic-condition visit and places a task on the provider's screen. The clinician addresses it during the next appointment without searching charts manually.
Mistake to avoid: Sending raw report listings to providers instead of distilled, actionable tasks tied to specific patients and needed documentation.
Reference: AAPC CRC study guide sample
12. EMR Diagnosis Truncation Risk
Systems and clearinghouses sometimes truncate submitted diagnoses without the provider knowing. Practices should verify with their EMR and vendors that up to twelve diagnosis codes per claim can be transmitted, because truncation erases documented work and creates an incomplete clinical picture for risk adjustment.
Example: A provider documents eight active diagnoses, but the system submits only four. The coder confirms the vendor configuration supports twelve, restoring the full clinical picture for the patient's risk profile.
Mistake to avoid: Assuming the EMR transmits every diagnosis entered; unverified vendor settings can silently drop codes from claims.
Reference: AAPC CRC study guide sample
HIPAA Privacy in Risk Adjustment Practice
13. Who Is a Covered Entity
The Privacy Rule covers health plans, health care clearinghouses, and providers who transmit health information electronically in connection with standard HIPAA transactions. Risk adjustment work typically involves health plans, so their uses of member diagnosis data fall squarely within covered-entity obligations.
Example: A billing service converts a clinic's nonstandard claim data into HIPAA standard format for a health plan. It functions as a clearinghouse, and only certain Privacy Rule provisions apply to its processing activities.
Mistake to avoid: Assuming every company touching health data is covered; entities like workers' compensation insurers are generally not health plans.
Reference: HHS Summary of the HIPAA Privacy Rule
14. Business Associates in Risk Adjustment Work
A business associate is a non-workforce person or organization performing functions for a covered entity involving PHI, such as claims processing, data analysis, utilization review, or billing. A written agreement must impose safeguards, and a covered entity cannot authorize any use the Rule itself would prohibit.
Example: A plan hires an outside firm to perform risk adjustment data analysis on member records. A signed business associate agreement imposing written safeguards is required before the vendor may access the PHI.
Mistake to avoid: Letting a risk adjustment vendor access member records without a compliant business associate agreement in place.
Reference: HHS Summary of the HIPAA Privacy Rule
15. PHI Versus De-Identified Data
Protected health information is individually identifiable health information in any form, electronic, paper, or oral, held by a covered entity or business associate. De-identified information, achieved through statistician certification or removal of specified identifiers, carries no use or disclosure restrictions.
Example: A coder prepares a training deck using member claims. She removes names, full dates, and identifiers so the data is de-identified, allowing unrestricted educational use without member authorization.
Mistake to avoid: Treating a spreadsheet of diagnoses with member names and birth dates as if it were de-identified because it came from claims data.
Reference: HHS Summary of the HIPAA Privacy Rule
16. Permitted Uses: Treatment, Payment, Operations
Covered entities may use and disclose PHI without authorization for treatment, payment, and health care operations. Operations include quality assessment, case management, medical review, audits, fraud detection, and specified insurance functions like risk rating, which encompass much routine risk adjustment activity.
Example: A plan uses member PHI to calculate risk scores and conduct fraud detection audits. These are payment and health care operations activities, permissible without individual authorization under the Rule.
Mistake to avoid: Believing risk adjustment analytics always require member authorization when they typically qualify as payment or operations activities.
Reference: HHS Summary of the HIPAA Privacy Rule
17. Minimum Necessary Standard
Covered entities must make reasonable efforts to use, disclose, and request only the minimum PHI needed for the purpose. The entire record cannot be disclosed unless specifically justified. Exceptions include treatment disclosures, disclosures to the individual, and uses pursuant to a valid authorization.
Example: A coder receives a payer request for records supporting one audited diagnosis. She sends only the encounters relevant to that condition rather than the member's complete history, satisfying minimum necessary.
Mistake to avoid: Sending complete medical records when an audit or data request only requires the specific dates of service and conditions at issue.
Reference: HHS Summary of the HIPAA Privacy Rule
18. Authorization Requirements and Marketing
Written authorization is required for uses outside permitted categories, including most marketing communications and most psychotherapy note uses. Authorizations must be plain language, specify information and recipients, include expiration and revocation rights, and reveal remuneration when marketing involves paid disclosure.
Example: A plan wants to share member PHI with a pharmaceutical company promoting its own products. Because remuneration is involved and the communication encourages purchase, individual authorization is required first.
Mistake to avoid: Treating a paid third-party product promotion as a plan service communication that needs no authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
ICD-10-CM Structure and Conventions
19. Alphabetic Index First, Tabular List Verification
Diagnosis coding always begins in the Alphabetic Index to locate the condition and subterms, then moves to the Tabular List for verification. The Tabular List contains instructional notes, excludes, and required characters that can override the initial Index entry, so unverified lookups produce invalid codes.
Example: For abdominal pain, the coder locates Pain, abdominal in the Index, follows subterms to a code, then verifies it in the Tabular List, where notes and required characters may change the final selection.
Mistake to avoid: Coding directly from the Index without Tabular List verification, missing required additional characters or exclusion notes.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
20. NEC Versus NOS Abbreviations
NEC, not elsewhere classifiable, means the provider documented specific detail but no exact code exists, directing you to an other specified code. NOS, not otherwise specified, equals unspecified and applies only when the coder lacks the information needed for any more specific code.
Example: A provider documents a specific liver disorder with no dedicated code; the coder selects the other specified code. For a rash documented only as a rash, the unspecified code is correct because detail is genuinely absent.
Mistake to avoid: Choosing an other specified code when the documentation itself lacks detail; that situation calls for the unspecified code instead.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
21. Placeholder X and Seventh-Character Extensions
Certain categories require a seventh character for all codes within them. When the code is shorter than six characters, placeholder X fills the empty positions so the extension lands in the seventh position. Omitting either the X or the extension renders the code invalid for reporting.
Example: A four-character code in a category requiring a seventh character cannot be submitted as-is. The coder inserts placeholder X characters, then the extension, producing a valid six-plus-extension code.
Mistake to avoid: Appending a seventh character directly to a short code without X placeholders, creating an invalid code string.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
22. Bracket Meanings Differ by Volume
In the Alphabetic Index, brackets indicate that multiple codes are required to fully report the condition. In the Tabular List, brackets instead enclose synonyms, alternate wording, or explanatory phrases. Reading bracket conventions in the wrong volume leads to missing required code pairs.
Example: The Index entry for congenital syphilitic hepatitis shows a code followed by a bracketed second code. The coder reports both, understanding the Index brackets demand the additional code pair.
Mistake to avoid: Interpreting Tabular List brackets as multiple-code instructions; that convention belongs to the Index.
Reference: AAPC CRC study guide sample
23. Acceptable Use of Unspecified and Symptom Codes
Sign, symptom, and unspecified codes have acceptable and sometimes necessary uses. Each encounter should be coded to the level of certainty documented. When documentation and clinical knowledge support a specific diagnosis, report it; otherwise an unspecified or symptom code accurately reflects the encounter.
Example: A record documents only general malaise with no workup conclusion. The coder assigns the symptom code, reflecting the level of certainty known, rather than guessing a definitive condition.
Mistake to avoid: Automatically treating every unspecified code as an error; the real question is whether documentation supports greater specificity.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. The With Convention for Presumed Linkage
ICD-10-CM allows certain conditions linked by the word with in the classification to be presumed related, such as diabetes with certain manifestations and hypertensive conditions. This presumptive cause-and-effect spares the coder from requiring explicit provider linkage for these defined pairings only.
Example: A note lists diabetes and chronic kidney disease in the assessment. Because the classification links them under the with convention, the coder reports diabetic chronic kidney disease without demanding an explicit linkage statement.
Mistake to avoid: Requiring documented linkage for with-pair conditions the classification already presumes, or presuming linkage outside the convention.
Reference: AAPC CRC study guide sample
Outpatient Versus Inpatient Reporting Rules
25. Uncertain Diagnoses in Outpatient Records
For outpatient records, conditions documented as probable, suspected, questionable, possible, or still to be ruled out are not reported as definitive diagnoses. Instead, code the signs, symptoms, or established findings. This contrasts with inpatient rules, where certain uncertain diagnoses may be reported at discharge.
Example: An outpatient note states pneumonia is suspected pending cultures. The coder does not report pneumonia, coding only the documented symptoms, because outpatient rules bar uncertain diagnosis reporting.
Mistake to avoid: Reporting a possible or questionable condition as confirmed in an outpatient record, which the guidelines expressly prohibit.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
26. Coexisting Conditions Versus Resolved Conditions
Code all documented conditions that coexist at the encounter and that require or affect patient care treatment or management. Do not code conditions previously treated and no longer existing. History codes may serve as secondary codes when the historical condition or family history impacts current care.
Example: A patient's resolved appendicitis from a prior year appears in the history. The coder excludes it but reports current hypertension because it is documented and affects today's management.
Mistake to avoid: Coding every historical entry as current, or skipping active chronic conditions because they were not the visit's chief focus.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
27. Principal Diagnosis Selection in Inpatient Settings
In non-outpatient settings, the principal diagnosis is the condition established after study to be chiefly responsible for occasioning the admission, per the Uniform Hospital Discharge Data Set definition. The circumstances of admission always govern this selection, not which condition consumed the most resources.
Example: A patient is admitted for heart failure that study confirms prompted the admission. Heart failure is sequenced as principal diagnosis even though other chronic conditions were also managed.
Mistake to avoid: Choosing the most resource-intensive condition as principal when admission circumstances point to a different condition.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Present on Admission Indicator Logic
Present on admission indicators apply to inpatient claims after codes are assigned. Conditions diagnosed during admission but clearly present before it, and suspected conditions at admission later confirmed, are marked Y. Unclear documentation calls for query, with U used only in very limited circumstances.
Example: A patient arrives with suspected sepsis that blood cultures later confirm. Because it was documented as suspected at admission, the confirmed sepsis is marked present on admission.
Mistake to avoid: Assigning U routinely when documentation is unclear instead of querying the provider for clarification first.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. First-Listed Diagnosis in Outpatient Reporting
Outpatient reporting uses first-listed diagnosis logic rather than inpatient principal diagnosis rules. The definitive diagnosis is sequenced first, and signs or symptoms routinely associated with it are not coded separately. Symptoms may accompany a definitive diagnosis only when not routinely associated with it.
Example: A clinic visit for cough yields a confirmed bronchitis diagnosis. The coder lists bronchitis first and does not separately code the cough, which is routinely associated with the diagnosis.
Mistake to avoid: Sequencing a symptom ahead of an established diagnosis, or adding symptom codes that the definitive code already includes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Symptom Codes Alongside Definitive Diagnoses
When a sign or symptom is not routinely associated with a definitive diagnosis, both may be reported, with the definitive diagnosis sequenced first. Combination codes that already include common symptoms prevent separate symptom coding. This distinction keeps encounter data complete without redundancy.
Example: A patient with a documented syndrome experiences an unusual symptom not typically part of it. The coder reports the syndrome diagnosis first, then the symptom code, since it is not routinely associated.
Mistake to avoid: Reporting separate codes for symptoms already captured within a combination code for the same condition.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Risk Adjustment Models and Hierarchies
31. Diagnosis-Based Versus Prescription-Based Models
Risk adjustment models divide into diagnosis-based programs, such as CMS-HCC for Medicare Part C, HHS-HCC for commercial exchange plans, CDPS for Medicaid, and DRG and ACG systems, and prescription-based programs like RxHCC and MedicaidRx that use drug data. Identifying the model tells you which data drives payment.
Example: A coder sees diagnoses converted to condition category values and also notes the plan uses pharmacy data. She recognizes the plan may run both a diagnosis-based model and a prescription-based model side by side.
Mistake to avoid: Assuming all risk adjustment flows from diagnosis codes; prescription-based models derive risk from pharmacy data instead.
Reference: AAPC CRC study guide sample
32. Matching Model to Population
CMS-HCC serves Medicare Advantage Part C populations; HHS-HCC applies to commercial, individual, and small group exchange plans; CDPS serves Medicaid chronic illness and disability payment. Matching the member's insurance status to the correct model determines which diagnoses and submissions affect payment.
Example: A member is dually eligible for Medicare and Medicaid. The coder knows the Medicare HCC model applies to Part C payment while CDPS serves the Medicaid program, affecting which submissions matter for each plan.
Mistake to avoid: Applying Medicare HCC logic to exchange-plan members whose payment actually follows the HHS-HCC model.
Reference: AAPC CRC study guide sample
33. How HCC Hierarchies Drop Lower Categories
Hierarchical condition categories rank related conditions so only the most severe within a hierarchy counts toward the risk score. When a higher category is reported, specified lower categories in that hierarchy are dropped. This prevents double-counting severity within a single body system or disease group.
Example: One visit documents moderate dementia, and a later neurology encounter in the same data year documents severe dementia. Because the severe dementia category sits above the moderate categories in the hierarchy, the model counts only the severe category and drops the moderate ones, so the member's cognitive impairment is counted once at its highest documented severity.
Mistake to avoid: Adding risk values for both a higher and lower category in the same hierarchy; the model counts only the highest.
Reference: AAPC CRC study guide sample
34. From Diagnosis Codes to Risk Scores
Diagnosis codes submitted for risk adjustment convert to condition category values that produce a risk adjustment factor, feeding an adjusted risk score. This score informs how the plan budgets for annual patient care and calculates financial reserves for future treatment of existing diagnoses.
Example: A plan reviews a member's accumulated diagnosis values for the year, which combine into an adjusted risk score used to budget for that patient's expected annual care needs.
Mistake to avoid: Thinking diagnoses are submitted for service reimbursement; in risk adjustment they build a supplemental picture of patient conditions.
Reference: AAPC CRC study guide sample
35. Acceptable Provider Specialty Types
Medicare risk adjustment data submission accepts diagnoses only from acceptable physician specialty types, a published list covering physicians and various practitioners. A record from a provider type outside the list cannot support a submitted HCC, regardless of how well the condition is documented.
Example: A health assessment performed by a provider type not on the acceptable specialty list cannot support a diagnosis submission. The coder routes the condition to an acceptable treating provider for documentation instead.
Mistake to avoid: Accepting well-documented diagnoses from provider types excluded from the acceptable specialty list for submission.
Reference: AAPC CRC study guide sample
36. Model Variables Beyond Diagnosis Codes
Beyond diagnoses, models incorporate age, gender, socioeconomic status, disability status, insurance status including dual eligibility, claims elements like procedure and place-of-service codes, and special conditions such as hospice enrollment or end-stage renal disease. These variables explain spending differences and refine risk predictions.
Example: Two members carry identical diagnoses, but one is enrolled in hospice. The coder expects the hospice status to change how the model weights that member's risk despite identical coded conditions.
Mistake to avoid: Assuming identical diagnosis lists always produce identical risk scores; demographic and enrollment variables also apply.
Reference: AAPC CRC study guide sample
Quality Programs and Predictive Modeling
37. What Stars Ratings Measure
The Part C and Part D Stars Ratings publicly report health plan quality and performance to help Medicare beneficiaries choose plans. Ratings identify top performing plans, and plans earning higher ratings can receive bonus payments, while lower ratings bring financial and reputational consequences.
Example: Asked what Stars ratings identify, a coder correctly answers top performing health plans, not top providers, since the program publicly rates plan quality for beneficiaries choosing coverage.
Mistake to avoid: Confusing plan-level Stars ratings with evaluations of individual providers or the amounts plans pay providers.
Reference: AAPC CRC study guide sample
38. HEDIS and Stars Data Overlap
From a data discovery perspective, HEDIS and Star Ratings are essentially inseparable, since much Stars measurement draws on HEDIS-collected data. Understanding this overlap lets risk adjustment teams streamline record retrieval and coordinate quality data collection with diagnosis capture efforts.
Example: A plan prepares for HEDIS measurement season knowing the same chart pulls and data discovery serve its Stars submissions, so coders collect records once for both purposes.
Mistake to avoid: Running separate, duplicative record retrieval projects for HEDIS and Stars when the underlying data discovery overlaps.
Reference: AAPC CRC study guide sample
39. Quality Data Versus Risk Adjustment Data Sources
Stars data comes from patient surveys and performance measures documented in the medical record, while risk adjustment draws only diagnosis data from the record. The programs correlate because both rest on documentation, but they collect different elements and serve different payment purposes.
Example: A quality measure requires documented follow-up, while risk adjustment requires the underlying diagnosis. The coder pulls one encounter supporting both, recognizing the record serves two distinct programs.
Mistake to avoid: Claiming quality measures and risk adjustment share no correlation; both depend heavily on the same underlying record documentation.
Reference: AAPC CRC study guide sample
40. Predictive Modeling in Risk Adjustment
Predictive modeling analytically reviews known data elements, including claims, disease management records, equipment requests, and prescription drug events, to form educated hypotheses about future patient health. Risk adjustment teams use it to anticipate needs and uncover current diagnoses that should be counted.
Example: A model flags a member with frequent pharmacy fills and equipment claims as likely to develop a costly condition. The plan schedules outreach and checks whether related current diagnoses were captured for risk adjustment.
Mistake to avoid: Treating predictive model output as confirmed diagnosis; it flags possibilities that still require provider documentation.
Reference: AAPC CRC study guide sample
41. Matching Records to Request Type
Providers receive high volumes of records requests tied to different programs. A coder who understands exactly which records a specific request type needs, such as risk adjustment versus HEDIS, saves the office substantial time and ensures the correct documentation supports each submission.
Example: A coder preparing for a quality-focused review knows the request seeks measure-supporting records, so she pulls documentation of the performed service rather than only the diagnosis list a risk adjustment request would need.
Mistake to avoid: Sending generic record batches for every payer request instead of tailoring documentation to the requesting program.
Reference: AAPC CRC study guide sample
42. Quality Payment Program Connections
The Quality Payment Program and related quality initiatives tie payment to performance measurement. Plans below the four-star threshold may lose bonus opportunities, while higher ratings increase payments. Coders contribute by ensuring the documentation feeding these measures is complete and accurate.
Example: A plan's quality rating sits at four stars. Leadership notes improvement remains possible since five stars is the ceiling, and higher ratings bring bonus payment opportunities.
Mistake to avoid: Assuming quality ratings are purely reputational; they directly affect plan payment through bonus structures.
Reference: AAPC CRC study guide sample
Documentation Sources Within the Medical Record
43. Coding from Chief Complaint and HPI
Diagnoses documented in the chief complaint or history of present illness may be coded when the provider documents them as current conditions. These sections often reveal the reason for the encounter and active problems, but the coder must still confirm the condition is current and not merely historical mention.
Example: The chief complaint reads chest pain, and the HPI describes stable angina with exertion. The coder reports the documented angina diagnosis, since these sections carry diagnostic weight when provider-documented.
Mistake to avoid: Coding every condition mentioned in the HPI without confirming it is current rather than historical context.
Reference: AAPC CRC study guide sample
44. Past Medical History Is Not Automatically Current
Past medical history and similar historical lists cannot automatically be treated as current diagnoses. A historical listing alone may not serve as a diagnosis source for risk adjustment. Look for evidence of current assessment, treatment, or monitoring before reporting any listed condition as active.
Example: A past medical history lists prostate cancer with no active treatment noted. The coder does not report active cancer; without ongoing treatment or current assessment, the entry reads as historical only.
Mistake to avoid: Harvesting every PMH entry as a current diagnosis, a practice that inflates risk scores and fails audit.
Reference: AAPC CRC study guide sample
45. ROS Requires Provider Validation
The review of systems records patient-reported feedback by body system, and anyone, even the patient, may record it if the provider reviews and notes pertinent positives and negatives. However, conditions recounted only by the patient are not codable without provider validation elsewhere in the record.
Example: In the ROS the patient reports asthma, but the provider never confirms it in the assessment. The coder excludes asthma because patient-stated conditions lack provider validation.
Mistake to avoid: Coding diagnoses from patient-stated ROS comments that the provider never validated or assessed.
Reference: AAPC CRC study guide sample
46. Coding from the Exam Portion
Objective findings in the exam portion can support diagnosis coding, particularly when paired with provider assessment. Certain clinical details like pressure ulcer stage may be documented by other clinicians, but the associated diagnosis itself must come from the patient's provider to be reportable.
Example: The exam notes a stage 3 pressure ulcer observed by the nurse and the provider documents the ulcer diagnosis. Both the stage detail and the provider's diagnosis support accurate coding of the condition.
Mistake to avoid: Assigning diagnoses from exam findings alone when the provider never establishes the corresponding diagnosis.
Reference: AAPC CRC study guide sample
47. Assessment and Plan as Primary Source
The assessment and plan typically contains the provider's conclusions and is the strongest source for current diagnoses, linkages, and manifestations. Conditions documented here with treatment plans generally support coding, including cause-and-effect relationships the provider explicitly states.
Example: The assessment states 'NSAID-induced gastritis; ibuprofen discontinued, PPI started, GI referral if symptoms persist.' The coder reports the drug-induced gastritis with its documented cause because the assessment explicitly states the cause-and-effect relationship and shows active management of the condition.
Mistake to avoid: Overlooking the assessment while coding only from earlier record sections, missing linkages and current status determinations.
Reference: AAPC CRC study guide sample
48. Annual Face-to-Face Requirement for Chronic Conditions
For a chronic condition to count for risk adjustment, the patient must have a face-to-face visit each year with a provider who assesses and documents that condition. Prior-year documentation alone does not carry forward, which drives annual chronic-condition visit outreach and pre-visit planning.
Example: A member's COPD was documented last year but not this year. The coder flags the member for a visit so the treating provider can assess and document COPD, making it countable again.
Mistake to avoid: Assuming a chronic diagnosis documented in a prior year automatically counts toward the current payment year.
Reference: AAPC CRC study guide sample
Special Coding Rules for Frequently Coded Conditions
49. Status Codes Versus History Codes
Status codes indicate ongoing conditions, sequelae, or devices from past treatment, such as transplant or carrier status. History codes indicate the condition no longer exists. Status codes should not accompany diagnosis codes that already include the status information, and they affect treatment decisions.
Example: A patient has a heart transplant and is being seen for a transplant complication. The coder reports the complication code alone, since the status code would add no information the complication code lacks.
Mistake to avoid: Pairing a status code with a diagnosis code that already conveys the same status, creating redundant reporting.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
50. BMI Coding Conditions
BMI codes are assigned only when an associated reportable diagnosis like obesity exists, are reported as secondary diagnoses only, and are not assigned during pregnancy. The BMI value itself may come from another clinician such as a dietitian, but the associated diagnosis requires provider documentation.
Example: A nurse documents BMI 32.4 and the provider documents obesity. The coder reports obesity with the adult BMI code as secondary; without the obesity diagnosis, the BMI code alone would be incorrect.
Mistake to avoid: Reporting a BMI code without a provider-documented associated diagnosis, or using it as a first-listed code.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
51. Social Determinants of Health Documentation Sources
Social determinants of health codes may be assigned from documentation by clinicians involved in care who are not the patient's provider, such as social workers, case managers, or nurses, when included in the official record. Patient self-reported information also works when signed off and incorporated by a clinician or provider.
Example: A social worker's note in the official record states the patient experiences food insecurity. The coder may assign the food insecurity code based on that documentation, since SDOH represents social rather than medical information.
Mistake to avoid: Coding SDOH from patient mentions never signed off or incorporated into the official medical record.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
52. HIV Coding: Disease Versus Asymptomatic Status
Documented HIV disease, HIV-related illness, or AIDS managed on antiretrovirals codes to HIV disease. Asymptomatic positive status managed on antiretroviral medication, without additional disease documentation, codes to asymptomatic infection status. Screening encounters without symptoms use the HIV screening code, not a diagnosis code.
Example: An asymptomatic patient with documented positive HIV status takes antiretrovirals. The coder assigns the asymptomatic HIV status code, not the HIV disease code, absent documentation of illness or AIDS.
Mistake to avoid: Assigning the HIV disease code for asymptomatic positive status, or a screening code when symptoms are already present.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
53. Chronic Hepatitis Classification
Hepatitis is acute under six months and chronic beyond. Chronic viral hepatitis B and C are frequently coded conditions in risk adjustment models, while the chronic hepatitis unspecified code excludes viral forms. Knowing transmission routes and chronicity helps coders frame accurate queries when documentation is incomplete.
Example: A record documents chronic hepatitis C with ongoing monitoring. The coder reports the chronic viral hepatitis code, understanding chronic hepatitis not otherwise specified excludes the viral hepatitis categories.
Mistake to avoid: Using the chronic hepatitis NOS code for viral hepatitis, which that code expressly excludes.
Reference: AAPC CRC study guide sample
54. Conditions Commonly Miscoded as Current
Certain conditions are routinely miscoded as current: cancers should use history codes when treatment is complete, stroke cannot be coded as active after discharge for that episode, and fractures are not coded once repaired, though untreated vertebral compression fractures may remain current.
Example: A list titled chronic problems includes a hip fracture internally fixed in 2019, breast cancer whose treatment ended in 2018 with no ongoing therapy, and a stroke from 2012 with no residuals documented. The coder reports none as active: the repaired fracture is not coded after repair, the completed cancer calls for a history code, and an active stroke code cannot be used after the discharge episode, though documented residuals would support sequela coding.
Mistake to avoid: Coding an active CVA after the discharge episode, or active cancer absent ongoing treatment, from an unqualified list entry.
Reference: AAPC CRC study guide sample
Audits, Validation, and Review Types
55. RADV Audit Purpose and Structure
A Risk Adjustment Data Validation audit is CMS's review of Part C HCCs to verify that diagnoses in risk scores are supported by documentation. CMS samples patients across high, medium, and low risk factors, and the health plan must submit its best records from acceptable treating providers demonstrating current-year diagnoses.
Example: CMS selects a stratified sample of a plan's members for audit. The plan gathers its best supporting records, knowing the audit evaluates whether paid risk scores match documentation.
Mistake to avoid: Confusing RADV with a claims payment audit; it validates diagnosis support behind risk scores, not billed services.
Reference: AAPC CRC study guide sample
56. RADV Evidence: Authorship and Authentication
The Medicare RADV checklist summarized in the reference requires legible documentation, an acceptable provider type, a valid signature or attestation, a diagnosis current in the audited year, and a face-to-face visit. Authorship and authentication are independent checks: detailed clinical wording cannot cure an ineligible author or a missing signature. One qualifying record may support multiple current diagnoses, not only the diagnosis initially targeted by the audit.
Example: An unsigned medication-review note written by a pharmacist lists diabetes. It cannot serve as acceptable diagnosis support under the checklist merely because the disease is named: both acceptable provider authorship and authentication are missing. Obtain eligible supporting documentation rather than treating the medication list as proof.
Mistake to avoid: Accepting a diagnosis because it appears in a detailed note without checking who documented it, whether the record is authenticated, and whether it supports the audited year.
Reference: AAPC CRC study guide sample
57. Initial Validation Auditor Role
In a hybrid RADV, an Initial Validation Auditor reviews the sample to identify dates of service supporting the HCCs for chosen patients. Understanding this layer helps plans prepare records organized by encounter date and condition, streamlining validation responses.
Example: During a hybrid audit, an Initial Validation Auditor reviews the sampled patients' dates of service to identify which diagnosis codes support the HCCs under review before any CMS follow-up occurs.
Mistake to avoid: Preparing unorganized record sets for audit without mapping encounters to the specific HCCs being validated.
Reference: AAPC CRC study guide sample
58. Retrospective, Concurrent, and Prospective Reviews
Review types are defined by the current date relative to the treatment dates reviewed. Retrospective reviews cover already-reported prior-year encounters; concurrent reviews happen ongoing during the current year; prospective reviews, including home risk assessments, address encounters that affect the following year's payment.
Example: A plan reviews last year's encounters after submission, a retrospective review, while also running ongoing current-year checks, a concurrent review that affects next year's payment.
Mistake to avoid: Labeling a current-year review retrospective simply because the encounter already occurred; timing versus reporting defines the type.
Reference: AAPC CRC study guide sample
59. Supplemental Diagnoses in Validation
Supplemental diagnoses, those not originally submitted through claims, may be approved in validation if documented as current diagnoses in the record for the audited year. Because submitted HCCs are cumulative, audit outcomes can be negative or positive depending on the balance of supported and unsupported conditions.
Example: An HCC was never submitted on a claim, but the record documents the condition as current in the audited year. The supplemental diagnosis may be approved, potentially offsetting other audit findings.
Mistake to avoid: Assuming an audit can only reduce payment; newly supported supplemental diagnoses can offset recoupments.
Reference: AAPC CRC study guide sample
60. Query Triggers: Unclear and Conflicting Documentation
Query the provider whenever documentation is ambiguous, incomplete, or conflicting before assigning codes. The guidelines direct coders to query for clarification when documentation of a condition is unclear, and to query the patient's attending provider when record documentation conflicts, whether the conflicting entries come from the same clinician or different clinicians. Querying a provider on potential omissions also prevents rework and financial loss.
Example: A nurse's note lists the patient's adult BMI as 31.2 while a dietitian's note from the same visit lists 28.9, and the provider documents obesity. Because the BMI documentation conflicts, the coder does not pick between the values but queries the attending provider for clarification before assigning the BMI code.
Mistake to avoid: Coding from conflicting documentation by choosing one value, or silently dropping the condition, instead of querying the attending provider for clarification.
Reference: AAPC CRC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
References and further reading
Source links checked on Oct 2, 2026.