FDA-cleared profile

HALO

NICo-Lab B.V. · CT/CTA · FDA-cleared (510(k))

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.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
CT image networking, processing, enhancement, triage, measurement, or professional workflow support.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported CT or CTA DICOM images and the metadata required by the exact release-specific processing workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Processed CT image objects, measurements, notifications, or worklist outputs for professional review.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Radiology workstations, connected imaging environments, or other exact-release CT-processing workflows.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Qualified radiologists and other trained imaging professionals.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
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.
  • Exact FDA submission
  • Checked 2026-09-04
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.
  • 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.

Evidence

Performance evidence

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.

Reported sensitivity
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.

Reported specificity
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 & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. 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.

    Field checked 2026-09-04 · FDA decision summary for K200873 - HALO

  2. Routing

    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.

    Field checked 2026-11-14 · FDA decision summary for K200873 - HALO

  3. AI processing

    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.

    Field checked 2026-11-14 · FDA decision summary for K200873 - HALO

  4. Returned objects

    Source context, not route validation: Processed CT image objects, measurements, notifications, or worklist outputs for professional review.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA decision summary for K200873 - HALO

  5. Viewer/worklist/report

    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.

    Field checked 2026-09-04 · FDA decision summary for K200873 - HALO

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
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.

Integration
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.

Workflow role

CT image networking, processing, enhancement, triage, measurement, or professional workflow support.

exact submission · checked 2026-09-04

This is a submission-anchored intended-use summary, not a local acceptance result.

Input

Supported CT or CTA DICOM images and the metadata required by the exact release-specific processing workflow.

exact submission · checked 2026-09-04

Exact supported inputs and protocol limits must be confirmed from the complete labeling.

Output

Processed CT image objects, measurements, notifications, or worklist outputs for professional review.

exact submission · checked 2026-09-04

Output review, editing, and downstream use remain release- and site-specific.

Vendor family context

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.

Site validation status

Exact local interfaces, deployment topology, security controls, downtime behavior, and support obligations remain unestablished.

exact submission · checked 2026-09-04

Obtain organization-specific implementation evidence before procurement or clinical use.

Sources & review details FDA 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.

FDA submission
K200873
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Brain
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-11-20
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

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.

13 sources - 3 history items

Source ledger

  1. FDA decision summary for K200873 - HALO

    U.S. Food and Drug Administration - Published 2020-11-20 - Accessed 2026-09-04

    Scope: regulatoryIdentity, productIdentity, indication, modality, anatomy, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. HALO model card (K200873)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  8. NICO.LAB HALO family context

    NICO.LAB - Accessed 2026-09-04

    Scope: productFamilyContext, workflowRole, implementationCapabilities

  9. A pulse-chasable reporter processing assay for mammalian autophagic flux with HaloTag.

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  10. Halo angiokeratoma.

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  11. Halo Brace.

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  12. Pilot Study to evaluateThrombomodulin to Rule Out Giant Cell Arteritis (GCA) in Polymyalgia Rheumatica (PMR) Patients. (THROPIQ)

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  13. Association of Ultrasonographic Temporal Artery Lesions and Relapse in Patients With Giant Cell Arteritis

    U.S. National Library of Medicine - Accessed 2026-09-04

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

Research history

  1. K200873 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K251590

Methinks CTA Stroke

Methinks Software S.L.

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-08-20
FDA-cleared K251151

Rapid CTA 360

iSchemaView

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-07-16
FDA-cleared K250685

Methinks NCCT Stroke

Methinks Software S.L.

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-06-16

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history