K253927 · Live Medica, LLC · LLZ · Feb 6, 2026 · Radiology
Device Facts
Record ID
K253927
Device Name
LiveMedica Enterprise PACS
Applicant
Live Medica, LLC
Product Code
LLZ · Radiology
Decision Date
Feb 6, 2026
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
LiveMedica Enterprise PACS is a system for distributing, viewing, processing and archiving medical images within and outside healthcare environments. The LiveMedica Enterprise PACS server receives image data in DICOM format via the hospital network. This provides universal connections to archives, modalities, and workstations. The supported modalities are listed in the DICOM Conformance Statement. LiveMedica Enterprise PACS is to be used only by trained and instructed health care professionals. It can support physicians and/or their medical staff in providing their own diagnosis for medical cases. The final decision regarding diagnosis, however, resides with the doctor and/or their medical staff in their own area of responsibility. Although the web and technologies allow the software to run on a variety of hardware platforms, for diagnostic purposes the user must make sure that the display hardware used for reading the images complies with state-of-the-art diagnostic requirements and currently valid laws. Only DICOM for presentation images can be used on an FDA approved monitor for mammography for primary image diagnosis. Only uncompressed or non-lossy compressed images must be used for primary image diagnosis in mammography.
Device Story
LiveMedica Enterprise PACS is a server-side rendering system for storage, retrieval, management, and display of DICOM-compliant medical images; used in hospitals and multi-site networks. Inputs include DICOM image data from various modalities (CR, CT, DR, DX, ES, ECG, GM, IO, MG, MR, NM, PT, OT, RF, RT, US, XA, XC) via hospital network. System provides tools for image manipulation (zoom, pan, window/level, annotations, measurements, MPR, MIP, fusion) and study management. Operated by trained healthcare professionals; supports clinical decision-making by providing diagnostic-quality images. Final diagnostic responsibility remains with the clinician. System integrates with HIS/RIS/EMR via HL7/FHIR. Benefits include centralized study management, universal connectivity to archives/modalities, and advanced visualization capabilities for diagnostic workflows.
Clinical Evidence
Bench testing only. No clinical data provided. Verification and validation testing conducted per FDA guidance for software functions and cybersecurity. Compliance with DICOM (NEMA PS 3.1-3.20) and ISO/IEC 10918-1 standards confirmed.
Technological Characteristics
Server-side rendering PACS; Windows Server 2022/Ubuntu 24.04 OS; PostgreSQL database. Supports DICOM 3.0, HL7, and FHIR. Hardware requirements: 16 vCPU, 32 GB RAM, SSD storage. Connectivity: Networked via hospital infrastructure. Software developed per IEC 62304 and ISO 14971. Cybersecurity controls per 2025 FDA guidance.
Indications for Use
Indicated for trained healthcare professionals to distribute, view, process, and archive medical images for diagnostic purposes across healthcare environments. Supports physicians and medical staff in clinical diagnosis. Requires FDA-approved monitors for primary mammography diagnosis using uncompressed or non-lossy compressed images.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
February 6, 2026
Live Medica LLC
% Danielle Short
Regulatory Consultant
MEDIcept, Inc.
200 Homer Ave.
Ashland, Massachusetts 01721
Re: K253927
Trade/Device Name: LiveMedica Enterprise PACS
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: LLZ
Dated: December 8, 2025
Received: December 8, 2025
Dear Danielle Short:
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 (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
{1}
K253927 - Danielle Short
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13484 clause 8.3 (Nonconforming product), and ISO 13485 clause 8.5 (Corrective and preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K253927 - Danielle Short
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Jessica Lamb, Ph.D.
Assistant Director, Imaging Software Team
DHT8B: Division of Radiological Imaging Devices and Electronic Products
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K253927 | ? |
| Please provide the device trade name(s). | | ? |
| LiveMedica Enterprise PACS | | |
| Please provide your Indications for Use below. | | ? |
| LiveMedica Enterprise PACS is a system for distributing, viewing, processing and archiving medical images within and outside healthcare environments. The LiveMedica Enterprise PACS server receives image data in DICOM format via the hospital network. This provides universal connections to archives, modalities, and workstations. The supported modalities are listed in the DICOM Conformance Statement. LiveMedica Enterprise PACS is to be used only by trained and instructed health care professionals. It can support physicians and/or their medical staff in providing their own diagnosis for medical cases. The final decision regarding diagnosis, however, resides with the doctor and/or their medical staff in their own area of responsibility. Although the web and technologies allow the software to run on a variety of hardware platforms, for diagnostic purposes the user must make sure that the display hardware used for reading the images complies with state-of-the-art diagnostic requirements and currently valid laws. Only DICOM for presentation images can be used on an FDA approved monitor for mammography for primary image diagnosis. Only uncompressed or non-lossy compressed images must be used for primary image diagnosis in mammography. | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
{4}
Traditional 510(k) Premarket Notification
Live Medica LLC
K253927
510(k) Summary
DATE PREPARED
February 3, 2026
MANUFACTURER AND 510(k) OWNER
Live Medica LLC
2301 Sunnystone Way
Raleigh, NC 27613
Official Contact: Nick Ponder, COO
REPRESENTATIVE/CONSULTANT
Danielle Short
MEDIcept
Telephone: (610)-304-4614
Email: dshort@medicept.com
DEVICE INFORMATION
Proprietary Name/Trade Name: LiveMedica Enterprise PACS
Common Name: Medical Image Management and Processing System
Regulation Number: 21 CFR 892.2050
Class: II
Product Code: LLZ
Review Panel: Radiology
PREDICATE DEVICE IDENTIFICATION
| 510(k) Number | Predicate Device Name / Manufacturer | Predicate/Reference |
| --- | --- | --- |
| K082269 | VISAGE PACS6.0/CS 3.1 | Predicate |
The predicate devices have not been subject to a design related recall.
DEVICE DESCRIPTION
LiveMedica Enterprise PACS is a Picture Archiving and Communication System designed to store, retrieve, manage and display DICOM-compliant medical images for diagnostic imaging workflows across hospitals, imaging centers and multi-site healthcare networks. It includes functionality for server-side image rendering, centralized and edge-based study management and routing. The system is to be used by trained healthcare professionals to perform advanced image manipulations, including zoom, pan, window/level adjustments, annotations, measurements and more. LiveMedica Enterprise PACS supports DICOM conformance, HL7/FHIR-based interoperability and integrates with HIS/RIS/EMR systems.
Page 1
{5}
Traditional 510(k) Premarket Notification
Live Medica LLC
# INTENDED USE
LiveMedica Enterprise PACS is a system for distributing, viewing, processing and archiving medical images within and outside healthcare environments. The LiveMedica Enterprise PACS server receives image data in DICOM format via the hospital network. This provides universal connections to archives, modalities, and workstations. The supported modalities are listed in the DICOM Conformance Statement.
LiveMedica Enterprise PACS is to be used only by trained and instructed health care professionals. It can support physicians and/or their medical staff in providing their own diagnosis for medical cases. The final decision regarding diagnosis, however, resides with the doctor and/or their medical staff in their own area of responsibility.
Although the web and technologies allow the software to run on a variety of hardware platforms, for diagnostic purposes the user must make sure that the display hardware used for reading the images complies with state-of-the-art diagnostic requirements and currently valid laws.
Only DICOM for presentation images can be used on an FDA approved monitor for mammography for primary image diagnosis.
Only uncompressed or non-lossy compressed images must be used for primary image diagnosis in mammography.
# COMPARISON OF TECHNOLOGICAL CHARACTERISTICS
LiveMedica believes that the LiveMedica Enterprise PACS is substantially equivalent to the predicate device based on the information summarized here:
The subject device has the same intended use and similar indications for use. The subject device has the same and/or similar technological characteristics as the device cleared in K082269. These technological characteristics have undergone testing to ensure the device is as safe and effective as the predicate.
| Characteristic | Subject Device
LiveMedica Enterprise PACS | Predicate Device
VISAGE PACS 6.0/CS 3.1
K082269 | Equivalence |
| --- | --- | --- | --- |
| Intended Use and Indications for Use | LiveMedica Enterprise PACS is a system- for distributing, viewing, processing, and archiving medical images within and outside health care environments. The LiveMedica PACS server receives image data in DICOM format via the hospital network. This provides universal connections to | Visage PACS/CS is a system- for distributing, viewing, processing, and archiving medical images within and outside health care environments. The Visage PACS/CS server receives image data in DICOM format via the hospital network. This provides universal connections to | Same intended use and similar indications for use. |
{6}
Traditional 510(k) Premarket Notification
Live Medica LLC
| Characteristic | Subject Device
LiveMedica Enterprise
PACS | Predicate Device
VISAGE PACS 6.0/CS 3.1
K082269 | Equivalence |
| --- | --- | --- | --- |
| | DICOM format via the hospital network. This provides universal connections to archives, modalities, and workstations. The supported modalities are listed in the DICOM Conformance Statement.
LiveMedica Enterprise PACS is to be used only by trained and instructed health care professionals. It can support physicians and/or their medical staff in providing their own diagnosis for medical cases. The final decision regarding diagnoses, however, resides with the doctors and/or their medical staff in their own area of responsibility.
Although the web and thin client technologies allow the software to be run on a variety of hardware platforms, for diagnostic purposes the user must make sure that the display hardware used for reading the images complies with state-of-the-art diagnostic requirements and currently valid laws.
Only DICOM for presentation images can be used on an FDA approved monitor for mammography | archives, modalities, and workstations. The supported modalities are listed in the DICOM Conformance Statement.
Besides general image interpretation and processing tools, Visage PACS/CS provides specific tool sets for several clinical applications, including:
- CT/MR angiography, e.g. for vascular analysis and stent planning
- Cardiac analysis, including calcium scoring and functional assessment of cardiac CT data
-Neuroradiology, including CT and MR brain perfusion analysis
-Oncology, including SUV analysis and lesion marking and analysis
Visage PACS/CS is to be used only by trained and instructed health care professionals. It can support physicians and/or their medical staff in providing their own diagnosis for medical cases. The final decision regarding diagnoses, however, resides with the doctors and/or their medical staff in their own area of responsibility.
Although the web and thin client technologies allow the software to be run on a variety of hardware platforms, for diagnostic purposes the user must make sure that the display | |
Page 3
{7}
Traditional 510(k) Premarket Notification
Live Medica LLC
| Characteristic | Subject Device
LiveMedica Enterprise
PACS | Predicate Device
VISAGE PACS 6.0/CS 3.1
K082269 | Equivalence |
| --- | --- | --- | --- |
| | for primary image
diagnosis. Only
uncompressed or non-lossy
compressed images must be
used for primary image
diagnosis in mammography. | hardware used for reading the
images complies with state-of-
the-art diagnostic requirements
and currently valid laws.
Only DICOM for presentation
images can be used on an FDA
approved monitor for
mammography for primary
image diagnosis. Only
uncompressed or non-lossy
compressed images must be used
for primary image diagnosis in
mammography. | |
| Product Codes
and Regulation
Number | LLZ
21 CFR 892.2050 | LLZ
21 CFR 892.2050 | Same |
| Image file
formats | DICOM 3.0 | DICOM 3.0 | Same |
| Image
Acquisition and
Communication | DICOM Compliant | DICOM Compliant | Same |
| Supported
Modalities | CR, CT, DR, DX, ES, ECG
GM, IO, MG, MR, NM, PT,
OT, RF, RT, US, XA, XC | CR, CT, DR, DS, DX, ES, GM,
IO, MG, MR, NM, PT, OT, RF,
RT, US, XA, XC | Similar |
| Image
Processing | Server-Side Rendering | Server-Side Rendering | Same |
| Operating
System | Windows | Windows | Same |
| Intended Users | Trainer Healthcare
Professionals | Trained Healthcare Professionals | Same |
Page 4
{8}
Traditional 510(k) Premarket Notification
Live Medica LLC
| Characteristic | Subject Device
LiveMedica Enterprise
PACS | Predicate Device
VISAGE PACS 6.0/CS 3.1
K082269 | Equivalence |
| --- | --- | --- | --- |
| Image
Manipulation
Functions | • Zoom
• Quad Zoom
• Magnify
• Pan
• Window Level
• Contrast Enhance
• Invert Color
• Palette
• Context Tool
• Flip Horizontal
• Flip Vertical
• Rotate Right
• Rotate Left
• Bone Enhancement
• Simple MPR
• MPR
• MIP
• MinIP
• AVG
• Fusion
• Reset Frame | • Zoom
• Quick Zoom
• Magnifying glass
• Pan
• Window Leveling
• Edge enhancement
• Grayscale Inversion
• Rotating, flipping
• MPR,MIP
• Bone removal
• Fusion
• Side-by-side Registration
• Volume Measurement | Similar |
| Measurement | • Line
• Ratio of length
• Measure Compare
• Center Point
• Radial Length
• Ellipse Area
• Rectangle Area
• Cardiothoracic Ratio
• Cobb Angle
• HO Angle
• Freehand ROI
• Perfect Circle
• Three Point Angle
• Point Pixel
• Spine label
• 3D Point
• 3D Measure
• 3D Angle
• 3D Cursor
• 3D Spine Label
• Cineplay
• Calibration | • Distance
• Angulation
• Area
• Greyscale density
• Manual distance calibration
• Cine Mode
• 3D visualization of 3D image series with gantry tilt
• Automatic generation of thick slices | Similar |
Page 5
{9}
Traditional 510(k) Premarket Notification
Live Medica LLC
| Characteristic | Subject Device
LiveMedica Enterprise
PACS | Predicate Device
VISAGE PACS 6.0/CS 3.1
K082269 | Equivalence |
| --- | --- | --- | --- |
| Hardware Requirements for Server | Minimum Spec for Application server (<100k studies/year)
CPU: 16 vCPU
RAM: 32 GB
Disk: 500 GB SSD (RAID-10)
Storage: 10 TB SAN/NAS
RAID-6
IOPS ≥ 10K+ scalable
SAN/NAS
Database server
CPU: 16 vCPU
RAM: 32 GB | PC 2X Pentium III 1,4 Ghz or PC 1x Pentium IV 3GHz (Hyperthreading),
>= 1GB RAM 2x 60 GB Harddisk SCSI or SATA | Similar |
| Software Requirements for Server | Window Server
2022/Ubuntu 24.04
PostgreSQL
RabbitMQ
Redis
Erlang
Apache Kafka
Nginx
Openrestry | Windows 2003 Server Internet Explorer 6 | Similar |
| Workflow Features – Database Filter, DICOM query/retrace from archives and workstations, change assignment of patients | Yes | Yes | Same |
Page 6
{10}
Traditional 510(k) Premarket Notification
Live Medica LLC
Based on the technological characteristics, it can be concluded that the subject device is substantially equivalent to the predicate device.
## SUMMARY OF NON-CLINICAL TESTING
The software was developed per the following standards:
- IEC 62304:2015 Medical Device software – software life cycle process
- ISO 14971:2019 Medical Devices – Application of risk management to medical devices
The device meets the following voluntary standards:
- NEMA PS 3.1 - 3.20, Digital Imaging and Communications in medicine (DICOM) Set. (Radiology), 2024e
- ISO IEC 10918-1, Information technology – Digital compression and coding of continuous-tone still images: Requirements and guidelines
The device underwent verification and validation testing according to the following guidance documents:
- Content of Premarket Submissions for Device Software Functions, Issued June 2023
- Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions, Issued June 2025
The results of these tests indicate that the subject device is safe, effective, and substantially equivalent to the predicate device.
## CONCLUSION
The LiveMedica Enterprise PACS is concluded to be substantially equivalent to the predicate device based on the testing performed, similar indications for use with the same intended use, and similar technological characteristics. It can be concluded that the subject device does not raise new issues of safety or efficacy compared to the predicate device.
Page 7
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.