🧬 ICD-10 CM H33.029 — Retinal Detachment with Multiple Breaks, Unspecified Eye
Billable Code Confirmed
ICD-10 CM H33.029 is a complete 6-character code, combining the H33.02 subcategory (multiple breaks) with the “9” laterality character indicating the affected eye was not specified in the documentation.⁵ Despite the unspecified laterality, this code carries full billing validity and does not require any further extension.⁵
Non-Billable Parent Codes
H33.02 (Retinal detachment with multiple breaks) is non-billable on its own because it omits laterality entirely and always requires a 6th character (right, left, bilateral, or unspecified) before submission.⁶ H33.0 (Retinal detachment with retinal break) sits one level higher and is non-billable at every point until it drills down through a break-subtype subcategory like H33.02.⁷ H33 (Retinal detachments and breaks) is the top-level non-billable header for this entire code family and cannot be used for any claim.⁷
Clinical Context
The clinical distinction driving H33.029 selection is that the provider documented multiple discrete retinal breaks (as opposed to a single break, giant tear, or dialysis) causing the detachment, but did not specify which eye was affected in the note.⁸ Unspecified-eye codes should be used sparingly in ophthalmology documentation, since laterality is almost always determinable on exam and payers may flag repeated use of unspecified codes as a documentation quality issue.⁸
Code Classification
ICD-10 CM H33.029 is a diagnosis code under ICD-10-CM, not a procedure code, and it classifies an acute structural retinal condition that frequently necessitates urgent surgical intervention rather than describing any treatment itself.⁹
🔍 Code Description
ICD-10 CM H33.029 describes a rhegmatogenous retinal detachment in which the neurosensory retina separates from the underlying retinal pigment epithelium due to fluid passing through more than one full-thickness retinal break, with the affected eye not specified in the encounter documentation. This mechanism differs fundamentally from H33.2- serous retinal detachment, where fluid accumulates beneath the retina without any actual break in the tissue — a distinction that determines urgency, since rhegmatogenous detachments with breaks progress rapidly toward vision loss and typically require surgery within 24-72 hours, while serous detachments are often managed medically first.
Multiple breaks specifically (as opposed to the single-break code H33.01 or giant-tear code H33.03) usually indicate more extensive peripheral retinal pathology, such as widespread lattice degeneration or significant trauma, and often correlate with a higher risk of proliferative vitreoretinopathy and surgical failure. Surgeons commonly repair this condition with pars plana vitrectomy, scleral buckling, or a combination of both, and the choice of technique is frequently documented in the operative note alongside the specific breaks identified intraoperatively. Coders should always attempt to identify laterality from the exam, imaging, or operative report before defaulting to the unspecified-eye code, since accurate laterality is essential for surgical scheduling, prior authorization, and any future bilateral-episode tracking.
🌳 Code Tree / Hierarchy
H33 Retinal detachments and breaks ❌ Non-billable
│
├── H33.0 Retinal detachment with retinal break ❌ Non-billable
│ │
│ ├── H33.00 Unspecified retinal detachment with retinal break ❌ Non-billable (requires laterality)
│ ├── H33.01 Retinal detachment with single break ❌ Non-billable (requires laterality)
│ │
│ ├── H33.02 Retinal detachment with multiple breaks ❌ Non-billable
│ │ │
│ │ ├── H33.021 Retinal detachment with multiple breaks, right eye ✅ Billable
│ │ ├── H33.022 Retinal detachment with multiple breaks, left eye ✅ Billable
│ │ ├── H33.023 Retinal detachment with multiple breaks, bilateral ✅ Billable
│ │ └── H33.029 Retinal detachment with multiple breaks, unspecified eye ◀ THIS CODE ✅ Billable
│ │
│ ├── H33.03 Retinal detachment with giant retinal tear ❌ Non-billable (requires laterality)
│ ├── H33.04 Retinal detachment with retinal dialysis ❌ Non-billable (requires laterality)
│ └── H33.05 Total retinal detachment ❌ Non-billable (requires laterality)
│
├── H33.1 Retinoschisis and retinal cysts ❌ Non-billable
│
└── H33.2 Serous retinal detachment ❌ Non-billable
Multiple Breaks vs. Single Break Specificity
Selecting H33.029 (or its laterality-specific siblings) over H33.011 or H33.012 matters because “multiple breaks” signals more extensive retinal pathology to the surgical team and payer, often supporting medical necessity for combined vitrectomy-buckle procedures rather than a simpler single-break repair.¹⁰
Tip
Always review the retina specialist’s exam or operative note before defaulting to the “9” unspecified-eye character — laterality is documented in nearly every ophthalmology encounter, and defaulting to unspecified when the chart actually supports right or left eye is a preventable specificity gap.¹¹
✅ Includes
- Rhegmatogenous retinal detachment involving two or more distinct retinal breaks, laterality not documented.
- Retinal detachment with multiple tears identified on fundus exam or B-scan ultrasound, eye not specified.
- Acute retinal separation from multiple full-thickness breaks pending laterality confirmation.
❌ Excludes
Excludes 1
H33.22, H33.21, H33.20, and other H33.2- codes (Serous retinal detachment) are excluded here because serous detachment occurs without any actual retinal break — it’s a fundamentally different fluid-accumulation mechanism that should never be coded alongside a break-associated detachment for the same event.¹² H35.72-/H35.73- (Detachment of retinal pigment epithelium) are excluded because RPE detachment involves separation of a different anatomic layer than the full-thickness neurosensory retinal break captured by H33.029.¹³
Danger
The most common Excludes1 error occurs when a coder sees both “retinal detachment” and “serous component” mentioned in the same complex retinal exam note and codes both H33.02- and H33.2- together, when the documentation usually supports only one true underlying mechanism — clarify with the provider or operative report before dual-coding.¹²
Excludes 2
There is no standard Excludes2 pairing commonly reported alongside H33.029, since retinal detachment with multiple breaks is typically the primary and defining diagnosis for the encounter; however, coders may separately report H35.71 (proliferative vitreoretinopathy with retinal detachment) when documented as a distinct complicating process alongside the detachment itself.¹⁴
📋 Clinical Overview
Break Count and Laterality Specificity
Retinal detachment coding hinges on two key variables: how many retinal breaks are present, and which eye is affected. This table compares H33.029 to its more common laterality-specific siblings and the single-break alternative.
| Feature | H33.029 | H33.022 | H33.012 |
|---|---|---|---|
| Laterality Documentation | Eye affected is not specified in the encounter documentation, often due to incomplete transcription or an early triage note preceding full exam. | Left eye is clearly documented as the affected side based on exam or operative findings. | Left eye documented, but only a single retinal break identified rather than multiple. |
| Surgical Complexity Implication | Cannot be used to infer complexity since laterality gaps often coincide with incomplete break-count documentation too. | Multiple breaks typically indicate more extensive peripheral pathology, often prompting combined vitrectomy-buckle repair. | Single-break detachments are frequently amenable to simpler pneumatic retinopexy or focal buckle repair. |
| CDI Query Priority | High priority for a laterality query, since nearly all ophthalmology exams document which eye is affected. | No query needed — laterality is already fully specified. | No query needed — laterality is already fully specified. |
Important
A CDI trigger here is any ophthalmology note using “retinal detachment, multiple breaks” without eye specification — this is almost always determinable from the same encounter’s exam findings, so query the provider rather than defaulting to H33.029 whenever possible.¹⁵
Manifestations & Symptom Burden
- Sudden onset of floaters, described by patients as “cobwebs” or dark spots moving through the visual field.
- Flashes of light (photopsia), particularly noticeable in peripheral vision or in dim lighting.
- A progressive curtain-like or shadow effect obscuring part of the visual field, often starting peripherally and advancing centrally.
- Painless, acute vision loss or blurring, sometimes described as looking through a “wavy” or distorted lens.
- Loss of central visual acuity if the detachment progresses to involve the macula (macula-off presentation), which significantly worsens visual prognosis.
Tip
Macula-involving status (“macula-on” vs. “macula-off”) isn’t captured by a separate ICD-10-CM character but is a critical clinical detail that should still be abstracted into the coding summary or CDI note, since it heavily influences surgical urgency and expected visual outcome documentation.¹⁶
💰 HCC Risk Adjustment
| Attribute | Value |
|---|---|
| HCC Category | N/A — Not HCC-Mapped |
| RAF Impact | None |
| Annual Capture Required | No |
ICD-10 CM H33.029 carries no CMS-HCC or RxHCC weight, meaning its presence or absence on a claim has zero effect on a patient’s risk adjustment factor score.¹⁷ This diagnosis is treated purely as an acute surgical episode rather than a chronic condition warranting risk-adjustment tracking, so coders should focus documentation efforts on medical necessity and surgical authorization support rather than annual HCC recapture strategy.¹⁷
🏥 MS-DRG Assignment
| Attribute | Value |
|---|---|
| DRG with MCC | N/A — Driven by procedure code when surgery performed |
| DRG with CC | N/A — Driven by procedure code when surgery performed |
| DRG without CC/MCC | DRG 124-125 — Other Disorders of the Eye (when managed without an OR procedure) |
When a patient is admitted specifically for surgical repair of this detachment, the ICD-10-PCS procedure code for the vitrectomy or scleral buckle — not the diagnosis code itself — becomes the primary MS-DRG driver, typically grouping to a surgical ophthalmology DRG.¹⁸ If the detachment is instead managed without an inpatient OR procedure (rare, but possible in complex medical comorbidity cases), the encounter would group to the medical eye disorder DRG range (124-125) based on CC/MCC status of secondary diagnoses.¹⁸
🔗 Related ICD-10-CM Codes
Retinal Detachment with Break Family
- H33.021 — Retinal detachment with multiple breaks, right eye
- H33.022 — Retinal detachment with multiple breaks, left eye
- H33.023 — Retinal detachment with multiple breaks, bilateral
- H33.019 — Retinal detachment with single break, unspecified eye
- H33.039 — Retinal detachment with giant retinal tear, unspecified eye
- H33.059 — Total retinal detachment, unspecified eye
Associated Retinal Pathology
- H33.20 — Serous retinal detachment, unspecified eye
- H35.71 — Proliferative vitreoretinopathy with retinal detachment
- H43.10 — Vitreous hemorrhage, unspecified eye
- H33.30 — Retinal breaks without detachment, unspecified
🛠️ Commonly Associated CPT Codes
- 67108 — Repair of retinal detachment with vitrectomy; the most common surgical CPT paired with multiple-break detachment repair, especially when combined with scleral buckling.
- 67107 — Repair of retinal detachment with scleral buckling; used when the surgeon opts for external buckle repair alone rather than a vitrectomy approach.
- 67101 — Repair of retinal detachment with cryotherapy or diathermy; occasionally reported for simpler cases, though multiple-break detachments more often require vitrectomy-level intervention.
- 92225/92226 — Extended ophthalmoscopy with retinal drawing; frequently billed at the diagnostic encounter to document the location and number of breaks prior to surgical planning.
NCCI Bundling Considerations
CPT 67108 (vitrectomy repair) typically bundles diagnostic extended ophthalmoscopy codes performed on the same date as the surgery itself, so 92225/92226 should generally be reported only at the initial diagnostic visit rather than the operative date.¹⁹ When both scleral buckling (67107) and vitrectomy (67108) are performed in the same operative session, most payers expect a single combined procedure code rather than separate line items, so coders should verify operative documentation supports distinct, separately reportable techniques before unbundling.¹⁹
🔬 ICD-10-PCS Crosswalk
When this diagnosis results in an inpatient surgical repair, the most relevant PCS codes fall under the Eye body system with root operation Repair or Drainage, such as 08NX3ZZ (Release of right eye vitreous, percutaneous approach) or a comparable retina-specific code depending on the exact technique. Because the ICD-10-CM code itself carries no procedural information, coders must always cross-reference the actual operative report to select the correct root operation, approach, and device characters for the PCS code rather than inferring it from the diagnosis alone.
💊 Coding Scenarios and Examples
Scenario 1: A patient presents to the emergency department with acute onset of floaters and a curtain-like shadow in the peripheral vision. Emergency ophthalmology consult documents “retinal detachment, multiple breaks noted on exam” but the note does not clearly state which eye was examined due to a transcription gap in the urgent consult documentation.
- Correct coding: H33.029
- Sequencing: Reported as principal diagnosis for this emergent encounter since it’s the primary reason for the ED visit and consult.
- CDI note: Query the ophthalmologist to confirm laterality before final code assignment, since ED documentation gaps like this are usually resolvable with a quick chart addendum.
Scenario 2: A 68-year-old man undergoes urgent pars plana vitrectomy with scleral buckling for a right-eye retinal detachment with three distinct breaks identified intraoperatively, following a comprehensive dilated exam the prior day that clearly documented laterality.
- Correct coding: H33.021, 67108
- Sequencing: The laterality-specific diagnosis code is reported first, followed by the vitrectomy repair CPT code capturing the surgical intervention.
- CDI note: No query needed here — this scenario demonstrates why H33.029 should be reserved only for true documentation gaps, since laterality was clearly available in this chart.
Scenario 3: A patient with known bilateral lattice degeneration develops sudden vision loss, and the on-call ophthalmologist’s initial phone note states “likely retinal detachment, multiple breaks, will confirm eye on morning exam,” with the formal exam note completed the following day confirming left eye involvement.
- Correct coding: H33.022 (once the follow-up exam confirms laterality)
- Sequencing: The coder should hold the chart pending the confirmatory exam note rather than finalizing H33.029 prematurely from the incomplete phone note alone.
- CDI note: This scenario illustrates why coders should always review the full encounter timeline before finalizing an unspecified-laterality code when a same-stay confirmatory note is pending.
⚠️ Coding Pitfalls and Tips
- Pitfall 1: Defaulting to H33.029 when a same-encounter exam or operative note actually specifies laterality elsewhere in the chart — always review the full record, not just the initial triage note.
- Pitfall 2: Forgetting that the parent codes H33.02, H33.0, and H33 are all non-billable and will trigger a claim rejection if submitted without full 6th-character specificity.
- Pitfall 3: Coding H33.2- (serous detachment) alongside H33.029 without confirming the documentation truly supports two distinct mechanisms rather than describing the same detachment event twice.
- Pitfall 4: Missing the connection between break-count documentation and surgical CPT selection — multiple-break detachments often justify combined vitrectomy-buckle procedures, so verify the operative note matches the diagnosis complexity.
- Pitfall 5: Assuming H33.029 carries any HCC or RAF weight — it does not, so don’t prioritize annual recapture of this code for risk-adjustment revenue purposes.
- Pitfall 6: Billing extended ophthalmoscopy (92225/92226) on the same date as the vitrectomy repair without confirming it isn’t bundled under NCCI edits for that operative date.