Context-switching is the core skill to build for the CCA. A single patient story codes differently for an inpatient stay, a hospital outpatient visit, and a physician office encounter: different code sets, different sequencing rules, different reimbursement buckets. Structure your preparation around that switching skill. For every practice case, first label the setting, then state which guidelines and payment method apply, and only then assign and sequence codes. This guide walks through the settings side by side, works through two exam-style decisions in detail, and ends with a drill, a rubric, and an adaptable study sequence.
One Record, Three Lenses: Inpatient, Outpatient, and Physician Coding
Domain 1 asks you to apply separate inpatient, outpatient, and physician coding guidelines. Determining which lens a case requires is a skill worth making explicit, because it drives both the code set you open and the sequencing rules you follow.
Inpatient coding pairs ICD-10-CM diagnoses with ICD-10-PCS procedures and is judged through the DRG methodology. Hospital outpatient coding uses ICD-10-CM diagnoses plus CPT procedures, evaluated through the APC methodology. Physician practice coding relies mainly on CPT services, including E/M levels, with linked ICD-10-CM diagnoses supporting medical necessity. The official guidelines for each setting are not interchangeable: sequencing conventions that apply on an inpatient claim do not automatically transfer to an outpatient or physician encounter.
Make the lens choice an explicit habit. Before reading a practice case, write down the setting; before answering, name the payment methodology attached to it. When you review rationale explanations, go back and ask what would change if the same patient had been seen in a different setting. That counterfactual habit trains the switching skill the domain outline describes, from interpreting healthcare data to sequencing codes according to the healthcare setting, and it prevents one setting's rules from bleeding into another.
| Setting | Diagnosis coding | Services and procedures | Reimbursement lens |
|---|---|---|---|
| Inpatient hospital | ICD-10-CM, principal diagnosis drives sequencing | ICD-10-PCS procedures | MS-DRG methodology |
| Hospital outpatient | ICD-10-CM, first-listed diagnosis supports medical necessity | CPT procedures and services | APC methodology, NCCI edits |
| Physician practice | ICD-10-CM linked to each service | CPT including E/M levels and modifiers | Payer-specific linkage, LCD/NCD medical necessity |
E/M Levels: When Time Is on the Chart and When It Is Not
The content outline requires determining an E/M level by medical decision making or by time. The distinction turns on what the documentation actually records, and practice cases exploit exactly that gap.
Worked scenario: an established patient returns for follow-up on hypertension and type 2 diabetes. The scheduler's note shows a 30-minute appointment block, but the encounter note itself never states total time on the date of the service. The note documents two stable chronic conditions, review of a recent lab panel, and prescription drug management. A plausible mistake is selecting an E/M level based on the 30-minute appointment length. The appointment block is scheduling information, not documented total time, so it cannot support a time-based level.
The better decision is to determine the level through medical decision making: two stable chronic conditions addressed, review of external notes or tests, and prescription drug management together characterize a low-to-moderate level of decision making depending on the exact elements documented. Time-based selection requires that total time on the date of the encounter be recorded in the note. Why it matters: the compliant-coding habit this decision trains is reading the documentation as written rather than importing information from outside the record, which is exactly the discipline ethical code assignment demands on the job.
Sequencing for the Right Payment Bucket: DRG and APC Logic
Domain 2 ties sequencing to reimbursement. Inpatient sequencing follows the principal diagnosis definition; outpatient sequencing supports medical necessity and must survive NCCI edits. Practice both payment buckets deliberately on the same case.
Worked scenario: a patient is admitted through the emergency department with shortness of breath and lower-extremity edema. After imaging, labs, and cardiology consultation, the discharge documentation establishes acutely decompensated heart failure as the reason for admission, with the symptom resolved during the stay. A plausible mistake is sequencing the symptom as the principal diagnosis because it appeared first in the record. The principal diagnosis is the condition established after study to be chiefly responsible for occasioning the admission, not the first diagnosis mentioned.
The better decision is to sequence the confirmed heart failure as principal, which drives the MS-DRG assignment, and report the symptom as an additional diagnosis only if it meets reporting criteria for secondary diagnoses. Contrast the outpatient lens: on a hospital outpatient claim there is no principal diagnosis in the same sense; the first-listed diagnosis must support medical necessity, often checked against LCD and NCD policies, and procedure pairs that trip NCCI edits must be resolved with modifiers only when the documentation independently supports them. Practicing the same story through both buckets makes the divergence concrete.
Abstraction and Querying: What the Record Supports Versus What It Suggests
Domain 3 covers abstracting pertinent information and analyzing records for completeness and deficiencies; Domain 4 covers validating codes against documentation and performing ethical physician queries. Together they define the evidence standard for every code you assign.
Treat abstraction as a targeted search, not a full read. For a case, decide in advance what you need: the reason for the encounter, conditions managed, procedures performed, and discharge or disposition details. Quantitative analysis asks whether required elements are present; qualitative analysis asks whether the content is internally consistent. When computer-assisted coding software suggests codes, the outline is explicit that you validate them against the documentation, so practice treating auto-suggested codes as candidates to verify rather than answers to accept.
The query process is the compliance counterpart. When coded data conflict with the documentation, or the documentation supports more than one interpretation, an ethical physician query is the mechanism to clarify it. Practice writing queries that are non-leading: they present the facts in the record and the available options without suggesting a preferred answer. The habit this builds is refusing to code from an assumption, an index entry alone, or a habit from a previous similar case, which is precisely the discrepancy-identification work listed in the compliance domain.
Privacy Decisions Inside Everyday Coding Work
Domain 6 covers confidentiality in operational terms: accessing only the minimum necessary information, releasing records to authorized recipients, recognizing violations, and handling PHI securely in electronic workflows.
Ground your study in the minimum necessary principle: a coder retrieves the records needed for the assignment at hand, not the entire patient history out of curiosity or convenience. Release decisions turn on authorization: patient-specific data goes to individuals verified as authorized to receive it, and the outline adds newer operational concepts such as information blocking and secure electronic transfer of documents. Recognizing a privacy issue is a task in itself, so practice noticing scenarios where a colleague's access pattern or an unsecured attachment crosses a line.
Link this domain to your own study workflow. If you use shared or cloud storage for practice notes, keep any sample scenarios fully de-identified rather than working from real records, which is both a compliance habit and a realistic simulation of the secure handling the domain describes. When you evaluate exam-style privacy items, read the operational cues in the stem deliberately: identify who is requesting the data and for what stated purpose, then judge the described access against the minimum necessary and authorization requirements those details invoke.
A Two-Pass Drill with a Self-Check Rubric
Use a two-pass structure on every practice case: pass one assigns codes, pass two audits the setting, sequence, and reimbursement logic. The rubric below gives observable checkpoints and learning milestones, not score predictions.
Set up the drill: take one coded case from any practice set. Pass one, timed, assign and sequence codes as you would on exam day, remembering that the live exam does not let you flag items or return to them, so first-pass discipline matters. Pass two, untimed, audit your own work: confirm the setting lens, recheck the sequencing decision against the setting's rules, name the payment methodology, and verify each code against the documentation rather than your memory of the case. Expect two observations as you repeat this: your pass-one answers start converging with your pass-two audits, and the time you need for pass two shrinks as the checking becomes automatic.
Self-check rubric, one point each out of five: (1) correctly identified the setting before coding; (2) used the code set appropriate to that setting; (3) sequencing follows the setting's rules, including principal or first-listed diagnosis logic; (4) named the correct reimbursement methodology and any edits or medical-necessity checks involved; (5) every code is traceable to a specific documentation statement. Treat a steady four or five as a learning milestone indicating the case type is in good shape; a score of two or fewer flags that case type for focused review.
An Adaptable Preparation Sequence and Readiness Checks
Structure preparation in four stages: foundation review, lens-switching drills, domain-weighted practice, and timed simulation. Adjust durations to your background, and check readiness against observable behaviors rather than feelings.
A workable sequence: weeks one and two, rebuild foundations across anatomy and physiology, terminology, and the layout of each codebook, including the guideline chapters, since you will bring and use codebooks on exam day. Weeks three and four, run lens-switching drills: code the same story three ways, inpatient, outpatient, and physician, and write down what changed. Weeks five and six, work practice questions organized by the six domains, weighting your time toward the largest domains, clinical classification systems and reimbursement methodologies, while still covering records, compliance, technology, and privacy. Weeks seven and eight, take timed practice exams under the constraint of no returns, then audit every miss with the two-pass method.
A short note on logistics: codebook editions, scheduling, fees, and eligibility are administrative details governed by AHIMA, and they change; confirm current requirements on the official CCA page linked below rather than relying on any article, including this one. Readiness checks before exam day: you can label a case's setting within seconds; you can state the principal versus first-listed diagnosis distinction without prompting; you can write a non-leading query from a conflicting note; you can determine an E/M level and explain which route, decision making or documented time, you used and why; and your rubric scores on mixed cases sit consistently at your target milestone.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.