MONITORING STATION, CONNEX(R) CENTRAL STATION (CS)
K132807 · Welch Allyn, Inc. · MWI · Jan 31, 2014 · Cardiovascular
Device Facts
Record ID
K132807
Device Name
MONITORING STATION, CONNEX(R) CENTRAL STATION (CS)
Applicant
Welch Allyn, Inc.
Product Code
MWI · Cardiovascular
Decision Date
Jan 31, 2014
Decision
SESE
Submission Type
Special
Regulation
21 CFR 870.2300
Device Class
Class 2
Attributes
Software as a Medical Device, Pediatric
Indications for Use
The Connex Central Station (CS) is intended to be used by clinicians for the central monitoring of neonatal, pediatric, and adult patients in health care facilities. In addition to the central monitoring of patient data and alarms, the Connex software can include optional modules to provide extended recording of patient data, including full disclosure.
Device Story
Connex Central Station is a Windows-based software platform for remote, centralized monitoring of multiple patients. It receives vital signs and alarm data from continuous patient monitors and episodic spot-check devices via hospital network (Ethernet/wireless/USB). The system displays real-time patient data, manages audio alarms, and provides historical data review (flow sheets, graphical/continuous trends, full disclosure). It supports up to 48 patients per workstation and can interface with 3rd-party notification systems, ADT/EMR systems, and repeater displays. Clinicians use the station to oversee patient status, adjust alarm limits (excluding Early Sense settings), and pause alarms. The device benefits patients by enabling centralized, continuous oversight of vital signs and alarm conditions, facilitating timely clinical intervention.
Clinical Evidence
No clinical studies were utilized. Safety and effectiveness were established through bench testing, including verification of alarm gateway performance, data integration, and usability validation with trained end-users.
Technological Characteristics
Windows-based software running on PC hardware. Interfaces via Ethernet/USB/wireless. Supports WACP protocol. Compliant with IEC 60601-1, 60601-1-4, 60601-1-8, 60601-2-49, EN/IEC 62304, and ISO 14971. Features include SQL Server database, 24" LCD display, and integration with Early Sense modules.
Indications for Use
Indicated for central monitoring of neonatal, pediatric, and adult patients in healthcare facilities. No contraindications.
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.
Connex Vital Signs Monitor (CVSM) 6000 Series (K132808)
Submission Summary (Full Text)
{0}------------------------------------------------
K132807
ן
JAN 3 1 2014
#### 510(k) Summary [As described in 21 CFR 807.92]
| Submitted by: | Welch Allyn Inc. 4341 State Street Road Skaneateles Falls, NY 13153-0220 |
|---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact Person: | Kevin Crossen Director, Regulatory Affairs Phone: (315) 685-2609 Fax: (315) 685-2532 E-mail: kevin.crossen@welchallyn.com |
| Date Prepared: | September 06, 2013 |
| Trade Names: | 901066 Monitoring Station Connex® Central Station |
| Common Name: | Central Station |
| Classification Name: | Monitor, Physiological, Patient (Without Arrhythmia Detection or Alarms) |
| Classification Reference: | Class II, 21 CFR 870.2300, Cardiac monitor (including cardiotachnometer and rate alarm) Product Code: MWI |
| Predicate Device: | Connex Workstation Welch Allyn, Inc. 510(k) Number: K120343 Class II, 21 CFR 870.2300, Cardiac monitor (including cardiotachnometer and rate alarm) Product Code: MWI |
#### Description of the Device:
Connex Central Station, also known as Monitoring Station, is a Windows-based product that provides clinicians with a means to remotely monitor the health of several patients simultaneously. The Monitoring Station receives patient vital signs and alarm data from patient monitors and spot check devices over a network, then displays the data and sounds audio alarms in a centralized location.
Specific patient populations are determined by the requirements of the devices gathering the patient data.
{1}------------------------------------------------
In the Monitoring Station, there are two possible sources of patient data, namely:
- a. Continuous monitoring devices that are attached to the patient, or
- b. Episodic measurements taken from devices that may or may not be constantly connected to the patient.
Devices providing the patient data may transfer the data electronically to the hospital network for communication with the Monitoring Station via methods such as USB, wired Ethernet, or wireless communications. The Monitoring Station is wired to the network via Ethernet.
The Monitoring Station can be deployed as either a standalone central station or as a server-based deployment where one or more monitoring stations are connected to a Connex server.
Additionally, a kiosk option may be installed on personal computers (PCs) that are running Windows 7, 64 bit, which allows the user to upload episodic data through a USB port to the Server, via the network.
#### Indications for Use:
The Connex Central Station is intended to be used by clinicians for the central monitoring of neonatal, pediatric, and adult patients in health care facilities. In addition to the central monitoring of patient data and alarms, the Connex software can include optional modules to provide extended recording of patient data, including full disclosure.
#### Contraindications:
There are no known contraindications for use.
#### Technological Characteristics:
The subject device has the same technological characteristics and indications for use as the predicate device. The hardware and software functionality of the Monitoring Station remain the same as the cleared device except as described below. The Monitoring Station includes the following new features: support for new patient vital signs data and alarms from a new module, called Early Sense. in the Connex Vital Signs Monitor 6000 Series patient monitor, ability to provide hallway displays that duplicate the content on the Monitoring Station's main display, ability to display patient data graphically, ability to deliver alarm notifications to 3d party communication systems, and minor software and connectivity enhancements to improve performance and customer experience.
{2}------------------------------------------------
### WelchAllym
### Non-Clinical Tests:
The Monitoring Station was tested to the following standards:
| Standard | Version | Title |
|----------------|-----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| IEC 60601-1-1 | 2 Ed 2000 | Information Technology Equipment - Safety - Part 1: General Requirements |
| IEC 60601-1 | 2 Ed 1988 | Medical electrical equipment -- Part 1: General requirements for basic safety and essential performance |
| IEC 60601-1-4 | 1 Ed 1996 | Medical electrical equipment - Part 1-4: Consolidated edition 1.1 - General requirements for safety - Collateral standard: Programmable electrical medical systems |
| IEC 60601-1-8 | 1 Ed 2003 | Medical Electrical Equipment - Part 1-8: General Requirements for Basic Safety and Essential Performance - Collateral Standard: General Requirements, Tests and Guidance for Alarm Systems in Medical Electrical Equipment and Medical Electrical Systems |
| IEC 60601-2-49 | 1 Ed 2001 | Medical Electrical Equipment - Part 2-49: Particular Requirements for the Basic Safety and Essential Performance of Multifunction Patient Monitoring Equipment |
| EN/IEC 62304 | 1 Ed 2006 | Medical Device Software – Software Life Cycle Processes |
| ISO 14971 | 2 Ed 2007 | Medical devices - Application of risk management to medical devices |
Verification and validation were conducted to ensure expected performance of the Monitoring Station. The following tests were performed:
| Test Description | Test Objective | Conclusions |
|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
| Alarm Gateway<br>Service Configuration<br>Settings - single<br>central station | Verified that alarm notifications are properly<br>sent to the 3rd party notification system based<br>on whether or not the alarm notifications<br>module is enabled and which alarm priorities<br>are configured in the Monitoring Station to be<br>sent. | Pass |
| Test Description | Test Objective | Conclusions |
| Alarm Gateway<br>Service Configuration<br>Settings - multiple<br>central stations | Verified that the alarm priorities can be<br>configured for each central station's alarm<br>notifications module from the server or any of<br>six central stations.<br>Verified that alarm notifications are properly<br>sent to the 3rd party notification system based<br>on whether or not each alarm notifications<br>module is enabled and which alarm priorities<br>are configured to be sent. | Pass |
| Disconnection with<br>3rd Party System -<br>single central station | Verified that alarms are displayed on the 3rd<br>party notification system on the first<br>connection or re-connection. It also verifies<br>that the disconnection event with the 3rd party<br>system is logged in the monitoring station logs. | Pass |
| Disconnection with<br>3rd Party System -<br>multiple central<br>stations | Verified that alarms are displayed on the 3rd<br>party notification system on the first<br>connection or re-connection. It also verifies<br>that the disconnection event with the 3rd party<br>system is logged in the monitoring stations<br>logs. | Pass |
| Physiological and<br>Technical Alarms -<br>single central station | Verified that the physiological and technical<br>alarms triggered from the patient monitors and<br>the monitoring station are delivered to the 3rd<br>party notification system. | Pass |
| Alarm Logging,<br>Acknowledgment and<br>Response - single<br>central station | Verified that the alarm notification messages<br>are logged with a timestamp in the monitoring<br>station's log.<br>Verified that acknowledgement of receipt of<br>the alarm by the 3rd party notification system is<br>logged in the monitoring station's log.<br>Verifies that the responses sent by the 3rd party<br>notification system on the receipt of the alarm<br>messages are logged in the monitoring station<br>logs. | Pass |
| Test Description | Test Objective | Conclusions |
| AGS Outbound<br>Licensing | Verified that monitoring station sends alarm<br>notifications to the 3rd party notification<br>system when valid software licenses for the 3rd<br>party notification module are available on the<br>monitoring station, and does not send alarm<br>notifications when there are no valid software<br>licenses.<br>Verified that alarm notifications are sent to 3rd<br>party notification system after software license<br>for 3rd party notification module is activated. | Pass |
| AGS Performance -<br>single central station | Verified that an alarm from an initiating source<br>shall be delivered to the 3rd party notification<br>system within 8 seconds. | Pass |
| Early Sense Settings | Verified that the Early Sense patient monitor<br>module settings cannot be changed from the<br>monitoring station and changes to Early Sense<br>settings on the patient monitor are displayed on<br>the monitoring station. | Pass |
| Early Sense Patient<br>Turning | Verify that the patient turn timer and the<br>completed turns sent from the patient monitor<br>are received and display correctly on the<br>monitoring station. | Pass |
| Early Sense Sources | Verify that Monitoring Station displays the<br>parameter sources correctly for the Early Sense<br>sensors. | Pass |
| Early Sense Exit and<br>Motion Alarms | Verify that the Early Sense Exit and Motion<br>alarms and values display correctly on<br>Monitoring Station. | Pass |
| Early Sense<br>Functionality Multiple<br>Devices | Verify the Early Sense functionality when<br>using multiple patient monitors. | Pass |
| Early Sense Technical<br>Alarms | Verify that the Early Sense technical alarms<br>display correctly on Monitoring Station. | Pass |
| HL7 - Configuration<br>Settings | Verify that the Monitoring Station allows HL7<br>settings to be configured including which<br>parameters are exported and the HL7 version. | Pass |
| Test Description | Test Objective | Conclusions |
| Repeater Display<br>Visual Duplications | Verify that the Repeater Display is a visual<br>duplication of the Central Station display. | Pass |
| Visual and Audible<br>Duplications of<br>Alarms | Verify that the Repeater Display is visual and<br>audible duplication of the Monitoring Station<br>display. | Pass |
| Graphical Trends -<br>Parameters | Verify that Monitoring Station can display and<br>graphically trend parameters. | Pass |
| Graphical Trends<br>Display Options and<br>Navigation | Verify that Monitor Station can display and<br>graphically trend parameters. | Pass |
| Graphical Trends<br>Review Report | Verify printing of Graphical Trends Review<br>report. | Pass |
| Patient Review and 1<br>day Full disclosure<br>licensing | Verify that application allows reviewing last<br>24 hours of vitals data on Flow sheet,<br>Graphical trends and Continuous trends view<br>when these licenses are activated. | Pass |
| Patient Review and 1<br>day Full disclosure<br>licensing | Verify that when the Full disclosure.<br>Continuous Trends, Graphical Trends and<br>Flow Sheet view licenses are configured, the<br>review functionalities are available. | Pass |
| Connex Central<br>Station and CVSM<br>6000 Series Patient<br>Monitor, with Early<br>Sense, Directions for<br>Use Summative<br>Validation | Verify and validate that the Directions For Use<br>for the Connex Central Station and CVSM<br>6000 series patient monitor with integration of<br>the Early Sense Module meet usability<br>requirements as defined in Usability<br>Specifications (DIR 60042476 and DIR<br>60029496, respectively). | Pass |
| Test Description | Test Objective | Conclusions |
| Connex Central<br>Station and CVSM<br>6000 Series Patient<br>Monitor, with Early<br>Sense, Summative<br>Validation | The primary objective of this study is to verify<br>and validate that Connex Central Station and<br>CVSM 6000 Series, with Early Sense, meet<br>their usability requirements with trained end<br>users and that the product satisfies users'<br>needs. | Pass |
.
{3}------------------------------------------------
{4}------------------------------------------------
{5}------------------------------------------------
# WelchAllym
{6}------------------------------------------------
### WelchAllym
#### Clinical Performance Data:
No clinical studies were utilized for the purpose of obtaining safety or effectiveness data.
#### Device Comparison Table:
The Monitoring Station is substantially equivalent in operation and performance to the Connex Workstation (K120343).
| | Subject Device and Predicate Device Comparison | | | |
|---------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--|
| Characteristic | Subject Device | Predicate Device | Differences | |
| Device | Monitoring Station or<br>Connex Central Station | Connex Workstation | Name change | |
| Manufacturer | Welch Allyn, Inc. | Welch Allyn, Inc. | Same | |
| 510(k) Number | Not yet assigned | K120343 | N/A | |
| Regulation Number | 870.2300 Cardiac monitor<br>(including cardiotachmometer<br>and rate alarm) | 870.2300 Cardiac monitor<br>(including cardiotachmometer<br>and rate alarm) | Same | |
| Classification code | MWI<br>Monitor, Physiological,<br>Patient (Without Arrhythmia<br>Detection Or Alarms) | MWI<br>Monitor, Physiological,<br>Patient (Without Arrhythmia<br>Detection Or Alarms) | Same | |
| Indications for Use | The Connex Central Station is<br>intended to be used by<br>clinicians for the central<br>monitoring of neonatal,<br>pediatric and adult patients in<br>health care facilities.<br>In addition to the central<br>monitoring of patient data and<br>alarms, the Connex software<br>can include optional modules<br>to provide extended recording<br>of patient data, including full<br>disclosure. | The Connex Workstation is<br>intended to be used by<br>clinicians for the central<br>monitoring of neonatal,<br>pediatric and adult patients in<br>health care facilities.<br>In addition to the central<br>monitoring of patient data and<br>alarms, the Connex software<br>can include optional modules<br>to provide extended recording<br>of patient data, including full<br>disclosure. | Same | |
| Target Population | Adult and pediatric patients | Adult and pediatric patients | Same | |
| Use Environment | Medical/Clinical | Medical/Clinical | Same | |
| | Subject Device and Predicate Device Comparison | | | |
| Characteristic | Subject Device | Predicate Device | Differences | |
| Patients supported<br>on one workstation | Up to 48 | Up to 48 | Same | |
| Full disclosure data<br>storage | 168 hours | 168 hours | Same | |
| Central station<br>interfaces with<br>wireless and<br>hardwired patient<br>monitors over the<br>network | Yes (Monitoring Station<br>connects to the network by<br>ethernet) | Yes (Connex Workstation<br>connects to the network by<br>ethernet) | Same | |
| Communication<br>with patient<br>monitors and spot<br>check devices:<br>devices supported | • Episodic Devices that can<br>communicate with the<br>Episodic Connectivity<br>Service (ECS) software<br>module (tested with actual<br>episodic devices)<br>• Continuous monitors that<br>can communicate with the<br>Continuous Connectivity<br>Service (CCS) software<br>module (tested with actual<br>patient monitors) | • Episodic Devices that can<br>communicate with the<br>Episodic Connectivity<br>Service (ECS) software<br>module (tested with actual<br>episodic devices)<br>• Continuous monitors that<br>can communicate with the<br>Continuous Connectivity<br>Service (CCS) software<br>module (tested with<br>simulator that uses the same<br>user interface specification<br>used for patient monitors) | Same | |
| Device<br>communication<br>protocol | WACP | WACP | Same | |
| Adjustments made<br>on patient monitor<br>from central<br>station. | Alarm limits (except Early<br>Sense settings),<br>Suspend (pause audio) alarms,<br>except pausing Early Sense<br>alarms will have no effect on<br>the patient monitor. | Alarm limits,<br>Suspend (pause audio) alarms. | Same, except<br>setting<br>adjustments for<br>the new Early<br>Sense patient<br>monitor module<br>can only be<br>made at the<br>bedside, not at<br>the central<br>station. | |
| Supports USB<br>kiosk for data<br>loading from<br>periodic devices to<br>central station | Yes | Yes | Same | |
| Subject Device and Predicate Device Comparison | | | | |
| Characteristic | Subject Device | Predicate Device | Differences | |
| Review capability | Yes<br>• Patient List<br>• Patient Details<br>• Flow Sheet (historic<br>episodic vital signs data and<br>alarms for one patient in<br>tabular format)<br>• Continuous Trends (historic<br>continuous and episodic<br>vital signs data and alarms<br>for one patient in tabular<br>format)<br>• Graphical Trends (historic<br>continuous and episodic<br>vital signs data and alarms<br>for one patient in graphical<br>format)<br>• Patient Alarms history (in<br>tabular format) | Yes<br>• Patient List<br>• Patient Details<br>• Patient Review (Alarm<br>history for one patient in<br>tabular format) | Added new<br>review<br>capabilities | |
| Software Licensing | Yes | No | Added ability to<br>license some<br>software<br>features | |
| User Configuration | Yes | No | Added user<br>settable,<br>password<br>protected,<br>software<br>features | |
| Informational<br>messages | Yes (additional messages were<br>added to support changes, like<br>adding the ADT/EMR<br>support, which improve users'<br>interactions with the device) | Yes | Additional<br>messages added<br>to support new<br>features and<br>clarify<br>information for<br>users. These<br>are not alarms. | |
| Compliant with<br>IEC 60601-1-8<br>alarm standard | 1st edition | 1st edition | Same | |
| Supports multiple<br>workstations | Yes | Architecture was present but<br>feature was not implemented | Implemented<br>ability for<br>multiple<br>workstations to<br>be on the same | |
| Subject Device and Predicate Device Comparison | | | | |
| Characteristic | Subject Device | Predicate Device | Differences | |
| Hardcopy printing | Yes<br>Patient List<br>Flow Sheet<br>Continuous Trends<br>Graphical Trends<br>Patient Alarms history<br>Station Alarms history | Yes<br>Patient List | Added ability to<br>print additional<br>reports | |
| Language Support | English, French, German,<br>Spanish | English | More languages<br>supported | |
| Service support<br>tools | Yes (added service support<br>tools such as logs, upgrade.<br>downgrade, and configuration<br>tools) | No | Added various<br>service tools | |
| Interfaces with external systems | | | | |
| Ability to forward<br>notifications and<br>alarms to 3rd party<br>notification<br>systems | Yes | No | Added ability to<br>interface with<br>3rd party<br>notification<br>systems | |
| Admit, discharge<br>and transfer (ADT)<br>patients | Yes - Admit: can load<br>patients from a list generated<br>from the hospital's ADT<br>system or manually;<br>Discharge: can remove<br>patient from Monitoring<br>Station:<br>Transfer: Can move a patient<br>from one bed to another while<br>connected to the same<br>Monitoring Station. | Yes — Admit: can load<br>patients manually. Does not<br>communicate with the<br>hospital's ADT system:<br>Discharge: can remove<br>patient from Connex<br>Workstation;<br>Transfer: Can move a patient<br>from one bed to another while<br>connected to the same Connex<br>Workstation. | Added option to<br>interface with<br>hospital's ADT<br>system | |
| Optional HL7<br>interface capability<br>to health<br>information system<br>(HIS) | CorePoint Integration Engine<br>(OTS) | Includes architecture to<br>support this feature in the<br>future. | EMR support is<br>now<br>implemented. | |
| Remote technical<br>support | Yes - Partner Connect | No | Added ability to<br>interface with<br>Partner Connect<br>(a separate<br>Service<br>software<br>program) to<br>provide remote | |
| Subject Device and Predicate Device Comparison | | | | |
| Characteristic | Subject Device | Predicate Device | Differences | |
| Physiological Parameters Monitored | | | | |
| Non-invasive blood<br>pressure<br>monitoring | Yes (includes display of Mean<br>Arterial Pressure (MAP)) | Yes (received MAP from<br>patient monitor, but does not<br>display) | Minor change<br>to display MAP | |
| SpHb | Yes | Yes (received SpHb from<br>patient monitor, but does not<br>display) | Minor change<br>to display SpHb | |
| SpO2 monitoring | Yes | Yes | Same | |
| Pulse rate<br>monitoring | Yes (from SpO2 module or<br>Early Sense module in patient<br>monitor) | Yes (from SpO2 module) | Additional<br>sensor source(s)<br>added | |
| Temperature<br>monitoring | Yes | Yes | Same | |
| CO2 monitoring | Yes (includes display of<br>FiCO2, a patient monitor-<br>calculated value) | Yes (received FiCO2 from<br>patient monitor, but does not<br>display) | Minor change<br>to display<br>FiCO2 | |
| Respiration rate<br>(RR) monitoring…
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.