FDA-cleared profile

Rapid LVO

iSchemaView Inc. · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Assist hospital networks and trained radiologists with workflow triage by flagging and communicating suspected ICA or MCA-M1 large-vessel occlusion findings in head CTA images.

Clinical role
Triage and notification prioritization for suspected LVO; the device does not alter the original image and compressed previews are informational only.
Images and patients
CT/CTA · Head/brain vasculature, specifically the intracranial ICA and MCA-M1 segments.
Key limitation
Keep in mind: This is a workflow-prioritization/notification device, not a diagnostic device. Excessive motion may make a scan technically inadequate; email/mobile/web previews are compressed and non-diagnostic; notified clinicians must view non-compressed images on a diagnostic viewer and use professional judgment before care decisions.

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: Assist hospital networks and trained radiologists with workflow triage by flagging and communicating suspected ICA or MCA-M1 large-vessel occlusion findings in head CTA images.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head/brain vasculature, specifically the intracranial ICA and MCA-M1 segments. Input: CTA head images acquired from DICOM-compliant imaging devices and modalities.
  • Who uses it?Intended users: Hospital networks and trained radiologists; notified clinicians must review full images under the standard of care.
  • What does the software produce?Output: Priority notifications indicating suspected ICA or MCA-M1 LVO, compressed preview images, and notification delivery through the described PACS, email, and mobile pathways.
  • What is its most important limitation?Key limitation: This is a workflow-prioritization/notification device, not a diagnostic device. Excessive motion may make a scan technically inadequate; email/mobile/web previews are compressed and non-diagnostic; notified clinicians must view non-compressed images on a diagnostic viewer and use professional judgment before care decisions.

Clinical takeaway. Clinical role: Assist hospital networks and trained radiologists with workflow triage by flagging and communicating suspected ICA or MCA-M1 large-vessel occlusion findings in head CTA images.

Evidence takeaway. Evidence from the reviewed source record: FDA K221248 reports standalone performance on 217 CTA head scans from eight sites/studies (135 positive and 82 negative), truthed by three expert neuroradiologists with 2:3 concurrence. Sensitivity was 0.96 (95% CI 0.91-0.97) and specificity 0.98 (95% CI 0.93-0.99); PPV was 0.98, NPV 0.96, and ROC AUC 0.99. Time-to-notification was 3.18 minutes (95% CI 3.11-3.25), meeting the <=3.5-minute goal. Geography, gender, age, scanner manufacturer, and slice-thickness subgroup endpoints were also reported and remain distinct from overall sensitivity/specificity.

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
Assist hospital networks and trained radiologists with workflow triage by flagging and communicating suspected ICA or MCA-M1 large-vessel occlusion findings in head CTA images.
  • Exact FDA submission
  • Checked 2026-09-09
Workflow role
Triage and notification prioritization for suspected LVO; the device does not alter the original image and compressed previews are informational only.
  • Exact FDA submission
  • Checked 2026-09-09
Required input
CTA head images acquired from DICOM-compliant imaging devices and modalities.
  • Exact FDA submission
  • Checked 2026-09-09
Output and clinician action
Priority notifications indicating suspected ICA or MCA-M1 LVO, compressed preview images, and notification delivery through the described PACS, email, and mobile pathways.
  • Exact FDA submission
  • Checked 2026-09-09
Care setting
Hospital-network stroke/head triage workflow in parallel with standard of care; the packet describes a server or standalone desktop application.
  • Exact FDA submission
  • Checked 2026-09-09
Intended users
Hospital networks and trained radiologists; notified clinicians must review full images under the standard of care.
  • Exact FDA submission
  • Checked 2026-09-09
Limitations
This is a workflow-prioritization/notification device, not a diagnostic device. Excessive motion may make a scan technically inadequate; email/mobile/web previews are compressed and non-diagnostic; notified clinicians must view non-compressed images on a diagnostic viewer and use professional judgment before care decisions.
  • Exact FDA submission
  • Checked 2026-09-09
Evidence summary
FDA K221248 reports standalone performance on 217 CTA head scans from eight sites/studies (135 positive and 82 negative), truthed by three expert neuroradiologists with 2:3 concurrence. Sensitivity was 0.96 (95% CI 0.91-0.97) and specificity 0.98 (95% CI 0.93-0.99); PPV was 0.98, NPV 0.96, and ROC AUC 0.99. Time-to-notification was 3.18 minutes (95% CI 3.11-3.25), meeting the <=3.5-minute goal. Geography, gender, age, scanner manufacturer, and slice-thickness subgroup endpoints were also reported and remain distinct from overall sensitivity/specificity.
  • Exact FDA submission
  • Checked 2026-09-09

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
FDA K221248 reports standalone performance on 217 CTA head scans from eight sites/studies (135 positive and 82 negative), truthed by three expert neuroradiologists with 2:3 concurrence. Sensitivity was 0.96 (95% CI 0.91-0.97) and specificity 0.98 (95% CI 0.93-0.99); PPV was 0.98, NPV 0.96, and ROC AUC 0.99. Time-to-notification was 3.18 minutes (95% CI 3.11-3.25), meeting the <=3.5-minute goal. Geography, gender, age, scanner manufacturer, and slice-thickness subgroup endpoints were also reported and remain distinct from overall sensitivity/specificity.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Reported sensitivity
Standalone Rapid LVO sensitivity: 0.96 (95% CI 0.91-0.97) on 217 CTA head scans, with 135 positive and 82 negative scans.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09

