This guide organizes sixty teaching concepts into ten groups, moving from the business of medicine and terminology through diagnosis conventions, outpatient reporting rules, chapter-specific logic, CPT and modifiers, documentation dissection, and privacy compliance. Work through the groups in order, since later application assumes earlier foundations. Each concept pairs a rule with a resolved example and a targeted mistake, so you practice decisions rather than memorize definitions. References below support every rule stated. Use this alongside official code books and current guidelines rather than as a replacement for them.
The Business of Medicine and the Coder's Role
1. The coder's core function
Medical coding is the translation of provider documentation into standardized diagnosis and procedure codes; it is not the design of claim forms, EHR programming, or electronic file creation. The coder reads the record, assigns codes, and those codes then drive billing and reimbursement downstream.
Example: A note describing removal of a skin lesion becomes an excision code paired with a diagnosis code; the coder assigns codes rather than building the electronic claim file itself.
Mistake to avoid: Confusing code assignment with claim form completion or transaction file creation tasks.
Reference: AAPC CPC study guide sample
2. Provider hierarchy and accountability
Physicians and other qualified practitioners legally accountable for establishing the patient's diagnosis are the source for diagnosis code assignment, while clinical staff may document supporting data. Staff entries supply permitted supplementary details only under limited exceptions, such as pressure ulcer stage, BMI, coma scale, and laterality; the associated diagnosis itself must still come from the patient's provider.
Example: A nurse documents a pressure ulcer stage, but the provider must document the ulcer diagnosis itself before both can be reported together.
Mistake to avoid: Assigning a diagnosis code based solely on nursing or other ancillary staff documentation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
3. Payer types and Medicare parts
Payers divide into commercial insurers, such as Blue Cross Blue Shield, and government programs like Medicare and Medicaid. Medicaid is federally and state funded but state administered; Medicare splits into parts covering hospital, medical, Advantage plans, and prescription drugs delivered through private insurers.
Example: A patient discharged from the hospital after surgery fills a prescription for an oral pain reliever at a retail pharmacy near home; the pharmacy bills the Medicare prescription drug benefit, not the hospital or medical parts, because Part D covers outpatient prescription drugs through private insurers approved by Medicare.
Mistake to avoid: Treating Medicaid or Medicare as commercial payers, or assuming one Medicare part covers all services.
Reference: AAPC CPC study guide sample
4. Relative value scale components
Medicare physician payment uses a resource-based relative value scale with three components: physician work, practice expense, and professional liability insurance. Practice expense varies by site of service, so the same code carries different facility and non-facility totals.
Example: A code with a non-facility total higher than its facility total pays more in the office than in the hospital because practice expense differs.
Mistake to avoid: Expecting identical reimbursement for a code regardless of where the service is performed.
Reference: AAPC CPC study guide sample
5. Medical necessity linkage
Medical necessity ties each reported service to a diagnosis that justifies it. Payers deny services lacking diagnostic support, so the coder must confirm the documented reason for the encounter supports every procedure billed on that claim.
Example: A screening colonoscopy supported by documented personal history of colon cancer qualifies as high risk, justifying the high-risk screening code.
Mistake to avoid: Reporting a procedure on a claim without any diagnosis that establishes its medical necessity.
Reference: AAPC CPC study guide sample
6. Compliance programs, audits and the OIG work plan
Practices need internal compliance rules and routine audits to detect and correct coding errors before payers do. The HHS Office of Inspector General publishes a work plan identifying areas under scrutiny, which guides where a practice should focus its self-audit effort.
Example: A practice self-audits its visit-level coding after noticing high utilization patterns, correcting documentation gaps before a payer review.
Mistake to avoid: Treating compliance policies and periodic internal audits as optional administrative paperwork.
Reference: AAPC CPC study guide sample
Medical Terminology and Anatomy for Coding
7. Decoding terms from word parts
Medical terms decode by combining word parts: roots identify the body part or organ, combining vowels link the pieces, and suffixes describe the condition such as disease or enlargement. Breaking a term apart yields its approximate meaning and speeds accurate Alphabetic Index lookups.
Example: Cardi plus my plus pathy translates to diseased heart muscle, directing the coder to the correct index entry for cardiomyopathy.
Mistake to avoid: Guessing at unfamiliar terms instead of decomposing them into root and suffix.
Reference: AAPC CPC study guide sample
8. Plural ending patterns
Singular-to-plural conversions follow predictable patterns rather than simply adding s: vertebra becomes vertebrae, thrombus becomes thrombi, phalanx becomes phalanges, and index becomes indices. Recognizing the plural form tells the coder whether one or multiple structures are documented.
Example: A note referencing phalanges documents multiple finger bones, so the site coding must reflect plural involvement rather than a single digit.
Mistake to avoid: Coding a single site when the documented plural form indicates multiple structures.
Reference: AAPC CPC study guide sample
9. Anatomic position and directional terms
The anatomic position is upright, face forward, arms at the sides with palms forward. All directional terms, such as lateral, medial, and distal, describe the patient's body in this orientation, never the viewer's perspective.
Example: A note says the lateral left thigh; lateral refers to the outer side of the patient's own leg, not the observer's left.
Mistake to avoid: Applying left and right from the coder's or viewer's perspective instead of the patient's.
Reference: AAPC CPC study guide sample
10. Skin layers versus subcutaneous tissue
Skin comprises the epidermis and dermis, with the dermis holding vessels, nerves, and glands; the papillary and reticular layers sit within it. Subcutaneous fat lies beneath the dermis and is not a skin layer, a distinction that changes repair and lesion coding depth.
Example: A lesion documented to the subcutaneous tissue involves a deeper layer than one confined to the dermis, altering code selection.
Mistake to avoid: Counting subcutaneous fat as a third skin layer when classifying lesion depth.
Reference: AAPC CPC study guide sample
11. Body system to chapter mapping
Skin conditions scatter across ICD-10-CM chapters: neoplasms in Chapter 2, dermatitis and ulcers in Chapter 12, and injuries in Chapter 19. Breast diagnoses, by contrast, fall under genitourinary categories N60 through N65, not the skin chapter.
Example: A breast disorder must be sought in the N60-N65 categories; searching only skin categories will miss the correct code.
Mistake to avoid: Searching only the skin chapter for breast, nipple, or areolar conditions.
Reference: AAPC CPC study guide sample
12. Eponyms, synonyms and lay terms
Eponyms and everyday words appear constantly in documentation: a boil is a furuncle, several furuncles form a carbuncle, and staphylococcal infection typically causes both. The Alphabetic Index lists these synonyms, so coders convert lay terms into indexable main terms.
Example: A note saying boils on the neck converts to furuncle of the neck for the index lookup, yielding the correct code.
Mistake to avoid: Skipping the Alphabetic Index because the note uses everyday or eponymic wording.
Reference: AAPC CPC study guide sample
ICD-10-CM Structure and Conventions
13. Index first, Tabular verification second
Code selection always starts in the Alphabetic Index and ends with verification in the Tabular List, where notes and required characters may change the answer. Conventions and instructions within the classification itself take precedence over any general guideline.
Example: The index points to a code, but a Tabular note demands an additional character, so the verified final code differs from the index entry.
Mistake to avoid: Assigning a code straight from the Alphabetic Index without verifying it in the Tabular List.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
14. Placeholder X for seventh characters
When a code requiring a seventh character has fewer than six characters, the placeholder X fills each empty position so the extension lands in the correct slot. Every code within a category requiring extensions needs one, per the Tabular notes.
Example: A five-character code requiring a seventh character takes one placeholder, five characters plus X plus the extension; a four-character code in the same category takes two X placeholders so the extension still lands in the seventh position.
Mistake to avoid: Omitting the X placeholder and misplacing the seventh character in the code.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
15. NEC versus NOS abbreviations
NEC means the provider documented more specific information than the classification can capture, so an other specified code is used. NOS means the coder lacks the information needed for any more specific code; it is the equivalent of unspecified.
Example: A documented, uniquely specified disorder with no dedicated code takes the other specified code; a vague note with no detail takes the unspecified code.
Mistake to avoid: Defaulting to an unspecified code when the documentation clearly supports an other specified entry.
Reference: AAPC CPC study guide sample
16. Brackets versus parentheses
Brackets serve two roles: in the Tabular List they enclose synonyms or explanatory phrases, while in the Alphabetic Index they signal that multiple codes are required. Parentheses enclose nonessential modifiers whose presence or absence does not change the code.
Example: An index entry showing a bracketed second code means both codes are reported, such as a congenital infection plus its liver manifestation.
Mistake to avoid: Reporting only one code when Alphabetic Index brackets clearly require two codes.
Reference: AAPC CPC study guide sample
17. Excludes1 versus Excludes2 notes
An Excludes1 note means the excluded code can never be reported with the code above the note, typically because the conditions cannot coexist, like congenital versus acquired forms. An Excludes2 note means the condition is not included here but may coexist and be coded separately.
Example: A congenital form excluded by an Excludes1 note from the acquired code means only the congenital code is assigned.
Mistake to avoid: Reporting both conditions together despite an Excludes1 note prohibiting the combination.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
18. Includes notes and inclusion terms
An Includes note sits under a three-character category title to define or exemplify its content. Inclusion terms list conditions assigned to a code, often as synonyms, and are not exhaustive; additional terms found only in the Alphabetic Index may also map to the code.
Example: A documented synonym appearing as an inclusion term confirms the code choice even though it differs from the code title wording.
Mistake to avoid: Rejecting a correct code because the documented synonym is not the code title.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
General Diagnosis Coding Guidelines
19. Default codes
The default code is the one listed next to an Alphabetic Index main term, representing the most common presentation or the unspecified form. When a condition is documented without qualifying detail, such as acuity, the default code is assigned rather than an assumed specific one.
Example: Appendicitis documented with no acute or chronic qualifier takes the default code rather than an assumed acute code.
Mistake to avoid: Assuming acuity or laterality the record never documents instead of using the default.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
20. Provider statement over clinical criteria
Code assignment rests on the provider's diagnostic statement that the condition exists, not on the clinical criteria the provider used to reach it. When record documentation conflicts, the coder queries the provider rather than choosing between versions independently.
Example: The provider documents pneumonia despite an atypical radiograph; the pneumonia code is assigned because the provider stated the diagnosis.
Mistake to avoid: Overriding the provider's stated diagnosis based on the coder's own clinical interpretation.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
21. Laterality from other clinicians
Laterality may be taken from documentation by clinicians other than the treating provider when the provider is silent, but conflicting laterality requires a provider query. Unspecified side codes should rarely be used, only when clarification is impossible.
Example: A nurse documents the affected left side while the provider omits side; the left-side code is used without a query.
Mistake to avoid: Defaulting to an unspecified side code when another clinician clearly documented the laterality.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
22. Code also notes and sequencing
A code also note signals that two codes may be required to fully describe a single condition, but it provides no sequencing direction. Sequencing instead depends on the circumstances of the encounter, such as which condition prompted the visit.
Example: A patient treated for a documented hypertensive crisis with known essential hypertension has both codes reported; the code also note at the crisis code requires the hypertension code but leaves which is listed first to the reason for that encounter.
Mistake to avoid: Treating a code also note as if it dictated a fixed code sequence.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
23. Borderline diagnoses
A borderline diagnosis documented at discharge is coded as confirmed unless the classification provides a specific entry for that borderline condition. This rule applies identically in inpatient and outpatient settings because borderline conditions are not uncertain diagnoses.
Example: Borderline hypertension documented without a specific index entry is coded as confirmed hypertension, not deferred or omitted.
Mistake to avoid: Dropping or deferring a borderline diagnosis instead of coding it as confirmed.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
24. Coding syndromes
Syndromes are coded by following Alphabetic Index guidance first. Where the index offers no direction, assign codes for the documented manifestations, and add separate codes for manifestations that are not integral to the disease process when no unique code exists.
Example: An unindexed syndrome with documented seizures and developmental delay is coded through its manifestation codes rather than an invented syndrome code.
Mistake to avoid: Coding a single manifestation while ignoring other documented manifestations of an unindexed syndrome.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Outpatient and Inpatient Reporting Rules
25. Uncertain diagnoses by care setting
For inpatient stays, conditions documented as suspected at discharge may be coded as if confirmed. Outpatient rules differ: do not code suspected or rule-out conditions; instead report the signs, symptoms, or other reasons that prompted the encounter.
Example: An outpatient note reading possible pneumonia yields a cough or fever symptom code, never the pneumonia code itself.
Mistake to avoid: Applying inpatient logic and coding suspected conditions as confirmed in outpatient encounters.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
26. Principal diagnosis selection
In non-outpatient settings, the principal diagnosis is the condition established after study to be chiefly responsible for prompting the admission. When two conditions equally meet that definition, or when the treatment plan changes, the sequencing rules for those situations govern the choice.
Example: An admission for chest pain that study confirms as acute myocardial infarction sequences the infarction, not the symptom, as principal.
Mistake to avoid: Sequencing the presenting symptom over the confirmed condition responsible for admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
27. Reporting additional diagnoses
Additional diagnoses in non-outpatient settings include conditions that receive clinical evaluation, treatment, or monitoring, or that extend the stay or increase nursing care. Historical conditions that merely appear in the past medical history without current relevance are not reported.
Example: Documented diabetes requiring medication adjustment during the stay is reported; a remote resolved appendectomy is not.
Mistake to avoid: Listing every historical condition in the past medical history as an additional diagnosis.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
28. Chronic diseases versus resolved history
Chronic conditions treated on an ongoing basis may be coded as additional diagnoses whenever the patient receives treatment or the condition influences the current encounter's care. The same condition documented only as resolved history takes a personal history code instead.
Example: Hypertension monitored and refilled at the visit is coded as current; resolved past cancer takes a history code.
Mistake to avoid: Reporting remote, resolved conditions as current active diagnoses instead of history codes.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
29. Routine screenings without findings
For routine health screenings with no abnormal findings, code the reason for the screening encounter, such as the screening examination Z code. When a screening yields abnormal findings, the findings are coded in addition to the screening reason.
Example: A screening colonoscopy with a clean exam reports only the screening indication; no condition code is added.
Mistake to avoid: Appending a diagnosis for a condition the screening exam specifically ruled out.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
30. Abnormal findings on general exams
When a general medical examination reveals abnormal findings and no related definitive diagnosis is established, code the abnormal finding itself alongside the exam code. If the provider establishes a diagnosis from the finding, code that diagnosis instead.
Example: An annual exam detects a heart murmur with no diagnosis rendered; the murmur finding code accompanies the exam code.
Mistake to avoid: Assigning a definitive diagnosis the provider never established from an abnormal finding.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Chapter-Specific Diagnosis Coding
31. Diabetes combination codes and type default
Diabetes codes in E08 through E13 are combination codes capturing type, affected body system, and complication. Assign as many codes as needed for all documented complications, sequenced by the reason for each encounter; when type is undocumented, default to type 2.
Example: Type 2 diabetes with a documented diabetic foot ulcer takes the combination code linking diabetes to that skin complication.
Mistake to avoid: Reporting diabetes and its complication as separate codes when a combination code exists.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
32. Long-term diabetes drug use codes
Long-term medication use is captured with Z79 codes: insulin as Z79.4, oral hypoglycemics as Z79.84, and injectable non-insulin drugs as Z79.85, with combinations assigned together. Z79.4 is not assigned for insulin used only temporarily to control blood sugar during an encounter.
Example: A type 2 patient using both oral medication and insulin long term receives both the oral and insulin use codes.
Mistake to avoid: Assigning the long-term insulin use code for temporary blood sugar control during one encounter.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
33. Sepsis, severe sepsis and urosepsis
Severe sepsis requires at least two codes: the underlying systemic infection first, then the severe sepsis subcategory, plus codes for associated acute organ dysfunction. The term urosepsis is nonspecific with no default code and always requires a provider query.
Example: A note stating urosepsis prompts a query for clarification before any sepsis code is assigned.
Mistake to avoid: Treating urosepsis as synonymous with sepsis and assigning a sepsis code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
34. Neoplasm behavior columns
The Table of Neoplasms offers six behavior columns: primary, secondary, and in-situ malignancy, then benign, uncertain behavior, and unspecified behavior. Uncertain behavior requires a pathology report showing a lesion that may transform; unspecified behavior means no pathology established the nature.
Example: A lesion excised with pathology showing benign findings takes the benign column; a lesion removed without any pathology takes unspecified behavior.
Mistake to avoid: Assigning uncertain behavior when no pathology report documents that behavioral designation.
Reference: AAPC CPC study guide sample
35. Pressure ulcer staging and progression
Pressure ulcer stage may be documented by clinicians other than the provider, such as nursing, but the provider must document the ulcer itself. When an ulcer progresses to a higher stage during a stay, assign two codes: the admission stage and the highest stage reached.
Example: An ulcer documented at stage 2 on admission that progresses to stage 3 receives both stage codes for the same site.
Mistake to avoid: Reporting only the highest stage for an ulcer that evolved during the admission.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
36. Pain category sequencing
When the encounter is for pain management, the category G89 pain code is sequenced first, followed by a site code. For encounters with other purposes and no confirmed related diagnosis, the site code is sequenced first, followed by the appropriate G89 code.
Example: A visit solely for chronic neck pain management sequences the chronic pain code before the cervical site code.
Mistake to avoid: Always sequencing the anatomic site code first regardless of the encounter's purpose.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
CPT, HCPCS and Code Set Navigation
37. CPT section organization
CPT organizes procedures by body area and service type across sections for surgery, radiology, pathology, and medicine. Body-system study pairs anatomy review with the relevant ICD-10-CM, CPT, and HCPCS codes, so locating the correct section depends on identifying both the anatomy and the service.
Example: Destruction of a skin lesion is located in the integumentary subsection, not the musculoskeletal section, because skin is the relevant system.
Mistake to avoid: Searching the wrong CPT section after misidentifying the involved body system.
Reference: AAPC CPC study guide sample
38. National Correct Coding Initiative edits
The National Correct Coding Initiative publishes edits that identify code pairs not separately payable, typically a component bundled into a more comprehensive service. Understanding which pairs are edited prevents submitting combinations that payers will automatically deny.
Example: A small paired procedure listed with its comprehensive service is not separately reportable because the edit bundles the component.
Mistake to avoid: Assuming every documented service in an operative note is separately billable.
Reference: AAPC CPC study guide sample
39. Category II versus Category III codes
Category II codes are optional performance-measurement codes tracking quality data, never substitutes for Category I reporting. Category III codes are temporary alphanumeric codes for emerging technology, allowing data collection before the procedure earns a permanent code.
Example: A new experimental ablation technique with no Category I code is reported with its temporary Category III code.
Mistake to avoid: Using a Category III code when an established Category I code describes the service.
Reference: AAPC CPC study guide sample
40. HCPCS Level II for Medicare services
HCPCS Level II provides alphanumeric codes for services and supplies CPT does not cover, including Medicare-specific screening services. Medicare patients require these codes where policy dictates, such as screening colonoscopy codes that vary by patient risk level.
Example: A Medicare patient with personal colon cancer history receives the high-risk screening colonoscopy HCPCS code rather than a CPT screening code.
Mistake to avoid: Reporting the CPT screening code when Medicare policy requires the corresponding G code.
Reference: AAPC CPC study guide sample
41. Comprehensive code for a multi-vein injection session
Sclerotherapy code selection turns on the documented details of the injection session: the CPT Index directs to the sclerotherapy code range, and when the note shows multiple veins injected in the same leg at one encounter, verification in that range leads to the single code for multiple veins in one leg. The coder must count the veins injected and identify which leg was treated from the procedure description, because those documented facts determine which code applies.
Example: A warehouse worker with varicose veins of the left calf and left thigh receives injections into both veins during a single office session; the claim reports the one code for multiple veins in the same leg, and billing a separate injection code for each vein misrepresents one session as two services.
Mistake to avoid: Reporting a separate injection code for each vein when one code covers multiple veins injected in the same leg during a single session.
Reference: AAPC CPC study guide sample
42. CPT Assistant as interpretive resource
CPT Assistant is the AMA's official advisory publication clarifying ambiguous code use through questions and answers. When code book wording is unclear or two readings conflict, this published interpretation is the authoritative source for resolving the correct application.
Example: An ambiguous distinction between excision and destruction coding is resolved by the published CPT Assistant interpretation of the codes.
Mistake to avoid: Resolving ambiguous code use from memory or unofficial summaries rather than published interpretation.
Reference: AAPC CPC study guide sample
Modifiers, Bundling and Payment Logic
43. What modifiers actually do
A modifier appended to a code changes the circumstance of the service without altering the code's definition, communicating details such as laterality, reduced service, or which professional performed the work. Modifiers explain; they never transform one service into another.
Example: A procedure performed on both hands during one session takes the bilateral modifier rather than two full procedure codes.
Mistake to avoid: Using modifiers to transform a code into a service it was never defined to describe.
Reference: AAPC CPC study guide sample
44. HCPCS Level II modifiers
HCPCS Level II includes two-character modifiers used for payer-specific circumstances, distinct from CPT's modifier list. Level II modifiers often serve Medicare payment policy purposes, so the applicable set depends on both the code set and the payer involved.
Example: A Medicare payment-policy situation calls for the Level II modifier rather than the similar-looking CPT modifier.
Mistake to avoid: Treating CPT and Level II modifiers as fully interchangeable across every payer.
Reference: AAPC CPC study guide sample
45. Excluding separately reported service time from visit time
When time determines the level of an E/M service, any time spent on a service that is separately reported with its own CPT or HCPCS Level II code is excluded from the time used to set the visit level. Reporting the separate service and folding its minutes into the visit time as well is double billing, because the same time is billed twice. The coder must identify which documented minutes belong to the separately reported service and remove them before totaling visit time.
Example: During an office visit whose level will be chosen by time, the provider also performs a separately reported laceration repair; the minutes spent on the repair are left out of the visit's total time, and counting them in both the visit level and the repair code would pay the same minutes twice.
Mistake to avoid: Including minutes spent on a separately reported procedure in the E/M visit time as well as the procedure's own code.
Reference: AAPC CPC study guide sample
46. Verifying payment against the correct fee schedule total
The National Medicare Physician Fee Schedule relative value file lists each CPT and HCPCS Level II code's component values: the physician work RVU, separate non-facility and facility practice expense RVUs, and the malpractice RVU, alongside computed non-facility and facility totals. Each total sums the work RVU, the malpractice RVU, and the practice expense RVU for that site of service, so verifying or auditing a payment requires matching the documented place of service to the correct total.
Example: An established patient visit carries a work RVU of 1.92, non-facility practice expense of 1.79, facility practice expense of 0.83, and malpractice RVU of 0.14; an office claim paid at the facility total of 2.89 instead of the non-facility total of 3.85 signals a place-of-service processing error to correct.
Mistake to avoid: Comparing a claim's payment to the total for the wrong site of service, or mixing facility and non-facility practice expense in a single total.
Reference: AAPC CPC study guide sample
47. Time excluded for separately reported services
When a separately reported service is performed during a visit, the time spent on that service cannot also count toward the time determining the visit level. Counting the same minutes twice constitutes double billing of identical time.
Example: A procedure performed during the visit has its minutes excluded from the visit's time total, so the level drops accordingly.
Mistake to avoid: Including minutes spent on a separately billed procedure inside the E/M time total.
Reference: AAPC CPC study guide sample
48. Global surgery package awareness
Surgery guidelines define what routine preoperative and postoperative work is included in a procedure's global package. Only services that are distinct, significant, and separately identified may be reported with their own codes during the package period.
Example: A routine uncomplicated postoperative check within the global period is not billed as a new visit.
Mistake to avoid: Billing routine postoperative visits as new encounters inside the global period.
Reference: AAPC CPC study guide sample
E/M Coding and Documentation Dissection
49. Three elements of medical decision making
Medical decision making rests on three elements: the number and complexity of problems addressed, the amount and complexity of data reviewed and analyzed, and the risk of complications or morbidity or mortality of patient management. The visit level is determined by applying what is documented for each element against the MDM leveling tables, never by the volume of documentation.
Example: An acute uncomplicated problem with minimal data review and low risk from a minor procedure supports a low-complexity level, regardless of how long the note runs.
Mistake to avoid: Selecting visit levels by note length instead of the documented decision-making elements.
Reference: AAPC CPC study guide sample
50. Emergency department leveling
Emergency department services have their own dedicated code series, and the level is selected using the AMA CPT E/M services guidelines based on the documented problems, data reviewed, and management risk. Office visit leveling logic does not transfer to the ED series.
Example: A skateboarder with a forearm laceration repaired in the ED has an acute uncomplicated problem, limited data, and low risk from a minor procedure, supporting a low-level ED code from the ED series rather than an office visit code.
Mistake to avoid: Assigning office visit codes or office leveling logic to an emergency department encounter.
Reference: AAPC CPC study guide sample
51. Third-party history as data
History provided by someone other than the patient, such as a parent or caregiver, counts when assessing the data element of decision making. The source of the history does not disqualify it; its contribution to complexity is what matters.
Example: A patient with advanced dementia cannot relate symptoms; the accompanying spouse provides the history of present illness, and that caregiver-obtained history counts in the data complexity assessment for the visit level.
Mistake to avoid: Discounting caregiver-obtained history as if it cannot count in the data element.
Reference: AAPC CPC study guide sample
52. Postoperative diagnosis governs reporting
When preoperative and postoperative diagnoses differ, the postoperative or final diagnosis is used for reporting because it reflects what was actually found. Pathology results and operative findings supersede the preoperative heading whenever they establish a definitive condition.
Example: A knee arthroscopy performed for a suspected meniscal tear visualizes an intact meniscus and a symptomatic synovial plica that is resected; the postoperative finding governs the diagnosis reported, not the preoperative suspicion.
Mistake to avoid: Coding the preoperative diagnosis when the operative or pathology findings establish a definitive one.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
53. Reading the whole note, not the headings
Headings in operative reports can be incomplete or stale; the indications and procedure description often supply the facts that determine codes. The entire record is reviewed, and the body of the note overrides the headings when they conflict.
Example: A report heading lists bilateral carpal tunnel syndrome, but the procedure description documents release of the right side only; the coder reports from the description because headings can be stale while the indications and note body supply the controlling facts.
Mistake to avoid: Coding only from report headings while ignoring the indications and procedure description.
Reference: AAPC CPC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
54. When a condition counts as a complication of care
Not every condition that appears during or after care is a complication: code assignment requires the provider's documentation of a cause-and-effect relationship between the care provided and the condition, and the documentation must show the condition is clinically significant. The provider does not need to write the word complication; a condition that alters the course of the surgery as documented in the operative report supports the complication code. When the relationship between the condition and the care is unclear, the provider is queried for clarification.
Example: An operative note for a laparoscopic procedure describes unexpected bleeding that forced conversion to an open approach; even though the word complication never appears, the documented cause-and-effect between the surgery and the bleeding supports a complication code. A separate note mentioning mild nausea the evening after an uneventful procedure, with no effect on the course of care, does not.
Mistake to avoid: Reporting a complication code for any condition that occurs after a procedure, or withholding one only because the provider never used the word complication.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Privacy, Security and Compliance
55. Who is a covered entity
Covered entities under the Privacy Rule are health plans, health care clearinghouses, and providers that transmit health information electronically in connection with standard HIPAA transactions. Workers' compensation carriers, auto insurers, and property-casualty insurers are not covered entities.
Example: A workers' compensation carrier requesting records is not a covered entity, so its request is governed by other rules, not covered-entity status.
Mistake to avoid: Assuming every payer or insurance entity is automatically a HIPAA covered entity.
Reference: HHS Summary of the HIPAA Privacy Rule
56. Business associates and agreements
A business associate is a non-workforce person or organization performing functions for a covered entity involving protected health information, such as claims processing or billing. The covered entity must impose written safeguards through a business associate agreement.
Example: An outside billing service processing a practice's claims must operate under a signed business associate agreement before receiving records.
Mistake to avoid: Releasing protected health information to contractors before a written business associate agreement is in place.
Reference: HHS Summary of the HIPAA Privacy Rule
57. Minimum necessary standard
The minimum necessary standard requires reasonable efforts to use, disclose, or request only the information needed for the purpose. It does not apply to treatment disclosures, disclosures to the individual, uses under authorization, or disclosures required by law.
Example: A payer reviewing one service receives the relevant encounter documentation, not the patient's entire record, unless the whole record is justified.
Mistake to avoid: Routinely sending the entire medical record when a narrower disclosure would accomplish the purpose.
Reference: HHS Summary of the HIPAA Privacy Rule
58. Treatment, payment and operations permissions
Covered entities may use and disclose protected health information without individual authorization for treatment, payment, and health care operations. Written consent for these purposes is optional under the rule, though an entity may choose to seek it.
Example: Sending records to a consulting physician for treatment requires no authorization; the disclosure falls within the treatment permission.
Mistake to avoid: Requiring written patient authorization for every routine treatment, payment, or operations disclosure.
Reference: HHS Summary of the HIPAA Privacy Rule
59. Psychotherapy notes protections
Psychotherapy notes, defined as a mental health professional's separated session analysis notes, require authorization for most uses, including treatment, payment, and operations. Session times, medication notes, and treatment summaries are excluded from this definition and follow ordinary rules.
Example: An insurer requesting a therapist's session analysis notes needs the patient's authorization; a treatment summary does not.
Mistake to avoid: Treating ordinary progress notes or treatment summaries as psychotherapy notes requiring authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
60. De-identification methods
De-identification removes protected status either through a qualified statistician's formal determination or by stripping the specified identifiers of the individual and relatives, with no actual knowledge the remainder could identify anyone. De-identified information carries no use or disclosure restrictions.
Example: A dataset stripped of names, dates, and record numbers, with no remaining identification risk, may be shared freely.
Mistake to avoid: Believing that removing only the patient's name de-identifies the entire record.
Reference: HHS Summary of the HIPAA Privacy Rule
References and further reading
Source links checked on Oct 2, 2026.