# Fetal heart rate monitoring strips in birth injury cases

> How to request and read fetal heart rate monitoring strips against the labor chart in a birth injury case: NICHD categories, missing strips and templates.

Canonical page: https://medrecords.ai/guides/fetal-monitoring-strips-birth-injury-cases/

---
New — **Missing Records Detection:** flags every visit, provider, and date missing from the file. [See how →](https://medrecords.ai/product/missing-records-identification/)
Field guide, October 2026. 13 chapters.

## Fetal monitoring strips in birth injury cases

For birth injury attorneys, defense counsel and legal nurse consultants who have to turn a fetal monitoring tracing and a labor chart into 1 timeline an expert can read. You walk away with a records request checklist for native EFM data, a strip-to-chart timeline worksheet and a gap table.

By [Ahmed Jemaa](https://medrecords.ai/authors/ahmed-jemaa/), Co-Founder and CEO, Medrecords AI. Published 24 October 2026.

Fetal monitoring strips in a birth injury case are the continuous record of the baby's heart rate and the mother's contractions during labor. Reviewers read them alongside the nursing notes, physician orders and delivery times to see what the tracing showed, when staff responded, and whether any part of the record is missing.

In most birth injury files the fetal monitoring tracing is the only record that ran every minute of labor. Everything else, the nursing flowsheet, the physician notes, the delivery record, is a set of snapshots written by people who were busy. The work of a record reviewer is to put the film and the snapshots on 1 clock and show the expert exactly where they agree, where they conflict and where nothing exists at all.

This guide is built from ACOG Clinical Practice Guideline No. 10, *Intrapartum Fetal Heart Rate Monitoring: Interpretation and Management* (October 2025), the 2 practice bulletins it replaced (No. 106, 2009, and No. 116, 2010), the 2008 NICHD, ACOG and Society for Maternal-Fetal Medicine workshop report on electronic fetal monitoring, the 2024 AWHONN position statement on fetal heart monitoring, a 2016 study of chart speed and tracing interpretation, the HIPAA access rule at 45 CFR 164.524, and Federal Rule of Civil Procedure 37(e). Every case example is a labeled hypothetical. Nothing here is legal or medical advice. Reading a tracing is a clinical opinion for a qualified expert, and records, discovery and spoliation rules vary by state and court. For the neonatal side of these cases (cord gases, cooling, MRI, the placenta), see our guide to [HIE birth injury medical records](https://medrecords.ai/guides/hie-birth-injury-medical-records/).

8 numbers

### The strip record in 8 numbers

3 cm/min
paper speed used for fetal heart rate tracings in the United States; many other countries print at 1 cm/min
Peleg and colleagues, J Matern Fetal Neonatal Med, 2016
3
tiers in the NICHD tracing classification still used in US charting: Category I, II and III
Macones and colleagues, NICHD workshop, 2008
110 to 160
beats per minute: the normal fetal heart rate baseline. Above 160 is tachycardia, below 110 is bradycardia
ACOG Practice Bulletin 106, 2009
10 minutes
the window used to set the baseline; a change that lasts 10 minutes or longer is a baseline change, not a deceleration or acceleration
ACOG Practice Bulletin 106, 2009
2 to 10 minutes
a prolonged deceleration: 15 bpm or more below baseline for 2 minutes or more but less than 10
ACOG Practice Bulletin 106, 2009
30 and 15
minutes between tracing reviews in an uncomplicated first and second stage under the 2009 bulletin; 15 and 5 with complications
ACOG Practice Bulletin 106, 2009
October 2025
ACOG Clinical Practice Guideline No. 10 replaced Practice Bulletins 106 and 116 and leaves review frequency to hospital protocol
ACOG CPG No. 10, 2025
30 days
for a covered entity to act on a patient's HIPAA access request, with 1 extension of up to 30 more
45 CFR 164.524(b)(2)
Chapter 1 Everyone

### What an EFM strip is, and what it is not

Electronic fetal monitoring (EFM) records 2 channels on 1 time axis. The top channel is the fetal heart rate in beats per minute. The bottom channel is uterine activity: the timing of contractions and, depending on the sensor, their strength. The printed or displayed result is called the strip, the tracing or, in some hospitals, the CTG (cardiotocograph). In a lawsuit it gets called all 3, sometimes in the same deposition.

Each channel can come from 1 of 2 sources, and the source changes what the tracing can show.

##### External monitoring

Heart rateDoppler ultrasound transducer on the abdomenContractionsTocodynamometer (toco) belt: shows timing and shape, not true pressureKnown weak spotSignal loss when the mother moves, and the chance of recording the maternal heart rate as fetalWhat to look for in the chartRepositioning of transducers, maternal pulse checks, notes about poor tracing quality

##### Internal monitoring

Heart rateFetal scalp electrode (FSE) attached after membranes ruptureContractionsIntrauterine pressure catheter (IUPC): measures pressure in mmHgKnown weak spotRequires ruptured membranes and a procedure; placement time must be documentedWhat to look for in the chartAn order or note for FSE or IUPC placement, the time, who placed it, and when the tracing source changed
The source matters to a reviewer for a plain reason. ACOG's 2025 guideline notes that when staff have ongoing difficulty telling the maternal from the fetal heart rate, "placing a fetal scalp electrode may provide more accurate monitoring." If the chart has a stretch where staff wrote that the tracing was hard to read, the expert will want to know which sensor was in use, when it changed and whether maternal pulse was recorded at the same time. Those facts sit in different places: the monitor stores the sensor mode with the tracing, the nurse writes the placement in the flowsheet, and the physician may mention it in a progress note.

#### What a printed strip page carries

A printed or exported page from a perinatal system carries more than the 2 lines. Learn to read the frame before anyone argues about the line.

EFM printout, 1 page hypothetical layout
Header
Patient, MRN, bed — DEMO, A. / 000000 / LDR 41
Date and time printed — 03/14 01:40 to 01:502
Paper speed — 3 cm/min3
Channels
FHR mode — US FECG4
UA mode — TOCO IUP5
Margin
Annotations — 01:44 "Pos L lat, IVF bolus"6
DEF 004812
1. 1
**Identity** Confirm the page belongs to this patient and this admission. Twin deliveries and transfers between rooms produce mixed sets.
2. 2
**Time window on the monitor clock** These times come from the monitor or archive server, which may not match the EHR clock. Log them as monitor time.
3. 3
**Paper speed** A tracing rescaled from 3 to 1 cm/min, or the reverse, looks different. A 2016 study found readers more often called variability absent rather than minimal at 1 cm/min.
4. 4
**Heart rate source** US means external ultrasound; FECG or similar means a scalp electrode. Log every change.
5. 5
**Contraction source** Toco shows timing; an IUPC reading in mmHg shows pressure. Tachysystole arguments need the timing either way.
6. 6
**Annotation** An event the nurse entered at the bedside monitor or central station. It is stored with the tracing, often not in the flowsheet.

#### Paper versus the archive

In older units the strip came out of the bedside monitor on folded paper and was boxed after delivery. Most hospitals now run a perinatal surveillance system that captures the tracing electronically, shows it at a central station and archives it. The printed pages in your production are often a print job someone ran after a request arrived. The 2009 bulletin was direct about storage: "Computer storage of the FHR tracing that does not permit overwriting or revisions is reasonable, as is microfilm recording." That sentence is why the native archive, not the print job, is the record to ask for (chapter 7).

The tracing is often not inside the main EHR at all. The EHR may hold only what the nurse charted about it: baseline, variability, decelerations, category, and notes. That split is the source of most strip problems in litigation, and it is why a release-of-information office can honestly send "the complete chart" without a single page of tracing.

If you remember one thing
The strip is 2 channels, 2 possible sensors per channel, and 1 monitor clock. Before anyone reads the line, log the sensor, the paper speed and the clock for every page.

Chapter 2 Deciding

### Which ACOG guidance applied on the delivery date

Expert reports in birth injury cases lean on ACOG guidance, and the guidance changed in October 2025. ACOG Clinical Practice Guideline No. 10 replaced Practice Bulletin 106 (July 2009), Practice Bulletin 116 (November 2010) and a 2022 practice advisory on oxygen for Category II or III tracings. Most cases filed in 2026 involve deliveries before that date. The right question for every guideline cited in a report is: which version was in force on the day of the labor?

Standard of care is a legal question answered by expert testimony, and guidelines are only part of it. Still, the change between versions decides what a reviewer should look for in the chart, so it belongs in the case file from day 1.

2009 and 2010 bulletins (106, 116)
Review frequency — About every 30 minutes in the first stage and 15 in the second for uncomplicated labor; 15 and 5 with complications
Documentation — Providers "should periodically document" that they reviewed the tracing
Storage — Tracing is part of the medical record; storage that prevents overwriting is reasonable
Oxygen — Listed among intrauterine resuscitation measures in 2010; a 2022 advisory later addressed it
2025 guideline (CPG No. 10)
Review frequency — Review "frequently"; document assessments "at frequencies established per individual hospital protocols"
Documentation — A member of the care team periodically documents tracing assessments
Storage — The tracing, "as part of the medical record, should be available for review"
Oxygen — Recommends against routine maternal oxygen for Category II or III tracings without maternal hypoxia
2 practical effects follow. First, for a labor after October 2025, the review interval comes from the hospital's own policy, so the unit's EFM policy in force on the delivery date becomes a core document. Ask for it with the records, not after the depositions. Second, an intervention charted in 2019 may look different against the 2025 text. Oxygen is the clearest example: the same flowsheet entry reads differently under the 2 versions. Your expert decides what it means. Your job is to give them the dated version of every guideline next to the entries it touches.

"An FHR tracing may move back and forth between the categories depending on the clinical situation and management strategies used."

If you remember one thing
Put the delivery date next to every guideline citation. A report that quotes the 2025 guideline about a 2021 labor, or the 2009 bulletin about a 2026 labor, invites a cross-examination you can see coming.

Chapter 3 Everyone

### NICHD fetal heart rate categories: Category 1, 2 and 3 tracings

The 2008 NICHD workshop set the 3-tier vocabulary that labor nurses and obstetricians chart in the United States, and the 2025 ACOG guideline keeps it while noting its limits, especially inside Category II. Our [HIE guide covers the categories and their link to timing an injury](https://medrecords.ai/guides/hie-birth-injury-medical-records/#nichd). This chapter does something narrower: for each category, what a reviewer should expect to find written in the chart near it. Whether care was right is the expert's call. Whether the chart says anything at all is yours.

| Category | Plain definition | What you expect to see documented near it |
| --- | --- | --- |
| Category I (often searched as category 1) | Normal baseline of 110 to 160 bpm, moderate variability, no late or variable decelerations; accelerations and early decelerations may be present or absent | Routine assessments at the interval in the unit policy; baseline, variability and decelerations charted in words or picklists |
| Category II (category 2 fetal heart tracing) | Every tracing that is neither Category I nor Category III; the largest and most argued-over group | Assessments at the policy interval; any intrauterine resuscitation (position change, IV fluid bolus, reducing or stopping oxytocin, amnioinfusion, treating a maternal cause); notification of the provider and the response; a plan or reassessment time |
| Category III (category 3 fetal heart tracing) | Absent variability with recurrent late decelerations, recurrent variable decelerations or bradycardia; or a sinusoidal pattern | Notification and bedside evaluation; resuscitation measures and their timing; a delivery decision, its time and its mode; team calls (anesthesia, neonatal team); move to the operating room |

The 2025 guideline lists features that make a Category II tracing higher risk: absent variability, prolonged and otherwise unexplained minimal variability, an unexplained change from a normal baseline to tachycardia, and recurrent late, recurrent variable, or more than 1 prolonged deceleration. It names moderate variability and accelerations as protective. A reviewer does not decide which features were present. A reviewer does check whether the chart describes them in words, because an expert who reads the strip as high-risk Category II will look for the nurse's description of the same minutes.

#### The words you will see in the flowsheet

BaselineThe mean heart rate over a 10-minute window, rounded to 5 bpm, present for at least 2 minutes of that window.VariabilityFluctuation around the baseline: absent (undetectable), minimal (5 bpm or less), moderate (6 to 25), marked (over 25).AccelerationAn abrupt rise; at 32 weeks or later, 15 bpm or more for 15 seconds or more but under 2 minutes.Late decelerationA gradual drop whose lowest point comes after the peak of the contraction.Variable decelerationAn abrupt drop of 15 bpm or more, lasting 15 seconds to under 2 minutes, not tied to contraction timing in a fixed way.Prolonged decelerationA drop of 15 bpm or more lasting 2 minutes or more but under 10.SinusoidalA smooth, wave-like pattern of 3 to 5 cycles a minute lasting 20 minutes or more.TachysystoleMore than 5 contractions in 10 minutes, averaged over 30 minutes.
Category is a snapshot. ACOG's 2025 text says categorization "evaluates the fetus at that point in time." So when the flowsheet says "Category II" at 01:00, 01:30 and 02:00, you have 3 snapshots of a continuous record. The rest of this guide is about the minutes between them.

If you remember one thing
For each charted category, ask what else the chart should say within the next few minutes: a description, an action, a call, a reassessment. List the entries you find and the ones you do not. That list is a records finding, not a clinical opinion.

Chapter 4 Building

### Where tracing-related entries hide in the chart

Tracing information is spread across 6 to 10 places in a typical labor chart. Missing 1 of them is how a timeline ends up with a 40-minute hole that was never a hole. Search each location below, in this order, and log every entry with its page and its clock.

1 —

##### Labor nursing flowsheet

The structured EFM assessment rows: baseline, variability, accelerations, decelerations, category, uterine activity, and the time each row was charted. Usually the densest source.

2 —

##### Nursing narrative notes

Free text: "MD notified of decels", "position changed", "tracing difficult to interpret". This is where notification and response usually live.

3 —

##### Annotations on the tracing

Events entered at the monitor or central station: exams, position changes, medications, provider at bedside. Stored with the tracing, stamped on the monitor clock.

4 —

##### Medication administration and pump records

Oxytocin starts, rate changes, pauses and stops; tocolytics; IV fluid boluses. Pump logs may hold times the MAR rounds off.

5 —

##### Physician and midwife notes

Progress notes, the delivery note and the operative note. Look for "tracing reviewed", the category they recorded and the decision to deliver.

6 —

##### Anesthesia record and OR log

Epidural times, boluses, maternal blood pressure, room entry, incision and delivery. Anesthesia systems log their own times automatically.

7 —

##### Orders and communication logs

Order times for FSE or IUPC placement, cesarean, team pages. Some hospitals log pages and secure messages separately from the chart.

8 —

##### Triage and admission records

The first tracing assessment and the admission strip, often charted in a separate triage module. The first 60 minutes can carry the most weight in timing arguments.

#### Late entries and copy-forward text

Labor and delivery charting is often finished after the fact. A note filed at 05:10 that describes events at 02:30 is a late entry, and most EHRs store both the event time the nurse chose and the time the note was saved. Log both. When the 2 are far apart, the expert and counsel will want to know, and the place to confirm the save time is the EHR's audit trail, which is a separate request (see [EHR audit trails in medical malpractice](https://medrecords.ai/guides/ehr-audit-trail-medical-malpractice/) ).

Ambient AI scribes now draft some physician notes in labor units. A scribe-drafted note can carry the time the draft was generated, not the time of the exam it describes, and it may echo phrasing from earlier notes. Treat those times like any other late entry: as the time of writing until something else proves the time of the event.

**Nursing note, version 1** — saved 03/14 02:51
Event time entered: 02:20 — Pt repositioned L lateral. IVF bolus started. FHR baseline 140s. Will continue to monitor.
**Nursing note, addendum** — saved 03/14 06:05
Event time entered: 02:20 — Pt repositioned L lateral. IVF bolus started. Decels noted with ctx, Dr. notified at 02:22 by phone. Will continue to monitor.
Hypothetical. 2 versions of 1 note, both dated to the same event time, saved 3 hours apart. Neither version proves what happened at 02:20. Both belong in the timeline with their save times.

If you remember one thing
Every entry has 2 times: when it says something happened, and when someone wrote it. Log both, every time, or you will not see the late entry that changes the order of events.

Chapter 5 Building

### How to read fetal heart rate monitoring strips against the chart

The fetal monitor, the EHR, the anesthesia system, the pump and the lab analyzer each keep their own clock. They are supposed to agree, and often they are a few minutes apart. In a case where the argument is about a 10-minute delay, a 6-minute clock offset is the whole case. Our HIE guide explains [how to anchor the clocks at the time of birth](https://medrecords.ai/guides/hie-birth-injury-medical-records/#birth-hour). Strip work needs more anchors than that, spread across the labor, because offsets can drift and because the monitor may have been restarted or swapped.

#### How to find the offset

1. **List every clock.** Monitor or archive server, EHR, anesthesia record, infusion pumps, lab analyzer, any paper form timed from a wall clock.
2. **Find events recorded by 2 systems.** Good anchors: an epidural bolus (anesthesia record and a tracing annotation), an FSE placement (tracing mode change and flowsheet entry), the move to the OR (end of tracing and OR log), birth.
3. **Compute the difference for each anchor.** Write the times as recorded and the difference in minutes. Do not adjust anything yet.
4. **Check that the offset is stable.** 3 anchors that agree within a minute support 1 offset for the labor. Anchors that disagree point to drift, a restart or a wrong entry, and each needs a note.
5. **Show both times in the timeline.** Keep the time as recorded in its own column and add a converted time only where the offset is supported. Never overwrite the original.

Tracing (monitor clock) — Chart (EHR or other clock) — Note
23:12 annotation "epidural bolus" — 23:06 anesthesia record bolus — Monitor 6 min ahead
00:41 FHR mode US to FECG — 00:35 flowsheet "FSE placed" — Monitor 6 min ahead
02:31 annotation "MD at bedside" — 02:20 physician note "called to bedside" — 11 min apart: offset explains 6; 5 unexplained
No tracing 02:58 to 03:16 — 03:05 flowsheet "FHR 90s by doppler" — Chart describes heart rate during a tracing gap
03:16 tracing ends — 03:24 birth, OR log and delivery record — 8 min with no tracing before birth
Hypothetical. The same labor appears in chapter 6 and in the sample timeline.

#### Annotations versus note times

Annotations are useful because they are stamped by the monitor at the moment someone entered them. They are limited because they are short, often abbreviated, and entered by whoever was at the central station. A note saying "MD notified 02:22" and an annotation reading "MD aware" at 02:31 monitor time (02:25 corrected) are 2 statements about 1 event, 3 minutes apart after correction. Put both in the timeline with their sources. Do not choose between them.

If you remember one thing
Use at least 3 anchors spread across the labor, with birth as only 1 of them. An offset you can show with 3 cites will survive a deposition; an offset you assumed will not.

Chapter 6 Building

### Worked example: a strip-to-chart timeline

**Hypothetical.** A fictional term labor, induced with oxytocin, delivered by cesarean. Every name, time and page number is invented. The monitor clock runs 6 minutes ahead of the EHR, shown by 3 anchors in chapter 5. Times below are EHR time, with monitor times converted and marked. The timeline reports what each record says. It does not say what the tracing showed or whether anyone acted correctly. That is for the experts.

**Strip-to-chart timeline, last 3 hours of labor** — hypothetical — Illustration
1. 00:35
**Scalp electrode placed**
Flowsheet records FSE placement. Tracing heart rate mode changes from ultrasound to FECG at 00:41 monitor time (00:35 corrected).

Flowsheet p. 212; tracing segment 14
2. 01:30
**Category II charted**
Flowsheet row: baseline 145, minimal variability, recurrent decelerations, Category II. Oxytocin running at 12 mU/min per MAR.

Flowsheet p. 214; MAR p. 301
3. 01:42
**Oxytocin reduced**
Pump log shows rate change from 12 to 6 mU/min. The MAR entry for the same change reads 01:45.

Pump log p. 330; MAR p. 301
4. 02:20
**Position change and fluid bolus**
Nursing note: repositioned, IV bolus started. Addendum saved at 06:05 adds "Dr. notified at 02:22 by phone". Original note saved 02:51 does not mention notification.

Nursing notes p. 240 and p. 247
5. 02:20 or 02:25
**Physician at bedside**
Physician note says called to bedside at 02:20. Tracing annotation "MD at bedside" at 02:31 monitor time, 02:25 corrected. 5-minute conflict after correction.

Progress note p. 118; tracing segment 19
6. 02:40
**Decision for cesarean**
Progress note documents decision to proceed with cesarean. Order time 02:43.

Progress note p. 119; orders p. 405
7. 02:58 to 03:16
**No tracing produced**
Produced tracing pages stop at 02:58 corrected and resume for 1 segment at 03:10 to 03:16. Flowsheet entry at 03:05 says "FHR 90s by doppler". No tracing pages cover 02:58 to 03:10.

Tracing segments 21 and 22; flowsheet p. 216
8. 03:08
**In operating room**
OR log: patient in room 03:08, incision 03:19.

OR log p. 512
9. 03:24
**Birth**
Delivery record, OR log and anesthesia record agree on 03:24. Last tracing data 03:16 corrected.

Delivery record p. 520; anesthesia record p. 610

The timeline produces 3 findings for the experts and counsel: a 5-minute conflict on when the physician arrived, a late addendum adding a notification time, and a 12-minute period with no tracing while the chart describes heart rate by doppler.

Notice what is not in the timeline: no category assigned by the reviewer, no statement that a deceleration was late or variable, no comment on whether 02:40 was soon enough. Those are clinical judgments. A reviewer who writes them into the timeline gives opposing counsel a reason to attack the whole document.

Notice also what the timeline makes easy. An obstetric expert can open tracing segment 19 and the progress note side by side. A nursing expert can see the 2 versions of the 02:20 note. Counsel can see exactly which tracing minutes were never produced and draft the follow-up request from the gap row (chapter 7).

If you remember one thing
A good strip-to-chart timeline answers "what does each record say, and when" for every minute in dispute. It never answers "was that right". Keep the 2 questions in different documents.

Chapter 7 Building

### When fetal monitoring strips are missing or partial

The common versions of the problem: a stack of printed pages that covers the last 40 minutes, a scan of a scan with an unreadable time axis, a production with no tracing at all, or a letter saying the tracing is not part of the legal medical record. Our [HIE guide has a decision path](https://medrecords.ai/guides/hie-birth-injury-medical-records/#missing-strip) for what to ask next. This chapter is the procedure: what the archive holds, how to ask for it, how to document gaps and what the law says when data is lost.

#### What the perinatal archive holds

Perinatal surveillance systems store the tracing as data, not as pictures. A complete export usually includes both channels at full resolution, the sensor mode for each period, annotations with their times, alarms or alerts where the system logs them, and system events such as disconnections. Many systems can also report who viewed, printed or annotated a tracing and when. The release-of-information office often cannot produce any of this because it does not run the system. Nursing informatics or clinical engineering does.

Step 1 — **Name the system** — Ask in writing which system captured and archived the tracing on the delivery date, and who administers it.
Step 2 — **Preserve** — Send a preservation request covering the native tracing, annotations, system logs and access logs, before any print request.
Step 3 — **Request native export** — Ask for the complete tracing in the system's native or viewer-readable format, admission to delivery, with the viewer if needed.
Step 4 — **Reconcile and log gaps** — Compare what came back to the chart minute by minute and send a written gap table for explanation.
For a patient's own request, HIPAA gives a right to a copy in the electronic form and format requested if it is readily producible (45 CFR 164.524(c)(2)(ii)), within 30 days with 1 extension of up to 30 more. Whether the tracing falls inside the hospital's designated record set, and how discovery works in litigation, depends on the hospital's policies, state law and your court's rules. Ask anyway, by name, and get the answer in writing.

#### Documenting the gaps

A complaint that "the strip is incomplete" goes nowhere. A table of specific missing minutes, each tied to a chart entry showing monitoring was running, forces a specific written answer. Build it like this:

Missing period (EHR time) — Minutes — Evidence monitoring was running
22:10 to 22:25 — 15 — Flowsheet row 22:15 charts baseline and variability, p. 209
01:05 to 01:12 — 7 — Annotation index lists 01:08 "SVE", no tracing page
02:58 to 03:10 — 12 — Flowsheet 03:05 "FHR 90s by doppler", p. 216
Total — 34 — hypothetical; each row goes to the custodian for a written explanation
Some gaps have plain explanations: the transfer to the OR, a bathroom break, a monitor swap, a period of intermittent auscultation under unit policy. Log the explanation the hospital gives and its source. The gap table is a record of questions and answers, not an accusation.

#### Spoliation, in plain terms

When evidence that should have been preserved is lost, courts have remedies, and they vary. In federal court, Rule 37(e) governs lost electronically stored information. It limits the harshest remedies to cases where a party acted with intent:

"only upon finding that the party acted with the intent to deprive another party of the information's use in the litigation may" the court presume the information was unfavorable.

Short of intent, a federal court that finds prejudice may order measures "no greater than necessary to cure the prejudice." Most birth injury cases are in state court, where spoliation doctrine, adverse inference instructions and any separate tort claim differ from state to state. Some states have specific rules. Virginia's birth injury compensation act deems fetal monitoring strips, "whether printed or in electronic format," part of the infant's medical records for that program. Counsel decides what to do with a gap. The reviewer's job is to make sure the record of the gap is exact: what was asked, when, by whom, and what came back.

If you remember one thing
Ask for preservation of the native archive before asking for a printout. Then turn every missing minute into a row with a cite. A specific gap table gets a specific written answer; a general complaint gets a general letter.

Chapter 8 Deciding

### Who reads the strip, and who builds the timeline

Interpreting a fetal heart rate tracing is a clinical opinion. In litigation it comes from a qualified expert: an obstetrician, a maternal-fetal medicine specialist, or a labor and delivery nurse expert for nursing standard of care, depending on the issue and the court's expert rules. AWHONN's 2024 position statement says fetal heart monitoring "requires advanced assessment and clinical judgment skills" and should not be delegated to people without the licensure, education and skills validation for it. That is a statement about clinical care, but it is a fair guide for litigation work too.

##### The record reviewer builds

Paralegal, LNC, case manager, or software with human review

- The inventory of every tracing page and segment, with times and sensor modes
- The clock offsets and their anchors
- Every tracing-related chart entry, cited to its page
- The gap table and the request log
- Conflicts between sources, stated without judgment

##### The expert decides

Qualified clinician, in a signed report

- What the tracing showed in each period
- The category at each point in time
- Whether the response met the standard of care
- What the gaps mean clinically
- Causation and timing of any injury

The split has a practical reason beyond credentials. Tracing interpretation varies between readers, and the presentation of the tracing affects it. In a 2016 study, 14 physicians read the same 19 tracing segments at 1 or 3 cm/min; at 1 cm/min they more often called variability absent rather than minimal and minimal rather than moderate, and agreement between readers was higher at 3 cm/min. If a reviewer sends an expert a rescaled printout without saying so, the reviewer has changed the evidence.

MythAn experienced LNC or paralegal can assign categories to save the expert time.
RuleReport the categories the clinicians charted, with cites. Leave new categorization to the expert who will sign it.
MythA printout is as good as the archive if it is legible.
RuleA printout is a derivative. Paper speed, annotations and sensor changes can be lost in the print job. Send the expert the native export when you have it.
MythThe flowsheet category entries tell you what the tracing showed.
RuleThey tell you what a nurse charted at a moment. ACOG says the category describes the fetus "at that point in time".
If you remember one thing
Send the expert the full native tracing, the timeline and the gap table, in that order, and nothing that looks like your own interpretation. Their opinion is stronger when the record they relied on is clean.

Chapter 9 Everyone

### Where AI helps and where it does not on fetal monitoring records

Birth injury files are large. A long induction can produce hundreds of flowsheet rows, dozens of notes, pump logs, anesthesia records and a few hundred tracing pages. Legal AI tools are good at some of this work and should not touch the rest.

Reviewer working by hand
Finding entries — Page through the chart and copy times into a spreadsheet
Clock conflicts — Spotted when someone happens to compare 2 sources
Missing periods — Found late, often after depositions
Handwritten pages — Read one by one
AI medical record review with human review
Finding entries — Every tracing-related entry, order and medication time pulled into 1 chronology, cited to its page
Clock conflicts — Entries about the same event with different times flagged for a person to check
Missing periods — Periods the chart describes with no matching pages flagged, with the entries that imply them
Handwritten pages — OCR and handwriting recognition, with low-confidence pages flagged for a person

#### What AI should not do here

An AI system should not read the tracing image and assign a category, call a deceleration late or variable, or say whether a response was timely. Those are clinical opinions. The 2025 ACOG guideline notes there are no clinical trials showing that computer-based tracing interpretation improves newborn outcomes. A litigation tool that offered strip interpretation would be offering an unsigned clinical opinion. Medrecords AI does not interpret strips, assign NICHD categories or read the tracing line. It works on the text of the record: entries, times, orders, annotations printed on the pages, and what is missing.

#### Failure modes to check for

- **Hallucinated facts** *A large language model (LLM) can write a fluent sentence that no page supports. Require a page-level citation on every line and click a sample of them.*
- **OCR errors on times** *Faxed and scanned flowsheets turn 01:38 into 01:58. Check every time that drives a conflict flag against the page image.*
- **Missed handwritten notes** *Paper delivery records and resuscitation forms are often handwritten. Confirm the tool flagged low-confidence pages and that someone read them.*
- **Copy-forward text dated wrong** *Text carried forward from an earlier note can carry an old time. Compare the note's save time to the event time.*
- **Monitor and EHR times merged** *A chronology that silently mixes clocks hides the offset. Keep the source clock in a column.*
- **Generative AI summaries without sources** *A paragraph summary of labor is useful only if each sentence links back to the record.*

**0** of 6 checked

Courts have sanctioned lawyers under Rule 11 for filing fabricated citations produced by generative AI; *Mata v. Avianca* (S.D.N.Y. 2023) is the case most people know. The same discipline applies to medical facts: every date and time in a filing should trace to a page someone opened. Retrieval-augmented generation with grounded citations makes that checking fast. It does not remove the need for it. Human-in-the-loop review is the method, not a disclaimer.

#### Vendor checklist for birth injury work

1. **HIPAA compliant AI with a signed business associate agreement (BAA).** No BAA, no upload.
2. **SOC 2 report available** on request, and a clear answer on whether your data trains any model (it should not).
3. **A citation on every line** of the chronology, linked to the source page.
4. **Source clock kept** with each time, so monitor and EHR times are never merged silently.
5. **Low-confidence OCR pages flagged** , including handwritten notes.
6. **No clinical interpretation** of the tracing, in the product or the marketing.
7. **A log of who ran what** on your file inside the tool, for your own chain of custody.

If you remember one thing
Use AI to find, cite and flag every entry in a labor chart. Do not use it, or let anyone use it, to read the tracing. That line keeps the work product defensible.

Chapter 10 Building

### Templates: EFM request, timeline worksheet and gap table

Copy these into your own forms. Adapt the request to your jurisdiction and your rules of discovery; counsel decides what gets sent.

##### 1. Records request checklist for EFM data

Attach to the first records request or request for production in a birth injury matter, before depositions.

EFM RECORDS REQUEST CHECKLIST
Patient: [NAME] DOB: [DATE] Admission: [DATE] to [DATE]
Facility: [HOSPITAL] Delivery date and time: [DATE, TIME]

1. Name of the perinatal surveillance or EFM archive system in use on the
 delivery date, its version, and the department that administers it.
2. The complete fetal heart rate and uterine activity tracing from the first
 minute of monitoring (including triage and any antepartum testing in this
 admission) to delivery, in native electronic format or a complete export
 that keeps the time axis, both channels and system time stamps.
3. A viewer or instructions to open the native file, if needed.
4. All annotations and event marks stored with the tracing, with times.
5. Sensor mode history: external ultrasound or fetal scalp electrode, toco or
 intrauterine pressure catheter, with the time of each change.
6. Maternal heart rate or pulse oximetry channel, if recorded.
7. Alarms, alerts and system event logs (disconnections, downtime, restarts)
 for the admission.
8. Access and print history for the tracing: who viewed, printed, annotated
 or exported it, and when.
9. A written statement of any period with no tracing data and the reason.
10. The unit's EFM and documentation policies in force on the delivery date,
 including tracing review frequency and notification procedures.
11. Monitor and archive server time synchronization records, if kept.
12. Retention policy for tracings in force on the delivery date.

##### 2. Strip-to-chart timeline worksheet

1 row per entry. Keep the original time and clock; add a corrected time only where 3 anchors support the offset.

STRIP-TO-CHART TIMELINE WORKSHEET
Case: [MATTER] Reviewer: [NAME] Offset used: monitor [+/- N] min vs EHR
Anchors: [EVENT 1, cites] [EVENT 2, cites] [EVENT 3, cites]

| Time as recorded | Source clock | Corrected EHR time | Source (doc, page or segment) | Entry, quoted or close paraphrase | Saved time if later | Flag |
|------------------|--------------|--------------------|-------------------------------|------------------------------------|---------------------|------|
| [HH:MM] | [Monitor/EHR/Anes/Pump/Lab] | [HH:MM] | [e.g. Flowsheet p. 214] | [ENTRY] | [HH:MM] | [conflict / gap / late entry / none] |

Flag rules:
- conflict: 2 sources describe 1 event with times that differ after correction
- gap: chart describes monitoring in a period with no tracing pages
- late entry: saved time more than [N] minutes after the event time
No category assignments or clinical judgments in this worksheet.

##### 3. Tracing gap table

Send to the records custodian with a request for a written explanation of each row.

FETAL MONITORING TRACING: GAP TABLE
Patient: [NAME] Facility: [HOSPITAL] Production reviewed: [BATES RANGE]

| # | Missing period (EHR time) | Minutes | Evidence monitoring was running (cite) | Date asked | Response (date, source) |
|---|---------------------------|---------|----------------------------------------|------------|-------------------------|
| 1 | [HH:MM to HH:MM] | [N] | [e.g. Flowsheet 03:05 "FHR 90s", p. 216] | [DATE] | [RESPONSE] |

For each row, please state: whether tracing data exists for the period;
if so, produce it in native format; if not, why not (disconnection,
transfer, downtime, intermittent auscultation, loss), with supporting logs.
If you remember one thing
Send the checklist first, the gap table second. The checklist gets you the native data; the gap table gets you written answers about what is still missing.

Chapter 11 Publisher

### What Medrecords AI does with a labor and delivery file

Medrecords AI is medical chronology software for legal and claims teams. You upload the records you have, and it reads about 100 pages a minute; it drafts a cited [AI medical chronology](https://medrecords.ai/product/chronology/) in which every entry links to its source page. For a birth injury file, that means every tracing-related entry the chart contains, the flowsheet assessments, nursing notes, oxytocin rate changes, provider notes, orders, OR and anesthesia times, organized in time order with a [citation on every line](https://medrecords.ai/product/citations/).

- It flags entries about the same event that carry different times, so a person can check the clocks.
- It flags periods the chart describes that have no matching pages in the production, through [missing records identification](https://medrecords.ai/product/missing-records-identification/), each flag cited to the entries that imply the record should exist.
- It shows near-duplicate pages that differ side by side through [record alteration detection](https://medrecords.ai/product/record-alteration-detection/), which surfaces addenda and late versions. A flag is a signal, not a verdict.
- It routes typed, handwritten and table pages to the right [OCR](https://medrecords.ai/product/ocr/) engine and flags low-confidence pages.

What it does not do: it does not retrieve records from the hospital, read the tracing image, assign NICHD categories, judge the standard of care or give legal advice. It does not parse a hospital's EHR audit trail export. You review, you revise, you sign.

To see the output format, open the [fetal monitoring timeline sample](https://medrecords.ai/content-hub/samples/fetal-monitoring-birth-injury-timeline-sample/), a hand-built illustration on a fictional labor. For the wider field of tools, see our list of [AI tools for birth injury law firms](https://medrecords.ai/best/ai-tools-for-birth-injury-law-firms/) and the [birth injury record review](https://medrecords.ai/solutions/birth-injury-record-review/) page.

The offer

#### See a cited labor and delivery chronology from your own file.

Book a demo on a birth injury file you are working, then run your first case on us. Every line comes back cited to its source page. You review, you revise, you sign.

[Book a demo](https://medrecords.ai/demo/?src=guide-fetal-monitoring-strips-birth-injury-cases) [See missing records identification](https://medrecords.ai/product/missing-records-identification/)
Scheduling only. No records move from a public page.

Chapter 12 Everyone

### Frequently asked questions

What is a Category 2 fetal heart tracing?A Category II (category 2) tracing is any fetal heart rate tracing that does not meet the definition of Category I or Category III under the 2008 NICHD system. It is the largest group and covers a wide range of patterns, which is why ACOG's 2025 guideline describes high-risk features within it. Deciding whether a specific tracing was Category II is an expert's clinical judgment.
What is a Category 3 fetal heart tracing?A Category III (category 3) tracing has absent baseline variability with recurrent late decelerations, recurrent variable decelerations or bradycardia, or a sinusoidal pattern. ACOG's 2025 guideline recommends expedited delivery when a Category III tracing does not respond to initial intrauterine resuscitation, when indicated. Whether a tracing met that definition is a question for a qualified expert.
What is an EFM strip?An EFM strip is the printed or displayed record from electronic fetal monitoring: the fetal heart rate on top and uterine activity below, on 1 time axis. In US hospitals it is usually printed at 3 cm per minute and stored electronically in a perinatal archive.
What if the fetal monitoring strips are missing?Ask in writing which archive system captured the tracing, request preservation and a native export, and send the custodian a gap table listing each missing period with the chart entries showing monitoring was running. Remedies for lost evidence vary by court and state; counsel decides the next step.
Are fetal monitoring strips part of the medical record?ACOG guidance treats the tracing as part of the medical record, and Virginia's birth injury act says so for that program. Whether a hospital produces it in response to a given request depends on its legal health record policy, state law and the discovery rules of the court.
Who can interpret a fetal monitoring strip in a lawsuit?A qualified clinical expert, usually an obstetrician, a maternal-fetal medicine specialist or a labor and delivery nurse expert, depending on the issue and the court's rules. A record reviewer prepares the tracing inventory, the timeline and the gap table that the expert relies on.
Can AI interpret a fetal monitoring strip?No AI tool should be used to interpret a tracing for litigation. ACOG's 2025 guideline notes no clinical trials show computer-based interpretation improves newborn outcomes. Medrecords AI does not read the tracing or assign categories; it organizes and cites the chart entries around it.
Is it HIPAA compliant to upload birth injury records to AI?It can be, if the vendor signs a business associate agreement, protects the data under audited controls such as SOC 2, and does not train models on your records. Check those 3 things before any upload.
Can ChatGPT summarize labor and delivery records for a lawsuit?A general chatbot can produce a fluent summary, but without page-level citations every fact has to be checked by hand, and consumer tools may not offer a business associate agreement. For litigation, use a tool that cites every line to its source page and keep a person reviewing the output.
How does AI medical record review help in a birth injury case?It pulls every tracing-related entry, medication time, order and procedure time into 1 cited chronology, flags conflicting times and periods with no matching records, and flags low-confidence scanned or handwritten pages for a person to read.

Chapter 13 Everyone

### Sources and method

Sources were opened and checked on 24 October 2026. Quotes are verbatim. The anatomy figure, timeline, crosswalk, note versions and gap rows are hypothetical. Nothing here is legal or medical advice.

- ACOG, [Clinical Practice Guideline No. 10, Intrapartum Fetal Heart Rate Monitoring: Interpretation and Management](https://www.acog.org/clinical/guidance/clinical-practice-guideline/2025/10/intrapartum-fetal-heart-rate-monitoring-interpretation-and-management/), Obstetrics and Gynecology 146(4), October 2025. Replaces Practice Bulletins 106 and 116 and the January 2022 oxygen advisory. Checked 24 Oct 2026; current.
- ACOG, [Practice Bulletin No. 106, Intrapartum fetal heart rate monitoring: nomenclature, interpretation, and general management principles](https://pubmed.ncbi.nlm.nih.gov/19546798/), 2009 (reaffirmed 2017, replaced 2025). Definitions, review intervals and storage language.
- ACOG, [Practice Bulletin No. 116, Management of intrapartum fetal heart rate tracings](https://pubmed.ncbi.nlm.nih.gov/20966730/), 2010 (replaced 2025).
- Macones and colleagues, [The 2008 NICHD workshop report on electronic fetal monitoring](https://pubmed.ncbi.nlm.nih.gov/18757666/), Obstetrics and Gynecology 112(3), 2008.
- AWHONN, [Fetal Heart Monitoring position statement](https://www.jognn.org/article/S0884-2175(24)00040-6/fulltext), Journal of Obstetric, Gynecologic and Neonatal Nursing 53(3), revised April 2024. Checked 24 Oct 2026; current per [AWHONN's position statement list](https://awhonn.org/resources-and-information/published-resources/awhonn-position-statements/).
- Peleg and colleagues, [The effect of chart speed on fetal monitor interpretation](https://pubmed.ncbi.nlm.nih.gov/26100761/), J Matern Fetal Neonatal Med, 2016.
- ACOG and AAP, [Neonatal Encephalopathy and Neurologic Outcome](https://publications.aap.org/pediatrics/article/133/5/e1482/32738/Neonatal-Encephalopathy-and-Neurologic-Outcome), 2nd ed., 2014: tachysystole definition. Covered in depth in our HIE guide.
- [45 CFR 164.524](https://www.law.cornell.edu/cfr/text/45/164.524), HIPAA right of access: (b)(2) and (c)(2)(ii).
- [Federal Rule of Civil Procedure 37(e)](https://www.law.cornell.edu/rules/frcp/rule_37), failure to preserve electronically stored information.
- [Va. Code 38.2-5004(F)](https://law.lis.virginia.gov/vacode/title38.2/chapter50/section38.2-5004/), fetal monitoring strips deemed part of the medical record for the Virginia program.
- Mata v. Avianca, Inc., 678 F. Supp. 3d 443 (S.D.N.Y. 2023): Rule 11 sanctions for fabricated AI-generated citations.

Related guides: [HIE birth injury medical records](https://medrecords.ai/guides/hie-birth-injury-medical-records/), [EHR audit trails in medical malpractice](https://medrecords.ai/guides/ehr-audit-trail-medical-malpractice/), [altered medical records](https://medrecords.ai/guides/altered-medical-records/) and [how legal nurse consultants build a medical chronology](https://medrecords.ai/guides/how-legal-nurse-consultants-build-a-medical-chronology/).

### More guides

- [**HIPAA and AI medical record review: what to verify** — A buyer checklist for HIPAA compliant AI medical record review: the agreements, encryption, data residency, and…](https://medrecords.ai/guides/hipaa-compliant-ai-medical-record-review/)
- [**History and physical: what each part means and how to test it against the chart** — What goes in a history and physical, CMS 30-day and 24-hour rules, what studies show about copied and templated…](https://medrecords.ai/guides/history-and-physical/)
- [**How legal nurse consultants build a medical chronology, step by step** — How do legal nurse consultants build a medical chronology? A 9-step LNC workflow with time and output per step…](https://medrecords.ai/guides/how-legal-nurse-consultants-build-a-medical-chronology/)
- [**How much does a medical chronology cost in 2026?** — What a medical chronology costs in 2026: hourly, per-case and per-page rates from vendor pages, worked on a…](https://medrecords.ai/guides/medical-chronology-cost/)
- [**How to become an AI-native IME physician in 2026** — What IME and QME work pays, how to get certified, and where AI belongs in the record packet. Built on RAND…](https://medrecords.ai/guides/ai-native-ime-physician/)
- [**How to become an AI-native legal nurse consultant in 2026** — How to become a legal nurse consultant in 2026: salary, certification, the first case, and running the practice…](https://medrecords.ai/guides/ai-native-legal-nurse-consultant/)

### Ranked lists