Physician and Outpatient Coding Scenarios

Physician Versus Outpatient Facility Focus

Physician (professional) coding reports the provider's work: E/M, surgery, interpretation, or procedure performance, billed on the CMS-1500 claim. Outpatient facility coding also represents facility resources, supplies, drugs, and devices, billed on the UB-04 (CMS-1450). One visit can generate both a professional claim and a facility claim, each following its own rules. A key contrast: the inpatient principal-diagnosis rules do not apply to outpatient encounters.

Scenario Workflow

Read the encounter from start to finish, then code in order:

1. Identify the chief reason for the visit and the final assessment.
2. Code confirmed diagnoses (ICD-10-CM); select the first-listed diagnosis as the main reason for the visit.
3. Assign CPT/HCPCS for procedures, drugs, and supplies actually performed or given.
4. Append supported modifiers (25, 59, LT/RT, 26/TC).
5. Link each diagnosis to its procedure for medical-necessity support.

Outpatient Diagnosis Logic

Under ICD-10-CM Official Guidelines Section IV (outpatient), code only confirmed conditions documented for that encounter. Do not code conditions described as probable, suspected, questionable, rule out, or working diagnosis as if established; instead, code the signs, symptoms, or reason for the visit. Example: a note that states "rule out pneumonia, final assessment cough" is coded to the cough (R05.9), not pneumonia. Chronic conditions may be coded when they are actively treated or affect care.

APCs and the Outpatient Payment System

On the facility side, hospital outpatient services are reimbursed under the Outpatient Prospective Payment System (OPPS) using Ambulatory Payment Classifications (APCs). CPT/HCPCS codes are grouped into APCs that determine the facility payment, and multiple services on one claim can each map to an APC. Status indicators tell the coder how a code is treated: some are paid separately, some are packaged into another service, and some are conditionally packaged. This is distinct from physician payment, which uses the Resource-Based Relative Value Scale (RBRVS) and the Medicare Physician Fee Schedule.

Understanding which system a claim falls under tells the coder whether a supply or drug is separately payable.

A Combined Scenario

Consider a patient who comes to a hospital outpatient department for a screening colonoscopy that becomes therapeutic when a polyp is removed by snare. The physician claim reports the colonoscopy-with-polypectomy CPT code and, because the screening converted to a therapeutic service, modifier PT on Medicare claims. The facility claim reports the same procedure mapped to its APC plus any separately payable supplies. The diagnosis sequencing places the screening Z-code as the reason for the encounter with the polyp finding as an additional diagnosis. One encounter thus generates two claims, two coding logics, and careful diagnosis linkage.

Documentation Sources

The operative/procedure report drives CPT selection: laparoscopic versus open approach, anatomic site, extent (partial versus total), laterality, device used, and diagnostic versus therapeutic intent. Code what was actually performed, not the scheduled procedure if it changed. The medication administration record (MAR) supports drug HCPCS units; orders and test reports support diagnostic services; pathology and radiology reports confirm findings; and nursing notes may document supplies. The provider's documentation must still establish medical necessity for every reported code.

When two sources conflict, the operative report controls procedure coding and the attending physician's documentation controls diagnosis coding; if the conflict cannot be resolved from the record, the coder issues a compliant query rather than guessing.

First-Listed Diagnosis and Sequencing

Outpatient coding uses the term first-listed diagnosis rather than the inpatient "principal diagnosis," and it represents the main reason the patient sought care that day. ICD-10-CM Section IV adds specific rules: code a chronic condition as often as it is treated; code an encounter for diagnostic services alone using the confirmed diagnosis or, if not confirmed, the sign or symptom prompting the test; and for therapeutic encounters, sequence the condition being treated first. For ambulatory surgery, code the postoperative diagnosis if it differs from the preoperative one, since it is more definitive.

A common trap pairs a vague preoperative impression with a confirmed postoperative finding and rewards the candidate who sequences the postoperative diagnosis.

Professional Versus Facility Coding in Practice

The two coding worlds diverge in more than claim form. Professional coding emphasizes the level of physician work and clinical decision-making, captured through E/M leveling and procedure codes with RVUs. Facility coding captures resource consumption: room, supplies, drugs, devices, and technician time, often through a chargemaster that maps revenue codes and HCPCS to APCs. The same colonoscopy generates a physician fee tied to RBRVS and a facility payment tied to OPPS.

A CCA candidate must be able to read a single encounter and decide which codes belong on which claim, never assuming the physician's E/M absorbs the facility's separately reportable drug or device, and never letting the facility claim carry the professional interpretation of a test.

Reading the Whole Record Before Coding

The single most reliable habit in scenario coding is to read the entire record before assigning anything. A surgeon's scheduled procedure may have been abandoned or extended; an ordered test may have been cancelled; a drug ordered may not have been administered. Coding from the order or the schedule rather than the performed-service documentation is a frequent error the exam punishes. The progression is: confirm what was actually done, locate the supporting documentation for each service, then assign and sequence codes.

A discharge summary, an operative note, the MAR, and the pathology report may each contribute a piece, and the coder reconciles them into one accurate claim.

Putting the Workflow Together

Tie the pieces into a repeatable method for every scenario question. Determine the setting (physician office, hospital outpatient, ambulatory surgery) because it fixes the rule set. Identify the first-listed diagnosis as the main reason for the encounter, code additional conditions that affect care, and exclude uncertain diagnoses. Select CPT/HCPCS for each performed service and convert drug doses to units. Apply only supported modifiers and verify NCCI edits and global-period implications. Finally, point each service line to its justifying diagnosis.

Working this order keeps professional and facility logic separate while ensuring every code is documentation-driven, which is exactly the competency the CCA scenario questions are written to assess.