The CIVNET CIV-ob is a software application that is intended for use as a clinical data management system (also referred to as a clinical information system - CIS). The function of the system is the management of fetal and maternal vital heart rate and uterine vital signs clinical data automatically acquired from a bedside fetal monitor, for the purpose of providing, ready and organized access to patient and/or clinical data that would normally be provided on paper records and/or separate clinical systems/devices. The CIV-ob serves as an electronic medical record. The CIV-ob operates with off-the-shelf software and hardware. The device is intended for use in a hospital/clinical environment.
Device Story
CIV-ob is a clinical information system (CIS) for obstetrical monitoring; manages fetal/maternal heart rate and uterine vital signs. Inputs: real-time data from bedside fetal monitors via interface protocols. Transformation: software processes, archives, and displays data; provides visual notifications for out-of-limit heart rates or poor signal quality; enables multi-bed monitoring. Output: electronic patient record, remote data review via TCP/IP, and printed reports. Used in hospital/clinical settings by healthcare providers. Benefits: replaces paper records with organized electronic access; facilitates remote monitoring and data storage; improves clinical workflow efficiency.
Clinical Evidence
Bench testing only. Validation performed via software test procedures addressing communication, power loss, out-of-limit conditions, server communication, installation, memory capacity, and user interface risks (data security/accuracy).
Technological Characteristics
Software application operating on off-the-shelf hardware. Connectivity via TCP/IP for remote review and IT system interfacing. Complies with IEC 60601-1-4 (Computer Controlled Medical Devices).
Indications for Use
Indicated for automatic fetal monitor patient data management in hospital/clinical environments. Facilitates display, archiving, and remote review of fetal heart rate and uterine (TOCO) vital signs. Provides visual alerts for high/low heart rate and poor signal quality. Intended for prescription use.
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.
Predicate Devices
GE Marquette Medical Quantitative Sentinel System (K993008)
{0}------------------------------------------------
K051175 page
# FEB 1 7 2006
### 510(k) Summary
CIV-ob Obstetrical Monitoring Software Application
510(k) Number K_
## Submitter's Name:
CIVNET Communication Ltd. Meshk 58, Ben Natan Moshav Hemed, Israel 50295 Tel: 972-3-6962240 / Ext 218 Mobile: 972-524-640089 Fax: 972-3-9607842 E-mail: rudi.lokits@ness.com
#### Contact Person:
Rudi Lokits Tel: 972-524-640089 E-mail: rudi.lokits@ness.com
Trade Name:
CIV-ob Obstetrical Monitoring Software Application
#### Classification Name:
System, Monitoring, Perinatal
### Classification:
The FDA has classified these devices as a class II device (product code HGM) and are reviewed by the Obstetrics and Gynecology Devices Group.
{1}------------------------------------------------
### Predicate Devices:
The CIV-ob Obstetrical Monitoring Software Application is substantially equivalent to:
· GE Marquette Medical Quantitative Sentinel System, cleared under K993008, Dec 6, 1999.
- · ClinComp. Intl CIS w/ FMRD, cleared under K931133.
#### Performance Standards:
No performance standards have been established for such devices under Sections 514 of the Federal Food, Drug, and Cosmetic Act. However, to the best of our knowledge, the CIV-ob Obstetrical Monitoring Software Application complies with the following voluntary standard:
IEC 60601-1-4 Computer Controlled Medical Devices i
#### Acceptance Criteria and Risk Analysis:
Acceptance criteria for compliance with the standards is detailed in CIVnet's IEC 60601-1-4 report and Risk Analysis.
The software risks addressed are communication, loss of power conditions, out of limit conditions, server communication, installation, memory capacity. These are checked as part of CIVnet's Software Test Procedure for validation of the software.
The hardware risks are those associated with the off-the-shelf devices and their possible failure.
The User Interface risks addressed are Patient Data Security and accuracy.
{2}------------------------------------------------
#### Device Description and Intended Use:
The CIVNET CIV-ob is a software application that is intended for use as a clinical data management system (also referred to as a clinical information system - CIS). The function of the system is the management of fetal and maternal vital heart rate and uterine vital signs clinical data automatically acquired from a bedside fetal monitor, for the purpose of providing, ready and organized access to patient and/or clinical data that would normally be provided on paper records and/or separate clinical systems/devices. The CIV-ob serves as an electronic medical record. The CIV-ob operates with off-the-shelf software and hardware. The device is intended for use in a hospital/clinical environment.
#### Substantial Equivalence:
The CIV-ob Obstetrical Monitoring Software Application is substantially equivalent to its predicate devices:
· GE Marquette Medical Quantitative Sentinel System, cleared under K993008, Dec 6, 1999.
- · ClinComp. Intl CIS w/ FMRD, cleared under K931133.
without raising new safety and/or effectiveness issues.
{3}------------------------------------------------
Food and Drug Administration 9200 Corporate Boulevard Rockville MD 20850
Mr. Rudi Lokits General Manager CIVNET Communication Ltd. Meshk 58, Ben Natan Moshav Hemed, 50295 ISRAEL
Re: K051175 Trade/Device Name: CIV-ob Monitoring Software Application Regulation Number: 21 CFR 884.2740 Regulation Name: Perinatal monitoring system and accessories Regulatory Class: II Product Code: HGM Dated: December 29, 2005 Received: January 4, 2006
Dear Mr. Lokits:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate 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) that do not require approval of a premarket approval application (PMA). 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 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act s requirements. including, but not limited to registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
FEB 1 7 2006
{4}------------------------------------------------
This letter will allow you to begin marketing your device as described in your Section 5 0(k) This letter will anow you to begin manxemig your antial equivalence of your device to a legally premarket notification. The FDA Inding of Sacsantial of Success of Survilles of Sermits your device to proceed to the market.
If you desire specific advice for your device on our labeling regulation (21 CFR Parl 801), please If you desire spective advice for your device on our labeling numbers, based on the regulation number at the top of this letter:
| 21 CFR 876.xxxx | (Gastroenterology/Renal/Urology) | 240-276-0115 |
|-----------------|----------------------------------|--------------|
| 21 CFR 884.xxxx | (Obstetrics/Gynecology) | 240-276-0115 |
| 21 CFR 892.xxxx | (Radiology) | 240-276-0120 |
| Other | | 240-276-0100 |
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Also, please note the regulation chance, "rinsonalisms of your responsibilities under the Act from the 807.97). You may obtain other general mornation your copyright its toll-free number (800) 638-2041 or (301) 443-6597 or at its Internet address http://www.fda.gov/cdrh/industry/support/index.html.
Sincerely yours,
Nancy C. Brigdon
Nancy C. Brogdon Director, Division of Reproductive, Abdominal, and Radiological Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
# INDICATIONS FOR USE
510(k) Number (if known):
K051175
Device Name:
CIV-ob Monitoring Software Application
Indications for Use:
The CIVNET CIV-ob software application is intended for automatic fetal monitor patient data management. The application does this by:
- a) Displaying on-line fetal heart rate and TOCO data received from the patient Displaying on mic recar near representation as it is displayed on the fetal monitor paper printout.
- b) Providing the means to control and display multiple beds simultaneously.
- c) Providing automatic Archiving of the data.
- c) Frovide the ability to interface with different fetal monitors operating with the same interface protocol.
- e) Easy interfacing with any IT patient record system for data acquisition, viewing and storage of electronic patient record.
- f) Provide visual notification of when acquired fetal monitor heart rate exceed I to ride visual nothlous for high and low fetal heart rate and poor signal quality.
- g) Providing the ability to record, with patient record, fluid input and output information that is defined by the user.
- h) Providing the ability to archive files to a secondary or tertiary storage medium (i.e. optical disk).
- Providing the ability to print (locally or remote) patient records. i)
- i) I roviding the ability to review fetal monitor data remotely over the TCP/IP
(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 Obstetrics and Gynecology Devices
510(k) Number
Prescription Use V (Per 21 CFR 801.109) OR
Over the Counter Use
(Per 21 CFR 801.109)
PREMARKET NOTIFICATION
David A. Hegy
ivicion Sion-Off Division of Reproductive, Abdominal, and Radiological Devices
510(k) Number
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.