A fracture diagnosis needs a seventh character for encounter type, but the record is unclear whether this is the initial or a subsequent encounter. What should the coder do?

When a fracture diagnosis needs a seventh character for encounter type but the record is unclear whether this is the initial or a subsequent encounter, the coder should obtain documentation of the encounter phase before assigning the seventh character rather than guessing. Seventh characters are required for valid traumatic fracture coding in civic inpatient and outpatient settings. Defaulting to initial encounter for any fracture treated in the hospital fails when the encounter may be subsequent active treatment. Omitting the seventh character and submitting an incomplete ICD-10-CM code fails reporting validity. Always using subsequent encounter because inpatient stays follow the ER visit fails as an automatic rule that ignores clinical encounter-phase definitions. Exam caveat: clarify initial versus subsequent (and other seventh-character meanings) from documentation; do not guess or omit. Operational check: review ED, ortho, and discharge documentation at the county facility for encounter phase, query when unclear, then assign the seventh character. Educate that inpatient timing after ED does not automatically equal subsequent encounter. In municipal and county facility practice, record the rationale for the chosen coding path and the rejected alternatives in the abstract notes so auditors and future coders understand the clinical and compliance basis. Re-check the decision if new authenticated documentation arrives before final bill drop, and escalate persistent documentation gaps to CDI or compliance rather than normalizing unsupported shortcuts that would distort civic claims, quality metrics, or case-mix reporting.