Skip to content

DICOM Adapter Upgrade Guide

Egor Radchenko edited this page Apr 17, 2020 · 3 revisions

To version 0.2.0

Due to changed entrypoint in Import/Export Adapter images, this part of yaml configuration

command:
            - "/import/bin/import" (or "/export/bin/export")
            ... (adapter parameters)

changed to:

args:
            ... (adapter parameters)

To version 0.1.1

Import Adapter

Users must make the following changes to their dicom_adapter.yaml file.

  • The container image URL must be updated to the new gcr.io URL.

    image: gcr.io/cloud-healthcare-containers/healthcare-api-dicom-dicomweb-adapter-import:0.1.1

  • The --dicomweb_address parameter must be specified, instead of the --dicomweb_addr and --dicomweb_stow_path parameters. The value of the dicomweb_address parameter must be the full DICOMweb path, up to /dicomWeb. For example:

    dicomweb_address=https://healthcare.googleapis.com/v1beta1/projects/myproject/locations/us-central1/datasets/mydataset/dicomStores/mydicomstore/dicomWeb

    Note that C-STORE will still work with the deprecated parameters --dicomweb_addr and --dicomweb_stow_path, however C-FIND, C-MOVE, and Storage Commitment will not.

Export Adapter

Users must make the following changes to their dicom_adapter.yaml file.

  • The container image URL must be updated to the new gcr.io URL.

    image: gcr.io/cloud-healthcare-containers/healthcare-api-dicom-dicomweb-adapter-export:0.1.1

  • The --peer_dicomweb_address parameter should be specified, instead of the --peer_dicomweb_addr and --peer_dicomweb_stow_path parameters. The value of the peer_dicomweb_address parameter must be the full DICOMweb path, up to /dicomWeb. For example:

    peer_dicomweb_address=https://healthcare.googleapis.com/v1beta1/projects/myproject/locations/us-central1/datasets/mydataset/dicomStores/mydicomstore/dicomWeb

    The export adapter will still work with either the new parameter or the old parameter. It has been updated for consistency with the import adapter.