510(k) Report

510(k) · Cleared

Recalled · 2005

Birthnet II Perinatal Patient Data Management System

K965008510(k) TraditionalCleared Dec 16, 1997365-day reviewClass II21 CFR 884.2740Recalls 1

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

Spacelabs Medical, Inc. · HGM System, Monitoring, Perinatal

Cleared on Dec 16, 1997 as substantially equivalent to K960109 (Quantitative Medicine, Inc., 1996) and 1 other predicate after a 365-day review. Its family tree reaches back 2 generations to 1984. 3 later devices descend from it. It has been recalled once.

Decided
Dec 16, 1997
Review
365 days
Class
Class II
Product code
HGM
Recalls
1
Predicates
2

Its longest line of descent runs back 2 generations to K833395 (1984). 4 ancestors in all. 3 later devices descend from it, 1 citing it directly.

Other ancestors, by year clearedDescendants, by year cleared 1990: 1 other ancestor1995: 1 other ancestor1998: 1 descendant cleared2011: 1 descendant cleared2005: 1 descendant clearedK833395 · Sentinel Systems · Quantitative Medicine, Inc. · 1984K960109 · Quantitative Sentinel System · Quantitative Medicine, Inc. · 199619801990200020102020
Other ancestors, by generationDescendants, by generation 1 generation back: 1 other ancestor2 generations back: 1 other ancestor 1 generation forward: 1 descendant2 generations forward: 2 descendants K960109 · Quantitative Sentinel System · Quantitative Medicine, Inc. · 1996K833395 · Sentinel Systems · Quantitative Medicine, Inc. · 19840
  1. Root · 2 generations backK833395 Sentinel SystemsQuantitative Medicine, Inc. · 1984
  2. 1 generation backK960109 Quantitative Sentinel SystemQuantitative Medicine, Inc. · 1996
  3. This deviceK965008 Birthnet II Perinatal Patient Data Management SystemSpacelabs Medical, Inc. · 1997
  4. Descendant · cites it directly · 2 of its ownK980719 CALMLms Medical Systems, Ltd. · 1998
  5. Descendant · 2 generations on · 0 of its ownK102263 Horizon Perinatal Care Surveillance and Archival Model Verson 4.0Mckesson Information Solutions, LLC · 2011
  6. Descendant · 2 generations on · 0 of its ownK052715 Calm Curve, Version 01.00Lms Medical Systems (Canada), Ltd. · 2005

Most influential descendants

Showing 3 of 3 · See all
  • K980719CALMLms Medical Systems, Ltd. · 1998 · cites it directly2descendants
  • K102263Horizon Perinatal Care Surveillance and Archival Model Verson 4.0Mckesson Information Solutions, LLC · 2011 · 2 generations on0descendants
  • K052715Calm Curve, Version 01.00Lms Medical Systems (Canada), Ltd. · 2005 · 2 generations on0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−2K833395Sentinel SystemsQuantitative Medicine, Inc.1984—
−1K960109Quantitative Sentinel SystemQuantitative Medicine, Inc.1996—
0 (this device)K965008Birthnet II Perinatal Patient Data Management SystemSpacelabs Medical, Inc.1997—
+1K980719CALMLms Medical Systems, Ltd.1998—
+2K102263Horizon Perinatal Care Surveillance and Archival Model Verson 4.0Mckesson Information Solutions, LLC2011—
+2K052715Calm Curve, Version 01.00Lms Medical Systems (Canada), Ltd.2005—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
199010
199510

Descendants by year cleared

Year clearedDevicesWith a Class I recall
199810
200510
201110
FIG. 1 — Lineage of K965008, 1984–2011Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.

Planning a device in HGM? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

Top candidate predicates for a new HGM device

  1. #1 K241882 Fetal & Maternal Monitor (F15A, F15A Air)score 19.5 · 33 generations · no Class I recall
  2. #2 Held for the reportin the report
  3. #3 Held for the reportin the report
Get a 510(k) Report

What was it cleared against? (2)

Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.

TypeNumberDeviceApplicantDecidedRecalls
*K960109Quantitative Sentinel System
Summary page 1
…. 3. Predicate Devices: The AMS BirthNet ™ II Perinatal Patient Data Management System is substantial equivalent to the Quantitative Sentinel Perinatal, as described in K960109; and the Air Shield WatchChild as described in K893981. 4. The BirthNet ™ II Perinatal Patient Data Management System is a compr…
Quantitative Medicine, Inc.1996—
*K893981Watchchild
Summary page 1
…l Patient Data Management System is substantial equivalent to the Quantitative Sentinel Perinatal, as described in K960109; and the Air Shield WatchChild as described in K893981. 4. The BirthNet ™ II Perinatal Patient Data Management System is a comprehensive on- line, real-time information system to coll…
Monox, Inc.1990—

