Athena GTX Device Management Suite (ADMS) Software
Applicant
Athena Gtx
Product Code
MSX · Cardiovascular
Decision Date
Mar 14, 2018
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device, Pediatric
Indications for Use
The intended use of the ADMS software application is to: Receive, aggregate, process, distribute and display physiologic waves, parameters, alarms and events at locations other than at the patient, for multiple patients. Display visual alarm conditions as generated by a connected monitor. Display of patient information can be real-time or historical record review. Provide review and trend application data, designed to the screening of patient condition. All information or visual indications provided are intended to support the judgement of a medical professional and are not intended to be the sole source of information for decision making. Provide connection to other systems not associated with active patient monitoring, such as information systems. The software performs the action to transfer, store, convert from one format to another according to preset specifications, or to display medical device data. ADMS is intended for use in professional healthcare facilities, emergency medical applications, during transport, and other healthcare environments by trained healthcare professionals. ADMS Software is not intended for home use. Indicated for use for specific patient populations (adult, pediatric, infant/neonate) depends on the indicated labeling of medical device(s) connected to ADMS providing the data.
Device Story
ADMS is a software-only device managing physiologic data from compatible monitors. It receives, aggregates, processes, distributes, and displays real-time or historical waveforms, parameters, and visual alarms for up to 20 patients simultaneously. Input data arrives via Wi-Fi (802.11) from Athena devices. The software runs on off-the-shelf Android, iOS, and Windows platforms. It supports bi-directional communication, allowing clinicians to adjust monitor configurations, alarm limits, and control specific monitor functions (e.g., start/stop blood pressure, find command). ADMS interfaces with EMRs via HL7. Used by trained healthcare professionals in hospitals, transport, and emergency settings, the system provides visual-only alarms to support clinical judgment. It does not perform independent diagnostic analysis or generate its own alarm conditions; it merely relays data and visual alerts from connected monitors. Benefits include centralized patient monitoring, remote data access, and historical trend review to assist in patient condition screening.
Clinical Evidence
No clinical study data. Bench testing only. Software verification and validation testing conducted per FDA guidance for moderate level of concern software.
Technological Characteristics
Software-only device; no patient-contact materials. Operates on off-the-shelf Windows, iOS, and Android platforms. Connectivity via Wi-Fi (802.11b/g/n), USB, LAN, and cellular. Supports bi-directional communication with connected monitors. Data stored in encrypted proprietary binary files. Interoperability via HL7 for EMR integration.
Indications for Use
Indicated for use in professional healthcare facilities, emergency medical applications, transport, and other healthcare environments by trained healthcare professionals to monitor adult, pediatric, and infant/neonate patients, contingent upon the labeling of the connected medical device.
Regulatory Classification
Identification
A cardiac monitor (including cardiotachometer and rate alarm) is a device used to measure the heart rate from an analog signal produced by an electrocardiograph, vectorcardiograph, or blood pressure monitor. This device may sound an alarm when the heart rate falls outside preset upper and lower limits.
Predicate Devices
M3290B Patient Information Center iX (PIC iX) (K163584)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health and Human Services logo on the left and the FDA logo 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 14, 2018
Athena GTX Sean Mahoney V.P. Regulatory Affairs 5900 NW 86th Street. Suite 300 Johnston, Iowa 50131
Re: K173203
Trade/Device Name: Athena GTX Device Management Suite (ADMS) Regulation Number: 21 CFR 870.2300 Regulation Name: Cardiac Monitor (Including Cardiotachometer And Rate Alarm) Regulatory Class: Class II Product Code: MSX, DRG, MHX, MWI, DSI, DXN, DQA, MLD Dated: November 3, 2017 Received: November 6, 2017
Dear Sean Mahoney:
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. 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 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); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
{1}------------------------------------------------
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 http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
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/DeviceRegulationandGuidance/) and CDRH Learn (http://www.fda.gov/Training/CDRHLearn). 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 (http://www.fda.gov/DICE) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
M.A. Hillemann
for Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
#### DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration
# Indications for Use
Form Approved: OMB No. 0910-0120 Expiration Date: 06/30/2020 See PRA Statement below
510(k) Number (if known)
#### K173203
Device Name
Athena GTX Device Management Suite (ADMS)
#### Indications for Use (Describe)
The intended use of the ADMS software application is to:
Receive, aggregate, process, distribute and display physiologic waves, parameters, alarms and events at locations other than at the patient, for multiple patients.
Display visual alarm conditions as generated by a connected monitor.
Display of patient information can be real-time or historical record review.
Provide review and trend application data, designed to the screening of patient condition. All information or visual indications provided are intended to support the judgement of a medical professional and are not intended to be the sole source of information for decision making.
Provide connection to other systems not associated with active patient monitoring, such as information systems. The software performs the action to transfer, store, convert from one format to another according to preset specifications, or to display medical device data.
ADMS is intended for use in professional healthcare facilities, emergency medical applications, during transport, and other healthcare environments by trained healthcare professionals. ADMS Software is not intended for home use.
Indicated for use for specific patient populations (adult, pediatric, infant/neonate) depends on the indicated labeling of medical device(s) connected to ADMS providing the data.
| Type of Use (Select one or both, as applicable) | |
|----------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
| <div> <span> Prescription Use (Part 21 CFR 801 Subpart D) </span> </div> | <div> <span> Over-The-Counter Use (21 CFR 801 Subpart C) </span> </div> |
#### 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}------------------------------------------------
#### K173203
# Exhibit H - Section 5 - 510(k) Summary of Safety and Effectiveness
# 510(k) Summary of Safety and Effectiveness
I. SUBMITTER 807.92(a)(1)]:
Athena GTX 5900 NW 86th Street, Suite 300 Johnston, lowa 50131
Phone: 515.288.3360 Fax: 515.288.3394
Company Contact: Sean Mahoney (VP of Regulatory Affairs) 515.288.3360 x103 smahoney@athenagtx.com
Date Prepared: January 12, 2018
II. DEVICE [807.92(a)(2)]:
Trade Name: Athena GTX Device Management Suite (ADMS) Common Name: Physiological Monitors Network and Communication System Classification Name: Cardiac monitor (incl. cardio tachometer and rate alarm) (21 CFR 870.2300) Radiofrequency physiological signal transmitter and receiver (21 CFR 870.2910)
Device Class: Class II Product Code: MSX. DRG Other Product Codes: MHX, MWI, DSI, DXN, DQA, MLD Basis for Submission: New Device
### III. PREDICATE DEVICE [807.92(a)(3)]:
Legally Marketed (Primary Predicate) Device: M3290B Patient Information Center iX (PIC iX) (K163584) (Second Predicate) Device: WVSM Management Suite (K130957)
#### IV. DEVICE DESCRIPTION [807.92(a)(4)]:
#### Device Identification
The Athena GTX Device Management Suite (ADMS) is a software only device that manages patient data from compatible monitoring devices.
#### Device Characteristics
The Athena GTX Device Management Suite (ADMS) receives, distributes and displays physiologic waves, parameters and visual alarms at locations other than at the patient, for multiple patients. Data is generate by compatible connected devices and can be real-time or historical review.
#### Environment of Use
ADMS is intended for use by trained healthcare providers in hospitals, healthcare facilities, emergency medical applications, during transport, and other healthcare environments.
> H - 1 Page 1 of 6
{4}------------------------------------------------
#### K173203
# Exhibit H - Section 5 - 510(k) Summary of Safety and Effectiveness
# Principle of Operation
The Athena GTX Device Management Suite provides a method of controlling ADMS compatible devices and viewing the device's data on Android devices (smartphones and tablets), iOS devices (smartphones and tablets) and on PCs running Windows OS.
The ADMS software receives data using Wi-Fi (802.11) from any Athena device within range. Whenever a device comes within range of ADMS, it will start receiving data from the device automatically. Commands to devices is transmitted via Wi-Fi (802.11) to the device. Each platform running ADMS can support viewing up to twenty (20) devices at one time.
#### Materials
The Athena GTX Device Management Suite (ADMS) consists of software only applications that do not come into physical contact with patients.
#### Key Performance Specification
Key performance specifications are listed in the table in section VI below.
### V. INDICATIONS FOR USE [807.92(a)(5)]:
The intended use of the ADMS software application is to:
Receive, aggregate, process, distribute and display physiologic waves, parameters, alarms and events at locations other than at the patient, for multiple patients.
Display visual alarm conditions as generated by a connected monitor.
Display of patient information can be real-time or historical record review.
Provide review and trend application data, designed to the screening of patient condition. All information or visual indications provided are intended to support the judgement of a medical professional and are not intended to be the sole source of information for decision making.
Provide connection to other systems not associated with active patient monitoring, such as information systems. The software performs the action to transfer, store, convert from one format to another according to preset specifications, or to display medical device data.
ADMS is intended for use in professional healthcare facilities, emergency medical applications, during transport, and other healthcare environments by trained healthcare professionals. ADMS Software is not intended for home use.
Indicated for use for specific patient populations (adult, pediatric, infant/neonate) depends on the indicated labeling of medical device(s) connected to ADMS providing the data.
{5}------------------------------------------------
# Exhibit H - Section 5 - 510(k) Summary of Safety and Effectiveness
# VI. COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH THE PREDICATE DEVICE
The new device (ADMS), the primary predicate and second predicate devices have similar technological characteristics: Software running on off-the-self personal computer and/or mobile platforms that establish a wired or wireless network with connected medical monitors. The second predicate more clearly demonstrates the specific use of a Bi-Directional communication technological characteristic (including adjusting monitor configuration, alarm limits, start/stop taking a blood pressure and initiating a "find" command) between the Software device and the connected medical monitor(s).
Summary points from the specification comparison show that the ADMS and the predicates:
- Use off the shelf operating systems. ●
- Use both wired and wireless network connections. .
- . Use off the shelf computers and handheld hardware.
- Provide the same function - central station and remote system patient monitoring.
- . Include use in fixed professional healthcare facilities as well as in the field, mobile applications and patient transport locations.
- Provide for real-time/active patient monitoring as well as historical patient record review.
- . Include bi-directional communication and control of some monitor functions and configuration settings.
- . Provide minimum requirements for hardware and operating system compatibility are specified by the manufacturer - typically in the Instructions for Use (IFU).
- . List system compatible monitors tvpically in the device labeling or in the 510(k) summary.
- Are able to receive, transmit, store, print and display patient information including: waveforms, numerical values, show trends and alarms.
- . Are able to interface to Electronic Medical Records data bases via the HL7 protocol.
- . Are touch screen compatible.
- ADMS and the secondary predicate have only visual alarms.
The following differences between the predicates and the ADMS software are as follows:
- . The primary predicate includes additional ECG waveform analysis and/or display capabilities that are not included in the ADMS.
- . The primary predicate has the ability to determine alarm conditions and generate alarm signals for Philips approved medical devices that send physiological data and do not have the ability to determine the alarm condition. This capability is not included in ADMS.
- . The primary predicate has both audio and visual alarms. ADMS has only visual alarms. The Secondary predicate has only visual alarms and is the same as ADMS.
- . The second predicate does not readily interface with EMRs and does not have an HL7 interface.
- The second predicate does not include Protected Health Information (PHI) data. PHI is . included and encrypted in ADMS.
{6}------------------------------------------------
# Exhibit H – Section 5 – 510(k) Summary of Safety and Effectiveness
These differences do not raise different questions of safety and effectiveness because they are additional features that are not part of the ADMS functionality or have been included in ADMS for HIPPA and security purposes.
The following is provided as a summary of how the technological characteristics of the device compare to the predicate devices:
| Product<br>Element | ADMS<br>(New Device) | PIC iX<br>(Primary Predicate) | WVSM Management<br>Suite<br>(Second Predicate) | Comments |
|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|------------------------------------------------------|
| Manufacturer | Athena GTX | Philips Medical Systems. | Athena GTX | - - - |
| 510(k)<br>Number | Pending - new device | K163584 | K130957 | - - - |
| Rx Only | Yes | Yes | Yes | Same |
| Physiological<br>Parameters | Indicated by labeling of<br>the Connected Medical<br>Device | Indicated by labeling of<br>the Connected Medical<br>Device | Indicated by WVSM<br>labeling | Same |
| Patient<br>Population | Indicated by labeling of<br>the Connected Medical<br>Device | Indicated by labeling of<br>the Connected Medical<br>Device | Indicated by WVSM<br>labeling | Same |
| User<br>Population | Trained healthcare<br>providers | Trained healthcare<br>professionals | Trained healthcare<br>providers | Same |
| Operating<br>Systems | Windows 7, 8,10<br>iOS<br>Android | Windows 10<br>Windows Server 2012 R2 | Window XP<br>iOS | Similar<br>(device<br>platform<br>dependent) |
| Network/<br>Connectivity<br>Capabilities | Wired (USB, LAN)<br>WiFi (802.11b/g/n)<br>Cell Network | Wired (LAN)<br>WiFi (802.11) | WiFi (802.11b/g) | Same |
| Location | Fixed and Field Mobile | Fixed Professional<br>healthcare facilities | Fixed and Field Mobile | Same |
| Real-time<br>data | Yes | Yes | Yes | Same |
| Historical/<br>saved record<br>review | Yes | Yes | No | Same except<br>for WVSM<br>Suite |
| Product<br>Element | ADMS<br>(New Device) | PIC iX<br>(Primary Predicate) | WVSM Management<br>Suite<br>(Second Predicate) | Comments |
| Bi-directional<br>Communicati<br>on with<br>connected<br>monitors | Yes (Configuration,<br>Alarm limits, Start/Stop<br>BP, Find) | Yes (Configuration,<br>Alarm limits, Start/Stop<br>BP, Find) | Yes (Configuration,<br>Alarm limits, Start/Stop<br>BP, Find) | Same |
| Display | Platform dependent.<br>Minimum requirements<br>specified in the IFU | Minimum requirements<br>specified in the IFU | Platform dependent.<br>Minimum requirements<br>specified in the IFU | Same defined<br>by minimum<br>requirement |
| Touch Screen<br>Compatible | Yes | Yes | Yes | Same |
| Host<br>Platforms<br>Supported | Off-the-shelf Windows<br>PCs, servers and<br>iOS/Android mobile<br>devices. Hardware<br>Requirements Specified<br>in IFU | Off-the-shelf Windows<br>PCs and servers.<br>Hardware Requirements<br>Specified in IFU | Off-the-shelf Windows<br>PCs and iOS Mobile<br>devices. Hardware<br>Requirements Specified<br>in IFU | Same defined<br>by minimum<br>requirement |
| Patient<br>Monitors<br>Supported | Up to 20 devices | Up to 4 devices per<br>patient. Up to 32<br>Patient Sectors | Up to 20 devices | Same or a<br>subset |
| Compatible<br>Devices/<br>Monitors | WVSM (K130957)<br>WiCap (K160582)<br>WiTemp (Not a medical<br>device) | Philips approved<br>medical devices.<br>Examples Include:<br>Bedside: IntelliVue MX<br>and MP Series<br>Portable: IntelliVue X2<br>Mobile: IntelliVue MX40 | WVSM (K130957) | Same<br>System<br>Compatible/<br>Approved<br>Devices |
| Types of Data<br>Transmitted,<br>Stored and<br>Displayed | Waveforms, numerical<br>values, trends, Alarms | Waveforms, numerical<br>values, trends, ECG<br>waveform analysis &<br>arrhythmia detection,<br>Alarms | Waveforms, numerical<br>values, trends, Alarms | Same or<br>Subset |
| Alarms | Visual | Audio and Visual | Visual | Same or<br>Subset |
| Remote<br>Network<br>Access/<br>Interface | Yes | Yes (via Web and iPad<br>Accessory) | No | Same for<br>PIC iX |
| Product<br>Element | ADMS<br>(New Device) | PIC iX<br>(Primary Predicate) | WVSM Management<br>Suite<br>(Second Predicate) | Comments |
| Print<br>Capability | Yes | Yes | Yes | Same |
| Data Storage | PHI Saved in an<br>encrypted file, data in a<br>proprietary binary file<br>structure | Not Stated. On a Server | Proprietary binary file<br>structure | Same or<br>Equivalent |
| Interface to<br>EMR | Yes (HL7) | Yes (HL7) | No | Same except<br>for WVSM<br>Suite |
H - 4
{7}------------------------------------------------
# Exhibit H – Section 5 – 510(k) Summary of Safety and Effectiveness
{8}------------------------------------------------
# Exhibit H - Section 5 - 510(k) Summary of Safety and Effectiveness
# VII. PERFORMANCE DATA [807.92(b)(1)]:
# Biocompatibility
ADMS is a software only device, does not come in contact with the patient and was not tested for biocompatibility.
# Industry Standards for Safety, EMC and Essential Performance
Athena GTX Device Management Suite (ADMS) software is a software only device and therefore all testing was completed under software verification and validation. This submission does not rely on FDA recognized performance standards or device-specific guidance for design or testing.
# Software Verification and Validation Testing
Software verification and validation testing were conducted and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices." The software for this device was considered as a "moderate" level of concern.
# Animal Study Data
None.
Clinical Study Data [807.92(b)(2)]: None.
#### VIII. CONCLUSION [807.92(b)(3)]:
The results for all safety, compliance, and non-clinical performance testing demonstrates that Athena GTX Device Management Suite (ADMS) software has the same performance characteristics and is substantially equivalent to the above listed predicate devices.
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.