FDA-cleared profile

syngo.CT Brain Hemorrhage

Siemens Medical Solutions USA, Inc. · CT/CTA · FDA-cleared (510(k))

Authorized purpose: Assist radiologists in prioritizing suspected intracranial hemorrhage, including subarachnoid hemorrhage, on non-contrast head CT through case-level worklist output; the output is informational and not diagnostic.

Clinical role
Parallel notification and worklist prioritization for suspected ICH or SAH, independent of the standard-of-care reading queue; all original images remain available for clinical review.
Images and patients
CT/CTA · Head/brain, including intracranial and subarachnoid spaces
Key limitation
Keep in mind: Output is informational only, not for diagnostic use, and not for standalone diagnosis. The device does not direct attention to a specific location, alter the original image, or remove cases from the worklist. The FDA endpoints distinguish ICH from SAH, and the input is non-contrast head CT rather than CTA.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Assist radiologists in prioritizing suspected intracranial hemorrhage, including subarachnoid hemorrhage, on non-contrast head CT through case-level worklist output; the output is informational and not diagnostic.
  • Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head/brain, including intracranial and subarachnoid spaces Input: DICOM-conformant, diagnostic-quality non-contrast head CT reconstructions from Siemens and other CT vendors; the labeled modality is non-contrast CT and the packet does not impose a Siemens-only restriction.
  • Who uses it?Intended users: Radiologists and clinical administrators
  • What does the software produce?Output: Case-level output indicating suspected hemorrhage, suspected hemorrhage including the subarachnoid space, or processing finished, made available to a CT scanner or PACS for worklist prioritization; the original image is not marked or altered.
  • What is its most important limitation?Key limitation: Output is informational only, not for diagnostic use, and not for standalone diagnosis. The device does not direct attention to a specific location, alter the original image, or remove cases from the worklist. The FDA endpoints distinguish ICH from SAH, and the input is non-contrast head CT rather than CTA.

Clinical takeaway. Clinical role: Assist radiologists in prioritizing suspected intracranial hemorrhage, including subarachnoid hemorrhage, on non-contrast head CT through case-level worklist output; the output is informational and not diagnostic.

Evidence takeaway. Evidence from the reviewed source record: FDA K232431 reports a retrospective standalone study of 900 anonymized head CT cases from 5 sites in the US and Europe with approximately equal positive and negative cases; ground truth used majority reading by three US board-certified neuroradiologists with more than 10 years of experience. For ICH, sensitivity was 95.0% (95% CI 92.5-96.7) and specificity 93.1% (95% CI 90.5-95.1). For SAH, sensitivity was 86.1% (95% CI 81.1-90.0) and specificity 85.2% (95% CI 82.3-87.7). Average per-case processing time was 13.34 seconds (95% CI 9.16-17.51).

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
Assist radiologists in prioritizing suspected intracranial hemorrhage, including subarachnoid hemorrhage, on non-contrast head CT through case-level worklist output; the output is informational and not diagnostic.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow role
Parallel notification and worklist prioritization for suspected ICH or SAH, independent of the standard-of-care reading queue; all original images remain available for clinical review.
  • Exact FDA submission
  • Checked 2026-09-08
Required input
DICOM-conformant, diagnostic-quality non-contrast head CT reconstructions from Siemens and other CT vendors; the labeled modality is non-contrast CT and the packet does not impose a Siemens-only restriction.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
Case-level output indicating suspected hemorrhage, suspected hemorrhage including the subarachnoid space, or processing finished, made available to a CT scanner or PACS for worklist prioritization; the original image is not marked or altered.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Acute care
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Radiologists and clinical administrators
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
Output is informational only, not for diagnostic use, and not for standalone diagnosis. The device does not direct attention to a specific location, alter the original image, or remove cases from the worklist. The FDA endpoints distinguish ICH from SAH, and the input is non-contrast head CT rather than CTA.
  • Exact FDA submission
  • Checked 2026-09-08
Evidence summary
FDA K232431 reports a retrospective standalone study of 900 anonymized head CT cases from 5 sites in the US and Europe with approximately equal positive and negative cases; ground truth used majority reading by three US board-certified neuroradiologists with more than 10 years of experience. For ICH, sensitivity was 95.0% (95% CI 92.5-96.7) and specificity 93.1% (95% CI 90.5-95.1). For SAH, sensitivity was 86.1% (95% CI 81.1-90.0) and specificity 85.2% (95% CI 82.3-87.7). Average per-case processing time was 13.34 seconds (95% CI 9.16-17.51).
  • Exact FDA submission
  • Checked 2026-09-08

Evidence

Performance evidence

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 K232431 reports a retrospective standalone study of 900 anonymized head CT cases from 5 sites in the US and Europe with approximately equal positive and negative cases; ground truth used majority reading by three US board-certified neuroradiologists with more than 10 years of experience. For ICH, sensitivity was 95.0% (95% CI 92.5-96.7) and specificity 93.1% (95% CI 90.5-95.1). For SAH, sensitivity was 86.1% (95% CI 81.1-90.0) and specificity 85.2% (95% CI 82.3-87.7). Average per-case processing time was 13.34 seconds (95% CI 9.16-17.51).
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
ICH: 95.0% (95% CI 92.5%-96.7%); SAH: 86.1%.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

FDA K232431 reports distinct intracranial-hemorrhage and subarachnoid-hemorrhage endpoints.

Reported specificity
ICH: 93.1% (95% CI 90.5%-95.1%); SAH: 85.2%.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

