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.
Clinical role
Parallel, notification-only triage and prioritization
Images and patients
CT/CTA · Brain and intracranial vessels: intracranial hemorrhage and LVO involving ICA, MCA-M1, and MCA-M2
Key limitation
Keep in mind: A missing notification must not be treated as excluding ICH or LVO. All patients should receive appropriate care including CTA and/or relevant treatment; the device does not replace CTA or MRA in ischemic-stroke workup. Exclusions include excessive motion, hemorrhagic transformation, and very thin or absent ventricles. Compressed previews are not for diagnosis beyond notification.
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: 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.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain and intracranial vessels: intracranial hemorrhage and LVO involving ICA, MCA-M1, and MCA-M2 Input: DICOM non-contrast head CT images from adult patients. CTA is described as part of the downstream standard stroke workup, not as the JLK-NCCT input.
Who uses it?Intended users: Hospital networks and trained clinicians receiving the alerts; notified clinicians must review full images per standard of care
What does the software produce?Output: Flags suspected ICH and LVO involving ICA, MCA-M1, and MCA-M2 and sends mobile notifications with compressed preview images for informational/triage use; the original medical image is not modified.
What is its most important limitation?Key limitation: A missing notification must not be treated as excluding ICH or LVO. All patients should receive appropriate care including CTA and/or relevant treatment; the device does not replace CTA or MRA in ischemic-stroke workup. Exclusions include excessive motion, hemorrhagic transformation, and very thin or absent ventricles. Compressed previews are not for diagnosis beyond notification.
Clinical takeaway. Clinical role: 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.
Evidence takeaway. Evidence from the reviewed source record: The standalone evaluation used 288 LVO cases, 144 positive and 144 negative, with an independent ground truth from two US board-certified neuroradiologists plus a third adjudicator. LVO sensitivity was 78.5% (95% CI 71.9-84.7), specificity 90.3% (85.1-94.7), and AUC 0.880 (0.837-0.920). Mean NCCT-to-notification time for suspected LVO was 1.67 +/- 0.10 minutes versus a 2.5 +/- 0.1-minute predicate goal. A reader-performance analysis reports device sensitivity 0.792 and specificity 0.933 versus average reader sensitivity 0.568 and specificity 0.840. The packet states that the ICH algorithm is the same as a previously cleared K243363 algorithm and was not additionally clinically validated here.
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
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.
Flags suspected ICH and LVO involving ICA, MCA-M1, and MCA-M2 and sends mobile notifications with compressed preview images for informational/triage use; the original medical image is not modified.
A missing notification must not be treated as excluding ICH or LVO. All patients should receive appropriate care including CTA and/or relevant treatment; the device does not replace CTA or MRA in ischemic-stroke workup. Exclusions include excessive motion, hemorrhagic transformation, and very thin or absent ventricles. Compressed previews are not for diagnosis beyond notification.
The standalone evaluation used 288 LVO cases, 144 positive and 144 negative, with an independent ground truth from two US board-certified neuroradiologists plus a third adjudicator. LVO sensitivity was 78.5% (95% CI 71.9-84.7), specificity 90.3% (85.1-94.7), and AUC 0.880 (0.837-0.920). Mean NCCT-to-notification time for suspected LVO was 1.67 +/- 0.10 minutes versus a 2.5 +/- 0.1-minute predicate goal. A reader-performance analysis reports device sensitivity 0.792 and specificity 0.933 versus average reader sensitivity 0.568 and specificity 0.840. The packet states that the ICH algorithm is the same as a previously cleared K243363 algorithm and was not additionally clinically validated here.
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
The standalone evaluation used 288 LVO cases, 144 positive and 144 negative, with an independent ground truth from two US board-certified neuroradiologists plus a third adjudicator. LVO sensitivity was 78.5% (95% CI 71.9-84.7), specificity 90.3% (85.1-94.7), and AUC 0.880 (0.837-0.920). Mean NCCT-to-notification time for suspected LVO was 1.67 +/- 0.10 minutes versus a 2.5 +/- 0.1-minute predicate goal. A reader-performance analysis reports device sensitivity 0.792 and specificity 0.933 versus average reader sensitivity 0.568 and specificity 0.840. The packet states that the ICH algorithm is the same as a previously cleared K243363 algorithm and was not additionally clinically validated here.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
JLK-NCCT regulatory performance study summary
DesignStand-alone performance and reader study (ACR AI Central category)
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K252421
Samplen=288
IndependenceIndependence not established
K252421
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 K252421. 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: DICOM non-contrast head CT images from adult patients. CTA is described as part of the downstream standard stroke workup, not as the JLK-NCCT input.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: DICOM-compliant AI processing on an on-premises or cloud-based JLK server with a mobile notification module; PACS integration is described as optional and supported when available, and the packet measures notification transmission to PACS and mobile devices.
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: 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: Flags suspected ICH and LVO involving ICA, MCA-M1, and MCA-M2 and sends mobile notifications with compressed preview images for informational/triage use; the original medical image is not modified.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Flags suspected ICH and LVO involving ICA, MCA-M1, and MCA-M2 and sends mobile notifications with compressed preview images for informational/triage use; the original medical image is not modified.
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.
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.
DICOM-compliant AI processing on an on-premises or cloud-based JLK server with a mobile notification module; PACS integration is described as optional and supported when available, and the packet measures notification transmission to PACS and mobile devices.
JLK's security page states a security program aligned with SOC 2 and HIPAA, AWS hosting in US regions with VPC isolation, TLS 1.2+ in transit, AES-256 at rest with KMS, role-based access, mandatory MFA for internal users, annual external penetration testing and security training. It states alignment, not an attestation report. Vendor-wide.
Vendor-wide
Checked 2026-10-25
Vendor statement, not an attestation; 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.
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
26Fields reviewed
10Source 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, acr ai central product, vendor documentation, fda decision summary, 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-08 - Exact FDA submission
No public price or quote for the exact K252421 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.
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-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
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: 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.
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.