Objective. Students will code complete physician-office and outpatient encounters from start to finish, assigning ICD-10-CM diagnosis codes alongside CPT and HCPCS procedure codes to produce a coded encounter record ready for claim generation.
This lesson, its worked examples and its practice questions has not yet been verified by a licensed clinician in the field or by a certification or approval body. It is a study draft and may contain errors. Do not use it to make decisions about any patient or medication. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
In a real coding department, you rarely code a single element in isolation. You receive a complete encounter record — the physician's note, any orders, lab or radiology results, and a charge sheet — and you must assign every code the claim requires before it leaves the office. That means selecting ICD-10-CM diagnosis codes, CPT procedure codes, HCPCS Level II codes where needed, and any modifiers, then checking that the entire set is internally consistent and supported by documentation. This lesson pulls together everything you have learned and asks you to work through complete records the way a professional coder does every day.
Working through an encounter in a consistent order prevents omissions and errors.
Step 1 — Read the entire record first. Skim the chief complaint, history, exam findings, assessment, and plan before you assign a single code. Coders who jump to the assessment section and start coding often miss secondary diagnoses or misunderstand the clinical picture.
Step 2 — Identify the principal or first-listed diagnosis. For physician office and outpatient settings, ICD-10-CM outpatient guidelines direct you to code the condition established by the end of the encounter. If the diagnosis is still uncertain, code the sign or symptom — not the unconfirmed condition.
Step 3 — Identify additional diagnoses. Code any co-existing condition that was evaluated, treated, or that affected management during the visit. Do not code diagnoses that are mentioned only in passing and had no bearing on the encounter.
Step 4 — Select procedure codes. Assign the CPT code that most accurately describes what the physician performed, supported by the documentation. If the service was a drug administration, a supply, or a service not covered by CPT, check HCPCS Level II.
Step 5 — Apply modifiers. Ask: Was the service bilateral? Performed by a different provider than usual? Only part of a global surgical period? Modifiers communicate these facts to the payer. Common office and outpatient modifiers include -25 (significant, separately identifiable E/M on the same day as a procedure), -57 (decision for surgery), -59 (distinct procedural service), and -76/-77 (repeat procedure).
Step 6 — Check for bundling issues. Certain code pairs cannot be billed together because one service is considered part of another. Encoder software flags many of these, but you must understand the underlying rule to decide whether an override is appropriate.
Step 7 — Verify units. Some services are reported in time units or by quantity. Make sure units match what the documentation supports.
The ICD-10-CM Official Guidelines for Coding and Reporting include a dedicated outpatient section. Key points include: code to the highest degree of certainty available at the end of the encounter; use V/Z codes (Z-codes) for screenings, vaccinations, and status conditions when they affect care; and sequence the reason for the visit first unless guidelines specify otherwise.
For E/M codes, the documented level of medical decision-making (MDM) or total provider time on the date of the encounter determines the correct code level. Under current CPT guidelines, MDM is assessed by the number and complexity of problems, the amount and complexity of data reviewed, and the risk of complications or morbidity.
Encoders are powerful tools, but they are not decision-makers — you are. Software can suggest codes, flag edits, and check payer rules, but it cannot read the clinical record the way a trained coder can. When an encoder presents an alert, read it, evaluate whether it applies to your specific documentation, and document your rationale if you override it. Overriding without a defensible reason creates compliance risk.
Auditing your own work is a professional habit; auditing a colleague's work is a foundational compliance skill. When you audit, check four things: (1) Is every code supported by documentation? (2) Is the code itself correct — right category, right specificity? (3) Is the modifier accurate and necessary? (4) Are any codes improperly bundled or unbundled? Document every finding in writing. Disagreements are resolved by returning to the source: the codebook guidelines and the clinical record.
Coding directly affects patient safety. An incorrect diagnosis code on a claim can follow a patient into their insurance record and influence future coverage decisions or clinical care. Upcoding (billing a higher-intensity service than documented) is fraud. Downcoding wastes revenue and may signal to payers that care was not delivered as ordered. If you are uncertain whether a procedure was performed or a diagnosis was confirmed, query the provider — do not guess or assume. Never alter documentation to make it fit a code you want to use. These principles are not just ethical: they are legal requirements under federal healthcare fraud and abuse statutes.
Each encounter record in today's lab is a realistic simulation of what you will handle on the job. Work methodically, use your codebooks and encoder as tools rather than shortcuts, and treat every code line as if a real patient's record and a real claim depend on it — because in your career, they will.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.