FDA-cleared profile

AI-Rad Companion Engine

Siemens Medical Solutions USA, Inc. · Radiological images; modality varies or is not specified in FDA list · FDA-cleared (510(k))

Authorized purpose: AI-Rad Companion Engine is a software platform that provides basic visualization and enables external post-processing extensions for medical images used for diagnostic purposes. It supports technicians and trained physicians in qualitative and quantitative measurement and analysis, stores data, transfers data to other systems such as PACS, validates DICOM tags, and provides interfaces for clinical extensions.

Clinical role
Multimodality image viewing, processing, analysis, measurement, comparison, and reporting under professional review.
Images and patients
Radiological images; modality varies or is not specified in FDA list · Medical images and clinical data represented in multimodality DICOM studies
Key limitation
Keep in mind: The exact submission is a platform for visualization and extension integration; extension-specific clinical uses, populations, and performance must be verified separately against the exact extension submission.

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: AI-Rad Companion Engine is a software platform that provides basic visualization and enables external post-processing extensions for medical images used for diagnostic purposes. It supports technicians and trained physicians in qualitative and quantitative measurement and analysis, stores data, transfers data to other systems such as PACS, validates DICOM tags, and provides interfaces for clinical extensions.
  • Which images or clinical context are in scope?Modality: Radiological images; modality varies or is not specified in FDA list Anatomy or clinical context: Medical images and clinical data represented in multimodality DICOM studies Input: Supported DICOM CT, MR, PET, SPECT, X-ray, ultrasound, or other labeled medical-image inputs.
  • Who uses it?Intended users: Trained physicians, radiologists, technologists, and other medical-image professionals.
  • What does the software produce?Output: Multimodality images, fused views, quantitative results, contours, measurements, and reports for professional review.
  • What is its most important limitation?Key limitation: The exact submission is a platform for visualization and extension integration; extension-specific clinical uses, populations, and performance must be verified separately against the exact extension submission.

Clinical takeaway. Clinical role: AI-Rad Companion Engine is a software platform that provides basic visualization and enables external post-processing extensions for medical images used for diagnostic purposes. It supports technicians and trained physicians in qualitative and quantitative measurement and analysis, stores data, transfers data to other systems such as PACS, validates DICOM tags, and provides interfaces for clinical extensions.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports only non-clinical testing of AI-Rad Companion Engine VA20: software validation and bench testing, unit, system and integration testing of new features and software updates, and software verification and regression testing that met previously determined acceptance criteria. No clinical tests were conducted for the VA20 modifications, and no animal testing was performed. Results are as reported in the FDA submission, not independent validation.

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
AI-Rad Companion Engine is a software platform that provides basic visualization and enables external post-processing extensions for medical images used for diagnostic purposes. It supports technicians and trained physicians in qualitative and quantitative measurement and analysis, stores data, transfers data to other systems such as PACS, validates DICOM tags, and provides interfaces for clinical extensions.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Multimodality image viewing, processing, analysis, measurement, comparison, and reporting under professional review.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported DICOM CT, MR, PET, SPECT, X-ray, ultrasound, or other labeled medical-image inputs.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Multimodality images, fused views, quantitative results, contours, measurements, and reports for professional review.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Clinical image-review and post-processing environments within the labeled workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Trained physicians, radiologists, technologists, and other medical-image professionals.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
The exact submission is a platform for visualization and extension integration; extension-specific clinical uses, populations, and performance must be verified separately against the exact extension submission.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports only non-clinical testing of AI-Rad Companion Engine VA20: software validation and bench testing, unit, system and integration testing of new features and software updates, and software verification and regression testing that met previously determined acceptance criteria. No clinical tests were conducted for the VA20 modifications, and no animal testing was performed. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Non-clinical tests were conducted to test the functionality of AI-Rad Companion Engine version VA20." … "Software validation and bench testing have been conducted to the performance claims as well as the claim of substantial equivalence to the predicate device.". Read from the exact FDA decision document on 2026-11-14.

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
The exact FDA document reports only non-clinical testing of AI-Rad Companion Engine VA20: software validation and bench testing, unit, system and integration testing of new features and software updates, and software verification and regression testing that met previously determined acceptance criteria. No clinical tests were conducted for the VA20 modifications, and no animal testing was performed. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Non-clinical tests were conducted to test the functionality of AI-Rad Companion Engine version VA20." … "Software validation and bench testing have been conducted to the performance claims as well as the claim of substantial equivalence to the predicate device.". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.

Reported specificity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.

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

K193294 FDA decision evidence package for AI-Rad Companion Engine

  • DesignFDA decision evidence and product verification described in the exact submission or PMA decision record.
  • PopulationMedical images and clinical data represented in multimodality DICOM studies
  • Scopeexact submission
  • Tested versionAI-Rad Companion Engine configuration described in K193294
  • IndependenceSponsor or vendor study

K193294

FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation unless the exact source expressly establishes that distinction; local technical, clinical, privacy, security, and workflow acceptance remains necessary.

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 2026-09-02 openFDA device-recall snapshot contained no record matched to K193294 by exact native submission identifier. This does not exclude product-family, later-version, or adverse-event information.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-04

