Authorized purpose: Adjunctive estimation of the BI-RADS 5th Edition breast-density category from processed digital 2D mammograms to aid radiologists; not diagnostic.
Clinical role
Automated post-processing breast-density assessment and quantitative-reporting support with physician review.
Images and patients
Mammography/DBT · Breast
Key limitation
Keep in mind: The output is adjunctive and not a diagnostic aid; an MQSA-qualified physician makes the final category. The labeled compatibility is limited to the identified FFDM systems and view configurations. Core software was built and tested on OS X, the GUI on Windows/OS X/Linux, the user computer must share a local network with the server, and a web browser is required.
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: Adjunctive estimation of the BI-RADS 5th Edition breast-density category from processed digital 2D mammograms to aid radiologists; not diagnostic.
Which images or clinical context are in scope?Modality: Mammography/DBT Anatomy or clinical context: Breast Input: Processed digital 2D mammograms from FFDM systems, with images extracted from DICOM files; the packet identifies GE Senographe Essentials and Hologic Selenia Dimension systems and supports CC/MLO pairs or specified single-view inputs.
Who uses it?Intended users: Radiologists; the final breast-density assessment is made by an MQSA-qualified interpreting physician
What does the software produce?Output: A BI-RADS breast-density 5th Edition category is produced for each breast and for each patient, with the patient result based on the maximum category of the two breasts; the browser interface can display the assessment and similar images.
What is its most important limitation?Key limitation: The output is adjunctive and not a diagnostic aid; an MQSA-qualified physician makes the final category. The labeled compatibility is limited to the identified FFDM systems and view configurations. Core software was built and tested on OS X, the GUI on Windows/OS X/Linux, the user computer must share a local network with the server, and a web browser is required.
Clinical takeaway. Clinical role: Adjunctive estimation of the BI-RADS 5th Edition breast-density category from processed digital 2D mammograms to aid radiologists; not diagnostic.
Evidence takeaway. Evidence from the reviewed source record: FDA verification and validation covered reproducibility, comparison of left/right and patient-level density results with visual assessments by MQSA-qualified radiologists, GE and Hologic datasets, two-view and single-view configurations, and beta-site testing for physician integration and usability. The packet states that all test acceptance criteria were met; it does not report a device-level sensitivity, specificity, or AUC endpoint.
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
Adjunctive estimation of the BI-RADS 5th Edition breast-density category from processed digital 2D mammograms to aid radiologists; not diagnostic.
Processed digital 2D mammograms from FFDM systems, with images extracted from DICOM files; the packet identifies GE Senographe Essentials and Hologic Selenia Dimension systems and supports CC/MLO pairs or specified single-view inputs.
A BI-RADS breast-density 5th Edition category is produced for each breast and for each patient, with the patient result based on the maximum category of the two breasts; the browser interface can display the assessment and similar images.
Women whose processed digital 2D mammograms from Full Field Digital Mammography systems are analyzed to estimate BI-RADS breast density category; the FDA document does not specify a facility type.
Exact FDA submission
Checked 2026-11-14
Packet wording: "DenSeeMammo is a software that aims at assessing the breast density of a woman." … "DenSeeMammo is a software application intended for use with Full Field Digital Mammography systems. DenSeeMammo estimates BI-RADS breast density category by analyzing processed digital 2D mammograms using a fully automated comparison procedure.". Read from the exact FDA decision document on 2026-11-14.
The output is adjunctive and not a diagnostic aid; an MQSA-qualified physician makes the final category. The labeled compatibility is limited to the identified FFDM systems and view configurations. Core software was built and tested on OS X, the GUI on Windows/OS X/Linux, the user computer must share a local network with the server, and a web browser is required.
FDA verification and validation covered reproducibility, comparison of left/right and patient-level density results with visual assessments by MQSA-qualified radiologists, GE and Hologic datasets, two-view and single-view configurations, and beta-site testing for physician integration and usability. The packet states that all test acceptance criteria were met; it does not report a device-level sensitivity, specificity, or AUC endpoint.
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
FDA verification and validation covered reproducibility, comparison of left/right and patient-level density results with visual assessments by MQSA-qualified radiologists, GE and Hologic datasets, two-view and single-view configurations, and beta-site testing for physician integration and usability. The packet states that all test acceptance criteria were met; it does not report a device-level sensitivity, specificity, or AUC endpoint.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
DenSeeMammo regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K173574
IndependenceIndependence not established
K173574
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K173574. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: Processed digital 2D mammograms from FFDM systems, with images extracted from DICOM files; the packet identifies GE Senographe Essentials and Hologic Selenia Dimension systems and supports CC/MLO pairs or specified single-view inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The software works in client-server mode: the user computer and server must be on the same local network, the server performs computation and provides the browser-based interface, and processed images are extracted from DICOM files. The FDA packet does not establish a PACS or RIS interface.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes DenSeeMammo working in client-server mode, with computations made on a server on the same local network as the user computer and a web browser required to display the graphical user interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The software works in a client-server mode and requires that the user computer be on the same local network as the server. Computations are made on the server part of the system that also" … "A web browser is required to display the graphical user interface: to select the patients’ images and to display the assessment". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: A BI-RADS breast-density 5th Edition category is produced for each breast and for each patient, with the patient result based on the maximum category of the two breasts; the browser interface can display the assessment and similar images.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A BI-RADS breast-density 5th Edition category is produced for each breast and for each patient, with the patient result based on the maximum category of the two breasts; the browser interface can display the assessment and similar images.
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.
The exact FDA package describes DenSeeMammo working in client-server mode, with computations made on a server on the same local network as the user computer and a web browser required to display the graphical user interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software works in a client-server mode and requires that the user computer be on the same local network as the server. Computations are made on the server part of the system that also" … "A web browser is required to display the graphical user interface: to select the patients’ images and to display the assessment". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The software works in client-server mode: the user computer and server must be on the same local network, the server performs computation and provides the browser-based interface, and processed images are extracted from DICOM files. The FDA packet does not establish a PACS or RIS interface.
ACR AI Central provides an exact-submission model card for DenSeeMammo; FDA labeling remains controlling for clinical use, limitations, and performance.
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.
Exact FDA record reviewedStatus
2026-09-20Last searched
24Fields reviewed
9Source classes checked
1Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 1 PubMed and 0 ClinicalTrials.gov candidate record. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. 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 device recall, literature index, trial registry, 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-09 - Exact FDA submission
No public price or quote for the exact K173574 configuration was established in this review.
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-09-09 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
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-09 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Monitoring: Not verified - checked 2026-09-09 - 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.