Work through the ten groups in order, because later application assumes earlier conventions. Each concept pairs a rule with a short resolved example and a common error, so read the explanation, predict the example's decision before finishing it, and note the mistake as a self-check. Use the group headings to locate weak areas, then revisit the underlying reference material for official wording. These are teaching concepts for review, not an official syllabus or a substitute for current code books and guidelines.
The Business of Medicine and the Coder's Role
1. What Medical Coding Actually Is
Coding means translating provider documentation into standardized diagnosis and procedure codes; it is not claim form completion, EHR programming, or electronic file creation. The coder's input is the medical record, and the output is code assignment that payers use for reimbursement and data.
Example: A note describes a laceration repair; the coder assigns the repair code rather than preparing the electronic claim transmission. Decision: coding is translation of documentation, not claims formatting.
Mistake to avoid: Defining coding as reporting services on a claim form; that is billing work, not code assignment.
Reference: AAPC CPC study guide sample
2. Provider Hierarchy and Who Establishes Diagnoses
Physicians and other qualified health practitioners who are legally accountable for establishing diagnoses drive diagnosis coding; clinical staff document supporting data. Distinguish physician or QHP diagnostic statements from nursing or technician notes, which generally cannot establish a diagnosis.
Example: A nurse documents a pressure ulcer stage, but the provider must document the ulcer diagnosis itself. Decision: take the stage from the nurse, the diagnosis from the provider.
Mistake to avoid: Assigning a diagnosis based only on a nurse's or technician's note when the provider never stated the condition.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
3. Commercial Payers versus Federal Payers
Commercial payers are private insurers such as Blue Cross Blue Shield; federal programs include Medicare and Medicaid. This classification matters because coding edits, coverage rules, and code sets like HCPCS Level II G codes apply differently depending on whether the payer is commercial or government sponsored.
Example: A claim goes to Blue Cross Blue Shield. Decision: commercial payer, so Medicare-specific G code policy does not automatically govern the claim.
Mistake to avoid: Treating Medicare or Medicaid as commercial payers when classifying coverage rules.
Reference: AAPC CPC study guide sample
4. Medicare Part Distinctions for Services and Drugs
Medicare parts divide responsibility: Part A covers inpatient hospital care, Part B covers physician and outpatient services, Part C bundles benefits through private Medicare Advantage plans, and Part D covers prescription drugs supplied through approved private plans. Match the service or drug to the correct part before billing.
Example: A pharmacy fills a pain prescription for a chemotherapy patient to take home. Decision: bill Part D, because take-home drugs fall under the prescription drug program.
Mistake to avoid: Billing a take-home prescription under Part B just because it was delivered during an office visit.
Reference: AAPC CPC study guide sample
5. Medicaid and State Child Health Programs
Medicaid is federal-state assistance for certain low-income people, administered state by state under federal guidelines; separate state programs cover children with disabilities or special healthcare needs up to age 21. Recognize these as distinct payer types with their own eligibility and billing pathways.
Example: A child with a special healthcare need receives therapy. Decision: check the state children's program rather than assuming standard commercial coverage applies.
Mistake to avoid: Assuming Medicaid rules are identical across states or conflating Medicaid with child disability programs.
Reference: AAPC CPC study guide sample
6. RBRVS Components Behind Physician Payment
Medicare physician payment uses a resource-based relative value scale with three components: physician work, practice expense, and professional liability insurance. Physician work reflects time, skill, effort, judgment, and risk; practice expense varies by site of service, which is why facility and non-facility totals differ.
Example: A fee schedule row shows separate facility and non-facility totals for one visit code. Decision: use the column matching the actual place of service.
Mistake to avoid: Applying the non-facility payment amount to a service performed in a hospital setting.
Reference: AAPC CPC study guide sample
Medical Terminology and Anatomy Foundations
7. Building Terms from Word Parts
Medical terms combine word roots, combining forms, prefixes, and suffixes; decoding the parts yields approximate meaning. Cardi means heart, my means muscle, and pathy means disease, so cardiomyopathy is diseased heart muscle. Use this decomposition to map unfamiliar terms to correct index entries.
Example: A note says hepatomegaly. Break it into liver plus enlargement, then look under the liver-related main term. Decision: decode before searching.
Mistake to avoid: Searching the index for a term you have not decomposed, missing the correct main term.
Reference: AAPC CPC study guide sample
8. Plural Endings That Change Lookup Terms
Singular-to-plural transformations follow set patterns: a becomes ae, is becomes es, um becomes a, us becomes i, nx becomes ges, and ex becomes ices. Notes may use the plural while the index lists the singular, so convert forms before searching.
Example: The note says phalanges; the index lists phalanx. Convert to singular to find the injury entry. Decision: normalize the term before lookup.
Mistake to avoid: Failing to convert plurals like thrombi to thrombus, causing missed index entries.
Reference: AAPC CPC study guide sample
9. Anatomic Position and Directional Language
The anatomic position is upright, face forward, arms at the sides, palms forward, feet parallel. Directional terms and planes are defined relative to this standard, so laterality and site language in notes must be interpreted against it when assigning site-specific codes.
Example: A note describes a wound on the lateral forearm. Interpret lateral relative to anatomic position. Decision: choose the site code matching that side and region.
Mistake to avoid: Interpreting right, left, medial, or lateral from the viewer's perspective instead of the patient's anatomic position.
Reference: AAPC CPC study guide sample
10. Skin Layers and What Counts as Skin
The epidermis is outermost with squamous, basal, and melanocyte cells; the dermis beneath has papillary and reticular layers with vessels, nerves, and glands. Subcutaneous fat is below the dermis and is not a skin layer, a distinction that drives depth-based procedure selection.
Example: A lesion removal note describes excision into subcutaneous tissue. Decision: recognize the depth extends beyond the true skin layers when reading the procedure.
Mistake to avoid: Treating subcutaneous tissue as a third skin layer when reading depth descriptions.
Reference: AAPC CPC study guide sample
11. Body System Vocabulary as a Navigation Tool
Each body system chapter pairs anatomy with terminology: respiratory alveoli and bronchi, digestive organs, urinary structures, endocrine glands, and hemic and immune cells. Knowing system vocabulary tells you which chapter of the diagnosis book and which CPT section a case belongs in.
Example: A note mentions alveoli and bronchioles. Decision: route diagnosis lookup to the respiratory chapter rather than a generic symptom code.
Mistake to avoid: Hunting through unrelated chapters because the note's system vocabulary was not recognized.
Reference: AAPC CPC study guide sample
12. Eponyms and Acronyms in Documentation
Providers document many conditions and procedures by eponym or acronym. The Alphabetic Index usually lists the expanded clinical term rather than the shorthand, so translate eponyms into their indexed disease names before assigning codes. Recognizing common eponyms per body area is a stated learning objective.
Example: A note names a fracture by the surgeon's eponym. Decision: convert to the indexed fracture description, then verify laterality and site in the Tabular List.
Mistake to avoid: Assuming an eponym has no index entry and defaulting to an unspecified code.
Reference: AAPC CPC study guide sample
ICD-10-CM Structure and Conventions
13. Two-Step Lookup: Index First, Tabular Second
Locate the documented term in the Alphabetic Index to find a candidate code, then verify it in the Tabular List, reading all instructional notes. A code found in the index is not final until the tabular entry, including excludes and use-additional notes, confirms it.
Example: The index points to a varicose vein entry; tabular verification confirms the laterality character. Decision: report only the fully verified code, never the index draft.
Mistake to avoid: Submitting a code straight from the Alphabetic Index without tabular verification and its notes.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
14. Placeholder X in Short Codes Requiring a 7th Character
Some categories require a seventh character for every code within them. When the underlying code has fewer than six characters, placeholder X fills the empty positions so the extension lands in the seventh position. Without the X, the code is invalid for reporting.
Example: A five-character injury code needs an initial encounter extension. Decision: insert one placeholder X, then append the seventh character so the extension sits in position seven.
Mistake to avoid: Appending the seventh character directly to a short code without placeholder X.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
15. NEC versus NOS in the Two Books
NEC, not elsewhere classifiable, points to an other specified code used when the provider documented detail the classification lacks a code for. NOS, not otherwise specified, equals unspecified and is used only when documentation lacks the detail a more specific code requires.
Example: The provider names a rare, clearly specified lesion with no dedicated code. Decision: assign the other specified code, because the detail exists but the classification lacks it.
Mistake to avoid: Using NOS when the provider actually documented specificity that belongs in an other specified code.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
16. Excludes1 versus Excludes2 Notes
Excludes1 means the excluded code can never be reported with the code above the note, typically because the conditions cannot coexist, such as congenital versus acquired forms. Excludes2 means the excluded condition is not part of the code but both may be reported together when documented.
Example: A code carries an Excludes2 for a comorbid condition the patient also has. Decision: report both codes together, because Excludes2 only excludes it from the code's content.
Mistake to avoid: Dropping a documented condition because an Excludes2 note was misread as a mutual exclusion.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
17. Brackets and Parentheses as Conventions
In the Tabular List, brackets enclose synonyms or alternate wording; in the Alphabetic Index, brackets mark required additional manifestation codes sequenced after the etiology. Parentheses enclose nonessential modifiers whose presence or absence does not change the code assignment.
Example: The index shows a bracketed second code after an etiology entry. Decision: report both codes with the etiology sequenced first, because brackets signal a required pair.
Mistake to avoid: Ignoring bracketed index codes and reporting only the first-listed etiology code.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
18. Code Structure and Character Meaning
Categories are three characters, with a letter first; subcategories add characters; only full codes are reportable. The fourth character often defines site, etiology, or manifestation, and fifth and sixth characters add specificity. A three-character category without subdivision is itself the code.
Example: A subcategory without further subdivision is the valid code. Decision: report the complete character string the tabular requires, never a category alone.
Mistake to avoid: Reporting a three-character category or subcategory when a fuller code exists.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
General Diagnosis Coding Guidelines
19. Etiology and Manifestation Sequencing
When one underlying condition produces manifestations, the etiology is sequenced first and the manifestation follows. Use additional code notes appear at the etiology; code first notes appear at the manifestation. Codes titled in diseases classified elsewhere may never be principal or first-listed.
Example: Dementia due to Parkinson's disease is documented. Decision: sequence the Parkinson's etiology code first, then the bracketed dementia code, never the reverse order.
Mistake to avoid: Listing a manifestation in diseases classified elsewhere as the first-listed diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
20. The With Presumption Linking Conditions
The word with or in between two conditions in a title, index entry, or note means associated with or due to, and the classification presumes a causal link even without explicit provider documentation, unless the record clearly states the conditions are unrelated or a specific guideline requires documented linkage.
Example: An index entry links diabetes with a renal condition using with. Decision: code them as related unless the record clearly states they are unrelated.
Mistake to avoid: Splitting with-linked conditions into unrelated codes without documentation explicitly separating them.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
21. Acute and Chronic Forms of One Condition
When the same condition is documented as both acute or subacute and chronic, and separate index subentries exist at the same indentation, assign both codes and sequence the acute code first. If a single combination code captures both, use it instead.
Example: A note documents acute on chronic respiratory illness with separate index subentries. Decision: report both codes, sequencing the acute one before the chronic one.
Mistake to avoid: Sequencing the chronic code first or collapsing both into one code when separate entries exist.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
22. Combination Codes versus Multiple Coding
A combination code captures two diagnoses, a diagnosis with a secondary process, or a diagnosis with a complication in one code. When a combination code fully identifies the conditions, assign only it; multiple coding is inappropriate where the classification already provides the combination.
Example: A single code covers a condition and its common complication, both documented. Decision: report the combination code alone rather than two separate codes.
Mistake to avoid: Splitting a documented diagnosis and its complication into two codes when one combination code exists.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
23. Laterality and Data from Other Clinicians
Laterality may be taken from other clinicians' documentation when the provider did not record the side, but conflicting documentation requires querying the provider. Unspecified side codes should be rare, used only when the record is insufficient and clarification is unobtainable.
Example: The provider omits the affected side, but a therapist's note in the record clearly identifies left. Decision: assign the left-sided code based on that documentation.
Mistake to avoid: Defaulting to an unspecified side code when laterality exists elsewhere in the record.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. Borderline Diagnoses Are Confirmed
A provider-documented borderline diagnosis is coded as confirmed unless the classification has a specific borderline entry, such as borderline diabetes. This rule applies regardless of setting, unlike uncertain diagnoses, and unclear documentation warrants a provider query.
Example: Documentation states a borderline condition with no specific index entry for it. Decision: code the condition as confirmed, not as uncertain or ruled out.
Mistake to avoid: Treating borderline documentation like an uncertain diagnosis and omitting the code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Outpatient Reporting and Diagnostic Uncertainty
25. First-Listed versus Principal Diagnosis
Outpatient and physician settings select a first-listed diagnosis; inpatient non-outpatient settings select a principal diagnosis under separate guideline sections. The coder must know which section governs the encounter because sequencing rules differ between the settings.
Example: A clinic encounter addresses a chronic illness plus a new symptom. Decision: apply the outpatient first-listed rules rather than inpatient principal diagnosis selection.
Mistake to avoid: Applying inpatient principal-diagnosis selection logic to a physician office encounter's first-listed code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
26. Uncertain Diagnoses Differ by Setting
In outpatient coding, do not code diagnoses documented as probable, suspected, rule out, or working diagnosis as if established; instead code the signs or symptoms that prompted the encounter. Inpatient rules treat uncertain diagnoses at discharge differently, so identify the setting first.
Example: An office note lists suspected pneumonia while cultures are pending. Decision: report the documented symptoms, such as cough and fever, rather than the unconfirmed pneumonia.
Mistake to avoid: Coding a suspected outpatient diagnosis as confirmed before the encounter ends.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
27. When Unspecified and Symptom Codes Are Correct
Specific codes should be reported when supported, but sign, symptom, and unspecified codes are appropriate when no definitive diagnosis exists by encounter end or when clinical detail is genuinely unknown. Never select specificity unsupported by the record or order unnecessary testing to obtain it.
Example: Pneumonia is diagnosed, but the type is never documented. Decision: report the unspecified pneumonia code, because it most accurately reflects what is known.
Mistake to avoid: Assigning a specific bacterial type code with no documentation supporting the organism.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Chronic and Coexisting Conditions in Outpatient Visits
For outpatient encounters, code all documented conditions that coexist and are managed or affect care during the visit, including chronic diseases under active management. Historical conditions no longer present are not coded as current; personal history codes apply instead.
Example: Diabetes and hypertension are both managed at the visit. Decision: report both as current coexisting diagnoses, each coded to its documented specificity.
Mistake to avoid: Omitting a managed chronic condition because it is not the visit's chief complaint.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Screening Encounters and Z Codes
Z codes report encounters for circumstances other than disease or injury, including routine health screenings and general examinations. They may serve as the reason for the encounter or supplement other codes, and they apply in any healthcare setting.
Example: A patient with no symptoms presents for a routine screening. Decision: assign the screening Z code as the first-listed reason for the encounter.
Mistake to avoid: Inventing a symptom code to justify a screening encounter that has no documented symptoms.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Provider Statement Over Clinical Criteria
Code assignment rests on the provider's diagnostic statement that a condition exists, not on the clinical criteria the provider used to reach it. If record documentation conflicts, query the provider rather than independently judging which diagnosis the evidence supports.
Example: The provider diagnoses a condition despite atypical findings. Decision: code the stated diagnosis, because the coder does not re-weigh the clinical evidence behind it.
Mistake to avoid: Overriding a provider's stated diagnosis because the coder reads the clinical criteria differently.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
CPT, HCPCS Level II, and Modifiers
31. Choosing CPT versus HCPCS Level II
CPT reports physician and outpatient services; HCPCS Level II covers supplies, products, and services CPT does not, including Medicare-specific G codes. When a Medicare patient receives a service with a dedicated G code, such as high-risk screening colonoscopy, the G code replaces the CPT equivalent.
Example: A Medicare patient undergoes high-risk screening colonoscopy. Decision: report the HCPCS Level II G code, because payer policy requires it for this Medicare service.
Mistake to avoid: Reporting a CPT code for a Medicare service that has a dedicated HCPCS Level II G code.
Reference: AAPC CPC study guide sample
32. NCCI Edits and Bundling Awareness
The National Correct Coding Initiative publishes edits that identify code pairs that cannot be reported together, supporting proper bundling decisions. Coders must check edits before finalizing code sets, because NCCI policy operates alongside CPT guidelines rather than replacing them.
Example: Two procedure codes describe services usually performed together during one session. Decision: consult the NCCI edit before reporting both codes on a single claim.
Mistake to avoid: Reporting code pairs together without checking whether an NCCI edit prohibits the combination.
Reference: AAPC CPC study guide sample
33. Sequencing Procedure Codes on a Claim
CPT codes follow sequencing conventions distinct from diagnosis sequencing; the study guide treats procedure code order as its own skill. Sequence procedures according to the conventions for the claim type and section rules rather than by code number or convenience.
Example: Multiple procedures from different CPT sections appear in one note. Decision: order them according to the applicable sequencing conventions, not by ascending code number.
Mistake to avoid: Listing procedure codes in numeric order and assuming that satisfies sequencing rules.
Reference: AAPC CPC study guide sample
34. Category II and Category III Code Purposes
Category II CPT codes are optional performance measurement codes that support data collection, not billing. Category III codes are temporary codes for emerging technology and services. Neither substitutes for a Category I code when one describes the service performed.
Example: A performance-measure code exists for a documented service. Decision: report the Category I code for payment and add Category II only for measurement.
Mistake to avoid: Billing a Category II or III code in place of the Category I code that describes the service.
Reference: AAPC CPC study guide sample
35. Surgery Guidelines and Included Services
CPT surgery guidelines define what surgical codes include, such as routine preoperative and postoperative work, and direct code selection within the surgery sections. Reading these introductory guidelines before coding an operative note prevents separating services the package already includes.
Example: An operative note separately mentions routine pre-service and post-service tasks. Decision: apply the surgery guidelines to determine what the surgical code already includes before adding codes.
Mistake to avoid: Coding routine included services separately because the note mentions them individually.
Reference: AAPC CPC study guide sample
36. Modifiers as Communication Tools
Modifiers attach to codes to indicate a service was altered by circumstance without changing its definition. Modifier choice depends on CPT guidance and payer policy, and HCPCS Level II carries its own modifier set. Append modifiers only when documentation supports the circumstance described.
Example: A documented circumstance changes how a standard service was delivered. Decision: append only the modifier whose definition the note actually supports, per CPT and payer rules.
Mistake to avoid: Appending a modifier habitually to force payment without matching documentation to its definition.
Reference: AAPC CPC study guide sample
Neoplasm and Integumentary Diagnosis Coding
37. Reading the Table of Neoplasms
The Table of Neoplasms lists sites in rows and six behavior columns: primary malignant, secondary malignant, carcinoma in situ, benign, uncertain behavior, and unspecified behavior. Find the site row first, then select the column matching the documented behavior before verifying in the Tabular List.
Example: A primary malignant lesion of the eyebrow skin is documented. Decision: use the eyebrow site row and the primary malignant column, then verify the full code.
Mistake to avoid: Choosing a column by habit, such as benign, without matching the documented pathology behavior.
Reference: AAPC CPC study guide sample
38. Primary versus Secondary Malignancy
Primary malignancy is the original cancer site; secondary malignancy is metastatic spread to another location. The same anatomic site can carry different codes depending on whether the cancer arose there or spread to it, so documentation of origin drives column choice.
Example: A skin lesion is documented as metastasis from a known primary elsewhere. Decision: use the secondary malignant column for the skin site.
Mistake to avoid: Coding a metastatic lesion as a new primary malignancy of the metastatic site.
Reference: AAPC CPC study guide sample
39. Uncertain Behavior Requires Pathology
Uncertain behavior is a specific pathologic diagnosis for a lesion currently benign but capable of malignant transformation; a pathology report must indicate it. This differs from unspecified behavior, which simply means no pathology report establishes the lesion's nature.
Example: Pathology describes a lesion whose behavior cannot be predicted and may transform. Decision: assign the uncertain behavior code, because the pathologist's report supports it.
Mistake to avoid: Assigning an uncertain behavior code when no pathology report describes the lesion's unpredictable nature.
Reference: AAPC CPC study guide sample
40. Unspecified Behavior When Pathology Is Absent
Unspecified behavior applies when no pathology report indicates the lesion's nature, such as a lesion removed or destroyed but never analyzed. It is a documentation-status choice, not a clinical judgment, and differs from uncertain behavior, which is a pathologist's determination.
Example: A lesion is destroyed in the office and no specimen is submitted for analysis. Decision: report the unspecified behavior code, because nothing establishes its nature.
Mistake to avoid: Confusing unspecified behavior with uncertain behavior and coding a pathologic determination that lacks a report.
Reference: AAPC CPC study guide sample
41. Melanoma Bypasses the Table of Neoplasms
Melanoma is indexed directly in the Alphabetic Index under melanoma with skin site entries, not through the general Table of Neoplasms. Starting at the table leads coders astray; the index entry directs to the correct malignant code for verification.
Example: Melanoma of the lip is documented. Decision: use the melanoma main term with the lip subterm in the index, bypassing the Table of Neoplasms entirely.
Mistake to avoid: Starting melanoma lookups in the Table of Neoplasms and selecting a generic skin malignant code.
Reference: AAPC CPC study guide sample
42. Where Skin and Breast Diagnoses Live
Skin diagnoses spread across three chapters: neoplasms, diseases of skin and subcutaneous tissue, and injury chapters. Breast diagnoses typically sit in the genitourinary chapter categories for breast disorders. Knowing the chapter prevents searching the skin chapter for breast conditions.
Example: A benign breast disorder is documented. Decision: look in the genitourinary chapter's breast disorder categories rather than the skin and subcutaneous tissue chapter.
Mistake to avoid: Searching the skin chapter for breast conditions and missing the genitourinary breast categories.
Reference: AAPC CPC study guide sample
Evaluation and Management Services
43. Three Elements of Medical Decision Making
E/M levels under current CPT guidelines rest on medical decision making: the number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications or morbidity from patient management. Weigh all three when selecting a level.
Example: A note shows an acute low-complexity problem, simple data review, and low management risk. Decision: the combination of low elements supports a low-level visit code.
Mistake to avoid: Selecting an E/M level from the highest single element while ignoring the other two.
Reference: AAPC CPC study guide sample
44. Leveling an Emergency Department Visit
Emergency department visits are leveled using the CPT E/M guidelines based on MDM, not the facility's internal triage level. An acute uncomplicated problem with straightforward data and low risk supports a low-level ED code; each element must be assessed from the note.
Example: A child's ED note shows an acute problem, history from a caregiver, and minor-procedure risk. Decision: the low elements support a low-level ED visit code.
Mistake to avoid: Matching the ED code to the triage acuity assignment instead of documented MDM elements.
Reference: AAPC CPC study guide sample
45. Time Exclusions for Separately Reported Services
When time drives an E/M level, minutes spent on services reported separately with their own CPT or HCPCS code are excluded from the E/M time. Counting that time in both places bills the same minutes twice, which the guide labels double billing.
Example: A same-day procedure with its own code took documented time. Decision: exclude those minutes from the E/M time total before selecting the level.
Mistake to avoid: Including time spent on a separately billed procedure when totaling E/M time.
Reference: AAPC CPC study guide sample
46. Third-Party History as Data Complexity
History obtained from someone other than the patient, such as a parent or caregiver, counts when assessing the amount and complexity of data reviewed. In the emergency example, caregiver-obtained history contributed to the data element of the MDM analysis.
Example: A grandmother provides the entire history for a nonverbal young child. Decision: count that independently obtained history when scoring the data element of medical decision making.
Mistake to avoid: Ignoring caregiver-obtained history as data because the patient did not speak.
Reference: AAPC CPC study guide sample
47. Setting-Specific E/M Guidelines
Different care settings use different leveling frameworks; emergency department visits follow the CPT E/M guidelines for that site, while office visits follow their own rules. Identify the setting from the note before choosing which leveling framework applies.
Example: A note documents care delivered in the emergency department. Decision: apply the ED E/M guidelines rather than office visit rules when selecting the level.
Mistake to avoid: Leveling an ED note with office visit rules and producing the wrong code.
Reference: AAPC CPC study guide sample
48. Scoring the Risk Element from Documented Management
The risk element of medical decision making measures the risk of complications and morbidity or mortality of patient management, and it is scored from the management the provider actually documented. In the emergency department example, removal of a nasal foreign body with bayonet forceps is a minor procedure, and the rationale scores the risk element as low on that basis. Judge this element from the documented management, such as performance of a minor procedure, rather than from how alarming the presenting complaint sounds.
Example: An ED note for a young child documents atraumatic removal of a raisin from the left nostril with bayonet forceps. Decision: the minor procedure scores the risk element as low, which combines with the low problem complexity and the caregiver-obtained history data to support a low-level ED visit code.
Mistake to avoid: Scoring the risk element from the drama of the presentation (a distressed toddler with a foreign body) instead of the documented management, such as a minor procedure.
Reference: AAPC CPC study guide sample
Coding from Operative and Pathology Reports
49. Read the Whole Note, Not the Headings
Do not code operative reports from the preoperative, postoperative, and procedure headings alone. Indications and procedure descriptions often contain the detail headings lack, such as findings that change a screening to high-risk or reveal absent pathology.
Example: Headings list colonic polyps, but the procedure narrative finds none present. Decision: code from the narrative findings, which control over the heading text.
Mistake to avoid: Assigning diagnosis codes straight from report headings without reading indications and findings.
Reference: AAPC CPC study guide sample
50. Postoperative Diagnosis Drives Reporting
For surgical cases, the postoperative diagnosis is used for reporting because it reflects findings at the end of the procedure. Compare it with the preoperative diagnosis; when they differ, the postoperative condition supplies the reported codes, keeping them aligned with what was actually found.
Example: The preoperative diagnosis is abdominal pain, but the postoperative diagnosis confirms cholecystitis. Decision: report the postoperative finding as the diagnosis for the case.
Mistake to avoid: Coding the preoperative diagnosis even when the postoperative diagnosis documents different findings.
Reference: AAPC CPC study guide sample
51. Pathology Reports Use the Clinical Diagnosis
On surgical pathology reports, the clinical diagnosis supplied with the specimen is used for reporting, not the gross description alone. The pathologist's clinical impression, such as chronic inflammation, drives the diagnosis code for the specimen service.
Example: A gallbladder pathology report concludes mild chronic cholecystitis as the clinical diagnosis. Decision: report that diagnosis rather than deriving codes from the gross description.
Mistake to avoid: Coding from the gross description instead of the pathologist's stated clinical diagnosis.
Reference: AAPC CPC study guide sample
52. History Codes When Disease Is Gone
When documentation shows a condition no longer exists, such as polyps absent at follow-up or a resected cancer under surveillance, code personal history rather than the active disease. History codes also support high-risk screening indications and follow-up encounters after completed treatment.
Example: Surveillance colonoscopy finds no polyps in a patient with prior polyps. Decision: report the personal history of polyps code, not a current polyp code.
Mistake to avoid: Coding a historical condition as current when the note shows it is resolved or absent.
Reference: AAPC CPC study guide sample
53. Follow-Up After Completed Cancer Treatment
Routine follow-up after completed treatment for a malignant neoplasm uses a dedicated follow-up examination code, and an instructional note requires an additional code identifying the personal history of that malignancy, sequenced after it.
Example: A patient returns for surveillance years after colon cancer treatment. Decision: report the follow-up examination code plus the personal history of colon malignancy code.
Mistake to avoid: Reporting the follow-up encounter without the required personal history of malignancy code.
Reference: AAPC CPC study guide sample
54. Building the Full Lookup Chain in Practice
Coding rationales in practice cases show the full chain: index lookup, subterm selection including side and clinical detail, code range verification, and final tabular confirmation. Reproduce this chain for every procedure and diagnosis rather than jumping to a memorized code.
Example: A varicose vein case with right-leg pain routes through varix, leg, right, with pain. Decision: the full chain yields the correct laterality-specific code.
Mistake to avoid: Skipping subterm steps like laterality or with-conditions and reporting an incomplete code.
Reference: AAPC CPC study guide sample
HIPAA Privacy in Coding Practice
55. Who Is a HIPAA Covered Entity
Covered entities are health plans, healthcare clearinghouses, and providers who transmit health information electronically in connection with standard HIPAA transactions. Workers' compensation programs and auto insurers are not covered entities, a distinction tested in coding coursework.
Example: A practice asks whether workers' compensation falls under HIPAA coverage. Decision: it does not, because such programs are excluded from the health plan definition.
Mistake to avoid: Assuming every payer or program touching health data is automatically a HIPAA covered entity.
Reference: AAPC CPC study guide sample; HHS Summary of the HIPAA Privacy Rule
56. What Counts as Protected Health Information
Protected health information is individually identifiable health information held or transmitted by a covered entity or business associate in any form: electronic, paper, or oral. It includes demographic identifiers linked to health, care, or payment, such as names, addresses, and record numbers.
Example: A coder discusses a patient's condition aloud where visitors can hear. Decision: oral disclosure of identifiable health information falls within PHI protections.
Mistake to avoid: Treating only electronic records as PHI and ignoring paper and oral forms.
Reference: HHS Summary of the HIPAA Privacy Rule
57. Minimum Necessary and Its Exceptions
Covered entities must limit uses, disclosures, and requests of PHI to the minimum necessary for the purpose, and generally may not send an entire record unless specifically justified. Exceptions include disclosures for treatment, to the individual, under authorization, to HHS, and when required by law.
Example: A routine recurring billing request seeks one encounter's details. Decision: send only the minimum necessary information under standard protocols, not the entire medical record.
Mistake to avoid: Releasing the entire medical record for routine purposes without specific justification.
Reference: HHS Summary of the HIPAA Privacy Rule
58. Treatment, Payment, and Operations Without Authorization
Covered entities may use and disclose PHI without individual authorization for treatment, payment, and healthcare operations. Payment includes obtaining premiums and reimbursement; operations include quality assessment, credentialing, audits, and fraud and abuse detection. Most other purposes require written authorization.
Example: A practice submits a claim to a payer for reimbursement of services. Decision: this payment activity proceeds without patient authorization as a permitted use.
Mistake to avoid: Believing every disclosure of PHI requires a signed patient authorization before a claim can be submitted.
Reference: HHS Summary of the HIPAA Privacy Rule
59. Business Associates and Their Agreements
A business associate is a non-workforce person or organization performing functions for a covered entity involving PHI, such as claims processing, billing, or data analysis. A written agreement must impose safeguards and cannot authorize any use or disclosure the Rule itself prohibits.
Example: A practice hires an outside billing service that handles identifiable claim data. Decision: a written business associate agreement imposing the required safeguards must govern the relationship.
Mistake to avoid: Letting a contractor handle PHI with no business associate agreement in place.
Reference: HHS Summary of the HIPAA Privacy Rule
60. De-Identification and Limited Data Sets
De-identified information, created by removing specified identifiers with no knowledge it could re-identify anyone, carries no Privacy Rule restrictions. A limited data set removes fewer direct identifiers and may be used for research, public health, or operations only under a data use agreement.
Example: A researcher needs identifiable-free claims data for a study. Decision: a limited data set with a data use agreement fits when full de-identification is unnecessary.
Mistake to avoid: Treating a limited data set as fully de-identified and sharing it without a data use agreement.
Reference: HHS Summary of the HIPAA Privacy Rule
References and further reading
Source links checked on Oct 2, 2026.