HomeFetal Monitoring & Non-Stress TestFetal Scalp pH Sampling Simulator

💓 Fetal Scalp pH Sampling Simulator

This simulation demonstrates the process of obtaining a scalp pH sample from the fetus to assess acid-base status and guide management decisions during labor.

Fetal Monitoring & Non-Stress Test2DModerate60 FPS
fetal-scalp-ph-sampling-simulator ↗ Open standalone

Category II FHR Tracings and the Rationale for Scalp Blood Sampling

Continuous electronic fetal monitoring (EFM) classifies intrapartum fetal heart rate patterns into three categories. Category I is normal and requires no intervention beyond routine surveillance; Category III is abnormal and mandates prompt action. Category II — the indeterminate middle ground — comprises the majority of tracings encountered clinically and includes a heterogeneous mix of patterns (minimal variability, recurrent variable decelerations, late decelerations with preserved variability, tachycardia without other features) that are neither clearly reassuring nor clearly predictive of fetal acidemia. Fetal scalp blood sampling was historically developed to add objective biochemical data to this ambiguous clinical picture.

  • I / II / III: FHR categories (NICHD 3-tier system)
  • ~80%: Category II prevalence (of intrapartum tracings at some point)
  • ≥3–4 cm: Cervical dilation needed (membranes ruptured, vertex accessible)
  • 7.25 / 7.20: Classic pH threshold (normal / abnormal cutoffs)

Physiologic basis: what capillary scalp blood actually measures

Fetal scalp capillary blood is arterialized peripheral blood obtained by warming/hyperemia of the puncture site and free flow (not squeezed) collection, intended to approximate systemic fetal acid-base status:

What the sample reflects: • pH — the net balance of respiratory (CO2) and metabolic (fixed acid/lactate) components of fetal acid-base state • pCO2 — respiratory component; reflects umbilical cord compression, reduced placental gas exchange, or maternal hyperventilation/hypoventilation • Base excess / base deficit — the metabolic component; reflects accumulation of lactic and other fixed acids from anaerobic metabolism • Lactate — a direct marker of anaerobic glycolysis, rises when oxygen delivery to fetal tissue is insufficient to sustain aerobic metabolism

Respiratory vs metabolic acidosis — why the distinction matters: • Respiratory acidosis: low pH with elevated pCO2 but near-normal base excess. Usually reflects transient impairment of gas exchange (e.g., cord compression during a contraction). Often resolves quickly with position change or reduced uterine activity and is generally well tolerated by the fetus in the short term. • Metabolic acidosis: low pH with a significantly negative base excess and elevated lactate, reflecting a more sustained oxygen deficit and anaerobic metabolism. This pattern correlates far more strongly with the risk of hypoxic-ischemic injury and is the pattern of greatest concern. • Mixed acidosis: both respiratory and metabolic components are abnormal — the most common pattern seen in genuinely compromised fetuses and the pattern most predictive of a depressed neonate.

Why pH alone can be misleading: • Two fetuses can have an identical pH of 7.15 — one from a transient cord compression episode (respiratory, high pCO2, normal-ish base excess) that will recover promptly, and another from sustained placental insufficiency (metabolic, markedly negative base excess) reflecting real hypoxic stress. This is precisely why modern practice increasingly reports base excess and lactate alongside pH rather than pH in isolation.

Correlation with hypoxia and injury risk: • The fetus buffers transient hypoxic episodes via anaerobic glycolysis, redistribution of blood flow to brain/heart/adrenals (the "brain-sparing" reflex), and buffering capacity of fetal blood and tissue. • Once buffering capacity is exhausted and metabolic acidosis becomes pronounced (base deficit >12 mmol/L is a commonly cited threshold in cord gas literature for significant metabolic acidemia), the risk of hypoxic-ischemic encephalopathy and other adverse neonatal outcomes rises substantially. • Scalp sampling therefore functions as a real-time checkpoint: does the indeterminate FHR pattern correspond to a fetus that is still compensating well, or one that is beginning to decompensate metabolically?

Clinical decision-making context — when scalp sampling is considered

Scalp pH/lactate sampling is not performed reflexively for every Category II tracing. It is considered selectively, typically after first-line conservative measures have been attempted and the tracing remains concerning:

Typical sequence of intrapartum management before sampling: • Maternal repositioning (lateral position to relieve aortocaval compression) • Correction of maternal hypotension, especially after epidural placement • Reduction or discontinuation of oxytocin to reduce contraction frequency/intensity • IV fluid bolus • Consideration of tocolysis for tachysystole • Amnioinfusion if variable decelerations are attributed to cord compression with oligohydramnios • Fetal scalp stimulation as a first, non-invasive check (see Stage 4 discussion)

