13.1.1. Introduction

Designed for the Clara Deploy SDK, the Clara DICOM Adapter implements the necessary DICOM services for interoperability between Clara and other medical devices. The Clara DICOM Adapter allows you to send/receive DICOM objects using standard DICOM protocols and interpret standard DICOM part-10 formats.

13.1.1.1. Requirements

  • This container requires Docker 18.09.2 or higher.

  • Helm v2.15.2 or higher.

  • Kubernetes v1.15.12.

13.1.1.2. Usages

13.1.1.2.1. DICOM SCP Service

The SCP service accepts standard DICOM C-ECHO and C-STORE commands. Please see the DICOM Interface section for more information.

All received instances are saved immediately to the configured temporary storage location (storage>temporary). With the default file processor (Nvidia.Clara.Dicom.Processors.JobProcessor), all received instances are uploaded to the Clara Payloads CRD service after the timeout elapses.

Received DICOM instances are stored on disk as-is using the original transfer syntax described in the DICOM Interface section. Users of the Clara Deploy SDK must handle the encoding/decoding of the DICOM files in their container(s). See Third Party Tools for a list of DICOM toolkits available for parsing, encoding, and decoding DICOM files.

13.1.1.2.2. DICOM SCU Service

The DICOM SCU Service, which is part of the Clara DICOM Adapter, queries the Clara Results Service for available tasks using the Clara SCU AET as the agent name (dicom>scu>ae-title). Each retrieved task contains a list of DICOM files to be exported to the configured DICOM devices. If more than 50% of the files fails to be exported, the job is marked as failed and reported back to the Results Service–it will be retried up to three times at a later time.

Note

DICOM instances are sent as-is; no codec conversion is done as part of the SCU process. See the DICOM Interface section for more information.

13.1.1.3. DICOM Interface

The following reference describes the connectivity capabilities of Clara Deploy SDK out of the box. Users implementing the Clara Deploy SDK must update their DICOM Conformance Statement according to the actual capabilities of their application.

13.1.1.3.1. DICOM SCP

Clara DICOM SCP implements C-ECHO and C-Store services to interface with other medical devices, such as PACS. It allows users to define multiple AE Titles to enable DICOM communication and maps each AE Title to a pipeline.

13.1.1.3.1.1. DIMSE Services (SCP)

  • C-STORE: Accepts incoming DICOM objects

  • C-ECHO: Accepts incoming DICOM verification requests

13.1.1.3.1.2. SOP Classes (Transfer) and Transfer Syntax Supported

Clara DICOM SCP accepts any proposed transfer syntaxes and stores any accepted instances as-is on disk without any decoding support. Each AE Title may be configured to ignore and not save certain SOP Classes.

13.1.1.3.1.3. Association Policies

  • Clara DICOM Storage SCP accepts associations but does not initiate associations.

  • Clara DICOM Storage SCP accepts two (configurable) simultaneous associations.

  • Asynchronous mode is not supported. All operations are performed synchronously.

  • The Implementation Class UID is “1.3.6.1.4.1.30071.8” and the Implementation Version Name is “fo-dicom 4.0.0”.

  • An association must be released properly for received instances to be associated with a pipeline. Files received from an aborted association or an interrupted connection are either removed immediately or removed based on a configured timeout value.

13.1.1.3.1.4. Security Profiles

Clara DICOM Storage SCP does not conform to any defined DICOM Security Profiles. It is assumed that the product is used within a secured environment that uses a firewall, router protection, VPN, and/or other network security provisions.

The Clara DICOM Storage SCP service can be configured to check the following DICOM values when determining whether to accept Association Open Requests:

  • Calling AE Title

  • Called AE Title

Clara SCP AE Title can be configured to accept Association Requests from only a limited list of Calling AE Titles.

13.1.1.3.2. DICOM SCU

The Clara DICOM Storage SCU provides the DICOM Storage Service for interfacing with other medical devices such as PACS. It is executed at system startup and exists in a container using a single configurable AE Title.

13.1.1.3.2.1. DIMSE Services (SCU)

C-STORE: Sends processed results that are stored in DICOM format

The Clara DICOM Storage SCU initiates a push of DICOM objects to the Remote DICOM Storage SCP. The system allows multiple remote SCPs to be configured.

13.1.1.3.2.2. SOP Classes (Transfer) Supported and Transfer Syntax

The DICOM Store SCU service supports all SOP classes of the Storage Service Class. The DICOM Store SCU service transfers a DICOM object as-is using the stored Transfer Syntax, without the support of compression, decompression, or Transfer Syntax Conversion.

13.1.1.3.2.3. Association Policies

  • Clara DICOM Storage SCU initiates associations but does not accept associations.

  • Clara DICOM Storage SCU allows two (configurable) SCU instances simultaneously.

  • Asynchronous mode is not supported. All operations are performed synchronously.

  • The Implementation Class UID is “1.3.6.1.4.1.30071.8” and the Implementation Version Name is “fo-dicom 4.0.0”.

13.1.1.3.2.4. Security Profiles

Not applicable

13.1.1.4. Changelog

13.1.1.4.1. 0.6.0

  • ➕New: configure Clara AE-Titles, Sources and *Destinations via Kubernetes CRD is added which allows user to add a new Clara AE-Title and associate it with a Clara Pipeline without restarting DICOM Adapter. DICOM sources and destination can also be added via CRD.

  • ➖Removed: timeout-group is no longer supported. This can be replaced by custom plug-in if required. timeout is still supported to accept multiple associations and associate al received DICOM instances with a Clara job.

13.1.1.5. Third Party Tools

13.1.1.5.1. DICOM Toolkits