Medscape Medical NewsAll articles

HALO

Nico.Lab B.V. • Radiology • 07/08/2021

510(k)IEC 62304 Class B
FDA Summary PDF

Device Purpose

HALO is an artificial intelligence-powered, cloud-based software designed to expedite the triage of potential stroke patients by analyzing CT angiograms of the brain for signs of Large Vessel Occlusion. The system operates by automatically processing images, identifying suggestive patterns, and rapidly notifying specialists to facilitate prompt review, without replacing the clinician's final diagnostic responsibility.

Summary

HALO is a cloud-based radiological computer-aided triage and notification software designed by Nico.Lab B.V. to assist medical specialists in the rapid evaluation of stroke patients. The system processes CT angiograms (CTA) of the brain using artificial intelligence algorithms to detect image patterns suggestive of intracranial Large Vessel Occlusion (LVO) in the anterior circulation. Original CTA images are transmitted to HALO's cloud servers for automated analysis, operating in parallel with standard care workflows. If a suspected LVO is identified, HALO sends a notification to a designated specialist, who can then remotely review the results via a DICOM web viewer, facilitating timely attention to potential stroke cases. The intended users of HALO are medical specialists such as neurologists, radiologists, and emergency department physicians involved in the diagnosis and care of stroke patients in acute settings. It is crucial to note that HALO's output is for notification and triage purposes only and should not be used for primary diagnosis or to make clinical decisions, as the final diagnosis remains the responsibility of the specialist. In a multi-center retrospective clinical study involving 287 patient scans, the HALO algorithm demonstrated a sensitivity of 90.1% and a specificity of 90.7% for LVO detection, with a median notification time of 1 minute and 4 seconds for positive cases. The system is compatible with CT scanners from GE Healthcare and Philips.

AI Regulatory Concerns

Powered byJev by TypeSafe AI

Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.

Keywords

Artificial IntelligenceStrokeLarge Vessel OcclusionCT AngiographyTriage SoftwareCloud-basedMedical ImagingNotification SystemNeuroradiologyAcute Care

Device Metadata

Submission Number
K211788
Company
Nico.Lab B.V.
Panel
Radiology
Product Code
N/A
Data Type
Images
Clinical Function
Assessment
AI Function
Analysis
AI Subclass
triage

Relevant Clinical Questions

  • Q1. How does the performance of the HALO AI algorithm vary with different CT scanner models from GE Healthcare and Philips, particularly regarding image quality and acquisition protocols?; What is the false positive notification rate in real-world clinical settings outside of a structured study, and what are the common characteristics of these false positives?; How does the integration of HALO into existing hospital IT infrastructures and PACS systems affect the overall workflow efficiency beyond just the notification time?; What specific AI architectural components or deep learning models are utilized by HALO, and how were they trained and validated to ensure generalizability across diverse patient populations?; Are there plans to expand HALO's capabilities to detect other critical neurological conditions or LVO in other circulations (e.g., posterior) visible on CTA scans?

Risk Classification

ESL Analysis
FDA Device ClassII

FDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Authorized before §524B enforcement

Learn how Parasoft automates IEC 62304 compliance testing →

Cybersecurity Evidence

Powered by SBOMator™

Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.

Cyber Score25/100
SBOM Evidence⚠ Not mentioned in summary
Cyber Risk Assessment⚠ Not mentioned in summary
Postmarket Plan✓ Detected in Summary
§524B ApplicableNo

Supply Chain BOM Evidence

Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.

SBOMSoftware Bill of Materials
- Not detected
ML-BOMMachine Learning Bill of Materials(deep learning, algorithm)
✓ Detected
SaaSBOMSoftware-as-a-Service Bill of Materials(cloud, server, remote, infrastructure)
✓ Detected
HBOMHardware Bill of Materials
- Not detected
CBOMCryptography Bill of Materials
- Not detected
VDR/VEXVulnerability Disclosure Report / Vulnerability Exploitability eXchange
- Not detected
OBOMOperations Bill of Materials
- Not detected

Analysis:

• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.

• Evidence of ML-BOM, SaaSBOM detected in AI-generated device summary.

• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.

• Not detected in AI-generated device summary: SBOM, HBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.

Preparing a similar submission?

ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.

Assess Your Readiness →Or contact ESL directly
HALO - Nico.Lab B.V. | ESL FDA AI Device Intelligence