ICD-10 code O76: Fetal heart rate abnormality in labor and delivery

Key Takeaways

ICD-10 code O76 is a billable ICD-10-CM diagnosis code for abnormality in fetal heart rate and rhythm complicating labor and delivery, valid for FY2026 claims submission

O76 applies to fetal bradycardia, fetal tachycardia, and late or variable decelerations identified via electronic fetal monitoring during active labor — not antepartum findings

O76 is distinct from O36.83: Use O76 for intrapartum fetal heart rate abnormalities and O36.83 for fetal heart rate or rhythm abnormalities (including tachycardia) diagnosed during pregnancy before labor onset

Pabau’s structured patient records and digital documentation tools help obstetric teams capture the EFM findings and physician attestation that support accurate O76 coding

What is ICD-10 code O76?

ICD-10 code O76 is the ICD-10-CM diagnosis code for abnormality in fetal heart rate and rhythm complicating labor and delivery. It is a billable, specific code valid for submission on claims under the CMS ICD-10 coding guidelines and is included in the FY2026 ICD-10-CM tabular list without revision or deletion since its introduction in October 2015.

The code sits within ICD-10-CM Chapter 15 (Pregnancy, childbirth and the puerperium) under the block O60-O77, which covers complications of labor and delivery. Because O76 is a single, non-expanded code with no subclassifications, coders apply it directly when a fetal heart rate abnormality is documented during active labor or the delivery encounter.

The timing criterion is strict: EFM findings identified before the onset of labor are coded differently.

Official code description and classification

The table below summarizes the key administrative facts coders need to verify O76 before claim submission. Cross-reference against the official CDC/NCHS ICD-10-CM lookup for the most current annual release.

Coders working in obstetric billing should also consult the AAPC’s ICD-10-CM code search for crosswalk references and coding tips aligned with current guidelines. Similar coding logic applies across obstetric specialties, as our article on O71.9 illustrates for a different labor and delivery complication.

Conditions included under O76 (applicable to notes)

The ICD-10-CM tabular list provides “Applicable To” notes that specify which clinical scenarios fall under O76. These are not exhaustive clinical definitions but official coder guidance on conditions the code is designed to capture.

Fetal bradycardia and O76

Fetal bradycardia during active labor maps to ICD-10 code O76 when the physician documents a sustained low baseline (typically below 110 beats per minute) on the electronic fetal monitoring strip.

The documentation must establish that the finding occurred during labor, not prior to its onset. Prolonged decelerations dropping to bradycardic levels and lasting more than two minutes also support O76 when identified intrapartum.

For obstetric teams using digital clinical documentation forms, structured EFM note templates help ensure the timing and pattern are captured in a way that coders can act on directly.

Fetal tachycardia and O76

Fetal tachycardia occurring during labor or delivery is coded with ICD-10 code O76. The critical distinction here is timing: If the elevated baseline (generally above 160 bpm) was first identified during the antepartum period before labor began, the code changes to O36.83 (maternal care for abnormalities of the fetal heart rate or rhythm).

When tachycardia is documented for the first time on the labor and delivery floor, O76 is correct. Physician documentation must clearly state that the finding emerged or was first noted during the labor encounter.

Fetal heart rate decelerations and O76

Late and variable decelerations are the most common reason O76 appears on labor and delivery claims. According to the WHO ICD-10 classification, these intrapartum findings fall squarely within the scope of fetal heart rate abnormalities complicating delivery.

Late decelerations are particularly significant: The American College of Obstetricians and Gynecologists (ACOG) and the National Institute of Child Health and Human Development (NICHD) classify recurrent late decelerations as a Category II or III EFM pattern, signaling possible uteroplacental insufficiency.

Early decelerations (head compression pattern) are generally considered Category I and may not require O76 when they are isolated and reassuring overall. The physician’s attestation of a non-reassuring pattern is what drives the coding decision.

When to use ICD-10 code O76: Coding guidelines

The single most important rule for O76 is timing. The fetal heart rate abnormality must occur during active labor or the delivery encounter to qualify. Antepartum findings before labor onset use different codes entirely.

