Authorized purpose: Passive, prioritization-only notification of 2D FFDM screening mammograms with at least one suspicious finding at the exam level; not diagnostic.
Clinical role
Passive notification and exam prioritization in parallel with the standard-of-care worklist; the radiologist decides how to use the code and reviews every exam diagnostically.
Images and patients
Mammography/DBT · Breast
Key limitation
Keep in mind: The device is limited to 2D FFDM screening mammograms and cannot be used where only 3D/DBT is acquired. It is prescription-only, passive rather than a proactive alert, does not alter or remove images, and must not replace full patient evaluation or diagnostic viewer review.
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: Passive, prioritization-only notification of 2D FFDM screening mammograms with at least one suspicious finding at the exam level; not diagnostic.
Which images or clinical context are in scope?Modality: Mammography/DBT Anatomy or clinical context: Breast Input: DICOM 2D FFDM screening mammograms, with up to four standard views (LCC, LMLO, RCC, and RMLO); the device does not operate for sites using only digital breast tomosynthesis (DBT).
Who uses it?Intended users: Radiologists
What does the software produce?Output: A DICOM Structured Report with a cmTriage code of Suspicious or blank is routed to the PACS worklist, where the exam may be sorted if the PACS supports that function. No diagnostic information beyond triage categorization is provided.
What is its most important limitation?Key limitation: The device is limited to 2D FFDM screening mammograms and cannot be used where only 3D/DBT is acquired. It is prescription-only, passive rather than a proactive alert, does not alter or remove images, and must not replace full patient evaluation or diagnostic viewer review.
Clinical takeaway. Clinical role: Passive, prioritization-only notification of 2D FFDM screening mammograms with at least one suspicious finding at the exam level; not diagnostic.
Evidence takeaway. Evidence from the reviewed source record: FDA reviewed a retrospective, blinded, multicenter study of 1,255 US mammographic studies (400 biopsy-proven cancers and 855 normal studies with BI-RADS 1/2 and two-year negative follow-up), using up to four standard views per study; the dataset was enriched with cancers. The observed primary sensitivity was 86.9% (95% CI: 83.6%-90.2%) and specificity was 88.5% (95% CI: 86.4%-90.7%). AUC was 0.951 (95% CI: 0.937-0.964) as a separate endpoint. At a separate 84.4% sensitivity operating point, specificity was 94.0% and the population-adjusted mark rate was 6.37%; average timing was 3.35 minutes at 10 Mbit/s upload and 37 Mbit/s download.
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
Passive, prioritization-only notification of 2D FFDM screening mammograms with at least one suspicious finding at the exam level; not diagnostic.
Passive notification and exam prioritization in parallel with the standard-of-care worklist; the radiologist decides how to use the code and reviews every exam diagnostically.
DICOM 2D FFDM screening mammograms, with up to four standard views (LCC, LMLO, RCC, and RMLO); the device does not operate for sites using only digital breast tomosynthesis (DBT).
A DICOM Structured Report with a cmTriage code of Suspicious or blank is routed to the PACS worklist, where the exam may be sorted if the PACS supports that function. No diagnostic information beyond triage categorization is provided.
The device is limited to 2D FFDM screening mammograms and cannot be used where only 3D/DBT is acquired. It is prescription-only, passive rather than a proactive alert, does not alter or remove images, and must not replace full patient evaluation or diagnostic viewer review.
FDA reviewed a retrospective, blinded, multicenter study of 1,255 US mammographic studies (400 biopsy-proven cancers and 855 normal studies with BI-RADS 1/2 and two-year negative follow-up), using up to four standard views per study; the dataset was enriched with cancers. The observed primary sensitivity was 86.9% (95% CI: 83.6%-90.2%) and specificity was 88.5% (95% CI: 86.4%-90.7%). AUC was 0.951 (95% CI: 0.937-0.964) as a separate endpoint. At a separate 84.4% sensitivity operating point, specificity was 94.0% and the population-adjusted mark rate was 6.37%; average timing was 3.35 minutes at 10 Mbit/s upload and 37 Mbit/s download.
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 reviewed a retrospective, blinded, multicenter study of 1,255 US mammographic studies (400 biopsy-proven cancers and 855 normal studies with BI-RADS 1/2 and two-year negative follow-up), using up to four standard views per study; the dataset was enriched with cancers. The observed primary sensitivity was 86.9% (95% CI: 83.6%-90.2%) and specificity was 88.5% (95% CI: 86.4%-90.7%). AUC was 0.951 (95% CI: 0.937-0.964) as a separate endpoint. At a separate 84.4% sensitivity operating point, specificity was 94.0% and the population-adjusted mark rate was 6.37%; average timing was 3.35 minutes at 10 Mbit/s upload and 37 Mbit/s download.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
cmTriage 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 K183285
Samplen=1255
IndependenceIndependence not established
K183285
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 K183285. 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: DICOM 2D FFDM screening mammograms, with up to four standard views (LCC, LMLO, RCC, and RMLO); the device does not operate for sites using only digital breast tomosynthesis (DBT).
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: A PACS listener/local DICOM router sends a de-identified and encrypted local copy to the CureMetrix cloud; the result DICOM SR returns through cmEdge, is re-associated with the original study, and is routed to the PACS. PACS features vary by manufacturer and a specific local interface is not established.
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 hospital-configured image forwarding software that interacts with the facility's PACS or local DICOM router and sends de-identified, encrypted image copies to the CureMetrix cloud, where the Image Processing and Analysis Software component is hosted. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The Image Forwarding and Result File Receiving Software is configured by the hospital to interact with a healthcare facility’s PACS or local DICOM router" … "creates a local copy of the image(s), de-identifies the local copy, encrypts the local copy, transmits the local copy to the CureMetrix cloud,". 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 DICOM Structured Report with a cmTriage code of Suspicious or blank is routed to the PACS worklist, where the exam may be sorted if the PACS supports that function. No diagnostic information beyond triage categorization is provided.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A DICOM Structured Report with a cmTriage code of Suspicious or blank is routed to the PACS worklist, where the exam may be sorted if the PACS supports that function. No diagnostic information beyond triage categorization is provided.
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 hospital-configured image forwarding software that interacts with the facility's PACS or local DICOM router and sends de-identified, encrypted image copies to the CureMetrix cloud, where the Image Processing and Analysis Software component is hosted. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The Image Forwarding and Result File Receiving Software is configured by the hospital to interact with a healthcare facility’s PACS or local DICOM router" … "creates a local copy of the image(s), de-identifies the local copy, encrypts the local copy, transmits the local copy to the CureMetrix cloud,". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
A PACS listener/local DICOM router sends a de-identified and encrypted local copy to the CureMetrix cloud; the result DICOM SR returns through cmEdge, is re-associated with the original study, and is routed to the PACS. PACS features vary by manufacturer and a specific local interface is not established.
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
26Fields 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 K183285 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
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
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: 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: Prioritizes suspicious screening DBT examinations for MQSA interpreting physicians; every examination remains subject to full physician review.
The VinDr-Mammo is a passive notification for prioritization-only, a parallel- workflow software tool used by MQSA qualified interpreting physicians to prioritize patients with suspicious findings in the medical care environment. VinDr-Mammo utilizes an artificial intelligence algorithm to analyze 2D FFDM screening mammograms and flags those that are suggestive of the presence of at least one suspicious finding at the exam- level. VinDr-Mammo produces an exam-level output to a PACS/Workstation for flagging the suspicious case and allows worklist prioritization. MQSA qualified interpreting physicians are responsible for reviewing each exam on a display approved for use in mammography, according to the current standard of care. VinDr-Mammo device is limited to the categorization of exams, does not provide any diagnostic information beyond triage and prioritization, does not remove images from the interpreting physician’s worklist, and should not be used in lieu of full patient evaluation, or relied upon to make or confirm diagnosis. The VinDr-Mammo device is intended for use with complete 2D FFDM mammography exams acquired using validated FFDM systems only.
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.