M84.649A vs M84.649G
M84.649A (Pathological fracture in other disease, unspecified hand, initial encounter for fracture) compared with M84.649G (Pathological fracture in other disease, unspecified hand, subsequent encounter for fracture with delayed healing), from the official CMS tabular data.
Current data releases:ICD-10-CM FY2027 · ICD-10-PCS FY2027 · HCPCS October 2026 · MS-DRG v44 · Medicare Code Editor v44.0 · NCCI PTP Q4 2026 · MUE Q4 2026 · NCD code lists 2026-01 · LCD export September 28, 2026 · All releases and sources
Summary
No tabular note links these codes. Both belong to category M84, and nothing in the tabular list prevents reporting each when it is documented.
Registry fact- What is different?
Title wording.The titles share “Pathological fracture in other disease, unspecified hand”; M84.649A says “initial encounter for fracture” where M84.649G says “subsequent encounter for fracture with delayed healing”.
Registry fact
Nothing found in 7 other checks
- Can these codes be reported together?
No instruction prevents it.No note in either entry names the other. Both belong to category M84; each may be reported when its own documentation is present.
Registry fact
- Is there an Excludes1 relationship?
None.Neither entry carries an Excludes1 note that names the other code. M84.649A carries 1 Excludes1 note and M84.649G carries 1 Excludes1 note covering other codes; the side-by-side table quotes them.
Official rule
- Is there an Excludes2 relationship?
None.Neither entry carries an Excludes2 note that names the other code. M84.649A carries 1 Excludes2 note and M84.649G carries 1 Excludes2 note covering other codes; the side-by-side table quotes them.
Official rule
- Is one more specific?
No.Both titles are unspecified forms within category M84, and neither is a subdivision of the other.
Registry fact
- Is one a parent or header code?
No.Both are billable codes, and neither contains the other.
Registry fact
- Are there sequencing instructions?
None.Neither entry carries a Code First or Use Additional Code note that names the other.
Official rule
- Are there other coding relationships?
None found.No laterality, encounter-phase, Table of Neoplasms, Table of Drugs and Chemicals, or history-versus-active-disease relationship links these codes.
MedCoder-derived
Official rule: a tabular instructional note or a section of the ICD-10-CM Official Guidelines, quoted as published. Registry fact: the codes’ own published attributes (titles, billable status, position in the hierarchy, code set). MedCoder-derived: a reading MedCoder computes from those facts; it is not itself a rule. How to read the labels
Can these codes be reported together?
Yes, when each is documented. M84.649A and M84.649G both belong to category M84.
No Excludes1/Excludes2 relationship exists between these codes in the official tabular list. The code titles state what each one covers, and the documentation decides which applies.
Side by side
Similar descriptions do not make codes interchangeable. The documentation and the official instructions decide which code applies.
Pathological fracture in other disease, unspecified hand, initial encounter for fracture
Pathological fracture in other disease, unspecified hand, subsequent encounter for fracture with delayed healing
- pathological fracture in osteoporosis (M80.-)
- traumatic fracture of bone-see fracture, by site
- underlying condition
M84 Disorder of continuity of bone
M00-M99 — Diseases of the Musculoskeletal System and Connective Tissue (M00-M99)
- The appropriate 7th character is to be added to each code from subcategory M84.6:
No Code first, Use additional code and Includes note at either code.
Notes are the code’s own tabular entry, quoted as published. A note that names the other code is the one the verdict above rests on. In a row that differs, each code’s own notes are listed under it, and the notes every code shares are listed once beneath them.
Derived from the official CMS ICD-10-CM tabular data (FY2027). A coding-rule comparison, not billing advice: payer-specific edits and medical-necessity policy are outside its scope. All data sources