Philips CS770 IntelliSpace Critical Care and Anesthesia
K151366 · Philips Medical Systems · DXJ · Oct 30, 2015 · Cardiovascular
Device Facts
Record ID
K151366
Device Name
Philips CS770 IntelliSpace Critical Care and Anesthesia
Applicant
Philips Medical Systems
Product Code
DXJ · Cardiovascular
Decision Date
Oct 30, 2015
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2450
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
Intended for use in the data collection, storage, and management with independent bedside devices, and ancillary systems that are connected either directly or through networks. The device is indicated for use whenever there is a need for generation of a patient record and computation of drug dosage in all areas patient care is given in the hospital, including critical care and anesthesia areas.
Device Story
CS770 IntelliSpace Critical Care and Anesthesia (ICCA) is a software-only clinical information management system; integrates data from bedside monitors, ancillary devices, and hospital systems (CPOE, lab). Operates as a centralized charting and data management platform; provides clinical decision support via advisories and evidence-based medicine bundles. Clinicians use the system for documentation, medication ordering, and patient record management. Features include a drug calculator, data analysis/reporting (DAR) toolset, and UI with ribbon-based navigation. Enhancements include third-party medical reference display, medication order co-signing workflows, and improved security/audit logging. System supports critical care and anesthesia environments by streamlining workflow and providing structured patient data access. Benefits include improved clinical documentation accuracy, standardized medication ordering, and enhanced data traceability.
Clinical Evidence
Bench testing only. Verification and validation activities performed, including system-level tests, performance tests, and hazard analysis-based testing. Results confirmed the device meets all reliability requirements and performance claims consistent with the predicate.
Technological Characteristics
Software-only product; runs on Windows Server 2008 R2/2012 R2 with SQL Server 2008 R2/2012. Programming language: Microsoft .NET C#. Connectivity: Ethernet LAN, HL7 interfaces, IntelliBridge System. Standards: ISO 15223-1, IEC 62304, AAMI/ANSI/IEC 62366. Features: ribbon-based UI, XML-based formulary import/export, audit logging, and role-based access control.
Indications for Use
Indicated for use in hospital settings, including critical care and anesthesia areas, for patient record generation and drug dosage computation. Applicable to all patient populations requiring clinical data management.
Regulatory Classification
Identification
A medical cathode-ray tube display is a device designed primarily to display selected biological signals. This device often incorporates special display features unique to a specific biological signal.
Predicate Devices
IntelliVue Clinical Information Portfolio, Release E.0 (K100272)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains two logos. The logo on the left is the Department of Health & Human Services - USA logo. The logo on the right is the FDA U.S. Food & Drug Administration logo. The FDA logo is blue and white.
September 1, 2023
Philips Medical Systems Kristen Phillips, RHIA, CTFL Regulatory Affairs Specialist 3000 Minuteman Road, MS 4304 Andover, Massachusetts 01810
Re: K151366
Trade/Device Name: CS770 IntelliSpace Critical Care and Anesthesia, Release H.0 Regulation Number: 21 CFR 870.2450 Regulation Name: Medical Cathode-ray Tube Display Regulatory Class: Class II Product Code: DXJ
Dear Kristen Phillips:
The Food and Drug Administration (FDA) is sending this letter to notify you of an administrative change related to your previous substantial equivalence (SE) determination letter dated October 30, 2015. Specifically, FDA is updating this SE Letter to remove the secondary product code NSX as an administrative correction.
Please note that the 510(k) submission was not re-reviewed. For questions regarding this letter, please contact Aneesh Deoras, OHT2: Office of Cardiovascular Devices, 240-402-4363, Aneesh.Deoras@fda.hhs.gov.
Sincerely,
Aneesh S. Deoras -S
for
Jennifer Shih Kozen Assistant Director Division of Cardiac Electrophysiology, Diagnostics, and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
{1}------------------------------------------------
Image /page/1/Picture/1 description: The image shows the seal of the Department of Health & Human Services - USA. The seal is circular and contains the words "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" around the perimeter. In the center of the seal is an abstract image of a human face in profile, with three stylized lines representing the nose, mouth, and chin.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
October 30, 2015
Philips Medical Systems Kristen Phillips, RHIA, CTFL Regulatory Affairs Specialist 3000 Minuteman Road, MS 4304 Andover, Massachusetts 01810-1099
Re: K151366
Trade/Device Name: CS770 IntelliSpace Critical Care and Anesthesia, Release H.0 Regulation Number: 21 CFR 870.2450 Regulation Name: Medical cathode-ray tube display Regulatory Class: II Product Code: DXJ. NSX Dated: September 29, 2015 Received: October 2, 2015
Dear Ms. Phillips:
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.
{2}------------------------------------------------
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 (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/Industry/default.htm. Also, please note the regulation entitled. "Misbranding by reference to premarket notification" (21CFR 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.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours, Tina Kiang -S
for Erin I. Keith, M.S. Director Division of Anesthesiology, General Hospital, Respiratory, Infection Control and Dental Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{3}------------------------------------------------
# Indications for Use
510(k) Number (if known) K151366
Device Name
CS770 IntelliSpace Critical Care and Anesthesia, Release H.0
#### Indications for Use (Describe)
Intended for use in the data collection, storage, and management with independent bedside devices, and ancillary systems that are connected either directly or through networks. The device is indicated for use whenever there is a need for generation of a patient record and computation of drug dosage in all areas patient care is given in the hospital, including critical care and anesthesia areas.
| Type of Use (Select one or both, as applicable) | |
|--------------------------------------------------|---------------------------------------------|
| × Prescription Use (Part 21 CFR 801 Subpart D) | 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."
{4}------------------------------------------------
Image /page/4/Picture/1 description: The image shows the word "PHILIPS" in large, bold, blue letters. The font is sans-serif and the letters are evenly spaced. The word is centered and takes up most of the frame.
Connected Care Solutions Quality & Regulatory Group 3000 Minuteman Road Mailstop 4304 Andover, MA 01810 Tel: (978) 659-3000 Fax: (978) 685-5624
# 510(k) SUMMARY
This summary of 510(k) information is submitted in accordance with the requirements of the Safe Medical Devices Act of 1990 and 21 CFR §807.92.
Reference 510(k) Number: K151366 CS770 IntelliSpace Critical Care and Anesthesia, Release H.0
- 1. The submitter of this premarket notification is:
Kristen Phillips Regulatory Affairs Specialist Philips Medical Systems 3000 Minuteman Road, MS 4304 Andover, Massachusetts 01810-1099 Tel: 978-659-4219 Fax: 978-659-4481 e-mail: Kristen.phillips@philips.com
This summary was prepared on 29 October 2015.
- 2. The name and classification of the device:
Trade Name: CS770 IntelliSpace Critical Care and Anesthesia, Release H.O. Common name: Clinical Information Management System Classification:
| Classification | ProCode | Description |
|----------------------|---------|--------------------------------------------------|
| 870.2450, II | DXJ | Display, Cathode-Ray Tube, Medical |
| Secondary Prod Code: | | |
| | NSX | Software, transmission and storage, patient data |
- 3. Device Description:
The CS770 IntelliSpace Critical Care and Anesthesia software (Release H.O), a modified version of the IntelliVue Clinical Information Portfolio which was last cleared under premarket notification number
{5}------------------------------------------------
K100272. ICCA is a software only product used for charting and data management, offers clinical decision and clinical workflow support for critical care environments, intra-operative anesthesia, and the anesthesia-critical care continuum. Integrating information from patient vital sign monitors and ancillary bedside devices, hospital systems such as CPOE and laboratory, and clinical documentation, ICCA uses advisories and evidence-based medicine bundles to provide information to clinicians. In addition ICCA provides a powerful Data Analysis and Reporting (DAR) database and reporting toolset for the critical care and anesthesia environments.
- 4. The CS770 IntelliSpace Critical Care and Anesthesia, Release H.O software is substantially equivalent to the previously cleared IntelliVue Clinical Information Portfolio, Release E.0 marketed pursuant to K100272.
- 5. Indications for Use
The device has an updated Indications for Use and Intended Use Statement: Intended for use in the data collection, storage, and management with independent bedside devices, and ancillary systems that are connected either directly or through networks. The device is indicated for use whenever there is a need for generation of a patient record and computation of drug dosage in all areas patient care is given in the hospital, including critical care and anesthesia areas.
- 6. The major modifications are as follows:
The purpose of this submission is to formally document the renaming of the product to the Philips CS770 IntelliSpace Critical Care and Anesthesia (ICCA) as well as to update the 510(k) filing to include the following software changes:
### Medical Reference capability
Third party medical reference information will be displayed to the end user at the time of entering an order. Depending on the configuration, the end user may be given the opportunity to review the medical reference information provided and cancel or modify the order.
### Patient Data Security
Patient data security is being enhanced in relation to controlling and tracking of users actions when they access restricted patient records.
# Formulary Upload
A new tool launched from ICCA's system management tools which allows the following functions:
- · Exporting ICCA configuration into XML files
- Importing XML files into an existing ICCA system
# User Interface (UI) Streamlining
The UI enhancements introduce a new "look" to the patient chart container (the parent window that hosts patient data), Patient Census, Notes and Forms. Preexisting chart functionality is retained with some minor exceptions; the user's navigation has been modified and the previous menu approach is replaced with an industry-standard ribbon approach. The new UI involves implementing
{6}------------------------------------------------
a ribbon that replaces most of the menu and toolbar commands (available from the chart, census, and personal organizer), a user login / logout area, a notification area (for reminder, advisory, notification icons), and a patient area (for the patient picker and infostrip) which is only visible from the patient chart. The core chart functionality (flowsheet) remains the same as in prior releases.
### Discharge Management Report
Enhance the discharge document to accommodate more data points, customization and capture data available in the record at the time the report is generated.
#### Medication Order co-signing
In many clinical environments, there is a list of drugs that the customer considers to be restricted and need two clinical approvals for ordering of the drug. ICCA supports:
- Configurable list of drugs that need the co-signing
- Holding the order release until one additional clinician has approved the original order. No interventions are generated until additional clinician approves the order.
- Allow the customer to designate specific users who have co-signing authority
- Modify the existing order workflow to present a co-signing authentication/opportunity for the end user.
- Log and traceability on all activities related to co-signing in orders audit trail
- Configuration is done as a check box on the drug in the pharmacy product editor
- Generate a reminder icon, an update to the reminder document
- If the user has cosign permission, it is configurable if the order can continue or be held.
- · Co-sign exists whenever the order is created or modified.
- Co-sign impacts all types of orders that uses that drug.
- Inbound interfaces are not impacted
- Comparative Predicate Device Subject Device CS770 IntelliSpace Critical Care and Characteristic IntelliVue Clinical Information Portfolio, Release E.0 Anesthesia, Release H.O IntelliVue Clinical Information Portfolio, Device Name CS770 IntelliSpace Critical Care and Release E.O Anesthesia, Release H.O The below indications for use have been updated to include the implied use in the name for critical care and anesthesia areas. Intended Use Intended for use in the data collection, Intended for use in the data collection, storage, and management with storage, and management with independent bedside devices, and ancillary independent bedside devices, and systems that are connected either directly ancillary systems that are connected or through networks. either directly or through networks. The device is indicated for use whenever The device is indicated for use whenever Indications for use there is a need for generation of a patient there is a need for generation of a patient record and computation of drug dosage. record and computation of drug dosage in all areas patient care is given in the
- 7. Comparison with predicate:
{7}------------------------------------------------
| Comparative<br>Characteristic | Predicate Device<br>IntelliVue Clinical Information Portfolio,<br>Release E.O | Subject Device<br>CS770 IntelliSpace Critical Care and<br>Anesthesia, Release H.O |
|---------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------|
| Population | No direct patient connection. As this<br>software is only intended for use in data<br>collection, storage, and management; the<br>performance of the software does not<br>change with different patient populations. | Same |
| Environment | Hospital | Same |
| Operating Principle | Data Management (charting and<br>reporting) | Same; with the addition of the Patient<br>Analytics Platform option. |
| Electronic Patient<br>Record | Configurable Patient Record usually<br>consisting of Flowsheets, Notes and Forms,<br>Medication Administration Record, Patient<br>Summary, History and Physical, Worklist,<br>procedure and diagnosis coding | Same; with UI enhancements, Discharge<br>Management report and Medication co-sign. |
| Census | Patient Census screen showing patient<br>status | Same |
| Configuration<br>Editors | A set of configuration editors are provided<br>that allow trained personnel to configure<br>the Patient Record documents and<br>reports. Programming language skill not<br>required. | Same, plus ability to import/export<br>configuration (known as Formulary<br>Upload) |
| Reporting Capability | Generate paper copy reports for the<br>patient record, including audit trail. | Same |
| Drug Calculator | Present | Same |
| Calculations Engine<br>& Clinical Advisories | Present | Same Calculations Engine with same<br>clinical advisories; added Deep Vein<br>Thrombosis advisory. |
| Alarm functionality | None | Same |
| Measurement<br>functionality | None | None |
| Technology | ICIP follows deployment model similar to<br>Microsoft technologies such as clustering.<br>ICIP was designed to be a cost effective<br>solution which handles single unit,<br>standalone starter configurations to large<br>scale, multi-unit installations.<br>Reference the ICIP Architecture Overview<br>in Appendix A, ICIP System Architecture<br>Enterprise View diagram in Appendix B<br>and the 865209 IntelliVue Clinical<br>Information Portfolio Release E.00<br>Technical Data Sheet in Appendix C. | Same |
| Comparative | Predicate Device | Subject Device |
| Characteristic | IntelliVue Clinical Information Portfolio, | CS770 IntelliSpace Critical Care and |
| | Release E.O | Anesthesia, Release H.O |
| | Windows Server 2008, Enterprise Edition;<br>SQL Server 2008 | Windows Server 2008 R2, Enterprise<br>Edition;<br>Windows Server 2012 R2, Enterprise<br>Edition;<br>SQL Server 2008 R2/2012, Enterprise<br>Edition |
| Programming<br>language | Microsoft .NET C# | Same |
| Remote Service<br>Network capability | To gain remote access, the user can run<br>Remote Desktop client, or Terminal Server<br>sessions on any appropriately configured<br>Windows Terminal Server Host. | Same |
| Interfaces/Data<br>Acquisition - Philips<br>Monitoring System | HL7 interface from Philips Information<br>Center server | Same |
| Interfaces/Data<br>Acquisition | Device Link II (K041942) and DataCapsule<br>Information using Ethernet LAN standard<br>protocol to interface with other hospital<br>networks. | Same, plus IntelliBridge System |
| Interfaces/Hospital<br>Information System<br>- Inputs | ICIP interfaces to other hospital systems<br>through Health Level 7 (HL7). | Same |
| Interfaces/Hospital<br>Information<br>Systems - Output | Patient Data export; Document Export | Same |
| Auto-Charting | Automatically stored device data without<br>user intervention | Same |
| Data Analysis and<br>Reporting | DAR provides users a location to query and<br>develop patient data reports without<br>impacting the performance of the ICCA<br>charting systems. | Same |
| Medical Reference | N/A | Third party medical reference information<br>displayed to user. |
| User Access &<br>Patient Data<br>Security | User Authentication services and user<br>roles to include logging for audit trail<br>information. | Individual Patient lock, Break glass (user<br>emergency access with logging) and<br>enhanced logging information. |
{8}------------------------------------------------
- 8. The technological characteristic changes of this device are the design changes as follows:
- The electronic patient record is the same with additional UI enhancements, Discharge . Management report and medication co-sign.
- The configuration editors are the same plus the ability to import/export formulary configuration ●
- . The Calculations Engine & Clinical Advisories are the same with the addition of the Deep Vein Thrombosis advisory.
{9}------------------------------------------------
- The operating system did not include a design change, however the device is verified for compatibility with the updated versions of Windows (as listed in the table above)
- . The Interfaces/Data acquisition in the devices are the same with the addition of interfacing with IntelliBridge System.
- The device has added a third party medical reference display.
- . The user access & patient data security is the same with the addition of enhanced logging, individual patient lock and user emergency access with logging.
- 9. Standards and Guidance used:
| Standard<br>Number & Date | Standard Title | Recognition<br>Number |
|-----------------------------------------|-----------------------------------------------------------------------------------------------------------------|-----------------------|
| ISO 15223-1:<br>2012 | Medical devices -- Symbols to be used<br>with medical device labels, labeling and<br>information to be supplied | 5-90 |
| IEC 62304: 2006 | Medical device software. Software<br>lifecycle processes | 13-32 |
| AAMI/ANSI/IEC<br>62366:<br>2007/(R)2013 | Medical devices. Application of usability<br>engineering to medical devices | 5-67 |
The following FDA documents were used for guidance:
- "The New 510(k) Paradigm, Alternate Approaches to Demonstrating Substantial Equivalence O in Premarket Notifications", issued March 20, 1998.
- O "Guidance for Industry and FDA Staff, Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices", issued May 11, 2005.
- "Guidance for FDA Reviewers and Compliance on Off-The-Shelf Software Use in Medical O Devices", issued September 9, 1999.
- "Guidance for Industry: Cybersecurity for Networked Medical Devices Containing Off-the- O Shelf (OTS) Software" issued January 14, 2005.
- "Guidance for Industry and Food and Drug Administration Staff; The 510(k) Program: O Evaluating Substantial Equivalence in Premarket Notifications [510(k)]", Document issued on: July 28, 2014
- "Use of Standards in Substantial Equivalence Determinations", March 12, 2000. O
- "Guidance for Industry", Alternative to Certain Prescription Device Labeling Requirements, O issued January 21, 2000.
- O "Guidance for Industry and FDA Staff, Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices", issued May 11, 2005. "General Principles of Software Validation; Final Guidance for Industry and FDA Staff", January 11, 2002
{10}------------------------------------------------
- "Guidance for Industry and Food and Drug Administration Staff"; Content of Premarket O Submissions for Management of Cybersecurity in Medical Devices, Document Issued on: October 2, 2014
- o "Guidance for Industry and Food and Drug Administration Staff, Mobile Medical Applications"; Document issued on: September 25, 2013
- 10. Non-clinical Testing:
Verification, validation, and testing activities, where required to establish the performance, functionality, and reliability characteristics of the new device with respect to the predicate are performed. Testing involved system level tests, performance tests, and peformance testing from hazard analysis. Pass/Fail criteria were based on the specifications cleared for the predicate device and test results showed substantial equivalence.
- 11. Conclusions from Non-clinical testing:
The CS770 IntelliSpace Critical Care and Anesthesia, Release H.O software meets all reliability requirements and performance claims; this supports a determination of substantial equivalence.
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.