Exact-identifier review does not prove absence of all product-family safety signals.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

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: Supported DICOM CT, MR, PET, SPECT, X-ray, ultrasound, or other labeled medical-image inputs.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K193294: AI-Rad Companion Engine

  2. Routing

    Source context, not route validation: The exact FDA package describes multi-modality and multi-vendor DICOM input and output, data-validity checks, and configurable result transfer to a target node through the teamplay infrastructure; verify the installed extension, identity, routing, archive, and downtime behavior.

    Scope: Exact FDA submission. This is a partial interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K193294: AI-Rad Companion Engine

  3. AI processing

    Unresolved route: Not established for the exact route.

    Scope: Exact FDA submission. The exact public FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-04 ·

  4. Returned objects

    Source context, not route validation: Multimodality images, fused views, quantitative results, contours, measurements, and reports for professional review.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K193294: AI-Rad Companion Engine

  5. Viewer/worklist/report

    Unresolved route: Multimodality images, fused views, quantitative results, contours, measurements, and reports for professional review.

    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-04 · FDA 510(k) decision material K193294: AI-Rad Companion Engine

  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

Integration
The exact FDA package describes multi-modality and multi-vendor DICOM input and output, data-validity checks, and configurable result transfer to a target node through the teamplay infrastructure; verify the installed extension, identity, routing, archive, and downtime behavior.
  • Exact FDA submission
  • Checked 2026-09-04

This is a partial interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

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.

Training
Only trained physicians, radiologists, technologists, and other medical-image professionals should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor K193294 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The exact submission is a platform for visualization and extension integration; extension-specific clinical uses, populations, and performance must be verified separately against the exact extension submission.
  • Exact FDA submission
  • Checked 2026-09-04

This is buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.

Release and scope verification

Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K193294 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared or authorized release includes them.

Deployment boundary

The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.

exact submission · checked 2026-09-04

FDA-described topology does not establish current hosting contracts, security controls, uptime, or local qualification.

Interoperability acceptance

The exact FDA package describes multi-modality and multi-vendor DICOM input and output, data-validity checks, and configurable result transfer to a target node through the teamplay infrastructure; verify the installed extension, identity, routing, archive, and downtime behavior.

exact submission · checked 2026-09-04

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.

Clinical acceptance

Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The exact submission is a platform for visualization and extension integration; extension-specific clinical uses, populations, and performance must be verified separately against the exact extension submission.

exact submission · checked 2026-09-04

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.

exact submission · checked 2026-09-04

No exact-product price or reimbursement determination was promoted.

Lifecycle monitoring

Monitor K193294 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The exact submission is a platform for visualization and extension integration; extension-specific clinical uses, populations, and performance must be verified separately against the exact extension submission.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.

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
K193294
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Radiological images; modality varies or is not specified in FDA list
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Medical images and clinical data represented in multimodality DICOM studies
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-07-10
  • 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
27Fields 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, fda decision material, 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 publicly available - checked 2026-09-04 - Exact FDA submission

    No public list price for the exact cleared or authorized configuration was found. Obtain a written quote separating license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.

  • 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-04 - Exact FDA submission

    No exact-product reimbursement determination was promoted in this timeboxed review. Verify payer, site-of-service, coding, coverage, and local payment assumptions independently.

  • Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission

    The exact public FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.

  • 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

6 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K193294: AI-Rad Companion Engine

    U.S. Food and Drug Administration - Published 2020-07-10 - Accessed 2026-09-04

    Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

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

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

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

    Scope: evidenceDiscovery, studyStatus

  5. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  6. Siemens Healthineers: Cybersecurity

    Siemens Healthineers - Accessed 2026-10-26

    Scope: security

Research history

  1. K193294 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 K253969

ADAS 3D

Adas3D Medical S.L.

Authorized purpose: ADAS 3D supports visualization and analysis of MR and CT images of the heart for individual patients with cardiovascular disease, including patients with myocardial scar from ischemic or non-ischemic heart disease. Qualified professionals may use it for cardiac calculation, quantification, visualization, pre-planning, and electrophysiology procedures; produced data support clinical decision-making and must not be used as irrefutable medical advice or for radiotherapy planning, dose calculation, or treatment delivery.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Heart; myocardial scar and cardiac structures
Decision
2026-06-29
FDA-cleared K260316

CMN Capillary Function with Oncology Virtual Expert

Cercare Medical A/S

Authorized purpose: Cercare Neurosuite with Capillary Function and Oncology Virtual Expert processes CT or MR information to provide perfusion, tissue-blood-volume, diffusion, labeling, and quantification support for adult brain glioma workflows.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Brain
Decision
2026-06-22
FDA-cleared K261713

Synapse PACS (7.6.0)

FUJIFILM Healthcare Americas Corporation

Synapse PACS 7.6.0 provides medical-image management and processing, including measurements, regional segmentation, clinical calculations, structured reports, comparison, fusion, and volume rendering to aid reading, interpretation, reporting, and treatment planning.

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
N/A
Decision
2026-06-18
FDA-cleared K252563

Neurophet SCALE PET

Neurophet., Inc.

Authorized purpose: Brain MRI/PET registration, segmentation and quantitative PET assessment

Modality
Radiological images; modality varies or is not specified in FDA list
Anatomy
Brain
Decision
2026-05-15

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