When the tracing remains Category II despite these measures — and especially when it shows recurrent decelerations with reduced variability, or a rising baseline suggesting evolving hypoxia or chorioamnionitis — the clinician faces a binary-feeling decision: continue labor with close surveillance, or move to operative/cesarean delivery. Scalp sampling exists to inform that decision with objective biochemical data rather than pattern recognition alone, potentially avoiding an unnecessary operative delivery for a fetus that is, in fact, well compensated, while also identifying a fetus that truly needs expedited delivery despite a tracing that looks only moderately concerning.

Prerequisites for the procedure: • Cervix dilated enough to allow instrument passage and scalp access (commonly cited as roughly ≥3–4 cm, though this varies by fascility and presentation) • Membranes ruptured (artificial rupture may be performed if not already ruptured) • Vertex presentation with the presenting part low enough and accessible • No contraindication present (covered in Stage 2) • Immediate availability of a point-of-care blood gas/lactate analyzer, since the value of the sample depends entirely on rapid turnaround

Performing Fetal Scalp Blood Sampling — Technique and Contraindications

Fetal scalp blood sampling is a brief transvaginal procedure performed with the mother in the dorsal lithotomy position. An amnioscope (a cone-shaped speculum, sometimes called an "amnioscope" or simply a sampling cone) is passed through the cervix and seated firmly against the fetal presenting part to create direct visual and mechanical access to the scalp, after which a small stab incision yields a free-flowing capillary blood sample for immediate blood gas and lactate analysis.

  • ~2 mm: Incision depth (guarded scalp blade)
  • ~35–50 µL: Sample volume needed (heparinized capillary tube)
  • 2–5 min: Procedure time (placement to sample collection)
  • ~60–90 sec: Turnaround to result (point-of-care analyzer)

Step-by-step technique

The procedure follows a consistent sequence designed to maximize sample quality while minimizing trauma and infection risk:

1. Positioning and preparation: • Mother positioned in dorsal lithotomy (or left lateral if preferred), similar to a vaginal examination • Sterile gloves, antiseptic preparation of the perineum • Membranes confirmed ruptured (artificial rupture performed if needed) to allow direct instrument access

2. Amnioscope / cone placement: • A hollow cone-shaped amnioscope with an integrated light source is introduced through the vagina and cervix under digital guidance • The cone is advanced until it is seated firmly and snugly against the fetal presenting part (the scalp in vertex presentation) — a secure seal is essential both for visualization and to stabilize the site for incision • Correct placement is confirmed visually through the cone; the caput or scalp surface should be clearly seen, free of excess vernix, blood, or amniotic debris

3. Site preparation: • The scalp is cleaned and dried using a swab, sometimes with a small amount of silicone/petroleum gel applied to encourage the blood to bead rather than spread across the scalp surface • Gentle pressure or an ethyl chloride spray may be used to induce local hyperemia, improving free flow of arterialized capillary blood

4. Stab incision: • A disposable, guarded scalp blade (blade depth fixed at approximately 2 mm to prevent excessive penetration) is used to make a small, quick stab incision in the scalp, avoiding the fontanelles, sutures, face, and genitalia • The incision should be just deep enough to produce a free-flowing droplet of capillary blood — deep enough to bleed adequately, shallow enough to avoid unnecessary trauma

5. Blood collection: • Free-flowing (not squeezed or "milked") blood is collected into a pre-heparinized, narrow-bore glass capillary tube by capillary action, minimizing air bubble introduction and clotting • A metal filar or "flea" is sometimes inserted into the tube and moved along a magnet to mix the heparin and prevent clotting during transport • The tube is capped/sealed at both ends immediately to prevent air exposure, which would alter blood gas values

6. Post-procedure: • Firm pressure applied to the puncture site with a swab until bleeding stops (typically well under a minute given the small incision) • The site is inspected before the cone is withdrawn to confirm hemostasis • Continuous FHR monitoring resumes immediately; the sample is rushed to the point-of-care analyzer for immediate pH/lactate/blood-gas measurement

Sample quality caveats: a sample contaminated with air bubbles, amniotic fluid, or maternal blood — or one that clots before analysis — is unreliable and should prompt a repeat attempt rather than acting on a spurious result.

Contraindications and safety considerations

Because scalp sampling creates a small skin-breaking wound and exposes the operator and mother to fetal blood, several categories of contraindication are recognized:

