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.
Clinical role
Parallel radiological triage and notification to surface suspected vessel occlusion for clinician attention; it does not alter the original study or provide a diagnosis.
Images and patients
CT/CTA · Brain
Key limitation
Keep in mind: The software is for triage and notification, not diagnosis or primary image interpretation. Notifications are informational, can be delayed or absent, and require review of the original CTA by qualified clinicians. The validated sensitivity and specificity apply to the FDA-described adult datasets and vessel definitions.
Clinical detailsPurpose, 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: 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.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain Input: Adult head CTA DICOM examinations covering the specified intracranial and vertebral vessel segments.
Who uses it?Intended users: Trained clinicians and stroke teams who review head CTA triage notifications and the source examination; a notification does not replace professional judgment or diagnosis.
What does the software produce?Output: Suspected occlusion triage notifications, reports, and DICOM Secondary Capture or compressed preview content for clinician workflow; the original CT study is not changed.
What is its most important limitation?Key limitation: The software is for triage and notification, not diagnosis or primary image interpretation. Notifications are informational, can be delayed or absent, and require review of the original CTA by qualified clinicians. The validated sensitivity and specificity apply to the FDA-described adult datasets and vessel definitions.
Clinical takeaway. Clinical role: 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.
Evidence takeaway. Evidence from the reviewed source record: K251151 FDA evidence is a regulatory head-CTA triage and notification validation; no independent paper or trial was promoted in this timeboxed review.
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
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.
Parallel radiological triage and notification to surface suspected vessel occlusion for clinician attention; it does not alter the original study or provide a diagnosis.
Suspected occlusion triage notifications, reports, and DICOM Secondary Capture or compressed preview content for clinician workflow; the original CT study is not changed.
Trained clinicians and stroke teams who review head CTA triage notifications and the source examination; a notification does not replace professional judgment or diagnosis.
The software is for triage and notification, not diagnosis or primary image interpretation. Notifications are informational, can be delayed or absent, and require review of the original CTA by qualified clinicians. The validated sensitivity and specificity apply to the FDA-described adult datasets and vessel definitions.
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
K251151 FDA evidence is a regulatory head-CTA triage and notification validation; no independent paper or trial was promoted in this timeboxed review.
DesignRetrospective regulatory development, test, and independent validation of computer-aided head-CTA triage and notification against three-expert reference review.
PopulationDevelopment/test corpus of 6,264 cases from 133 sites; final independent validation of 403 adult CTA examinations across scanner vendors with three-expert 2-of-3 reference review.
Scopeexact submission
Tested versionRapid CTA 360 configuration described in K251151
Samplen=403
Sites133
IndependenceSponsor or vendor study
K251151
Manufacturer-submitted FDA evidence; the 403-case test set is independent of development but the overall evidence is regulatory, not an independent clinical-outcome study.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The wave22 exact-submission recall query returned no native recall record for K251151. This does not establish absence of family, later-version, or adverse-event information.
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: Adult head CTA DICOM examinations covering the specified intracranial and vertebral vessel segments.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact system receives adult head CTA DICOM studies, processes them in parallel with standard reading, and sends notifications and DICOM Secondary Capture or preview outputs; local PACS/RIS routing, notification channels, downtime, and escalation require acceptance testing.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA packet describes server or standalone desktop deployment with workflow notifications; the reviewed exact materials do not establish current hosting topology, service availability, retention, or infrastructure terms for a particular installation.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Suspected occlusion triage notifications, reports, and DICOM Secondary Capture or compressed preview content for clinician workflow; the original CT study is not changed.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Suspected occlusion triage notifications, reports, and DICOM Secondary Capture or compressed preview content for clinician workflow; the original CT study is not changed.
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.
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 FDA packet describes server or standalone desktop deployment with workflow notifications; the reviewed exact materials do not establish current hosting topology, service availability, retention, or infrastructure terms for a particular installation.
The exact system receives adult head CTA DICOM studies, processes them in parallel with standard reading, and sends notifications and DICOM Secondary Capture or preview outputs; local PACS/RIS routing, notification channels, downtime, and escalation require acceptance testing.
The FDA packet describes an OWASP risk process, annual ISO 27001/27701 certification, and UL-2900-1 conformance as part of the reviewed security evidence; current certificate scope, expiry, deployed configuration, and operational controls require confirmation.
Exact FDA submission
Checked 2026-09-07
This records the exact FDA packet's described evidence and is not a current independent security attestation.
Trained clinicians must review notifications against the original CTA and understand that the output is triage-only; local onboarding should cover covered vessel segments, notification failure and delay, escalation, and downtime procedures.
The exact submission processes head CTA in parallel with standard reading and sends workflow notifications while leaving the original study unchanged; test notification latency, delivery, escalation, and downtime locally.
RapidAI describes Rapid CTA as automatically processing CTA to assess reduced blood flow, identify and locate suspected large- or distal-vessel occlusion, and notify stroke teams for transfer decisions.
product family · checked 2026-09-07
Current family workflow page; it does not establish every feature, vessel scope, or deployment term for the K251151 release.
The FDA packet describes DICOM Secondary Capture and compressed preview or notification outputs; establish local PACS storage, mobile/web or other notification channels, retention, and clinician acknowledgement procedures.
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.
Human reviewedStatus
2026-09-07Last searched
26Fields reviewed
11Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The stored PubMed and ClinicalTrials.gov candidate arrays were screened and were empty. No paper or trial was promoted; empty stored arrays do not establish that no external literature or trials exist. 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, stored candidate metadata, 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 publicly available - checked 2026-09-07 - Exact FDA submission
No public list price or contract unit for the exact K251151 configuration was established in the reviewed official sources.
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-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "Rapid CTA 360 RapidAI reimbursement CPT NTAP"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. RapidAI's reimbursement page lists NTAP for Rapid LVO (FY2021-2022 rules); it does not name this product. This records what was found, not that none exists; eligibility depends on payer, site of service and use case.
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: Methinks NCCT Stroke analyzes adult non-contrast head CT to flag suspected intracranial hemorrhage and suspected large-vessel occlusion of the ICA, MCA-M1, or MCA-M2 for parallel workflow triage via PACS and/or notifications; previews are informational, not diagnostic, and a negative notification does not rule out LVO or replace CTA/standard care.
Authorized purpose: Brainomix 360 e-ASPECTS registers adult non-contrast brain CT, segments ASPECTS regions, and provides an editable ASPECTS score with highlighted regions and voxel contribution views to assist trained clinicians evaluating suspected ischemic stroke within 24 hours of last known well.
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.