Health Information & Coding · Independent exam preparation
Certified Coding Associate (CCA) Study Guide
Practise setting-specific code selection, sequencing, claim edits, record validation and privacy decisions for AHIMA's early-career Certified Coding Associate exam.
By CertMedbry · Updated 29 October 2026
Learn to distinguish inpatient from outpatient coding rules, select supported classifications, investigate claim edits, and protect patient information. This guide develops those decisions through 60 concepts, original applications, 20 practice questions, and 20 flashcards. It prepares for AHIMA's Certified Coding Associate credential in the context of United States coding, Medicare, and privacy rules. The official six-domain content outline defines the full examination scope; these concepts provide selective coverage.
Try 20 free practice questionsWhat is the exam format?
Check the question types, timing and outline before planning your revision.
Which credential and pathway does this guide cover?
This guide covers AHIMA's Certified Coding Associate (CCA). AHIMA describes it as suitable for early-career professionals who abstract clinical data, assign medical codes, and evaluate claims. It does not combine CCA preparation with the separate CCS, CCS-P, RHIT, or RHIA examinations. International test availability does not change the United States coding and regulatory context used here.
How many questions are scored, and how much time is allowed?
AHIMA specifies 105 total questions: 90 scored questions and 15 unscored pretest questions, randomly distributed throughout the examination. The total appointment is two hours. AHIMA's detailed timing table allocates five minutes to the confidentiality, nondisclosure, and conduct agreement, followed by an examination timer of 1 hour 55 minutes for reading instructions and answering questions. Candidates therefore do not receive 120 minutes for answering questions. Pretest questions do not contribute to the score.
Certified Coding Associate (CCA) | AHIMA · Contact Information & Frequently Asked Questions | AHIMA
How is the examination delivered, and can candidates return to questions?
The CCA examination is computer based and scheduled at a Pearson VUE testing center, domestically or internationally. AHIMA states that candidates cannot move back and forth between items, flag items for review, or return to answered items. Complete each decision before moving forward.
Which item styles are verified?
AHIMA's CCA examination specifications establish question count, timing, and navigation rules without explicitly describing the complete live examination item-style mix. AHIMA describes multiple-choice questions in its preparation products. This guide uses independent four-option, single-best-answer learning drills; they do not reproduce the examination interface or predict a passing result.
Which blueprint applies, and how is this guide distributed?
The outline linked by AHIMA is effective May 1, 2022 and carries a 2024 copyright. Its domains are Clinical Classification Systems, 30–34%; Reimbursement Methodologies, 21–25%; Health Records and Data Content, 13–17%; Compliance, 12–16%; Information Technologies, 6–10%; and Confidentiality & Privacy, 6–10%. This guide allocates its 60 concepts as 20, 14, 9, 8, 4, and 5 respectively. Questions are allocated 6, 5, 3, 3, 1, and 2; flashcards are allocated 6, 4, 3, 3, 2, and 2. Whole-item allocations approximate the published ranges. The official outline remains the full scope.
Which codebooks are required?
For examinations delivered on or after May 1, 2026, AHIMA requires an approved 2026 ICD-10-CM book, an approved 2026 ICD-10-PCS book, and AMA CPT 2026 Professional Edition. Candidates must bring the correct books to the testing center. Check the issuer's approved titles and ISBNs; an otherwise useful coding reference is not automatically permitted.
CCA 2026 Exam Required Code Books · Certified Coding Associate (CCA) | AHIMA
How do examination book requirements differ from clinical code-set effective dates?
The May 1, 2026 examination book requirement is separate from the outline's May 1, 2022 effective date. FY 2027 ICD-10-CM guidelines apply clinically from October 1, 2026 through September 30, 2027. For examination preparation, use AHIMA's specified books. For operational coding, select the edition effective for the applicable encounter or discharge. The worked assignments here use codes available in the required 2026 references and do not require newly introduced FY 2027 codes.
CCA 2026 Exam Required Code Books · Certified Coding Associate (CCA) Exam Content Outline · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 · ICD-10 | CMS
What eligibility and passing information is verified?
AHIMA requires a high school diploma. Coding experience or relevant coding education is recommended rather than required. The published passing score is 300; it should not be interpreted as a percentage-correct requirement. AHIMA's October 29, 2026 CCA page lists examination fees of $199 for members and $299 for nonmembers. Verify current administrative requirements before applying.
The CCA is AHIMA's early-career coding credential. CCS, CCS-P, RHIT, and RHIA are separate credentials with different scopes and requirements. These independently authored learning materials are not official AHIMA examination questions or endorsed preparation materials.
Outline used: AHIMA Certified Coding Associate (CCA) Exam Content Outline: effective May 1, 2022; copyright 2024; currently linked from AHIMA's CCA certification page when reviewed on October 11, 2026. Separate 2026 examination codebook requirements took effect May 1, 2026. The workbook label matches the official credential name.
60 key concepts: understand, apply and avoid the traps
Work through the questions by exam domain. Explain the answer in your own words, try the example, then check the common pitfall.
Clinical Classification Systems30-34%
1.Which code sets fit the service and setting?
Code-set selection begins with the type of information and the reporting setting. ICD-10-CM classifies diagnoses across settings. ICD-10-PCS classifies procedures for hospital inpatient reporting, while CPT describes physician and many outpatient services. A physician's professional service during a hospital admission does not become an ICD-10-PCS service merely because the patient is hospitalized. Identify the claim perspective before selecting the procedure classification or applying setting-specific sequencing rules.
Apply it
An inpatient undergoes surgery, and the hospital and surgeon each prepare a claim. Use ICD-10-PCS for the hospital's inpatient procedure classification and the applicable CPT service classification for the surgeon's professional reporting.
Common pitfall: Choosing a procedure system solely from the patient's location confuses facility inpatient reporting with professional services furnished during the same stay.
ICD-10 | CMS · Certified Coding Associate (CCA) Exam Content Outline
2.How do the Alphabetic Index and Tabular List work together?
The Alphabetic Index supplies a starting point for diagnosis classification, including relevant main terms and subterms. The Tabular List then confirms the code's meaning, completeness, and applicable instructions. A plausible index result is not sufficient by itself because category-level notes, required characters, and sequencing instructions can change the final assignment. Follow the documented condition through both resources rather than selecting a familiar code from memory or a search result.
Apply it
Worked 2026 diagnosis assignment: an inpatient's final assessment establishes an acute gastric ulcer with hemorrhage, without perforation, as chiefly responsible for admission. Follow Ulcer, stomach, acute, with hemorrhage in the Alphabetic Index to K25.0, then verify the complete code in the Tabular List. K25.0 captures the ulcer and its bleeding and is principal under these facts; do not add an unspecified gastrointestinal-bleeding code for the same hemorrhage. K25.9 omits the documented acute status and bleeding; K25.2 adds unsupported perforation; K26.0 classifies a duodenal rather than gastric ulcer. The complete code meanings are corroborated in the [CMS FY 2026 definitions manual](https://www.cms.gov/icd10m/FY2026-fr-v43-fullcode-cms/fullcode_cms/P1421.html).
Common pitfall: Stopping at an index result can miss instructions inherited from a parent category, even when the displayed code description looks clinically appropriate.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026 · ICD-10 | CMS
3.How is a complete diagnosis code distinguished from a category?
An ICD-10-CM category may organize related conditions without being a complete reportable code. Assignment must include all required characters, including laterality and a seventh character when applicable. Placeholder X preserves required character positions in designated codes; it does not supply missing clinical information. Specificity comes from supported documentation and classification instructions, not from choosing the longest code or assuming the affected side from an unrelated part of the record.
Apply it
The documented injury requires a seventh character, but its code structure has fewer than six preceding characters. Insert the required placeholder positions, then select the seventh character supported by the treatment phase.
Common pitfall: A code that looks detailed may still be incomplete. Conversely, adding unsupported laterality creates false precision rather than improving coding accuracy or completeness.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
4.How do code-first and additional-code instructions affect sequencing?
Classification instructions can establish a required relationship between codes. A code-first instruction directs sequencing of the underlying condition before the associated manifestation. A use-additional-code instruction identifies information that another code must supply when applicable. These instructions are evaluated alongside setting-specific guidelines; they cannot be replaced by ordering conditions according to perceived severity, reimbursement, or the sequence in which the provider listed them in the assessment.
Apply it
A documented manifestation directs the coder to code the underlying disease first. Both conditions are supported, so sequence the underlying disease before the manifestation and then evaluate any further applicable reporting instructions.
Common pitfall: Placing the most resource-intensive condition first can violate a mandatory classification sequence, even when that ordering appears financially or clinically intuitive to staff.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
5.What distinguishes Excludes1 from Excludes2?
An Excludes1 note generally identifies conditions that should not be coded together at that location because the excluded condition represents an incompatible classification relationship. The guidelines recognize an exception when the conditions are unrelated; unclear relationships require clarification. An Excludes2 note means the excluded condition is not included in the code, so both may be reported when both exist. The decisive issue is the note's meaning and the documented relationship.
Apply it
Two independently documented conditions appear under an Excludes2 relationship. After confirming that each meets reporting requirements, retain both rather than deleting one simply because the classification places an exclusion note near the other.
Common pitfall: Treating every exclusion note as an absolute prohibition discards reportable conditions. Treating Excludes1 as routinely permissive ignores its different purpose and limited exception.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
6.How is the inpatient principal diagnosis selected?
The principal diagnosis is the condition established after study to be chiefly responsible for occasioning the hospital admission. Selection depends on the circumstances of admission, completed diagnostic evaluation, and applicable sequencing rules. It is not automatically the first symptom, the most expensive condition, or the diagnosis appearing first in a discharge summary. Conditions discovered during the stay must be evaluated for their relationship to admission rather than ranked solely by treatment intensity.
Apply it
A patient is admitted for evaluation of gastrointestinal bleeding. After study, a bleeding ulcer is established as the cause, while stable hypertension is also managed. Evaluate the ulcer as principal under the admission circumstances.
Common pitfall: Selecting the condition with the largest resource use substitutes a payment-oriented shortcut for the definition of principal diagnosis and applicable sequencing guidance.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
7.How is an outpatient first-listed diagnosis selected?
Outpatient first-listed diagnosis selection follows the condition, problem, or other reason chiefly responsible for the services provided, subject to specific encounter guidance. Use the highest degree of certainty established for that encounter. A scheduled service may be for screening, follow-up, or another circumstance rather than active disease treatment. Distinguish the actual reason for the encounter from unrelated chronic conditions and diagnoses that remain only suspected at its conclusion.
Apply it
A patient attends an outpatient visit for evaluation of dizziness. No definitive cause is established, and an unrelated chronic skin condition requires no care. Select the supported reason for the visit rather than the unrelated condition.
Common pitfall: Importing inpatient principal-diagnosis reasoning into outpatient reporting can turn an unconfirmed possibility or incidental problem into an unsupported first-listed diagnosis for the encounter.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
8.When can an uncertain diagnosis be coded as established?
Setting changes the treatment of diagnostic uncertainty. For qualifying inpatient hospital discharges, diagnoses documented at discharge with terms such as probable, suspected, or likely are coded as if established under the inpatient guideline. Outpatient and physician reporting do not apply that rule; report confirmed findings, symptoms, or other reasons for the encounter instead. The qualifying language must represent the final assessment, not merely a possibility mentioned earlier during the workup.
Apply it
An outpatient clinician documents probable pneumonia after evaluating cough and fever. Because pneumonia remains unconfirmed, code the supported symptoms or findings rather than applying the inpatient uncertain-diagnosis rule to this outpatient service.
Common pitfall: The word probable does not have one universal coding consequence. The reporting setting and final documentation determine whether the uncertain-diagnosis guideline applies.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026 · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027
9.When are symptoms reported with a definitive diagnosis?
Symptoms routinely associated with a confirmed disease generally are not separately coded unless classification instructions require otherwise. Symptoms that are not routinely associated with the disease may be reportable when documented and relevant. If no definitive diagnosis is established, symptoms can provide the appropriate diagnosis coding. The decision therefore requires both the certainty of the diagnosis and the relationship between that diagnosis and each symptom, rather than automatic retention of every presenting complaint.
Apply it
A provider establishes a definitive condition explaining the presenting symptom. Review whether the symptom is routinely integral to that condition before reporting it separately, and assess any independently evaluated symptom on its own merits.
Common pitfall: Coding every symptom from the chief complaint can duplicate information already represented by the definitive diagnosis and obscure which additional problems were actually reportable.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
10.When should a combination code be used?
A combination code can classify two diagnoses, a diagnosis with an associated manifestation, or a diagnosis with an associated complication. When it fully identifies the documented elements and the classification directs its use, it replaces unnecessary separate codes for those same elements. Additional coding may still be required by an instruction or to describe information the combination code does not capture. Confirm the documented relationship and the complete code descriptor.
Apply it
The classification provides a single code describing the documented disease and its complication. Verify that the relationship is supported, use that combination code, and then check whether an additional code is specifically required.
Common pitfall: Separately coding every word in a diagnosis can duplicate a combination code. Conversely, one combination code may not satisfy every additional-code instruction.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
11.How are acute and chronic forms of the same condition sequenced?
When the same condition is documented as both acute and chronic and separate subentries exist at the same indentation level in the Alphabetic Index, code both and sequence the acute form first. This rule depends on the classification structure, not merely the presence of both adjectives in a note. A dedicated combination code or other specific instruction may determine the assignment, so verify the index and tabular entries before applying the general rule.
Apply it
A diagnosis is explicitly documented as acute and chronic. The index supplies separate acute and chronic subentries at the same level. After tabular verification, assign both, with the acute condition sequenced before the chronic condition.
Common pitfall: Automatically assigning two codes whenever acute and chronic appear together ignores combination codes and the classification conditions required for this particular sequencing rule to apply.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
12.How does a sequela differ from routine healing?
A sequela is a residual effect remaining after the acute phase of an illness or injury has ended. It is distinguished by the clinical relationship to the old condition, not by a fixed elapsed time. Generally, sequence the residual condition first and the code identifying its cause second, subject to specific instructions. For injury coding, routine healing and recovery belong to subsequent-encounter classification rather than automatically qualifying as sequela care.
Apply it
A healed injury has left a persistent contracture that is now treated. Evaluate sequela coding for the residual contracture and its cause rather than selecting a subsequent-encounter character solely because treatment occurs after the original injury.
Common pitfall: Elapsed time alone does not identify a sequela. An encounter months later may still involve routine healing, while a residual effect requires different coding.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
13.How do poisoning, adverse effects, and underdosing differ?
The circumstances of medication use determine the classification. Poisoning includes improper use, such as an overdose or taking the wrong substance, and generally places the poisoning code before manifestations. An adverse effect follows correct prescription and proper administration; code the nature of the reaction first, followed by the appropriate drug adverse-effect code. Underdosing means taking less than prescribed or instructed. Establish administration circumstances before selecting codes or applying sequencing rules.
Apply it
A patient develops a documented reaction after taking the correctly prescribed dose exactly as directed. Classify the event as an adverse effect and sequence the documented reaction before the code identifying the responsible drug.
Common pitfall: Calling every harmful medication event poisoning ignores correct administration. Calling every missed dose an adverse effect likewise misses the distinct definition of underdosing.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
14.When is a condition present on admission?
Present-on-admission assessment concerns whether a condition existed when the inpatient admission order occurred, not when someone first wrote the diagnosis. Conditions developing during an emergency department, observation, or outpatient surgical encounter before the inpatient order are considered present on admission. A diagnosis established later may still describe a condition already present. Use the record's clinical chronology and applicable indicator definitions rather than equating documentation time with disease onset.
Apply it
A condition begins during observation and remains active when the patient is formally admitted as an inpatient. Although the final diagnosis is documented the next morning, evaluate present-on-admission status from the inpatient order time.
Common pitfall: A late diagnosis is not automatically hospital acquired. Conversely, copying a diagnosis into an admission note does not establish when the condition actually began.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
15.Which details may come from nonprovider documentation?
Diagnosis assignment generally relies on documentation by the provider legally accountable for establishing the diagnosis. The ICD-10-CM guidelines identify limited exceptions for certain details documented by other clinicians, such as body mass index and pressure-ulcer stage. These exceptions do not broadly authorize coders to diagnose disease from measurements, laboratory results, or nursing observations. Distinguish an allowed descriptive detail from the associated diagnosis, which may still require provider documentation.
Apply it
A dietitian documents body mass index, while the provider documents the associated reportable diagnosis. Evaluate the permitted use of the documented measurement without independently deriving an additional disease diagnosis from the number alone.
Common pitfall: An exception allowing a particular detail from another clinician does not authorize every diagnosis appearing in ancillary documentation or calculated from clinical measurements alone.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
16.How does the procedural objective determine the PCS root operation?
ICD-10-PCS root operations describe what the procedure accomplishes according to classification definitions. Excision removes a portion of a body part, while resection removes all of the body part represented by the applicable PCS value. The operative title alone may not establish that distinction. Read the operative description, identify the classified body part and extent removed, and match the objective to the root-operation definition rather than translating a familiar surgical suffix automatically.
Apply it
An operative report describes removal of only part of the classified organ. Even if the procedure title uses a broad removal term, compare the documented extent with the PCS definitions before selecting excision or resection.
Common pitfall: All tissue visible in the specimen is not necessarily all of the PCS body part. Extent must be judged against the classification's anatomical value.
ICD-10-PCS Official Guidelines for Coding and Reporting, 2027 · ICD-10 | CMS
17.How is a valid seven-character PCS code constructed?
A PCS code requires seven characters, with each character supplying a defined component such as root operation, body part, or approach. The index guides the coder to the appropriate table, but the table determines valid combinations. Characters cannot be assembled by mixing choices from incompatible table rows. Confirm the documented procedure against the table and select every required value, including the device and qualifier values applicable to that combination.
Apply it
Worked 2026 inpatient assignment: the surgeon removes the entire gallbladder laparoscopically, without hand assistance, conversion, or another procedure. Locate Resection, Gallbladder in the PCS Index and verify table 0FT. Select 0 Medical and Surgical, F Hepatobiliary System and Pancreas, T Resection, 4 Gallbladder, 4 Percutaneous Endoscopic, Z No Device, and Z No Qualifier: 0FT44ZZ. This is the sole procedure and therefore the principal procedure. Routine access and closure are integral. 0FB44ZZ incorrectly represents partial removal; 0FT40ZZ incorrectly represents an open approach; 0FT44ZG adds unsupported hand assistance. These complete assignments appear in the [CMS FY 2026 procedure listings](https://www.cms.gov/icd10m/FY2026-fr-v43-fullcode-cms/fullcode_cms/P0187.html); table construction and integral-step rules are explained in the [2026 PCS guidelines](https://www.cms.gov/files/document/2026-official-icd-10-pcs-coding-guidelines.pdf).
Common pitfall: Seven valid-looking characters do not guarantee a valid code. A combination can fail because its values are not available together in the same table row.
ICD-10-PCS Official Guidelines for Coding and Reporting, 2027 · ICD-10 | CMS
18.When are a biopsy and definitive procedure both coded in PCS?
PCS identifies qualifying biopsies using the appropriate root operation and the Diagnostic qualifier. When a diagnostic biopsy is followed by a more definitive procedure at the same procedure site, both are coded under the biopsy guideline. This differs from assuming that all diagnostic tissue removal is absorbed into the later therapeutic procedure. The operative record must support the diagnostic objective and the distinct definitive procedure, with valid values selected from the relevant tables.
Apply it
During one operation, a surgeon obtains a diagnostic tissue sample and then performs a definitive resection at that site after evaluation. Apply the PCS biopsy guidance to assess coding of both documented procedural objectives.
Common pitfall: CPT bundling assumptions cannot simply be transferred into PCS. Likewise, a specimen sent for routine pathology does not automatically establish a separately performed diagnostic biopsy.
ICD-10-PCS Official Guidelines for Coding and Reporting, 2027 · ICD-10 | CMS
19.How is a professional office/outpatient E/M level selected?
For professional office/outpatient visits that permit either method, select the level using MDM or total qualifying physician/QHP time on the encounter date. MDM evaluates problems addressed, data reviewed and analyzed, and management risk; at least two of these three elements must meet or exceed the selected level. Count problems actually evaluated or managed. Data includes relevant records, tests, an independent historian, qualifying independent interpretation, or external management discussions. Risk concerns management decisions, including prescription-drug management. One stable chronic illness is a low-level problem example; two stable chronic illnesses are a moderate-level problem example. Time includes patient-specific preparation, evaluation, counseling, orders, documentation, and care coordination when qualifying. Exclude clinical-staff time, work on other dates, and separately reported procedure or service time. History and examination remain medically appropriate but do not set the level. Emergency department, critical-care, preventive, and facility-clinic services have different selection rules. See [First Coast's office/outpatient guidance](https://medicare.fcso.com/evaluation-and-management/office-and-other-outpatient-em-services).
Apply it
Worked 2026 professional assignment: an established office patient has two stable chronic illnesses evaluated and managed. The practitioner documents medication response, adverse-effect assessment, and decisions to continue prescribed therapy; no data work contributes. Problems are moderate and prescription-drug management supplies moderate risk, meeting two of three elements: select CPT 99214. Alternatively, 32 documented qualifying physician/QHP minutes on that date support 99214 by time. It is the sole service, so no additional service sequencing or modifier is needed. 99213 understates the documented MDM when selecting by MDM; 99215 lacks high-level MDM or its time threshold; 99204 belongs to the new-patient family. The [AMA's 99214 guidance](https://www.ama-assn.org/practice-management/cpt/cpt-code-99214-established-patient-office-visit-30-39-minutes) identifies moderate MDM and the 30–39-minute time band. The [AMA's outpatient teaching example](https://edhub.ama-assn.org/steps-forward/audio-player/18889456) explains the two-stable-illness and prescription-management criteria.
Common pitfall: Prescription management supplies only the risk element; it does not independently establish moderate MDM. A long note, an untouched problem-list diagnosis, or staff time cannot supply missing level-selection criteria.
Certified Coding Associate (CCA) Exam Content Outline · mln006764-evaluation-management-services.pdf
54.Why is a clinical terminology not interchangeable with a classification?
Clinical terminologies support detailed recording and exchange of clinical concepts, while classifications organize information for defined reporting purposes. Mapping between them can help locate a candidate category, but different granularity and relationships may prevent a one-to-one match. A mapped code therefore still requires review against documentation, classification conventions, and the reporting context. The presence of a structured clinical term does not by itself establish the final billable code or resolve required sequencing. Technology cross-reference: EHR terminology mappings and encoder suggestions require validation before claim export.
Apply it
An EHR maps a detailed clinical term to a diagnosis category. Use the mapping as a starting point, then verify the complete reportable code, supported specificity, and applicable instructions rather than exporting the category without review.
Common pitfall: Assuming a one-to-one mapping can lose required detail or introduce unsupported precision. Structured terminology and reimbursement classification serve related but different information needs in practice.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
Reimbursement Methodologies21-25%
20.What drives MS-DRG grouping, and which secondary diagnoses are reportable?
Medicare Severity Diagnosis Related Group (MS-DRG) assignment uses the principal diagnosis, procedures, reportable secondary diagnoses, and applicable demographic and discharge information. Under Section III of the FY 2026 ICD-10-CM Official Guidelines, an additional clinically significant condition affects care by requiring at least one of these: clinical evaluation, therapeutic treatment, diagnostic procedures, extended hospitalization, or increased nursing care or monitoring. Conditions may coexist at admission or develop during the stay. Conditions from an earlier episode that have no bearing on the current hospitalization are excluded. Documentation, reportability, and grouping status are separate determinations: establish that the diagnosis is supported, determine whether it qualifies for reporting, and then determine its effect under the grouper. A reportable diagnosis need not be a complication or comorbidity (CC) or major complication or comorbidity (MCC), and a code's CC/MCC designation alone does not establish reportability.
Apply it
During an admission for pneumonia, the physician documents hypokalemia and orders potassium replacement and repeat laboratory testing. The hypokalemia meets additional-diagnosis criteria through therapeutic treatment and evaluation. A remote, resolved condition mentioned in the history that receives no evaluation or management and has no bearing on the stay does not qualify as an active additional diagnosis. After assigning supported codes, validate the MS-DRG; do not assume that every reportable secondary diagnosis changes the group.
Common pitfall: Neither appearance on a problem list nor potential CC/MCC status is sufficient by itself. Conversely, a condition does not need to prolong hospitalization if another Section III criterion is met. Do not infer a diagnosis solely from an abnormal laboratory value: diagnosis documentation and its effect on care must support reporting before grouping consequences are considered.
Medicare Payment Systems | CMS · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
21.How do APCs differ from inpatient DRGs?
Ambulatory Payment Classifications support Medicare hospital outpatient prospective payment, whereas MS-DRGs support eligible hospital inpatient stays. Outpatient payment evaluates reported services under applicable payment-status, packaging, and grouping rules. Multiple reported lines do not necessarily create separately payable services because some costs are packaged into other payments. The reporting setting and payment methodology must therefore be identified before interpreting a payment result or investigating why a coded service received no separate payment.
Apply it
A hospital outpatient claim contains several service lines, but one receives no separate payment. Examine the applicable outpatient packaging and payment-status rules before concluding that the service was omitted or that inpatient DRG logic applies.
Common pitfall: A valid outpatient code does not guarantee separate APC payment. Coding validity, payment status, and packaging answer related but distinct questions for the claim.
22.Why does Medicare Advantage use diagnosis-based risk adjustment?
Medicare Advantage risk adjustment seeks to account for differences in expected costs associated with beneficiary characteristics, including qualifying diagnoses. CMS-HCC models organize relevant diagnoses into condition categories and apply model rules, including hierarchies. This differs from paying separately for each diagnosis or reimbursing a single encounter through a DRG. Accurate, supported diagnosis reporting matters; adding historical, unsupported, or duplicate diagnoses does not become appropriate because a condition might affect risk adjustment.
Apply it
A reviewer proposes adding a serious condition from a remote historical note to improve a beneficiary's risk profile. Validate the applicable reporting evidence and current documentation instead of treating potential risk-adjustment impact as sufficient support.
Common pitfall: An HCC is not an automatic payment bonus attached to every diagnosis. Model eligibility, hierarchy, documentation, and reporting requirements determine whether information contributes to adjustment.
Report to Congress: Risk Adjustment in Medicare Advantage, December 2024 · AHIMA Standards of Ethical Coding, 2016 Version
23.How is a simplified relative-weight payment calculated?
A relative weight represents resource intensity relative to a reference level within a payment methodology. In a simplified exercise that explicitly defines payment as base amount multiplied by relative weight, multiply those supplied values and retain currency units. Actual Medicare payments can involve additional adjustments, so the simplified result is not a complete reimbursement quotation. Separate the arithmetic skill from the operational task of identifying every payment adjustment applicable to a real claim.
Apply it
An exercise supplies a $6,200 base amount and a relative weight of 1.25, with no other adjustments. Calculate $6,200 multiplied by 1.25 to obtain the exercise's simplified payment of $7,750.
Common pitfall: Adding the relative weight to the base amount confuses a multiplier with currency. Treating the simplified product as actual payment ignores additional methodology-specific adjustments.
24.What does an NCCI procedure-to-procedure edit evaluate?
A Medicare NCCI procedure-to-procedure edit evaluates a pair of procedure codes that ordinarily should not be reported together in the specified circumstances. The edit identifies a coding relationship, not a blanket rule that two services can never occur on the same date. Resolution requires the applicable edit, its modifier indicator, and documentation of what actually happened. Review the correct practitioner or outpatient hospital edit set rather than assuming every setting uses an identical file.
Apply it
Two procedure lines trigger an edit on a Medicare claim. Identify the applicable code pair and edit set, review the modifier indicator, and compare the documented services before removing a code or considering a modifier.
Common pitfall: Treating a code-pair edit as a unit limit confuses PTP edits with MUEs and directs the investigation toward the wrong claim characteristic entirely.
25.How do MUE Adjudication Indicators determine whether units are evaluated by claim line or date of service?
A Medicare NCCI medically unlikely edit (MUE) evaluates units of service for a particular code; a procedure-to-procedure edit evaluates a code pair. The MUE Adjudication Indicator (MAI) determines how the unit limit operates. MAI 1 evaluates each claim line separately. Appropriately reported separate lines with supported modifiers can therefore matter for distinct services. MAI 2 is a policy-based absolute date-of-service edit at Medicare Administrative Contractor (MAC) processing and redetermination; documentation of additional services does not permit the MAC to override that limit at those stages. MAI 3 is a clinical-benchmark date-of-service edit: units exceeding the benchmark may be payable following review when records establish that the services were actually furnished, correctly coded, and reasonable and necessary. For MAI 2 and MAI 3, units for the same code, beneficiary, provider or supplier, and date are aggregated across claim lines rather than evaluated independently.
Apply it
Hypothetically, a code has an MUE of two units. The record supports two units at an initial session and one unit at a separate repeat session, and the coding rules permit separate lines with an appropriate repeat-service modifier. With MAI 1, lines reporting two units and one unit each remain within the line-level MUE, although other payment rules still apply. With MAI 3, the same lines aggregate to three units and trigger the date-of-service edit; payment for the excess requires supporting review. With MAI 2, the three-unit total exceeds the absolute limit at MAC processing and redetermination.
Common pitfall: A modifier does not convert a date-of-service edit into a line edit. For MAI 2 or MAI 3, exceeding the aggregated limit causes denial of all units of that code for the date, not merely the excess. First verify the code's unit definition and actual quantity. Separate lines must accurately describe supported services; dividing one service into artificial lines solely to evade an edit is improper.
Medicare NCCI FAQ Library | CMS · Medicare NCCI 2026 Coding Policy Manual, Chapter 1
26.How do NCCI modifier indicators guide edit resolution?
For an active PTP edit, modifier indicator 0 means an NCCI-associated modifier cannot bypass the edit. Indicator 1 means an appropriate modifier may permit separate reporting when the clinical circumstances and documentation justify it. Indicator 1 is permission to evaluate a supported exception, not an instruction to append a modifier automatically. Confirm the edit's effective period as well as the code pair before applying the indicator to a particular service date.
Apply it
A code pair has modifier indicator 1, but the operative report describes one integral service. Retain the edit's consequence because the indicator alone does not establish a distinct service or support modifier use.
Common pitfall: Reading indicator 1 as guaranteed payment turns an edit attribute into unsupported clinical evidence. Indicator 0 likewise cannot be overcome simply by adding modifier 59.
27.When does modifier 59 support distinct procedural services?
Modifier 59 identifies a distinct procedural service when the circumstances meet applicable coding requirements and no more descriptive modifier is appropriate. Supporting distinctions can involve separate encounters, sites, lesions, or other qualifying independent circumstances. A different diagnosis alone does not establish a distinct service. First determine whether the services were genuinely separate, then verify that the edit permits an override and that the documentation supports the selected modifier or more specific alternative. Modifier 59 must not be appended to an E/M service.
Apply it
Two edited procedures were performed on separately documented lesions at distinct sites. Review the applicable edit and available anatomical or other specific modifiers before determining whether modifier 59 appropriately communicates the documented procedural distinction.
Common pitfall: Appending modifier 59 whenever two diagnoses differ mistakes diagnosis variety for procedural independence and can improperly unbundle services that remain integral to one another.
28.When is modifier 25 appropriate?
Modifier 25 identifies a significant, separately identifiable E/M service performed by the same physician or qualified practitioner on the same day as another procedure or service. The E/M work must exceed the evaluation normally inherent in the procedure. A separate diagnosis is not required, but supporting documentation is. Append the modifier to the E/M code when justified; routine preprocedure assessment alone does not create a separately reportable E/M service.
Apply it
At a procedure visit, the clinician also evaluates a separate acute complaint and documents substantial assessment and management beyond routine procedure-related work. Evaluate reporting the supported E/M service with modifier 25 on that E/M code.
Common pitfall: A same-day visit does not automatically warrant modifier 25. A different diagnosis can support context but cannot substitute for separately identifiable E/M work.
29.Why are integral procedural components bundled?
Bundling prevents separate reporting of components already represented by a more comprehensive service under applicable coding rules. A component may be clinically necessary and thoroughly documented yet remain included in the larger procedure. Evaluate code descriptors, coding instructions, and NCCI policy before treating separate documentation as proof of separate payment eligibility. Distinct reporting requires a supported exception; routine preparation, access, or closure does not become independent simply because it appears in its own paragraph.
Apply it
A surgeon documents routine steps required to complete a comprehensive procedure. Before adding component codes, determine whether those steps are included in the primary service and whether any documented circumstance supports a recognized separate-reporting exception.
Common pitfall: Documentation proves that work occurred; it does not independently prove that each step is separately reportable under the applicable procedure classification or payment rules.
30.How are NCDs and LCDs used to assess coverage?
A National Coverage Determination states Medicare coverage policy at the national level, while a Local Coverage Determination applies within the issuing contractor's jurisdiction. Coverage research must match the service, jurisdiction, and effective date. Related billing and coding articles may supply operational coding details. A diagnosis appearing on a list does not replace all other coverage conditions, and a technically valid procedure code does not establish that Medicare covers the service for that encounter.
Apply it
A Medicare service is denied for medical necessity. Locate the relevant national policy and any applicable local policy and coding article, then compare their effective requirements with the service date, indication, and supporting documentation.
Common pitfall: Using an LCD from another jurisdiction or a superseded policy can produce a confident but inapplicable coverage conclusion for the claim being reviewed today.
31.How should diagnoses be linked to individual services?
Diagnosis linkage explains which documented condition or reason supports a particular billed service. The presence of a diagnosis somewhere on a claim does not mean it supports every line. Review the service's actual indication and applicable payer policy, then link the supported diagnosis appropriately. Never add or substitute a diagnosis solely because it appears on a coverage list. A coverage problem may reflect missing linkage, incomplete documentation, or a genuinely noncovered circumstance.
Apply it
A visit addresses two conditions, but only one prompted a diagnostic test. Link the test to its documented indication and check the relevant coverage criteria rather than attaching every diagnosis indiscriminately to the service.
Common pitfall: Selecting a payable diagnosis from a policy list without encounter support converts coverage research into inaccurate coding and does not legitimately establish medical necessity.
Medicare Coverage Database | CMS · AHIMA Standards of Ethical Coding, 2016 Version
32.Which claim formats distinguish professional and institutional billing?
Professional services use the CMS-1500 paper claim or the corresponding 837P electronic transaction. Institutional services use the CMS-1450, commonly called UB-04, or the corresponding 837I electronic transaction. These distinctions concern the billing entity and service reporting framework rather than simply whether care occurred inside a hospital. Medicare generally requires electronic submission unless an applicable exception permits paper, so identifying a paper form does not establish permission to submit it.
Apply it
A physician submits a professional claim for services furnished in a hospital. Select the professional transaction framework rather than the institutional framework solely because the patient's care occurred in a hospital facility that day.
Common pitfall: Hospital location does not make every claim institutional. Confusing the billing perspective can lead to selecting the wrong form or electronic transaction for the service.
Professional Paper Claim Form (CMS-1500) | CMS · Medicare Claims During Public Health Emergencies | CMS
33.How should a coding-related denial be investigated?
Begin denial review by identifying the stated reason and locating the relevant claim, documentation, and applicable policy. Distinguish an incorrect code, missing information, unit error, coverage issue, and payer processing problem because each calls for a different response. Correct inaccurate claim data when supported; use an appeal or other appropriate review process when the original submission is supported but disputed. Preserve the rationale and communicate required action to the responsible department.
Apply it
A denied line carries a medical-necessity reason, but the documented covered indication was omitted from the claim linkage. Verify the policy and record, then pursue the supported claim correction through the payer's applicable process.
Common pitfall: Changing codes until a claim pays obscures the actual denial cause and can introduce unsupported information instead of resolving the original coding or coverage problem.
Medicare Coverage Database | CMS · AHIMA Standards of Ethical Coding, 2016 Version
Health Records and Data Content13-17%
34.What does quantitative record analysis establish?
Quantitative analysis asks whether required record components are present and complete in the expected structural sense. Examples include the presence of an operative report, required authentication, or a discharge summary. It identifies missing elements without establishing that the narrative is clinically coherent or sufficient for every assigned code. Distinguish this completeness review from qualitative analysis, which evaluates the substance and consistency of the information contained in those components.
Apply it
A completed surgical encounter has an anesthesia record and nursing notes, but no operative report appears in the record. Flag the missing report as a quantitative deficiency and request the appropriate documentation through established channels.
Common pitfall: A record containing every expected document can still contain contradictions. Structural completeness does not prove that its clinical content adequately supports the assigned codes.
35.What does qualitative record analysis establish?
Qualitative analysis evaluates whether record content is clear, internally consistent, and sufficient for its intended use. A report may be present and authenticated yet describe conflicting procedure sites or omit details needed to classify the service. This review examines meaning rather than counting documents. Identify the specific ambiguity and its coding consequence, then obtain an appropriate clarification rather than silently choosing whichever statement produces a convenient code assignment.
Apply it
Both the operative report and discharge summary are present, but they identify different procedure sides. Treat the inconsistency as a content deficiency and seek clarification before assigning a laterality-specific code for the affected service.
Common pitfall: Checking document presence alone misses substantive contradictions. Choosing the most detailed note without resolving conflicting information can preserve an unsupported assumption in the final code.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
36.How should patient identity be matched before abstraction?
Patient matching compares multiple demographic attributes to connect information to the correct individual. Names alone are insufficient because different people may share a name and one person's name may change. Date of birth, address, telephone information, and other available identifiers contribute to the assessment. Discrepancies require reconciliation before combining records or abstracting diagnoses; an incorrect match can contaminate clinical histories, coding, billing, and subsequent privacy decisions at the same time.
Apply it
Two master patient index entries share a name but differ in birth date and address. Investigate the discrepancy using additional identifiers and established identity-management procedures before merging records or importing either patient's clinical information.
Common pitfall: A matching name or one shared demographic field does not establish identity. Premature merging can combine two patients' records and create both clinical and privacy consequences.
37.Which record components answer different coding questions?
Different record components provide different kinds of evidence. Operative reports describe procedural objectives and technique; pathology reports describe examined tissue; medication records document administration; and provider assessments establish diagnostic conclusions within applicable coding rules. One component may inform review without independently supporting every code. Select the source that answers the specific classification question, reconcile conflicting information, and distinguish clinical findings from diagnoses that a coder is not authorized to establish independently.
Apply it
A procedure title lacks enough detail to distinguish partial from complete removal. Review the operative narrative for the extent and objective rather than relying solely on the scheduling label or the specimen's abbreviated description.
Common pitfall: Treating every record component as interchangeable can turn a test result into an unsupported diagnosis or a scheduling label into an inaccurate procedure classification.
Certified Coding Associate (CCA) Exam Content Outline · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026 · ICD-10-PCS Official Guidelines for Coding and Reporting, 2027
38.How is current clinical information separated from history?
Abstraction should preserve the distinction between a current condition, a resolved condition, and historical information relevant to the encounter. A diagnosis on a longstanding problem list does not automatically establish that it is currently active or reportable. Review the encounter's assessment, treatment, monitoring, and applicable setting-specific criteria. Historical status may itself be relevant, but it should not be converted into active disease merely because the same wording appears repeatedly in the record.
Apply it
A problem list carries a remote infection, while current notes describe it as resolved and provide no active treatment. Evaluate appropriate history reporting if relevant rather than abstracting the infection as an active condition today.
Common pitfall: Copying the entire problem list into coded data mistakes persistence in the software for current clinical status and can overstate the patient's active disease burden.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026 · AHIMA Standards of Ethical Coding, 2016 Version
39.How should missing patient-specific documentation be obtained?
A missing source document should be pursued through the department or practitioner responsible for that patient-specific information. Identify the encounter, document type, and unresolved coding question so the request is actionable. An ancillary report can complete the record, but obtaining it does not remove rules governing who may establish a diagnosis. Keep document retrieval separate from a clinical clarification request, which asks an accountable provider to resolve ambiguity in existing documentation.
Apply it
The chart refers to a procedure performed elsewhere, but its operative report is absent. Request that patient's report from the appropriate source, verify identity and encounter details, and reassess whether the recovered information answers the coding question.
Common pitfall: Using another patient's example report or a standard procedure template cannot replace missing patient-specific evidence, even when the scheduled procedure name appears to match exactly.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
40.How should corrections and delayed entries preserve record integrity?
CMS Program Integrity Manual section 3.3.2.5 states that an amendment, correction, or delayed entry should have an identifiable date and author, and the change or addendum should be clearly and permanently denoted. Additional record-integrity guidance from [Noridian on amended medical records](https://med.noridianmedicare.com/web/jeb/article-detail/-/view/10525/documentation-guidelines-for-amended-medical-records) expressly addresses preserving original entries: paper corrections keep the original legible, and electronic corrections track both the original entry and the correction. Together, these practices reveal the content, authorship, and chronology of changes without concealing earlier documentation.
Apply it
A practitioner notices an omitted detail after completing a note. Identify the addition, its author, and the actual amendment date. Preserve the original entry and distinguish the added information from earlier documentation. An electronic correction should retain both versions and identify the change.
Common pitfall: Backdating an addition or overwriting the original text hides chronology. A clinically plausible statement does not excuse an amendment process that obscures authorship or timing.
41.How should a coding accuracy report's denominator be interpreted?
A percentage has meaning only when its numerator, denominator, and unit of analysis are defined. Encounter-level accuracy asks how many reviewed encounters met the specified standard, while code-level accuracy asks how many individual codes were correct. Those measures can differ substantially when encounters contain multiple codes. Use the report's actual definition, apply consistent inclusion rules, and avoid generalizing a selected audit sample to all production without considering how that sample was chosen.
Apply it
An audit defines encounter accuracy as records with no coding errors divided by records reviewed. If 72 of 80 records meet that definition, report 90% encounter accuracy rather than using the total number of individual codes.
Common pitfall: Comparing code-level and encounter-level percentages as if they measure the same thing can create a false improvement or deterioration without any actual change in performance.
42.Why does documentation chronology matter during abstraction?
Chronology helps distinguish preliminary impressions from final conclusions and old information from the current encounter. A copied diagnosis may persist after it was ruled out, while a later authenticated assessment may clarify the final condition. Review encounter dates, author roles, document status, and amendments together. The latest timestamp alone is not a universal authority rule, but temporal context prevents a preliminary note or imported historical text from being mistaken for the final clinical assessment.
Apply it
An early progress note lists a possible condition, but the discharge assessment rules it out. Trace the sequence and final conclusion before abstraction rather than retaining the early wording because it appears repeatedly in copied notes.
Common pitfall: Counting repeated mentions does not establish diagnostic certainty. Multiple copied entries may originate from one preliminary statement that was later corrected or excluded from the final assessment.
ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026 · Medicare Program Integrity Manual, Chapter 3
Compliance12-16%
43.How does an ethical query clarify documentation?
An ethical query seeks clarification of incomplete, ambiguous, or conflicting documentation without directing the provider toward a preferred financial outcome. It presents relevant patient-specific information accurately and asks the accountable clinician to supply their clinical judgment. The coder identifies the documentation problem but does not diagnose the patient. A useful query makes the uncertainty clear and allows an appropriate response, including that a condition cannot be determined from the available clinical evidence.
Apply it
Two provider notes describe incompatible diagnoses affecting code assignment. Present the conflicting statements and relevant clinical context, then request clarification without suggesting that the higher-paying diagnosis is the expected or desired clinical conclusion.
Common pitfall: A query becomes leading when its wording pressures the provider to confirm a financially advantageous condition instead of accurately clarifying the patient's documented clinical circumstances.
44.How should discrepancies between coded data and documentation be resolved?
A discrepancy review compares the assigned code's meaning with the actual supporting record. Determine whether the problem is a selection error, missing specificity, conflicting documentation, or an unsupported diagnosis. Correct an evident coding error from existing support; seek clarification when the clinical documentation itself is unresolved. Preserve the basis for the final decision so later reviewers can distinguish a supported correction from an undocumented change made only to alter reimbursement.
Apply it
A code indicates a complication, but the provider's assessment does not establish that relationship. Review the full record and applicable instructions, then clarify the unresolved relationship rather than inferring a complication from timing alone.
Common pitfall: An event occurring after a procedure does not automatically establish a procedural complication. Temporal association cannot replace required documentation of the condition and its relationship.
AHIMA Standards of Ethical Coding, 2016 Version · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
45.Why must provider-entered codes still be validated?
A provider-entered code is proposed coded data, not an exemption from documentation and classification requirements. The narrative may support a different level of specificity, a different code, or no reportable condition. Compare the proposed assignment with the documented assessment and applicable instructions. Preserve the provider's authority over clinical diagnosis while exercising the coder's responsibility for accurate classification; clarification is appropriate when those sources cannot be reconciled without additional clinical information.
Apply it
A provider selects a detailed diagnosis code from a menu, but the assessment documents only an unspecified condition. Review whether existing documentation supports the detail and request clarification when needed instead of accepting the menu selection automatically.
Common pitfall: Treating a selected code as self-validating can preserve unsupported specificity. Conversely, a coder should not replace the provider's clinical diagnosis with an independently inferred disease.
46.How should financial pressure be handled in coding decisions?
Ethical coding reports the supported services and conditions accurately, even when an unsupported alternative would increase reimbursement. Upcoding exaggerates the reportable service or condition; inappropriate unbundling separates components that coding rules include together. Recognize the specific proposed distortion, explain the documentation or classification boundary, and use the organization's compliance process when pressure persists. Payment improvement should come from correcting legitimate omissions and errors, not from manufacturing diagnoses, complexity, or procedural independence.
Apply it
A supervisor requests a higher service level because a payer reimburses the current level poorly. Compare the service with the applicable criteria and documentation, retain the supported level, and address the request through established compliance channels.
Common pitfall: A revenue target is not evidence of service complexity. A payer's low payment does not justify changing codes beyond what the documented encounter supports.
47.Which date determines the applicable code-set version?
Code-set applicability depends on the relevant service or discharge date and the implementation rules for that setting. For inpatient ICD-10 reporting, discharge date determines the applicable version; outpatient reporting follows the applicable encounter or service date. The date a coder completes the claim does not ordinarily substitute for those dates. Verify official effective periods, including applicable interim updates, and distinguish operational code-set implementation from an examination's separate requirement to use specified books.
Apply it
An inpatient is discharged before an October code-set transition, but coding is completed afterward. Apply the version effective for the discharge rather than selecting the newer version merely because it is available on the coding date.
Common pitfall: The newest installed code set is not automatically correct for every claim. Delayed coding and retrospective corrections still require the version applicable to the encounter.
ICD-10 | CMS · ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
48.How should chargemaster and charge-ticket changes be implemented?
A coding update must reach the operational tools that generate charges and claims, including charge tickets and chargemaster mappings. Research additions, revisions, deletions, and effective dates, then assess which local services and linked systems are affected. A replacement code must accurately describe the service rather than merely resemble an old descriptor. Implement date-sensitive changes, communicate revised use, and verify downstream output so an updated reference does not coexist with obsolete production mappings.
Apply it
A procedure code is deleted for the next effective period. Identify every local charge linked to it, determine supported replacement handling, update the effective-date mapping, and inspect test claim output before the change enters routine production.
Common pitfall: Replacing a deleted code with the nearest-looking descriptor can misclassify services. Updating the reference library alone also leaves errors if charge-generation mappings remain unchanged elsewhere.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
49.What makes an external audit response defensible?
An audit response should connect each questioned assignment to the authentic encounter record, applicable coding rule, and version in effect. Organize requested materials so reviewers can follow the rationale without reconstructing it from unsupported assertions. Preserve original documentation and clearly identified amendments; do not rewrite records to make earlier coding appear justified. When review identifies an error, acknowledge and correct it through the appropriate process rather than defending an assignment solely because it was previously submitted.
Apply it
An auditor questions a secondary diagnosis. Assemble the relevant assessment, treatment evidence, applicable reporting rule, and code rationale, then evaluate whether they support the original assignment before preparing a response or correction for that encounter.
Common pitfall: A confident explanation cannot substitute for supporting records. Altering original documentation during an audit weakens integrity rather than curing a historical documentation deficiency after submission.
AHIMA Standards of Ethical Coding, 2016 Version · Medicare Program Integrity Manual, Chapter 3
50.How should audit findings guide provider education?
Effective education turns a recurring documentation or coding error into a specific, observable improvement. Identify the shared mechanism, explain the governing distinction, and demonstrate what adequate patient-specific documentation looks like. Avoid teaching providers to insert diagnoses or phrases solely to trigger payment. Measure the same defined error after education to determine whether the intervention improved accuracy, while separating documentation deficiencies from classification mistakes that belong to coder or system workflows.
Apply it
An audit finds repeated confusion between current disease and remote history. Teach that distinction using de-identified examples, explain the documentation needed for each status, and repeat a comparable review to assess whether the specific error declines.
Common pitfall: Generic reminders to document more may increase note length without correcting the actual error. Education should target the missing distinction and use consistent follow-up measures.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
Information Technologies6-10%
51.How should an EHR be navigated for coding evidence?
Efficient EHR navigation follows the coding question to the relevant encounter documents while preserving source context. Check patient identity, encounter date, author, document status, and whether information is historical, imported, or amended. Search results can reveal useful text without establishing its authority or current applicability. A diagnosis mentioned in a preliminary note, patient message, or copied problem list should not automatically carry the same coding significance as a supported final provider assessment.
Apply it
An EHR search finds a diagnosis in several notes. Open the source documents, verify the encounter and authorship, and determine whether the entries reflect a final assessment, copied history, or an earlier possibility that was later excluded.
Common pitfall: A prominent search result or dashboard label may hide provenance. Coding directly from snippets can miss negation, historical context, conflicting conclusions, or later clarifying amendments.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
52.How do encoders and groupers perform different tasks?
An encoder assists code selection through classification searches, pathways, and reference support. A grouper applies a payment classification methodology to supplied coded and encounter data. Neither tool independently proves that a diagnosis was documented or that a procedure was classified correctly. Validate source documentation and code construction first, then evaluate grouping results. A grouper output is only as sound as its inputs and the installed methodology version used for the relevant encounter.
Apply it
A user changes one diagnosis and sees the DRG change. Review whether the diagnosis is supported before accepting the new group, and distinguish the encoder's selection assistance from the grouper's calculation using the revised inputs.
Common pitfall: A successful software calculation confirms processing, not clinical truth. Neither a valid code nor a plausible group establishes that the underlying condition belongs on the claim.
Certified Coding Associate (CCA) Exam Content Outline · Medicare Payment Systems | CMS
53.How should computer-assisted coding suggestions be validated?
Computer-assisted coding identifies candidate codes from electronic text, but text recognition does not establish reportability. Review negation, uncertainty, historical context, patient versus family history, author role, and final clinical conclusions. A software suggestion may recognize a disease term while missing that the provider ruled it out. The coder remains responsible for applying setting-specific guidelines and confirming documentation support instead of accepting all suggestions or assuming that a high-confidence score resolves clinical context.
Apply it
CAC proposes an active disease code from the sentence stating that the disease was ruled out. Reject that suggestion after reviewing context and evaluate the final documented condition or symptoms under the applicable setting-specific guidelines.
Common pitfall: A confidence score measures the software's output, not legal or clinical documentation sufficiency. Recognizing the correct word can still produce the wrong reportable diagnosis.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
55.How can interface errors alter claims after coding?
Practice management, HIM, EHR, and billing systems exchange information through configured interfaces and mappings. An accurate code in the coding workspace may arrive incorrectly downstream if characters, units, modifiers, diagnosis links, or effective-date logic are changed or omitted. Validate the transmitted output when investigating a mismatch rather than repeatedly changing the source code. Comparing source data with the resulting claim helps locate whether the failure belongs to coding, mapping, or transmission.
Apply it
A coder's finalized record contains the correct modifier, but the submitted claim lacks it. Compare the finalized data with the claim output and investigate the interface mapping instead of adding an unsupported second modifier to compensate.
Common pitfall: Correcting accurate source data to counter a transmission defect can create new errors. Locate where the information changed before selecting the responsible corrective action.
Certified Coding Associate (CCA) Exam Content Outline · AHIMA Standards of Ethical Coding, 2016 Version
Confidentiality & Privacy6-10%
56.When does HIPAA's minimum necessary standard apply?
HIPAA generally requires reasonable efforts to limit covered uses, disclosures, and requests for PHI to the minimum necessary for their purpose. Policies can define role-based access for routine work. The standard has specific exceptions, including disclosures to or requests by a healthcare provider for treatment. That exception does not permit unrelated employee curiosity access. First identify the purpose and applicable exception, then apply the appropriate authorization and access requirements.
Apply it
A billing employee needs records to resolve a claim, while a treating provider requests information for care. Apply purpose-appropriate access to billing work and recognize the provider-treatment exception rather than imposing the same minimum-necessary rule on both.
Common pitfall: The treatment exception does not authorize every employee to browse records. Conversely, minimum necessary should not be used to misstate the rule for provider treatment requests.
57.Why are unique user IDs required for ePHI systems?
Unique user identification allows a system to identify and track each user's identity when accessing electronic protected health information. HHS explains that assigning the same login ID to multiple employees does not satisfy this requirement. Individual credentials support accountability and investigation of access events. Sharing a departmental password defeats that attribution even if everyone in the department has legitimate duties; access convenience should be addressed through appropriate individual accounts and permissions.
Apply it
A coding team proposes one shared account for weekend coverage. Maintain separate authorized user IDs so each person's activity remains attributable, and arrange appropriate access for coverage rather than distributing a common login credential.
Common pitfall: A shared account does not become compliant because its password is strong. Credential strength cannot restore the individual attribution lost when multiple employees use one identity.
58.What distinguishes information blocking from legitimate confidentiality controls?
Information-blocking rules cover healthcare providers, developers of certified health IT, and health information networks/exchanges. A practice can qualify when it is likely to interfere with access, exchange, or use of electronic health information, unless required by law or covered by a regulatory exception. For providers, the knowledge standard is knowing that the practice is unreasonable and likely to interfere; for covered developers and networks/exchanges, it is knowing or having reason to know that interference is likely. EHI includes electronic protected health information to the extent that it would be included in a designated record set, regardless of whether the records are used or maintained by or for a HIPAA covered entity. It excludes psychotherapy notes as defined in 45 CFR 164.501 and information compiled in reasonable anticipation of, or for use in, a civil, criminal, or administrative action or proceeding. Evaluate the actor, information, interference, knowledge standard, and legal or exception basis. Failure to meet an exception alone does not establish information blocking; all relevant elements require case-specific evaluation.
Apply it
A provider knowingly imposes an unnecessary seven-day hold on electronic results requested by an authenticated patient, despite immediate technical availability and no legal restriction or applicable exception. The delay interferes with access and raises an information-blocking concern under the provider knowledge standard. Merely believing that the patient might sue does not remove ordinary clinical results from EHI: the exclusion requires information compiled in reasonable anticipation of, or for use in, a specified action or proceeding. A restriction specifically required by applicable law is excluded from the information-blocking definition. Verify a recipient's identity and authority for release without extending that check into an unnecessary access delay.
Common pitfall: A generic appeal to privacy does not establish a lawful restriction or satisfy an exception's conditions. Conversely, absence of an exception is not automatic proof of information blocking. Do not equate any anticipation of litigation with reasonable anticipation, or assume that a non-HIPAA actor's records fall outside EHI solely because of that actor's HIPAA status.
Information Blocking - ONC - Office of the National Coordinator for Health Information Technology · Certified Coding Associate (CCA) Exam Content Outline · Understanding Electronic Health Information (EHI) - ONC - Office of the National Coordinator for Health Information Technology
59.How should confidentiality follow records through their lifecycle?
Confidentiality extends from active use through storage, transfer, retention, and destruction. The CCA outline expressly includes encryption, secure transfer sites, secure work environments, appropriate retention, and appropriate destruction. Match controls to each stage: protect active screens and documents, use approved secure transmission, and apply the relevant retention schedule before authorized disposal. Electronic storage does not eliminate paper risks, and deleting a working copy is different from deciding that the official record may be destroyed.
Apply it
A coding worksheet containing patient identifiers is no longer needed locally. Confirm whether it is a temporary working copy or part of a required record, then use the approved confidential disposal process rather than ordinary trash.
Common pitfall: Finishing a coding task does not determine a record's retention period. Secure transmission also cannot compensate for an unauthorized recipient or an improperly exposed printed copy.
60.What makes health information de-identified under HIPAA?
HIPAA recognizes Expert Determination and Safe Harbor as methods for de-identification. Expert Determination uses a qualified expert's assessment that identification risk is very small under the specified conditions. Safe Harbor requires removal of the specified identifier categories and no actual knowledge that remaining information could identify an individual. Removing names alone is insufficient. Identifying information can appear in structured fields, narrative text, images, and other media, so the review must match the full information being released.
Apply it
An educator removes patient names from coding examples but leaves full dates, detailed addresses, and identifying narrative. Reassess the entire material against a recognized de-identification method before treating the examples as de-identified teaching data.
Common pitfall: Pseudonyms and removed names do not automatically satisfy HIPAA de-identification. Remaining dates, geography, free text, or other identifiers can still permit identification of the patient.
Guidance Regarding Methods for De-identification of Protected Health Information | HHS
What to focus on during revision
The following are CertMedbry study suggestions. Use the official outline to check the full scope of your examination.
- Begin each coding problem by identifying the reporting setting, claim perspective, and applicable code-set edition.
- Practise complete ICD-10-CM, ICD-10-PCS, and CPT assignments, including index or service-family selection, verification, and sequencing.
- Derive office/outpatient E/M levels from two of three MDM elements or qualifying physician/QHP time; distinguish the rules of other E/M families.
- Separate code validity, documentation support, coverage, edit resolution, grouping, and payment; each answers a different question.
- Use the official six-domain outline as the full scope, including HCC, record reports, terminology, software validation, and information blocking.
- Treat missing documentation, conflicting documentation, coding errors, and interface errors as different problems requiring different corrective actions.
- Apply United States Medicare and HIPAA rules only to the program and disclosure contexts described in each case.
A practical preparation plan
1. Establish the examination framework
Read the official outline and approved codebook list. Organize study time around the published domain ranges, and verify that your practice books match AHIMA's examination requirements.
2. Build a setting comparison sheet
Compare inpatient facility, outpatient facility, and professional reporting. Include procedure code sets, diagnosis certainty, principal versus first-listed diagnosis, and the relevant code-set date.
3. Explain each classification decision
Rework the completed diagnosis, inpatient procedure, and office E/M examples using the required 2026 references. Identify supporting documentation, classification path, applicable instructions, complete codes, and sequencing. Explain the precise error in each competing assignment.
4. Work claims from evidence to resolution
Practise distinguishing PTP edits, MUEs, coverage failures, linkage problems, and interface defects. Calculate simplified payment examples only with their stated assumptions.
5. Review records and compliance together
Classify deficiencies as missing documents, unclear content, unsupported codes, or chronology problems. Draft neutral clarification requests and preserve original documentation when reviewing amendments.
6. Practise complete decisions before moving on
Answer the drills without returning to earlier questions, then review every explanation. Track the governing rule behind each error and use flashcards to recall that distinction before attempting a fresh case.
Use your sample score as a starting point
The free set contains 20 original practice questions. It is a small learning sample, not an official examination or a validated pass prediction. Review each explanation and its source before moving to another topic.
Start the free sampleOfficial sources and updates
- Certified Coding Associate (CCA) | AHIMA
- Certified Coding Associate (CCA) Exam Content Outline
- CCA 2026 Exam Required Code Books
- ICD-10-CM Official Guidelines for Coding and Reporting, FY 2026
- ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027
- ICD-10-PCS Official Guidelines for Coding and Reporting, 2027
- ICD-10 | CMS
- Medicare NCCI 2026 Coding Policy Manual, Chapter 1
- Medicare NCCI FAQ Library | CMS
- Medicare Payment Systems | CMS
- Professional Paper Claim Form (CMS-1500) | CMS
- Medicare Claims During Public Health Emergencies | CMS
- Medicare Coverage Database | CMS
- Patient Identity and Patient Record Matching | ONC
- Medicare Program Integrity Manual, Chapter 3
- AHIMA Standards of Ethical Coding, 2016 Version
- Minimum Necessary Requirement | HHS
- Does the Security Rule Permit Shared User IDs? | HHS
- Report to Congress: Risk Adjustment in Medicare Advantage, December 2024
- Guidance Regarding Methods for De-identification of Protected Health Information | HHS
- Contact Information & Frequently Asked Questions | AHIMA
- mln006764-evaluation-management-services.pdf
- Information Blocking - ONC - Office of the National Coordinator for Health Information Technology
- 2026-official-icd-10-pcs-coding-guidelines.pdf
- ICD-10-CM/PCS MS-DRG v43.0 Definitions Manual
- ICD-10-CM/PCS MS-DRG v43.0 Definitions Manual
- clm104c23.pdf
- Understanding Electronic Health Information (EHI) - ONC - Office of the National Coordinator for Health Information Technology
- CPT® code 99214: Established patient office visit, 30-39 minutes | American Medical Association
- Medicare Dental Coverage | CMS
- 2023-e-m-descriptors-guidelines.pdf
Confirm current eligibility, fees, scheduling and policies directly with the examination provider. CertMedbry is independent and is not endorsed by these organisations. How we handle content and corrections.