Authorized purpose: Notification-only parallel workflow for identifying and communicating images of patients with suspected subdural hemorrhage from non-contrast head CT to neurovascular or neurosurgical specialists; not diagnostic beyond notification.
Clinical role
Notification-only parallel workflow tool: the device analyzes non-contrast head CT for suspected subdural hemorrhage and notifies a neurovascular or neurosurgical specialist in parallel to standard of care image interpretation; findings are not for diagnostic use beyond notification.
Images and patients
CT/CTA · Brain
Key limitation
Keep in mind: Not diagnostic beyond notification; compressed previews are informational only; non-compressed images and full patient evaluation are required; not for confirming or ruling out 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: Notification-only parallel workflow for identifying and communicating images of patients with suspected subdural hemorrhage from non-contrast head CT to neurovascular or neurosurgical specialists; not diagnostic beyond notification.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain Input: Non-contrast CT images of the head from DICOM-compliant imaging devices.
Who uses it?Intended users: Hospital networks, trained clinicians, and neurovascular or neurosurgical specialists.
What does the software produce?Output: Notification to a neurovascular or neurosurgical specialist and a compressed, non-diagnostic mobile preview; no image marking.
What is its most important limitation?Key limitation: Not diagnostic beyond notification; compressed previews are informational only; non-compressed images and full patient evaluation are required; not for confirming or ruling out diagnosis.
Clinical takeaway. Clinical role: Notification-only parallel workflow for identifying and communicating images of patients with suspected subdural hemorrhage from non-contrast head CT to neurovascular or neurosurgical specialists; not diagnostic beyond notification.
Evidence takeaway. Evidence from the reviewed source record: FDA reports 542 NCCT studies from 3 U.S. sites with trained-neuroradiologist ground truth: sensitivity 94% (90-97%), specificity 92% (89-95%), and AUC 0.96.
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
Notification-only parallel workflow for identifying and communicating images of patients with suspected subdural hemorrhage from non-contrast head CT to neurovascular or neurosurgical specialists; not diagnostic beyond notification.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Notification-only parallel workflow tool: the device analyzes non-contrast head CT for suspected subdural hemorrhage and notifies a neurovascular or neurosurgical specialist in parallel to standard of care image interpretation; findings are not for diagnostic use beyond notification.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Viz SDH is a notification-only, parallel workflow tool for use by hospital networks and trained clinicians to identify and communicate images of specific patients to a specialist" … "Specifically, the device analyzes non-contrast CT images of the head for subdural hemorrhage and sends notifications to a neurovascular or neurosurgical specialist that a suspected subdural hemorrhage has been identified and recommends review of those images.". Read from the exact FDA decision document on 2026-11-14.
Hospital networks and trained clinicians, for patients whose non-contrast CT images of the head are analyzed for suspected subdural hemorrhage.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Viz SDH is a notification-only, parallel workflow tool for use by hospital networks and trained clinicians to identify and communicate images of specific patients to a specialist" … "Specifically, the device analyzes non-contrast CT images of the head for subdural hemorrhage and sends notifications to a neurovascular or neurosurgical specialist that a suspected subdural hemorrhage has been identified and recommends review of those images.". Read from the exact FDA decision document on 2026-11-14.
Not diagnostic beyond notification; compressed previews are informational only; non-compressed images and full patient evaluation are required; not for confirming or ruling out diagnosis.
FDA reports 542 NCCT studies from 3 U.S. sites with trained-neuroradiologist ground truth: sensitivity 94% (90-97%), specificity 92% (89-95%), and AUC 0.96.
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
FDA reports 542 NCCT studies from 3 U.S. sites with trained-neuroradiologist ground truth: sensitivity 94% (90-97%), specificity 92% (89-95%), and AUC 0.96.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Viz SDH 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 K220439
Samplen=542
Sites3
IndependenceIndependence not established
K220439
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 K220439. 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: Non-contrast CT images of the head from DICOM-compliant imaging devices.
Scope: Exact FDA submission. FDA input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes Viz SDH receiving NCCT head images forwarded from CT scanners to Viz.ai servers and sending suspected-finding notifications through a mobile module implemented in Viz.ai’s non-diagnostic DICOM image viewer, Viz VIEW. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "images of the head that are acquired on CT scanners and are forwarded to Viz.ai servers." … "Upon detection of a suspected subdural hemorrhage, the Viz SDH Image Analysis Algorithm sends a notification of the suspected finding.". 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 the Viz SDH image analysis algorithm as hosted on Viz.ai’s servers, analyzing NCCT head images forwarded from CT scanners, with a mobile software module for receiving notifications. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The Viz SDH Image Analysis Algorithm is hosted on Viz.ai’s servers and analyzes applicable stroke-protocoled NCCT" … "images of the head that are acquired on CT scanners and are forwarded to Viz.ai servers.". 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.
Source context, not route validation: Notification to a neurovascular or neurosurgical specialist and a compressed, non-diagnostic mobile preview; no image marking.
Scope: Exact FDA submission. FDA output and viewing boundary.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Notification to a neurovascular or neurosurgical specialist and a compressed, non-diagnostic mobile preview; no image marking.
Scope: Exact FDA submission. FDA output and viewing boundary.
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 the Viz SDH image analysis algorithm as hosted on Viz.ai’s servers, analyzing NCCT head images forwarded from CT scanners, with a mobile software module for receiving notifications. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The Viz SDH Image Analysis Algorithm is hosted on Viz.ai’s servers and analyzes applicable stroke-protocoled NCCT" … "images of the head that are acquired on CT scanners and are forwarded to Viz.ai servers.". 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 Viz SDH receiving NCCT head images forwarded from CT scanners to Viz.ai servers and sending suspected-finding notifications through a mobile module implemented in Viz.ai’s non-diagnostic DICOM image viewer, Viz VIEW. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "images of the head that are acquired on CT scanners and are forwarded to Viz.ai servers." … "Upon detection of a suspected subdural hemorrhage, the Viz SDH Image Analysis Algorithm sends a notification of the suspected finding.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Viz.ai's own news releases say the Viz.ai One platform completed a SOC 2 Type II + HIPAA audit (announced 2024-02-26) and received ISO 27001:2022 plus six other ISO certificates (announced 2024-07-10). These are vendor announcements; the report and certificates were not read, and certificate dates may have lapsed or renewed since.
Vendor-wide
Checked 2026-10-25
Vendor-wide statement, not an independent attestation. It does not establish certificate or report scope for this exact release, expiry, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.
Viz.ai's trust center states that its assurance program includes continuously monitored controls, SOC 2 Type II coverage that includes the availability criterion for Viz.ai production systems and supporting infrastructure, ISO 22301 business continuity certification to ensure uninterrupted clinical workflows, and ISO 27035 incident management certification.
Vendor-wide
Checked 2026-10-27
Vendor statements, not attestations. Certificates and audit reports were not read; the trust center names Viz.ai generally and does not scope these commitments to any specific product release; exact-release scope is not established.
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
27Fields reviewed
11Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 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, fda device recall, literature index, trial registry, fda decision summary packet, 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 verified - checked 2026-09-09 - Exact FDA submission
No public price or quote for the exact K220439 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-09 - 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
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support 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.