Infectious contraindications (fetal blood exposure / vertical transmission risk): • Maternal HIV infection — a scalp wound theoretically increases the risk of maternal-to-fetal blood exposure and has historically been considered a contraindication, particularly when maternal viral load is not well controlled • Maternal hepatitis B or hepatitis C infection — similar rationale regarding blood-borne vertical transmission risk through a fresh fetal skin wound • Active maternal genital herpes (HSV) with visible lesions — theoretical risk of inoculating the fetal scalp wound with virus during passage through an infected lower genital tract

Bleeding-risk contraindications: • Known or suspected fetal bleeding diathesis (e.g., suspected hemophilia in a male fetus with maternal carrier status, or other inherited coagulopathy) — an intentional puncture wound in a fetus with impaired clotting risks significant or prolonged bleeding • Maternal coagulopathy is a more relative concern (the wound is fetal, not maternal) but is still generally considered in the overall risk-benefit assessment, particularly regarding the mother's own bleeding risk from the associated vaginal examination and instrumentation • Fetal thrombocytopenia (e.g., known alloimmune thrombocytopenia) is a relative contraindication for the same bleeding-risk reasons

Anatomic / technical contraindications: • Face presentation — the presenting part is the face rather than the vertex, making the scalp inaccessible and risking injury to the eyes, mouth, or other facial structures; this is an absolute contraindication for standard scalp site sampling • Inadequate cervical dilation or inability to seat the amnioscope securely against the presenting part • Presenting part too high/mobile to allow safe, stable access

Gestational age considerations: • Extreme prematurity (commonly cited threshold around <34 weeks) is treated as a relative caution — preterm scalp/skin is more fragile, the sample volume needed can be a larger fraction of a preterm fetus's total blood volume, and interpretation thresholds derived largely from term studies are less well validated in the preterm population • In practice, at very preterm gestations most centers favor either non-invasive assessment or, if the tracing is truly concerning, delivery rather than an invasive scalp procedure

Operational considerations: • The procedure requires an operator experienced in the technique and an immediately available point-of-care blood gas/lactate analyzer — where either is unavailable, the procedure is effectively not feasible regardless of clinical indication, which is one of the major practical reasons for its decline (discussed further in Stage 4)

Interpreting Scalp pH, Lactate, and Base Excess Against Clinical Thresholds

Once the capillary sample reaches the point-of-care analyzer, results return within roughly a minute and must be interpreted against established thresholds to guide the next clinical decision: reassurance and continued labor, a repeat sample in a defined interval, or expedited delivery. The classic threshold scheme, descended from Saling's original work and referenced in ACOG practice guidance, uses pH as the primary discriminator, with lactate and base excess providing corroborating metabolic detail.

  • pH ≥ 7.25: Normal (reassuring) (resume routine surveillance)
  • pH 7.20–7.24: Borderline (repeat sample in ~30 min)
  • pH < 7.20: Abnormal (expedite delivery)
  • ≥4.8 mmol/L: Lactate cutoff (adjunct) (often paired with abnormal pH)

The classic three-tier pH threshold scheme

