Authorized purpose: Triage and notification for suspected intracranial hemorrhage and non-contrast CT large-vessel occlusion involving the ICA and MCA-M1.
Clinical role
Workflow triage that analyzes nonenhanced head CT and flags suspected intracranial hemorrhage or large vessel occlusion in parallel to standard-of-care interpretation, notifying users via PACS, email or mobile device; notified clinicians review the full images.
Images and patients
CT/CTA · Brain/head, including ICH and ICA/MCA-M1 LVO findings.
Key limitation
Keep in mind: Adults only; not primary diagnostic or standalone; not a rule-out device; does not replace CTA or MRA; motion, hemorrhagic transformation, hematoma, and very thin or absent ventricles are listed exclusions.
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: Triage and notification for suspected intracranial hemorrhage and non-contrast CT large-vessel occlusion involving the ICA and MCA-M1.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain/head, including ICH and ICA/MCA-M1 LVO findings. Input: Non-enhanced head CT images for both ICH and NCCT-LVO analysis.
Who uses it?Intended users: Trained clinicians; the device assists hospital-network workflow triage.
What does the software produce?Output: Priority notifications through PACS, email, or mobile device with compressed preview images indicating suspected ICH or NCCT LVO; original images are not altered.
What is its most important limitation?Key limitation: Adults only; not primary diagnostic or standalone; not a rule-out device; does not replace CTA or MRA; motion, hemorrhagic transformation, hematoma, and very thin or absent ventricles are listed exclusions.
Clinical takeaway. Clinical role: Triage and notification for suspected intracranial hemorrhage and non-contrast CT large-vessel occlusion involving the ICA and MCA-M1.
Evidence takeaway. Evidence from the reviewed source record: FDA packet describes a retrospective multicenter study of 254 cases with 10 excluded for age or technical inadequacy; ICH sensitivity/specificity were 0.962/0.974 and NCCT-LVO sensitivity/specificity were 0.635/0.951.
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
Triage and notification for suspected intracranial hemorrhage and non-contrast CT large-vessel occlusion involving the ICA and MCA-M1.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Workflow triage that analyzes nonenhanced head CT and flags suspected intracranial hemorrhage or large vessel occlusion in parallel to standard-of-care interpretation, notifying users via PACS, email or mobile device; notified clinicians review the full images.
Exact FDA submission
Checked 2026-11-14
Packet wording: "nonenhanced head CT (NCCT) images. The device is intended to assist hospital networks and trained clinicians in workflow triage by flagging and communicating suspected positive findings of (1) head CT images for Intracranial Hemorrhage (ICH) and (2) NCCT large vessel occlusion (LVO)" … "in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected ICH or LVO findings via PACS, email or mobile device.". Read from the exact FDA decision document on 2026-11-14.
Priority notifications through PACS, email, or mobile device with compressed preview images indicating suspected ICH or NCCT LVO; original images are not altered.
Adults only; not primary diagnostic or standalone; not a rule-out device; does not replace CTA or MRA; motion, hemorrhagic transformation, hematoma, and very thin or absent ventricles are listed exclusions.
FDA packet describes a retrospective multicenter study of 254 cases with 10 excluded for age or technical inadequacy; ICH sensitivity/specificity were 0.962/0.974 and NCCT-LVO sensitivity/specificity were 0.635/0.951.
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 packet describes a retrospective multicenter study of 254 cases with 10 excluded for age or technical inadequacy; ICH sensitivity/specificity were 0.962/0.974 and NCCT-LVO sensitivity/specificity were 0.635/0.951.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Rapid NCCT Stroke regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K222884
Samplen=214
IndependenceIndependence not established
K222884
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 K222884. 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: Non-enhanced head CT images for both ICH and NCCT-LVO analysis.
Scope: Exact FDA submission. FDA indications and comparison table; CTA/MRA are follow-up workup, not device input.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Cloud-based and on-premises deployment are explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Priority notifications through PACS, email, or mobile device with compressed preview images indicating suspected ICH or NCCT LVO; original images are not altered.
Scope: Exact FDA submission. FDA indications and device description.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Priority notifications through PACS, email, or mobile device with compressed preview images indicating suspected ICH or NCCT LVO; original images are not altered.
Scope: Exact FDA submission. FDA indications and device description.
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.
Cloud-based and on-premises deployment are explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-09-01
Deployment mode explicitly reported in the exact-submission ACR model card; hosting region and current commercial configuration still require vendor confirmation.
The exact-submission ACR model card explicitly references PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
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.
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.
Cloud-based and on-premises deployment are explicitly described in the exact-submission ACR model card; hosting region, data flow, and current commercial configuration require vendor confirmation.
ACR AI Central provides an exact-submission model card for Rapid NCCT Stroke; FDA labeling remains controlling for clinical use, limitations, and performance.
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-20Last searched
27Fields reviewed
11Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
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 security document, 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-09 - Exact FDA submission
No public price or quote for the exact K222884 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.
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
Authorized purpose: Triage and notification of suspected intracranial hemorrhage or anterior-circulation LVO on acute non-contrast head CT; not primary diagnosis.
Modality
CT/CTA
Anatomy
Brain/head, including intracranial ICA and M1 for LVO and intracranial hemorrhage findings
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.
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.