FDA-cleared profile

Viz LVO ContaCT

Viz.ai, Inc. · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Notification-only parallel workflow to identify and communicate suspected large vessel occlusion on acute brain CTA to a neurovascular specialist; identification is not for diagnosis beyond notification.

Clinical role
Notification-only parallel triage and specialist communication independent of the standard-of-care reading workflow; users can receive and toggle suspected-LVO notifications, view a patient list, and review informational mobile previews.
Images and patients
CT/CTA · Brain, specifically the terminal internal carotid artery and MCA-M1 vessels
Key limitation
Keep in mind: The device is notification-only and identification of suspected findings is not diagnostic. Mobile previews are compressed and informational only; notified clinicians must view non-compressed images on a diagnostic viewer and perform full patient evaluation and relevant discussion before care decisions. The software analyzes imaging data only, must not be used in lieu of full patient evaluation or relied upon to make or confirm a diagnosis, and does not establish a rule-out capability.

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: Notification-only parallel workflow to identify and communicate suspected large vessel occlusion on acute brain CTA to a neurovascular specialist; identification is not for diagnosis beyond notification.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain, specifically the terminal internal carotid artery and MCA-M1 vessels Input: Stroke-protocoled CTA images of the head acquired on CT scanners in the acute setting and forwarded to Viz.ai's Backend Server in DICOM format; the algorithm analyzes the terminal ICA and MCA-M1 vessels for suspected LVO.
  • Who uses it?Intended users: Hospital networks and trained clinicians, with notifications directed to a neurovascular specialist
  • What does the software produce?Output: A notification that a suspected large vessel occlusion has been identified and that the images should be reviewed by a neurovascular specialist; the mobile application provides a unique suspected-LVO patient list and compressed, non-diagnostic CT previews, while non-compressed images remain for diagnostic-viewer review.
  • What is its most important limitation?Key limitation: The device is notification-only and identification of suspected findings is not diagnostic. Mobile previews are compressed and informational only; notified clinicians must view non-compressed images on a diagnostic viewer and perform full patient evaluation and relevant discussion before care decisions. The software analyzes imaging data only, must not be used in lieu of full patient evaluation or relied upon to make or confirm a diagnosis, and does not establish a rule-out capability.

Clinical takeaway. Clinical role: Notification-only parallel workflow to identify and communicate suspected large vessel occlusion on acute brain CTA to a neurovascular specialist; identification is not for diagnosis beyond notification.

Evidence takeaway. Evidence from the reviewed source record: K223042 is a Special 510(k) for changes to the Viz LVO indications describing the intended regions analyzed. The FDA summary explicitly states that performance data were not included in the premarket notification; supporting software verification and validation testing was provided to demonstrate implementation of the changes. No subject-device sensitivity, specificity, AUC, or clinical-outcome performance estimate is established by this packet.

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 to identify and communicate suspected large vessel occlusion on acute brain CTA to a neurovascular specialist; identification is not for diagnosis beyond notification.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Notification-only parallel triage and specialist communication independent of the standard-of-care reading workflow; users can receive and toggle suspected-LVO notifications, view a patient list, and review informational mobile previews.
  • Exact FDA submission
  • Checked 2026-09-08
Required input
Stroke-protocoled CTA images of the head acquired on CT scanners in the acute setting and forwarded to Viz.ai's Backend Server in DICOM format; the algorithm analyzes the terminal ICA and MCA-M1 vessels for suspected LVO.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
A notification that a suspected large vessel occlusion has been identified and that the images should be reviewed by a neurovascular specialist; the mobile application provides a unique suspected-LVO patient list and compressed, non-diagnostic CT previews, while non-compressed images remain for diagnostic-viewer review.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Hospital networks and acute neurovascular clinical workflow
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Hospital networks and trained clinicians, with notifications directed to a neurovascular specialist
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
The device is notification-only and identification of suspected findings is not diagnostic. Mobile previews are compressed and informational only; notified clinicians must view non-compressed images on a diagnostic viewer and perform full patient evaluation and relevant discussion before care decisions. The software analyzes imaging data only, must not be used in lieu of full patient evaluation or relied upon to make or confirm a diagnosis, and does not establish a rule-out capability.
  • Exact FDA submission
  • Checked 2026-09-08