• Active labor criterion: Document that the EFM finding was identified after labor began. A prenatal visit note showing the same pattern does not support O76.
• Delivery encounter inclusion: O76 applies to abnormalities noted during the delivery itself, not only during the latent or active phases of labor.
• No further specificity required: O76 is the terminal code with no subclassification. You do not need to specify the type of deceleration in the ICD-10-CM code itself (though documentation of the specific pattern is required for the medical record).
• Multiple abnormalities, one code: If a patient has both fetal tachycardia and late decelerations during labor, O76 covers both. You do not assign two codes from this section for the same encounter.
• Secondary coding: O76 may be assigned alongside other obstetric codes when multiple complications are documented for the same delivery encounter, following standard ICD-10-CM multiple-coding rules.

Obstetric coding teams handling intrapartum claims will also encounter IVF-related delivery encounters where accurate complication coding is equally important. Our reference on IVF procedure coding covers the CPT side of assisted reproduction that often runs alongside obstetric ICD-10 documentation in fertility-adjacent practices.

O76 vs O36.83: Intrapartum vs antepartum fetal heart rate coding

Confusing O76 with O36.83 is the most common coding error in this category. The distinction hinges entirely on when the fetal heart rate abnormality was first identified and documented.

A practical scenario: A patient presents at 36 weeks with documented fetal tachycardia on a prenatal non-stress test. Her prenatal record carries O36.83 with the appropriate trimester extension.

When she returns two weeks later in active labor and the EFM again shows tachycardia, the labor and delivery encounter uses ICD-10 code O76, not O36.83. The prenatal diagnosis does not carry forward as the delivery encounter code.

Documentation requirements for O76

Missing or incomplete documentation is the primary reason O76 claims are queried or denied. Coders cannot assign a diagnosis the physician has not substantiated in the record.

The checklist below reflects what auditors and payers typically look for when reviewing intrapartum fetal heart rate claims. For teams looking to standardize their process, medical documentation compliance frameworks apply equally to obstetric records as they do to any other clinical encounter.

• EFM strip documentation: The electronic fetal monitoring tracing must be present in the medical record or clearly referenced by the physician. The strip itself is the primary evidence for the diagnosis.
• Specific pattern identified: The physician note should name the abnormality: “late decelerations,” “fetal tachycardia,” “variable decelerations,” or “non-reassuring fetal heart rate.” Generic phrases like “fetal heart rate changes” may not be sufficient for coding.
• Timing confirmation: The documentation must establish that the finding occurred during active labor, not on a prenatal visit. A timestamp on the EFM strip reading or a labor progress note with the documented finding satisfies this requirement.
• Physician attestation: A midwife or nurse observation alone is generally not sufficient. The attending obstetrician or provider of record must document the clinical finding or co-sign the nursing note.
• Clinical response documented: When an intervention was taken (position change, oxygen administration, expedited delivery), documenting the clinical response to the EFM abnormality strengthens the record and reduces audit risk.

Practices using structured patient records can template these documentation checkpoints directly into their labor and delivery note format, reducing the chance of an incomplete record reaching the coding queue. The same specificity requirements show up elsewhere in obstetric coding, as our article on O28.1 demonstrates for antenatal screening findings.

Obstetric documentation that supports accurate ICD-10 coding

Pabau helps labor and delivery teams structure clinical notes that capture the EFM findings, physician attestation, and timing details coders need. See how it works for your practice.

Book a demo

Electronic fetal monitoring and O76 coding

Electronic fetal monitoring (EFM) is the clinical tool that generates the findings coded under O76. Understanding how EFM output is classified helps coders confirm that the documented pattern genuinely supports the diagnosis.

ACOG and NICHD jointly developed a three-tier classification system for EFM patterns. The tier assigned to a monitoring tracing directly informs the clinical urgency and, by extension, the coding rationale.

Category II and III patterns are the most common drivers of O76 assignment. Category I tracings should raise a coder’s flag: If a claim carries O76 alongside a Category I-only EFM interpretation, the documentation may not support the diagnosis.

The attending physician’s note is the authoritative source. A nurse’s observation of the tracing alone typically does not create a billable diagnosis.

Related ICD-10 codes and code hierarchy

Obstetric coders frequently encounter O76 alongside sibling codes from the same O60-O77 block. The table below identifies the codes most commonly seen in conjunction with or as alternatives to O76, providing the context needed to choose the right code for each encounter.

Our article on K67 demonstrates how similar code-hierarchy navigation works in a different clinical chapter when multiple related codes exist in the same block.

Billing considerations for O76

O76 is a valid code for submission on Medicare, Medicaid, and commercial payer claims. Practices managing obstetric billing should be aware of several practical considerations.

