Authorized purpose: Provides a parallel triage workflow for head CT images with suspected intracranial hemorrhage and/or mass effect for radiologist prioritization.
Clinical role
Triage tool that automatically analyzes head CT DICOM images as they arrive in PACS for suspected intracranial hemorrhage and/or mass effect and identifies them in a radiologist's worklist; not to be relied on to make or confirm a diagnosis.
Images and patients
CT/CTA · Brain
Key limitation
Keep in mind: Notification only, not diagnostic; requires full evaluation, previews outside the DICOM viewer are informational, and cases remain on the standard worklist.
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: Provides a parallel triage workflow for head CT images with suspected intracranial hemorrhage and/or mass effect for radiologist prioritization.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain Input: DICOM noncontrast head CT images arriving in PACS.
Who uses it?Intended users: Hospital networks, trained clinicians, and radiologists.
What does the software produce?Output: Radiologist worklist notifications, optional HL7 messages and DICOM secondary series, and non-diagnostic previews.
What is its most important limitation?Key limitation: Notification only, not diagnostic; requires full evaluation, previews outside the DICOM viewer are informational, and cases remain on the standard worklist.
Clinical takeaway. Clinical role: Provides a parallel triage workflow for head CT images with suspected intracranial hemorrhage and/or mass effect for radiologist prioritization.
Evidence takeaway. Evidence from the reviewed source record: Separate retrospective trials at over 20 sites reported ICH sensitivity 0.899, mass-effect sensitivity 0.964, mass-effect specificity 0.911, and notification time 0.23 minutes; the printed ICH specificity interval is internally invalid and is not used.
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
Provides a parallel triage workflow for head CT images with suspected intracranial hemorrhage and/or mass effect for radiologist prioritization.
Exact FDA submission
Checked 2026-09-15
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Triage tool that automatically analyzes head CT DICOM images as they arrive in PACS for suspected intracranial hemorrhage and/or mass effect and identifies them in a radiologist's worklist; not to be relied on to make or confirm a diagnosis.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software automatically analyzes Digital Imaging and Communications in Medicine (DICOM) images as they arrive in the Picture Archive and Communication System (PACS) using machine learning algorithms." … "Specifically, the software analyzes head CT images of the brain to assess the suspected presence of intracranial hemorrhage and/or mass effect and identifies images with potential emergent findings in a radiologist’s worklist.". Read from the exact FDA decision document on 2026-11-14.
Used by hospital networks and trained clinicians on head CT images of the brain to aid radiologists in prioritizing review.
Exact FDA submission
Checked 2026-11-14
Packet wording: "NinesAI is a parallel workflow tool indicated for use by hospital networks and trained clinicians to identify images of specific patients to a radiologist, independent of standard of care workflow, to aid in prioritizing and performing the radiological review." … "Specifically, the software analyzes head CT images of the brain to assess the suspected presence of intracranial hemorrhage and/or mass effect". Read from the exact FDA decision document on 2026-11-14.
Notification only, not diagnostic; requires full evaluation, previews outside the DICOM viewer are informational, and cases remain on the standard worklist.
Separate retrospective trials at over 20 sites reported ICH sensitivity 0.899, mass-effect sensitivity 0.964, mass-effect specificity 0.911, and notification time 0.23 minutes; the printed ICH specificity interval is internally invalid and is not used.
Exact FDA submission
Checked 2026-09-15
Submission-reported endpoints with an explicitly quarantined invalid interval.
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
Separate retrospective trials at over 20 sites reported ICH sensitivity 0.899, mass-effect sensitivity 0.964, mass-effect specificity 0.911, and notification time 0.23 minutes; the printed ICH specificity interval is internally invalid and is not used.
FDA source
Exact FDA submission
Checked 2026-09-15
Submission-reported endpoints with an explicitly quarantined invalid interval.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
NinesAI-ICH 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 K193351
Sites20
IndependenceIndependence not established
K193351
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 K193351. 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 noncontrast head CT images arriving in PACS.
Scope: Exact FDA submission. FDA packet input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and HL7 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 NinesAI as a complete software package comprising image analysis software and a workstation module that is used to alert the radiologist. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The software system is a complete package comprised of image analysis software and a workstation module that is used to alert the radiologist.". 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: Radiologist worklist notifications, optional HL7 messages and DICOM secondary series, and non-diagnostic previews.
Scope: Exact FDA submission. FDA packet output scope.
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 NinesAI as a complete software package comprising image analysis software and a workstation module that is used to alert the radiologist. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The software system is a complete package comprised of image analysis software and a workstation module that is used to alert the radiologist.". 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 and HL7 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.
The 510(k) summary states NinesAI is a parallel workflow tool indicated for use by hospital networks and trained clinicians to identify images of specific patients to a radiologist, independent of standard of care workflow, to aid in prioritizing and performing the radiological review, and that all radiological studies are still reviewed by trained radiologists.
Exact FDA submission
Checked 2026-10-27
User qualification wording only; the summary specifies no training program or training offering for this device.
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 K193351 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
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: 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.
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.
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.