Also cleared against K960109: 3 other devices →

What descends from it? (3)

1 later device cites it directly; ranked here by how many devices descend from each in turn.

NumberDeviceApplicantDecidedDescendants
K980719CALMLms Medical Systems, Ltd.19982

Has anything in its family been recalled? (0 Class I)

Recalls of this device

DateClassRecallRoot causeReason
Oct 13, 2005Not classifiedZ-0115-06OtherPotential for incorrect weight to be displayed.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 13 years and passes through 2 companies; a new generation was cleared every 12.6 years on median.
  • None of the 4 ancestors has a recall.
  • Of its descendants, K980719 (Lms Medical Systems, Ltd., 1998) has gone furthest, with 2 descendants of its own.
  • 3 other devices also cite its predicate K960109.

How does its category compare?

All HGM devices

HGM System, Monitoring, Perinatal: FDA decisions, review times, recalls and adverse event reports over 20 years.

FDA decisions per year · HGM

4in 2025

2007: 32008: 42009: 42010: 42011: 132012: 42013: 22014: 42015: 52016: 12017: 32018: 32020: 12022: 12023: 22024: 12025: 42026 (partial year): 2
2007high 13 (2011) · low 0 (2019)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · HGM

269in 2025

2007: 56 days median2008: 75 days median2009: 66 days median2010: 193 days median2011: 141 days median2012: 107 days median2014: 231 days median2015: 169 days median2017: 138 days median2018: 258 days median2025: 269 days median
2007high 269 (2025) · low 56 (2007)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · HGM

5in 2019

2008: 42009: 62013: 12014: 12019: 52026 (partial year): 2
2007high 6 (2009) · low 0 (2007)2026

Class I (0 since 2007) Class II/III not classified

Adverse event reports per year · HGM

99in 2025

2007: 352008: 172009: 422010: 642011: 832012: 442013: 162014: 302015: 442016: 172017: 272018: 302019: 412020: 192021: 712022: 872023: 692024: 1742025: 99
2007high 174 (2024) · low 16 (2013)2025

MAUDE reports naming product code HGM, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
2007356035
2008475417
2009466642
20104193064
201113141083
20124107044
20132—116
20144231130
20155169044
20161—017
20173138027
20183258030
20190—541
20201—019
20210—071
20221—087
20232—069
20241—0174
20254269099
20262—2—

What is it indicated for?

The BirthNet™ Il Perinatal Patient Data Management System is designed for use in the following functions: a) Collect fetal monitor data for the purpose of central surveillance, local surveillance, review, annotation, and for archiving data for long storage. b) Report alert conditions generated by the AMS fetal monitors or the AMS computer interface module (CIM). c) Collect physiological, maternal and fetal data directly from physiological monitors and…

Read the full statement (224 words)

The BirthNet™ Il Perinatal Patient Data Management System is designed for use in the following functions:

a) Collect fetal monitor data for the purpose of central surveillance, local surveillance, review, annotation, and for archiving data for long storage.

b) Report alert conditions generated by the AMS fetal monitors or the AMS computer interface module (CIM).

c) Collect physiological, maternal and fetal data directly from physiological monitors and append such data to the proper patient database table.

d) Feed back selected data items to the AMS fetal monitor for the purpose of printing such data on the fetal monitor strip in real time.

e) Enable manual patient data entry into the system for the purpose of charting.

f) Assemble and display selected data in a summary format of r more efficient review capability by the care giver.

g) Validate data entry when applicable to ensure data integrity.

h) Print pre-formatted reports on individual patients

i) Reproduce fetal monitor records from storage to a printer or an AMS UR10 (stripped down fetal monitor) recorder.

j) Transmit selected items from the database via fax.

k) Enable authorized (password) care giver to access the system remotely.

l) Generate an audit trail for all transactions.

m) Generate statistics reports for quality assurance.

n) Facilitate the generation of a birth certificate by providing pertinent patient data acquired by the system.

Indications for use read by OCR from a scanned FDA summary, so letters may be misread. Check the PDF before quoting it.

Cite this page

510(k) Report. “K965008: Birthnet II Perinatal Patient Data Management System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 4, 2026. https://510kreport.com/device/K965008

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

Record history
  • FDA decision record loaded May 2, 2026
  • Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026