Authorized purpose: Case-level triage and notification of suspected central pulmonary embolism on CTPA in adults or transitional adolescents aged 18 years and older, in parallel with standard-of-care interpretation.
Clinical role
Parallel case-level triage and notification/worklist prioritization for suspected central PE; cases remain in the standard-of-care queue.
Images and patients
CT/CTA · Chest and central pulmonary arteries
Key limitation
Keep in mind: The preview is informational and not for diagnostic use beyond notification; the original image is not altered, cases are not removed or deprioritized, and clinicians must review full images with other patient information and professional judgment. The FDA packet does not specify an additional image-quality or slice-thickness exclusion.
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: Case-level triage and notification of suspected central pulmonary embolism on CTPA in adults or transitional adolescents aged 18 years and older, in parallel with standard-of-care interpretation.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest and central pulmonary arteries Input: Filtered DICOM CTPA images from adults or transitional adolescents aged 18 years and older; the algorithm processes the series chronologically.
Who uses it?Intended users: Hospital networks and appropriately trained medical specialists.
What does the software produce?Output: A pop-up/priority notification for suspected central PE with a compressed, low-quality, grayscale, unannotated preview labeled for prioritization only; the workflow prompts review of the original images in PACS.
What is its most important limitation?Key limitation: The preview is informational and not for diagnostic use beyond notification; the original image is not altered, cases are not removed or deprioritized, and clinicians must review full images with other patient information and professional judgment. The FDA packet does not specify an additional image-quality or slice-thickness exclusion.
Clinical takeaway. Clinical role: Case-level triage and notification of suspected central pulmonary embolism on CTPA in adults or transitional adolescents aged 18 years and older, in parallel with standard-of-care interpretation.
Evidence takeaway. Evidence from the reviewed source record: FDA packet: retrospective, blinded, multicenter pivotal study of 328 unique cases from 6 U.S. clinical sites, with three senior board-certified radiologists using majority voting. Default sensitivity was 89.2% (95% CI 82.5%-93.9%) and specificity 94.5% (90.3%-97.2%) against an 80% goal. AOP1 sensitivity/specificity were 96.9% (92.3%-99.2%)/85.9% (80.3%-90.4%). Default time-to-notification was 29.3 seconds (95% CI 26.8-31.9; n=115); PPV 52.9%, NPV 99.2%, PLR 16.1, and NLR 0.1 are separate endpoints.
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
Case-level triage and notification of suspected central pulmonary embolism on CTPA in adults or transitional adolescents aged 18 years and older, in parallel with standard-of-care interpretation.
A pop-up/priority notification for suspected central PE with a compressed, low-quality, grayscale, unannotated preview labeled for prioritization only; the workflow prompts review of the original images in PACS.
The preview is informational and not for diagnostic use beyond notification; the original image is not altered, cases are not removed or deprioritized, and clinicians must review full images with other patient information and professional judgment. The FDA packet does not specify an additional image-quality or slice-thickness exclusion.
FDA packet: retrospective, blinded, multicenter pivotal study of 328 unique cases from 6 U.S. clinical sites, with three senior board-certified radiologists using majority voting. Default sensitivity was 89.2% (95% CI 82.5%-93.9%) and specificity 94.5% (90.3%-97.2%) against an 80% goal. AOP1 sensitivity/specificity were 96.9% (92.3%-99.2%)/85.9% (80.3%-90.4%). Default time-to-notification was 29.3 seconds (95% CI 26.8-31.9; n=115); PPV 52.9%, NPV 99.2%, PLR 16.1, and NLR 0.1 are separate endpoints.
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: retrospective, blinded, multicenter pivotal study of 328 unique cases from 6 U.S. clinical sites, with three senior board-certified radiologists using majority voting. Default sensitivity was 89.2% (95% CI 82.5%-93.9%) and specificity 94.5% (90.3%-97.2%) against an 80% goal. AOP1 sensitivity/specificity were 96.9% (92.3%-99.2%)/85.9% (80.3%-90.4%). Default time-to-notification was 29.3 seconds (95% CI 26.8-31.9; n=115); PPV 52.9%, NPV 99.2%, PLR 16.1, and NLR 0.1 are separate endpoints.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
BriefCase-Central Pulmonary Embolism Triage regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K232751
Samplen=328
Sites6
IndependenceIndependence not established
K232751
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 K232751. 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: Filtered DICOM CTPA images from adults or transitional adolescents aged 18 years and older; the algorithm processes the series chronologically.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA packet describes a Linux-based cloud server receiving filtered DICOM images, an algorithm module integrated with a compatible image-communication platform and desktop workflow application, and review of original images in PACS; exact local interface compatibility 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 BriefCase-Triage software intended to run on a Linux-based server in a cloud environment, with DICOM exams de-identified and uploaded to the cloud for analysis and notifications sent back to a desktop application. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The software is based on an algorithm programmed component and is intended to run on a linux-based server in a cloud environment." … "The BriefCase-Triage time-to-notification includes the time to get the DICOM exam, de-identify it, upload it to the cloud, analyze and send a notification on a positive suspect case back to the desktop application.". 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 pop-up/priority notification for suspected central PE with a compressed, low-quality, grayscale, unannotated preview labeled for prioritization only; the workflow prompts review of the original images in PACS.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A pop-up/priority notification for suspected central PE with a compressed, low-quality, grayscale, unannotated preview labeled for prioritization only; the workflow prompts review of the original images in PACS.
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 BriefCase-Triage software intended to run on a Linux-based server in a cloud environment, with DICOM exams de-identified and uploaded to the cloud for analysis and notifications sent back to a desktop application. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software is based on an algorithm programmed component and is intended to run on a linux-based server in a cloud environment." … "The BriefCase-Triage time-to-notification includes the time to get the DICOM exam, de-identify it, upload it to the cloud, analyze and send a notification on a positive suspect case back to the desktop application.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The FDA packet describes a Linux-based cloud server receiving filtered DICOM images, an algorithm module integrated with a compatible image-communication platform and desktop workflow application, and review of original images in PACS; exact local interface compatibility is not established.
Aidoc's current public Security & Privacy page says its security work is led by a CISO and security team, that it has adopted the NIST Cybersecurity Framework, and that its platform runs on AWS and Azure using EDR, encryption, SIEM and CSPM tooling. The page's list of standards and certifications did not load as readable text, so no certification is stated here.
Vendor-wide
Checked 2026-10-25
Vendor-wide marketing statement, not an independent attestation. It does not establish certificate scope or expiry, the controls of this exact release, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.
Aidoc's security page states that its platform runs on AWS and Azure and that customer data protection is achieved with the use of EDR, encryption, SIEM, CSPM and other technologies.
Vendor-wide
Checked 2026-10-27
Vendor statement, not an attestation. The page names Aidoc's platform generally and does not scope these capabilities to any specific product release; exact-release scope is not established. The page lists technology categories in use; it states no uptime, alerting or response-time SLAs.
ACR AI Central provides an exact-submission model card for BriefCase-Triage; 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
26Fields 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, vendor product page, 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 K232751 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
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.
Authorized purpose: Parallel-workflow triage and notification of suspected incidental pulmonary embolism on contrast-enhanced images that include the lungs.
Authorized purpose: Worklist triage and notification for suspected incidental pulmonary embolism on contrast-enhanced CT acquired for another indication; not a diagnostic device
Modality
CT/CTA
Anatomy
Lung and pulmonary arterial segments containing incidental pulmonary embolism; subsegmental arteries are out of scope
Authorized purpose: BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of CTPA images in adults or transitional adolescents aged 18 and older. The device is intended to assist hospital networks and appropriately trained medical specialists in workflow triage by flagging and communication of suspected positive findings of Pulmonary Embolism (PE) pathologies. Briefcase uses an artificial intelligence algorithm to analyze images and highlight cases with detected findings on a Stand-Alone Performance desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected PE findings. Notifications include compressed preview images that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device. The results of BriefCase are intended to be used in conjunction with other patient information and based on their professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care.
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.