The interpretive framework most widely taught and referenced (rooted in Erich Saling's original technique and widely echoed in ACOG practice guidance) divides results into three actionable tiers:

pH ≥ 7.25 — Normal / Reassuring: • Considered consistent with adequate fetal oxygenation and a well-compensated acid-base state at the time of sampling • Labor may continue with routine or slightly intensified FHR surveillance; no immediate change in the delivery plan is mandated by this result alone • Because the result reflects only a single point in time, ongoing clinical judgment and continued monitoring of the FHR tracing remain essential — a reassuring pH does not guarantee the tracing will remain reassuring going forward

pH 7.20–7.24 — Borderline / Preacidotic: • Represents an equivocal zone; not clearly reassuring, not yet clearly abnormal • Standard practice is to repeat the sample within approximately 30 minutes (sooner if the FHR tracing worsens in the interim) to establish a trend rather than rely on a single borderline value • A repeat value that has improved or stabilized is more reassuring than one that has fallen further, even if both technically remain in the borderline band — the trajectory carries as much information as the absolute number • Clinical context matters heavily here: a borderline value in the setting of a rapidly progressing labor with an otherwise improving tracing is managed differently than the same value with a persistently non-reassuring tracing

pH < 7.20 — Abnormal / Acidotic: • Considered indicative of significant fetal acidemia and an unacceptably elevated risk of ongoing hypoxic compromise • Standard recommendation is to expedite delivery (operative vaginal delivery if criteria are met, otherwise cesarean delivery), rather than repeating the sample and waiting • The urgency of delivery should also be weighted by absolute pH value, trend from any prior sample, base excess/lactate, and the real-time FHR tracing rather than treated as a rigid, isolated cutoff

Role of lactate and base excess as adjuncts: • A markedly negative base excess (often cited around ≤ -8 to -12 mmol/L as a concerning metabolic threshold) or an elevated lactate in the setting of a borderline pH raises concern that the acidemia is predominantly metabolic rather than respiratory, and therefore more likely to reflect a genuinely hypoxic, poorly-compensating fetus rather than a transient respiratory effect from cord compression • Conversely, a borderline pH with a near-normal base excess and only mildly elevated lactate is more reassuring, suggesting a predominantly respiratory pattern that is more likely transient

Distinguishing respiratory, metabolic, and mixed acidemia at the bedside

Use the simulator's "Acidosis Type" control to see how, at an identical pH, a shift toward the metabolic end of the spectrum drives lactate up and base excess sharply more negative, while a shift toward the respiratory end leaves base excess relatively preserved:

Respiratory-predominant pattern: • pH low, pCO2 elevated, base excess only mildly negative, lactate only mildly elevated • Typical mechanism: transient cord compression during contractions, reducing umbilical blood flow and CO2 clearance without a sustained oxygen deficit • Clinical implication: often resolves with position change, reduced contraction frequency, or amnioinfusion; a repeat sample after such an intervention frequently normalizes

Metabolic-predominant pattern: • pH low, base excess markedly negative, lactate significantly elevated, pCO2 relatively less deranged • Typical mechanism: sustained impairment of oxygen delivery — placental insufficiency, abruption, prolonged severe cord compression, uterine tachysystole — driving anaerobic glycolysis and fixed acid accumulation • Clinical implication: this pattern correlates most strongly with the risk of hypoxic-ischemic injury and generally argues most strongly for expedited delivery, even at a pH value that alone might look only modestly abnormal

Mixed pattern: • Combination of the two; most commonly seen in fetuses with genuine, ongoing compromise, since an initial respiratory insult that is not corrected tends to evolve into a mixed or metabolic picture as compensatory mechanisms are progressively exhausted

Why repeating a borderline sample matters clinically: • A single value is a snapshot; labor is dynamic • A rising lactate or falling base excess on a repeat sample, even if pH itself has not yet crossed 7.20, signals a deteriorating trend that should prompt escalation of care regardless of the absolute pH threshold • This trend-based reasoning is a major part of why experienced clinicians treat the numeric thresholds as decision aids embedded in a broader clinical picture, not as a rigid, stand-alone algorithm

Correlating Scalp Sampling with Cord Gases at Birth, and Why the Technique Has Declined

The ultimate validation of any intrapartum scalp sample is what happens at delivery: umbilical artery and vein blood gas values, obtained from a segment of double-clamped cord immediately after birth, provide the definitive record of the fetus's acid-base status at the moment of delivery. Comparing the trend of intrapartum scalp values to these cord gases closes the interpretive loop — and, together with the practical burdens of the procedure, helps explain why routine scalp pH sampling has become far less common in many modern labor and delivery units, even as scalp lactate testing and non-invasive alternatives have grown in relative importance.

  • ≥ 7.10–7.20: Normal UA pH (lab-dependent reference range)
  • BD ≥12 mmol/L: Significant metabolic acidemia (umbilical arterial base deficit)
  • ~5 µL: Scalp lactate sample volume (vs ~35–50 µL for full blood gas)
  • Uncommon: Modern utilization (largely supplanted in many units)

Umbilical cord blood gas correlation and outcome prediction

Immediately after delivery, a segment of umbilical cord is double-clamped and both the umbilical artery (reflecting fetal condition, since it carries blood away from the fetus toward the placenta) and umbilical vein (reflecting placental/maternal exchange, blood returning to the fetus) are sampled for blood gas analysis:

Why the umbilical artery sample is the key reference standard: • Umbilical arterial blood has just left the fetus and therefore most directly reflects fetal metabolic status at the moment of birth, distinct from the vein which reflects blood coming from the placenta toward the fetus • A normal umbilical arterial pH and base deficit at birth is one of the most reassuring pieces of objective evidence that the fetus tolerated labor well, and is frequently used medico-legally and in quality-review settings to characterize the adequacy of intrapartum management

Expected correlation with a reassuring scalp sampling trend: • A fetus whose last intrapartum scalp pH was ≥7.25 (or whose serial values were stable/improving) would be expected, in the great majority of cases, to have a normal umbilical arterial pH and base deficit at delivery, and to be born in good condition (reassuring Apgar scores, no need for extensive resuscitation) • When a fetus with reassuring scalp values is later found to have unexpectedly poor cord gases or a depressed neonate, this discordance usually reflects either a rapid, acute intrapartum event occurring after the last sample (e.g., cord prolapse, abruption, uterine rupture) rather than a failure of the scalp value itself — reinforcing that scalp sampling reflects status only at the moment it is drawn

When scalp trends predict abnormal cord gases: • A falling pH trend, rising lactate, or worsening base excess on serial scalp sampling that culminates in an abnormal final value (pH <7.20) correlates reasonably well with subsequent umbilical arterial acidemia, particularly when the metabolic component (base deficit, lactate) is prominent rather than purely respiratory • This is precisely the scenario the technique is designed to catch early — identifying a fetus trending toward significant acidemia while there is still time to intervene via expedited delivery, rather than only discovering the acidemia retrospectively from cord gases after an adverse outcome

Limitations of the correlation: • The interval between the last scalp sample and delivery may be substantial, during which fetal status can change significantly in either direction • Sampling technique, contamination, and analyzer calibration all introduce variability that can create discordance between intrapartum and birth values independent of true physiologic change

Modern alternatives and the decline of routine scalp pH sampling

Full scalp blood gas sampling (pH + pCO2 + base excess) has become substantially less common in many contemporary labor and delivery units, for a combination of clinical-evidence and practical-operational reasons:

Fetal scalp stimulation test — the leading non-invasive alternative: • A gloved, sterile digital vaginal examination is used to firmly stimulate the fetal scalp (typically alongside or instead of vibroacoustic stimulation) • A resulting FHR acceleration (commonly defined as ≥15 bpm above baseline for ≥15 seconds, similar to a reactive non-stress test criterion) is considered a reassuring surrogate for a normal fetal pH, based on studies correlating the presence of an acceleration with a low likelihood of significant acidemia • Major advantage: entirely non-invasive, essentially no procedural risk, no contraindications related to infection or coagulopathy, immediately available at the bedside without any laboratory equipment, and can be repeated freely • Limitation: a reassuring acceleration is a reasonably good rule-out for acidemia, but the absence of an acceleration is a much weaker rule-in for acidemia — a non-reacting fetus may simply be in a quiet sleep state rather than acidotic, so a negative test often still prompts further evaluation rather than immediate delivery

Scalp lactate-only sampling: • A smaller-volume capillary sample (on the order of 5 microliters, versus 35–50 microliters for a full blood gas) is applied directly to a portable lactate analyzer strip • Advantages over full pH/blood-gas sampling: technically easier to obtain adequate volume (a major source of failed/repeat scalp pH attempts is insufficient sample volume), faster turnaround, less expensive point-of-care equipment, and evidence from randomized comparisons suggesting equivalent or superior predictive performance for adverse outcome compared with pH alone • In units that have retained some form of invasive scalp sampling, lactate-only testing has increasingly been favored over full pH/blood-gas analysis for exactly these practical reasons

Why overall utilization has declined: • Technical difficulty: the procedure requires adequate cervical dilation, ruptured membranes, an accessible vertex, and a skilled operator — many real-world attempts fail to yield an adequate sample on the first pass • Time delay and workflow burden: assembling the equipment, performing the procedure, and awaiting analysis takes several minutes during an already time-pressured clinical scenario, and repeat sampling for a borderline result compounds this delay • Maternal discomfort and the invasive nature of an additional vaginal instrumentation during active labor • Equipment availability: not all units maintain a functioning point-of-care blood gas analyzer with reagents on the labor floor at all times, and staff familiarity/competency with the technique has declined as it is used less often — a self-reinforcing cycle • Mixed evidence base: randomized and observational evidence on whether routine scalp pH sampling, when added to continuous EFM, meaningfully improves neonatal outcomes (versus EFM plus clinical judgment and other adjuncts) has been inconsistent, and some analyses have not demonstrated a clear reduction in cesarean delivery rates or improvement in neonatal metrics attributable specifically to routine scalp sampling • Net effect: many contemporary labor units have shifted toward a strategy of continuous EFM interpretation using the standardized 3-tier category system, first-line conservative measures, fetal scalp stimulation as a rapid non-invasive adjunct, and a lower threshold for proceeding to delivery when a Category II tracing fails to resolve — reserving full invasive scalp blood sampling (pH or lactate) for select centers, select clinical scenarios, or settings where it remains part of established local protocol

⚙ Under the hood

This simulation demonstrates the process of obtaining a scalp pH sample from the fetus to assess acid-base status and guide management decisions during labor.

CanvasBiomedicine

2D · HTML5 Canvas 2D · 60 FPS target · runs fully client-side, no install

What did you find?

Add reproduction steps (optional)