FDA K232431 reports distinct intracranial-hemorrhage and subarachnoid-hemorrhage endpoints.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

syngo.CT Brain Hemorrhage regulatory performance study summary

  • DesignStand-Alone Performance
  • PopulationPopulation described in the exact-submission ACR model card
  • Scopeexact submission
  • Tested version2
  • Samplen=900
  • Sites5
  • IndependenceIndependence not established

K232431

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

Safety and lifecycle

Postmarket record

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 K232431. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: DICOM-conformant, diagnostic-quality non-contrast head CT reconstructions from Siemens and other CT vendors; the labeled modality is non-contrast CT and the packet does not impose a Siemens-only restriction.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-08 · FDA K232431: syngo.CT Brain Hemorrhage

  2. Routing

    Source context, not route validation: The packet describes DICOM-conformant head CT input, case-level output to a CT scanner or PACS, and deployment compatibility with the SOMARIS-X and syngo.via host systems. Specific interface versions and local compatibility are not established.

    Scope: Exact FDA submission.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-08 · FDA K232431: syngo.CT Brain Hemorrhage

  3. AI processing

    Source context, not route validation: The exact FDA package describes deployment compatibility with the SOMARIS-X platform and the syngo.via platform, with syngo.via host-system compatibility added over the predicate. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Additional deployment compatibility with the syngo.via host system." … "Deployment Compatibility SOMARIS-X platform, SOMARIS-X platform Extended syngo.via platform". 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.

    Field checked 2026-11-14 · FDA K232431: syngo.CT Brain Hemorrhage

  4. Returned objects

    Source context, not route validation: Case-level output indicating suspected hemorrhage, suspected hemorrhage including the subarachnoid space, or processing finished, made available to a CT scanner or PACS for worklist prioritization; the original image is not marked or altered.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-08 · FDA K232431: syngo.CT Brain Hemorrhage

  5. Viewer/worklist/report

    Unresolved route: Case-level output indicating suspected hemorrhage, suspected hemorrhage including the subarachnoid space, or processing finished, made available to a CT scanner or PACS for worklist prioritization; the original image is not marked or altered.

    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.

    Field checked 2026-09-08 · FDA K232431: syngo.CT Brain Hemorrhage

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
The exact FDA package describes deployment compatibility with the SOMARIS-X platform and the syngo.via platform, with syngo.via host-system compatibility added over the predicate. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Additional deployment compatibility with the syngo.via host system." … "Deployment Compatibility SOMARIS-X platform, SOMARIS-X platform Extended syngo.via platform". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The packet describes DICOM-conformant head CT input, case-level output to a CT scanner or PACS, and deployment compatibility with the SOMARIS-X and syngo.via host systems. Specific interface versions and local compatibility are not established.
  • Exact FDA submission
  • Checked 2026-09-08
Security
Siemens Healthineers' corporate cybersecurity page states a Secure Development Lifecycle addressing pre-market and post-market phases for products under development and a range of existing offerings; a Cybersecurity Management Service maintaining a product security inventory (over 1,000 product versions and over 21,000 monitored software components) with security whitepapers, SBOMs and vulnerability assessments available to customers via teamplay Fleet; incident and vulnerability management channels; and that Siemens Healthineers AG maintains an independent certification of its global Cybersecurity Management System to ISO/IEC 27001:2022 extended by ISO/IEC 27701:2019, with the certificate referenced to the SGS directory. Vendor statement; no certificate or report was read.
  • Vendor-wide
  • Checked 2026-10-26

Vendor statement, not an attestation. Identity bridge: Siemens Healthineers' own corporate-info page names Siemens Medical Solutions USA, Inc. (Malvern, PA), and its 2024 governance press release states Siemens Healthcare GmbH's business was transferred to Siemens Healthineers AG. Corporate program statement; exact-release scope is not established.

Monitoring
Siemens Healthineers' cybersecurity page states that its Cybersecurity Management Service maintains a product security inventory of over 1,000 product versions and over 21,000 monitored software components, with security whitepapers, SBOMs and vulnerability assessments delivered via teamplay Fleet, and that it operates incident and vulnerability management.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. The page names Siemens Healthineers generally and does not scope these commitments to any specific product release; exact-release scope is not established.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for syngo.CT Brain Hemorrhage; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
Sources & review details FDA 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.

FDA submission
K232431
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Head/brain, including intracranial and subarachnoid spaces
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2024-03-22
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
24Fields reviewed
9Source 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, 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 K232431 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.

8 sources - 3 history items

Source ledger

  1. FDA K232431: syngo.CT Brain Hemorrhage

    U.S. Food and Drug Administration - Published 2024-03-22 - Accessed 2026-09-08

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. syngo.CT Brain Hemorrhage model card (K232431)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, output, reportedSensitivity, reportedSpecificity, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K232431

    U.S. Food and Drug Administration - Accessed 2026-09-08

    Scope: postmarketSafety

  8. Siemens Healthineers: Cybersecurity

    Siemens Healthineers - Accessed 2026-10-26

    Scope: security

Research history

  1. K232431 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K252421

JLK-NCCT

JLK, Inc.

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
Decision
2026-03-24
FDA-cleared K251983

Brainomix 360 Triage Stroke

Brainomix Limited

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
Decision
2025-08-26
FDA-cleared K251590

Methinks CTA Stroke

Methinks Software S.L.

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.

Modality
CT/CTA
Anatomy
Brain
Decision
2025-08-20

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history