• CMS claim submission: O76 is accepted on institutional claims (UB-04) and professional claims (CMS-1500) where the patient encounter supports its use. Confirm payer-specific requirements, as some managed Medicaid plans require additional documentation review for labor complications.
• Principal vs secondary diagnosis: When the delivery is the principal diagnosis (the reason for the encounter), O76 may be sequenced as an additional diagnosis code. Follow ICD-10-CM guideline Section I.C.15 for obstetric coding sequencing rules.
• No additional specificity required: Because O76 has no subclassifications, coders do not need to append characters for trimester or fetus number. The code is complete as coded.
• Procedure codes: O76 commonly appears alongside CPT codes for continuous electronic fetal monitoring. Payer policies on separately billing the monitoring procedure vary; verify coverage before submitting.

For practices managing multi-payer obstetric billing, claims management software that surfaces code-level payer rules helps reduce the manual verification burden on billing teams. Practices also benefit from reviewing their procedure code fee schedules to ensure obstetric procedure codes align with the diagnosis codes submitted on the same claim.

Common coding pitfalls and how to avoid them

Few competitors cover coding pitfalls for O76 in depth. These are the errors that show up in audits and claim queries most frequently.

• Coding O76 for antepartum EFM findings: The most common error. If the monitoring strip showing tachycardia or decelerations is from a prenatal visit, not the labor and delivery encounter, O76 does not apply. Use the O36.83 family with the appropriate trimester extension.
• Relying on nursing documentation only: Physician attestation is required. A nursing note that says “variable decelerations noted at 0330” does not create a billable diagnosis unless the attending physician has documented the finding or explicitly co-signed the observation as a clinical diagnosis.
• Omitting the EFM pattern from the note: Vague physician language (“fetal heart rate irregularity,” “some decelerations”) may not satisfy payer or audit requirements. The specific pattern (late, variable, bradycardia, tachycardia) should appear in the physician’s documentation.
• Assigning O76 alongside O77.9 for the same finding: O76 and O77.9 (fetal stress, unspecified) should not be coded together for the same clinical finding. When the abnormality is an EFM pattern, O76 is the more specific and appropriate code. O77.9 adds no value when O76 already covers the documented finding.
• Missing secondary codes for concurrent complications: When O76 occurs alongside another documented labor complication (e.g., O77.0 for meconium), both codes should be assigned. Under-coding concurrent conditions reduces the accuracy of the clinical record and may affect DRG assignment on inpatient claims.

How Pabau supports obstetric ICD-10 coding

Accurate ICD-10 code O76 assignment depends on documentation quality at the point of care. Pabau’s structured patient records allow obstetric teams to build note templates that prompt for the exact elements coders need: EFM pattern type, timing relative to labor onset, and physician attestation language.

Most coding errors happen when a physician understands the documentation requirement but the patient record never actually captures it in the moment.

For practices managing labor and delivery alongside related specialties, Pabau’s OB/GYN EMR software brings scheduling, clinical notes, and billing workflows into one system, reducing the handoff errors that occur when documentation and coding live in separate tools.

Teams using compliance management tools within Pabau can also flag incomplete labor notes before they reach the coding queue, catching missing physician attestation or undocumented EFM pattern descriptions early. For practices that span reproductive health more broadly, fertility clinic software from Pabau supports the antepartum coding workflow that often precedes intrapartum encounters where O76 applies.

Continue your research

Looking for a documentation reference for labor and delivery? VBAC birth plan template shows how Pabau structures similar labor and delivery documentation.

Working with ICD-10 codes across multiple clinical specialties? M34.9 shows how similar specificity requirements apply outside obstetric coding.

Want to see how extension characters work in a different code family? T31.85 covers its own set of required extensions.

Conclusion

Fetal heart rate abnormalities during labor are high-stakes clinical events, and the coding has to match. ICD-10 code O76 is the right code when the abnormality occurs intrapartum and the physician has documented the specific EFM finding.

Getting the timing right, intrapartum versus antepartum, and ensuring the medical record contains physician-attested pattern documentation are the two factors that separate clean claims from queried ones.

Pabau’s structured note templates and digital clinical documentation forms help obstetric teams build the documentation foundation that supports accurate O76 coding from the first labor note. To see how Pabau supports labor and delivery documentation workflows, book a demo with our team.

Frequently asked questions