Authorized purpose: Passive exam-level notification and prioritization of suspicious findings in screening mammograms.
Clinical role
Passive, prioritization-only, parallel-workflow notification tool: analyzes 2D FFDM screening mammograms and sends an exam-level flag to PACS/workstation for worklist prioritization; it provides no diagnostic information beyond triage and does not remove images from the worklist.
Images and patients
Mammography/DBT · Breast
Key limitation
Keep in mind: Not diagnostic or a substitute for full evaluation; DBT images and 2D synthetic views are excluded; exact broader device compatibility is unknown.
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 exam-level notification and prioritization of suspicious findings in screening mammograms.
Which images or clinical context are in scope?Modality: Mammography/DBT Anatomy or clinical context: Breast Input: Complete 2D FFDM screening mammography exams acquired on validated FFDM systems.
Who uses it?Intended users: MQSA-qualified interpreting physicians.
What does the software produce?Output: Exam-level PACS/workstation flagging for worklist prioritization; no diagnostic information and no image removal.
What is its most important limitation?Key limitation: Not diagnostic or a substitute for full evaluation; DBT images and 2D synthetic views are excluded; exact broader device compatibility is unknown.
Clinical takeaway. Clinical role: Passive exam-level notification and prioritization of suspicious findings in screening mammograms.
Evidence takeaway. Evidence from the reviewed source record: FDA packet reports 800 retrospective anonymized 2D FFDM exams, 399 biopsy-proven cancer and 401 negative BI-RADS 1/2 cases; AUROC 0.9569 (95% CI 0.9364-0.9738), sensitivity 87%, and specificity 89%. Accuracy 95.6% is not reported.
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 exam-level notification and prioritization of suspicious findings in screening mammograms.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Passive, prioritization-only, parallel-workflow notification tool: analyzes 2D FFDM screening mammograms and sends an exam-level flag to PACS/workstation for worklist prioritization; it provides no diagnostic information beyond triage and does not remove images from the worklist.
Exact FDA submission
Checked 2026-11-14
Packet wording: "is a passive notification for prioritization-only, parallel-workflow software tool used by MQSA qualified interpreting physicians to prioritize patients with suspicious findings in the medical care environment. QmTRIAGETM utilizes an artificial intelligence algorithm to analyze 2D FFDM screening mammograms" … "produces an exam level output to a PACS/Workstation for flagging the suspicious study and allows for worklist prioritization.". Read from the exact FDA decision document on 2026-11-14.
Patients with 2D FFDM screening mammograms (complete exams acquired using validated FFDM systems) in the medical care environment; the FDA document does not specify a facility type.
Exact FDA submission
Checked 2026-11-14
Packet wording: "software tool used by MQSA qualified interpreting physicians to prioritize patients with suspicious findings in the medical care environment." … "QmTRIAGE™ utilizes an artificial intelligence algorithm to analyze 2D FFDM screening mammograms and flags those that are suggestive of". Read from the exact FDA decision document on 2026-11-14.
FDA packet reports 800 retrospective anonymized 2D FFDM exams, 399 biopsy-proven cancer and 401 negative BI-RADS 1/2 cases; AUROC 0.9569 (95% CI 0.9364-0.9738), sensitivity 87%, and specificity 89%. Accuracy 95.6% is not reported.
Exact FDA submission
Checked 2026-09-19
Submission-reported retrospective validation; no subgroup breakdown.
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 packet reports 800 retrospective anonymized 2D FFDM exams, 399 biopsy-proven cancer and 401 negative BI-RADS 1/2 cases; AUROC 0.9569 (95% CI 0.9364-0.9738), sensitivity 87%, and specificity 89%. Accuracy 95.6% is not reported.
FDA source
Exact FDA submission
Checked 2026-09-19
Submission-reported retrospective validation; no subgroup breakdown.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
CogNet QmTRIAGE 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 K220080
Samplen=800
IndependenceIndependence not established
K220080
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 K220080. 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: Complete 2D FFDM screening mammography exams acquired on validated FFDM systems.
Scope: Exact FDA submission. FDA indications statement.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
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 QmTRIAGE as offering cloud-based analysis, noting that only the predicate also offers an on-premise option. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "While both the proposed device and the predicate offer cloud-based analysis, the predicate also offers an on-premise option.". 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: Exam-level PACS/workstation flagging for worklist prioritization; no diagnostic information and no image removal.
Scope: Exact FDA submission. FDA intended-use and technological-characteristics scope.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Exam-level PACS/workstation flagging for worklist prioritization; no diagnostic information and no image removal.
Scope: Exact FDA submission. FDA intended-use and technological-characteristics scope.
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 QmTRIAGE as offering cloud-based analysis, noting that only the predicate also offers an on-premise option. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "While both the proposed device and the predicate offer cloud-based analysis, the predicate also offers an on-premise option.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact-submission ACR model card explicitly references PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
ACR AI Central provides an exact-submission model card for CogNet QmTRIAGE; 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
27Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 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, fda decision summary packet, 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 K220080 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.