ACR exact-submission catalog context
ACR AI Central provides an exact-submission model card for Rapid LVO; FDA labeling remains controlling for clinical use, limitations, and performance.
exact submission · checked 2026-09-08FDA-cleared profile
iSchemaView Inc. · CT/CTA · FDA-cleared (510(k))
Authorized purpose: Notification-only triage of adult head CTA for suspected large-vessel occlusion; results do not replace diagnostic interpretation.
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 triage of adult head CTA for suspected large-vessel occlusion; results do not replace diagnostic interpretation.
Evidence takeaway. Evidence from the reviewed source record: Standalone performance testing reported sensitivity 0.970 (95% CI: 0.933, 0.987), specificity 0.956 (95% CI: 0.919, 0.977), and ROC AUC 0.99 (95% CI: 0.972, 0.995). Time to notification was 2.86 minutes (95% CI: 2.79, 2.92).
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.
Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.
Packet wording: "Rapid LVO uses a software algorithm to analyze images and highlight cases with suspected LVO on a server or standalone desktop application in parallel to the ongoing standard of care image interpretation." … "The user is presented with notifications for cases with suspected LVO findings. Notifications include compressed preview images, that are meant for informational purposes only and not intended for diagnostic use beyond notification.". Read from the exact FDA decision document on 2026-11-14.
The exact device description states the DICOM-compliant CTA-scanner input path.
The exact indication describes notifications and compressed preview images; it does not support the dossier's generic qualified-user output wording.
Packet wording: "Rapid LVO is one input to physician diagnosis for patients undergoing screening for acute ischemic stroke." … "The device is intended to assist hospital networks and trained radiologists in workflow triage by flagging and communication of suspected positive Large Vessel Occlusion (LVO) findings in head CTA images.". Read from the exact FDA decision document on 2026-11-14.
The exact indication names hospital networks, trained radiologists, and notified clinicians.
These are the exact notification, diagnostic-use, image-integrity, and clinician-review boundaries in the packet.
The exact packet reports these performance values and notification time; the current 95%/95% wording is not retained.
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.
The exact packet reports these performance values and notification time; the current 95%/95% wording is not retained.
Values reported in the exact-submission materials. Consult the linked source for endpoint, threshold, population, and confidence interval before comparison.
Values reported in the exact-submission materials. Consult the linked source for endpoint, threshold, population, and confidence interval before comparison.
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: DICOM-compliant medical image data from CTA scanners through the Rapid Platform interface.
Scope: Exact FDA submission. The exact device description states the DICOM-compliant CTA-scanner input path.
Confirm scanner/model, protocol, series completeness and both software builds.
Field checked 2026-09-19 · FDA K200941: Rapid LVO
Source context, not route validation: The exact FDA package describes Rapid LVO acquiring DICOM-compliant image data from CTA scanners through the Rapid Platform, which receives DICOM images from modalities, PACS and workstations, sends DICOM images to external image consumers, and sends summary results over email and a mobile application. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "Rapid LVO acquires (DICOM compliant) medical image data from CTA scanners through the Rapid Platform interface:" … "receives DICOM images from external DICOM image providers (modalities (CT/MRI Scanners), PACS and Workstations) and sends DICOM images to external image consumers.". 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.
Field checked 2026-11-14 · FDA K200941: Rapid LVO
Source context, not route validation: The exact FDA package describes Rapid LVO as a module hosted by the Rapid Platform, which can be installed directly on a customer's Linux-based server or accessed online as Virtual Rapid. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "the Rapid LVO module which functions as one of many image processing modules hosted by the platform." … "Standard Rapid, which is installed directly on a customer's Linux-based server and integrated with medical image processing software such as commercial PACS.". 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 K200941: Rapid LVO
Source context, not route validation: Notifications for suspected LVO findings on a server or standalone desktop application, including compressed preview images for informational triage only.
Scope: Exact FDA submission. The exact indication describes notifications and compressed preview images; it does not support the dossier's generic qualified-user output wording.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Field checked 2026-09-19 · FDA K200941: Rapid LVO
Unresolved route: Notifications for suspected LVO findings on a server or standalone desktop application, including compressed preview images for informational triage only.
Scope: Exact FDA submission. The exact indication describes notifications and compressed preview images; it does not support the dossier's generic qualified-user output wording.
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-19 · FDA K200941: Rapid LVO
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 Rapid LVO module which functions as one of many image processing modules hosted by the platform." … "Standard Rapid, which is installed directly on a customer's Linux-based server and integrated with medical image processing software such as commercial PACS.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Packet wording: "Rapid LVO acquires (DICOM compliant) medical image data from CTA scanners through the Rapid Platform interface:" … "receives DICOM images from external DICOM image providers (modalities (CT/MRI Scanners), PACS and Workstations) and sends DICOM images to external image consumers.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
This is a current vendor-wide statement, not an independent attestation for the exact K223396 release; site-specific architecture, retention, contractual scope and current certification evidence remain unestablished.
Vendor statement, not an attestation. No certificate or audit report was read; the one-pager names the RapidAI platform 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 Rapid LVO; 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.
The subject-device comparison identifies the imaging type as CT Angiography; the packet does not establish the broader CT/CTA value. Controlled directory display reconciled from exact FDA wording: CT angiography (CTA). -> CT/CTA.
The exact indication repeatedly specifies CTA head images; Brain is not the packet's wording for this field. Controlled directory display reconciled from exact FDA wording: Head. -> Brain.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
The refreshed discovery snapshot contains 4 PubMed and 0 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 4 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 security document, fda device recall, literature index, trial registry, fda decision summary packet, 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 K200941 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.
9 sources - 3 history items
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary, deployment, integration
Scope: regulatoryIdentity, modalityContext
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: vendorWideSecurity, deployment, implementationCapabilities
Scope: postmarketSafety
Scope: security, monitoring
Regulatory record
510(k)
Research record
fda record reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
Harrison-AI Medical Pty, Ltd.
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.
Aidoc Medical, Ltd.
Authorized purpose: Adult contrast-enhanced brain CT triage for suspected brain aneurysm findings at least 3.0 mm.
Methinks Software S.L.
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.
iSchemaView
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.
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