Search Results

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.

The software platform is designed to support technicians and trained physicians in qualitative and quantitative measurement and analysis of clinical data. The software platform provides the means for viewing, storing and transferring data into other systems such as PACS systems.

The software platform also provides an interface to integrate additional Siemens Healthineers' clinical processing extensions.

AI-Rad Companion Engine functionality includes:

• Interface for multi-modality and multi-vendor Input/Output of DICOM data
• Check of data validity using information of DICOM tags
• Interface for extensions that provide post-processing functionality
• Confirmation user interface for visualization of medical images processed by extensions
• Configuration user interface for configuration of the medical device and extensions

AI-Rad Companion Engine, as previously cleared under K183272, has been enhanced in version VA20. AI-Rad Companion Engine still provides the platform for all clinical extensions of the AI Rad Companion system and still falls under the same classification regulation as the predicate device. The engine supports DICOM communication, enabling post-processing extensions for medical images to be used for diagnostic purposes.

AI-Rad Companion Engine will receive the imaging data to be processed either from an imaging modality or via auto-routing from the PACS system or a DICOM gateway. The results of the AIRC Extensions will be sent back to a configurable target node also utilizing DICOM standards. The means of data transfer will be handled by the "teamplay" infrastructure. Teamplay Images is an MDDS product, intended for data transfer, display and online storage of medical images and related data.

As an update to the previously cleared device, the following modifications have been made:

• 1. Support of software version VA20:
  • a. Support for additional clinical extensions
  • b. Modified workflow to increase the usability within AI-Rad Companion as well as with respect to informing the user regarding the status of clinical extensions
• 2. Subject device claims list

The provided document is a 510(k) Premarket Notification for the Siemens AI-Rad Companion Engine, specifically for an updated version (VA20). This document primarily focuses on demonstrating substantial equivalence to a previously cleared predicate device (AI-Rad Companion Engine, K183272).

Crucially, the document states that no clinical tests were conducted for the modified AI-Rad Companion Engine VA20. This means the typical design of an AI/ML medical device approval process, which often includes a standalone performance study and a multi-reader multi-case (MRMC) comparative effectiveness study, was not performed for this specific submission. The reliance is on non-clinical bench testing and software validation to demonstrate equivalent safety and performance to the existing predicate.

Therefore, many of the requested details about acceptance criteria and study design are not applicable to this specific 510(k) submission, as it is a predicate-based clearance.

However, based on the information provided regarding the type of device and the predicate clearance strategy, we can infer some information and highlight what is explicitly stated:

Acceptance Criteria and Study Details (Based on Provided Document)

Since this 510(k) is for a software update (VA20) to an already cleared device (K183272) and relies on demonstrating substantial equivalence through non-clinical testing, there are no specific acceptance criteria for "device performance" in terms of clinical accuracy (e.g., sensitivity, specificity, accuracy) reported in this document. The acceptance criteria are instead focused on software functionality, validation, and adherence to established standards, demonstrating that the updated device is equally safe and effective as the predicate.

1. Table of Acceptance Criteria and Reported Device Performance

Given the nature of this 510(k) (software update demonstrating equivalence), the "acceptance criteria" are related to software validation and regulatory compliance, rather than clinical performance metrics. The "reported device performance" is the successful completion of these non-clinical tests.

2. Sample Size Used for the Test Set and Data Provenance

• Test Set Sample Size:
  • Clinical Data: "No clinical tests were conducted to test the performance and functionality of the modifications introduced within AI-Rad Companion Engine VA20." Therefore, no clinical test set sample size is reported.
  • Non-Clinical Data: The document mentions "Unit, System and Integration" bench testing and "software verification and regression testing." The exact number of test cases or "samples" for these software tests is not specified in the provided text.
• Data Provenance: Not applicable as clinical data was not used for this submission. The origin of the data used for software verification (e.g., simulated data, internal test data) is not detailed.

3. Number of Experts Used to Establish Ground Truth for the Test Set and Qualifications of Experts

• Not applicable for this submission, as no clinical test set requiring expert ground truth was used. The submission relies on non-clinical software validation and equivalence to a predicate.

4. Adjudication Method for the Test Set

• Not applicable for this submission, as no clinical test set requiring adjudication was used.

5. If a Multi-Reader Multi-Case (MRMC) Comparative Effectiveness Study was done, and the Effect Size of How Much Human Readers Improve with AI vs. Without AI Assistance

• No MRMC study was done for this specific 510(k) submission. The document explicitly states: "No clinical tests were conducted to test the performance and functionality of the modifications introduced within AI-Rad Companion Engine VA20."

6. If a Standalone (i.e., algorithm only without human-in-the-loop performance) Study was done

• No standalone clinical performance study was done for this specific 510(k) submission. As stated: "No clinical tests were conducted..."

7. The Type of Ground Truth Used

• Not applicable for clinical ground truth: Since no clinical studies were performed, there was no need for clinical ground truth (e.g., expert consensus, pathology, outcome data).
• Operational Ground Truth: For the software validation, the "ground truth" would be established against the defined software requirements and specifications, which are verified through various levels of testing (unit, system, integration) designed to confirm the software performs as expected.

8. The Sample Size for the Training Set

• Not applicable: The AI-Rad Companion Engine is described as a "software platform that provides basic visualization and enables external post-processing extensions." It is the engine that interfaces with clinical processing extensions. The nature of this "Engine" (a platform) and the fact that it's an update means it's unlikely to have its own "training set" in the sense of a machine learning model. If ML models are part of the "clinical processing extensions," those would have their own training sets and validation processes, but they are not the subject of this 510(k) submission (which cleared the engine). The document doesn't mention any de novo training of AI/ML models for this submission.

9. How the Ground Truth for the Training Set Was Established

• Not applicable: As there's no mentioned training set for this device (the Engine), the establishment of ground truth for a training set is not covered.

Summary of Device and Approval Strategy:

The AI-Rad Companion Engine is a Class II Picture Archiving and Communication System (PACS) with specific functionalities providing a platform for connecting to "clinical processing extensions." This 510(k) (K193294) is for an update (software version VA20) to an already cleared predicate device (K183272).

The core of this 510(k) submission is to demonstrate substantial equivalence to the predicate device. This is achieved by showing that despite enhancements (e.g., support for additional clinical extensions, modified workflow), the updated device maintains an equivalent safety and performance profile. This demonstration primarily relies on non-clinical bench testing and software validation, as explicitly stated: "No clinical tests were conducted to test the performance and functionality of the modifications introduced within AI-Rad Companion Engine VA20."

Ask a specific question about this device