FDA-cleared profile

BriefCase

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

Authorized purpose: BriefCase analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.

Clinical role
CT image networking, processing, enhancement, triage, measurement, or professional workflow support.
Images and patients
CT/CTA · Chest/Lung
Key limitation
Keep in mind: Input protocol, contrast, anatomy, model, software version, output review, and local integration limits are release-specific. BriefCase analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.

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: BriefCase analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest/Lung Input: Supported CT or CTA DICOM images and the metadata required by the exact release-specific processing workflow.
  • Who uses it?Intended users: Qualified radiologists and other trained imaging professionals.
  • What does the software produce?Output: Processed CT image objects, measurements, notifications, or worklist outputs for professional review.
  • What is its most important limitation?Key limitation: Input protocol, contrast, anatomy, model, software version, output review, and local integration limits are release-specific. BriefCase analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.

Clinical takeaway. Clinical role: BriefCase analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports a retrospective, blinded, multicenter study of 268 contrast-enhanced chest CTs (74 positive, 194 negative) from 2 US sites for incidental pulmonary embolism: sensitivity 90.5% (95% CI: 81.4%, 96.2%) and specificity 88.7% (95% CI: 83.3%, 92.8%). In 63 true positive cases, time-to-notification was 4.7 minutes versus 223.3 minutes for standard-of-care time-to-exam-open. Results are as reported in the FDA submission, not independent validation.

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 analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
CT image networking, processing, enhancement, triage, measurement, or professional workflow support.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported CT or CTA DICOM images and the metadata required by the exact release-specific processing workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Processed CT image objects, measurements, notifications, or worklist outputs for professional review.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Radiology workstations, connected imaging environments, or other exact-release CT-processing workflows.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Qualified radiologists and other trained imaging professionals.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
Input protocol, contrast, anatomy, model, software version, output review, and local integration limits are release-specific. BriefCase analyzes contrast-enhanced chest CT for suspected pulmonary embolism and notifies or prioritizes the study in the labeled hospital or cloud worklist workflow; the output is not a primary diagnosis.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports a retrospective, blinded, multicenter study of 268 contrast-enhanced chest CTs (74 positive, 194 negative) from 2 US sites for incidental pulmonary embolism: sensitivity 90.5% (95% CI: 81.4%, 96.2%) and specificity 88.7% (95% CI: 83.3%, 92.8%). In 63 true positive cases, time-to-notification was 4.7 minutes versus 223.3 minutes for standard-of-care time-to-exam-open. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software with the primary endpoint to evaluate the software’s performance in identifying Contrast-enhanced chest CTs (but not dedicated CTPA protocol), containing Incidental Pulmonary Embolism in 268 cases from 2 clinical study sites in the US." … "There were 74 positive cases and 194 negative cases (images with iPE versus without iPE) included in the analysis.". Read from the exact FDA decision document on 2026-11-14.

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
The exact FDA document reports a retrospective, blinded, multicenter study of 268 contrast-enhanced chest CTs (74 positive, 194 negative) from 2 US sites for incidental pulmonary embolism: sensitivity 90.5% (95% CI: 81.4%, 96.2%) and specificity 88.7% (95% CI: 83.3%, 92.8%). In 63 true positive cases, time-to-notification was 4.7 minutes versus 223.3 minutes for standard-of-care time-to-exam-open. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software with the primary endpoint to evaluate the software’s performance in identifying Contrast-enhanced chest CTs (but not dedicated CTPA protocol), containing Incidental Pulmonary Embolism in 268 cases from 2 clinical study sites in the US." … "There were 74 positive cases and 194 negative cases (images with iPE versus without iPE) included in the analysis.". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Standalone sensitivity for incidental pulmonary embolism on 268 contrast-enhanced chest CTs from 2 US sites: 90.5% (95% CI 81.4%-96.2%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software with the primary endpoint to evaluate the software’s performance in identifying Contrast-enhanced chest CTs (but not dedicated CTPA protocol), containing Incidental Pulmonary Embolism in 268 cases from 2 clinical study sites in the US." … "Specifically, sensitivity was 90.5% (95% CI: 81.4%, 96.2%) and specificity was 88.7% (95% CI: 83.3%, 92.8%).". Read from the exact FDA decision document on 2026-11-14; this is the submission-reported standalone result, not independent validation.

