FDA-cleared profile

BriefCase

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

Authorized purpose: Chest and abdominal CT triage and notification for suspected vertebral compression fractures in the standard-of-care bone-health workflow; notifications are non-diagnostic and clinicians review the original study.

Clinical role
Computer-aided triage and notification: a suspect case appears in a desktop feed with an unannotated compressed preview while the original PACS workflow continues.
Images and patients
CT/CTA · Chest/Lung
Key limitation
Keep in mind: The preview and notification are informational and not for diagnostic use beyond notification. Clinicians must review the full original images in local PACS with other patient information and professional judgment; the device does not replace diagnosis or disturb standard interpretation.

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: Chest and abdominal CT triage and notification for suspected vertebral compression fractures in the standard-of-care bone-health workflow; notifications are non-diagnostic and clinicians review the original study.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest/Lung Input: Filtered and de-identified DICOM chest and abdominal CT images, received, saved and processed chronologically by series.
  • Who uses it?Intended users: Hospital networks and appropriately trained medical specialists within the standard-of-care bone-health setting.
  • What does the software produce?Output: A desktop feed notification for a suspected VCFx case and a compressed, low-quality, grayscale, unannotated preview captioned for prioritization only; the original medical image is not altered.
  • What is its most important limitation?Key limitation: The preview and notification are informational and not for diagnostic use beyond notification. Clinicians must review the full original images in local PACS with other patient information and professional judgment; the device does not replace diagnosis or disturb standard interpretation.

Clinical takeaway. Clinical role: Chest and abdominal CT triage and notification for suspected vertebral compression fractures in the standard-of-care bone-health workflow; notifications are non-diagnostic and clinicians review the original study.

Evidence takeaway. Evidence from the reviewed source record: K222692's exact FDA pivotal study evaluated 318 chest and abdominal CT cases at five U.S. sites against ground truth from three senior board-certified radiologists. The study reported observed AUC, sensitivity, specificity and notification-time results; its performance goals were thresholds and are kept separate from the observed values.

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
Chest and abdominal CT triage and notification for suspected vertebral compression fractures in the standard-of-care bone-health workflow; notifications are non-diagnostic and clinicians review the original study.
  • Exact FDA submission
  • Checked 2026-09-07
Workflow role
Computer-aided triage and notification: a suspect case appears in a desktop feed with an unannotated compressed preview while the original PACS workflow continues.
  • Exact FDA submission
  • Checked 2026-09-07
Required input
Filtered and de-identified DICOM chest and abdominal CT images, received, saved and processed chronologically by series.
  • Exact FDA submission
  • Checked 2026-09-07
Output and clinician action
A desktop feed notification for a suspected VCFx case and a compressed, low-quality, grayscale, unannotated preview captioned for prioritization only; the original medical image is not altered.
  • Exact FDA submission
  • Checked 2026-09-07
Care setting
Hospital-network radiology workflows in the standard-of-care bone-health setting.
  • Exact FDA submission
  • Checked 2026-09-07
Intended users
Hospital networks and appropriately trained medical specialists within the standard-of-care bone-health setting.
  • Exact FDA submission
  • Checked 2026-09-07
Limitations
The preview and notification are informational and not for diagnostic use beyond notification. Clinicians must review the full original images in local PACS with other patient information and professional judgment; the device does not replace diagnosis or disturb standard interpretation.
  • Exact FDA submission
  • Checked 2026-09-07
Evidence summary
K222692's exact FDA pivotal study evaluated 318 chest and abdominal CT cases at five U.S. sites against ground truth from three senior board-certified radiologists. The study reported observed AUC, sensitivity, specificity and notification-time results; its performance goals were thresholds and are kept separate from the observed values.
  • Exact FDA submission
  • Checked 2026-09-07

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
K222692's exact FDA pivotal study evaluated 318 chest and abdominal CT cases at five U.S. sites against ground truth from three senior board-certified radiologists. The study reported observed AUC, sensitivity, specificity and notification-time results; its performance goals were thresholds and are kept separate from the observed values.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07
Reported sensitivity
95.11% (95% CI: 90.92%, 97.74%)
  • 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
93.28% (95% CI: 87.63%, 96.88%)
  • 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.

