AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K203517 · Apr 16, 2021
Saige-Q
DeepHealth, Inc.
Retrospective clinical mammography records (FFDM and DBT); Pathology reports; Clinical interpretation records
Retrospective clinical data was used to evaluate the standalone performance (sensitivity, specificity, and AUC) of the Saige-Q AI algorithm compared to radiologist performance benchmarks.
Retrospective study; Multi-center; FFDM; DBT; AI algorithm validation
Clinical Evidence
Study Design
Population
Comparator
Key Endpoints
FFDM Retrospective Study; Retrospective, blinded, multi-center study
Screening mammography patients (excluding BI-RADS 0 cases); Sample Size: 1,333 exams (501 malignant, 832 normal); Number of Sites: 8
Not applicable for this study
Sensitivity, specificity, and AUC relative to BCSC benchmarks
DBT Retrospective Study; Retrospective, blinded, multi-center study
Screening mammography patients (excluding BI-RADS 0 cases); Sample Size: 1,528 exams (517 malignant, 1,011 normal); Number of Sites: 6
Not applicable for this study
Sensitivity, specificity, and AUC relative to BCSC benchmarks
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Breast cancer triage
Deep neural networks
Sensitivity and specificity 95% CI above 80% BCSC data
Sensitivity 92.2% (95% CI: 90.2%, 93.8%) at 86.9% specificity; Sensitivity 88.9% at 91.2% specificity (95% CI: 88.4%, 93.4%)
—
—
Retrospective, blinded, multi-center study: 501 malignant exams and 832 normal exams
>1 (expert radiologists) + >1 (adjudicator)
Breast cancer triage
Deep neural networks
Sensitivity and specificity 95% CI above 80% BCSC data
Sensitivity 98.3% (95% CI: 97.3%, 99.0%) at 86.9% specificity; Sensitivity 95.7% (95% CI: 93.6%, 97.2%) at 89.9% specificity
—
—
Retrospective, blinded, multi-center study: 517 malignant exams and 1011 normal exams
>1 (expert radiologists) + >1 (adjudicator)
Indications for Use
Saige-Q is a software workflow tool designed to aid radiologists in prioritizing exams within the standard-of-care image worklist for compatible full-field digital mammography (FFDM) and digital breast tomosynthesis (DBT) screening mammograms. Saige-Q uses an artificial intelligence algorithm to generate a code for a given mammogram, indicative of the software's suspicion that the mammogram contains at least one suspicious finding. Saige-Q makes the assigned codes available to a PACS/EPR/RIS/workstation for worklist prioritization or triage. Saige-Q is intended for passive notification only and does not provide any diagnostic information beyond triage and prioritization. Thus, it is not intended to replace the review of images or be used on a stand-alone basis for clinical decision-making. The decision to use Saige-Q codes and how to use those codes is ultimately up to the interpreting radiologist. The interpreting radiologist is responsible for reviewing each exam on a diagnostic viewer and evaluating each patient according to the current standard of care.
Device Story
Saige-Q is a software-only workflow tool for radiologists; processes FFDM and DBT screening mammograms. Input: DICOM files from screening studies. Operation: AI algorithm (deep neural networks) analyzes images to detect suspicious findings; assigns a 'Suspicious' or non-suspicious code. Output: Code sent to PACS/EPR/RIS worklist for triage/prioritization; generates non-diagnostic compressed preview image for suspicious cases. Used in clinical settings; operates in parallel with standard-of-care. Radiologists use output to reorder worklists; does not remove cases from queue. Benefits: Enables prioritized review of potentially malignant cases, improving workflow efficiency. Does not provide diagnostic information; radiologist remains responsible for final clinical evaluation.
Clinical Evidence
Two retrospective, blinded, multi-center studies (FFDM: 501 malignant, 832 normal; DBT: 517 malignant, 1011 normal). Primary endpoints: sensitivity and specificity relative to BCSC benchmarks. FFDM results: AUC 0.966; specificity 86.9% at 92.2% sensitivity; sensitivity 88.9% at 91.2% specificity. DBT results: AUC 0.985; specificity 86.9% at 98.3% sensitivity; sensitivity 89.9% at 95.7% specificity. Sub-analyses by lesion type, breast density, and age showed consistent performance. Secondary endpoint: processing times (median 15.5s FFDM, 196.8s DBT) met clinical expectations.
Technological Characteristics
Software-only device; runs on compatible host server. Inputs: DICOM FFDM/DBT images. Processing: Preprocessing followed by deep neural network AI analysis. Outputs: Triage code and preview image sent to PACS/RIS/EPR. Connectivity: Networked with clinical IT systems. Software level of concern: Moderate.
Indications for Use
Indicated for radiologists to prioritize screening mammography exams (FFDM and DBT) within a standard-of-care worklist by identifying exams suspicious for malignancy. Not for diagnostic use; not a replacement for clinical review.
Regulatory Classification
Identification
Radiological computer aided triage and notification software is an image processing prescription device intended to aid in prioritization and triage of radiological medical images. The device notifies a designated list of clinicians of the availability of time sensitive radiological medical images for review based on computer aided image analysis of those images performed by the device. The device does not mark, highlight, or direct users' attention to a specific location in the original image. The device does not remove cases from a reading queue. The device operates in parallel with the standard of care, which remains the default option for all cases.
Special Controls
Radiological computer aided triage and notification software must comply with the following special controls: 1. Design verification and validation must include: i. A detailed description of the notification and triage algorithms and all underlying image analysis algorithms including, but not limited to, a detailed description of the algorithm inputs and outputs, each major component or block, how the algorithm affects or relates to clinical practice or patient care, and any algorithm limitations. ii. A detailed description of pre-specified performance testing protocols and dataset(s) used to assess whether the device will provide effective triage (e.g., improved time to review of prioritized images for pre-specified clinicians). iii. Results from performance testing that demonstrate that the device will provide effective triage. The performance assessment must be based on an appropriate measure to estimate the clinical effectiveness. The test dataset must contain sufficient numbers of cases from important cohorts (e.g., subsets defined by clinically relevant confounders, effect modifiers, associated diseases, and subsets defined by image acquisition characteristics) such that the performance estimates and confidence intervals for these individual subsets can be characterized with the device for the intended use population and imaging equipment. iv. Standalone performance testing protocols and results of the device. v. Appropriate software documentation (e.g., device hazard analysis; software requirements specification document; software design specification document; traceability analysis; description of verification and validation activities including system level test protocol, pass/fail criteria, and results). 2. Labeling must include the following: i. A detailed description of the patient population for which the device is indicated for use. ii. A detailed description of the intended user and user training that addresses appropriate use protocols for the device. iii. Discussion of warnings, precautions, and limitations must include situations in which the device may fail or may not operate at its expected performance level (e.g., poor image quality for certain subpopulations), as applicable. iv. A detailed description of compatible imaging hardware, imaging protocols, and requirements for input images. v. Device operating instructions. vi. A detailed summary of the performance testing, including: test methods, dataset characteristics, triage effectiveness (e.g., improved time to review of prioritized images for pre-specified clinicians), diagnostic accuracy of algorithms informing triage decision, and results with associated statistical uncertainty (e.g., confidence intervals), including a summary of subanalyses on case distributions stratified by relevant confounders, such as lesion and organ characteristics, disease stages, and imaging equipment.
*Classification.* Class II (special controls). The special controls for this device are:(1) Design verification and validation must include:
(i) A detailed description of the notification and triage algorithms and all underlying image analysis algorithms including, but not limited to, a detailed description of the algorithm inputs and outputs, each major component or block, how the algorithm affects or relates to clinical practice or patient care, and any algorithm limitations.
(ii) A detailed description of pre-specified performance testing protocols and dataset(s) used to assess whether the device will provide effective triage (
*e.g.,* improved time to review of prioritized images for pre-specified clinicians).(iii) Results from performance testing that demonstrate that the device will provide effective triage. The performance assessment must be based on an appropriate measure to estimate the clinical effectiveness. The test dataset must contain sufficient numbers of cases from important cohorts (
*e.g.,* subsets defined by clinically relevant confounders, effect modifiers, associated diseases, and subsets defined by image acquisition characteristics) such that the performance estimates and confidence intervals for these individual subsets can be characterized with the device for the intended use population and imaging equipment.(iv) Stand-alone performance testing protocols and results of the device.
(v) Appropriate software documentation (
*e.g.,* device hazard analysis; software requirements specification document; software design specification document; traceability analysis; description of verification and validation activities including system level test protocol, pass/fail criteria, and results).(2) Labeling must include the following:
(i) A detailed description of the patient population for which the device is indicated for use;
(ii) A detailed description of the intended user and user training that addresses appropriate use protocols for the device;
(iii) Discussion of warnings, precautions, and limitations must include situations in which the device may fail or may not operate at its expected performance level (
*e.g.,* poor image quality for certain subpopulations), as applicable;(iv) A detailed description of compatible imaging hardware, imaging protocols, and requirements for input images;
(v) Device operating instructions; and
(vi) A detailed summary of the performance testing, including: test methods, dataset characteristics, triage effectiveness (
*e.g.,* improved time to review of prioritized images for pre-specified clinicians), diagnostic accuracy of algorithms informing triage decision, and results with associated statistical uncertainty (*e.g.,* confidence intervals), including a summary of subanalyses on case distributions stratified by relevant confounders, such as lesion and organ characteristics, disease stages, and imaging equipment.
{0}------------------------------------------------
April 16, 2021
Image /page/0/Picture/1 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
DeepHealth, Inc. A. Gregory Sorensen, M.D. President and CEO 1000 Massachusetts Ave CAMBRIDGE MA 02138
Re: K203517
Trade/Device Name: Saige-O Regulation Number: 21 CFR 892.2080 Regulation Name: Radiological Computer aided triage and notification software Regulatory Class: Class II Product Code: QFM Dated: March 19, 2021 Received: March 19, 2021
Dear Dr. Sorensen:
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. 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 located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmp/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.
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 and Part 809); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see
{1}------------------------------------------------
https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-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/medicaldevices/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-device-advice-comprehensive-regulatoryassistance/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,
For
Thalia T. Mills, Ph.D. Director Division of Radiological Health OHT7: Office of In Vitro Diagnostics and Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K203517
Device Name Saige-Q
### Indications for Use (Describe)
Saige-Q is a software workflow tool designed to aid radiologists in prioritizing exams within the standard-of-care image worklist for compatible full-field digital mammography (FFDM) and digital breast tomosynthesis (DBT) screening mammograms. Saige-Q uses an artificial intelligence algorithm to generate a code for a given mammogram, indicative of the software's suspicion that the mammogram contains at least one suspicious finding. Saige-Q makes the assigned codes available to a PACS/EPR/RIS/workstation for worklist prioritization or triage.
Saige-Q is intended for passive notification only and does not provide any diagnostic information beyond triage and prioritization. Thus, it is not intended to replace the review of images or be used on a stand-alone basis for clinical decision-making. The decision to use Saige-Q codes and how to use those codes is ultimately up to the interpreting radiologist. The interpreting radiologist is reviewing each exam on a diagnostic viewer and evaluating each patient according to the current standard of care.
| Type of Use (Select one or both, as applicable) |
|-------------------------------------------------------------------------------------------------------------------|
| <div> <span> <span style="font-size:16px">☒</span> Prescription Use (Part 21 CFR 801 Subpart D) </span> </div> |
| <div> <span> <span style="font-size:16px">☐</span> Over-The-Counter Use (21 CFR 801 Subpart C) </span> </div> |
# CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
### 510(k) SUMMARY
### DeepHealth's Saige-Q
### 501(k) Submission Number K203517
#### Submitter:
DeepHealth, Inc. 1000 Massachusetts Avenue Cambridge, MA 02138 Phone: 617-970-3817 Email: sorensen@deep.health
Contact Person: A. Gregory Sorensen Date Prepared: November 30, 2020
Name of Device: Saige-Q™ Common or Usual Name: Medical Imaging Software Classification Name: Radiological Computer-Assisted Triage and Notification Software Regulatory Class: Class II (21 CFR 892.2080) Product Code: QFM
Predicate Devices CureMetrix, Inc., cmTriage, K183285
#### Device Description
Saige-Q is a software workflow device that processes Digital Breast Tomosynthesis (DBT) and Full-Field Digital Mammography (FFDM) screening mammograms using artificial intelligence to act as a prioritization tool for interpreting radiologists. By automatically indicating whether a given mammogram is suspicious for malignancy. Saige-Q can help the user prioritize or triage cases in their worklist (or queue) that may benefit from prioritized review.
Saige-Q takes as input a set of x-ray mammogram DICOM files from a single screening mammography study (FFDM or DBT). The software first checks that the study is appropriate for Saige-Q analysis and then extracts, processes and analyses the DICOM images using an artificial intelligence alqorithm. As a result of the analysis, the software generates a Saige-Q code indicating the software's suspicion of the presence of findings suggestive of breast cancer. For mammograms given a Saige-Q code of "Suspicious," the software also generates a compressed preview image, which is for informational purposes only and is not intended for diagnostic use.
The Saige-Q code can be viewed by radiologists on a picture archiving and communication system (PACS), Electronic Patient Record (EPR), and/or Radiology Information System (RIS) worklist and can be used to reorder the worklist. As a software-only device, Saige-Q can be hosted on a compatible host server connected to the necessary clinical IT systems such that DICOM studies can be received and the resulting outputs returned where they can be incorporated into the radiology worklist.
The Saige-Q codes can be used for triage or prioritization. For example, "Suspicious" studies could be given prioritized review. With a worklist that supports sorting, batches of mammograms could also be sorted based on the Saige-Q code.
{4}------------------------------------------------
# Intended Use / Indications for Use
Saige-Q is a software workflow tool designed to aid radiologists in prioritizing exams within the standard-of-care image worklist for compatible full-field digital mammography (FFDM) and digital breast tomosynthesis (DBT) screening mammograms. Saige-Q uses an artificial intelligence algorithm to generate a code for a qiven mammogram, indicative of the software's suspicion that the mammogram contains at least one suspicious finding. Saige-Q makes the assigned codes available to a PACS/EPR/RIS/workstation for worklist prioritization or triage.
Saige-Q is intended for passive notification only and does not provide any diagnostic information beyond triage and prioritization. Thus, it is not intended to replace the review of images or be used on a stand-alone basis for clinical decision-making. The decision to use Saige-Q codes and how to use those codes is ultimately up to the interpreting radiologist. The interpreting radiologist is responsible for reviewing each exam on a diagnostic viewer and evaluating each patient according to the current standard of care.
### Summary of Technological Characteristics
Saige-Q is a software only device that consists of several core components that perform the following functions: 1) receive mammogram study data as DICOM files, 2) preprocess the DICOM files and check that the study is appropriate for analysis, 3) analyze the study images using an artificial intelligence algorithm, 4) generate outputs based on the analysis and 5) send the outputs to the appropriate clinical IT system for viewing on a radiology worklist.
The receiving and sending components are configured at the time of installation in conjunction with clinical IT staff. The software should be installed on a compatible host machine that is connected to the appropriate clinical IT systems (e.g., RIS, PACS and/or EPR) that enable the device to receive DICOM studies and return Saige-Q outputs.
The preprocessing component of the device performs two functions. The first function is to check that the study is appropriate for analysis. For example, if the study is not a mammogram, Saige-Q will not proceed with analysis. Saige-Q is compatible with FFDM and DBT mammogram studies acquired using Hologic mammography equipment. The second function is to preprocess the images to be analyzed. The preprocessed images become the input to the AI algorithm, which generates the Saige-Q code using deep neural networks that have been trained on large numbers of mammograms where cancer status is known.
The technical components described above are also found in the predicate device, though the exact implementation may vary. One difference relative to the predicate device is Saige-Q's ability to process DBT mammograms, which requires an additional Al model. A comprehensive comparison with the predicate device is provided in the following table:
| | Subject device | Predicate device | Summary | | Software | | |
|----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|--------------|----------|-----|------|
| | Saige-Q<br>DeepHealth Inc. | cmTriage<br>CureMetrix.<br>K183285 | | Product code | QFM | QFM | Same |
| Regulation<br>number | 21 CFR 892.2080 -<br>Radiological Computer-<br>Assisted Prioritization | 21 CFR 892.2080 -<br>Radiological Computer-<br>Assisted Prioritization Software | Same | Class | II | II | Same |
| Intended use | Saige-Q is a software<br>workflow tool designed to aid<br>radiologists in prioritizing<br>exams within the standard-of-<br>care image worklist for full-<br>field digital mammography<br>(FFDM) and digital breast<br>tomosynthesis (DBT)<br>screening mammograms.<br>Saige-Q uses an artificial<br>intelligence algorithm to<br>generate a code for a given<br>mammogram, indicative of<br>the software's suspicion that<br>the mammogram contains at<br>least one suspicious finding.<br>Saige-Q makes the assigned<br>codes available to a<br>PACS/EPR/RIS/workstation<br>for worklist prioritization or<br>triage.<br>Saige-Q is intended for<br>passive notification only and<br>does not provide any<br>diagnostic information<br>beyond triage and<br>prioritization. Thus, it is not<br>intended to replace the review<br>of images or be used on a<br>stand-alone basis for clinical<br>decision-making. The<br>decision to use Saige-Q codes<br>and how to use those codes is<br>ultimately up to the<br>interpreting radiologist. The<br>interpreting radiologist is<br>responsible for reviewing<br>each exam on a diagnostic<br>viewer and evaluating each<br>patient according to the<br>current standard of care. | cmTriage is a passive<br>prioritization-only, parallel-<br>workflow software tool used by<br>radiologists to prioritize specific<br>patients within the standard-of-<br>care image worklist for 2D<br>FFDM screening mammograms.<br>cmTriage uses an artificial<br>intelligence algorithm to<br>analyze 2D FFDM screening<br>mammograms and flags those<br>that are suggestive of the<br>presence of at least one<br>suspicious finding at the exam<br>level. These flags are viewed by<br>the radiologist via their PACS<br>worklist. The decision to use<br>cmTriage codes and how to use<br>cmTriage codes is ultimately up<br>to the radiologist. cmTriage<br>does not send a proactive alert<br>directly to the radiologist.<br>Radiologists are responsible for<br>reviewing each exam on a<br>diagnostic viewer according to<br>the current standard of care.<br>cmTriage is limited to the<br>categorization of exams, does<br>not provide any diagnostic<br>information beyond triage and<br>prioritization, does not remove<br>images from the radiologist's<br>worklist, and should not be used<br>in lieu of full patient evaluation,<br>or relied upon to make or<br>confirm diagnosis.<br>cmTriage is for prescription use<br>only. | Both devices have the<br>same intended use<br>per 21 CFR 892.2080 | | | | |
| Technical<br>Method | The device provides triage or<br>notification that is informed<br>by artificial intelligence<br>algorithms. | The device provides triage or<br>notification that is informed by<br>artificial intelligence<br>algorithms. | Same | | | | |
{5}------------------------------------------------
{6}------------------------------------------------
| Anatomical Site | Breast | Breast | Same |
|--------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Clinical<br>condition | Breast cancer | Breast cancer | Same |
| Notification-<br>only, parallel<br>workflow tool | Yes | Yes | Same |
| Alert to finding | Passive notification flagged<br>for review | Passive notification flagged for<br>review | Same |
| Preview Image | Preview of the<br>study for initial assessment,<br>not meant for diagnostic<br>purposes.<br>The device operates in<br>parallel with the standard of<br>care, which remains the<br>default option for all cases. | Preview of the study for initial<br>assessment, not meant for<br>diagnostic purposes.<br>The device operates in parallel<br>with the standard of care, which<br>remains the default option for<br>all cases. | Same |
| Multiple<br>operating<br>points | Yes; 3 operating points | Yes; a continuous range of<br>operating points. | Similar but Saige-Q<br>uses a more<br>conservative<br>approach by pre-<br>specifying a discrete<br>number of operating<br>points. |
| Independent of<br>standard of care<br>workflow | Yes; no cases are removed<br>from worklist | Yes; no cases are removed from<br>worklist | Same |
| End users | Radiologists | Radiologists | Same |
| Type of<br>mammograms | FFDM and DBT screening<br>mammograms. | FFDM screening mammograms. | Both devices operate<br>on screening<br>mammograms (x-ray<br>images), but<br>cmTriage is intended<br>for FFDM cases only<br>whereas Saige-Q is<br>intended for both<br>FFDM and DBT<br>cases. |
| Deployment | On-premise | On-premise with cloud<br>processing | Different, but does<br>not raise any new<br>questions regarding<br>safety and<br>effectiveness. |
| Output device | The end user interacts with | The end user interacts with the | There is no |
| | the output of the device in the<br>facility's PACS/EPR/RIS<br>software (worklist). | output of the device in the<br>facility's PACS software<br>(worklist). | significant difference. |
| Software levels<br>of concern | Moderate | Moderate | Same |
{7}------------------------------------------------
# Performance Data
DeepHealth conducted two retrospective, blinded, multi-center studies to evaluate the standalone performance of Saige-Q, one study using FFDM and a separate study using DBT mammograms. The primary objective was the same for each study: to assess the sensitivity and specificity of Saige-Q relative to radiologist performance, as estimated by BCSC. The secondary objective was to assess the processing time performance when executing Saige-Q software on FFDM and separately on DBT mammograms to ensure processing times are within clinically acceptable ranges.
Data for the FFDM study was collected from eight clinical sites across two states in the United States with 501 malignant exams and 832 normal exams. Data for the DBT study was collected from six clinical sites across two states in the United States, with 517 malignant exams and 1011 normal exams. The test dataset excludes screening BI-RADS 0 cases that were determined to be benign after diagnostic workup. DeepHealth had never collected data from the clinical sites previous to this study either for training or testing. Malignant exams were confirmed using pathology reports from biopsied lesions and normal cases were confirmed with a negative clinical interpretation (BIRADS 1 or 2) followed by another negative clinical interpretation at least two years later. Each case was reviewed by two independent expert radiologists (and an adjudicator if discordance was observed) to establish the reference standard for each case.
In the FFDM study, Saige-Q achieved an overall area under the receiver operating characteristic curve (AUC) of 0.966 (95% C1: [0.957, 0.975]). In the DBT study, Saige-Q achieved an overall AUC of 0.985 (95% Cl: [0.979, 0.990]) on the DBT data. This performance meets or exceeds the performance of the predicate device and exceeds the requirement specified for the QFM product code for effective triage with an AUC >0.95.
The primary endpoints of the studies consisted of sensitivity and specificity targets to validate that Saige-Q operates with a 95% CI for both sensitivity and specificity above the 80% CI reported in BCSC data.
The primary endpoint for FFDM was successfully met with Saige-Q demonstrating a specificity at 86.9% sensitivity of 92.2% (95% Cl: 190.2%, 93.8%)) and a sensitivity at 88.9% specificity of 91.2% (95%: [88.4%, 93.4%]).
The primary endpoint for DBT was also successfully met with Saige-Q demonstrating a specificity at 86.9% sensitivity: 98.3% (95% Cl: [97.3%, 99.0%]) and a sensitivity at 89.9% specificity of 95.7% (95% CI: [93.6%, 97.2%]).
A sub-analysis of performance by lesion type (soft tissue densities vs. calcifications), breast density (dense vs. non-dense), age, and lesion size showed similar performance across subcategories. For instance, on FFDM, Saige-Q achieved an AUC of 0.964 (95% Cl: [0.954,
{8}------------------------------------------------
0.974)) on soft tissue densities and an AUC of 0.973 (95% Cl: [0.958, 0.988]) on calcifications. For DBT, Saige-Q achieved an AUC of 0.983 (95% Cl: [0.977, 0.990]) on soft tissue densities and an AUC of 0.989 (95% Cl: [0.983, 0.996]) on calcifications. For breast density, Saige-Q achieved an AUC of 0.959 (95% Cl: [0.945, 0.973]) on dense breasts and an AUC of 0.972 (95% Cl: [0.961, 0.984]) on non-dense breasts for FFDM exams. For DBT, Saige-Q achieved an AUC of 0.980 (95% Cl: [0.971, 0.988]) on dense breasts and an AUC of 0.988 (95% Cl: [0.981, 0.996]) on non-dense breasts.
The secondary endpoints required the processing time for each FFDM and DBT mammogram to be within clinical operational expectations of breast cancer screening. The median processing time for FFDM was 15.5 seconds and was 196.8 seconds for DBT. These processing times are within the clinical expectations for screening mammograms.
Based on the clinical performance as documented in the pivotal clinical study, Saige-Q has a safety and effectiveness profile that is similar to the predicate device.
# Conclusions
Saige-Q is as safe and effective as cmTriage. Saige-Q has the same intended uses and similar indications, technological characteristics, and principles of operation as its predicate device. The minor differences in indications do not alter the intended use of the device and do not affect its safety and effectiveness when used as labeled. In addition, the minor technological differences between Saige-Q and its predicate device raise no new issues of safety or effectiveness. Performance data demonstrate that Saige-Q is as safe and effective as cmTriage. Thus, Saige-Q is substantially equivalent to the legally marketed predicate device.
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.