ICD-10 code O01.1: Incomplete and partial hydatidiform mole

Key takeaways

ICD-10 code O01.1 is the billable ICD-10-CM code for incomplete and partial hydatidiform mole, and it took effect October 1, 2025.

The O01 category has three billable codes: O01.0 for a complete mole, O01.1 for a partial mole, and O01.9 when the type isn’t specified.

Coders need pathology confirmation of a partial or incomplete mole before assigning O01.1 instead of the unspecified O01.9.

O01.1 is not POA exempt, so hospitals must report present-on-admission status for it on every inpatient claim.

A pathology result of chorioadenoma destruens or malignant mole (D39.2) excludes O01.1 entirely under the category’s Excludes1 note.

ICD-10 code O01.1 is the billable ICD-10-CM code for incomplete and partial hydatidiform mole. It describes a molar pregnancy where trophoblastic tissue overgrows alongside some fetal tissue.

It sits in the O00-O08 range for pregnancy with an abortive outcome, and the 2026 ICD-10-CM edition took effect on October 1, 2025.

Most molar pregnancy coding errors don’t happen at diagnosis. They happen at the specificity stage, when a provider documents “molar pregnancy” without saying whether the mole is complete or partial. Coders then default to the unspecified O01.9, and that default costs reimbursement accuracy and invites a payer audit.

Getting the partial-versus-complete call right, and documenting it, keeps the chart, the code, and the claim aligned. Practices charting in OB/GYN EMR software that ties pathology and ultrasound results to the same encounter make that call easier to support. Here’s how to make the distinction and document it correctly.

The core billing details for ICD-10 code O01.1

Here’s the core reference data coders and billers need before submitting a claim with O01.1.

How a partial mole differs from a complete mole

A partial mole carries some fetal tissue and a triploid karyotype. A complete mole has neither, and its genetic material is entirely paternal. That distinction, confirmed by pathology, decides whether a claim uses O01.1 or O01.0.

Both types fall under hydatidiform mole, an abnormal pregnancy where trophoblastic tissue proliferates without a viable ongoing pregnancy. They sit within the broader category of gestational trophoblastic disease (GTD), and the complete-versus-partial call is what routes the ICD-10-CM code.

• Partial mole features: triploid complement (69, XXX or 69, XXY), fetal red blood cells or fetal parts, and focal trophoblastic swelling with villous scalloping
• Complete mole features: diploid karyotype, entirely paternal genetic origin, diffuse trophoblastic hyperplasia, no fetal tissue present
• Clinical presentation (both types): vaginal bleeding, uterine size/date discrepancy, elevated beta-hCG, diagnosis confirmed by ultrasound and pathological examination of evacuated tissue

Partial moles carry a lower risk of developing into persistent gestational trophoblastic neoplasia than complete moles, per the American College of Obstetricians and Gynecologists (ACOG). Follow-up with serial beta-hCG monitoring remains standard care either way. That complete-versus-partial call rests on pathological confirmation, not imaging findings alone.

What the O01 category’s coding notes require

ICD-10 code O01.1 sits within parent category O01, which spans the full range of hydatidiform mole diagnoses. Two Tabular List notes govern how coders use it, and mixing them up is a common miscoding trap. Verify both against the CDC/NCHS ICD-10-CM web tool for the current edition.

• Excludes1 (O01, applies to every subcode): Chorioadenoma destruens (D39.2); malignant hydatidiform mole (D39.2). Coders cannot use these codes with O01.0, O01.1, or O01.9 – they describe a mutually exclusive, more specific condition.
• Includes note (O01.9 only): Trophoblastic disease NOS; vesicular mole NOS. This term sits under the unspecified subcode alone, so it does not extend to O01.0 or O01.1.

The Excludes1 note is a hard coding rule. When a provider documents chorioadenoma destruens or a malignant transformation, coders must use D39.2, not ICD-10 code O01.1. Read every Excludes1 note before finalizing an O01 code. Missing one is an easy way to submit two codes that should never appear on the same claim.

Choosing between O01.0, O01.1, and O01.9

