CPT Codes — Portfolio Projects
Build a body of coded work you can walk an interviewer or hiring coding manager through — accuracy, reasoning, and how you resolved ambiguous documentation matter more than volume.
Project 1: E/M Level-Selection Practice Set
Level: Beginner | Time: 2 days
Code 15-20 realistic outpatient encounter notes to the correct Evaluation & Management level, choosing consistently between the medical-decision-making (MDM) pathway and time-based selection for each note. Write a one-line justification per code explaining which pathway you used and why.
Steps
Skills Demonstrated
Note
E/M guideline specifics have been revised in recent years (most significantly the 2021 office/outpatient E/M overhaul) and continue to be refined — verify current E/M guideline details against current CMS/AMA CPT guidance before treating any specific level-selection rule as settled.
---
Project 2: Surgical Coding with Modifiers
Level: Intermediate | Time: 3-4 days
Code a set of operative reports and correctly apply modifiers (e.g., -25, -51, -59, RT/LT) while identifying which procedures fall inside another procedure's global surgical period.
Steps
Skills Demonstrated
Note
Verify current NCCI (National Correct Coding Initiative) edits and modifier-specific rules against current CMS/AAPC guidance — bundling edits and modifier requirements are updated regularly and a stale rule can silently produce an incorrect claim.
---
Project 3: Full CPT Audit Portfolio
Level: Advanced | Time: 1 week
A comprehensive coding audit spanning E/M, surgery, and at least one other CPT section (radiology or pathology/lab) — the centerpiece project for a CPC-track portfolio.
Steps
Skills Demonstrated
Portfolio Artifact Name
cpt-audit-portfolio
---
Tips for Great Projects
Use real-looking documentation, not invented codes. Coding backward from a code you already know defeats the point — work from a clinical note and derive the code, the way you will on the job.
Document your reasoning, not just the answer. In interviews and on the job, you'll be asked "why this code and not that one" — practice writing that justification down every time.
Flag genuine ambiguity instead of guessing. A note that's honestly unclear should be marked "needs physician query" — that's correct coder behavior, and worth demonstrating.
Track your own accuracy over time. Keep a running log of self-audit corrections; a visible accuracy trend is a stronger portfolio signal than any single project.