Authorized purpose: Notification-only, parallel-workflow triage that identifies and communicates acute non-contrast brain CT studies with suspected ICH to a specialist for image review; not for diagnosis beyond notification.
Clinical role
Parallel AI triage and notification independent of standard-of-care image interpretation.
Images and patients
CT/CTA · Brain, for suspected intracranial hemorrhage and/or hematoma.
Key limitation
Keep in mind: Identification is not for diagnostic use beyond notification. Clinicians must view the complete CT on a diagnostic viewer, perform full patient evaluation, and discuss care with a treating specialist; DeepCT must not be used in lieu of evaluation or to make or confirm a diagnosis.
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, parallel-workflow triage that identifies and communicates acute non-contrast brain CT studies with suspected ICH to a specialist for image review; not for diagnosis beyond notification.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Brain, for suspected intracranial hemorrhage and/or hematoma. Input: DICOM series of acute non-contrast CT images of the brain from patients suspected of ICH and/or hematoma.
Who uses it?Intended users: Hospital networks and trained clinicians; notified medical specialists in hospital emergency-room settings.
What does the software produce?Output: Binary ICH-present/ICH-absent interpretation result and a notification or text message identifying the study for specialist review; no other diagnostic information is generated.
What is its most important limitation?Key limitation: Identification is not for diagnostic use beyond notification. Clinicians must view the complete CT on a diagnostic viewer, perform full patient evaluation, and discuss care with a treating specialist; DeepCT must not be used in lieu of evaluation or to make or confirm a diagnosis.
Clinical takeaway. Clinical role: Notification-only, parallel-workflow triage that identifies and communicates acute non-contrast brain CT studies with suspected ICH to a specialist for image review; not for diagnosis beyond notification.
Evidence takeaway. Evidence from the reviewed source record: Retrospective multicenter, multinational performance study: 260 cases from 5 sites (2 US and 3 OUS), with approximately equal ICH-positive and ICH-negative cases. FDA reports sensitivity 93.8% (95% CI 88.3%-96.8%) and specificity 92.3% (95% CI 86.4%-95.7%), both exceeding an 80% goal. Processing time was measured in 122 cases at 30.6 seconds (95% CI 25.8-35.4 seconds); latency is distinct from the diagnostic endpoints.
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, parallel-workflow triage that identifies and communicates acute non-contrast brain CT studies with suspected ICH to a specialist for image review; not for diagnosis beyond notification.
Binary ICH-present/ICH-absent interpretation result and a notification or text message identifying the study for specialist review; no other diagnostic information is generated.
Identification is not for diagnostic use beyond notification. Clinicians must view the complete CT on a diagnostic viewer, perform full patient evaluation, and discuss care with a treating specialist; DeepCT must not be used in lieu of evaluation or to make or confirm a diagnosis.
Retrospective multicenter, multinational performance study: 260 cases from 5 sites (2 US and 3 OUS), with approximately equal ICH-positive and ICH-negative cases. FDA reports sensitivity 93.8% (95% CI 88.3%-96.8%) and specificity 92.3% (95% CI 86.4%-95.7%), both exceeding an 80% goal. Processing time was measured in 122 cases at 30.6 seconds (95% CI 25.8-35.4 seconds); latency is distinct from the diagnostic endpoints.
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
Retrospective multicenter, multinational performance study: 260 cases from 5 sites (2 US and 3 OUS), with approximately equal ICH-positive and ICH-negative cases. FDA reports sensitivity 93.8% (95% CI 88.3%-96.8%) and specificity 92.3% (95% CI 86.4%-95.7%), both exceeding an 80% goal. Processing time was measured in 122 cases at 30.6 seconds (95% CI 25.8-35.4 seconds); latency is distinct from the diagnostic endpoints.
93.8% (95% CI: 88.3%-96.8%) for identifying non-contrast CT head images containing ICH in a 260-case, 5-site retrospective study; exceeded the 80% performance goal.
FDA source
Exact FDA submission
Checked 2026-09-09
Bounds the sensitivity to the FDA ICH-detection endpoint; 96.8% is the upper sensitivity confidence bound, not a specificity value.
92.3% (95% CI: 86.4%-95.7%) for identifying non-contrast CT head images containing ICH in the same 260-case, 5-site retrospective study; exceeded the 80% performance goal.
FDA source
Exact FDA submission
Checked 2026-09-09
Corrects the active-directory conflation of the 80% goal and the 96.8% sensitivity confidence bound; FDA specificity is 92.3% with its own confidence interval.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
DeepCT 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 K182875
Samplen=260
Sites5
IndependenceIndependence not established
K182875
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 K182875. 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 series of acute non-contrast CT images of the brain from patients suspected of ICH and/or hematoma.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Software-only device with hospital-configured Image Forwarding Software and an Image Processing and Analysis Server; a copy of local DICOM files is sent for analysis, the result is shown on screen, and suspected ICH triggers specialist notification. The packet does not establish a specific local PACS/RIS/EHR interface.
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 exact FDA package describes two components: Image Forwarding Software configured by the hospital on a computer, which sends DICOM copies through a secured channel to an Image Processing and Analysis Server that runs the algorithm; where that server is hosted is not stated. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "DeepCT (Ver. 4.1.4) is a software-only device that uses two components: (1) Image Forwarding Software and (2) Image Processing and Analysis Server." … "The Image Forwarding Software is configured by the hospital to be used on a computer and is responsible for transmitting a copy of DICOM files from the local through a secured channel to the Image Processing and Analysis Server.". 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.
Source context, not route validation: Binary ICH-present/ICH-absent interpretation result and a notification or text message identifying the study for specialist review; no other diagnostic information is generated.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Binary ICH-present/ICH-absent interpretation result and a notification or text message identifying the study for specialist review; no other diagnostic information is generated.
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 exact FDA package describes two components: Image Forwarding Software configured by the hospital on a computer, which sends DICOM copies through a secured channel to an Image Processing and Analysis Server that runs the algorithm; where that server is hosted is not stated. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "DeepCT (Ver. 4.1.4) is a software-only device that uses two components: (1) Image Forwarding Software and (2) Image Processing and Analysis Server." … "The Image Forwarding Software is configured by the hospital to be used on a computer and is responsible for transmitting a copy of DICOM files from the local through a secured channel to the Image Processing and Analysis Server.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Software-only device with hospital-configured Image Forwarding Software and an Image Processing and Analysis Server; a copy of local DICOM files is sent for analysis, the result is shown on screen, and suspected ICH triggers specialist notification. The packet does not establish a specific local PACS/RIS/EHR interface.
The 510(k) summary states DeepCT is a notification-only, parallel workflow tool for use by hospital networks and trained clinicians to identify and communicate images of specific patients to a specialist, independent of standard of care workflow.
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
25Fields reviewed
9Source classes checked
8Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 8 PubMed and 0 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 8 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, 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 K182875 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: 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.