Study-level AUC (normalized from FDA-reported 97.6%)

0.976 proportion

  • EndpointROC discrimination for vertebral compression fractures
  • PopulationChest and abdominal CT cases from five U.S. clinical sites
  • Tested versionBriefCase vertebral-compression-fracture triage release reviewed in FDA submission K222692

Sensitivity

95.11 percent

  • EndpointDetection of suspected vertebral compression fractures
  • PopulationChest and abdominal CT cases from five U.S. clinical sites
  • Tested versionBriefCase vertebral-compression-fracture triage release reviewed in FDA submission K222692

Specificity

93.28 percent

  • EndpointExclusion of suspected vertebral compression fractures
  • PopulationChest and abdominal CT cases from five U.S. clinical sites
  • Tested versionBriefCase vertebral-compression-fracture triage release reviewed in FDA submission K222692

Mean time-to-notification

117.2 seconds

  • EndpointDICOM receipt, de-identification, cloud upload, analysis and desktop notification for a true-positive case
  • PopulationTrue-positive cases in the K222692 time-to-notification analysis
  • Tested versionBriefCase vertebral-compression-fracture triage release reviewed in FDA submission K222692

K222692 BriefCase VCFx pivotal study

  • DesignRetrospective, blinded, multicenter FDA submission study comparing BriefCase with ground truth from three senior board-certified radiologists.
  • Population318 chest and abdominal CT cases from five U.S.-based clinical sites; pivotal cases were distinct in time or center from training data.
  • Scopeexact submission
  • Tested versionBriefCase vertebral-compression-fracture triage release reviewed in FDA submission K222692
  • Samplen=318
  • Sites5
  • IndependenceIndependence not established

K222692

The FDA summary reports the study and vendor submission; independent-investigator status was not established.

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
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

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 and de-identified DICOM chest and abdominal CT images, received, saved and processed chronologically by series.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-07 · FDA 510(k) decision summary K222692: BriefCase VCFx triage

  2. Routing

    Source context, not route validation: Uses PACS and radiology-workstation workflow with DICOM acquisition, filtered/de-identified transfer to cloud processing, and a desktop feed/non-diagnostic viewer that sends the clinician back to local PACS for full-image review.

    Scope: Exact FDA submission.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-07 · FDA 510(k) decision summary K222692: BriefCase VCFx triage

  3. AI processing

    Source context, not route validation: The exact FDA description uses an Aidoc Hospital Server/Orchestrator for acquisition, an Aidoc Cloud Server for processing and an Aidoc Desktop Application for workflow integration; the described server stack includes a DICOM module and de-identification before cloud processing.

    Scope: Exact FDA submission. This is the submission-era architecture; current tenant, hosting, security and contract terms require vendor confirmation.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-07 · FDA 510(k) decision summary K222692: BriefCase VCFx triage

  4. Returned objects

    Source context, not route validation: A desktop feed notification for a suspected VCFx case and a compressed, low-quality, grayscale, unannotated preview captioned for prioritization only; 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.

    Field checked 2026-09-07 · FDA 510(k) decision summary K222692: BriefCase VCFx triage

  5. Viewer/worklist/report

    Unresolved route: A desktop feed notification for a suspected VCFx case and a compressed, low-quality, grayscale, unannotated preview captioned for prioritization only; 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.

    Field checked 2026-09-07 · FDA 510(k) decision summary K222692: BriefCase VCFx 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 description uses an Aidoc Hospital Server/Orchestrator for acquisition, an Aidoc Cloud Server for processing and an Aidoc Desktop Application for workflow integration; the described server stack includes a DICOM module and de-identification before cloud processing.
  • Exact FDA submission
  • Checked 2026-09-07

This is the submission-era architecture; current tenant, hosting, security and contract terms require vendor confirmation.

Integration
Uses PACS and radiology-workstation workflow with DICOM acquisition, filtered/de-identified transfer to cloud processing, and a desktop feed/non-diagnostic viewer that sends the clinician back to local PACS for full-image review.
  • Exact FDA submission
  • Checked 2026-09-07
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.

Exact DICOM triage and cloud-processing path

