Authorized purpose: Saige-Dx analyzes screening DBT stacks and associated full-field digital or synthetic 2D mammograms, assigning finding and case suspicion levels to support qualified interpreting physicians; it does not replace their review or clinical judgment.
Clinical role
Detection, localization, or diagnostic support
Images and patients
Mammography/DBT · Breast
Key limitation
Keep in mind: Outputs are adjunctive and must not be the sole basis for patient-management decisions; the device does not replace review of the complete mammography examination.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: Saige-Dx analyzes screening DBT stacks and associated full-field digital or synthetic 2D mammograms, assigning finding and case suspicion levels to support qualified interpreting physicians; it does not replace their review or clinical judgment.
Which images or clinical context are in scope?Modality: Mammography/DBT Anatomy or clinical context: Breast Input: DBT screening mammogram stacks and associated 2D FFDM and/or synthetic images from compatible Hologic SD/HD and GE DBT hardware.
Who uses it?Intended users: Physicians qualified to interpret screening mammography examinations.
What does the software produce?Output: Finding bounding boxes and finding/case suspicion levels, packaged in DICOM Structured Report and Secondary Capture summary objects and routed to PACS or another worklist.
What is its most important limitation?Key limitation: Outputs are adjunctive and must not be the sole basis for patient-management decisions; the device does not replace review of the complete mammography examination.
Clinical takeaway. Clinical role: Saige-Dx analyzes screening DBT stacks and associated full-field digital or synthetic 2D mammograms, assigning finding and case suspicion levels to support qualified interpreting physicians; it does not replace their review or clinical judgment.
Evidence takeaway. Evidence from the reviewed source record: A retrospective blinded multicenter standalone assessment used 2,002 unique women from 12 U.S. sites (259 cancer and 1,743 noncancer cases); the primary noninferiority comparison with the predicate met its acceptance criterion.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
Saige-Dx analyzes screening DBT stacks and associated full-field digital or synthetic 2D mammograms, assigning finding and case suspicion levels to support qualified interpreting physicians; it does not replace their review or clinical judgment.
Finding bounding boxes and finding/case suspicion levels, packaged in DICOM Structured Report and Secondary Capture summary objects and routed to PACS or another worklist.
Outputs are adjunctive and must not be the sole basis for patient-management decisions; the device does not replace review of the complete mammography examination.
A retrospective blinded multicenter standalone assessment used 2,002 unique women from 12 U.S. sites (259 cancer and 1,743 noncancer cases); the primary noninferiority comparison with the predicate met its acceptance criterion.
Exact FDA submission
Checked 2026-09-05
No release-specific sensitivity or specificity was abstracted from the reviewed FDA text.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
A retrospective blinded multicenter standalone assessment used 2,002 unique women from 12 U.S. sites (259 cancer and 1,743 noncancer cases); the primary noninferiority comparison with the predicate met its acceptance criterion.
FDA source
Exact FDA submission
Checked 2026-09-05
No release-specific sensitivity or specificity was abstracted from the reviewed FDA text.
A numerical sensitivity with complete endpoint context was not established in the reviewed material.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-05
A numerical specificity with complete endpoint context was not established in the reviewed material.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
1 unlinked candidate evidence record is retained for source review and excluded from this evidence display.
Safety and lifecycle
Postmarket record
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: DBT screening mammogram stacks and associated 2D FFDM and/or synthetic images from compatible Hologic SD/HD and GE DBT hardware.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA workflow routes DICOM input from a facility to the software and DICOM results back to PACS or another worklist.
Scope: Exact FDA submission. Site-specific interfaces and compatibility require vendor confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The reviewed labeling describes data routing but does not establish a current hosting model.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-05 ·
Returned objects
Source context, not route validation: Finding bounding boxes and finding/case suspicion levels, packaged in DICOM Structured Report and Secondary Capture summary objects and routed to PACS or another worklist.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Finding bounding boxes and finding/case suspicion levels, packaged in DICOM Structured Report and Secondary Capture summary objects and routed to PACS or another worklist.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-05Last searched
24Fields reviewed
11Source classes checked
1Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
Stored PubMed metadata was screened. PMID 40983310 is a Saige-Dx family microsimulation model and is retained as contextual evidence only; it is not product pricing or real-world performance. No stored trial candidates. The current discovery snapshot contains 1 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, acr ai central product, fda decision material, vendor product page, literature index, trial registry, fda device recall, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not verified - checked 2026-09-06 - Exact FDA submission
No scoped public price or procurement award was reviewed; commercial terms require quotation.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Reimbursement: Not publicly available - checked 2026-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "DeepHealth Saige-Dx reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. This records what was found, not that none exists; eligibility depends on payer, site of service and use case.
Deployment: Not verified - checked 2026-09-05 - Exact FDA submission
The reviewed labeling describes data routing but does not establish a current hosting model.
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Security: Not verified - checked 2026-09-06 - Exact FDA submission
No dated, scoped security attestation was reviewed.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-06 - Exact FDA submission
Current training and support commitments were not established.
Monitoring: Not verified - checked 2026-10-27 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Flags calcifications, masses, asymmetries and architectural distortions on compatible FFDM or DBT screening examinations; management must not be based solely on MammoScreen output.
Authorized purpose: Tags screening cases as suspicious or blank to aid worklist prioritization; radiologists must review every examination and it does not mark original images.
Authorized purpose: Lunit INSIGHT MMG v1.1.10 aids physicians in detection, localization and characterization of suspicious breast-cancer areas on female screening mammograms from compatible FFDM systems, viewed after the physician's initial read as an adjunct to complete clinical interpretation.
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.