Coding Medical Encounters

Coding Medical Encounters

Assigns ICD-10-CM diagnosis codes and CPT/HCPCS procedure codes to clinical encounters. Validates documentation sufficiency and ensures sequencing compliance.

Related Skills

Why This Skill Exists

Every code assigned to a medical encounter has downstream impact:

• Revenue — incorrect codes cause denials, underpayment, or overpayment
• Compliance — upcoding and unbundling trigger OIG audits and False Claims Act liability
• Data quality — HCC risk adjustment, quality measures, and population health analytics depend on accurate coding
• Legal defensibility — "if it's not documented, it didn't happen" is the foundational coding principle

This skill enforces a structured, documentation-driven coding workflow that reduces error rates and produces auditable output.

Checkpoint A: Pre-Draft Intake (Mandatory)

Before assigning any code, confirm all inputs. Present this table and fill with user-supplied or document-derived answers:

Stop conditions — Do NOT proceed if:

• Clinical documentation is incomplete or unsigned
• Encounter type is ambiguous and cannot be inferred
• No provider attestation exists for the services rendered

Flag missing items with [QUERY PROVIDER] and escalate to the CDI workflow (managing-cdi-programs).

Step 1: Assign Diagnosis Codes (ICD-10-CM)

Sequencing Rules

1. Principal/primary diagnosis — the condition established after study to be chiefly responsible for the encounter
2. Secondary diagnoses — conditions that affect treatment, require monitoring, or increase complexity
3. Chronic conditions — code only if addressed, treated, or affecting management during this encounter
4. External cause codes (V00-Y99) — required for injuries; never principal
5. Z-codes — for encounters driven by factors other than disease (screening, history, status)

Specificity Requirements

Always code to the highest level of specificity the documentation supports:

• Laterality (right, left, bilateral) when the code set requires it
• Episode of care (initial, subsequent, sequela) for injury codes
• Trimester for obstetric codes
• Type 1 vs Type 2 for diabetes with manifestations

Common specificity failures:

• Using unspecified site when laterality is documented
• Defaulting to .9 (unspecified) when a more specific code exists
• Missing 7th character extensions on injury/fracture codes

Output: Diagnosis Code Table

Mark any code where documentation is insufficient as [QUERY PROVIDER] with the specific deficiency noted.

Step 2: Assign Procedure/Service Codes (CPT / HCPCS)

E/M Code Selection (2021+ Guidelines)

For evaluation and management services, determine the level using Medical Decision Making (MDM):

Level requires 2 of 3 elements to meet or exceed the threshold.

For the full MDM grid with examples, load references/CODING-REFERENCE.md.

Non-E/M Procedure Codes

For procedures, surgeries, and ancillary services:

1. Identify the procedure performed from the operative/procedure note
2. Match to the most specific CPT or HCPCS Level II code
3. Check NCCI edits for bundling conflicts with other codes on the same DOS
4. Apply modifiers as needed (see Modifier section below)
5. Verify units if applicable (e.g., infusion time, lesion count)

Modifier Application

Apply modifiers only when documentation supports them:

Output: Procedure Code Table

Step 3: Validate Code-to-Documentation Linkage

Every code must trace back to a specific documentation element. Complete this validation:

- [ ] Each diagnosis code supported by documented clinical finding, test result, or provider assessment
- [ ] Each procedure code supported by procedure note, operative report, or provider documentation
- [ ] E/M level supported by at least 2 of 3 MDM elements at or above the billed level
- [ ] Modifiers supported by documentation of distinct service, laterality, or separate encounter
- [ ] Sequencing follows principal diagnosis rules for the encounter type
- [ ] No unspecified codes when specific information is available in the documentation
- [ ] HCC-relevant diagnoses captured if payer is Medicare Advantage

Checkpoint B: Post-Draft Alignment (Mandatory)

Present the complete coded encounter to the user before finalizing:

Coded Encounter Summary

Encounter: [type] | DOS: [date] | Provider: [name] | Payer: [payer]

Diagnosis Codes: (Diagnosis Code Table from Step 1)

Procedure Codes: (Procedure Code Table from Step 2)

Flags:

• Queries pending: [count] — list each [QUERY PROVIDER] item
• NCCI conflicts: [count] — list each with resolution
• Specificity gaps: [count] — list codes that could be more specific

Ask: "Does this coded encounter accurately reflect the services documented? Should any codes be added, removed, or changed?"

Do NOT finalize until the user confirms.

Quality Audit

Run these checks on every coded encounter before delivery:

If any check fails: flag the specific code, cite the deficiency, and recommend corrective action before finalizing.

Reference Files