Authorized purpose: BriefCase-Triage CARE Multi-Triage CT analyzes contrast and non-contrast chest, abdomen, or chest/abdomen CT in adults or transitional adolescents aged 18 and older to flag suspected pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation for hospital-network workflow triage; notifications and previews are for prioritization, not diagnosis.
Clinical role
Parallel CT triage and notification support to prioritize review of suspected urgent findings.
Images and patients
CT/CTA · Chest and abdomen; pneumothorax, pericardial effusion, large aortic aneurysm, and shoulder fracture/dislocation
Key limitation
Keep in mind: Notifications and previews are for prioritization and are not diagnostic. Clinicians must review the full images; the cleared age, anatomy, acquisition, finding, and hospital-network limits apply.
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: BriefCase-Triage CARE Multi-Triage CT analyzes contrast and non-contrast chest, abdomen, or chest/abdomen CT in adults or transitional adolescents aged 18 and older to flag suspected pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation for hospital-network workflow triage; notifications and previews are for prioritization, not diagnosis.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest and abdomen; pneumothorax, pericardial effusion, large aortic aneurysm, and shoulder fracture/dislocation Input: Contrast and non-contrast CT of the chest, abdomen, or chest and abdomen with the labeled acquisition and metadata conditions.
Who uses it?Intended users: Trained radiologists, emergency or acute-care clinicians, and hospital-network staff responsible for triage review.
What does the software produce?Output: Suspected finding flags, prioritization notifications, and key-image previews for pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation.
What is its most important limitation?Key limitation: Notifications and previews are for prioritization and are not diagnostic. Clinicians must review the full images; the cleared age, anatomy, acquisition, finding, and hospital-network limits apply.
Clinical takeaway. Clinical role: BriefCase-Triage CARE Multi-Triage CT analyzes contrast and non-contrast chest, abdomen, or chest/abdomen CT in adults or transitional adolescents aged 18 and older to flag suspected pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation for hospital-network workflow triage; notifications and previews are for prioritization, not diagnosis.
Evidence takeaway. Evidence from the reviewed source record: The FDA package documents multi-triage CT verification for the four labeled suspected findings; it does not make the notifications diagnostic or establish independent outcome benefit.
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-Triage CARE Multi-Triage CT analyzes contrast and non-contrast chest, abdomen, or chest/abdomen CT in adults or transitional adolescents aged 18 and older to flag suspected pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation for hospital-network workflow triage; notifications and previews are for prioritization, not diagnosis.
Suspected finding flags, prioritization notifications, and key-image previews for pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation.
Notifications and previews are for prioritization and are not diagnostic. Clinicians must review the full images; the cleared age, anatomy, acquisition, finding, and hospital-network limits apply.
The FDA package documents multi-triage CT verification for the four labeled suspected findings; it does not make the notifications diagnostic or establish independent outcome benefit.
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
The FDA package documents multi-triage CT verification for the four labeled suspected findings; it does not make the notifications diagnostic or establish independent outcome benefit.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K253578 FDA evidence package for BriefCase-Triage: CARE Multi-Triage CT for Pneumothorax; Pericardial effusion; Large aortic aneurysm; Shoulder fracture or dislocation device
DesignFDA 510(k) verification and validation evidence described in the exact submission
PopulationChest and abdomen; pneumothorax, pericardial effusion, large aortic aneurysm, and shoulder fracture/dislocation
Scopeexact submission
Tested versionBriefCase-Triage CARE Multi-Triage CT
IndependenceSponsor or vendor study
K253578
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
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: Contrast and non-contrast CT of the chest, abdomen, or chest and abdomen with the labeled acquisition and metadata conditions.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes return of triage flags, notifications, and key images in the hospital workflow; exact PACS/RIS, worklist, notification, and downtime behavior require local testing.
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 FDA package describes a Linux-based server in a cloud environment; current hosting, service, security, network, and local operational boundaries remain unverified.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Suspected finding flags, prioritization notifications, and key-image previews for pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Suspected finding flags, prioritization notifications, and key-image previews for pneumothorax, pericardial effusion, large aortic aneurysm, or shoulder fracture/dislocation.
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 FDA package describes a Linux-based server in a cloud environment; current hosting, service, security, network, and local operational boundaries remain unverified.
The FDA package describes return of triage flags, notifications, and key images in the hospital workflow; exact PACS/RIS, worklist, notification, and downtime behavior require local testing.
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.
Only trained radiologists, emergency or acute-care clinicians, and hospital-network staff responsible for triage review. should operate or interpret this product. Local onboarding must cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K253578 by exact software, hardware, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: Notifications and previews are for prioritization and are not diagnostic. Clinicians must review the full images; the cleared age, anatomy, acquisition, finding, and hospital-network limits apply.
The FDA package describes a Linux-based server in a cloud environment; current hosting, service, security, network, and local operational boundaries remain unverified.
exact submission · checked 2026-09-04
FDA-described deployment details do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes return of triage flags, notifications, and key images in the hospital workflow; exact PACS/RIS, worklist, notification, and downtime behavior require local testing.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Notifications and previews are for prioritization and are not diagnostic. Clinicians must review the full images; the cleared age, anatomy, acquisition, finding, and hospital-network limits apply.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price or product-specific reimbursement was established in the reviewed public material.
Monitor K253578 by exact software, hardware, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: Notifications and previews are for prioritization and are not diagnostic. Clinicians must review the full images; the cleared age, anatomy, acquisition, finding, and hospital-network limits apply.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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-04Last searched
25Fields reviewed
11Source classes checked
20Screened PubMed leads
10Screened trial leads
0Unreviewed FDA recall leads
Screened 20 PubMed titles and 10 trial records. They concern pericardial effusion or unrelated acute-care topics and do not identify BriefCase-Triage CARE Multi-Triage CT, its tested release, or K253578; all 30 are quarantined. The current discovery snapshot contains 20 PubMed and 10 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, acr ai central product, vendor product page, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared product version was established. Obtain a written quote separating license, implementation, interfaces, compute, storage, training, support, upgrades, renewal, and exit costs.
Authorized purpose: Workflow triage and notification of suspect cases with three or more acute rib-fracture (RibFx) pathologies in adults or transitional adolescents aged 18 and older.
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.