Evidence summary
K223042 is a Special 510(k) for changes to the Viz LVO indications describing the intended regions analyzed. The FDA summary explicitly states that performance data were not included in the premarket notification; supporting software verification and validation testing was provided to demonstrate implementation of the changes. No subject-device sensitivity, specificity, AUC, or clinical-outcome performance estimate is established by this packet.
  • Exact FDA submission
  • Checked 2026-09-08

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
K223042 is a Special 510(k) for changes to the Viz LVO indications describing the intended regions analyzed. The FDA summary explicitly states that performance data were not included in the premarket notification; supporting software verification and validation testing was provided to demonstrate implementation of the changes. No subject-device sensitivity, specificity, AUC, or clinical-outcome performance estimate is established by this packet.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

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
The exact-identifier FDA recall query returned no native recall record for K223042. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

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: Stroke-protocoled CTA images of the head acquired on CT scanners in the acute setting and forwarded to Viz.ai's Backend Server in DICOM format; the algorithm analyzes the terminal ICA and MCA-M1 vessels for suspected LVO.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-08 · FDA K223042: Viz LVO ContaCT

  2. Routing

    Source context, not route validation: The LVO algorithm is hosted on Viz.ai's Backend Server and receives applicable stroke-protocol CTA images in DICOM format from CT imaging devices or the connected imaging workflow; the Viz VIEW mobile module presents notifications and non-diagnostic previews. The reviewed FDA packet does not establish a specific PACS, RIS, EHR, interface version, or current deployment configuration.

    Scope: Exact FDA submission.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-08 · FDA K223042: Viz LVO ContaCT

  3. AI processing

    Source context, not route validation: The exact FDA package describes the LVO Detection Algorithm as hosted on Viz.ai's Backend Server, analyzing CTA images forwarded to that server, and a mobile application software module through which the non-diagnostic CT scan is viewed in Viz VIEW. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "The LVO Detection Algorithm is hosted on Viz.ai’s Backend Server and analyzes applicable stroke-protocoled CTA images of the head that are acquired on CT scanners and are forwarded to Viz.ai’s Backend Server." … "Viz LVO consists of an algorithm and mobile application software module.". 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 K223042: Viz LVO ContaCT

  4. Returned objects

    Source context, not route validation: A notification that a suspected large vessel occlusion has been identified and that the images should be reviewed by a neurovascular specialist; the mobile application provides a unique suspected-LVO patient list and compressed, non-diagnostic CT previews, while non-compressed images remain for diagnostic-viewer review.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-08 · FDA K223042: Viz LVO ContaCT

  5. Viewer/worklist/report

    Unresolved route: A notification that a suspected large vessel occlusion has been identified and that the images should be reviewed by a neurovascular specialist; the mobile application provides a unique suspected-LVO patient list and compressed, non-diagnostic CT previews, while non-compressed images remain for diagnostic-viewer 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-08 · FDA K223042: Viz LVO ContaCT

  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 the LVO Detection Algorithm as hosted on Viz.ai's Backend Server, analyzing CTA images forwarded to that server, and a mobile application software module through which the non-diagnostic CT scan is viewed in Viz VIEW. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The LVO Detection Algorithm is hosted on Viz.ai’s Backend Server and analyzes applicable stroke-protocoled CTA images of the head that are acquired on CT scanners and are forwarded to Viz.ai’s Backend Server." … "Viz LVO consists of an algorithm and mobile application software module.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The LVO algorithm is hosted on Viz.ai's Backend Server and receives applicable stroke-protocol CTA images in DICOM format from CT imaging devices or the connected imaging workflow; the Viz VIEW mobile module presents notifications and non-diagnostic previews. The reviewed FDA packet does not establish a specific PACS, RIS, EHR, interface version, or current deployment configuration.
  • Exact FDA submission
  • Checked 2026-09-08
Security
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.

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

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for Viz LVO ContaCT; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
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
K223042
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Brain, specifically the terminal internal carotid artery and MCA-M1 vessels
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-10-21
  • 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
20Fields reviewed
10Source 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, 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-08 - Exact FDA submission

    No public price or quote for the exact K223042 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
  • 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.

10 sources - 3 history items

Source ledger

  1. FDA K223042: Viz LVO ContaCT

    U.S. Food and Drug Administration - Published 2022-10-21 - Accessed 2026-09-08

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. Viz LVO model card (K223042)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, anatomy

  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. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K223042

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

    Scope: postmarketSafety

  8. Viz.ai Announces Completion of SOC 2 Type II + HIPAA Audits

    Viz.ai, Inc. - Published 2024-02-26 - Accessed 2026-10-25

    Scope: security

  9. Viz.ai Strengthens Information Security with ISO Certification

    Viz.ai, Inc. - Published 2024-07-10 - Accessed 2026-10-25

    Scope: security

  10. Viz.ai: Trust Center

    Viz.ai - Accessed 2026-10-27

    Scope: security

Research history

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

Vascular Assist Occlusion Triage (VAOT) (v1.0)

GuideAI Health

Authorized purpose: Passive workflow prioritization for studies with imaging patterns consistent with possible total arterial occlusion in the specified vessels; not primary diagnosis, screening, disease detection, or patient-management decision support

Modality
CT/CTA
Anatomy
Aorta and lower-extremity arteries: common iliac, external iliac, common femoral, superficial femoral, and popliteal arteries
Decision
2026-06-18
FDA-cleared K261317

BriefCase-Triage

Aidoc Medical, Ltd.

Authorized purpose: Adult head CTA or mCTA triage for suspected complete large-vessel and medium-vessel occlusion.

Modality
CT/CTA
Anatomy
Head/Brain
Decision
2026-05-14
FDA-cleared K252421

JLK-NCCT

JLK, Inc.

Authorized purpose: Notification-only triage of adult non-contrast head CT for suspected intracranial hemorrhage and large-vessel occlusion, with parallel communication to trained clinicians during standard care.

Modality
CT/CTA
Anatomy
Brain and intracranial vessels: intracranial hemorrhage and LVO involving ICA, MCA-M1, and MCA-M2
Decision
2026-03-24

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