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.
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: 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.
Computer-aided triage and notification: a suspect case appears in a desktop feed with an unannotated compressed preview while the original PACS workflow continues.
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.
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.
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.
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.
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 & contractsPublic price, contract terms, and reimbursement
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 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.
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.
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.
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.
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.
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 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.
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.
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.
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.
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 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.
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.
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.
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.
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.
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.