BIRTHNET II PERINATAL PATIENT DATA MANAGEMENT SYSTEM
K965008 · Spacelabs Medical, Inc. · HGM · Dec 16, 1997 · Obstetrics/Gynecology
Device Facts
Record ID
K965008
Device Name
BIRTHNET II PERINATAL PATIENT DATA MANAGEMENT SYSTEM
Applicant
Spacelabs Medical, Inc.
Product Code
HGM · Obstetrics/Gynecology
Decision Date
Dec 16, 1997
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 884.2740
Device Class
Class 2
Attributes
Pediatric
Indications for Use
The BirthNet™ II 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.
Device Story
BirthNet™ II is a real-time perinatal patient data management system; collects physiological data (fetal heart rate, uterine activity) from AMS fetal monitors and other physiological monitors; integrates manual clinician-entered data (medicinal administrations, physiological conditions). System operates via hospital-based workstations; allows remote access for authorized caregivers. Outputs include real-time displays, printed reports, archived records on optical disks, and statistical reports for quality assurance. Facilitates clinical decision-making by centralizing patient data for review and annotation; enables efficient monitoring of multiple patients. Benefits include improved data management, streamlined charting, and support for birth certificate generation.
Clinical Evidence
Bench testing only. The system underwent extensive safety and performance testing, including comprehensive validation of system requirements and compliance with applicable industry and safety standards.
Technological Characteristics
System consists of interface modules with surface-mounted printed circuit boards and software. Interfaces with AMS fetal monitors and third-party physiological monitors. Data storage via optical disks. Connectivity includes hospital-based workstations and remote access. Software is validated and functionally tested.
Indications for Use
Indicated for use in pregnancy, delivery, and early neonatal care to capture, display, and manage physiological obstetrical and fetal patient data for multiple patients simultaneously.
Regulatory Classification
Identification
A perinatal monitoring system is a device used to show graphically the relationship between maternal labor and the fetal heart rate by means of combining and coordinating uterine contraction and fetal heart monitors with appropriate displays of the well-being of the fetus during pregnancy, labor, and delivery. This generic type of device may include any of the devices subject to §§ 884.2600, 884.2640, 884.2660, 884.2675, 884.2700, and 884.2720. This generic type of device may include the following accessories: Central monitoring system and remote repeaters, signal analysis and display equipment, patient and equipment supports, and component parts.
{0}
K965008 1/2
# 510(k) Summary
## Advanced Medical Systems BirthNet™ II Perinatal Patient Data Management System
DEC 16 1997
1. Submitter’s Name: Advanced Medical Systems, Inc.
925 Sherman Avenue
Hamden, CT 06514
Telephone: (800) 325-2070
Facsimile: (203) 288-9032
2. Name of Device: BirthNet™ II Perinatal Patient Data Management System
Classification: The BirthNet™ II Perinatal Patient Data Management System is classified under Perinatal Monitoring System and Accessories which has been classified as a Class II device, in accordance to 21 CFR 884.2740.
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 comprehensive online, real-time information system to collect, display, and store physiological (e.g. fetal heart rate and uterine activity) data and other pertinent patient medical information. Designed specifically for pregnancy, delivery, and early neonatal care, medical personnel can review the status and management of each patient form any hospital based workstation. The primary function of the BirthNet™ II Perinatal Patient Data Management System is to automatically receive and record physiological monitoring data, and correlate this data with health care practitioner supplied data such as medicinal administrations, and recognized physical and physiological conditions.
The BirthNet™ II Perinatal Patient Data Management System is also designed to interface with all AMS fetal monitors and most all fetal and maternal physiological monitors presently available. Patient information can be archived onto optical disks for long-term storage. Aggregate statistical reports can also be generated.
{1}
<965008 2/3>
5. The BirthNet™ II Perinatal Patient Data Management System is designed for use to capture, display, and manage physiological obstetrical and fetal patient data. It is intended to permit the real-time monitoring of multiple obstetrical and fetal patients simultaneously, and to correlate non-monitored patient data with monitored physiological parameters.
6. The BirthNet™ II Perinatal Patient Data Management System software is manufactured by conventional CD-ROM replication from an authenticated master image under configuration control. The interface modules are comprised of surface mounted printed circuit boards and manufactured in a conventional manner. The installed software is validated prior to release and functionally tested at installation using validated test software.
7. The BirthNet™ II Perinatal Patient Data Management System has been subject to extensive safety testing and will be subject to extensive performance testing prior to release. Final testing for the system includes a comprehensive validation of the entire system requirements. Safety tests have been performed to ensure the device complies to all applicable industry and safety standards.
In conclusion, the BirthNet™ II Perinatal Patient Data Management System is as safe and effective as the predicate devices and raises no new issues.
{2}
DEPARTMENT OF HEALTH & HUMAN SERVICES
Public Health Service
Food and Drug Administration
9200 Corporate Boulevard
Rockville MD 20850
DEC 16 1997
Mr. Anthony Calderoni
Vice President
Advanced Medical System, Inc.
925 Sherman Avenue
Hamden, Connecticut 06514
Re: K965008
BirthNet™ II Perinatal Patient Data Management System
Dated: September 24, 1997
Received: September 29, 1997
Regulatory class: II
21 CFR §884.2740/Product code: 85 HGM
Dear Mr. Calderoni:
We have reviewed your Section 510(k) notification of intent to market the device referenced above and we have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act). You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration.
If your device is classified (see above) into either class II (Special Controls) or class III (Premarket Approval), it may be subject to such additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 895. A substantially equivalent determination assumes compliance with the Current Good Manufacturing Practice requirement, as set forth in the Quality System Regulation (QS) for Medical Devices: General regulation (21 CFR Part 820) and that, through periodic QS inspections, the Food and Drug Administration (FDA) will verify such assumptions. Failure to comply with the GMP regulation may result in regulatory action. In addition, FDA may publish further announcements concerning your device in the Federal Register. Please note: this response to your premarket notification submission does not affect any obligation you might have under sections 531 through 542 of the Act for devices under the Electronic Product Radiation Control provisions, or other Federal laws or regulations.
This letter will allow you to begin marketing your device as described in your 510(k) premarket notification. The FDA finding of substantial equivalence of your device to a legally marketed predicate device results in a classification for your device and thus, permits your device to proceed to the market.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801 and additionally 809.10 for in vitro diagnostic devices), please contact the Office of Compliance at (301) 594-4613. Additionally, for questions on the promotion and advertising of your device, please contact the Office of Compliance at (301) 594-4639. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). Other general information on your responsibilities under the Act may be obtained from the Division of Small Manufacturers Assistance at its toll-free number (800) 638-2041 or (301) 443-6597 or at its Internet address http://www.fda.gov/cdrh/dsmamain.html".
Sincerely yours,

Enclosure
{3}
Page 1 of 1
510(k) Number (if known): K965008
Device Name: BirthNet™ II Perinatal Patient Data Management System
Indications for Use:
The BirthNet™ II 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.
(PLEASE DO NOT WRITE BELOW THIS LINE. CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
(Division Sign-Off)
Division of Reproductive, Abdominal, ENT, and Radiological Devices
510(k) Number K96 5008
Prescription Use ☑ (Per 21 CFR 801.109)
OR
Over-The-Counter Use ☐
(Optional Format 1-2-96)
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.