ContaCT 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, 1 independent of the standard of care workflow. ContaCT uses an artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation. Identification of suspected findings is not for diagnostic use beyond notification. Specifically, the device analyzes CT angiogram images of the brain acquired in the acute setting and sends notifications to a neurovascular specialist that a suspected large vessel occlusion has been identified and recommends review of those images. Images can be previewed through a mobile application. Images that are previewed through the mobile application are compressed and are for informational purposes only and not intended for diagnostic use beyond notification. Notified clinicians are responsible for viewing non-compressed images on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating physician before making care-related decisions or requests. ContaCT is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
Clinical role
Triage or notification support
Images and patients
CT/CTA · Brain
Key limitation
Identification of suspected findings is not for diagnostic use beyond notification. Images that are previewed through the mobile application are compressed and are for informational purposes only and not intended for diagnostic use beyond notification. Notified clinicians are responsible for viewing non-compressed images on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating physician before making care-related decisions or requests. ContaCT is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
Imaging and anatomyCT/CTA · Brain
Workflow roleTriage or notification support
Required inputCT angiogram images of the brain acquired in the acute setting
Output and human actionNotification of suspected large vessel occlusion
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
ContaCT 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, 1 independent of the standard of care workflow. ContaCT uses an artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation. Identification of suspected findings is not for diagnostic use beyond notification. Specifically, the device analyzes CT angiogram images of the brain acquired in the acute setting and sends notifications to a neurovascular specialist that a suspected large vessel occlusion has been identified and recommends review of those images. Images can be previewed through a mobile application. Images that are previewed through the mobile application are compressed and are for informational purposes only and not intended for diagnostic use beyond notification. Notified clinicians are responsible for viewing non-compressed images on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating physician before making care-related decisions or requests. ContaCT is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
Identification of suspected findings is not for diagnostic use beyond notification. Images that are previewed through the mobile application are compressed and are for informational purposes only and not intended for diagnostic use beyond notification. Notified clinicians are responsible for viewing non-compressed images on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating physician before making care-related decisions or requests. ContaCT is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
Exact FDA submission
Checked 2026-09-19
The exact decision summary states the notification-only, compressed-preview, diagnostic-viewer, full-evaluation, and diagnosis boundaries.
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.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Viz LVO (ContaCT) regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission DEN170073
Samplen=300
Sites2
IndependenceIndependence not established
DEN170073
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 DEN170073. 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: CT angiogram images of the brain acquired in the acute setting
Scope: Exact FDA submission. The exact indication states the image type, anatomy, and acute-setting scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes Image Forwarding Software that interacts with a facility's scanner, PACS or local DICOM router to transmit DICOM file copies to server-hosted analysis software, which sends neurovascular specialist notifications linking to a compressed study preview on a mobile application. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "The Image Forwarding Software is configured by the hospital to interact with a healthcare facility’s scanner, PACS or local DICOM router and is responsible for automatically transmitting a copy of DICOM files from the local router" … "The Image Processing and Analysis Software component of the device is hosted on a server and is responsible for receiving, assembling, processing, analyzing and storing DICOM images.". 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.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-08 ·
Returned objects
Source context, not route validation: Notification of suspected large vessel occlusion
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Notification of suspected large vessel occlusion
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
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 Image Forwarding Software that interacts with a facility's scanner, PACS or local DICOM router to transmit DICOM file copies to server-hosted analysis software, which sends neurovascular specialist notifications linking to a compressed study preview on a mobile application. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The Image Forwarding Software is configured by the hospital to interact with a healthcare facility’s scanner, PACS or local DICOM router and is responsible for automatically transmitting a copy of DICOM files from the local router" … "The Image Processing and Analysis Software component of the device is hosted on a server and is responsible for receiving, assembling, processing, analyzing and storing DICOM images.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Viz.ai's trust center describes an independently audited security and privacy program: SOC 2 Type II scoped to Viz.ai production systems and supporting infrastructure, a HIPAA compliance program with third-party risk assessments, ISO 27001, 27701, 27799, 27017/27018, 22301, 27035, and 42001 certifications, GDPR program with EU-US Data Privacy Framework participation, encryption in transit and at rest, defense-in-depth architecture, and continuous monitoring via Drata.
Vendor-wide
Checked 2026-10-27
Vendor statement; the SOC 2 report and certificates were not read (request-gated via the trust center). Applicant name variants ('Viz. ai, Inc.', 'Viz.Al, Inc.') are bridged via the identical distinctive name and Viz product naming (Viz AAA, ContaCT). Exact-release scope is not established.
The De Novo decision summary states the indicated user population: the ContaCT mobile application is intended to be used by neurovascular specialists, such as vascular neurologists, neuro-interventional specialists, or users with similar training who have been pre-authorized by their healthcare organization or facility. The special controls also require labeling to include a detailed description of the intended user and user training that addresses appropriate use protocols for the device.
Exact FDA submission
Checked 2026-10-27
Indicated-user qualification wording plus a special-control labeling requirement; the summary specifies no vendor-provided training program for this device.
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-19Last searched
25Fields reviewed
11Source classes checked
20Awaiting review PubMed leads
10Awaiting review trial leads
0Unreviewed FDA recall leads
Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA support assessed on 2026-09-19. Packet-supported facts: purpose, modality, anatomy, intendedUsers, output, evidenceSummary; packet-unavailable facts: input, limitations. Candidate literature and postmarket candidates remain in their existing review state. Automated exact-name discovery found 20 PubMed and 10 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, acr ai central product, fda de novo summary, 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-08 - Exact FDA submission
No public price or quote for the exact DEN170073 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.
Deployment: Not verified - checked 2026-09-08 - Exact FDA submission
The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
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
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Annalise Enterprise prioritizes and notifies trained CT clinicians of suspected acute infarct on non-contrast brain CT for adults; it is a study-level, non-localizing worklist aid and never downgrades an existing priority.
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.
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.