Syneris PACS is a software device intended to be used by healthcare personnel and intended for viewing, reviewing, performing measurements/quantifications and reporting of medical images and data acquired from DICOM compliant medical imaging systems. Images and data can be stored, communicated, processed and displayed within the system or across computer networks at distributed locations. Lossy images and digitized film images must not be used for primary diagnosis or interpretation.
Device Story
Syneris PACS is a software-as-a-medical-device (SaMD) for radiologists and clinicians to manage, view, and analyze medical images. Input: DICOM-compliant images from imaging modalities (e.g., CT, PET, ultrasound). Operation: System receives, organizes, and displays images via a desktop Viewer application; supports multi-monitor workspaces and hanging protocols. Features: 2D/3D visualization (MPR, MIP, volume rendering), PET-CT fusion display, and manual measurement tools (orthopedic indices, cardiac Doppler parameters). Output: Visualized images, annotations, and PDF reports. Context: Used in clinical environments; operates via cloud/server-hosted infrastructure. Healthcare providers use the output for clinical review and decision-making. Benefits: Streamlined image access, standardized measurement calculations, and efficient reporting across distributed clinical networks.
Clinical Evidence
No clinical data. Bench testing only. Software verification and validation testing conducted per FDA guidance confirmed that design requirements were met and the intended use was validated.
Technological Characteristics
Software-only PACS; Windows 10/11 compatible. Architecture: Workstation viewer and cloud/server-hosted backend. Connectivity: HTTPS, DICOM-compliant. Visualization: 2D, MPR, MIP, volume rendering, PET-CT fusion. Measurement: Manual landmark-based tools for orthopedic/cardiac parameters. Reporting: PDF. No automated image segmentation or AI/ML algorithms.
Indications for Use
Indicated for healthcare personnel to view, review, measure, quantify, and report medical images/data from DICOM-compliant systems. Applicable to all age groups: neonates, infants, children, adolescents, and adults. Contraindicated for primary diagnosis or interpretation using lossy or digitized film 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
Syneris
Lily Timonina
Regulatory Affairs Manager
1600 Steeles Ave. W., Suite 214
Concord, ON L4K 4M2
Canada
September 23, 2026
Re: K261874
Trade/Device Name: Syneris PACS v.1.0.1.0
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: LLZ
Dated: September 2, 2026
Received: September 3, 2026
Dear Lily Timonina:
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
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K261874 - Lily Timonina
Page 2
Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
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 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (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 ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
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}
K261874 - Lily Timonina
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. | | K261874 | ? |
| --- | --- | --- | --- |
| Please provide the device trade name(s). | | | ? |
| Syneris PACS v.1.0.1.0 | | | |
| Please provide your Indications for Use below. | | | ? |
| Syneris PACS is a software device intended to be used by healthcare personnel and intended for viewing, reviewing, performing measurements/quantifications and reporting of medical images and data acquired from DICOM compliant medical imaging systems. Images and data can be stored, communicated, processed and displayed within the system or across computer networks at distributed locations. Lossy images and digitized film images must not be used for primary diagnosis or interpretation. | | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | | ? |
| Please select the age group(s) for which the device(s) is to be used. | ☑ Neonates/Newborns (Birth to < 29 days old) ☑ Infants (29 days old to < 2 years old) ☑ Children (2 years old to < 12 years old) ☑ Adolescents (12 years old to < 22 years old) ☑ Adults (22 years old and greater) | | ? |
{4}
K261874
# 510(k) summary
1. Submitter
| Name | Syneris |
| --- | --- |
| Address | 1600 Steeles Avenue West, Suite 214, Concord, Ontario, L4K 4M2, Canada |
| Phone | (416) 699 4125 |
| Email | lily.timonina@synerishealth.com |
| Contacts | Lily Timonina, Regulatory Affairs |
| Date Prepared | 2026-08-20 |
2. Subject Device
| Trade Name | Syneris PACS v.1.0.1.0 |
| --- | --- |
| K Number | K261874 |
| Common Name | Picture Archiving Communications System |
| Regulation Number | 21 CFR 892.2050 |
| Regulatory Class | II |
| Product Code | LLZ |
| Review Panel | Radiology |
3. Predicate Device
| Trade Name | ONIS-PACS System |
| --- | --- |
| K Number | K181318 |
| Common Name | Picture Archiving Communications System |
| Regulation Number | 21 CFR 892.2050 |
| Regulatory Class | II |
1
{5}
| Product Code | LLZ |
| --- | --- |
| Review Panel | Radiology |
#### 4. Device Description
Syneris is a software-as-medical-device Picture Archiving and Communication System (PACS) designed for radiologists to view, interpret, and manage medical imaging studies. The system operates in compliance with DICOM standards for medical imaging and uses HTTPS for secure communication between its components.
The Syneris PACS receives, organizes, and displays patient images for diagnostic review. It includes structured viewing, measurement, annotation, and reporting features tailored to different specialties, such as orthopedics, cardiology, and nuclear medicine. It supports a wide range of DICOM modalities and enables work across multiple monitors using a workspace organized via Hanging Protocols.
The system includes logging and encryption modules and interacts with external systems such as RIS and imaging modalities.
#### 5. Indications For Use
Syneris PACS is a software device intended to be used by healthcare personnel and intended for viewing, reviewing, performing measurements/quantifications and reporting of medical images and data acquired from DICOM compliant medical imaging systems. Images and data can be stored, communicated, processed and displayed within the system or across computer networks at distributed locations. Lossy images and digitized film images must not be used for primary diagnosis or interpretation.
#### 6. Comparison Of Technological Characteristics With The Predicate Device
Both the subject (Syneris PACS) and predicate (ONIS-PACS) devices are Picture Archiving Communications Systems, which are indicated for medical image management, review, and data distribution. Both systems have been developed to replace traditional film handling in radiology.
Syneris PACS is substantially equivalent to the identified predicate device ONIS-PACS (K181318) in the following areas:
- Both devices fall under the 892.2050 regulation classification.
- Both devices fall under the LLZ product code for Automated Radiological Image Processing Software.
- Both devices have similar indications for use, as described in the Substantial Equivalence Comparison Table below.
2
{6}
- Both devices have similar technological characteristics, as described in the Substantial Equivalence Comparison Table below.
| Functionality | Subject Device | Predicate Device | Justification for Differences |
| --- | --- | --- | --- |
| Trade Name | Syneris PACS | ONIS-PACS | N/A |
| Manufacturer | 1000935486 ONTARIO INC. | DigitalCore Co., Ltd | N/A |
| 510(k) Number | K261874 | K181318 | N/A |
| Classification | Device Class:II Product Code: LLZ 21 CFR 892.2050 | Device Class:II Product Code: LLZ 21 CFR 892.2050 | Equivalent |
| Indications for Use | Syneris PACS is a software device intended to be used by healthcare personnel and intended for viewing, reviewing, performing measurements/quantifications and reporting of medical images and data acquired from DICOM compliant medical imaging systems. Images and data can be stored, communicated, processed and displayed within the system or across computer networks at distributed locations. Lossy images and digitized film images must not be used for primary diagnosis or interpretation. | ONIS-PACS is a software device intended to be used by healthcare personnel and intended for viewing, reviewing, performing measurements/quantifications and reporting of medical images and data acquired from DICOM compliant medical imaging systems. Images and data can be stored, communicated, processed and displayed within the system or across computer networks at distributed locations. Lossy images and digitized film images must not be used for primary diagnosis or interpretation. | Equivalent, both devices are software only devices intended to allow clinicians to view and process DICOM images, and communicate results over a network. Both devices provide support for mammographic images, and both devices contraindicate that lossy images should not be used for primary diagnosis nor interpretation. |
| Device Description and Key Components | Syneris PACS software is a Picture Archiving Communication System suitable for storing, distributing, visualizing, and manipulating DICOM images. | ONIS-PACS is a Picture Archiving Communication System (PACS) fully compliant with the DICOM version 3.0 Standard. It is suitable for storing, distributing, retrieving, | Comparable components: - desktop viewer application (Viewer and ONIS Viewer) - DICOM retrieval application |
3
{7}
| | Syneris System is comprised of the following interrelated software components: Viewer is a desktop application that provides navigation and visualization of multimodality and multidimensional images and acts as a DICOM viewer capable of connecting to a DICOM network. Viewer Provider component is responsible for fetching medical images from the storage system or DICOM server and delivering them to the Viewer. DICOM Server manages the storage and exchange of medical images and related information using the DICOM standard. Worklist Assistant provides multi-clinic worklist navigation and credential management, launching selected studies into the Viewer. Cloud Infrastructure provides scalable, off-site storage and management of medical images and data, accessible via the internet. | visualizing, manipulating, performing measurements/quantifications and reporting various DICOM objects. ONIS Viewer is a desktop application that makes it possible to visualize, manipulate and process medical images of many different modalities. ONIS Remote is a desktop application identical to the ONIS Viewer, except that it runs without the Local Server. WebONIS is an ActiveX component loaded into an HTML page that provides the same functionality as the ONIS Remote application. ONIS Site Server is a server application that supports the storage and retrieval of a wide range of DICOM Storage objects. ONIS Organization Server is a server that provides a single access point to multiple Site Servers. | (Provider and Local Server) - local DICOM server (DICOM Server and ONIS Site Server) Both devices include server-side distributed-access components. The specific implementation differs: ONIS-PACS uses Site Server and Organization Server components, while Syneris PACS uses cloud/server-hosted infrastructure, Viewer Provider, DICOM Server, databases, and storage components. While there is no direct equivalent of the ONIS Remote application, the Syneris Viewer provides comparable remote/distributed viewing functionality through connection to the Syneris backend/cloud infrastructure. There is no direct equivalent of a browser-based WebONIS component. This represents a difference in access method and a subset of the predicate's access modes. The absence of a browser-based viewer |
| --- | --- | --- | --- |
4
{8}
| | | | does not raise different questions of safety or effectiveness because diagnostic image review is performed through the validated Syneris desktop Viewer. |
| --- | --- | --- | --- |
| Device Property | SaMD | SaMD | Equivalent |
| Intended User | Physicians or other licensed practitioners in healthcare institutions | Physicians or other licensed practitioners in healthcare institutions | Equivalent |
| Prescription / OTC Use | Prescription Use | Prescription Use | Equivalent |
| **Technological Characteristics** | | | |
| System Architecture | Software-only device comprising workstation software and server-side software | Software-only device comprising workstation, web, and server software | Comparable. Both devices are software-only PACS systems with viewer/workstation and server-side components for DICOM image storage, retrieval, communication, display, manipulation, measurement/annotation, and reporting. Syneris uses a cloud/server-hosted architecture and does not include a browser-based ActiveX WebONIS component. This is an implementation difference and does not introduce a new clinical function or different question of safety or effectiveness. |
| Operating System | Windows 10, 11 | Windows 7, 8, 10 Microsoft Windows 2008 Server Standard Microsoft Windows | Equivalent |
5
{9}
| | | 2012 Server Standard | |
| --- | --- | --- | --- |
| Functions and Capabilities | | | |
| Data Access and Communication with Connected Systems | Yes. Syneris PACS supports system-managed exchange of images, reports, patient/encounter data, and related clinical information with configured connected systems, including DICOM-compliant imaging devices and site-configured RIS/CIS/EMR systems, as applicable. These exchanges are performed through configured Syneris interfaces and workflow, not through direct user-controlled local file upload/download from within the Viewer. | Yes. ONIS-PACS supports DICOM-based data access and communication with connected systems, including DICOM servers, PACS workstations, ONIS Site Server, and ONIS Organization Server. | Comparable for networked PACS data communication. Both devices support exchange of medical images and related data across connected clinical/networked systems, although the specific implementation differs. Syneris uses configured server/cloud and clinical-system interfaces, while ONIS includes direct DICOM/server, local media, and direct user-controlled import/export functions. These differences do not raise different questions of safety or effectiveness because both devices support the intended PACS workflow of making medical images and related data available for clinical review, measurement/annotation, and reporting. |
| Data Output | Syneris PACS supports system-managed output and distribution of images, reports, patient/encounter data, and related clinical information through configured connected-system interfaces. Syneris PACS does not provide direct in-Viewer local | ONIS-PACS supports export of images to various image formats, local filesystem/media export, PACS transfer, and printing functions as described in the predicate documentation. | Comparable for the intended PACS communication workflow, with differences in implementation. Syneris uses configured system interfaces for clinical data output and distribution, while ONIS also provides |
6
{10}
| | image/report export and does not support DICOM Print Management. | | direct user-controlled local/media export and printing functions. The absence of direct in-Viewer local export and DICOM Print Management does not raise different questions of safety or effectiveness because these functions are not required for Syneris PACS's intended use. |
| --- | --- | --- | --- |
| DICOM Storage and Modality Worklist Communication | Supports DICOM Storage and Modality Worklist-related communication as described in the DICOM Conformance Statement. Syneris PACS does not support DICOM Query/Retrieve services, including Query/Retrieve C-FIND, C-MOVE, or C-GET, and does not support DICOM Print Management. | Supports DICOM communication functions, including DICOM storage/retrieval functions, as described in the predicate device documentation. | Comparable. Syneris PACS supports the DICOM services required for image receipt, worklist-related communication, storage, display, measurement, annotation, reporting, and distribution through its validated system architecture. The absence of DICOM Query/Retrieve and DICOM Print Management does not raise different questions of safety or effectiveness because those services are not required for the subject device's intended use and workflow. |
| Hanging Protocols | Yes | Yes | Equivalent |
| Image Visualization | Supports 2D, Mammography, Multi Planar Reconstruction (Axial, Sagittal, Coronal), Maximum Intensity Projection, and volume rendering through 3D cursor | Supports 2D, Mammography, Multi Planar Reconstruction (Axial, Sagittal, Coronal), Maximum Intensity Projection, and Volume Rendered views | Equivalent, both devices provide standard rendering tools |
7
{11}
| Image Manipulation Tools | Supports W/L, zoom, pan, stack, 1:1 scale, rotate, flip, invert, brightness/contrast, magnifying glass | Supports W/L, zoom, pan, stack, move, rotate, flip, color LUT, opacity table, image filters | Equivalent, both devices provide standard image manipulation tools |
| --- | --- | --- | --- |
| Measurement Tools | Supports distance and angle measurements, path length measurements, and regions of interest measurements | Supports distance and angle measurements, and pixel statistics for user-drawn regions of interest | Equivalent, both devices provide standard measurement tools |
| Orthopaedic measurement tools | Cobb angle, acetabular index, Sharp angle, centre-edge angle, Reimer index. | Named indices not provided. Provides angle between segments, ratio between segments, parallel and orthogonal segment construction, and segment calibration. | Comparable. The predicate provides every primitive from which these indices are derived — the angle between two user-placed segments, the ratio between two user-placed segments, and orthogonal construction — but not the named indices, which the user would identify and calculate from the same measurements. The subject device applies the published formula to the same user-placed geometry, reducing calculation and transcription error. No automated analysis or interpretation is introduced and the intended use is unchanged. |
| Cardiac measurement tools | Doppler velocity, Doppler time, Doppler trace, Doppler deceleration, cardiac area and volume | Not provided. | Difference. These measurements are routinely performed on the acquiring ultrasound system at the time of acquisition. The subject device reproduces them from the same image |
8
{12}
| | | | data, using calipers or a contour placed by the user and scaled by the DICOM region calibration data supplied by the acquiring system. No automated analysis or interpretation is introduced, and the intended use is unchanged, so this difference does not raise different questions of safety or effectiveness. |
| --- | --- | --- | --- |
| PET-CT display | Fusion display with adjustable fusion ratio, colour scheme, gamma and fusion/maximum levels. Does not compute SUV or any quantitative uptake metric. | Displays PET images. | Different. Fusion display is a presentation function: it superimposes two registered series for simultaneous review and does not derive, quantify or interpret radiotracer uptake, nor does it alter the diagnostic information present in either series. The difference does not raise different questions of safety or effectiveness. |
| Annotation Tools | Supports text, arrow, angle, line, ellipse | Supports text, arrow, angle, line and other user drawn region of interest shapes | Equivalent, both devices provide standard annotation tools |
| Reporting | Yes (PDF format) | Yes (HTML format) | Equivalent |
| JPEG lossless/lossy compression | Yes | Yes | Equivalent |
| Multi-monitor awareness | Yes | Yes | Equivalent |
| Image layout | Yes | Yes | Equivalent |
9
{13}
Fundamentally, Syneris PACS is the same as the referenced predicate device in that it is a radiology image management system. As detailed above in the comparison table, most of their specifications and features are also the same and comparable. Syneris PACS and ONIS-PACS share a high degree of functional and technological overlap. Both serve the same clinical role within radiology workflows — managing, viewing, and measuring diagnostic images across a connected healthcare enterprise. Both devices are intended to be used by physicians or other licensed practitioners in healthcare institutions.
Syneris PACS also has some differences in technological characteristics when compared to its predicate device. The main differences are listed below:
- • **Cloud/server-hosted architecture.** Syneris uses a cloud/server-hosted implementation, while ONIS-PACS uses Site Server and Organization Server components. This is an implementation difference in the storage, retrieval, and distribution architecture.
- • **Browser-based viewing component.** ONIS-PACS includes WebONIS, an ActiveX component loaded into an HTML page and used with Microsoft Internet Explorer to provide functionality similar to ONIS Remote. Syneris PACS does not currently offer a WebONIS-equivalent browser-based component. Thus, the subject device uses a different access method and has a subset of the predicate's access modes. This difference does not raise different questions of safety or effectiveness.
- • **Different remote-access implementation.** Both devices support distributed access to medical images, but the subject device implements this through the desktop Viewer and backend/server infrastructure rather than through a separate ONIS Remote component
- • **Differences in direct import/export and DICOM services.** ONIS-PACS supports direct local/media import/export, DICOM Query/Retrieve, and DICOM Print Management. Syneris PACS does not support these functions and instead uses configured system-managed exchange through connected-system interfaces.
- • **Named measurement presets.** Syneris PACS provides named orthopaedic and cardiac measurement presets that the predicate does not: Cobb angle, acetabular index, Sharp angle, centre-edge angle, Reimer index, Doppler velocity, Doppler time, Doppler trace, Doppler deceleration, and cardiac area and volume. Each preset applies an established published formula to landmarks placed manually by the user. The predicate provides the underlying angle, ratio and orthogonal constructions from which the orthopaedic indices are derived; the cardiac measurements are routinely performed on the acquiring ultrasound system at the time of acquisition. No image segmentation, landmark detection, automated analysis or interpretation is introduced, and the intended use is unchanged.
- • **PET-CT fusion display.** Syneris PACS provides fusion display controls for PET-CT studies, comprising superimposition of the CT series over the PET series with adjustable fusion ratio, colour scheme, gamma, and fusion and
10
{14}
maximum levels. Fusion display is a presentation function that does not derive, quantify or interpret radiotracer uptake; neither device computes SUV or any other quantitative uptake metric.
## **7. Software Validation and Verification Testing**
Software verification and validation testing were conducted, and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Device Software Functions".
The software verification and validation testing verified that the design requirements were successfully met. The Intended Use was successfully validated.
As the intended use, functionality, and performance of Syneris PACS and the predicate device are equivalent, the result of the performance testing is evidence that Syneris PACS performs in an equivalent manner to the ONIS-PACS.
## **8. Conclusion**
The subject device and the predicate device are substantially equivalent in the areas of general function, application, and intended use. Any differences between the subject device and the predicate device do not impact safety or effectiveness and do not raise new questions of safety or effectiveness. Syneris is equivalent in performance to existing legally marketed devices
11
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:
Guidance alerts
New and changed FDA guidance documents, emailed as a daily digest.
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 ? 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 as a Medical Device, 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 as a Medical Device), 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.