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 role
Triage or notification support
Images and patients
CT/CTA · Brain
Key limitation
Scanner manufacturers: All
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyCT/CTA · Brain
Workflow roleTriage or notification support
Required inputCT/CTA images or data involving Brain; consult the FDA labeling for exact protocol, series, and quality requirements.
Output and human actionHALO sends a notification email to the specialist identifying the study of interest if a pattern suggestive of an intracranial Large Vessel Occlusion (LVO) of the anterior circulation (ICA, M1 or M2) has been identified. Additionally, the device provides the user with a link to a DICOM Web viewer allowing users to review the images remotely.
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
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.
HALO sends a notification email to the specialist identifying the study of interest if a pattern suggestive of an intracranial Large Vessel Occlusion (LVO) of the anterior circulation (ICA, M1 or M2) has been identified. Additionally, the device provides the user with a link to a DICOM Web viewer allowing users to review the images remotely.
Exact FDA submission
Checked 2026-09-01
Clinical output reported in the exact-submission ACR model card.
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.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
HALO regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K211788
Samplen=427
IndependenceIndependence not established
K211788
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The exact-identifier FDA recall query returned no native recall record for K211788. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: CT/CTA images or data involving Brain; consult the FDA labeling for exact protocol, series, and quality requirements.
Scope: Exact FDA submission. Conservative normalization of explicit wording in an exact-submission source.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: HALO sends a notification email to the specialist identifying the study of interest if a pattern suggestive of an intracranial Large Vessel Occlusion (LVO) of the anterior circulation (ICA, M1 or M2) has been identified. Additionally, the device provides the user with a link to a DICOM Web viewer allowing users to review the images remotely.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: HALO sends a notification email to the specialist identifying the study of interest if a pattern suggestive of an intracranial Large Vessel Occlusion (LVO) of the anterior circulation (ICA, M1 or M2) has been identified. Additionally, the device provides the user with a link to a DICOM Web viewer allowing users to review the images remotely.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
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.
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 FDA submission
Checked 2026-09-01
Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Cloud-based deployment is explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require 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.
Exact FDA record reviewedStatus
2026-09-08Last searched
24Fields reviewed
9Source classes checked
20Awaiting review PubMed leads
10Awaiting review trial leads
0Unreviewed FDA recall leads
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
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.
Care setting: Not yet reviewed - checked 2026-08-31 - Exact FDA submission
Confirm the intended care setting, patient population, and service line.
Public pricing: Not verified - checked 2026-09-08 - Exact FDA submission
No public price or quote for the exact K211788 configuration 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 publicly available - checked 2026-09-08 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by 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
Security: Not verified - checked 2026-09-08 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: 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 and sends PACS and/or specialist notifications in parallel to standard care; previews are informational and not diagnostic.
Authorized purpose: 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 clinicians for workflow triage; notifications are informational and not diagnostic.
Authorized purpose: 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 workflow triage via PACS and/or notifications; previews are informational, not diagnostic, and a negative notification does not rule out LVO or replace CTA/standard 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.