Authorized purpose: HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; 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 · Brain
Key limitation
Keep in mind: Input protocol, contrast, anatomy, model, software version, output review, and local integration limits are release-specific. HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; the output is not a primary diagnosis.
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: HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; the output is not a primary diagnosis.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain 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. HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; the output is not a primary diagnosis.
Clinical takeaway. Clinical role: HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; the output is not a primary diagnosis.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports non-clinical software testing and a retrospective multi-center clinical study in a consecutive patient cohort admitted to US comprehensive stroke centers, with ground truth by an expert panel of 3 neuro radiologists. For the primary endpoint, LVO detection sensitivity was 91.1% (95% CI 86.0%-94.8%) and specificity 87.0% (95% CI 81.2%-91.5%), with AUC 0.97; median notification time for detected LVO cases was 4 minutes 31 seconds. 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
HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; the output is not a primary diagnosis.
Input protocol, contrast, anatomy, model, software version, output review, and local integration limits are release-specific. HALO analyzes contrast-enhanced brain CTA in the acute setting for suspected anterior-circulation large-vessel occlusion and provides notification support for emergency stroke specialists; the output is not a primary diagnosis.
The exact FDA document reports non-clinical software testing and a retrospective multi-center clinical study in a consecutive patient cohort admitted to US comprehensive stroke centers, with ground truth by an expert panel of 3 neuro radiologists. For the primary endpoint, LVO detection sensitivity was 91.1% (95% CI 86.0%-94.8%) and specificity 87.0% (95% CI 81.2%-91.5%), with AUC 0.97; median notification time for detected LVO cases was 4 minutes 31 seconds. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-Clinical software testing has been performed in accordance with the" … "In a multi-center clinical study, the performance of the HALO clinical". 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 non-clinical software testing and a retrospective multi-center clinical study in a consecutive patient cohort admitted to US comprehensive stroke centers, with ground truth by an expert panel of 3 neuro radiologists. For the primary endpoint, LVO detection sensitivity was 91.1% (95% CI 86.0%-94.8%) and specificity 87.0% (95% CI 81.2%-91.5%), with AUC 0.97; median notification time for detected LVO cases was 4 minutes 31 seconds. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-Clinical software testing has been performed in accordance with the" … "In a multi-center clinical study, the performance of the HALO clinical". Read from the exact FDA decision document on 2026-11-14.
Standalone sensitivity for LVO detection in a retrospective multi-center consecutive cohort from US comprehensive stroke centers: 91.1% (95% CI 86.0%-94.8%).
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "For the primary endpoint: calculation of the performance of the HALO algorithm showed a sensitivity and specificity for LVO detection of respectively 91.1% (95% CI, 86.0%-94.8%) and 87.0% (95% CI, 81.2%- 91.5%)." … "In a multi-center clinical study, the performance of the HALO clinical". Read from the exact FDA decision document on 2026-11-14; this is the submission-reported standalone result, not independent validation.
Standalone specificity for LVO detection in a retrospective multi-center consecutive cohort from US comprehensive stroke centers: 87.0% (95% CI 81.2%-91.5%).
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "For the primary endpoint: calculation of the performance of the HALO algorithm showed a sensitivity and specificity for LVO detection of respectively 91.1% (95% CI, 86.0%-94.8%) and 87.0% (95% CI, 81.2%- 91.5%)." … "In a multi-center clinical study, the performance of the HALO clinical". 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 K200873
DesignRegulatory verification, validation, and labeling evidence reviewed for exact FDA submission K200873.
PopulationThe labeled population and test materials for exact submission K200873; a general clinical study population is not established here.
Scopeexact submission
Tested versionHALO (K200873)
IndependenceSponsor or vendor study
K200873
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 & contractsPublic price, contract terms, and reimbursement
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 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.
Source context, not route validation: The exact FDA package describes a copy of the original CTA images being sent to HALO cloud servers, a notification to a specialist, and remote review of results in a compatible DICOM web viewer. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "A copy of the original CTA images is sent to HALO cloud servers for automatic image processing." … "After analyzing the images, HALO sends a notification regarding a suspected finding to a specialist, recommending review of these images. The specialist can review the results remotely in a compatible DICOM web viewer.". 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.
Source context, not route validation: The exact FDA package describes a cloud-based tool in which a copy of the original CTA images is sent to HALO cloud servers for automatic image processing. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "HALO is a notification only, cloud-based clinical support tool which identifies image features and communicates the analysis results to a specialist" … "A copy of the original CTA images is sent to HALO cloud servers for automatic image processing.". 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.
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.
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 exact FDA package describes a cloud-based tool in which a copy of the original CTA images is sent to HALO cloud servers for automatic image processing. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "HALO is a notification only, cloud-based clinical support tool which identifies image features and communicates the analysis results to a specialist" … "A copy of the original CTA images is sent to HALO cloud servers for automatic image processing.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes a copy of the original CTA images being sent to HALO cloud servers, a notification to a specialist, and remote review of results in a compatible DICOM web viewer. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "A copy of the original CTA images is sent to HALO cloud servers for automatic image processing." … "After analyzing the images, HALO sends a notification regarding a suspected finding to a specialist, recommending review of these images. The specialist can review the results remotely in a compatible DICOM web viewer.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Current vendor material is product-family context for K200873 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.
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-20Last searched
28Fields reviewed
14Source classes checked
20Screened PubMed leads
10Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 20 PubMed and 10 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 10 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
Security: Not publicly available - checked 2026-09-04 - Exact FDA submission
Public sources reviewed here do not establish the complete exact-release security posture, including identity, audit, encryption, retention, remote access, vulnerability management, backup, or incident response.
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.
Monitoring: Not verified - checked 2026-10-27 - 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.