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-08FDA-cleared profile
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.
Overview status: Source-reviewed overview
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
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 not reviewed for this FDA record.
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.
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.
This field has not been curated yet.
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
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Price not public here; enter your quote
Not verified: Pricing information is recorded but not verified against a resolving source.
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.
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
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
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
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
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
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
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.
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.
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 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-08Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
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
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.
No public price or quote for the exact K223042 configuration was established in this review.
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
10 sources - 3 history items
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment
Scope: regulatoryIdentity, modalityContext
Scope: intendedUsers, careSetting, output, anatomy
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: postmarketSafety
Scope: security
Scope: security
Scope: security
Regulatory record
510(k)
Research record
fda record reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
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
Aidoc Medical, Ltd.
Authorized purpose: Adult head CTA or mCTA triage for suspected complete large-vessel and medium-vessel occlusion.
Ever Fortune.Ai, Co., Ltd.
Authorized purpose: Triage notification of suspected appendicitis on contrast-enhanced abdominal CT
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.
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 destinationPermission 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.
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