DicomConfigArgs

data class DicomConfigArgs(val filterProfile: Output<DicomConfigFilterProfile>? = null, val keepList: Output<TagFilterListArgs>? = null, val removeList: Output<TagFilterListArgs>? = null, val skipIdRedaction: Output<Boolean>? = null) : ConvertibleToJava<DicomConfigArgs>

Specifies the parameters needed for de-identification of DICOM stores.

Constructors

Link copied to clipboard
fun DicomConfigArgs(filterProfile: Output<DicomConfigFilterProfile>? = null, keepList: Output<TagFilterListArgs>? = null, removeList: Output<TagFilterListArgs>? = null, skipIdRedaction: Output<Boolean>? = null)

Functions

Link copied to clipboard
open override fun toJava(): DicomConfigArgs

Properties

Link copied to clipboard

Tag filtering profile that determines which tags to keep/remove.

Link copied to clipboard
val keepList: Output<TagFilterListArgs>? = null

List of tags to keep. Remove all other tags.

Link copied to clipboard
val removeList: Output<TagFilterListArgs>? = null

List of tags to remove. Keep all other tags.

Link copied to clipboard
val skipIdRedaction: Output<Boolean>? = null

If true, skip replacing StudyInstanceUID, SeriesInstanceUID, SOPInstanceUID, and MediaStorageSOPInstanceUID and leave them untouched. The Cloud Healthcare API regenerates these UIDs by default based on the DICOM Standard's reasoning: "Whilst these UIDs cannot be mapped directly to an individual out of context, given access to the original images, or to a database of the original images containing the UIDs, it would be possible to recover the individual's identity." http://dicom.nema.org/medical/dicom/current/output/chtml/part15/sect_E.3.9.html