Reported specificity
Standalone specificity for incidental pulmonary embolism on 268 contrast-enhanced chest CTs from 2 US sites: 88.7% (95% CI 83.3%-92.8%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Aidoc conducted a retrospective, blinded, multicenter study with the BriefCase software with the primary endpoint to evaluate the software’s performance in identifying Contrast-enhanced chest CTs (but not dedicated CTPA protocol), containing Incidental Pulmonary Embolism in 268 cases from 2 clinical study sites in the US." … "Specifically, sensitivity was 90.5% (95% CI: 81.4%, 96.2%) and specificity was 88.7% (95% CI: 83.3%, 92.8%).". Read from the exact FDA decision document on 2026-11-14; this is the submission-reported standalone result, not independent validation.

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

FDA submission-specific verification and validation evidence for K201020

  • DesignRegulatory verification, validation, and labeling evidence reviewed for exact FDA submission K201020.
  • PopulationThe labeled population and test materials for exact submission K201020; a general clinical study population is not established here.
  • Scopeexact submission
  • Tested versionBriefCase (K201020)
  • IndependenceSponsor or vendor study

K201020

FDA regulatory evidence is submission-specific but is not independent clinical performance evidence.

5 unlinked candidate evidence records are retained for source review and excluded from this evidence display.

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: Supported CT or CTA DICOM images and the metadata required by the exact release-specific processing workflow.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA decision summary for K201020 - BriefCase

  2. Routing

    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." … "The software then flags suspect cases by sending notifications to the Worklist desktop application, thereby prompting preemptive triage and prioritization by the attending radiologist.". 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 decision summary for K201020 - BriefCase

  3. AI processing

    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.

    Field checked 2026-11-14 · FDA decision summary for K201020 - BriefCase

  4. Returned objects

    Source context, not route validation: Processed CT image objects, measurements, notifications, or worklist outputs for professional review.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA decision summary for K201020 - BriefCase

  5. Viewer/worklist/report

    Unresolved route: Processed CT image objects, measurements, notifications, or worklist outputs for professional review.

    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-04 · FDA decision summary for K201020 - BriefCase

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

Integration
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." … "The software then flags suspect cases by sending notifications to the Worklist desktop application, thereby prompting preemptive triage and prioritization by the attending radiologist.". 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.

Workflow role

CT image networking, processing, enhancement, triage, measurement, or professional workflow support.

exact submission · checked 2026-09-04

This is a submission-anchored intended-use summary, not a local acceptance result.

Input

Supported CT or CTA DICOM images and the metadata required by the exact release-specific processing workflow.

exact submission · checked 2026-09-04

Exact supported inputs and protocol limits must be confirmed from the complete labeling.

Output

Processed CT image objects, measurements, notifications, or worklist outputs for professional review.

exact submission · checked 2026-09-04

Output review, editing, and downstream use remain release- and site-specific.

Vendor family context

Current vendor material is product-family context for K201020 only; exact release, enabled options, deployment, and local interoperability require confirmation.

product family · checked 2026-09-04

Vendor material is not exact-release evidence unless that linkage is separately proven.

Site validation status

Exact local interfaces, deployment topology, security controls, downtime behavior, and support obligations remain unestablished.

exact submission · checked 2026-09-04

Obtain organization-specific implementation evidence before procurement or clinical use.

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
K201020
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Chest/Lung
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-08-26
  • 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
28Fields reviewed
14Source classes checked
20Screened PubMed leads
6Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 20 PubMed and 6 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. 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, implementation documentation, reimbursement policy, peer reviewed literature, clinical trial registry, 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 publicly available - checked 2026-09-04 - Exact FDA submission

    No public exact-release price, license fee, subscription, contract, or implementation cost 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 applicable - checked 2026-09-04 - Not applicable

    CMS index context was checked, but no product-specific coverage or reimbursement determination is inferred.

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

14 sources - 3 history items

Source ledger

  1. FDA decision summary for K201020 - BriefCase

    U.S. Food and Drug Administration - Published 2020-08-26 - Accessed 2026-09-04

    Scope: regulatoryIdentity, productIdentity, indication, modality, anatomy, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. BriefCase model card (K201020)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

  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. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  8. Aidoc BriefCase family context

    Aidoc - Accessed 2026-09-04

    Scope: productFamilyContext, workflowRole, implementationCapabilities

  9. Myocardial ischemic effects of isometric, dynamic and combined exercise in coronary artery disease.

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

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  10. The Briefcase She Carried.

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

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  11. Real-world performance evaluation of a commercial deep learning model for intracranial hemorrhage detection.

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

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  12. Integral Clinical Plan Shared With or Without Telemonitoring of Constants in Patient With Chronic Diseases

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

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  13. PRP Versus Saline in Lateral Epicondylitis

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

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  14. Aidoc Security & Privacy

    Aidoc Medical - Accessed 2026-10-25

    Scope: security

Research history

  1. K201020 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 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
FDA-cleared K213886

BriefCase

Aidoc Medical, Ltd.

Authorized purpose: BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of contrast-enhanced chest CTs (not dedicated CTPA protocol) in adults or transitional adolescents age 18 and older. The device is intended to assist hospital networks and appropriately trained medical specialists in workflow triage by flagging and communication of suspect cases of incidental Pulmonary Embolism (iPE) pathologies. The device is intended to be used on single energy exams only. Briefcase uses an artificial intelligence algorithm to analyze images and flag suspect cases on a Stand-Alone Performance desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for suspect cases. 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 tobe 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-04-26
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

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