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
Nico.Lab B.V.
HALO is a notification only cloud-based image processing software application using artificial intelligence algorithms to analyze patient imaging data in parallel to the standard of care imaging interpretation. Its intended use is to identify suggestive imaging patterns of a pre-specified clinical condition and to directly notify an appropriate medical specialist. HALO's indication is to facilitate the evaluation of the brain vasculature on patients suspected of stroke by processing and analyzing CT angiograms of the brain acquired in an acute setting. After completion of the data analysis, HALO sends a notification if a pattern suggestive for a suspected intracranial Large Vessel Occlusion (LVO) of the anterior circulation (ICA,MI or M2) has been identified an image. The intended users of HALO are defined as medical specialists or a team of specialists that are involved in the diagnosis and care of stroke patients at emergency departments or other department where stroke patients are administered. They include physicians such as neurologists, radiologists, and/or other emergency department physicians. HALO's output should not be used for primary diagnosis or clinical decisions; the final diagnosis is always decided upon by the medical specialist. HALO is indicated for CT scanners from GE Healthcare and Philips.
Clinical fit
Start with the authorized purpose, then verify how it fits your service line and reading workflow.
Intended-user text reported in the exact-submission ACR model card.
Confirm the intended care setting, patient population, and service line.
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.
Limitations and supported-acquisition details reported in the exact-submission ACR model card.
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.
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.
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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 deployment is 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-01Scanner manufacturers: All
exact submission · checked 2026-09-01Confirm currently supported software versions, protocols, and site-specific acquisition configurations.
ACR AI Central provides an exact-submission model card for HALO; FDA labeling remains controlling for clinical use, limitations, and performance.
exact submission · checked 2026-09-08Evidence
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.
Stand-Alone Performance · Population described in the exact-submission ACR model card
exact submission · Tested version: Exact product version not reported; regulatory study summarized for FDA submission K211788 · n=427 · Independence not establishedK211788
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.
No public price or quote for the exact K211788 configuration was established in this review.
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Safety and lifecycle
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
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. Exact FDA scope controls clinical claims. ACR and official vendor material provide bounded catalog or product-family context. Candidate literature metadata remains a discovery queue until full-text identity, endpoint, population, and version review is completed. Automated exact-name discovery found 20 PubMed and 10 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, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall
Sources
Sources accessed through 2026-09-08.
Alternatives
Methinks Software S.L.
Methinks CTA Stroke analyzes acute-setting brain CT angiography in adults over 21 with suspected stroke for suspected large-vessel occlusion in the terminal ICA, MCA-M1, or MCA-M2...
iSchemaView
Rapid CTA 360 analyzes adult head CTA DICOM images to flag suspected large- and medium-vessel occlusion in specified intracranial and vertebral segments and notify trained...
Methinks Software S.L.
Methinks NCCT Stroke analyzes adult non-contrast head CT to flag suspected intracranial hemorrhage and suspected large-vessel occlusion of the ICA, MCA-M1, or MCA-M2 for parallel...
JLK, Inc.
Notification-only triage of suspected intracranial hemorrhage on non-contrast head CT