K191401 · Nuvo- Group , Ltd. · LQK · Mar 27, 2020 · Obstetrics/Gynecology
Device Facts
Record ID
K191401
Device Name
PregSense
Applicant
Nuvo- Group , Ltd.
Product Code
LQK · Obstetrics/Gynecology
Decision Date
Mar 27, 2020
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 884.2730
Device Class
Class 2
Indications for Use
PregSense is a maternal-fetal monitor that non-invasively measures and displays fetal heart rate (FHR) and maternal heart rate (MHR). The PregSense acquires and displays the FHR and MHR tracings from abdominal surface electrodes that pick up the fetal heart biopotential and maternal heart biopotential signal, and from surface acoustic sensors that pick up the fetal PCG (fPCG; phonocardiogram) and the maternal PCG (mPCG; phonocardiogram) signals. PregSense is indicated for use by pregnant women who need documentation of fetal heart rate activity, and who are in their 32nd week of gestation (or later), with a singleton pregnancy. PregSense is intended to be used for a maximum of five minutes. The PregSense maternal-fetal monitor is intended for use in the antepartum period by healthcare professionals in health care facilities and by the patient in the patient's home, on the order of a physician. The PregSense is not intended for use in critical care situations or in laboring patients hospitalized for or suspected to have preterm labor. PregSense is not intended to be used for antepartum monitoring (e.g., non-stress testing).
Device Story
PregSense is a non-invasive maternal-fetal monitor. It uses a belt with embedded ECG-like biopotential sensors and acoustic sensors (phonocardiogram) worn on the maternal abdomen. The device captures fetal and maternal heart rate signals. Data is processed at a cloud-server level, where inputs are merged and transmitted to the PregSense ME app (patient) and PregSense MD app (physician). Monitoring is limited to five-minute sessions initiated by a healthcare provider. The physician reviews the tracings remotely to document fetal heart rate activity. The device is intended for use in healthcare facilities or at home by prescription. It provides clinicians with objective heart rate data to support antepartum monitoring, potentially improving access to fetal heart rate documentation.
Clinical Evidence
Clinical evidence included a feasibility study (n=76) and a pivotal study (n=149). The pivotal study compared PregSense to standard-of-care CTG monitoring in healthcare settings. Bland-Altman analysis for 30-minute sessions showed 97.08% of FHR differences within [-8.84, 8.24] bpm and 95.31% of MHR differences within [-5.30, 5.86] bpm. A sub-analysis of 5-minute data showed narrower limits of agreement (95% CI lower bound -7.47 bpm, upper bound 8.16 bpm) with 96.64% of differences within limits. Usability testing confirmed lay users can successfully operate the device.
Technological Characteristics
System includes a belt with ECG-like biopotential sensors and acoustic sensors. Connectivity via Bluetooth to mobile apps and cloud-based processing. Software versions: PregSense ME (0.40.1.3669), PregSense MD (0.2), WSH firmware (0.123), Server (0.1.90). Biocompatibility per ISO 10993-1; electrical safety per IEC 60601-1 and IEC 60601-1-2. Data processing occurs at the cloud level.
Indications for Use
Indicated for pregnant women ≥32 weeks gestation with singleton pregnancy needing fetal heart rate documentation. Not for critical care, laboring patients, suspected preterm labor, or non-stress testing.
Regulatory Classification
Identification
A home uterine activity monitor (HUAM) is an electronic system for at home antepartum measurement of uterine contractions. The HUAM system comprises a tocotransducer and an at-home recorder. This device is intended for use in women with a previous preterm delivery to aid in the detection of preterm labor.
Special Controls
*Classification.* Class II (special controls); guidance document (Class II Special Controls Guidance for Home Uterine Activity Monitors).
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logos of the Department of Health & Human Services and the Food and Drug Administration (FDA). The Department of Health & Human Services logo is on the left, and the FDA logo is on the right. The FDA logo is a blue square with the letters "FDA" in white, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue.
March 27, 2020
Nuvo-Group Ltd. % Janice Hogan Partner Hogan Lovells US LLP 1735 Market St., 23rd F1. Philadelphia, PA 19103
Re: K191401
Trade/Device Name: PregSense™ Regulation Number: 21 CFR 884.2730 Regulation Name: Home Uterine Activity Monitor Regulatory Class: II Product Code: LOK Dated: March 23, 2020 Received: March 23, 2020
Dear Janice Hogan:
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. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. 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. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to 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
{1}------------------------------------------------
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); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
for Monica D. Garcia, Ph.D. Acting Assistant Director DHT3B: Division of Reproductive. Gynecology and Urology Devices OHT3: Office of GastroRenal, ObGyn, General Hospital and Urology Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K191401
Device Name PregSense™
#### Indications for Use (Describe)
PregSense is a maternal-fetal monitor that non-invasively measures and displays fetal heart rate (FHR) and maternal heart rate (MHR). The PregSense acquires and displays the FHR and MHR tracings from abdominal surface electrodes that pick up the fetal heart biopotential and maternal heart biopotential signal, and from surface acoustic sensors that pick up the fetal PCG (fPCG; phonocardiogram) and the maternal PCG (mPCG; phonocardiogram) signals.
PregSense is indicated for use by pregnant women who need documentation of fetal heart rate activity, and who are in their 32nd week of gestation (or later), with a singleton pregnancy. PregSense is intended to be used for a maximum of five minutes.
The PregSense maternal-fetal monitor is intended for use in the antepartum period by healthcare professionals in health care facilities and by the patient in the patient's home, on the order of a physician.
The PregSense is not intended for use in critical care situations or in laboring patients hospitalized for or suspected to have preterm labor.
PregSense is not intended to be used for antepartum monitoring (e.g., non-stress testing).
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| <span> <span style="font-size:16px"> <span style="font-family:Arial, sans-serif"> <span style="color:#000000"> <span style="font-weight:normal"> <span style="font-style:normal"> <span style="text-decoration:none"> <span> </span> </span> </span> </span> </span> </span> </span> </span> Prescription Use (Part 21 CFR 801 Subpart D) | <span> <span style="font-size:16px"> <span style="font-family:Arial, sans-serif"> <span style="color:#000000"> <span style="font-weight:normal"> <span style="font-style:normal"> <span style="text-decoration:none"> <span> </span> </span> </span> </span> </span> </span> </span> </span> Over-The-Counter Use (21 CFR 801 Subpart C) |
## CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
#### 510(k) SUMMARY
#### K191401 - PregSense™
#### Submitter
Nuvo-Group Ltd. Yigal Alon 94 St., Alon Tower 1 Tel Aviv, Israel 6789155 Phone: +972-54 234 7770 Contact Person: Adar Shani
Date Prepared: March 26, 2020
Name of Device: PregSense™ Common or Usual Name: Home Uterine Activity Monitor Regulation Number: 21 CFR 884.2730 Regulation Name: Home Uterine Activity Monitor Product Code: LQK Product Code Name: Home Uterine Activity Monitor Regulatory Class: II
Predicate Device: Sense4Baby System Model B+ (K143114). The predicate device has been subject to a design-related recall (belt clip defects).
### Device Description
PregSense™ is a non-invasive medical device that acquires and displays vital signs of the pregnant woman and of her fetus. It measures and processes signals picked up on the abdominal surface using sensors, electronic circuitry and processing software. Two types of sensors pick up the signals: electrocardiogram (ECG)-like sensors that capture bio-potential signals, and acoustic sensors. The biopotential (ECG-like) sensors capture fECG (heartrate of the fetus) and mECG signals (heartrate of the pregnant woman). The acoustic sensors measure the sounds from the pregnant woman's abdomen, (PCG -phonocardiogram and fPCG -fetal PCG). Monitoring of the fetal and maternal heart rate using PregSense is limited to a five-minute session.
PregSense™ is an integrated platform that uses a signal acquisition tool to provide input to two separate software applications, one for the patient (PregSense™ ME) and one for the physician (PregSense™ MD). The sensors are incorporated in a belt (PregSense™ Belt) that is worn on the abdomen of the pregnant woman, where it acquires both biopotential and acoustic signals are processed at the cloud-server level where the inputs from the sensors are processed, merged and downloaded to the mobile devices of the pregnant woman and her health care provider. The PregSense™ ME application (for the patient) allows the pregnant woman to view the average maternal and fetal heart rate after a
{4}------------------------------------------------
five minute session has been completed and PregSense™-MD application (for the health care provider) allows the health care provider to view the complete fetal and maternal heart rate data from the five minute session online and remotely via the internet. A monitoring session can only be initiated by a health care provider.
## Indications for Use
PregSense is a maternal-fetal monitor that non-invasively measures and displays fetal heart rate (FHR) and maternal heart rate (MHR). The PregSense acquires and displays the FHR and MHR tracings from abdominal surface electrodes that pick up the fetal heart biopotential and maternal heart biopotential signal, and from surface acoustic sensors that pick up the fetal PCG (fPCG; phonocardiogram) and the maternal PCG (mPCG; phonocardiogram) signals.
PregSense is indicated for use by pregnant women who need documentation of fetal heart rate activity, and who are in their 32nd week of gestation (or later), with a singleton pregnancy. PregSense is intended to be used for a maximum of five minutes.
The PregSense maternal-fetal monitor is intended for use in the antepartum period by healthcare professionals in health care facilities and by the patient's home, on the order of a physician.
The PregSense is not intended for use in critical care situations or in laboring patients hospitalized for or suspected to have preterm labor.
PregSense is not intended to be used for antepartum monitoring (e.g., non-stress testing).
## Substantial Equivalence Comparison
A table comparing the intended use and technological characteristics of the subject and predicate devices is provided below.
| | Subject Device: | Predicate Device: |
|-----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Nuvo's PregSense System | Sense4Baby System Model B+ |
| 510(k) Number | K191401 | K143114 |
| Product Code | LQK | LQK, MOH, HGM |
| Classification | 21 CFR 884.2730 | 21 CFR 884.2730 |
| Device Type | Maternal-fetal monitor | Maternal-fetal monitor |
| Intended Use/<br>Indications for<br>Use | PregSense is a maternal-fetal monitor<br>that non-invasively measures and<br>displays fetal heart rate (FHR) and<br>maternal heart rate (MHR). The<br>PregSense acquires and displays the<br>FHR and MHR tracings from abdominal<br>surface electrodes that pick up the | The Sense4Baby System Model B+ is<br>indicated for conventional antepartum<br>fetal monitoring applications in<br>pregnancies greater than or equal to<br>24 weeks gestation. It may be used for<br>antenatal monitoring (e.g., non-stress<br>testing and/or uterine activity |
| | Subject Device: | Predicate Device: |
| | Nuvo's PregSense System | Sense4Baby System Model B+ |
| | fetal heart biopotential and maternal heart biopotential signal, and from surface acoustic sensors that pick up the fetal PCG (fPCG; phonocardiogram) and the maternal PCG (mPCG; phonocardiogram) signals.<br>PregSense is indicated for use by pregnant women who need documentation of fetal heart rate activity, and who are in their 32nd week of gestation (or later), with a singleton pregnancy. PregSense is intended to be used for a maximum of five minutes.<br>The PregSense maternal-fetal monitor is intended for use in the antepartum period by healthcare professionals in health care facilities and by the patient in the patient's home, on the order of a physician.<br>The PregSense is not intended for use in critical care situations or in laboring patients or those patients hospitalized for or suspected to have preterm labor.<br>PregSense is not intended to be used for antepartum monitoring (e.g., non-stress testing). | monitoring) in a health care setting or home.<br>It is to be used by health care professionals and patients on the order of a physician.<br>Before the Sense4Baby System Model B+ is prescribed for home use, the user (patient) must be instructed/trained in proper use of the equipment.<br>Home uterine activity monitoring has not been shown to prevent the onset of preterm labor nor will it prevent the occurrence of preterm birth. |
| Prescription<br>Use | Medical personnel or patients on order of physician | Medical personnel or patients on order of physician |
| Intended<br>Environments | Health care setting or home | Health care setting or home |
| Target<br>Population | Women who are ≥32 gestational weeks with singleton pregnancy | Women who are ≥24 weeks gestation |
| Patient<br>Interface | Maternal abdomen connected to surface ECG-like bio-potential sensors | Maternal abdomen connected to sensor with Piezo-electric crystals |
| | Subject Device: | Predicate Device: |
| | Nuvo's PregSense System | Sense4Baby System Model B+ |
| | and acoustic sensors | |
| Data Collected<br>from Sensor<br>Array | Fetal heart rate,<br>Maternal heart rate | Fetal heart rate,<br>Maternal heart rate,<br>Uterine activity |
| Technology<br>Employed | Transabdominal electrocardiography<br>signals and acoustic signals | Pulsed Doppler Ultrasound |
| Monitoring<br>Session | 5 minutes | 30 minutes |
| Information<br>Displayed On | Cloud or mobile based software<br>applications | Web based portal |
### Comparison Chart
{5}------------------------------------------------
{6}------------------------------------------------
The subject and the predicate device have different indications for use statements, but have the same intended use – for antenatal monitoring in a health care setting or home environment by the patient by prescription only.
The subject device is to be utilized in women who are greater than 32 weeks of gestation, whereas the predicate device can be used in subjects who are greater the 24 weeks of gestation. Both the subject and predicate device are intended to be used for conventional antepartum monitoring by both the physician and the patient. The predicate device is indicated for use for both fetal/maternal heart rate monitoring and uterine activity monitoring, whereas the subject device is indicated for fetal/maternal heart rate monitoring only. However, as both the subject and predicate device are intended to be used for fetal/maternal heart rate monitoring, the lack of uterine activity monitoring does not raise different questions of safety and effectiveness as it pertains to the function of the device. In addition, the subject device is intended to be used for a maximum of five minutes, rather than 30 minutes as indicated for the predicate device. This is not a new intended use, as both the subject and predicate device are used to document fetal and maternal heart rate activity.
The subject and predicate devices have different technological characteristics. The FHR/MHR technology (i.e., ECG vs pulsed doppler ultrasound) of the subject and predicate device are different, as are the related hardware components associated with these different technologies. In addition, the subject device does not contain uterine activity monitoring technology. Finally, the method of data display between the subject and predicate device is different, with the subject device using a cloud-based service and software apps and the predicate device using a web based portal. However, different types of safety and effectiveness questions are not raised by these differences in technological characteristics.
{7}------------------------------------------------
## Non-Clinical Performance Data
The following non-clinical performance testing was provided to support the performance of PregSense™:
- . Electronical testing
- electromagnetic testing (IEC 60601-1-2), O
- electrical safety testing (IEC 60601-1), O
- O battery safety
- external defibrillation safety testing, O
- o testing of the electrical interface and electronic parts,
- O Bluetooth functionality,
- O over-temperature protection, safety tests, and relevant use cases;
- Functionality testing to evaluate the durability and functionality of the various parts of the device, including hardware and accessories
- O PCB testing
- Belt electronic testing O
- Short circuit protection testing O
- Mechanical functionality O
- O Cable and rubber webbing testing
- Velcro degradation o
- ECG acquisition/processing/detection/classification per 60601-2-27 and 606001-2-47 O
- Software verification and validation testing for the PregSense ME App, Software version: 0.40.1.3669; PregSense MD App, Software version: 0.2 (117); PregSense WSH firmware version: 0.123; and the PregSense Server, Software version 0.1.90 per the recommendations of the 2005 guidance document Guidance for the Content of Premarket Submission for Software Contained in Medical Devices
- . Cleaning and disinfection information per the recommendations of the 2015 guidance document Reprocessing Medical Devices in Health Care Settings: Validation Methods and Labeling
- . Biocompatibility testing per the recommendations of the 2016 guidance document Use of International Standard ISO 10993-1, "Biological evaluation of medical devices - Part 1: Evaluation and testing within a risk management process" as follows:
- Cytotoxicity ISO 10993-5:2009/®2014 O
- O Sensitization - ISO 10993-10:2010
- Irritation ISO 10993-10:2010 o
- Human Factors testing per the recommendations of the 2016 guidance document Applying Human factors and Usability Engineering to Medical devices
## Clinical Performance Data
Two clinical studies were performed using the belt with embedded sensors and associated software for analysis: a feasibility study and a pivotal study. The feasibility study was conducted to assess the feasibility and safety of PregSense™ system. The pivotal trial was conducted in order to demonstrate
{8}------------------------------------------------
that the PregSense™ performs appropriately for its intended use. The feasibility and pivotal trials were conducted using the device in thirty-minute sessions. However, the data used to support the safety and effectiveness of the subject device was limited to five minutes.
During the feasibility study, a total of 76 subjects participated for which a total of 510 recording sessions were executed. Female subjects aged ≥ 18 years with a singleton pregnancy between 20-40 weeks of gestation and who were capable of signing informed consent were included in the study. No adverse events, procedure-related or device-related, were reported during the study. The results of the feasibility study showed that the overall detection percentage was > 70% for the overall population and 90% (±11.3) for those at least 32 weeks of gestation. Therefore, the pivotal study was performed in women at 32 weeks or more.
A pivotal clinical study in four healthcare settings (two in the United States and two outside the United States) to permit comparison to a "standard of care" monitoring device (CTG) was performed in 149 subjects. Because this type of "standard of care" monitoring could not be performed in a home environment, use in a healthcare setting was required. To ensure the device will perform appropriately when the belt is worn by the patient at home, a usability study was performed with lay users. Using Bland-Altman Limits of Agreement, the pivotal clinical testing for the complete 30-minute session demonstrated that for FHR, 97.08% of all differences lie between the 95% agreement limits of [-8.84, 8.24] bpm in the 149 subjects with no adverse events reported. In addition, the pivotal clinical testing demonstrated that for MHR, 95.31% (48241/50616) of all differences lie between the 95% agreement limits of [-5.30, 5.86] bpm.
As the duration of data collection of the PregSense system is limited to 5 minutes, an additional analysis of the limits of agreement using only 5 minutes of outputted data post-calibration showed narrower limits of agreement than originally reported using the entire 30-minute data collection: the lower limit of the 95% confidence interval of the lower agreement bound is -7.47 bpm and the upper limit is 8.16 bpm. Furthermore, 96.64% of the differences fall between the limits of agreement.
Together, the completed clinical and usability testing demonstrate that the device accuracy is acceptable and that lay users can use the device successfully.
## Conclusions
The results of the performance testing described above demonstrate that the PregSense device is as safe and effective as the predicate device and supports a determination of substantial equivalence.
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.