Default to O01.9 only when the pathology report genuinely doesn’t specify complete or partial. The most common error in this category is reaching for O01.9 the moment a provider writes “molar pregnancy.” Coders default there without checking whether a pathology result already answers the question.

Per the CMS ICD-10-CM Official Guidelines for Coding and Reporting, coders should query the provider whenever documentation is ambiguous. That’s especially true when the specificity between O01.1 and O01.9 is determinable from the available test results. Querying before defaulting to unspecified protects both reimbursement accuracy and the medical record.

What the chart needs before you code O01.1

O01.1 needs five supporting elements in the chart before a coder can assign it over O01.9. Missing any one of them is the single biggest reason O01.9 gets over-used in gynecologic practices. Using digital intake forms and structured clinical templates at the point of care catches most of this early, well before the claim is submitted.

The following five elements support O01.1 assignment. Each one should already be in the record before the code is finalized.

• Pathology report: Histological confirmation explicitly stating “partial mole,” “incomplete mole,” or equivalent language. A triploid karyotype finding or fetal red blood cells on the report add strong support.
• Ultrasound report: Findings consistent with partial mole (heterogeneous uterine contents, a partial “snowstorm” pattern, a possible gestational sac remnant). Ultrasound alone can’t support code assignment without pathology behind it.
• Provider attestation: The treating physician’s or midwife’s clinical impression should match the final histology result. A provider query is warranted when the attending’s notes and the pathology report disagree.
• Beta-hCG levels: Serial measurements that establish trophoblastic activity support the molar pregnancy diagnosis. Rising or elevated beta-hCG after evacuation can trigger additional follow-up codes.
• Procedure documentation: Operative notes for uterine evacuation or suction curettage should record the tissue type removed and how it correlates with the pathology findings.

Coders following HIPAA-compliant documentation practices should confirm every supporting record is retrievable within the EHR before the coded claim goes out. Missing pathology results at the time of initial coding are the main driver of O01.9 over-use in gynecologic practices.

The World Health Organization‘s ICD-10 classification confirms O01.1’s place within the O01 category as a distinct, billable entity that requires histological specificity.

How sequencing and POA rules apply to molar pregnancy encounters

The ICD-10-CM Official Guidelines for Coding and Reporting set the sequencing rules for O01.1 encounters. CMS and the National Center for Health Statistics (NCHS) co-maintain them. Getting sequencing right affects DRG assignment, POA reporting, and claim integrity.

When O01.1 is sequenced as the principal diagnosis

O01.1 is the principal diagnosis for inpatient encounters where the patient is admitted to manage an incomplete hydatidiform mole. Any complication codes, covered in the next section, are sequenced as secondary diagnoses.

How outpatient encounters sequence O01.1

In outpatient settings, the code representing the reason for the encounter goes first. For a follow-up visit after uterine evacuation, O01.1 stays the primary diagnosis code. Coders apply the same sequencing logic in other reproductive health billing, like IVF CPT codes.

Why O01.1 requires POA reporting

O01.1 is not POA exempt. The CMS/CDC FY2026 POA Exempt Code list doesn’t include any code in the O00-O08 range. Hospitals must therefore report present-on-admission status for O01.1 on every applicable inpatient claim. Confirm this against the current CMS POA Exempt List each year, since the list is rebuilt with every ICD-10-CM edition.

Why O01.1 skips trimester qualifiers

O01.1 carries no trimester subclassification. A molar pregnancy is, by definition, a non-viable outcome, so the trimester structure used for codes like O21.x or O60.x doesn’t apply here. No additional trimester code is needed.

Which additional codes capture O01.1 complications

Incomplete molar pregnancies often come with complications that need their own ICD-10-CM codes alongside O01.1. Each one, such as O08.3 for shock, gets its own code only when it meets UHDDS criteria for clinical significance. That means it required added treatment or monitoring during the encounter.

Code every complication that meets UHDDS (Uniform Hospital Discharge Data Set) criteria for secondary diagnosis. That means clinical evaluation, added therapeutic treatment, or a diagnostic procedure during the encounter. Skip conditions that were monitored but didn’t change management.

What payers check before reimbursing O01.1

