Input or output interoperability
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
FDA-cleared profile
Brainomix Limited
Brainomix 360 Triage Stroke is a radiological computer aided triage and notification software indicated for use in the analysis of non-contrast head CT (NCCT) images to assist hospital networks and trained clinicians in workflow triage by flagging and communicating suspected positive findings of head NCCT images for large vessel occlusion (LVO) of the intracranial ICA and M1 and intracranial hemorrhage (ICH). Specifically, the device is intended to be used for the triage of images acquired from adult patients in the acute setting, within 24 hours of the onset of the acute symptoms, or where this is unclear, since last known well (LKW) time. It is not intended to detect isolated subarachnoid hemorrhage and symmetrical bilateral MCA occlusions. Brainomix 360 Triage Stroke uses an artificial intelligence algorithm to analyze images and highlight cases with detected NCCT LVO or ICH on the Brainomix server on premise or in the cloud in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected LVO or ICH findings via a web user interface or mobile application. Notifications include compressed preview images that are meant for informational purposes only and are not intended for diagnostic use beyond notification. The device does not alter the original medical image, and it is not intended to be used as a primary diagnostic device. The results of Brainomix 360 Triage Stroke are intended to be used in conjunction with other patient information and based on professional judgment to assist with triage/prioritization of medical images. Notified clinicians are ultimately responsible for reviewing full images per the standard of care.
Clinical fit
Start with the authorized purpose, then verify how it fits your service line and reading workflow.
Exact-submission indication text from the ACR AI Central model card. FDA labeling remains controlling.
Identify the intended clinical user and the human action expected after the output.
Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.
Conservative normalization of explicit wording in an exact-submission source.
Conservative normalization of explicit wording in an exact-submission source.
Clinical output reported in the exact-submission ACR model card.
Confirm contraindications, unsupported populations, scanners, protocols, and known failure modes.
Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
Imaging modality reported in the exact-submission ACR AI Central model card.
Anatomy normalized from explicit exact-submission ACR model-card wording.
Implementation
Use these fields to structure a vendor demo, security review, and implementation estimate.
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
FDA authorization does not establish the current commercial security posture. Request data-flow diagrams, hosting and retention details, access controls, audit logging, attestations, and incident-response documentation.
Training, onboarding, competency, and support commitments are commercial implementation details that require current vendor documentation.
Local acceptance testing, production monitoring, drift review, update control, and incident escalation require a current vendor and site-specific governance plan.
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
Cloud-based and on-premises deployment are explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
exact submission · checked 2026-09-01Evidence
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version.
Structured study metadata from the exact-submission ACR model card; this is not an independent evidence synthesis.
Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.
Model specificity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Regulatory performance study summarized by ACR AI Central · Adult
exact submission · Tested version: Exact product version not reported; regulatory study summarized for FDA submission K232496 · n=267 · Independence not establishedK232496
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Economics and lifecycle
These are common procurement questions; unknown values remain visible until a source supports them.
FDA submission materials do not establish current commercial pricing. Request the pricing unit, term, minimum commitment, implementation fees, and included support from the vendor.
Determine whether any product-specific CPT/HCPCS pathway exists and separate it from billing for the underlying imaging service.
Safety and lifecycle
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
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.
Buyer worksheet
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Automated exact-name discovery found 0 PubMed and 0 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, acr ai central product, pubmed, clinical trials, openfda device recall
Sources
Sources accessed through 2026-09-02.
Alternatives
AVICENNA.AI
CINA analyzes nonenhanced head CT for suspected intracranial hemorrhage and head CTA for suspected large-vessel occlusion for computer-aided triage and notification in parallel...
Mlhealth 360
FDA product code QAS identifies this device class as Radiological Computer-Assisted Triage And Notification Software. Radiological computer-assisted triage and notification...
Brainomix Limited
FDA product code QAS identifies this device class as Radiological Computer-Assisted Triage And Notification Software. Radiological computer-assisted triage and notification...
Methinks Software S.L.
FDA product code QAS identifies this device class as Radiological Computer-Assisted Triage And Notification Software. Radiological computer-assisted triage and notification...