Work through the ten groups in order, because diagnosis conventions come before E/M leveling, and leveling comes before procedures, modifiers, and compliance applications. Each concept pairs a rule with a resolved example and a specific error to avoid, so read all three parts before moving on. Keep your current ICD-10-CM, CPT, and HCPCS code books open beside you, since the concepts assume you can look up codes. This guide is independent study support, not an official syllabus, and it does not replace the official study materials or hands-on coding experience.
ICD-10-CM Conventions and Code Structure
1. Alphabetic Index to Tabular List Workflow
Begin with the main term in the Alphabetic Index, follow every see and see also cross-reference, then verify the code in the Tabular List, reading notes, footnotes, and inclusion terms before finalizing. The Index alone never finalizes a code because Tabular instructions can change, expand, or invalidate the selection.
Example: A coder finds a burn entry in the Index pointing to a code family; in the Tabular List a laterality and 7th character requirement appear, so both are added before reporting. The code is completed in the Tabular List because Index entries alone are incomplete.
Mistake to avoid: Reporting a code straight from the Index without verifying Tabular List instructions and required characters.
Reference: AAPC CEDC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
2. Placeholder Character X
Where the classification inserts the placeholder character X, it must be entered in the empty positions so that a required 7th character lands in the seventh position; omitting the X produces an invalid code. This applies notably in poisoning and injury categories where codes are shorter than seven characters.
Example: A five-character injury code requiring an initial-encounter 7th character is reported with X filling the sixth position, because the 7th character must occupy the final data field for the code to be valid.
Mistake to avoid: Dropping the X placeholder and submitting a malformed code that fails validity edits.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
3. Seventh Character Episode of Care
Chapter 19 injury categories generally require a 7th character indicating initial encounter, subsequent encounter, or sequela for every code within the category, not merely some codes. The 7th character must reflect the episode of care actually being managed at the current encounter.
Example: An ED visit for a newly diagnosed wrist fracture takes the initial-encounter 7th character, because this encounter is the first active treatment episode documented for that injury.
Mistake to avoid: Assigning a subsequent or sequela 7th character during the first active treatment encounter.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
4. Excludes1 Versus Excludes2
An Excludes1 note means the excluded code is never used at the same time as the code above the note, because the two conditions cannot coexist. An Excludes2 note means the excluded condition is not part of that code but the patient may have both, so both codes may be reported when documented.
Example: A congenital-versus-acquired pairing blocked by Excludes1 is not reported together; an Excludes2 pair such as two coexisting digestive conditions is coded together because the note permits coexistence when documented.
Mistake to avoid: Treating every Excludes note as an absolute bar and dropping a legitimately coexisting condition.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
5. NEC Versus NOS Abbreviations
NEC, not elsewhere classifiable, directs the coder to an other specified code when the documentation names a condition lacking a dedicated code. NOS, not otherwise specified, is the equivalent of unspecified and is used when the documentation itself lacks the detail needed for anything more specific.
Example: A documented rare fracture variant with no unique code is assigned the other-specified fracture code, because the provider specified the condition even though the classification lacks a dedicated entry for it.
Mistake to avoid: Defaulting to an unspecified NOS code when the documentation actually supports an other-specified NEC code.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
6. The With Convention Presumption
When with or in links two conditions in a code title, Index entry, or Tabular note, the classification presumes a causal relationship even without explicit provider linkage, unless the documentation clearly states the conditions are unrelated or another guideline specifically requires documented linkage between them.
Example: An Index entry linking diabetes with a documented complication is coded as related, because the classification's relational term presumes causation absent a provider statement that the two conditions are unrelated.
Mistake to avoid: Separating conditions the classification links with with simply because the provider did not explicitly connect them.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
Outpatient Diagnosis Selection and Sequencing
7. First-Listed Diagnosis Selection
For outpatient encounters, the first-listed diagnosis describes the most significant reason for the visit and reflects the chief complaint; relevant coexisting conditions and history are reported as secondary diagnoses. Each date of service stands alone, so the first-listed code must be supported by that specific encounter's documentation.
Example: A patient presents after a fall with hip pain and imaging confirms dislocation. The dislocation is first-listed because it is the chief reason the encounter occurred and required active treatment that day.
Mistake to avoid: Sequencing a historical or incidental condition first instead of the reason that occasioned the visit.
Reference: AAPC CEDC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
8. Uncertain Diagnoses Are Not Coded
Terms such as probable, possible, suspected, likely, rule out, compatible with, and consistent with are not coded in outpatient reporting. Code the highest level of certainty known, using documented signs, symptoms, or abnormal test results, until a definitive diagnosis is actually established for that encounter.
Example: A note reads suspected pneumonia with cultures pending. The coder reports the documented cough and fever, because an unconfirmed diagnosis cannot be assigned in the outpatient setting.
Mistake to avoid: Assigning a suspected or rule-out diagnosis as though it were confirmed at the outpatient encounter.
Reference: AAPC CEDC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
9. Symptoms Integral to a Definitive Diagnosis
Once a definitive diagnosis is established, signs and symptoms integral to that disease process are not reported separately. Add symptom codes only when a symptom is not integral to the confirmed condition, or when the provider documents a reason to believe the symptom stems from a separate, unrelated process.
Example: A note confirms cellulitis of the lower leg as the reason for the visit, but the provider documents that the patient's chest pain appears unrelated and possibly cardiac: the chest pain is coded alongside the cellulitis because the provider documented a reason to believe the symptom stems from a separate process.
Mistake to avoid: Stacking every listed symptom beneath a confirmed diagnosis that already explains those symptoms.
Reference: AAPC CEDC study guide sample
10. Acute-on-Chronic Sequencing
When a condition is documented as both acute or subacute and chronic, and no single code captures the combination, the code book instructs you to report the acute or subacute code as the first-listed diagnosis with the chronic code reported as a secondary diagnosis.
Example: A flare of a chronically diseased joint without a combination code is coded with the acute exacerbation first and the chronic condition second, because the acute process drove the encounter.
Mistake to avoid: Sequencing the chronic code first when the documentation describes an acute-on-chronic presentation.
Reference: AAPC CEDC study guide sample
11. Postoperative Diagnosis Governs
When both a preoperative and a postoperative diagnosis are documented and they differ, always report the postoperative diagnosis. The findings established during the procedure supersede the working impression that prompted it, because the confirmed result reflects what was actually treated.
Example: A patient undergoes drainage of a suspected abscess that exploration shows to be a hematoma; the hematoma is coded because the postoperative finding replaced the preoperative suspicion.
Mistake to avoid: Coding the preoperative working diagnosis when the postoperative finding differs.
Reference: AAPC CEDC study guide sample
12. Chronic Conditions Reported Only When Relevant
Report a chronic diagnosis only when that condition is treated at the encounter or becomes an active factor in the patient's care. Do not report conditions that no longer exist or that do not pertain to the current visit, even though they appear in the recorded history.
Example: A history lists remote cholecystectomy and stable hypertension untouched during a laceration repair; neither is coded because neither was treated nor affected management of the visit.
Mistake to avoid: Extracting every historical condition from the chart onto the current claim.
Reference: AAPC CEDC study guide sample; CDC ICD-10-CM Official Guidelines, FY 2027
ED-Specific Diagnosis Applications
13. Fracture Coding Specificity Requirements
Fracture coding for the wrist and hand requires a fifth character for location, a sixth character for laterality and displacement status, and a seventh character for episode of care. If any of these elements is missing from the documentation, a valid code cannot be constructed, so work with the provider to obtain it.
Example: A note documents a nondisplaced left distal radius fracture at the initial visit; the coder builds the complete code because location, laterality, displacement, and episode of care are all stated.
Mistake to avoid: Assigning an unspecified fracture code when the note actually contains the detail needed for full specificity.
Reference: AAPC CEDC study guide sample
14. Glasgow Coma Scale Code Use
Coma scale codes are supplementary and sequenced after the diagnosis code, with the 7th character matching across the eye, verbal, and motor components. At minimum, report the initial score documented on presentation, which may come from emergency medical technicians or ED staff rather than the provider.
Example: EMS documents a total score on arrival; the coder reports the coma scale code sequenced after the head injury code, using the initial presentation score with matching 7th characters.
Mistake to avoid: Sequencing coma scale codes before the injury diagnosis or omitting the initial documented score.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
15. NIHSS Stroke Scale Codes
NIH stroke scale codes may be used with acute stroke codes to convey neurologic status and severity, and they are sequenced after the acute stroke diagnosis. Report at least the initial documented score; the score itself may be documented by clinicians other than the patient's provider.
Example: An ED stroke patient has an initial scale score recorded by nursing; the scale code follows the stroke code because it supplements rather than replaces the diagnosis.
Mistake to avoid: Using the stroke scale code as a stand-in for the acute stroke diagnosis or sequencing it first.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
16. Death on Arrival Coding Limits
The code for ill-defined and unknown cause of mortality is used only in the very limited circumstance of a patient who has already died being brought to the ED or another facility and pronounced dead on arrival. It does not represent a discharge disposition of death for patients treated first.
Example: A patient arrives without vital signs and is pronounced dead on arrival; the ill-defined mortality code is assigned because the encounter fits the narrow on-arrival-death circumstance.
Mistake to avoid: Assigning the death NOS code for a patient who died during treatment in the department.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
17. SIRS of Non-Infectious Origin
When SIRS is documented with a non-infectious process such as trauma, pancreatitis, or malignancy, and no infection is documented, code the underlying condition first, then the SIRS code without or with acute organ dysfunction as documented. Query the provider if dysfunction attribution to SIRS is unclear.
Example: A trauma patient meets SIRS criteria with documented acute kidney injury; the injury is coded first, then the SIRS-with-dysfunction code plus the organ dysfunction code, because the underlying trauma drives sequencing.
Mistake to avoid: Coding sepsis or infection when only non-infectious SIRS with an underlying condition is documented.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
18. Clinician Values Versus Provider Diagnoses
Clinical staff such as dietitians, nurses, or emergency technicians may document measurable values like BMI, coma scale scores, or pressure ulcer stages, but the associated diagnosis must be documented by the patient's provider. When documentation conflicts, query the provider for clarification before coding.
Example: Nursing documents a BMI value, but obesity is coded only because the provider's note independently documents the obesity diagnosis, since staff may record values but not diagnoses.
Mistake to avoid: Coding a diagnosis solely because a non-provider clinician documented the associated measurement.
Reference: CDC ICD-10-CM Official Guidelines, FY 2027
E/M Leveling Foundations for ED Visits
19. MDM or Time, But Never Time in the ED
E/M levels are selected by either the level of medical decision making or the total time on the date of the encounter. However, time is not a descriptive component of emergency department E/M services, so for ED visits, MDM is the sole determining factor for code selection.
Example: An ED note documents 45 minutes of care; the coder still levels the visit strictly by MDM because time does not drive ED E/M code selection.
Mistake to avoid: Selecting an ED E/M level from documented time the way office visits may be leveled.
Reference: AAPC CEDC study guide sample
20. The Three Elements of MDM
MDM is graded across three components: the number and complexity of problems addressed at the encounter, the amount and complexity of data to be reviewed and analyzed, and the risk of complications, morbidity, or mortality of patient management. The definitions in the CPT E/M guidelines govern how each element is scored.
Example: A visit addressing one stable problem with no data review and minimal risk levels as straightforward, because each element is evaluated and the overall grade follows the guideline definitions.
Mistake to avoid: Leveling MDM from a single element or from the final diagnosis alone.
Reference: AAPC CEDC study guide sample
21. Problems Must Be Addressed to Count
A problem counts toward the number and complexity of problems only if it is addressed during the encounter through history, exam, or medical decision making, including ordered diagnostic studies such as lab or radiology. Problems merely listed in the history but never worked are excluded from the count.
Example: A note lists distant asthma but no assessment, testing, or plan touches it; asthma is excluded from MDM because it was not addressed at this encounter.
Mistake to avoid: Counting every documented history item as an addressed problem for MDM.
Reference: AAPC CEDC study guide sample
22. Comorbidities Must Be Addressed for Risk
Comorbidities and underlying diseases do not influence the E/M level unless the provider addresses them during the encounter and their presence increases the amount or complexity of data reviewed or the risk of patient management. A bare mention of a chronic illness in the record is not sufficient.
Example: Diabetes appears in the history of a laceration repair with no impact on care; it does not raise risk because the documentation never links it to assessment or management decisions.
Mistake to avoid: Inflating MDM risk by counting chronic diseases that were listed but never addressed.
Reference: AAPC CEDC study guide sample
23. Externally Managed Conditions in Leveling
When documentation only states that a condition exists and is being treated by another provider, it is not considered in leveling. It counts only if additional documentation shows assessment or care coordination regarding that diagnosis beyond the bare statement of outside management.
Example: A note says hypertension is managed by the PCP with no further involvement; it is excluded from MDM because mere acknowledgment of outside management is not assessment or coordination.
Mistake to avoid: Counting externally managed conditions toward the level without documented assessment or coordination.
Reference: AAPC CEDC study guide sample
24. History and Exam Do Not Set the Level
A medically appropriate history and physical examination should be documented and is included in the service, but under current guidelines history and exam are not used to determine the level of the code. Only MDM, or time where the code family permits it, sets the level of service.
Example: An exhaustive review of systems and full physical exam accompany a low-complexity decision; the visit still levels low because exam breadth cannot raise the ED E/M level.
Mistake to avoid: Up-leveling a visit because the history and exam sections are lengthy.
Reference: AAPC CEDC study guide sample
MDM Depth: Data and Risk Grading
25. Risk Reflects Management Decisions
Risk is evaluated from the provider's assessment of the patient's potential for illness, complications, or death between the current encounter and the next scheduled visit, and it is distinct from the inherent risk of the condition itself. Management options considered but not selected, as discussed with the patient or family, also count.
Example: A provider weighs admission versus discharge with the family and chooses discharge with return precautions; the considered admission counts toward risk because weighed options are evaluated.
Mistake to avoid: Grading risk solely by how dangerous the final diagnosis sounds.
Reference: AAPC CEDC study guide sample
26. Extensive Data Requires Two of Three Categories
The extensive level of data review requires meeting two of the three data categories, such as ordering or reviewing multiple unique tests combined with discussing the patient's management with another provider. Satisfying one category alone, however heavily, does not reach the extensive level of data.
Example: A provider orders three unique tests and confers with a consultant about management; extensive data is met because two distinct categories, tests and discussion, are both satisfied.
Mistake to avoid: Marking data as extensive after satisfying only one category, such as many tests alone.
Reference: AAPC CEDC study guide sample
27. Final Diagnosis Does Not Fix Complexity
The final diagnosis for a condition does not by itself determine complexity or risk, because extensive evaluation may be required to conclude that symptoms do not represent a highly morbid condition. Presenting symptoms likely to represent a highly morbid condition may drive MDM even when the ultimate diagnosis is not highly morbid.
Example: A chest pain workup rules out infarction; the encounter still reflects higher MDM because ruling out a life-threatening presentation drove the decision making.
Mistake to avoid: Down-leveling a visit because the workup ended in a benign final diagnosis.
Reference: AAPC CEDC study guide sample
28. Aggregate Risk of Multiple Problems
Multiple problems of lower severity may, in aggregate, create higher risk because of interaction among them. Evaluate the combined effect of the problems on management decisions rather than dismissing each problem as minor when viewed in isolation from the others.
Example: A patient with several modest acute issues that complicate each other's treatment supports a higher risk level because their interaction raises overall management complexity.
Mistake to avoid: Treating each low-severity problem as if it existed alone when grading risk.
Reference: AAPC CEDC study guide sample
29. The Lowest ED Code Has No MDM
The lowest ED E/M code is reported for services that typically do not require the presence of a provider, so the concept of MDM does not apply to it. The remaining ED levels map respectively to straightforward, low, moderate, and high MDM, correlating each level of service to a graded level of decision making.
Example: A minimal ED service not requiring provider presence is reported with the lowest ED code, because no MDM grading applies to that level of service.
Mistake to avoid: Attempting to grade MDM elements to justify the lowest ED E/M code.
Reference: AAPC CEDC study guide sample
30. Read the Whole Note for Problems
The number and complexity of problems must be determined by reading the entire note rather than relying on the chief complaint, which will not always accurately describe what was addressed. Conditions worked up in the assessment, plan, and orders expand the problem count even when the chief complaint sounds narrow.
Example: A wrist-pain note also evaluates and treats an acute allergic reaction; both count toward problems because the full record shows both were addressed during the visit.
Mistake to avoid: Leveling from the chief complaint alone and missing problems addressed later in the note.
Reference: AAPC CEDC study guide sample
ED Provider Scenarios and Regulatory Context
31. ED Provider Treating an Inpatient
When an ED provider is called up to a hospital floor, such as the ICU, to provide services to a patient, the ED E/M code is not reported. Instead, a hospital inpatient and observation care E/M code is reported, because the setting and nature of the service have changed.
Example: An ED physician manages a critical patient upstairs in the ICU; the encounter is coded with inpatient E/M codes because the service occurred outside the emergency department.
Mistake to avoid: Reporting ED E/M codes for care the ED provider delivered on an inpatient unit.
Reference: AAPC CEDC study guide sample
32. Disclosing to Avert a Serious and Imminent Threat
A covered entity may disclose protected health information it believes necessary to prevent or lessen a serious and imminent threat to a person or the public, when the disclosure is made to someone the entity believes can prevent or lessen the threat, including the target of the threat. Disclosure to law enforcement is also permitted to identify or apprehend an escapee or violent criminal. These disclosures are permitted without patient authorization.
Example: A patient treated in the ED after an overdose tells the provider he intends to kill a named neighbor when discharged; the ED may disclose the information necessary to prevent the threat to the neighbor and to law enforcement, because the rule permits disclosure to someone able to lessen a serious and imminent threat, including the target of the threat.
Mistake to avoid: Withholding a permitted warning disclosure because no patient authorization was signed, or assuming threat disclosures always require the patient's permission.
Reference: HHS Summary of the HIPAA Privacy Rule
33. The Only Two Required Disclosures
A covered entity must disclose protected health information in only two situations: to individuals or their personal representatives when they request access to their records or an accounting of disclosures, and to HHS when it undertakes a compliance investigation, review, or enforcement action. Every other disclosure is permitted but not required, so outside these two situations the entity decides under the rule's permitted-use categories or an authorization.
Example: An attorney contacts the ED demanding a patient's chart for a lawsuit; the demand is not one of the two required disclosures, so the chart is released only under another permitted basis, such as a court order or the patient's authorization, not because the request itself compels turnover.
Mistake to avoid: Treating every records demand as mandatory when only individual access or accounting requests and HHS compliance demands require disclosure.
Reference: HHS Summary of the HIPAA Privacy Rule
34. Family Involvement When the Patient Cannot Agree
A covered entity may rely on an individual's informal permission to disclose to family, relatives, friends, or other persons the patient identifies, protected health information directly relevant to that person's involvement in the patient's care or payment for care. Where the patient is incapacitated, in an emergency situation, or not available, the entity generally may make these disclosures if, in the exercise of professional judgment, the disclosure is determined to be in the best interests of the individual.
Example: An unconscious trauma patient's spouse asks about the treatment plan; the ED may share the information directly relevant to the spouse's involvement in the patient's care, because professional judgment supports the disclosure as being in the patient's best interest while the patient cannot agree or object.
Mistake to avoid: Refusing all communication with the family of incapacitated patients instead of applying the best-interest judgment the rule permits.
Reference: HHS Summary of the HIPAA Privacy Rule
35. Facility Directory Disclosures
A covered health care provider may rely on an individual's informal permission to list the patient's name, general condition, religious affiliation, and location in a facility directory. The provider may then disclose the patient's condition and location in the facility to anyone asking for the patient by name, and may disclose religious affiliation to members of the clergy, who are not required to ask for the individual by name.
Example: A caller asks the ED about a patient by name; the ED may confirm the patient's general condition and location under the facility directory practice, but a caller who cannot identify the patient by name receives no condition information.
Mistake to avoid: Disclosing condition and location information to callers who never identified the patient by name.
Reference: HHS Summary of the HIPAA Privacy Rule
36. CPT Guidelines Unless Medicare Is Stated
On the CEDC exam, individual payer rules are not a consideration when choosing the right answer. Unless it is specifically stated in the case note or exam question that the patient is covered by Medicare, apply the CPT coding guidelines rather than any payer-specific policy.
Example: A case note is silent on insurance; the coder answers using CPT guidelines because payer policy only enters when Medicare coverage is explicitly stated in the question.
Mistake to avoid: Applying Medicare-specific policy to exam answers when the case does not state Medicare coverage.
Reference: AAPC CEDC study guide sample
CPT Structure and Procedure Reporting
37. Sequencing Multiple Procedures by RVU
When multiple procedures are performed, CPT codes are sequenced based on the most complex or labor-intensive procedures first. The codes with the highest relative value units are sequenced first on the claim, regardless of the chronological order in which the services appear in the note.
Example: A sedated reduction and a wound repair are both performed; the reduction code is listed first because it carries the higher relative value units and greater complexity.
Mistake to avoid: Sequencing procedure codes by the order events occurred in the note rather than by RVU.
Reference: AAPC CEDC study guide sample
38. Three Documentation Verification Principles
Three general principles govern whether documentation can be thoroughly verified for billing: the documentation should be legible to someone other than the documenting physician or provider and their staff; the date of service, the name of the patient, and the name of the provider of service should be easily demonstrated by the documentation; and the documentation should support the nature of the visit and the medical necessity of the services rendered.
Example: A procedure note is filed with only illegible initials, no date, and no patient identifier; the claim is held because the record fails the identification principle, and neither the date of service nor the responsible provider can be established from the note itself.
Mistake to avoid: Billing from a note whose author, date of service, or patient cannot be easily demonstrated from the record itself.
Reference: AAPC CEDC study guide sample
39. Modifier 57 and Modifier 54 on One Encounter
Modifier 57 attaches to the E/M code when the decision to perform a major procedure, one assigned 90 global days, is made the day before or the same day as the procedure. Modifier 54 attaches to the procedure code when postoperative aftercare will be handled by another provider. They answer different questions and can appear on the same encounter: the E/M carries 57 for the decision, and the procedure carries 54 for the transferred aftercare.
Example: An ED provider evaluates a patient, decides that same day to perform closed fracture care, performs the reduction, and orthopedics will manage the follow-up: the E/M is reported with modifier 57 and the fracture code with modifier 54, because one modifier documents the decision for the major procedure and the other documents the split of the global package.
Mistake to avoid: Appending modifier 54 to the E/M or modifier 57 to the procedure code, confusing which service each modifier attaches to.
Reference: AAPC CEDC study guide sample
40. Procedure Documentation Requirements
Procedure notes must document what the provider personally performed, including approach, technique, and findings, because code selection depends on the documented service. Steps that are not documented cannot be assumed or inferred from the diagnosis or from the apparent intent of the visit.
Example: A note describes manual traction reduction of a dislocation in one attempt; the closed-reduction code is selected because the documented technique, not the diagnosis alone, defines the service.
Mistake to avoid: Selecting a procedure code from the diagnosis or implied intent rather than the documented technique.
Reference: AAPC CEDC study guide sample
41. Global Surgical Package and Aftercare
Major procedures carry a 90-day global period that bundles routine postoperative aftercare into the procedure code. When the postoperative management will be handled by another provider, the operating provider reports surgical care only by appending modifier 54 to the procedure code.
Example: An ED provider reduces a fracture with a 90-day global period and orthopedics will manage follow-up; modifier 54 is appended because the aftercare portion transfers to the outside provider.
Mistake to avoid: Reporting the full global service when another provider will deliver the postoperative aftercare.
Reference: AAPC CEDC study guide sample
42. Parentheticals and Guidelines Govern Selection
CPT parenthetical notes and subsection guidelines control code selection and pairing. A code that appears appropriate by its descriptor may be prohibited, redirected, or paired differently by a parenthetical immediately following it, so the notes surrounding a code must be read before it is assigned.
Example: A sedation pairing looks correct until a parenthetical bars its use with a code specifying anesthesia; the parenthetical wins because notes override descriptor-level assumptions.
Mistake to avoid: Skipping the parenthetical notes that prohibit or redirect the code pairing you selected.
Reference: AAPC CEDC study guide sample
Sedation, Cardiology, and Debridement Coding
43. MCS Codes When One Provider Does Both
When the same provider performs both the moderate conscious sedation and the procedure, report the initial sedation code for the first 15 minutes plus the add-on code for each additional 15 minutes. Determine who performed each element before selecting, because the performer drives code choice.
Example: An ED physician personally administers 32 minutes of moderate conscious sedation while also performing a foreign body removal from a forearm; the initial sedation code plus one add-on unit are reported because the same provider performed both the sedation and the procedure.
Mistake to avoid: Reporting sedation add-on units without confirming the treating provider also performed the sedation.
Reference: AAPC CEDC study guide sample
44. Moderate Sedation Is Not Anesthesia
Some procedure codes offer with anesthesia and without anesthesia options. The with-anesthesia choice requires general, regional, or monitored anesthesia care; moderate conscious sedation is not anesthesia, so select the without-anesthesia code and report the sedation separately.
Example: An ED provider performs closed treatment of an elbow dislocation in an adult under moderate conscious sedation with a trained observer present; the without-anesthesia closed treatment code is selected and the sedation codes are reported separately, because moderate conscious sedation does not satisfy the general, regional, or monitored anesthesia care requirement.
Mistake to avoid: Choosing the with-anesthesia procedure code when only moderate conscious sedation was used.
Reference: AAPC CEDC study guide sample
45. ECG Codes Without Modifier 26 or TC
ECG codes in the 93000 through 93010 range are differentiated by which portion of the service is being reported. Modifiers 26 and TC are not used with these codes; when reporting the ED physician's interpretation of an ECG, report the interpretation code without appending a modifier.
Example: The ED physician only interprets a tracing performed by staff; the interpretation-only ECG code is reported without modifier 26 because that code already denotes the professional portion.
Mistake to avoid: Appending modifier 26 or TC to ECG codes that already distinguish the reported portion.
Reference: AAPC CEDC study guide sample
46. Surface Debridement Versus Open-Wound Debridement
The code for debridement of extensive infected or eczematous conditions describes removal of surface skin layers, epidermis and possibly dermis, over a wide area without an open wound. The open-wound debridement code describes removal of skin and subcutaneous tissue from an open wound, including epidermis and dermis if performed.
Example: A wide infected rash without an open wound is debrided; the surface debridement code is selected because the service involved surface layers over a broad area, not open-wound tissue removal.
Mistake to avoid: Reporting the open-wound debridement code for surface debridement of a widespread rash without a wound.
Reference: AAPC CEDC study guide sample
47. Independent Observer Sedation Documentation
Moderate conscious sedation reporting depends on documentation of the sedation details, including the intraservice time and, where required, the record of an independent trained observer. The observer's documented template supports the time units billed, so verify it exists before reporting add-on units.
Example: A sedation record documents an independent trained observer and 45 minutes of intraservice time; the initial sedation code plus two add-on units are reported because the documented intraservice time, not the length of the procedure, drives the units billed.
Mistake to avoid: Billing sedation time units without the independent observer's or equivalent sedation documentation.
Reference: AAPC CEDC study guide sample
48. Sedation Excluded From Anesthesia-Specifying Codes
Moderate conscious sedation should not be reported for procedure codes that specify the service as performed with anesthesia. The anesthesia language in the code descriptor precludes separate sedation reporting, so the descriptor must be checked before appending sedation codes to any procedure.
Example: A fracture code stating with anesthesia is selected for an operating-room service; no sedation codes are added because the descriptor already includes anesthesia.
Mistake to avoid: Adding sedation codes to a procedure whose descriptor already specifies anesthesia.
Reference: AAPC CEDC study guide sample
Fracture, Dislocation, and Modifier Decisions
49. Modifier 57 for Major Procedure Decisions
When the decision to perform a major procedure is made the day before or the same day as the major procedure, report modifier 57 with the E/M code in addition to the major procedure code. Major procedures are those assigned 90 global days, with fracture care the most common major procedure in the ED.
Example: An ED provider evaluates a patient and decides same-day to perform fracture care; the E/M carries modifier 57 because the decision preceded a 90-day-global procedure.
Mistake to avoid: Using modifier 57 on an E/M leading to a minor procedure with a short global period.
Reference: AAPC CEDC study guide sample
50. Modifier 54 Surgical Care Only
When the ED provider performs the procedure but postoperative aftercare will be handled by another provider, such as orthopedics, append modifier 54 to indicate surgical care only. The global package's aftercare portion transfers to the provider who will actually manage the follow-up.
Example: A hip reduction with a 90-day global is followed by planned orthopedic follow-up; modifier 54 is appended because the aftercare portion moves to the outside provider.
Mistake to avoid: Omitting modifier 54 when documentation shows follow-up care transfers to another physician.
Reference: AAPC CEDC study guide sample
51. Open Injury Versus Open Fracture Care
Open fracture care is reported when the provider creates an opening to expose the bone, which is not performed in the ED. A patient may present with an open fracture, bone piercing the skin, yet be treated with closed care, because the treatment performed dictates the fracture care code, not the diagnosis.
Example: A bone-protruding fracture is irrigated, manually reduced, sutured, and casted in the ED; closed treatment is coded because no surgical exposure of the bone occurred.
Mistake to avoid: Coding open fracture care merely because the patient's injury was an open fracture.
Reference: AAPC CEDC study guide sample
52. Who Performed the Fracture Care
The ED provider reports a fracture care code only when documentation confirms the ED provider personally performed the treatment. If another provider, such as an orthopedist, is called to the ED to treat the fracture, the ED provider reports only the appropriate ED E/M code, and the specialist reports the fracture care.
Example: Orthopedics is called in and performs the reduction; the ED physician bills the E/M only because the fracture treatment was personally performed by the consultant.
Mistake to avoid: The ED provider billing fracture care that a consulting specialist actually performed.
Reference: AAPC CEDC study guide sample
53. Post-Arthroplasty Dislocation Code Selection
A hip dislocation in a patient with prior hip arthroplasty is coded with the closed treatment of post-hip-arthroplasty dislocation code when manually reduced, distinct from codes for a native hip. The surgical history changes the code selection, so always check for prior joint replacement in dislocation cases.
Example: A patient with a documented history of a right total hip arthroplasty dislocates that prosthetic joint while bending at home; films confirm an anterior dislocation and the ED provider reduces it with in-line traction under sedation. The closed treatment of post-hip-arthroplasty dislocation code is selected because the prior replacement redirects the choice away from native-hip reduction codes.
Mistake to avoid: Using a native-hip dislocation reduction code when the record documents prior hip arthroplasty.
Reference: AAPC CEDC study guide sample
54. GC Modifier for Resident Involvement
When a resident is involved with the care, the teaching physician appends modifier GC to indicate the service was performed in part by a resident under the teaching physician's direction. Modifier GE, used when a resident performs services without the teaching physician under the primary care exception, is not applicable in the emergency department.
Example: A resident performs part of an ED service with the teaching physician directing; modifier GC is appended because resident involvement under teaching supervision triggers GC.
Mistake to avoid: Appending GE in the emergency department, where the primary-care-exception modifier does not apply.
Reference: AAPC CEDC study guide sample
Privacy, Compliance, and Professional Conduct
55. PHI Scope Across All Media
Protected health information is individually identifiable health information held or transmitted by a covered entity or its business associate in any form or medium, whether electronic, paper, or oral, including demographic data relating to health, care, or payment. Oral statements about patients are covered, not just written or electronic records.
Example: A staff member discusses a patient's condition aloud in a crowded ED hallway; the conversation involves PHI because the rule protects oral as well as written and electronic forms.
Mistake to avoid: Assuming only electronic or written records qualify as protected health information.
Reference: HHS Summary of the HIPAA Privacy Rule
56. Treatment, Payment, and Operations Uses
A covered entity may use and disclose PHI without individual authorization for treatment, payment, and health care operations. Consent for these purposes is optional under the rule, and disclosure to another health care provider for the patient's treatment, including consultation and referral, is expressly permitted.
Example: The ED sends records to the patient's admitting hospitalist for continued care; no authorization is needed because treatment disclosure to another provider is permitted.
Mistake to avoid: Delaying provider-to-provider treatment disclosures while waiting for a signed authorization.
Reference: HHS Summary of the HIPAA Privacy Rule
57. Minimum Necessary Standard
Covered entities must make reasonable efforts to use, disclose, and request only the minimum PHI needed for the intended purpose, supported by role-based access policies. The standard does not apply to treatment disclosures, disclosures to the individual, or uses made pursuant to an authorization.
Example: A billing query for a single encounter's codes is limited to that visit's information because the minimum necessary rule bars sending the whole record without specific justification.
Mistake to avoid: Releasing an entire medical record when only the specific encounter's information is needed.
Reference: HHS Summary of the HIPAA Privacy Rule
58. Business Associate Agreements
A business associate is a person or organization outside the covered entity's workforce that performs functions involving PHI on the entity's behalf, such as claims processing, data analysis, or billing. A written agreement imposing specified safeguards is required before PHI is shared for those services.
Example: An outside billing company processes the ED's claims; a business associate agreement is executed because the contractor's services involve PHI use on the entity's behalf.
Mistake to avoid: Sharing PHI with a claims-processing vendor without a signed business associate agreement.
Reference: HHS Summary of the HIPAA Privacy Rule
59. Privacy Notice in Emergency Treatment
Direct treatment providers must deliver the notice of privacy practices at the first service encounter and make a good-faith effort to obtain written acknowledgement. In emergency treatment situations, the provider furnishes the notice as soon as practicable after the emergency abates and is relieved of requesting acknowledgement during the emergency.
Example: An unconscious trauma patient cannot receive or acknowledge the notice; the ED delivers it once the patient can engage because emergency treatment postpones the notice obligation.
Mistake to avoid: Forgoing the notice entirely for emergency patients instead of providing it once the emergency abates.
Reference: HHS Summary of the HIPAA Privacy Rule
60. Personal Representatives and Minors
A personal representative legally authorized to make health decisions for an individual, including most parents for minor children, is treated as the individual for uses, disclosures, and rights. Exceptions exist where the entity reasonably believes the representative may abuse or endanger the patient, and state law governs certain minor-record situations.
Example: A parent requests a minor's ED records; access is generally granted because parents are personal representatives, unless state law or safety concerns carve out the situation.
Mistake to avoid: Treating every parental request for a minor's records identically without checking exceptions and state law.
Reference: HHS Summary of the HIPAA Privacy Rule
References and further reading
Source links checked on Oct 2, 2026.