FDA-cleared profile

BriefCase-Triage

Aidoc Medical, Ltd. · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Triages CT scans including the cervical spine for suspected fracture-compatible linear lucencies.

Clinical role
Workflow triage tool that flags cases with suspected linear lucencies in the cervical spine bone compatible with fractures, notifying users in parallel to standard-of-care interpretation with non-diagnostic compressed previews; it neither removes nor deprioritizes cases.
Images and patients
CT/CTA · Cervical spine
Key limitation
Keep in mind: Inadequate field of view is excluded; reviewed performance inclusion used 0.3-5.0 mm studies with bone or standard kernels, and the output is not diagnostic.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Triages CT scans including the cervical spine for suspected fracture-compatible linear lucencies.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Cervical spine Input: Filtered DICOM cervical-spine CT in adults and transitional adolescents aged 18 years or older.
  • Who uses it?Intended users: Hospital networks and appropriately trained medical specialists.
  • What does the software produce?Output: A pop-up notification and compressed low-quality grayscale preview without alteration of the original image.
  • What is its most important limitation?Key limitation: Inadequate field of view is excluded; reviewed performance inclusion used 0.3-5.0 mm studies with bone or standard kernels, and the output is not diagnostic.

Clinical takeaway. Clinical role: Triages CT scans including the cervical spine for suspected fracture-compatible linear lucencies.

Evidence takeaway. Evidence from the reviewed source record: FDA reported 487 cases from six US sites with sensitivity 92.1%, specificity 92.6%, and mean notification time 15.1 seconds.

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
Triages CT scans including the cervical spine for suspected fracture-compatible linear lucencies.
  • Exact FDA submission
  • Checked 2026-09-15

Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.

Workflow role
Workflow triage tool that flags cases with suspected linear lucencies in the cervical spine bone compatible with fractures, notifying users in parallel to standard-of-care interpretation with non-diagnostic compressed previews; it neither removes nor deprioritizes cases.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The device is intended to assist hospital networks and appropriately trained medical specialists in workflow triage by flagging and communication of linear lucencies in the cervical spine bone in patterns compatible with fractures." … "with detected findings 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.". Read from the exact FDA decision document on 2026-11-14.

Required input
Filtered DICOM cervical-spine CT in adults and transitional adolescents aged 18 years or older.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Output and clinician action
A pop-up notification and compressed low-quality grayscale preview without alteration of the original image.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Care setting
Adult
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
Hospital networks and appropriately trained medical specialists.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Limitations
Inadequate field of view is excluded; reviewed performance inclusion used 0.3-5.0 mm studies with bone or standard kernels, and the output is not diagnostic.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Evidence summary
FDA reported 487 cases from six US sites with sensitivity 92.1%, specificity 92.6%, and mean notification time 15.1 seconds.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Evidence

Performance evidence

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 reported 487 cases from six US sites with sensitivity 92.1%, specificity 92.6%, and mean notification time 15.1 seconds.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Reported sensitivity
92.1% (95% CI: 87.5%, 95.4%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

Reported specificity
92.6% (95% CI: 89.0%, 95.4%)
  • Public source
  • Exact FDA submission
  • Checked 2026-09-01

Model specificity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

BriefCase-C-Spine Fracture Triage regulatory performance study summary

  • DesignStand-Alone Performance
  • PopulationAdult
  • Scopeexact submission
  • Tested version3
  • Samplen=487
  • Sites6
  • IndependenceIndependence not established

K242837

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

Safety and lifecycle

Postmarket record

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 K242837. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-09
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Filtered DICOM cervical-spine CT in adults and transitional adolescents aged 18 years or older.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-19 · FDA K242837: BriefCase-Triage

  2. Routing

    Source context, not route validation: The exact FDA package describes DICOM image input, with algorithm output transferred to an image review desktop application that gives pop-up notifications, and an analysis module integrated with image communication platforms meeting its input and output requirements. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "The BriefCase-Triage receives filtered DICOM Images, and processes them chronologically" … "Following the AI processing, the output of the algorithm analysis is transferred to an image review software (desktop application). When a suspected case is detected, the user receives a pop-up notification". 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.

    Field checked 2026-11-14 · FDA K242837: BriefCase-Triage

  3. AI processing

    Source context, not route validation: The exact FDA package describes software intended to run on a linux-based server in a cloud environment. 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.". 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.

    Field checked 2026-11-14 · FDA K242837: BriefCase-Triage

  4. Returned objects

    Source context, not route validation: A pop-up notification and compressed low-quality grayscale preview without alteration of the original image.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-19 · FDA K242837: BriefCase-Triage

  5. Viewer/worklist/report

    Unresolved route: A pop-up notification and compressed low-quality grayscale preview without alteration of the original image.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    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.

    Field checked 2026-09-19 · FDA K242837: BriefCase-Triage

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
The exact FDA package describes software intended to run on a linux-based server in a cloud environment. 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.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact FDA package describes DICOM image input, with algorithm output transferred to an image review desktop application that gives pop-up notifications, and an analysis module integrated with image communication platforms meeting its input and output requirements. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The BriefCase-Triage receives filtered DICOM Images, and processes them chronologically" … "Following the AI processing, the output of the algorithm analysis is transferred to an image review software (desktop application). When a suspected case is detected, the user receives a pop-up notification". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Security
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.

Monitoring
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 exact-submission catalog context

ACR AI Central provides an exact-submission model card for BriefCase-Triage; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
Sources & review details FDA 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.

FDA submission
K242837
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Anatomy
Cervical spine
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2024-10-18
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
11Source 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, 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 K242837 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.

8 sources - 3 history items

Source ledger

  1. FDA K242837: BriefCase-Triage

    U.S. Food and Drug Administration - Published 2024-10-18 - Accessed 2026-09-19

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary, deployment, integration

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. BriefCase-C-Spine Fracture Triage model card (K242837)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, anatomy, evidenceStudies

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K242837

    U.S. Food and Drug Administration - Accessed 2026-09-09

    Scope: postmarketSafety

  8. Aidoc Security & Privacy

    Aidoc Medical - Accessed 2026-10-25

    Scope: security

Research history

  1. K242837 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K253578

BriefCase-Triage: CARE Multi-Triage CT for Pneumothorax; Pericardial effusion; Large aortic aneurysm; Shoulder fracture or dislocation device

Aidoc Medical, Ltd.

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.

Modality
CT/CTA
Anatomy
Chest and abdomen; pneumothorax, pericardial effusion, large aortic aneurysm, and shoulder fracture/dislocation
Decision
2026-02-26
FDA-cleared K252970

BriefCase-Triage: CARE Multi-triage CT Body

Aidoc Medical, Ltd.

Authorized purpose: Adult contrast-enhanced and non-contrast CT triage for 11 chest, abdominal, and pelvic findings: diverticulitis, abdominal-pelvic abscess, appendicitis, intestinal ischemia/pneumatosis, obstructive renal stone, small- and large-bowel obstruction, spleen injury, liver injury, kidney injury, and pelvic fracture.

Modality
CT/CTA
Anatomy
Chest, Abdomen, and Pelvis
Decision
2026-01-07
FDA-cleared K243548

BriefCase-Triage

Aidoc Medical, Ltd.

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.

Modality
CT/CTA
Anatomy
Ribs
Decision
2024-12-11
FDA-cleared K240942

CINA-CSpine

Avicenna.AI

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
Decision
2024-09-12

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history