BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of abdominal CT images. The device is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive findings of Intra-abdominal free gas (IFG) 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 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.
Clinical role
Triage and notification software: an AI algorithm analyzes abdominal CT images and sends notifications of suspected intra-abdominal free gas to the Worklist desktop application, prompting preemptive triage in parallel to standard-of-care image interpretation.
Images and patients
CT/CTA · Abdomen
Key limitation
Exclusion criteria: All studies that are technically inadequate, including studies with severe motion artifacts, severe metal artifacts, or an inadequate field of view.. Supported hardware: Unspecified. Scanner manufacturers: All. Slice thickness: Slice thickness 0.625 mm - 5 mm axial.. Reconstruction kernel: Not Applicable
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyCT/CTA · Abdomen
Workflow roleTriage and notification software: an AI algorithm analyzes abdominal CT images and sends notifications of suspected intra-abdominal free gas to the Worklist desktop application, prompting preemptive triage in parallel to standard-of-care image interpretation.
Required inputAbdominal CT images received in DICOM format, which are saved, filtered and de-identified before the algorithm processes each series chronologically.
Output and human actionIntra-abdominal Free Gas (Triage)
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
BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of abdominal CT images. The device is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive findings of Intra-abdominal free gas (IFG) 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 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.
Triage and notification software: an AI algorithm analyzes abdominal CT images and sends notifications of suspected intra-abdominal free gas to the Worklist desktop application, prompting preemptive triage in parallel to standard-of-care image interpretation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "indicated for use in the analysis of abdominal CT images. The device is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive findings of Intra-abdominal free gas (IFG) pathologies." … "BriefCase uses an artificial intelligence algorithm to analyze images and highlight cases with detected findings on a standalone desktop application in parallel to the ongoing standard of care image interpretation.". Read from the exact FDA decision document on 2026-11-14.
Abdominal CT images received in DICOM format, which are saved, filtered and de-identified before the algorithm processes each series chronologically.
Exact FDA submission
Checked 2026-11-14
Packet wording: "BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of abdominal CT images." … "DICOM images are received, saved, filtered and de-identified before processing. Series are processed chronologically by running an algorithm on each series to detect suspected findings". Read from the exact FDA decision document on 2026-11-14.
Exclusion criteria: All studies that are technically inadequate, including studies with severe motion artifacts, severe metal artifacts, or an inadequate field of view.. Supported hardware: Unspecified. Scanner manufacturers: All. Slice thickness: Slice thickness 0.625 mm - 5 mm axial.. Reconstruction kernel: Not Applicable
Exact FDA submission
Checked 2026-09-01
Limitations and supported-acquisition details reported in the exact-submission ACR model card.
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
Study type: Stand-Alone Performance. Cases: 186. Sites: 3. Reference standard: Interpretation by Reviewing Clinician. Reported sensitivity: 91%. Reported specificity: 89%
Public source
Exact FDA submission
Checked 2026-09-01
Structured study metadata from the exact-submission ACR model card; this is not an independent evidence synthesis.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
BriefCase-Intra-abdominal Free Gas Triage regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested version1
Samplen=186
Sites3
IndependenceIndependence not established
K193298
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 K193298. 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: Abdominal CT images received in DICOM format, which are saved, filtered and de-identified before the algorithm processes each series chronologically.
Scope: Exact FDA submission. Packet wording: "BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of abdominal CT images." … "DICOM images are received, saved, filtered and de-identified before processing. Series are processed chronologically by running an algorithm on each series to detect suspected findings". Read from the exact FDA decision document on 2026-11-14.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes BriefCase receiving and de-identifying DICOM images before processing, sending notifications to the Worklist desktop application, and prompting the user to assess the original images in the PACS. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "DICOM images are received, saved, filtered and de-identified before processing." … "Series are processed chronologically by running an algorithm on each series to detect suspected findings and then notifications on flagged series are sent to the Worklist desktop application,". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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 as three modules (an Aidoc Hospital Server for image acquisition, an Aidoc Cloud Server for image processing, and an Aidoc Worklist Application installed on the radiologist's desktop), with exams de-identified and uploaded to the cloud for analysis. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The device consists of the following three modules: (1) Aidoc Hospital Server (AHS) for image acquisition; (2) Aidoc Cloud Server (ACS) for image processing; and (3) Aidoc Worklist Application for workflow integration, installed on the radiologist’ desktop" … "The BriefCase 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 worklist 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.
Unresolved route: Intra-abdominal Free Gas (Triage)
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
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 as three modules (an Aidoc Hospital Server for image acquisition, an Aidoc Cloud Server for image processing, and an Aidoc Worklist Application installed on the radiologist's desktop), with exams de-identified and uploaded to the cloud for analysis. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The device consists of the following three modules: (1) Aidoc Hospital Server (AHS) for image acquisition; (2) Aidoc Cloud Server (ACS) for image processing; and (3) Aidoc Worklist Application for workflow integration, installed on the radiologist’ desktop" … "The BriefCase 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 worklist application.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes BriefCase receiving and de-identifying DICOM images before processing, sending notifications to the Worklist desktop application, and prompting the user to assess the original images in the PACS. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "DICOM images are received, saved, filtered and de-identified before processing." … "Series are processed chronologically by running an algorithm on each series to detect suspected findings and then notifications on flagged series are sent to the Worklist desktop application,". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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.
The 510(k) summary states BriefCase (abdominal CT) is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive findings of intra-abdominal free gas.
Exact FDA submission
Checked 2026-10-27
User qualification wording only; the summary specifies no training program or training offering for this device.
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.
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-08Last searched
25Fields reviewed
10Source classes checked
20Awaiting review PubMed leads
6Awaiting review trial leads
0Unreviewed FDA recall leads
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA scope controls clinical claims. ACR and official vendor material provide bounded catalog or product-family context. Candidate literature metadata remains a discovery queue until full-text identity, endpoint, population, and version review is completed. Automated exact-name discovery found 20 PubMed and 6 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
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 K193298 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.
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: Assist hospital networks and appropriately trained physician specialists by flagging suspected acute cervical-spine fractures on cervical-spine CT for triage and prioritization; it is not designed to detect vertebral compression fractures.
Modality
CT/CTA
Anatomy
Cervical spine; acute cervical-spine fractures including non-displaced lines and displaced fragments
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.