O01.1 is billable and valid for submission to Medicare and commercial payers alike. Coverage policy for molar pregnancy management still varies by payer. Coders shouldn’t assume universal coverage without checking claims management workflows against the applicable Local Coverage Determinations (LCDs) and National Coverage Determinations (NCDs).

What proves medical necessity for O01.1

Payers want the record to show medical necessity for the procedure performed, such as suction curettage or uterine evacuation. They also want objective findings behind the diagnosis code. A pathology report is the strongest document for O01.1. Beta-hCG trends, ultrasound reports, and operative notes should all be retrievable from the chart.

How O01.1 affects DRG assignment

For inpatient encounters, O01.1 coded as the principal diagnosis maps to obstetric DRGs under MDC 14 (Pregnancy, Childbirth, and Puerperium). The exact DRG depends on the complications coded alongside it. Accurately documented complications raise the DRG weight and the reimbursement that follows.

The most common reasons O01.1 claims get denied

Mismatched procedure-to-diagnosis codes trigger most molar pregnancy claim denials. The evacuation code, typically CPT 59812, has to line up with an obstetric diagnosis that actually supports it.

Excludes1 conflicts cause the rest. If pathology comes back D39.2 for malignant hydatidiform mole, O01.1 has to be replaced outright. It can’t be submitted next to D39.2.

Run through a short check before you submit:

• Does the pathology report support O01.1 over O01.9?
• Does the evacuation code match the diagnosis on the claim?
• Are there any Excludes1 conflicts left unresolved?

The AAPC ICD-10-CM code reference is a useful cross-check for O01.1 pairings against procedure codes.

How Pabau supports accurate ICD-10-CM coding for gynecologic practices

Accurate O01.1 coding depends on what’s captured at the point of care, not on what happens at the billing desk. Practices that record histological findings, procedure notes, and provider attestations in a structured clinical record reach a clean claim faster.

Practice management software like Pabau brings clinical record management into that same workflow. OB/GYN and fertility teams can build structured encounter templates that prompt for the exact documentation O01.1 needs: procedure type, pathology correlation, and complication monitoring notes. That structure is what keeps O01.9 from becoming the default.

• Digital forms: Structured intake and post-procedure data feed straight into the patient record, cutting reliance on free-text notes that are harder to code accurately.
• Claims management: Pabau’s claims management software keeps required submission fields, documentation, and claim status together in one dashboard. Missing information surfaces before a claim goes out, not after a denial.
• Multi-provider coordination: When pathology results land after the first coding pass, Pabau’s record update workflows support late-entry code amendments without disturbing the original encounter documentation.

Gynecologic practices using fertility clinic software with integrated coding support see fewer coding queries and faster claims resolution. A standardized medical forms approach means coders already have what they need before the chart is finalized.

Documentation that holds up when O01.1 is audited

Pabau's clinical record tools help OB/GYN and fertility practices capture the histological and procedural detail that keeps ICD-10 code O01.1 defensible at audit, so claims move faster and denials drop.

Book a demo

Conclusion

Molar pregnancy coding comes down to one question: does the record support specificity? O01.1 is the right code when pathology confirms an incomplete or partial hydatidiform mole. Without that confirmation, O01.9 is the defensible choice until a provider query or a late pathology result settles it.

Practices that build documentation capture into the clinical workflow, instead of chasing it after the fact, land more accurate codes on first submission. Pabau’s structured clinical records and digital forms give gynecologic and fertility teams the documentation trail that makes ICD-10-CM specificity achievable at the point of care.

Book a demo to see how Pabau supports accurate molar pregnancy coding from the first encounter.

Continue your research

Need the anesthesia billing rules for another obstetric procedure? CPT 00842 covers anesthesia for amniocentesis, a related prenatal diagnostic procedure.

Coding other gynecologic diagnoses in the same practice? N83.8 covers other noninflammatory disorders of the ovary, a common companion diagnosis on gynecologic charts.

Billing anesthesia for a delivery instead? CPT 01968 is the add-on code for cesarean delivery anesthesia.

Need the code for a related pelvic infection diagnosis? N74 covers female pelvic inflammatory disorders classified elsewhere.

Coding a patient after their molar pregnancy has resolved? O94 applies to sequelae of a completed pregnancy complication.

Frequently asked questions