8-14 Week Study Plan

Choose a Track

Match the length to your starting point:

• 8 weeks if you recently finished coding training, can study most days, and scored well on a diagnostic.
• 12-14 weeks if you are new to coding, returning after a break, or weak in anatomy, medical terminology, ICD, or CPT.

Whatever the length, keep a domain error log — a running list of missed items tagged by the six blueprint domains — so review targets your real gaps, not your comfort zones.

Weeks 1-2: Orientation and Baseline

Read the Candidate Guide, confirm eligibility, and verify the official AHIMA/Pearson facts (105 items, 2 hours, 300 to pass, in-person delivery). Obtain the 2026 required code books since current exams fall after 2026-05-01. Take a full diagnostic quiz, score it by domain, and start the error log.

Weeks 3-6: High-Weight Domains (CCS + Reimbursement)

Spend the largest block on Clinical Classification Systems (30-34%): abstract record facts, apply inpatient/outpatient/physician guidelines, assign ICD-10-CM/PCS and CPT/HCPCS codes, sequence the principal vs. secondary diagnosis by setting, apply modifiers, and determine Evaluation and Management (E/M) levels when tested.

Layer in Reimbursement Methodologies (21-25%): diagnosis-to-CPT linkage by payer rules, Diagnosis-Related Group (DRG) and Ambulatory Payment Classification (APC) basics, National Correct Coding Initiative (NCCI) edits, Local/National Coverage Determination (LCD/NCD) medical necessity, denial handling, Hierarchical Condition Category (HCC) awareness, and compliant physician queries.

Weeks 7-10: Records, Compliance, Technology, Privacy

• Health Records and Data Content (13-17%): record retrieval, quantitative/qualitative analysis, abstraction, the Master Patient Index (MPI), and required record components.
• Compliance (12-16%): documentation support for codes, ethical coding standards, the physician query process, chargemaster updates, provider education, and audit preparation.
• Information Technologies (6-10%): how coders use EHRs, encoders, groupers, practice-management systems, and Computer-Assisted Coding (CAC).
• Confidentiality and Privacy (6-10%): HIPAA and state rules, minimum-necessary access, secure passwords, breach/violation reporting, and safe work habits.

Final 2-4 Weeks: Simulate and Repair

Confirm your appointment is comfortably inside the 120-day window, and lock the test-day kit before the final week so nothing logistical can cost you the attempt.

Weekly Cadence That Actually Works

A plan only helps if it survives a busy week. Set a sustainable rhythm rather than heroic weekend marathons: aim for short daily blocks (45-60 minutes) of focused practice plus one longer weekend block for a timed set. Mixed retrieval beats rereading — answer questions, then study the explanations for the ones you missed, and re-test the same concept a few days later (spaced repetition). Studying the explanation for a correct guess is just as important as studying a miss, because a lucky guess is not yet a reliable point.

Turning the Error Log Into Score Gains

The error log is the engine of the whole plan. Tag every miss with its domain and a one-line reason — "didn't verify in Tabular," "missed Excludes1," "didn't recognize the NCCI edit," "thought a query was leading." Patterns emerge fast: most candidates discover a handful of recurring failure modes rather than 90 unrelated gaps. Attack the top three patterns first; fixing a single recurring mistake (for example, always verifying the principal-diagnosis sequencing rule) can recover several scattered points across the exam.

Avoiding the Two Most Common Plan Failures

The first failure is front-loading coding and starving the reasoning domains — candidates run out of weeks and walk in weak on reimbursement, compliance, and privacy, which together are nearly half the exam. The second is skipping full timed simulation — practicing untimed builds knowledge but not the endurance and pacing discipline a 2-hour, 105-item sitting demands. Schedule at least two complete timed simulations in the final stretch, treat the first as a dress rehearsal (correct books, real pacing, no pauses), and use the second to confirm your weak domains have actually moved.

A plan that ends with proven timed performance and a clean logistics check is what converts study hours into a scaled score at or above 300.

Sample Week-by-Week Skeleton (12-Week Track)

Use this as a starting template and bend it toward your diagnostic results:

• Weeks 1-2: orientation, official-fact verification, diagnostic, obtain 2026 books, start error log.
• Weeks 3-5: Clinical Classification Systems — ICD-10-CM index/tabular, ICD-10-PCS tables, CPT/HCPCS and E/M.
• Weeks 6-7: Reimbursement Methodologies — DRG/APC, NCCI edits, LCD/NCD, denials, HCC, queries.
• Week 8: Health Records and Data Content plus Compliance.
• Week 9: Information Technologies and Confidentiality and Privacy.
• Weeks 10-11: two full timed 105-item simulations with weak-domain repair between them.
• Week 12: light review, logistics lock-in, rest before exam day.

Compress the early weeks for the 8-week track or extend the foundation weeks for the 14-week track.

Integrating Practice With This Guide

The chapters that follow go deep on each domain, so treat this plan as the scaffolding that schedules them. As you finish a domain chapter, immediately do a timed question set on that domain and log the misses; do not let knowledge sit untested. Revisit the error log weekly and re-test the recurring failure modes rather than passively rereading explanations. By the time you reach the final simulations, your weak-domain list should be short and specific, and your code-book lookups should be fast and automatic — the combination that reliably clears the 300 scaled-score cut on the first, paid attempt.