The exact FDA record describes Aidoc Hospital Server acquisition, de-identification and filtering, Aidoc Cloud Server processing, and a desktop feed/non-diagnostic viewer that prompts review of original images in local PACS.

exact submission · checked 2026-09-07

Current Aidoc VCF family workflow

Aidoc's current neuro solution page lists vertebral compression fractures among CT algorithms in its Full Brain AI Solution and describes facility-level CT processing with deep integration and aiOS orchestration.

product family · checked 2026-09-07

Current family platform context does not establish the exact K222692 release, configuration or contractual interfaces.

Current Aidoc workstation and enterprise integrations

Aidoc's current radiology platform page describes a workstation Widget with key images and AI-result summaries, direct worklist marking, and integrations with PACS, EHR, scheduling and reporting.

product family · checked 2026-09-07

Family-level buyer workflow context only; exact K222692 compatibility requires site and vendor confirmation.

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
K222692
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07
Anatomy
Chest/Lung
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07

The exact indication covers chest and abdominal CT; the controlled directory anatomy is normalized to Chest/Lung.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-12-05
  • 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.

Human reviewedStatus
2026-09-07Last searched
26Fields reviewed
13Source classes checked
20Screened PubMed leads
6Screened trial leads
0Unreviewed FDA recall leads

The stored PubMed and ClinicalTrials candidate metadata were screened in the exact stored order; this was metadata triage, not full-text paper or registry-record review, and no candidate was promoted. The stored recall query returned no records, so no event was promoted and no absence claim is made. The current discovery snapshot contains 20 PubMed and 6 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, vendor clinical study, vendor press release, literature index, trial registry, stored candidate metadata, stored recall candidates, 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-07 - Exact FDA submission

    No public exact-submission price or procurement terms were reviewed.

  • 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-10-26 - Exact FDA submission

    Bounded web search on 2026-10-26 (query: "Aidoc BriefCase reimbursement NTAP CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. Aidoc's 2026-08-13 release announces a Medicare NTAP for CARE Body CT Multi-Triage; it does not name this product or clearance. This records what was found, not that none exists; eligibility depends on 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-10-27 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

10 sources - 3 history items

Source ledger

  1. K222692 FDA decision source

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

    Scope: regulatoryIdentity, purpose, modality, anatomy

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. BriefCase-Vertebral Compression Fracture Triage model card (K222692)

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

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

  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. FDA 510(k) decision summary K222692: BriefCase VCFx triage

    U.S. Food and Drug Administration - Published 2022-12-05 - Accessed 2026-09-07

    Scope: identity, clinicalUse, purpose, modality, anatomy, input, output, limitations, deployment, integration, evidenceSummary, evidenceMetrics, evidenceStudies

  8. Aidoc radiology platform and workflow integrations

    Aidoc - Accessed 2026-09-07

    Scope: product_family, workflow, PACS_integration, EHR_integration, worklist, implementationCapabilities

  9. Aidoc neuro AI solution and vertebral compression fracture workflow

    Aidoc - Accessed 2026-09-07

    Scope: product_family, vertebral_compression_fracture, CT_workflow, PACS_integration, implementationCapabilities

  10. Aidoc Security & Privacy

    Aidoc Medical - Accessed 2026-10-25

    Scope: security

Research history

  1. K222692 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K230020

BriefCase

Aidoc Medical, Ltd.

Authorized purpose: Chest CT (with or without contrast) triage and notification for suspected three or more acute rib fractures in adults or transitional adolescents age 18 or older; notifications are non-diagnostic and clinicians review the original study.

Modality
CT/CTA
Anatomy
Chest/Lung
Decision
2023-02-01
FDA-cleared K242919

V5med Lung AI

V5med Inc.

Authorized purpose: V5med Lung AI provides concurrent-read adjunctive notification of suspected pulmonary nodules on chest CT; it does not replace radiologist judgment, diagnostic processes, or review of original CT series.

Modality
CT/CTA
Anatomy
Chest/Lung
Decision
2025-03-27
FDA-cleared K222277

BriefCase

Aidoc Medical, Ltd.

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.

Modality
CT/CTA
Anatomy
Chest/Lung
Decision
2022-08-26

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