Authorized purpose: Parallel triage notification of suspected aortic dissection on contrast CT chest/abdomen; compressed previews are not diagnostic.
Clinical role
Parallel worklist triage and notification support; the original PACS images remain the basis for diagnostic interpretation.
Images and patients
CT/CTA · Chest and abdomen; suspected aortic dissection
Key limitation
Keep in mind: Not a diagnostic device and preview images are not for diagnosis beyond notification. Full original images in PACS must be reviewed with other patient information and professional judgment. Scope is contrast CT chest/abdomen in patients aged 18 and older, slice thickness 0.5-5.0 mm, excluding inadequate field of view.
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: Parallel triage notification of suspected aortic dissection on contrast CT chest/abdomen; compressed previews are not diagnostic.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest and abdomen; suspected aortic dissection Input: Filtered DICOM contrast CT chest, abdomen, or chest/abdomen exams, including CTA and CT with contrast, from adults or transitional adolescents aged 18 and older; slice thickness 0.5-5.0 mm and adequate field of view are required.
Who uses it?Intended users: Hospital networks and appropriately trained medical specialists
What does the software produce?Output: A priority flag and pop-up notification for suspected aortic dissection in a standalone desktop/image-review workflow, with an unannotated, compressed, low-quality grayscale preview for informational prioritization; the original medical image is not altered.
What is its most important limitation?Key limitation: Not a diagnostic device and preview images are not for diagnosis beyond notification. Full original images in PACS must be reviewed with other patient information and professional judgment. Scope is contrast CT chest/abdomen in patients aged 18 and older, slice thickness 0.5-5.0 mm, excluding inadequate field of view.
Clinical takeaway. Clinical role: Parallel triage notification of suspected aortic dissection on contrast CT chest/abdomen; compressed previews are not diagnostic.
Evidence takeaway. Evidence from the reviewed source record: FDA retrospective blinded multicenter performance testing used 509 contrast CT chest/abdomen cases from five U.S. clinical sites, with ground truth from three senior board-certified radiologists. Primary sensitivity was 92.7% (95% CI 88.2%-95.8%) and specificity was 92.8% (95% CI 89.2%-95.4%) against an 80% performance goal. Secondary mean time-to-notification for true-positive subject cases was 10.7 seconds (95% CI 10.5-10.9), compared with 38.0 seconds for the predicate.
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
Parallel triage notification of suspected aortic dissection on contrast CT chest/abdomen; compressed previews are not diagnostic.
Filtered DICOM contrast CT chest, abdomen, or chest/abdomen exams, including CTA and CT with contrast, from adults or transitional adolescents aged 18 and older; slice thickness 0.5-5.0 mm and adequate field of view are required.
A priority flag and pop-up notification for suspected aortic dissection in a standalone desktop/image-review workflow, with an unannotated, compressed, low-quality grayscale preview for informational prioritization; the original medical image is not altered.
Not a diagnostic device and preview images are not for diagnosis beyond notification. Full original images in PACS must be reviewed with other patient information and professional judgment. Scope is contrast CT chest/abdomen in patients aged 18 and older, slice thickness 0.5-5.0 mm, excluding inadequate field of view.
FDA retrospective blinded multicenter performance testing used 509 contrast CT chest/abdomen cases from five U.S. clinical sites, with ground truth from three senior board-certified radiologists. Primary sensitivity was 92.7% (95% CI 88.2%-95.8%) and specificity was 92.8% (95% CI 89.2%-95.4%) against an 80% performance goal. Secondary mean time-to-notification for true-positive subject cases was 10.7 seconds (95% CI 10.5-10.9), compared with 38.0 seconds for the predicate.
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 retrospective blinded multicenter performance testing used 509 contrast CT chest/abdomen cases from five U.S. clinical sites, with ground truth from three senior board-certified radiologists. Primary sensitivity was 92.7% (95% CI 88.2%-95.8%) and specificity was 92.8% (95% CI 89.2%-95.4%) against an 80% performance goal. Secondary mean time-to-notification for true-positive subject cases was 10.7 seconds (95% CI 10.5-10.9), compared with 38.0 seconds for the predicate.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
BriefCase-Aortic Dissection Triage regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K251406
Samplen=509
Sites5
IndependenceIndependence not established
K251406
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 K251406. 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 contrast CT chest, abdomen, or chest/abdomen exams, including CTA and CT with contrast, from adults or transitional adolescents aged 18 and older; slice thickness 0.5-5.0 mm and adequate field of view are required.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: A Linux-based server in a cloud environment receives filtered DICOM images, processes series chronologically, and transfers algorithm output to desktop image-review software with pop-up notification and worklist prioritization; diagnostic assessment occurs on original PACS images. Specific local interfaces are 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 as 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 priority flag and pop-up notification for suspected aortic dissection in a standalone desktop/image-review workflow, with an unannotated, compressed, low-quality grayscale preview for informational prioritization; the original medical image is not altered.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A priority flag and pop-up notification for suspected aortic dissection in a standalone desktop/image-review workflow, with an unannotated, compressed, low-quality grayscale preview for informational prioritization; the original medical image is not altered.
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 as 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.
A Linux-based server in a cloud environment receives filtered DICOM images, processes series chronologically, and transfers algorithm output to desktop image-review software with pop-up notification and worklist prioritization; diagnostic assessment occurs on original PACS images. Specific local interfaces are 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-19Last searched
25Fields 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-08 - Exact FDA submission
No public price or quote for the exact K251406 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-08 - 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-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Authorized purpose: Passive workflow prioritization for studies with imaging patterns consistent with possible total arterial occlusion in the specified vessels; not primary diagnosis, screening, disease detection, or patient-management decision support
Modality
CT/CTA
Anatomy
Aorta and lower-extremity arteries: common iliac, external iliac, common femoral, superficial femoral, and popliteal arteries
Authorized purpose: Notification-only triage of adult non-contrast head CT for suspected intracranial hemorrhage and large-vessel occlusion, with parallel communication to trained clinicians during standard care.
Modality
CT/CTA
Anatomy
Brain and intracranial vessels: intracranial hemorrhage and LVO involving ICA, MCA-M1, and MCA-M2
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.