Authorized purpose: BriefCase analyzes supported noncontrast head CT, head CTA, noncontrast cervical-spine CT, and CTPA examinations to triage suspected intracranial hemorrhage, large-vessel occlusion, cervical-spine fracture-related findings, and pulmonary embolism-related findings for trained professional review.
Clinical role
Case-level triage, notification, and worklist prioritization for supported CT studies.
Keep in mind: BriefCase is a triage and notification aid, not a standalone diagnosis or rule-out system. Professionals must review the complete source study and follow standard of care; exact indication, acquisition, and single-energy CTPA limits apply.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: BriefCase analyzes supported noncontrast head CT, head CTA, noncontrast cervical-spine CT, and CTPA examinations to triage suspected intracranial hemorrhage, large-vessel occlusion, cervical-spine fracture-related findings, and pulmonary embolism-related findings for trained professional review.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Adult head, brain, cervical spine, pulmonary arteries, and thorax Input: Supported DICOM CT and CTA examinations received through the hospital imaging network.
Who uses it?Intended users: Appropriately trained medical specialists in hospital networks.
What does the software produce?Output: Case-level notifications, worklist priority, and compressed previews or findings for professional review; original images are not replaced.
What is its most important limitation?Key limitation: BriefCase is a triage and notification aid, not a standalone diagnosis or rule-out system. Professionals must review the complete source study and follow standard of care; exact indication, acquisition, and single-energy CTPA limits apply.
Clinical takeaway. Clinical role: BriefCase analyzes supported noncontrast head CT, head CTA, noncontrast cervical-spine CT, and CTPA examinations to triage suspected intracranial hemorrhage, large-vessel occlusion, cervical-spine fracture-related findings, and pulmonary embolism-related findings for trained professional review.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports that performance data was not needed to support this modification to BriefCase, which broadens the intended use population from radiologists to appropriately trained medical specialists; each 510(k) summary in the document refers to the earlier BriefCase 510(k) summary for the data used to support initial clearance. 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 supported noncontrast head CT, head CTA, noncontrast cervical-spine CT, and CTPA examinations to triage suspected intracranial hemorrhage, large-vessel occlusion, cervical-spine fracture-related findings, and pulmonary embolism-related findings for trained professional review.
BriefCase is a triage and notification aid, not a standalone diagnosis or rule-out system. Professionals must review the complete source study and follow standard of care; exact indication, acquisition, and single-energy CTPA limits apply.
The exact FDA document reports that performance data was not needed to support this modification to BriefCase, which broadens the intended use population from radiologists to appropriately trained medical specialists; each 510(k) summary in the document refers to the earlier BriefCase 510(k) summary for the data used to support initial clearance. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Performance data was not needed to support this modification to BriefCase. The 510(k) Summary for K190896 describes the data that was used to support initial clearance of BriefCase." … "The only difference is that the subject device has a broadened intended use population of appropriately trained medical specialists, whereas the predicate device is indicated for use by radiologists.". Read from the exact FDA decision document on 2026-11-14.
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 that performance data was not needed to support this modification to BriefCase, which broadens the intended use population from radiologists to appropriately trained medical specialists; each 510(k) summary in the document refers to the earlier BriefCase 510(k) summary for the data used to support initial clearance. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Performance data was not needed to support this modification to BriefCase. The 510(k) Summary for K190896 describes the data that was used to support initial clearance of BriefCase." … "The only difference is that the subject device has a broadened intended use population of appropriately trained medical specialists, whereas the predicate device is indicated for use by radiologists.". Read from the exact FDA decision document on 2026-11-14.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K203508 FDA evidence package for BriefCase
DesignFDA 510(k) decision evidence and product verification for the exact submission.
PopulationAdult head, brain, cervical spine, pulmonary arteries, and thorax
Scopeexact submission
Tested versionBriefCase
IndependenceSponsor or vendor study
K203508
FDA-submitted evidence for the exact decision; it is not independent clinical validation and does not establish local production qualification.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
No record matched K203508 by exact native submission identifier in the 2026-09-02 openFDA snapshot; this does not exclude product-family, later-version, or adverse-event information.
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: Supported DICOM CT and CTA examinations received through the hospital imaging network.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes an Aidoc Health Solutions platform, Aidoc Cloud Server, and desktop Worklist receiving, filtering, de-identifying, and returning DICOM-based notifications in a hospital network.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA package describes an Aidoc Cloud Server plus desktop Worklist and hospital-network workflow; current hosting responsibility, security, availability, and site configuration remain unknown.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Case-level notifications, worklist priority, and compressed previews or findings for professional review; original images are not replaced.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Case-level notifications, worklist priority, and compressed previews or findings for professional review; original images are not replaced.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
The FDA package describes an Aidoc Cloud Server plus desktop Worklist and hospital-network workflow; current hosting responsibility, security, availability, and site configuration remain unknown.
The FDA package describes an Aidoc Health Solutions platform, Aidoc Cloud Server, and desktop Worklist receiving, filtering, de-identifying, and returning DICOM-based notifications in a hospital network.
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.
Use by appropriately trained medical specialists in hospital networks. Follow the exact labeling, local training, supervision, and escalation requirements.
The FDA package describes an Aidoc Cloud Server plus desktop Worklist and hospital-network workflow; current hosting responsibility, security, availability, and site configuration remain unknown.
The FDA package describes an Aidoc Health Solutions platform, Aidoc Cloud Server, and desktop Worklist receiving, filtering, de-identifying, and returning DICOM-based notifications in a hospital network.
Monitor labeling, software version, complaints, recalls, failed inputs, overrides, and postmarket signals against the exact submission and installed configuration.
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-04Last searched
27Fields reviewed
12Source classes checked
20Screened PubMed leads
6Screened trial leads
0Unreviewed FDA recall leads
No evidence was promoted. PMID 41444826 names Aidoc Medical Briefcase ICH Triage but omits the tested software version and K203508; all remaining records are unrelated briefcase alias matches or unrelated trials. 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, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not publicly available - checked 2026-09-04 - Exact FDA submission
No public list price or commercial contract for the exact submission and version was identified.
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-04 - Exact FDA submission
No exact-product payer coverage or reimbursement determination was identified in reviewed public material.
qER is a radiological computer aided triage and notification software indicated for use in the analysis of non-contrast head CT images. The device is intended to assist hospital networks and trained medical specialists in workflow triage by flagging the following suspected positive findings of pathologies in head CT images: intracranial hemorrhage, mass effect, midline shift and cranial fracture. qER uses an artificial intelligence algorithm to analyze images on a Stand-Alone Performance cloud-based application in parallel to the ongoing standard of care image interpretation.
Authorized purpose: BriefCase is a radiological computer aided triage and notification software indicated for use in the analysis of non-enhanced CT and CTPA images. The device is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive findings of Intracranial Hemorrhage and Pulmonary Embolism pathologies. For the PE pathology, the software is only intended to be used on single-energy exams.
Authorized purpose: Notification-only triage of adult non-contrast head CT for suspected intracranial hemorrhage and large-vessel occlusion, with parallel communication to trained clinicians during standard care.
Modality
CT/CTA
Anatomy
Brain and intracranial vessels: intracranial hemorrhage and LVO involving ICA, MCA-M1, and MCA-M2
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
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.