Authorized purpose: Triage and prioritize suspected intracranial hemorrhage on non-enhanced head CT alongside standard-of-care interpretation.
Clinical role
Flags suspected ICH cases in a worklist, in parallel to standard-of-care image interpretation; it does not alter images or remove cases from queue, is not a diagnostic device, and notified clinicians view full images per standard of care.
Images and patients
CT/CTA · Head
Key limitation
Keep in mind: Not diagnostic; does not alter the original image or remove cases; full-image standard-of-care review remains required.
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 prioritize suspected intracranial hemorrhage on non-enhanced head CT alongside standard-of-care interpretation.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head Input: Non-enhanced head CT images with DICOM patient, study, and image information.
Who uses it?Intended users: Trained radiologists
What does the software produce?Output: Worklist marking or indicator for suspected ICH, with an informational preview.
What is its most important limitation?Key limitation: Not diagnostic; does not alter the original image or remove cases; full-image standard-of-care review remains required.
Clinical takeaway. Clinical role: Triage and prioritize suspected intracranial hemorrhage on non-enhanced head CT alongside standard-of-care interpretation.
Evidence takeaway. Evidence from the reviewed source record: FDA reports 369 non-contrast brain CT studies from three U.S. hospitals: sensitivity 0.916, specificity 0.922, AUC 0.962, and mean notification time 1.07 +/- 0.57 minutes.
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 prioritize suspected intracranial hemorrhage on non-enhanced head CT alongside standard-of-care interpretation.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Flags suspected ICH cases in a worklist, in parallel to standard-of-care image interpretation; it does not alter images or remove cases from queue, is not a diagnostic device, and notified clinicians view full images per standard of care.
Exact FDA submission
Checked 2026-11-14
Packet wording: "uses an artificial intelligence algorithm to analyze images and highlight cases with detected ICH on a standalone desktop application in parallel to the ongoing standard of care image interpretation." … "The user is presented with a worklist with marked cases of suspected ICH findings. The device does not alter the original medical image, does not remove cases from queue, and is not intended to be used as a diagnostic device.". Read from the exact FDA decision document on 2026-11-14.
Non-enhanced head CT analysis to assist hospital networks and trained radiologists, with deployment possible as an onsite server in the hospital; the FDA document does not specify a patient population.
Exact FDA submission
Checked 2026-11-14
Packet wording: "radiological computer aided triage and notification software for use in the analysis of non-enhanced head CT images. The device is intended to assist hospital networks and trained radiologists in workflow triage" … "The device can be deployed as an onsite server in the hospital and the user interacts with the software from a client workstation.". Read from the exact FDA decision document on 2026-11-14.
FDA reports 369 non-contrast brain CT studies from three U.S. hospitals: sensitivity 0.916, specificity 0.922, AUC 0.962, and mean notification time 1.07 +/- 0.57 minutes.
Exact FDA submission
Checked 2026-09-19
Submission-reported retrospective performance; not an independent validation.
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 reports 369 non-contrast brain CT studies from three U.S. hospitals: sensitivity 0.916, specificity 0.922, AUC 0.962, and mean notification time 1.07 +/- 0.57 minutes.
FDA source
Exact FDA submission
Checked 2026-09-19
Submission-reported retrospective performance; not an independent validation.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
InferRead CT Stroke.AI 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 K211179
Samplen=369
Sites3
IndependenceIndependence not established
K211179
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 K211179. 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 with DICOM patient, study, and image information.
Scope: Exact FDA submission. FDA device description and comparison table.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM 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: The exact FDA package describes a deep learning program running on the Ubuntu operating system that can be deployed as an onsite server in the hospital, with users interacting with the software from a client workstation. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The software device is a computer program with a deep learning algorithm running on Ubuntu operating system." … "The device can be deployed as an onsite server in the hospital and the user interacts with the software from a client workstation.". 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.
Unresolved route: Worklist marking or indicator for suspected ICH, with an informational preview.
Scope: Exact FDA submission. FDA device description; preview is not for primary diagnosis.
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 exact FDA package describes a deep learning program running on the Ubuntu operating system that can be deployed as an onsite server in the hospital, with users interacting with the software from a client workstation. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software device is a computer program with a deep learning algorithm running on Ubuntu operating system." … "The device can be deployed as an onsite server in the hospital and the user interacts with the software from a client workstation.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact-submission ACR model card explicitly references DICOM 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.
ACR AI Central provides an exact-submission model card for InferRead CT Stroke.AI; 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
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, fda decision summary, acr ai central product, 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 K211179 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
Security: Not verified - checked 2026-09-09 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
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.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: JLK-SDH analyzes non-contrast head CT for suspected hemispheric subdural hemorrhage and sends notification to a clinician for review in parallel to standard care; PACS/mobile previews may be compressed and are non-diagnostic, while full patient evaluation and uncompressed diagnostic viewing remain required.
Authorized purpose: Enhanced Boundary for PCCT is a deep-learning CT processing function for improved soft-tissue delineation in routine head examinations with or without contrast.
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.