This is the overall standalone endpoint; PPV, NPV, AUC, time-to-notification, and subgroup estimates are separate.

Reported specificity
Standalone Rapid LVO specificity: 0.98 (95% CI 0.93-0.99) on the same 217 CTA head scans.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09

This replaces the active-row 95% value with the FDA overall specificity and keeps it distinct from PPV/NPV and subgroup specificity.

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

Rapid LVO 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 K221248
  • Samplen=217
  • Sites8
  • IndependenceIndependence not established

K221248

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

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 K221248. 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-09
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: CTA head images acquired from DICOM-compliant imaging devices and modalities.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K221248: Rapid LVO

  2. Routing

    Source context, not route validation: The Rapid Platform provides DICOM processing and image output; the comparison describes standard PC workstation/server or VMware operation and PACS, email, and mobile notification pathways. A specific local interface, hosting model, or PACS/RIS/EHR version compatibility is not established.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K221248: Rapid LVO

  3. AI processing

    Source context, not route validation: The exact FDA package describes Rapid LVO as a module within the integrated Rapid Platform that highlights cases on a server or standalone desktop application, on a standard off-the-shelf PC workstation/server or a virtual platform such as VMware. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Computer Platform Standard off-the-shelf PC Same workstation/server Virtual platform such as VMware Same" … "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.". 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 K221248: Rapid LVO

  4. Returned objects

    Source context, not route validation: Priority notifications indicating suspected ICA or MCA-M1 LVO, compressed preview images, and notification delivery through the described PACS, email, and mobile pathways.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K221248: Rapid LVO

  5. Viewer/worklist/report

    Unresolved route: Priority notifications indicating suspected ICA or MCA-M1 LVO, compressed preview images, and notification delivery through the described PACS, email, and mobile pathways.

    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-09 · FDA K221248: Rapid LVO

  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 Rapid LVO as a module within the integrated Rapid Platform that highlights cases on a server or standalone desktop application, on a standard off-the-shelf PC workstation/server or a virtual platform such as VMware. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Computer Platform Standard off-the-shelf PC Same workstation/server Virtual platform such as VMware Same" … "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.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The Rapid Platform provides DICOM processing and image output; the comparison describes standard PC workstation/server or VMware operation and PACS, email, and mobile notification pathways. A specific local interface, hosting model, or PACS/RIS/EHR version compatibility is not established.
  • Exact FDA submission
  • Checked 2026-09-09
Security
RapidAI's current platform security and compliance one-pager states that its portfolio uses encryption at rest and in transit, role-based access control, monitoring/logging and listed HIPAA, GDPR, ISO 13485, ISO 27001, ISO 27701 and SOC 2 Type 1 claims.
  • Vendor-wide
  • Checked 2026-10-25

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.

Monitoring
RapidAI's security and compliance one-pager (Rev 8, published by iSchemaView, Inc.) states continuous infrastructure monitoring and system telemetry to detect operational anomalies in real time, plus a formal incident response and escalation framework with defined communication protocols.
  • Vendor-wide
  • Checked 2026-10-27

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.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

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-09
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
K221248
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Anatomy
Head/brain vasculature, specifically the intracranial ICA and MCA-M1 segments.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-05-31
  • 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
25Fields reviewed
10Source classes checked
4Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

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, 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 K221248 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.

9 sources - 3 history items

Source ledger

  1. FDA K221248: Rapid LVO

    U.S. Food and Drug Administration - Published 2022-05-31 - Accessed 2026-09-09

    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. Rapid LVO model card (K221248)

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

    Scope: intendedUsers, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  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. RapidAI security and compliance one-pager

    RapidAI - Accessed 2026-09-08

    Scope: vendorWideSecurity, deployment, implementationCapabilities

  8. openFDA exact recall query for K221248

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

    Scope: postmarketSafety

  9. RapidAI security and compliance one-pager (Rev 8)

    iSchemaView, Inc. (RapidAI) - Accessed 2026-10-27

    Scope: security, monitoring

Research history

  1. K221248 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 K251151

Rapid CTA 360

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-07-16
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
FDA-cleared K251610

qER-CTA (v1.0)

Qure.ai Technologies

Authorized purpose: Parallel notification of suspected anterior-circulation large vessel occlusion on acute head CTA for specialist review; notification only, not diagnosis.

Modality
CT/CTA
Anatomy
Brain anterior circulation: internal carotid artery and M1 segment of the middle cerebral artery
Decision
2025-09-08

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