diff --git a/.github/workflows/gradleBuild.yml b/.github/workflows/gradleBuild.yml index af0952c..12ab6fc 100644 --- a/.github/workflows/gradleBuild.yml +++ b/.github/workflows/gradleBuild.yml @@ -19,18 +19,33 @@ jobs: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v3 - name: Set up Java - uses: actions/setup-java@v2 + uses: actions/setup-java@v3 with: - java-version: '17' - distribution: 'adopt' + java-version: '11' + distribution: 'temurin' - name: Build with Gradle - uses: gradle/gradle-build-action@4137be6a8bf7d7133955359dbd952c0ca73b1021 + uses: gradle/gradle-build-action@v2 with: arguments: build - - uses: actions/upload-artifact@v2 + - uses: actions/upload-artifact@v3 with: - name: Artifacts - path: dcm4che-typeddicom-lib/build/libs + name: Standard Library + path: dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/build/libs + retention-days: 7 + - uses: actions/upload-artifact@v3 + with: + name: Generator Gradle Plugin + path: dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/build/libs + retention-days: 7 + - uses: actions/upload-artifact@v3 + with: + name: Library Skeleton + path: dcm4che-typeddicom-skeleton/build/libs + retention-days: 7 + - uses: actions/upload-artifact@v3 + with: + name: Parser DTOs + path: dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/build/libs retention-days: 7 diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index f653181..f7dc194 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -12,55 +12,66 @@ jobs: environment: publishToDcm4cheMaven runs-on: ubuntu-latest steps: - - uses: actions/checkout@v2 + - uses: actions/checkout@v3 - name: Get release id: get_release - uses: bruceadams/get-release@v1.2.3 + uses: bruceadams/get-release@v1.3.2 env: GITHUB_TOKEN: ${{ github.token }} - name: Set up Java - uses: actions/setup-java@v2 + uses: actions/setup-java@v3 with: - java-version: '17' - distribution: 'adopt' + java-version: '11' + distribution: 'temurin' - name: Validate Gradle wrapper - uses: gradle/wrapper-validation-action@e6e38bacfdf1a337459f332974bb2327a31aaf4b + uses: gradle/wrapper-validation-action@v1 - name: Build package run: gradle build - - name: Publish bin jar to GitHub - uses: actions/upload-release-asset@v1 - env: - GITHUB_TOKEN: ${{ github.token }} - with: - upload_url: ${{ steps.get_release.outputs.upload_url }} - asset_path: ./dcm4che-typeddicom-lib/build/libs/dcm4che-typeddicom-lib.jar - asset_name: dcm4che-typeddicom-lib-${{ steps.get_release.outputs.tag_name }}.jar - asset_content_type: application/jar - - - name: Publish javadoc jar to GitHub - uses: actions/upload-release-asset@v1 - env: - GITHUB_TOKEN: ${{ github.token }} - with: - upload_url: ${{ steps.get_release.outputs.upload_url }} - asset_path: ./dcm4che-typeddicom-lib/build/libs/dcm4che-typeddicom-lib-javadoc.jar - asset_name: dcm4che-typeddicom-lib-javadoc-${{ steps.get_release.outputs.tag_name }}.jar - asset_content_type: application/jar - - - name: Publish sources jar to GitHub - uses: actions/upload-release-asset@v1 - env: - GITHUB_TOKEN: ${{ github.token }} + - name: Upload release assets + uses: actions/github-script@v6 with: - upload_url: ${{ steps.get_release.outputs.upload_url }} - asset_path: ./dcm4che-typeddicom-lib/build/libs/dcm4che-typeddicom-lib-sources.jar - asset_name: dcm4che-typeddicom-lib-sources-${{ steps.get_release.outputs.tag_name }}.jar - asset_content_type: application/jar + script: | + console.log('environment', process.versions); + + const fs = require('fs'); + + const { repo: { owner, repo }, sha } = context; + console.log({ owner, repo, sha }); + + const publishableSubProjects = [ + 'dcm4che-typeddicom-skeleton', + 'dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std', + 'dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos', + 'dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib', + 'dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin' + ]; + for (let project of publishableSubProjects) { + fs.readdir(`./${project}/build/libs`, (err, files) => { + if (err) { + console.log(err); + } else { + files.forEach(file => { + const releaseAssetName = file.replace(/(.*?)(-\d+\.\d+\.\d+(-SNAPSHOT)?)?(-(javadoc|sources))?.jar/, "$1-${{ steps.get_release.outputs.tag_name }}$4.jar"); + const filePath = `./${project}/build/libs/${file}` + + console.log('uploading ' + filePath + ' > ' + releaseAssetName); + + github.rest.repos.uploadReleaseAsset({ + owner, + repo, + release_id: "${{ steps.get_release.outputs.id }}", + name: releaseAssetName, + data: fs.readFileSync(filePath) + }); + }); + } + }); + } - name: Publish package to dcm4che Maven Repository run: gradle publishAllPublicationsToDcm4cheMavenRepository diff --git a/.gitignore b/.gitignore index 5df6bc8..115ed12 100644 --- a/.gitignore +++ b/.gitignore @@ -3,6 +3,7 @@ build # IntelliJ .idea/ +machinet.conf # Eclipse .classpath diff --git a/README.MD b/README.MD index ea607b3..bbaaeac 100644 --- a/README.MD +++ b/README.MD @@ -5,9 +5,15 @@ This library creates typed wrappers around dcm4che attributes to make DICOM obje We tried our best to mimic a lot of the DICOM standard in this library but due to the complexity and openness of the standard we cannot possibly cover everything. If you encounter unsupported fields you can always use the `getAttributes()` method and use dcm4che means to get whatever you want from the data. +## Dependencies +This library is based on the +* [DICOM Standard Version 2022d](https://dicom.nema.org/medical/dicom/2022d/output/chtml/part01/ps3.1.html). +* [dcm4che version 5.29.0](https://github.com/dcm4che/dcm4che/releases/tag/5.29.0) + ## How to add it to your project -### Gradle -#### Groovy +### Standard Library +#### Gradle +##### Groovy ```groovy repositories { // Add dicom4che repository @@ -19,11 +25,11 @@ repositories { ```groovy dependencies { - implementation 'org.dcm4che:dcm4che-typeddicom:0.4.3' + implementation 'org.dcm4che:dcm4che-typeddicom-lib-std:0.5.0' } ``` -#### Kotlin +##### Kotlin ```kotlin repositories { // Add dicom4che repository @@ -35,11 +41,11 @@ repositories { ```kotlin dependencies { - implementation("org.dcm4che:dcm4che-typeddicom:0.4.3") + implementation("org.dcm4che:dcm4che-typeddicom-lib-std:0.5.0") } ``` -### Maven +#### Maven ```xml @@ -54,18 +60,51 @@ dependencies { org.dcm4che dcm4che-typeddicom - 0.4.3 + 0.5.0 ``` +### Use private tags with the gradle plugin -## How to build it yourself -Run ```.\gradlew jar```. The JAR-file is then located under ```typeddicom-lib/build/libs/typeddicom-lib.jar```. +In the ```build.gradle``` put: +```groovy +plugins { + id 'java-library' + id 'org.dcm4che.typeddicom-java-generator' version '0.5.0' +} + +generateTypeddicomJavaSources { + privateDicomMetamodelYamlDirectory = layout.projectDirectory.dir("src/main/resources") // default - so this is optional when using this directory + generatedJavaOutputDirectory = layout.buildDirectory.dir("typeddicom") // default - so this is optional when using this directory +} +``` +or put this into ```build.gradle.kts```: +```kotlin +plugins { + id("java-library") + id("org.dcm4che.typeddicom-java-generator") version "0.5.0" +} +generateTypeddicomJavaSources { + privateDicomMetamodelYamlDirectory.set(layout.projectDirectory.dir("src/main/resources")) // default - so this is optional when using this directory + generatedJavaOutputDirectory.set(layout.buildDirectory.dir("typeddicom")) // default - so this is optional when using this directory +} +``` +Put your custom yaml file into the specified ```src/main/resources``` folder and populate it with your custom tags. Examples for this are plenty in ```dcm4che-typeddicom-java-generator-gradleplugin-.jar/std.dicom-meta-model.yaml```. + +* ```gradle generateJavaSourceFiles``` will generate the source files in the specified ```build/typeddicom``` folder. +* You can do anything as with the usual `java-library` projects (see https://docs.gradle.org/current/userguide/java_library_plugin.html). The ```generateJavaSourceFiles``` task is properly integrated with them and will run when needed. -You can also run ```.\gradlew publishToMavenLocal``` to install it to your local Maven repository. +## How to build it yourself +Run ```.\gradlew build```. The JAR-files are then located under: +* ```dcm4che-typeddicom-skeleton\build\libs``` for the skeleton java library containing interfaces and abstract classes which are implemented and extended by the generated classes. +* ```dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std\build\libs``` contains an easily usable library for all standard dicom IODs, Modules and Attributes. +* ```dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos\build\libs``` contains the DTOs which are needed to parse the metadata representation of the dicom standard. +* ```dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib\build\libs``` contains a library to generate a typeddicom implementation with custom adaptations using additional yaml files. +* ```dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin\build\libs``` contains the plugin which generates a typeddicom java implementation from a provided private tags file. +You can also run ```.\gradlew publishToMavenLocal``` to install all packages to your local Maven repository. ## How to use ### Reading fields Instead of -``` +```java Attributes attributes = readDicomFile("GSPS.dcm"); int[] untypedPixelAspectRatio = attributes.getSequence(Tag.DisplayedAreaSelectionSequence) @@ -74,7 +113,7 @@ int[] untypedPixelAspectRatio = attributes.getSequence(Tag.DisplayedAreaSelectio ``` you can now use -``` +```java Attributes attributes = readDicomFile("GSPS.dcm"); GrayscaleSoftcopyPresentationStateIOD gsps = new GrayscaleSoftcopyPresentationStateIOD(attributes); @@ -88,7 +127,7 @@ Where everything is checked for type-safety. ### Synthesizing Dicom Attributes A fluent API was implemented to make DICOM attributes synthesizing easily read and writable. Instead of -``` +```java Attributes gspsClassic = new Attributes(); gspsClassic.setString(Tag.PatientName, VR.PN, "Niklas"); Sequence referencedSeriesSequence = gspsClassic.newSequence(Tag.ReferencedSeriesSequence, 1); @@ -114,7 +153,7 @@ displayedAreaSelectionSequenceItem.setInt(Tag.PresentationPixelAspectRatio, VR.I displayedAreaSelectionSequence.add(displayedAreaSelectionSequenceItem); ``` you can now use -``` +```java GrayscaleSoftcopyPresentationStateIOD gsps = GrayscaleSoftcopyPresentationStateIOD.builder() .setPatientName().asString("Niklas") .setReferencedSeriesSequence( @@ -140,4 +179,3 @@ GrayscaleSoftcopyPresentationStateIOD gsps = GrayscaleSoftcopyPresentationStateI ``` ### JavaDocs Check out the javadocs. They should represent the stuff written in the DICOM Standard. - diff --git a/build.gradle b/build.gradle deleted file mode 100644 index 0ee1a88..0000000 --- a/build.gradle +++ /dev/null @@ -1 +0,0 @@ -group 'org.dcm4che' diff --git a/build.gradle.kts b/build.gradle.kts new file mode 100644 index 0000000..8a078e1 --- /dev/null +++ b/build.gradle.kts @@ -0,0 +1,32 @@ +val releasableProjects = arrayOf( + "dcm4che-typeddicom-parser", + "dcm4che-typeddicom-generator", + "dcm4che-typeddicom-lib", + "dcm4che-typeddicom-skeleton" +) + +tasks.register("publishAllPublicationsToDcm4cheMavenRepository") { + dependsOn(gradle.includedBuilds + .filter { it.name in releasableProjects } + .map { it.task(":publishAllPublicationsToDcm4cheMavenRepository") } + ) +} + +tasks.register("publishToMavenLocal") { + dependsOn(gradle.includedBuilds + .filter { it.name in releasableProjects } + .map { it.task(":publishToMavenLocal") } + ) +} + +tasks.register("clean") { + dependsOn(gradle.includedBuilds + .map { it.task(":clean") } + ) +} + +tasks.register("build") { + dependsOn(gradle.includedBuilds + .map { it.task(":build") } + ) +} diff --git a/buildSrc/build.gradle.kts b/buildSrc/build.gradle.kts deleted file mode 100644 index 9e7b22f..0000000 --- a/buildSrc/build.gradle.kts +++ /dev/null @@ -1,49 +0,0 @@ -plugins { - `java-gradle-plugin` -} - -gradlePlugin { - plugins { - create("processDicomXml") { - id = "org.dcm4che.typeddicom.gradleplugin.sourcegeneration" - implementationClass = "org.dcm4che.typeddicom.gradleplugin.ProcessDicomXmlPlugin" - } - } -} - -repositories { - mavenLocal() - mavenCentral() - maven { - url = uri("http://maven.scijava.org/content/repositories/public/") - isAllowInsecureProtocol = true - } -} - -dependencies { - implementation("com.github.spullara.mustache.java:compiler:0.9.10") - - implementation("org.apache.commons:commons-text:1.9") - implementation("com.github.davidmoten:word-wrap:0.1.9") - - implementation("org.apache.commons:commons-lang3:3.12.0") - - implementation("org.dcm4che:dcm4che-core:5.23.3") - - implementation("org.jsoup:jsoup:1.14.3") - - testImplementation("org.junit.jupiter:junit-jupiter-api:5.7.0") - testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.7.0") -} - -java { - sourceCompatibility = JavaVersion.VERSION_16 - targetCompatibility = JavaVersion.VERSION_16 -} - - -tasks.test { - useJUnitPlatform() -} - - diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomXmlParser.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomXmlParser.java deleted file mode 100644 index e9e2ce1..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomXmlParser.java +++ /dev/null @@ -1,178 +0,0 @@ -package org.dcm4che.typeddicom; - -import com.github.mustachejava.DefaultMustacheFactory; -import com.github.mustachejava.Mustache; -import com.github.mustachejava.MustacheNotFoundException; -import com.github.mustachejava.MustacheResolver; -import com.github.mustachejava.reflect.ReflectionObjectHandler; -import org.dcm4che.typeddicom.metamodel.DataElementMetaInfo; -import org.dcm4che.typeddicom.metamodel.InformationObjectDefinitionMetaInfo; -import org.dcm4che.typeddicom.metamodel.ModuleMetaInfo; -import org.dcm4che.typeddicom.metamodel.ValueRepresentationMetaInfo; -import org.xml.sax.SAXException; - -import javax.xml.parsers.ParserConfigurationException; -import javax.xml.parsers.SAXParser; -import javax.xml.parsers.SAXParserFactory; -import java.io.*; -import java.nio.charset.StandardCharsets; -import java.util.HashMap; -import java.util.HashSet; -import java.util.Map; -import java.util.Set; -import java.util.function.Function; -import java.util.stream.Collectors; - -public class DicomXmlParser { - public static final String JAVA_FILE_EXTENSION = ".java"; - private final SAXParser saxParser; - private final DefaultMustacheFactory mustacheFactory; - private final File dicomXmlDirectory; - private final File javaOutputDirectory; - - public DicomXmlParser(File dicomXmlDirectory, File mustacheTemplateDirectory, File javaOutputDirectory) { - try { - this.dicomXmlDirectory = dicomXmlDirectory; - this.javaOutputDirectory = javaOutputDirectory; - SAXParserFactory saxParserFactory = SAXParserFactory.newInstance(); - saxParser = saxParserFactory.newSAXParser(); - MustacheResolver mustacheResolver = resourceName -> { - File mustacheFile = new File(mustacheTemplateDirectory, resourceName + ".java.mustache"); - try { - return new FileReader(mustacheFile); - } catch (FileNotFoundException e) { - throw new MustacheNotFoundException(resourceName, e); - } - }; - mustacheFactory = new DefaultMustacheFactory(mustacheResolver); - mustacheFactory.setObjectHandler(new MapMethodReflectionHandler()); - } catch (ParserConfigurationException | SAXException e) { - throw new RuntimeException("Wasn't able to create the DICOM XML Parser", e); - } - } - - public void generateSources() { - try { - DicomPart05Handler handlerPart5 = new DicomPart05Handler(); - saxParser.parse(new File(dicomXmlDirectory, "part05.xml"), handlerPart5); - Set valueRepresentations = handlerPart5.getValueRepresentations(); - Set multiValueRepresentations = handlerPart5.getMultiValueRepresentations(); - - Map valueRepresentationsMap = - valueRepresentations.stream().collect(Collectors.toMap( - ValueRepresentationMetaInfo::tag, - Function.identity()) - ); - - Map multiValueRepresentationsMap = - multiValueRepresentations.stream().collect(Collectors.toMap( - ValueRepresentationMetaInfo::tag, - Function.identity()) - ); - - DicomPart06Handler handlerPart6 = new DicomPart06Handler(valueRepresentationsMap, multiValueRepresentationsMap); - saxParser.parse(new File(dicomXmlDirectory, "part06.xml"), handlerPart6); - Set dataElements = handlerPart6.getDataElements(); - - Map> dataElementMetaInfoMap = new HashMap<>(); - for (DataElementMetaInfo dataElement : dataElements) { - dataElementMetaInfoMap.computeIfAbsent(dataElement.getTag(), (key) -> new HashSet<>()); - dataElementMetaInfoMap.get(dataElement.getTag()).add(dataElement); - } - - DicomPart03Handler handlerPart3 = new DicomPart03Handler(dataElementMetaInfoMap); - saxParser.parse(new File(dicomXmlDirectory, "part03.xml"), handlerPart3); - Set modules = handlerPart3.getModules(); - Set iods = handlerPart3.getIODs(); - - DicomPart04Handler handlerPart4 = new DicomPart04Handler(iods); - saxParser.parse(new File(dicomXmlDirectory, "part04.xml"), handlerPart4); - - generateValueRepresentationInterfaces(valueRepresentations); - System.out.println("Generated " + valueRepresentations.size() + " Value Representation classes"); - - generateValueRepresentationInterfaces(multiValueRepresentations); - System.out.println("Generated " + multiValueRepresentations.size() + " Multi Value Representation classes"); - - generateDataElementWrapperClasses(dataElements); - System.out.println("Generated " + dataElements.size() + " Data Element classes"); - - generateModuleInterfaces(modules); - System.out.println("Generated " + modules.size() + " Module classes"); - - generateIODClasses(iods); - System.out.println("Generated " + iods.size() + " IOD classes"); - } catch (SAXException | IOException e) { - throw new RuntimeException("Wasn't able to generate the Sources", e); - } - } - - private void generateValueRepresentationInterfaces(Set valueRepresentations) throws IOException { - Mustache mustache = mustacheFactory.compile("ValueRepresentation"); - File valueRepresentationDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/valuerepresentations"); - //noinspection ResultOfMethodCallIgnored - valueRepresentationDir.mkdirs(); - for (ValueRepresentationMetaInfo valueRepresentation : valueRepresentations) { - String filename = valueRepresentation.keyword() + JAVA_FILE_EXTENSION; - File javaFile = new File(valueRepresentationDir, filename); - try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { - mustache.execute(javaFileWriter, valueRepresentation); - } - } - } - - private void generateDataElementWrapperClasses(Set dataElements) throws IOException { - Mustache mustache = mustacheFactory.compile("DataElement"); - File dataElementDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/dataelements"); - //noinspection ResultOfMethodCallIgnored - dataElementDir.mkdirs(); - for (DataElementMetaInfo dataElementMetaInfo : dataElements) { - String filename = dataElementMetaInfo.getKeyword() + JAVA_FILE_EXTENSION; - File javaFile = new File(dataElementDir, filename); - try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { - mustache.execute(javaFileWriter, dataElementMetaInfo); - } - } - } - - private void generateIODClasses(Set iods) throws IOException { - Mustache mustache = mustacheFactory.compile("InformationObjectDefinition"); - File dataElementDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/iods"); - //noinspection ResultOfMethodCallIgnored - dataElementDir.mkdirs(); - for (InformationObjectDefinitionMetaInfo iod : iods) { - String filename = iod.getKeyword() + JAVA_FILE_EXTENSION; - File javaFile = new File(dataElementDir, filename); - try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { - mustache.execute(javaFileWriter, iod); - } - } - } - - private void generateModuleInterfaces(Set moduleMetaInfoSet) throws IOException { - Mustache mustache = mustacheFactory.compile("Module"); - File dataElementDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/modules"); - //noinspection ResultOfMethodCallIgnored - dataElementDir.mkdirs(); - for (ModuleMetaInfo moduleMetaInfo : moduleMetaInfoSet) { - String filename = moduleMetaInfo.getKeyword() + JAVA_FILE_EXTENSION; - File javaFile = new File(dataElementDir, filename); - try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { - mustache.execute(javaFileWriter, moduleMetaInfo); - } - } - } - - /** - * Extended reflection handler that can access map methods. - */ - private static class MapMethodReflectionHandler extends ReflectionObjectHandler { - - @Override - protected boolean areMethodsAccessible(Map map) { - return true; - } - } - - -} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/ProcessDicomXmlPlugin.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/ProcessDicomXmlPlugin.java deleted file mode 100644 index 6ac6eb9..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/ProcessDicomXmlPlugin.java +++ /dev/null @@ -1,15 +0,0 @@ -package org.dcm4che.typeddicom.gradleplugin; - -import org.gradle.api.Plugin; -import org.gradle.api.Project; - -public class ProcessDicomXmlPlugin implements Plugin { - public void apply(final Project target) { - final ProcessDicomXmlPluginExtension extension = target.getExtensions().create("processDicomXml", ProcessDicomXmlPluginExtension.class); - target.getTasks().register("generateJavaSourceFiles", GenerateJavaSourcesTask.class, task -> { - task.getMustacheTemplateDirectory().set(extension.getMustacheTemplateDirectory()); - task.getDicomStandardXmlDirectory().set(extension.getDicomStandardXmlDirectory()); - task.getGeneratedJavaOutputDirectory().set(extension.getGeneratedJavaOutputDirectory()); - }); - } -} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/ProcessDicomXmlPluginExtension.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/ProcessDicomXmlPluginExtension.java deleted file mode 100644 index d8463d4..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/ProcessDicomXmlPluginExtension.java +++ /dev/null @@ -1,16 +0,0 @@ -package org.dcm4che.typeddicom.gradleplugin; - -import org.gradle.api.file.DirectoryProperty; -import org.gradle.api.tasks.InputDirectory; -import org.gradle.api.tasks.OutputDirectory; - -public interface ProcessDicomXmlPluginExtension { - @InputDirectory - DirectoryProperty getDicomStandardXmlDirectory(); - - @InputDirectory - DirectoryProperty getMustacheTemplateDirectory(); - - @OutputDirectory - DirectoryProperty getGeneratedJavaOutputDirectory(); -} \ No newline at end of file diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/AdditionalAttributeInfo.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/AdditionalAttributeInfo.java deleted file mode 100644 index 81a76fe..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/AdditionalAttributeInfo.java +++ /dev/null @@ -1,4 +0,0 @@ -package org.dcm4che.typeddicom.metamodel; - -public record AdditionalAttributeInfo(String name, String type, String attributeDescription) { -} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ContextEntry.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ContextEntry.java deleted file mode 100644 index df46ea4..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ContextEntry.java +++ /dev/null @@ -1,4 +0,0 @@ -package org.dcm4che.typeddicom.metamodel; - -public record ContextEntry(String contextName, String href) { -} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/IODModuleReference.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/IODModuleReference.java deleted file mode 100644 index d7a4043..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/IODModuleReference.java +++ /dev/null @@ -1,4 +0,0 @@ -package org.dcm4che.typeddicom.metamodel; - -public record IODModuleReference(ModuleMetaInfo moduleMetaInfo) { -} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/SOPClass.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/SOPClass.java deleted file mode 100644 index a5cf2ef..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/SOPClass.java +++ /dev/null @@ -1,4 +0,0 @@ -package org.dcm4che.typeddicom.metamodel; - -public record SOPClass(String name, String uid) { -} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ValueRepresentationMetaInfo.java b/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ValueRepresentationMetaInfo.java deleted file mode 100644 index e6a1ea3..0000000 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ValueRepresentationMetaInfo.java +++ /dev/null @@ -1,6 +0,0 @@ -package org.dcm4che.typeddicom.metamodel; - -public record ValueRepresentationMetaInfo(String tag, String name, String keyword, String definition, - String characterRepertoire, String lengthOfValue, - String href, String implementsInterfaces, String setterImplementsInterfaces) { -} diff --git a/dcm4che-typeddicom-generator/build.gradle.kts b/dcm4che-typeddicom-generator/build.gradle.kts new file mode 100644 index 0000000..8ac21e1 --- /dev/null +++ b/dcm4che-typeddicom-generator/build.gradle.kts @@ -0,0 +1,15 @@ +tasks.register("publishAllPublicationsToDcm4cheMavenRepository") { + dependsOn(project.getTasksByName("publishAllPublicationsToDcm4cheMavenRepository", true).filter { it != this }) +} + +tasks.register("publishToMavenLocal") { + dependsOn(project.getTasksByName("publishToMavenLocal", true).filter { it != this }) +} + +tasks.register("clean") { + dependsOn(project.getTasksByName("clean", true).filter { it != this }) +} + +tasks.register("build") { + dependsOn(project.getTasksByName("build", true).filter { it != this }) +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/build.gradle.kts b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/build.gradle.kts new file mode 100644 index 0000000..9ea48e2 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/build.gradle.kts @@ -0,0 +1,54 @@ +plugins { + id("com.gradle.plugin-publish") version "1.1.0" + id("org.dcm4che.typeddicom-xml-parser") + id("org.dcm4che.typeddicom-publisher") +} + +processDicomXml { + dicomStandardXmlDirectory.set(layout.projectDirectory.dir("src/main/resources/dicom-standard-xml")) + generatedYamlMetamodelOutputDirectory.set(layout.buildDirectory.dir("typeddicom-generated/resources")) +} + +gradlePlugin { + plugins { + create("typeddicomJavaGenerator") { + id = "org.dcm4che.typeddicom-java-generator" + displayName = "Typeddicom Java Generator" + description = "This gradle plugin provides a Task to generate Java code which provides the classes which " + + "are specified in the DICOM standard. The classes can be extended with custom tags by providing a yaml " + + "file containing the changes." + implementationClass = "org.dcm4che.typeddicom.generator.gradleplugin.TypeddicomJavaGeneratorPlugin" + } + } +} + +typeddicomPublisher { + pomName.set("dcm4che-typeddicom-java-generator-gradleplugin") + pomDescription.set("This gradle plugin provides a Task to generate Java code which provides the classes which " + + "are specified in the DICOM standard. The classes can be extended with custom tags by providing a yaml " + + "file containing the changes."); +} + +repositories { + mavenCentral() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } +} + +dependencies { + implementation(project(":dcm4che-typeddicom-java-generator-lib")) +} + +java { + sourceCompatibility = JavaVersion.VERSION_11 + targetCompatibility = JavaVersion.VERSION_11 +} + +tasks.withType { + exclude("dicom-standard-xml/") +} + +tasks.test { + useJUnitPlatform() +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/GenerateJavaSourcesTask.java b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/GenerateJavaSourcesTask.java new file mode 100644 index 0000000..2dbc05a --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/GenerateJavaSourcesTask.java @@ -0,0 +1,65 @@ +package org.dcm4che.typeddicom.generator.gradleplugin; + +import org.dcm4che.typeddicom.generator.JavaGenerator; +import org.gradle.api.DefaultTask; +import org.gradle.api.file.Directory; +import org.gradle.api.file.DirectoryProperty; +import org.gradle.api.tasks.*; + +import java.io.File; +import java.io.IOException; +import java.nio.file.FileVisitResult; +import java.nio.file.Files; +import java.nio.file.Path; +import java.nio.file.SimpleFileVisitor; +import java.nio.file.attribute.BasicFileAttributes; +import java.util.LinkedList; +import java.util.List; + +public abstract class GenerateJavaSourcesTask extends DefaultTask { + @InputDirectory + public abstract DirectoryProperty getPrivateDicomMetamodelYamlDirectory(); + + @OutputDirectory + public abstract DirectoryProperty getGeneratedJavaOutputDirectory(); + + @TaskAction + public void generateJavaSources() { + List privateMetamodelYamlFiles = new LinkedList<>(); + Directory privateDicomMetamodelYamlDirectory = this.getPrivateDicomMetamodelYamlDirectory().getOrNull(); + if (privateDicomMetamodelYamlDirectory != null) { + privateMetamodelYamlFiles.addAll(privateDicomMetamodelYamlDirectory.getAsFileTree().getFiles()); + } + File javaDirectory = this.getGeneratedJavaOutputDirectory().get().getAsFile(); + + + if (javaDirectory.exists()) { + try { + Files.walkFileTree(javaDirectory.toPath(), + new SimpleFileVisitor<>() { + @Override + public FileVisitResult postVisitDirectory( + Path dir, IOException exc) throws IOException { + Files.delete(dir); + return FileVisitResult.CONTINUE; + } + + @Override + public FileVisitResult visitFile( + Path file, BasicFileAttributes attrs) + throws IOException { + Files.delete(file); + return FileVisitResult.CONTINUE; + } + }); + } catch (IOException e) { + throw new RuntimeException("Couldn't delete java directory", e); + } + } + + //noinspection ResultOfMethodCallIgnored + javaDirectory.mkdirs(); + JavaGenerator javaGenerator = new JavaGenerator("std.dicom-meta-model.yaml", privateMetamodelYamlFiles, javaDirectory); + javaGenerator.generateSources(); + } +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/TypeddicomJavaGeneratorPlugin.java b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/TypeddicomJavaGeneratorPlugin.java new file mode 100644 index 0000000..80b7c18 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/TypeddicomJavaGeneratorPlugin.java @@ -0,0 +1,27 @@ +package org.dcm4che.typeddicom.generator.gradleplugin; + +import org.gradle.api.Plugin; +import org.gradle.api.Project; +import org.gradle.api.tasks.SourceSetContainer; +import org.gradle.api.tasks.TaskProvider; + +public class TypeddicomJavaGeneratorPlugin implements Plugin { + public void apply(final Project target) { + final TypeddicomJavaGeneratorPluginExtension extension = + target.getExtensions().create("generateTypeddicomJavaSources", TypeddicomJavaGeneratorPluginExtension.class); + extension.getGeneratedJavaOutputDirectory().convention(target.getLayout().getBuildDirectory().dir("typeddicom")); + extension.getPrivateDicomMetamodelYamlDirectory().convention(target.getLayout().getProjectDirectory().dir("src/main/resources")); + TaskProvider generateJavaSourcesFileTaskProvider = + target.getTasks().register("generateJavaSourceFiles", GenerateJavaSourcesTask.class, task -> { + task.getPrivateDicomMetamodelYamlDirectory().set(extension.getPrivateDicomMetamodelYamlDirectory()); + task.getGeneratedJavaOutputDirectory().set(extension.getGeneratedJavaOutputDirectory()); + }); + target.getPluginManager().withPlugin("java-library", javaPlugin -> { + SourceSetContainer sourceSets = target.getExtensions().getByType(SourceSetContainer.class); + sourceSets.named("main", sourceSet -> sourceSet.getJava().srcDir(generateJavaSourcesFileTaskProvider)); + String version = TypeddicomJavaGeneratorPlugin.class.getPackage().getImplementationVersion(); + target.getDependencies().add("api", "org.dcm4che:dcm4che-typeddicom-skeleton:" + version); + target.getDependencies().add("implementation", "org.dcm4che:dcm4che-core"); + }); + } +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/TypeddicomJavaGeneratorPluginExtension.java b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/TypeddicomJavaGeneratorPluginExtension.java new file mode 100644 index 0000000..1341d31 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/java/org/dcm4che/typeddicom/generator/gradleplugin/TypeddicomJavaGeneratorPluginExtension.java @@ -0,0 +1,11 @@ +package org.dcm4che.typeddicom.generator.gradleplugin; + +import org.gradle.api.file.DirectoryProperty; +import org.gradle.api.tasks.Optional; + +public interface TypeddicomJavaGeneratorPluginExtension { + @Optional + DirectoryProperty getPrivateDicomMetamodelYamlDirectory(); + + DirectoryProperty getGeneratedJavaOutputDirectory(); +} diff --git a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part03.xml b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part03.xml similarity index 95% rename from dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part03.xml rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part03.xml index 9b73747..51d338c 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part03.xml +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part03.xml @@ -1,13 +1,13 @@ PS3.3 - DICOM PS3.3 2021d - Information Object Definitions + DICOM PS3.3 2022d - Information Object Definitions DICOM Standards Committee - 2021 + 2022 NEMA @@ -323,7 +323,7 @@ 2001 Electronic still-picture imaging - Removable memory - Part 2: TIFF/EP image data formats - + @@ -419,16 +419,18 @@ - - ISO 19980 - - ISO - - 2012 - second edition - Ophthalmic instruments - Corneal topographers - - + + ISO 21320-1 + + ISO/IEC + + 2015 + Information technology – Document Container File – Part 1: Core + + + + + ISO 22028-2 ISO @@ -459,7 +461,16 @@ - + + IEC 60601-2-1 + + IEC + + 2020 + Ed.4 + Medical Electrical Equipment - Part 2-1: Particular requirements for the basic safety and essential performance of electron accelerators in the range 1 MeV to 50 MeV + + IEC 60601-2-33 IEC @@ -547,7 +558,7 @@ 1975 Registration - The Japanese Roman graphic set of characters - + @@ -717,6 +728,26 @@ + + RFC1951 + + IETF + + DEFLATE Compressed Data Format Specification Version 1.3 + + + + + + RFC1952 + + IETF + + GZIP file format specification version 4.3 + + + + RFC2046 @@ -784,6 +815,36 @@ + + RFC7230 + + IETF + + Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing + + + + + + RFC7231 + + IETF + + Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content + + + + + + RFC7530 + + IETF + + Network File System (NFS) Version 4 Protocol + + + + Health Level Seven (HL7) @@ -1401,6 +1462,28 @@ 1989 StereoLithography Interface Specification + + POSIX + + IEEE and The Open Group + + 2017 + POSIX.1-2017 (IEEE Std 1003.1™-2017) + + + + + + ZIP + + PKWARE, Inc. + + 1989 + ZIP File Format Specification + + + + @@ -1682,7 +1765,7 @@ An affirmative statement or declaration by a specified entity about a specified or implied subject for a specified or implied purpose. - + Attribute Tag A unique identifier for an Attribute of an Information Object composed of an ordered pair of numbers (a Group Number followed by an Element number). @@ -1760,6 +1843,12 @@ A data abstraction of a class of similar Real-World Objects that defines the nature and Attributes relevant to the class of Real-World Objects represented. + + Inventory + + A listing of DICOM Studies, Series, and SOP Instances, and associated metadata, managed by a repository system. + + Module @@ -1790,6 +1879,12 @@ A sequential component of the reconstruction portion of a protocol, such as generating CT thin images or multiplanar reformats, or generating XA 2D processed images and/or 3D X-Ray images. + + Scope of Inventory + + The parameters that select the DICOM Studies that are included in an Inventory. Parameters are specified as matching rules for Attribute values. + + Specialization @@ -2219,6 +2314,17 @@ + + DICOM Media Storage and File Format + This Part of the Standard makes use of the following terms defined in : + + DICOM File Format + + +. + + + @@ -2298,7 +2404,13 @@ Computer-Aided Detection and/or Computer-Aided Diagnosis for chest radiography - + + CSV + + Comma-separated Values + + + CTV Clinical target volume @@ -2364,7 +2476,13 @@ (United States) Food and Drug Administration - + + FHIR + + Fast Healthcare Interoperability Resources + + + GTV Gross tumor volume @@ -2544,7 +2662,13 @@ Open Systems Interconnection - + + OWL + + Web Ontology Language + + + PDF Portable Document Format @@ -2958,9 +3082,9 @@ 1 - This is an example of a Sequence Attribute - - + This is an example of a Sequence Attribute. + + @@ -2969,9 +3093,9 @@ - In this Module, Attribute D (dddd,dddd) is Type 1 - - + In this Module, Attribute D (dddd,dddd) is Type 1. + + @@ -3244,7 +3368,7 @@
Service-Object Pair Class (SOP Class) The SOP Class definitions in contain the rules and semantics that may restrict the use of the services in the DIMSE Service Group and/or the Attributes of the IOD. - and contain the rules and semantics that may restrict the attributes of the IOD or the use of the services in the Media Storage Services and the Web Services respectively. + and contain the rules and semantics that may restrict the Attributes of the IOD or the use of the services in the Media Storage Services and the Web Services respectively. The selection of SOP Classes is used by Application Entities to establish an agreed set of capabilities to support their interaction for SOP Classes based on DIMSE Services. This negotiation is performed at association establishment time as described in . An extended negotiation allows Application Entities to further agree on specific options within a SOP Class. @@ -3486,15 +3610,15 @@
General Purpose Scheduled Procedure Step (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
General Purpose Performed Procedure Step (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
Workitem (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
Clinical Document @@ -3540,7 +3664,7 @@
Extension of the DICOM Model of the Real World for the General Purpose Worklist (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
Organizing Large Sets of Information @@ -3815,6 +3939,37 @@
+
+ Inventory + + shows the E-R diagram for the Inventory Information Model. + The Inventory Information Entity provides an Inventory of Studies, and their component Series and SOP Instances, managed by a repository (such as a Picture Archiving and Communication System - PACS). + The Inventory Information Model includes contextual information about each Study through the Patient and Imaging Service Request IEs. + It includes information on the stored SOP Instances, including access mechanisms supported by the repository. + + + + This information model is similar to the Study Root Query/Retrieve Information Model (see ). + + + There is a potentially complex relationship between the Study and Imaging Service Requests in the real world (e.g., see Section 4.6.4.1.2.3 Relationship between Scheduled and Performed Procedure Steps). + However, the Inventory Information Model follows the basic Study Information Model and supports only a single Accession Number representing an Imaging Service Request (see ). + Note that if a Study has multiple associated Imaging Service Requests, the request Attributes may be encoded at the Series level. + + + +
+ Inventory Information Model E-R Diagram + + + + + + +
+ + +
Extension of The DICOM Model of The Real-world for Radiotherapy Second Generation Information Objects @@ -3944,11 +4099,11 @@ Each Item of a Code Sequence Attribute contains the triplet of Coding Scheme Designator (0008,0102), the Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)), and Code Meaning (0008,0104). Other optional and conditional Attributes may also be present. For any particular Code Sequence Attributes, the range of codes that may be used for that Attribute (the Value Set) may be suggested or constrained by specification of a Context Group. The Module or Template in which the Attribute is used will specify whether or not the context group is baseline or defined. A Baseline Context Group lists codes for terms that are suggested and may be used, but are not required to be used. A Defined Context Group lists codes for terms that shall be used if the term is used. Context Groups are defined in a Mapping Resource, such as the DICOM Content Mapping Resource (DCMR) specified in . Context Groups consist of lists of contextually related coded concepts, including Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Coding Scheme Designator (0008,0102). Each concept is unique within the Context Group and identified by its Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Coding Scheme Designator (0008,0102). The Context Group specification identifies whether it is extensible, i.e., whether it may be modified in an Application to use additional terms (see ). Whether a Context Group is used as a Baseline or Defined Context Group is defined not in the mapping resource, but rather in the Template or Module in which the Code Sequence Attribute is used. - Context Groups are identified by labels referred to as Context Identifiers (CID). Formally, the Context Identifier specifies the context of use, not the specific list of coded values selected for that context of use in the Context Group. The set of values specified in the Standard for a particular context may change over time, and set of values used by an Application Entity for a particular context may include a local or private extension beyond the Standard value set. + Context Groups are identified by labels referred to as Context Identifiers (CID). Formally, the Context Identifier (0008,010F) specifies the context of use, not the specific list of coded values selected for that context of use in the Context Group. The set of values specified in the Standard for a particular context may change over time, and set of values used by an Application Entity for a particular context may include a local or private extension beyond the Standard value set. - A specific set of coded values used by an Application Entity is therefore identified by the Mapping Resource Identifier, plus the Context Identifier, plus the Context Group Version, plus the identifiers for any private extension. + A specific set of coded values used by an Application Entity is therefore identified by the Mapping Resource (0008,0105), plus the Context Identifier (0008,010F), plus the Context Group Version (0008,0106), plus the identifiers for any private extension. The use by an Application Entity of coded terms not in the Standard specified Context Group does not require the explicit identification of a private extension. The Application Entity is then the implicit source of the extension. @@ -4037,11 +4192,11 @@
Context Group Version - Context Group Version (0008,0106) conveys the version of the Context Group identified by Context Identifier (0008,010F). This Attribute uses VR DT, but for Context Groups defined in the precision of Context Group Version is limited to the day, and the time zone offset is not used. + Context Group Version (0008,0106) conveys the version of the Context Group identified by Context Identifier (0008,010F). This Attribute uses VR DT, but for Context Groups defined in the precision of Context Group Version (0008,0106) is limited to the day, and the time zone offset is not used.
Context Identifier and Context UID - The value of Context Identifier (0008,010F) identifies the Context Group defined by Mapping Resource (0008,0105) from which the values of Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Code Meaning (0008,0104) were selected, or to which Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Code Meaning (0008,0104) have been added as a private Context Group extension (see ). The Context Identifier Attribute uses VR CS, and for Context Groups defined in the value shall be the Context Group Identifier as a string of digits without leading zeros, and does not include the string "CID". + The value of Context Identifier (0008,010F) identifies the Context Group defined by Mapping Resource (0008,0105) from which the values of Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Code Meaning (0008,0104) were selected, or to which Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Code Meaning (0008,0104) have been added as a private Context Group extension (see ). The Context Identifier (0008,010F) Attribute uses VR CS, and for Context Groups defined in the value shall be the Context Group Identifier as a string of digits without leading zeros, and does not include the string "CID". The value of Context UID (0008,0117) uniquely identifies the Context Group. See . Privately defined Context Groups may be identified by Context Identifier and Mapping Resource. @@ -4049,11 +4204,11 @@
Context Group Extensions - Context Group Extension Flag (0008,010B) may be used to designate a pair of Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Code Meaning (0008,0104) as a selection from a private extension of a Context Group. If the Context Group Extension Flag is present, and has a value of "Y", Context Group Extension Creator UID (0008,010D) shall be used to identify the person or organization who created the extension to the Context Group. Context Group Local Version (0008,0107) conveys an implementation-specific private version DateTime of a Context Group that contains private extensions + Context Group Extension Flag (0008,010B) may be used to designate a pair of Code Value (0008,0100) (or Long Code Value (0008,0119) or URN Code Value (0008,0120)) and Code Meaning (0008,0104) as a selection from a private extension of a Context Group. If the Context Group Extension Flag (0008,010B) is present, and has a value of "Y", Context Group Extension Creator UID (0008,010D) shall be used to identify the person or organization who created the extension to the Context Group. Context Group Local Version (0008,0107) conveys an implementation-specific private version DateTime of a Context Group that contains private extensions. - These Attributes provide the means for implementations to extend code sets conveniently, while preserving referential integrity with respect to the original Context Group Version. + These Attributes provide the means for implementations to extend code sets conveniently, while preserving referential integrity with respect to the original Context Group Version (0008,0106). The locally-defined (private) value of Context Group Local Version (0008,0107) typically would be a more recent date than the standard value of Context Group Version (0008,0106) specified in the standard message/terminology Mapping Resource that defines the Context Group. @@ -5023,13 +5178,13 @@
Retired Codes and Expected Behavior As this Standard and external coding schemes are maintained, the codes specified as Values for Attributes and in Conditions may change. The previous codes are considered Retired but implementations may continue to send them and receivers will be expected to be able to continue to recognize the Retired codes, including the Code Value and Coding Scheme Designator, even if the current Standard does not publish them. - A notable example is the change throughout the Standard from using "SNOMED-RT style" code values with a Coding Scheme Designator of "SRT", "SNM3" or "99SDM", to the use of SNOMED CT numeric code values with a Coding Scheme Designator of "SCT". Those retired codes may be found in PS3.3 2019a. A mapping of retired to new SNOMED codes is found in . + A notable example is the change throughout the Standard from using "SNOMED-RT style" code values with a Coding Scheme Designator of "SRT", "SNM3" or "99SDM", to the use of SNOMED CT numeric code values with a Coding Scheme Designator of "SCT". Those retired codes may be found in PS3.3-2019a. A mapping of retired to new SNOMED codes is found in .
Template Identification Macro (Retired) - was defined in a previous version of the DICOM Standard (see PS3.3-2004). The Section is now retired, and its contents have been consolidated into . + was defined in a previous version of the DICOM Standard (see PS3.3-2004). The Section is now retired, and its contents have been consolidated into . Miscellaneous Macros @@ -5053,7 +5208,7 @@ - + - + Person's mailing address. + + - + Person's telephone number(s). + +
Person Identification Macro Attributes DescriptionPerson Identification Macro Attributes
@@ -5111,9 +5266,9 @@ 3 - Person's mailing address -
Person's Telephone Numbers @@ -5125,9 +5280,9 @@ 3 - Person's telephone number(s) -
Person's Telecom Information @@ -5271,7 +5426,7 @@ - Specific uses of the Content Item may invoke the Content Item Macro defined in this Section, the Document Content Macro of , or another similar construct. An invocation of the Content Item Macro may constrain the allowed values of Value Type (0040,A040). + Specific uses of the Content Item may invoke the Content Item Macro defined in this Section, the of , or another similar construct. An invocation of the Content Item Macro may constrain the allowed values of Value Type (0040,A040). @@ -5287,7 +5442,7 @@ See for the meaning of the Type column in this Macro when applied to Normalized IODs. - + - + Required if Type of Instances (0040,E020) is DICOM and the Information Model of the referenced Instance contains the Study IE. + + - + Required if Type of Instances (0040,E020) is DICOM and the Information Model of the referenced Instance contains the Series IE. + + - + One or more Items shall be included in this Sequence. + +
Content Item Macro Attributes DescriptionContent Item Macro Attributes
@@ -5929,9 +6084,9 @@ Unique identifier for the Study. - Required if Type of Instances (0040,E020) is DICOM and the Information Model of the referenced Instance contains the Study IE -
Series Instance UID @@ -5944,9 +6099,9 @@ Unique identifier for the Series that is part of the Study identified in Study Instance UID (0020,000D), if present, and contains the referenced object Instance(s). - Required if Type of Instances (0040,E020) is DICOM and the Information Model of the referenced Instance contains the Series IE -
Referenced SOP Sequence @@ -5959,9 +6114,9 @@ References to object Instances. - One or more Items shall be included in this Sequence -
>Referenced SOP Class UID @@ -6378,9 +6533,9 @@
- Series and Instance Reference Macro - - defines the Attributes that list Series and SOP Instances within those Series. + Series and Instance Reference Macro + + specifies the Attributes of the , which lists Series, and SOP Instances within those Series. @@ -6461,7 +6616,7 @@
General Anatomy Macros - , , and describe the Attributes for identifying the general region of the Patient anatomy examined using coded terminology, as well as the principal structure(s) within that region that is the target of the current SOP Instance. + , , and specify the Attributes for identifying the general region of the Patient anatomy examined using coded terminology, as well as the principal structure(s) within that region that is the target of the current SOP Instance. The only differences between the Macros are the Type and Number of Items of the Anatomic Region Sequence (0008,2218) Attribute. describe the Attributes for the coding of the principal structure only. The invocation of these Macros may specify Baseline or Defined CIDs for the Anatomic Region Sequence (0008,2218), the Anatomic Region Modifier Sequence (0008,2220), and/or the Primary Anatomic Structure Sequence (0008,2228). The general region of the body (e.g., the anatomic region, organ, or body cavity being examined) is identified by the Anatomic Region Sequence (0008,2218). Characteristics of the anatomic region being examined, such as sub-region (e.g., medial, lateral, superior, inferior, lobe, quadrant) and laterality (e.g., right, left, both), may be refined by the Anatomic Region Modifier Sequence (0008,2220). @@ -7300,9 +7455,9 @@
- Basic Pixel Spacing Calibration Macro - - defines the Attributes for the Basic Pixel Spacing Calibration Macro. + Basic Pixel Spacing Calibration Macro + + specifies the Attributes of the .
Series and Instance Reference Macro Attributes
@@ -7474,9 +7629,9 @@
- SOP Instance Reference Macro - - specifies the Attributes that reference an SOP Instance. + SOP Instance Reference Macro + + specifies the Attributes of the , which references a SOP Instance.
Basic Pixel Spacing Calibration Macro Attributes
@@ -7528,9 +7683,9 @@
SOP Instance Reference Macro Attributes
- Content Identification Macro - - describe the Attributes for identifying a SOP Instance potentially created by a human user interacting with an application. + Content Identification Macro + + specifies the Attributes of the , which identify and describe a SOP Instance potentially created by a human user interacting with an application. @@ -7706,267 +7861,238 @@ - - - - - - - - - - - -
Content Identification Macro Attributes
- Content Creator's Name - - (0070,0084) - - 2 - - Name of operator (such as a technologist or physician) creating the content of the SOP Instance. -
- Content Creator's Identification Code Sequence - - (0070,0086) - - 3 - - Identification of the person who created the content. Only a single Item is permitted in this Sequence. -
- - >Include + + Include - +
-
- Enhanced Content Identification Macro - The Enhanced Content Identification Macro identifies content using a label supporting lower case characters and specified character sets. - If a Code String is required, see . - - +
+ Enhanced Content Identification Macro + + specifies the Attributes of the Enhanced Content Identification Macro, which identifies content using a label supporting lower case characters and specified character sets. If a Code String is required, see . +
Enhanced Content Identification Macro Attributes
+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Enhanced Content Identification Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ User Content Label + + (3010,0033) + + 1 + + User-defined label for this SOP Instance. + See . +
+ Content Description + + (0070,0081) + + 2 + + User-defined description for the content of this SOP Instance. + See . +
+ + Include + + + + +
+
+ Enhanced Content Identification Macro Attribute Descriptions +
+ User Content Label and Content Description + User Content Label (3010,0033) shall represent a user-defined short free text providing the primary identification of this entity to other users. Content Description (0070,0081) allows a longer string containing additional descriptive identifying text. + This information is intended for display to human readers. Shall not be used for structured processing. +
+
+
+
+ Extended Content Identification Macro + + specifies the Attributes of the Extended Content Identification Macro, which identifies content using a label supporting lower case characters and specified character sets. If a Code String is required, see . + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Extended Content Identification Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ User Content Long Label + + (3010,0034) + + 1 + + User-defined label for the content of this SOP Instance. + See . +
+ Content Description + + (0070,0081) + + 2 + + User-defined description for the content of this SOP Instance. + See . +
+ + Include + + + + +
+
+ Extended Content Identification Macro Attribute Descriptions +
+ User Content Long Label and Content Description + User Content Long Label (3010,0034) shall represent a user-defined free text providing the primary identification of this entity to other users. Content Description (0070,0081) allows a longer string containing additional descriptive identifying text. + This information is intended for display to human readers. Shall not be used for structured processing. +
+
+
+
+ Content Creator Macro + + - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Content Creator Macro Attributes
- Attribute Name + Attribute Name - Tag + Tag - Type + Type - Attribute Description + Attribute Description
- User Content Label - - (3010,0033) - - 1 - - User-defined label for this SOP Instance. - See . -
- Content Description - - (0070,0081) - - 2 - - User-defined description for the content of this SOP Instance. - See . + + Content Creator's Name
- Content Creator"s Name - - (0070,0084) - - 2 - - Name of operator (such as a technologist or physician) creating the content of the SOP Instance. + + (0070,0084)
- Content Creator"s Identification Code Sequence - - (0070,0086) - - 3 - - Identification of the person who created the content. - Only a single Item is permitted in this Sequence. + + 3
- - >Include - - - - - - + + Name of operator (such as a technologist or physician) creating the content of the SOP Instance.
-
- Enhanced Content Identification Macro Attribute Descriptions -
- User Content Label and Content Description - User Content Label (3010,0033) shall represent a user-defined short free text providing the primary identification of this entity to other users. - Content Description (0070,0081) allows a longer string containing additional descriptive identifying text. - This information is intended for display to human readers. Shall not be used for structured processing. -
-
-
-
- Extended Content Identification Macro - The Extended Content Identification Macro identifies content using a label supporting lower case characters and specified character sets. - If a Code String is required, see . - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +
Extended Content Identification Macro Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- User Content Long Label - - (3010,0034) - - 1 - - User-defined label for the content of this SOP Instance. - See . + + Content Creator's Identification Code Sequence
- Content Description - - (0070,0081) - - 2 - - User-defined description for the content of this SOP Instance. - See . + + (0070,0086)
- Content Creator's Name - - (0070,0084) - - 2 - - Name of operator (such as a technologist or physician) creating the content of the SOP Instance. + + 3
- Content Creator's Identification Code Sequence - - (0070,0086) - - 3 - - Identification of the person who created the content. - Only a single Item is permitted in this Sequence. + + Identification of the person who created the content. + Only a single Item is permitted in this Sequence.
- - >Include - - - - - + + + >Include + + +
-
- Extended Content Identification Macro Attribute Descriptions -
- User Content Long Label and Content Description - User Content Long Label (3010,0034) shall represent a user-defined free text providing the primary identification of this entity to other users. - Content Description (0070,0081) allows a longer string containing additional descriptive identifying text. - This information is intended for display to human readers. Shall not be used for structured processing. -
-
-
- General Contributing Sources Macro - - contains IOD Attributes that describe the general characteristics of the contributing sources used to create a new SOP Instance. + General Contributing Sources Macro + + specifies the Attributes of the , which describe the general characteristics of the contributing sources used to create a new SOP Instance. @@ -8305,9 +8431,9 @@ Typically the General Contributing Sources Macro is invoked from inside another Sequence. Therefore, if the "common" Attributes of the Macro are different among the Referenced SOP Instances, like different acquisition protocols, software versions etc., the invoking Sequence will contain several Items.
- Contributing Image Sources Macro - - contains IOD Attributes that describe the image related characteristics of the contributing image sources used to create a new SOP Instance (e.g., a volume SOP Instance). + Contributing Image Sources Macro + + specifies the Attributes of the , which describe the image related characteristics of the contributing image sources used to create a new SOP Instance (e.g., a volume SOP Instance).
General Contributing Sources Macro Attributes
@@ -8440,8 +8566,8 @@
Patient Orientation Macro - This section describes the Patient orientation related to gravity and equipment. - contains Attributes that describe the Patient Orientation related to gravity and equipment. + + specifies the Attributes of the Patient Orientation Macro, which describe the Patient Orientation related to gravity and equipment.
Contributing Image Sources Macro Attributes
@@ -8530,7 +8656,7 @@ 3 @@ -8549,107 +8675,109 @@
Patient Orientation Macro Attributes
- Sequence that describes the orientation of the Patient with respect to the head of the table. See for further explanation. + Description of the orientation of the Patient with respect to the head of the table. See for further explanation. Only a single Item is permitted in this Sequence.
+ + contains Attributes that describe the Patient Orientation related to gravity and the mandatory relationship to the equipment. @@ -8870,9 +8998,9 @@
Patient Orientation And Equipment Relationship Macro Attributes
- Attribute Name + Attribute Name - Tag + Tag - Type + Type - Attribute Description + Attribute Description
- Patient Orientation Code Sequence + Patient Orientation Code Sequence - (0054,0410) + (0054,0410) - 1 + 1 - Sequence that describes the orientation of the Patient with respect to gravity. - See and for further explanation. - Only a single Item shall be included in this Sequence. + Sequence that describes the orientation of the Patient with respect to gravity. + See and for further explanation. + Only a single Item shall be included in this Sequence.
- + >Include - + B.
- >Patient Orientation Modifier Code Sequence + >Patient Orientation Modifier Code Sequence - (0054,0412) + (0054,0412) - 1C + 1C - Patient orientation modifier. - Required if needed to fully specify the orientation of the Patient with respect to gravity. - Only a single Item shall be included in this Sequence. + Patient orientation modifier. + Required if needed to fully specify the orientation of the Patient with respect to gravity. + Only a single Item shall be included in this Sequence.
- + >>Include - + B.
- Patient Equipment Relationship Code Sequence + Patient Equipment Relationship Code Sequence - (3010,0030) + (3010,0030) - 3 + 1 - Description of the orientation of the Patient with respect to the equipment. See for further explanation. - Only a single Item is permitted in this Sequence. + Description of the orientation of the Patient with respect to the equipment. See for further explanation. + Only a single Item shall be included in this Sequence.
- + >Include - + B.
- HL7v2 Hierarchic Designator Macro - - describes the Attributes for identifying an entity (system, organization, agency, or department) that has responsibility for managing or assigning a defined set of instance identifiers (such as placer or filler number, Patient identifiers, provider identifiers, etc.). This entity could be a particular health care application such as a registration system that assigns Patient identifiers, a governmental entity such as a licensing authority that assigns professional identifiers or drivers' license numbers, or a facility where such identifiers are assigned. + HL7v2 Hierarchic Designator Macro + + specifies the Attributes of the , which identify an entity (system, organization, agency, or department) that has responsibility for managing or assigning a defined set of instance identifiers (such as placer or filler number, Patient identifiers, provider identifiers, etc.). This entity could be a particular health care application such as a registration system that assigns Patient identifiers, a governmental entity such as a licensing authority that assigns professional identifiers or drivers' license numbers, or a facility where such identifiers are assigned. This definition is identical to HL7 v2.5, Section 2.A.33, with only minor changes for editorial style. @@ -8988,9 +9116,9 @@
- Issuer of Patient ID Macro - - describes the Attributes for identifying the source of Patient ID (0010,0020). + Issuer of Patient ID Macro + + specifies the Attributes of the , which identify the source of Patient ID (0010,0020). These Attributes are equivalent to components of the HL7 v2 Extended Composite ID with Check Digit (CX) data type (see HL7 v2 Chapter 2.A.14), as used in the HL7 v2 PID-3 Patient Identifier List field. @@ -9188,9 +9316,9 @@
Issuer of Patient ID Macro Attributes
- Algorithm Identification Macro - - describes the Attributes for encoding the algorithm used to create or derive a SOP Instance contents. An algorithm is described by the Algorithm Family, a specific Algorithm Name, and an Algorithm Version. A character string containing parameters that were used in the algorithm can be included. + Algorithm Identification Macro + + specifies the Attributes of the , which identifies and describes the algorithm used to create or derive a SOP Instance contents. An algorithm is described by the Algorithm Family, a specific Algorithm Name, and an Algorithm Version. A character string containing parameters that were used in the algorithm can be included. @@ -9328,7 +9456,7 @@
Selector Attribute Macro - specifies the Attributes that identify either a particular value of an Attribute, all values of an Attribute, a specific Item in a Sequence, or all Items in a Sequence. The Attribute or Item may be nested within one or more Sequences, and/or a Private Attribute. + specifies the Attributes of the , which identify either a particular value of an Attribute, all values of an Attribute, a specific Item in a Sequence, or all Items in a Sequence. The Attribute or Item may be nested within one or more Sequences, and/or a Private Attribute. The invocation of the Selector Attribute Macro may define additional semantics. E.g., if the Selector Attribute Macro is used to select "all" values of an Attribute and then test that set of value against some condition, then an invocation might define whether it is required that at least one value in the set meet the condition or whether all values in the set must meet the condition. extends the Selector Attribute Macro with additional Attribute descriptors. @@ -9706,9 +9834,9 @@
- Externally-Sourced Data Set Identification Macro - - describes the Attributes for the identification of an Externally-Sourced Data Set. + Externally-Sourced Data Set Identification Macro + + specifies the Attributes of the , which identify an Externally-Sourced Data Set.
Algorithm Identification Macro Attributes
@@ -9788,9 +9916,9 @@
Externally-Sourced Data Set Identification Macro Attributes
- Exposure Index Macro - - describes the Attributes for describing the Exposure Index for single projection X-Ray images, as described by IEC 62494-1 and the report of AAPM Task Group 116. + Exposure Index Macro + + specifies the Attributes of the , which describe the Exposure Index for single projection X-Ray images, as described by IEC 62494-1 and the report of AAPM Task Group 116. @@ -9866,9 +9994,9 @@
Exposure Index Macro Attributes
- Mandatory View and Slice Progression Direction Macro - - specifies the Attributes that describe the view, and in the case of cardiac views, the direction of the slices relative to the cardiac anatomy. + Mandatory View and Slice Progression Direction Macro + + specifies the Attributes of the , which describe the view, and in the case of cardiac views, the direction of the slices relative to the cardiac anatomy. @@ -9964,7 +10092,7 @@
Mandatory View and Slice Progression Direction Macro Attributes
- Mandatory View and Slice Progression Direction Macro Attributes + Mandatory View and Slice Progression Direction Macro Attribute Descriptions
Slice Progression Direction The image or frame order to which the Slice Progression Direction (0054,0500) applies depends on the IOD: @@ -10043,9 +10171,9 @@
- Optional View and Slice Progression Direction Macro - - specifies the Attributes that describe the view, and in the case of cardiac views, the direction of the slices relative to the cardiac anatomy. + Optional View and Slice Progression Direction Macro + + specifies the Attributes of the , which describe the view, and in the case of cardiac views, the direction of the slices relative to the cardiac anatomy. @@ -10140,9 +10268,9 @@
Optional View and Slice Progression Direction Macro Attributes
- Numeric Value Macro - - describes the Attributes used to relate and convey a numeric value to a coded concept. + Numeric Value Macro + + specifies the Attributes of the , which is used to relate and convey a numeric value to a coded concept. @@ -10238,7 +10366,7 @@
RT Equipment Correlation Macro
Numeric Value Macro Attributes
- +
RT Equipment Correlation Macro Attributes DescriptionRT Equipment Correlation Macro Attributes
@@ -10330,11 +10458,11 @@
- Device Motion Control Macro - - specifies the Attributes that describe requirements on performing the movement of a device from an actual to a desired position. + Device Motion Control Macro + + specifies the Attributes of the , which describe requirements on performing the movement of a device from an actual to a desired position. - +
Device Motion Control Macro Attributes DescriptionDevice Motion Control Macro Attributes
@@ -10430,7 +10558,7 @@
- Device Motion Control Macro Attributes + Device Motion Control Macro Attribute Descriptions
Device Motion Execution Mode Device Motion Execution Mode (300A,0451) identifies how the operator invokes and controls the motion. @@ -10478,9 +10606,9 @@
- Attribute Value Constraint Macro - - allows an Attribute to be identified and to have constraints placed on acceptable values for that Attribute. An Attribute being constrained is referred to in the Macro as a Selector Attribute. + Attribute Value Constraint Macro + + specifies the Attributes of the , which allows an Attribute to be identified and to have constraints placed on acceptable values for that Attribute. An Attribute being constrained is referred to in the Macro as a Selector Attribute. @@ -10852,9 +10980,9 @@
- Attribute Value Macro - - includes an Attribute to store a value of a specified VR. + Attribute Value Macro + + specifies the Attributes of the , which includes an Attribute to store a value of a specified VR. @@ -11417,7 +11545,8 @@
Reference Location Macro - This Macro allows a reference location in the context of a Patient or scan to be identified and described. E.g., the Macro may describe an anatomically defined location along the axis of a CT scan to prescribe the extent of a scan or reconstruction. The location might be internal to the Patient (and appear on a localizer image) or might be an external landmark (on which a laser is aligned). + + specifies the Attributes of the Reference Location Macro, which allows a reference location in the context of a Patient or scan to be identified and described. E.g., the Macro may describe an anatomically defined location along the axis of a CT scan to prescribe the extent of a scan or reconstruction. The location might be internal to the Patient (and appear on a localizer image) or might be an external landmark (on which a laser is aligned).
Attribute Value Macro Attributes
@@ -11698,7 +11827,8 @@
Protocol Element Identification Macro - This Macro identifies and describes an element in a protocol such as an acquisition protocol, a reconstruction protocol or a storage protocol. + + specifies the Attributes of the Protocol Element Identification Macro, which identifies and describes an element in a protocol such as an acquisition protocol, a reconstruction protocol or a storage protocol.
Reference Location Macro Attributes
@@ -11765,7 +11895,7 @@ This is intended for use by the radiologist, technologist and/or physicist during management of the Protocol to understand the purpose the Protocol Element serves in the Protocol. - It is not intended to be copied into the Series Description. Rather there is an Attribute in the Performed Storage Module called Requested Series Description (0018,9937) that is intended to be copied into the Series Description of the stored Instances. + It is not intended to be copied into the Series Description. Rather there is an Attribute in the called Requested Series Description (0018,9937) that is intended to be copied into the Series Description of the stored Instances. @@ -11789,7 +11919,7 @@ This is intended for use by the radiologist, technologist and/or physicist during management of the Protocol to understand the characteristics of the Protocol Element. - It is not intended to be copied into the Series Description. Rather there is an Attribute in the Performed Storage Module called Requested Series Description (0018,9937) that is intended to be copied into the Series Description of the stored Instances. + It is not intended to be copied into the Series Description. Rather there is an Attribute in the called Requested Series Description (0018,9937) that is intended to be copied into the Series Description of the stored Instances. @@ -11800,7 +11930,8 @@
UDI Macro - This Macro records details associated with a Unique Device Identifier (UDI). + + specifies the Attributes of the UDI Macro, which records details associated with a Unique Device Identifier (UDI).
Protocol Element Identification Macro Attributes
@@ -11878,7 +12009,8 @@
Assertion Macro - This Macro is used to record Assertions made by a person or device about the content of a SOP Instance. The nature of the Assertion is defined by the Assertion Code. + + specifies the Attributes of the , which is used to record Assertions made by a person or device about the content of a SOP Instance. The nature of the Assertion is defined by the Assertion Code. The scope of the Assertion (e.g., whether it applies to the whole Instance, to a specific Item in a Sequence, etc.) is described at the point where the Macro is included. It is also expected that when this Macro is included, the Baseline CID for the Assertion Code Sequence (0044,0101) will be constrained.
UDI Macro Attributes
@@ -12056,9 +12188,9 @@ 3 - + Unique identifier for the referenced document as used in DICOM Instance references (see ). + + + + + + + + + + + + + + + + + + + +
Assertion Macro Attributes
- Unique identifier for the referenced document as used in DICOM Instance references (see ) -
>HL7 Instance Identifier @@ -12125,7 +12257,8 @@
Entity Labeling Macro - The Entity Labeling Macro provides identification of an entity to a user. + + specifies the Attributes of the , which provides identification of an entity to a user. This information is intended for display to human readers. Shall not be used for structured processing. @@ -12208,7 +12341,8 @@
Entity Long Labeling Macro - The Entity Long Labeling Macro provides identification of an entity to a user. + + specifies the Attributes of the Entity Long Labeling Macro, which provides identification of an entity to a user. This information is intended for display to human readers. Shall not be used for structured processing.
Entity Labeling Macro Attributes
@@ -12271,7 +12405,8 @@
Conceptual Volume Macro - A Conceptual Volume is an abstract entity used to identify an anatomic region (such as a planning target volume or a combination of multiple anatomic volumes) or non-anatomic volumes such as a bolus or a marker. + + specifies the Attributes of the . A Conceptual Volume is an abstract entity used to identify an anatomic region (such as a planning target volume or a combination of multiple anatomic volumes) or non-anatomic volumes such as a bolus or a marker. A Conceptual Volume can be established without necessarily defining its spatial extent (for example a Conceptual Volume for a tumor can be established prior to segmenting it). The spatial extent of a Conceptual Volume may change over time (for example as treatment proceeds the tumor volume corresponding to the Conceptual Volume will change). The spatial extent of a Conceptual Volume may be defined by any general-purpose entity that represents geometric information (such as Segmentation, Surface Segmentation, RT Structure Set SOP Instance and alike) or a combination thereof, although the Conceptual Volume does exist independently of a specific definition of its spatial extent. @@ -12587,7 +12722,8 @@
Conceptual Volume Segmentation Reference and Combination Macro - This Macro allows the combination of Conceptual Volumes as constituents of a combined volume. + + specifies the Attributes of the , which allows the combination of Conceptual Volumes as constituents of a combined volume. A representative example is to have the Left Lung and the Right Lung segmented, and then to declare the Lungs as a combined Conceptual Volume, for which prescription constraints can be defined. The Macro also allows reference to RT Segment Annotation SOP Instances, which contain a segmented representation of the Conceptual Volume. @@ -13332,7 +13468,8 @@
Device Model Macro - The Device Model Macro contains general Attributes needed to specify a device model other than the device creating the SOP Instance. + + specifies the Attributes of the Device Model Macro, which contains general Attributes needed to specify a device model other than the device creating the SOP Instance.
Entity Long Labeling Macro Attributes
@@ -13399,7 +13536,8 @@
Device Identification Macro - The Device Identification Macro identifies a (physical or virtual) device. + + specifies the Attributes of the Device Identification Macro, which identifies a (physical or virtual) device.
Device Model Macro Attributes
@@ -13626,9 +13764,10 @@
Related Information Entities Macro - This Macro defines references to entities and their purpose of reference. References can be made at the Study level, Series level, Instance level or Frame Level. - The attributes Pertinent SOP Classes in Study (3010,0052) and Pertinent SOP Classes in Series (3010,0053) allow the specification of the relevant SOP Classes for the given purpose. - These attributes support filtering for certain SOP Classes, specification of corresponding query keys, and allowing the receiving application to assess its capabilities to handle the specified objects. + + specifies the Attributes of the Related Information Entities Macro, which defines references to entities and their purpose of reference. References can be made at the Study level, Series level, Instance level or Frame Level. + The Attributes Pertinent SOP Classes in Study (3010,0052) and Pertinent SOP Classes in Series (3010,0053) allow the specification of the relevant SOP Classes for the given purpose. + These Attributes support filtering for certain SOP Classes, specification of corresponding query keys, and allowing the receiving application to assess its capabilities to handle the specified objects. All referenced Studies, Series and Instances share the same single Purpose of Reference.
Device Identification Macro Attributes
@@ -13826,7 +13965,8 @@
Outline Definition Macro - The Outline Definition Macro describes a 2D outline in a given coordinate system. + + specifies the Attributes of the Outline Definition Macro, which describes a 2D outline in a given coordinate system.
Related Information Entities Macro Attributes
@@ -14026,7 +14166,8 @@
Patient to Equipment Relationship Macro - The Patient to Equipment Relationship Macro describes a position of the patient with respect to a device. The position is defined by means of a transformation matrix between a Patient Frame of Reference and an Equipment Frame of Reference. + + specifies the Attributes of the Patient to Equipment Relationship Macro, which describes the position of the patient with respect to a device. The position is defined by means of a transformation matrix between a Patient Frame of Reference and an Equipment Frame of Reference.
Outline Definition Macro Attributes
@@ -14092,7 +14233,7 @@ + + + + + +
Patient to Equipment Relationship Macro Attributes
- >3D Point Coordinate + >3D Point Coordinates (0068,6590) @@ -14169,16 +14310,20 @@ The Image to Equipment Mapping Matrix (0028,9520) describes the relationship between the Patient-oriented coordinate system and an Equipment Coordinate System. This matrix AM Bdescribes a rigid transformation of a point ( Bx, By, Bz) with respect to the Patient coordinate system into ( Ax, Ay, Az) with respect to the Equipment Coordinate System as defined in . The Equipment Coordinate System is identified by the Equipment Frame of Reference UID (300A,0675). For further information on the definition of the Equipment Frame of Reference, see . The patient-oriented coordinate system is identified by the Frame of Reference UID (0020,0052) of the SOP Instance it is used within. Both coordinate systems are expressed in millimeters. - The Patient Support Position Macro invoked by Patient Support Position Sequence (3006,00CB) allows the exchange of device-specific parameters for the patient support device. Applications designed to guide a specific patient support device will be able to de-compose the transformation into device-specific parameters or derive a transformation matrix out of these parameters. Applications that are unable to know the decomposition of the transformation to those parameters and vice versa will still be able to display the native labels and numerical values of those parameters to human readers. - The Patient Support Position Sequence (3006,00CB) may be present to annotate the matrix and display the decomposed matrix contents. The content of the Patient Support Position Macro shall be used for display purposes only. It shall not be used for other purposes. The content of this Macro shall not be used as a substitute for the Image to Equipment Mapping Matrix (0028,9520). In general, there is more than one way to reach the point in space that is described by the Image to Equipment Mapping Matrix (0028,9520). Hence it is explicitly not implied how this position is reached. - In some cases (e.g., emergency treatments in Radiotherapy), the Patient Frame of Reference is not defined by an image series. In this case an arbitrary Frame of Reference is used for the patient coordinate system in the Frame of Reference Module of the SOP Instance. The Image to Equipment Mapping Matrix (0028,9520) has the same meaning as in the case of image-based Patient Frame of Reference. + The invoked by Patient Support Position Sequence (3006,00CB) allows the exchange of device-specific parameters for the patient support device. Applications designed to guide a specific patient support device will be able to de-compose the transformation into device-specific parameters or derive a transformation matrix out of these parameters. Applications that are unable to know the decomposition of the transformation to those parameters and vice versa will still be able to display the native labels and numerical values of those parameters to human readers. + The Patient Support Position Sequence (3006,00CB) may be present to annotate the matrix and display the decomposed matrix contents. The content of the shall be used for display purposes only. It shall not be used for other purposes. The content of this Macro shall not be used as a substitute for the Image to Equipment Mapping Matrix (0028,9520). In general, there is more than one way to reach the point in space that is described by the Image to Equipment Mapping Matrix (0028,9520). Hence it is explicitly not implied how this position is reached. + In some cases (e.g., emergency treatments in Radiotherapy), the Patient Frame of Reference is not defined by an image series. In this case an arbitrary Frame of Reference is used for the patient coordinate system in the of the SOP Instance. The Image to Equipment Mapping Matrix (0028,9520) has the same meaning as in the case of image-based Patient Frame of Reference. + When a Frame of Reference of a patient model is not available, the well-known Frame of Reference of a patient support device may be used. + The well-known Frame of Reference and its origin and orientation with respect to the device shall be documented in the Conformance Statement. Note that the orientation of the axes of the well-known Frame of Reference are tied to the device and not to the patient. + As an example, the initial position needs to be specified for the patient setup, prior to any imaging. For a treatment table whose origin and orientation are defined by , the well-known Frame of Reference UID "1.2.840.10008.1.4.3.3" may be used. If the Image to Equipment Mapping Matrix (0028,9520) and the Patient Support Position Sequence (3006,00CB) are both present, the information in both locations shall be consistent.
Patient Support Position Macro - This Macro provides the device-specific geometric settings for the Patient Support device. + + specifies the Attributes of the , which provides the device-specific geometric settings for the Patient Support device. The information is intended for display to human readers and to support non-image-based patient positioning; however, the definition of the patient position with respect to the device is contained in the Image to Equipment Mapping Matrix (0028,9520). @@ -14337,7 +14482,7 @@ IEC 61217 Patient Support DeviceDevices using the IEC 61217 coordinate systems to define geometric settings for the Patient Support device shall use the codes in in the order specified in column Patient Support Position Parameter Order Index (300A,065F). Other codes shall not be used.
Patient Support Position Macro Attributes
- + + + + + + + + + + + + + + + + + - + @@ -18348,6 +18742,58 @@ M + + + + + + + + + + + + + + - + + + + + @@ -18476,7 +18942,7 @@ C - + @@ -18496,7 +18962,7 @@ C - + @@ -18938,7 +19404,7 @@ - + @@ -18958,7 +19424,7 @@ U - + @@ -18978,7 +19444,7 @@ U - + @@ -19744,7 +20210,7 @@ - + @@ -20594,74 +21060,94 @@ + + + + + @@ -20700,6 +21186,26 @@ U + + + + + + + + + + + + + + + - + @@ -23099,7 +23633,7 @@ - + @@ -23114,7 +23648,7 @@ M - + @@ -23217,15 +23751,9 @@ - - @@ -23278,11 +23806,9 @@ - - @@ -23333,11 +23859,9 @@ - - @@ -23388,11 +23912,9 @@ - - @@ -23443,11 +23965,9 @@ - - @@ -23498,11 +24018,9 @@ - - @@ -23551,11 +24069,9 @@ - - @@ -23600,11 +24116,9 @@ - - @@ -23630,8 +24144,6 @@ @@ -23661,8 +24173,6 @@ - + @@ -23983,8 +24469,6 @@ @@ -24010,12 +24494,10 @@ @@ -24063,11 +24545,9 @@ - - @@ -24110,11 +24590,9 @@ - @@ -24141,37 +24619,10 @@ - - - - - - - - - - - - @@ -24440,8 +24825,6 @@ @@ -24465,8 +24848,6 @@ @@ -24506,8 +24887,6 @@ - - @@ -24871,88 +25224,11 @@ - - - - - - - - - - - - @@ -25022,15 +25296,9 @@ - - @@ -26197,10 +26465,10 @@ Rob Arm Rec @@ -26243,10 +26511,10 @@ M @@ -26287,10 +26555,10 @@ U @@ -26331,10 +26599,10 @@ M @@ -26375,10 +26643,10 @@ U @@ -26419,10 +26687,10 @@ U @@ -26459,10 +26727,10 @@ M @@ -26503,10 +26771,10 @@ U @@ -26547,10 +26815,10 @@ M @@ -26591,10 +26859,10 @@ M @@ -26635,10 +26903,10 @@ M @@ -26675,7 +26943,7 @@ - + @@ -26737,10 +27005,10 @@ M @@ -26845,7 +27113,7 @@ @@ -27238,10 +27506,10 @@ M @@ -27282,10 +27550,10 @@ M @@ -27326,10 +27594,10 @@ M @@ -29074,7 +29342,7 @@ - + @@ -29626,7 +29894,7 @@ - + @@ -31228,7 +31496,7 @@ M - + @@ -31244,7 +31512,7 @@ M - + @@ -31712,6 +31980,127 @@
Isocentric Patient Support Position Parameter Order IndexIEC 61217 Patient Support Position Parameter Order Index
@@ -14512,9 +14657,9 @@
- General Procedure Protocol Reference Macro - - describes the Attributes for identifying the Procedure Protocol SOP Instance and the Protocol Element related to the creation of an Instance. + General Procedure Protocol Reference Macro + + specifies the Attributes of the , which identifies the Procedure Protocol SOP Instance and the Protocol Element related to the creation of an Instance. Because all the Instances in a Series are often generated from the same acquisition/reconstruction protocol, protocol is often considered at the Series level (Protocol Name (0018,1030) is in the General Series Module). It is however valid to have several Instances in the same Series where each Instance was generated using a different protocol and/or a different protocol element. @@ -14667,6 +14812,178 @@ In case where the acquisition and the reconstruction are done in two separate devices connected through the network, the reconstruction device can use the Source Acquisition Protocol Element of the Referenced Defined Protocol to determine the images that will be reconstructed with a given reconstruction protocol element.
+
+ Hierarchical Evidence Reference Macro + + specifies the Attributes of the . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Hierarchical Evidence Reference Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Referenced Raw Data Sequence + + (0008,9121) + + 3 + + The Raw data that was used to derive this Image. + One or more Items are permitted in this Sequence. + + The Items of in this Sequence may identify raw data that has not been stored or encoded as a DICOM object. This allows recognition that images and spectra in different Instances have been reconstructed from the same raw data. For such Items the SOP Class UID may be "1.2.840.10008.5.1.4.1.1.66" (Raw Data SOP Class). + +
+ + >Include + + + + +
+ Referenced Waveform Sequence + + (0008,113A) + + 3 + + References to waveforms acquired in conjunction with this image. These Waveforms may or may not be temporally synchronized with this image. + One or more Items are permitted in this Sequence. +
+ + >Include + + + + +
+ Referenced Image Evidence Sequence + + (0008,9092) + + 1C + + Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this Instance. See for further explanation. + One or more Items shall be included in this Sequence. + Required if the Referenced Image Sequence (0008,1140) is present and not empty, and the SOP Class UID of the referencing SOP Instance is not a legacy converted SOP Class (Legacy Converted Enhanced CT Image Storage "1.2.840.10008.5.1.4.1.1.2.2", Legacy Converted Enhanced MR Image Storage "1.2.840.10008.5.1.4.1.1.4.4", Legacy Converted Enhanced PET Image Storage "1.2.840.10008.5.1.4.1.1.128.1"). May be present otherwise. +
+ + >Include + + + + +
+ Source Image Evidence Sequence + + (0008,9154) + + 1C + + Full set of Composite SOP Instances referred to inside the Source Image Sequences of this Instance. See for further explanation. + One or more Items shall be included in this Sequence. + Required if the Source Image Sequence (0008,2112) is present and not empty, and the SOP Class UID of the referencing SOP Instance is not a legacy converted SOP Class (Legacy Converted Enhanced CT Image Storage "1.2.840.10008.5.1.4.1.1.2.2", Legacy Converted Enhanced MR Image Storage "1.2.840.10008.5.1.4.1.1.4.4", Legacy Converted Enhanced PET Image Storage "1.2.840.10008.5.1.4.1.1.128.1"). May be present otherwise. +
+ + >Include + + + + +
+ Referenced Presentation State Sequence + + (0008,9237) + + 1C + + References to Presentation State instances created together with this instance + + This Sequence does not reference Presentation States generated after image creation, such as during interpretation. + + One or more Items shall be included in this Sequence. + Required if Presentation State is created together with the images. +
+ + >Include + + + + +
+
+ Hierarchical Evidence Reference Macro Attribute Descriptions +
+ Evidence Sequence Attributes + The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) Attributes respectively. +
+
+
Composite Information Object Definitions (Normative) @@ -14788,30 +15105,30 @@
Real World Value Mapping Data - The Real World Value Mapping data describes the transformation of the image pixel values into real world values in defined units. There may be multiple transformations, each scoped by a range of input pixel values. Each transformation may be linear, described by Slope and Intercept, or non-linear, described by a Lookup Table. + The Real World Value Mapping data describes the transformation of the image pixel values into Real World Values in defined units. There may be multiple transformations, each scoped by a range of input pixel values. Each transformation may be linear, described by Slope and Intercept, or non-linear, described by a Lookup Table.
Overlay IE - Retired. See PS3.3-2016a. + Retired. See PS3.3-2016a. Overlays were previously modeled as independent Information Entities; in the current model they are considered Attributes within the Image IE or Presentation State IE. See .
Curve IE - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Modality LUT IE - Retired. See PS3.3-2016a. + Retired. See PS3.3-2016a. Modality LUTs were previously modeled as independent Information Entities; in the current model they are considered Attributes within the Image IE or Presentation State IE. See .
VOI LUT IE - Retired. See PS3.3-2016a. + Retired. See PS3.3-2016a. VOI LUTs were previously modeled as independent Information Entities; in the current model they are considered Attributes within the Image IE or Presentation State IE. See . @@ -14912,6 +15229,35 @@ Procedure Protocol IE The Procedure Protocol IE defines the Attributes that describe a Protocol. This IE may encode a Defined Procedure Protocol or a Performed Procedure Protocol.
+
+ Acquisition IE + The Acquisition IE defines the Attributes that describe a single continuous gathering of data. + An Acquisition may result in more than one Series, and a Series may contain Instances from more than one Acquisition. +
+
+ Multi-Resolution Pyramid IE + The Multi-Resolution Pyramid IE describes a set of Images that encode the same image data at different spatial resolutions, i.e., a base (highest resolution) layer that is successively smoothed and down-sampled to create additional lower resolution layers (a multi-resolution decomposition). + + No specific method of filtering or down-sampling is specified by the Standard, nor is there a requirement for any specific down-sampling factor between layers, nor that an integer factor be used. + + Each layer is encoded as a separate DICOM Image, each of which has a uniform resolution (same value for Pixel Spacing (0028,0030)). Layers may be tiled, with each tile encoded as a frame of a multi-frame image. + All DICOM Image SOP Instances that constitute a single Multi-Resolution Pyramid shall share the same Frame of Reference, and shall be contained in the same Series. + Only one Multi-Resolution Pyramid shall be contained in a Series (i.e., each such Multi-Resolution Pyramid will be in a different Series). + + + + In historical usage, there is no Multi-Resolution Pyramid IE and thus a Series is not constrained to contain only a single conceptual pyramid. However, any instantiation of the Multi-Resolution Pyramid in a Series constrains the Series to one Multi-Resolution Pyramid. + + + Each Multi-Resolution Pyramid may be accompanied in the same Series by LABEL, OVERVIEW and THUMBNAIL images if they share the same Frame of Reference (but not otherwise, per the definition of the Series IE). The THUMBNAIL image rather than a VOLUME image may be the apex (lowest resolution layer) of the Multi-Resolution Pyramid. + + + A unique identifier, Pyramid UID (0008,0019) will be assigned to an instance of a Multi-Resolution Pyramid, and will be shared by all of the layers that constitute that instance of a Multi-Resolution Pyramid, whether or not a particular resolution layer (usually the highest resolution) is deemed to be ORIGINAL, and the lower resolution layers DERIVED (e.g., by some down-sampling image processing operation). By definition, the absence of Pyramid UID (0008,0019) implies the absence of instantiation of the Multi-Resolution Pyramid IE. + That use is distinct from the Pyramid UID (0008,0019) of different Multi-Resolution Pyramids that may be further derived from a Multi-Resolution Pyramid. In otherwords, the Pyramid UID (0008,0019) of a Multi-Resolution Pyramid will not be shared between two pyramids that contain different pixel data (other than differences due to lossless representation of the same pixel data in different Transfer Syntaxes). + + + +
IOD Module Table and Functional Group Macro Table @@ -15915,6 +16261,54 @@
+ Acquisition + + M + + M + + + M + + + + M + + M + + M + + M + + M + + M + + M + + M + + M + + M + +
General Image @@ -18130,7 +18524,7 @@
Parametric Map Series
+ Acquisition + + M + + + M + + + + + + + M + + M + + M + + M + + U +
+ Multi-Resolution Pyramid + + + + + + + + + + + + + + U +
General Image @@ -18456,7 +18902,27 @@ C
+ Microscope Slide Layer Tile Organization + + + + + + + + + + + + + + C +
Floating Point Image Pixel
Double Floating Point Image Pixel
Palette Color Lookup Table
Cardiac Synchronization
Respiratory Synchronization
Bulk Motion Synchronization
Parametric Map Image
- General Image + Acquisition - M + M - M + M - M + M - M + M - M + M - M + M - M + M - M + M - M + M - M + U +
+ Multi-Resolution Pyramid + + + + + U + + + + + + + + U
- General Image + General Image - U + M - U + M - U + M - U + M - U + M - U + M - U + M - U + M - U + M - U + M
+ Microscope Slide Layer Tile Organization + + + + + M + + + + + + + + C +
Image Pixel @@ -21855,6 +22361,34 @@ M
+ Acquisition + + M + + M + + M + + M + + + M + + + M + + M +
General Image @@ -23058,7 +23592,7 @@
Content Assessment Results
Common Instance Reference
ICC Profile Str Rl - HP - Sfc Seg - Col Pal - Bs St Dsp M M M U U U M M M U U U U U U M M M U U U - - M - -
@@ -23686,8 +24196,6 @@ - -
@@ -23711,8 +24219,6 @@ - -
@@ -23736,8 +24242,6 @@ - -
@@ -23756,13 +24260,11 @@ - M -
@@ -23786,8 +24288,6 @@ - -
@@ -23811,8 +24311,6 @@ - -
@@ -23836,8 +24334,6 @@ - -
@@ -23861,8 +24357,6 @@ - -
@@ -23886,8 +24380,6 @@ - -
@@ -23911,8 +24403,6 @@ - -
@@ -23936,8 +24426,6 @@ - -
@@ -23961,10 +24449,8 @@ - -
Tractography Results Series - - M - M - M M M M - M M - - U
- Palette Color LUT - - - - - - - - - - - - - - - - - M - - -
Stereometric Relationship @@ -24194,33 +24645,6 @@ - - -
- ICC Profile - - - - - - - - - - - - - - - - - M - -
@@ -24244,8 +24668,6 @@ - -
@@ -24269,8 +24691,6 @@ - -
@@ -24294,8 +24714,6 @@ - -
@@ -24319,8 +24737,6 @@ - -
@@ -24339,13 +24755,11 @@ - M -
@@ -24364,38 +24778,11 @@ - M - -
- Color Palette Definition - - - - - - - - - - - - - - - - - M - -
@@ -24415,8 +24802,6 @@ - - M - - M - - U - -
@@ -24531,8 +24910,6 @@ - -
@@ -24556,8 +24933,6 @@ - -
@@ -24581,8 +24956,6 @@ - -
@@ -24606,8 +24979,6 @@ - -
@@ -24631,8 +25002,6 @@ - -
@@ -24656,8 +25025,6 @@ - -
@@ -24681,8 +25048,6 @@ - -
@@ -24706,8 +25071,6 @@ - -
@@ -24731,8 +25094,6 @@ - -
@@ -24756,8 +25117,6 @@ - -
@@ -24781,8 +25140,6 @@ - -
@@ -24806,8 +25163,6 @@ - -
@@ -24836,11 +25191,9 @@ M C M - U - -
- Hanging Protocol Definition - - - - - - - - - - - - - - - M - - - - -
- Hanging Protocol Environment - - - - - - - - - - - - - - - M - - - - -
- Hanging Protocol Display - - - - - - - - - - - - - - - M - - - -
@@ -24973,8 +25249,6 @@ - - M M - M - M - M - M - RT Rad Set Del Inst + RT Rad Set Del Inst - RT Treat Prep + RT Treat Prep
- M + M - M + M
- U + U - U + U
- M + M - M + M
- U + U - U + U
- U + U - U + U
- M + M - M + M
- U + U - U + U
- M + M - M + M
- M + M - M + M
- M + M - M + M
Synchronization - M + M - M + M
- RT Radiation Set Delivery Instruction + RT Radiation Set Delivery Instruction @@ -26859,13 +27127,13 @@ - M + M
- RT Treatment Preparation + RT Treatment Preparation @@ -26880,7 +27148,7 @@ - M + M
- M + M - M + M
- M + M - M + M
- M + M - M + M
Timezone
Timezone
Manufacturing 3D Model
ICC Profile
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Composite Information Object Modules Overview – Non-Patient Related Information
+ + IODs + + + Modules + + + Hanging Protocol + + Color Palette + + Inventory +
+ Equipment + + + + M +
+ Hanging Protocol Definition + + M + + +
+ Hanging Protocol Environment + + M + + +
+ Hanging Protocol Display + + M + + +
+ Palette Color LUT + + + M + +
+ ICC Profile + + + M + +
+ Color Palette Definition + + + M + +
+ Inventory + + + + M +
+ SOP Common + + M + + M + + M +
@@ -31879,6 +32268,22 @@ M
+ Acquisition + + General Acquisition + + + + + + M +
Image @@ -32054,7 +32459,7 @@
- The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004.
@@ -32236,6 +32641,22 @@ M
+ Acquisition + + General Acquisition + + + + + + M +
Image @@ -32592,6 +33013,22 @@ M
+ Acquisition + + General Acquisition + + + + + + M +
Image @@ -32950,6 +33387,22 @@ M
+ Acquisition + + General Acquisition + + + + + + M +
Image @@ -33256,7 +33709,7 @@
- The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004.
Acquisition Context Module @@ -33448,6 +33901,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -33636,12 +34105,12 @@ - The was previously included in this IOD, but has been retired. See PS3.3-2003. + The was previously included in this IOD, but has been retired. See PS3.3-2003.
Mutually Exclusive IEs - A Curve IE was previously included in this IOD that was mutually exclusive with the Image IE, but has been retired. See PS3.3-2004. + A Curve IE was previously included in this IOD that was mutually exclusive with the Image IE, but has been retired. See PS3.3-2004.
@@ -33842,6 +34311,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -34095,12 +34580,12 @@ - The was previously included in this IOD, but has been retired. See PS3.3-2003. + The was previously included in this IOD, but has been retired. See PS3.3-2003.
Mutually Exclusive IEs - A Curve IE was previously included in this IOD that was mutually exclusive with the Image IE, but has been retired. See PS3.3-2004. + A Curve IE was previously included in this IOD that was mutually exclusive with the Image IE, but has been retired. See PS3.3-2004.
@@ -34326,12 +34811,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -34652,12 +35153,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -35065,12 +35582,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -35591,12 +36124,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -36108,12 +36657,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -36433,23 +36998,23 @@
Standalone Overlay IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Standalone Curve IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Basic Study Descriptor IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Standalone Modality LUT IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Standalone VOI LUT IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
X-Ray Angiographic Image IOD @@ -36631,6 +37196,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -36963,7 +37544,7 @@ - The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004.
@@ -37153,6 +37734,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -37498,7 +38095,7 @@ - The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004.
@@ -37667,6 +38264,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -37863,7 +38476,7 @@ The has been included to allow the possibility of conversion between portal image pixel values and dose transmitted through the Patient. The has been included to allow the possibility of translation between stored pixel values (after the Modality LUT has been applied if specified) and display levels. - The and were previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The and were previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. The contains information describing the equipment used to acquire or generate the RT Image (such as a portal imager, conventional simulator or treatment planning system). However, the equipment Attributes in the describe the equipment on which the treatment has been or will be given, typically an electron accelerator. @@ -38263,7 +38876,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. @@ -38533,7 +39146,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. Previously the was not included (see PS3.3-2014b). Historically, more than one Frame of Reference could be referenced within the 's Referenced Frame of Reference Sequence (3006,0010), in which case the would not have been present. @@ -38543,7 +39156,7 @@
RT Structure Set IOD Content Constraints - For Purpose of Reference Code Sequence (0040,A170) within Source Instance Sequence (0042,0013) in the General Reference Module D shall be used. + For Purpose of Reference Code Sequence (0040,A170) within Source Instance Sequence (0042,0013) in the D shall be used.
@@ -38862,10 +39475,10 @@ - Retired. See PS3.3-2011. + Retired. See PS3.3-2011. - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. @@ -39119,6 +39732,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -39289,19 +39918,19 @@
Standalone PET Curve IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Stored Print IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Hardcopy Grayscale Image IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Hardcopy Color Image IOD - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Digital X-Ray Image IOD @@ -39503,6 +40132,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -39843,7 +40488,7 @@ The Attributes and behavior are further specialized in the . - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. @@ -40053,6 +40698,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -40387,7 +41048,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -40595,6 +41256,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -40929,7 +41606,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -41227,7 +41904,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004.
@@ -41516,7 +42193,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. @@ -41740,7 +42417,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2004. + The was previously included in this IOD but has been retired. See PS3.3-2004. @@ -41784,7 +42461,7 @@ Several distinct diagnostic or therapeutic processes might occur during an endoscopic procedure. For example: Endoscopic examination of duodenal mucosa, biopsy, lavage, or biliary stone removal. - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. @@ -41929,12 +42606,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -42097,7 +42790,7 @@ - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -42245,12 +42938,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -42426,13 +43135,13 @@ - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. - The Frame of Reference IE was previously (incorrectly) identified as not used in this IOD, although the was specified as Mandatory. See PS3.3-2009. + The Frame of Reference IE was previously (incorrectly) identified as not used in this IOD, although the was specified as Mandatory. See PS3.3-2009. @@ -42593,12 +43302,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -42787,7 +43512,7 @@ - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -42948,12 +43673,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -43162,7 +43903,7 @@ The has not been included because the selection of relevant sub-sequence(s) is usually made in a second workflow step and stored into separate Key Object Selection Documents. - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. @@ -43307,12 +44048,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -43494,7 +44251,7 @@ Image Related Data Encoding The , , and shall not be present. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
Anatomic Region Sequence @@ -43521,7 +44278,7 @@ The has not been included because the selection of relevant sub-sequence(s) is usually made in a second step and stored into separate Key Object Selection Documents. - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -43669,12 +44426,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -43853,7 +44626,7 @@ Image Related Data Encoding The , , and shall not be present. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
@@ -43876,7 +44649,7 @@ The has not been included because the selection of relevant sub-sequence(s) is usually made in a second step and stored into separate Key Object Selection Documents. - The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. + The Curve entity was previously include in the list of entities that are not used, but has been retired from DICOM. It is still not used in this IOD. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -44040,12 +44813,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -44224,7 +45013,7 @@ Image Related Data Encoding The , , and shall not be present. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. @@ -44233,9 +45022,12 @@ VL Whole Slide Microscopy Image IOD
VL Whole Slide Microscopy Image IOD Description - The VL Whole Slide Microscopy Image IOD specifies the Attributes of a multi-frame visible light whole slide microscopy image encoded as a tiled decomposition. Each frame encodes a single tile within a three-dimensional imaged volume at a uniform resolution. + The VL Whole Slide Microscopy Image IOD specifies the Attributes of a multi-frame visible light whole slide microscopy image divided into a set of tiles. + Each frame encodes a single tile within a three-dimensional imaged volume, with all tiles at a uniform resolution (same value for Pixel Spacing (0028,0030)). + The image may be one layer of a Multi-Resolution Pyramid. - An entire set of tiles for an acquisition may be encoded in the frames of a single SOP Instance, in multiple SOP Instances of a single concatenation, or in multiple SOP Instances in a Series (with or without concatenations). E.g., a single SOP Instance may contain an entire low resolution image as a single tile (single frame), or a single SOP Instance may contain an entire high resolution, multi-focal depth, multi-spectral acquisition (multiple frames). + An entire set of tiles for a single layer of an Acquisition may be encoded in the frames of a single SOP Instance, in multiple SOP Instances of a single concatenation, or in multiple SOP Instances in a Series (with or without concatenations). + E.g., a single SOP Instance may contain an entire low resolution image as a single tile (single frame), or a single SOP Instance may contain an entire high resolution, multi-focal depth, multi-spectral Acquisition (multiple frames).
@@ -44424,12 +45216,44 @@ - - Image + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Multi-Resolution Pyramid + + + Multi-Resolution Pyramid + + + + + - General Image + U - Shall be present only if Image Type Value 3 is VOLUME or THUMBNAIL. + + + + Image + + + General Image + @@ -44452,6 +45276,19 @@ U + + + Microscope Slide Layer Tile Organization + + + + + + + + M + + Image Pixel @@ -44598,7 +45435,7 @@ - The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2021c. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2021c.
VL Whole Slide Microscopy Image IOD Content Constraints @@ -44983,12 +45820,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -45151,7 +46004,7 @@ Modality The value of Modality (0008,0060) shall be ES. - The use of a single value for Modality recognizes the fact that the same acquisition equipment is often used for different purposes (e.g., laparoscopy and colonoscopy). This means that Modality is not useful to distinguish one type of endoscopy from another when browsing a collection of studies. Therefore, the use of Procedure Code Sequence (0008,1032) and Anatomic Region Sequence (0008,2218) in the Image Instances and in the query response is recommended, though gathering sufficient information to populate these attributes in an unscheduled workflow environment (i.e.; in the absence of Modality Worklist) may require operator intervention. + The use of a single value for Modality recognizes the fact that the same acquisition equipment is often used for different purposes (e.g., laparoscopy and colonoscopy). This means that Modality is not useful to distinguish one type of endoscopy from another when browsing a collection of studies. Therefore, the use of Procedure Code Sequence (0008,1032) and Anatomic Region Sequence (0008,2218) in the Image Instances and in the query response is recommended, though gathering sufficient information to populate these Attributes in an unscheduled workflow environment (i.e.; in the absence of Modality Worklist) may require operator intervention.
@@ -45439,12 +46292,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -45870,12 +46739,28 @@ - - Image - - - General Image - + + Acquisition + + + General Acquisition + + + + + + + + M + + + + + Image + + + General Image + @@ -46014,7 +46899,7 @@
Frame of Reference Module - The Frame of Reference Module may be used if multiple successive images are acquired during a single acquisition. + The may be used if multiple successive images are acquired during a single acquisition. All images in a Series that share the same Frame of Reference UID will be spatially related to each other.
@@ -46027,11 +46912,11 @@
VL Photographic Equipment Module - The may be used to encode Lens attributes. Some dermoscopes have interchangeable lenses. + The may be used to encode Lens Attributes. Some dermoscopes have interchangeable lenses.
VL Photographic Acquisition Module - The Digital Zoom Ratio (0016,0044) attribute may be used to encode the digital zoom ratio of the dermoscope when the image was acquired. + The Digital Zoom Ratio (0016,0044) Attribute may be used to encode the digital zoom ratio of the dermoscope when the image was acquired.
ICC Profile Module @@ -46870,7 +47755,7 @@ - In the Color Softcopy Presentation State IOD, the specializes some Attributes of the , and the specializes some Attributes of the and . + In the Color Softcopy Presentation State IOD, the specializes some Attributes of the , and the specializes some Attributes of the and .
@@ -48306,7 +49191,7 @@ - In the XA/XRF Grayscale Softcopy Presentation State IOD, the specializes some Attributes of the , the specializes some Attributes of the , and the specializes some Attributes of the and . + In the XA/XRF Grayscale Softcopy Presentation State IOD, the specializes some Attributes of the , the specializes some Attributes of the , and the specializes some Attributes of the and . @@ -48684,7 +49569,7 @@ Waveform Information Object Definitions
Waveform IOD Entity-Relationship Model - These IODs use the E-R Model in Section , with only the Waveform IE below the Series IE. + These IODs use the E-R Model in , with only the Waveform IE below the Series IE.
Basic Voice Audio Waveform IOD @@ -53598,7 +54483,7 @@ - Document + SR Document SR Document General @@ -53641,7 +54526,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
Basic Text SR IOD Content Constraints @@ -54006,7 +54891,7 @@ - Document + SR Document SR Document General @@ -54049,7 +54934,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
Enhanced SR IOD Content Constraints @@ -54453,7 +55338,7 @@ - Document + SR Document SR Document General @@ -54496,7 +55381,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
Comprehensive SR IOD Content Constraints @@ -54893,7 +55778,7 @@ - Document + SR Document Key Object Document @@ -54936,7 +55821,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
Key Object Selection Document IOD Content Constraints @@ -55213,7 +56098,7 @@ - Document + SR Document SR Document General @@ -55256,7 +56141,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
Mammography CAD SR IOD Content Constraints @@ -55633,7 +56518,7 @@ - Document + SR Document SR Document General @@ -55676,7 +56561,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
Chest CAD SR IOD Content Constraints @@ -55811,7 +56696,8 @@ HAS OBS CONTEXT - TEXT, CODE, NUM, DATE, TIME, PNAME, UIDREF, COMPOSITE1 + TEXT, CODE, NUM, DATE, TIME, PNAME, UIDREF, COMPOSITE1 + @@ -55844,7 +56730,8 @@ HAS CONCEPT MOD - TEXT, CODE2 + TEXT, CODE2 + @@ -55888,7 +56775,8 @@ SELECTED FROM - SCOORD, IMAGE1, WAVEFORM1 + SCOORD, IMAGE1, WAVEFORM1 + @@ -56064,7 +56952,7 @@ - Document + SR Document SR Document General @@ -56490,7 +57378,7 @@ - Document + SR Document SR Document General @@ -56889,7 +57777,7 @@ - Document + SR Document SR Document General @@ -57173,7 +58061,7 @@ - Document + SR Document SR Document General @@ -57347,7 +58235,8 @@ HAS OBS CONTEXT - TEXT, CODE, NUM, DATE, TIME, PNAME, UIDREF, COMPOSITE1 + TEXT, CODE, NUM, DATE, TIME, PNAME, UIDREF, COMPOSITE1 + @@ -57380,7 +58269,8 @@ HAS CONCEPT MOD - TEXT, CODE2 + TEXT, CODE2 + @@ -57413,7 +58303,8 @@ SELECTED FROM - IMAGE1 + IMAGE1 + @@ -57424,7 +58315,8 @@ SELECTED FROM - SCOORD, SCOORD3D, IMAGE1, WAVEFORM1 + SCOORD, SCOORD3D, IMAGE1, WAVEFORM1 + @@ -57607,7 +58499,7 @@ - Document + SR Document SR Document General @@ -57959,7 +58851,7 @@ - Document + SR Document SR Document General @@ -58319,7 +59211,7 @@ - Document + SR Document SR Document General @@ -58794,7 +59686,7 @@ - Document + SR Document SR Document General @@ -59174,7 +60066,7 @@ - Document + SR Document SR Document General @@ -59453,7 +60345,7 @@ - Document + SR Document SR Document General @@ -59499,7 +60391,7 @@ Acquisition Context SR IOD Content Constraints
Value Type - Value Type (0040,A040) in Content Sequence (0040,A730) of the SR Document Content Module is constrained to the following Enumerated Values (see for Value Type definitions): + Value Type (0040,A040) in Content Sequence (0040,A730) of the is constrained to the following Enumerated Values (see for Value Type definitions): Enumerated Values: @@ -59568,7 +60460,7 @@ Relationship Constraints Relationships between Content Items in the content of this IOD shall be conveyed in the by-value mode. See for Relationship Type definitions. - Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the SR Document Content Module. + Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the . specifies the relationship constraints of this IOD. @@ -59844,7 +60736,7 @@ - Document + SR Document SR Document General @@ -59907,7 +60799,7 @@
Value Type - Value Type (0040,A040) in Content Sequence (0040,A730) of the SR Document Content Module is constrained to the following Enumerated Values (see for Value Type definitions): + Value Type (0040,A040) in Content Sequence (0040,A730) of the is constrained to the following Enumerated Values (see for Value Type definitions): Enumerated Values: @@ -59982,7 +60874,7 @@ Relationship Constraints Relationships between Content Items in the content of this IOD shall be conveyed in the by-value mode. See for Relationship Type definitions. - Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the SR Document Content Module. + Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the . specifies the relationship constraints of this IOD. @@ -60105,10 +60997,12 @@
Patient Radiation Dose SR IOD Entity-Relationship Model - This IOD uses the E-R Model in , with only the SR Document IE below the Series IE. specifies the Modules of the Patient Radiation Dose SR IOD. + This IOD uses the E-R Model in , with only the SR Document IE below the Series IE.
Patient Radiation Dose SR IOD Module Table + + specifies the Modules of the Patient Radiation Dose SR IOD. @@ -60255,7 +61149,7 @@ + + + + + +
Patient Radiation Dose Structured Report IOD Modules
- Document + SR Document SR Document General @@ -60486,6 +61380,8 @@
Planned Imaging Agent Administration SR IOD Module Table + + specifies the Modules of the Planned Imaging Agent Administration SR IOD. @@ -60618,7 +61514,7 @@ + + + + + +
Planned Imaging Agent Administration SR IOD Modules
- Document + SR Document SR Document General @@ -60848,6 +61744,8 @@
Performed Imaging Agent Administration SR IOD Module Table + + specifies the Modules of the Performed Imaging Agent Administration SR IOD. @@ -60994,7 +61892,7 @@
Performed Imaging Agent Administration SR IOD Modules
- Document + SR Document SR Document General @@ -61399,7 +62297,7 @@
- Frame Of Reference + Frame of Reference Synchronization @@ -61415,7 +62313,7 @@
- Document + SR Document Key Object Document @@ -61461,7 +62359,7 @@ Rendition Selection Document IOD Content Constraints
Value Type - Value Type (0040,A040) in Content Sequence (0040,A730) of the SR Document Content Module is constrained to the following Enumerated Values (see for Value Type definitions): + Value Type (0040,A040) in Content Sequence (0040,A730) of the is constrained to the following Enumerated Values (see for Value Type definitions): Enumerated Values: @@ -61519,7 +62417,7 @@ Relationship Constraints Relationships between Content Items in the content of this IOD shall be conveyed in the by-value mode. See for Relationship Type definitions. - Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the SR Document Content Module. + Relationships by-reference are forbidden. Therefore, Referenced Content Item Identifier (0040,DB73) is not present in any of the Content Items within the . specifies the relationship constraints of this IOD. @@ -61591,10 +62489,12 @@
Enhanced X-Ray Radiation Dose SR IOD Entity-Relationship Model - This IOD uses the E-R Model in , with only the SR Document IE below the Series IE. specifies the Modules of the Enhanced X-Ray Radiation Dose SR IOD. + This IOD uses the E-R Model in , with only the SR Document IE below the Series IE.
Enhanced X-Ray Radiation Dose SR IOD Module Table + + specifies the Modules of the Enhanced X-Ray Radiation Dose SR IOD. @@ -61741,7 +62641,7 @@
Enhanced X-Ray Radiation Dose Structured Report IOD Modules
- Document + SR Document SR Document General @@ -62436,7 +63336,7 @@ Grayscale Softcopy Presentation State Storage Instances that are generated during acquisition may be referenced from the Image SOP Instance by using the Referenced Grayscale Presentation State Sequence in the invoked from the . See . - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -64233,7 +65133,7 @@
- Enhanced Computed Tomography Image IOD + Enhanced CT Image Information Object Definitions
Enhanced CT Image IOD
@@ -64662,7 +65562,7 @@ Grayscale Softcopy Presentation State Storage Instances that are generated during acquisition may be referenced from the Image SOP Instance by using the Referenced Grayscale Presentation State Sequence in the . See . - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -65289,7 +66189,7 @@
- The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -65766,7 +66666,7 @@
- The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -65781,7 +66681,7 @@ Ophthalmic Photography 8 Bit Image IOD Entity-Relationship Model This IOD uses the E-R Model in , with only the Image IE below the Series IE. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
@@ -65950,6 +66850,22 @@ M
+ Acquisition + + General Acquisition + + + + + + M +
Image @@ -66165,7 +67081,7 @@
- The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -66192,7 +67108,7 @@ Ophthalmic Photography 16 Bit Image IOD Entity-Relationship Model This IOD uses the E-R Model in , with only the Image IE below the Series IE. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
@@ -66361,6 +67277,22 @@ M
+ Acquisition + + General Acquisition + + + + + + M +
Image @@ -66576,7 +67508,7 @@
- The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -66797,7 +67729,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -67100,7 +68032,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -67536,7 +68468,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -68051,7 +68983,7 @@ The VOI LUT function is provided by a Frame VOI LUT Functional Group. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -68970,7 +69902,7 @@ The VOI LUT function is provided by a Frame VOI LUT Functional Group. - The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The was previously include in the list of Modules that shall not be present, but has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. The was previously included in this IOD but has been retired, and its functionality replaced by the . See PS3.3-2008. @@ -70121,7 +71053,39 @@ - + + Acquisition + + + General Acquisition + + + + + + + + U + + + + + Multi-Resolution Pyramid + + + Multi-Resolution Pyramid + + + + + + + + U + + + + Image @@ -70149,6 +71113,19 @@ U + + + Microscope Slide Layer Tile Organization + + + + + + + + C - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. + + Image Pixel @@ -70265,7 +71242,7 @@ The shall not be present. The shall not be present. Pixel Padding Value (0028,0120) shall not be present. - For Purpose of Reference Code Sequence (0040,A170) within Source Instance Sequence (0042,0013) in the General Reference Module D shall be used. + For Purpose of Reference Code Sequence (0040,A170) within Source Instance Sequence (0042,0013) in the D shall be used.
Segmentation Functional Groups @@ -70388,9 +71365,9 @@ Segmentation Functional Groups Description When a Frame of Reference UID is present the segment shall be specified within that coordinate system, using the Pixel Measures and either the Plane Position (Patient) and Plane Orientation (Patient), or the Plane Position (Slide) Functional Groups. Since this defines the spatial relationship of the segment, the size of the segmentation frames need not be the same size, or resolution, as the image data used to generate the segment data. The Derivation Image Functional Group may also be present, to specify on which images the segmentation was actually performed (since there may be others in the same Frame of Reference that are spatially co-located, but were not used to perform the segmentation). If the Frame of Reference UID is not present, each pixel of the segmentation shall correspond to a pixel in a referenced image, using the Derivation Image Functional Group. Hence, the rows and columns of each referenced image will match the segmentation image. If both the Frame of Reference UID and the Derivation Image Functional Group are present, the segmentation and referenced image pixels need not correspond. - The value of Purpose of Reference Code Sequence (0040,A170) in the Derivation Image Functional Group Macro shall be (121322, DCM, "Source Image for Image Processing Operation"). The value of Derivation Code Sequence (0008,9215) shall be (113076, DCM, "Segmentation"). + The value of Purpose of Reference Code Sequence (0040,A170) in the shall be (121322, DCM, "Source Image for Image Processing Operation"). The value of Derivation Code Sequence (0008,9215) shall be (113076, DCM, "Segmentation"). - Non-image source Instances used during segmentation, such as real world value maps, can be described in the top level Data Set in the Source Instance Sequence (0042,0013) of the General Reference Module and are implied to have been used for the derivation of all frames. I.e., there is no mechanism for selectively specifying on a per-frame basis which non-Image Instances were used. Real World Value Map Instances already contain a means of selectively applying different scale factors to different frames. + Non-image source Instances used during segmentation, such as Real World Value maps, can be described in the top level Data Set in the Source Instance Sequence (0042,0013) of the and are implied to have been used for the derivation of all frames. I.e., there is no mechanism for selectively specifying on a per-frame basis which non-Image Instances were used. Real World Value Map Instances already contain a means of selectively applying different scale factors to different frames.
@@ -71414,7 +72391,7 @@ The VOI LUT function is provided by a Frame VOI LUT Functional Group. - The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. @@ -72071,7 +73048,7 @@ The VOI LUT function is provided by a Frame VOI LUT Functional Group. - The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. + The was previously included in the Image IE for this IOD but has been retired. See PS3.3-2004. @@ -73912,7 +74889,7 @@
Surface Segmentation IOD Content Constraints - For Purpose of Reference Code Sequence (0040,A170) within Source Instance Sequence (0042,0013) in the General Reference Module D shall be used. + For Purpose of Reference Code Sequence (0040,A170) within Source Instance Sequence (0042,0013) in the D shall be used.
@@ -74037,9 +75014,9 @@ - The 3D volume data (the diagonally shaded box in ) contains a Cartesian volume or two or more temporally related Cartesian volumes. 3D volume data is exchanged using the Enhanced US Volume SOP Class, and are suitable for subsequent Multi-Planar Reconstruction and rendering operations. Within each Enhanced US Volume Instance, each Cartesian volume consists of a set of parallel planes, and each plane consists of one or more frames each of a single data type. All Cartesian volumes have the same spacing between adjacent planes. + The 3D volume data (shown in ) contains a Cartesian volume or two or more temporally related Cartesian volumes. 3D volume data is exchanged using the Enhanced US Volume SOP Class, and are suitable for subsequent Multi-Planar Reconstruction and rendering operations. Within each Enhanced US Volume Instance, each Cartesian volume consists of a set of parallel planes, and each plane consists of one or more frames each of a single data type. All Cartesian volumes have the same spacing between adjacent planes. Most acquisition devices construct the Cartesian volume by resampling data from a different acquisition geometry. The method of generation of the Cartesian volume, its relationship to spatially-related 2D frames (whether the volume was created from spatially-related frames, or spatially-related frames extracted from the Cartesian volume), and the algorithms used for Multi-Planar Reconstruction and rendering operations are outside the scope of this Standard. - The 2D image types represent collections of frames that are derived from the volume data, namely 3D rendered views (projections), separate Multi-Planar Reconstructed (MPR) views, or collections of spatially-related source frames, either parallel or oblique (the cross-hatched boxes in ). The Ultrasound Image and Ultrasound Multi-frame Image IODs are used to represent these derived images. See for the Ultrasound Image IOD description or for the Ultrasound Multi-frame Image IOD description. + The 2D image types represent collections of frames that are derived from the volume data, namely 3D rendered views (projections), separate Multi-Planar Reconstructed (MPR) views, or collections of spatially-related source frames, either parallel or oblique (shown in ). The Ultrasound Image and Ultrasound Multi-frame Image IODs are used to represent these derived images. See for the Ultrasound Image IOD description or for the Ultrasound Multi-frame Image IOD description. See for an informative discussion on the use of these objects for the exchange of 3D ultrasound volume data. @@ -74255,6 +75232,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -77695,7 +78688,7 @@ - C - Required if Intravascular Acquisition (0018,3100) equals MEASURED or Presentation Intent Type (0008,0068) equals FORPRESENTATION. + C - Required if Intravascular Acquisition (0018,3100) equals MEASURED or Presentation Intent Type (0008,0068) equals FOR PRESENTATION. @@ -77898,6 +78891,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -78975,6 +79984,9 @@
Legacy Converted Enhanced CT Image IOD Content Constraints + + The Photometric Interpretation (0028,0004) defined in is MONOCHROME2. If the value of Photometric Interpretation in the source single frame images is MONOCHROME1, which is permitted by , lossless conversion of the PixelData to MONOCHROME2 and updating of any related Attributes is necessary. + The , , , and shall not be used in a Standard Extended SOP Class of the Legacy Converted Enhanced CT Image. In order to annotate images, whether during acquisition or subsequently, SOP Instances of the Grayscale Softcopy Presentation State Storage or the Structured Report Storage SOP Classes that reference the image SOP Instance, may be used. @@ -78982,7 +79994,7 @@ No standard mechanism is provided for inclusion of annotations within the image SOP Instance itself, and implementers are discouraged from using private extensions to circumvent this restriction. Grayscale Softcopy Presentation State Storage Instances that are generated during conversion shall be referenced from the Image SOP Instance by using the Referenced Grayscale Presentation State Sequence in the . See . - The has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
@@ -79650,6 +80662,10 @@
Legacy Converted Enhanced MR Image IOD Content Constraints + The Photometric Interpretation (0028,0004) defined in shall be MONOCHROME2. + + If the value of Photometric Interpretation in the source single frame images is MONOCHROME1, which is permitted by , lossless conversion of the PixelData to MONOCHROME2 and updating of any related Attributes is necessary. + The , , , and shall not be used in a Standard Extended SOP Class of the Legacy Converted Enhanced MR Image. In order to annotate images, whether during acquisition or subsequently, SOP Instances of the Grayscale Softcopy Presentation State Storage or the Structured Report Storage SOP Classes that reference the image SOP Instance, may be used. @@ -79657,7 +80673,7 @@ No standard mechanism is provided for inclusion of annotations within the image SOP Instance itself, and implementers are discouraged from using private extensions to circumvent this restriction. Grayscale Softcopy Presentation State Storage Instances that are generated during conversion shall be referenced from the Image SOP Instance by using the Referenced Grayscale Presentation State Sequence in the . See . - The has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
@@ -80286,6 +81302,9 @@
Legacy Converted Enhanced PET Image IOD Content Constraints + + The value of Photometric Interpretation (0028,0004) defined in and is MONOCHROME2. So no conversion of the Pixel Data from MONOCHROME1 to MONOCHROME2 is necessary. + The , , , and shall not be used in a Standard Extended SOP Class of the Legacy Converted Enhanced PET Image. In order to annotate images, whether during acquisition or subsequently, SOP Instances of the Grayscale Softcopy Presentation State Storage or the Structured Report Storage SOP Classes that reference the image SOP Instance, may be used. @@ -80293,7 +81312,7 @@ No standard mechanism is provided for inclusion of annotations within the image SOP Instance itself, and implementers are discouraged from using private extensions to circumvent this restriction. Grayscale Softcopy Presentation State Storage Instances that are generated during conversion shall be referenced from the Image SOP Instance by using the Referenced Grayscale Presentation State Sequence in the . See . - The has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004. + The has been retired from DICOM. It is still not permitted to be present. See PS3.3-2004.
@@ -80559,7 +81578,8 @@ Corneal Topography Map IOD
Corneal Topography Map IOD Description - The Corneal Topography Map IOD is generated by ophthalmic corneal topography mapping devices, such as reflection-based topography and elevation-based tomography instruments to generate curvature and/or elevation measurements of corneal anterior and posterior surfaces that are presented topographically using a monochromatic image and a pseudo-color map. + The Corneal Topography Map IOD is generated by ophthalmic corneal topography mapping devices, such as reflection-based topography and elevation-based tomography instruments to generate curvature and/or elevation measurements of corneal anterior and posterior surfaces that are presented topographically using a monochromatic image and a pseudo-color map. + The pseudo-colored map may be superimposed over the source image for display.
Corneal Topography Map IOD Entity-Relationship Model @@ -80746,6 +81766,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -80889,6 +81925,29 @@ Prohibited Modules The , and shall not be used in a Standard Extended SOP Class of the Corneal Topography Map.
+
+ Pixel Padding, Real World Value Mapping and Palette Color LUT + When a Corneal Topography Map is superimposed on the corresponding source image, + the background color of the map that is specified by the Pixel Padding Value (0028,0120) Attribute may be rendered “transparently” so that parts of the underlying source image become visible + (see ). + To support this rendering, no mapping shall be defined in the Real World Value Mapping Sequence (0040,9096) for the value of the Pixel Padding Value (0028,0120) Attribute. + The Pixel Padding Range Limit (0028,0121) Attribute shall not be used for this IOD. + + + + In order to facilitate the rendering and to preserve backward compatibility with existing implementations, + it is suggested that a value of 0 for the Pixel Padding Value (0028,0120) Attribute be used, + and to explicitly define this background color in the Palette Color Lookup Table as black + (i.e. the corresponding entry in Red, Green and Blue Palette Color Lookup Table Data (0028,1201-1203) is set to 0). + + + There is no reason to specify a range of Pixel Padding Values, + since the Corneal Topography Map is the result of a calculation and the background color can, therefore, be specified as a distinct value. + + + + +
@@ -81648,7 +82707,7 @@ Parametric Map IOD
Parametric Map IOD Description - The Parametric Map Information Object Definition (IOD) specifies a multi-frame image representing pixels with real world values. Parametric Maps are either integer or floating point. + The Parametric Map Information Object Definition (IOD) specifies a multi-frame image representing pixels with Real World Values. Parametric Maps are either integer or floating point. The Parametric Map IOD does not include the full set of acquisition parameters of any acquired images from which they were derived, e.g., cardiac phase. An application rendering or processing the Parametric Map may need to access the source images for such information. The Parametric Map IOD requires the presence of VOI LUT (window) information with the intent that at a minimum the image be renderable without special processing. The output space is defined as P-Values to achieve consistency. @@ -81873,7 +82932,39 @@ - + + Acquisition + + + General Acquisition + + + + + + + + U + + + + + Multi-Resolution Pyramid + + + Multi-Resolution Pyramid + + + + + + + + U + + + + Image @@ -81901,6 +82992,19 @@ U + + + Microscope Slide Layer Tile Organization + + + + + + + + C - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. + + Image Pixel @@ -82381,7 +83485,7 @@
Parametric Map Functional Groups Description - For the Derivation Image Functional Group Macro: + For the : For Purpose of Reference Code Sequence (0040,A170) B may be used. @@ -82611,6 +83715,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -83123,6 +84243,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -84383,7 +85519,7 @@
Volumetric Presentation State Reference Coordinate System - All SOP Instances referenced in the Volumetric Presentation State Relationship Module shall be registered to the Volumetric Presentation State Reference Coordinate System. See . + All SOP Instances referenced in the shall be registered to the Volumetric Presentation State Reference Coordinate System. See .
@@ -84851,7 +85987,7 @@
Volumetric Presentation State Reference Coordinate System - All SOP Instances referenced in the Volumetric Presentation State Relationship Module shall be registered to the Volumetric Presentation State Reference Coordinate System. See C.11.23.3. + All SOP Instances referenced in the shall be registered to the Volumetric Presentation State Reference Coordinate System. See C.11.23.3.
@@ -86314,6 +87450,22 @@ M + + + Acquisition + + + General Acquisition + + + + + + + + M + + Image @@ -86884,10 +88036,10 @@
Ophthalmic Optical Coherence Tomography B-scan Volume Analysis IOD Content Constraints - This source for an Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance is one or more multi-frame Ophthalmic Tomography SOP Instance(s). The correlation is encoded at the Frame Level and conveyed in the Derivation Image Macro (see for examples). + This source for an Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance is one or more multi-frame Ophthalmic Tomography SOP Instance(s). The correlation is encoded at the Frame Level and conveyed in the (see for examples).
Derivation Image Functional Group - The following constraints to the Derivation Image Macro shall apply: + The following constraints to the shall apply: Derivation Image Sequence (0008,9124) shall be Type 1 @@ -87166,7 +88318,7 @@ - The was previously included in this IOD but has been retired. See PS3.3-2008. + The was previously included in this IOD but has been retired. See PS3.3-2008.
@@ -87180,7 +88332,7 @@ The original STL specification in 1989 required that all 3 vertex coordinates of each triangle be located in the positive quadrant. The creators of the standard (3D Systems) later relaxed this restriction and negative coordinates were allowed. It is common practice in medical usage for STL models to align with the coordinate system of the source DICOM data, which will often result in negative vertex coordinates. - The Frame Of Reference UID (0020,0052) is an identifier for the origin and axes implicit in the STL data. + The Frame of Reference UID (0020,0052) is an identifier for the origin and axes implicit in the STL data. @@ -87468,7 +88620,7 @@ Encapsulated Document The Encapsulated Document (0042,0011) Attribute shall contain an ASCII OBJ byte stream . - The Frame Of Reference UID (0020,0052) is an identifier for the origin and axes implicit in the OBJ data. + The Frame of Reference UID (0020,0052) is an identifier for the origin and axes implicit in the OBJ data.
@@ -90474,7 +91626,7 @@
RT Delivery Device Common Module - The Equipment Frame of Reference UID (300A,0675) shall have the value used by the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the RT Radiation Record Common Module. + The Equipment Frame of Reference UID (300A,0675) shall have the value used by the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the . The following code sequences shall have values from the identified CIDs: @@ -90493,7 +91645,7 @@ Radiation Dosimeter Unit Sequence (300A,0658) - Defined CID is the CID specified for the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the RT Radiation Record Common Module. + Defined CID is the CID specified for the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the . @@ -90521,7 +91673,7 @@ RT Treatment Technique Code Sequence (3010,0080) - Defined CID is the CID specified for the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the RT Radiation Record Common Module. + Defined CID is the CID specified for the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the . @@ -90529,7 +91681,7 @@ Treatment Machine Special Mode Sequence (300A,0635) - Defined CID is the CID specified for the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the RT Radiation Record Common Module. + Defined CID is the CID specified for the SOP Instance referenced in the Referenced RT Instance Sequence (300A,0631) of the . @@ -91821,11 +92973,11 @@ RT Radiation Set Delivery Instruction IOD
RT Radiation Set Delivery Instruction IOD Description - The RT Radiation Set Delivery Instruction IOD contains all the parameters needed to deliver a single RT Treatment Fraction of one RT Radiation Set in the scope of one RT Treatment Session. It handles either the delivery of the complete fraction of the RT Radiation Set or the continuation of a formerly treated fraction which was interrupted and not completely delivered. + The RT Radiation Set Delivery Instruction IOD contains all the parameters needed to deliver a single RT Treatment Fraction of one RT Radiation Set in the scope of one RT Treatment Session. It handles either the delivery of the complete fraction of the RT Radiation Set or the continuation of a formerly treated fraction which was interrupted and not completely delivered.
RT Radiation Set Delivery Instruction IOD Entity-Relationship Model - See . + See .
RT Radiation Set Delivery Instruction IOD Module Table @@ -91834,228 +92986,228 @@ - IE + IE - Module + Module - Reference + Reference - Usage + Usage - Patient + Patient - Patient + Patient - + - M + M - Clinical Trial Subject + Clinical Trial Subject - + - U + U - Study + Study - General Study + General Study - + - M + M - Patient Study + Patient Study - + - U + U - Clinical Trial Study + Clinical Trial Study - + - U + U - Series + Series - General Series + General Series - + - M + M - Clinical Trial Series + Clinical Trial Series - + - U + U - Enhanced RT Series + Enhanced RT Series - + - M + M - Equipment + Equipment - General Equipment + General Equipment - + - M + M - Enhanced General Equipment + Enhanced General Equipment - + - M + M - Plan + Plan - General Reference + General Reference - + - M + M - RT Radiation Set Delivery Instruction + RT Radiation Set Delivery Instruction - + - M + M - SOP Common + SOP Common - + - M + M - Common Instance Reference + Common Instance Reference - + - M + M - Radiotherapy Common Instance + Radiotherapy Common Instance - + - M + M @@ -92065,7 +93217,7 @@ RT Radiation Set Delivery Instruction IOD Constraints
Modality Attribute - The value of Modality (0008,0060) shall be PLAN. + The value of Modality (0008,0060) shall be PLAN.
@@ -92074,11 +93226,11 @@ RT Treatment Preparation IOD
RT Treatment Preparation IOD Description - The RT Treatment Preparation IOD describes the setup of the patient in preparation for delivery of the therapeutic radiation within an RT Treatment Session. It may include an initial patient’s position in preparation for treatment delivery, the treatment setup positions, or setup procedures along with the use of any fixation or shielding devices. + The RT Treatment Preparation IOD describes the setup of the patient in preparation for delivery of the therapeutic radiation within an RT Treatment Session. It may include an initial patient’s position in preparation for treatment delivery, the treatment setup positions, or setup procedures along with the use of any fixation or shielding devices.
RT Treatment Preparation IOD Entity-Relationship Model - See . + See .
RT Treatment Preparation IOD Module Table @@ -92087,228 +93239,228 @@ - IE + IE - Module + Module - Reference + Reference - Usage + Usage - Patient + Patient - Patient + Patient - + - M + M - Clinical Trial Subject + Clinical Trial Subject - + - U + U - Study + Study - General Study + General Study - + - M + M - Patient Study + Patient Study - + - U + U - Clinical Trial Study + Clinical Trial Study - + - U + U - Series + Series - General Series + General Series - + - M + M - Clinical Trial Series + Clinical Trial Series - + - U + U - Enhanced RT Series + Enhanced RT Series - + - M + M - Equipment + Equipment - General Equipment + General Equipment - + - M + M - Enhanced General Equipment + Enhanced General Equipment - + - M + M - RT Treatment Preparation + RT Treatment Preparation - General Reference + General Reference - + - M + M - RT Treatment Preparation + RT Treatment Preparation - + - M + M - SOP Common + SOP Common - + - M + M - Common Instance Reference + Common Instance Reference - + - M + M - Radiotherapy Common Instance + Radiotherapy Common Instance - + - M + M @@ -92318,7 +93470,7 @@ RT Treatment Preparation IOD Constraints
Modality Attribute - The value of Modality (0008,0060) shall be PLAN. + The value of Modality (0008,0060) shall be PLAN.
@@ -92516,7 +93668,7 @@ - + Annotation @@ -92544,6 +93696,19 @@ U + + + Specimen + + + + + + + + U + + Common Instance Reference @@ -92574,32 +93739,125 @@
+
+ Inventory IOD +
+ Inventory IOD Description + The Inventory IOD defines an Inventory of all Studies, Series, and SOP Instances managed by a repository, or a specified subset of those Studies, Series, and SOP Instances. + It includes information about the available mechanisms to access such Studies, Series, and SOP Instances, including both DICOM and non-DICOM protocols. + The Inventory provides selected Patient, Procedure, and Imaging Service Request Attribute values for the inventoried Studies. + For implementation-specific reasons, a complete Inventory may need to be divided across multiple SOP Instances. + The Inventory IOD allows a SOP Instance to reference other SOP Instances whose content is logically included by such reference. + A complete inventory thus consists of one root SOP Instance, with a tree of references to additional SOP Instances, the content of all of which comprises the Inventory. + + See additional explanatory information in , including discussion of the use of the Repository Query SOP Class or the Inventory Creation SOP Class to produce an Inventory SOP Instance. + +
+
+ Inventory IOD Entity-Relationship Model + The Inventory IOD uses the E-R Model specified in . +
+
+ Inventory IOD Module Table + + lists the Modules that make up the Inventory IOD. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Inventory IOD Modules
+ IE + + Module + + Reference + + Usage +
+ Equipment + + General Equipment + + + + + + M +
+ Inventory + + Inventory + + + + + + M +
+ SOP Common + + + + + + M +
+ + The Attributes of the other Information Entities of the Inventory Information Model (such as Study, Series, Patient, etc.) are hierarchically encoded (within Sequence Attributes) in the , and thus do not appear as separate Modules in the IOD. + +
+
Normalized Information Object Definitions (Normative)
Patient Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Visit Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Component Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Results Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Interpretation Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Basic Film Session Information Object Definition @@ -92774,7 +94032,7 @@ - Image Box Presentation + Image Box Pixel Presentation @@ -92787,7 +94045,7 @@ - The was previously defined in DICOM. It is now retired. See PS3.3-1998. + The was previously defined in DICOM. It is now retired. See PS3.3-1998.
@@ -92954,11 +94212,15 @@
VOI LUT Box Information Object Definition (Retired) - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See +PS3.3-1998 +.
Image Overlay Box Information Object Definition (Retired) - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See +PS3.3-1998 +.
Storage Commitment Information Object Definition @@ -93018,7 +94280,7 @@
Print Queue Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Modality Performed Procedure Step Information Object Definition @@ -93104,7 +94366,7 @@ - Billing and Material Management Codes + Billing and Material Management Code @@ -93118,7 +94380,7 @@ - The has been retired. See PS3.3 2017c. + The has been retired. See PS3.3-2017c.
@@ -93149,7 +94411,7 @@ - SOP Common Information + SOP Common @@ -93179,7 +94441,7 @@
Pull Print Request Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Printer Configuration Information Object Definition @@ -93250,15 +94512,15 @@
Basic Print Image Overlay Box Information Object Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
General Purpose Scheduled Procedure Step Information Object Definition (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
General Purpose Performed Procedure Step Information Object Definition (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
Instance Availability Notification Information Object Definition @@ -93749,6 +95011,60 @@
+
+ Inventory Creation IOD +
+ Inventory Creation IOD Description + The Inventory Creation IOD describes the Attributes that may be present in an Inventory Creation Request or Response. +
+
+ Inventory Creation IOD Module Table + + + + + + + + + + + + + + + + + + + + + +
Inventory Creation IOD Modules
+ Module + + Reference + + Description +
+ Inventory Creation + + + + + + Contains parameters for initiation of inventory production +
+ SOP Common + + + + + + Contains SOP common information +
+
+
Information Module Definitions (Normative) @@ -93822,8 +95138,8 @@ The following Sections specify Modules used for Patient management.
Patient Relationship Module - - defines the Attributes that reference SOP Instances related to this SOP Class. + + specifies the Attributes of the , which reference SOP Instances related to this SOP Class. @@ -93912,8 +95228,8 @@
Patient Identification Module - - defines the Attributes relevant to identifying a Patient. + + specifies the Attributes of the , which define the Attributes relevant to identifying a Patient.
Patient Relationship Module Attributes
@@ -93938,7 +95254,7 @@ (0010,0010) @@ -94002,7 +95318,7 @@ The identifier is coded as a string regardless of the type, not as a binary value. - When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the Scheduled Procedure Step Module, if present. + When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the , if present. @@ -94081,7 +95397,7 @@ The identifier is coded as a string regardless of the type, not as a binary value. - When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the Scheduled Procedure Step Module, if present. + When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the , if present. @@ -94158,10 +95474,10 @@
Patient Identification Module Attributes
- Patient's full name + Patient's full name.
- Previously, Other Patient IDs (0010,1000) and Medical Record Locator (0010,1090) were included in this table. These Attributes have been retired. See PS3.3 2017a. + Previously, Other Patient IDs (0010,1000) and Medical Record Locator (0010,1090) were included in this table. These Attributes have been retired. See PS3.3-2017a.
- Patient Identification Module Attributes + Patient Identification Module Attribute Descriptions
Referenced Patient Photo Sequence A Patient Photo may be provided as an additional means to confirm the identity of the Patient. @@ -94172,8 +95488,8 @@
Patient Demographic Module - - defines the Attributes relevant to generally describing a Patient at a specific point in time, e.g., at the time of admission. + + specifies the Attributes of the , which generally describe the Patient at a specific point in time, e.g., at the time of admission. @@ -94231,7 +95547,7 @@ (0010,0030) @@ -94242,7 +95558,7 @@ (0010,0032) @@ -94387,7 +95703,7 @@ (0010,1020) @@ -94398,7 +95714,7 @@ (0010,1030) @@ -94434,7 +95750,7 @@ (0010,1040) @@ -94445,7 +95761,7 @@ (0010,1080) @@ -94467,7 +95783,7 @@ (0010,2150) @@ -94478,7 +95794,7 @@ (0010,2152) @@ -94489,7 +95805,7 @@ (0010,2154) @@ -94521,7 +95837,7 @@ (0010,2160) @@ -94532,7 +95848,7 @@ (0010,21F0) @@ -94543,7 +95859,7 @@ (0010,4000) @@ -94885,8 +96201,8 @@
Patient Medical Module - - defines the Attributes relevant to a Patient's medical state or history. + + specifies the Attributes of the , which describe a Patient's medical state or history.
Patient Demographic Module Attributes
- Date of birth of the named Patient + Date of birth of the named Patient.
- Time of birth of the named Patient + Time of birth of the named Patient.
- Patient's height or length in meters + Patient's height or length in meters.
- Weight of the Patient in kilograms + Weight of the Patient in kilograms.
- Legal address of the named Patient + Legal address of the named Patient.
- Military rank of Patient + Military rank of Patient.
- Country in which Patient currently resides + Country in which Patient currently resides.
- Region within Patient's country of residence + Region within Patient's country of residence.
- Telephone numbers at which the Patient can be reached + Telephone numbers at which the Patient can be reached.
- Ethnic group or race of Patient + Ethnic group or race of Patient.
- The religious preference of the Patient + The religious preference of the Patient.
- User-defined comments about the Patient + User-defined comments about the Patient.
@@ -94911,7 +96227,7 @@ (0010,2000) @@ -94965,7 +96281,7 @@ (0010,21B0) @@ -95014,7 +96330,7 @@ (0010,21D0) @@ -95090,7 +96406,7 @@ (0038,0050) @@ -95101,7 +96417,7 @@ (0038,0500) @@ -95300,8 +96616,8 @@ The following Sections specify Modules relevant to a Real World Patient visit.
Visit Relationship Module - - defines the Attributes that reference SOP Instances related to this SOP Class. + + specifies the Attributes of the , which reference SOP Instances related to this SOP Class.
Patient Medical Module Attributes
- Conditions to which medical staff should be alerted (e.g., contagious condition, drug allergies, etc.) + Conditions to which medical staff should be alerted (e.g., contagious condition, drug allergies, etc.).
- Additional information about the Patient's medical history + Additional information about the Patient's medical history.
- Date of onset of last menstrual period + Date of onset of last menstrual period.
- Medical and social needs (e.g., wheelchair, oxygen, translator, etc.) + Medical and social needs (e.g., wheelchair, oxygen, translator, etc.).
- Description of Patient state (comatose, disoriented, vision impaired, etc.) + Description of Patient state (comatose, disoriented, vision impaired, etc.).
@@ -95368,8 +96684,8 @@
Visit Identification Module - - defines the Attributes relevant to identifying a Visit. + + specifies the Attributes of the , which identify a Visit.
Visit Relationship Module Attributes
@@ -95394,7 +96710,7 @@ (0008,0080) @@ -95405,7 +96721,7 @@ (0008,0081) @@ -95555,7 +96871,7 @@ (0038,0060) @@ -95597,8 +96913,8 @@
Visit Status Module - - defines the Attributes relevant to the Patient's stay with the healthcare provider. + + specifies the Attributes of the , which are relevant to the Patient's stay with the healthcare provider.
Visit Identification Module Attributes
- Institution where the equipment is located + Institution where the equipment is located.
- Mailing Address of the institution where the equipment is located + Mailing Address of the institution where the equipment is located.
- Identifier of the Service Episode as assigned by the healthcare provider + Identifier of the Service Episode as assigned by the healthcare provider.
@@ -95661,7 +96977,7 @@ (0038,0300) @@ -95672,7 +96988,7 @@ (0038,0400) @@ -95683,7 +96999,7 @@ (0038,4000) @@ -95691,8 +97007,8 @@
Visit Admission Module - - defines the Attributes relevant to admitting a Patient during a Visit. + + specifies the Attributes of the , which are relevant to admitting the Patient during the Visit.
Visit Status Module Attributes
- Describes the current known location of the Patient + Describes the current known location of the Patient.
- Primary location where Patient resides (ward, floor, room, etc. or outpatient) + Primary location where Patient resides (ward, floor, room, etc. or outpatient).
- User-defined comments about the Visit + User-defined comments about the Visit.
@@ -95717,7 +97033,7 @@ (0008,0090) @@ -95728,7 +97044,7 @@ (0008,0092) @@ -95739,7 +97055,7 @@ (0008,0094) @@ -95849,7 +97165,7 @@ (0038,0016) @@ -95860,7 +97176,7 @@ (0038,0020) @@ -95871,7 +97187,7 @@ (0038,0021) @@ -95879,11 +97195,11 @@
Visit Discharge Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Visit Scheduling Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
@@ -95891,39 +97207,39 @@ The following Sections specify Modules relevant to a Real World diagnostic imaging Study performed on a Patient.
Study Relationship Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Identification Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Classification Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Scheduling Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Acquisition Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Read Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Component Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Component Relationship Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Component Acquisition Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Scheduled Procedure Step Module @@ -96297,7 +97613,7 @@
@@ -96382,7 +97698,7 @@ - In the case of a scanned patient label, this may be the same as Patient ID (0010,0020), but it is included in the Scheduled Procedure Step Module rather than the Patient Identification Module since barcodes may also be used to identify lower level entities and/or different forms of patient identifier may be in use. + In the case of a scanned patient label, this may be the same as Patient ID (0010,0020), but it is included in the rather than the Patient Identification Module since barcodes may also be used to identify lower level entities and/or different forms of patient identifier may be in use. In the case of a scanned slide label, this may be the same as Container Identifier (0040,0512). @@ -96486,6 +97802,7 @@ @@ -96497,7 +97814,33 @@ + + + + + + + + + @@ -96509,7 +97852,7 @@ (0020,000D) @@ -96566,7 +97909,7 @@ (0032,1060) @@ -96721,7 +98064,9 @@
Visit Admission Module Attributes
- Patient's primary referring physician for this Visit + Patient's primary referring physician for this Visit.
- Referring physician's address + Referring physician's address.
- Referring physician's telephone numbers + Referring physician's telephone numbers.
- Mode of admission: emergency, normal + Mode of admission: emergency, normal.
- Date Patient Visit began + Date Patient Visit began.
- Time Patient Visit began + Time Patient Visit began.
Type of device, process or method for which the Scheduled Procedure Step is scheduled. - See for Defined Terms. + See for Defined Terms.
A Sequence that conveys the Requested Procedure of one Procedure Type. + Only a single Item shall be included in this Sequence.
- No Baseline CID is defined. + B. + +
+ Requested Laterality Code Sequence + + (0032,1065) + + Laterality of body part subject of procedure. + Only a single Item shall be included in this Sequence. + If present, shall not conflict with any pre-coordinated laterality in Requested Procedure Code Sequence (0032,1064). +
+ + >Include + + + + + D.
- Unique identifier to be used to identify the Study + Unique identifier to be used to identify the Study.
- Institution-generated administrative description or classification of Requested Procedure + Institution-generated administrative description or classification of Requested Procedure.
- Placer Order Number / Procedure (0040,1006) and Filler Order Number / Procedure (0040,1007) were previously defined in DICOM. They are now retired (see PS3.3-1998). + Placer Order Number / Procedure (0040,1006) and Filler Order Number / Procedure (0040,1007) were previously defined in DICOM. They are now retired (see + PS3.3-1998 + ).
@@ -97138,7 +98483,9 @@ Placer Order Number / Imaging Service Request (0040,2016) and Filler Order Number / Imaging Service Request (0040,2017) are intended to convey the corresponding order numbers as defined in HL7, in the case where interoperability with an HL7 environment is the objective. - Attributes (0040,2001), (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see PS3.3-1998). + Attributes (0040,2001), (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see + PS3.3-1998 + ). Both Requesting Service (0032,1033) and Requesting Service Code Sequence (0032,1034) are defined in this table; the latter is preferred, but the former may be copied from an HL7 message whether or not there is also the ability to map it to a coded form (e.g., with only ORC-17 component 1 valued). @@ -97147,9 +98494,9 @@
- Performed Procedure Step Relationship - - specifies the Attributes used to reference other SOP Classes and other Information Entities of the DICOM real-world model as defined in . + Performed Procedure Step Relationship Module + + specifies the Attributes of the , which are used to reference other SOP Classes and other Information Entities of the DICOM real-world model as defined in . @@ -97210,7 +98557,7 @@ (0010,0030) @@ -97351,7 +98698,7 @@ (0038,0060) @@ -97694,18 +99041,22 @@ Placer Order Number / Imaging Service Request (0040,2016) and Filler Order Number / Imaging Service Request (0040,2017) are intended to convey the corresponding order numbers as defined in HL7, in the case where interoperability with an HL7 environment is the objective. - Attributes (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see PS3.3-1998). + Attributes (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see + PS3.3-1998 + ). - Placer Order Number / Procedure (0040,1006) and Filler Order Number / Procedure (0040,1007) were previously defined in DICOM. They are now retired (see PS3.3-1998). + Placer Order Number / Procedure (0040,1006) and Filler Order Number / Procedure (0040,1007) were previously defined in DICOM. They are now retired (see + PS3.3-1998 + ).
- Performed Procedure Step Information - - defines the general Attributes that may be used by all specific Procedure Steps. + Performed Procedure Step Information Module + + specifies the Attributes of the , which may be used by all specific Procedure Steps.
Performed Procedure Step Relationship Module Attributes
- Date of birth of the named Patient + Date of birth of the named Patient.
- Identifier of the Service Episode as assigned by the healthcare provider + Identifier of the Service Episode as assigned by the healthcare provider.
@@ -97902,7 +99253,7 @@ @@ -97963,8 +99314,8 @@
Image Acquisition Results Module - - specifies Attributes that describe the acquisition of images during the performance of the Procedure Step and that provide references to the Series, Images and other Composite SOP Instances associated with this Modality Performed Procedure Step. + + specifies the Attributes of the , which describe the acquisition of images during the performance of the Procedure Step and that provide references to the Series, Images and other Composite SOP Instances associated with this Modality Performed Procedure Step.
Performed Procedure Step Information Module Attributes
- No Baseline CID is defined. + B.
@@ -97990,7 +99341,7 @@ @@ -98361,11 +99712,13 @@
Radiation Dose Module - This Module has been retired. See PS3.3 2017c + This Module has been retired. See PS3.3-2017c +
Billing and Material Management Code Module - The Attributes defined in provide a means to transmit billing and material management codes from a modality to an Information System. It is beyond the scope of this Standard to define all the required coding schemes and the relevant codes. + + specifies the Attributes of the Billing and Material Management Code Module, which provide a means to transmit billing and material management codes from a modality to an Information System. It is beyond the scope of this Standard to define all the required coding schemes and the relevant codes.
Image Acquisition Results Module Attributes
Type of device, process or method that originally acquired the data used to create the Instances associated with this Modality Performed Procedure Step. - See for Defined Terms. + See for Defined Terms. A Modality value in the created SOP Instances may be different from the MPPS Modality value. For example, multiple Series may have been created during the MPPS (images, waveforms, softcopy presentation states and/or structured reports) with SOP Instances in different Series having different modality values. @@ -98194,7 +99545,7 @@ (0008,103E) - Description of the Series + Description of the Series.
@@ -98541,28 +99894,28 @@
General Purpose Scheduled Procedure Step Relationship Module (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
General Purpose Scheduled Procedure Step Information Module (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
General Purpose Performed Procedure Step Relationship Module (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
General Purpose Performed Procedure Step Information Module (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
General Purpose Results (Retired) - Retired. See PS3.3-2011. + Retired. See PS3.3-2011.
Instance Availability Notification Module - - specifies the Attributes used to describe which Instances are available and their relationships. + + specifies the Attributes of the , which describe which Instances are available and their relationships.
Billing and Material Management Code Module Attributes
@@ -98819,11 +100172,11 @@
Results Modules - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Interpretation Modules - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Common Composite Image IOD Modules @@ -98832,9 +100185,9 @@ Common Patient IE Modules The following Patient IE Module is common to all Composite Image IODs that reference the Patient IE.
- Patient Module + Patient Module - specifies the Attributes of the Patient that describe and identify the Patient who is the subject of a Study. This Module contains Attributes of the Patient that are needed for interpretation of the Composite Instances and are common for all Studies performed on the Patient. It contains Attributes that are also included in the Patient Modules in . + specifies the Attributes of the , which identify and describe the Patient who is the subject of the Study. This Module contains Attributes of the Patient that are needed for interpretation of the Composite Instances and are common for all Studies performed on the Patient. It contains Attributes that are also included in the .
Instance Availability Notification Module Attributes
@@ -98935,7 +100288,7 @@ The identifier is coded as a string regardless of the type, not as a binary value. - When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the SOP Common Module, if present. + When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the , if present. @@ -99223,7 +100576,7 @@ The identifier is coded as a string regardless of the type, not as a binary value. - When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the SOP Common Module, if present. + When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the , if present. @@ -99773,10 +101126,10 @@
Patient Module Attributes
- Previously, Other Patient IDs (0010,1000) was included in this table. This Attribute have been retired. See PS3.3 2017a. + Previously, Other Patient IDs (0010,1000) was included in this table. This Attribute have been retired. See PS3.3-2017a.
- Patient Module Attributes + Patient Module Attribute Descriptions
Patient Breed Description and Code Sequence The breed of an animal, if known, shall be encoded in either Patient Breed Description (0010,2292) or Patient Breed Code Sequence (0010,2293) or both. @@ -100012,15 +101365,15 @@
Specimen Identification Module - Retired. See PS3.3-2008. + Retired. See PS3.3-2008. The functionality of the has been replaced by the . See .
- Clinical Trial Subject Module + Clinical Trial Subject Module - contains Attributes that identify a Patient as a clinical trial or research Subject. + specifies the Attributes of the , which identify a Patient as a clinical trial or research Subject. @@ -100170,7 +101523,7 @@
Clinical Trial Subject Module Attributes
- Clinical Trial Subject Attribute Descriptions + Clinical Trial Subject Module Attribute Descriptions Identification of subjects in clinical trials or research generally requires a combination of the following four Attributes: @@ -100224,9 +101577,9 @@
- Patient Group Macro + Patient Group Macro - specifies the Attributes of the Patient Group Macro that describe multiple imaging subjects (such as small animals for pre-clinical research) imaged at the same time as a group. This Macro may be included in the and the . + specifies the Attributes of the , which describe multiple imaging subjects (such as small animals for pre-clinical research) imaged at the same time as a group. This Macro may be included in the and the . @@ -100358,7 +101711,7 @@
Patient Group Macro Attributes
- Patient Group Macro Attributes + Patient Group Macro Attribute Descriptions
Groups of Subjects It is common to image multiple small animals for pre-clinical research as a group at the same time. @@ -100566,11 +101919,11 @@
Common Study IE Modules - The following Study IE Modules are common to all Composite Image IODs that reference the Study IE. These Modules contain Attributes of the Patient and Study that are needed for interpretation of the Composite Instances. They contain Attributes that are also in the Patient Modules in and Study Modules in . + The following Study IE Modules are common to all Composite Image IODs that reference the Study IE. These Modules contain Attributes of the Patient and Study that are needed for interpretation of the Composite Instances. They contain Attributes that are also in the and the .
General Study Module - specifies the Attributes that describe and identify the Study performed upon the Patient. + specifies the Attributes, which identify and describe the Study performed upon the Patient. @@ -100643,9 +101996,9 @@ 2 - + Name of the Patient's referring physician. + + - + Names of the physician(s) who are responsible for overall Patient care at time of Study (see for Performing Physician). + + @@ -100999,7 +102352,7 @@
- General Study Attribute Descriptions + General Study Module Attribute Descriptions
Referring Physician, Physician of Record, Physician Reading Study, Consulting Physician The model used for application of Attributes related to different functions of Physicians involved in the care of a Patient is shown in . shows some of the relationships and information flows between physician roles that might be present in some healthcare business models. @@ -101020,9 +102373,9 @@
- Patient Study Module + Patient Study Module - defines Attributes that provide information about the Patient at the time the Study started. + specifies the Attributes of the , which provide information about the Patient at the time the Study started. In the case of imaging a group of small animals simultaneously, the Attributes in this Module can only have values that apply to the entire group, otherwise they are absent (e.g., Patient's Weight (0010,1030)) or empty (e.g., Patient's Sex Neutered (0010,2203). @@ -101056,9 +102409,9 @@ 3
- + Description of the admitting diagnosis (diagnoses). + + - + Conditions to which medical staff should be alerted (e.g., contagious condition, drug allergies, etc.). + + - + Date of onset of last menstrual period. + + - + Description of Patient state (comatose, disoriented, vision impaired, etc.). + + - + Identifier of the Service Episode as assigned by the healthcare provider. + +
General Study Module Attributes
- Name of the Patient's referring physician -
Referring Physician Identification Sequence @@ -100789,9 +102142,9 @@ 3 - Names of the physician(s) who are responsible for overall Patient care at time of Study (see for Performing Physician) -
Physician(s) of Record Identification Sequence @@ -100951,7 +102304,7 @@ - No Baseline CID is defined. + B.
- Description of the admitting diagnosis (diagnoses) -
Admitting Diagnoses Code Sequence @@ -101219,9 +102572,9 @@ 3 - Conditions to which medical staff should be alerted (e.g., contagious condition, drug allergies, etc.) -
Allergies @@ -101323,9 +102676,9 @@ 3 - Date of onset of last menstrual period -
Patient State @@ -101337,9 +102690,9 @@ 3 - Description of Patient state (comatose, disoriented, vision impaired, etc.) -
Occupation @@ -101467,9 +102820,9 @@ 3 - Identifier of the Service Episode as assigned by the healthcare provider -
Issuer of Service Episode ID Sequence @@ -101547,9 +102900,9 @@
- Clinical Trial Study Module + Clinical Trial Study Module - contains Attributes that identify a Study in the context of a clinical trial or research. + specifies the Attributes of the , which identify a Study in the context of a clinical trial or research. @@ -101597,6 +102950,34 @@ A description of a set of one or more Studies that are grouped together to represent a clinical time point or submission in a clinical trial or research. See . + + + + + + + + + +
Clinical Trial Study Module Attributes
+ Clinical Trial Time Point Type Code Sequence + + (0012,0054) + + 3 + + A pre-defined type of a set of one or more Studies that are grouped together to represent a clinical time point or submission in a clinical trial or research. See . + One or more Items are permitted in this Sequence. +
+ + >Include + + + + + B. + +
Longitudinal Temporal Offset from Event @@ -101751,10 +103132,13 @@
- Clinical Trial Study Attribute Descriptions + Clinical Trial Study Module Attribute Descriptions
Clinical Trial Time Point - The Clinical Trial Time Point ID (0012,0050) Attribute identifies an imaging Study within the context of an investigational protocol. This Attribute is used to define a set of Studies that are grouped together as a clinical time point or data submission in a clinical trial or research. The Clinical Trial Time Point Description (0012,0051) Attribute can be used to give a description of the Clinical Trial Time Point to which the set of Studies belongs. + The Clinical Trial Time Point ID (0012,0050) Attribute identifies an imaging Study within the context of an investigational protocol. + This Attribute is used to define a set of Studies that are grouped together as a clinical time point or data submission in a clinical trial or research. + The Clinical Trial Time Point Description (0012,0051) Attribute can be used to give a description of the Clinical Trial Time Point to which the set of Studies belongs. + Clinical Trial Time Point Type Code Sequence (0012,0054) can be used to specify one or more pre-defined type of time point from a standard lexicon; more than one type is permitted, e.g., a time point may be "posttreatment" as well as "unscheduled" or "nadir", etc.
Consent For Clinical Trial Use Sequence @@ -101808,9 +103192,9 @@ Common Series IE Modules The following Series IE Modules are common to all Composite Image IODs that reference the Series IE.
- General Series Module + General Series Module - specifies the Attributes that identify and describe general information about the Series within a Study. + specifies the Attributes of the , which identify and describe general information about the Series within a Study. @@ -101842,7 +103226,7 @@ @@ -102011,9 +103395,9 @@ 3 - + Description of the Series. + + - + Instance UID of Study to which the related Series belongs. + + - + Instance UID of Related Series. + +
General Series Module Attributes
Type of device, process or method that originally acquired or produced the data used to create the Instances in this Series. - See for Defined Terms. + See for Defined Terms.
- Description of the Series -
Series Description Code Sequence @@ -102149,9 +103533,9 @@ 1 - Instance UID of Study to which the related Series belongs -
>Series Instance UID @@ -102163,9 +103547,9 @@ 1 - Instance UID of Related Series -
>Purpose of Reference Code Sequence @@ -102343,7 +103727,7 @@
- General Series Attribute Descriptions + General Series Module Attribute Descriptions
Modality @@ -102629,7 +104013,7 @@ Plan - The term "PLAN" denotes Series describing planned activities. It is not be confused with radiotherapy treatment plans. + The term "PLAN" denotes Series describing planned activities. It is not be confused with radiotherapy treatment plans. @@ -103222,9 +104606,9 @@
- Clinical Trial Series Module + Clinical Trial Series Module - contains Attributes that identify a Series in the context of a clinical trial or research. + specifies the Attributes of the , which identify a Series in the context of a clinical trial or research. @@ -103289,7 +104673,7 @@
Clinical Trial Series Module Attributes
- Clinical Trial Series Attribute Descriptions + Clinical Trial Series Module Attribute Descriptions
Clinical Trial Coordinating Center Name The Clinical Trial Coordinating Center Name (0012,0060) identifies the institution responsible for coordinating the collection of images and associated data for subjects enrolled in the clinical trial or research. @@ -103301,9 +104685,9 @@
- Enhanced Series Module + Enhanced Series Module - Table specifies the Attributes that identify and describe general information about the Series within a Study. + specifies the Attributes of the , which identify and describe general information about the Series within a Study. This table contains a subset of the Attributes of () but the Type designation is changed into Type 1. Including this Module in an IOD overwrites the Type designation of the . @@ -103384,10 +104768,10 @@
Common Frame of Reference Information Entity Modules
- Frame of Reference Module + Frame of Reference Module - specifies the Attributes necessary to uniquely identify a Frame of Reference that ensures the spatial relationship of Images within a Series. It also allows Images across multiple Series to share the same Frame Of Reference. This Frame Of Reference (or coordinate system) shall be constant for all Images related to a specific Frame Of Reference. - When a Frame of Reference is identified, it is not important how the imaging target (patient, specimen, or phantom) is positioned relative to the imaging equipment or where the origin of the Frame Of Reference is located. It is important that the position of the imaging target and the origin are constant in relationship to a specific Frame Of Reference. + specifies the Attributes of the , which are necessary to uniquely identify a Frame of Reference that ensures the spatial relationship of Images within a Series. It also allows Images across multiple Series to share the same Frame of Reference. This Frame of Reference (or coordinate system) shall be constant for all Images related to a specific Frame of Reference. + When a Frame of Reference is identified, it is not important how the imaging target (patient, specimen, or phantom) is positioned relative to the imaging equipment or where the origin of the Frame of Reference is located. It is important that the position of the imaging target and the origin are constant in relationship to a specific Frame of Reference. Since the criteria used to group images into a Series is application specific, it is possible for imaging applications to define multiple Series within a Study that share the same imaging space. Previous versions of the DICOM Standard specified that all images within the Series must be spatially related. However, insufficient information was available to determine if multiple Series within a Study were spatially related. @@ -103441,7 +104825,7 @@
- Frame of Reference Attribute Descriptions + Frame of Reference Module Attribute Descriptions
Frame of Reference UID The Frame of Reference UID (0020,0052) shall be used to uniquely identify a Frame of Reference for a Series. Each Series shall have a single Frame of Reference UID. However, multiple Series within a Study may share a Frame of Reference UID. All images in a Series that share the same Frame of Reference UID shall be spatially related to each other. @@ -103470,9 +104854,9 @@
- Synchronization Module + Synchronization Module - specifies the Attributes necessary to uniquely identify a Frame of Reference that establishes the temporal relationship of SOP Instances. A synchronized environment may be established based on a shared time of day clock, and/or on a shared trigger event or synchronization waveform channel. + specifies the Attributes of the , which are necessary to uniquely identify a Frame of Reference that establishes the temporal relationship of SOP Instances. A synchronized environment may be established based on a shared time of day clock, and/or on a shared trigger event or synchronization waveform channel. Within a synchronized environment, different devices may use the shared data differently. An electrical pulse, for example, may be treated as a trigger event by one device (e.g., an X-Ray imaging system), but may be recorded as a synchronization waveform by another device (e.g., a hemodynamics system). @@ -103561,9 +104945,9 @@ 3 - Specifies equipment ID of trigger source and/or type of trigger - - + Specifies equipment ID of trigger source and/or type of trigger. + + Synchronization Channel @@ -103576,9 +104960,9 @@ Identifier of waveform channel that records the synchronization channel or trigger, see . - Required if synchronization channel or trigger is encoded in a waveform in this SOP Instance - - + Required if synchronization channel or trigger is encoded in a waveform in this SOP Instance. + + Acquisition Time Synchronized @@ -103621,9 +105005,9 @@ 3 - ID of equipment or system providing time reference - - + ID of equipment or system providing time reference. + + Time Distribution Protocol @@ -103691,7 +105075,7 @@
- Synchronization Attribute Descriptions + Synchronization Module Attribute Descriptions
Synchronization Frame of Reference UID A set of equipment may share a common acquisition synchronization environment, which is identified by a Synchronization Frame of Reference UID. All SOP Instances that share the same Synchronization Frame of Reference UID shall be temporally related to each other. If a Synchronization Frame of Reference UID is present, all SOP Instances in the Series must share the same Frame of Reference. @@ -103723,7 +105107,7 @@
Acquisition Time Synchronized - The Acquisition Time Synchronized (0018,1800) Attribute specifies whether Acquisition DateTime (0008,002A) of the or the represents an accurate synchronized timestamp for the acquisition of the waveform and/or image data. For triggered multi-frame images, the Acquisition DateTime applies to the trigger for the first image frame (see Attribute Image Trigger Delay (0018.1067) in the ). + The Acquisition Time Synchronized (0018,1800) Attribute specifies whether Acquisition DateTime (0008,002A) of the or the represents an accurate synchronized timestamp for the acquisition of the waveform and/or image data. For triggered multi-frame images, the Acquisition DateTime applies to the trigger for the first image frame (see Attribute Image Trigger Delay (0018,1067) in the ). The degree of precision of the Acquisition DateTime and its accuracy relative to the external clock are not specified, but need to be appropriate for the clinical application. @@ -103745,9 +105129,9 @@ Common Equipment IE Modules The following Equipment IE Module is common to all Composite IODs that reference the Equipment IE.
- General Equipment Module + General Equipment Module - specifies the Attributes that identify and describe the piece of equipment that produced Composite Instances. + specifies the Attributes of the , which identify and describe the piece of equipment that produced Composite Instances. @@ -104060,7 +105444,7 @@ 1C @@ -104083,7 +105470,7 @@
General Equipment Module Attributes
- Single pixel value or one limit (inclusive) of a range of pixel values used in an image to pad to rectangular format or to signal background that may be suppressed. See for further explanation. + Single pixel value or one limit (inclusive) of a range of pixel values used in an image to pad to rectangular format or to signal background that may be suppressed or that may be rendered "transparently" when superimposing images. See for further explanation. Required if Pixel Padding Range Limit (0028,0121) is present and either Pixel Data (7FE0,0010) or Pixel Data Provider URL (0028,7FE0) is present. May be present otherwise only if Pixel Data (7FE0,0010) or Pixel Data Provider URL (0028,7FE0) is present. @@ -104068,7 +105452,7 @@ The Value Representation of this Attribute is determined by the value of Pixel Representation (0028,0103). - This Attribute is not used in Presentation State Instances; there is no means in a Presentation State to "override" any Pixel Padding Value specified in the referenced images. + This Attribute is not used in Presentation State Instances; there is no means in a Presentation State to "override" any Pixel Padding Value (0028,0120) specified in the referenced images. This Attribute does apply to RT Dose and Segmentation Instances, since they include Pixel Data. @@ -104076,6 +105460,9 @@ This Attribute does not apply when Float Pixel Data (7FE0,0008) or Double Float Pixel Data (7FE0,0009) are used instead of Pixel Data (7FE0,0010); Float Pixel Padding Value (0028,0122) or Double Float Pixel Padding Value (0028,0123), respectively, are used instead, and defined at the Image, not the Equipment, level. + + Only a single Value is allowed for this Attribute, so it only applies to images with Samples per Pixel (0028,0002) of 1, i.e., images with a Photometric Interpretation (0028,0004) of MONOCHROME1, MONOCHROME2 or PALETTE COLOR. See for details. +
- General Equipment Attribute Descriptions + General Equipment Module Attribute Descriptions The Attributes Manufacturer (0008,0070), Manufacturer's Model Name (0008,1090) and Device Serial Number (0018,1000) are intended to be a primary identification of the system that produces the data (e.g., modality or workstation application providing the content of the SOP Instance) and not the identification of the component that encodes the SOP Instance (e.g., a commonly used DICOM encoding toolkit). @@ -104093,26 +105480,26 @@
Pixel Padding Value and Pixel Padding Range Limit - Pixel Padding Value (0028,0120) is used to pad grayscale images (those with a Photometric Interpretation of MONOCHROME1 or MONOCHROME2) to rectangular format. The native format of some images is not rectangular. It is common for devices with this format to pad the images to the rectangular format required by the DICOM Standard with a specific pixel value that is not contained in the native image. Further, when resampling, such as after spatial registration, padding may need to be used to fill previously non-existent pixels. - Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) are also used to identify pixels to be excluded from the normal grayscale rendering pipeline for other reasons, such as suppression of background air. Pixel Padding Range Limit (0028,0121) is defined in the . + Pixel Padding Value (0028,0120) is typically used to pad grayscale images (those with a Photometric Interpretation (0028,0004) of MONOCHROME1 or MONOCHROME2), or color images with a Photometric interpretation (0028,0004) of PALETTE COLOR, to rectangular format. The native format of some images is not rectangular. It is common for devices with this format to pad the images, to the rectangular format required by the DICOM Standard, with a specific pixel value that is not contained in the native image. Further, when resampling, such as after spatial registration, padding may need to be used to fill previously non-existent pixels. + Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) are also used to identify pixels to be excluded from the rendering pipeline for other reasons, such as suppression of background air. Pixel Padding Range Limit (0028,0121) is defined in the . - The "native image" is that which is being padded to the required rectangular format, e.g., the area within the circular reconstruction perimeter of a CT image, or the subset of the rectangular area that contains useful image information. + The "native image" is that which is being padded to the required rectangular format, e.g., the area within the circular reconstruction perimeter of a CT image, or the subset of the rectangular area that contains useful image information, i.e., which is not to be suppressed, or e.g., is that part of a pseudo-colored image that might be superimposed on top of another image. For other mechanisms, see . - The pixel padding value is explicitly described in order to prevent display applications from taking it into account when determining the dynamic range of an image, since the Pixel Padding Value will be outside the range between the minimum and maximum values of the pixels in the native image + The Pixel Padding Value is explicitly described in order to prevent display applications from taking it into account when determining the dynamic range of an image, since the Pixel Padding Value will be outside the range between the minimum and maximum values of the pixels in the native image - No pixels in the native image will have a value equal to Pixel Padding Value. + No pixels in the native image will have a value equal to Pixel Padding Value (0028,0120). - Pixel Padding Value (0028,0120) specifies either a single value of this padding value, or when combined with Pixel Padding Range Limit (0028,0121), a range of values (inclusive) that are padding. + Pixel Padding Value (0028,0120) specifies either a single value of this padding, or when combined with Pixel Padding Range Limit (0028,0121), a range of values (inclusive) that are padding. The values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be valid values within the constraints defined by Bits Allocated (0028,0100), Bits Stored (0028,0101), and High Bit (0028,0102). - The padding value shall correspond to a value in the original stored pixel data, before the Modality LUT Transformation or any other transformations are applied. + The Pixel Padding Value shall correspond to a value in the original stored pixel data, before the Modality LUT Transformation or any other transformations are applied. Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall not be present when padding is performed but the pixel value used for padding does occur in the native image. - If Photometric Interpretation (0028,0004) is MONOCHROME2, Pixel Padding Value (0028,0120) shall be less than (closer to or equal to the minimum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121). If Photometric Interpretation (0028,0004) is MONOCHROME1, Pixel Padding Value (0028,0120) shall be greater than (closer to or equal to the maximum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121). + If Photometric Interpretation (0028,0004) is MONOCHROME2 or PALETTE COLOR, Pixel Padding Value (0028,0120) shall be less than (closer to or equal to the minimum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121). If Photometric Interpretation (0028,0004) is MONOCHROME1, Pixel Padding Value (0028,0120) shall be greater than (closer to or equal to the maximum possible pixel value) or equal to Pixel Padding Range Limit (0028,0121). @@ -104141,17 +105528,17 @@ . - The conditional requirement for the Pixel Padding Value Range Limit (0028,0121) in the means that it shall not be present unless Pixel Padding Value (0028,0120) is also present. + The conditional requirement for the Pixel Padding Range Limit (0028,0121) in the means that it shall not be present unless Pixel Padding Value (0028,0120) is also present. - The range of values to be suppressed between Pixel Padding Value (0028,0120) and Pixel Padding Value Range Limit (0028,0121) is specified as being inclusive, that is the values themselves as well as all values between are suppressed. + The range of values to be suppressed between Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) is specified as being inclusive, that is the values themselves as well as all values between are suppressed. - When Pixel Padding Value Range Limit (0028,0121) is present, but not supported by a rendering application, the constraint that Pixel Padding Value (0028,0120) is closest to the "blackest" value, which is typically the most frequently occurring background pixel, will most often result in an acceptable display, permitting "backward compatibility" in the majority of cases. + When Pixel Padding Range Limit (0028,0121) is present, but not supported by a rendering application, the constraint that Pixel Padding Value (0028,0120) is closest to the "blackest" value, which is typically the most frequently occurring background pixel, will most often result in an acceptable display, permitting "backward compatibility" in the majority of cases. - When modifying equipment changes the pixel padding value in the image, it shall change the values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121), if present. If modifying equipment changes the pixel padding values in the image to values present in the native image, the Attribute Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be removed. + When modifying equipment changes the Pixel Padding Value in the image, it shall change the values of Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121), if present. If modifying equipment changes the Pixel Padding Values in the image to values present in the native image, the Attribute Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) shall be removed. @@ -104170,9 +105557,9 @@
- Enhanced General Equipment Module + Enhanced General Equipment Module - specifies the Attributes that identify and describe the piece of equipment that produced Composite Instances. + specifies the Attributes of the , which identify and describe the piece of equipment that produced Composite Instances. @@ -104266,9 +105653,9 @@ Common Image IE Modules The following Image IE Modules are common to all Composite Image IODs that reference the Image IE.
- General Image Module + General Image Module - specifies the Attributes that identify and describe an image within a particular Series. + specifies the Attributes of the , which identify and describe an image within a particular Series. @@ -104369,79 +105756,6 @@ Image identification characteristics. See for Defined Terms and further explanation. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + User-defined comments about the image. + + @@ -104666,20 +105996,6 @@ When this Attribute is used with a color photometric interpretation then the luminance component is in P-Values. - - - - - -
General Image Module Attributes
- Acquisition Number - - (0020,0012) - - 3 - - A number identifying the single continuous gathering of data over a period of time that resulted in this image. -
- Acquisition Date - - (0008,0022) - - 3 - - The date the acquisition of data that resulted in this image started -
- Acquisition Time - - (0008,0032) - - 3 - - The time the acquisition of data that resulted in this image started -
- Acquisition DateTime - - (0008,002A) - - 3 - - The date and time that the acquisition of data that resulted in this image started. - - The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). - -
- Images in Acquisition - - (0020,1002) - - 3 - - Number of images that resulted from this acquisition of data -
Image Comments @@ -104453,9 +105767,9 @@ 3 - User-defined comments about the image -
Quality Control Image @@ -104467,24 +105781,40 @@ 3 - Indicates whether or not this image is a quality control or phantom image. + Indicates whether or not quality control material (such as calibration or control material, or a phantom) is present in this image. Enumerated Values: YES - + the image contains only quality control material NO - + the image does not contain quality control material + + + + BOTH + + the image contains both subject (patient) and quality control information - If this Attribute is absent, then the image may or may not be a quality control or phantom image. The phantom device in the image can be described using the . See - + If this Attribute is absent, then the image may or may not be a quality control or phantom image. The phantom device or quality control material in the image can be described using the . See . + + Examples of the presence of both subject and quality control information include: + + + presence of objects of known density in radiographic images for calibration + + + presence of control material for immunohistochemistry within slide images + + +
- Irradiation Event UID - - (0008,3010) - - 3 - - Unique identification of the irradiation event(s) associated with the acquisition of this image. See . -
Real World Value Mapping Sequence @@ -104761,7 +106077,7 @@ Anatomic Region Sequence B for humans. - + Anatomic Region Sequence B for animals. @@ -104770,10 +106086,10 @@
- Previous editions of this Standard specified use of the Referenced Waveform Sequence (0008,113A), but that use has been superseded by Referenced Instance Sequence (0008,114A). See PS3.3-2004. + Previous editions of this Standard specified use of the Referenced Waveform Sequence (0008,113A), but that use has been superseded by Referenced Instance Sequence (0008,114A). See PS3.3-2004.
- General Image Attribute Descriptions + General Image Module Attribute Descriptions
Patient Orientation Patient Orientation (0020,0020) relative to the image plane shall be specified by two values that designate the anatomical direction of the positive row axis (left to right) and the positive column axis (top to bottom). The first entry is the direction of the rows, given by the direction of the last pixel in the first row from the first pixel in that row. The second entry is the direction of the columns, given by the direction of the last pixel in the first column from the first pixel in that column. Shall be consistent with Image Orientation (Patient) (0020,0037), if both Attributes are present and Patient Orientation (0020,0020) is not zero length. @@ -104961,7 +106277,7 @@
Source Image Sequence - Source Image Sequence (0008,2112) was formerly used in this Module but has been move to the . See . + Source Image Sequence (0008,2112) was formerly used in this Module but has been moved to the . See .
Lossy Image Compression @@ -105049,7 +106365,7 @@
Icon Image Sequence - An Icon Image may be used as a key representative of an Image. It is defined as a Sequence that contains a single Item encapsulating the Data Set made of the Data Elements of the Icon Image. The Data Elements are defined by the Image Pixel Macro (see ). Unless otherwise specified in the Module or Macro table where the Icon Image Sequence (0088,0200) is used, the following restrictions shall apply on the Image Pixel Macro usage: + An Icon Image may be used as a key representative of an Image. It is defined as a Sequence that contains a single Item encapsulating the Data Set made of the Data Elements of the Icon Image. The Data Elements are defined by the . Unless otherwise specified in the Module or Macro table where the Icon Image Sequence (0088,0200) is used, the following restrictions shall apply on the usage: Only monochrome and palette color images shall be used. Samples per Pixel (0028,0002) shall have a Value of 1, Photometric Interpretation (0028,0004) shall have a Value of either MONOCHROME 1, MONOCHROME 2 or PALETTE COLOR, Planar Configuration (0028,0006) shall not be present. @@ -105067,7 +106383,7 @@ Pixel Representation (0028,0103) shall specify an unsigned integer representation (Value 0000H). - Pixel Aspect Ratio (0028,0034) shall have a Value of 1:1. + the pixels shall be square (i.e., their aspect ratio shall be 1:1) and therefore Pixel Aspect Ratio (0028,0034) shall not be present. If a Palette Color lookup Table is used, Bits Allocated (0028,0100) shall have a Value of 8. @@ -105076,14 +106392,14 @@
Irradiation Event UID - An irradiation event is the loading of X-Ray equipment caused by a single continuous actuation of the equipment's irradiation switch, from the start of the loading time of the first pulse until the loading time trailing edge of the final pulse. Any on-off switching of the irradiation source during the event shall not be treated as separate events, rather the event includes the time between start and stop of irradiation as triggered by the user. E.g., a pulsed fluoro X-Ray acquisition shall be treated as a single irradiation event. + See .
- Image Plane Module + Image Plane Module - specifies the Attributes that define the transmitted pixel array of a two dimensional image plane in a three dimensional space. + specifies the Attributes of the , which define the transmitted pixel array of a two dimensional image plane in a three dimensional space. In previous versions of this Standard, image position and image orientation were specified relative to a specific equipment coordinate system. This equipment coordinate system was not fully defined and a number of ambiguities existed. The Equipment-Based Coordinate System has been retired and replaced by the Patient-Based Coordinate System defined in this Module. @@ -105194,7 +106510,7 @@
- Image Plane Attribute Descriptions + Image Plane Module Attribute Descriptions
Image Position and Image Orientation Image Position (0020,0032) specifies the x, y, and z coordinates of the upper left hand corner of the image; it is the center of the first voxel transmitted. Image Orientation (0020,0037) specifies the direction cosines of the first row and the first column with respect to the patient. These Attributes shall be provide as a pair. Row value for the x, y, and z axes respectively followed by the Column value for the x, y, and z axes respectively. @@ -105576,9 +106892,9 @@
- Image Pixel Module + Image Pixel Module - describes the Image Pixel Module. + specifies the Attributes of the . @@ -105613,7 +106929,7 @@ See . - When the IOD is encoded as metadata in a STOW-RS Request and the bulk pixel data is compressed, the STOW-RS origin server is required to be able to derive appropriate values for the Image Pixel Macro Attributes from the compressed bit stream. + When the IOD is encoded as metadata in a STOW-RS Request and the bulk pixel data is compressed, the STOW-RS origin server is required to be able to derive appropriate values for the Attributes from the compressed bit stream. @@ -105738,380 +107054,8 @@
Image Pixel Module Attributes
- - specifies the common Attributes that describe and encode the pixel data of the image. - - - - - - - - - - - - - - - - - - - - - -
Image Pixel Macro Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- - Include - - - -
- Pixel Data - - (7FE0,0010) - - 1 - - A data stream of the pixel samples that comprise the Image. See for further explanation. -
- - specifies the common Attributes that describe the pixel data of the image. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Image Pixel Description Macro Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- Samples per Pixel - - (0028,0002) - - 1 - - Number of samples (planes) in this image. See for further explanation. -
- Photometric Interpretation - - (0028,0004) - - 1 - - Specifies the intended interpretation of the pixel data. See for further explanation. -
- Rows - - (0028,0010) - - 1 - - Number of rows in the image. - Shall be an exact multiple of the vertical downsampling factor if any of the samples (planes) are encoded downsampled in the vertical direction for pixel data encoded in a Native (uncompressed) format. E.g., required to be an even value for a Photometric Interpretation (0028,0004) of YBR_FULL_422. -
- Columns - - (0028,0011) - - 1 - - Number of columns in the image. - Shall be an exact multiple of the horizontal downsampling factor if any of the samples (planes) are encoded downsampled in the horizontal direction for pixel data encoded in a Native (uncompressed) format. E.g., required to be an even value for a Photometric Interpretation (0028,0004) of YBR_FULL_422. -
- Bits Allocated - - (0028,0100) - - 1 - - Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. Bits Allocated (0028,0100) shall be either 1, or a multiple of 8. See for further explanation. -
- Bits Stored - - (0028,0101) - - 1 - - Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See for further explanation. -
- High Bit - - (0028,0102) - - 1 - - Most significant bit for pixel sample data. Each sample shall have the same high bit. High Bit (0028,0102) shall be one less than Bits Stored (0028,0101). See for further explanation. -
- Pixel Representation - - (0028,0103) - - 1 - - Data representation of the pixel samples. Each sample shall have the same pixel representation. - - Enumerated Values: - - 0000H - - unsigned integer. - - - - 0001H - - 2's complement - - - -
- Planar Configuration - - (0028,0006) - - 1C - - Indicates whether the pixel data are encoded color-by-plane or color-by-pixel. Required if Samples per Pixel (0028,0002) has a value greater than 1. See for further explanation. -
- Pixel Aspect Ratio - - (0028,0034) - - 1C - - Ratio of the vertical size and horizontal size of the pixels in the image specified by a pair of integer values where the first value is the vertical pixel size, and the second value is the horizontal pixel size. Required if the aspect ratio values do not have a ratio of 1:1 and the physical pixel spacing is not specified by Pixel Spacing (0028,0030), or Imager Pixel Spacing (0018,1164) or Nominal Scanned Pixel Spacing (0018,2010), either for the entire Image or per-frame in a Functional Group Macro. See . -
- Smallest Image Pixel Value - - (0028,0106) - - 3 - - The minimum actual pixel value encountered in this image. -
- Largest Image Pixel Value - - (0028,0107) - - 3 - - The maximum actual pixel value encountered in this image. -
- Red Palette Color Lookup Table Descriptor - - (0028,1101) - - 1C - - Specifies the format of the Red Palette Color Lookup Table Data (0028,1201). Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. -
- Green Palette Color Lookup Table Descriptor - - (0028,1102) - - 1C - - Specifies the format of the Green Palette Color Lookup Table Data (0028,1202). Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. -
- Blue Palette Color Lookup Table Descriptor - - (0028,1103) - - 1C - - Specifies the format of the Blue Palette Color Lookup Table Data (0028,1203). Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. -
- Red Palette Color Lookup Table Data - - (0028,1201) - - 1C - - Red Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. -
- Green Palette Color Lookup Table Data - - (0028,1202) - - 1C - - Green Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. -
- Blue Palette Color Lookup Table Data - - (0028,1203) - - 1C - - Blue Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. -
- ICC Profile - - (0028,2000) - - 3 - - An ICC Profile encoding the transformation of device-dependent color stored pixel values into PCS-Values. - See . - When present, defines the color space of color Pixel Data (7FE0,0010) values, and the output of Palette Color Lookup Table Data (0028,1201-1203). - - The profile applies only to Pixel Data (7FE0,0010) at the same level of the Data Set and not to any icons nested within Sequences, which may or may not have their own ICC profile specified. - -
- Color Space - - (0028,2002) - - 3 - - A label that identifies the well-known color space of the image. Shall be consistent with any ICC Profile (0028,2000) that is also present. - See . -
- Image Pixel Attribute Descriptions + Image Pixel Module Attribute Descriptions
Samples Per Pixel Samples per Pixel (0028,0002) is the number of separate planes in this image. One and three image planes are defined. Other numbers of image planes are allowed, but their meaning is not defined by this Standard. @@ -106231,7 +107175,7 @@ YBR_PARTIAL_422 - Retired. See PS3.3 2017b. + Retired. See PS3.3-2017b. @@ -106420,11 +107364,389 @@ The byte offsets are measured from the first byte of the first Item Tag following the empty (zero length) Basic Offset Table item, i.e., the Item Tag of the first fragment of the first frame.
+
+ Image Pixel Macro + + specifies the Attributes of the , which describe and encode the pixel data of the image. + + + + + + + + + + + + + + + + + + + + + +
Image Pixel Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ + Include + + + +
+ Pixel Data + + (7FE0,0010) + + 1 + + A data stream of the pixel samples that comprise the Image. See for further explanation. +
+
+
+ Image Pixel Description Macro + + specifies the Attributes of the , which are the common Attributes that describe the pixel data of the image. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Image Pixel Description Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Samples per Pixel + + (0028,0002) + + 1 + + Number of samples (planes) in this image. See for further explanation. +
+ Photometric Interpretation + + (0028,0004) + + 1 + + Specifies the intended interpretation of the pixel data. See for further explanation. +
+ Rows + + (0028,0010) + + 1 + + Number of rows in the image. + Shall be an exact multiple of the vertical downsampling factor if any of the samples (planes) are encoded downsampled in the vertical direction for pixel data encoded in a Native (uncompressed) format. E.g., required to be an even value for a Photometric Interpretation (0028,0004) of YBR_FULL_422. +
+ Columns + + (0028,0011) + + 1 + + Number of columns in the image. + Shall be an exact multiple of the horizontal downsampling factor if any of the samples (planes) are encoded downsampled in the horizontal direction for pixel data encoded in a Native (uncompressed) format. E.g., required to be an even value for a Photometric Interpretation (0028,0004) of YBR_FULL_422. +
+ Bits Allocated + + (0028,0100) + + 1 + + Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. Bits Allocated (0028,0100) shall be either 1, or a multiple of 8. See for further explanation. +
+ Bits Stored + + (0028,0101) + + 1 + + Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See for further explanation. +
+ High Bit + + (0028,0102) + + 1 + + Most significant bit for pixel sample data. Each sample shall have the same high bit. High Bit (0028,0102) shall be one less than Bits Stored (0028,0101). See for further explanation. +
+ Pixel Representation + + (0028,0103) + + 1 + + Data representation of the pixel samples. Each sample shall have the same pixel representation. + + Enumerated Values: + + 0000H + + unsigned integer. + + + + 0001H + + 2's complement + + + +
+ Planar Configuration + + (0028,0006) + + 1C + + Indicates whether the pixel data are encoded color-by-plane or color-by-pixel. Required if Samples per Pixel (0028,0002) has a value greater than 1. See for further explanation. +
+ Pixel Aspect Ratio + + (0028,0034) + + 1C + + Ratio of the vertical size and horizontal size of the pixels in the image specified by a pair of integer values where the first value is the vertical pixel size, and the second value is the horizontal pixel size. Required if the aspect ratio values do not have a ratio of 1:1 and the physical pixel spacing is not specified by Pixel Spacing (0028,0030), or Imager Pixel Spacing (0018,1164) or Nominal Scanned Pixel Spacing (0018,2010), either for the entire Image or per-frame in a Functional Group Macro. See . +
+ Smallest Image Pixel Value + + (0028,0106) + + 3 + + The minimum actual pixel value encountered in this image. +
+ Largest Image Pixel Value + + (0028,0107) + + 3 + + The maximum actual pixel value encountered in this image. +
+ Red Palette Color Lookup Table Descriptor + + (0028,1101) + + 1C + + Specifies the format of the Red Palette Color Lookup Table Data (0028,1201). Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. +
+ Green Palette Color Lookup Table Descriptor + + (0028,1102) + + 1C + + Specifies the format of the Green Palette Color Lookup Table Data (0028,1202). Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. +
+ Blue Palette Color Lookup Table Descriptor + + (0028,1103) + + 1C + + Specifies the format of the Blue Palette Color Lookup Table Data (0028,1203). Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. +
+ Red Palette Color Lookup Table Data + + (0028,1201) + + 1C + + Red Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. +
+ Green Palette Color Lookup Table Data + + (0028,1202) + + 1C + + Green Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. +
+ Blue Palette Color Lookup Table Data + + (0028,1203) + + 1C + + Blue Palette Color Lookup Table Data. Required if Photometric Interpretation (0028,0004) has a value of PALETTE COLOR or Pixel Presentation (0008,9205) at the image level equals COLOR or MIXED. See for further explanation. +
+ ICC Profile + + (0028,2000) + + 3 + + An ICC Profile encoding the transformation of device-dependent color stored pixel values into PCS-Values. + See . + When present, defines the color space of color Pixel Data (7FE0,0010) values, and the output of Palette Color Lookup Table Data (0028,1201-1203). + + The profile applies only to Pixel Data (7FE0,0010) at the same level of the Data Set and not to any icons nested within Sequences, which may or may not have their own ICC profile specified. + +
+ Color Space + + (0028,2002) + + 3 + + A label that identifies the well-known color space of the image. Shall be consistent with any ICC Profile (0028,2000) that is also present. + See . +
+
Contrast/Bolus Module - specifies the Attributes that describe the contrast /bolus used in the acquisition of the Image. + specifies the Attributes of the Contrast/Bolus Module, which describe the contrast /bolus used in the acquisition of the Image. @@ -106455,9 +107777,9 @@ 2 - + Contrast or bolus agent. + + - + Administration route of contrast agent. + + - + Volume injected in milliliters of diluted contrast agent. + + - + Time of start of injection. + + - + Time of end of contrast injection. + + - + Total amount in milliliters of the undiluted contrast agent. + + - + Rate(s) of injection(s) in milliliters/sec. + + - + Milligrams of active ingredient per milliliter of (diluted) agent. + +
Contrast/Bolus Module Attributes
- Contrast or bolus agent -
Contrast/Bolus Agent Sequence @@ -106497,9 +107819,9 @@ 3 - Administration route of contrast agent -
Contrast/Bolus Administration Route Sequence @@ -106567,9 +107889,9 @@ 3 - Volume injected in milliliters of diluted contrast agent -
Contrast/Bolus Start Time @@ -106581,9 +107903,9 @@ 3 - Time of start of injection -
Contrast/Bolus Stop Time @@ -106595,9 +107917,9 @@ 3 - Time of end of contrast injection -
Contrast/Bolus Total Dose @@ -106609,9 +107931,9 @@ 3 - Total amount in milliliters of the undiluted contrast agent -
Contrast Flow Rate @@ -106623,9 +107945,9 @@ 3 - Rate(s) of injection(s) in milliliters/sec -
Contrast Flow Duration @@ -106692,9 +108014,9 @@ 3 - Milligrams of active ingredient per milliliter of (diluted) agent -
@@ -106731,7 +108053,7 @@
Enhanced Contrast/Bolus Module - specifies the Attributes that describe the contrast/bolus used in the acquisition of the Image. + specifies the Attributes of the Enhanced Contrast/Bolus Module, which describe the contrast/bolus used in the acquisition of the Image. @@ -107023,7 +108345,7 @@
Enhanced Contrast/Bolus Module Attributes
- Enhanced Contrast/Bolus Module Attributes + Enhanced Contrast/Bolus Module Attribute Descriptions
Contrast/Bolus Ingredient Opaque for X-Ray Equipment Contrast/Bolus Ingredient Opaque (0018,9425) Attribute specifies the type of relative X-Ray absorption of the contrast/bolus ingredient, compared to the X-Ray absorption of water. @@ -107061,9 +108383,9 @@
- Cine Module + Cine Module - specifies the Attributes of a Multi-frame Cine Image. + specifies the Attributes of the , which describe a Multi-frame Cine Image. @@ -107345,7 +108667,7 @@
Cine Module Attributes
- Cine Attribute Descriptions + Cine Module Attribute Descriptions
Frame Time Frame Time (0018,1063) is the nominal time (in milliseconds) between individual frames of a Multi-frame image. If the Frame Increment Pointer points to this Attribute, Frame Time shall be used in the following manner to calculate 'the relative time' for each frame: @@ -107412,9 +108734,9 @@
- Multi-frame Module + Multi-frame Module - specifies the Attributes of a Multi-frame pixel data Image. + specifies the Attributes of the , which describe a Multi-frame pixel data Image. @@ -107491,10 +108813,27 @@ + + + + + +
Multi-frame Module Attributes
+ Encapsulated Pixel Data Value Total Length + + (7FE0,0003) + + 3 + + The length of the pixel data bit stream encapsulated in Pixel Data (7FE0,0010), in bytes, when all the fragments have been combined, not including any trailing padding to even length in the last Fragment added for encapsulation. + + This value will depend on the Transfer Syntax in which the Pixel Data (7FE0,0010) is encoded, and may need to be updated depending on the Transfer Syntax negotiated and selected for a particular transfer. See . + +
- Multi-frame Attribute Descriptions + Multi-frame Module Attribute Descriptions
Number of Frames and Frame Increment Pointer A Multi-frame Image is defined as a Image whose pixel data consists of a sequential set of individual Image Pixel frames. A Multi-frame Image is transmitted as a single contiguous stream of pixels. Frame headers do not exist within the data stream. @@ -107543,9 +108882,9 @@
- Frame Pointers Module + Frame Pointers Module - specifies the Attributes of a Frame Pointer Module. + specifies the Attributes of the . @@ -107576,9 +108915,9 @@ 3 - + The frame number selected for use as a pictorial representation (e.g., icon) of the Multi-frame Image. + + @@ -109200,6 +110537,23 @@ If present, shall have a value greater than one, unless an IOD overrides this constraint to enumerate a value of 1 to prevent the use of Concatenations (e.g., see and ). + + + + + +
Frame Pointers Module Attributes
- The frame number selected for use as a pictorial representation (e.g., icon) of the Multi-frame Image -
Frame Numbers Of Interest (FOI) @@ -107662,9 +109001,9 @@
- Mask Module + Mask Module - specifies the Attributes that describe mask operations for a Multi-frame image. + specifies the Attributes of the , which describe mask operations for a Multi-frame image. @@ -107886,7 +109225,7 @@ Frame numbers begin at 1.
- Mask Subtraction Attribute Descriptions + Mask Module Attribute Descriptions
Mask Operation Mask Operation (0028,6101) specifies a type of mask operation to be performed. @@ -108325,9 +109664,9 @@
- Device Module + Device Module - describes the Attributes of devices or calibration objects (e.g., catheters, markers, baskets) that are associated with a Study and/or image. + specifies the Attributes of the , which identifies and describes devices or calibration objects (e.g., catheters, markers, baskets) or other quality control materials that are associated with a Study and/or image.
Mask Module Attributes
@@ -108386,9 +109725,9 @@ 3 - + Manufacturer of the device. + + - + Manufacturer's model name of the device. + + - + Manufacturer's serial number of the device. + + - + User-supplied identifier for the device. + +
Device Module Attributes
- Manufacturer of the device -
>Manufacturer's Model Name @@ -108400,9 +109739,9 @@ 3 - Manufacturer's model name of the device -
>Device Serial Number @@ -108414,9 +109753,9 @@ 3 - Manufacturer's serial number of the device -
>Device ID @@ -108428,9 +109767,9 @@ 3 - User-supplied identifier for the device -
>Device Length @@ -108545,7 +109884,7 @@
- Device Attribute Descriptions + Device Module Attribute Descriptions
Device Type and Size Depending on the type of device specified by Code Value (0008,0100) in an Item of Device Sequence (0050,0010), various device size Attributes (e.g., Device Length (0050,0014), Device Diameter (0050,0016), Device Volume (0050,0018), Inter Marker Distance (0050,0019)) may be required to fully characterize the device. @@ -108553,9 +109892,9 @@
- Intervention Module + Intervention Module - describes the Attributes of therapies (e.g., interventions during an angiographic procedure) that are associated with a Study and/or image. + specifies the Attributes of the , which describes therapies (e.g., interventions during an angiographic procedure) that are associated with a Study and/or image. @@ -108745,20 +110084,18 @@
Intervention Module Attributes
- Therapy Description (0018,0039) was included in this Module in earlier editions, but its use has been retired. See PS3.3-2003. + Therapy Description (0018,0039) was included in this Module in earlier editions, but its use has been retired. See PS3.3-2003.
- Acquisition Context Module + Acquisition Context Module - specifies Attributes for description of the conditions present during data acquisition. + specifies the Attributes of the , which describes the conditions present during data acquisition. This Module shall not contain descriptions of conditions that replace those that are already described in specific Modules or Attributes that are also contained within the IOD that contains this Module. - If this SOP Instance is a Multi-frame SOP Instance, each Item of the Acquisition Context Sequence (0040,0555) may be configured to describe one frame, all frames, or any specifically enumerated subset set of frames of the Multi-frame SOP Instance. - Previously, Referenced Frame Numbers (0040,A136) was used to enumerate which frames were described, but its length was limited, so it has been replaced by Referenced Frame Number (0008,1160). - Similarly, applicability to a subset of Segments or Waveform Channels may be specified. + If this SOP Instance is a Multi-frame SOP Instance, each Item of the Acquisition Context Sequence (0040,0555) may be configured to describe one frame, all frames, or any specifically enumerated subset set of frames of the Multi-frame SOP Instance. Previously, Referenced Frame Numbers (0040,A136) was used to enumerate which frames were described, but its length was limited, so it has been replaced by Referenced Frame Number (0008,1160). Similarly, applicability to a subset of Segments or Waveform Channels may be specified. @@ -108799,9 +110136,9 @@
->Include - - + >Include + +
+ Encapsulated Pixel Data Value Total Length + + (7FE0,0003) + + 3 + + The length of the pixel data bit stream encapsulated in Pixel Data (7FE0,0010), in bytes, when all the fragments have been combined, not including any trailing padding to even length in the last Fragment added for encapsulation. + + This value will depend on the Transfer Syntax in which the Pixel Data (7FE0,0010) is encoded, and may need to be updated depending on the Transfer Syntax negotiated and selected for a particular transfer. See . + +
@@ -109268,9 +110622,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean "for all frames".
- Pixel Measures Macro - - specifies the Attributes of the Pixel Measures Functional Group Macro. + Pixel Measures Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -109323,7 +110677,7 @@ Required if: - Volumetric Properties (0008,9206) is other than DISTORTED or SAMPLED, or + Volumetric Properties (0008,9206) is other than DISTORTED or SAMPLED, and Image Type (0008,0008) Value 3 is not LABEL or OVERVIEW, or SOP Class UID is Segmentation Storage ("1.2.840.10008.5.1.4.1.1.66.4") and Frame of Reference UID (0020,0052) is present, or @@ -109357,7 +110711,7 @@ Required if: - Volumetric Properties (0008,9206) is VOLUME or SAMPLED, or + Volumetric Properties (0008,9206) is VOLUME or SAMPLED, and Image Type (0008,0008) Value 3 is not LABEL or OVERVIEW, or SOP Class UID is Segmentation Storage ("1.2.840.10008.5.1.4.1.1.66.4") and Frame of Reference UID (0020,0052) is present, or @@ -109394,9 +110748,9 @@
Pixel Measures Macro Attributes
- Frame Content Macro - - specifies the Attributes of the Frame Content Functional Group Macro. + Frame Content Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. This Functional Group Macro may only be part of the Per-frame Functional Groups Sequence (5200,9230) Attribute. @@ -109459,7 +110813,7 @@ @@ -109815,10 +111169,10 @@
- Plane Position (Patient) Macro - - specifies the Attributes of the Plane Position (Patient) Functional Group Macro. -
Frame Content Macro Attributes
The point in time that is most representative of when data was acquired for this frame. See and for further explanation. - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL and the SOP Class UID is not "1.2.840.10008.5.1.4.1.1.2.2" or "1.2.840.10008.5.1.4.1.1.4.4" or "1.2.840.10008.5.1.4.1.1.128.1" (Legacy Converted) or 1.2.840.10008.5.1.4.1.1.77.1.6 (VL Whole Slide Microscopy Image Storage). May be present otherwise.
+ Plane Position (Patient) Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -109899,10 +111253,10 @@
- Plane Orientation (Patient) Macro - - specifies the Attributes of the Plane Orientation (Patient) Functional Group Macro. -
Plane Position (Patient) Macro Attributes
+ Plane Orientation (Patient) Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -109970,9 +111324,9 @@
Plane Orientation (Patient) Macro Attributes
- Referenced Image Macro - - specifies the Attributes of the Referenced Image Functional Group Macro. + Referenced Image Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -110059,9 +111413,9 @@
- Derivation Image Macro - - specifies the Attributes of the Derivation Image Functional Group Macro. + Derivation Image Macro + + specifies the Attributes of the , which is used as a Functional Group Macro.
Referenced Image Macro Attributes
@@ -110258,9 +111612,9 @@
Derivation Image Macro Attributes
- Cardiac Synchronization Macro - - specifies the Attributes of the Cardiac Synchronization Functional Group Macro. + Cardiac Synchronization Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -110496,9 +111850,9 @@
- Frame Anatomy Macro - - specifies the Attributes of the Frame Anatomy Functional Group Macro. + Frame Anatomy Macro + + specifies the Attributes of the , which is used as a Functional Group Macro.
Cardiac Synchronization Macro Attributes
@@ -110591,7 +111945,7 @@ Anatomic Region Modifier Sequence (0008,2220) D. - + Primary Anatomic Structure Modifier Sequence (0008,2230) D. @@ -110601,9 +111955,9 @@
Frame Anatomy Macro Attributes
- Pixel Value Transformation Macro - - specifies the Attributes of the Pixel Value Transformation Functional Group Macro. + Pixel Value Transformation Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. This Macro is equivalent with the Modality LUT transformation in non Multi-frame IODs. @@ -110701,9 +112055,9 @@
- Identity Pixel Value Transformation Macro - - specifies the Attributes of the Identity Pixel Value Transformation Functional Group Macro. + Identity Pixel Value Transformation Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. This Macro constrains the Modality LUT Transformation step in the grayscale rendering pipeline to be an identity transformation. @@ -110816,9 +112170,9 @@
- Frame VOI LUT Macro - - specifies the Attributes of the Frame VOI LUT Functional Group Macro. + Frame VOI LUT Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -110963,9 +112317,9 @@
Frame VOI LUT Macro Attributes
- Frame VOI LUT With LUT Macro - - specifies the Attributes of the Frame VOI LUT With LUT Functional Group Macro. This Macro contains one or more sets of linear or sigmoid window values and/or one or more sets of lookup tables. + Frame VOI LUT With LUT Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. This Macro contains one or more sets of linear or sigmoid window values and/or one or more sets of lookup tables. @@ -111015,9 +112369,9 @@
Frame VOI LUT with LUT Macro Attributes
- Real World Value Mapping Macro + Real World Value Mapping Macro - specifies the Attributes of the Real World Value Mapping Functional Group Macro. + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -111187,7 +112541,7 @@ 1C @@ -111299,7 +112653,7 @@ Real World Value Representation
Real World Value Mapping Sequence - The Items in the Real World Value Mapping Sequence (0040,9096) may be used to translate stored values into real world values when there is such a relationship. The Real World Value Mapping Sequence (0040,9096) is independent of the Modality LUT (or Pixel Value Transformation Macro), as illustrated in . + The Items in the Real World Value Mapping Sequence (0040,9096) may be used to translate stored values into Real World Values when there is such a relationship. The Real World Value Mapping Sequence (0040,9096) is independent of the Modality LUT (or Pixel Value Transformation Macro), as illustrated in . Each Item specifies the range of stored values as well as the associated mapping function. Each Item can specify either a linear mapping, using Real World Value Slope (0040,9225) and Real World Value Intercept (0040,9224), or a non-linear mapping using Real World Value LUT Data (0040,9212). More than one Real World Value Mapping Item is allowed. The range of stored pixel values specified by different Real Value World Mapping Sequence (0040,9096) Items can overlap (as illustrated in the example in ). @@ -111314,15 +112668,15 @@ - For example, MR images may contain data that is not only the result of the physical/chemical properties of the scanned anatomy, but may also contain information that is representing real world values, such as, temperature [in degrees C], flow [in l/min], speed [in m/sec], relative activity [in %], relative contrast enhancement [in %], diffusion [in sec/mm2], etc. + For example, MR images may contain data that is not only the result of the physical/chemical properties of the scanned anatomy, but may also contain information that is representing Real World Values, such as, temperature [in degrees C], flow [in l/min], speed [in m/sec], relative activity [in %], relative contrast enhancement [in %], diffusion [in sec/mm2], etc. In some cases the conversion from Stored Values to Real World Values can be linear (through "slope" and "intercept") or non-linear (through look-up tables). Both transformation methods can be applied to one range of stored values. Overlapped ranges might be used for different representations such as log versus linear scales or for different representations in units such as cm/sec versus mm/sec. Alternative methods can be identified by the labels assigned to the transformations.
- Real World Values Mapping Sequence Attributes + Real World Value Mapping Sequence Attributes The Real World Value First Value Mapped (0040,9216) and Real World Value Last Value Mapped (0040,9211) Attributes describe the range of stored pixel values that are mapped by the Sequence Item. Stored pixel values less than the first value mapped, or greater than the last value mapped have no real value attached. - When the Real World Value Intercept (0040,9224) and Real World Value Slope (0040,9225) Attributes are supplied, the stored value (SV) is converted to a real world value (RV) using the equation: + When the Real World Value Intercept (0040,9224) and Real World Value Slope (0040,9225) Attributes are supplied, the stored value (SV) is converted to a Real World Value (RV) using the equation: RV = (Real World Value Slope) * SV + Real World Value Intercept When the Real World Value LUT Data (0040,9212) Attribute is supplied, Real World Values are obtained via a lookup operation. The stored pixel value of the first value mapped is mapped to the first entry in the LUT Data. Subsequent stored pixel values are mapped to the subsequent entries in the LUT Data up to a stored pixel value equal to the last value mapped. The number of entries in the LUT data is given by: @@ -111334,8 +112688,8 @@ In practice, integer values may well be sufficient to define an input range that exceeds the actual stored floating point pixel value range. The reason to permit floating point alternatives to an integer range is that sometimes the stored floating point values may be very large and exceed what can be specified as an integer value. - The physical units for the real world values obtained from the Sequence Item are given by the Measurement Units Code Sequence (0040,08EA). - The quantity that the real world values represent may be described by the Quantity Definition Sequence (0040,9220), which consists of a list of name-value pairs, in which the coded concept name specifies what aspect of the physical quantity is being described. + The physical units for the Real World Values obtained from the Sequence Item are given by the Measurement Units Code Sequence (0040,08EA). + The quantity that the Real World Values represent may be described by the Quantity Definition Sequence (0040,9220), which consists of a list of name-value pairs, in which the coded concept name specifies what aspect of the physical quantity is being described. @@ -111385,7 +112739,7 @@
- Example of mapping stored values to real world values + Example of Mapping Stored Values to Real World Values @@ -111398,10 +112752,10 @@
- Contrast/Bolus Usage Macro - - specifies the Attributes of the Contrast/Bolus Usage Macro. -
Real World Value Mapping Macro Attributes
- The Slope value in relationship between stored values (SV) and the real world values. + The Slope value in relationship between stored values (SV) and the Real World Values. See for further explanation. Required if Float Pixel Data (7FE0,0008) or Double Float Pixel Data (7FE0,0009) are present or Real World Value LUT Data (0040,9212) is not present.
+ Contrast/Bolus Usage Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -111590,9 +112944,9 @@
Contrast/Bolus Usage Macro Attributes
- Pixel Intensity Relationship LUT Macro - - specifies the Attributes of the Pixel Intensity Relationship LUT Functional Group Macro. + Pixel Intensity Relationship LUT Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -111709,9 +113063,9 @@
- Frame Pixel Shift Macro - - specifies the Attributes of the Frame Pixel Shift Functional Group Macro. + Frame Pixel Shift Macro + + specifies the Attributes of the , which is used as a Functional Group Macro.
Pixel Intensity Relationship LUT Macro Attributes
@@ -111809,9 +113163,9 @@
- Patient Orientation in Frame Macro - - specifies the Attributes of the Patient Orientation in Frame Functional Group Macro. + Patient Orientation in Frame Macro + + specifies the Attributes of the , which is used as a Functional Group Macro.
Frame Pixel Shift Macro Attributes
@@ -111865,10 +113219,10 @@
Patient Orientation in Frame Macro Attributes
- Frame Display Shutter - - specifies the Attributes of the Frame Display Shutter Functional Group Macro. - + Frame Display Shutter + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -111917,9 +113271,9 @@
Frame Display Shutter Macro Attributes
- Respiratory Synchronization Macro - - specifies the Attributes of the Respiratory Synchronization Functional Group Macro. + Respiratory Synchronization Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112160,10 +113514,10 @@
- Irradiation Event Identification Macro - - specifies the Attributes containing the Irradiation Event Identification Functional Group Macro. -
Respiratory Synchronization Macro Attributes
+ Irradiation Event Identification Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -112215,9 +113569,9 @@
Irradiation Event Identification Macro Attributes
- Radiopharmaceutical Usage Macro - - specifies the Attributes of the Radiopharmaceutical Usage Functional Group Macro. + Radiopharmaceutical Usage Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112269,9 +113623,9 @@
Radiopharmaceutical Usage Macro Attributes
- Patient Physiological State Macro - - specifies the Attributes of the Patient Physiological State Functional Group Macro, which describes the physiological state of the patient. + Patient Physiological State Macro + + specifies the Attributes of the , which is used as a Functional Group Macro, which describes the physiological state of the patient. @@ -112338,10 +113692,10 @@
Patient Physiological State Macro Attributes
- Plane Position (Volume) Macro - - specifies the Attributes of the Plane Position (Volume) Functional Group Macro. - + Plane Position (Volume) Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -112393,10 +113747,10 @@
Plane Position (Volume) Macro Attributes
- Plane Orientation (Volume) Macro - - specifies the Attributes of the Plane Orientation (Volume) Functional Group Macro. - + Plane Orientation (Volume) Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. +
@@ -112448,9 +113802,9 @@
Plane Orientation (Volume) Macro Attributes
- Temporal Position Macro - - specifies the Attributes of the Temporal Position Functional Group Macro. + Temporal Position Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112503,9 +113857,9 @@
Temporal Position Macro Attributes
- Image Data Type Macro - - specifies the Attributes of the Image Data Type Functional Group Macro. + Image Data Type Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112624,81 +113978,81 @@ TISSUE_INTENSITY - + Tissue intensity typically displayed as grayscale (e.g., B-mode). + + - + Velocity (Doppler shifts) of tissue. + + - + Velocity (Doppler shifts) of blood flow. + + - + Power contained in the Doppler signal. + + - + Directional power contained in the Doppler signal. + + - + Statistical variance of blood velocity relative to mean. + + - + Scalar value related to the elastic properties of the tissue. + + - + Scalar value related to the volume of blood perfusing into tissue. + + - + Speed of sound in tissue. + + - + Reduction in strength of ultrasound signal as the wave traverses through the medium. + +
Image Data Type Macro Attributes
- Tissue intensity typically displayed as grayscale (e.g., B-mode) -
TISSUE_VELOCITY - Velocity (Doppler shifts) of tissue -
FLOW_VELOCITY - Velocity (Doppler shifts) of blood flow -
FLOW_POWER - Power contained in the Doppler signal -
DIRECTION_POWER - Directional power contained in the Doppler signal -
FLOW_VARIANCE - Statistical variance of blood velocity relative to mean -
ELASTICITY - Scalar value related to the elastic properties of the tissue -
PERFUSION - Scalar value related to the volume of blood perfusing into tissue -
SOUND_SPEED - Speed of sound in tissue -
ATTENUATION - Reduction in strength of ultrasound signal as the wave traverses through the medium -
@@ -112729,19 +114083,19 @@ - An example of an Attribute that might be included in the Unassigned Shared Converted Attributes Macro is Filter Type (0018,1160), which typically would be the same for all Classic CT images in a set, and is not included in any modality-specific Module or Functional Group Macro. + An example of an Attribute that might be included in the is Filter Type (0018,1160), which typically would be the same for all Classic CT images in a set, and is not included in any modality-specific Module or Functional Group Macro. - An example of an Attribute that might be included in the Unassigned Per-Frame Converted Attributes Macro is Slice Location (0020,1041), which typically would be different for each Classic CT image in a set, and is not included in any modality-specific Module or Functional Group Macro. + An example of an Attribute that might be included in the is Slice Location (0020,1041), which typically would be different for each Classic CT image in a set, and is not included in any modality-specific Module or Functional Group Macro. - An example of an Attribute that might be included in the Unassigned Shared Converted Attributes Macro is Series Number (0020,0011), which typically would be the same for all Classic CT images in a set (but is not required to be), and will be replaced with a different value in the top-level Data Set, and hence if the original is to be preserved, needs to be recorded. + An example of an Attribute that might be included in the is Series Number (0020,0011), which typically would be the same for all Classic CT images in a set (but is not required to be), and will be replaced with a different value in the top-level Data Set, and hence if the original is to be preserved, needs to be recorded. - An example of an Attribute that might be included in the Unassigned Per-Frame Converted Attributes Macro is Instance Number (0020,0013), which typically would be different for each Classic CT image in a set, and will be replaced with a different value in the top-level Data Set, and hence if the original is to be preserved, needs to be recorded. + An example of an Attribute that might be included in the is Instance Number (0020,0013), which typically would be different for each Classic CT image in a set, and will be replaced with a different value in the top-level Data Set, and hence if the original is to be preserved, needs to be recorded. - The UIDs of the converted Instances are recorded in the Conversion Source Attributes Sequence, and are not included in the Unassigned Shared and Per-Frame Converted Attributes Macros. + The UIDs of the converted Instances are recorded in the Conversion Source Attributes Sequence, and are not included in the and . @@ -112750,9 +114104,9 @@ The necessary Private Creator Data Element within each Sequence Item accompanies Private Data Elements. There is no requirement to preserve the private block of Data Elements used in the Classic images to be converted. Nor is there a requirement that a Private Data Element use the same private block in all of the Classic images. Matching of Private Attribute Values for the purpose of determining whether they are shared or per-frame may be performed using the equivalent meaning if the Value Representation is Explicit and not UN, or known through other means, otherwise, byte matching of the UN VR shall be performed.
- Unassigned Shared Converted Attributes Macro - - specifies the Attributes of the Unassigned Shared Converted Attributes Functional Group Macro. + Unassigned Shared Converted Attributes Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112792,9 +114146,9 @@
Unassigned Shared Converted Attributes Macro Attributes
- Unassigned Per-Frame Converted Attributes Macro - - specifies the Attributes of the Unassigned Per-Frame Converted Attributes Functional Group Macro. + Unassigned Per-Frame Converted Attributes Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112834,9 +114188,9 @@
Unassigned Per-Frame Converted Attributes Macro Attributes
- Image Frame Conversion Source Macro - - specifies the Attributes of the Image Frame Conversion Source Functional Group Macro. + Image Frame Conversion Source Macro + + specifies the Attributes of the , which is used as a Functional Group Macro. @@ -112889,7 +114243,7 @@
Stored Value Color Range Macro - defines the Attributes of the Stored Value Color Range Functional Group Macro + defines the Attributes of the , which is used as a Functional Group Macro.
Image Frame Conversion Source Macro Attributes
@@ -112978,9 +114332,9 @@
- Frame Usefulness Macro - - specifies the Attributes of the Frame Usefulness Functional Group Macro, related to the clinical usefulness of the current frame. + Frame Usefulness Macro + + specifies the Attributes of the , which is used as a Functional Group Macro, related to the clinical usefulness of the current frame.
Stored Value Color Range Macro Attributes
@@ -113077,9 +114431,9 @@
Frame Usefulness Functional Group Macro Attributes
- Camera Position Macro - - specifies the Attributes of the Camera Position Functional Group Macro, related to the position of the camera or the acquisition device for the current frame, with regards to the patient. + Camera Position Macro + + specifies the Attributes of the , which is used as a Functional Group Macro, related to the position of the camera or the acquisition device for the current frame, with regards to the patient. @@ -113149,7 +114503,7 @@ @@ -113164,7 +114518,7 @@ @@ -113179,7 +114533,7 @@ @@ -113201,9 +114555,9 @@
Camera Position Functional Group Macro Attributes
Position of the viewpoint in volume space. - A point (x,y,z) in the Frame Reference Coordinate System referenced in the Frame of Reference Module. + A point (x,y,z) in the Frame Reference Coordinate System referenced in the .
Point the viewpoint is looking at. - A point (x,y,z) in the Frame Reference Coordinate System referenced in the Frame of Reference Module. + A point (x,y,z) in the Frame Reference Coordinate System referenced in the .
Vertical orientation of the view. - A vector (x,y,z) in the Frame Reference Coordinate System referenced in the Frame of Reference Module. + A vector (x,y,z) in the Frame Reference Coordinate System referenced in the .
- Time of Frame Macro - - specifies the Attributes of the Time of Frame Functional Group Macro, related to the time of frame. + Time of Frame Macro + + specifies the Attributes of the , which is used as a Functional Group Macro, related to the time of frame. @@ -113651,16 +115005,16 @@ If Dimension Organization Type (0020,9311) is absent or has a value of TILED_SPARSE, then the spatial location of each tile is explicitly encoded using information in the Per-Frame Functional Group Sequence, and the recipient shall not make any assumption about the spatial position or optical path or order of the encoded frames but shall rely on the values of the relevant Per-Frame Functional Group Macro. Images with an Image Type (0008,0008) Value 3 of THUMBNAIL, LABEL or OVERVIEW are single frame and may have a spatial extent that is not the same as the Total Pixel Matrix, so Dimension Organization Type (0020,9311) is not applicable. - The same previously applied to images with an Image Type (0008,0008) Value 3 of LOCALIZER, which has been retired. See PS3.3-2021c. + The same previously applied to images with an Image Type (0008,0008) Value 3 of LOCALIZER, which has been retired. See PS3.3-2021c.
Physiological Synchronization
- Cardiac Synchronization Module - - specifies the Attributes of the Cardiac Synchronization Module. + Cardiac Synchronization Module + + specifies the Attributes of the .
Time of Frame Functional Group Macro Attributes
@@ -113932,7 +115286,7 @@ Low R-R Value (0018,1081), High R-R Value (0018,1082), Intervals Acquired (0018,1083) and Intervals Rejected (0018,1084) in this Module apply to the entire Image. The Cardiac Synchronization Sequence (0018,9118) in the Cardiac Synchronization Functional Group uses the same Attributes and specifies the values for a single frame.
- Attribute Descriptions + Cardiac Synchronization Module Attribute Descriptions
Cardiac Framing Type Cardiac Framing Type (0018,1064) is the mechanism used to select the data acquired to construct the frames within a specified cardiac timing interval. @@ -113961,9 +115315,9 @@
- Respiratory Synchronization Module - - specifies the Attributes of the Respiratory Synchronization Module. + Respiratory Synchronization Module + + specifies the Attributes of the .
Cardiac Synchronization Module Attributes
@@ -114171,9 +115525,9 @@
Respiratory Synchronization Module Attributes
- Bulk Motion Synchronization Module - - specifies the Attributes of the Bulk Motion Synchronization Module. + Bulk Motion Synchronization Module + + specifies the Attributes of the . @@ -114290,9 +115644,9 @@
Supplemental Palette Color Lookup Table Module - This Module is used in conjunction with Multi-frame IODs that use RGB color in a number of frames. The value of Pixel Presentation (0008,9205) for such frames equals COLOR. - specifies the Attributes that describe the Lookup table data. + specifies the Attributes of the . + This Module is used in conjunction with Multi-frame IODs that use RGB color in a number of frames. The value of Pixel Presentation (0008,9205) for such frames equals COLOR.
Bulk Motion Synchronization Module Attributes
@@ -114401,7 +115755,8 @@
Patient Orientation Module - This section describes Attributes of the Patient Orientation Module by describing the patient orientation related to gravity and equipment. contains IOD Attributes that describe the Patient Orientation. + + specifies the Attributes of the , which describe the patient orientation related to gravity and equipment.
Supplemental Palette Color Lookup Table Module Attributes
@@ -114437,7 +115792,8 @@
Image - Equipment Coordinate Relationship Module - This section describes the Image - Equipment Coordinate Relationship Module. contains the Attributes that specify how the equipment (e.g., gantry) and patient oriented coordinate system (in conjunction with Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) Attributes) are related. + + specifies the Attributes of the , which specify how the equipment (e.g., gantry) and patient oriented coordinate system (in conjunction with Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) Attributes) are related.
Patient Orientation Module Attributes
@@ -114745,9 +116101,9 @@
- Specimen Module + Specimen Module - specifies the Attributes that identify one or more Specimens being imaged. + specifies the Attributes of the , which identify one or more Specimens being imaged.
Image - Equipment Coordinate Relationship Module Attributes
@@ -115073,9 +116429,9 @@ 3 - + Thickness in mm of container component. + + @@ -115347,7 +116703,7 @@
Specimen Module Attributes
- Thickness in mm of container component -
>Container Component Material @@ -115307,12 +116663,12 @@ -Original anatomic location in patient of specimen. This location may be identical to that of the parent specimen, may be further refined by modifiers depending on the sampling procedure for this specimen, or may be a distinct concept. - + Original anatomic location in patient of specimen. This location may be identical to that of the parent specimen, may be further refined by modifiers depending on the sampling procedure for this specimen, or may be a distinct concept. + -B - - + B + +
- Specimen Module Attributes + Specimen Module Attribute Descriptions
Container Identifier and Specimen Identifier "Specimen" is the role played by a discrete physical object (or a collection of objects that are considered as a unit) that is the subject of pathology examination. @@ -115382,9 +116738,9 @@
- Enhanced Palette Color Lookup Table Module + Enhanced Palette Color Lookup Table Module - specifies the Attributes that define data flow through the Enhanced Blending and Display Pipeline. See for an overview of the Enhanced Blending and Display Pipeline. + specifies the Attributes of the , which define data flow through the Enhanced Blending and Display Pipeline. See for an overview of the Enhanced Blending and Display Pipeline. @@ -116005,7 +117361,7 @@ value of that component. All inputs to the Blending Operation are normalized to the range 0.0 to 1.0, inclusive, even if they are fixed integer values that had been the entries in a lookup table.Each of the Weight inputs to the blending operation is the output of a corresponding Blending LUT Transfer Function, which is selectable as either a constant or a derivation of the data frame values as described in .The RGB output from the Blending Operation is clamped to limit each color component (R, G, and B) to fall within the range 0.0 to 1.0, inclusive. The clamping function simply sets the value of any color component to 1.0 if the output from the Blending operation for that component exceeds 1.0. The RGB output of the clamping function is made available for use in rendering and slicing algorithms. Further, the output of the clamping function is transformed by the Profile Connection Space Transformation to device independent color values (PCS-values) for presentation. - If the input data frame values are representative of real world data, then they can be mapped to the real world values and units using the Real World Value Mapping Macro. + If the input data frame values are representative of real world data, then they can be mapped to the Real World Values and units using the . describes a number of examples of the Enhanced Blending and Display Pipeline with specific Attribute values for each example that invoke particular data flows through the pipeline. @@ -116131,7 +117487,7 @@
Floating Point Image Pixel Module - describes the . This Module differs from the + specifies the Attributes of the . This Module differs from the in that: @@ -116330,7 +117686,7 @@
Double Floating Point Image Pixel Module - describes the . This Module differs from the + specifies the Attributes of the . This Module differs from the in that: @@ -116531,7 +117887,8 @@
Real-Time Bulk Data Flow Module - This module references pixels/waveforms that are not contained within the DICOM data set but conveyed in the associated Flows, as described in . + + specifies the Attributes of the , which references pixels/waveforms that are not contained within the DICOM data set but conveyed in the associated Flows, as described in . specifies the Attributes for the Real-Time Bulk Data Flow Module.
Enhanced Palette Color Lookup Table Module Attributes
@@ -116647,7 +118004,7 @@
In case the Source is producing different Flows of the same Essence (e.g., video with two different sampling rates), the sequence must include at least the audio or video Flow that is associated with the present RTV Flow, and may in addition include the other Flow(s), enabling the receiver to subscribe to another Flow.
- Real-Time Bulk Data Flow Module Attributes + Real-Time Bulk Data Flow Module Attribute Descriptions
Source Identifier The Source Identifier(0034,0005) is a Universally Unique Identifier (UUID). The value is 128 bits long encoded in binary. It shall correspond to the value of the Source Identifier of the related bulk data Flow which may contain this Source Identifier in the RTP Extended Header. In case such Source Identifier is not present in the related bulk data flow, this Source Identifier shall be set to enable multiple IODs to refer the same Source. @@ -116667,9 +118024,9 @@
- Current Frame Functional Groups Module + Current Frame Functional Groups Module - defines the Attributes related to the current frame when the IOD is transported using Real-Time Communication. It corresponds to the "per-frame" Attribute for the non-Real-Time IODs. + specifies the Attributes of the , which are related to the current frame when the IOD is transported using Real-Time Communication. It corresponds to the "per-frame" Attribute for the non-Real-Time IODs. The group number (0006H) of the Sequence containing the Attributes of the Current Frame Functional Groups Module is used to contain Attributes that are specific to real-time transfer. If this information needs to be kept in a persistent object, its contents have to be copied into an Attribute that has a group number of 0008H or higher. The Current Frame Functional Groups Module is relative to the dynamic part of the RTP Payload. Its group number is lower than that of other Attributes in order to be placed before the static part of the RTP Payload, but higher than the Attributes of the RTV Metadata Information, in order to be placed after the header of the RTP Payload, as is done in . @@ -116720,7 +118077,7 @@
- Current Frame Functional Groups Module Attributes + Current Frame Functional Groups Module Attribute Descriptions
Frame Origin Timestamp Frame Origin Timestamp (0034,0007) contains 10 bytes conforming with the IEEE 1588:2008 (PTPv2) standard. IEEE 1588:2008 represents seconds and nanoseconds since Epoch, defined as 1 of January, 1970, at 00:00:00 TAI (International Atomic Time). The first 6 bytes contain the number of seconds, and the last 4 bytes contain the number of nanoseconds. The Time Source and Time Distribution Protocol values defined in describe how the time was obtained. @@ -116730,9 +118087,9 @@
- Real-Time Acquisition Module + Real-Time Acquisition Module - defines the Attributes related to all frames when the IOD is transported using Real-Time Communication. + specifies the Attributes of the , which are related to all frames when the IOD is transported using Real-Time Communication. @@ -116754,7 +118111,7 @@
Real-Time Acquisition Module Attributes
- Shared Functional Group Sequence + Shared Functional Groups Sequence (5200,9229) @@ -116810,7 +118167,7 @@
- Real-Time Acquisition Module Attributes + Real-Time Acquisition Module Attribute Descriptions
Stereo Pairs Present Stereo Pairs Present (0022,0028) shall have the value of YES when frame is encoded as left and right stereoscopic pair. @@ -116820,16 +118177,16 @@
Patient Summary Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Content Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Palette Color Lookup Table Module - - specifies the Attributes that describe the Lookup table data for images with Palette Color photometric interpretation. + + specifies the Attributes of the , which describe the Lookup table data for images with Palette Color photometric interpretation. When the is present in an Image IOD, the conditional requirements for the use of Palette Color Lookup Table Data (0028,1201-1203) and Segmented Palette Color Lookup Table Data (0028,1221-1223), described in , shall take precedence over the conditional requirements described in the (see ). When the is present in a Presentation State IOD, the Palette Color Lookup Table Data (0028,1201-1203) Attributes are mandatory and the Segmented Palette Color Lookup Table Data (0028,1221-1223) shall not be present. When the is present in a Color Palette IOD, either the Palette Color Lookup Table Data (0028,1201-1203) or Segmented Palette Color Lookup Table Data (0028,1221-1223) Attributes may be used. When the is present in a Color Palette IOD, the 3rd value of Palette Color Lookup Table Descriptor (0028,1101-1103) (i.e, the number of bits for each entry in the Lookup Table Data) shall be 8. @@ -117201,6 +118558,239 @@
+
+ Common Acquisition IE Modules + The following Acquisition IE Modules are common to all Composite Image IODs that reference the Acquisition IE. +
+ General Acquisition Module + + specifies the Attributes of the , which identify and describe general information about an Acquisition. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
General Acquisition Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Acquisition UID + + (0008,0017) + + 3 + + Unique identification of the single continuous gathering of data over a period of time that resulted in this instance. +
+ Acquisition Number + + (0020,0012) + + 3 + + A number identifying the single continuous gathering of data over a period of time that resulted in this instance. +
+ Acquisition Date + + (0008,0022) + + 3 + + The date the acquisition of data that resulted in this instance started. +
+ Acquisition Time + + (0008,0032) + + 3 + + The time the acquisition of data that resulted in this instance started. +
+ Acquisition DateTime + + (0008,002A) + + 3 + + The date and time that the acquisition of data that resulted in this instance started. + + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). + +
+ Acquisition Duration + + (0018,9073) + + 3 + + Duration of the single continuous gathering of data over a period of time that resulted in this instance, in seconds. + + E.g., to acquire the data for an image, such as for an MR image, to run the prescribed pulse sequence. + +
+ Images in Acquisition + + (0020,1002) + + 3 + + Number of images that resulted from this acquisition of data. +
+ Irradiation Event UID + + (0008,3010) + + 3 + + Unique identification of the irradiation event(s) associated with the acquisition of this instance. See . + + There is not necessarily a 1:1 relationship between an Irradiation Event and an Acquisition. An Acquisition may not involve the use of ionizing radiation, in which case this Attribute would be absent. A single Acquisition may result from more than one Irradiation Event, e.g., when there are multiple X-Ray sources. More than one Irradiation Event may be involved in a single Acquisition, e.g., when there is a quiescent period between Irradiation Events during which data gathering continues. + +
+
+ General Acquisition Module Attribute Descriptions +
+ Irradiation Event UID + An irradiation event is the loading of X-Ray equipment caused by a single continuous actuation of the equipment's irradiation switch, from the start of the loading time of the first pulse until the loading time trailing edge of the final pulse. Any on-off switching of the irradiation source during the event shall not be treated as separate events, rather the event includes the time between start and stop of irradiation as triggered by the user. E.g., a pulsed fluoro X-Ray acquisition shall be treated as a single irradiation event. +
+
+
+ + +
+
+ Common Multi-Resolution Pyramid IE Modules + The following Multi-Resolution Pyramid IE Modules are common to all Composite Image IODs that reference the Multi-Resolution Pyramid IE. +
+ Multi-Resolution Pyramid Module + + specifies the Attributes of the , which identify and describe general information about a Multi-Resolution Pyramid. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Multi-Resolution Pyramid Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Pyramid UID + + (0008,0019) + + 1 + + Unique identifier of a multi-resolution representation of an image. +
+ Pyramid Label + + (0020,0027) + + 3 + + User-defined label identifying a multi-resolution representation of an image. +
+ Pyramid Description + + (0008,1088) + + 3 + + User-defined description of a multi-resolution representation of an image. +
+
+
Modality Specific Modules @@ -117208,9 +118798,9 @@ Computed Radiography Modules This Section describes Computed Radiography Series and Image Modules. These Modules contain Attributes that are specific to Computed Radiography images. There is no Computed Radiography Equipment Module.
- CR Series Module + CR Series Module - contains IOD Attributes that describe a computed radiography Series performed on the patient. + specifies the Attributes of the , which describe a computed radiography Series performed on the patient. @@ -117241,9 +118831,9 @@ 2 - + Text description of the part of the body examined. See for Defined Terms. + + - + Label for the type of filter inserted into the X-Ray beam. + + - + Label of the type of storage phosphor plates used in this Series. + + - + Label of type of phosphor on the plates. + +
CR Series Module Attributes
- Text description of the part of the body examined. See for Defined Terms -
View Position @@ -117332,9 +118922,9 @@ 3 - Label for the type of filter inserted into the X-Ray beam -
Collimator/grid Name @@ -117374,9 +118964,9 @@ 3 - Label of the type of storage phosphor plates used in this Series -
Phosphor Type @@ -117388,16 +118978,16 @@ 3 - Label of type of phosphor on the plates -
- CR Image Module + CR Image Module - contains IOD Attributes that describe computed radiography images. + specifies the Attributes of the , which describe computed radiography images. @@ -117457,9 +119047,9 @@ 3 - + Peak kilo voltage output of the X-Ray generator used. + + - + The ID or serial number of the sensing plate upon which the image was acquired. + + - + Time of X-Ray exposure in msec. + + - + Describes device-specific processing associated with the image (e.g., Organ Description). + + - + Code representing the device-specific processing associated with the image (e.g., CR Organ Filtering code). + + - + Total number of X-Ray exposures that have been made on the plate identified in Plate ID (0018,1004). + + @@ -117825,7 +119415,8 @@ This Section describes the CT Image Module. This Module contains all Attributes that are specific to CT images.
CT Image Module - The table in this Section contains IOD Attributes that describe CT images. + + specifies the Attributes of the , which describe CT images.
CR Image Module Attributes
- Peak kilo voltage output of the X-Ray generator used -
Plate ID @@ -117471,9 +119061,9 @@ 3 - The ID or serial number of the sensing plate upon which the image was acquired -
Distance Source to Detector @@ -117519,9 +119109,9 @@ 3 - Time of X-Ray exposure in msec -
X-Ray Tube Current @@ -117615,9 +119205,9 @@ 3 - Describes device-specific processing associated with the image (e.g., Organ Description) -
Acquisition Device Processing Code @@ -117629,9 +119219,9 @@ 3 - Code representing the device-specific processing associated with the image (e.g., CR Organ Filtering code) -
Cassette Orientation @@ -117755,9 +119345,9 @@ 3 - Total number of X-Ray exposures that have been made on the plate identified in Plate ID (0018,1004) -
Relative X-Ray Exposure @@ -117788,7 +119378,7 @@ Read out sensitivity. - This value is manufacturer-specific. DICOM specifies Standard Attributes in 'Exposure Index Macro', which are recommended. + This value is manufacturer-specific. DICOM specifies Standard Attributes in the , which are recommended.
@@ -118030,9 +119621,9 @@ 2 - + A number identifying the single continuous gathering of data over a period of time that resulted in this image. + + + @@ -118320,9 +119911,9 @@ 3 - + A label describing the convolution kernel or algorithm used to reconstruct the data. + +
CT Image Module Attributes
- A number identifying the single continuous gathering of data over a period of time that resulted in this image -
Scan Options @@ -118045,7 +119636,7 @@ Parameters of scanning sequence. -
@@ -118125,8 +119716,8 @@ Distance in mm from source to detector center. This value is traditionally referred to as Source Image Receptor Distance (SID). - Shall not be present if this Attribute is present in Multi-energy CT Acquisition Sequence (0018,9362) and the value of this Attribute is not the same in all Items of the Multi-energy CT Acquisition Sequence (0018,9362). + Shall not be present if this Attribute is present in Multi-energy CT Acquisition Sequence (0018,9362) and the value of this Attribute is not the same in all Items of the Multi-energy CT Acquisition Sequence (0018,9362).
- A label describing the convolution kernel or algorithm used to reconstruct the data -
Revolution Time @@ -118815,7 +120406,7 @@
- CT Image Attribute Descriptions + CT Image Module Attribute Descriptions
Image Type For CT Images, Image Type (0008,0008) is specified to be Type 1. @@ -118985,7 +120576,8 @@
Multi-energy CT Image Module - The table in this Section contains IOD Attributes that describe a Multi-energy CT image. + + specifies the Attributes of the , which describe a Multi-energy CT image. @@ -119016,7 +120608,7 @@ 1 @@ -119119,7 +120711,8 @@
Multi-energy CT Image Module Attributes
- The attributes of a Multi-energy CT Image acquisition. + The Attributes of a Multi-energy CT Image acquisition. One Item shall be included in this Sequence.
Multi-energy CT X-Ray Source Macro - Attributes for the CT X-Ray Source(s). + + specifies the Attributes of the , which describe the CT X-Ray Source(s). @@ -119310,12 +120903,13 @@
Multi-energy CT X-Ray Source Macro Attributes
Multi-energy X-Ray Source Description - Each item in the Multi-energy CT X-Ray Source Sequence (0018,9365) might describe either a constant source, a constant source with energy selective filter or one output corresponding to a specific energy of a KV switching source. The attributes will refer to a source, meaning one item in the Multi-energy CT X-Ray Source Sequence (0018,9365). The attributes use the phrase "physical X-Ray Source" when it is necessary to refer to the actual device (tube) rather than the current item. + Each item in the Multi-energy CT X-Ray Source Sequence (0018,9365) might describe either a constant source, a constant source with energy selective filter or one output corresponding to a specific energy of a KV switching source. The Attributes will refer to a source, meaning one item in the Multi-energy CT X-Ray Source Sequence (0018,9365). The Attributes use the phrase "physical X-Ray Source" when it is necessary to refer to the actual device (tube) rather than the current item.
Multi-energy CT X-Ray Detector Macro - Attributes for the CT X-Ray Detector(s). + + specifies the Attributes of the , which describe the CT X-Ray Detector(s). @@ -119482,7 +121076,7 @@
Multi-energy CT X-Ray Detector Macro Attributes
- Multi-energy X-Ray Detector Description + Multi-energy X-Ray Detector Sequence Each item in the Multi-energy CT X-Ray Detector Sequence (0018,936F) might describe either an integrating detector or one output corresponding to a specific spectrum of a physical detector like: @@ -119495,13 +121089,13 @@ One energy threshold of a photon counting detector. - The sequence attribute descriptions will refer to a detector, meaning one item in the Multi-energy CT X-Ray Detector Sequence (0018,936F). The attributes use the phrase "physical detector" when it is necessary to refer to the actual device rather than the current item. + The Sequence Attribute descriptions will refer to a detector, meaning one item in the Multi-energy CT X-Ray Detector Sequence (0018,936F). The Attributes use the phrase "physical detector" when it is necessary to refer to the actual device rather than the current item.
Multi-energy CT Path Macro - A Multi-energy CT Path is an X-Ray source paired with a corresponding X-Ray detector for a particular energy level. - + + specifies the Attributes of the , which describe a Multi-energy CT Path. A Multi-energy CT Path is an X-Ray source paired with a corresponding X-Ray detector for a particular energy level. @@ -119589,9 +121183,9 @@ MR ModulesThis Section describes the MR Image Module. This Module contains all Attributes that are specific to MR images.
- MR Image Module + MR Image Module - contains the Attributes that describe MR images. + specifies the Attributes of the , which describe MR images.
Multi-energy CT Path Macro Attributes
@@ -119978,9 +121572,9 @@ 2C - + Time, in msec, between peak of the R wave and the peak of the echo produced. In the case of segmented k-space, the TE(eff) is the time between the peak of the echo that is used to cover the center of k-space. Required for Scan Options (0018,0022) that include heart gating (e.g., CG, PPG, etc.). + + - + Number of times a given pulse sequence is repeated before any parameter is changed. + + - + Precession frequency in MHz of the nucleus being addressed. + + - + Nucleus that is resonant at the imaging frequency. Examples: 31P, 1H. + + - + Nominal field strength of MR magnet, in Tesla. + + - + Average R-R interval used for the scans, in msec. + + - + R-R interval low limit for beat rejection, in msec. + + - + R-R interval high limit for beat rejection, in msec. + +
MR Image Module Attributes
- Time, in msec, between peak of the R wave and the peak of the echo produced. In the case of segmented k-space, the TE(eff) is the time between the peak of the echo that is used to cover the center of k-space. Required for Scan Options (0018,0022) that include heart gating (e.g., CG, PPG, etc.) -
Sequence Name @@ -120035,9 +121629,9 @@ 3 - Number of times a given pulse sequence is repeated before any parameter is changed -
Imaging Frequency @@ -120049,9 +121643,9 @@ 3 - Precession frequency in MHz of the nucleus being addressed -
Imaged Nucleus @@ -120063,9 +121657,9 @@ 3 - Nucleus that is resonant at the imaging frequency. Examples: 31P, 1H -
Echo Number(s) @@ -120091,9 +121685,9 @@ 3 - Nominal field strength of MR magnet, in Tesla -
Number of Phase Encoding Steps @@ -120161,9 +121755,9 @@ 3 - Average R-R interval used for the scans, in msec -
Beat Rejection Flag @@ -120204,9 +121798,9 @@ 3 - R-R interval low limit for beat rejection, in msec -
High R-R Value @@ -120218,9 +121812,9 @@ 3 - R-R interval high limit for beat rejection, in msec -
Intervals Acquired @@ -120577,11 +122171,11 @@
- MR Image Attribute Descriptions + MR Image Module Attribute Descriptions
Image Type For MR Images, Image Type (0008,0008) is specified to be Type 1. - + Defined Terms for Value 3: DENSITY MAP @@ -120732,7 +122326,7 @@
NM/PET Patient Orientation Module - specifies the Attributes that describe the NM/PET Patient Orientation. + specifies the Attributes of the NM/PET Patient Orientation Module, which describe the NM/PET Patient Orientation. @@ -120848,7 +122442,7 @@
NM/PET Patient Orientation Module Attributes
- NM/PET Patient Orientation Attribute Descriptions + NM/PET Patient Orientation Module Attribute Descriptions
Patient Orientation Code Sequence The Patient Orientation Code Sequence (0054,0410) is used to describe the orientation of the patient with respect to gravity, and is independent of the position in the gantry. @@ -120865,9 +122459,9 @@
- NM Image Pixel Module + NM Image Pixel Module - specifies the Attributes that describe the pixel data of a NM image. + specifies the Attributes of the , which describe the pixel data of a NM image. @@ -120989,7 +122583,7 @@
NM Image Pixel Module Attributes
- NM Image Pixel Attribute Descriptions + NM Image Pixel Module Attribute Descriptions
Photometric Interpretation @@ -121014,7 +122608,7 @@
NM Multi-frame Module - specifies the Attributes of a NM Multi-frame Image. This Module is always included in a NM SOP Instance, even if there is only one frame in the image. + specifies the Attributes of the NM Multi-frame Image. This Module is always included in a NM SOP Instance, even if there is only one frame in the image. A NM Image object is always a multi-dimensional multi-frame image. The order and organization of the frames within each image is defined by the Frame Increment Pointer (0028,0009). The Frame Increment Pointer (0028,0009) references one or more indexing vectors. An indexing vector is a 1 dimensional array with exactly one element for each frame in the image. The value of the nth element in the indexing vector represents the index for the nth frame, in that dimension. Indices are always numbered starting from 1. The scheme for encoding a multi-dimensional array of frames into a single image object is as follows. First, the definition of the Data Element called the Frame Increment Pointer is changed so that it can be multi-valued (i.e., its VM is now 1-n). Each value of Frame Increment Pointer represents one of the dimensions of the array, with the last value representing the most rapidly changing index. Each value of Frame Increment Pointer is the Tag of a Data Element that is an indexing vector. An indexing vector is a 1 dimensional array with exactly one element for each frame in the image. The value of the nth element in the indexing vector represents the index for the nth frame, in that dimension. For example, suppose you are encoding a Dynamic image consisting of 2 phases (containing 5 and 2 frames, respectively), from each of two detectors, using one @@ -121531,7 +123125,7 @@ Per the rules in , if an Attribute of Type 1C or 2C is not required, it shall not be included.
- NM Multi-frame Attribute Descriptions + NM Multi-frame Module Attribute Descriptions
Frame Increment Pointer By definition, NM Images are multi-dimensional Multi-frame Images. The value of Frame Increment Pointer (0028,0009) contains the Tag for one or more frame indexing vectors. This determines the number of dimensions of frame indices in the image, and the order in which these indices vary from one frame to the next, with the last Tag indicating the most rapidly changing index. The Enumerated Values for Frame Increment Pointer (0028,0009) are determined by Image Type (0008,0008) Value 3, as shown in . @@ -121665,9 +123259,9 @@
- NM Image Module + NM Image Module - contains the Attributes that describe Nuclear Medicine Images. + specifies the Attributes of the , which describe Nuclear Medicine Images. @@ -122092,7 +123686,7 @@ 3 @@ -122146,7 +123740,7 @@ Content Date (0008,0023) and Content Time (0008,0033) are included in the , , whenever the images are temporally related. For this purpose, all NM Images are considered temporally related, so that these elements are included in an NM Image. - Referenced Overlay Sequence (0008,1130) and Referenced Curve Sequence (0008,1145) were previously included in this Module as optional Attributes but have been retired. See PS3.3-2004. Referenced Image Real World Value Mapping Sequence (0040,9094) was previously used in this Module to enclose the Real World Value Mapping Sequence (0040,9096) but has been retired. See PS3.3-2011. + Referenced Overlay Sequence (0008,1130) and Referenced Curve Sequence (0008,1145) were previously included in this Module as optional Attributes but have been retired. See PS3.3-2004. Referenced Image Real World Value Mapping Sequence (0040,9094) was previously used in this Module to enclose the Real World Value Mapping Sequence (0040,9096) but has been retired. See PS3.3-2011. @@ -122155,7 +123749,7 @@
Image Type For NM images, Image Type (0008,0008) Value 3 is specified to be Type 1. - + Enumerated Values for Value 3: STATIC @@ -122206,7 +123800,7 @@ - + Enumerated Values for Value 4: EMISSION @@ -122280,9 +123874,9 @@
- NM Isotope Module + NM Isotope Module - contains Attributes that describe the isotope administered for the acquisition. + specifies the Attributes of the , which describe the isotope administered for the acquisition.
NM Image Module Attributes
- The mapping of stored values to associated real world values. + The mapping of stored values to associated Real World Values. One or more Items are permitted in this Sequence.
@@ -122822,9 +124416,9 @@
- NM Detector Module + NM Detector Module - contains IOD Attributes that describe Nuclear Medicine Detectors used to produce an image. + specifies the Attributes of the , which describe Nuclear Medicine Detectors used to produce an image.
NM Isotope Module Attributes
@@ -122871,9 +124465,9 @@ 3 - + Label describing the collimator used (LEAP, hires, etc.). + +
NM Detector Module Attributes
- Label describing the collimator used (LEAP, hires, etc.) -
>Collimator Type @@ -123228,7 +124822,7 @@
- NM Detector Attribute Descriptions + NM Detector Module Attribute Descriptions
Focal Distance Focal Distance (0018,1182) for NM Image data is the focal distance, in mm for converging or diverging collimators, measured from the front face of the detector to the focus. Positive values indicate converging and negative values indicate diverging collimators. A value of 0 means infinite distance for parallel collimation. @@ -123503,7 +125097,7 @@
- NM Tomo Acquisition Attribute Descriptions + NM Tomo Acquisition Module Attribute Descriptions
Angular Step Angular Step (0018,1144) is the nominal frame-to-frame incremental angle for TOMO and GATED TOMO acquisition images, defined in degrees. Angular Step (0018,1144) shall be a positive number. Summation of Angular Step values is not defined to give accurate Angular Position or Scan Arc values. The Angular Step is the effective angular spacing between resultant frames of the Multi-framed planar image data. @@ -123511,9 +125105,9 @@
- NM Multi-gated Acquisition Module + NM Multi-gated Acquisition Module - contains Attributes that describe a multi-gated acquisition image performed on the patient. This refers to frames acquired while the patient is connected to a gating device. + specifies the Attributes of the , which describe a multi-gated acquisition image performed on the patient. This refers to frames acquired while the patient is connected to a gating device. @@ -123587,9 +125181,9 @@ 3 - + Number of beats skipped after a detected arrhythmia. + + - + R-R interval lower limit for beat rejection, in msec. + + - + R-R interval upper limit for beat rejection, in msec. + +
NM Multi-Gated Acquisition Module Attributes
- Number of beats skipped after a detected arrhythmia -
Heart Rate @@ -123704,9 +125298,9 @@ 3 - R-R interval lower limit for beat rejection, in msec -
>>High R-R Value @@ -123718,9 +125312,9 @@ 3 - R-R interval upper limit for beat rejection, in msec -
>>Intervals Acquired @@ -123782,7 +125376,7 @@
- NM Multi-gated Acquisition Attribute Descriptions + NM Multi-gated Acquisition Module Attribute Descriptions
Data Information Sequence Data Information Sequence (0054,0063) shall contain a single Item that applies to the sum of all angular views, except when Image Type (0008,0008) Value 3 is GATED TOMO. In this case it shall have either a single Item that applies to the sum of all angular views, or it shall have one Item for each angular view. @@ -123794,9 +125388,9 @@
- NM Phase Module + NM Phase Module - contains Attributes that describe dynamic phases of a dynamic acquisition image performed on the patient. This Module is present only when Image Type (0008,0008), Value 3, is equal to DYNAMIC. A phase is defined as a collection of frames in which the acquisition time per frame and the time delay between frames remains constant. A new phase shall be defined whenever there is a change in the time between frames, the acquisition time per frame, or the position of the patient relative to the detector. + specifies the Attributes of the , which describe dynamic phases of a dynamic acquisition image performed on the patient. This Module is present only when Image Type (0008,0008), Value 3, is equal to DYNAMIC. A phase is defined as a collection of frames in which the acquisition time per frame and the time delay between frames remains constant. A new phase shall be defined whenever there is a change in the time between frames, the acquisition time per frame, or the position of the patient relative to the detector. @@ -123974,9 +125568,9 @@
- NM Reconstruction Module + NM Reconstruction Module - contains Attributes that describe Nuclear Medicine reconstructed volumes. Reconstructed volumes are created by applying a transformation (reconstruction) process to the acquired TOMO frames. This Module is present only when Image Type (0008,0008) Value 3 is equal to RECON TOMO or RECON GATED TOMO. + specifies the Attributes of the , which that describe Nuclear Medicine reconstructed volumes. Reconstructed volumes are created by applying a transformation (reconstruction) process to the acquired TOMO frames. This Module is present only when Image Type (0008,0008) Value 3 is equal to RECON TOMO or RECON GATED TOMO.
NM Phase Module Attributes
@@ -124007,7 +125601,7 @@ 2 @@ -124122,7 +125716,7 @@
US Frame of Reference Module - This Section was defined in a previous version of the DICOM Standard. The Section is now retired. See PS3.3-2003. + This Section was defined in a previous version of the DICOM Standard. The Section is now retired. See PS3.3-2003.
US Region Calibration Module @@ -124553,7 +126147,7 @@ 1C
@@ -124571,9 +126165,9 @@ - + Otherwise not used. See for further explanation. + +
NM Reconstruction Module Attributes
- Spacing between slices, in mm, measured from center-to-center of each slice along the normal to the first image. The sign of the Spacing Between Slices (0018,0088) determines the direction of stacking. The normal is determined by the cross product of the direction cosines of the first row and first column of the first frame, such that a positive spacing indicates slices are stacked behind the first slice and a negative spacing indicates slices are stacked in front of the first slice. See Image Orientation (0020,0037) in the NM Detector Module. + Spacing between slices, in mm, measured from center-to-center of each slice along the normal to the first image. The sign of the Spacing Between Slices (0018,0088) determines the direction of stacking. The normal is determined by the cross product of the direction cosines of the first row and first column of the first frame, such that a positive spacing indicates slices are stacked behind the first slice and a negative spacing indicates slices are stacked in front of the first slice. See Image Orientation (0020,0037) in the .
- A table of Pixel Values used in conjunction with the Table of Parameter Values (0018,605A) or Pixel Value Mapping Code Sequence (0040,9098) to provide a mapping from Pixel Value to a real world value. + A table of Pixel Values used in conjunction with the Table of Parameter Values (0018,605A) or Pixel Value Mapping Code Sequence (0040,9098) to provide a mapping from Pixel Value to a Real World Value. Required if the Pixel Component Organization equals 2. Otherwise not used. See for further explanation. A table of Parameter Values used in conjunction with the Table of Pixel Values (0018,6058) to provide a mapping from Pixel Value to Parameter Value. Required if the value of Pixel Component Organization (0018,6044) is 2. - Otherwise not used. See for further explanation -
>Pixel Value Mapping Code Sequence @@ -124763,15 +126357,14 @@ 3 - Specifies the Group (60xx) that contains an Overlay that identifies the active image area of the pixel data within this region, - as defined in the . + Specifies the Group (60xx) that contains an Overlay that identifies the active image area of the pixel data within this region, as defined in the . See for further explanation.
- US Region Calibration Attribute Descriptions + US Region Calibration Module Attribute Descriptions
Region Spatial Format Values for Region Spatial Format (0018,6012) indicate the spatial organization of the data within the region. @@ -125055,7 +126648,7 @@ Other values reserved for future use. - Pixel Component Organization defines the way in which the composite pixel values are mapped into real world values with physical units, as illustrated in . + Pixel Component Organization defines the way in which the composite pixel values are mapped into Real World Values with physical units, as illustrated in .
Pixel Component Calibration @@ -125271,21 +126864,18 @@
Table of Pixel Values The Table of Pixel Values (0018,6058) specifies the pixel values that are mapped to real world parameter values or coded concepts (tissue characterizations). The number of entries in the table is given by Number of Table Entries (0018,6056). - A pixel is calibrated (mapped to a real-world value) by finding an entry in the Table of Pixel Values that matches its Composite Pixel Code (see ). The offset index of this entry is used as an index into the Parameter Value Table (0018,605A) or as a Sequence Item number in the Pixel Value Mapping Code Sequence (0040,9098) to select the real world value. The first Table of Pixel Values entry corresponds to Sequence Item 1. + A pixel is calibrated (mapped to a real-world value) by finding an entry in the Table of Pixel Values that matches its Composite Pixel Code (see ). The offset index of this entry is used as an index into the Parameter Value Table (0018,605A) or as a Sequence Item number in the Pixel Value Mapping Code Sequence (0040,9098) to select the Real World Value. The first Table of Pixel Values entry corresponds to Sequence Item 1. If a Composite Pixel Code has no matching value in the Pixel Value Table then there is no unambiguous way to determine the corresponding Parameter Value. A method may exist to determine a valid Parameter Value but the specification of such a method is outside the scope of the DICOM Standard. No assumption should be made that linear interpolation will produce a valid result.
Table of Parameter Values - The Table of Parameter Values (0018,605A) provides the real world values for pixel values identified in the Table of Pixel Values (0018,6058). The number of table entries is given by Number of Table Entries (0018,6056) and the physical units are given by Pixel Component Physical Units (0018,604C). Values may repeat when a parameter value is associated with more than one Composite Pixel Code value. + The Table of Parameter Values (0018,605A) provides the Real World Values for pixel values identified in the Table of Pixel Values (0018,6058). The number of table entries is given by Number of Table Entries (0018,6056) and the physical units are given by Pixel Component Physical Units (0018,604C). Values may repeat when a parameter value is associated with more than one Composite Pixel Code value.
Region Location Min X0, Min Y0, Max X1 and Max Y1 - These Attributes specify the location of the region, Region Location Min X0 (0018,6018), Region Location Min Y0 (0018,601A), Region Location Max X1 (0018,601C), Region Location Max Y1 (0018,601E) expressed as offsets to the pixel coordinates. - The upper left corner of the entire image is x=0,y=0 and the lower right corner is x=number of columns - 1, and y=number of rows - 1. - Thus, a region will be specified as within these bounds. - Where x0,y0 is the coordinate of the upper left corner of the region and x1,y1 is the coordinate of the lower right corner of the region. + These Attributes specify the location of the region, Region Location Min X0 (0018,6018), Region Location Min Y0 (0018,601A), Region Location Max X1 (0018,601C), Region Location Max Y1 (0018,601E) expressed as offsets to the pixel coordinates. The upper left corner of the entire image is x=0,y=0 and the lower right corner is x=number of columns - 1, and y=number of rows - 1. Thus, a region will be specified as within these bounds. Where x0,y0 is the coordinate of the upper left corner of the region and x1,y1 is the coordinate of the lower right corner of the region.
Physical Units X Direction and Physical Units Y Direction @@ -125506,16 +127096,14 @@
Pixel Value Mapping Code Sequence - The Pixel Value Mapping Code Sequence (0040,9098) provides the real world values for pixel values identified in the Table of Pixel Values (0018,6058). The number of Items in the Sequence is given by Number of Table Entries (0018,6056). + The Pixel Value Mapping Code Sequence (0040,9098) provides the Real World Values for pixel values identified in the Table of Pixel Values (0018,6058). The number of Items in the Sequence is given by Number of Table Entries (0018,6056). Pixel Component Physical Units (0018,604C) does not apply to Sequence of Pixel Value Codes and should be set to 0000H (none or not applicable).
Active Image Area Overlay Group - In a 2D region, the field of view of the transducer typically does not extend to the edges of the defined region (e.g., for a fan shape as seen in the example in ). - The pixels that are within the field of view may be identified by an Overlay with Overlay Type (60xx,0040) value R and an Overlay Subtype (60xx,0045) of "ACTIVE 2D/BMODE IMAGE AREA" or "ACTIVE VOLUME FLOW IMAGE AREA" (see ). - The size and location of such a referenced Overlay shall be identical to the size and location of the defined region. + In a 2D region, the field of view of the transducer typically does not extend to the edges of the defined region (e.g., for a fan shape as seen in the example in ). The pixels that are within the field of view may be identified by an Overlay with Overlay Type (60xx,0040) value R and an Overlay Subtype (60xx,0045) of "ACTIVE 2D/BMODE IMAGE AREA" or "ACTIVE VOLUME FLOW IMAGE AREA" (see ). The size and location of such a referenced Overlay shall be identical to the size and location of the defined region. For historical reasons, the specification of the ultrasound image region in Region Location Min X0 (0018,6018), Region Location Min Y0 (0018,601A), Region Location Max X1 (0018,601C), and Region Location Max Y1 (0018,601E) uses 0\0 to identify the top left pixel of the image, whereas the specification of the overlay in Overlay Origin (60xx,0050) uses 1\1 to identify the top left pixel. @@ -125523,9 +127111,9 @@
- US Image Module + US Image Module - specifies the Attributes that describe ultrasound images. + specifies the Attributes of the , which describe ultrasound images. @@ -125557,9 +127145,9 @@ - + See for specialization. + + - + Time interval measured in msec from the start of the R-wave to the beginning of data taking. + + - + Average R-R interval used for these data, in msec. + + - + R-R interval low limit for beat rejection, in msec. + + - + R-R interval high limit for beat rejection, in msec. + + - + Required if Modality (0008,0060) = IVUS. + +
US Image Module Attributes
Number of samples (planes) in this image. - See for specialization -
Photometric Interpretation @@ -126017,9 +127605,9 @@ 3 - Time interval measured in msec from the start of the R-wave to the beginning of data taking -
Nominal Interval @@ -126031,9 +127619,9 @@ 3 - Average R-R interval used for these data, in msec -
Beat Rejection Flag @@ -126074,9 +127662,9 @@ 3 - R-R interval low limit for beat rejection, in msec -
High R-R Value @@ -126088,9 +127676,9 @@ 3 - R-R interval high limit for beat rejection, in msec -
Heart Rate @@ -126145,9 +127733,9 @@ See - Required if Modality (0008,0060) = IVUS -
IVUS Pullback Rate @@ -126538,10 +128126,10 @@
- Referenced Overlay Sequence (0008,1130) and Referenced Curve Sequence (0008,1145) were previously included in this Module as optional Attributes but have been retired. See PS3.3-2004. + Referenced Overlay Sequence (0008,1130) and Referenced Curve Sequence (0008,1145) were previously included in this Module as optional Attributes but have been retired. See PS3.3-2004.
- US Image Attribute Descriptions + US Image Module Attribute Descriptions
Image Type For US Images, Image Type (0008,0008) is specified to be Type 2. @@ -126842,7 +128430,7 @@ - The ARGB and YBR_PARTIAL_422 photometric interpretations were previously defined but are retired. See PS3.3 2017b. + The ARGB and YBR_PARTIAL_422 photometric interpretations were previously defined but are retired. See PS3.3-2017b. When Samples per Pixel (0028,0002) is greater than 1, Photometric Interpretation (0028,0004) shall be RGB for uncompressed or lossless compressed Transfer Syntaxes that do not have defined color space transformations, YBR_ICT for irreversible JPEG 2000 Transfer Syntaxes, YBR_RCT for reversible JPEG 2000 Transfer Syntaxes, YBR_PARTIAL_420 for MPEG2, MPEG-4 AVC/H.264 and HEVC/H.265 Transfer Syntaxes, YBR_FULL_422 for JPEG lossy compressed Transfer Syntaxes and YBR_FULL or RGB for RLE Transfer Syntaxes. See for additional restrictions imposed by compressed Transfer Syntaxes. @@ -126897,7 +128485,7 @@
Image Transformation Matrix and Image Translation Vector - This section was defined in a previous version of the DICOM Standard. The Section is now retired. See PS3.3-2003. + This section was defined in a previous version of the DICOM Standard. The Section is now retired. See PS3.3-2003.
Ultrasound Color Data Present @@ -127186,22 +128774,18 @@ The view may be described by a single Code Sequence Item, or by combination of post-coordinated Code Sequence Items. The principal code is specified in View Code Sequence, and modifier terms in the View Modifier Code Sequence (0054,0222). For post-coordinated encoding of view: - - B (typically used for the primary coded item) + B (typically used for the primary coded item) - - B + B - - B + B - - B + B @@ -127209,13 +128793,12 @@ For cardiac imaging, pre-coordinated view codes are specified: - - B + B - Transducer Position Sequence (0008,2240) and Transducer Orientation Sequence (0008,2244), defined in this Module in an earlier edition of the Standard (see PS3.3-2004), are retired. + Transducer Position Sequence (0008,2240) and Transducer Orientation Sequence (0008,2244), defined in this Module in an earlier edition of the Standard (See PS3.3-2004), are retired.
@@ -127386,7 +128969,7 @@ Type of device, process or method that originally acquired the data used to create the Instances in this Series. - This type definition shall override the definition in the . See Note 2. + This type definition shall override the definition in the . See Note 2. See for Defined Terms. @@ -127401,9 +128984,9 @@ 3 - User defined identification of the device that converted the image - - + User defined identification of the device that converted the image. + + Secondary Capture Device Manufacturer @@ -127415,9 +128998,9 @@ 3 - Manufacturer of the Secondary Capture Device - - + Manufacturer of the Secondary Capture Device. + + Secondary Capture Device Manufacturer's Model Name @@ -127429,9 +129012,9 @@ 3 - Manufacturer's model number of the Secondary Capture Device - - + Manufacturer's model number of the Secondary Capture Device. + + Secondary Capture Device Software Versions @@ -127443,9 +129026,9 @@ 3 - Manufacturer's designation of software version of the Secondary Capture Device - - + Manufacturer's designation of software version of the Secondary Capture Device. + + Video Image Format Acquired @@ -127457,9 +129040,9 @@ 3 - Original format of the captured video image (e.g., NTSC, PAL, Videomed-H) - - + Original format of the captured video image (e.g., NTSC, PAL, Videomed-H). + + Digital Image Format Acquired @@ -127471,9 +129054,9 @@ 3 - Additional information about digital interface used to acquire the image - - + Additional information about digital interface used to acquire the image. + + @@ -127587,16 +129170,15 @@ - Modality (0008,0060) specified in the (see ) has been specialized by this Module and is defined as a Type 3 Attribute. - The value of Modality (0008,0060) is intended to describe the equipment that originally created or generated the data, not the equipment performing the digitization or capture. + Modality (0008,0060) specified in the (see ) has been specialized by this Module and is defined as a Type 3 Attribute. The value of Modality (0008,0060) is intended to describe the equipment that originally created or generated the data, not the equipment performing the digitization or capture.
- SC Image Module + SC Image Module - contains IOD Attributes that describe Secondary Capture Images. + specifies the Attributes of the , which describe Secondary Capture Images. @@ -127716,9 +129298,9 @@
- SC Multi-frame Image Module + SC Multi-frame Image Module - contains IOD Attributes that describe SC Multi-frame images. + specifies the Attributes of the , which describe SC Multi-frame images.
SC Image Module Attributes
@@ -128016,9 +129598,9 @@
- SC Multi-frame Vector Module + SC Multi-frame Vector Module - contains IOD Attributes that may be the target of the Frame Increment Pointer (0028,0009) for SC Multi-frame images. + specifies the Attributes of the , which may be the target of the Frame Increment Pointer (0028,0009) for SC Multi-frame images.
SC Multi-frame Image Module Attributes
@@ -128555,9 +130137,9 @@
SC Multi-frame Vector Module Attributes
-Include - - + Include + + @@ -128566,7 +130148,7 @@
- X-Ray Image Attribute Descriptions + X-Ray Image Module Attribute Descriptions
Image Type The Image Type Attribute identifies important image characteristics in a multiple valued Data Element. For X-Ray, Image Type is specialized as follows: @@ -128767,7 +130349,7 @@ Synchronization of Frame and Waveform Times The synchronization of a multi-frame X-Ray image with a waveform (e.g., ECG, pressure, or respiration) encoded in a different SOP Instance is managed through the Attributes of the (see ) of the Frame of Reference IE. - The use of a Curve IE within the X-Ray IODs was previously defined in DICOM (see PS3.3-2004). That use has been retired in favor of encoding waveform data in a separate IOD. + The use of a Curve IE within the X-Ray IODs was previously defined in DICOM (See PS3.3-2004). That use has been retired in favor of encoding waveform data in a separate IOD.
@@ -129104,9 +130686,9 @@ 3 - Diameter of X-Ray intensifier in mm - - + Diameter of X-Ray intensifier in mm. + + Field of View Shape @@ -129210,7 +130792,7 @@
- X-Ray Acquisition Attribute Descriptions + X-Ray Acquisition Module Attribute Descriptions
Exposure Time Exposure time is the cumulative time the patient received X-Ray exposure during this image (Multi-frame image acquisition). Calculation is pulse width * number of frames. @@ -129428,7 +131010,7 @@
- X-Ray Collimator Attribute Descriptions + X-Ray Collimator Module Attribute Descriptions
Collimator Vertical and Horizontal Edges These Attributes specify the pixel row or column where the X-Ray beam is fully obscured by a rectangular collimator: @@ -129450,9 +131032,9 @@
- X-Ray Table Module + X-Ray Table Module - contains Attributes that describe X-Ray images acquired with movement of the patient imaging table. + specifies the Attributes of the , which describe X-Ray images acquired with movement of the patient imaging table. @@ -129562,7 +131144,7 @@
X-Ray Table Module Attributes
- X-Ray Table Attribute Descriptions + X-Ray Table Module Attribute Descriptions
Table Motion Increments This section is replaced by @@ -129629,9 +131211,9 @@
- XA Positioner Module + XA Positioner Module - contains IOD Attributes that describe a c-arm positioner typically used in acquiring X-Ray Angiographic Images. The coordinate system used to track the positioner is defined in reference to the patient. The definition of coordinates with respect to the equipment is not supported. Furthermore, this Module does not describe the movement of the patient. + specifies the Attributes of the , which describe a c-arm positioner typically used in acquiring X-Ray Angiographic Images. The coordinate system used to track the positioner is defined in reference to the patient. The definition of coordinates with respect to the equipment is not supported. Furthermore, this Module does not describe the movement of the patient. The scope of the XA IOD is to address images produced on acquisition equipment equipped with an X-Ray source and an image Receptor positioned by what is general called a c-arm. For clinical areas other than Angiography that are using a c-arm to position the X-Ray source and image receptor (e.g., Interventional Procedures and Myelography and Biopsy/Localization), the X-Ray Angiography Image Object should be also used. Although the object is optimized for c-arm systems, it may also be used by other systems that support a similar coordinate system, such as some RF systems. @@ -129836,7 +131418,7 @@
- XA Positioner Attribute Descriptions + XA Positioner Module Attribute Descriptions
Positioner Motion Positioner Motion (0018,1500) Attribute is STATIC if the imaging table moves during a multi-frame acquisition, but the X-Ray positioner do not move. @@ -129982,7 +131564,7 @@
X-Ray Tomography Acquisition Module - This Module describes the Attributes of a Tomography acquisition (translation of X-Ray source during the acquisition of a single-frame image). + This Module specifies the Attributes of a Tomography acquisition (translation of X-Ray source during the acquisition of a single-frame image). @@ -130360,7 +131942,7 @@ This may be a calculated or measured value. Examples are the detector entrance dose (KB), the CR sensitivity value (S), or the logarithmic median (lgM). - DICOM specifies Standard Attributes in 'Exposure Index Macro', which are recommended. + DICOM specifies Standard Attributes in the , which are recommended. @@ -130463,7 +132045,7 @@ This may be an estimated value based on assumptions about the patient's body size and habitus. - This Attribute was previously used in the with units in mm. This use has been retired. See PS3.3 2017c. + This Attribute was previously used in the with units in mm. This use has been retired. See PS3.3-2017c. @@ -130998,9 +132580,9 @@ 3 - + Identifier of the generator. + +
X-Ray Tomography Acquisition Module Attributes
- Identifier of the generator -
@@ -131449,9 +133031,9 @@ 3 - Identifier of the grid - - + Identifier of the grid. + +
@@ -131657,7 +133239,7 @@ 3 - Identification of the operator(s) supporting the Series. One or more Items may be present in this Sequence. If more than one Item, the number and order shall correspond to the value of Operators' Name (0008,1070), if present. + Identification of the operator(s) supporting the Series. One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Operators' Name (0008,1070), if present. @@ -131794,9 +133376,9 @@
- RT Image Module + RT Image Module - contains Attributes that describe RT-specific characteristics of a projection image. The image described by these Attributes must be a radiotherapy image acquired or calculated using a conical imaging geometry. + specifies the Attributes of the , which describe RT-specific characteristics of a projection image. The image described by these Attributes must be a radiotherapy image acquired or calculated using a conical imaging geometry. @@ -133196,9 +134778,9 @@ 3 - + Machine-readable identifier for this accessory. + + + + + + + + @@ -134328,6 +135933,21 @@ + + + + + + @@ -134663,6 +136284,217 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
RT Image Module Attributes
- Machine-readable identifier for this accessory -
>>Source to General Accessory Distance @@ -133794,7 +135376,7 @@ If the is present and the is not present then the Frame Increment Pointer (0028,0009) shall have the Enumerated Value of 00200013 (Instance Number). If the and are both present then the Frame Increment Pointer (0028,0009) shall have an Enumerated Value of either 00181063 (Frame Time) or 00181065 (Frame Time Vector).
- Image Pixel Module Attributes + Image Pixel Attributes
Samples Per Pixel @@ -133916,8 +135498,8 @@
Exposure Time and Meterset Exposure Multi-frame RT Images may encode a continuous acquisition. In this case, the Exposure Sequence (3002,0030) may not reference all frames. - The Attributes Exposure Time (00018,1150), Exposure Time in ms (0018,9328) and Meterset Exposure (3002,0032) Attributes in the Exposure Sequence (3002,0030), if present with values, contain the exposure values encompassing the X-Ray exposure during the acquisition of the single frame referenced by the Referenced Frame Number (0008,1160). Note that not all frames may be referenced in this Sequence and therefore the sum of these values may not equal the total exposure value. - The Attributes Exposure Time (00018,1150), Exposure Time in ms (0018,9328) and Meterset Exposure (3002,0032) Attributes outside the Exposure Sequence (3002,0030) may be used to record the total exposure values. + The Attributes Exposure Time (0018,1150), Exposure Time in ms (0018,9328) and Meterset Exposure (3002,0032) Attributes in the Exposure Sequence (3002,0030), if present with values, contain the exposure values encompassing the X-Ray exposure during the acquisition of the single frame referenced by the Referenced Frame Number (0008,1160). Note that not all frames may be referenced in this Sequence and therefore the sum of these values may not equal the total exposure value. + The Attributes Exposure Time (0018,1150), Exposure Time in ms (0018,9328) and Meterset Exposure (3002,0032) Attributes outside the Exposure Sequence (3002,0030) may be used to record the total exposure values.
@@ -134197,6 +135779,21 @@ A number that identifies this object Instance.
+ Entity Long Label + + (3010,0038) + + 3 + + User-defined label for dose data. + See . +
Dose Comment @@ -134251,6 +135848,12 @@ dose calculated for entire delivery of 2 or more RT Plans + + PLAN_OVERVIEW + + dose calculated with respect to plan overview parameters + + FRACTION @@ -134313,7 +135916,9 @@ 1C - Sequence describing RT Plan associated with dose. Required if Dose Summation Type (3004,000A) is PLAN, MULTI_PLAN, FRACTION, BEAM, BRACHY, FRACTION_SESSION, BEAM_SESSION, BRACHY_SESSION or CONTROL_POINT. + Sequence describing RT Plan associated with dose. + Required if Dose Summation Type (3004,000A) is PLAN, MULTI_PLAN, FRACTION, BEAM, BRACHY, FRACTION_SESSION, BEAM_SESSION, BRACHY_SESSION or CONTROL_POINT. + May be present if Dose Summation Type (3004,000A) is PLAN_OVERVIEW. Only a single Item shall be included in this Sequence, unless Dose Summation Type (3004,000A) is MULTI_PLAN, in which case two or more Items shall be included in this Sequence. See Note 1.
+ >Referenced Plan Overview Index + + (300C,0118) + + 1C + + The value of Plan Overview Index (300C,0117) from the Plan Overview Sequence (300C,0116) to which this RT Plan corresponds. + Required if Plan Overview Sequence (300C,0116) is present. +
>Referenced Fraction Group Sequence @@ -134339,7 +135959,8 @@ 1C - Sequence of one Fraction Group containing beams or brachy application setups contributing to dose. Required if Dose Summation Type (3004,000A) is FRACTION, BEAM, BRACHY, FRACTION_SESSION, BEAM_SESSION, BRACHY_SESSION or CONTROL_POINT. + Sequence of one Fraction Group containing beams or brachy application setups contributing to dose. + Required if Dose Summation Type (3004,000A) is FRACTION, BEAM, BRACHY, FRACTION_SESSION, BEAM_SESSION, BRACHY_SESSION or CONTROL_POINT. Only a single Item shall be included in this Sequence. See Note 1.
+ Plan Overview Sequence + + (300C,0116) + + 1C + + Parameters providing an overview of the plan used to create this RT Dose Instance. + Required if Dose Summation Type (3004,000A) is PLAN_OVERVIEW. May be present if Dose Summation Type (3004,000A) is PLAN, MULTI_PLAN or RECORD. + One or more Items shall be included in this Sequence if Dose Summation Type (3004,000A) is PLAN_OVERVIEW. + Only one Item shall be included in this Sequence if Dose Summation Type (3004,000A) is PLAN or RECORD. + Two or more Items shall be included in this Sequence if Dose Summation Type (3004,000A) is MULTI_PLAN. +
+ >Plan Overview Index + + (300C,0117) + + 1 + + The index of the Plan Overview within this Sequence. + The value shall start at 1 and increase monotonically by 1. +
+ >RT Plan Label + + (300A,0002) + + 2 + + User-defined label of treatment plan. +
+ >Number of Fractions Included + + (300C,0119) + + 1C + + Number of fractions of the plan included in this RT Dose Instance. + Required if Dose Summation Type (3004,000A) is PLAN_OVERVIEW, PLAN or MULTI_PLAN. + If Dose Summation Type is PLAN or MULTI_PLAN the Number of Fractions Included (300C,0119) shall equal the Number of Fractions Planned (300A,0078) of the referenced RT Plan Instance. +
+ >Current Fraction Number + + (3008,0022) + + 1C + + Fraction Number of the fraction included in this RT Dose Instance. + Required if Dose Summation Type (3004,000A) is RECORD. +
+ >Treatment Site + + (3010,0077) + + 2 + + A free-text label describing the anatomical treatment site. +
+ >Treatment Site Code Sequence + + (3010,0078) + + 2 + + Coded description of the treatment site. + Zero or more Items are permitted in this Sequence. +
+ + >>Include + + + + + B. + +
+ >Prescription Overview Sequence + + (300C,0114) + + 2 + + Prescription parameters for evaluation of the dose matrix. + Zero or more Items shall be included in this Sequence. +
+ >>Total Prescription Dose + + (300C,0115) + + 1 + + Prescribed total dose in Gy for all fractions for the dose type defined in Dose Type (3004,0004). +
+ >>Referenced ROI Number + + (3006,0084) + + 3 + + ROI for which the prescription parameters in this Sequence apply, specified by ROI Number (3006,0022) in the Instance referenced by Referenced Structure Set Sequence (300C,0060). +
+ >Referenced Structure Set Sequence + + (300C,0060) + + 1C + + Structure Set containing structures that were used to calculate the RT Dose. + Required if Referenced Image Sequence (0008,1140) is not present. + Only a single Item shall be included in this Sequence. +
+ + >>Include + + +
+ >Referenced Image Sequence + + (0008,1140) + + 1C + + Images used to calculate the RT Dose. + Required if Referenced Structure Set Sequence (300C,0060) is not present. + One or more Items shall be included in this Sequence. +
+ + >>Include + + +
@@ -134792,7 +136624,7 @@ Dose Units are specified in both the and . The Attribute Dose Type present in the shall apply to all doses present in the .
- Image Pixel Module Attributes + Image Pixel Attributes
Samples Per Pixel @@ -135500,6 +137332,31 @@ Identification number of the ROI. The value of ROI Number (3006,0022) shall be unique within the Structure Set in which it is created. + + + >Conceptual Volume Identification Sequence + + + (3010,00A0) + + + 3 + + + Identifies the Conceptual Volume which is represented by this ROI. + Only a single Item is permitted in this Sequence. + + + + + + >>Include . + + + + + + >Referenced Frame of Reference UID @@ -135750,7 +137607,7 @@
Frame of Reference Relationship Sequence and Transformation Matrix - Retired. See PS3.3-2011. + Retired. See PS3.3-2011. The concept of definition of registered Frame of References using the Frame of Reference Relationship Sequence (3006,00C0) formerly present in the Standard is retired. The use of Registration IODs is advised since the introduction of Spatial Registration IOD, which is a much stronger and more general concept, and independent from the specifics of RT Structure Sets. Additionally it is of importance that registrations are decoupled from image and segmentation objects.
@@ -135934,6 +137791,48 @@ The x, y and z coordinates in mm of the upper left hand corner of the pixel matrix in the Patient-Based Coordinate System described in . + + + >>Number of Frames + + + (0028,0008) + + + 1 + + + Number of source pixel planes. + + + + + >>Rows + + + (0028,0010) + + + 1 + + + Number of rows in the source pixel planes. + + + + + >>Columns + + + (0028,0011) + + + 1 + + + Number of columns in the source pixel planes. + + >Contour Sequence @@ -136087,23 +137986,18 @@ A Contour Geometric Type (3006,0042) of CLOSED_PLANAR indicates that the last point shall be connected to the first point, where the first point is not repeated in Contour Data (3006,0050). All points in Contour Data (3006,0050) shall be coplanar. - A Contour Geometric Type (3006,0042) of CLOSEDPLANAR_XOR indicates that the last point shall be connected to the first point, where the first is not repeated in Contour Data (3006,0050). - All points in Contour Data (3006,0050) shall be coplanar. - More than one Contour is used to describe an ROI and these Contours are combined by geometric exclusive disjunction, see . - If any of the Contours within an ROI is of Contour Geometric Type (3006,0042) CLOSEDPLANAR_XOR, all Contours of that ROI shall be of the same type. + A Contour Geometric Type (3006,0042) of CLOSEDPLANAR_XOR indicates that the last point shall be connected to the first point, where the first is not repeated in Contour Data (3006,0050). All points in Contour Data (3006,0050) shall be coplanar. More than one Contour is used to describe an ROI and these Contours are combined by geometric exclusive disjunction, see . If any of the Contours within an ROI is of Contour Geometric Type (3006,0042) CLOSEDPLANAR_XOR, all Contours of that ROI shall be of the same type.
Contour Slab Thickness - Retired. See PS3.3 2020e. + Retired. See PS3.3-2020e.
Representing Inner and Outer Contours Inner and Outer Contours can be represented by two different techniques: - Using the "keyhole" technique, an ROI with an excluded inner part is represented with a single planar Contour. - In this method, an arbitrarily narrow channel is used to connect the outer contour to the inner contour, so that it is drawn as a single contour. - An example of such a structure is shown in with the channel at roughly the 12 o'clock position. + Using the "keyhole" technique, an ROI with an excluded inner part is represented with a single planar Contour. In this method, an arbitrarily narrow channel is used to connect the outer contour to the inner contour, so that it is drawn as a single contour. An example of such a structure is shown in with the channel at roughly the 12 o'clock position. Points in space lying along the path defined by the contour are considered to be part of the ROI.
@@ -136115,24 +138009,18 @@
- Using the "XOR" technique, an ROI with an excluded inner part is represented by two planar Contours that are combined by a geometric exclusive disjunction, - thus extracting the inner from the outer Contour, see . - The contours have the Contour Geometric Type (3006,0042) CLOSEDPLANAR_XOR. + Using the "XOR" technique, an ROI with an excluded inner part is represented by two planar Contours that are combined by a geometric exclusive disjunction, thus extracting the inner from the outer Contour, see . The contours have the Contour Geometric Type (3006,0042) CLOSEDPLANAR_XOR.
Example of ROI with contours exclusively added - +
- Using this technique, it is also possible to create an ROI that includes disjoint parts of the ROI within an interior void. - When two or more Contours are present, two Contours are combined using a geometric exclusive disjunction ("XOR"). - Then this result is combined by an XOR operation with a third Contour, and so on for all other Contours of this ROI. - The order of combination does not matter. - An example of the result of an XOR operation of three Contours is visualized in . + Using this technique, it is also possible to create an ROI that includes disjoint parts of the ROI within an interior void. When two or more Contours are present, two Contours are combined using a geometric exclusive disjunction ("XOR"). Then this result is combined by an XOR operation with a third Contour, and so on for all other Contours of this ROI. The order of combination does not matter. An example of the result of an XOR operation of three Contours is visualized in .
Example of ROI with disjoint parts @@ -136362,34 +138250,6 @@ Uniquely identifies the referenced ROI described in the Structure Set ROI Sequence (3006,0020). - - - >ROI Observation Label - - - (3006,0085) - - - 3 - - - User-defined label for ROI Observation. - - - - - >ROI Observation Description - - - (3006,0088) - - - 3 - - - User-defined description for ROI Observation. - - >RT Related ROI Sequence @@ -136495,7 +138355,7 @@ - No Baseline CID is defined. + B. @@ -136524,10 +138384,7 @@ - For dose measurement devices B. - - - No Baseline CID is defined otherwise. + See . @@ -136559,6 +138416,62 @@ + + + >Therapeutic Role Category Code Sequence + + + (3010,0064) + + + 3 + + + The general category of the therapeutic role of this ROI. + Only a single Item is permitted in this Sequence. + + + + + + >>Include + + + + + + B. + + + + + + >Therapeutic Role Type Code Sequence + + + (3010,0065) + + + 3 + + + The specific property type of the therapeutic role of this ROI. + Only a single Item is permitted in this Sequence. + + + + + + >>Include + + + + + + See . + + + >Related RT ROI Observations Sequence @@ -136638,6 +138551,12 @@ Irradiated Volume (as defined in ) + + OAR + + Organ at Risk (as defined in ) + + BOLUS @@ -136922,10 +138841,398 @@
RT ROI Interpreted Type RT ROI Interpreted Type (3006,00A4) shall describe the class of ROI (e.g., CTV, PTV). Individual instances of each class of structure (e.g., CTV1, CTV2) can be distinguished using ROI Observation Label (3006,0085). + In addition to providing a Defined Term in RT ROI Interpreted Type (3006,00A4), it is recommended that coded information be included; see .
Additional RT ROI Identification Code Sequence - Retired. See DICOM PS3.3 2016c. + Retired. See PS3.3-2016c. +
+
+ RT ROI Identification Code Sequence and Therapeutic Role Type Code Sequence + The CID for RT ROI Identification Code Sequence (3006,0086) shall correspond to the CID defined in for each value in Segmented Property Category Code Sequence (0062,0003). + The CID for Therapeutic Role Type Code Sequence (3010,0065) is defined in . +
+ Mapping of RT ROI Interpreted Type + + defines a mapping between the geometric concepts represented in RT ROI Interpreted Type (3006,00A4) and coded values in Segmented Property Category Code Sequence (0062,0003) in combination with RT ROI Identification Code Sequence (3006,0086). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
RT ROI Interpreted Type Code Mapping
+ RT ROI Interpreted Type (3006,00A4) + + Segmented Property Category Code Sequence (0062,0003) + + RT ROI Identification Code Sequence (3006,0086) +
+ EXTERNAL + + + (130047, DCM, "External Body Model") + + + Any value from D + +
+ BOLUS + + + (130405, DCM, "Patient-Attached Dose Control Object)" + + + + (228736002, SCT, "Surface Bolus") + +
+ MARKER + + + (130666, DCM, "Radiotherapy Fiducial") + + + Any value from B + +
+ ISOCENTER + + + (130043, DCM, "RT Geometric Information") + + + + (130073, DCM, "Isocentric Treatment Location") + +
+ CONTRAST_AGENT + + + (105590001, SCT, "Substance") + + + + (7140000, SCT, "Contrast agent") + +
+ CAVITY + + + (91723000, SCT, "Anatomical Structure") + + + + (91806002, SCT, "Body Cavity") + +
+ BRACHY_CHANNEL + + + (130045, DCM, "Brachytherapy Device") + + + + (130080, DCM, "Brachytherapy channel") + +
+ BRACHY_ACCESSORY + + + (130045, DCM, "Brachytherapy Device") + + + No Baseline CID defined. +
+ BRACHY_SRC_APP + + + (130045, DCM, "Brachytherapy Device") + + + + (130078, DCM, "Brachytherapy source applicator") + +
+ BRACHY_CHNL_SHLD + + + (130045, DCM, "Brachytherapy Device") + + + + (130079, DCM, "Brachytherapy channel shield") + +
+ SUPPORT + + + (130044, DCM, "Fixation or Positioning Device") + + + Any value from D + +
+ FIXATION + + + (130044, DCM, "Fixation or Positioning Device") + + + Any value from D + +
+ DOSE_REGION + + + (130748, DCM, "Radiotherapy Dose Region") + + + + (130747, DCM, "Isodose Volume") + +
+ DOSE_MEASUREMENT + + + (260787004, SCT, "Physical object") + + + Any value from D + +
+ + defines a mapping between therapeutic roles represented in RT ROI Interpreted Type (3006,00A4) and coded values in Therapeutic Role Category Code Sequence (3010,0064) in combination with Therapeutic Role Type Code Sequence (3010,0065). + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Therapeutic Role Code Mapping
+ RT ROI Interpreted Type (3006,00A4) + + Therapeutic Role Category Code Sequence (3010,0064) + + Therapeutic Role Type Code Sequence (3010,0065) +
+ PTV + + + (130041, DCM, "RT Target") + + + + (228793007, SCT, "PTV") + +
+ CTV + + + (130041, DCM, "RT Target") + + + + (228792002, SCT, "CTV") + +
+ GTV + + + (130041, DCM, "RT Target") + + + + (228791009, SCT, "GTV") + +
+ OAR + + + (130042, DCM, "RT Dose Calculation Structure") + + + + (130060, DCM, "Organ At Risk") + +
+ TREATED_VOLUME + + + (130041, DCM, "RT Target") + + + + (130059, DCM, "Treated Volume") + +
+ IRRAD_VOLUME + + + (130041, DCM, "RT Target") + + + + (228790005, SCT, "Irradiated Volume") + +
+ AVOIDANCE + + + (130042, DCM, "RT Dose Calculation Structure") + + + + (130058, DCM, "Avoidance Volume") + +
+ REGISTRATION + + + (130746, DCM, "RT Registration Mark") + + + + (112171, DCM, "Fiducial mark") + +
+ CONTROL + + + (130042, DCM, "RT Dose Calculation Structure") + + + + (130061, DCM, "Radiation Dose Shaping Volume") or (130062, DCM, "Conformality Shell") + +
+ For examples of how the mapping is applied see . +
@@ -137108,16 +139415,44 @@ - Treatment Sites + Treatment Site - (300A,000B) + (3010,0077) 3 - Planned treatment sites. + A free-text label describing the anatomical treatment site. + + + + + Treatment Site Code Sequence + + + (3010,0078) + + + 3 + + + Coded description of the treatment site. + One or more Items are permitted in this Sequence. + + + + + + >Include + + + + + + B. + @@ -138830,7 +141165,7 @@
- RT Patient Setup Module Attributes + RT Patient Setup Module Attribute Descriptions
Referenced Setup Image Sequence Images with modality SC or VL serve as visible light photos for visual setup control. Images with modality RTIMAGE serve as reference images on plan level. RT Images present in this Sequence shall not be referenced in the Referenced Reference Image Sequence (300C,0042) of the . @@ -139265,7 +141600,7 @@ 3 - Identifies the Dose Reference specified by Dose Reference UID (300A,0013) in the Dose Reference Sequence (300A,0010) in the RT Prescription Module which specifies the primary target for the current Beam. + Identifies the Dose Reference specified by Dose Reference UID (300A,0013) in the Dose Reference Sequence (300A,0010) in the , which specifies the primary target for the current Beam. If present shall have a value that is present in the Dose Reference Sequence. @@ -139389,6 +141724,147 @@ The expected maximum delivery time in sec. See Note 7. + + + >>Dose Calibration Conditions Verified Flag + + + (300C,0123) + + + 3 + + + Indicates whether the current RT Plan was verified against calibration conditions of the delivery device. + + Enumerated Values: + + YES + + + + + + NO + + + + + + + + + + >>Dose Calibration Conditions Sequence + + + (300C,0120) + + + 1C + + + Dose calibration conditions for the referenced beam. + Required if Dose Calibration Conditions Verified Flag (300C,0123) is present and equals YES and Radiation Device Configuration and Commissioning Key Sequence (300A,065A) is absent. + May be present if Radiation Device Configuration and Commissioning Key Sequence (300A,065A) is present. + Only a single Item shall be present in this Sequence. + + + + + >>>Absorbed Dose to Meterset Ratio + + + (300C,0121) + + + 1 + + + Ratio of absorbed dose in Gy to Meterset as defined by Primary Dosimeter Unit (300A,00B3) in the reference conditions. + + + + + >>>Delineated Radiation Field Size + + + (300C,0122) + + + 1 + + + Field size in mm in X and Y directions in the IEC BEAM LIMITING DEVICE coordinate system, specified by a numeric pair, X value then Y value. + + + + + >>>Calibration Reference Point Depth + + + (300C,0124) + + + 1 + + + Calibration reference point depth in mm from the phantom surface. + + + + + >>>Source to Surface Distance + + + (300A,0130) + + + 1 + + + Distance in mm from the radiation source to the phantom surface during calibration. + + + + + >>>Calibration DateTime + + + (0018,1203) + + + 2 + + + Date and time the calibration was performed. + + + + + >>Radiation Device Configuration and Commissioning Key Sequence + + + (300A,065A) + + + 1C + + + Keys identifying the configuration and commissioning data used as input for treatment planning of this Instance. + Value Type (0040,A040) is constrained to value UIDREF. + Required if Dose Calibration Conditions Verified Flag (300C,0123) is present and equals YES and Dose Calibration Conditions Sequence (300C,0120) is absent. + May be present if Dose Calibration Conditions Sequence (300C,0120) is present. + One or more Items shall be included in this Sequence. + + + + + + >>>Include . + + + >Number of Brachy Application Setups @@ -139470,7 +141946,7 @@ 3 - Identifies the Dose Reference specified by Dose Reference UID (300A,0013) in the Dose Reference Sequence (300A,0010) in the RT Prescription Module that specifies the primary target for the current Brachy Application Setup. + Identifies the Dose Reference specified by Dose Reference UID (300A,0013) in the Dose Reference Sequence (300A,0010) in the that specifies the primary target for the current Brachy Application Setup. If present, shall have a value that is present in the Dose Reference Sequence (300A,0010). @@ -139543,25 +142019,25 @@ The Meterset at a given Control Point (see ) is equal to Beam Meterset (300A,0086) multiplied by the Cumulative Meterset Weight (300A,0134) for the Control Point, divided by the Final Cumulative Meterset Weight (300A,010E). - Attribute Referenced Patient Setup Number (300C,006A) was previously defined. Its use in this Module is now retired (see PS3.3-2004). + Attribute Referenced Patient Setup Number (300C,006A) was previously defined. Its use in this Module is now retired (See PS3.3-2004). - Attributes Beam Dose Point Depth, Beam Dose Point Equivalent Depth and Beam Dose Point SSD were previously included in this Module as optional Attributes but have been retired. See PS3.3-2011. + Attributes Beam Dose Point Depth, Beam Dose Point Equivalent Depth and Beam Dose Point SSD were previously included in this Module as optional Attributes but have been retired. See PS3.3-2011. The Beam Delivery Duration Limit (300A,00C5) is the maximum time span allowed to deliver a single fraction of a beam to prevent significant over-treatments. Treatment is expected to be terminated upon reaching the Beam Delivery Duration Limit independent of the Meterset. This limit represents the expected time span including some increase by a factor greater than 1 to accommodate normal variations in delivery. - The Beam Dose Verification Control Point Sequence was previously included and has been retired. See PS 3.3 2017c. The information is now described in the Referenced Dose Reference Sequence (300C,0050) in the . + The Beam Dose Verification Control Point Sequence was previously included and has been retired. See PS3.3-2017c. The information is now described in the Referenced Dose Reference Sequence (300C,0050) in the . - The Beam Dose Specification Point (300A,0082) was previously included in this module as a means to specify a single point at which dose contributions of different beams could be specified. This attribute has been retired as it no longer reflects clinical practice. Along with this, the semantics of the Beam Dose (300A,0084) and Alternate Beam Dose (300A,0091) have been adapted to reflect the absence of the Beam Dose Specification Point. In order to refer to an Item in the Dose Reference Sequence (300A,0010) it is recommended to utilize the Referenced Dose Reference UID (300A,0083) and the Dose Reference UID (300A,0013) respectively. + The Beam Dose Specification Point (300A,0082) was previously included in this module as a means to specify a single point at which dose contributions of different beams could be specified. This Attribute has been retired as it no longer reflects clinical practice. Along with this, the semantics of the Beam Dose (300A,0084) and Alternate Beam Dose (300A,0091) have been adapted to reflect the absence of the Beam Dose Specification Point. In order to refer to an Item in the Dose Reference Sequence (300A,0010) it is recommended to utilize the Referenced Dose Reference UID (300A,0083) and the Dose Reference UID (300A,0013) respectively.
Beam Dose Verification Parameters - Retired. See PS3.3 2017c. + Retired. See PS3.3-2017c.
@@ -139629,6 +142105,20 @@ User-defined name for Beam. See Note 1. + + + >Entity Long Label + + + (3010,0038) + + + 3 + + + User-defined label for this Beam. See Note 1. + + >Beam Description @@ -141665,9 +144155,9 @@ 3 - Machine-readable identifier for this accessory - - + Machine-readable identifier for this accessory. + + >>Source to General Accessory Distance @@ -141708,7 +144198,7 @@ 1 - Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in RT Prescription Module. + Uniquely identifies Dose Reference specified by Dose Reference Number (300A,0012) in Dose Reference Sequence (300A,0010) in . @@ -141723,7 +144213,7 @@ Whether or not the depth values have been averaged. - + Enumerated Values: YES @@ -142643,10 +145133,10 @@ - Beam Number (300A,00C0) is provided to link related information across Modules, and its value should not be required to have any real-world interpretation. Beam Name (300A,00C2), a Type 3 Attribute, is intended to store the primary beam identifier (often referred to as "field identifier"). Beam Description (300A,00C3), a Type 3 Attribute, is intended to store additional beam identifying information (often referred to as "field name"). Equipment supporting both these Attributes should state this clearly in the Conformance Statement. + Beam Number (300A,00C0) is provided to link related information across Modules, and its value should not be required to have any real-world interpretation. Beam Name (300A,00C2), a Type 3 Attribute, is intended to store the primary beam identifier (often referred to as "field identifier"). Entity Long Label (3010,0038), a Type 3 Attribute, is intended to store additional beam identifying information (often referred to as "field name"). Beam Description (300A,00C3), a Type 3 Attribute, is intended to store beam summary information (often referred to as "field note"). Equipment supporting these Attributes should state this clearly in the Conformance Statement. - The DICOM Standard does not support the transmission of treatment unit modeling information such as depth doses and beam profiles. + The RT Beams Module does not support the transmission of treatment unit modeling information such as depth doses and beam profiles, except for absolute dose calibration information. Implementers should take note that Leaf Position Boundaries (300A,00BE) are the positions of the mechanical boundaries (projected to the isocentric plane) between beam limiting device (collimator) leaves, fixed for a given beam limiting device (collimator). Leaf/Jaw Positions (300A,011C) are values specific to a given beam control point, specifying the beam limiting device (collimator) leaf (element) openings. @@ -142658,7 +145148,7 @@ Refer to for examples of STATIC and DYNAMIC Beam Type. Note that beams having Wedge Type = DYNAMIC as the only moving parameter are not considered DYNAMIC according to the definition of Beam Type (300A,00C4). - Attributes Beam Dose Point Depth (300A,0088), Beam Dose Point Equivalent Depth (300A,0089), Beam Dose Point SSD (300A,008A) were previously included in this Module on the level of Beam Sequence (300A,00B0) > Control Points Beam Sequence (300A,0111) > Referenced Dose Reference Sequence (300C,0050). These Attributes have been retired at this location. See PS3.3-2011. + Attributes Beam Dose Point Depth (300A,0088), Beam Dose Point Equivalent Depth (300A,0089), Beam Dose Point SSD (300A,008A) were previously included in this Module on the level of Beam Sequence (300A,00B0) > Control Points Beam Sequence (300A,0111) > Referenced Dose Reference Sequence (300C,0050). These Attributes have been retired at this location. See PS3.3-2011. @@ -146712,9 +149202,9 @@ 3 - Machine-readable identifier for this accessory - - + Machine-readable identifier for this accessory. + + >>Source to General Accessory Distance @@ -146942,6 +149432,170 @@ Machine setting actually delivered as recorded by secondary Meterset. + + + >Dose Calibration Conditions Verified Flag + + + (300C,0123) + + + 3 + + + Indicates whether the delivered plan was verified against calibration conditions of the delivery device. + + Enumerated Values: + + YES + + + + + + NO + + + + + + + + + + >Dose Calibration Conditions Sequence + + + (300C,0120) + + + 1C + + + Dose calibration conditions for the delivered beam. + Required if Dose Calibration Conditions Verified Flag (300C,0123) is present and equals YES and Radiation Device Configuration and Commissioning Key Sequence (300A,065A) is absent. + May be present if Dose Calibration Conditions Verified Flag (300C,0123) is present and equals YES and Radiation Device Configuration and Commissioning Key Sequence (300A,065A) is present. + Only a single Item shall be present in this Sequence. + + + + + >>Absorbed Dose to Meterset Ratio + + + (300C,0121) + + + 1 + + + Ratio of absorbed dose in Gy to Meterset as defined by Primary Dosimeter Unit (300A,00B3) in the reference conditions. + + + + + >>Delineated Radiation Field Size + + + (300C,0122) + + + 1 + + + Field size in mm in X and Y directions in the IEC BEAM LIMITING DEVICE coordinate system, specified by a numeric pair, X value then Y value. + + + + + >>Calibration Reference Point Depth + + + (300C,0124) + + + 1 + + + Calibration reference point depth in mm from the phantom surface. + + + + + >>Source to Surface Distance + + + (300A,0130) + + + 1 + + + Distance in mm from the radiation source to the phantom surface during calibration. + + + + + >>Calibration DateTime + + + (0018,1203) + + + 2 + + + Date and time the calibration was performed. + + + + + >Radiation Device Configuration and Commissioning Key Sequence + + + (300A,065A) + + + 1C + + + Keys identifying the configuration and commissioning data used as input for treatment planning of this Instance. + Value Type (0040,A040) is constrained to value UIDREF. + Required if Dose Calibration Conditions Verified Flag (300C,0123) is present and equals YES and Dose Calibration Conditions Sequence (300C,0120) is absent. + May be present if Dose Calibration Conditions Sequence (300C,0120) is present. + One or more Items shall be included in this Sequence. + + + + + + >>Include . + + + + + + >Interlock Sequence + + + (300A,0740) + + + 3 + + + Interlocks which occurred prior, during or after the delivery of radiation of this beam. + One or more Items are permitted in this Sequence. + + + + + + >>Include + + + + >Specified Treatment Time @@ -146970,6 +149624,91 @@ Treatment Time actually delivered (sec). + + + >Gating Beam Hold Transition Sequence + + + (300C,0125) + + + 3 + + + The beam hold transitions due to beam gating function according to . + One or more items are permitted in this Sequence. + + + + + >>Beam Hold Transition + + + (300C,0126) + + + 1 + + + Beam hold transition during irradiation. + + Enumerated Values: + + HOLD + + Beam held. + + + + RESTART + + Beam restarted. + + + + + + + + >>Beam Hold Transition DateTime + + + (300C,0127) + + + 1 + + + DateTime of the beam hold transition. + + + + + >>Beam Hold Originating Device Sequence + + + (300C,0128) + + + 1C + + + The device that triggered the beam hold. + Required if there are multiple devices in the treatment delivery device that can trigger the beam hold. + Only a single Item shall be included in this Sequence. + + + + + + >>>Include + + + + + No Baseline CID is defined. + + >Number of Control Points @@ -151104,7 +153843,7 @@ 3 - Maximum permitted difference (in mm) between planned and delivered Fixation Light Polar Angle (300A,0358). + Maximum permitted difference (in degrees) between planned and delivered Fixation Light Polar Angle (300A,0358). @@ -151265,9 +154004,9 @@ 1C - Mass number of radiation. Required if Radiation Type (300A,00C6) is ION - - + Mass number of radiation. Required if Radiation Type (300A,00C6) is ION. + + >Radiation Atomic Number @@ -151279,9 +154018,9 @@ 1C - Atomic number of radiation. Required if Radiation Type (300A,00C6) is ION - - + Atomic number of radiation. Required if Radiation Type (300A,00C6) is ION. + + >Radiation Charge State @@ -151293,9 +154032,9 @@ 1C - Charge state of radiation. Required if Radiation Type (300A,00C6) is ION - - + Charge state of radiation. Required if Radiation Type (300A,00C6) is ION. + + >Scan Mode @@ -153067,9 +155806,9 @@ 3 - Machine-readable identifier for this accessory - - + Machine-readable identifier for this accessory. + + >>Isocenter to General Accessory Distance @@ -153448,9 +156187,9 @@ 1C - User-supplied identifier for the beam current modulation pattern. Required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS - - + User-supplied identifier for the beam current modulation pattern. Required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS. + + @@ -153936,9 +156675,9 @@ 1C - Start position defines the range modulator position at which the beam is switched on. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS - - + Start position defines the range modulator position at which the beam is switched on. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS. + + >>>Range Modulator Gating Stop Value @@ -153950,9 +156689,9 @@ 1C - Stop position defines the range modulator position at which the beam is switched off. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS - - + Stop position defines the range modulator position at which the beam is switched off. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS. + + >>>Range Modulator Gating Start Water Equivalent Thickness @@ -154186,7 +156925,7 @@ Indicates whether the spot delivery order shall remain the same as planned order. - + Enumerated Values: ALLOWED @@ -154989,7 +157728,7 @@
- Depth Dose Parameters Sequence Attributes + Depth Dose Parameters Sequence Some delivery systems determine the settings of the range shifter (or beam energy) and range modulators internally based upon clinical parameters. The Attributes mentioned in this section represent those clinical parameters. When the Depth Dose Parameters Sequence (300A,0505) is present, those specifications have precedence over the definitions of the Range Shifters defined in Range Shifter Settings Sequence (300A,0360) and the Range Modulator defined in Range Modulator Settings Sequence (300A,0380). @@ -155110,9 +157849,9 @@
- RT Ion Beams Session Record Module + RT Ion Beams Session Record Module - specifies the Attributes that describe the measured and recorded settings acquired during Ion Radiation Treatments. + specifies the Attributes of the , which describe the measured and recorded settings acquired during Ion Radiation Treatments. @@ -155321,9 +158060,9 @@ 1C - + Mass number of radiation. Required if Radiation Type (300A,00C6) is ION. + + - + Atomic number of radiation. Required if Radiation Type (300A,00C6) is ION. + + - + Charge state of radiation. Required if Radiation Type (300A,00C6) is ION. + + @@ -155983,7 +158722,7 @@ 1C @@ -156045,6 +158785,66 @@ User-defined name for block. + + + + + + + + + + + + + + + + + + + + + + + + - + Machine-readable identifier for this accessory. + + - + User-supplied identifier for the beam current modulation pattern. Required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS. + + - + Start position defines the range modulator position at which the beam is switched on. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS. + + - + Stop position defines the range modulator position at which the beam is switched off. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS. + + @@ -169293,23 +171985,22 @@
RT Ion Beams Session Record Module Attributes
- Mass number of radiation. Required if Radiation Type (300A,00C6) is ION -
>Radiation Atomic Number @@ -155335,9 +158074,9 @@ 1C - Atomic number of radiation. Required if Radiation Type (300A,00C6) is ION -
>Radiation Charge State @@ -155349,9 +158088,9 @@ 1C - Charge state of radiation. Required if Radiation Type (300A,00C6) is ION -
>Scan Mode @@ -155969,7 +158708,7 @@ 1 - Number of shielding blocks associated with Beam. + Number of blocks recorded as being present during beam delivery.
- Sequence of blocks associated with Beam. + Sequence of blocks recorded as being present during beam delivery. Required if Number of Blocks (300A,00F0) is non-zero. One or more Items shall be included in this Sequence. The number of Items shall be identical to the value of Number of Blocks (300A,00F0). @@ -156015,6 +158754,7 @@ An accessory identifier to be read by a device such as a bar code reader. + Shall not be present if Recorded Block Slab Sequence (3008,00D1) is present.
+ >>Number of Block Slab Items + + (300A,0440) + + 3 + + Number of Block Slabs comprising the Block recorded as being present during beam delivery. +
+ >>Recorded Block Slab Sequence + + (3008,00D1) + + 1C + + Sequence of slab(s) that comprise the block recorded as being present during beam delivery. + Required if Number of Block Slab Items (300A,0440) is present and has a value greater than zero. + The number of Items included in this Sequence shall equal the value of Number of Block Slab Items (300A,0440). +
+ >>>Block Slab Number + + (300A,0443) + + 1 + + Identification number of the Block Slab. + The value shall start at 1, and increase monotonically by 1. + The number indicates the order of the slabs with respect to the source, where number 1 corresponds to the slab nearest to the source. +
+ >>>Accessory Code + + (300A,00F9) + + 3 + + Recorded machine-readable identifier for this accessory during beam delivery. +
>Recorded Snout Sequence @@ -156309,9 +159109,9 @@ 3 - Machine-readable identifier for this accessory -
>Number of Range Shifters @@ -156578,9 +159378,9 @@ 1C - User-supplied identifier for the beam current modulation pattern. Required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS -
@@ -156922,19 +159722,19 @@ HIGHEST - + MAXIMUM - + CENTER - + @@ -157378,9 +160178,9 @@ 1C - Start position defines the range modulator position at which the beam is switched on. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS -
>>>Range Modulator Gating Stop Value @@ -157392,9 +160192,9 @@ 1C - Stop position defines the range modulator position at which the beam is switched off. Required if Range Modulator Type (300A,0348) of the range modulator referenced by Referenced Range Modulator Number (300C,0104) is WHL_MODWEIGHTS or WHL_FIXEDWEIGHTS -
>>Gantry Angle @@ -157670,7 +160470,7 @@ Indicates that the spots were delivered in a different order than in the plan. - + Enumerated Values: YES @@ -158911,9 +161711,9 @@
- Beam Limiting Device Position Macro + Beam Limiting Device Position Macro - specifies the Attributes that specify the Beam Limiting Device Sequence. + specifies the Attributes of the , which specify the Beam Limiting Device Sequence. @@ -159020,9 +161820,9 @@
Beam Limiting Device Position Macro Attributes
- Patient Support Identification Macro + Patient Support Identification Macro - specifies the Attributes that identify the Patient Support System. + specifies the Attributes of the , which identify the Patient Support System. @@ -160572,9 +163372,9 @@ PET Information Module DefinitionsThis Section describes Positron Emission Tomography Series and Image Modules. These Modules contain Attributes that are specific to Positron Emission Tomography images.
- PET Series Module + PET Series Module - contains IOD Attributes that describe a PET Series. + specifies the Attributes of the , which describe a PET Series.
Patient Support Identification Macro Attributes
@@ -161073,9 +163873,9 @@ 3 - + Textual description of the convolution kernel(s) used to reconstruct the data (e.g., name, cutoff, radial/axial/angular, mathematical form, DC handling). + + - + Increasing Low R-R Value (0018,1081). + + - + Increasing Trigger Time (0018,1060). + + - + Increasing Frame Reference Time (0054,1300). + + @@ -163304,12 +166104,12 @@
PET Curve Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Hardcopy Modules - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
DX Modules @@ -163448,7 +166248,7 @@
PET Series Module Attributes
- Textual description of the convolution kernel(s) used to reconstruct the data (e.g., name, cutoff, radial/axial/angular, mathematical form, DC handling) -
Reconstruction Method @@ -161605,7 +164405,7 @@ The Janmahasatian LBM formula is defined in Janmahasatian et al. Quantification of Lean Bodyweight. Clin Pharmacokinet. 2005 Oct 1;44(10):1051–65. at and its role in SUVlbm(Janma) calculation is discussed in Tahari et al. Optimum Lean Body Formulation for Correction of Standardized Uptake Value in PET Imaging. Journal of Nuclear Medicine. 2014 Sep 1;55(9):1481–4. at . See also .
- PET Series Attribute Descriptions + PET Series Module Attribute Descriptions The meaning of a General Series in DICOM is determined by the Attributes in the and by the Source Entities (Patient, Study, Frame of Reference, Equipment) that originate the Series. The Source Entities are the single-valued entities of the 1->n relationship, where the Series is the multi-valued entity. Therefore, a Series is a group of images that: are from the same patient and Study; are from the same Equipment; and, are from the same spatial Frame of Reference. @@ -161998,9 +164798,9 @@
- PET Isotope Module + PET Isotope Module - contains IOD Attributes that describe a PET Isotope. + specifies the Attributes of the , which describe a PET Isotope. @@ -162404,9 +165204,9 @@
PET Isotope Module Attributes
- PET Multi-gated Acquisition Module + PET Multi-gated Acquisition Module - contains IOD Attributes that describe a PET Multi-gated Acquisition. + specifies the Attributes of the , which describe a PET Multi-gated Acquisition. @@ -162538,9 +165338,9 @@
PET Multi-Gated Acquisition Module Attributes
- PET Image Module + PET Image Module - contains IOD Attributes that describe PET images. + specifies the Attributes of the , which describe PET images. @@ -163029,7 +165829,7 @@
PET Image Module Attributes
- Referenced Overlay Sequence (0008,1130) and Referenced Curve Sequence (0008,1145) were previously included in this Module as optional Attributes but have been retired. See PS3.3-2004. + Referenced Overlay Sequence (0008,1130) and Referenced Curve Sequence (0008,1145) were previously included in this Module as optional Attributes but have been retired. See PS3.3-2004.
PET Image Module Attribute Descriptions @@ -163198,9 +165998,9 @@ 1 to Number of R-R Intervals (0054,0061)
- Increasing Low R-R Value (0018,1081) -
Time Slot Index @@ -163209,9 +166009,9 @@ 1 to Number of Time Slots (0054,0071) - Increasing Trigger Time (0018,1060) -
Time Slice Index @@ -163220,9 +166020,9 @@ 1 to Number of Time Slices (0054,0101) - Increasing Frame Reference Time (0054,1300) -
Slice Index @@ -163231,8 +166031,8 @@ 1 to Number of Slices (0054,0081) - If Series Type (0054,1000) Value 2 is IMAGE:Order is in increasing position along the normal, where the normal is determined by the cross product of the direction cosines of the row and column of the image. See Image Orientation (0020,0037) in the . - If Series Type (0054,1000) Value 2 is REPROJECTION:Order is in increasing or decreasing angle of the normal, where the normal is determined by the cross product of the direction cosines of the row and column of the image. See Image Orientation (0020,0037) in the . (Note that reprojection images rotate about only a single axis as described in . Therefore, all normals are co-planar and make a single angle with respect to each other.) + If Series Type (0054,1000) Value 2 is IMAGE: Order is in increasing position along the normal, where the normal is determined by the cross product of the direction cosines of the row and column of the image. See Image Orientation (0020,0037) in the . + If Series Type (0054,1000) Value 2 is REPROJECTION: Order is in increasing or decreasing angle of the normal, where the normal is determined by the cross product of the direction cosines of the row and column of the image. See Image Orientation (0020,0037) in the . (Note that reprojection images rotate about only a single axis as described in . Therefore, all normals are co-planar and make a single angle with respect to each other.)
- DX Series Attribute Descriptions + DX Series Module Attribute Descriptions
Presentation Intent Type Presentation Intent Type (0008,0068) shall identify the intent for the purposes of display or other presentation of all Images within this Series. @@ -163512,9 +166312,9 @@
- DX Anatomy Imaged Module + DX Anatomy Imaged Module - contains IOD Attributes that describe the anatomy contained in a DX IOD. + specifies the Attributes of the , which describe the anatomy contained in a DX IOD. @@ -163601,14 +166401,14 @@
DX Anatomy Imaged Module Attributes
- DX Anatomy Imaged Attribute Descriptions + DX Anatomy Imaged Module Attribute Descriptions The Attributes in this Module extend the function of Body Part Examined (0018,0015) as used in other IODs, and are intended to be used to facilitate the management of images and Series in terms of routing, storage and display, as well as to dictate certain Conditions on Attributes and Modules in the DX IOD.
- DX Image Module + DX Image Module - contains IOD Attributes that describe a DX Image by specializing Attributes of the and , and adding additional Attributes. + specifies the Attributes of the , which describe a DX Image by specializing Attributes of the and , and adding additional Attributes. @@ -164285,7 +167085,7 @@
DX Image Module Attributes
- DX Image Attribute Descriptions + DX Image Module Attribute Descriptions
Image Type Value 1 shall identify the Pixel Data Characteristics in accordance with where the Enumerated Values are defined to be ORIGINAL or DERIVED. @@ -164357,9 +167157,9 @@
- DX Detector Module + DX Detector Module - contains IOD Attributes that describe a DX detector. + specifies the Attributes of the , which describe a DX detector. @@ -164847,9 +167647,9 @@ 3 - + Name of the manufacturer of the detector component of the acquisition system. + + - + Model name of the detector component of the acquisition system. + +
DX Detector Module Attributes
- Name of the manufacturer of the detector component of the acquisition system -
Detector Manufacturer's Model Name @@ -164861,9 +167661,9 @@ 3 - Model name of the detector component of the acquisition system -
Detector Conditions Nominal Flag @@ -164928,7 +167728,7 @@ This value is intended to provide a single location where manufacturer specific information can be found for annotation on a display or film, that has meaning to a knowledgeable observer. - This value is manufacturer-specific. DICOM specifies Standard Attributes in 'Exposure Index Macro', which are recommended. + This value is manufacturer-specific. DICOM specifies Standard Attributes in the , which are recommended. @@ -165057,7 +167857,7 @@
- DX Detector Attribute Descriptions + DX Detector Module Attribute Descriptions
Physical, Active, Field of View, Exposed and Displayed Areas The relationship between the Physical Detector Area, the Active Detector Area, the Field of View (what is stored in Pixel Data (7FE0,0010)), the Exposed Area (after X-Ray Collimation) and the Displayed Area is illustrated in the following diagrams. @@ -165184,9 +167984,9 @@
- DX Positioning Module + DX Positioning Module - contains IOD Attributes that describe the positioning used in acquiring Digital X-Ray Images. + specifies the Attributes of the , which describe the positioning used in acquiring Digital X-Ray Images. @@ -165746,7 +168546,7 @@
DX Positioning Module Attributes
- DX Positioning Attribute Descriptions + DX Positioning Module Attribute Descriptions
View Code Sequence View Code Sequence (0054,0220) replaces the function of View Position (0018,5101), and describes the radiographic view of the image relative to the real-world patient orientation as described in . @@ -165758,9 +168558,9 @@
- Mammography Series Module + Mammography Series Module - specifies the Attributes that identify and describe general information about a Digital Mammography Series. + specifies the Attributes of the , which identify and describe general information about a Digital Mammography Series. @@ -165828,8 +168628,7 @@
Mammography Series Module Attributes
- Reason for Requested Procedure Code Sequence (0040,100A) B - and B. + Reason for Requested Procedure Code Sequence (0040,100A) B and B. No Baseline CIDs are defined for other Attributes. @@ -165843,9 +168642,9 @@
- Mammography Image Module + Mammography Image Module - contains IOD Attributes that describe a Digital Mammography X-Ray Image including its acquisition and positioning. + specifies the Attributes of the , which describe a Digital Mammography X-Ray Image including its acquisition and positioning. @@ -166364,7 +169163,7 @@
Mammography Image Module Attributes
- Mammography Image Attribute Descriptions + Mammography Image Module Attribute Descriptions
Mammography X-Ray Beam and X-Ray Beam Vector Definition @@ -167228,9 +170027,9 @@
- Intra-Oral Series Module + Intra-Oral Series Module - specifies the Attributes that identify and describe general information about a Digital Intra-Oral X-Ray Series. + specifies the Attributes of the , which identify and describe general information about a Digital Intra-Oral X-Ray Series. @@ -167278,9 +170077,9 @@
Intra-Oral Series Module Attributes
- Intra-Oral Image Module + Intra-Oral Image Module - contains IOD Attributes that describe a Digital Intra-Oral X-Ray Image including its acquisition and positioning. + specifies the Attributes of the , which describe a Digital Intra-Oral X-Ray Image including its acquisition and positioning. @@ -167461,13 +170260,10 @@
Intra-Oral Image Module Attributes
- Intra-Oral Image Attribute Descriptions + Intra-Oral Image Module Attribute Descriptions
Primary Anatomic Structure Sequence - D. - This Context Group includes D, for permanent dentition, - D for deciduous dentition and - D for supernumerary dentition. + D. This Context Group includes D, for permanent dentition, D for deciduous dentition and D for supernumerary dentition. These Context Groups contain concepts that are mapped to ISO 3950-2010, which describes a designation of permanent and deciduous dentition using a two digit code, the first digit of which designates a quadrant, and the second digit a tooth. The teeth imaged shall be listed as multiple Items in the Primary Anatomic Structure Sequence (0008,2228).
@@ -167572,8 +170368,7 @@
- Reason for Requested Procedure Code Sequence (0040,100A) B - and B. + Reason for Requested Procedure Code Sequence (0040,100A) B and B. No Baseline CIDs are defined for other Attributes. @@ -167590,9 +170385,9 @@
VL Modules and Functional Group Macros
- VL Image Module + VL Image Module - specifies the Attributes that describe a VL Image produced by Endoscopy (ES), General Microscopy (GM), Automated-Stage Microscopy (SM), External-camera Photography (XC), Dermoscopy (DMS), or other VL imaging Modalities. + specifies the Attributes of the , which describe a VL Image produced by Endoscopy (ES), General Microscopy (GM), Automated-Stage Microscopy (SM), External-camera Photography (XC), Dermoscopy (DMS), or other VL imaging Modalities. @@ -167949,8 +170744,7 @@ B for the VL Photographic Image IOD and Dermoscopic Photography Image IOD for dermatology applications. - B for humans - and B for animals. + B for humans and B for animals. @@ -168281,7 +171075,7 @@ There is no a priori correspondence of pixels to Slide Coordinates. Therefore, the geometrical symmetry point through the pixel plane of the digital microscope may not correspond to the center of a pixel. The geometrical symmetry point could be between pixels. - This Module formerly included a Type 3 Attribute Pixel Spacing Sequence (0040,08D8), and subsidiary Attributes; see PS3.3-2009. Pixel Spacing is an Attribute of the image acquisition, not the slide coordinates, and is inappropriate for this Module. It is now conveyed by Pixel Spacing (0028,0030) in the or the Pixel Measures Functional Group (see ). + This Module formerly included a Type 3 Attribute Pixel Spacing Sequence (0040,08D8), and subsidiary Attributes; see PS3.3-2009. Pixel Spacing is an Attribute of the image acquisition, not the slide coordinates, and is inappropriate for this Module. It is now conveyed by Pixel Spacing (0028,0030) in the or the Pixel Measures Functional Group (see ). @@ -168359,13 +171153,16 @@ 2
VL Image Module Attributes
- The Z offset in microns from the image substrate reference plane (i.e., utilized surface of a glass slide). + The Z offset in µm from the image substrate reference plane (i.e., utilized surface of a glass slide). + + The use of units of microns is inconsistent with the use of millimeters for Point Coordinates Data (0066,0016), Double Point Coordinates Data (0066,0022) and Common Z Coordinate Value (006A,0010) in the . +
- Slide Coordinates Attribute Descriptions + Slide Coordinates Module Attribute Descriptions
Image Center Point Coordinates Sequence This Section defines the Slide Coordinate System and specifies the Attributes that shall be used to describe the location of the center point of the Image pixel plane (as captured through a microscope) in the Slide Coordinate System Frame of Reference. @@ -168431,7 +171228,7 @@
Whole Slide Microscopy Series Module - specifies Attributes for the Whole Slide Microscopy Series Module, including specialization of Attributes in the for use in the Whole Slide Microscopy Series Module. + specifies Attributes for the Whole Slide Microscopy Series Module, including specialization of Attributes in the for use in this Module. @@ -168506,9 +171303,9 @@
Whole Slide Microscopy Series Module Attributes
- Whole Slide Microscopy Image Module + Whole Slide Microscopy Image Module - specifies the Attributes that describe the Whole Slide Microscopy Image Module. + specifies the Attributes of the . @@ -168551,11 +171348,12 @@ (0048,0001) @@ -168566,11 +171364,12 @@ (0048,0002) @@ -168581,119 +171380,12 @@ (0048,0003) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -168786,7 +171478,7 @@ - This Enumerated Value of 1 previously applied to Image Type (0008,0008) Value 3 of LOCALIZER, which has been retired. See PS3.3-2021c. + This Enumerated Value of 1 previously applied to Image Type (0008,0008) Value 3 of LOCALIZER, which has been retired. See PS3.3-2021c. @@ -169085,8 +171777,8 @@ - Shall be YES if Image Type (0008,0008) Value 3 is OVERVIEW or LABEL. - Shall be NO if Image Type (0008,0008) Value 3 is THUMBNAIL or VOLUME. + Shall be YES if Image Type (0008,0008) Value 3 is OVERVIEW or LABEL. + Shall be NO if Image Type (0008,0008) Value 3 is THUMBNAIL or VOLUME. @@ -169226,9 +171918,9 @@ 3 - + Description of visual processing performed on the image prior to exchange. Examples of this processing are: edge enhanced, gamma corrected, convolved (spatially filtered). + + - + Label for convolution kernel used in acquisition device visual processing. + +
Whole Slide Microscopy Image Module Attributes
- 1 + 1C Width of total imaged volume (distance in the direction of rows in each frame) in mm. See + Required if Image Type (0008,0008) Value 3 is VOLUME. May be present otherwise.
- 1 + 1C Height of total imaged volume (distance in the direction of columns in each frame) in mm. See + Required if Image Type (0008,0008) Value 3 is VOLUME. May be present otherwise.
- 1 + 1C Depth of total imaged volume (distance in the Z direction of focal planes) in µm. See -
- Total Pixel Matrix Columns - - (0048,0006) - - 1 - - Total number of columns in pixel matrix; i.e., width of total imaged volume in pixels. See - -
- Total Pixel Matrix Rows - - (0048,0007) - - 1 - - Total number of rows in pixel matrix; i.e., height of total imaged volume in pixels. See - -
- Total Pixel Matrix Focal Planes - - (0048,0303) - - 1C - - Total number of focal planes (Z locations) in the pixel matrix; i.e., depth of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. - - Total Pixel Matrix Focal Planes (0048,0303) describes the number of focal planes separately encoded, and is distinct from Number of Focal Planes (0048,0013), which describes in what manner different focal planes were combined into a single encoded plane (focus stacking). - -
- Total Pixel Matrix Origin Sequence - - (0048,0008) - - 1 - - Location of pixel 1\1 of the total pixel matrix in the Slide Coordinate System Frame of Reference. - Only a single Item shall be included in this Sequence. - See and for further explanation. -
- >X Offset in Slide Coordinate System - - (0040,072A) - - 1 - - The X offset in millimeters from the Origin of the Slide Coordinate System. -
- >Y Offset in Slide Coordinate System - - (0040,073A) - - 1 - - The Y offset in millimeters from the Origin of the Slide Coordinate System. -
- Image Orientation (Slide) - - (0048,0102) - - 1 - - The direction cosines of the first row and the first column of the total pixel matrix with respect to the Slide Coordinate System Frame of Reference. See - + Required if Image Type (0008,0008) Value 3 is VOLUME. May be present otherwise.
- Description of visual processing performed on the image prior to exchange. Examples of this processing are: edge enhanced, gamma corrected, convolved (spatially filtered) -
Convolution Kernel @@ -169240,9 +171932,9 @@ 3 - Label for convolution kernel used in acquisition device visual processing -
Recommended Absent Pixel CIELab Value @@ -169260,7 +171952,7 @@
- Whole Slide Microscopy Image Attribute Descriptions + Whole Slide Microscopy Image Module Attribute Descriptions
Image Type Image Type (0008,0008) is specified to be Type 1 with the following constraints: @@ -169275,7 +171967,7 @@ VOLUME
- Set of frames that define a regularly sampled volume; shall not include the label. + Set of frames that define a regularly sampled volume; shall not include the label; may be used for each layer of a Multi-Resolution Pyramid.
Purpose of image is to provide an overview of the entire glass slide; shall include at least part of the label, all of the specimen and the empty space that are shown in . - One purpose of the OVERVIEW image is to allow visual quality control to assure that tissue fragments have not been omitted when selecting areas (manually or automatically) to digitize at high resolution. - The OVERVIEW image is distinct from the lowest resolution VOLUME image(s) of Whole Slide Microscopy Image pyramids, and the THUMBNAIL image, neither of which includes the label. + One purpose of the OVERVIEW image is to allow visual quality control to assure that tissue fragments have not been omitted when selecting areas (manually or automatically) to digitize at high resolution. The OVERVIEW image is distinct from the lowest resolution VOLUME image(s) of Whole Slide Microscopy Image pyramids, and the THUMBNAIL image, neither of which includes the label.
- THUMBNAIL + THUMBNAIL - Purpose of image is to provide an overview of the specimen; shall not include the label. + Purpose of image is to provide an overview of the specimen; shall not include the label; may be the apex (lowest resolution) layer of a Multi-Resolution Pyramid.
- A Value 3 of LOCALIZER was previously defined, which triggered the mandatory inclusion of the retired . See PS3.3-2021c. + A Value 3 of LOCALIZER was previously defined, which triggered the mandatory inclusion of the retired . See PS3.3-2021c. Value 4 (Derived Pixel) shall have the Defined Terms specified in . @@ -169320,17 +172011,17 @@ NONE - + No derivation of pixels (original). + + - + Pixels were derived by down sampling a higher resolution image. + +
- No derivation of pixels (original) -
RESAMPLED - Pixels were derived by down sampling a higher resolution image -
No additional values shall be present. @@ -169342,15 +172033,11 @@
Total Pixel Matrix Columns, Rows, Focal Planes - Total Pixel Matrix Columns (0048,0006), Total Pixel Matrix Rows (0048,0007) and Total Pixel Matrix Focal Planes (0048,0303) describe the size of the entire imaged volume as a single extent across all frames (tiles). - The extent would be as described in these Attributes if the whole volume would be imaged and encoded as a non-sparse pixel matrix with the pixel spacing as specified in Pixel Spacing (0028,0030) of the Pixel Measures Functional Group (see ), such as when Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. + See .
Total Pixel Matrix Origin Sequence and Image Orientation (Slide) - Total Pixel Matrix Origin Sequence (0048,0008) specifies the location of the top leftmost pixel of the pixel matrix, and Image Orientation (Slide) (0048,0102) specifies the direction cosines of the first row and the first column of the pixel matrix, both with respect to the Slide Coordinate System Frame of Reference (see ). Although the image acquisition may vary the true row and column orientation at the pixel scale to account for local variation in the physical specimen, this Attribute describes the orientation as if the Pixel Matrix were flat. - - Typically, Image Orientation (Slide) will describe only a planar rotation, as the image plane is usually nominally parallel to the slide surface. - + See .
Photometric Interpretation and Samples Per Pixel @@ -169646,9 +172333,9 @@ 3 - Nominal pass-through wavelength of light path filter(s) in nm - - + Nominal pass-through wavelength of light path filter(s) in nm. + + >Light Path Filter Pass Band @@ -169704,9 +172391,9 @@ 3 - Nominal pass-through wavelength of image path filter(s) in nm - - + Nominal pass-through wavelength of image path filter(s) in nm. + + >Image Path Filter Pass Band @@ -169719,9 +172406,9 @@ Pass band of image path filter(s) in nm. This Attribute has two Values. The first is the shorter and the second the longer wavelength relative to the peak. The values are for the - 3dB nominal (1/2 of peak) pass through intensity. - One of the two Values may be zero length, in which case it is a cutoff filter - - + One of the two Values may be zero length, in which case it is a cutoff filter. + + >Lenses Code Sequence @@ -169761,9 +172448,9 @@ 3 - Nominal power of the condenser lens - - + Nominal power of the condenser lens. + + >Objective Lens Power @@ -169891,7 +172578,7 @@
- Optical Path Attribute Descriptions + Optical Path Module Attribute Descriptions
Optical Path Sequence and Optical Path Identifier The Optical Path Sequence (0048,0105) shall include an Item for every optical path used in the acquisition of the current image. @@ -169936,10 +172623,10 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean "for all frames".
- Plane Position (Slide) Macro - - specifies the Attributes of the Plane Position (Slide) Functional Group Macro. - + Plane Position (Slide) Macro + + specifies the Attributes of the . +
@@ -170051,9 +172738,9 @@
Plane Position (Slide) Macro Attributes
- Optical Path Identification Macro - - specifies the Attributes of the Optical Path Identification Functional Group Macro. + Optical Path Identification Macro + + specifies the Attributes of the . @@ -170106,9 +172793,9 @@
Optical Path Identification Macro Attributes
- Specimen Reference Macro - - specifies the Attributes of the Specimen Reference Functional Group Macro. This allows association of the frame with specific specimens imaged on the same slide (e.g., tissue micro-arrays). + Specimen Reference Macro + + specifies the Attributes of the . This allows association of the frame with specific specimens imaged on the same slide (e.g., tissue micro-arrays). @@ -170166,9 +172853,9 @@ Retired. See PS3.3-2021c.
- Slide Label Module + Slide Label Module - specifies the Attributes that describe the interpretation of a scanned Slide Label. + specifies the Attributes of the , which describe the interpretation of a scanned Slide Label.
Specimen Reference Macro Attributes
@@ -170223,9 +172910,9 @@
Slide Label Module Attributes
- Whole Slide Microscopy Image Frame Type Macro + Whole Slide Microscopy Image Frame Type Macro - specifies the Attributes of the Whole Slide Microscopy Image Frame Type Functional Group Macro. + specifies the Attributes of the . @@ -170280,9 +172967,9 @@
- VL Photographic Equipment Module + VL Photographic Equipment Module - specifies the Attributes that identify and describe a photographic device such as a camera. + specifies the Attributes of the , which identify and describe a photographic device such as a camera.
Whole Slide Microscopy Image Frame Type Macro Attributes
@@ -170378,9 +173065,9 @@
- VL Photographic Acquisition Module + VL Photographic Acquisition Module - specifies the Attributes that describe the process of acquisition of a photographic image. + specifies the Attributes of the , which describe the process of acquisition of a photographic image.
VL Photographic Equipment Module Attributes
@@ -171224,7 +173911,7 @@ @@ -173895,143 +176746,15 @@ Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and SOP Class UID is not "1.2.840.10008.5.1.4.1.1.4.4" (Legacy Converted). May be present otherwise. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -174340,16 +177063,15 @@
Evidence Sequence Attributes - The intent of the Referenced Image Evidence Sequence (0008,9092) and Source Image Evidence Sequence (0008,9154) is to provide a list of all unique SOP Instances listed in the Referenced Image Sequence (0008,1140) and Source Image Sequence (0008,2112) Attributes respectively. + See .
- MR Image Description Macro - This section describes the MR Image Description Macro. - - specifies the Attributes of the MR Image Description Macro. -
The detection of returned light from firing of the flash (strobe light). - + Defined Terms: 0 @@ -171266,7 +173953,7 @@ The camera's flash (strobe light) mode. - + Defined Terms: 0 @@ -171307,7 +173994,7 @@ Whether or not the camera has a flash function flash (strobe light). - + Defined Terms: 0 @@ -171336,7 +174023,7 @@ Whether or not the camera supports red-eye reduction. - + Defined Terms: 0 @@ -172045,7 +174732,7 @@ Identification of the interoperability rule to which the image conforms. - + Defined Terms: R98 @@ -172089,9 +174776,9 @@
- VL Photographic Geolocation Module + VL Photographic Geolocation Module - specifies the Attributes that describe the geographic location during acquisition of a photographic image. + specifies the Attributes of the , which describe the geographic location during acquisition of a photographic image. @@ -172137,7 +174824,7 @@
VL Photographic Geolocation Module Attributes
Whether the latitude is north or south latitude. - + Enumerated Values: N @@ -172180,7 +174867,7 @@ Whether the longitude is east or west longitude. - + Enumerated Values: E @@ -172280,7 +174967,7 @@ The status of the GPS receiver when the image is recorded. - + Enumerated Values: A @@ -172309,7 +174996,7 @@ The GPS measurement mode. - + Enumerated Values: 2 @@ -172353,7 +175040,7 @@ The unit used to express the GPS Speed (0016,007D). - + Enumerated Values: K @@ -172402,7 +175089,7 @@ The reference for giving the direction of GPS receiver movement. - + Enumerated Values: T @@ -172445,7 +175132,7 @@ The reference for giving the direction of the image when it is captured. - + Enumerated Values: T @@ -172502,7 +175189,7 @@ Whether the latitude of the destination point is north or south latitude. - + Enumerated Values: N @@ -172545,7 +175232,7 @@ Whether the longitude of the destination point is east or west longitude. - + Enumerated Values: E @@ -172588,7 +175275,7 @@ Indicates the reference used for giving the bearing to the destination point. - + Enumerated Values: T @@ -172631,7 +175318,7 @@ The unit used to express the distance to the destination point. - + Enumerated Values: K @@ -172731,7 +175418,7 @@
Dermoscopic Image Module - specifies the Attributes that describe dermoscopic images. + specifies the Attributes that describe dermoscopic images. @@ -172778,9 +175465,9 @@ - The value of Recognizable Visual Features (0028,0302) shall be YES if the image contains the patient's fingerprints - - + The value of Recognizable Visual Features (0028,0302) shall be YES if the image contains the patient's fingerprints. + + - + Required if Contact Method (0016,1003) is CONTACT. + + @@ -172975,8 +175657,7 @@ 1C
Dermoscopic Image Module Attributes
Light Source Polarization @@ -172898,9 +175585,9 @@ - Required if Contact Method (0016,1003) is CONTACT -
Optical Magnification Factor @@ -172912,12 +175599,7 @@ 2 - Optical magnification factor when the image was acquired. - Optical magnification is achieved using the optics of the dermoscope. - The number indicates the magnification factor in times (X). - The size of an object (e.g., a skin lesion) would appear on the sensor - n times larger than the object when imaged with a dermoscope using - n X optical magnification. + Optical magnification factor when the image was acquired. Optical magnification is achieved using the optics of the dermoscope. The number indicates the magnification factor in times (X). The size of an object (e.g., a skin lesion) would appear on the sensor n times larger than the object when imaged with a dermoscope using n X optical magnification.
- A text label used for tracking a finding or feature, potentially across multiple reporting objects, over time. - This label shall be unique within the domain in which it is used. + A text label used for tracking a finding or feature, potentially across multiple reporting objects, over time. This label shall be unique within the domain in which it is used. Required if Tracking UID (0062,0021) is present. This Attribute allows linkage to Content Items in SR instances with observation context (112039, DCM, "Tracking Identifier") having the same value. @@ -173004,16 +175685,186 @@
+
+ Microscope Slide Layer Tile Organization Module + + specifies the Attributes of the , which describe the logical and physical organization of the tiles within a single resolution layer encoded as a tiled Image, such as that of a Multi-Resolution Pyramid. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Microscope Slide Layer Tile Organization Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Total Pixel Matrix Columns + + (0048,0006) + + 1 + + Total number of columns in pixel matrix; i.e., width of total imaged volume in pixels. See + +
+ Total Pixel Matrix Rows + + (0048,0007) + + 1 + + Total number of rows in pixel matrix; i.e., height of total imaged volume in pixels. See + +
+ Total Pixel Matrix Focal Planes + + (0048,0303) + + 1C + + Total number of focal planes (Z locations) in the pixel matrix; i.e., depth of total imaged volume in pixels. See + + Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. + + Total Pixel Matrix Focal Planes (0048,0303) describes the number of focal planes separately encoded, and is distinct from Number of Focal Planes (0048,0013), which describes in what manner different focal planes were combined into a single encoded plane (focus stacking). + +
+ Total Pixel Matrix Origin Sequence + + (0048,0008) + + 1 + + Location of pixel 1\1 of the total pixel matrix in the Slide Coordinate System Frame of Reference. + Only a single Item shall be included in this Sequence. + See and for further explanation. +
+ >X Offset in Slide Coordinate System + + (0040,072A) + + 1 + + The X offset in millimeters from the Origin of the Slide Coordinate System. +
+ >Y Offset in Slide Coordinate System + + (0040,073A) + + 1 + + The Y offset in millimeters from the Origin of the Slide Coordinate System. +
+ >Z Offset in Slide Coordinate System + + (0040,074A) + + 1C + + The Z offset in µm from the image substrate reference plane (i.e., utilized surface of a glass slide). + Required if the Z offset is not zero. May be present otherwise. + + The conditional requirement is used because, historically, this Attribute was not present. + +
+ Image Orientation (Slide) + + (0048,0102) + + 1C + + The direction cosines of the first row and the first column of the total pixel matrix with respect to the Slide Coordinate System Frame of Reference. See . + Required if Plane Position (Slide) Sequence (0048,021A) is present within a Functional Group Sequence or Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. + + This condition will always be satisfied when this Module is included in the Whole Slide Microscopy Image IOD. + +
+
+ Microscope Slide Layer Tile Organization Module Attribute Descriptions +
+ Total Pixel Matrix Columns, Rows, Focal Planes + Total Pixel Matrix Columns (0048,0006), Total Pixel Matrix Rows (0048,0007) and Total Pixel Matrix Focal Planes (0048,0303) describe the size of the entire imaged volume as a single extent across all frames (tiles). + The extent would be as described in these Attributes if the whole volume would be imaged and encoded as a non-sparse pixel matrix with the pixel spacing as specified in Pixel Spacing (0028,0030) of the Pixel Measures Functional Group (see ), such as when Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. +
+
+ Total Pixel Matrix Origin Sequence and Image Orientation (Slide) + Total Pixel Matrix Origin Sequence (0048,0008) specifies the location of the top leftmost pixel of the pixel matrix, and Image Orientation (Slide) (0048,0102) specifies the direction cosines of the first row and the first column of the pixel matrix, both with respect to the Slide Coordinate System Frame of Reference (see ). Although the image acquisition may vary the true row and column orientation at the pixel scale to account for local variation in the physical specimen, this Attribute describes the orientation as if the Pixel Matrix were flat. + + Typically, Image Orientation (Slide) will describe only a planar rotation, as the image plane is usually nominally parallel to the slide surface. + +
+
+
Enhanced MR Image This section describes the specific Modules for the Enhanced MR Image IOD.
- Enhanced MR Image Module - This section describes the Enhanced MR Image Module. - - specifies the Attributes of the Enhanced MR Image Module. - + Enhanced MR Image Module + + specifies the Attributes of the . +
@@ -173398,25 +176249,25 @@ ANGIO_TIME - + Angio time acquisition (peripheral vascular/carotid). + + - + Arterial Spin Labeling. + + - + Cardiac CINE. + + - + Flow Encoded. + + - + Fluid Attenuated T2 weighted. + + - + Maximum Intensity Projection. + + - + Minimum Intensity Projection. + + - + Image line over time. + + - + Metabolite Maps from spectroscopy data. + + - + Multiple echoes with different contrast weighting (e.g., proton density and T2 weighted). + + - + Proton density weighted. + + - + Real-time collection of single slices. + + - + Short Tau Inversion Recovery. + + - + Images with superposition of thin saturation bands. + + - + Images record temperature. + + - + T1 weighted. + + - + T2 weighted. + + - + T2* weighted. + + - + Time Of Flight weighted. + + - + Velocity encoded. + +
Enhanced MR Image Module Attributes
- Angio time acquisition (peripheral vascular/carotid) -
ASL - Arterial Spin Labeling -
CINE - Cardiac CINE -
DIFFUSION @@ -173438,17 +176289,17 @@ FLOW_ENCODED - Flow Encoded -
FLUID_ATTENUATED - Fluid Attenuated T2 weighted -
FMRI @@ -173462,121 +176313,121 @@ MAX_IP - Maximum Intensity Projection -
MIN_IP - Minimum Intensity Projection -
M_MODE - Image line over time -
METABOLITE_MAP - Metabolite Maps from spectroscopy data -
MULTIECHO - Multiple echoes with different contrast weighting (e.g., proton density and T2 weighted) -
PROTON_DENSITY - Proton density weighted -
REALTIME - Real-time collection of single slices -
STIR - Short Tau Inversion Recovery -
TAGGING - Images with superposition of thin saturation bands -
TEMPERATURE - Images record temperature -
T1 - T1 weighted -
T2 - T2 weighted -
T2_STAR - T2* weighted -
TOF - Time Of Flight weighted -
VELOCITY - Velocity encoded -
@@ -173608,7 +176459,7 @@
- This table formerly contained defined terms such as ADC, etc. These have been replaced with the use of QUANTITY and the appropriate coded entry used in Quantity Definition Sequence (0040,9220) of the . For former defined terms, see PS3.3 2018c. + This table formerly contained defined terms such as ADC, etc. These have been replaced with the use of QUANTITY and the appropriate coded entry used in Quantity Definition Sequence (0040,9220) of the . For former defined terms, see PS3.3-2018c.
@@ -173875,7 +176726,7 @@ 		The date and time that the acquisition of data started. - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). Required if Image Type (0008,0008) Value 1 is ORIGINAL or MIXED and SOP Class UID is not "1.2.840.10008.5.1.4.1.1.4.4" (Legacy Converted). May be present otherwise.
- Referenced Raw Data Sequence - - (0008,9121) - - 3 - - The Raw data that was used to derive this Image. - One or more Items are permitted in this Sequence. - - The Items of in this Sequence may identify raw data that has not been stored or encoded as a DICOM object. This allows recognition that images and spectra in different Instances have been reconstructed from the same raw data. - -
- - >Include - - - - -
- Referenced Waveform Sequence - - (0008,113A) - - 3 - - References to waveforms acquired in conjunction with this image. These Waveforms may or may not be temporally synchronized with this image. - One or more Items are permitted in this Sequence. -
- - >Include - - - - -
- Referenced Image Evidence Sequence - - (0008,9092) - - 1C - - Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this Enhanced MR Image SOP Instance. See for further explanation. - One or more Items shall be included in this Sequence. - Required if the Referenced Image Sequence (0008,1140) is present. -
- - >Include - - - - -
- Source Image Evidence Sequence - - (0008,9154) - - 1C - - Full set of Composite SOP Instances referred to inside the Source Image Sequences of this Enhanced MR Image SOP Instance. See for further explanation. - One or more Items shall be included in this Sequence. - Required if the Source Image Sequence (0008,2112) is present. -
- - >Include - - - - -
- Referenced Presentation State Sequence - - (0008,9237) - - 1C - - References to Presentation State instances created together with this instance - - This Sequence does not reference Presentation States generated after image creation, such as during interpretation. - - One or more Items shall be included in this Sequence. - Required if Presentation State is created together with the images. -
- - >Include + + Include - +
+ MR Image Description Macro + + specifies the Attributes of the . +
@@ -174514,89 +177236,89 @@ DIFFUSION - + Diffusion weighted contrast. + + - + Flow Encoded contrast. + + - + Fluid Attenuated T2 weighted contrast. + + - + Perfusion weighted contrast. + + - + Proton Density weighted contrast. + + - + Short Tau Inversion Recovery. + + - + Superposition of thin saturation bands onto image. + + - + T1 weighted contrast. + + - + T2 weighted contrast. + + - + T2* weighted contrast. + + - + Time Of Flight weighted contrast. + + @@ -240503,7 +243798,7 @@ (2010,0080) @@ -240530,7 +243825,7 @@ - i where i represents the desired density in hundredths of OD (e.g., 150 corresponds with 1.5 OD) + i where i represents the desired density in hundredths of OD (e.g., 150 corresponds with 1.5 OD). @@ -240557,7 +243852,7 @@ - i where i represents the desired density in hundredths of OD (e.g., 150 corresponds with 1.5 OD) + i where i represents the desired density in hundredths of OD (e.g., 150 corresponds with 1.5 OD). @@ -241052,7 +244347,7 @@ (0028,0010) @@ -241063,7 +244358,7 @@ (0028,0011) @@ -241074,7 +244369,7 @@ (0028,0034) @@ -241189,7 +244484,7 @@ (7FE0,0010) @@ -241386,13 +244681,80 @@ (7FE0,0010) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
MR Image Description Macro Attributes
- Diffusion weighted contrast -
FLOW_ENCODED - Flow Encoded contrast -
FLUID_ATTENUATED - Fluid Attenuated T2 weighted contrast -
PERFUSION - Perfusion weighted contrast -
PROTON_DENSITY - Proton Density weighted contrast -
STIR - Short Tau Inversion Recovery -
TAGGING - Superposition of thin saturation bands onto image -
T1 - T1 weighted contrast -
T2 - T2 weighted contrast -
T2_STAR - T2* weighted contrast -
TOF - Time Of Flight weighted contrast -
UNKNOWN @@ -174619,10 +177341,10 @@
- MR Pulse Sequence Module - The primary purpose of this Module is to identify the pulse sequence and variations on that, which was used in creation of the image. Terminology is intended to be neutral, and allow equivalent sequences provided by different vendors to be classified the same. + MR Pulse Sequence Module - specifies the Attributes of the MR Pulse Sequence Module. + specifies the Attributes of the . + The primary purpose of this Module is to identify the pulse sequence and variations on that, which was used in creation of the image. Terminology is intended to be neutral, and allow equivalent sequences provided by different vendors to be classified the same. @@ -175304,9 +178026,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".".
- MR Image Frame Type Macro - - specifies the Attributes of the MR Image Frame Type Functional Group Macro. + MR Image Frame Type Macro + + specifies the Attributes of the .
MR Pulse Sequence Module Attributes
@@ -175382,9 +178104,9 @@
MR Image Frame Type Macro Attributes
- MR Timing and Related Parameters Macro - - specifies the Attributes of the MR Timing and Related Parameters Functional Group Macro. + MR Timing and Related Parameters Macro + + specifies the Attributes of the . @@ -175803,10 +178525,10 @@
- MR FOV/Geometry Macro - - specifies the Attributes of the MR FOV/Geometry Functional Group Macro. -
MR Timing and Related Parameters Macro Attributes
+ MR FOV/Geometry Macro + + specifies the Attributes of the . +
@@ -175955,9 +178677,9 @@
MR FOV/Geometry Macro Attributes
- MR Echo Macro - - specifies the Attributes of the MR Echo Functional Group Macro. + MR Echo Macro + + specifies the Attributes of the . @@ -176011,9 +178733,9 @@
MR Echo Macro Attributes
- MR Modifier Macro - - specifies the Attributes of the MR Modifier Functional Group Macro. + MR Modifier Macro + + specifies the Attributes of the . @@ -176541,9 +179263,9 @@
MR Modifier Macro Attributes
- MR Imaging Modifier Macro - - specifies the Attributes of the MR Imaging Modifier Functional Group Macro. + MR Imaging Modifier Macro + + specifies the Attributes of the . @@ -176808,9 +179530,9 @@
MR Imaging Modifier Macro Attributes
- MR Receive Coil Macro - - specifies the Attributes of the MR Receive Coil Functional Group Macro. + MR Receive Coil Macro + + specifies the Attributes of the . @@ -177023,9 +179745,9 @@
MR Receive Coil Macro Attributes
- MR Transmit Coil Macro - - specifies the Attributes of the MR Transmit Coil Functional Group Macro. + MR Transmit Coil Macro + + specifies the Attributes of the . @@ -177130,9 +179852,9 @@
MR Transmit Coil Macro Attributes
- MR Diffusion Macro - - specifies the Attributes of the MR Diffusion Functional Group Macro. + MR Diffusion Macro + + specifies the Attributes of the . @@ -177398,9 +180120,9 @@
MR Diffusion Macro Attributes
- MR Averages Macro - - specifies the Attributes of the MR Averages Functional Group Macro. + MR Averages Macro + + specifies the Attributes of the . @@ -177454,9 +180176,9 @@
MR Averages Macro Attributes
- MR Spatial Saturation Macro - - specifies the Attributes of the MR Spatial Saturation Functional Group Macro. + MR Spatial Saturation Macro + + specifies the Attributes of the . @@ -177537,9 +180259,9 @@
MR Spatial Saturation Macro Attributes
- MR Metabolite Map Macro - - specifies the Attributes of the MR Metabolite Map Functional Group Macro. + MR Metabolite Map Macro + + specifies the Attributes of the . @@ -177664,9 +180386,9 @@
MR Metabolite Map Macro Attributes
- MR Velocity Encoding Macro - - specifies the Attributes of the MR Velocity Encoding Functional Group Macro. This Functional Group contains the velocity encoding values as valid for the reconstructed Images, rather than for their acquisition. The velocity encoding directions for acquisition are described in the Velocity Encoding Acquisition Sequence (0018,9092) defined in the . + MR Velocity Encoding Macro + + specifies the Attributes of the . This Functional Group contains the velocity encoding values as valid for the reconstructed Images, rather than for their acquisition. The velocity encoding directions for acquisition are described in the Velocity Encoding Acquisition Sequence (0018,9092) defined in the . @@ -177755,9 +180477,9 @@
- MR Arterial Spin Labeling Macro - - specifies the Attributes of the MR Arterial Spin Labeling Functional Group Macro. + MR Arterial Spin Labeling Macro + + specifies the Attributes of the .
MR Velocity Encoding Macro Attributes
@@ -178115,9 +180837,10 @@
- Functional MR Macro - Table C.8-100c specifies the Attributes of the Functional MR Group Macro. -
MR Arterial Spin Labeling Macro Attributes
+ Functional MR Macro + + specifies the Attributes of the . +
@@ -178208,9 +180931,9 @@
MR Series Module - The MR IODs use the , specialized by the MR Series Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of MR device. - specifies the Attributes that identify and describe general information about the MR Series. + specifies the Attributes of the , which identify and describe general information about the MR Series. + The MR IODs use the , specialized by the MR Series Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of MR device.
Functional MR Macro Attributes
@@ -178292,9 +181015,9 @@ Many Attributes have names and descriptions that include the terms "pixel" and "image". Although MR spectroscopy is not pixel based, some of these "pixel" and "image" Attributes encode concepts that are still relevant for this technique. Where such Attributes appear in the MR Spectroscopy IOD, it may be helpful to consider the term "pixel" to be equivalent to a spectroscopy "voxel", and the term "image" to be equivalent to "MR Spectroscopy SOP Instance".
- MR Spectroscopy Module + MR Spectroscopy Module - specifies the Attributes of the MR Spectroscopy Module. + specifies the Attributes of the .
MR Series Module Attributes
@@ -179148,10 +181871,10 @@
- MR Spectroscopy Pulse Sequence Module + MR Spectroscopy Pulse Sequence Module + + specifies the Attributes of the . The primary purpose of this Module is to identify the pulse sequence and variations that were used in creation of the spectroscopic data. Terminology is intended to be neutral, and allow equivalent pulse sequences provided by different vendors to be classified together. - - specifies the Attributes of the MR Spectroscopy Pulse Sequence Module.
MR Spectroscopy Module Attributes
@@ -179649,14 +182372,14 @@
MR Spectroscopy Functional Group Macros - The following sections contain Functional Group Macro's specific to the MR Spectroscopy IOD. + The following sections contain Functional Group Macros specific to the MR Spectroscopy IOD. The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".".
- MR Spectroscopy Frame Type Macro - - specifies the Attributes of the MR Spectroscopy Frame Type Functional Group Macro. + MR Spectroscopy Frame Type Macro + + specifies the Attributes of the .
MR Spectroscopy Pulse Sequence Module Attributes
@@ -179720,10 +182443,10 @@
MR Spectroscopy Frame Type Macro Attributes
- MR Spectroscopy FOV/Geometry Macro - - specifies the Attributes of the MR Spectroscopy FOV/Geometry Functional Group Macro. - + MR Spectroscopy FOV/Geometry Macro + + specifies the Attributes of the . +
@@ -179852,9 +182575,9 @@
- MR Spectroscopy Data Module + MR Spectroscopy Data Module - specifies the Attributes that describe the Spectroscopy Data. + specifies the Attributes of the , which describe the Spectroscopy Data.
MR Spectroscopy FOV/Geometry Macro Attributes
@@ -180042,9 +182765,9 @@ - + Required if First Order Phase Correction (0018,9198) equals YES. + + - + Created through point by point addition operation. + + - + Created through point by point division operation. + + - + Created through point by point maximum operation. + + - + Created through point by point mean operation. + + - + Created through point by point minimum operation. + + - + Created through point by point multiplication operation. + + - + Standard Deviation. + + - + Created through point by point subtraction operation. + + - + Not calculated. + + - + Maximum Intensity Projection. + + - + Minimum Intensity Projection. + + - + Pixels not derived geometrically. + + - + The real and imaginary components of the complex spectroscopy data. + + - + Proton Density weighted contrast. + + - + T1 weighted contrast. + + - + T2 weighted contrast. + + - + An image filter has been applied. + + - + Pixel by pixel median. + +
MR Spectroscopy Data Module Attributes
First Order Phase Correction Angle. Number of values is determined by Row*Column*Number of Frames. - Required if First Order Phase Correction (0018,9198) equals YES -
Spectroscopy Data @@ -180091,9 +182814,9 @@
- MR Spectroscopy Description Macro + MR Spectroscopy Description Macro - specifies the Attributes that describe the Spectroscopy. + specifies the Attributes of the , which describe the Spectroscopy. @@ -180208,9 +182931,9 @@ SPECTROSCOPY - + Spectroscopy. + +
MR Spectroscopy Description Macro Attributes
- Spectroscopy -
@@ -180237,73 +182960,73 @@ ADDITION 		- Created through point by point addition operation -
DIVISION - Created through point by point division operation -
MAXIMUM - Created through point by point maximum operation -
MEAN - Created through point by point mean operation -
MINIMUM - Created through point by point minimum operation -
MULTIPLICATION - Created through point by point multiplication operation -
STD_DEVIATION - Standard Deviation -
SUBTRACTION - Created through point by point subtraction operation -
NONE - Not calculated -
MIXED @@ -180343,25 +183066,25 @@ MAX_IP - Maximum Intensity Projection -
MIN_IP - Minimum Intensity Projection -
NONE - Pixels not derived geometrically -
MIXED @@ -180428,9 +183151,9 @@ COMPLEX - The real and imaginary components of the complex spectroscopy data -
MIXED @@ -180464,25 +183187,25 @@ PROTON_DENSITY - Proton Density weighted contrast -
T1 - T1 weighted contrast -
T2 - T2 weighted contrast -
UNKNOWN @@ -180510,9 +183233,9 @@ This section describes the specific Modules for the Enhanced CT Image IOD.
CT Series Module - The CT IODs use the , specialized by the CT Series Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of CT device. - specifies the Attributes that identify and describe general information about the CT Series. + specifies the Attributes of the , which identify and describe general information about the CT Series. + The CT IODs use the , specialized by the CT Series Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of CT device. @@ -180694,7 +183417,7 @@ - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). See for an overview of all acquisition related timing Attributes. @@ -180719,143 +183442,15 @@ Required if Image Type (0008,0008) Value 1 of this frame is ORIGINAL or MIXED and SOP Class UID is not "1.2.840.10008.5.1.4.1.1.2.2" (Legacy Converted), may be present otherwise. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -180986,9 +183581,9 @@ 3 - + User-defined comments about the image. + + - + Collected for the purpose of performing attenuation corrections (e.g., PET attenuation correction). + + - + Images of the heart collected for the purpose of CT Coronary Angiography (CTA). + + - + Images of the heart collected for the purpose of CT Coronary Calcium Scoring. + + - + Collected for anatomical reference for PET or SPECT. + +
CT Series Module Attributes
- Referenced Raw Data Sequence - - (0008,9121) - - 3 - - The Raw data that was used to derive this Image. - One or more Items are permitted in this Sequence. - - The Items of in this Sequence may identify raw data that has not been stored or encoded as a DICOM object. This allows recognition that images in different Instances have been reconstructed from the same raw data. - -
- - >Include + + Include - -
- Referenced Waveform Sequence - - (0008,113A) - - 3 - - References to waveforms acquired in conjunction with this image. These Waveforms may or may not be temporally synchronized with this image. - One or more Items are permitted in this Sequence. -
- - >Include - - - - -
- Referenced Image Evidence Sequence - - (0008,9092) - - 1C - - Full set of Composite SOP Instances referring to image SOP Instances inside the frames of this Enhanced CT Image SOP Instance. See for further explanation. - One or more Items shall be included in this Sequence. - Required if the Referenced Image Sequence (0008,1140) is present. -
- - >Include - - - - -
- Source Image Evidence Sequence - - (0008,9154) - - 1C - - Full set of Composite SOP Instances used as source image SOP Instances inside the frames of this Enhanced CT Image SOP Instance. See for further explanation. - One or more Items shall be included in this Sequence. - Required if the Source Image Sequence (0008,2112) is present. -
- - >Include - - - - -
- Referenced Presentation State Sequence - - (0008,9237) - - 1C - - References to Presentation State instances created together with this instance - - This Sequence does not reference Presentation States generated after image creation, such as during interpretation. - - One or more Items shall be included in this Sequence. - Required if Presentation State is created together with the images. -
- - >Include - - - - +
- User-defined comments about the image -
Burned In Annotation @@ -181235,33 +183830,33 @@ ATTENUATION - Collected for the purpose of performing attenuation corrections (e.g., PET attenuation correction) -
CARDIAC_CTA - Images of the heart collected for the purpose of CT Coronary Angiography (CTA) -
CARDIAC_CASCORE - Images of the heart collected for the purpose of CT Coronary Calcium Scoring -
REFERENCE - Collected for anatomical reference for PET or SPECT -
@@ -181287,17 +183882,17 @@ FILTERED 		- An image filter has been applied -
MEDIAN - Pixel by pixel median -
ENERGY_PROP_WT @@ -181319,9 +183914,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".
- CT Image Frame Type Macro - - specifies the Attributes of the CT Image Frame Type Functional Group Macro. + CT Image Frame Type Macro + + specifies the Attributes of the . @@ -181386,9 +183981,9 @@
CT Image Frame Type Macro Attributes
- CT Acquisition Type Macro - - specifies the Attributes of the CT Acquisition Type Functional Group Macro. + CT Acquisition Type Macro + + specifies the Attributes of the . @@ -181557,9 +184152,9 @@
- CT Acquisition Details Macro - - specifies the Attributes of the CT Acquisition Details Functional Group Macro. + CT Acquisition Details Macro + + specifies the Attributes of the .
CT Acquisition Type Macro Attributes
@@ -181608,7 +184203,7 @@ @@ -181748,9 +184343,9 @@
CT Acquisition Details Macro Attributes
References the X-Ray Path Index (0018,937A) in the Multi-energy CT Path Sequence (0018,9379) for this exposure. - This attribute may contain multiple values if this item describes multiple paths. + This Attribute may contain multiple values if this item describes multiple paths. Required if Multi-energy CT Acquisition (0018,9361) is YES.
- CT Table Dynamics Macro - - specifies the Attributes of the CT Table Dynamics Functional Group Macro. + CT Table Dynamics Macro + + specifies the Attributes of the . @@ -181847,9 +184442,9 @@
- CT Position Macro - - specifies the Attributes of the CT Position Functional Group Macro. + CT Position Macro + + specifies the Attributes of the .
CT Table Dynamics Macro Attributes
@@ -181946,9 +184541,9 @@
CT Position Macro Attributes
- CT Geometry Macro - - specifies the Attributes of the CT Geometry Functional Group Macro. + CT Geometry Macro + + specifies the Attributes of the . @@ -181997,7 +184592,7 @@ @@ -182053,9 +184648,9 @@
- CT Reconstruction Macro - - specifies the Attributes of the CT Reconstruction Functional Group Macro. + CT Reconstruction Macro + + specifies the Attributes of the .
CT Geometry Macro Attributes
References the X-Ray Path Index (0018,937A) in the Multi-energy CT Path Sequence (0018,9379) for this exposure. - This attribute may contain multiple values if this item describes multiple paths. + This Attribute may contain multiple values if this item describes multiple paths. Required if Multi-energy CT Acquisition (0018,9361) is YES.
@@ -182277,7 +184872,7 @@ @@ -182286,9 +184881,9 @@
CT Reconstruction Macro Attributes
A label describing the filter applied to the reconstructed image after the original reconstruction has been completed. - When Frame Type (0008,9007) Value 1 of this frame is DERIVED and Frame Type (0008,9007) Value 4 is FILTERED the type of filtration is described in Derivation Image Macro. + When Frame Type (0008,9007) Value 1 of this frame is DERIVED and Frame Type (0008,9007) Value 4 is FILTERED the type of filtration is described in . Required if Frame Type (0008,9007) Value 1 of this frame is ORIGINAL.
- CT Exposure Macro - - specifies the Attributes of the CT Exposure Functional Group Macro. + CT Exposure Macro + + specifies the Attributes of the . @@ -182553,9 +185148,9 @@
- CT X-Ray Details Macro - - specifies the Attributes of the CT X-Ray Details Functional Group Macro. + CT X-Ray Details Macro + + specifies the Attributes of the .
CT Exposure Macro Attributes
@@ -182604,7 +185199,7 @@ @@ -182836,9 +185431,9 @@
CT X-Ray Details Macro Attributes
References the X-Ray Path Index (0018,937A) in the Multi-energy CT Path Sequence (0018,9379) for this exposure. - This attribute may contain multiple values if this item describes multiple paths. + This Attribute may contain multiple values if this item describes multiple paths. Required if Multi-energy CT Acquisition (0018,9361) is YES.
- CT Pixel Value Transformation Macro - - specifies the Attributes of the CT Pixel Value Transformation Functional Group Macro. + CT Pixel Value Transformation Macro + + specifies the Attributes of the . @@ -182932,9 +185527,9 @@
- CT Additional X-Ray Source Macro - - specifies the Attributes of the CT Additional X-Ray Source Macro. This Sequence may be multi-valued, depending on the number of additional active X-Ray sources. It defines the X-Ray source parameters beyond the basic system. + CT Additional X-Ray Source Macro + + specifies the Attributes of the . This Sequence may be multi-valued, depending on the number of additional active X-Ray sources. It defines the X-Ray source parameters beyond the basic system. @@ -183296,9 +185891,9 @@ 3 - + Description of decomposition method. + + @@ -227185,10 +230029,10 @@ + + Objective Image Family + + + + Material Quantification Family + + + + Material Visualization Family + + @@ -240199,7 +243265,7 @@ (2000,0060) @@ -240210,7 +243276,7 @@ (2100,0160) @@ -240257,11 +243323,240 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
CT Additional X-Ray Source Macro Attributes
- Description of decomposition method -
>Decomposition Algorithm Identification Sequence @@ -183417,9 +186012,9 @@
- Enhanced Multi-energy CT Acquisition Module + Enhanced Multi-energy CT Acquisition Module - specifies the Attributes that describe the Multi-energy CT Acquisition technique in the Enhanced CT Image. + specifies the Attributes of the , which describe the Multi-energy CT Acquisition technique in the Enhanced CT Image. @@ -183605,33 +186200,33 @@ ANGIO - + Collected for the purpose of angiography. + + - + Images of the heart. + + - + Cardiac gated images, other than of the heart. + + - + Cardiac and respiratory gated images. + + - + Real-time collection of single slices (e.g., CT or MR Fluoroscopy). + + - + Collected for looking at body motion. + + - + Collected before contrast was administered. + + - + Collected during or after contrast was administered. + + - + Respiratory gated images. + + - + Cardiac rest image set. + + - + Cardiac stress image set. + + - + Set of frames that define a regularly sampled volume. + + - + Set of frames that are not parallel. + + - + Set of frames that are parallel but do not constitute a regularly sampled volume. + + - + Created through Pixel by pixel addition operation. + + - + Created through Pixel by pixel division operation. + + - + Created through Pixel by pixel masking operation. + + - + Created through Pixel by Pixel maximum operation. + + - + Created through Pixel by pixel mean operation. + + - + Created through Pixel by Pixel minimum operation. + + - + Created through Pixel by pixel multiplication operation. + + @@ -183845,25 +186440,25 @@ RESAMPLED - + Pixels have been spatially re-sampled, e.g., MPR. + + - + Standard Deviation. + + - + Created through Pixel by pixel subtraction operation. + + @@ -183872,9 +186467,9 @@ NONE - + Not a calculated image. + + - + Maximum Intensity Projection. + + - + Minimum Intensity Projection. + + - + Multi-Planar Reformat. + + - + Curved Multi-Planar Reformat. + + - + Pixels not derived geometrically. + + - + The horizontal field of view in degrees. + +
Enhanced Multi-energy CT Acquisition Module Attributes
- Collected for the purpose of angiography -
CARDIAC - Images of the heart -
CARDIAC_GATED - Cardiac gated images, other than of the heart -
CARDRESP_GATED - Cardiac and respiratory gated images -
DYNAMIC @@ -183648,9 +186243,9 @@ FLUOROSCOPY - Real-time collection of single slices (e.g., CT or MR Fluoroscopy) -
LOCALIZER @@ -183664,9 +186259,9 @@ MOTION - Collected for looking at body motion -
PERFUSION @@ -183680,33 +186275,33 @@ PRE_CONTRAST - Collected before contrast was administered -
POST_CONTRAST - Collected during or after contrast was administered -
RESP_GATED - Respiratory gated images -
REST - Cardiac rest image set -
STATIC @@ -183720,33 +186315,33 @@ STRESS - Cardiac stress image set -
VOLUME - Set of frames that define a regularly sampled volume -
NON_PARALLEL - Set of frames that are not parallel -
PARALLEL - Set of frames that are parallel but do not constitute a regularly sampled volume -
WHOLE_BODY @@ -183786,58 +186381,58 @@ ADDITION - Created through Pixel by pixel addition operation -
DIVISION - Created through Pixel by pixel division operation -
MASKED - Created through Pixel by pixel masking operation -
MAXIMUM - Created through Pixel by Pixel maximum operation -
MEAN - Created through Pixel by pixel mean operation -
MINIMUM - Created through Pixel by Pixel minimum operation -
MULTIPLICATION - Created through Pixel by pixel multiplication operation -
- Pixels have been spatially re-sampled, e.g., MPR -
STD_DEVIATION - Standard Deviation -
SUBTRACTION - Created through Pixel by pixel subtraction operation -
- Not a calculated image -
QUANTITY @@ -183897,9 +186492,8 @@
Common CT/MR Image Description Macro - This section describes the Common CT/MR Image Description Macro. - specifies the Attributes of the Common CT/MR Image Description Macro. + specifies the Attributes of the . @@ -184009,9 +186603,9 @@ TRUE_COLOR - + Image can be displayed in color only. + +
Common CT/MR Image Description Macro Attributes
- Image can be displayed in color only -
@@ -184123,17 +186717,17 @@ MAX_IP
- Maximum Intensity Projection -
MIN_IP - Minimum Intensity Projection -
VOLUME_RENDER @@ -184157,25 +186751,25 @@ MPR - Multi-Planar Reformat -
CURVED_MPR - Curved Multi-Planar Reformat -
NONE - Pixels not derived geometrically -
MIXED @@ -184196,9 +186790,9 @@
Ophthalmic Photography and Tomography Modules
- Ophthalmic Photography Series Module + Ophthalmic Photography Series Module - specifies the Attributes that describe an Ophthalmic Photography Series. + specifies the Attributes of the , which describe an Ophthalmic Photography Series. @@ -184245,9 +186839,9 @@
Ophthalmic Photography Series Module Attributes
- Ophthalmic Photography Image Module + Ophthalmic Photography Image Module - specifies the Attributes that describe an Ophthalmic Photography Image produced by Ophthalmic Photography equipment (OP) imaging Modalities. + specifies the Attributes of the , which describe an Ophthalmic Photography Image produced by Ophthalmic Photography equipment (OP) imaging Modalities. @@ -184474,7 +187068,7 @@ @@ -184618,9 +187212,9 @@ - Required if Photometric Interpretation (0028,0004) is MONOCHROME2 - - + Required if Photometric Interpretation (0028,0004) is MONOCHROME2. + + - + Nominal pass-through wavelength of light path filter in nm. + + - + Nominal pass-through wavelength of image path filter in nm. + + - + One of the two Values may be zero length, in which case it is a cutoff filter. + + - + The aperture angle of the camera, in degrees. + +
Ophthalmic Photography Image Module Attributes
The date and time that the acquisition of data started. - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time Synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). Required if Image Type (0008,0008) Value 1 is ORIGINAL. May be present otherwise.
Calibration Image @@ -184981,9 +187575,9 @@ 3 - Nominal pass-through wavelength of light path filter in nm -
Light Path Filter Pass Band @@ -185038,9 +187632,9 @@ 3 - Nominal pass-through wavelength of image path filter in nm -
Image Path Filter Pass Band @@ -185053,9 +187647,9 @@ Pass band of image path filter in nm. This Attribute has two Values. The first is the shorter and the second the longer wavelength relative to the peak. The values are for the - 3dB nominal (1/2 of peak) pass through intensity - One of the two Values may be zero length, in which case it is a cutoff filter -
Lenses Code Sequence @@ -185155,9 +187749,9 @@ 3 - The aperture angle of the camera, in degrees -
@@ -185251,9 +187845,9 @@ 2
- The horizontal field of view in degrees -
@@ -185269,9 +187863,9 @@
- Ocular Region Imaged Module + Ocular Region Imaged Module - contains IOD Attributes that describe the anatomy imaged in an Ophthalmic Photography or Ophthalmic Tomography Image Storage SOP Instance. + specifies the Attributes of the , which describe the anatomy imaged in an Ophthalmic Photography or Ophthalmic Tomography Image Storage SOP Instance. @@ -185440,9 +188034,9 @@
- Ophthalmic Tomography Series Module + Ophthalmic Tomography Series Module - specifies the Attributes that identify and describe general information about the Ophthalmic Tomography Series. + specifies the Attributes of the , which identify and describe general information about the Ophthalmic Tomography Series.
Ocular Region Imaged Module Attributes
@@ -185531,9 +188125,9 @@
Ophthalmic Tomography Series Module Attributes
- Ophthalmic Tomography Image Module + Ophthalmic Tomography Image Module - specifies the Attributes that describe an Image produced by Ophthalmic Tomography imaging modalities. + specifies the Attributes of the , which describe an Image produced by Ophthalmic Tomography imaging modalities. @@ -185633,7 +188227,7 @@ @@ -185788,9 +188382,9 @@ - + High Bit (0028,0102) shall be one less than Bits Stored. + + - + User-defined comments about the image. + +
Ophthalmic Tomography Image Module Attributes
The date and time that the acquisition of data started. - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800).
Most significant bit for pixel sample data. Each sample shall have the same high bit. - High Bit (0028,0102) shall be one less than Bits Stored -
Presentation LUT Shape @@ -186011,18 +188605,18 @@ 3 - User-defined comments about the image -
The value constraints on Concatenation Frame Offset Number (0020,9228), In-concatenation Number (0020,9162), and In-concatenation Total Number (0020,9163) have the effect of preventing the use of concatenations. The Attribute Ophthalmic Volumetric Properties Flag (0022,1622) is YES when the Ophthalmic Tomography Image Storage SOP Instance encodes volumetric spatial information (e.g. Frame of Reference, Pixel Measures, Plane Orientation, Plane Position, etc.). For example, ophthalmic tomography volumetric information is required when implementations encode Surface Segmentation SOP Instance(s) (e.g., surface segmentation is applied to the structural OCT volume to delineate the anatomical boundaries) and/or an Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Storage SOP Instance (e.g., angiographic (blood flow) volume information) based upon the volumetric Ophthalmic Tomography Image Storage SOP Instance.
- Ophthalmic Tomography Acquisition Parameters Module + Ophthalmic Tomography Acquisition Parameters Module - describes patient clinical conditions related to an Ophthalmic Tomography image acquisition. + specifies the Attributes of the , which describe patient clinical conditions related to an Ophthalmic Tomography image acquisition. @@ -186067,9 +188661,9 @@ 2 - + The horizontal field of view in degrees. + + - + Sphere value in diopters. + + - + Cylinder value in diopters. + + - + Axis value in degrees. + + - + Zero length means the pressure was not measured. + +
Ophthalmic Tomography Acquisition Parameters Module Attributes
- The horizontal field of view in degrees -
@@ -186129,9 +188723,9 @@ 1 - Sphere value in diopters -
>Cylinder Lens Power @@ -186143,9 +188737,9 @@ 1 - Cylinder value in diopters -
>Cylinder Axis @@ -186157,9 +188751,9 @@ 1 - Axis value in degrees -
Emmetropic Magnification @@ -186186,9 +188780,9 @@ Value of intraocular pressure in mmHg. - Zero length means the pressure was not measured -
Pupil Dilated @@ -186328,9 +188922,9 @@
- Ophthalmic Tomography Parameters Module + Ophthalmic Tomography Parameters Module - describes the parameters and characteristics of the acquisition device related to an Ophthalmic Tomography image acquisition. + specifies the Attributes of the , which describe the parameters and characteristics of the acquisition device related to an Ophthalmic Tomography image acquisition. @@ -186417,9 +189011,9 @@ 3 - + Nominal pass-through wavelength of light path filter in nm. + + @@ -186586,7 +189180,7 @@ 1C @@ -186614,7 +189208,7 @@ 1C @@ -186637,9 +189231,9 @@
Ophthalmic Tomography Functional Group Macros
- Ophthalmic Frame Location Macro - - specifies the Attributes of the Ophthalmic Frame Location Functional Group Macro. This is used to provide a frame location relative to one or more referenced images. This Macro describes a frame perpendicular or parallel to the reference image; it describes column locations for frames that are scanned either uniformly along a line segment, or with a non-uniform spacing along any trajectory in the reference image. + Ophthalmic Frame Location Macro + + specifies the Attributes of the . This is used to provide a frame location relative to one or more referenced images. This Macro describes a frame perpendicular or parallel to the reference image; it describes column locations for frames that are scanned either uniformly along a line segment, or with a non-uniform spacing along any trajectory in the reference image.
Ophthalmic Tomography Parameters Module Attributes
- Nominal pass-through wavelength of light path filter in nm -
>Light Path Filter Pass Band @@ -186558,7 +189152,7 @@ 1C - The inherent limiting resolution in microns for depth of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable, the value at the center of the scanning volume. Required if Acquisition Device Type Code Sequence (0022,0015) contains an Item with the value (392012008, SCT, "Optical Coherence Tomography Scanner"). May be present otherwise. + The inherent limiting resolution in µm for depth of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable, the value at the center of the scanning volume. Required if Acquisition Device Type Code Sequence (0022,0015) contains an Item with the value (392012008, SCT, "Optical Coherence Tomography Scanner"). May be present otherwise.
- The inherent limiting resolution in microns of the acquisition equipment in the direction of a row. Required if Acquisition Device Type Code Sequence (0022,0015) contains an Item with the value (392012008, SCT, "Optical Coherence Tomography Scanner"). May be present otherwise. + The inherent limiting resolution in µm of the acquisition equipment in the direction of a row. Required if Acquisition Device Type Code Sequence (0022,0015) contains an Item with the value (392012008, SCT, "Optical Coherence Tomography Scanner"). May be present otherwise.
- The inherent limiting resolution in microns of the acquisition equipment perpendicular to the slice. Required if Acquisition Device Type Code Sequence (0022,0015) contains an Item with the value (392012008, SCT, "Optical Coherence Tomography Scanner"). May be present otherwise. + The inherent limiting resolution in µm of the acquisition equipment perpendicular to the slice. Required if Acquisition Device Type Code Sequence (0022,0015) contains an Item with the value (392012008, SCT, "Optical Coherence Tomography Scanner"). May be present otherwise.
@@ -186740,7 +189334,7 @@ 2C @@ -186841,9 +189435,9 @@
- Wide Field Ophthalmic Photography Stereographic Projection Module + Wide Field Ophthalmic Photography Stereographic Projection Module - specifies the Attributes that describe the Wide Field Photography Stereographic Projection Module. + specifies the Attributes of the .
Ophthalmic Frame Location Macro Attributes
- Relative position in microns signifying the location of a Transverse image in the z-axis. Required if Ophthalmic Image Orientation (0022,0039) is TRANSVERSE. + Relative position in µm signifying the location of a Transverse image in the z-axis. Required if Ophthalmic Image Orientation (0022,0039) is TRANSVERSE.
@@ -187322,9 +189916,9 @@
- Wide Field Ophthalmic Photography 3D Coordinates Module + Wide Field Ophthalmic Photography 3D Coordinates Module - specifies the Attributes that describe the Wide Field Ophthalmic Photography 3D Coordinates Module. + specifies the Attributes of the .
Wide Field Ophthalmic Photography Stereographic Projection Module Attributes
@@ -187537,7 +190131,7 @@
Wide Field Ophthalmic Photography 3D Coordinates Module Attributes
- Wide Field Ophthalmic Photography 3D Coordinates Attribute Descriptions + Wide Field Ophthalmic Photography 3D Coordinates Module Attribute Descriptions
Transformation Method Code Sequence If Transformation Method Code Sequence (0022,1512) is (111791, DCM, "Spherical projection") all the coordinates in the Two Dimensional to Three Dimensional Map Data (0022,1531) shall lie on a sphere with a diameter that shall be equal to Ophthalmic Axial Length (0022,1019). @@ -187570,9 +190164,9 @@
- Wide Field Ophthalmic Photography Quality Rating Module + Wide Field Ophthalmic Photography Quality Rating Module - specifies the Attributes that evaluate the quality of the projection or mapping used for a wide field ophthalmic photography image. + specifies the Attributes of the , which evaluate the quality of the projection or mapping used for a wide field ophthalmic photography image. @@ -187667,9 +190261,9 @@
Wide Field Ophthalmic Photography Quality Rating Module Attributes
- Ophthalmic Optical Coherence Tomography En Face Image Module + Ophthalmic Optical Coherence Tomography En Face Image Module - specifies the Attributes that describe the Ophthalmic Optical Coherence Tomography En Face Image Module. + specifies the Attributes of the , which describe the Ophthalmic Optical Coherence Tomography En Face Image Module. Table @@ -188277,9 +190871,9 @@ - Required if Photometric Interpretation (0028,0004) is MONOCHROME2 - - + Required if Photometric Interpretation (0028,0004) is MONOCHROME2. + + @@ -188672,9 +191266,9 @@
Ophthalmic Optical Coherence Tomography En Face Image Module Attributes
Calibration Image @@ -188583,7 +191177,7 @@
Relationship Between Ophthalmic Tomography Image and Ophthalmic Optical Coherence Tomography B-scan Volume Analysis IODs When generating an angiographic en face Image SOP Instance implementations need to understand the relationship between the Ophthalmic Tomography Image SOP Instance(s) and the Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance. - The Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance, which is a multi-frame SOP Instance, references one or more Ophthalmic Tomography Image SOP Instances using the Derivation Image Macro. The Derivation Image Macro defines Attributes at the Frame Level (i.e. each frame in the Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance, references an Ophthalmic Tomography Image SOP Instance and the Ophthalmic Tomography Image SOP Instance frame number that was used to generate the specific Ophthalmic Optical Coherence Tomography B-scan Volume Analysis frame). + The Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance, which is a multi-frame SOP Instance, references one or more Ophthalmic Tomography Image SOP Instances using the . The defines Attributes at the Frame Level (i.e. each frame in the Ophthalmic Optical Coherence Tomography B-scan Volume Analysis SOP Instance, references an Ophthalmic Tomography Image SOP Instance and the Ophthalmic Tomography Image SOP Instance frame number that was used to generate the specific Ophthalmic Optical Coherence Tomography B-scan Volume Analysis frame). Examples are shown in .
@@ -188636,7 +191230,7 @@ 		Concept Name Code Sequence (0040,A043) D - +
- Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Image Module + Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Image Module - specifies the Attributes that describe the Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Image Module. + specifies the Attributes of the . @@ -189275,9 +191869,9 @@ 3 - + User-defined comments about the image. + +
Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Image Module Attributes
- User-defined comments about the image -
@@ -189372,9 +191966,9 @@
- Ophthalmic Tomography En Face Series Module + Ophthalmic Tomography En Face Series Module - specifies the Attributes that identify and describe general information about the Ophthalmic Tomography En Face Series. + specifies the Attributes of the , which identify and describe general information about the Ophthalmic Tomography En Face Series. @@ -189463,9 +192057,9 @@
Ophthalmic Tomography En Face Series Module Attributes
- Ophthalmic Tomography B-scan Volume Analysis Series Module + Ophthalmic Tomography B-scan Volume Analysis Series Module - specifies the Attributes that identify and describe general information about the Ophthalmic Tomography B-scan Volume Analysis Series. + specifies the Attributes of the , which identify and describe general information about the Ophthalmic Tomography B-scan Volume Analysis Series. @@ -189557,9 +192151,9 @@
Stereometric Modules
- Stereometric Series Module + Stereometric Series Module - specifies the Attributes that describe a Stereometric Series produced by Ophthalmic Photography equipment (OP) imaging Modalities. + specifies the Attributes of the , which describe a Stereometric Series produced by Ophthalmic Photography equipment (OP) imaging Modalities.
Ophthalmic Tomography B-scan Volume Analysis Series Module Attributes
@@ -189653,9 +192247,9 @@ 3 - + Stereo separation angle in degrees. + + - + Horizontal displacement of instrument between left and right image in mm. + + @@ -190581,7 +193175,7 @@ 1C @@ -190654,9 +193248,9 @@
Stereometric Series Module Attributes
- Stereo separation angle in degrees -
>Stereo Baseline Displacement @@ -189667,9 +192261,9 @@ 3 - Horizontal displacement of instrument between left and right image in mm -
>Stereo Horizontal Pixel Offset @@ -190554,7 +193148,7 @@ 1C - Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this SOP Instance. See for further explanation. + Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this SOP Instance. See for further explanation. One or more Items shall be included in this Sequence. Required if the Referenced Image Sequence (0008,1140) is present. - Full set of Composite SOP Instances referred to inside the Source Image Sequences of this SOP Instance. See for further explanation. + Full set of Composite SOP Instances referred to inside the Source Image Sequences of this SOP Instance. See for further explanation. One or more Items shall be included in this Sequence. Required if the Source Image Sequence (0008,2112) is present.
-Include - - + Include + + @@ -190851,10 +193445,10 @@
- XA/XRF Acquisition Module - - specifies the Attributes of the XA/XRF Acquisition Module. - + XA/XRF Acquisition Module + + specifies the Attributes of the . +
@@ -190987,9 +193581,9 @@ - + See for further explanation. + +
XA/XRF Acquisition Module Attributes
The time in seconds needed for the complete acquisition. - See for further explanation -
Radiation Mode @@ -191255,9 +193849,9 @@
- X-Ray Image Intensifier Module + X-Ray Image Intensifier Module - specifies the Attributes of the X-Ray Image Intensifier Module. + specifies the Attributes of the . @@ -191357,9 +193951,9 @@
X-Ray Image Intensifier Module Attributes
- X-Ray Detector Module + X-Ray Detector Module - contains IOD Attributes that describe an X-Ray detector. + specifies the Attributes of the , which describe an X-Ray detector. @@ -191429,10 +194023,10 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".".
- X-Ray Frame Characteristics Macro - - specifies the Attributes of the XA/XRF Frame Characteristics Functional Group Macro. -
X-Ray Detector Module Attributes
+ X-Ray Frame Characteristics Macro + + specifies the Attributes of the . +
@@ -191546,9 +194140,9 @@
X-Ray Frame Characteristics Macro Attributes
- X-Ray Field of View Macro - - specifies the Attributes of the X-Ray Field of View Functional Group Macro. + X-Ray Field of View Macro + + specifies the Attributes of the . @@ -191741,9 +194335,9 @@
X-Ray Field of View Macro Attributes
- X-Ray Exposure Control Sensing Regions Macro - - specifies the Attributes that describe the region targeted as area where the X-Ray dose value is estimated. + X-Ray Exposure Control Sensing Regions Macro + + specifies the Attributes of the , which describe the region targeted as area where the X-Ray dose value is estimated. @@ -191918,14 +194512,14 @@
X-Ray Exposure Control Sensing Regions Macro Attributes
- X-Ray Exposure Control Sensing Regions Attributes + X-Ray Exposure Control Sensing Regions Macro Attribute Descriptions The Exposure Control Sensing Region Left Vertical Edge (0018,9436), Exposure Control Sensing Region Right Vertical Edge (0018,9437), Exposure Control Sensing Region Upper Horizontal Edge (0018,9438), Exposure Control Sensing Region Lower Horizontal Edge (0018,9439) and Center of Circular Exposure Control Sensing Region (0018,9440) may have a negative value when the point defined by the Attribute lies outside the left or upper border of the pixel data matrix. The top left pixel of the image has a pixel row and column value of 1.
- X-Ray Frame Pixel Data Properties Macro - - specifies the Attributes of the X-Ray Frame Pixel Data Properties Functional Group Macro. + X-Ray Frame Pixel Data Properties Macro + + specifies the Attributes of the . @@ -192177,7 +194771,7 @@
X-Ray Frame Pixel Data Properties Macro Attributes
- X-Ray Frame Pixel Data Properties Attributes + X-Ray Frame Pixel Data Properties Macro Attribute Descriptions
Pixel Intensity Relationship Pixel Intensity Relationship (0028,1040) shall identify the relationship of the pixel values to the X-Ray beam intensity. @@ -192255,10 +194849,10 @@
- X-Ray Frame Detector Parameters Macro - - specifies the Attributes containing the X-Ray Frame Detector Parameters Functional Group Macro. - + X-Ray Frame Detector Parameters Macro + + specifies the Attributes of the . +
@@ -192327,10 +194921,10 @@
X-Ray Frame Detector Parameters Macro Attributes
- X-Ray Calibration Device Usage Macro - - specifies the Attributes containing the X-Ray Calibration Device Usage Functional Group Macro. - + X-Ray Calibration Device Usage Macro + + specifies the Attributes of the . +
@@ -192400,10 +194994,10 @@
X-Ray Calibration Device Usage Macro Attributes
- X-Ray Object Thickness Macro - - specifies the Attributes containing the X-Ray Object Thickness Group Macro. - + X-Ray Object Thickness Macro + + specifies the Attributes of the . +
@@ -192458,10 +195052,10 @@
X-Ray Object Thickness Macro Attributes
- X-Ray Frame Acquisition Macro - - specifies the Attributes containing the X-Ray Frame Acquisition Functional Group Macro. - + X-Ray Frame Acquisition Macro + + specifies the Attributes of the . +
@@ -192526,14 +195120,14 @@
X-Ray Frame Acquisition Macro Attributes
- X-Ray Frame Acquisition Sequence Attributes + X-Ray Frame Acquisition Sequence Macro Attribute Descriptions These Attributes may only be used if the information is available on a frame-by-frame base. The average values for these Attributes of all frames shall be stored in the same Attribute in the or in the .
- X-Ray Projection Pixel Calibration Macro - - specifies the Attributes of the X-Ray Projection Pixel Calibration Functional Group Macro. + X-Ray Projection Pixel Calibration Macro + + specifies the Attributes of the . @@ -192695,9 +195289,9 @@
- X-Ray Positioner Macro - - specifies the Attributes of the X-Ray Positioner Functional Group Macro. If included into the Shared Functional Groups Sequence (5200,9229) no DYNAMIC motion was performed during acquisition. If included in the Per-frame Functional Groups Sequence (5200,9230) the indication of a DYNAMIC motion is given. + X-Ray Positioner Macro + + specifies the Attributes of the . If included into the Shared Functional Groups Sequence (5200,9229) no DYNAMIC motion was performed during acquisition. If included in the Per-frame Functional Groups Sequence (5200,9230) the indication of a DYNAMIC motion is given.
X-Ray Projection Pixel Calibration Macro Attributes
@@ -192794,9 +195388,9 @@
X-Ray Positioner Macro Attributes
- X-Ray Table Position Macro - - specifies the Attributes of the X-Ray Table Position Functional Group Macro. + X-Ray Table Position Macro + + specifies the Attributes of the . @@ -192842,9 +195436,9 @@ 1 - + Table Top Vertical position with respect to an arbitrary chosen reference by the equipment in (mm). Table motion downwards is positive. + + @@ -226721,7 +229156,7 @@
X-Ray Table Position Macro Attributes
- Table Top Vertical position with respect to an arbitrary chosen reference by the equipment in (mm). Table motion downwards is positive -
>Table Top Longitudinal Position @@ -192939,9 +195533,9 @@
- X-Ray Collimator Macro - - specifies the Attributes of the X-Ray Collimator Functional Group Macro. + X-Ray Collimator Macro + + specifies the Attributes of the . @@ -193117,14 +195711,14 @@
X-Ray Collimator Macro Attributes
- X-Ray Collimator Attributes + X-Ray Collimator Macro Attribute Descriptions The top left pixel of the image has a pixel row and column value of 1.
- X-Ray Isocenter Reference System Macro - - specifies the Attributes of the X-Ray Isocenter Reference System Functional Group Macro. + X-Ray Isocenter Reference System Macro + + specifies the Attributes of the . @@ -193529,10 +196123,10 @@
- X-Ray Geometry Macro - - specifies the Attributes containing the X-Ray Geometry Functional Group Macro. -
X-Ray Isocenter Reference System Macro Attributes
+ X-Ray Geometry Macro + + specifies the Attributes of the . +
@@ -193604,7 +196198,7 @@
XA/XRF Multi-frame Presentation Module - specifies the Attributes of a XA/XRF Multi-frame Presentation Module. + specifies the Attributes of the .
X-Ray Geometry Macro Attributes
@@ -193807,7 +196401,7 @@
XA/XRF Multi-frame Presentation Module Attributes
- Multi-frame Presentation Attributes + XA/XRF Multi-frame Presentation Module Attribute Descriptions
Mask Visibility Percentage (Informative) An example of the usage of the Mask Visibility Percentage (0028,9478) Attribute is illustrated below. @@ -193825,10 +196419,10 @@ Segmentation This section describes the specific Modules for the Segmentation IOD.
- Segmentation Series Module - - defines the general Attributes of the Segmentation Series Module. - + Segmentation Series Module + + specifies the Attributes of the . +
@@ -193881,9 +196475,9 @@ 1 - + A number that identifies this Series. + +
Segmentation Series Module Attributes
- A number that identifies this Series -
Referenced Performed Procedure Step Sequence @@ -193915,10 +196509,10 @@
- Segmentation Image Module - - defines the general Attributes of the Segmentation Image Module. - + Segmentation Image Module + + specifies the Attributes of the . +
@@ -193962,117 +196556,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -194450,9 +196933,9 @@ @@ -194549,9 +197032,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean "for all frames".
- Segmentation Macro - - specifies the Attributes of the Segmentation Functional Group Macro. + Segmentation Macro + + specifies the Attributes of the .
Segmentation Image Module Attributes
- Total Pixel Matrix Columns - - (0048,0006) - - 1C - - Total number of columns in pixel matrix; i.e., width of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
- Total Pixel Matrix Rows - - (0048,0007) - - 1C - - Total number of rows in pixel matrix; i.e., height of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
- Total Pixel Matrix Focal Planes - - (0048,0303) - - 1C - - Total number of focal planes (Z locations) in the pixel matrix; i.e., depth of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. - - Total Pixel Matrix Focal Planes (0048,0303) describes the number of focal planes separately encoded, and is distinct from Number of Focal Planes (0048,0013), which describes in what manner different focal planes were combined into a single encoded plane (focus stacking). - -
- Total Pixel Matrix Origin Sequence - - (0048,0008) - - 1C - - Location of pixel 1\1 of the total pixel matrix in the Slide Coordinate System Frame of Reference. - Only a single Item shall be included in this Sequence. - See and for further explanation. - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
- >X Offset in Slide Coordinate System - - (0040,072A) - - 1 - - The X offset in millimeters from the Origin of the Slide Coordinate System. -
- >Y Offset in Slide Coordinate System - - (0040,073A) - - 1 - - The Y offset in millimeters from the Origin of the Slide Coordinate System. -
- Image Orientation (Slide) - - (0048,0102) - - 1C - - The direction cosines of the first row and the first column of the total pixel matrix with respect to the Slide Coordinate System Frame of Reference. See . - Required if Plane Position (Slide) Sequence (0048,021A) is present within a Functional Group Sequence or Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
Samples Per Pixel @@ -194434,7 +196917,7 @@ 1C - Name of algorithm used to generate the segment. Required if Segment Algorithm Type (0062,0008) is not MANUAL. + The name(s) of algorithm(s) used to generate the segment. Required if Segment Algorithm Type (0062,0008) is not MANUAL.
A description of how this segment was derived. Algorithm Name (0066,0036) within this Sequence may be identical to Segment Algorithm Name (0062,0009). - Only a single Item is permitted in this Sequence. + One or more Items are permitted in this Sequence. - Previously, the Segment Surface Generation Algorithm Identification Code Sequence (0066,002D) was used, but it has been replaced in this Module, since not all segmentation algorithms involve surface generation. See PS3.3 2016d. + Previously, the Segment Surface Generation Algorithm Identification Code Sequence (0066,002D) was used, but it has been replaced in this Module, since not all segmentation algorithms involve surface generation. See PS3.3-2016d.
@@ -194608,9 +197091,9 @@ Segmentation MacrosThe following sections contain Macros specific to the Segmentation IOD.
- Segment Description Macro - - specifies the Attributes of the Segment Description Macro. + Segment Description Macro + + specifies the Attributes of the .
Segmentation Macro Attributes
@@ -194906,6 +197389,19 @@ Required if Referenced SOP Class UID (0008,1150) is RT Structure Set Storage ("1.2.840.10008.5.1.4.1.1.481.3"). + + + +
Segment Description Macro Attributes
+ + Include + + + + + + +
@@ -194915,7 +197411,8 @@ X-Ray 3D
X-Ray 3D Image Module - This section describes the X-Ray 3D Image Module. contains IOD Attributes that describe a X-Ray 3D Image by specializing Attributes of the and , and adding additional Attributes. + + specifies the Attributes of the , which contains Attributes that describe a X-Ray 3D Image by specializing Attributes of the and , and adding additional Attributes. @@ -195275,7 +197772,7 @@ 1C @@ -195294,9 +197791,9 @@ - + The percentile of the Global Deviation from Normal (0024,0066) value within the normal population, in percent.0024. + +
X-Ray 3D Image Module Attributes
- Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this SOP Instance. See for further explanation. + Full set of Composite SOP Instances referred to inside the Referenced Image Sequences of this SOP Instance. See for further explanation. One or more Items shall be included in this Sequence. Required if the Referenced Image Sequence (0008,1140) is present.
-Include - - + Include + + @@ -195530,7 +198027,8 @@
X-Ray 3D Angiographic Image Contributing Sources Module - This section describes the X-Ray 3D Angiographic Image Contributing Sources Module. The Attributes in this Module specify the overall characteristics of one or more sources that were used to create a X-Ray 3D Angiographic Image SOP Instance. contains the relevant IOD Attributes that describe X-Ray 3D Angiographic Image Contributing Sources. + + specifies the Attributes of the , which describe X-Ray 3D Angiographic Image Contributing Sources. The Attributes in this Module specify the overall characteristics of one or more sources that were used to create a X-Ray 3D Angiographic Image SOP Instance. @@ -195674,7 +198172,8 @@
X-Ray 3D Craniofacial Image Contributing Sources Module - This section describes the X-Ray 3D Craniofacial Image Contributing Sources Module. The Attributes in this Module specify the overall characteristics of one or more sources that were used to create a X-Ray 3D Craniofacial Image SOP Instance. contains the relevant IOD Attributes that describe X-Ray 3D Craniofacial Image Contributing Sources. + + specifies the Attributes of the , which describe X-Ray 3D Craniofacial Image Contributing Sources. The Attributes in this Module specify the overall characteristics of one or more sources that were used to create a X-Ray 3D Craniofacial Image SOP Instance.
X-Ray 3D Angiographic Image Contributing Sources Module Attributes
@@ -195782,7 +198281,8 @@
Breast Tomosynthesis Contributing Sources Module - This section describes the Breast Tomosynthesis Contributing Sources Module. The Attributes in this Module specify the overall characteristics of one or more source images that were used to create a Breast Tomosynthesis Image SOP Instance. contains the IOD Attributes that describe Breast Tomosynthesis Contributing Sources. + + specifies the Attributes of the , which describe Breast Tomosynthesis Contributing Sources. The Attributes in this Module specify the overall characteristics of one or more source images that were used to create a Breast Tomosynthesis Image SOP Instance. The intention of this Module is to supply acquisition information without the need to have access to all the source projection images. @@ -196019,7 +198519,7 @@
X-Ray 3D General Shared Acquisition Macro - describes the X-Ray 3D General Shared Acquisition Macro that specifies the Attributes that are applicable for all the projection images belonging to this acquisition context. + specifies the Attributes of the , which specify the Attributes that are applicable for all the projection images belonging to this acquisition context.
X-Ray 3D Craniofacial Image Contributing Sources Module Attributes
@@ -196343,7 +198843,7 @@
X-Ray 3D General Per Projection Acquisition Macro - describes the X-Ray 3D General Per Projection Acquisition Macro that specifies the Attributes that are applicable for a single projection belonging to this acquisition context. + specifies the Attributes of the , which specify the Attributes that are applicable for a single projection belonging to this acquisition context.
X-Ray 3D General Shared Acquisition Macro Attributes
@@ -196462,7 +198962,7 @@
X-Ray 3D General Positioner Movement Macro - describes the X-Ray 3D General Positioner Movement Macro that specifies the Attributes that describe the movement of a positioner during the acquisition of more than one projection. + specifies the Attributes of the , which describe the movement of a positioner during the acquisition of more than one projection.
X-Ray 3D General Per Projection Acquisition Macro Attributes
@@ -196647,7 +199147,8 @@
X-Ray 3D Angiographic Acquisition Module - This section describes the X-Ray 3D Angiographic Acquisition Module. + + specifies the Attributes of the .
X-Ray 3D General Positioner Movement Macro Attributes
@@ -197153,7 +199654,8 @@
X-Ray 3D Craniofacial Acquisition Module - This section describes the X-Ray 3D Craniofacial Acquisition Module. + + specifies the Attributes of the .
X-Ray 3D Angiographic Acquisition Module Attributes
@@ -197303,7 +199805,8 @@
Breast Tomosynthesis Acquisition Module - This section describes the Breast Tomosynthesis Acquisition Module. + + specifies the Attributes of the .
X-Ray 3D Craniofacial Acquisition Module Attributes
@@ -197979,7 +200482,7 @@ This may be a calculated or measured value. Examples are the detector entrance dose (KB), the CR sensitivity value (S), or the logarithmic median (lgM). - This value is manufacturer-specific. DICOM specifies Standard Attributes in 'Exposure Index Macro', which are recommended. + This value is manufacturer-specific. DICOM specifies Standard Attributes in the , which are recommended. @@ -198092,7 +200595,8 @@
X-Ray 3D Reconstruction Module - This section describes the X-Ray 3D Reconstruction Module. contains IOD Attributes that describe the reconstructions used to create this SOP Instance. A single SOP Instance may contain the result of one or more reconstructions (e.g., a set of volumes). Each Item in the X-Ray 3D Reconstruction Sequence specifies the characteristics of such a result. + + specifies the Attributes of the , which describe the reconstructions used to create this SOP Instance. A single SOP Instance may contain the result of one or more reconstructions (e.g., a set of volumes). Each Item in the X-Ray 3D Reconstruction Sequence specifies the characteristics of such a result.
Breast Tomosynthesis Acquisition Module Attributes
@@ -198250,9 +200754,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".".
- X-Ray 3D Frame Type Macro - - specifies the Attributes of the X-Ray 3D Frame Type Functional Group Macro. + X-Ray 3D Frame Type Macro + + specifies the Attributes of the .
X-Ray 3D Reconstruction Module Attributes
@@ -198332,9 +200836,9 @@
X-Ray 3D Frame Type Macro Attributes
- Breast Biopsy Target Macro - - specifies the Attributes of the Breast Biopsy Target Functional Group Macro. + Breast Biopsy Target Macro + + specifies the Attributes of the . @@ -198458,9 +200962,9 @@
- Breast View Module + Breast View Module - contains IOD Attributes that describe the view of a digital breast tomosynthesis image. + specifies the Attributes of the , which describe the view of a digital breast tomosynthesis image.
Breast Biopsy Target Macro Attributes
@@ -199304,9 +201808,9 @@ 1 - + Instance UID of Study to which the related Series belongs. + + - + Instance UID of Related Series. + +
Breast View Module Attributes
- Instance UID of Study to which the related Series belongs -
>Series Instance UID @@ -199318,9 +201822,9 @@ 1 - Instance UID of Related Series -
>Purpose of Reference Code Sequence @@ -199354,9 +201858,9 @@
- Enhanced PET Acquisition Module + Enhanced PET Acquisition Module - specifies the Attributes that describe PET Acquisitions. + specifies the Attributes of the , which describe PET Acquisitions. @@ -199521,9 +202025,9 @@ - + Required if Acquisition Termination Condition (0018,0071) equals TIME. + + - + Required if Acquisition Termination Condition (0018,0071) equals CARD_TRIG. + + - + Required if Acquisition Termination Condition (0018,0071) equals RESP_TRIG. + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -200328,9 +202732,9 @@ 3 - + User-defined comments about the image. + +
Enhanced PET Acquisition Module Attributes
The time duration after which the acquisition was terminated, in sec. - Required if Acquisition Termination Condition (0018,0071) equals TIME -
Termination Cardiac Trigger Count Threshold @@ -199536,9 +202040,9 @@ The number of cardiac triggers that triggered the termination of the acquisition. - Required if Acquisition Termination Condition (0018,0071) equals CARD_TRIG -
Termination Respiratory Trigger Count Threshold @@ -199551,9 +202055,9 @@ The number of respiratory triggers that triggered the termination of the acquisition. - Required if Acquisition Termination Condition (0018,0071) equals RESP_TRIG -
Type of Detector Motion @@ -200065,7 +202569,7 @@ - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800). See for an overview of all acquisition related timing Attributes. @@ -200090,115 +202594,15 @@ Required if Image Type (0008,0008) Value 1 of this frame is ORIGINAL and SOP Class UID is not "1.2.840.10008.5.1.4.1.1.128.1" (Legacy Converted), may be present otherwise.
- Referenced Raw Data Sequence - - (0008,9121) - - 3 - - A Sequence that identifies the set of Raw Data SOP Class/Instance pairs of the Raw data that were used to derive this Image. - One or more Items are permitted in this Sequence. - - The Items of in this Sequence may identify raw data that has not been stored or encoded as a DICOM object. This allows recognition that images and spectra in different Instances have been reconstructed from the same raw data. For such Items the SOP Class UID would be "1.2.840.10008.5.1.4.1.1.66" (Raw Data SOP Class) and the SOP Instance UID would be any appropriate UID. - -
- - >Include + + Include - -
- Referenced Waveform Sequence - - (0008,113A) - - 3 - - References to waveforms acquired in conjunction with this image. These Waveforms may or may not be temporally synchronized with this image. - One or more Items are permitted in this Sequence. -
- - >Include - - - - - D. - -
- Referenced Image Evidence Sequence - - (0008,9092) - - 1C - - Full set of Composite SOP Instances referring to image SOP Instances inside the frames of this Enhanced PET Image SOP Instance. See for further explanation. - One or more Items shall be included in this Sequence. - Required if the Referenced Image Sequence (0008,1140) is present. -
- - >Include - - - - -
- Source Image Evidence Sequence - - (0008,9154) - - 1C - - Full set of Composite SOP Instances used as source image SOP Instances inside the frames of this Enhanced PET Image SOP Instance. See for further explanation. - One or more Items shall be included in this Sequence. - Required if the Source Image Sequence (0008,2112) is present. -
- - >Include - - - - +
- User-defined comments about the image -
Burned in Annotation @@ -200590,9 +202994,9 @@
- Enhanced PET Isotope Module + Enhanced PET Isotope Module - contains IOD Attributes that describe a PET Isotope. + specifies the Attributes of the , which describe a PET Isotope. @@ -200850,9 +203254,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".
- PET Frame Type Macro - - specifies the Attributes of the PET Frame Type Functional Group Macro. + PET Frame Type Macro + + specifies the Attributes of the .
Enhanced PET Isotope Module Attributes
@@ -200917,9 +203321,9 @@
PET Frame Type Macro Attributes
- PET Frame Acquisition Macro - - specifies the Attributes of the PET Frame Acquisition Functional Group Macro. + PET Frame Acquisition Macro + + specifies the Attributes of the . @@ -201014,9 +203418,9 @@
PET Frame Acquisition Macro Attributes
- PET Detector Motion Details Macro - - specifies the Attributes of the PET Detector Motion Details Functional Group Macro. + PET Detector Motion Details Macro + + specifies the Attributes of the . @@ -201098,9 +203502,9 @@
PET Detector Motion Details Macro Attributes
- PET Position Macro - - specifies the Attributes of the PET Position Functional Group Macro. + PET Position Macro + + specifies the Attributes of the . @@ -201212,9 +203616,9 @@
- PET Frame Correction Factors Macro - - specifies the Attributes of the PET Frame Correction Factors Functional Group Macro. + PET Frame Correction Factors Macro + + specifies the Attributes of the .
PET Position Macro Attributes
@@ -201328,9 +203732,9 @@
PET Frame Correction Factors Macro Attributes
- PET Reconstruction Macro - - specifies the Attributes of the PET Reconstruction Functional Group Macro, which describe the method used to reconstruct this image. + PET Reconstruction Macro + + specifies the Attributes of the , which describe the method used to reconstruct this image. @@ -201553,9 +203957,9 @@
PET Reconstruction Macro Attributes
- PET Table Dynamics Macro - - specifies the Attributes of the PET Table Dynamics Functional Group Macro, which describes the table motion during acquisition of the data. + PET Table Dynamics Macro + + specifies the Attributes of the , which describes the table motion during acquisition of the data. @@ -201609,9 +204013,9 @@
- Enhanced PET Corrections Module + Enhanced PET Corrections Module - specifies the Attributes of the Enhanced PET Corrections Module. + specifies the Attributes of the .
PET Table Dynamics Macro Attributes
@@ -202085,10 +204489,10 @@ Surface SegmentationThis section describes the specific Modules for the Surface Segmentation IOD.
- Surface Segmentation Module - - defines the general Attributes of the Surface Segmentation Module. -
Enhanced PET Corrections Module Attributes
+ Surface Segmentation Module + + specifies the Attributes of the . +
@@ -202228,7 +204632,7 @@ @@ -202279,7 +204683,7 @@
Enhanced US Series Module - specifies Attributes for the Enhanced US Series Module, including specialization of Attributes in the for use in the Enhanced US Series Module. + specifies Attributes for the Enhanced US Series Module, including specialization of Attributes in the .
Surface Segmentation Module Attributes
A description of how this segment surface was derived. - Only a single Item shall be included in this Sequence. + One or more Items shall be included in this Sequence.
@@ -202476,9 +204880,9 @@
Enhanced US Series Module Attributes
- Ultrasound Frame of Reference Module + Ultrasound Frame of Reference Module - specifies the Attributes of the Ultrasound Frame Of Reference Module. See . + specifies the Attributes of the . See . @@ -202685,8 +205089,8 @@
Ultrasound Frame of Reference Module Attributes
Ultrasound Frame of Reference Module Overview - The Ultrasound Frame of Reference Module is used to relate the image planes to a Frame of Reference appropriate for the ultrasound modality, most notably a volume-based Frame of Reference. There are many different transducer scan acquisition geometries used in 3D ultrasound imaging. Regardless of the acquisition geometry, after acquisition of the initial scan images comprising the volume, the ultrasound (US) scanner will assemble (reformat) the data into a proper Cartesian volume with the assumption that the data are related through a Right-Hand Coordinate System (RHCS). x-positions are defined in mm with positive values increasing towards the right. y-positions are defined in mm with positive values in the direction of increasing image depth. z-positions are defined in mm with positive values in the direction as defined in a right-hand coordinate system. - A Cartesian volume will consist of a series of 1 to n parallel planes. The image planes comprising the Cartesian volume are typically oriented during creation of the volume so that the best image quality is in the XY plane. specifies the Attributes of the Ultrasound Frame of Reference Module. There are three levels of detail for the Ultrasound Frame of Reference: Volume, Transducer and Table. + The is used to relate the image planes to a Frame of Reference appropriate for the ultrasound modality, most notably a volume-based Frame of Reference. There are many different transducer scan acquisition geometries used in 3D ultrasound imaging. Regardless of the acquisition geometry, after acquisition of the initial scan images comprising the volume, the ultrasound (US) scanner will assemble (reformat) the data into a proper Cartesian volume with the assumption that the data are related through a Right-Hand Coordinate System (RHCS). x-positions are defined in mm with positive values increasing towards the right. y-positions are defined in mm with positive values in the direction of increasing image depth. z-positions are defined in mm with positive values in the direction as defined in a right-hand coordinate system. + A Cartesian volume will consist of a series of 1 to n parallel planes. The image planes comprising the Cartesian volume are typically oriented during creation of the volume so that the best image quality is in the XY plane. specifies the Attributes of the . There are three levels of detail for the Ultrasound Frame of Reference: Volume, Transducer and Table.
Volume Frame of Reference The Volume Frame of Reference is a Right-hand Coordinate System consisting of a Volume Origin at the location (0,0,0) and mutually orthogonal XV, YV, and ZV axes in a Right-Hand Coordinate System. The particular IOD using the Volume Frame of Reference may constrain the alignment of frames with respect to the axes of the Volume Frame of Reference. For example, illustrates the use of the Volume Frame of Reference with frames whose rows are parallel to the XV axis and columns are parallel to the YV axis and whose origins lie on the ZV axis. @@ -202741,7 +205145,7 @@
- Ultrasound Frame of Reference Module Attributes + Ultrasound Frame of Reference Module Attribute Descriptions
Volume to Transducer Mapping Matrix The Volume to Transducer Mapping Matrix (0020,9309) is used to describe the relationship between the Transducer Frame of Reference coordinate system and the Volume Frame of Reference coordinate system. @@ -203050,9 +205454,9 @@
- Enhanced US Image Module + Enhanced US Image Module - specifies the Attributes that describe the Enhanced US Image Module. As described in , the Attributes in this Module apply to the first frame of a multi-frame image; any or all of this information may be overridden by Attributes in Per-frame Functional Groups. + specifies the Attributes of the . As described in , the Attributes in this Module apply to the first frame of a multi-frame image; any or all of this information may be overridden by Attributes in Per-frame Functional Groups. @@ -203873,9 +206277,9 @@ 3 - + Manufacturer defined code or description. + + - + Tag of Attribute specifying temporal position of frames. + + - + Tag of Sequence containing above Attribute. + +
Enhanced US Image Module Attributes
- Manufacturer defined code or description -
Transducer Identification Sequence @@ -204132,7 +206536,7 @@ - The real-world values that are inherently signed (e.g., Flow Velocity, Tissue Velocity, Variance) are represented as unsigned, unitless pixel values and may be mapped to signed real-world quantities via the Real World Value Mapping Macro. + The real-world values that are inherently signed (e.g., Flow Velocity, Tissue Velocity, Variance) are represented as unsigned, unitless pixel values and may be mapped to signed real-world quantities via the .
@@ -204199,9 +206603,9 @@ (0020,9165)
- Tag of Attribute specifying temporal position of frames -
>Functional Group Pointer @@ -204210,9 +206614,9 @@ (0020,9167) - Tag of Sequence containing above Attribute -
… @@ -204511,9 +206915,9 @@
- IVUS Image Module + IVUS Image Module - specifies the Attributes of an IVUS Module. + specifies the Attributes of the . @@ -204732,9 +207136,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean " for all frames".
- US Image Description Macro - - specifies the Attributes of the US Image Description Functional Group Macro. + US Image Description Macro + + specifies the Attributes of the .
IVUS Image Module Attributes
@@ -205217,7 +207621,7 @@
Cylinder Sequence Macro - describes the Attributes for the Cylinder Sequence Macro + specifies the Attributes of the Cylinder Sequence Macro
US Image Description Macro Attributes
@@ -205288,10 +207692,10 @@
Cylinder Sequence Macro Attributes
- Prism Sequence Macro - - describes the Attributes for the Prism Sequence Macro - + Prism Sequence Macro + + specifies the Attributes of the . +
@@ -205420,10 +207824,10 @@
- General Ophthalmic Refractive Measurements Module - - defines the General Ophthalmic Refractive Measurements Module Attributes. -
Prism Sequence Macro Attributes
+ General Ophthalmic Refractive Measurements Module + + specifies the Attributes of the . +
@@ -205574,7 +207978,7 @@
General Ophthalmic Refractive Measurements Module Attributes
- General Ophthalmic Refractive Measurements Module Attributes + General Ophthalmic Refractive Measurements Module Attribute Descriptions
Referenced Refractive Measurements Sequence Whenever visual acuity is measured it is necessary to know the conditions under which it was measured. If the vision was measured with the patient's habitual correction in place, this Attribute is used to reference a lensometry measurements SOP Instance for the current glasses. If the measurements are of the patient's best-corrected vision, this Attribute may reference the SOP Instance that describes the correction that resulted in that vision, which may for example be the subjective refraction, or the autorefraction. @@ -205585,7 +207989,7 @@
Lensometry Measurements Module - defines the Attributes used to capture the refractive measurements by a lensometer for spectacles. This is typically for a pair of lenses, but sometimes for just one. Sometimes a single lens is measured with an unknown laterality. + specifies the Attributes of the , which are used to capture the refractive measurements by a lensometer for spectacles. This is typically for a pair of lenses, but sometimes for just one. Sometimes a single lens is measured with an unknown laterality. @@ -205712,9 +208116,11 @@
Lensometry Measurements Module Attributes
+
+ Lensometry Measurements Macro - describes the Attributes for the Lensometry Measurements Macro. - + specifies the Attributes of the . +
@@ -205919,6 +208325,7 @@
Lensometry Measurements Macro Attributes
+
Autorefraction Measurements Module @@ -206217,9 +208624,11 @@
- - describes the Attributes for the Keratometric Measurements Macro. - +
+ Keratometric Measurements Macro + + specifies the Attributes of the . +
@@ -206355,6 +208764,7 @@
Keratometric Measurements Macro Attributes
+
Subjective Refraction Measurements Module @@ -206497,7 +208907,7 @@
- describes the Attributes used for the Subjective Refraction Measurements Macro. + specifies the Attributes of the Subjective Refraction Measurements Macro. @@ -207003,7 +209413,7 @@
Subjective Refraction Measurements Macro Attributes
- describes the Attributes for the Visual Acuity Measurements Macro. + specifies the Attributes of the Visual Acuity Measurements Macro. @@ -207076,9 +209486,9 @@
Visual Acuity Measurements Macro Attributes
- Ophthalmic Axial Measurements Series Module + Ophthalmic Axial Measurements Series Module - specifies the Attributes that identify and describe general information about the Ophthalmic Axial Measurements Series. + specifies the Attributes of the , which identify and describe general information about the Ophthalmic Axial Measurements Series. @@ -207348,10 +209758,10 @@
Ophthalmic Axial Measurements Series Module Attributes
- Ophthalmic Axial Measurements Macro - - describes the Attributes for the Ophthalmic Axial Measurements Macro. - + Ophthalmic Axial Measurements Macro + + specifies the Attributes of the . +
@@ -207940,10 +210350,10 @@
- Ophthalmic Axial Length Segmental Measurements Macro - - describes the Attributes for the Ophthalmic Axial Length Segmental Measurements Macro. -
Ophthalmic Axial Measurements Macro Attributes
+ Ophthalmic Axial Length Segmental Measurements Macro + + specifies the Attributes of the . +
@@ -208051,10 +210461,10 @@
Ophthalmic Axial Length Segmental Measurements Macro Attributes
- Ophthalmic Axial Measurements Related Information Macro - - describes the Attributes for the Ophthalmic Axial Measurements Related Information Macro. - + Ophthalmic Axial Measurements Related Information Macro + + specifies the Attributes of the . +
@@ -208253,10 +210663,10 @@
Ophthalmic Axial Measurements Related Information Macro Attributes
- Ophthalmic Axial Measurements Selected Macro - - describes the Attributes for the Ophthalmic Axial Measurements Selected Macro. These are the Attributes of the Ophthalmic Axial Length (0022,1019) selected for use in IOL calculations. - + Ophthalmic Axial Measurements Selected Macro + + specifies the Attributes of the . These are the Attributes of the Ophthalmic Axial Length (0022,1019) selected for use in IOL calculations. +
@@ -208359,8 +210769,8 @@ @@ -208737,10 +211147,10 @@
Ophthalmic Axial Measurements Selected Macro Attributes
-D. - + D. +
- Ophthalmic Axial Measurements Quality Metric Macro - - describes the Attributes for the Ophthalmic Axial Length Quality Metric Macro. - + Ophthalmic Axial Measurements Quality Metric Macro + + specifies the Attributes of the . +
@@ -208835,9 +211245,9 @@
- Intraocular Lens Calculations Series Module + Intraocular Lens Calculations Series Module - specifies the Attributes that identify and describe general information about the Intraocular Lens Calculations Series. + specifies the Attributes of the , which identify and describe general information about the Intraocular Lens Calculations Series.
Ophthalmic Axial Length Quality Metric Macro Attributes
@@ -208997,17 +211407,17 @@
Intraocular Lens Calculations Series Module Attributes
- Intraocular Lens Calculations Module Attributes + Intraocular Lens Calculations Module Attribute Descriptions
Referenced SOP Sequence Data in an IOL Calculations SOP Instance will frequently be gathered from other SOP Instances, such as ophthalmic axial measurements SOP Instances or refractive measurements SOP Instances. If this occurs, a reference to the SOP Instances is desired in Attribute Referenced SOP Sequence (0008,1199).
- Intraocular Lens Calculations Macro - - describes the Attributes for the Intraocular Lens Calculations Macro. - + Intraocular Lens Calculations Macro + + specifies the Attributes of the . +
@@ -209722,10 +212132,10 @@
Intraocular Lens Calculations Macro Attributes
- Keratometry Macro - - describes the Attributes for the Keratometry Macro. - + Keratometry Macro + + specifies the Attributes of the . +
@@ -209905,10 +212315,10 @@
Keratometry Macro Attributes
- IOL Ophthalmic Axial Length Macro - - describes the Attributes for the IOL Ophthalmic Axial Length Macro. - + IOL Ophthalmic Axial Length Macro + + specifies the Attributes of the . +
@@ -210076,10 +212486,10 @@
IOL Ophthalmic Axial Length Macro Attributes
- Calculated IOL Macro - - describes the Attributes for the Calculated IOL Macro. - + Calculated IOL Macro + + specifies the Attributes of the . +
@@ -210501,7 +212911,7 @@
Calculated IOL Macro Attributes
- Calculated IOL Macro Attributes + Calculated IOL Macro Attribute Descriptions
Calculation Comment Sequence Specific behaviors associated with Calculation Comment Type (0022,112B) are left to implementations to define. For example, the user might be expected to be notified about a comment with a type of WARNING whereas they might have to seek out comments with a type of INFORMATIVE. However, since this is an optional Attribute, and one that was added to this Module after its original definition, and there are no SOP Class specific constraints on display behavior, the sender cannot be guaranteed that a receiving system or user will not ignore or discard the comments. @@ -210511,7 +212921,7 @@
Ophthalmic Axial Measurements Quality Image SOP Instance Reference Macro - describes the Attributes for the Ophthalmic Axial Measurements Quality Image SOP Instance Reference Macro + specifies the Attributes of the Ophthalmic Axial Measurements Quality Image SOP Instance Reference Macro @@ -210598,7 +213008,7 @@
Calculated Toric Power Macro - specifies and describes the attributes that identify the toric amount of calculated refractive power used in IOL calculation. + specifies and describes the Attributes that identify the toric amount of calculated refractive power used in IOL calculation.
Ophthalmic Axial Measurements Quality Image SOP Instance Reference Macro Attributes
@@ -210666,7 +213076,7 @@
Cornea Measurement Macro - specifies and describes the attributes for the Cornea Measurement Macro used in IOL calculation. + specifies the Attributes of the Cornea Measurement Macro used in IOL calculation.
Calculated Toric Power Macro Attributes
@@ -210881,9 +213291,9 @@
Visual Field Static Perimetry Measurements Modules
- Visual Field Static Perimetry Measurements Series Module + Visual Field Static Perimetry Measurements Series Module - specifies the Attributes that identify and describe general information about the Visual Field Static Perimetry Measurements Series. + specifies the Attributes of the , which identify and describe general information about the Visual Field Static Perimetry Measurements Series.
Cornea Measurement Macro Attributes
@@ -211800,10 +214210,10 @@
Visual Field Static Perimetry Measurements Series Module Attributes
- Ophthalmic Visual Field Global Index Macro - - describes the Attributes for the Ophthalmic Visual Field Global Index Macro. - + Ophthalmic Visual Field Global Index Macro + + specifies the Attributes of the . +
@@ -212684,7 +215094,7 @@
Ophthalmic Visual Field Global Index Macro Attributes
- Visual Field Static Perimetry Test Measurement Attribute Descriptions + Visual Field Static Perimetry Test Measurement Module Attribute Descriptions
Measurement Laterality When B (both left and right together) eyes are provided for Measurement Laterality (0024,0113) it shall mean that both eyes are open during the test (binocular). It shall not be used to provide two monocular tests (i.e., one for the left eye and one for the right). Two monocular tests require two SOP Instances and two monocular tests with one binocular test require three SOP Instances. @@ -212875,9 +215285,9 @@ 1
- The percentile of the Global Deviation from Normal (0024,0066) value within the normal population, in percent.0024 -
@@ -213258,10 +215668,10 @@
- Ophthalmic Patient Clinical Information and Test Lens Parameters Macro - - describes the Attributes for the Ophthalmic Patient Clinical and Test Lens Parameters Macro. - + Ophthalmic Patient Clinical Information and Test Lens Parameters Macro + + specifies the Attributes of the . +
@@ -213429,9 +215839,9 @@
Intravascular Optical Coherence Tomography Modules
- Intravascular OCT Series Module + Intravascular OCT Series Module - specifies the Attributes that identify and describe general information about the Intravascular Optical Coherence Tomography Series. + specifies the Attributes of the , which identify and describe general information about the Intravascular Optical Coherence Tomography Series.
Ophthalmic Patient Clinical Information and Test Lens Parameters Macro Attributes
@@ -213565,7 +215975,7 @@
Intravascular OCT Series Module Attributes
- Intravascular OCT Series Attribute Descriptions + Intravascular OCT Series Module Attribute Descriptions
Presentation Intent Type Presentation Intent Type (0008,0068) identifies the intent for the purposes of display or other presentation of all Images within this Series. @@ -213580,11 +215990,11 @@ A Series of Images intended for viewing by an observer shall have an Enumerated Value of FOR PRESENTATION. The value shall not be set to FOR PRESENTATION unless Z Offset correction, refractive index correction and polar to rectangular conversion have been applied - Images or individual frames of a FOR PRESENTATION image shall reference their associated source FOR PROCESSING frames, if any exist, using the Derivation Image Functional Group Macro, with the Derivation Code (113093, DCM, "Polar to Rectangular Scan Conversion") and the Purpose of Reference Code (121358, DCM, "For Processing Image"). + Images or individual frames of a FOR PRESENTATION image shall reference their associated source FOR PROCESSING frames, if any exist, using the , with the Derivation Code (113093, DCM, "Polar to Rectangular Scan Conversion") and the Purpose of Reference Code (121358, DCM, "For Processing Image"). - FOR PRESENTATION images are still be of Image Type (0008,0008) and Frame Type (0008,9007) ORIGINAL rather than DERIVED despite having undergone processing, such as corrections for Z Offset, Refractive index and Polar to Rectangular conversion. In this case a DERIVED image would have undergone yet further processing to make it substantially different from the original. See . The Derivation Image Functional Group Macro may be used even if Image Type (0008,0008) and Frame Type (0008,9007) is ORIGINAL. + FOR PRESENTATION images are still be of Image Type (0008,0008) and Frame Type (0008,9007) ORIGINAL rather than DERIVED despite having undergone processing, such as corrections for Z Offset, Refractive index and Polar to Rectangular conversion. In this case a DERIVED image would have undergone yet further processing to make it substantially different from the original. See . The may be used even if Image Type (0008,0008) and Frame Type (0008,9007) is ORIGINAL. FOR PRESENTATION images may still be subjected to processing or further processing, if appropriate, depending on the application. @@ -213593,7 +216003,7 @@ FOR PRESENTATION images are intended for display on a device, without (further) processing, since that device may not be capable of image processing. The quality of the displayed image or its suitability for any purpose is beyond the scope of the DICOM Standard. - If all of the frames of a FOR PRESENTATION image are created by processing all of the frames of a FOR PROCESSING image, then a reference to the FOR PROCESSING SOP Instance only, without reference to specific frame numbers, in the Shared Functional Group Sequence avoids the need for a frame-by-frame reference in each Per-Frame Functional Group, though there is no requirement that the order of the frames or the number of frames in the FOR PROCESSING and FOR PRESENTATION SOP Instances correspond. + If all of the frames of a FOR PRESENTATION image are created by processing all of the frames of a FOR PROCESSING image, then a reference to the FOR PROCESSING SOP Instance only, without reference to specific frame numbers, in the Shared Functional Groups Sequence avoids the need for a frame-by-frame reference in each Per-Frame Functional Group, though there is no requirement that the order of the frames or the number of frames in the FOR PROCESSING and FOR PRESENTATION SOP Instances correspond. @@ -213613,9 +216023,9 @@
- Intravascular OCT Image Module + Intravascular OCT Image Module - specifies the Attributes that describe an Image produced by Intravascular OCT imaging modalities. + specifies the Attributes of the , which describe an Image produced by Intravascular OCT imaging modalities. @@ -213714,7 +216124,7 @@ @@ -214267,9 +216677,9 @@
- Intravascular OCT Acquisition Parameters Module + Intravascular OCT Acquisition Parameters Module - describes the parameters used to acquire an Intravascular Optical Coherence Tomography image. + specifies the Attributes of the , which describe the parameters used to acquire an Intravascular Optical Coherence Tomography image.
Intravascular OCT Image Module Attributes
The date and time that the acquisition of data started. - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800).
@@ -214392,9 +216802,9 @@ 2 - + The full width at half maximum (FWHM) of the axial plane response function, in µm (measured in air). + +
Intravascular OCT Acquisition Parameters Module Attributes
- The full width at half maximum (FWHM) of the axial plane response function, in µm (measured in air) -
Ranging Depth @@ -214447,9 +216857,9 @@
- Intravascular OCT Processing Parameters Module + Intravascular OCT Processing Parameters Module - describes the parameters used for processing an Intravascular Optical Coherence Tomography polar data image. + specifies the Attributes of the , which describe the parameters used for processing an Intravascular Optical Coherence Tomography polar data image. @@ -214598,9 +217008,9 @@
- Intravascular Image Acquisition Parameters Module + Intravascular Image Acquisition Parameters Module - describes the parameters and characteristics of an intravascular image acquisition. These parameters are common to both IVUS and IVOCT. + specifies the Attributes of the , which describe the parameters and characteristics of an intravascular image acquisition. These parameters are common to both IVUS and IVOCT.
Intravascular OCT Processing Parameters Module Attributes
@@ -215039,9 +217449,9 @@
Ophthalmic Thickness Map Modules
- Ophthalmic Thickness Map Series Module + Ophthalmic Thickness Map Series Module - specifies the Attributes that identify and describe general information about the Ophthalmic Thickness Map Series. + specifies the Attributes of the , which identify and describe general information about the Ophthalmic Thickness Map Series.
Intravascular Image Acquisition Parameters Module Attributes
@@ -215116,9 +217526,9 @@
Ophthalmic Thickness Map Series Module Attributes
- Ophthalmic Thickness Map Module + Ophthalmic Thickness Map Module - specifies the Attributes that describe an Image produced by ophthalmic thickness mapping devices. + specifies the Attributes of the , which describe an Image produced by ophthalmic thickness mapping devices. @@ -215702,7 +218112,7 @@ D - + @@ -215818,9 +218228,9 @@ - + Only a single Item shall be included in this Sequence. + + @@ -215862,9 +218272,9 @@ - + Only a single Item shall be included in this Sequence. + + @@ -225276,7 +227571,7 @@ 3 @@ -225349,7 +227644,7 @@ 3 @@ -225425,7 +227720,7 @@ @@ -225520,7 +227815,7 @@ 3 @@ -225638,7 +227933,7 @@ 3 @@ -225652,7 +227947,36 @@ 1 + + + + + + @@ -225663,10 +227987,41 @@ (003A,0220) + + + + + + + + + + @@ -225677,10 +228032,41 @@ (003A,0221) + + + + + + + + + + @@ -225694,7 +228080,7 @@ 3 @@ -225708,7 +228094,57 @@ 3 + + + + + + + + + + + + + + + + + + + + @@ -225796,7 +228232,7 @@ - + @@ -225822,7 +228258,7 @@ 3 @@ -226089,7 +228525,7 @@
Ophthalmic Thickness Map Module Attributes
Attributes from the OPT image that provide critical context for the interpretation of this ophthalmic map SOP Instance. Required if Ophthalmic Mapping Device Type (0022,1415) is OCT. - Only a single Item shall be included in this Sequence -
>Depth Spatial Resolution @@ -215832,7 +218242,7 @@ 1 - The inherent limiting resolution in microns for depth of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable, the value at the center of the scanning volume. + The inherent limiting resolution in µm for depth of the acquisition equipment for high contrast objects for the data gathering and reconstruction technique chosen. If variable, the value at the center of the scanning volume.
The Image SOP Class/Instance pair of the Image that was used to generate this Image. Required if Ophthalmic Mapping Device Type (0022,1415) is OCT. May be present otherwise. - Only a single Item shall be included in this Sequence -
@@ -216035,10 +218445,10 @@ Anatomic Region Sequence (0008,2218) shall be (81745001, SCT, "Eye"). - + Anatomic Region Modifier Sequence (0008,2220) D. - + Primary Anatomic Structure Sequence (0008,2228) D. Only a single Item shall be included in this Sequence. @@ -216172,7 +218582,7 @@
Ophthalmic Mapping Device Type - For Ophthalmic Mapping Device Type (0022,1415), Scanning Laser Ophthalmoscopy Tomography (SLO_TOMO) produces a topographical representation of the optic nerve head (ONH) rather than a thickness depiction. However, the topographical depiction can be considered as "thickness" measurements of multiple points of the ONH surface relative to an assigned datum plane. For this reason, the topographical image is included in the ophthalmic thickness map Module. + For Ophthalmic Mapping Device Type (0022,1415), Scanning Laser Ophthalmoscopy Tomography (SLO_TOMO) produces a topographical representation of the optic nerve head (ONH) rather than a thickness depiction. However, the topographical depiction can be considered as "thickness" measurements of multiple points of the ONH surface relative to an assigned datum plane. For this reason, the topographical image is included in the .
Optic Nerve Head Thickness Example @@ -216200,9 +218610,9 @@
- Ophthalmic Thickness Map Quality Rating Module + Ophthalmic Thickness Map Quality Rating Module - specifies the Attributes that describe the quality rating for the ophthalmic mapping. + specifies the Attributes of the , which describe the quality rating for the ophthalmic mapping. @@ -216301,9 +218711,9 @@ Optical Surface Scanner ModulesThis Section describes Optical Surface Scanner Modules. These Modules contain Attributes that are specific to Optical Surface Scanner scans.
- Optical Surface Scanner Series Module + Optical Surface Scanner Series Module - contains IOD Attributes that describe an optical surface scan Series performed on the patient. + specifies the Attributes of the , which describe an optical surface scan Series performed on the patient.
Ophthalmic Thickness Map Quality Rating Module Attributes
@@ -216404,9 +218814,9 @@
Optical Surface Scanner Series Module Attributes
- Scan Procedure Module + Scan Procedure Module - specifies the Attributes of the Scan Procedure Module. + specifies the Attributes of the . @@ -216611,9 +219021,9 @@
Corneal Topography Map Modules
- Corneal Topography Map Series Module + Corneal Topography Map Series Module - specifies the Attributes that identify and describe general information about the Corneal Topography Map Series. + specifies the Attributes of the , which identify and describe general information about the Corneal Topography Map Series.
Scan Procedure Module Attributes
@@ -216714,9 +219124,9 @@
Corneal Topography Map Series Module Attributes
- Corneal Topography Map Image Module + Corneal Topography Map Image Module - specifies the Attributes that describe an Image produced by corneal topography mapping devices. + specifies the Attributes of the , which describe an Image produced by corneal topography mapping devices. @@ -217120,7 +219530,7 @@ @@ -217162,7 +219572,7 @@
Corneal Topography Map Real World Value and Image Transformations The Corneal Topography Map SOP Class supports a sequence of transformations that completely define the conversion of a stored image into a displayed image. - The sequence of transformations from corneal measurements to a displayable image is explicitly defined in . also conveys the transformation to display the scaling of the color map using its Real World Value Macro (see for more details on the Real World Value Macro). + The sequence of transformations from corneal measurements to a displayable image is explicitly defined in . also conveys the transformation to display the scaling of the color map using its .
Corneal Topography Map Real World Value and Image Transformation Pipeline @@ -217174,14 +219584,16 @@
- An SCP of the Corneal Topography Map Storage SOP Class, when rendering SOP Instances of the Class shall apply the image transformations (i.e., Palette Color LUT) and the Real World Value LUT to display the annotated color scale. The annotated color scale shall conform to the "ISO Standard 19980 - Ophthalmic instruments - Corneal topographers, second edition, section B.4 Standardized colour Scale." + + Requirements for an SCP of the Corneal Topography Map Storage SOP Class when rendering SOP Instances of this SOP Class are defined in . Formerly, these requirements could be found in this Section of PS3.3. +
- Corneal Topography Map Analysis Module + Corneal Topography Map Analysis Module - specifies the Attributes that describe the corneal Topography map analysis. + specifies the Attributes of the , which describe the corneal Topography map analysis.
Corneal Topography Map Image Module Attributes
D - +
@@ -217686,9 +220098,9 @@ - Required if a quality rating value exists for the corneal topography map - - + Required if a quality rating value exists for the corneal topography map. + +
Corneal Topography Map Analysis Module Attributes
Corneal Topography Map Type Code Sequence @@ -217979,7 +220391,7 @@
Corneal Vertex Location - The Corneal Vertex Location (0046,0202) establishes the reference point for the corneal vertex, the origin of the Ophthalmic Coordinate System. The Ophthalmic Coordinate System is used as the Frame of Reference that establishes the spatial relationship for the corneal vertex (i.e., used within corneal topography maps) for a set of Images within a Series. It also allows Images across multiple Series to share the same Frame Of Reference. The corneal vertex is the point located at the intersection of the patient's line of sight (visual axis) and the corneal surface. It is represented by the corneal light reflex when the cornea is illuminated coaxially with fixation. + The Corneal Vertex Location (0046,0202) establishes the reference point for the corneal vertex, the origin of the Ophthalmic Coordinate System. The Ophthalmic Coordinate System is used as the Frame of Reference that establishes the spatial relationship for the corneal vertex (i.e., used within corneal topography maps) for a set of Images within a Series. It also allows Images across multiple Series to share the same Frame of Reference. The corneal vertex is the point located at the intersection of the patient's line of sight (visual axis) and the corneal surface. It is represented by the corneal light reflex when the cornea is illuminated coaxially with fixation. Since the criteria used to group images into a Series is application specific, it is possible for imaging applications to define multiple Series within a Study that share the same imaging space. Therefore the images with the same Frame of Reference UID (0020,0052) Attribute value share the same corneal vertex location within the patient's eye. @@ -218039,9 +220451,9 @@
Breast Projection Image Modules
- Enhanced Mammography Image Module + Enhanced Mammography Image Module - specifies the Attributes that identify and describe general information about the Enhanced Mammography Image Module. + specifies the Attributes of the . @@ -218882,7 +221294,7 @@
Enhanced Mammography Image Module Attributes
- Positioner and Detector Motion Attribute Descriptions + Positioner and Detector Motion Attributes Positioner Motion (0018,1500) and Type of Detector Motion (0054,0202) shall have the Defined Terms specified in . @@ -218892,66 +221304,66 @@ STATIONARY - + No motion. + + - + Circular arc motion, stepped, acquire only while stationary. + + - + Circular arc motion, continuous during acquisition. + + - + Linear motion, stepped, acquire only while stationary. + + - + Linear motion, continuous during acquisition. + + - + Complex motion, stepped, acquire only while stationary. + + - + Complex motion, continuous during acquisition. + +
Types of Positioner and Detector Motion
- No motion -
ROTATION_STEP - Circular arc motion, stepped, acquire only while stationary -
ROTATION_CONT - Circular arc motion, continuous during acquisition -
TRANSLATION_STEP - Linear motion, stepped, acquire only while stationary -
TRANSLATION_CONT - Linear motion, continuous during acquisition -
COMPLEX_STEP - Complex motion, stepped, acquire only while stationary -
COMPLEX_CONT - Complex motion, continuous during acquisition -
Complex motion is defined as that which is not simply described by linear translation or rotation around an axis.
- Breast X-Ray Positioner Macro + Breast X-Ray Positioner Macro - specifies the Attributes of the Breast X-Ray Positioner Functional Group Macro. + specifies the Attributes of the . @@ -219050,7 +221462,7 @@
Breast X-Ray Positioner Macro Attributes
- Breast X-Ray Positioner Attribute Descriptions + Breast X-Ray Positioner Macro Attribute Descriptions illustrates the Defined Terms for Positioner Primary Angle Direction (0018,9559), indicating which C-arm movement direction defines a positive value for Positioner Primary Angle (0018,1510). @@ -219068,9 +221480,9 @@
- Breast X-Ray Detector Macro + Breast X-Ray Detector Macro - specifies the Attributes of the Breast X-Ray Detector Functional Group Macro. + specifies the Attributes of the . @@ -219141,9 +221553,9 @@
Breast X-Ray Detector Macro Attributes
- Breast X-Ray Geometry Macro + Breast X-Ray Geometry Macro - specifies the Attributes of the Breast X-Ray Geometry Functional Group Macro. + specifies the Attributes of the . @@ -219281,9 +221693,9 @@
Breast X-Ray Geometry Macro Attributes
- Breast X-Ray Acquisition Dose Macro + Breast X-Ray Acquisition Dose Macro - specifies the Attributes of the X-Ray Acquisition Dose Functional Group Macro. + specifies the Attributes of the . @@ -219469,9 +221881,9 @@
Breast X-Ray Acquisition Dose Macro Attributes
- Breast X-Ray Isocenter Reference System Macro + Breast X-Ray Isocenter Reference System Macro - specifies the Attributes of the Breast X-Ray Isocenter Reference System Functional Group Macro. + specifies the Attributes of the . @@ -219579,7 +221991,7 @@ @@ -219595,7 +222007,7 @@ @@ -219611,7 +222023,7 @@ @@ -219657,7 +222069,7 @@ @@ -219673,7 +222085,7 @@ @@ -219689,7 +222101,7 @@ @@ -219705,7 +222117,7 @@ @@ -219721,13 +222133,13 @@
Breast X-Ray Isocenter Reference System Macro Attributes
X position of the Breast Support Reference Point with respect to the Isocenter (mm). See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
Y position of the Breast Support Reference Point with respect to the Isocenter (mm). See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
Z position of the Breast Support Reference Point with respect to the Isocenter (mm). See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
X position of the Detector Reference Point with respect to the Isocenter (mm). See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
Y position of the Detector Reference Point with respect to the Isocenter (mm). See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
Z position of the Detector Reference Point with respect to the Isocenter (mm). See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
The x, y, and z coordinates in mm of the center of the top left hand corner detector element of the detector active area in the Detector coordinate system. See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
The direction cosines of the first row and the first column with respect to the Detector coordinate system. See for further explanation. - Required if Presentation Intent Type (0008.0068) = FOR PROCESSING. May be present otherwise. + Required if Presentation Intent Type (0008,0068) = FOR PROCESSING. May be present otherwise.
- Isocenter Reference System Attribute Descriptions + Breast X-Ray Isocenter Reference System Macro Attribute Descriptions The Isocenter Reference System Attributes describe the 3D geometry of the X-Ray equipment composed by the X-Ray Source, Breast Support and the Detector. These Attributes define four coordinate systems in the 3D space: @@ -220084,9 +222496,9 @@
- X-Ray Grid Macro - - specifies the Attributes of the X-Ray Grid Functional Group Macro. + X-Ray Grid Macro + + specifies the Attributes of the . @@ -220187,9 +222599,9 @@
X-Ray Grid Macro Attributes
- X-Ray Filter Macro - - specifies the Attributes of the X-Ray Filter Functional Group Macro. + X-Ray Filter Macro + + specifies the Attributes of the . @@ -220241,10 +222653,10 @@ Parametric MapThis section describes the specific Modules for the Parametric Map IOD.
- Parametric Map Series Module - - defines the general Attributes of the Parametric Map Series Module. -
X-Ray Filter Macro Attributes
+ Parametric Map Series Module + + specifies the Attributes of the . +
@@ -220298,9 +222710,9 @@ 1 - + A number that identifies this Series. + +
Parametric Map Series Module Attributes
- A number that identifies this Series -
Referenced Performed Procedure Step Sequence @@ -220332,10 +222744,10 @@
- Parametric Map Image Module - - defines the general Attributes of the Parametric Map Image Module. - + Parametric Map Image Module + + specifies the Attributes of the . +
@@ -220399,117 +222811,6 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -220916,9 +223217,9 @@ The Attribute descriptions in the Functional Group Macros are written as if they were applicable to a single frame (i.e., the Macro is part of the Per-frame Functional Groups Sequence). If an Attribute is applicable to all frames (i.e., the Macro is part of the Shared Functional Groups Sequence) the phrase "this frame" in the Attribute description shall be interpreted to mean "for all frames".
- Parametric Map Frame Type Macro - - specifies the Attributes of the Parametric Map Frame Type Functional Group Macro. + Parametric Map Frame Type Macro + + specifies the Attributes of the .
Parametric Map Image Module Attributes
- Total Pixel Matrix Columns - - (0048,0006) - - 1C - - Total number of columns in pixel matrix; i.e., width of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
- Total Pixel Matrix Rows - - (0048,0007) - - 1C - - Total number of rows in pixel matrix; i.e., height of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
- Total Pixel Matrix Focal Planes - - (0048,0303) - - 1C - - Total number of focal planes (Z locations) in the pixel matrix; i.e., depth of total imaged volume in pixels. See - - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. - - Total Pixel Matrix Focal Planes (0048,0303) describes the number of focal planes separately encoded, and is distinct from Number of Focal Planes (0048,0013), which describes in what manner different focal planes were combined into a single encoded plane (focus stacking). - -
- Total Pixel Matrix Origin Sequence - - (0048,0008) - - 1C - - Location of pixel 1\1 of the total pixel matrix in the Slide Coordinate System Frame of Reference. - Only a single Item shall be included in this Sequence. - See and for further explanation. - Required if Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
- >X Offset in Slide Coordinate System - - (0040,072A) - - 1 - - The X offset in millimeters from the Origin of the Slide Coordinate System. -
- >Y Offset in Slide Coordinate System - - (0040,073A) - - 1 - - The Y offset in millimeters from the Origin of the Slide Coordinate System. -
- Image Orientation (Slide) - - (0048,0102) - - 1C - - The direction cosines of the first row and the first column of the total pixel matrix with respect to the Slide Coordinate System Frame of Reference. See . - Required if Plane Position (Slide) Sequence (0048,021A) is present within a Functional Group Sequence or Dimension Organization Type (0020,9311) is present with a value of TILED_FULL. May be present otherwise. -
Pixel Presentation @@ -220863,7 +223164,7 @@ Palette Color Lookup Table UID. See for further explanation. - Required if Pixel Presentation (0008,9205) equals COLOR_RANGE and the Palette Color Lookup Table Module is not present. + Required if Pixel Presentation (0008,9205) equals COLOR_RANGE and the is not present.
@@ -220977,9 +223278,9 @@ Tractography Results ModulesThis Section describes Tractography Results Modules.
- Tractography Results Series Module + Tractography Results Series Module - specifies the Attributes that identify and describe general information about a Tractography Results Series. + specifies the Attributes of the , which identify and describe general information about a Tractography Results Series.
Parametric Map Frame Type Macro Attributes
@@ -221066,9 +223367,9 @@
Tractography Results Series Module Attributes
- Tractography Results Module + Tractography Results Module - specifies the Attributes that describe the tracks and measurements in the tractography results. + specifies the Attributes of the , which describe the tracks and measurements in the tractography results. @@ -221723,7 +224024,7 @@
Tractography Results Module Attributes
- Tractography Results Module Attributes + Tractography Results Module Attribute Descriptions This Module encodes one or more Track Sets, each of which consists of one or more Tracks, each of which is defined by one or more points. For each Track, optionally one or more measurements may be defined, either for every point or a subset of points. Measurements are described by coded type and unit. For each Track and/or Track Set, summary statistics derived from measurements may be included (whether or not the actual measurements are encoded). When a measurement (i.e., an Item of Measurements Sequence (0066,0121) ) is encoded for every point in a track, then Floating Point Values (0066,0125) contains the corresponding values for every point. When a measurement is encoded for a subset of points, then Floating Point Values (0066,0125) contains measurement values for the points in Point Coordinates Data (0066,0016) which are referenced in Track Point Index List (0066,0129). More than one Measurements Sequence (0066,0121) Item may be used, for example to encode different types of measurements, such as Fractional Anisotropy (FA) and Apparent Diffusion Coefficient (ADC), or to encode different components of a measurement that is a tuple, e.g., a diffusion tensor. In the latter case, which component, and which tensor, will be identified by the fully pre-coordinated code in the Concept Name Code Sequence (0040,A043). @@ -221865,17 +224166,17 @@ Overlays
Overlay Identification Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Overlay Plane Module - - contains Attributes that describe characteristics of an Overlay Plane. + + specifies the Attributes of the , which describe characteristics of an Overlay Plane. An Overlay Plane describes graphics or bit-mapped text that is associated with an Image. It may also describe a Region of Interest in an Image. Each Overlay Plane is one bit deep. Sixteen separate Overlay Planes may be associated with an Image. Overlay data is stored in Overlay Data (60xx,3000). See the Section Repeating Groups in for a description of permitted values of 60xx. - Overlay data stored in unused bit planes of Pixel Data (7FE0,0010) with Samples Per Pixel (0028,0002) of 1 was previously described in DICOM. This usage has now been retired. See PS3.3-2004 and PS3.5-2004. + Overlay data stored in unused bit planes of Pixel Data (7FE0,0010) with Samples Per Pixel (0028,0002) of 1 was previously described in DICOM. This usage has now been retired. See PS3.3-2004 and PS3.5-2004. Attributes describing display of grayscale and color overlays were defined in a previous version of the DICOM Standard. These have now been retired. How an Overlay Plane is rendered is undefined; specifically there is no mechanism to specify with what color or intensity an Overlay Plane is to be displayed, except when rendered under the control of a Softcopy Presentation State SOP Instance. @@ -221987,7 +224288,7 @@ Number of Bits Allocated in the Overlay.The value of this Attribute shall be 1. - Formerly the Standard described embedding the overlay data in the Image Pixel Data (7FE0,0010), in which case the value of this Attribute was required to be the same as Bits Allocated (0028,0100). This usage has been retired. See PS3.3-2004. + Formerly the Standard described embedding the overlay data in the Image Pixel Data (7FE0,0010), in which case the value of this Attribute was required to be the same as Bits Allocated (0028,0100). This usage has been retired. See PS3.3-2004. @@ -222004,7 +224305,7 @@ @@ -222115,7 +224416,7 @@
The value of this Attribute shall be 0. - Formerly the Standard described embedding the overlay data in the Image Pixel Data (7FE0,0010), in which case the value of this Attribute specified the bit in which the overlay was stored. This usage has been retired. See PS3.3-2004. + Formerly the Standard described embedding the overlay data in the Image Pixel Data (7FE0,0010), in which case the value of this Attribute specified the bit in which the overlay was stored. This usage has been retired. See PS3.3-2004.
- Overlay Attribute Descriptions + Overlay Plane Module Attribute Descriptions
Overlay Type There are two specific types of overlays. The type is specified in this Attribute. @@ -222153,9 +224454,7 @@ Additional or alternative Defined Terms may be specified in modality specific Modules, such as the specific use of "ACTIVE 2D/BMODE IMAGE AREA" as described in the . - An active image area overlay identifies all pixels in the Pixel Data that are generated from image data acquisition. - Each pixel in the active area shall have an overlay bit value of 1; all other bits are set to 0. - Any area of burned in annotation (not generated from image data acquisition) shall be excluded from the active image area. + An active image area overlay identifies all pixels in the Pixel Data that are generated from image data acquisition. Each pixel in the active area shall have an overlay bit value of 1; all other bits are set to 0. Any area of burned in annotation (not generated from image data acquisition) shall be excluded from the active image area. @@ -222179,14 +224478,10 @@
Multi-frame Overlay Module - specifies the Attributes of a Multi-frame overlay, or of a single frame overlay applied to a specific image frame. - This Module specifies additional attributes for overlay planes specified in . - All Overlay frames have the same characteristics. + specifies the Attributes of a Multi-frame overlay, or of a single frame overlay applied to a specific image frame. This Module specifies additional Attributes for overlay planes specified in . All Overlay frames have the same characteristics. A Multi-frame Overlay is defined as an Overlay whose overlay data consists of a sequential set of individual Overlay frames. - A Multi-frame Overlay is encoded as a single contiguous stream of overlay data. - Neither frame delimiters nor padding between overlay frames are contained within the overlay bit stream. - See . + A Multi-frame Overlay is encoded as a single contiguous stream of overlay data. Neither frame delimiters nor padding between overlay frames are contained within the overlay bit stream. See . A Multi-frame Overlay applies only to a Multi-frame Image. @@ -222240,17 +224535,13 @@
- Multi-frame Overlay Attribute Descriptions + Multi-frame Overlay Module Attribute Descriptions
Number of Frames in Overlay The total number of frames contained within a Multi-frame Overlay is conveyed in the Number of Frames in Overlay (60xx,0015). - The frames within a Multi-frame Overlay shall be conveyed as a logical sequence. - The order of the Overlay Frames correspond one to one with the order of the Image frames. - If Image Frame Origin (60xx,0051) is present, the Overlay frames correspond one to one to the Image frames, beginning at the indicated frame number. - Otherwise, the Overlay Frames correspond beginning with the first Image frame. + The frames within a Multi-frame Overlay shall be conveyed as a logical sequence. The order of the Overlay Frames correspond one to one with the order of the Image frames. If Image Frame Origin (60xx,0051) is present, the Overlay frames correspond one to one to the Image frames, beginning at the indicated frame number. Otherwise, the Overlay Frames correspond beginning with the first Image frame. - When an Overlay consisting of one frame is to be applied to one frame of a Multi-frame Image, it is specified with a Number of Frames in Overlay (60xx,0015) value of 1, and a frame number in Image Frame Origin (60xx,0051), because Image Frame Origin is invoked only by this Module, in which Number of Frames in Overlay (60xx,0015) is Type 1. - In the absence of Number of Frames in Overlay (60xx,0015) and Image Frame Origin (60xx,0051), per , a single frame overlay applies to all frames of a multi-frame image. + When an Overlay consisting of one frame is to be applied to one frame of a Multi-frame Image, it is specified with a Number of Frames in Overlay (60xx,0015) value of 1, and a frame number in Image Frame Origin (60xx,0051), because Image Frame Origin is invoked only by this Module, in which Number of Frames in Overlay (60xx,0015) is Type 1. In the absence of Number of Frames in Overlay (60xx,0015) and Image Frame Origin (60xx,0051), per , a single frame overlay applies to all frames of a multi-frame image. The Number of Frames in Overlay (60xx,0015) plus the Image Frame Origin (60xx,0051) minus 1 shall be less than or equal to the total number of frames in the Multi-frame Image.
@@ -222262,22 +224553,22 @@
Basic Print Image Overlay Box Module (Retired) - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Curve, Graphic and Waveform
Curve Identification Module (Retired) - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Curve Module (Retired) - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Audio Module (Retired) - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Displayed Area Module @@ -223676,7 +225967,7 @@
- Graphic Annotation Attribute Descriptions + Graphic Annotation Module Attribute Descriptions
Unformatted Text Value The text shall be displayed if any part of the bounding box or anchor point is within the Specified Display Area. @@ -223904,9 +226195,26 @@
Text Style Sequence Text Style Sequence (0070,0231) contains the text style for each text object. This Attribute gives recommendations on how the annotation text should be rendered at the display. - - specifies the Attributes that describe Text Style Sequence Macro. - +
+ Text Alignment + Horizontal Alignment (0070,0242) and Vertical Alignment (0070,0243) define the position of the text relative to the bounding box of the text object (see ). + +
+ Example of Horizontal and Vertical CENTER Alignment + + + + + + +
+ +
+
+ Text Style Sequence Macro + + specifies the Attributes of the . +
@@ -224271,27 +226579,13 @@
Text Style Sequence Macro Attributes
-
- Text Alignment - Horizontal Alignment (0070,0242) and Vertical Alignment (0070,0243) define the position of the text relative to the bounding box of the text object (see ). - -
- Example of Horizontal and Vertical CENTER Alignment - - - - - - -
-
- Line Style Sequence - - specifies the Attributes that describe Line Style Sequence Macro. - + Line Style Sequence + + specifies the Attributes of the . +
@@ -224573,10 +226867,10 @@
- Fill Style Sequence - - specifies the Attributes that describe Fill Style Sequence Macro. -
Line Style Sequence Macro Attributes
+ Fill Style Sequence Macro + + specifies the Attributes of the . +
@@ -224832,7 +227126,8 @@
Graphic Layer Module - This Module defines the characteristics of the layers in which overlays, graphic and text may be rendered. + + specifies the Attributes of the , which describe the characteristics of the layers in which overlays, graphic and text may be rendered. Layers group together graphics that are related. It is recommended that a layer be displayed such that it may be distinguished from other layers that have a different value for Graphic Layer Order (0070,0062). The transparency, opacity, and any other interaction (such as exclusive or) with underlying layers or image data are not specified and are at the discretion of the implementation. @@ -224951,10 +227246,10 @@
Fill Style Sequence Macro Attributes
- Graphic Layer Recommended Display RGB Value (0070,0067) was previously used in this Module, but has been retired and its function replaced by Graphic Layer Recommended Display CIELab Value (0070,0401). See PS3.3-2004. + Graphic Layer Recommended Display RGB Value (0070,0067) was previously used in this Module, but has been retired and its function replaced by Graphic Layer Recommended Display CIELab Value (0070,0401). See PS3.3-2004.
- Graphic Layer Module Attributes + Graphic Layer Module Attribute Descriptions
Encoding of CIELab Values Attributes such as Graphic Layer Recommended Display CIELab Value (0070,0401) consist of three unsigned short values: @@ -225262,7 +227557,7 @@ 1
- Frequency in Hz + Frequency in Hz.
- Label for multiplex group + Label for multiplex group.
- Text label for channel, which may be used for display purposes + Text label for channel, which may be used for display purposes.
A coded descriptor of the waveform channel source (metric, anatomical position, function, and technique). Only a single Item shall be included in this Sequence. - (see ) + (see ).
- Additional description of waveform channel derivation + Additional description of waveform channel derivation.
- Additional offset of first sample of channel to be used in aligning multiple channels for presentation or analysis, in seconds (see ) + Additional offset of first sample of channel to be used in aligning multiple channels for presentation or analysis, in seconds (see ).
- Number of significant bits within the waveform samples (see ) + Number of significant bits within the waveform samples (see ). +
+ >>Waveform Amplifier Type + + (003A,0317) + + 3 + + The type of amplifier used for waveform acquisition. + + Enumerated Values: + + AC + + + + + + DC + + + + +
- 3 + 1C - Nominal 3dB point of lower frequency of pass band; in Hz + Nominal 3dB point of lower frequency of pass band; in Hz. + Required if Waveform Amplifier Type (003A,0317) is AC and Filter Low Frequency Characteristics Sequence (003A,0318) is not present. Shall not be present if Waveform Amplifier Type (003A,0317) is DC. May be present otherwise. + + This frequency is the cutoff frequency of a high-pass filter. + +
+ >>Filter Low Frequency Characteristics Sequence + + (003A,0318) + + 1C + + The properties of low frequency (high-pass) filters used for the waveform acquisition. + Required if Waveform Amplifier Type (003A,0317) is AC and Filter Low Frequency (003A,0220) is not present. May be present otherwise unless Waveform Amplifier Type (003A,0317) is DC. + At least one item shall be included in this Sequence. +
+ + >>>Include + + + +
- 3 + 1C + + Nominal 3dB point of upper frequency of pass band; in Hz. + Required if Waveform Amplifier Type (003A,0317) is present and Filter High Frequency Characteristics Sequence (003A,0319) is not present. May be present otherwise. + + This frequency is the cutoff frequency of a low-pass filter. + +
+ >>Filter High Frequency Characteristics Sequence + + (003A,0319) + + 1C + + The properties of high frequency (low-pass) filters used for the waveform acquisition. + Required if Waveform Amplifier Type (003A,0317) is present and Filter High Frequency (003A,0221) is not present. May be present otherwise. + At least one item shall be included in this Sequence. +
+ + >>>Include + + - Nominal 3dB point of upper frequency of pass band; in Hz +
- Center frequency of notch filter(s); in Hz + Center frequency of notch filter(s); in Hz.
- Nominal 3dB bandwidth of notch filter(s); in Hz + Nominal 3dB bandwidth of notch filter(s); in Hz. +
+ >>Notch Filter Characteristics Sequence + + (003A,0321) + + 3 + + The properties of notch filters used for the waveform acquisition. +
+ + >>>Include + + + + +
+ >>Summarized Filter Lookup Table Sequence + + (003A,0320) + + 3 + + Filter Lookup Table providing the total effect of all filters applied. +
+ + >>>Include + + + +
>>Channel Minimum Value @@ -225808,7 +228244,7 @@ 3 - Minimum valid sample value as limited by the acquisition equipment (see ) + Minimum valid sample value as limited by the acquisition equipment (see ).
- Maximum valid sample value as limited by the acquisition equipment (see ) + Maximum valid sample value as limited by the acquisition equipment (see ).
- Waveform Attribute Descriptions + Waveform Module Attribute Descriptions
Multiplex Group Time Offset Multiplex Group Time Offset (0018,1068) specifies the offset time in milliseconds from a reference time to the first sample of the multiplex group. The reference time is Acquisition DateTime (0008,002A), if present in the SOP Instance. @@ -226179,8 +228615,7 @@ Channel Sensitivity and Channel Sensitivity Units Channel Sensitivity (003A,0210) is the nominal value of one unit (i.e., the least significant bit) of each waveform sample in Waveform Data (5400,1010). It includes both the amplifier gain and the analog-digital converter resolution. It does not relate the vertical scaling of a waveform on a particular display. - A prior edition specified Channel Sensitivity Units Sequence (003A,0211) D. - was a subset of , and has been retired in favor of the more general . See PS3.3-2011. + A prior edition specified Channel Sensitivity Units Sequence (003A,0211) D. was a subset of , and has been retired in favor of the more general . See PS3.3-2011. Channel Sensitivity Correction Factor (003A,0212) is the ratio of the actual (calibrated) value to the nominal channel sensitivity specified in Channel Sensitivity (003A,0210). Thus a waveform sample value multiplied by the Channel Sensitivity value provides the nominal measured value in Channel Sensitivity Units, and that nominal value multiplied by the Channel Sensitivity Correction Factor provides the calibrated measured value.
@@ -226379,7 +228814,7 @@ - Channel sample value 0 maps to the Channel Position (003A,0245) display baseline. The real world value associated with the baseline is specified in Channel Baseline (003A,0213). + Channel sample value 0 maps to the Channel Position (003A,0245) display baseline. The Real World Value associated with the baseline is specified in Channel Baseline (003A,0213). Multiple channels may overlap, and may share the same Channel Position (003A,0245).
@@ -226471,7 +228906,7 @@
Text Observation Value (annotation). - Mutually exclusive with Concept Name Code Sequence (0040,A043) + Mutually exclusive with Concept Name Code Sequence (0040,A043).
- Waveform Annotation Attribute Descriptions + Waveform Annotation Module Attribute Descriptions
Referenced Channels Referenced Waveform Channels (0040,A0B0) is a multi-value Attribute that lists the channels to which an annotation of a waveform applies. Each channel is specified as a pair of values (M,C), where the first value is the ordinal of the Item of Waveform Sequence (5400,0100) (i.e., the Multiplex Group Number), and the second value is the ordinal of the Item of the Channel Definition Sequence (003A,0200) Attribute (i.e., the Waveform Channel Number) within the multiplex group. @@ -226788,7 +229223,8 @@
Graphic Group Module - Graphic Group Module provides the label and description for the logical associations made by the Graphic Group ID (0070,0295) of graphic objects. + + specifies the Attributes of the , which provide the label and description for the logical associations made by the Graphic Group ID (0070,0295) of graphic objects. The grouping concept used in the differs from the grouping concept used in the . addresses the rendering order by using the Graphic Layer Order (0070,0062), which specifies which annotations are rendered first. The is used to specify which annotations belong together and shall be handled together (e.g., rotate, move) independent of the Graphic Layer to which they are assigned. @@ -226869,13 +229305,419 @@
Graphic Group Module Attributes
+
+ Waveform Filter Characteristics Macro + This Macro contains properties of analog and digital filters applied to waveform data. It can be used for filter settings applied on the recording device at the time of data acquisition as well as for filter settings used to achieve a specific waveform display. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Waveform Filter Characteristics Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Waveform Filter Type + + (003A,0322) + + 1 + + The type of filter. + + Enumerated Values: + + ANALOG + + + + + + DIGITAL + + + + + +
+ Filter Low Frequency + + (003A,0220) + + 1C + + Nominal 3dB point of lower frequency of pass band in Hz. This is the cutoff frequency of a high-pass filter. + Required if the filter is a high-pass filter. + Shall be consistent with Filter Low Frequency (003A,0220) in the enclosing Dataset, if present. +
+ Filter High Frequency + + (003A,0221) + + 1C + + Nominal 3dB point of upper frequency of pass band in Hz. This is the cutoff frequency of a low-pass filter. + Required if the filter is a low-pass filter. + Shall be consistent with Filter High Frequency (003A,0221) in the enclosing Dataset, if present. +
+ Notch Filter Frequency + + (003A,0222) + + 1C + + Center frequency of the notch filter in Hz. + Required if the filter is a notch filter. +
+ Notch Filter Bandwidth + + (003A,0223) + + 2C + + Nominal 3dB bandwidth of the notch filter; in Hz. + Required if the filter is a notch filter. +
+ Analog Filter Characteristics Sequence + + (003A,0323) + + 1C + + Characteristic parameters of the analog filter. + Required if Waveform Filter Type (003A,0322) is ANALOG. + A single Item shall be included in this Sequence. +
+ >Analog Filter Roll Off + + (003A,0324) + + 1 + + The slope of the filter response between pass-band and stop-band given in dB/octave. +
+ >Analog Filter Type Code Sequence + + (003A,0325) + + 1 + + A coded descriptor of the type of analog filter. +
+ + >>Include + . + + + B. + +
+ Digital Filter Characteristics Sequence + + (003A,0326) + + 1C + + Characteristic parameters of the digital filter. + Required if Waveform Filter Type (003A,0322) is DIGITAL. + A single Item shall be included in this Sequence. +
+ >Digital Filter Order + + (003A,0327) + + 1 + + Filter order is the maximum delay, in samples, used in creating each output sample. +
+ >Digital Filter Type Code Sequence + + (003A,0328) + + 1 + + A coded descriptor of the type of digital filter. +
+ + >>Include + . + + + B. + +
+ Waveform Filter Description + + (003A,0329) + + 3 + + A textual description of the filter. +
+ Filter Lookup Table Sequence + + (003A,032A) + + 3 + + A Lookup Table defining the filter. +
+ + >Include + . + + +
+
+
+ Waveform Filter Lookup Table Macro + This Macro contains attributes of a Waveform Filter Lookup Table. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Waveform Filter Lookup Table Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Filter Lookup Table Description + + (003A,032B) + + 3 + + A textual description of the Filter Lookup Table. +
+ Frequency Encoding Code Sequence + + (003A,032C) + + 1 + + Encoding of frequency values in the Lookup Table Data. +
+ + >Include + . + + + B. + +
+ Magnitude Encoding Code Sequence + + (003A,032D) + + 1 + + Encoding of filter response magnitude in the Lookup Table Data. +
+ + >Include + . + + + B. + +
+ Filter Lookup Table Data + + (003A,032E) + + 1 + + Lookup Table Data. + See for further explanation. +
+
+ Lookup Table Data + Lookup Table Data consist of n triplets of double values: the first value is the input frequency. The second value is the magnitude. The third value is the phase shift of the signal resulting from filtering. + The input frequency values in the Lookup Table shall cover all frequencies from 0 to ½ of the sampling frequency. For input frequencies between two values in the Lookup Table an interpolation between the neighboring values can take place. + Frequency Encoding Code Sequence (003A,032C) defines the encoding of the first value, which could be: + + + frequency given in Hz + + + frequency given in radians per second + + + normalized frequency, which is frequency in Hz divided by ½ of the sampling rate + + + or angular frequency, which is frequency in Hz divided by ½ of the sampling rate and then multiplied by π (pi). + + + Magnitude Encoding Code Sequence (003A,032D) defines the encoding of the second value, which could be: + + + dB microvolts, dB millivolts + + + normalized magnitude + + + absolute magnitude in millivolt or microvolt. + + + Normalized magnitude is (ω - |H(ω)|)/ ωmax, which is the input signal amplitude minus the filter output signal amplitude both divided by the maximum input signal amplitude, and has a value between 0-1; (no units, because it is the ratio of input and output amplitudes). + The phase shift is given in degrees. +
+
Look Up Tables and Presentation States
Modality LUT Module - - specifies the Attributes that describe the Modality LUT. + + specifies the Attributes of the , which describe the Modality LUT. Either a Modality LUT Sequence containing a single Item or Rescale Slope and Intercept values shall be present but not both. This requirement for only a single transformation makes it possible to unambiguously define the input of succeeding stages of the grayscale pipeline such as the VOI LUT. @@ -227055,7 +229897,7 @@
- LUT Attribute Descriptions + Modality LUT Module Attribute Descriptions
LUT Descriptor The three values of LUT Descriptor (0028,3002) describe the format of the LUT Data in the corresponding LUT Data (0028,3006) Attribute. @@ -227165,7 +230007,7 @@ Real World Value First Value Mapped (0040,​9216)
- Real World Value Last Value Mapped (0040,​9211) + Real World Value Last Value Mapped (0040,​9211) Real World Value Intercept (0040,​9224) @@ -227174,10 +230016,12 @@ Real World Value Slope (0040,​9225) - LUT Label (0040,​9210) in Real World Value Macro + LUT Label (0040,​9210) in + - Measurement Units Code Sequence (0040,​08EA) in Real World Value Macro + Measurement Units Code Sequence (0040,​08EA) in +
- - Objective Image Family - -
@@ -227210,7 +230054,7 @@ 0 - 4095 + 4095 -1024 @@ -227245,7 +230089,7 @@ 0 - 4000 + 4000 0 @@ -227280,7 +230124,7 @@ 0 - 4000 + 4000 0 @@ -227312,7 +230156,7 @@ 0 - 4000 + 4000 0 @@ -227329,10 +230173,10 @@
- - Material Quantification Family - -
@@ -227354,7 +230198,7 @@ 0 - 4000 + 4000 -3 @@ -227386,7 +230230,7 @@ 0 - 4095 + 4095 -1024 @@ -227421,7 +230265,7 @@ 0 - 4095 + 4095 -1024 @@ -227453,7 +230297,7 @@ 0 - 4095 + 4095 -1024 @@ -227488,7 +230332,7 @@ 0 - 1000 + 1000 0 @@ -227523,7 +230367,7 @@ 0 - 100 + 100 0 @@ -227540,10 +230384,10 @@
- - Material Visualization Family - -
@@ -227565,7 +230409,7 @@ 0 - 4095 + 4095 -1024 @@ -227597,8 +230441,8 @@
VOI LUT Module - - specifies the Attributes that describe the VOI LUT. + + specifies the Attributes of the , which describe the VOI LUT. @@ -227794,7 +230638,7 @@
VOI LUT Module Attributes
- LUT Attribute Descriptions + VOI LUT Module Attribute Descriptions
LUT Descriptor The three values of LUT Descriptor (0028,3002) describe the format of the LUT Data in the corresponding LUT Data (0028,3006) Attribute. @@ -228054,13 +230898,13 @@ c - is the Window Center defined interactively by the user or by using the values provided in (0028,1050). + is the Window Center defined interactively by the user or by using the values provided in Window Center (0028,1050). w - is the Window Width defined interactively by the user or by using the values provided in (0028,1051). + is the Window Width defined interactively by the user or by using the values provided in Window Width (0028,1051). @@ -228123,12 +230967,12 @@
LUT Identification Module - This section has been retired. See PS3.3-2006. + This section has been retired. See PS3.3-2006.
Presentation LUT Module - - specifies the Attributes that describe the Presentation LUT. + + specifies the Attributes of the , which describe the Presentation LUT. @@ -228366,7 +231210,7 @@
Presentation LUT Module Attributes
- Image Histogram Attribute Descriptions + Image Histogram Module Attribute Descriptions The Image Histogram is a Sequence with multiple Items representing a sequential count of binned stored image pixel values in ascending order. One reason to include a histogram with an image is as an aid to image processing applications. For applications that use them, computations of histograms for very large images can be a significant burden on computer resources and can seriously degrade the response time to the user. @@ -228391,8 +231235,8 @@
Softcopy Presentation LUT Module - - specifies the Attributes that describe the Softcopy Presentation LUT. + + specifies the Attributes of the , which describe the Softcopy Presentation LUT. @@ -228507,7 +231351,7 @@ This Module differs from the used in the hardcopy (print) related SOP Classes in that Optical Density is not supported for Presentation LUT Shape (since Optical Density has no meaning for softcopy display devices).
- Softcopy Presentation LUT Attributes + Softcopy Presentation LUT Module Attribute Descriptions When the Presentation LUT is specified as a Presentation LUT Sequence, then the input range of values is specified by the LUT Descriptor as the first value mapped and the number of entries (values mapped). However, there is an implicit linear scaling of the output range of the preceding transformation (such as the VOI LUT transformation) so that it is always mapped to the specified input range of the Presentation LUT. When the Presentation LUT is specified as Presentation LUT Shape, then the input range is implicitly specified to be the output range of the preceding transformation (VOI LUT, or if the VOI LUT is identity or absent, the Modality LUT, or if the Modality LUT and VOI LUT are identity or absent, the stored pixel values). In this case, the full range of the output of the preceding transformation will be mapped to the full input range of the display device that receives the output of the Presentation LUT. @@ -228608,18 +231452,18 @@ - Previously, those bits that are stored in Pixel Data (7FE0,0010) above High Bit (0028,0102) could be used as overlay bit planes if they were referenced by an Overlay Bit Position (60xx,0102). This usage has been retired. See PS3.3-2004. Their contents are unspecified in DICOM and should not be displayed. Usually they will be zero, though if the pixel data is signed, i.e., Pixel Representation (0028,0103) is 0001H, then it is possible that the sign bit may be "extended" through these values. Alternatively, they may have been "masked off" even if the value is signed and negative. + Previously, those bits that are stored in Pixel Data (7FE0,0010) above High Bit (0028,0102) could be used as overlay bit planes if they were referenced by an Overlay Bit Position (60xx,0102). This usage has been retired. See PS3.3-2004. Their contents are unspecified in DICOM and should not be displayed. Usually they will be zero, though if the pixel data is signed, i.e., Pixel Representation (0028,0103) is 0001H, then it is possible that the sign bit may be "extended" through these values. Alternatively, they may have been "masked off" even if the value is signed and negative. - Previously, Curve Activation Layer (50xx,1001) was defined in this Module. Its usage has been retired. See PS3.3-2004. + Previously, Curve Activation Layer (50xx,1001) was defined in this Module. Its usage has been retired. See PS3.3-2004.
Softcopy VOI LUT Module - - specifies the Attributes that describe the Softcopy VOI LUT. These Attributes have the same meaning and behavior as defined in the . + + specifies the Attributes of the , which describe the Softcopy VOI LUT. These Attributes have the same meaning and behavior as defined in the .
Softcopy Presentation LUT Module Attributes
@@ -228698,8 +231542,8 @@
Presentation Series Module - - contains Attributes that identify and describe a Presentation Series. + + specifies the Attributes of the , which identify and describe a Presentation Series.
Softcopy VOI LUT Module Attributes
@@ -228751,8 +231595,8 @@
Presentation State Identification Module - - contains Attributes that identify a Presentation State. + + specifies the Attributes of the , which identify a Presentation State.
Presentation Series Module Attributes
@@ -228824,8 +231668,8 @@
Presentation State Relationship Module - - contains Attributes that describe the images to which a Presentation State applies. + + specifies the Attributes of the , which describe the images to which a Presentation State applies.
Presentation State Identification Module Attributes
@@ -228858,7 +231702,9 @@
Presentation State Relationship Module Attributes
- +
+ Presentation State Relationship Macro +
@@ -228938,11 +231784,12 @@
Presentation State Relationship Macro Attributes
+
Presentation State Shutter Module - - contains Attributes that specialize Attributes in other Modules included in a Presentation State. + + specifies the Attributes of the , which specialize Attributes in other Modules included in a Presentation State. @@ -229003,8 +231850,8 @@
Presentation State Mask Module - - contains Attributes that specialize the use of masks in a Presentation State. + + specifies the Attributes of the , which specialize the use of masks in a Presentation State.
Presentation State Shutter Module Attributes
@@ -229134,8 +231981,8 @@
Presentation State Blending Module - - contains Attributes that describe the identification of two sets of grayscale images and the grayscale transformations to be applied to them, for the purpose of blending. + + specifies the Attributes of the , which describe the identification of two sets of grayscale images and the grayscale transformations to be applied to them, for the purpose of blending.
Presentation State Mask Module Attributes
@@ -229337,11 +232184,11 @@
Presentation State Blending Module Attributes
- Presentation State Blending Module Attributes + Presentation State Blending Module Attribute Descriptions
Blending Sequence Blending Sequence (0070,0402) is used to identify two sets of images, one to be superimposed upon the other. - The sets of images and any subset of the frames therein in the case of multi-frame images are identified by Study, Series, SOP Instance and Frame Number. In the case of a Segmentation image, the subset of segments is identified by the Attribute Referenced Segment Number (0062,000B) in the Referenced Image Sequence (0008,1140) invoked in the Presentation State Relationship Macro. + The sets of images and any subset of the frames therein in the case of multi-frame images are identified by Study, Series, SOP Instance and Frame Number. In the case of a Segmentation image, the subset of segments is identified by the Attribute Referenced Segment Number (0062,000B) in the Referenced Image Sequence (0008,1140) invoked in the . This Module specifies no explicit relationship (such as pairing or ordering) between the sets of images and frames defined in the first Item for the underlying images, and the second Item for the superimposed images. This Module does not define how the images are spatially related, and what re-sampling, if any, needs to be performed before the images are blended for rendering. @@ -229361,8 +232208,8 @@
ICC Profile Module - - contains Attributes that identify and describe an ICC Profile. + + specifies the Attributes of the , which identify and describe an ICC Profile. @@ -229414,7 +232261,7 @@
ICC Profile Module Attributes
- Attribute Descriptions + ICC Profile Module Attribute Descriptions
ICC Profile ICC Profile (0028,2000) encodes an ICC Input Device Profile that encodes the transformation of device-dependent color stored pixel values into PCS-Values. @@ -229508,8 +232355,8 @@
Structured Display Module - - describes the Attributes of the Structured Display Module. + + specifies the Attributes of the . @@ -229711,7 +232558,7 @@
Structured Display Image Box Module - describes the Attributes of the . + specifies the Attributes of the .
Structured Display Module Attributes
@@ -230324,7 +233171,7 @@
Structured Display Image Box Module Attributes
- Structured Display Image Box Attribute Descriptions + Structured Display Image Box Module Attribute Descriptions
Display Environment Spatial Position The Display Environment Spatial Position (0072,0108) specifies the corners of the Image Box relative to the vertical and horizontal dimensions of the Display Environment, specified as Number of Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106) in the Nominal Screen Definition Sequence (0072,0102). @@ -230432,6 +233279,8 @@
Structured Display Annotation Module + + specifies the Attributes of the . This Module defines Attributes of text annotation that shall be applied to a Structured Display. The text is defined in position and size relative to the Display Environment. @@ -230443,8 +233292,6 @@ - - describes the Attributes of the . @@ -230567,7 +233414,7 @@
Structured Display Annotation Module Attributes
- Structured Display Annotation Attribute Descriptions + Structured Display Annotation Module Attribute Descriptions
Unformatted Text Value and Display Environment Spatial Position The Unformatted Text Value (0070,0006) rendered in Display Environment Spatial Position (0072,0108) need not be confined to the specified bounding box. @@ -230598,8 +233445,8 @@
XA/XRF Presentation State Mask Module - - specifies the Attributes that describe mask operations for a XA/XRF Multi-frame image. + + specifies the Attributes of the , which describe mask operations for a XA/XRF Multi-frame image. @@ -230795,7 +233642,7 @@ 1 @@ -230913,7 +233760,7 @@
XA/XRF Presentation State Mask Module Attributes
- LUT Data in this Sequence + LUT Data in this Sequence.
- XA/XRF Presentation State Mask Attributes + XA/XRF Presentation State Mask Module Attribute Descriptions
Mask Sub-pixel Shift A pair of floating point numbers specifying the fractional vertical [adjacent row spacing] and horizontal [adjacent column spacing] pixel shift applied to the mask before subtracting it from the specified region of the contrast frame. The row offset results in a shift of the pixels along the column axis. The column offset results in a shift of the pixels along the row axis. A positive row offset is a shift toward the pixels of the lower row of the pixel plane. A positive column offset is a shift toward the pixels of the left hand side column of the pixel plane. @@ -230966,8 +233813,8 @@
XA/XRF Presentation State Shutter Module - - specifies the Attributes that describe shutter operations for a XA/XRF Multi-frame image. + + specifies the Attributes of the , which describe shutter operations for a XA/XRF Multi-frame image. @@ -231044,9 +233891,9 @@
XA/XRF Presentation State Shutter Module Attributes
- XA/XRF Presentation State Presentation Module + XA/XRF Presentation State Presentation Module - specifies the Attributes of a XA/XRF Presentation State Presentation Module. + specifies the Attributes of the . @@ -231292,8 +234139,8 @@
Volumetric Presentation State Identification Module - - contains Attributes that describe the volume view type of this Presentation State. + + specifies the Attributes of the , which describe the volume view type of this Presentation State.
XA/XRF Presentation State Presentation Module Attributes
@@ -231483,8 +234330,8 @@
Volumetric Presentation State Relationship Module - - contains Attributes that describe sets of inputs to a Presentation State and how each input is to be displayed in the presentation. + + specifies the Attributes of the , which describe sets of inputs to a Presentation State and how each input is to be displayed in the presentation.
Volumetric Presentation State Identification Module Attributes
@@ -231515,7 +234362,7 @@ 1 @@ -231930,7 +234777,7 @@
Volumetric Presentation State Reference Coordinate System The Volumetric Presentation State Reference Coordinate System (VPS-RCS) is identified by the . - All SOP Instances specified in the Volumetric Presentation State Relationship Module shall be implicitly or explicitly registered to the Volumetric Presentation State Reference Coordinate System. Registration is implicit if the Frame of Reference of a particular input SOP Instance is chosen as the VPS-RCS. Explicit registration is required if the Frame of Reference UID value of one or more input SOP Instances are different from the Frame of Reference UID value of the Presentation State. + All SOP Instances specified in the shall be implicitly or explicitly registered to the Volumetric Presentation State Reference Coordinate System. Registration is implicit if the Frame of Reference of a particular input SOP Instance is chosen as the VPS-RCS. Explicit registration is required if the Frame of Reference UID value of one or more input SOP Instances are different from the Frame of Reference UID value of the Presentation State. @@ -231974,8 +234821,8 @@
Volume Cropping Module - - contains the Attributes of the Volume Cropping Module. This Module limits the spatial extent of inputs in Volumetric Presentation State Input Sequence (0070,1201) that are used. + + specifies the Attributes of the . This Module limits the spatial extent of inputs in Volumetric Presentation State Input Sequence (0070,1201) that are used.
Volumetric Presentation State Relationship Module Attributes
- Input sets specified for use by this Volumetric Presentation State + Input sets specified for use by this Volumetric Presentation State.
@@ -232194,8 +235041,8 @@
Presentation View Description Module - - contains Attributes that describe the view of this presentation in anatomical terms. + + specifies the Attributes of the , which describe the view of this presentation in anatomical terms. Note: For example, a Volumetric Presentation State derived from a whole-body CT source volume could be restricted to the left leg.
Volume Cropping Module Attributes
@@ -232225,8 +235072,8 @@ @@ -232328,8 +235175,8 @@
Multi-Planar Reconstruction Geometry Module - - contains Attributes that describe the geometry of this Multi-Planar Reconstruction view. + + specifies the Attributes of the , which describe the geometry of this Multi-Planar Reconstruction view.
Presentation View Description Module Attributes
-No Baseline CID is defined. - + No Baseline CID is defined. +
@@ -232516,7 +235363,7 @@ - A PLANAR MPR is a thin slice or thick slab of the input volume defined by a geometric plane as illustrated by . and depict the relationships between MPR Geometry Module Attributes and Thin and Slab MPR views, respectively. + A PLANAR MPR is a thin slice or thick slab of the input volume defined by a geometric plane as illustrated by . and depict the relationships between Attributes and Thin and Slab MPR views, respectively.
Planar MPR THIN Geometry @@ -232562,8 +235409,8 @@
MPR Volumetric Presentation State Display Module - - specifies the Attributes that define the transformations of the processed MPR Volumetric Presentation State inputs into a single VPS display space, as described in the Volumetric Presentation State pipeline in . + + specifies the Attributes of the , which define the transformations of the processed MPR Volumetric Presentation State inputs into a single VPS display space, as described in the Volumetric Presentation State pipeline in .
Multi-Planar Reconstruction Geometry Module Attributes
@@ -232686,7 +235533,7 @@ 1 @@ -233180,8 +236027,8 @@
Volumetric Graphic Annotation Module - - contains Attributes that specify graphic annotation placed in the Volumetric Presentation State Reference Coordinate System coordinate space. + + specifies the Attributes of the , which specify graphic annotation placed in the Volumetric Presentation State Reference Coordinate System coordinate space. This Module specifies literal text and/or graphic annotation only. Provision is made to reference external measurement Structured Report Instances to provide context for the annotation, if desired. @@ -233473,7 +236320,7 @@ 1
@@ -233634,8 +236481,8 @@
Presentation Animation Module - - contains Attributes that describe animation of the presentation. + + specifies the Attributes of the , which describe animation of the presentation.
MPR Volumetric Presentation State Display Module Attributes
- Value of Volumetric Presentation Input Number (0070,1207) for this input in the Volumetric Presentation State Input Sequence (0070,1201) + Value of Volumetric Presentation Input Number (0070,1207) for this input in the Volumetric Presentation State Input Sequence (0070,1201).
- The layer defined in the Graphic Layer Module C.10.7 in which the graphic or text is to be rendered. + The layer defined in the in which the graphic or text is to be rendered.
@@ -233914,8 +236761,8 @@
Volume Render Geometry Module - - contains Attributes that describe the geometry of the volume rendered view. + + specifies the Attributes of the , which describe the geometry of the volume rendered view.
Presentation Animation Module Attributes
@@ -234036,7 +236883,6 @@ @@ -239574,7 +242640,7 @@ @@ -239590,7 +242656,7 @@ @@ -239598,8 +242664,8 @@
General Reference Module - - specifies the Attributes that reference source and other related Instances and describe the manner of derivation. + + specifies the Attributes of the , which reference source and other related Instances and describe the manner of derivation.
Volume Render Geometry Module Attributes
The rendering method used during the ray casting compositing operation. - Enumerated values: Enumerated Values: @@ -234283,8 +237129,8 @@
Render Display Module - - specifies the Attributes that define the transformations of the processed Volumetric Presentation State inputs into a single VPS display space, as described in the Volumetric Presentation State pipelines in . + + specifies the Attributes of the , which define the transformations of the processed Volumetric Presentation State inputs into a single VPS display space, as described in the Volumetric Presentation State pipelines in . @@ -234809,7 +237655,7 @@ 1 @@ -234850,10 +237696,8 @@
Advanced Blending Presentation State Module -
- Advanced Blending Presentation State Module Attributes - contains Attributes that describe one or more inputs optionally one or more sets of registration objects, and the color and thresholds to be applied to them, for the purpose of blending. + specifies the Attributes of the , which describe one or more inputs optionally one or more sets of registration objects, and the color and thresholds to be applied to them, for the purpose of blending.
Render Display Module Attributes
- LUT Data + LUT Data.
@@ -234928,9 +237772,9 @@ 1 - + Unique identifier of a Series that is part of the Study defined by the Study Instance UID (0020,000D). + + - + Required if the input is a Time Series and all time points need to be blended with the other Series. May be present otherwise. + +
Advanced Blending Presentation State Module Attributes
- Unique identifier of a Series that is part of the Study defined by the Study Instance UID (0020,000D) -
>Referenced Image Sequence @@ -235029,9 +237873,9 @@ Only a single Item in the Sequence may have the value TRUE - Required if the input is a Time Series and all time points need to be blended with the other Series. May be present otherwise -
>Geometry for Display @@ -235066,6 +237910,8 @@
+
+ Advanced Blending Presentation State Module Attribute Descriptions
Advanced Blending Sequence The images to be blended are specified in the Advanced Blending Sequence (0070,1B01). @@ -235247,7 +238093,8 @@
Advanced Blending Presentation State Display Module - The Advanced Blending Presentation State Display Module specifies the input and the method used for each blending step. + + specifies the Attributes of the , which specify the input and the method used for each blending step. @@ -235351,7 +238198,7 @@ @@ -235412,7 +238259,7 @@
SOP Common Module - defines the Attributes that are required for proper functioning and identification of the associated SOP Instances. They do not specify any semantics about the Real-World Object represented by the IOD. + specifies the Attributes of the , which are required for proper functioning and identification of the associated SOP Instances. They do not specify any semantics about the Real-World Object represented by the IOD.
Advanced Blending Presentation State Display Module Attributes
Specifies Relative Opacity for the visible pixels of the set referenced by the first Blending Input Number (0070,1B02) - Required if Blending Mode (0070,1B06) is equal to FOREGROUND + Required if Blending Mode (0070,1B06) is equal to FOREGROUND.
@@ -235656,7 +238503,7 @@ 3 @@ -235734,6 +238581,12 @@ The resource contains a comma separated value text file that contains a representation of the coding scheme. + + FHIR + + The resource is a FHIR CodingScheme, e.g., as would be referred to in the Coding.system element of a FHIR Coding resource. + + @@ -235867,7 +238720,7 @@ 3 @@ -236130,6 +238983,61 @@ Manufacturer's designation of the software version of the equipment that contributed to the Composite Instance. See . + + + + + + + + + + + + + + + + @@ -236458,7 +239366,7 @@ - See . + See and . @@ -236961,7 +239869,7 @@ In the case of a scanned patient label, this may be the same as Patient ID (0010,0020), but it is included in an Instance level Module rather than a Patient level Module since barcodes may also be used to identify lower level entities. This might be obtained by scanning the patient's wrist band, request form, or extracting a burned-in label from the image pixel data, for example. - In the case of a scanned slide label, this may be the same as Container Identifier (0040,0512) in the Specimen Module. + In the case of a scanned slide label, this may be the same as Container Identifier (0040,0512) in the . @@ -236975,13 +239883,13 @@
SOP Common Module Attributes
- The coding scheme full common name + The coding scheme full common name.
- The unique identifier of the Mapping Resource + The unique identifier of the Mapping Resource.
+ >Device UID + + (0018,1002) + + 3 + + Unique identifier of the contributing equipment. + + There is no requirement that this Device UID (0018,1002) be the same as the Instance Creator UID (0008,0014) in the , though it may be. + +
+ >UDI Sequence + + (0018,100A) + + 3 + + Unique Device Identifier (UDI) of the contributing equipment. + One or more Items are permitted in this Sequence. + + + + This is the UDI that corresponds to the entire contributing equipment as described by the other attributes in the Contributing Equipment Sequence Item. This is not intended to contain the UDIs of sub-components of the contributing equipment. + + + Multiple Items may be present if the contributing equipment has UDIs issued by different Issuing Authorities. + + + +
+ + >>Include + + + + + + +
>Spatial Resolution @@ -236363,7 +239271,7 @@ - +
- +
- SOP Common Attribute Descriptions + SOP Common Module Attribute Descriptions
SOP Class UID, SOP Instance UID The SOP Class UID and SOP Instance UID Attributes are defined for all DICOM IODs. However, they are only encoded in Composite IODs with the Type equal to 1. See . When encoded they shall be equal to their respective Attributes in the DIMSE Services and the File Meta Information header (see PS3.10 Media Storage). @@ -236990,7 +239898,7 @@ Specific Character Set Specific Character Set (0008,0005) identifies the Character Set that expands or replaces the Basic Graphic Set (ISO 646) for values of Data Elements that have Value Representation of SH, LO, ST, PN, LT, UC or UT. See . If the Attribute Specific Character Set (0008,0005) is not present or has only a single value, Code Extension techniques are not used. Defined Terms for the Attribute Specific Character Set (0008,0005), when single valued, are derived from the International Registration Number as per ISO 2375 (e.g., ISO_IR 100 for Latin alphabet No. 1). See . - +
@@ -237032,7 +239940,9 @@ G0 @@ -237052,8 +239962,12 @@ G1 @@ -237067,7 +239981,9 @@ G0 @@ -237087,8 +240003,12 @@ G1 @@ -237102,7 +240022,9 @@ G0 @@ -237122,8 +240044,12 @@ G1 @@ -237137,7 +240063,9 @@ G0 @@ -237157,8 +240085,12 @@ G1 @@ -237172,7 +240104,9 @@ G0 @@ -237192,8 +240126,12 @@ G1 @@ -237207,7 +240145,9 @@ G0 @@ -237227,8 +240167,12 @@ G1 @@ -237242,7 +240186,9 @@ G0 @@ -237262,8 +240208,12 @@ G1 @@ -237277,7 +240227,9 @@ G0 @@ -237297,8 +240249,12 @@ G1 @@ -237312,7 +240268,9 @@ G0 @@ -237332,8 +240290,12 @@ G1 @@ -237347,42 +240309,50 @@ G0 @@ -237402,8 +240372,11 @@ G1 @@ -237417,8 +240390,11 @@ G0 @@ -237438,8 +240414,12 @@ G1 @@ -237453,7 +240433,9 @@ G0 @@ -237524,7 +240506,9 @@ G0 @@ -237550,8 +240534,12 @@ G1 @@ -237571,7 +240559,9 @@ G0 @@ -237597,8 +240587,12 @@ G1 @@ -237618,7 +240612,9 @@ G0 @@ -237644,8 +240640,12 @@ G1 @@ -237665,7 +240665,9 @@ G0 @@ -237691,8 +240693,12 @@ G1 @@ -237712,7 +240718,9 @@ G0 @@ -237738,8 +240746,12 @@ G1 @@ -237759,7 +240771,9 @@ G0 @@ -237785,8 +240799,12 @@ G1 @@ -237806,7 +240824,9 @@ G0 @@ -237832,8 +240852,12 @@ G1 @@ -237853,7 +240877,9 @@ G0 @@ -237879,8 +240905,12 @@ G1 @@ -237900,7 +240930,9 @@ G0 @@ -237926,8 +240958,12 @@ G1 @@ -237947,54 +240983,62 @@ G0 @@ -238020,8 +241064,11 @@ G1 @@ -238041,8 +241088,11 @@ G0 @@ -238068,8 +241118,12 @@ G1 @@ -238089,7 +241143,9 @@ G0 @@ -238151,7 +241207,8 @@ G0 @@ -238174,7 +241231,8 @@ G0 @@ -238200,7 +241258,8 @@ G1 @@ -238226,7 +241285,9 @@ G1 @@ -238271,7 +241332,9 @@ Defined Term @@ -238284,7 +241347,9 @@ ISO_IR 192 @@ -238295,7 +241360,9 @@ GB18030 @@ -238306,7 +241373,9 @@ GBK @@ -238614,7 +241683,7 @@
Defined Terms for Single-Byte Character Sets Without Code Extensions
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- Latin alphabet No. 9 + Latin alphabet No. 9 - ISO_IR 203 + ISO_IR 203 - ISO-IR 203 + ISO-IR 203 - 96 + 96 - G1 + G1 - - + + + + + +
- ISO-IR 6 + ISO-IR 6 - 94 + 94 - G0 + G0 - + + +
- - : Katakana + + + + + : Katakana
- - : Romaji + + + + + : Romaji
- - + + + + + +
- + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- - + + + + + +
- + + +
- Latin alphabet No. 9 + Latin alphabet No. 9 - ISO 2022 IR 203 + ISO 2022 IR 203 - ISO 2022 + ISO 2022 - ESC 02/13 06/02 + ESC 02/13 06/02 - ISO-IR 203 + ISO-IR 203 - 96 + 96 - G1 + G1 - - + + + + + +
- ISO 2022 + ISO 2022 - ESC 02/08 04/02 + ESC 02/08 04/02 - ISO-IR 6 + ISO-IR 6 - 94 + 94 - G0 + G0 - + + +
- - : Katakana + + + + + : Katakana
- - : Romaji + + + + + : Romaji
- - + + + + + +
- + + +
- : Kanji + + : Kanji
- : Supplementary Kanji set + + : Supplementary Kanji set
- : Hangul and Hanja + + : Hangul and Hanja
- + + +
- Character Set + + Character Set +
- + + +
- + + +
- + + +
- Digital Signature Attribute Descriptions + Digital Signatures Macro Attribute Descriptions
Data Elements Signed The Data Elements Signed Attribute shall list the Tags of the Data Elements that are included in the MAC calculation. The Tags listed shall reference Data Elements at the same level as the Mac Parameters Sequence (4FFE,0001) Data Element in which the Data Elements Signed Attribute appears. Tags included in Data Elements Signed shall be listed in the order in which they appear within the Data Set. @@ -238657,7 +241726,7 @@ If any of the Data Element Tags in the list refer to a Sequence of Items, then the Tags of all Data Elements within all Items of that Sequence shall be implicitly included in the list of Data Elements Signed, except those disallowed above. This implicit list shall also include the Item Tag (FFFE,E000) Data Elements that separate the Sequence Items and the Sequence Delimitation Item (FFFE,E0DD). - It is possible to sign individual Items within a Sequence by including the Digital Signatures Macro in that Sequence Item. In fact, this is a highly desirable feature, particular when used in the context of reports. The Digital Signatures Macro is applied at the Data Set level, and Sequences of Items are merely Data Sets embedded within a larger Data Set. Essentially, the Digital Signature Macro may be applied recursively. + It is possible to sign individual Items within a Sequence by including the in that Sequence Item. In fact, this is a highly desirable feature, particular when used in the context of reports. The is applied at the Data Set level, and Sequences of Items are merely Data Sets embedded within a larger Data Set. Essentially, the may be applied recursively. An example of nesting Digital Signatures within Data Elements is illustrated in .
@@ -238700,154 +241769,154 @@ - lists the Defined Terms for MAC Algorithm (0400,0015). + lists the Defined Terms for MAC Algorithm (0400,0015). - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Defined Terms for MAC Algorithm (0400,0015)
- Defined Term - - Reference -
- RIPEMD160 - - - - -
- MD5 - - - - - - See also security considerations in . The use of MD5 is no longer recommended. - -
- SHA1 - - - - -
- SHA224 - - - - -
- SHA256 - - - - -
- SHA384 - - - - -
- SHA512 - - - - -
- SHA512_224 - - - - -
- SHA512_256 - - - - -
- SHA3_224 - - - - -
- SHA3_256 - - - - -
- SHA3_384 - - - - -
- SHA3_512 - - - - -
+ Defined Term + + Reference +
+ RIPEMD160 + + + + +
+ MD5 + + + + + + See also security considerations in . The use of MD5 is no longer recommended. + +
+ SHA1 + + + + +
+ SHA224 + + + + +
+ SHA256 + + + + +
+ SHA384 + + + + +
+ SHA512 + + + + +
+ SHA512_224 + + + + +
+ SHA512_256 + + + + +
+ SHA3_224 + + + + +
+ SHA3_256 + + + + +
+ SHA3_384 + + + + +
+ SHA3_512 + + + + +
Security Profiles (see ) may restrict or extend the list of MAC algorithms that are permitted or required by a specific profile. @@ -238863,7 +241932,7 @@
- Encrypted Attribute Descriptions + Encrypted Attributes
Encrypted Attributes Sequence Each Item of the Encrypted Attributes Sequence (0400,0500) contains an encrypted DICOM Data Set containing a single instance of the Encrypted Attributes Data Set (). It also contains encrypted content-encryption keys for one or more recipients. The encoding is based on the Enveloped-data Content Type of the Cryptographic Message Syntax defined in IETF STD 70 . It allows to encrypt the embedded Data Set for an arbitrary number of recipients using any of the three key management techniques supported by IETF STD 70 : @@ -238967,7 +242036,7 @@
Contributing Equipment Sequence - Contributing Equipment Sequence (0018,A001) allows equipment that has contributed towards the creation of the Composite Instance to be described. The general class of contribution is denoted via a coded entry within the Purpose of Reference Code Sequence (0040,A170). + Contributing Equipment Sequence (0018,A001) allows equipment that has contributed towards the creation of the Composite Instance to be described. Equipment encompasses both hardware (such as an acquisition device or a film digitizer or a workstation) and software (such as a de-identification tool or an AI model). The general class of contribution is denoted via a coded entry within the Purpose of Reference Code Sequence (0040,A170). @@ -238985,6 +242054,9 @@ For example, equipment that has been used for de-identifying could retain information about the creating equipment within the and provide its own identification, and that of its operator, as an Item within Contributing Equipment Sequence (0018,A001). Here, the value of Purpose of Reference Code Sequence (0040,A170) within the Item would be (109104, DCM, "De-identifying Equipment"). + + In the case of processing equipment, further information about the algorithm(s) used may be found in invocations of the , or in SR instances, . +
@@ -239036,7 +242108,7 @@
Private Data Element Characteristics - The creator of the Private Data Elements (identified by the value of Private Creator Reference (0008,0302)) is responsible for managing the Private Data Element Tags associated with them and ensuring that the Private Data Element (0008,0308) and the Private Data Element Keyword (0008,030D) are a unique pair, and that the other associated details in the Data Element Definition Macro are consistent. + The creator of the Private Data Elements (identified by the value of Private Creator Reference (0008,0302)) is responsible for managing the Private Data Element Tags associated with them and ensuring that the Private Data Element (0008,0308) and the Private Data Element Keyword (0008,030D) are a unique pair, and that the other associated details are consistent. Implementers are encouraged to describe all Private Data Elements in the Private Data Element Characteristics Sequence (0008,0300). The Private Data Element Characteristics Sequence (0008,0300) may describe Data Elements that are referenced in the current SOP Instance (for example they may be identified as a Selector Attribute), but do not exist as actual Data Elements in the current SOP Instance. @@ -239098,16 +242170,12 @@
Original Attributes Sequence and Instance Coercion DateTime - Every transfer of a SOP Instance may result in Attribute coercion (see ) by the receiving application. - The receiving application may also detect and correct errors in SOP Instances to bring them into conformance with the SOP Class definition without changing the SOP Instance UID or creating a derived Instance (see status Warning in and . - When performing coercion, correction or conversion, the application may set Instance Coercion DateTime (0008,0015) to the current datetime. - When performing such actions, the application may add an Item to the Original Attributes Sequence (0400,0561) describing the change and the prior values of replaced or removed Attributes. - Any existing Items in the Original Attributes Sequence shall be preserved. + Every transfer of a SOP Instance may result in Attribute coercion (see ) by the receiving application. The receiving application may also detect and correct errors in SOP Instances to bring them into conformance with the SOP Class definition without changing the SOP Instance UID or creating a derived Instance (see status Warning in and . + When performing coercion, correction or conversion, the application may set Instance Coercion DateTime (0008,0015) to the current datetime. When performing such actions, the application may add an Item to the Original Attributes Sequence (0400,0561) describing the change and the prior values of replaced or removed Attributes. Any existing Items in the Original Attributes Sequence shall be preserved. - Attributes may also be coerced, corrected or converted outside the context of transfer (e.g., while being managed in a storage system). For example, see the IHE Patient Information Reconciliation Integration Profile . - Such updates may also be recorded in the Instance Coercion DateTime (0008,0015) and Original Attributes Sequence (0400,0561). + Attributes may also be coerced, corrected or converted outside the context of transfer (e.g., while being managed in a storage system). For example, see the IHE Patient Information Reconciliation Integration Profile . Such updates may also be recorded in the Instance Coercion DateTime (0008,0015) and Original Attributes Sequence (0400,0561). If Patient ID (0010,0020) is included in the Modified Attributes Sequence (0400,0550), inclusion of Issuer of Patient ID (0010,0021), even if unchanged, or absent in the original, can more precisely identify the context of the replaced value. @@ -239115,7 +242183,7 @@ - defines the Attributes of the Original Attributes Sequence (0400,0561). + defines the Attributes of the Original Attributes Sequence (0400,0561). @@ -239302,9 +242370,7 @@
Original Attributes Macro Attributes
Modified Attributes Sequence - Attributes that were replaced, added or removed shall be placed in the Modified Attributes Sequence (0400,0550) with their prior values. - If an Attribute within a Sequence was replaced, added or removed, the entire prior value of the Sequence shall be placed in the Modified Attributes Sequence (0400,0550); - this applies recursively up to the enclosing Sequence Attribute in the top level Data Set. + Attributes that were replaced, added or removed shall be placed in the Modified Attributes Sequence (0400,0550) with their prior values. If an Attribute within a Sequence was replaced, added or removed, the entire prior value of the Sequence shall be placed in the Modified Attributes Sequence (0400,0550); this applies recursively up to the enclosing Sequence Attribute in the top level Data Set. Attributes that were empty or absent and for which values have been added may be present in the Modified Attributes Sequence (0400,0550) with a zero length value. If an Attribute was replaced, added or removed because its value was nonconforming to its Value Representation or Value Multiplicity, it shall be included in the Modified Attributes Sequence (0400,0550) with a zero length value. Any Private Data Elements present in the Item shall be accompanied by their respective Private Data Element Creator Attribute. @@ -239312,15 +242378,15 @@
Nonconforming Modified Attributes Sequence If an Attribute Value was replaced or removed because its value was nonconforming to its Value Representation or Value Multiplicity, the original value (which was replaced by a zero length value in the Modified Attributes Sequence) may be recorded in the Nonconforming Modified Attributes Sequence (0400,0551). - The nonconforming Attribute is identified by the attributes of the Selector Attribute Macro. Because a single Attribute is being identified, Selector Attribute (0072,0026) shall be present. - The Data Set to which the Selector Attribute Macro applies is the single Item of the Modified Attributes Sequence (0400,0550) within the same Item of the Original Attributes Sequence (0400,0561). Therefore, the Modified Attributes Sequence (0400,0550) is not identified in the Selector Sequence Pointer (0072,0052). + The nonconforming Attribute is identified by the Attributes of the . Because a single Attribute is being identified, Selector Attribute (0072,0026) shall be present. + The Data Set to which the applies is the single Item of the Modified Attributes Sequence (0400,0550) within the same Item of the Original Attributes Sequence (0400,0561). Therefore, the Modified Attributes Sequence (0400,0550) is not identified in the Selector Sequence Pointer (0072,0052). - This is effectively the same as a pointer to the equivalent attribute in the original top level Data Set. + This is effectively the same as a pointer to the equivalent Attribute in the original top level Data Set. - Characters in text attributes non-conformant to the identified Specific Character Set (0008,0005) may be considered non-conformant to the VR. + Characters in text Attributes non-conformant to the identified Specific Character Set (0008,0005) may be considered non-conformant to the VR. For example, if Body Part Examined (0018,0015) had a nonconforming value, the Nonconforming Modified Attributes Sequence (0400,0551) Item would have the Attributes: @@ -239558,7 +242624,7 @@
A list of Frames that were extracted in the form of a simple list. Required if object extraction is based on a Frame Level Retrieve using the Simple Frame List (0008,1161) Attribute. - See "Instance and Frame Level Retrieve SOP Classes" + See "Instance and Frame Level Retrieve SOP Classes".
A list of Frames that were extracted in the form of one or more triplets Required if object extraction is based on a Frame Level Retrieve using the Calculated Frame List (0008,1162) Attribute. - See "Instance and Frame Level Retrieve SOP Classes" + See "Instance and Frame Level Retrieve SOP Classes".
The start and end times of the frames that were extracted. Required if object extraction is based on a Frame Level Retrieve using Time Range (0008,1163). - See "Instance and Frame Level Retrieve SOP Classes" + See "Instance and Frame Level Retrieve SOP Classes".
@@ -239630,7 +242696,7 @@ 3 @@ -239945,7 +243011,7 @@
General Reference Module Attributes
- Other images significantly related to this image (e.g., post-localizer CT image or Mammographic biopsy or partial view images). + Other images significantly related to this image (e.g., post-localizer CT image, Mammographic biopsy or partial view images, or slide images containing control material). One or more Items are permitted in this Sequence.
- General Reference Module Attributes + General Reference Module Attribute Descriptions
Derivation Description If an Image is identified to be a Derived Image (see ), Derivation Description (0008,2111) and Derivation Code Sequence (0008,9215) describe the way in which the image was derived. They may be used whether or not the Source Image Sequence (0008,2112) is provided. They may also be used in cases when the Derived Image pixel data is not significantly changed from one of the source images and the SOP Instance UID of the Derived Image is the same as the one used for the source image. @@ -240188,7 +243254,7 @@ (2000,0050)
- Human readable label that identifies the film session + Human readable label that identifies the film session.
- Amount of memory allocated for the film session. Value is expressed in KB + Amount of memory allocated for the film session. Value is expressed in KB.
- Identification of the owner of the film session + Identification of the owner of the film session.
+ Proposed Study Sequence + + (2130,00A0) + + Attributes that may be used to identify and describe the Patient, Study and Series that are the subject of this Film Session. + Only a single Item is permitted in this Sequence. +
+ >Patient's Name + + (0010,0010) + + See for description. +
+ >Patient ID + + (0010,0020) + + See for description. +
+ >Patient's Birth Date + + (0010,0030) + + See for description. +
+ >Patient's Birth Time + + (0010,0032) + + See for description. +
+ >Patient's Sex + + (0010,0040) + + See for description. +
+ >Patient's Age + + (0010,1010) + + See for description. +
+ >Other Patient ID + + (0010,1000) + + See for description. +
+ >Other Patient Names + + (0010,1001) + + See for description. +
+ >Ethnic Group + + (0010,2160) + + See for description. +
+ >Patient Comments + + (0010,4000) + + See for description. +
+ >Study Instance UID + + (0020,000D) + + See for description. +
+ >Study Date + + (0008,0020) + + See for description. +
+ >Study Time + + (0008,0030) + + See for description. +
+ >Study ID + + (0020,0010) + + See for description. +
+ >Study Description + + (0008,1030) + + See for description. +
+ >Accession Number + + (0008,0050) + + See for description. +
+ >Referring Physician’s Name + + (0008,0090) + + See for description. +
+ >Name of Physician(s) Reading Study + + (0008,1060) + + See for description. +
+ >Admitting Diagnoses Description + + (0008,1080) + + See for description. +
+ >Series Number + + (0020,0011) + + See for description. +
- - Proposed Study Sequence (2130,00A0) was previously included in this Module but has been retired. See PS3.3-2004. -
Basic Film Box Presentation Module @@ -240339,7 +243634,7 @@ (2010,0030)
- Identification of annotation display format. The definition of the annotation display formats and the annotation box position Sequence are defined in the Conformance Statement + Identification of annotation display format. The definition of the annotation display formats and the annotation box position Sequence are defined in the Conformance Statement.
- Further specifies the type of the interpolation function. Values are defined in Conformance Statement. Only valid for Magnification Type (2010,0060) = CUBIC + Further specifies the type of the interpolation function. Values are defined in Conformance Statement. Only valid for Magnification Type (2010,0060) = CUBIC.
- See for description + See for description.
- See for description + See for description.
- See for description + See for description.
- See for description + See for description.
- See for description + See for description. +
+ Original Image Sequence + + (2130,00C0) + + Attributes of the original modality images to be printed in this Film Session. + Only a single Item is permitted in this Sequence. +
+ >Study Instance UID + + (0020,000D) + + See for description. +
+ >Series Instance UID + + (0020,000E) + + See for description. +
+ >Patient ID + + (0010,0020) + + See for description. +
+ >Referenced SOP Class UID + + (0008,1150) + + SOP Class UID of the original modality image used to create this Image Box. +
+ >Referenced SOP Instance UID + + (0008,1155) + + SOP Instance UID of the original modality image used to create this Image Box.
- Referenced Image Overlay Box Sequence (2020,0130) and Original Image Sequence (2130,00C0) were previously included in this Module but have been retired. See PS3.3-2004. + Referenced Image Overlay Box Sequence (2020,0130) was previously included in this Module but has been retired. See PS3.3-2004.
Image Box Position @@ -241421,7 +244783,9 @@
Image Box Relationship Module (Retired) - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See + PS3.3-1998 + .
Basic Annotation Presentation Module @@ -241449,7 +244813,7 @@ (2030,0010) - The position of the annotation box in the parent film box. Annotation position sequence depends on the selected Annotation Display Format ID (2010,0030) + The position of the annotation box in the parent film box. Annotation position sequence depends on the selected Annotation Display Format ID (2010,0030). @@ -241460,7 +244824,7 @@ (2030,0020) - Text string + Text string. @@ -242186,9 +245550,9 @@ FINISHER LOW - The finisher is low on supplies - - + The finisher is low on supplies. + + LOW 8X10 @@ -242466,9 +245830,9 @@ NO RECEIVE MGZ - The film receive magazine not available - - + The film receive magazine not available. + + NO RIBBON @@ -242578,9 +245942,9 @@ QUEUED - Print Job in Queue - - + Print Job in Queue. + + RECEIVER FULL @@ -242643,15 +246007,19 @@
Image Overlay Box Presentation Module (Retired) - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See + PS3.3-1998 + .
Image Overlay Box Relationship Module (Retired) - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See + PS3.3-1998 + .
Print Request Module - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Printer Configuration Module @@ -242886,7 +246254,7 @@ (0028,0011) - Number of printable columns in an Image Box + Number of printable columns in an Image Box. @@ -243270,7 +246638,7 @@ Conditions under which Attributes are required (i.e., Retrieve AE Title, etc.) are defined in the Storage Commitment Service Class in . - Referenced Performed Procedure Step Sequence (0008,1111) was included in this Module in earlier versions, but its use here has been retired. See PS3.4-2001, in which the Attribute was formerly known as Referenced Study Component Sequence. + Referenced Performed Procedure Step Sequence (0008,1111) was included in this Module in earlier versions, but its use here has been retired. See PS3.4-2001, in which the Attribute was formerly known as Referenced Study Component Sequence. @@ -243329,11 +246697,11 @@
Queue Management Specific Modules - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Stored Print Specific Modules - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
SR Document Modules @@ -243476,7 +246844,7 @@ 3 - Description of the Series + Description of the Series. @@ -243555,7 +246923,7 @@
SR Document General Module - defines the general Attributes of an SR Document Instance. These Attributes identify the SR Document and provide context for the entire document. + specifies the Attributes of an SR Document Instance. These Attributes identify the SR Document and provide context for the entire document. @@ -244081,262 +247449,15 @@ Required if this Document fulfills at least one Requested Procedure. May be present otherwise. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -244480,9 +247601,9 @@
SR Document General Module Attributes
- >Study Instance UID - - (0020,000D) - - 1 - - Unique identifier for the Study. -
- >Referenced Study Sequence - - (0008,1110) - - 2 - - Uniquely identifies the Study SOP Instance. - Zero or one Item shall be included in this Sequence. - See . -
- - >>Include - - - - -
- >Accession Number - - (0008,0050) - - 2 - - A departmental Information System generated number that identifies the Imaging Service Request. -
- >Issuer of Accession Number Sequence - - (0008,0051) - - 3 - - Identifier of the Assigning Authority that issued the Accession Number. - Only a single Item is permitted in this Sequence. -
- - >>Include - - - - -
- >Placer Order Number / Imaging Service Request - - (0040,2016) - - 2 - - The order number assigned to the Imaging Service Request by the party placing the order. -
- >Order Placer Identifier Sequence - - (0040,0026) - - 3 - - Identifier of the Assigning Authority that issued the Placer Order Number. - Only a single Item is permitted in this Sequence. -
- - >>Include - - - - -
- >Filler Order Number / Imaging Service Request - - (0040,2017) - - 2 - - The order number assigned to the Imaging Service Request by the party filling the order. -
- >Order Filler Identifier Sequence - - (0040,0027) - - 3 - - Identifier of the Assigning Authority that issued the Filler Order Number. - Only a single Item is permitted in this Sequence. -
- - >>Include + + >Include - -
- >Requested Procedure ID - - (0040,1001) - - 2 - - Identifier of the related Requested Procedure -
- >Requested Procedure Description - - (0032,1060) - - 2 - - Institution-generated administrative description or classification of Requested Procedure. -
- >Requested Procedure Code Sequence - - (0032,1064) - - 2 - - A Sequence that conveys the requested procedure. Zero or one Item shall be included in this Sequence. -
- - >>Include - - - - - No Baseline CID is defined. - -
- >Reason for the Requested Procedure - - (0040,1002) - - 3 - - Reason for requesting this procedure. -
- >Reason for Requested Procedure Code Sequence - - (0040,100A) - - 3 - - Coded Reason for requesting this procedure. - One or more Items are permitted in this Sequence. -
- - >>Include - - - - - No Baseline CID is defined. - + +
- Hierarchical SOP Instance Reference Macro + Hierarchical SOP Instance Reference Macro - specifies the Attributes that reference a list of SOP Instances. + specifies the Attributes of the , which reference a list of SOP Instances. @@ -244513,9 +247634,9 @@ 1 - + Unique identifier for the Study. + + - + One or more Items shall be included in this Sequence. + + @@ -245265,573 +248673,6 @@
Hierarchical SOP Instance Reference Macro Attributes
- Unique identifier for the Study -
Referenced Series Sequence @@ -244528,9 +247649,9 @@ Sequence of Items where each Item includes the Attributes of a Series containing referenced Composite Object(s). - One or more Items shall be included in this Sequence -
@@ -244854,7 +247975,7 @@ For a completed SR Document satisfying (i.e., being the final report for) the current Requested Procedure(s), this Sequence shall list the full set of Composite SOP Instances created for the current Requested Procedure(s). For other SOP Instances that include the , this Sequence shall contain at minimum the set of Composite SOP Instances from the current Requested Procedure(s) that are referenced in the content tree. The Pertinent Other Evidence Sequence (0040,A385) Attribute is used to reference all other evidence considered pertinent for this SR Document that is not listed in the Current Requested Procedure Evidence Sequence (0040,A375). This requires that the same SOP Instance shall not be referenced in both of these Sequences. - For the purposes of inclusion in the Current Requested Procedure Evidence Sequence (0040,A375) and the Pertinent Other Evidence Sequence (0040,A385), the set of Composite SOP Instances is defined to include not only the images and waveforms referenced in the content tree, but also all presentation states, real world value maps and other accompanying Composite Instances that are referenced from the Content Items. + For the purposes of inclusion in the Current Requested Procedure Evidence Sequence (0040,A375) and the Pertinent Other Evidence Sequence (0040,A385), the set of Composite SOP Instances is defined to include not only the images and waveforms referenced in the content tree, but also all presentation states, Real World Value maps and other accompanying Composite Instances that are referenced from the Content Items.
Identified Person or Device Macro @@ -245218,6 +248339,293 @@
+
+ Referenced Request Macro + + defines the Attributes of a Requested Procedure that was associated with production of a Document. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Referenced Request Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Study Instance UID + + (0020,000D) + + 1 + + Unique identifier for the Study. +
+ Referenced Study Sequence + + (0008,1110) + + 2 + + Uniquely identifies the Study SOP Instance. + Zero or one Item shall be included in this Sequence. + See . +
+ + >Include + + + + +
+ Accession Number + + (0008,0050) + + 2 + + A departmental Information System generated number that identifies the Imaging Service Request. +
+ Issuer of Accession Number Sequence + + (0008,0051) + + 3 + + Identifier of the Assigning Authority that issued the Accession Number. + Only a single Item is permitted in this Sequence. +
+ + >Include + + + + +
+ Placer Order Number / Imaging Service Request + + (0040,2016) + + 2 + + The order number assigned to the Imaging Service Request by the party placing the order. +
+ Order Placer Identifier Sequence + + (0040,0026) + + 3 + + Identifier of the Assigning Authority that issued the Placer Order Number. + Only a single Item is permitted in this Sequence. +
+ + >Include + + + + +
+ Filler Order Number / Imaging Service Request + + (0040,2017) + + 2 + + The order number assigned to the Imaging Service Request by the party filling the order. +
+ Order Filler Identifier Sequence + + (0040,0027) + + 3 + + Identifier of the Assigning Authority that issued the Filler Order Number. + Only a single Item is permitted in this Sequence. +
+ + >Include + + + + +
+ Requested Procedure ID + + (0040,1001) + + 2 + + Identifier of the related Requested Procedure. +
+ Requested Procedure Description + + (0032,1060) + + 2 + + Institution-generated administrative description or classification of Requested Procedure. +
+ Requested Procedure Code Sequence + + (0032,1064) + + 2 + + A Sequence that conveys the requested procedure. Zero or one Item shall be included in this Sequence. +
+ + >Include + + + + + No Baseline CID is defined. + +
+ Reason for the Requested Procedure + + (0040,1002) + + 3 + + Reason for requesting this procedure. +
+ Reason for Requested Procedure Code Sequence + + (0040,100A) + + 3 + + Coded Reason for requesting this procedure. + One or more Items are permitted in this Sequence. +
+ + >Include + + + + + No Baseline CID is defined. + +
+ + +
SR Document Content Module @@ -245249,7 +248657,7 @@
- With a Value Type (0040,A040) of CONTAINER + With a Value Type (0040,A040) of CONTAINER.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Document Content Macro Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- Value Type - - (0040,A040) - - 1 - - The type of the value encoded in this Content Item. - - Enumerated Values: - - TEXT - - - - - - NUM - - - - - - CODE - - - - - - DATE - - - - - - TIME - - - - - - DATETIME - - - - - - UIDREF - - - - - - PNAME - - - - - - COMPOSITE - - - - - - IMAGE - - - - - - WAVEFORM - - - - - - SCOORD - - - - - - SCOORD3D - - - - - - TCOORD - - - - - - CONTAINER - - - - - - TABLE - - - - - - See for further explanation. -
- Concept Name Code Sequence - - (0040,A043) - - 1C - - Code describing the concept represented by this Content Item. Also conveys the value of Document Title and section headings in documents. - Only a single Item shall be included in this Sequence. - Required if Value Type (0040,A040) is TEXT, NUM, CODE, DATETIME, DATE, TIME, UIDREF, TABLE or PNAME. - Required if Value Type (0040,A040) is CONTAINER and a heading is present, or this is the Root Content Item. - - That is, containers without headings do not require Concept Name Code Sequence - - Required if Value Type (0040,A040) is COMPOSITE, IMAGE, WAVEFORM, SCOORD, SCOORD3D or TCOORD, and the Purpose of Reference is conveyed in the Concept Name. - - Though many Templates in - do not require that the Purpose of Reference be conveyed in the Concept Name, - a generic Concept Name, such as - (260753009, SCT, "Source"), - may be used, since anonymous (unnamed) Content Items may be undesirable for some implementations (e.g., for which the name of a name-value pair is required). - UMLS (C0449416) - maps - (260753009, SCT, "Source") - to - (C25683, NCIt, "Source"). - NCIt defines it as "Where something is available or from where it originates". - - See for further explanation. -
- - >Include - - - - - No Baseline CID is defined. - -
- Text Value - - (0040,A160) - - 1C - - This is the value of the Content Item. - Required if Value Type (0040,A040) is TEXT. - Text data that is unformatted and whose manner of display is implementation dependent. - The text value may contain spaces, as well as multiple lines separated by CR LF, but otherwise no format control characters (such as horizontal or vertical tab and form feed) shall be present, even if permitted by the Value Representation of UT. - The text shall be interpreted as specified by Specific Character Set (0008,0005) if present in the . - - The text may contain single or multi-byte characters and use code extension techniques as described in if permitted by the values of Specific Character Set (0008,0005). - -
- DateTime - - (0040,A120) - - 1C - - This is the value of the Content Item. - Required if Value Type (0040,A040) is DATETIME. -
- Date - - (0040,A121) - - 1C - - This is the value of the Content Item. - Required if Value Type (0040,A040) is DATE. -
- Time - - (0040,A122) - - 1C - - This is the value of the Content Item. - Required if Value Type (0040,A040) is TIME. -
- Person Name - - (0040,A123) - - 1C - - This is the value of the Content Item. - Required if Value Type (0040,A040) is PNAME. -
- UID - - (0040,A124) - - 1C - - This is the value of the Content Item. - Required if Value Type (0040,A040) is UIDREF. -
- - Include if and only if Value Type (0040,A040) is NUM. - - - -
- - Include if and only if Value Type (0040,A040) is CODE. - - - -
- - Include if and only if Value Type (0040,A040) is COMPOSITE. - - - -
- - Include if and only if Value Type (0040,A040) is IMAGE. - - - -
- - Include if and only if Value Type (0040,A040) is WAVEFORM. - - - -
- - Include if and only if Value Type (0040,A040) is SCOORD. - - - -
- - Include if and only if Value Type (0040,A040) is SCOORD3D. - - - -
- - Include if and only if Value Type (0040,A040) is TCOORD. - - - -
- - Include if and only if Value Type (0040,A040) is CONTAINER. - - - -
- - Include if and only if Value Type (0040,A040) is TABLE. - - - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Document Relationship Macro Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- Observation DateTime - - (0040,A032) - - 1C - - The date and time on which this Content Item was completed. For the purpose of recording measurements or logging events, completion time is defined as the ending time of data acquisition of the measurement, or the ending time of occurrence of the event. - Required if the date and time are different from Content Date (0008,0023) and Content Time (0008,0033) or Observation DateTime (0040,A032) defined in higher Items. May be present otherwise. - - When Content Items are copied into successor reports, Content Date (0008,0023) and Content Time (0008,0033) of the new report are likely to be different than the date and time of the original observation. Therefore this Attribute may need to be included in any copied Content Items to satisfy the condition. - -
- Observation UID - - (0040,A171) - - 3 - - Unique identifier for the observation Content Item (and its subsidiary Content Items, if any). The UID represents the semantic content of the observation; an encoding of the same observation with the same context into another representation (e.g., a CDA Entry) may use the same UID. -
- Content Sequence - - (0040,A730) - - 1C - - A potentially recursively nested Sequence of Items that conveys content that is the Target of Relationships with the enclosing Source Content Item. - One or more Items shall be included in this Sequence. - Required if the enclosing Content Item has relationships. - - - - If this Attribute is not present then the enclosing Item is a leaf. - - - The order of Items within this Sequence is semantically significant for presentation. - - - - See for further explanation. -
- >Relationship Type - - (0040,A010) - - 1 - - The type of relationship between the (enclosing) Source Content Item and the Target Content Item. - IODs specify additional constraints on Relationships (including lists of Enumerated Values). - - Enumerated Values: - - CONTAINS - - - - - - HAS PROPERTIES - - - - - - HAS OBS CONTEXT - - - - - - HAS ACQ CONTEXT - - - - - - INFERRED FROM - - - - - - SELECTED FROM - - - - - - HAS CONCEPT MOD - - - - - - See for further explanation. -
- - >Include if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference. - - - -
- - >Include if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference. - - - -
- >Referenced Content Item Identifier - - (0040,DB73) - - 1C - - An ordered set of one or more integers that uniquely identifies the Target Content Item of the relationship. - The root Content Item is referenced by a single value of 1. - Each subsequent integer represents an ordinal position of a Content Item in the Content Sequence (0040,A730) in which it belongs. The Referenced Content Item Identifier is the set of these ordinal positions along the by-value relationship path. The number of values in this Multi-Value Attribute is exactly the number of relationships traversed in the SR content tree plus one. - - - - See . - - - Content Items are ordered in a Content Sequence starting from 1 as defined in VR of SQ (see ). - - - - Required if the Target Content Item is denoted by-reference, i.e., the Document Relationship Macro and Document Content Macro are not included. -
SR Document Content Tree The Module consists of a single root Content Item that is the root of the SR Document tree. The root Content Item is of type CONTAINER, and its Content Sequence conveys either directly or indirectly through further nested Content Sequences, all of the other Content Items in the document. This root Content Item shall have a heading in the Concept Name Code Sequence (0040,A043) that conveys the title of the SR Document, i.e., the Document Title. @@ -246141,7 +248982,7 @@
Concept Name Code Sequence - Concept Name Code Sequence (0040,A043) conveys the name of the concept whose value is expressed by the value attribute or set of attributes. Depending on the Value Type (0040,A040), the meaning of the Concept Name Code Sequence may reflect specifics of the use of the particular data type (see ). + Concept Name Code Sequence (0040,A043) conveys the name of the concept whose value is expressed by the value Attribute or set of Attributes. Depending on the Value Type (0040,A040), the meaning of the Concept Name Code Sequence may reflect specifics of the use of the particular data type (see ).
Continuity of Content @@ -246177,9 +249018,9 @@ Source Item contains Target Content Item. - E.g., CONTAINER "History" {CONTAINS: TEXT "mother had breast cancer", CONTAINS: IMAGE} - - + E.g., CONTAINER "History" {CONTAINS: TEXT "mother had breast cancer", CONTAINS: IMAGE}. + + HAS OBS CONTEXT @@ -246189,9 +249030,9 @@ Target Content Items shall convey any specialization of Observation Context needed for unambiguous documentation of the Source Content Item. - E.g., CONTAINER "Report" {HAS OBS CONTEXT: PNAME "Recording Observer" = "Smith^John^^Dr^"} - - + E.g., CONTAINER "Report" {HAS OBS CONTEXT: PNAME "Recording Observer" = "Smith^John^^Dr^"}. + + HAS CONCEPT MOD @@ -246203,9 +249044,9 @@ Used to qualify or describe the Concept Name of the Source Content Item, such as to create a post-coordinated description of a concept, or to further describe a concept. E.g., CODE "Chest X-Ray" {HAS CONCEPT MOD: CODE "View = PA and Lateral"} E.g., CODE "Breast" {HAS CONCEPT MOD: TEXT "French Translation" = "Sein"} - E.g., CODE "2VCXRPALAT" {HAS CONCEPT MOD: TEXT "Further Explanation" = "Chest X-Ray, Two Views, Postero-anterior and Lateral"} - - + E.g., CODE "2VCXRPALAT" {HAS CONCEPT MOD: TEXT "Further Explanation" = "Chest X-Ray, Two Views, Postero-anterior and Lateral"}. + + HAS PROPERTIES @@ -246278,589 +249119,946 @@
-
-
- SR Content Tree Example (Informative) - - depicts the content of an example diagnostic interpretation. - - - - For nodes of type CONTAINER, the contents of the Concept Name Code Sequence are shown in quotes and italicized. - - - For nodes of Value Type CODE, PNAME, NUM the contents are shown as "Concept Name Code Sequence = Value". - - - For the nodes of Value Type IMAGE and SCOORD, the contents of the Concept Name Code Sequence indicating the purpose of reference are shown in quotes and italicized. - - - The root node containing the Document Type is illustrated using a post-coordinated node of "Chest X-Ray", qualified using a HAS CONCEPT MOD relationship by a child with a CODE meaning "Views = PA and Lateral". An alternative would be to use a single pre-coordinated code in one node that applies to the entire concept of a "Two-view (PA and Lateral) Chest X-Ray". However, the use of pre-coordinated terms to describe complex concepts rapidly becomes unwieldy and difficult to search on (in the sense that more specific pre-coordinated codes do not have a visible relationship with more general codes). If it were necessary to include a longer textual description of Document Type, then this could be achieved with a HAS CONCEPT MOD relationship with one or more TEXT nodes, perhaps in different languages. - - - The Document Type is only a title, and is not being used to convey the Procedure Context, although in this example it does appear to contain a description of some aspects of Procedure Context. - - - - -
- SR Content Tree for an Example Diagnostic Interpretation (Informative) - - - - - -
- -
-
- Observation Context Encoding - Observation Context describes who or what is performing the interpretation (observer context), whether the examination of evidence is direct or quoted (quotation mode), what procedure generated the evidence that is being interpreted (procedure context), and who or what is the subject of the evidence that is being interpreted (subject context). - Initial Observation Context is defined outside the SR Document Content tree by other Modules in the SR IOD. The specifies the default Subject Context, the specifies the default Procedure Context, and the specifies the default Observer Context. The default context has the meaning "this Structured Report was produced by the observer identified in the , using direct observation, for the procedure identified in the , and is about the patient identified in the ." Observation Context defined by Attributes in these Modules applies to all Content Items in the SR Document Content tree and - need not be explicitly coded in the tree. The initial Observation Context from outside the tree can be explicitly replaced for the entire tree, or for any sub-tree. - Observer Context is set from the Author Observer Sequence (0040,A078), if present, or secondarily from the Verifying Observer Sequence (0040,A073). If neither is present, the Observer Context is undefined. - - In the absence of Observer Context, it may be presumed that the observations were generated by or with the equipment identified in the . - - The Procedure Context is set from the Study Instance UID (0020,000D), Study ID (0020,0010), Accession Number (0008,0050), and Procedure Code Sequence (0008,1032) of the . The Referenced Request Sequence (0040,A370) might include an Item with the same Study Instance UID that further elaborates the Procedure Context, e.g., providing Placer Order Number / Imaging Service Request (0040,2016) and/or Filler Order Number / Imaging Service Request (0040,2017). If the Referenced Request Sequence includes Items with different Study Instance UIDs, those shall be treated as Procedure Context only if explicitly encoded in the Content Tree. - Medical or clinical characteristics of the patient specified in the , such as in Attributes Patient's Size (0010,1020) and Patient's Weight (0010,1030), shall not be inherited by the Content Tree as part of the default Patient Context. Such characteristics must be specifically encoded in the Content Tree to be part of the Structured Report. - - The may be included in SR SOP Instances. As part of the Study IE shared by all SOP Instances within a Study, such inclusion should be consistent across all Instances. However, its purpose is to provide a minimum set of clinical context for the (initial) interpretation of the images or waveforms of the Study. An SR SOP Instance that documents the interpretation must explicitly describe the relevant clinical context in the SR Content Tree. - - If a Content Item in the SR Document Content tree has Observation Context different from the initial context already encoded elsewhere in the IOD, the context information applying to that Content Item shall be encoded as child nodes of the Content Item in the tree using the HAS OBS CONTEXT relationship. That is, Observation Context is a property of its parent Content Item. - The context information specified in the Observation Context child nodes (i.e., target of the HAS OBS CONTEXT relationship) sets the Observation Context of their parent node Content Item. Observation Context is encoded in the same manner as any other Content Item. - The Observation Context applies to all the by-value descendant nodes of that parent node regardless of the relationship type between the parent and the descendant nodes, until and unless the context of a descendant node is reset by other Observation Context Content Items. Observation Context shall not be inherited across by-reference relationships. The four dimensions of Observation Context (observer context, quotation mode, procedure context, and subject context) may be reset independently; e.g., resetting the subject context does not reset the observer or procedure context, or the quotation mode. See the example in . - - For example, the "subject context" may be defined by attaching an appropriate Content Item to the root node with a HAS OBS CONTEXT relationship. This "subject context" then applies not only to the root node, but to all its descendants, until such time as a Content Item explicitly replaces the "subject context" attribute, the new value of which is then inherited by all of that nodes descendants. - - Observation DateTime is not included as part of the HAS OBS CONTEXT relationship, and therefore is not inherited along with other Observation Context. The Observation DateTime Attribute is included in each Content Item, which allows different observation dates and times to be attached to different Content Items. - The IOD may specify restrictions on Content Items and Relationship Types that also constrain the flexibility with which Observation Context may be described. - The IOD may specify Templates that offer or restrict patterns and content in Observation Context. - - - - Node 2 inherits any Observation Context of Node 1, which is then extended or replaced by the additional Observation Context defined in Nodes C1 and C2 (that is C1 and C2 are properties of 2). - - - Node 3 and its descendents inherit the Observation Context of Node 2, which includes C1 and C2. - - - Node 4 inherits the Observation Context of Node 2, which includes C1 and C2. - - - - -
- Definition and Inheritance of Observation Context (Informative) - - - - - -
- -
-
- Key Object Selection Modules -
- Key Object Document Series Module - - defines the Attributes of the Key Object Document Series. - - Series of Key Object Selection Documents are separate from Series of Images or other Composite SOP Instances. Key Object Documents do not reside in a Series of Images or other Composite SOP Instances. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Key Object Document Series Module Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- Modality - - (0008,0060) - - 1 - - Type of device, process or method that created the Instances in this Series. - - Enumerated Values: - - KO - - Key Object Selection - - - -
- Series Instance UID - - (0020,000E) - - 1 - - Unique identifier of the Series. - - No specific semantics are specified. - -
- Series Number - - (0020,0011) - - 1 - - A number that identifies the Series. - - No specific semantics are specified. - -
- Series Date - - (0008,0021) - - 3 - - Date the Series started. -
- Series Time - - (0008,0031) - - 3 - - Time the Series started. -
- Protocol Name - - (0018,1030) - - 3 - - Description of the conditions under which the Series was performed. - - This may represent the type of analysis used in creation of the KO SOP Instances. - -
- Series Description - - (0008,103E) - - 3 - - Description of the Series -
- Series Description Code Sequence - - (0008,103F) - - 3 - - A coded description of the Series. - Only a single Item is permitted in this Sequence. -
- - >Include - - - - - No Baseline CID is defined. - -
- Referenced Performed Procedure Step Sequence - - (0008,1111) - - 2 - - Uniquely identifies the Performed Procedure Step SOP Instance for which the Series is created. - Zero or one Item shall be included in this Sequence. - - See notes on this Attribute in - - -
- - >Include - - - - -
-
-
- Key Object Document Module - - defines the general Attributes of a Key Object Selection Document. These Attributes identify and provide context for the Key Object Selection Document. - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Key Object Document Module Attributes
- Attribute Name - - Tag +
+ Document Content Macro + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Document Content Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Value Type + + (0040,A040) + + 1 + + The type of the value encoded in this Content Item. + + Enumerated Values: + + TEXT + + + + + + NUM + + + + + + CODE + + + + + + DATE + + + + + + TIME + + + + + + DATETIME + + + + + + UIDREF + + + + + + PNAME + + + + + + COMPOSITE + + + + + + IMAGE + + + + + + WAVEFORM + + + + + + SCOORD + + + + + + SCOORD3D + + + + + + TCOORD + + + + + + CONTAINER + + + + + + TABLE + + + + + + See for further explanation. +
+ Concept Name Code Sequence + + (0040,A043) + + 1C + + Code describing the concept represented by this Content Item. Also conveys the value of Document Title and section headings in documents. + Only a single Item shall be included in this Sequence. + Required if Value Type (0040,A040) is TEXT, NUM, CODE, DATETIME, DATE, TIME, UIDREF, TABLE or PNAME. + Required if Value Type (0040,A040) is CONTAINER and a heading is present, or this is the Root Content Item. + + That is, containers without headings do not require Concept Name Code Sequence + + Required if Value Type (0040,A040) is COMPOSITE, IMAGE, WAVEFORM, SCOORD, SCOORD3D or TCOORD, and the Purpose of Reference is conveyed in the Concept Name. + + Though many Templates in do not require that the Purpose of Reference be conveyed in the Concept Name, a generic Concept Name, such as (260753009, SCT, "Source"), may be used, since anonymous (unnamed) Content Items may be undesirable for some implementations (e.g., for which the name of a name-value pair is required). UMLS (C0449416) maps (260753009, SCT, "Source") to (C25683, NCIt, "Source"). NCIt defines it as "Where something is available or from where it + originates". + + See for further explanation. +
+ + >Include + + + + + No Baseline CID is defined. + +
+ Text Value + + (0040,A160) + + 1C + + This is the value of the Content Item. + Required if Value Type (0040,A040) is TEXT. + Text data that is unformatted and whose manner of display is implementation dependent. + The text value may contain spaces, as well as multiple lines separated by CR LF, but otherwise no format control characters (such as horizontal or vertical tab and form feed) shall be present, even if permitted by the Value Representation of UT. + The text shall be interpreted as specified by Specific Character Set (0008,0005) if present in the . + + The text may contain single or multi-byte characters and use code extension techniques as described in if permitted by the values of Specific Character Set (0008,0005). + +
+ DateTime + + (0040,A120) + + 1C + + This is the value of the Content Item. + Required if Value Type (0040,A040) is DATETIME. +
+ Date + + (0040,A121) + + 1C + + This is the value of the Content Item. + Required if Value Type (0040,A040) is DATE. +
+ Time + + (0040,A122) + + 1C + + This is the value of the Content Item. + Required if Value Type (0040,A040) is TIME. +
+ Person Name + + (0040,A123) + + 1C + + This is the value of the Content Item. + Required if Value Type (0040,A040) is PNAME. +
+ UID + + (0040,A124) + + 1C + + This is the value of the Content Item. + Required if Value Type (0040,A040) is UIDREF. +
+ + Include if and only if Value Type (0040,A040) is NUM. + + + +
+ + Include if and only if Value Type (0040,A040) is CODE. + + + +
+ + Include if and only if Value Type (0040,A040) is COMPOSITE. + + + +
+ + Include if and only if Value Type (0040,A040) is IMAGE. + + + +
+ + Include if and only if Value Type (0040,A040) is WAVEFORM. + + + +
+ + Include if and only if Value Type (0040,A040) is SCOORD. + + + +
+ + Include if and only if Value Type (0040,A040) is SCOORD3D. + + + +
+ + Include if and only if Value Type (0040,A040) is TCOORD. + + + +
+ + Include if and only if Value Type (0040,A040) is CONTAINER. + + + +
+ + Include if and only if Value Type (0040,A040) is TABLE. + + + +
+
+
+ Document Relationship Macro + + + + + + - - - + + + +
Document Relationship Macro Attributes
+ Attribute Name - Type + Tag - Attribute Description + Type + + Attribute Description
- Instance Number + Observation DateTime - (0020,0013) + (0040,A032) - 1 + 1C - A number that identifies the Document. + The date and time on which this Content Item was completed. For the purpose of recording measurements or logging events, completion time is defined as the ending time of data acquisition of the measurement, or the ending time of occurrence of the event. + Required if the date and time are different from Content Date (0008,0023) and Content Time (0008,0033) or Observation DateTime (0040,A032) defined in higher Items. May be present otherwise. + + When Content Items are copied into successor reports, Content Date (0008,0023) and Content Time (0008,0033) of the new report are likely to be different than the date and time of the original observation. Therefore this Attribute may need to be included in any copied Content Items to satisfy the condition. +
- Content Date + Observation UID - (0008,0023) + (0040,A171) - 1 + 3 - The date the document content creation started. + Unique identifier for the observation Content Item (and its subsidiary Content Items, if any). The UID represents the semantic content of the observation; an encoding of the same observation with the same context into another representation (e.g., a CDA Entry) may use the same UID.
- Content Time + Content Sequence - (0008,0033) + (0040,A730) - 1 + 1C - The time the document content creation started. + A potentially recursively nested Sequence of Items that conveys content that is the Target of Relationships with the enclosing Source Content Item. + One or more Items shall be included in this Sequence. + Required if the enclosing Content Item has relationships. + + + + If this Attribute is not present then the enclosing Item is a leaf. + + + The order of Items within this Sequence is semantically significant for presentation. + + + + See for further explanation.
- Referenced Request Sequence + >Relationship Type - (0040,A370) + (0040,A010) - 1C + 1 - Identifies Requested Procedures to which this Document pertains. - One or more Items shall be included in this Sequence. - Required if this Document pertains to at least one Requested Procedure. + The type of relationship between the (enclosing) Source Content Item and the Target Content Item. + IODs specify additional constraints on Relationships (including lists of Enumerated Values). + + Enumerated Values: + + CONTAINS + + + + + + HAS PROPERTIES + + + + + + HAS OBS CONTEXT + + + + + + HAS ACQ CONTEXT + + + + + + INFERRED FROM + + + + + + SELECTED FROM + + + + + + HAS CONCEPT MOD + + + + + + See for further explanation.
- >Study Instance UID + + + >Include if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference. + - (0020,000D) + + - 1 +
+ + >Include if the Target Content Item is included by-value in the Source Content Item. The Macro shall not be present if the relationship is by-reference. + - Unique identifier for the Study. +
- >Referenced Study Sequence + >Referenced Content Item Identifier - (0008,1110) + (0040,DB73) - 2 + 1C - Uniquely identifies the Study SOP Instance. - Zero or one Item shall be included in this Sequence. - See . + An ordered set of one or more integers that uniquely identifies the Target Content Item of the relationship. + The root Content Item is referenced by a single value of 1. + Each subsequent integer represents an ordinal position of a Content Item in the Content Sequence (0040,A730) in which it belongs. The Referenced Content Item Identifier is the set of these ordinal positions along the by-value relationship path. The number of values in this Multi-Value Attribute is exactly the number of relationships traversed in the SR content tree plus one. + + + + See . + + + Content Items are ordered in a Content Sequence starting from 1 as defined in VR of SQ (see ). + + + + Required if the Target Content Item is denoted by-reference, i.e., the and are not included.
+ +
+ SR Content Tree Example (Informative) + + depicts the content of an example diagnostic interpretation. + + + + For nodes of type CONTAINER, the contents of the Concept Name Code Sequence are shown in quotes and italicized. + + + For nodes of Value Type CODE, PNAME, NUM the contents are shown as "Concept Name Code Sequence = Value". + + + For the nodes of Value Type IMAGE and SCOORD, the contents of the Concept Name Code Sequence indicating the purpose of reference are shown in quotes and italicized. + + + The root node containing the Document Type is illustrated using a post-coordinated node of "Chest X-Ray", qualified using a HAS CONCEPT MOD relationship by a child with a CODE meaning "Views = PA and Lateral". An alternative would be to use a single pre-coordinated code in one node that applies to the entire concept of a "Two-view (PA and Lateral) Chest X-Ray". However, the use of pre-coordinated terms to describe complex concepts rapidly becomes unwieldy and difficult to search on (in the sense that more specific pre-coordinated codes do not have a visible relationship with more general codes). If it were necessary to include a longer textual description of Document Type, then this could be achieved with a HAS CONCEPT MOD relationship with one or more TEXT nodes, perhaps in different languages. + + + The Document Type is only a title, and is not being used to convey the Procedure Context, although in this example it does appear to contain a description of some aspects of Procedure Context. + + + + +
+ SR Content Tree for an Example Diagnostic Interpretation (Informative) + + + + + +
+ +
+
+ Observation Context Encoding + Observation Context describes who or what is performing the interpretation (observer context), whether the examination of evidence is direct or quoted (quotation mode), what procedure generated the evidence that is being interpreted (procedure context), and who or what is the subject of the evidence that is being interpreted (subject context). + Initial Observation Context is defined outside the SR Document Content tree by other Modules in the SR IOD. The specifies the default Subject Context, the specifies the default Procedure Context, and the specifies the default Observer Context. The default context has the meaning "this Structured Report was produced by the observer identified in the , using direct observation, for the procedure identified in the , and is about the patient identified in the ." Observation Context defined by Attributes in these Modules applies to all Content Items in the SR Document Content tree and + need not be explicitly coded in the tree. The initial Observation Context from outside the tree can be explicitly replaced for the entire tree, or for any sub-tree. + Observer Context is set from the Author Observer Sequence (0040,A078), if present, or secondarily from the Verifying Observer Sequence (0040,A073). If neither is present, the Observer Context is undefined. + + In the absence of Observer Context, it may be presumed that the observations were generated by or with the equipment identified in the . + + The Procedure Context is set from the Study Instance UID (0020,000D), Study ID (0020,0010), Accession Number (0008,0050), and Procedure Code Sequence (0008,1032) of the . The Referenced Request Sequence (0040,A370) might include an Item with the same Study Instance UID that further elaborates the Procedure Context, e.g., providing Placer Order Number / Imaging Service Request (0040,2016) and/or Filler Order Number / Imaging Service Request (0040,2017). If the Referenced Request Sequence includes Items with different Study Instance UIDs, those shall be treated as Procedure Context only if explicitly encoded in the Content Tree. + Medical or clinical characteristics of the patient specified in the , such as in Attributes Patient's Size (0010,1020) and Patient's Weight (0010,1030), shall not be inherited by the Content Tree as part of the default Patient Context. Such characteristics must be specifically encoded in the Content Tree to be part of the Structured Report. + + The may be included in SR SOP Instances. As part of the Study IE shared by all SOP Instances within a Study, such inclusion should be consistent across all Instances. However, its purpose is to provide a minimum set of clinical context for the (initial) interpretation of the images or waveforms of the Study. An SR SOP Instance that documents the interpretation must explicitly describe the relevant clinical context in the SR Content Tree. + + If a Content Item in the SR Document Content tree has Observation Context different from the initial context already encoded elsewhere in the IOD, the context information applying to that Content Item shall be encoded as child nodes of the Content Item in the tree using the HAS OBS CONTEXT relationship. That is, Observation Context is a property of its parent Content Item. + The context information specified in the Observation Context child nodes (i.e., target of the HAS OBS CONTEXT relationship) sets the Observation Context of their parent node Content Item. Observation Context is encoded in the same manner as any other Content Item. + The Observation Context applies to all the by-value descendant nodes of that parent node regardless of the relationship type between the parent and the descendant nodes, until and unless the context of a descendant node is reset by other Observation Context Content Items. Observation Context shall not be inherited across by-reference relationships. The four dimensions of Observation Context (observer context, quotation mode, procedure context, and subject context) may be reset independently; e.g., resetting the subject context does not reset the observer or procedure context, or the quotation mode. See the example in . + + For example, the "subject context" may be defined by attaching an appropriate Content Item to the root node with a HAS OBS CONTEXT relationship. This "subject context" then applies not only to the root node, but to all its descendants, until such time as a Content Item explicitly replaces the "subject context" attribute, the new value of which is then inherited by all of that nodes descendants. + + Observation DateTime is not included as part of the HAS OBS CONTEXT relationship, and therefore is not inherited along with other Observation Context. The Observation DateTime Attribute is included in each Content Item, which allows different observation dates and times to be attached to different Content Items. + The IOD may specify restrictions on Content Items and Relationship Types that also constrain the flexibility with which Observation Context may be described. + The IOD may specify Templates that offer or restrict patterns and content in Observation Context. + + + + Node 2 inherits any Observation Context of Node 1, which is then extended or replaced by the additional Observation Context defined in Nodes C1 and C2 (that is C1 and C2 are properties of 2). + + + Node 3 and its descendents inherit the Observation Context of Node 2, which includes C1 and C2. + + + Node 4 inherits the Observation Context of Node 2, which includes C1 and C2. + + + + +
+ Definition and Inheritance of Observation Context (Informative) + + + + + +
+ +
+
+ Key Object Selection Modules +
+ Key Object Document Series Module + + defines the Attributes of the Key Object Document Series. + + Series of Key Object Selection Documents are separate from Series of Images or other Composite SOP Instances. Key Object Documents do not reside in a Series of Images or other Composite SOP Instances. + + + + + + + + + + + + - + + - + + - - + + + + + + + + + + +
Key Object Document Series Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
- - >>Include - - + + Modality + + (0008,0060) + + 1 - + Type of device, process or method that created the Instances in this Series. + + Enumerated Values: + + KO + + Key Object Selection + + +
- >Accession Number + Series Instance UID - (0008,0050) + (0020,000E) - 2 + 1 - A departmental Information System generated number that identifies the Imaging Service Request. + Unique identifier of the Series. + + No specific semantics are specified. +
- >Issuer of Accession Number Sequence + Series Number - (0008,0051) + (0020,0011) - 3 + 1 - Identifier of the Assigning Authority that issued the Accession Number. - Only a single Item is permitted in this Sequence. + A number that identifies the Series. + + No specific semantics are specified. +
- - >>Include - - + + Series Date + + (0008,0021) + + 3 - + Date the Series started.
- >Placer Order Number / Imaging Service Request + Series Time - (0040,2016) + (0008,0031) - 2 + 3 - The order number assigned to the Imaging Service Request by the party placing the order. + Time the Series started.
- >Order Placer Identifier Sequence + Protocol Name - (0040,0026) + (0018,1030) - 3 + 3 - Identifier of the Assigning Authority that issued the Placer Order Number. - Only a single Item is permitted in this Sequence. + Description of the conditions under which the Series was performed. + + This may represent the type of analysis used in creation of the KO SOP Instances. +
- - >>Include - - - - + Series Description
+ (0008,103E) + + 3 + + Description of the Series. +
- >Filler Order Number / Imaging Service Request + Series Description Code Sequence - (0040,2017) + (0008,103F) - 2 + 3 + + A coded description of the Series. + Only a single Item is permitted in this Sequence. +
+ + >Include + + - The order number assigned to the Imaging Service Request by the party filling the order. + + No Baseline CID is defined. +
- >Order Filler Identifier Sequence + Referenced Performed Procedure Step Sequence - (0040,0027) + (0008,1111) - 3 + 2 - Identifier of the Assigning Authority that issued the Filler Order Number. - Only a single Item is permitted in this Sequence. + Uniquely identifies the Performed Procedure Step SOP Instance for which the Series is created. + Zero or one Item shall be included in this Sequence. + + See notes on this Attribute in + +
- - >>Include + + >Include - + +
+
+
+ Key Object Document Module + + specifies the Attributes of a Key Object Selection Document. These Attributes identify and provide context for the Key Object Selection Document. + + + + + + + + + + + + + + + + - @@ -246874,11 +250072,8 @@ 1 @@ -246936,13 +250131,10 @@ Content Macros
Numeric Measurement Macro - - specifies the Attributes that convey a NUM (numeric measurement) value. + + specifies the Attributes of the , which convey a NUM (numeric measurement) value. - The Measured Value Sequence (0040,A300) may be empty to convey the concept of a measurement whose value is unknown or missing, or a measurement or calculation failure. - Whether or not an Item is required may be controlled by the Template that defines the use of this Content Item. - See PS3.16 . - If the Sequence is empty, neither the value nor the units will be sent. + The Measured Value Sequence (0040,A300) may be empty to convey the concept of a measurement whose value is unknown or missing, or a measurement or calculation failure. Whether or not an Item is required may be controlled by the Template that defines the use of this Content Item. See . If the Sequence is empty, neither the value nor the units will be sent.
Key Object Document Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Instance Number + + (0020,0013) + + 1 + + A number that identifies the Document.
- >Requested Procedure ID + Content Date - (0040,1001) + (0008,0023) - 2 + 1 - Identifier of the related Requested Procedure + The date the document content creation started.
- >Requested Procedure Description + Content Time - (0032,1060) + (0008,0033) - 2 + 1 - Institution-generated administrative description or classification of Requested Procedure. + The time the document content creation started.
- >Requested Procedure Code Sequence + Referenced Request Sequence - (0032,1064) + (0040,A370) - 2 + 1C - A Sequence that conveys the requested procedure. - Zero or one Item shall be included in this Sequence. + Identifies Requested Procedures to which this Document pertains. + One or more Items shall be included in this Sequence. + Required if this Document pertains to at least one Requested Procedure.
- - >>Include + + >Include - - No Baseline CID is defined. - + +
- List of all Composite SOP Instances referenced in Content Sequence (0040,A730), including all presentation states, real world value maps and other accompanying Composite Instances that are referenced from the Content Items. + List of all Composite SOP Instances referenced in the Content Sequence (0040,A730). The current evidence is considered to be only the set of Instances referenced within the Key Object Selection. One or more Items shall be included in this Sequence. - - In the context of the Key Object Selection, the current evidence is considered to be only the set of Instances referenced within the Key Object Selection. -
@@ -247101,8 +250293,8 @@
Code Macro - - specifies the Attributes that convey a CODE value. + + specifies the Attributes of the , which convey a CODE value.
Numeric Measurement Macro Attributes
@@ -247155,12 +250347,12 @@
Composite Object Reference Macro - - specifies the Attributes that convey a reference to a DICOM Composite Object that is not a DICOM Image or Waveform (such as an SR Document), or to an HL7 Structured Document. + + specifies the Attributes of the , which convey a reference to a DICOM Composite Object that is not a DICOM Image or Waveform (such as an SR Document), or to an HL7 Structured Document. - If a Softcopy Presentation State is to be applied to an Image, it should be referenced by an Image Reference Macro. + If a Softcopy Presentation State is to be applied to an Image, it should be referenced by an . Other SR Documents may be referenced by this Macro, but there is no facility to reference individual Content Items within those reports. @@ -247220,8 +250412,8 @@
Image Reference Macro - - specifies the Attributes that convey a reference to a DICOM image. + + specifies the Attributes of the , which convey a reference to a DICOM image.
Code Macro Attributes
@@ -247371,8 +250563,8 @@
Waveform Reference Macro - - specifies the Attributes that convey a reference to a DICOM waveform. + + specifies the Attributes of the , which convey a reference to a DICOM waveform.
Image Reference Macro Attributes
@@ -247435,8 +250627,8 @@
Spatial Coordinates Macro - - specifies the Attributes that convey Spatial Coordinates in an SCOORD Content Item. An SCOORD Content Item shall always be the Source Content Item of one or more SELECTED FROM Relationships with IMAGE Target Content Items. Each IMAGE Target Content Item shall contain a reference to one single-frame or multi-frame Image. + + specifies the Attributes of the , which convey Spatial Coordinates in an SCOORD Content Item. An SCOORD Content Item shall always be the Source Content Item of one or more SELECTED FROM Relationships with IMAGE Target Content Items. Each IMAGE Target Content Item shall contain a reference to one single-frame or multi-frame Image. The same set of spatial coordinates may be selected from more than one single-frame image, or more than one frame of a multi-frame image when the purpose of reference is applicable to multiple images. For example, the spatial coordinates may specify the outline of a sampling region at the same spatial location on multiple images acquired over time. @@ -247598,8 +250790,8 @@
Temporal Coordinates Macro - - specifies the Attributes that convey TCOORD Content Items. A TCOORD Content Item shall be the Source Content Item of one or more SELECTED FROM relationships with one or more SCOORD Content Items, one or more IMAGE Content Items, or one or more WAVEFORM Content Items. + + specifies the Attributes of the , which convey TCOORD Content Items. A TCOORD Content Item shall be the Source Content Item of one or more SELECTED FROM relationships with one or more SCOORD Content Items, one or more IMAGE Content Items, or one or more WAVEFORM Content Items. @@ -247740,8 +250932,8 @@
Container Macro - - specifies the Attributes that convey a CONTAINER Content Item. + + specifies the Attributes of the , which convey a CONTAINER Content Item.
Waveform Reference Macro Attributes
@@ -247896,8 +251088,8 @@
3D Spatial Coordinates Macro - - specifies the Attributes that convey 3D Spatial Coordinates in an SCOORD3D Content Item. + + specifies the Attributes of the , which convey 3D Spatial Coordinates in an SCOORD3D Content Item.
Container Macro Attributes
@@ -248058,781 +251250,778 @@
Table Content Item Macro - - specifies the Attributes that convey a TABLE (two-dimensional tabulated data) Content Item value. - A TABLE consists of a rectangular array of row and column values, which may be of the same or different Value Representation, and be associated with coded row and column descriptions, and units for numeric values when required. - Cell values may be specified individually or as complete row or column lists of values in single Attributes. - The values may be described completely or sparsely (i.e., empty cells are permitted) + + specifies the Attributes of the , which convey a TABLE (two-dimensional tabulated data) Content Item value. + A TABLE consists of a rectangular array of row and column values, which may be of the same or different Value Representation, and be associated with coded row and column descriptions, and units for numeric values when required. Cell values may be specified individually or as complete row or column lists of values in single Attributes. The values may be described completely or sparsely (i.e., empty cells are permitted)
3D Spatial Coordinates Macro Attributes
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Table Content Item Macro Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- Tabulated Values Sequence - - (0040,A801) - - 1 - - This is the table that represents the value of the Content Item. - Shall consist of a single Item whose Attributes convey the cell value(s), which represent rows and columns consisting of text, codes, integers, real numbers or DateTimes. - Only a single Item shall be included in this Sequence. -
- >Number of Table Rows - - (0040,A802) - - 1 - - The number of rows in this table. -
- >Number of Table Columns - - (0040,A803) - - 1 - - The number of columns in this table. -
- >Table Row Definition Sequence - - (0040,A806) - - 3 - - The concepts that define the meaning of the rows of the table. - One or more Items are permitted in this Sequence. - If a single Item is present, then the concept applies to all the rows. - Not all rows need to be described. - Items of this Sequence shall be sorted by Table Row Number. - See . -
- >>Table Row Number - - (0040,A804) - - 1C - - The row, numbered from 1, of the table that this concept describes. - Required if the concept does not apply to all rows. -
- >>Concept Name Code Sequence - - (0040,A043) - - 1 - - The concept that describes the meaning of the row(s). - Only a single Item shall be included in this Sequence. -
- - >>>Include - - - - - No Baseline CID is defined. - -
- >>Measurement Units Code Sequence - - (0040,08EA) - - 1C - - Units of measurement that apply to all the numeric values in this row. - Only a single Item shall be included in this Sequence. - Required if all the columns in this row are numeric values (Selector Attribute VR is DS, FD, FL, IS, SL, SS, UL, or US), have units (are not dimensionless), and have the same units. -
- - >>>Include - - - - - D. - -
- >Table Column Definition Sequence - - (0040,A807) - - 3 - - The concepts that define the meaning of the columns of the table. - One or more Items are permitted in this Sequence. - Not all columns need to be described. - If a single Item is present, then the concept applies to all the columns. - Items of this Sequence shall be sorted by Table Column Number. - See . -
- >>Table Column Number - - (0040,A805) - - 1C - - The column, numbered from 1, of the table that this concept describes. - Required if the concept does not apply to all columns. -
- >>Concept Name Code Sequence - - (0040,A043) - - 1 - - The concept that describes the meaning of the column(s). - Only a single Item shall be included in this Sequence. -
- - >>>Include - - - - - No Baseline CID is defined. - -
- >>Measurement Units Code Sequence - - (0040,08EA) - - 1C - - Units of measurement that apply to all the numeric values in this column. - Only a single Item shall be included in this Sequence. - Required if all the rows in this column are numeric values (Selector Attribute VR is DS, FD, FL, IS, SL, SS, UL, or US), have units (are not dimensionless), and have the same units. -
- - >>>Include - - - - - D. - -
- >Cell Values Sequence - - (0040,A808) - - 1 - - The values of each populated cell in the table, identified by row and column. - One or more Items shall be included in this Sequence. - The table may be sparse (i.e., not every cell is required to be populated). - Entire rows may be specified in a single Item if all the columns have the same VR. - Entire columns may be specified in a single Item if all the rows have the same VR. - Items of this Sequence shall be in row-major order, then sorted by column. - See . -
- >>Table Row Number - - (0040,A804) - - 1C - - The row, numbered from 1, of the table. - Required if Table Column Number is absent, or all the rows for the column specified in Table Column Number are not encoded in a single Attribute (containing multiple values) in this Item (i.e., with a single VR). -
- >>Table Column Number - - (0040,A805) - - 1C - - The column, numbered from 1, of the table. - Required if Table Row Number is absent, or all the columns for the row specified in Table Row Number are not encoded in a single Attribute (containing multiple values) in this Item (i.e., with a single VR). -
- >>Referenced Content Item Identifier - - (0040,DB73) - - 1C - - An ordered set of one or more integers that uniquely identifies the Content Item that is the value for this cell. - See . - Required if Selector Attribute VR (0072,0050) is not present. -
- >>Selector Attribute VR - - (0072,0050) - - 1C - - Value Representation of the value(s) of the cell(s) in this Item. - Required if Referenced Content Item Identifier (0040,DB73) is not present. - - Enumerated Values: - - DS - - - - - - DT - - - - - - FD - - - - - - FL - - - - - - IS - - - - - - SL - - - - - - SQ - - - - - - SS - - - - - - SV - - - - - - UC - - - - - - UL - - - - - - US - - - - - - UV - - - - - - - - - Only a subset of the possible VRs (value in the VR column of Table 6-1 in PS3.6) is permitted. - - - The value SQ is a special case, in that it is used to specify that the value is Code Sequence Attribute, rather than any other type of Sequence. - - - -
- >>Selector DS Value - - (0072,0072) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is DS, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector DT Value - - (0072,0063) - - 1C - - The DateTime value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is DT. -
- >>Selector FD Value - - (0072,0074) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is FD, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector FL Value - - (0072,0076) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is FL, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector IS Value - - (0072,0064) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is IS, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector SL Value - - (0072,007C) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is SL, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector SS Value - - (0072,007E) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is SS, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector SV Value - - (0072,0082) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is SV, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector UC Value - - (0072,006F) - - 1C - - The text value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is UC. -
- >>Selector UL Value - - (0072,0078) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is UL, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector US Value - - (0072,007A) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is US, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Selector UV Value - - (0072,0083) - - 1C - - The numeric value(s) of the cell(s) in this Item. - Required if Selector Attribute VR (0072,0050) is present and the value is UV, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. -
- >>Concept Code Sequence - - (0040,A168) - - 1C - - The coded value(s) of the cell(s) in this Item. - One or more Items shall be included in this Sequence. - Required if Selector Attribute VR (0072,0050) is present and the value is SQ. -
- - >>>Include - - - - - No Baseline CID is defined. - -
- >>Measurement Units Code Sequence - - (0040,08EA) - - 1C - - Units of measurement that apply to all the numeric value in this cell. - Only a single Item shall be included in this Sequence. - Required if this cell is a numeric value (Selector Attribute VR is DS, FD, FL, IS, SL, SS, SV, UL, US or UV) has a unit (is not dimensionless), and the unit is not specified within the Table Row Definition Sequence for this row or Table Column Definition Sequence for this column. -
- - >>>Include - - - - - D. - -
- >>Numeric Value Qualifier Code Sequence - - (0040,A301) - - 1C - - The reason for the absence of the numeric value. - Only a single Item is permitted in this Sequence. - Required if this cell is a numeric value (Selector Attribute VR is DS, FD, FL, IS, SL, SS, SV, UL, US or UV), and the numeric value cannot be provided. -
- - >>>Include - - - - - D. - -
+
Table Content Item Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Tabulated Values Sequence + + (0040,A801) + + 1 + + This is the table that represents the value of the Content Item. + Shall consist of a single Item whose Attributes convey the cell value(s), which represent rows and columns consisting of text, codes, integers, real numbers or DateTimes. + Only a single Item shall be included in this Sequence. +
+ >Number of Table Rows + + (0040,A802) + + 1 + + The number of rows in this table. +
+ >Number of Table Columns + + (0040,A803) + + 1 + + The number of columns in this table. +
+ >Table Row Definition Sequence + + (0040,A806) + + 3 + + The concepts that define the meaning of the rows of the table. + One or more Items are permitted in this Sequence. + If a single Item is present, then the concept applies to all the rows. + Not all rows need to be described. + Items of this Sequence shall be sorted by Table Row Number. + See . +
+ >>Table Row Number + + (0040,A804) + + 1C + + The row, numbered from 1, of the table that this concept describes. + Required if the concept does not apply to all rows. +
+ >>Concept Name Code Sequence + + (0040,A043) + + 1 + + The concept that describes the meaning of the row(s). + Only a single Item shall be included in this Sequence. +
+ + >>>Include + + + + + No Baseline CID is defined. + +
+ >>Measurement Units Code Sequence + + (0040,08EA) + + 1C + + Units of measurement that apply to all the numeric values in this row. + Only a single Item shall be included in this Sequence. + Required if all the columns in this row are numeric values (Selector Attribute VR is DS, FD, FL, IS, SL, SS, UL, or US), have units (are not dimensionless), and have the same units. +
+ + >>>Include + + + + + D. + +
+ >Table Column Definition Sequence + + (0040,A807) + + 3 + + The concepts that define the meaning of the columns of the table. + One or more Items are permitted in this Sequence. + Not all columns need to be described. + If a single Item is present, then the concept applies to all the columns. + Items of this Sequence shall be sorted by Table Column Number. + See . +
+ >>Table Column Number + + (0040,A805) + + 1C + + The column, numbered from 1, of the table that this concept describes. + Required if the concept does not apply to all columns. +
+ >>Concept Name Code Sequence + + (0040,A043) + + 1 + + The concept that describes the meaning of the column(s). + Only a single Item shall be included in this Sequence. +
+ + >>>Include + + + + + No Baseline CID is defined. + +
+ >>Measurement Units Code Sequence + + (0040,08EA) + + 1C + + Units of measurement that apply to all the numeric values in this column. + Only a single Item shall be included in this Sequence. + Required if all the rows in this column are numeric values (Selector Attribute VR is DS, FD, FL, IS, SL, SS, UL, or US), have units (are not dimensionless), and have the same units. +
+ + >>>Include + + + + + D. + +
+ >Cell Values Sequence + + (0040,A808) + + 1 + + The values of each populated cell in the table, identified by row and column. + One or more Items shall be included in this Sequence. + The table may be sparse (i.e., not every cell is required to be populated). + Entire rows may be specified in a single Item if all the columns have the same VR. + Entire columns may be specified in a single Item if all the rows have the same VR. + Items of this Sequence shall be in row-major order, then sorted by column. + See . +
+ >>Table Row Number + + (0040,A804) + + 1C + + The row, numbered from 1, of the table. + Required if Table Column Number is absent, or all the rows for the column specified in Table Column Number are not encoded in a single Attribute (containing multiple values) in this Item (i.e., with a single VR). +
+ >>Table Column Number + + (0040,A805) + + 1C + + The column, numbered from 1, of the table. + Required if Table Row Number is absent, or all the columns for the row specified in Table Row Number are not encoded in a single Attribute (containing multiple values) in this Item (i.e., with a single VR). +
+ >>Referenced Content Item Identifier + + (0040,DB73) + + 1C + + An ordered set of one or more integers that uniquely identifies the Content Item that is the value for this cell. + See . + Required if Selector Attribute VR (0072,0050) is not present. +
+ >>Selector Attribute VR + + (0072,0050) + + 1C + + Value Representation of the value(s) of the cell(s) in this Item. + Required if Referenced Content Item Identifier (0040,DB73) is not present. + + Enumerated Values: + + DS + + + + + + DT + + + + + + FD + + + + + + FL + + + + + + IS + + + + + + SL + + + + + + SQ + + + + + + SS + + + + + + SV + + + + + + UC + + + + + + UL + + + + + + US + + + + + + UV + + + + + + + + + Only a subset of the possible VRs (value in the VR column of Table 6-1 in PS3.6) is permitted. + + + The value SQ is a special case, in that it is used to specify that the value is Code Sequence Attribute, rather than any other type of Sequence. + + + +
+ >>Selector DS Value + + (0072,0072) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is DS, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector DT Value + + (0072,0063) + + 1C + + The DateTime value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is DT. +
+ >>Selector FD Value + + (0072,0074) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is FD, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector FL Value + + (0072,0076) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is FL, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector IS Value + + (0072,0064) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is IS, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector SL Value + + (0072,007C) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is SL, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector SS Value + + (0072,007E) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is SS, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector SV Value + + (0072,0082) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is SV, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector UC Value + + (0072,006F) + + 1C + + The text value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is UC. +
+ >>Selector UL Value + + (0072,0078) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is UL, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector US Value + + (0072,007A) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is US, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Selector UV Value + + (0072,0083) + + 1C + + The numeric value(s) of the cell(s) in this Item. + Required if Selector Attribute VR (0072,0050) is present and the value is UV, and Numeric Value Qualifier Code Sequence (0040,A301) is not present. +
+ >>Concept Code Sequence + + (0040,A168) + + 1C + + The coded value(s) of the cell(s) in this Item. + One or more Items shall be included in this Sequence. + Required if Selector Attribute VR (0072,0050) is present and the value is SQ. +
+ + >>>Include + + + + + No Baseline CID is defined. + +
+ >>Measurement Units Code Sequence + + (0040,08EA) + + 1C + + Units of measurement that apply to all the numeric value in this cell. + Only a single Item shall be included in this Sequence. + Required if this cell is a numeric value (Selector Attribute VR is DS, FD, FL, IS, SL, SS, SV, UL, US or UV) has a unit (is not dimensionless), and the unit is not specified within the Table Row Definition Sequence for this row or Table Column Definition Sequence for this column. +
+ + >>>Include + + + + + D. + +
+ >>Numeric Value Qualifier Code Sequence + + (0040,A301) + + 1C + + The reason for the absence of the numeric value. + Only a single Item is permitted in this Sequence. + Required if this cell is a numeric value (Selector Attribute VR is DS, FD, FL, IS, SL, SS, SV, UL, US or UV), and the numeric value cannot be provided. +
+ + >>>Include + + + + + D. + +
Table Content Item Macro Attribute Descriptions
Table Row and Column Definition Sequences - The meaning of the table rows and columns are described in Items of Table Row Definition Sequence (0040,A806) and Table Column Definition Sequence (0040,A807). - A coded concept name is provided in Concept Code Sequence (0040,A168) and units, if applicable, in Measurement Units Code Sequence (0040,08EA). - For example: - - Example 1. A two-column table, consisting of multiple rows describing forty values of datetime and X-Ray tube current, could be described as follows: - - Concept Name Code Sequence (0040,A043) = (113734, DCM, "X-Ray Tube Current") - Tabulated Values Sequence (0040,A801) - Item 1 - >Number of Table Rows (0040,A802) = 40 - >Number of Table Columns (0040,A803) = 2 - >Table Column Definition Sequence (0040,A807) - >Item 1 - >>Table Column Number (0040,A805) = 1 - >>Concept Name Code Sequence (0040,A043) = (111526, DCM, "DateTime Started") - >Item 2 - >>Table Column Number (0040,A805) = 2 - >>Concept Name Code Sequence (0040,A043) = (113734, DCM, "X-Ray Tube Current") - >>Measurement Units Code Sequence (0040,08EA) = (mA, UCUM, "mA") - - - - The same concept (113734, DCM, "X-Ray Tube Current") can be used to describe the entire table as the column of values that represent the actual values. - - - No Table Row Definition Sequence (0040,A806) is needed, since rows consist of unnamed observations. - - - No Measurement Units Code Sequence (0040,08EA) is needed for the first column, since it contains DateTimes, not numeric values. - - - + The meaning of the table rows and columns are described in Items of Table Row Definition Sequence (0040,A806) and Table Column Definition Sequence (0040,A807). A coded concept name is provided in Concept Code Sequence (0040,A168) and units, if applicable, in Measurement Units Code Sequence (0040,08EA). + For example: + + Example 1. A two-column table, consisting of multiple rows describing forty values of datetime and X-Ray tube current, could be described as follows: + + Concept Name Code Sequence (0040,A043) = (113734, DCM, "X-Ray Tube Current") + Tabulated Values Sequence (0040,A801) + Item 1 + >Number of Table Rows (0040,A802) = 40 + >Number of Table Columns (0040,A803) = 2 + >Table Column Definition Sequence (0040,A807) + >Item 1 + >>Table Column Number (0040,A805) = 1 + >>Concept Name Code Sequence (0040,A043) = (111526, DCM, "DateTime Started") + >Item 2 + >>Table Column Number (0040,A805) = 2 + >>Concept Name Code Sequence (0040,A043) = (113734, DCM, "X-Ray Tube Current") + >>Measurement Units Code Sequence (0040,08EA) = (mA, UCUM, "mA") + + + + The same concept (113734, DCM, "X-Ray Tube Current") can be used to describe the entire table as the column of values that represent the actual values. + + + No Table Row Definition Sequence (0040,A806) is needed, since rows consist of unnamed observations. + + + No Measurement Units Code Sequence (0040,08EA) is needed for the first column, since it contains DateTimes, not numeric values. + + + - - Example 2. A four by four matrix representing an affine transformation between two frames of reference could be described as: - - Concept Name Code Sequence (0040,A043) = (eRDSRX16, DCM, "X-Ray Source Transformation Matrix") - Tabulated Values Sequence (0040,A801) - Item 1 - >Number of Table Rows (0040,A802) = 4 - >Number of Table Columns (0040,A803) = 4 - - - - No Table Row Definition Sequence (0040,A806) or Table Column Definition Sequence (0040,A807) is needed, since the meaning of the rows and columns in a transformation matrix is implicit in the definition of the matrix (for example, the template using this Content Item might reference the behavior defined in ). - - - No Measurement Units Code Sequence (0040,08EA) is needed since the numeric values are dimensionless (have no units). - - - - - - Example 3. A four-column table, consisting of multiple (ten) measurements along an artery, could be described as follows: - - Concept Name Code Sequence (0040,A043) = (, , "Arterial Measurements") - Tabulated Values Sequence (0040,A801) - Item 1 - >Number of Table Rows (0040,A802) = 10 - >Number of Table Columns (0040,A803) = 4 - >Table Column Definition Sequence (0040,A807) - >Item 1 - >>Table Column Number (0040,A805) = 1 - >>Concept Name Code Sequence (0040,A043) = (, , " Distance from landmark ") - >>Measurement Units Code Sequence (0040,08EA) = (mm, UCUM, "mm") - >Item 2 - >>Table Column Number (0040,A805) = 2 - >>Concept Name Code Sequence (0040,A043) = (, , "X- Measured lumen diameter") - >>Measurement Units Code Sequence (0040,08EA) = (mm, UCUM, "mm") - >Item 3 - >>Table Column Number (0040,A805) = 3 - >>Concept Name Code Sequence (0040,A043) = (, , "Calculated lumen cross-section area") - >>Measurement Units Code Sequence (0040,08EA) = (mm2, UCUM, " mm2") - >Item 4 - >>Table Column Number (0040,A805) = 4 - >>Concept Name Code Sequence (0040,A043) = (, , "Stenosis") - >>Measurement Units Code Sequence (0040,08EA) = ([%], UCUM, " [%]") - - No Table Row Definition Sequence (0040,A806) is needed, since rows consist of unnamed observations. - + + Example 2. A four by four matrix representing an affine transformation between two frames of reference could be described as: + + Concept Name Code Sequence (0040,A043) = (eRDSRX16, DCM, "X-Ray Source Transformation Matrix") + Tabulated Values Sequence (0040,A801) + Item 1 + >Number of Table Rows (0040,A802) = 4 + >Number of Table Columns (0040,A803) = 4 + + + + No Table Row Definition Sequence (0040,A806) or Table Column Definition Sequence (0040,A807) is needed, since the meaning of the rows and columns in a transformation matrix is implicit in the definition of the matrix (for example, the template using this Content Item might reference the behavior defined in ). + + + No Measurement Units Code Sequence (0040,08EA) is needed since the numeric values are dimensionless (have no units). + + + + + + Example 3. A four-column table, consisting of multiple (ten) measurements along an artery, could be described as follows: + + Concept Name Code Sequence (0040,A043) = (, , "Arterial Measurements") + Tabulated Values Sequence (0040,A801) + Item 1 + >Number of Table Rows (0040,A802) = 10 + >Number of Table Columns (0040,A803) = 4 + >Table Column Definition Sequence (0040,A807) + >Item 1 + >>Table Column Number (0040,A805) = 1 + >>Concept Name Code Sequence (0040,A043) = (, , " Distance from landmark ") + >>Measurement Units Code Sequence (0040,08EA) = (mm, UCUM, "mm") + >Item 2 + >>Table Column Number (0040,A805) = 2 + >>Concept Name Code Sequence (0040,A043) = (, , "X- Measured lumen diameter") + >>Measurement Units Code Sequence (0040,08EA) = (mm, UCUM, "mm") + >Item 3 + >>Table Column Number (0040,A805) = 3 + >>Concept Name Code Sequence (0040,A043) = (, , "Calculated lumen cross-section area") + >>Measurement Units Code Sequence (0040,08EA) = (mm2, UCUM, " mm2") + >Item 4 + >>Table Column Number (0040,A805) = 4 + >>Concept Name Code Sequence (0040,A043) = (, , "Stenosis") + >>Measurement Units Code Sequence (0040,08EA) = ([%], UCUM, " [%]") + + No Table Row Definition Sequence (0040,A806) is needed, since rows consist of unnamed observations. +
Cell Values Sequence @@ -248905,29 +252094,20 @@
Referenced Content Item Identifier Instead of encoding a value for a cell or list of values for a row or column, a reference can be made to another Content Item. - For the structure and encoding of the Referenced Content Item Identifier (0040,DB73) Attribute, - see - and the definition of Referenced Content Item Identifier in . - The reference mechanism allows the context of a cell value to be preserved. - For example, if it is necessary to tabulate a list of measurements on regions of interest (ROIs), - then each ROI and its associated measurements, descriptive codes, segmentation references, coordinates and image references can be encoded in the Content Tree in the normal manner, - and references to the NUM Content Items that encode the measurements can be tabulated in a TABLE Content Item by using the Referenced Content Item Identifier (0040,DB73). - Other cells in the table might reference other Content Items associated with the measurements, such as a tracking identifier or target anatomy or time point identifier. - Frequently, the description of the row or column (as described in ), - will match the pre-coordinated concept name and units that describes a referenced Content Item. - E.g., the same code can be used for the Concept Name Code Sequence (0040,A043) and Measurement Units Code Sequence (0040,08EA) of the referenced NUM Content Item as for the corresponding Table Row Definition Sequence (0040,A806) or Table Column Definition Sequence (0040,A807). - However, it may be that a referenced Content Item has a relatively complex post-coordinated description defined by related parent, sibling or child Content Items, in which case a more specific code may need to be used for the Concept Name Code Sequence (0040,A043) in Table Row Definition Sequence (0040,A806) or Table Column Definition Sequence (0040,A807). + For the structure and encoding of the Referenced Content Item Identifier (0040,DB73) Attribute, see and the definition of Referenced Content Item Identifier in . + The reference mechanism allows the context of a cell value to be preserved. For example, if it is necessary to tabulate a list of measurements on regions of interest (ROIs), then each ROI and its associated measurements, descriptive codes, segmentation references, coordinates and image references can be encoded in the Content Tree in the normal manner, and references to the NUM Content Items that encode the measurements can be tabulated in a TABLE Content Item by using the Referenced Content Item Identifier (0040,DB73). Other cells in the table might reference other Content Items associated with the measurements, such as a tracking identifier or target anatomy or time point identifier. + Frequently, the description of the row or column (as described in ), will match the pre-coordinated concept name and units that describes a referenced Content Item. E.g., the same code can be used for the Concept Name Code Sequence (0040,A043) and Measurement Units Code Sequence (0040,08EA) of the referenced NUM Content Item as for the corresponding Table Row Definition Sequence (0040,A806) or Table Column Definition Sequence (0040,A807). However, it may be that a referenced Content Item has a relatively complex post-coordinated description defined by related parent, sibling or child Content Items, in which case a more specific code may need to be used for the Concept Name Code Sequence (0040,A043) in Table Row Definition Sequence (0040,A806) or Table Column Definition Sequence (0040,A807).
-
+
Raw Data Specific Modules The following Modules are used by the Raw Data IOD.
Raw Data Module - - specifies the Attributes that describe a raw data stream. + + specifies the Attributes of the , which describe a raw data stream. @@ -249002,7 +252182,7 @@ @@ -249183,16 +252363,16 @@
Raw Data Module Attributes
The date and time that the acquisition of data started. - The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800). + The synchronization of this time with an external clock is specified in the in Acquisition Time Synchronized (0018,1800).
Raw Data - The Raw Data stored with the Raw Data Module consists of one or more Private Attributes that are vendor specific. No rules are specified about the content and format of the raw data. + The Raw Data stored with the consists of one or more Private Attributes that are vendor specific. No rules are specified about the content and format of the raw data.
Spatial Registration
- Spatial Registration Series Module + Spatial Registration Series Module - defines the general Attributes of the Spatial Registration Series Module. + specifies the Attributes of the . @@ -249239,9 +252419,9 @@
Spatial Registration Series Module Attributes
- Spatial Registration Module + Spatial Registration Module - defines the general Attributes of the Spatial Registration Module. + specifies the Attributes of the . @@ -249504,7 +252684,7 @@ @@ -249544,7 +252724,7 @@ @@ -249561,10 +252741,50 @@ Uniquely identifies the segment described in Segment Sequence (0062,0002) by reference to Segment Number (0062,0004). Referenced Segment Number (0062,000B) shall not be multi-valued. + + + + + + + + + + + + + + + +
Spatial Registration Module Attributes
- Reference to the Spatial Fiducial SOP Instance identifying the Used Fiducial(s) + Reference to the Spatial Fiducial SOP Instance identifying the used Fiducial(s).
- Reference to the Segmentation or Surface Segmentation SOP Instance identifying the Used Segments. + Reference to the Segmentation or Surface Segmentation SOP Instance identifying the used Segments.
+ >Used RT Structure Set ROI Sequence Sequence + + (0070,0315) + + 3 + + The ROIs defined in an RT Structure Set Instance used to determine the Frame of Reference Transformation Matrix. + One or more Items are permitted in this Sequence. +
+ + >>Include + + + + Reference to the RT Structure Set SOP Instance identifying the used ROIs. +
+ >>Referenced ROI Number + + (3006,0084) + + 1 + + Uniquely identifies the ROI described in the Structure Set ROI Sequence (3006,0020) by reference to ROI Number (3006,0022). +
- Registration Module Attribute Descriptions + Spatial Registration Module Attribute Descriptions
Frame of Reference Transformation Matrix The Frame of Reference Transformation Matrix (3006,00C6) AMB describes how to transform a point (Bx,By,Bz) with respect to RCSB into (Ax,Ay,Az) with respect to RCSA according to . @@ -250134,9 +253354,9 @@
- Deformable Spatial Registration Module + Deformable Spatial Registration Module - defines the general Attributes of the Deformable Spatial Registration Module. + specifies the Attributes of the . @@ -250536,7 +253756,7 @@ @@ -251396,9 +254616,9 @@
Spatial Fiducials
- Spatial Fiducials Series Module + Spatial Fiducials Series Module - defines the general Attributes of the Spatial Fiducials Series Module. + specifies the Attributes of the .
Deformable Spatial Registration Module Attributes
- Reference to the Spatial Fiducial SOP Instance identifying the Used Fiducial(s) + Reference to the Spatial Fiducial SOP Instance identifying the used Fiducial(s).
@@ -251447,7 +254667,7 @@
Spatial Fiducials Module - defines the general Attributes of the Registration. + specifies the Attributes of the Registration.
Spatial Fiducials Series Module Attributes
@@ -251604,7 +254824,7 @@ @@ -252252,7 +255472,7 @@ (0008,1199) @@ -252311,7 +255531,7 @@ @@ -252713,8 +255933,8 @@ The following Sections specify Modules used for Hanging Protocols.
Hanging Protocol Definition Module - - specifies the Attributes that describe and identify the high level definition of a Hanging Protocol, including its overall purpose, and the types of image sets to which it applies. See for further explanation. + + specifies the Attributes of the , which identify and describe the high level definition of a Hanging Protocol, including its overall purpose, and the types of image sets to which it applies. See for further explanation.
Spatial Fiducials Module Attributes
Sequence defining the general category of the property the fiducial represents. - Only a single Item is permitted in this Sequence + Only a single Item is permitted in this Sequence.
- A Sequence of Items where each Item references a single SOP Instance, the Media Application Profile to be used, and, where applicable, the icon representing the referenced image + A Sequence of Items where each Item references a single SOP Instance, the Media Application Profile to be used, and, where applicable, the icon representing the referenced image.
Execution status of a request. - See for Enumerated Values + See for Enumerated Values.
@@ -252958,7 +256178,7 @@ @@ -253429,7 +256649,7 @@
Hanging Protocol Definition Module Attributes
- No Baseline CID is defined. + B.
- Attribute Descriptions + Hanging Protocol Definition Module Attribute Descriptions
Hanging Protocol Definition Sequence Attributes The Hanging Protocol Definition Sequence (0072,000C) provides a collection of one or more Items that defines the intent for the Hanging Protocol with respect to modality, anatomy, laterality, procedure and/or reason. @@ -253444,10 +256664,9 @@ Procedure Code Sequence (0008,1032): - SNOMED codes - - - ICD-10-PCS Procedure Codes + + + Local Codes @@ -253514,11 +256733,11 @@ Image Set Selector Sequence Attributes The Image Set Selector Sequence (0072,0022) contains Items that specify the DICOM Attribute Data Element Tags and values that shall be used to identify the image or other object set. The Image Set Selector Usage Flag (0072,0024) indicates whether the Attribute identified by Selector Attribute (0072,0026) causes matching to succeed or fail if the Attribute is not available in an image object. - Within an Item, Selector Attribute (0072,0026) identifies a DICOM Attribute Data Element Tag that is likely to be present in image or other object Instances that are desired for the Image Set. If it is a multi-valued Attribute, the Selector Value Number (0072,0028) indicates which value is intended to be used for matching. The Selector Attribute VR (0072,0050) identifies the Value Representation of Selector Attribute (0072,0026). The value of Selector Attribute VR (0072,0050) determines which Attribute of the Hanging Protocol Selector Attribute Value Macro is required to specify one or more desired values for the DICOM Attribute. If more than one value is specified for the Attribute, or more than one Item is specified in the Selector Code Sequence Value (0072,0080), then image object Instances with a corresponding Attribute that matches any one of the values shall be included in the Image Set. + Within an Item, Selector Attribute (0072,0026) identifies a DICOM Attribute Data Element Tag that is likely to be present in image or other object Instances that are desired for the Image Set. If it is a multi-valued Attribute, the Selector Value Number (0072,0028) indicates which value is intended to be used for matching. The Selector Attribute VR (0072,0050) identifies the Value Representation of Selector Attribute (0072,0026). The value of Selector Attribute VR (0072,0050) determines which Attribute of the is required to specify one or more desired values for the DICOM Attribute. If more than one value is specified for the Attribute, or more than one Item is specified in the Selector Code Sequence Value (0072,0080), then image object Instances with a corresponding Attribute that matches any one of the values shall be included in the Image Set. The values used for Selector Attribute (0072,0026) are intended to identify a type of image set via the general categories of modality, anatomy, procedure intent and/or reason. Therefore the values of the Attributes represented by Selector Attribute (0072,0026) are likely to be coded terms, Enumerated Values, Defined Terms or free text. The use of free text Attributes is less desirable, because their values are less predictable for matching. - In an image object, some Attributes occur at the top level, or nested within a Sequence or Functional Group Sequence, or both. In addition, a Private Attribute may be identified as a Selector Attribute (0072,0026). The Attributes of the Hanging Protocol Selector Attribute Context Macro identify a Sequence, Functional Group Sequence, or Private Group context for Selector Attribute (0072,0026). + In an image object, some Attributes occur at the top level, or nested within a Sequence or Functional Group Sequence, or both. In addition, a Private Attribute may be identified as a Selector Attribute (0072,0026). The Attributes of the identify a Sequence, Functional Group Sequence, or Private Group context for Selector Attribute (0072,0026). The creator of a Hanging Protocol Instance uses this collection of Attributes to identify one type of image set to which the Hanging Protocol is intended to apply. The user of a Hanging Protocol Instance (e.g., softcopy review workstation or pre-fetching application) uses this collection of Attributes to match a specific image set to a Hanging Protocol, and/or to determine which image sets need to be retrieved in order to use a Hanging Protocol Instance. The Key Attributes to match against to obtain image sets are specified in Selector Attribute (0072,0026) and its context in each Sequence Item. If the value of the Attribute represented by Selector Attribute (0072,0026) contains a free text description (i.e., Selector Attribute VR = LO, SH, ST, LT, UT), whether exact or partial matching is used to identify a specific Image Instance when applying a Hanging Protocol Instance is implementation dependent.
@@ -253526,8 +256745,8 @@
Hanging Protocol Environment Module - - specifies the Attributes that describe and identify the best suited display environment for a Hanging Protocol. + + specifies the Attributes of the , which identify and describe the best suited display environment for a Hanging Protocol. Different viewing styles and interactions may be defined depending on a workstation's capabilities. For example, the hanging preferences for viewing a screening mammogram Study on a 1Kx1K screen with a 10 second repaint time versus a 2Kx2.5K screen may differ. @@ -253720,7 +256939,7 @@
- Hanging Protocol Environment Attribute Descriptions + Hanging Protocol Environment Module Attribute Descriptions
Display Environment Spatial Position For the Display Environment Spatial Position (0072,0108) Attribute, the lower left corner of the overall bounding box has Cartesian coordinates of (0.0,0.0). The upper right corner has coordinates of (1.0,1.0). The scale of the box is based on the Number of Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106), not the physical size of the screens that are part of the workstation. The coordinates of each individual screen's box are defined in absolute coordinates relative to the (0,0) and (1,1) range of the overall box. Position of a box is given by a (x1,y1), (x2,y2) pair that identifies the upper left corner and lower right corner if the box is rectangular. @@ -253744,8 +256963,8 @@
Hanging Protocol Display Module - - specifies the Attributes that describe operations (filter, reformat, sort, presentation intent), layout and interactions for a Hanging Protocol. See for further explanation. + + specifies the Attributes of the , which describe operations (filter, reformat, sort, presentation intent), layout and interactions for a Hanging Protocol. See for further explanation. @@ -254333,7 +257552,7 @@ 1C
Hanging Protocol Display Module Attributes
- Operation to be applied between the value(s) in the Hanging Protocol Selector Attribute Value Macro ("selector"), and the value(s) of the Attribute identified by Selector Attribute (0072,0026) (or the value implied by the Filter-by Category (0072,0402)) in each image of the Image Set. See . + Operation to be applied between the value(s) in the ("selector"), and the value(s) of the Attribute identified by Selector Attribute (0072,0026) (or the value implied by the Filter-by Category (0072,0402)) in each image of the Image Set. See . Required if Filter-by Category (0072,0402) is present, or if Selector Attribute (0072,0026) is present and Filter-by Attribute Presence (0072,0404) is not present. Enumerated Values: @@ -255178,7 +258397,7 @@
- Attribute Descriptions + Hanging Protocol Display Module Attribute Descriptions The Attributes of a Display Sets Sequence (0072,0200) Item shall be applied to the image set represented by the value of Image Set Number (0072,0032) in the following order: @@ -255359,7 +258578,7 @@ - An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026). The Image Set Selector Usage Flag (0072,0024) specifies whether or not the image is included in the filter output when the Attribute or value identified by Selector Attribute (0072,0026) is not available in an image. The Attributes of the Hanging Protocol Selector Attribute Context Macro specify whether Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence, or Private Group. + An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026). The Image Set Selector Usage Flag (0072,0024) specifies whether or not the image is included in the filter output when the Attribute or value identified by Selector Attribute (0072,0026) is not available in an image. The Attributes of the specify whether Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence, or Private Group. @@ -255536,7 +258755,7 @@ When the Sort-by Category (0072,0602) is used with a value of ALONG_AXIS, such as for CT, MR or other cross-sectional image sets, the sorting operation is computed from the values Image Position (Patient) (0020,0032) and Image Orientation (Patient) (0020,0037) in the image objects. For the image set to be displayed, a "dominant axis" of the set shall be determined. The dominant axis is the normal to Image Orientation (Patient) (0020,0037) (assuming all selected images are parallel), computed as the dot product in a right-handed coordinate system (see ). The INCREASING direction for ALONG_AXIS of the image set shall be in the positive direction along the dominant axis. The DECREASING direction shall be in the negative direction along that axis. When the Sort-by Category (0072,0602) is used with a value of BY_ACQ_TIME, the sorting operation is computed from appropriate values in the image objects (e.g., Frame Acquisition DateTime, Acquisition Time, Content Time, Acquisition DateTime), since the specific Attribute used may vary from one Image Instance or SOP Class to another, yet the Hanging Protocol Instance may be generally applicable. - An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026), provided that it is present in the referenced Image Set. The Attributes of the Hanging Protocol Selector Attribute Context Macro specify whether Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence or Private Group. + An application that is applying a Hanging Protocol Instance shall support any value for Selector Attribute (0072,0026), provided that it is present in the referenced Image Set. The Attributes of the specify whether Selector Attribute (0072,0026) is contained in a Sequence, Functional Group Sequence or Private Group. @@ -255631,9 +258850,9 @@
Hanging Protocol Selector Attribute Macros
- Hanging Protocol Selector Attribute Context Macro + Hanging Protocol Selector Attribute Context Macro - specifies the Attributes that identify the context for a Data Element Tag that is used as a Selector Attribute (0072,0026) in Image Set Selector Sequence (0072,0022), Filter Operations Sequence (0072,0400), or Sorting Operations Sequence (0072,0600). The Attribute may be an Attribute nested within a Sequence or Functional Group Sequence, and/or a Private Attribute. + specifies the Attributes of the , which identify the context for a Data Element Tag that is used as a Selector Attribute (0072,0026) in Image Set Selector Sequence (0072,0022), Filter Operations Sequence (0072,0400), or Sorting Operations Sequence (0072,0600). The Attribute may be an Attribute nested within a Sequence or Functional Group Sequence, and/or a Private Attribute. @@ -255746,9 +258965,9 @@
- Hanging Protocol Selector Attribute Value Macro + Hanging Protocol Selector Attribute Value Macro - specifies the Attributes that identify the value(s) for a Data Element Tag that is used as a Selector Attribute (0072,0026) in the Image Set Selector Sequence (0072,0022) or Filter Operations Sequence (0072,0400). + specifies the Attributes of the , which identify the value(s) for a Data Element Tag that is used as a Selector Attribute (0072,0026) in the Image Set Selector Sequence (0072,0022) or Filter Operations Sequence (0072,0400).
Hanging Protocol Selector Attribute Context Macro Attributes
@@ -256222,7 +259441,7 @@ 3 @@ -256494,7 +259713,7 @@ One or more Items shall be included in this Sequence.Required if derived from one or more DICOM Instances. May be present otherwise. - Unlike other uses of Source Instance Sequence (0042,0013), such as in the General Reference Module, references to images are permitted in this Module. This Module does not include the Source Image Sequence (0008,2112). The Defined Context Group for Purpose of Reference Code Sequence (0040,A170) includes an appropriate concept. + Unlike other uses of Source Instance Sequence (0042,0013), such as in the , references to images are permitted in this Module. This Module does not include the Source Image Sequence (0008,2112). The Defined Context Group for Purpose of Reference Code Sequence (0040,A170) includes an appropriate concept. @@ -256767,8 +259986,7 @@ @@ -256884,7 +260102,7 @@ - Required if Content Sequence (0040,A730) is present + Required if Content Sequence (0040,A730) is present. @@ -257208,9 +260426,9 @@
Real World Value Mapping Modules
- Real World Value Mapping Series Module + Real World Value Mapping Series Module - defines the general Attributes of the Real World Value Mapping Series Module. + specifies the Attributes of the .
Hanging Protocol Selector Attribute Value Macro Attributes
- Description of the Series + Description of the Series.
- Purpose of Reference Code Sequence in the Hierarchical SOP Instance Reference Macro D if Modality (0008,0060) is M3D; - otherwise, D. + Purpose of Reference Code Sequence in the Hierarchical SOP Instance Reference Macro D if Modality (0008,0060) is M3D; otherwise, D.
@@ -257257,9 +260475,9 @@
Real World Value Mapping Series Module Attributes
- Real World Value Mapping Module + Real World Value Mapping Module - defines the general Attributes of the Real World Value Mapping Module. + specifies the Attributes of the . @@ -257329,7 +260547,7 @@ 1 @@ -257343,7 +260561,7 @@ @@ -257441,7 +260659,7 @@ @@ -257555,7 +260773,7 @@ (0008,1155) @@ -257658,7 +260876,7 @@ (0044,0004) @@ -257740,7 +260958,7 @@ (0010,0010) @@ -257773,7 +260991,7 @@ (0038,0010) @@ -257843,7 +261061,7 @@ (0044,0010) @@ -257915,7 +261133,7 @@ @@ -257966,8 +261184,8 @@ This section describes the specific Modules for the Surface IE.
Surface Mesh Module - - specifies the Attributes of the Surface Mesh Module. + + specifies the Attributes of the .
Real World Value Mapping Module Attributes
- A Sequence of real world value mapping Items. Each Item defines a single mapping and a list of images to which the mapping applies. + A Sequence of Real World Value mapping Items. Each Item defines a single mapping and a list of images to which the mapping applies. One or more Items shall be included in this Sequence.
Measurement Units Code Sequence D. - +
For drugs, a coded terminology in the US is RxNorm - For devices, a coded terminology in the US is the FDA CDRH Product Code Classification + For devices, a coded terminology in the US is the FDA CDRH Product Code Classification.
- Unique identifier for the HL7 Structured Product Label Document as used in DICOM Instance references (see ) + Unique identifier for the HL7 Structured Product Label Document as used in DICOM Instance references (see ).
- Timestamp for the Substance Administration Approval response + Timestamp for the Substance Administration Approval response.
- Patient's full name + Patient's full name.
- Identification number of the Visit as assigned by the healthcare provider + Identification number of the Visit as assigned by the healthcare provider.
- Date and Time of Substance Administration + Date and Time of Substance Administration.
For administration of drugs or contrast agents, Concept Name Code Sequence B. - +
@@ -258459,8 +261677,7 @@
Recommended Presentation - Recommended Presentation Opacity (0066,000C) is a fraction between 0.0 and 1.0 encoded as a float value representing the blending proportion of the rendering of the surface relative to underlying features. - A value of 0.0 is interpreted as complete transparency, while a value of 1.0 is interpreted as fully opaque. + Recommended Presentation Opacity (0066,000C) is a fraction between 0.0 and 1.0 encoded as a float value representing the blending proportion of the rendering of the surface relative to underlying features. A value of 0.0 is interpreted as complete transparency, while a value of 1.0 is interpreted as fully opaque. The Recommended Presentation Type (0066,000D) Attribute provides guidance as to the default presentation of the Surface. Defined Terms: @@ -258547,8 +261764,8 @@
Points Macro - - specifies the Attributes of the Points Macro. + + specifies the Attributes of the .
Surface Mesh Module Attributes
@@ -258696,8 +261913,8 @@
Vectors Macro - - specifies the Attributes of the Vectors Macro. + + specifies the Attributes of the .
Points Macro Attributes
@@ -258787,8 +262004,8 @@
Surface Mesh Primitives Macro - - specifies the Attributes of the Surface Mesh Primitives Macro. + + specifies the Attributes of the .
Vectors Macro Attributes
@@ -258973,9 +262190,9 @@
Surface Mesh Primitives Macro Attributes
Surface Mesh Primitives Macro Attribute Descriptions - The Surface Mesh Primitives Macro uses 32-bit long integer point indices to reference the point rather than repeating point coordinates. All of the point coordinates used are specified within the Surface Points Sequence (0066,0011) of the same Surface Sequence (0066,0002) Item. Point indices are described in . + The uses 32-bit long integer point indices to reference the point rather than repeating point coordinates. All of the point coordinates used are specified within the Surface Points Sequence (0066,0011) of the same Surface Sequence (0066,0002) Item. Point indices are described in . - In a previous edition, other Attributes were used that had an OW VR and a limitation to no more than 65535 points per surface. These have been retired and replaced with new Attributes. See PS 3.3 2014a. + In a previous edition, other Attributes were used that had an OW VR and a limitation to no more than 65535 points per surface. These have been retired and replaced with new Attributes. See PS3.3-2014a. A Surface Mesh shall contain one or more of the following primitive types: @@ -259033,8 +262250,8 @@
Point Cloud Module - - specifies the Attributes of the Point Cloud Module. + + specifies the Attributes of the . @@ -259151,7 +262368,7 @@ @@ -259167,7 +262384,7 @@ @@ -259177,8 +262394,8 @@
UV Mapping Module - - specifies the Attributes of the UV Mapping Module. + + specifies the Attributes of the .
Point Cloud Module Attributes
Contains a vector of P-Values to assign a gray value to each point. - The number of values shall be equal to the value of Number Of Surface Points (0066,0015) in the Points Macro. + The number of values shall be equal to the value of Number Of Surface Points (0066,0015) in the . Each value shall correspond to the respective point in the Point Coordinates Data (0066,0016).
Contains a vector of color triplets to assign colors to each point. - The number of triplets shall be equal to the value of Number Of Surface Points (0066,0015) in the Points Macro. + The number of triplets shall be equal to the value of Number Of Surface Points (0066,0015) in the . The units are PCS-Values, and the value is encoded as CIELab. See . Each triplet shall correspond to the respective point in the Point Coordinates Data (0066,0016).
@@ -259213,6 +262430,21 @@ One or more Items shall be included in this Sequence. + + + + + + @@ -259310,8 +262542,8 @@ Color Palette Modules
Color Palette Definition Module - - specifies the Attributes that describe and identify a Color Palette. + + specifies the Attributes of the , which identify and describe a Color Palette.
UV Mapping Module Attributes
+ >Referenced Surface Number + + (0066,002C) + + 1C + + Identifies the Surface Number (0066,0003) of the Item in Surface Sequence (0066,0002) to which this UV Mapping applies. + Required when Surface Sequence (0066,0002) is present and contains more than one Item. +
>Texture Label @@ -259269,13 +262501,13 @@ The image that is being mapped to the point cloud or the surface mesh. - Only one Item shall be included in the Sequence. + Only a single Item shall be included in this Sequence.
- >>Include + >>Include
@@ -259345,7 +262577,7 @@
Color Palette Definition Module Attributes
- Attribute Descriptions + Color Palette Definition Module Attribute Descriptions
Content Identification Content Label (0070,0080) is intended to be a short human-readable label for a palette, suitable for rendering in a pick-list for the user to choose from. For standard palettes with well-known SOP Instance UIDs, values for this Attribute are pre-defined by the Standard. @@ -259362,7 +262594,7 @@
Generic Implant Template Description Module - defines the general Attributes of the Generic Implant Template Description Module. + specifies the Attributes of the . @@ -259961,23 +263193,23 @@
Generic Implant Template Description Module Attributes
- Generic Implant Template Description Attribute Descriptions + Generic Implant Template Description Module Attribute Descriptions
Implant Size Implant Size (0068,6210) is the descriptor defined by the manufacturer to distinguish between different sizes of one kind of implant, e.g., size S/M/L/XL.
Frame of Reference - The Frame of Reference UID (0020,0052) Attribute is used as an identifier for spatial registration in 3D. The Frame Of Reference UID uniquely identifies the spatial Frame of Reference of all 3D models contained in an Implant Template UID Instance. - If the Frame Of Reference UIDs in two Instances are identical, the contained 3D Models are defined in the same 3D space, i.e., require no additional registration. + The Frame of Reference UID (0020,0052) Attribute is used as an identifier for spatial registration in 3D. The Frame of Reference UID uniquely identifies the spatial Frame of Reference of all 3D models contained in an Implant Template UID Instance. + If the Frame of Reference UIDs in two Instances are identical, the contained 3D Models are defined in the same 3D space, i.e., require no additional registration.
- Generic Implant Template 2D Drawings Module - - defines the general Attributes of the Generic Implant Template 2D Drawings Module. This Module contains all Attributes required for the inclusion of technical 2D drawings in an IOD, e.g., the Implant Template IOD. The Module specification contains the definition of a subset of the HPGL plotter language that is used for the graphical definition of the drawings. - + Generic Implant Template 2D Drawings Module + + specifies the Attributes of the . This Module contains all Attributes required for the inclusion of technical 2D drawings in an IOD, e.g., the Implant Template IOD. The Module specification contains the definition of a subset of the HPGL plotter language that is used for the graphical definition of the drawings. +
@@ -260164,9 +263396,9 @@ 1 - + Numeric ID of the pen in the HPGL document. + +
Generic Implant Template 2D Drawings Module Attributes
- Numeric ID of the pen in the HPGL document -
>>HPGL Pen Label @@ -260226,7 +263458,7 @@
- Generic Implant Template 2D Drawings Attribute Descriptions + Generic Implant Template 2D Drawings Module Attribute Descriptions
HPGL Document Scaling and Coordinate System HPGL Documents use integer coordinates based on a 25µm grid in the printing space - i.e., the paper to print on - rather than the object space. HPGL Document Scaling (0068,62F2) is used to scale the printed dimensions measured in millimeters to match the real dimensions of the implant measured in millimeters. @@ -260380,7 +263612,7 @@
Generic Implant Template 3D Models Module - defines the general Attributes of the Generic Implant Template 3D Models Module. This Module contains Attributes that add context and scaling information to surfaces specified in the , for 3D Models in an Implant Template Instance. + specifies the Attributes of the Generic Implant Template 3D Models Module. This Module contains Attributes that add context and scaling information to surfaces specified in the , for 3D Models in an Implant Template Instance. @@ -260476,7 +263708,7 @@
Generic Implant Template 3D Models Module Attributes
- Generic Implant Template 3D Models Attribute Descriptions + Generic Implant Template 3D Models Module Attribute Descriptions
Surface Model Scaling Factor Surface Model Scaling Factor (0068,6390) is used to scale dimensions of the surface mesh representation to match the real dimensions of the implant measured in millimeters. @@ -260487,7 +263719,7 @@
Generic Implant Template Mating Features Module - defines the general Attributes of the Generic Implant Template Mating Features Module. This Module adds coordinate systems that can be utilized to geometrically constrain mating of Implant Templates when planning the implantation of a modular implant. + specifies the Attributes of the Generic Implant Template Mating Features Module. This Module adds coordinate systems that can be utilized to geometrically constrain mating of Implant Templates when planning the implantation of a modular implant. An Implant Template may contain 2D drawings of the described implant, 3D surface models of the described implant, or both. In this Module mating features that constrain the geometric matching of implants in multi-component assemblies are specified. These geometric features (points and axes) can be specified in the 2D drawings as well as the 3D models. Mating features are grouped into mating feature sets (see ). Based on the existence of 2D drawings and/or 3D models in the Instance, either or both is possible. In this Module, there are a number of conditions on Attribute use to support the following cases: @@ -260620,7 +263852,7 @@ 1C - The Axes of contact described as direction cosines in the 3D coordinate system defined by the Frame Of Reference UID. + The Axes of contact described as direction cosines in the 3D coordinate system defined by the Frame of Reference UID. Required if 3D Mating Point (0068,64C0) is present. See @@ -260848,7 +264080,7 @@
- Generic Implant Template 2D Drawings Attribute Descriptions + Generic Implant Template Mating Features Module Attribute Descriptions
Mating Features These Attributes establish a Cartesian coordinate system relative to the Frame of Reference of the implant. When two implants are assembled using a pair of mating features, a rigid spatial registration can be established, that transforms one Frame of Reference so that the mating features align. @@ -260864,7 +264096,7 @@
Generic Implant Template Planning Landmarks Module - defines the general Attributes of the Generic Implant Template Planning Landmarks Module. This Module adds planning landmarks, i.e., geometric annotations that constrain implant template registration to anatomical features, to the Implant Template IOD. + specifies the Attributes of the Generic Implant Template Planning Landmarks Module. This Module adds planning landmarks, i.e., geometric annotations that constrain implant template registration to anatomical features, to the Implant Template IOD. An Implant Template may contain 2D drawings from several viewpoints, 3D surface models, or both. The planning landmarks that are specified with this Module may occur in all of these, but may also only occur in some of these (due to their invisibility or irrelevance in some drawings or the 3D representation). Each 2D drawing specifies its own 2D drawing space, which requires a separate geometric description for each drawing. The 3D models share one Frame of Reference. Thus, each landmark needs only one 3D representation that then applies to all 3D models contained in one Instance. The Attribute Descriptions of the Attributes that geometrically define landmarks (in and and ) contain complicated Conditions that express the following constraints: @@ -261446,7 +264678,7 @@
Implant Assembly Template Module - defines the general Attributes of the Implant Assembly Template Module. + specifies the Attributes of the . @@ -262018,9 +265250,9 @@ Implant Template Group ModuleThis section describes the specific Modules for the Implant Template Group IOD.
- Implant Template Group Module + Implant Template Group Module - contains the Attributes of the Implant Template Group Module. + specifies the Attributes of the .
Implant Assembly Template Module Attributes
@@ -262065,9 +265297,9 @@ 1 - + Name of this group. + +
Implant Template Group Module Attributes
- Name of this group -
Implant Template Group Description @@ -262431,8 +265663,8 @@ The following Sections specify Modules used for Unified Procedure Steps.
Unified Procedure Step Progress Information Module - - specifies the Attributes that describe the progress of a Unified Procedure Step (UPS). + + specifies the Attributes of the , which describe the progress of a Unified Procedure Step (UPS). @@ -262667,8 +265899,8 @@
Unified Procedure Step Scheduled Procedure Information Module - - specifies the Attributes that describe the Unified Procedure Step (UPS) to be performed. The UPS may or may not be scheduled for a specific time or device, or may simply represent a piece of work that is intended to be performed. + + specifies the Attributes of the , which describe the Unified Procedure Step (UPS) to be performed. The UPS may or may not be scheduled for a specific time or device, or may simply represent a piece of work that is intended to be performed.
Unified Procedure Step Progress Information Module Attributes
@@ -263121,8 +266353,8 @@
Unified Procedure Step Performed Procedure Information Module - - specifies the Attributes that describe the performance and results of a Unified Procedure Step (UPS). + + specifies the Attributes of the , which describe the performance and results of a Unified Procedure Step (UPS).
Unified Procedure Step Scheduled Procedure Information Module Attributes
@@ -263358,7 +266590,7 @@ @@ -263435,8 +266667,8 @@
Unified Procedure Step Relationship Module - - specifies the Attributes that describe the relationship of a Unified Procedure Step (UPS). + + specifies the Attributes of the , which describe the relationship of a Unified Procedure Step (UPS).
Unified Procedure Step Performed Procedure Information Module Attributes
Parameters used to perform the procedure. - Zero or more Items shall be present in this Sequence + Zero or more Items shall be present in this Sequence.
@@ -263527,7 +266759,7 @@ The identifier is coded as a string regardless of the type, not as a binary value. - When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the SOP Common Module, if present. + When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the , if present. @@ -263603,7 +266835,7 @@ The identifier is coded as a string regardless of the type, not as a binary value. - When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the SOP Common Module, if present. + When this Attribute has a value of BARCODE, Patient ID (0010,0020) may or may not have the same value as Barcode Value (2200,0005) in the , if present. @@ -266594,7 +269826,7 @@ Display System Modules
Display System Module - This Module describes the Display System. + This Module specifies the Attributes of the Display System Module, and describes the Display System.
Unified Procedure Step Relationship Module Attributes
@@ -266816,7 +270048,7 @@ (0028,7022) @@ -267507,7 +270739,7 @@ (0028,7011) @@ -268364,7 +271596,7 @@ Content Assessment Modules
Content Assessment Results Module - This Module describes the results of the assessment of a SOP Instance. + This Module specifies the Attributes of the Content Assessment Results Module, and describes the results of the assessment of a SOP Instance. The type of observations that are included in the results is up to the implementation. Although all observations with the Observation Significance (0082,0008) with value MAJOR are included, inclusion of other observation is on the discretion of the implementation.
Display System Module Attributes
- Type of technology used in the Display Device + Type of technology used in the Display Device.
- Results of QA activities for the identified Display Subsystem in the identified configuration + Results of QA activities for the identified Display Subsystem in the identified configuration.
@@ -268540,7 +271772,7 @@ @@ -268620,7 +271852,7 @@ 3 @@ -268665,7 +271897,7 @@
Content Assessment Results Module Attributes
Summary of the assessment result. The relationship between the values of Observation Type (0082,0008) found and the Assessment Summary value is implementation dependent. - + Enumerated Values: PASSED @@ -268592,7 +271824,7 @@ This may include specifications for the assessment process and criteria for determining the Observation Type (0082,0008). - One or more Items may be present in this Sequence. + One or more Items are permitted in this Sequence.
- Description or title of the resource + Description or title of the resource.
The significance of this observation regarding the quality or effectiveness of the assessed SOP Instance of this observation. - + Enumerated Values: MAJOR @@ -268802,9 +272034,10 @@ This section describes Modules specific to the family of Defined and Performed Procedure Protocol IODs.
CT Protocol Series Module - The CT Protocol IODs use the General Series Module described in , specialized by the CT Protocol Series Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of a Protocol. - specifies the Attributes that describe a CT Protocol Series. + specifies the Attributes of the . + The CT Protocol IODs use the , specialized by this Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of a Protocol. + @@ -268853,7 +272086,8 @@
Protocol Context Module - The context in which the described Protocol is defined or performed. This Module is applicable to defined and performed procedure protocols. + + specifies the Attributes of the , which describe the context in which the described Protocol is defined or performed. This Module is applicable to defined and performed procedure protocols. Details like the Potential Reasons for Procedure Code Sequence (0018,9909) or the Protocol Planning Information (0018,990F) may be copied from the defined protocol into the performed protocol to support quality assurance activities like checking whether the contents of the Reason for Requested Procedure Code Sequence (0040,100A) recorded in the performed protocol are consistent with the contents of the Potential Reasons for Procedure Code Sequence (0018,9909).
CT Protocol Series Module Attributes
@@ -268887,7 +272121,7 @@ @@ -268947,7 +272181,7 @@ @@ -269102,7 +272336,7 @@ @@ -269291,7 +272525,7 @@
Protocol Management - The Protocol Context Module contains Attributes for grouping and managing Protocol objects. + The contains Attributes for grouping and managing Protocol objects. The Responsible Group Code Sequence (0008,0220) can be used by the department or clinical specialty to collect the Protocols for which they are responsible for review and management. The Potential Scheduled Protocol Code Sequence (0018,9906) and Potential Reasons for Procedure Code Sequence (0018,9909) can gather Protocols associated with a given procedure code or indication respectively. The contents of the Referenced Defined Protocol Sequence (0018,990C) in a collection of Performed Procedure Protocol objects can be used to determine the frequency of usage of the corresponding Defined Procedure Protocol objects. @@ -269299,7 +272533,8 @@
Patient Protocol Context Module - The patient specific context in which the described Protocol is performed. This Module is applicable to performed procedures. + + specifies the Attributes of the , which describe the patient specific context in which the described Protocol is performed. This Module is applicable to performed procedures.
Protocol Context Module Attributes
Custodial organization for this Protocol Instance. Represents the organization that is currently in charge of maintaining this protocol Instance. - This may or may not be identical to the Institution identified in the Equipment Module. This may or may not be the Institution that originally created this Instance. + This may or may not be identical to the Institution identified in the . This may or may not be the Institution that originally created this Instance. Only a single Item is permitted in this Sequence. The department, unit or service that is responsible for the management of this Protocol. See . - Zero or more Items shall be included in this Sequence + Zero or more Items shall be included in this Sequence.
List of reasons for which the authors of the Protocol deemed it contraindicated. - Constraints on values of patient demographic Attributes such as sex, age or weight are addressed separately in the Patient Specification Module. See . + Constraints on values of patient demographic Attributes such as sex, age or weight are addressed separately in the . See . One or more Items are permitted in this Sequence.
@@ -269348,8 +272583,8 @@
Clinical Trial Context Module - - contains Attributes that identify a clinical trial context independent of any specific Clinical Trial Subjects. + + specifies the Attributes of the , which identify a clinical trial context independent of any specific Clinical Trial Subjects.
Patient Protocol Context Module Attributes
@@ -269520,8 +272755,8 @@
Patient Specification Module - - contains patient characteristics for which a Protocol may be considered applicable. + + specifies the Attributes of the , which describes patient characteristics for which a Protocol may be considered applicable.
Clinical Trial Context Module Attributes
@@ -269564,11 +272799,11 @@ @@ -269589,8 +272824,8 @@
Equipment Specification Module - - contains equipment characteristics for which a Protocol may be considered appropriate. + + specifies the Attributes of the , which describe equipment characteristics for which a Protocol may be considered appropriate.
Patient Specification Module Attributes
- Only Attributes defined in the Patient Module (See ) or the Patient Study Module (See ) may be specified as Selector Attributes. + Only Attributes defined in the or the may be specified as Selector Attributes. See . The same Attribute shall not be constrained in more than one Item in this Sequence. - Since these constraints are being placed on the Attributes that will appear in the Patient Module or Patient Study Module of the resulting Instances, the Patient Specification Sequence will not appear in the Selector Sequence Pointer (0072,0052). + Since these constraints are being placed on the Attributes that will appear in the or the of the resulting Instances, the Patient Specification Sequence will not appear in the Selector Sequence Pointer (0072,0052).
@@ -269756,8 +272991,8 @@
Instructions Module - - contains instructions relating to preparation and performance of the Protocol. + + specifies the Attributes of the , which describe instructions relating to preparation and performance of the Protocol.
Equipment Specification Module Attributes
@@ -269934,15 +273169,15 @@ Start the AP Localizer Acquisition Protocol Element eight minutes after start of contrast injection and repeat the AP Localizer Acquisition Protocol Element at one minute intervals until adequate ureter opacification is observed, then proceed to the abdomen Acquisition Protocol Element - Instructions related to the initial positioning of the patient are included in the Patient Positioning Module. This Module may describe subsequent changes in position between steps of the protocol. + Instructions related to the initial positioning of the patient are included in the . This Module may describe subsequent changes in position between steps of the protocol.Equipment preparation instructions would typically be limited to phantom imaging or other calibration procedures related to the individual patient scan. Phantom Imaging and/or Calibration to be performed as general QA/qualification (i.e., not associated with the individual patient scan) shall not be described in this Module.Activities that are associated with the protocol but which are not typically performed in the scanning room, such as the need to obtain creatinine values within 7 days before performing the Protocol, or to premedicate the patient with Benadryl 1 hour before performing the Protocol, are described in the Protocol Planning Information (0018,990F) rather than in this Module.
Patient Positioning Module - - contains details about the positioning of the patient before and during the imaging procedure. + + specifies the Attributes of the , which describe details about the positioning of the patient before and during the imaging procedure.
Instructions Module Attributes
@@ -270311,7 +273546,8 @@ Anatomic Region & Primary Anatomic StructurePrimary Anatomic Structure Sequence (0008,2228) shall identify the specific organ or structure that is the focus of the procedure described by the Protocol and will generally correlate with the Reason for Study and the Procedure Code. Anatomic Region Sequence (0008,2218) shall identify the region of the body spanned by the images produced by the Protocol. For example, a Protocol might identify the Primary Anatomic Structure as "liver" and the Anatomic Region as "abdomen".The contents of the Anatomic Region Sequence (0008,2218) is not necessarily a precise description of the full extent of the scan or the reconstructed slices. "Chest" may refer to a scan that spans only part of the chest, the whole chest, or includes parts of regions beyond the chest. For a more precise description of the extent of the acquisition or reconstructed slices, refer to the Acquisition Start Location Sequence (0018,9931) and Acquisition End Location Sequence (0018,9932) or the Reconstruction Start Location Sequence (0018,993B) and Reconstruction End Location Sequence (0018,993C). - For Protocols that could be used in a variety of anatomic regions, such as one designed for a certain type of metastasis or biopsy, the Primary Anatomic Structure Sequence might contain a generic code like (49755003, SCT, "Morphologically abnormal structure") and the Anatomic Region Sequence may be empty in the (non-patient-specific) Defined Protocol, but could be populated in the Performed Protocol. In such cases, the Protocol Context Module may describe a list of anatomic regions for which the Protocol is intended/appropriate. + For Protocols that could be used in a variety of anatomic regions, such as one designed for a certain type of metastasis or biopsy, the Primary Anatomic Structure Sequence might contain a generic code like (49755003, SCT, "Morphologically abnormal structure") and the Anatomic Region Sequence may be empty in the (non-patient-specific) Defined Protocol, but could be populated in the Performed Protocol. + In such cases, the may describe a list of anatomic regions for which the Protocol is intended/appropriate. It is expected that the modality will migrate these codes, as appropriate, into the resulting images to facilitate the selection of hanging protocols and report templates appropriate to the primary anatomic structure or future searches for anatomically relevant priors. @@ -270319,8 +273555,8 @@
General Defined Acquisition Module - - contains a specification of acceptable values and ranges of acquisition parameters for an imaging procedure. + + specifies the Attributes of the , which describe a specification of acceptable values and ranges of acquisition parameters for an imaging procedure.
Patient Positioning Module Attributes
@@ -270393,8 +273629,8 @@ @@ -270432,13 +273668,12 @@
General Defined Acquisition Module Attributes
- For CT only Attributes defined in (i.e., in the Acquisition Protocol Element Sequence (0018,9920) in the Performed CT Acquisition Module) and Private Data Elements associated with this acquisition protocol element may be specified as Selector Attributes. - For XA only Attributes defined in (i.e., in the Acquisition Protocol Element Sequence (0018,9920) in the Performed XA Acquisition Module) and Private Data Elements associated with this acquisition protocol element may be specified as Selector Attributes. + For CT only Attributes defined in (i.e., in the Acquisition Protocol Element Sequence (0018,9920) in the ) and Private Data Elements associated with this acquisition protocol element may be specified as Selector Attributes. + For XA only Attributes defined in (i.e., in the Acquisition Protocol Element Sequence (0018,9920) in the ) and Private Data Elements associated with this acquisition protocol element may be specified as Selector Attributes. The semantics of values of Constraint Violation Significance (0082,0036) in the Macro are assigned in . The same Attribute shall not appear in more than one Item in the Sequence with the same values for Selector Sequence Pointer (0072,0052) and Selector Sequence Pointer Items (0074,1057).
- The Performed CT Acquisition Module in the CT Performed Procedure Protocol will generally be "fully populated". The General Defined Acquisition Module in the CT Defined Procedure Protocol Object may be "sparsely populated" (i.e., contains only the Attributes the system that is specifying the protocol "cares about"). + The in the CT Performed Procedure Protocol will generally be "fully populated". The General Defined Acquisition Module in the CT Defined Procedure Protocol Object may be "sparsely populated" (i.e., contains only the Attributes the system that is specifying the protocol "cares about").
Acquisition Protocol Elements A Protocol usually includes more than one Acquisition Protocol Element. For example, a chest Protocol in CT might include three elements in total: two localizer CT radiographs (AP and Lateral), and a single helical scan. - An illustrative example for CT is provided in . - In this example, since all parameters will be nested inside an Acquisition Protocol Element Sequence (0018,9920) and some of the parameters will be further nested inside a CT X-Ray Details Sequence (0018,9325), close attention must be paid to the use of the Selector Sequence Pointer (0072,0052) in the Attribute Value Constraint Macro. + An illustrative example for CT is provided in . In this example, since all parameters will be nested inside an Acquisition Protocol Element Sequence (0018,9920) and some of the parameters will be further nested inside a CT X-Ray Details Sequence (0018,9325), close attention must be paid to the use of the Selector Sequence Pointer (0072,0052) in the . @@ -270592,15 +273827,16 @@ Modifiable Constraint FlagNew protocol Instances derived from original protocol Instances with different constraints on a given Attribute "modify" the constraint. This flag may be used by devices that create original Instances to specify which constraints can be modified by other devices in derived Instances.For example, a CT device that creates a Defined Procedure Protocol, may indicate that the Element Name (0018,9922) of the Acquisition Protocol Element, or the CTDIvol Notification Trigger (0018,9942) constraints may be modified, but the Spiral Pitch Factor (0018,9311) constraint may not since the latter depends on correlated changes by the device to other Attributes. Such information would be useful to a protocol management workstation that is letting its operator make changes to the CTDIvol Notification Trigger. - For example, an XA device that creates a Defined Procedure Protocol, may indicate that the Element Name (0018,9922) of the Acquisition Protocol Element may be modified, but the Focal Spot(s) (0018,1190) constraint may not since the latter depends on correlated changes by the device to other attributes. Such information would be useful to a protocol management workstation that is letting its operator make changes to the Element Name (0018,9922) of the Acquisition Protocol Element. + For example, an XA device that creates a Defined Procedure Protocol, may indicate that the Element Name (0018,9922) of the Acquisition Protocol Element may be modified, but the Focal Spot(s) (0018,1190) constraint may not since the latter depends on correlated changes by the device to other Attributes. Such information would be useful to a protocol management workstation that is letting its operator make changes to the Element Name (0018,9922) of the Acquisition Protocol Element. - There is a difference between these "derivation" modifications and what an operator does at the time of protocol execution. At execution time, the operator is using the device to change Selector Attribute values and those values are compared to the Constraint Values in the Constraint Macro of the Defined Protocol. The result may (or may not be) stored in a Performed Procedure Protocol Instance. At derivation time, an operator is using a workstation to change Constraint Values in the Constraint Macro and store a new Defined Procedure Protocol Instance. + There is a difference between these "derivation" modifications and what an operator does at the time of protocol execution. At execution time, the operator is using the device to change Selector Attribute values and those values are compared to the Constraint Values in the of the Defined Protocol. The result may (or may not be) stored in a Performed Procedure Protocol Instance. At derivation time, an operator is using a workstation to change Constraint Values in the and store a new Defined Procedure Protocol Instance.
Performed CT Acquisition Module - This Module contains acquisition parameter values for a performed CT imaging procedure. The purpose of this Module is to record all relevant parameters, not just to record the values that were constrained in the executed Defined Protocol (if any). + + specifies the Attributes of the , which contain acquisition parameter values for a performed CT imaging procedure. The purpose of this Module is to record all relevant parameters, not just to record the values that were constrained in the executed Defined Protocol (if any). This Module contains Attributes that are "set" on the machine, e.g., to affect its behavior, but not those that describe the results. The latter may be found in the reconstructed images.
Example Usage of Selector Macro Attributes for Acquisition Constraints
@@ -271808,8 +275044,8 @@
General Defined Reconstruction Module - - contains specification of acceptable values and ranges of reconstruction parameters for an imaging procedure. + + specifies the Attributes of the , which describe specification of acceptable values and ranges of reconstruction parameters for an imaging procedure.
Performed CT Acquisition Module Attributes
@@ -271882,8 +275118,8 @@ @@ -271922,14 +275158,13 @@
General Defined Reconstruction Module Attributes
- For CT only Attributes defined in (i.e., in the Reconstruction Protocol Element Sequence (0018,9934) in the Performed CT Reconstruction Module) and Private Data Elements associated with this reconstruction protocol element may be specified as Selector Attributes. - For XA only Attributes defined in (i.e., in the Reconstruction Protocol Element Sequence (0018,9934) in the Performed XA Reconstruction Module) and Private Data Elements associated with this reconstruction protocol element may be specified as Selector Attributes. + For CT only Attributes defined in (i.e., in the Reconstruction Protocol Element Sequence (0018,9934) in the ) and Private Data Elements associated with this reconstruction protocol element may be specified as Selector Attributes. + For XA only Attributes defined in (i.e., in the Reconstruction Protocol Element Sequence (0018,9934) in the ) and Private Data Elements associated with this reconstruction protocol element may be specified as Selector Attributes. The semantics of values of Constraint Violation Significance (0082,0036) in the Macro are assigned in . The same Attribute shall not appear in more than one Item in the Sequence with the same values for Selector Sequence Pointer (0072,0052) and Selector Sequence Pointer Items (0074,1057).
Reconstruction Protocol Elements - A Protocol may specify multiple reconstructions. - For example, a CT single helical Acquisition Protocol Element may be reconstructed once as thin slices and a second time as thick slices. - Also an XA single subtracted rotational Acquisition Protocol Element may be reconstructed once as mask slices and a second time as subtracted slices. + A Protocol may specify multiple reconstructions. For example, a CT single helical Acquisition Protocol Element may be reconstructed once as thin slices and a second time as thick slices. Also an XA single subtracted rotational Acquisition Protocol Element may be reconstructed once as mask slices and a second time as subtracted slices.
Performed CT Reconstruction Module - This Module contains reconstruction parameter values for a performed CT imaging procedure. + + specifies the Attributes of the , which contain reconstruction parameter values for a performed CT imaging procedure. This Module contains Attributes that affect machine behavior but not those that are merely descriptive. The latter may be found in the reconstructed images. @@ -272388,7 +275623,7 @@ 3 @@ -272547,8 +275782,8 @@
Defined Storage Module - - contains specification of acceptable values and ranges of storage parameters for an imaging procedure. Storage protocol elements may be used to automatically send the output of particular protocol elements to particular destinations. For example, a lung protocol might send thick images to PACS for reading and thin images to a CAD workstation for detection of nodules; a cardiac protocol might send an image set to a clinical analysis workstation; and a protocol used for pre-operative hip replacement planning might send images to the orthopedics department. + + specifies the Attributes of the , which describe specification of acceptable values and ranges of storage parameters for an imaging procedure. Storage protocol elements may be used to automatically send the output of particular protocol elements to particular destinations. For example, a lung protocol might send thick images to PACS for reading and thin images to a CAD workstation for detection of nodules; a cardiac protocol might send an image set to a clinical analysis workstation; and a protocol used for pre-operative hip replacement planning might send images to the orthopedics department.
Performed CT Reconstruction Module Attributes
- Additional processing applied to the reconstructed image after image filter (if any) + Additional processing applied to the reconstructed image after image filter (if any).
@@ -272621,7 +275856,7 @@ @@ -272672,13 +275907,13 @@
Storage Protocol Elements - A Protocol frequently specifies multiple storage protocol elements. - For example, in CT thin slices may be transmitted to a 3D workstation, while raw data is stored on a local cache and thick slices are stored to PACS for reading. + A Protocol frequently specifies multiple storage protocol elements. For example, in CT thin slices may be transmitted to a 3D workstation, while raw data is stored on a local cache and thick slices are stored to PACS for reading.
Performed Storage Module - This Module contains storage parameter values for a performed imaging procedure. + + specifies the Attributes of the , which contain storage parameter values for a performed imaging procedure.
Defined Storage Module Attributes
- Only Attributes defined in (i.e., in the Storage Protocol Element Sequence (0018,9936) in the Performed Storage Module) and Private Data Elements associated with this storage protocol element may be specified as Selector Attributes. + Only Attributes defined in (i.e., in the Storage Protocol Element Sequence (0018,9936) in the ) and Private Data Elements associated with this storage protocol element may be specified as Selector Attributes. The semantics of values of Constraint Violation Significance (0082,0036) in the Macro are assigned in . The same Attribute shall not appear in more than one Item in the Sequence with the same values for Selector Sequence Pointer (0072,0052) and Selector Sequence Pointer Items (0074,1057).
@@ -272716,8 +275951,7 @@ - Whether to report failure of one or more of the storage protocol elements as a failure of the protocol is at the discretion of the performing system. - The performing system may, additionally or as a fallback, have configured behaviors to store output objects to a default destination or retain them locally. + Whether to report failure of one or more of the storage protocol elements as a failure of the protocol is at the discretion of the performing system. The performing system may, additionally or as a fallback, have configured behaviors to store output objects to a default destination or retain them locally. Similarly, whether the need to complete and record performed storage protocol elements merits delaying the creation of the Performed Protocol objects in which that would be recorded is left to the discretion of the implementation. @@ -272726,7 +275960,7 @@ Further, there is no intention to record instance storage events that occur beyond those immediately associated with the initial acquisition and reconstruction of the study data. - + @@ -272874,9 +276108,10 @@
Protocol Approval Module - The Protocol Approval Module records approvals of the content of one or more SOP Instances containing protocols by a person or device. - An approval is modeled as a form of Assertion. The nature of the approval is defined by the Assertion Code in the embedded Assertion Macro. - Neither the Protocol Approval Module nor the underlying Assertion Macro address securing the approved Instance against tampering (e.g., via a digital hash) or authenticating the identity of the source of the Assertion. + + specifies the Attributes of the , which record approvals by a person or device of the content of one or more SOP Instances containing protocols. + An approval is modeled as a form of Assertion. The nature of the approval is defined by the Assertion Code in the embedded . + Neither the nor the underlying address securing the approved Instance against tampering (e.g., via a digital hash) or authenticating the identity of the source of the Assertion.
Performed Storage Module Attributes
@@ -272948,7 +276183,7 @@ Assertion Code Sequence (0044,0101) B. - The Approver is recorded in the Asserter Identification Sequence inside the Assertion Macro. + The Approver is recorded in the Asserter Identification Sequence inside the . @@ -273196,11 +276431,9 @@
XA Protocol Series Module - The XA Protocol IODs use the , specialized by the XA Protocol Series Module, - to describe the DICOM Series Entity described in , - and to define what constitutes a Series for the context of a Protocol. + The XA Protocol IODs use the , specialized by the XA Protocol Series Module, to describe the DICOM Series Entity described in , and to define what constitutes a Series for the context of a Protocol. - specifies the Attributes that describe a XA Protocol Series. + specifies the Attributes that describe a XA Protocol Series.
Protocol Approval Module Attributes
@@ -273249,19 +276482,13 @@
Performed XA Acquisition Module - This Module contains acquisition parameter values for a performed XA imaging procedure. - The purpose of this Module is to record all relevant parameters, not just to record the values that were constrained in the executed Defined Protocol (if any). - This Module contains Attributes that are "set" on the machine, e.g., to affect its behavior, but not those that describe the results. - The latter may be found in the acquired images. + + specifies the Attributes of the , which contain acquisition parameter values for a performed XA imaging procedure. The purpose of this Module is to record all relevant parameters, not just to record the values that were constrained in the executed Defined Protocol (if any). + This Module contains Attributes that are "set" on the machine, e.g., to affect its behavior, but not those that describe the results. The latter may be found in the acquired images. - The acquisition parameters for an XA imaging system are those involved in the creation of the 2D ORIGINAL pixel data. - They include two different activities: the control of the X-Ray generation and beam formation to obtain the output signal from the X-Ray detector (so-called raw data), - and the linear and image-independent corrections of the raw data. + The acquisition parameters for an XA imaging system are those involved in the creation of the 2D ORIGINAL pixel data. They include two different activities: the control of the X-Ray generation and beam formation to obtain the output signal from the X-Ray detector (so-called raw data), and the linear and image-independent corrections of the raw data. - The XA Defined Acquisition Protocol is typically selected manually from the device console, although rules may exist on the device to pre-select a default protocol based on procedure type and patient characteristics. - Each Protocol Element contains the parameters of one acquisition mode. - For a biplane system, the parameters for both planes are contained in the same protocol element. - The operator may choose which Protocol Elements are performed during the procedure. + The XA Defined Acquisition Protocol is typically selected manually from the device console, although rules may exist on the device to pre-select a default protocol based on procedure type and patient characteristics. Each Protocol Element contains the parameters of one acquisition mode. For a biplane system, the parameters for both planes are contained in the same protocol element. The operator may choose which Protocol Elements are performed during the procedure.
XA Protocol Series Module Attributes
@@ -273292,8 +276519,7 @@ 2 @@ -274108,7 +277334,7 @@ @@ -274233,7 +277459,7 @@ Fluoroscopy PersistenceAn XA device acquires fluoroscopy to be primarily displayed in real time during image-guided procedures.Fluoroscopy Persistence means that the fluoroscopy pixel data is not discarded immetiately after the acquisition, but rather it is kept locally on the acquisition device for further use, either to be reviewed, processed, stored on media and/or transmitted as DICOM instances to another DICOM device. - The attributes Fluoroscopy Persistence Flag (0018,11B3) and Fluoroscopy Last Image Hold Persistence Flag (0018,11B4) do not suggest or assume any further use of the data other than the local storage on the acquisition device. The workflows related to the presentation, processing or transmission of Fluoroscopy data is handled outside the Acquisition Protocols. + The Attributes Fluoroscopy Persistence Flag (0018,11B3) and Fluoroscopy Last Image Hold Persistence Flag (0018,11B4) do not suggest or assume any further use of the data other than the local storage on the acquisition device. The workflows related to the presentation, processing or transmission of Fluoroscopy data is handled outside the Acquisition Protocols.
XA Acquisition Phase Details Sequence @@ -274244,10 +277470,11 @@
Performed XA Reconstruction Module - This Module contains reconstruction parameter values for a performed XA imaging procedure. + + specifies the Attributes of the , which contain reconstruction parameter values for a performed XA imaging procedure. This Module contains Attributes that reflect machine behavior but not those that are merely descriptive. The latter may be found in the reconstructed images. - Although the protocol elements are performed in the order of their Protocol Element Number (0018,9921), the order in which the attributes inside an item in the Reconstruction Protocol Element Sequence (0018,9934) is not encoded here but rather is determined by the processing pipeline of the specific device. + Although the protocol elements are performed in the order of their Protocol Element Number (0018,9921), the order in which the Attributes inside an item in the Reconstruction Protocol Element Sequence (0018,9934) is not encoded here but rather is determined by the processing pipeline of the specific device. The XA Reconstruction Protocol includes 2D and 3D processing parameters. Some parameters are applicable to both 2D and 3D processing while other parameters are only applicable to 3D processing (e.g. slice thickness).
Performed XA Acquisition Module Attributes
- Parameter values for each Protocol Element in the acquisition protocol. Each item in the sequence describes one Element. - Elements are performed in the order of their Protocol Element Number (0018,9921). + Parameter values for each Protocol Element in the acquisition protocol. Each item in the sequence describes one Element. Elements are performed in the order of their Protocol Element Number (0018,9921). See . Zero or more Items shall be included in this Sequence.
- >>Rotational Primary Angle Rotation Step + >>Primary Positioner Increment (0018,9514) @@ -274123,7 +277349,7 @@
- >>Rotational Secondary Angle Rotation Step + >>Secondary Positioner Increment (0018,9515) @@ -274138,7 +277364,7 @@
- >>Rotational SID (distance source to detector) + >>Distance Source to Detector (0018,1110) @@ -274177,7 +277403,7 @@ A code that is intended to be copied into the Series Description Code Sequence (0008,103F) of the images resulting from this Acquisition Protocol Element. - Only a single Item is permitted in this Sequence + Only a single Item is permitted in this Sequence.
@@ -274348,7 +277575,7 @@ @@ -274398,7 +277625,7 @@ @@ -274766,7 +277993,7 @@ @@ -274829,9 +278056,9 @@
Content Qualification - Content Qualification (0018,9004), if present, specifies the value to be copied into reconstructed instances. For details on the meaning of this attribute in those instances, see . - This attribute does not describe the content qualification of the protocol itself. -
+ Content Qualification (0018,9004), if present, specifies the value to be copied into reconstructed instances. For details on the meaning of this Attribute in those instances, see . + This Attribute does not describe the content qualification of the protocol itself. +
@@ -275052,8 +278279,7 @@ 3
@@ -275145,11 +278371,8 @@
Beam Modifier Coordinate System Beam modifiers, e.g., beam limiting devices, compensators and blocks, are specified by geometric coordinates. - A Base Beam Modifier Coordinate System is defined with respect to a parent coordinate system, which may be the Equipment Coordinate System (see ) or another coordinate system derived from the Equipment Coordinate System. - The parent coordinate system is specified in Equipment Frame of Reference UID (300A,0675) (see ) using a Well-known Frame of Reference UID listed in . - The x/y plane of the Base Beam Modifier Coordinate System is referred to as the Base Beam Modifier Definition Plane. - The orientation of the Base Beam Modifier Coordinate System is such that the Base Beam Modifier Definition Plane is parallel to the x/y plane of the parent coordinate system. - The origin of the Base Beam Modifier Coordinate System is offset from the RT Device Distance Reference Location by the RT Beam Modifier Definition Distance (300A,0688) as shown in . + A Base Beam Modifier Coordinate System is defined with respect to a parent coordinate system, which may be the Equipment Coordinate System (see ) or another coordinate system derived from the Equipment Coordinate System. specifies several Well-known Frames of Reference used as the Equipment Frame of Reference, and specifies how a Base Beam Modifier Coordinate System is related to each as a child coordinate system. + The x/y plane of the Base Beam Modifier Coordinate System is referred to as the Base Beam Modifier Definition Plane. The orientation of the Base Beam Modifier Coordinate System is such that the Base Beam Modifier Definition Plane is parallel to the x/y plane of the parent coordinate system. The origin of the Base Beam Modifier Coordinate System is offset from the RT Device Distance Reference Location by the RT Beam Modifier Definition Distance (300A,0688) as shown in .
Base Beam Modifier Coordinate System and a rotated Beam Modifier Coordinate System @@ -275189,7 +278412,8 @@ RT Second Generation General Purpose Macros
Radiation Fraction Pattern Macro - The Radiation Fraction Pattern Macro specifies the intended fraction pattern to be used to deliver the radiation treatment. + + specifies the Attributes of the , which describe the intended fraction pattern to be used to deliver the radiation treatment.
Uniquely identifies the referenced SOP Class. Required if the referenced acquisition protocol element is not in this instance. - Shall have a value of 1.2.840.10008.5.1.4.1.1.200.8 (XA Performed Procedure Protocol Storage) + Shall have a value of 1.2.840.10008.5.1.4.1.1.200.8 (XA Performed Procedure Protocol Storage).
- >Window Width + >Window Center (0028,1050) @@ -274412,7 +277639,7 @@
- >Window Center + >Window Width (0028,1051) @@ -274724,7 +277951,7 @@ 3 - Additional processing applied to the reconstructed image after image filter (if any) + Additional processing applied to the reconstructed image after image filter (if any).
A code that is intended to be copied into the Series Description Code Sequence (0008,103F) of the images resulting from this Reconstruction Protocol Element. - Only a single Item is permitted in this Sequence + Only a single Item is permitted in this Sequence.
- Uniquely identifies a group to which the model belongs. - Manufacturing models that share the same Model Group UID are considered distinct parts within the same assembly. + Uniquely identifies a group to which the model belongs. Manufacturing models that share the same Model Group UID are considered distinct parts within the same assembly.
@@ -275414,7 +278638,8 @@
RT Treatment Phase Macro - The treatment phase Macro contains the identification and additional information about an RT Treatment Phase. + + specifies the Attributes of the , which contain the identification and additional information about an RT Treatment Phase.
Radiation Fraction Pattern Macro Attributes
@@ -275517,7 +278742,8 @@
RT Treatment Phase Interval Macro - The RT Treatment Phase Interval Macro contains the information about time-relationship between RT Treatment Phases. This consists of sets of pair-wise relationships, declaring the relation of a earlier phase to a later, potentially overlapping, phase. + + specifies the Attributes of the , which contain the information about time-relationship between RT Treatment Phases. This consists of sets of pair-wise relationships, declaring the relation of a earlier phase to a later, potentially overlapping, phase.
RT Treatment Phase Macro Attributes
@@ -275661,7 +278887,8 @@
Dosimetric Objective Macro - The Dosimetric Objective Macro specifies an intended goal to be used in the definition of the dosimetric plan, for plan optimization etc. Dosimetric Objectives may define limits which affect the dose, such as dose volume constraints, minimum or maximum dose, treatment time or MU limits, and radiobiologic effects. + + specifies the Attributes of the , which specify an intended goal to be used in the definition of the dosimetric plan, for plan optimization etc. Dosimetric Objectives may define limits which affect the dose, such as dose volume constraints, minimum or maximum dose, treatment time or MU limits, and radiobiologic effects. Dosimetric Objectives, such as dose volume constraints, minimum or maximum dose, etc., can be used to specify dose goals for anatomical or other treatment volumes that are referenced by Conceptual Volumes. Other Dosimetric Objectives can also be used to specify general plan optimization objectives not related to anatomical or other treatment volumes, such as Meterset Minimization, etc.
RT Treatment Phase Interval Macro Attributes
@@ -276223,7 +279450,8 @@
Radiobiological Dose Effect Description Macro - The Radiobiological Dose Effect Description Macro describes whether dose values are provided as physical dose or effective dose. An effective dose value incorporates adjustments to dose by taking into account the radiobiological effects. + + specifies the Attributes of the , which describe whether dose values are provided as physical dose or effective dose. An effective dose value incorporates adjustments to dose by taking into account the radiobiological effects.
Dosimetric Objective Macro Attributes
@@ -276398,7 +279626,8 @@
RT Radiation Common Base Macro - The Radiation Fraction Pattern Macro specifies the intended fraction pattern to be used to deliver the radiation treatment. + + specifies the Attributes of the .
Radiobiological Dose Effect Description Macro Attributes
@@ -276510,17 +279739,17 @@ - - - + + +
RT Radiation Common Base Macro Attributes
- - Include . - - - -See . - -
+ + Include . + + + + See . + +
RT Tolerance Set Sequence @@ -276573,14 +279802,14 @@
- RT Radiation Common Attribute Descriptions + RT Radiation Common Base Macro Attribute Descriptions
Radiotherapy Procedure Technique Sequence The RT Treatment Technique Code Sequence (3010,0080) describes the treatment technique, i.e., how the radiation beam is shaped and targeted.
RT Treatment Position Macro - The RT Treatment Position Macro describes how the patient is to be positioned with respect to the delivery device for treatment. + The describes how the patient is to be positioned with respect to the delivery device for treatment. The behavior of the machine regarding the patient position between specified Control Points is outside the scope of this Standard. Communicating devices shall agree on this behavior.
@@ -276594,7 +279823,8 @@ RT Second Generation Device Macros
Treatment Device Identification Macro - The Treatment Device Identification Macro identifies a device used to deliver radiation to the patient during a radiotherapy treatment session. + + specifies the Attributes of the , which identify a device used to deliver radiation to the patient during a radiotherapy treatment session. @@ -276701,7 +279931,8 @@
RT Patient Support Devices Macro - The RT Patient Support Devices Macro identifies a patient support device (table, table top, chair or similar) which shall be used for treatment. + + specifies the Attributes of the , which identify a patient support device (table, table top, chair or similar) which shall be used for treatment.
Treatment Device Identification Macro Attributes
@@ -276812,7 +280043,8 @@
RT Accessory Device Identification Macro - The RT Accessory Device Identification Macro identifies an RT accessory device and its location. + + specifies the Attributes of the , which identify an RT accessory device and its location.
RT Patient Support Devices Macro Attributes
@@ -276840,17 +280072,17 @@ - - - + + +
RT Accessory Device Identification Macro Attributes
- - Include . - - - -CID is specified at invocation. - -
+ + Include . + + + + CID is specified at invocation. + +
RT Accessory Device Slot ID @@ -276917,22 +280149,17 @@
RT Accessory Device Slot and RT Accessory Holder Slot Description - An RT treatment delivery unit may allow the direct attachment of one or more RT Accessory Devices to the delivery unit in RT Accessory Device Slots, - identified by RT Accessory Device Slot ID (300A,0615). - Such an RT Accessory Device may be for example any kind of beam limiting device like a wedge tray or an electron applicator. - An RT Accessory Device may be mounted in or on an RT Accessory Holder which is a specific RT Accessory Device. - See . - If this RT Accessory Holder does not provide slots, the RT Accessory Holder is referred to by Referenced RT Accessory Holder Device Index (300A,060E), - for example, a block tray for a block. - If the RT Accessory Holder provides slots these are referred to by Referenced RT Accessory Holder Device Index (300A,060E) and RT Accessory Holder Slot ID (300A,0611), - for example, an electron applicator holding a block tray. - Any RT Accessory Device may either be mounted in an RT Accessory Device Slot or on an RT Accessory Device Holder. - Thus, for any RT Accessory Device the Referenced RT Accessory Holder Device Index (300A,060E) and RT Accessory Holder Slot ID (300A,0611) are mutually exclusive. + An RT treatment delivery unit may allow the direct attachment of one or more RT Accessory Devices to the delivery unit in RT Accessory Device Slots, identified by RT Accessory Device Slot ID (300A,0615). Such an RT Accessory Device may be for example any kind of beam limiting device like a wedge tray or an electron applicator. + An RT Accessory Device may be mounted in or on an RT Accessory Holder which is a specific RT Accessory Device. See . + If this RT Accessory Holder does not provide slots, the RT Accessory Holder is referred to by Referenced RT Accessory Holder Device Index (300A,060E), for example, a block tray for a block. + If the RT Accessory Holder provides slots these are referred to by Referenced RT Accessory Holder Device Index (300A,060E) and RT Accessory Holder Slot ID (300A,0611), for example, an electron applicator holding a block tray. + Any RT Accessory Device may either be mounted in an RT Accessory Device Slot or on an RT Accessory Device Holder. Thus, for any RT Accessory Device the Referenced RT Accessory Holder Device Index (300A,060E) and RT Accessory Holder Slot ID (300A,0611) are mutually exclusive.
RT Treatment Position Macro - The RT Treatment Position Macro establishes a connection between the patients geometry and the treatment delivery equipment to define the treatment position. When used in an RT Radiation object, this treatment position is the prescribed position. When used in an RT Radiation Record object, this treatment position is the record of the actual position. + + specifies the Attributes of the , which establish a connection between the patients geometry and the treatment delivery equipment to define the treatment position. When used in an RT Radiation object, this treatment position is the prescribed position. When used in an RT Radiation Record object, this treatment position is the record of the actual position. @@ -276954,7 +280181,7 @@ @@ -277007,7 +280234,8 @@
RT Control Point General Macro - This Macro specifies the base Attributes for the definition of an RT Radiation Control Point. + + specifies the Attributes of the , which specifiy the base Attributes for the definition of an RT Radiation Control Point.
RT Treatment Position Macro Attributes
- + Include .
@@ -277120,11 +280348,11 @@
Requirements for Changing Values within RT Control Point Sequence Attributes - This Section specifies when individual attributes shall be present in a Sequence. + This Section specifies when individual Attributes shall be present in a Sequence. The RT Control Point Sequence specifies a certain order of execution. - At each RT Control Point the value of various Attributes may be specified as an explicit value (which in the case of a type 2C attribute may be a null value) and if absent remain at the same value as specified previously. There are physical and mechanical implications of specifying a new value as opposed to staying at the same value, for example gear lash, floating point jitter, etc. + At each RT Control Point the value of various Attributes may be specified as an explicit value (which in the case of a type 2C Attribute may be a null value) and if absent remain at the same value as specified previously. There are physical and mechanical implications of specifying a new value as opposed to staying at the same value, for example gear lash, floating point jitter, etc. At the first Sequence Item in RT Control Point Sequences (i.e., with an RT Control Point Index (300A,0600) equal to 1) all Attributes affected by this Section shall be present if applicable conditions are met. - For Sequence Items other than the first Sequence Item, Attributes shall be present if applicable conditions are met and the value is different from the previously populated value for the same Attribute (in the case of a type 2C attribute, a null value is considered as a value). The previously populated value is the value from the Item where the Attribute was present with the greatest value of RT Control Point Index (300A,0600) less than the value of the RT Control Point Index (300A,0600) in the current Item. + For Sequence Items other than the first Sequence Item, Attributes shall be present if applicable conditions are met and the value is different from the previously populated value for the same Attribute (in the case of a type 2C Attribute, a null value is considered as a value). The previously populated value is the value from the Item where the Attribute was present with the greatest value of RT Control Point Index (300A,0600) less than the value of the RT Control Point Index (300A,0600) in the current Item. This means that for an Item in which an Attribute is absent, the application stays at the value of the previously populated Item. For Sequences inside a RT Control Point Sequence Item, the Sequence shall be present if any of the nested Attributes affected by this Section differ from the corresponding previously populated Item. For multi-valued Attributes, such as Parallel RT Beam Delimiter Positions (300A,064A), all values shall be present if any value changes. @@ -277436,13 +280664,14 @@
Cumulative Meterset - The Meterset at a given Control Point is specified by Cumulative Meterset (300A,063C). This value is specified in units defined by Radiation Dosimeter Unit Sequence (300A,0658) in the RT Delivery Device Common Module in . The Meterset values are intended to correspond to the values produced by the primary or the single Meterset-measuring device of a RT Radiation Delivery Device. + The Meterset at a given Control Point is specified by Cumulative Meterset (300A,063C). This value is specified in units defined by Radiation Dosimeter Unit Sequence (300A,0658) in the . The Meterset values are intended to correspond to the values produced by the primary or the single Meterset-measuring device of a RT Radiation Delivery Device.
External Beam Control Point General Macro - This Macro specifies the RT Control Point Attributes used to model external beam radiation. + + specifies the Attributes of the , which specify the RT Control Point Attributes used to model external beam radiation.
RT Control Point General Macro Attributes
@@ -277481,7 +280710,7 @@ @@ -277545,7 +280774,8 @@
Radiation Generation Mode Macro - The Radiation Generation Mode Macro contains Attributes required to generate radiation by a delivery device. + + specifies the Attributes of the , which are required to generate radiation by a delivery device. Treatment devices can produce a multitude of different beams with properties such as energy spectrum, depth dose, surface dose and beam profile. A particular combination of such properties is referred to as a Radiation Generation Mode. Such Radiation Generation Modes are created by the machine by using different primary electron/particle beams, flattening and scattering filters, etc., creating a specific physical and geometric distribution of radiation. In many cases the Radiation Generation Mode characterizes the fluence just below the Monitor Chamber. Subsequently these primary beams may be modulated by beam modifiers such as Beam Limiting Devices, Wedges, Spreaders etc. While these beam modifiers are described in the Control Point Sequence, the primary beam is assumed to have fixed characteristics. In many cases, the Radiation Generation Mode will be constant throughout the radiation. Radiation Generation Modes specify the beam fluence. To convey content other than the beam fluence, such as annotating the role of the beam in the clinical process or the usage of that beam during a treatment session, annotate treatment constraints, use other Attributes like RT Radiation Set Intent (300A,0637) in the and information provided by the workflow protocols.
External Beam Control Point General Macro Attributes
The value of the intended nominal rate of delivery of the specified Cumulative Meterset (300A,063C). - The units are defined in the Delivery Rate Unit Sequence (300A,063E). + The units are defined in the Delivery Rate Unit Sequence (300A,063E). Required if the conditions in are satisfied. See .
@@ -277807,6 +281037,7 @@ @@ -277818,31 +281049,37 @@
Keys identifying the configuration and commissioning data used as input for treatment planning of this Instance. Value Type (0040,A040) is constrained to value UIDREF. + See . Zero or more Items shall be included in this Sequence.
- No Baseline CID defined. + No Baseline TID defined.
- Radiation Generation Mode Macro Attribute Description + Radiation Generation Mode Macro Attribute Descriptions
Energy Attributes The Nominal Energy (300A,0680) parameter is provided for beams where a single discrete energy is annotated by that value. Energy modulation can be used at the Control Point level (both discrete and continuous), in which case the Minimal Nominal Energy (300A,0681) and Maximal Nominal Energy (300A,0682) are used.
Radiation Generation Mode Machine Code - When two Radiation Generation Modes differ in any value of Nominal Energy (300A,0680), Minimum Nominal Energy (300A,0681), Maximum Nominal Energy (300A,0682) or any code value(s) of the Radiation Type Code Sequence (300A,067F) or the Radiation Fluence Modifier Code Sequence(300A,0683), the Radiation Generation Modes must have different values for Radiation Generation Mode Machine Code. Even if all those attributes have the same values, the two modes may still have a different value for Radiation Generation Mode Machine Code, e.g., when other device-specific beam generation steering parameters differ. + When two Radiation Generation Modes differ in any value of Nominal Energy (300A,0680), Minimum Nominal Energy (300A,0681), Maximum Nominal Energy (300A,0682) or any code value(s) of the Radiation Type Code Sequence (300A,067F) or the Radiation Fluence Modifier Code Sequence(300A,0683), the Radiation Generation Modes must have different values for Radiation Generation Mode Machine Code. Even if all those Attributes have the same values, the two modes may still have a different value for Radiation Generation Mode Machine Code, e.g., when other device-specific beam generation steering parameters differ.
Radiation Generation Mode Label - Radiation Generation Mode Label (300A,067C) should uniquely identify a specific mode within a treatment device. The label is intended only for display to human readers, while the authoritative definition of the Radiation Generation Mode is contained in the other attributes of the Sequence. + Radiation Generation Mode Label (300A,067C) should uniquely identify a specific mode within a treatment device. The label is intended only for display to human readers, while the authoritative definition of the Radiation Generation Mode is contained in the other Attributes of the Sequence. +
+
+ Radiation Device Configuration and Commissioning Key Sequence + The Radiation Device Configuration and Commissioning Key Sequence (300A,065A) has no TID defined, as it is intended that the codes for the UIDs that are defined are vendor-specific and also specific to actual installations. + For example, vendor A may provide a UID to identify specific beam parameter measurements used during creation of the Instance. Vendor B may provide a UID for a specific treatment machine configuration currently active for a certain treatment device.
RT Beam Limiting Devices Definition Macro - This Macro describes the configuration of Beam Limiting Devices which cannot vary during delivery. + + specifies the Attributes of the , which describe the configuration of Beam Limiting Devices which cannot vary during delivery. @@ -278198,7 +281435,7 @@
RT Beam Limiting Device Proximal Distance and RT Beam Limiting Device Distal Distance - shows the RT Beam Limiting Device Proximal Distance (300A,0642) and RT Beam Limiting Device Distal Distance (300A,0643). + shows the RT Beam Limiting Device Proximal Distance (300A,0642) and RT Beam Limiting Device Distal Distance (300A,0643). In this example the reference location specified by the RT Device Distance Reference Location Code Sequence (300A,0659) has the value (130358, DCM, "Nominal Radiation Source Location").
@@ -278243,7 +281480,8 @@
RT Beam Limiting Device Opening Macro - This Macro defines the opening created by RT Beam Limiting Devices at a specific Control Point or set of Control Points. + + specifies the Attributes of the , which define the opening created by RT Beam Limiting Devices at a specific Control Point or set of Control Points.
RT Beam Limiting Devices Definition Macro Attributes
@@ -278378,7 +281616,7 @@
RT Beam Limiting Device Opening Macro Attributes
- RT Beam Limiting Device Opening Attribute Descriptions + RT Beam Limiting Device Opening Macro Attribute Descriptions
Geometric Value Attributes All geometric values in are defined in the Beam Modifier Definition Plane. @@ -278398,7 +281636,8 @@
Wedges Definition Macro - This Macro defines the geometric configuration elements which cannot vary during delivery. + + specifies the Attributes of the , which define the geometric configuration elements which cannot vary during delivery. @@ -278575,7 +281814,8 @@
Wedge Positions Macro - This Macro defines the positions of Wedges used in a specific Control Point or set of Control Points. + + specifies the Attributes of the , which define the positions of Wedges used in a specific Control Point or set of Control Points.
Wedges Definition Macro Attributes
@@ -278715,7 +281955,8 @@
Compensators Definition Macro - This Macro defines the geometric configuration elements which cannot vary during delivery. + + specifies the Attributes of the , which define the geometric configuration elements which cannot vary during delivery.
Wedge Positions Macro Attributes
@@ -279041,7 +282282,8 @@
Blocks Definition Macro - This Macro defines the geometric configuration elements which cannot vary during delivery. + + specifies the Attributes of the , which define the geometric configuration elements which cannot vary during delivery.
Compensators Definition Macro Attributes
@@ -279104,7 +282346,7 @@ D. - The Device Alternate Identifier (3010,001B) Attribute of the RT Accessory Device Identification Macro shall not contain a value when the Number of Block Slab Items (300A,0440) is non-zero. + The Device Alternate Identifier (3010,001B) Attribute of the shall not contain a value when the Number of Block Slab Items (300A,0440) is non-zero. @@ -279312,7 +282554,7 @@ >>Block Slab Number
Blocks Definition Macro Attributes
- (300A,0043) + (300A,0443) 1 @@ -279403,7 +282645,8 @@
RT Accessory Holders Definition Macro - This Macro defines the geometric configuration elements which cannot vary during delivery and which are used to hold accessories such as blocks or compensators. + + specifies the Attributes of the , which define the geometric configuration elements which cannot vary during delivery and which are used to hold accessories such as blocks or compensators. @@ -279608,9 +282851,7 @@
RT Accessory Holders Definition Macro Attributes
RT Accessory Holders Description - In addition to RT Accessory Device Slots that are mounted directly on the treatment delivery unit, - a treatment delivery unit may also allow the attachment of one or more accessory holders within which the user may install various devices for applying the beam to the patient, see . - Treatment accessory devices may include, but not be limited to, one or more of the following items: + In addition to RT Accessory Device Slots that are mounted directly on the treatment delivery unit, a treatment delivery unit may also allow the attachment of one or more accessory holders within which the user may install various devices for applying the beam to the patient, see . Treatment accessory devices may include, but not be limited to, one or more of the following items: custom blocks on a block tray for patient-specific lateral collimation (beam limiting), @@ -279640,22 +282881,16 @@ applicator sealer for preventing fluids from entering the applicator. - The following example illustrates the use of the RT Accessory Holders Macro and the RT Accessory Device Identification Macro: + The following example illustrates the use of the and the : The gantry head has an RT Accessory Device Slot ID called Acc Mount. - In this example, an electron applicator is mounted in that RT Accessory Device Slot. - The electron applicator itself has an RT Accessory Holder Slot called E Aperture, where other accessories can be mounted. - Therefore, the electron applicator is an RT Accessory Holder, - which includes an RT Accessory Holder Slot Sequence (300A,06010) Item to model that RT Accessory Holder Slot, - identified by an RT Accessory Holder Slot ID (300A,0611). + In this example, an electron applicator is mounted in that RT Accessory Device Slot. The electron applicator itself has an RT Accessory Holder Slot called E Aperture, where other accessories can be mounted. Therefore, the electron applicator is an RT Accessory Holder, which includes an RT Accessory Holder Slot Sequence (300A,06010) Item to model that RT Accessory Holder Slot, identified by an RT Accessory Holder Slot ID (300A,0611). - In this example, a block tray is mounted in the E Aperture RT Accessory Holder Slot. - The block tray can support blocks, therefore it is an RT Accessory Holder, but the RT Accessory Holder Slot Sequence (300A,0610) is absent in the block tray definition, - since the tray has no RT Accessory Holder Slots. + In this example, a block tray is mounted in the E Aperture RT Accessory Holder Slot. The block tray can support blocks, therefore it is an RT Accessory Holder, but the RT Accessory Holder Slot Sequence (300A,0610) is absent in the block tray definition, since the tray has no RT Accessory Holder Slots. The block is an RT Accessory Device, which is mounted in the block tray. @@ -279677,7 +282912,8 @@
General Accessories Definition Macro - This Macro defines the geometric configuration elements which cannot vary during delivery. + + specifies the Attributes of the , which define the geometric configuration elements which cannot vary during delivery. @@ -279792,7 +283028,8 @@
Boluses Definition Macro - This Macro defines the geometric configuration elements which cannot vary during delivery. + + specifies the Attributes of the , which define the geometric configuration elements which cannot vary during delivery.
General Accessories Definition Macro Attributes
@@ -279916,14 +283153,15 @@ Boluses Definition Macro Attribute Description
Conceptual Volume Sequence - The Conceptual Volume Sequence (3010,0025), if present, identifies the segmented Conceptual Volume used to define the bolus. The segment is defined by the Referenced Segment Reference Index (3010,0020) in the Conceptual Volume Segmentation Reference and Combination Macro (see ). + The Conceptual Volume Sequence (3010,0025), if present, identifies the segmented Conceptual Volume used to define the bolus. The segment is defined by the Referenced Segment Reference Index (3010,0020) in the . Alternatively, the bolus may not be associated with a Conceptual Volume. For example, a bolus may cover the entire area of radiation and not require a specific segmentation for definition.
RT Tolerance Set Macro - The RT Tolerance Set Macro contains information describing the maximum differences between planned and delivered values. This information is used in the context of delivery of the RT Radiation Set. If the absolute difference between a planned and delivered value exceeds the tolerance value, then it is expected that the delivery of the RT Radiation Set will be inhibited unless an authorized operator confirms that the tolerance may be exceeded. + + specifies the Attributes of the , which contain information describing the maximum differences between planned and delivered values. This information is used in the context of delivery of the RT Radiation Set. If the absolute difference between a planned and delivered value exceeds the tolerance value, then it is expected that the delivery of the RT Radiation Set will be inhibited unless an authorized operator confirms that the tolerance may be exceeded.
Boluses Definition Macro Attributes
@@ -279969,8 +283207,8 @@ @@ -279993,7 +283231,7 @@ 1 @@ -280132,137 +283370,311 @@ RT Tolerance Set Attribute Description
Attribute Tolerance Values Sequence - The Attribute Tolerance Values Sequence (300A,062B) allows for the reference to any numerical parameter in an RT Radiation IOD. The RT Tolerance Set Macro is invoked to specify a tolerance value for this parameter. The reference specification is conveyed by the Selector Attribute Macro, which allows reference to a tag on any level of nested Sequences, and to refer to specific Items in the Sequence. The unit of the tolerance value is the unit as specified by the data element tag referenced in the Selector Attribute (0072,0026). + The Attribute Tolerance Values Sequence (300A,062B) allows for the reference to any numerical parameter in an RT Radiation IOD. The is invoked to specify a tolerance value for this parameter. The reference specification is conveyed by the , which allows reference to a tag on any level of nested Sequences, and to refer to specific Items in the Sequence. The unit of the tolerance value is the unit as specified by the data element tag referenced in the Selector Attribute (0072,0026).
Patient Support Position Tolerance Sequence - When describing a tolerance for a specific patient support position value, the patient support device parameter is defined using the same code used in the Patient Support Position Macro in . + When describing a tolerance for a specific patient support position value, the patient support device parameter is defined using the same code used in the .
+
+ Interlock Macro + + specifies the Attributes of the . +
RT Tolerance Set Macro Attributes
Tolerance values representing the allowed difference between the planned and actual values. - The Selector Attribute Macro identifies the Attributes for which the tolerances are specified. - Required if a tolerance value is specified for at least one Attribute which can be referenced by the Selector Attribute Macro. + The identifies the Attributes for which the tolerances are specified. + Required if a tolerance value is specified for at least one Attribute which can be referenced by the . See . Zero or more Items shall be included in this Sequence. - Maximum permitted difference between the planned and the delivered value. Units are those specified for the corresponding Attribute referenced by the Selector Attribute Macro. + Maximum permitted difference between the planned and the delivered value. Units are those specified for the corresponding Attribute referenced by the .
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Interlock Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Interlock DateTime + + (300A,0741) + + 1 + + Date and Time when the Interlock occurred. + The date and time of occurrence may be when the interlock occurred (e.g. by a real-time system) or when the interlock was recorded. + See . +
+ Interlock Description + + (300A,0742) + + 1 + + User-readable description of the interlock. +
+ Interlock Origin Description + + (300A,0783) + + 1C + + Description of the origin of the interlock. + Required if Interlock Originating Device Sequence (300A,0743) is not present. +
+ Interlock Originating Device Sequence + + (300A,0743) + + 1C + + Contains the attributes that identify the device that originated the interlock. + Only a single Item shall be included in this Sequence. + Required if Interlock Origin Description (300A,0783) is not present. +
+ + >Include + + + + No Baseline CID is defined. +
+ Interlock Code Sequence + + (300A,0744) + + 1 + + Code(s) that describe the interlock(s) that occurred. + One or more Items shall be included in this Sequence. +
+ + >Include + + + + B. +
+ Interlock Resolution Code Sequence + + (300A,0745) + + 1 + + The action applied to resolve the interlock. + One or more Items shall be included in this Sequence. +
+ + >Include + + + + D. +
+ Interlock Resolution User Sequence + + (300A,0746) + + 2 + + The user that resolved the interlock. + Zero or more Items shall be included in this Sequence. +
+ + >Include + + +
+
RT Second Generation Positioning Macros
RT Patient Position Scope Macro - The RT Patient Position Scope Macro defines the RT Radiation Set, RT Radiation Instances or the Treatment Position Groups to which a set of positioning parameters apply. + + specifies the Attributes of the , which define the RT Radiation Set, RT Radiation Instances or the Treatment Position Groups to which a set of positioning parameters apply. @@ -280270,183 +283682,184 @@
RT Patient Position Macro - The RT Patient Position Macro defines a patient position in a treatment delivery or imaging session. This patient position may be specified as an absolute position of the patient positioning device or as relative displacement against a specified reference location. - The patient position may be based on recorded positions used in previous treatment sessions, or based on a position marked on the patient during a CT acquisition prior to treatment planning and delivery, or on other procedures. - The patient position approximates the desired patient position during radiation delivery. These attributes do not affect the original spatial relationship between the RT Radiations and the planning image patient anatomy. + + specifies the Attributes of the , which define a patient position in a treatment delivery or imaging session. This patient position may be specified as an absolute position of the patient positioning device or as relative displacement against a specified reference location. + The patient position may be based on recorded positions used in previous treatment sessions, or based on a position marked on the patient during a CT acquisition prior to treatment planning and delivery, or on other procedures. + The patient position approximates the desired patient position during radiation delivery. These Attributes do not affect the original spatial relationship between the RT Radiations and the planning image patient anatomy.
RT Patient Position Scope Macro Attributes
- Attribute Name + Attribute Name - Tag + Tag - Type + Type - Attribute Description + Attribute Description
- Referenced RT Radiation Sequence + Referenced RT Radiation Sequence - (300A,0630) + (300A,0630) - 1C + 1C - A set of RT Radiation Instances for which the positioning parameters apply. - Required if Referenced RT Radiation Set Sequence (300A,0702) is absent. - One or more Items shall be included in this Sequence. + A set of RT Radiation Instances for which the positioning parameters apply. + Required if Referenced RT Radiation Set Sequence (300A,0702) is absent. + One or more Items shall be included in this Sequence.
- + >Include .
- Referenced RT Radiation Set Sequence + Referenced RT Radiation Set Sequence - (300A,0702) + (300A,0702) - 1C + 1C - A collection of RT Radiation Sets for which the positioning parameters apply.. - Required if Referenced RT Radiation Sequence (300A,0630) is absent. - One or more Items shall be included in this Sequence. + A collection of RT Radiation Sets for which the positioning parameters apply.. + Required if Referenced RT Radiation Sequence (300A,0630) is absent. + One or more Items shall be included in this Sequence.
- + >Include .
- >Referenced RT Radiation Sequence + >Referenced RT Radiation Sequence - (300A,0630) + (300A,0630) - 1C + 1C - A subset of the SOP Instances referenced in the RT Radiation Set SOP Instance for which the parameters apply. - Required if Treatment Position Group Sequence (300A,060A) is absent and the scope is limited to a subset of RT Radiation SOP Instances of the referenced RT Radiation Set. - One or more Items shall be included in this Sequence. The maximum number of Items is one less than the number of RT Radiation SOP Instances in the referenced RT Radiation Set SOP Instance. + A subset of the SOP Instances referenced in the RT Radiation Set SOP Instance for which the parameters apply. + Required if Treatment Position Group Sequence (300A,060A) is absent and the scope is limited to a subset of RT Radiation SOP Instances of the referenced RT Radiation Set. + One or more Items shall be included in this Sequence. The maximum number of Items is one less than the number of RT Radiation SOP Instances in the referenced RT Radiation Set SOP Instance.
- + >>Include .
- >Treatment Position Group Sequence + >Treatment Position Group Sequence - (300A,060A) + (300A,060A) - 1C + 1C - Treatment Position Groups defining patient positions for which the parameters apply. - Required if Referenced RT Radiation Sequence (300A,0630) is absent and Treatment Position Groups to which the positioning parameters apply are defined in the referenced RT Radiation Set. - One or more Items shall be included in this Sequence. - See . + Treatment Position Groups defining patient positions for which the parameters apply. + Required if Referenced RT Radiation Sequence (300A,0630) is absent and Treatment Position Groups to which the positioning parameters apply are defined in the referenced RT Radiation Set. + One or more Items shall be included in this Sequence. + See .
- >>Referenced Treatment Position Group UID + >>Referenced Treatment Position Group UID - (300A,0785) + (300A,0785) - 1 + 1 - Referenced unique identifier of the Treatment Position Group. + Referenced unique identifier of the Treatment Position Group.
@@ -280457,17 +283870,17 @@ RT Patient Position Macro Attribute Descriptions
RT Patient Position Sequences - This Sequence communicates a patient position as defined by the Image to Equipment Mapping Matrix (0028,9520) and may additionally contain native device parameters displayed to the user. + This Sequence communicates a patient position as defined by the Image to Equipment Mapping Matrix (0028,9520) and may additionally contain native device parameters displayed to the user.
RT Patient Position Displacement Sequence - This Sequence communicates a patient position by specifying a displacement of the position with respect to a reference location. The reference location may be, for example, a set of skin markers used to align the patient using room lasers. - The Displacement Matrix (300A,079B) describes a relative displacement in the Patient Frame of Reference. The Patient Frame of Reference is aligned with the coordinate system of the patient support system (i.e., the axes are parallel). This specification is independent of the mechanical nature and readout of the patient support device. The calculation of the native parameters for the patient support system is specific to the current device. + This Sequence communicates a patient position by specifying a displacement of the position with respect to a reference location. The reference location may be, for example, a set of skin markers used to align the patient using room lasers. + The Displacement Matrix (300A,079B) describes a relative displacement in the Patient Frame of Reference. The Patient Frame of Reference is aligned with the coordinate system of the patient support system (i.e., the axes are parallel). This specification is independent of the mechanical nature and readout of the patient support device. The calculation of the native parameters for the patient support system is specific to the current device.
Patient Support Displacement Sequence - The Displacement Matrix (300A,079B) is the exclusive source of information to define the displacement. Positioning devices will solely derive the displacement from this matrix. - Some applications, which do not act as positioning devices and cannot decompose the Displacement Matrix (300A,079B) into device-specific parameters, may want to informatively display device-specific parameters to the user. The purpose of the Patient Support Displacement Sequence (300A,079C) is to facilitate such display. The Patient Support Displacement Sequence (300A,079C) is not a substitute for the Displacement Matrix (300A,079B). + The Displacement Matrix (300A,079B) is the exclusive source of information to define the displacement. Positioning devices will solely derive the displacement from this matrix. + Some applications, which do not act as positioning devices and cannot decompose the Displacement Matrix (300A,079B) into device-specific parameters, may want to informatively display device-specific parameters to the user. The purpose of the Patient Support Displacement Sequence (300A,079C) is to facilitate such display. The Patient Support Displacement Sequence (300A,079C) is not a substitute for the Displacement Matrix (300A,079B).
@@ -280475,9 +283888,9 @@
Enhanced RT Series Module - The RT Second Generation IODs use the General Series Module described in , specialized by the Enhanced RT Series Module. - specifies the Attributes that identify and describe general information about the Enhanced RT Series. + specifies the Attributes of the , which identify and describe general information about the Enhanced RT Series. + The RT Second Generation IODs use the , specialized by this Module.
RT Patient Position Macro Attributes
- Attribute Name + Attribute Name - Tag + Tag - Type + Type - Attribute Description + Attribute Description
- + Include .
- RT Patient Position Sequence + RT Patient Position Sequence - (300A,0799) + (300A,0799) - 2C + 2C - Definition of patient position. - See . - Required if RT Patient Position Displacement Sequence (300A,0798) is absent. - Zero or one Item shall be included in this Sequence. + Definition of patient position. + See . + Required if RT Patient Position Displacement Sequence (300A,0798) is absent. + Zero or one Item shall be included in this Sequence.
- + >Include . - + D.
- RT Patient Position Displacement Sequence + RT Patient Position Displacement Sequence - (300A,0798) + (300A,0798) - 2C + 2C - Displacement of the patient position. - See . - Required if RT Patient Position Sequence (300A,0799) is absent. - Zero or one Item shall be included in this Sequence. + Displacement of the patient position. + See . + Required if RT Patient Position Sequence (300A,0799) is absent. + Zero or one Item shall be included in this Sequence.
- >Displacement Reference Label + >Displacement Reference Label - (300A,079A) + (300A,079A) - 3 + 3 - A user-defined label describing the reference location used for a displacement of the patient’s treatment position. + A user-defined label describing the reference location used for a displacement of the patient’s treatment position.
- >Displacement Reference Location Code Sequence + >Displacement Reference Location Code Sequence - (300A,079D) + (300A,079D) - 1 + 1 - The reference location with respect to which the displacement is provided. + The reference location with respect to which the displacement is provided.
- + >>Include . - + D.
- >Conceptual Volume Sequence + >Conceptual Volume Sequence - (3010,0025) + (3010,0025) - 2 + 2 - References a Conceptual Volume that describes the geometry and properties of the Displacement Reference. - See . - Zero or one Item shall be included in this Sequence. + References a Conceptual Volume that describes the geometry and properties of the Displacement Reference. + See . + Zero or one Item shall be included in this Sequence.
- + >>Include .
- >Displacement Matrix + >Displacement Matrix - (300A,079B) + (300A,079B) - 1 + 1 - A rigid, homogeneous 4x4 transformation matrix that expresses the patient’s treatment position displacement in the patient coordinate space. Matrix elements shall be listed in row-major order. - See . + A rigid, homogeneous 4x4 transformation matrix that expresses the patient’s treatment position displacement in the patient coordinate space. Matrix elements shall be listed in row-major order. + See .
- >Patient Support Displacement Sequence + >Patient Support Displacement Sequence - (300A,079C) + (300A,079C) - 2 + 2 - evice-specific positioning parameters, derived from the Displacement Matrix (300A,079B). - See . - Zero or one Item shall be included in this Sequence. + evice-specific positioning parameters, derived from the Displacement Matrix (300A,079B). + See . + Zero or one Item shall be included in this Sequence.
- + >>Include . - + D.
@@ -280587,10 +284000,10 @@
Enhanced RT Series Module Attributes
- Enhanced RT Series Attribute Descriptions + Enhanced RT Series Module Attribute Descriptions
Modality - The Modality (0008,0060) is defined for each IOD including the Enhanced RT Series Module. + The Modality (0008,0060) is defined for each IOD including this Module. Enumerated Values: @@ -280614,9 +284027,9 @@ PLAN - Plan + Plan - The term "PLAN" denotes Series describing planned activities. It is not be confused with radiotherapy treatment plans. + The term "PLAN" denotes Series describing planned activities. It is not be confused with radiotherapy treatment plans. @@ -280626,8 +284039,8 @@
Radiotherapy Common Instance Module - - specifies the Attributes that identify and describe general information in RT Second Generation IODs. + + specifies the Attributes of the , which identify and describe general information in RT Second Generation IODs. @@ -280767,7 +284180,8 @@
RT Physician Intent Module - The RT Physician Intent Module contains information about the overall intent of the treatment. The content is mostly descriptive text and allows for the presence of unstructured advice by the physician along the established nomenclature of the actual institution. + + specifies the Attributes of the , which contain information about the overall intent of the treatment. The content is mostly descriptive text and allows for the presence of unstructured advice by the physician along the established nomenclature of the actual institution.
Radiotherapy Common Instance Module Attributes
@@ -280898,7 +284312,7 @@ @@ -280907,7 +284321,7 @@ >>Treatment Site Modifier Code Sequence
RT Physician Intent Module Attributes
- No Baseline CID is defined. + B.
- (3010,0078) + (3010,0089) 3 @@ -281127,7 +284541,7 @@
- RT Physician Intent Attribute Descriptions + RT Physician Intent Module Attribute Descriptions
RT Physician Intent Sequence The RT Physician Intent Sequence (3010,0057) allows one or more clinical intents to be identified for treatment in a treatment course. For example, the simultaneous treatment of multiple primary targets may require separate intents to be defined, each with its own prescription(s) and having different sets of reference imaging studies. @@ -281138,7 +284552,7 @@
RT Physician Intent Input Instance Sequence - The purpose of this Sequence is to reference all the Instances that have been used by the RT Physician to establish the Intent. It may include the Images that were used in the treatment planning process, which are also referenced in the Planning Input Information Sequence (3010,0076) of the RT Enhanced Prescription Module. + The purpose of this Sequence is to reference all the Instances that have been used by the RT Physician to establish the Intent. It may include the Images that were used in the treatment planning process, which are also referenced in the Planning Input Information Sequence (3010,0076) of the . When there are multiple Purposes of References, one Item will be included for each purpose.
@@ -281149,7 +284563,8 @@
RT Enhanced Prescription Module - The RT Enhanced Prescription Module describes the delivery objectives and labels for intended treatment for a specific target, as defined by the physician. + + specifies the Attributes of the , which describe the delivery objectives and labels for intended treatment for a specific target, as defined by the physician. @@ -281242,7 +284657,7 @@ @@ -282015,7 +285430,7 @@ @@ -282129,47 +285544,10 @@
RT Enhanced Prescription Module Attributes
The value of the RT Prescription Index (3010,003C) corresponding to a prescription that is the parent prescription to this one. - This attribute shall reference a Prescription that contains Referenced RT Physician Intent Index (3010,005E). + This Attribute shall reference a Prescription that contains Referenced RT Physician Intent Index (3010,005E). Required if the Referenced RT Physician Intent Index (3010,005E) is absent. See .
- + >>Include .
- RT Enhanced Prescription Attribute Descriptions + RT Enhanced Prescription Module Attribute Descriptions
Therapeutic Role Type Code Sequence - The Therapeutic Role Type Code Sequence (3010,0065) further specifies the role of the anatomy along the Therapeutic Role Category (3010,0064). describes the codes permitted in the Therapeutic Role Type Code Sequence (3010,0065), when the code used in the Therapeutic Role Category Code Sequence (3010,0064) is as specified. - - - - - - - - - - - - - - - - - - -
Therapeutic Role Type Codes
- Code Value of Therapeutic Role Category Sequence (3010,0064) - - Context Group for Therapeutic Role Property Type Sequence (3010,0065) -
- - (130041, DCM, "RT Target") - - - D - -
- - (130042, DCM, "RT Dose Calculation Structure") - - - D - -
+ The Therapeutic Role Type Code Sequence (3010,0065) further specifies the role of the anatomy along the Therapeutic Role Category Code Sequence (3010,0064). The CID for Therapeutic Role Type Code Sequence (3010,0065) shall correspond to the CID defined in for each value in Therapeutic Role Category Code Sequence (3010,0064).
Conceptual Volume Type Code Sequence @@ -282237,7 +285615,7 @@
Conceptual Volume Sequence - The Conceptual Volume Sequence (3010,0025) identifies the Conceptual Volume associated with an RT Anatomy Prescription Item. If the Conceptual Volume is associated with a segment, the segment is defined by the Referenced Segment Reference Index (3010,0020) in the Conceptual Volume Reference Combination and Segmentation Macro (see ). Alternatively, the anatomy volume may not (yet) be associated with a segment. For example, an initial prescription may be entered prior to the definition of an organ at risk. + The Conceptual Volume Sequence (3010,0025) identifies the Conceptual Volume associated with an RT Anatomy Prescription Item. If the Conceptual Volume is associated with a segment, the segment is defined by the Referenced Segment Reference Index (3010,0020) in the . Alternatively, the anatomy volume may not (yet) be associated with a segment. For example, an initial prescription may be entered prior to the definition of an organ at risk.
Fraction-based Relationship Sequence @@ -282260,7 +285638,7 @@
Parent RT Prescription - The RT Enhanced Prescription Module supports a two-level prescription model (see ) in order to document an approach where a high-level prescription is created and then more details may be added. The first level would typically be created during the time of prescription definition with only high-level prescription information based on the RT Physician Intent. The second level, if present, would represent a derived prescription containing more detailed information, such as constraints and objectives. A third or subsequent levels are not permitted. + The supports a two-level prescription model (see ) in order to document an approach where a high-level prescription is created and then more details may be added. The first level would typically be created during the time of prescription definition with only high-level prescription information based on the RT Physician Intent. The second level, if present, would represent a derived prescription containing more detailed information, such as constraints and objectives. A third or subsequent levels are not permitted.
Parent and Child RT Prescriptions @@ -282363,7 +285741,8 @@
RT Segment Annotation Module - The RT Segment Annotation Module references segments and provides radiotherapy-specific annotations for them. The geometry of each segment is defined by a referenced Segmentation, Surface Segmentation, RT Structure Set or any other general-purpose Instance that represents geometric information. + + specifies the Attributes of the , which reference segments and provide radiotherapy-specific annotations for them. The geometry of each segment is defined by a referenced Segmentation, Surface Segmentation, RT Structure Set or any other general-purpose Instance that represents geometric information. The values of the following Attribute shall take precedence over values in the referenced SOP Instances: @@ -282731,114 +286110,10 @@
- RT Segment Annotation Attribute Descriptions + RT Segment Annotation Module Attribute Descriptions
RT Segment Annotation Type Code Sequence - In , if the Segment Annotation Category Code Sequence (3010,002B) has the code value specified in the left column, the Context Group for Segment Annotation Type Code Sequence (3010,002C) shall be the one specified in the right column. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
RT Segment Annotation Type CIDs
- Code Value of Segment Annotation Category Code Sequence (3010,002B) - - Context Group for Segment Annotation Type Code Sequence (3010,002C) -
- - (130041, DCM, "RT Target") - - - D - -
- - (130042, DCM, "RT Dose Calculation Structure") - - - D - -
- - (130043, DCM, "RT Geometric Information") - - - D - -
- - (130047, DCM, "External Body Model") - - - D - -
- - (130405, DCM, "Patient-Attached Dose Control Object") - - - D - -
- - (130044, DCM, "Fixation or Positioning Device") - - - D - -
- - (130045, DCM, "Brachytherapy Device") - - - D - -
- - (130046, DCM, "Non-specific Volume") - - - D - -
- For code values in Segment Annotation Category Code Sequence (3010,002B) that are not present in , Segment Annotation Type Code Sequence (3010,002C) B may be used where applicable. + The CID for Segment Annotation Type Code Sequence (3010,002C) shall correspond to the CID defined in Segment Annotation Type and RT ROI Identification Context Group in for each value in Segment Annotation Category Code Sequence (3010,002B).
Segmented RT Accessory Device Sequence @@ -282868,7 +286143,8 @@
Segment Reference Module - The Segment Reference Module references geometrical representations, such as regions of interest, surfaces, lines, or points, which have been associated with a Conceptual Volume. + + specifies the Attributes of the , which reference geometrical representations, such as regions of interest, surfaces, lines, or points, which have been associated with a Conceptual Volume. These referenced representations are referred to as segments. @@ -283163,7 +286439,7 @@
Segment Reference Module Attributes
- Segment Reference Attribute Descriptions + Segment Reference Module Attribute Descriptions
Segmentation SOP Instance Reference Sequence Only the SOP Classes contained in shall be referenced. @@ -283273,12 +286549,12 @@
The column Referenced Attribute identifies the Attribute used to identify the geometric representation in the SOP Instance referenced in the Segmentation Referenced SOP Sequence (0008,1199). - Depending on the SOP Class UID (0008,0016) in the Referenced SOP Sequence (0008,1199) the corresponding attribute as specified in the Required Referencing Attribute column is required to be present. + Depending on the SOP Class UID (0008,0016) in the Referenced SOP Sequence (0008,1199) the corresponding Attribute as specified in the Required Referencing Attribute column is required to be present. It is anticipated that in future additional referencing Attributes may be needed to accommodate new representations of segmentations. Hence the collection of Required Referencing Attributes in and the conditionally required Type 1C Attributes in the Segment Reference Module may be extended.
Combination Segment Reference Sequence - A Conceptual Volume may be expressed as a combination of other segmented Conceptual Volumes. Those other segments are referenced in the Conceptual Volume Segmentation Reference and Combination Macro (see section 10.34). + A Conceptual Volume may be expressed as a combination of other segmented Conceptual Volumes. Those other segments are referenced in the . The Conceptual Volume Combination Flag (3010,000E) shall be YES. The Conceptual Volume Segmentation Defined Flag (3010,0010) shall be NO. The Conceptual Volume Constituent Segmentation Reference Sequence (3010,0012) in the Conceptual Volume Constituent Sequence (3010,0008) shall not be present since the segmented representation of a constituent of a combination is specified by an Item of the Segment Reference Sequence (3010,0021) as follows: If a constituent in the Conceptual Volume Constituent Sequence (3010,0008) is a combination its constituents must @@ -283301,8 +286577,9 @@
RT Radiation Set Module - The RT Radiation Set Module describes treatment fractions that contain a set of beams or brachytherapy setups used within a treatment session to help achieve the dosimetric requirements of a given Treatment Phase. The Module references a set of RT Radiation Instances that describe the geometric and physical parameters that define the delivery of dose for a single fraction. In addition, the overall number of treatment fractions is defined, as well as possibly the fractionation scheme according to which, fractions will be delivered. - A Treatment Phase is achieved by delivering one or more RT Radiation Sets. The chronological relationships between RT Radiation Sets (the actual start of each set, the order or timing among sets, etc.) are recorded in Attributes outside the RT Radiation Set Module. + + specifies the Attributes of the , which describe treatment fractions that contain a set of beams or brachytherapy setups used within a treatment session to help achieve the dosimetric requirements of a given Treatment Phase. The Module references a set of RT Radiation Instances that describe the geometric and physical parameters that define the delivery of dose for a single fraction. In addition, the overall number of treatment fractions is defined, as well as possibly the fractionation scheme according to which, fractions will be delivered. + A Treatment Phase is achieved by delivering one or more RT Radiation Sets. The chronological relationships between RT Radiation Sets (the actual start of each set, the order or timing among sets, etc.) are recorded in Attributes outside the . @@ -283419,7 +286696,7 @@ 1 @@ -283516,9 +286793,10 @@
RT Radiation Set Module Attributes
- A general indication of the type of information contained within this RT Radiation Set. + A general indication of the intended use of this RT Radiation Set. See .
- RT Radiation Set Attribute Descriptions + RT Radiation Set Module Attribute Descriptions
RT Radiation Set Intent, RT Radiation Set Usage and RT Radiation Usage + RT Radiation Set Intent (300A,0637) describes the intended usage of the Radiation Set. RT Radiation Set Usage (300A,0707) and RT Radiation Usage (300A,0701) record the actual usage of the Radiation Set or individual Radiations, which may differ from the intent. Defined Terms for RT Radiation Set Intent (300A,0637), RT Radiation Set Usage (300A,0707) and RT Radiation Usage (300A,0701) @@ -283552,16 +286830,18 @@ + Example: + A treatment is defined by the RT Radiation Set SOP Instance whose RT Radiation Set Intent (300A,0637) value is TREATMENT. This value indicates that this RT Radiation Set is intended to be used for a treatment of the patient. The RT Radiation Set is sent to the treatment device and used for quality assurance without a patient being present. In this case, RT Radiation Set Usage (300A,0707) in the RT Radiation Record SOP Instance and the referenced RT Radiation Records have the value PLAN_QA. The same RT Radiation Set SOP Instance will be sent again to the treatment device for therapeutic radiation of a patient and then the RT Radiation Set Usage (300A,0707) of the SOP Instances recording the therapeutic radiation will contain the value TREATMENT.
RT Radiation Sequence All SOP Instances referenced in this Sequence shall: - share the same Frame of Reference (defined by the Frame of Reference UID (0020,0052) in the Frame Of Reference Module), and + share the same Frame of Reference (defined by the Frame of Reference UID (0020,0052) in the ), and - be defined for the same treatment device (specified by the Treatment Device Identification Macro within the RT Delivery Device Common Module). + be defined for the same treatment device (specified by the within the ). The SOP Classes referenced in this Sequence shall contain the following Modules: @@ -283603,14 +286883,15 @@
Intended Number of Fractions and Radiation Fraction Pattern Macro - The values of Intended Number of Fractions (300A,0636) and the attributes in Radiation Fraction Pattern Macro provide information about the planned treatment at the time the RT Radiation Set Instance was created. + The values of Intended Number of Fractions (300A,0636) and the Attributes in provide information about the planned treatment at the time the RT Radiation Set Instance was created.
RT Dose Contribution Module - The RT Dose Contribution Module contains information about the contribution of dose of the RT Radiations referenced by this RT Radiation Set IOD. Dose contributions refer to the RT Radiations delivering the dose and to anatomical structures receiving the dose. - Note that an anatomical structure (as defined by the Conceptual Volume Macro) can either be a textually tagged definition, or a reference to a Conceptual Volume defined in the RT Segment Annotation IOD. In all cases, Conceptual Volumes are identified by a UID which allows accumulation of dose to a given Conceptual Volume across RT Radiation Sets and comparison with prescribed Dosimetric Objectives. + + specifies the Attributes of the , which contain information about the contribution of dose of the RT Radiations referenced by this RT Radiation Set IOD. Dose contributions refer to the RT Radiations delivering the dose and to anatomical structures receiving the dose. + Note that an anatomical structure (as defined by the ) can either be a textually tagged definition, or a reference to a Conceptual Volume defined in the RT Segment Annotation IOD. In all cases, Conceptual Volumes are identified by a UID which allows accumulation of dose to a given Conceptual Volume across RT Radiation Sets and comparison with prescribed Dosimetric Objectives. Dose contributions are defined using Meterset values. The definition points in the Meterset to Dose Mapping Sequence may or may not align with the Meterset values at the Control Points of the RT Radiation SOP Instance. For example, where a dose deposition between Control Points cannot be determined individually per segment or where this definition is not useful, the lookup table may just contain the Meterset of first and last Control Points. The Meterset and dose contribution of the first Control Point are always zero. For further details see . @@ -284103,7 +287384,7 @@
Conceptual Volume Sequence The Conceptual Volume Sequence (3010,0025) identifies a Conceptual Volume that defines a volume for which dose is tracked during treatments. - If the Conceptual Volume is associated with a segment, the segment is defined by the Referenced Segment Reference Index (3010,0020) in the Conceptual Volume Segmentation Reference and Combination Macro (see ). + If the Conceptual Volume is associated with a segment, the segment is defined by the Referenced Segment Reference Index (3010,0020) in the . Alternatively, the Conceptual Volume may not be associated with a segment. For example, dose tracking may specify a nominal dose to an anatomical region of interest and the tracking coefficients approximated by Meterset values.
@@ -284122,7 +287403,8 @@
RT Delivery Device Common Module - The RT Delivery Device Common Module contains general information pertaining to the physical device used to deliver the treatment. + + specifies the Attributes of the , which contain general information pertaining to the physical device used to deliver the treatment.
RT Dose Contribution Module Attributes
@@ -284186,7 +287468,7 @@ @@ -284279,7 +287561,7 @@
RT Delivery Device Common Module Attributes
- CID is specified in the IOD + CID is specified in the IOD.
- >3D Point Coordinate + >3D Point Coordinates (0068,6590) @@ -284410,7 +287692,8 @@
RT Radiation Common Module - The RT Radiation Common Module contains the Attributes shared by all RT Radiation IODs used for radiation treatment delivery. + + specifies the Attributes of the , which are shared by all RT Radiation IODs used for radiation treatment delivery. @@ -284462,7 +287745,7 @@
RT Radiation Common Module Attributes
- RT Radiation Common Attribute Descriptions + RT Radiation Common Module Attribute Descriptions
Radiotherapy Procedure Technique Sequence See . @@ -284483,7 +287766,8 @@
C-Arm Photon-Electron Delivery Device Module - The C-Arm Photon-Electron Delivery Device Module contains C-Arm-specific parameters pertaining to the physical device. These parameters are used to specify or record photon and electron treatments, including geometrical parameters of the collimation system. + + specifies the Attributes of the , which contain C-Arm-specific parameters pertaining to the physical device. These parameters are used to specify or record photon and electron treatments, including geometrical parameters of the collimation system. @@ -284526,13 +287810,13 @@ @@ -284543,8 +287827,8 @@ @@ -284594,7 +287878,8 @@
C-Arm Photon-Electron Beam Module - The C-Arm Photon-Electron Beam Module specifies how a C-Arm photon or electron treatment beam is to be delivered. + + specifies the Attributes of the , which specify how a C-Arm photon or electron treatment beam is to be delivered.
C-Arm Photon-Electron Delivery Device Module Attributes
Radiation Type Code Sequence (300A,067F) D. - + Energy Unit Code Sequence (300A,0684) D. - + Radiation Fluence Modifier Code Sequence (300A,0683) D. - +
- Device Type Code Sequence (3010,002E) within RT Accessory Device Identification Macro D. - + Device Type Code Sequence (3010,002E) within D. +
@@ -284764,7 +288049,8 @@
Tomotherapeutic Delivery Device Module - The Tomotherapeutic Delivery Device Module contains tomotherapy-specific information pertaining to the physical device. These parameters are used to specify or record the treatment, including geometrical parameters of the collimation system. + + specifies the Attributes of the , which contain tomotherapy-specific information pertaining to the physical device. These parameters are used to specify or record the treatment, including geometrical parameters of the collimation system.
C-Arm Photon-Electron Beam Module Attributes
@@ -284833,7 +288119,8 @@
Tomotherapeutic Beam Module - The Tomotherapeutic Beam Module specifies or records how a tomotherapeutic treatment is to be or was delivered. + + specifies the Attributes of the , which specify or record how a tomotherapeutic treatment is to be or was delivered.
Tomotherapeutic Delivery Device Module Attributes
@@ -285127,7 +288414,8 @@
Robotic-Arm Delivery Device Module - The Robotic-Arm Delivery Device Module contains robot-specific information pertaining to the physical device. These parameters are used to specify or record the treatment, including geometric parameters of the collimation system. + + specifies the Attributes of the , which contain robot-specific information pertaining to the physical device. These parameters are used to specify or record the treatment, including geometric parameters of the collimation system.
Tomotherapeutic Beam Module Attributes
@@ -285224,7 +288512,8 @@
Robotic-Arm Path Module - The Robotic-Arm Path Module specifies or records how a Robotic Path treatment is to be delivered. Multiple paths are encoded as separate RT Radiation Instances referred to in the RT Radiation Set IOD. + + specifies the Attributes of the , which specify or record how a Robotic Path treatment is to be delivered. Multiple paths are encoded as separate RT Radiation Instances referred to in the RT Radiation Set IOD.
Robotic-Arm Delivery Device Module Attributes
@@ -285429,9 +288718,10 @@
RT Radiation Record Set Module - The RT Radiation Record Set Module contains treatment-modality-independent information about a set of RT Radiation Records. + + specifies the Attributes of the , which contain treatment-modality-independent information about a set of RT Radiation Records. The RT Radiation Record Set may refer to an RT Radiation Set SOP Instance that has been used to define the treatment delivery. It may also record ad hoc delivery. -
Robotic-Arm Path Module Attributes
+
@@ -285453,9 +288743,9 @@ @@ -285491,9 +288781,9 @@ @@ -285510,7 +288800,6 @@ A general indication of how the referenced RT Radiation Set was used.The Defined Terms are specified in .This value may differ from the RT Radiation Set Intent (300A,0637) within the Instance referenced by the Referenced RT Radiation Set Sequence (300A,0702). - See . @@ -285532,9 +288821,9 @@ @@ -285602,37 +288891,41 @@
RT Radiation Record Set Module Attributes
-Include - - + Include + +
->Include - - + >Include + +
->Include - - + >Include + +
- RT Radiation Record Set Attribute Descriptions + RT Radiation Record Set Module Attribute Descriptions
Referenced RT Radiation Record Sequence - All SOP Instances referenced in this Sequence shall be recorded by the same treatment device (specified by the Treatment Device Identification Macro within the RT Delivery Device Common Module). + All SOP Instances referenced in this Sequence shall be recorded by the same treatment device (specified by the within the ). An RT Radiation Record instance shall be referenced in exactly one RT Radiation Record Set instance. The Treatment Session UID within the RT Radiation Record Set shall be identical to those in the Referenced RT Radiation Record instances. The SOP Classes referenced in this Sequence shall contain the following Modules: - Enhanced RT Series Module specified in . + +. - Radiotherapy Common Instance Module specified in . + +. - RT Delivery Device Common Module specified in . + +. - RT Radiation Record Common Module specified in . + +.
RT Radiation Set Delivery Number and Clinical Fraction Number The Clinical Fraction Number (300A,0705) tracks the clinical progress of treatment delivery. - It is a counter that represents an ordinal count of deliveries of fractions within a radiotherapy treatment serving a given combination of prescriptions. - When it is used prospectively in instructions, the value indicates the ordinal count of the treatment fraction to be delivered in the upcoming treatment session. When the upcoming delivery of therapeutic radiation is intended to consist of the delivery of a complete RT Radiation Set serving the same combination of RT Prescriptions as the previous fraction, the value is incremented. When the upcoming delivery of therapeutic radiation is intended to resume the delivery of a previously incomplete fraction, the value is not incremented, i.e. the value is the same as that of the resumed fraction. - When it is used retrospectively in recording, the value indicates the ordinal count of the treatment fraction which has been delivered. + It is a counter that represents an ordinal count of deliveries of fractions within a radiotherapy treatment serving a given combination of prescriptions. + When it is used prospectively in instructions, the value indicates the ordinal count of the treatment fraction to be delivered in the upcoming treatment session. When the upcoming delivery of therapeutic radiation is intended to consist of the delivery of a complete RT Radiation Set serving the same combination of RT Prescriptions as the previous fraction, the value is incremented. When the upcoming delivery of therapeutic radiation is intended to resume the delivery of a previously incomplete fraction, the value is not incremented, i.e. the value is the same as that of the resumed fraction. + When it is used retrospectively in recording, the value indicates the ordinal count of the treatment fraction which has been delivered. The RT Radiation Set Delivery Number (300A,0704) tracks the number of times a fraction specified by the referenced RT Radiation Set Instance has been delivered. - When it is used prospectively in instructions, the value indicates the ordinal count of the treatment to be delivered by a referenced RT Radiation Set Instance. When the upcoming delivery of therapeutic radiation is intended to consist of the delivery of a complete RT Radiation Set, the value for that RT Radiation Set is incremented. When the upcoming delivery of therapeutic radiation is intended to resume the delivery of a previously incomplete fraction, the value is not incremented, i.e. the value is the same as that of the resumed fraction. - When it is used retrospectively in recording, the value indicates the ordinal count of deliveries by a referenced RT Radiation Set Instance. + When it is used prospectively in instructions, the value indicates the ordinal count of the treatment to be delivered by a referenced RT Radiation Set Instance. When the upcoming delivery of therapeutic radiation is intended to consist of the delivery of a complete RT Radiation Set, the value for that RT Radiation Set is incremented. When the upcoming delivery of therapeutic radiation is intended to resume the delivery of a previously incomplete fraction, the value is not incremented, i.e. the value is the same as that of the resumed fraction. + When it is used retrospectively in recording, the value indicates the ordinal count of deliveries by a referenced RT Radiation Set Instance. @@ -285642,11 +288935,11 @@ For some adaptive treatment approaches, details of the device parameters may be altered at the treatment session to accommodate the current position and shape of the patient. In this case, a new RT Radiation Set SOP Instance is used for the subsequent RT Treatment Fractions serving the same set of RT Prescriptions and the RT Radiation Set Delivery Number (300A,0704) re-starts at 1. - The Clinical Fraction Number (300A,0705) is continuously incremented to reflect the clinical progress of a therapeutic series of treatments. In the RT Radiation Record Set for the last of the intended RT Treatment Fractions, this value will usually be equal to the Number of Fractions (3010,007D) present in the corresponding RT Prescription(s). + The Clinical Fraction Number (300A,0705) is continuously incremented to reflect the clinical progress of a therapeutic series of treatments. In the RT Radiation Record Set for the last of the intended RT Treatment Fractions, this value will usually be equal to the Number of Fractions (3010,007D) present in the corresponding RT Prescription(s). - + Example RT Radiation Set P contains RT Radiations A, B; Adapted RT Radiations indicated by (') and (") ; RT Radiation Sets created are P, P' and P''. @@ -285979,13 +289272,14 @@
RT Radiation Set Usage - A typical example for different values of RT Radiation Set Usage (300A,0707) in the current RT Radiation Record Set SOP Instance versus in the SOP Instance referenced by the Referenced RT Radiation Set Sequence (300A,0702) is as follows: The treatment defined by the RT Radiation Set SOP Instance, in which RT Radiation Set Usage (300A,0707) has the value TREATMENT, may be sent to the treatment device and applied for quality assurance without a patient being present. In this case, RT Radiation Set Usage (300A,0707) in the current SOP Instance has the value PLAN_QA. + See .
RT Dose Contribution Record Module - The RT Dose Contribution Record Module contains information about the delivered dose. + + specifies the Attributes of the , which describe the delivered dose. @@ -286084,9 +289378,9 @@ @@ -286123,9 +289417,9 @@ @@ -286289,15 +289583,15 @@ @@ -286321,7 +289615,7 @@
Conceptual Volume Sequence The Conceptual Volume Sequence (3010,0025) identifies a Conceptual Volume defining a volume for which dose has been recorded during treatments. - If the Conceptual Volume is associated with a segment, the segment is defined by the Referenced Segment Reference Index (3010,0020) in the Conceptual Volume Segmentation Reference and Combination Macro (see ). + If the Conceptual Volume is associated with a segment, the segment is defined by the Referenced Segment Reference Index (3010,0020) in the . Alternatively, the Conceptual Volume might not be associated with a segment; for example, when dose recording is specified using a nominal dose to a volume and the tracking coefficients are approximated by Meterset values. Typically, this Module references Conceptual Volumes which have been used in the RT Dose Contribution Module of the RT Radiation Set SOP Instance referenced by the Referenced RT Radiation Set Sequence (300A,0702).
@@ -286329,7 +289623,8 @@
RT Radiation Record Common Module - The RT Radiation Record Common Module contains treatment-modality-independent information about a delivered RT Radiation. A delivered RT Radiation may be radiation to a patient or radiation without a patient being present (e.g. for QA purposes). + + specifies the Attributes of the , which contain treatment-modality-independent information about a delivered RT Radiation. A delivered RT Radiation may be radiation to a patient or radiation without a patient being present (e.g. for QA purposes).
RT Dose Contribution Record Module Attributes
->>Include - - + >>Include + +
->>Include - - + >>Include + +
->>>Include - - + >>>Include + + -D - - + D + +
@@ -286352,17 +289647,17 @@ @@ -286399,9 +289694,9 @@ @@ -286418,7 +289713,6 @@ A general indication of how the referenced RT Radiation was used.The Defined Terms are specified in .This value may differ from the RT Radiation Set Intent (300A,0637) within the Instance referenced by the Referenced RT Radiation Set Sequence (300A,0702). - See . @@ -286433,7 +289727,7 @@ @@ -286557,14 +289851,14 @@ @@ -286623,7 +289917,7 @@ @@ -286689,15 +289983,15 @@ @@ -286719,9 +290013,9 @@ @@ -286788,14 +290082,14 @@ @@ -286845,15 +290139,15 @@ @@ -286874,14 +290168,14 @@ @@ -286899,158 +290193,12 @@ Zero or more Items shall be included in this Sequence. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - @@ -287072,9 +290220,9 @@ @@ -287099,7 +290247,7 @@
RT Radiation Record Common Module Attributes
-Include - - + Include + +
-Include - - + Include + +
->Include - - + >Include + +
The origin of the content of this SOP Instance. - + Enumerated Values: DEVICE @@ -286463,7 +289757,7 @@ Indicates whether this SOP Instance represents the record of a treatment delivery which was a continuation of a previously interrupted treatment delivery of the RT Treatment Fraction specified by the RT Radiation Set Delivery Number (300A,0704). - + Enumerated Values: YES @@ -286492,7 +289786,7 @@ Termination status of the recorded treatment. - + Enumerated Values: NORMAL @@ -286528,15 +289822,15 @@
->Include - - + >Include + + -D - - + D + +
->Include - - + >Include + + -No Baseline CID is defined. - + No Baseline CID is defined. +
The category of tolerance violation which was exceeded. - + Defined Terms: CLINICAL @@ -286658,17 +289952,17 @@
->>Include - - + >>Include + + -If Treatment Tolerance Violation Category (300A,0732) has the value CLINICAL, Defined CID is 9566 "Clinical Tolerance Violation Types" - + If Treatment Tolerance Violation Category (300A,0732) has the value CLINICAL, Defined CID is 9566 "Clinical Tolerance Violation Types" + -If Treatment Tolerance Violation Category (300A,0732) has the value MACHINE, Defined CID is 9567 "Machine Tolerance Violation Types" - + If Treatment Tolerance Violation Category (300A,0732) has the value MACHINE, Defined CID is 9567 "Machine Tolerance Violation Types" +
->>Include - - + >>Include + + -D - - + D + +
->>Include - - + >>Include + +
->>>Include - - + >>>Include + + -The Observer Type (0040,A084) shall be PSN. - + The Observer Type (0040,A084) shall be PSN. +
->>>Include - - + >>>Include + + -B - - + B + +
->Include - - + >Include + + -Assertion Code Sequence (0044,0101) B. - + Assertion Code Sequence (0044,0101) B. +
- >Interlock DateTime - - (300A,0741) - - 1 - - Date and Time when the Interlock occurred. - The date and time of occurrence may be when the interlock occurred (e.g. by a real-time system) or when the interlock was recorded. - See . -
- >Interlock Description - - (300A,0742) - - 1 - - User-readable description of the interlock. -
- >Interlock Origin Description - - (300A,0783) - - 1C - - Description of the origin of the interlock. - Required if Interlock Originating Device Sequence (300A,0743) is not present. -
- >Interlock Originating Device Sequence - - (300A,0743) - - 1C - - Contains the attributes that identify the device that originated the interlock. - Only a single Item shall be included in this Sequence. - Required if Interlock Origin Description (300A,0783) is not present. -
- ->>Include - - - - -No Baseline CID is defined. - -
- >Interlock Code Sequence - - (300A,0744) - - 1 - - Code(s) that describe the interlock(s) that occurred. - One or more Items shall be included in this Sequence. -
- ->>Include - - - - -B. - -
- >Interlock Resolution Code Sequence - - (300A,0745) - - 1 - - The action applied to resolve the interlock. - One or more Items shall be included in this Sequence. -
- ->>Include - - - - -D - - -
- >Interlock Resolution User Sequence - - (300A,0746) - - 1 - - The user that resolved the interlock. - One or more Items shall be included in this Sequence. -
- ->>Include - - + + >Include + +
->Include - - + >Include + +
- RT Radiation Record Common Attribute Descriptions + RT Radiation Record Common Module Attribute Descriptions
Additional Parameter Recording Instance Sequence @@ -287109,576 +290257,578 @@
- RT Radiation Salvage Record Module - The RT Radiation Salvage Record Module contains information about the values which have been recorded when recording by the modality-specific RT Radiation Record IOD was not possible and thus only a minimal subset of attributes is present. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
RT Radiation Salvage Record Module Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- -Include . - -
- Starting Meterset Value Known Flag - - (300A,0723) - - 1 - - Whether it is known that the value of the Cumulative Meterset at the first recorded RT Control Point represents the actual value at the start of the treatment delivery. - - Enumerated Values: - - NO - - The Cumulative Meterset at the first recorded RT Control Point may have an estimated or arbitrary value. - - - - YES - - The Cumulative Meterset at the first recorded RT Control Point has the actual value at which the treatment was started or resumed. - - - -
- -Optionally, all other Attributes at Instance level that are part of the RT Radiation SOP Instance referenced in Referenced RT Instance Sequence (300A,0631), describing the delivery device. See . - -
- Number of RT Control Points - - (300A,0604) - - 1 - - Number of RT Control Points in the RT Radiation Salvage Record Control Point Sequence (300A,0722). - The value shall be equal to or greater than 2. -
- RT Radiation Salvage Record Control Point Sequence - - (300A,0722) - - 1 - - Control Points used to record the beam delivery. - The number of Items included in this Sequence shall equal the value of Number of RT Control Points (300A,0604). -
- ->Include - - -
- >Referenced Radiation Generation Mode Index - - (300A,0605) - - 1C - - The value of Radiation Generation Mode Index (300A,0601) in the Radiation Generation Mode Sequence (300A,067B) in this IOD that defines the Radiation Generation Mode used for this Control Point. - Required if Number of Radiation Generation Modes (300A,0685) is present and the conditions in Section C.36.2.2.5.1.1are satisfied. -
- ->Optionally, all other Attributes at RT Control Point level that are part of the RT Radiation SOP Instance referenced in Referenced RT Instance Sequence (300A,0631). See . - -
-
- RT Radiation Salvage Record Module Attribute Descriptions -
- Recorded Parameter - Additional optional attributes contain values which are known after the termination of the treatment delivery. Any subset of Attributes of the referenced RT Radiation SOP Instance may be provided. If present, an Attribute shall be enclosed in the nested Sequence as it appears in the referenced RT Radiation SOP Instance. If additional parameters are supported these are expected to be documented in an implementation's Conformance Statement. - - Example - - The following example shows the recording of a Source Gantry Angle of 5 deg and the Y Jaw Openings of 2/3 mm at Control Point 7. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Additional Optional Parameter Example
- Attribute - - Tag - - Additional Optional Parameter - - Value -
... - - -
- Starting Meterset Value Known Flag - - (300A,0723) - - No - - YES -
... - - -
- RT Beam Limiting Device Definition Sequence - - (300A,0641) - - Yes - -
- >Device Index - - (3010,0039) - - Yes - - 2 -
- >Beam Modifier Orientation Angle - - (300A,0645) - - Yes - - 90 -
- >Device Type Code Sequence - - (3010,002E) - - Yes - - -(130330, DCM, "Jaw Pair") - -
- >Parallel RT Beam Delimiter Device Sequence - - (300A,0648) - - Yes - -
- >>Parallel RT Beam Delimiter Device Orientation Label Code Sequence - - (300A,0644) - - Yes - - -(130335, DCM, "Y Orientation") - -
... - - -
- RT Radiation Salvage Record Control Point Sequence - - (300A,0722) - - No - -
- >RT Control Point Index - - (300A,0600) - - No - - 7 -
... - - -
- >Source Roll Angle - - (300A,067A) - - Yes - - 5 -
- >RT Beam Limiting Device Opening Sequence - - (300A,0656) - - Yes - -
- >>Referenced Device Index - - (300A,0607) - - Yes - - 2 -
- >>Parallel RT Beam Delimiter Positions - - (300A,064A) - - Yes - - 2/3 -
-
-
-
-
- RT Radiation Set Delivery Instruction Module - The RT Radiation Set Delivery Instruction Module contains information required by a Treatment Delivery System (TDS) to deliver an external beam radiotherapy treatment. - The Module provides data which are not part of the RT Radiation Set and referenced SOP Instances that were issued at the time of treatment planning. The content does not alter the planned amount and location of dose. - The Module provides data which are specific to the upcoming RT Treatment Session, such as the RT Radiation Set to be delivered, the fraction numbers, information about the continuation of delivery, etc. If more than one RT Radiation Set will be delivered in the upcoming RT Treatment session, treatment delivery of each RT Radiation Set will be specified by a separate instance containing this Module. - Typically, this information is supplied by a Treatment Management System to the TDS when it creates an RT Radiation Set Delivery Instruction SOP Instance so that the TDS does not require any additional information beyond the current RT Treatment Session. - The content of the RT Radiation Set Delivery Instruction Module applies to all or a subset of the RT Radiations specified in the referenced RT Radiation Set. - - + RT Radiation Salvage Record Module + + specifies the Attributes of the , which contain information about the values that have been recorded when recording by the modality-specific RT Radiation Record IOD was not possible and thus only a minimal subset of Attributes is present. +
RT Radiation Set Delivery Instruction Module Attributes
+ - - - - - - + + + + + + + + + + + + +
RT Radiation Salvage Record Module Attributes
- Attribute Name + Attribute Name - Tag + Tag - Type + Type - Attribute Description + Attribute Description
- Referenced RT Radiation Set Sequence - - (300A,0702) - - 1 - - Reference to a Radiation Set SOP Instance containing the Radiations to which the current SOP Instance applies. - Only a single Item shall be included in this sequence. -
- - >Include . + + Include .
- Treatment Device Identification Sequence + Starting Meterset Value Known Flag - (300A,063A) + (300A,0723) - 2 + 1 - Identifies the treatment device intended to be used for delivering the RT Radiation. - See . - Zero or one Item shall be included in this Sequence. + Whether it is known that the value of the Cumulative Meterset at the first recorded RT Control Point represents the actual value at the start of the treatment delivery. + + Enumerated Values: + + NO + + The Cumulative Meterset at the first recorded RT Control Point may have an estimated or arbitrary value. + + + + YES + + The Cumulative Meterset at the first recorded RT Control Point has the actual value at which the treatment was started or resumed. + + +
- - >Include . + + Optionally, all other Attributes at Instance level that are part of the RT Radiation SOP Instance referenced in Referenced RT Instance Sequence (300A,0631), describing the delivery device. See .
- RT Radiation Set Delivery Usage + Number of RT Control Points - (300A,079E) + (300A,0604) - 1 + 1 - The intended usage of the RT Radiation Set. - This value may differ from the RT Radiation Set Intent (300A,0637) within the Instance referenced by the Referenced RT Radiation Set Sequence (300A,0702). - The Defined Terms are specified in . + Number of RT Control Points in the RT Radiation Salvage Record Control Point Sequence (300A,0722). + The value shall be equal to or greater than 2.
- RT Radiation Set Delivery Number + RT Radiation Salvage Record Control Point Sequence - (300A,0704) + (300A,0722) - 1C + 1 - A number that indicates the RT Treatment Fraction of the referenced RT Radiation Set Instance to be delivered. - Required if RT Radiation Set Delivery Usage (300A,079E) is TREATMENT. May be present otherwise. - See . + Control Points used to record the beam delivery. + The number of Items included in this Sequence shall equal the value of Number of RT Control Points (300A,0604).
+ + >Include + + +
+ >Referenced Radiation Generation Mode Index + + (300A,0605) + + 1C + + The value of Radiation Generation Mode Index (300A,0601) in the Radiation Generation Mode Sequence (300A,067B) in this IOD that defines the Radiation Generation Mode used for this Control Point. + Required if Number of Radiation Generation Modes (300A,0685) is present and the conditions in Section C.36.2.2.5.1.1are satisfied. +
+ + >Optionally, all other Attributes at RT Control Point level that are part of the RT Radiation SOP Instance referenced in Referenced RT Instance Sequence (300A,0631). See . + +
+
+ RT Radiation Salvage Record Module Attribute Descriptions +
+ Recorded Parameter + Additional optional Attributes contain values which are known after the termination of the treatment delivery. Any subset of Attributes of the referenced RT Radiation SOP Instance may be provided. If present, an Attribute shall be enclosed in the nested Sequence as it appears in the referenced RT Radiation SOP Instance. If additional parameters are supported these are expected to be documented in an implementation's Conformance Statement. + + Example + + The following example shows the recording of a Source Gantry Angle of 5 deg and the Y Jaw Openings of 2/3 mm at Control Point 7. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Additional Optional Parameter Example
+ Attribute + + Tag + + Additional Optional Parameter + + Value +
... + + +
+ Starting Meterset Value Known Flag + + (300A,0723) + + No + + YES +
... + + +
+ RT Beam Limiting Device Definition Sequence + + (300A,0641) + + Yes + +
+ >Device Index + + (3010,0039) + + Yes + + 2 +
+ >Beam Modifier Orientation Angle + + (300A,0645) + + Yes + + 90 +
+ >Device Type Code Sequence + + (3010,002E) + + Yes + + + (130330, DCM, "Jaw Pair") + +
+ >Parallel RT Beam Delimiter Device Sequence + + (300A,0648) + + Yes + +
+ >>Parallel RT Beam Delimiter Device Orientation Label Code Sequence + + (300A,0644) + + Yes + + + (130335, DCM, "Y Orientation") + +
... + + +
+ RT Radiation Salvage Record Control Point Sequence + + (300A,0722) + + No + +
+ >RT Control Point Index + + (300A,0600) + + No + + 7 +
... + + +
+ >Source Roll Angle + + (300A,067A) + + Yes + + 5 +
+ >RT Beam Limiting Device Opening Sequence + + (300A,0656) + + Yes + +
+ >>Referenced Device Index + + (300A,0607) + + Yes + + 2 +
+ >>Parallel RT Beam Delimiter Positions + + (300A,064A) + + Yes + + 2/3 +
+
+
+
+
+ RT Radiation Set Delivery Instruction Module + + specifies the Attributes of the , which contains information required by a Treatment Delivery System (TDS) to deliver an external beam radiotherapy treatment. + This Module provides data that are not part of the RT Radiation Set and referenced SOP Instances that were issued at the time of treatment planning. The content does not alter the planned amount and location of dose. + This Module provides data that are specific to the upcoming RT Treatment Session, such as the RT Radiation Set to be delivered, the fraction numbers, information about the continuation of delivery, etc. If more than one RT Radiation Set will be delivered in the upcoming RT Treatment session, treatment delivery of each RT Radiation Set will be specified by a separate instance containing this Module. + Typically, this information is supplied by a Treatment Management System to the TDS when it creates an RT Radiation Set Delivery Instruction SOP Instance so that the TDS does not require any additional information beyond the current RT Treatment Session. + The content of this Module applies to all or a subset of the RT Radiations specified in the referenced RT Radiation Set. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - @@ -287874,145 +291024,146 @@ Radiation Set Delivery Attribute Description
Treatment Device Identification Sequence - The RT Radiation Set Delivery Instruction Module may specify a treatment device to be used for radiation delivery. This treatment device may differ from the device specified in the referenced RT Radiation Instances. + The may specify a treatment device to be used for radiation delivery. This treatment device may differ from the device specified in the referenced RT Radiation Instances.
RT Treatment Preparation Module - The RT Treatment Preparation Module contains information describing the procedures to prepare the patient for a radiotherapeutic treatment. These procedures may include aligning the patient position, setting up required accessories, such as fixation and shielding devices applied to the patient, administrating medications, etc. + + specifies the Attributes of the , which contain information describing the procedures to prepare the patient for a radiotherapeutic treatment. These procedures may include aligning the patient position, setting up required accessories, such as fixation and shielding devices applied to the patient, administrating medications, etc.
RT Radiation Set Delivery Instruction Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Referenced RT Radiation Set Sequence + + (300A,0702) + + 1 + + Reference to a Radiation Set SOP Instance containing the Radiations to which the current SOP Instance applies. + Only a single Item shall be included in this sequence. +
+ + >Include . + +
+ Treatment Device Identification Sequence + + (300A,063A) + + 2 + + Identifies the treatment device intended to be used for delivering the RT Radiation. + See . + Zero or one Item shall be included in this Sequence. +
+ + >Include . + +
+ RT Radiation Set Delivery Usage + + (300A,079E) + + 1 + + The intended usage of the RT Radiation Set. + This value may differ from the RT Radiation Set Intent (300A,0637) within the Instance referenced by the Referenced RT Radiation Set Sequence (300A,0702). + The Defined Terms are specified in . +
+ RT Radiation Set Delivery Number + + (300A,0704) + + 1C + - Clinical Fraction Number + A number that indicates the RT Treatment Fraction of the referenced RT Radiation Set Instance to be delivered. + Required if RT Radiation Set Delivery Usage (300A,079E) is TREATMENT. May be present otherwise. + See . +
+ Clinical Fraction Number - (300A,0705) + (300A,0705) - 1C + 1C - A number that indicates the RT Treatment Fraction to be delivered. - Required if RT Radiation Set Delivery Usage (300A,079E) is TREATMENT. May be present otherwise. - See . + A number that indicates the RT Treatment Fraction to be delivered. + Required if RT Radiation Set Delivery Usage (300A,079E) is TREATMENT. May be present otherwise. + See .
- RT Radiation Task Sequence + RT Radiation Task Sequence - (300A,0797) + (300A,0797) - 1 + 1 - Subset of RT Radiations to be delivered and/or to have quality assurance procedures applied. - One or more Items shall be included in this Sequence. - All RT Radiation SOP Instances in the referenced RT Radiation Set shall either be in this Sequence or the Omitted Radiation Sequence (300A,0787). Correspondingly the sum of the number of Items in this Sequence and the number of Items in the Omitted Radiation Sequence (300A,0787) shall be the number of RT Radiation SOP Instances in the referenced RT Radiation Set. - If a complete fraction (no continuation of a previously interrupted treatment) is to be delivered, the number of Items in the Sequence shall be the number of RT Radiation SOP Instances in the referenced RT Radiation Set. The Omitted Radiation Sequence (300A,0787) will not be present in this case. + Subset of RT Radiations to be delivered and/or to have quality assurance procedures applied. + One or more Items shall be included in this Sequence. + All RT Radiation SOP Instances in the referenced RT Radiation Set shall either be in this Sequence or the Omitted Radiation Sequence (300A,0787). Correspondingly the sum of the number of Items in this Sequence and the number of Items in the Omitted Radiation Sequence (300A,0787) shall be the number of RT Radiation SOP Instances in the referenced RT Radiation Set. + If a complete fraction (no continuation of a previously interrupted treatment) is to be delivered, the number of Items in the Sequence shall be the number of RT Radiation SOP Instances in the referenced RT Radiation Set. The Omitted Radiation Sequence (300A,0787) will not be present in this case. - The number of RT Radiation SOP Instances in the referenced RT Radiation Set is the number of SOP Instances contained in the Referenced RT Radiation Sequence (300A,0630) of the Radiation Set SOP Instance referenced in the Referenced RT Radiation Set Sequence (300A,0702). + The number of RT Radiation SOP Instances in the referenced RT Radiation Set is the number of SOP Instances contained in the Referenced RT Radiation Sequence (300A,0630) of the Radiation Set SOP Instance referenced in the Referenced RT Radiation Set Sequence (300A,0702).
- >Referenced RT Radiation Sequence + >Referenced RT Radiation Sequence - (300A,0630) + (300A,0630) - 1 + 1 - Reference to a single RT Radiation SOP Instance containing the parameters to be used for the delivery of the RT Radiation. - The reference shall contain an RT Radiation SOP Instance that has been referenced in the RT Radiation Set SOP Instance in the Referenced RT Radiation Set Sequence (300A,0702). - Only a single Item shall be included in this sequence. + Reference to a single RT Radiation SOP Instance containing the parameters to be used for the delivery of the RT Radiation. + The reference shall contain an RT Radiation SOP Instance that has been referenced in the RT Radiation Set SOP Instance in the Referenced RT Radiation Set Sequence (300A,0702). + Only a single Item shall be included in this sequence.
- + >>Include .
- >RT Delivery Start Patient Position Sequence + >RT Delivery Start Patient Position Sequence - (300A,0789) + (300A,0789) - 2 + 2 - The position of the patient at the start of delivery of the RT Radiation referenced in the RT Radiation Sequence (300A,0630). - The content of this Sequence shall take precedence over the treatment positions specified in the referenced RT Radiation. - Zero or one Item shall be included in this Sequence. + The position of the patient at the start of delivery of the RT Radiation referenced in the RT Radiation Sequence (300A,0630). + The content of this Sequence shall take precedence over the treatment positions specified in the referenced RT Radiation. + Zero or one Item shall be included in this Sequence.
- + >>Include .
- >Treatment Delivery Continuation Flag + >Treatment Delivery Continuation Flag - (300A,0708) + (300A,0708) - 1 + 1 - Whether the task defines a continuation of a previously interrupted treatment delivery of the referenced RT Radiation. + Whether the task defines a continuation of a previously interrupted treatment delivery of the referenced RT Radiation. Enumerated Values: YES - The task represents a continuation. + The task represents a continuation. NO - The task represents a treatment delivery that starts at the first RT Control Point. + The task represents a treatment delivery that starts at the first RT Control Point. @@ -287686,186 +290836,186 @@
- >Continuation Start Meterset + >Continuation Start Meterset - (0074,0120) + (0074,0120) - 1C + 1C - Meterset within the RT Radiation referenced in the Referenced RT Radiation Sequence (300A,0630) at which treatment delivery starts. - The Meterset is expressed in units specified by Radiation Dosimeter Unit Sequence (300A,0658) in the referenced RT Radiation SOP Instance. - Required if Treatment Delivery Continuation Flag (300A,0708) is YES. + Meterset within the RT Radiation referenced in the Referenced RT Radiation Sequence (300A,0630) at which treatment delivery starts. + The Meterset is expressed in units specified by Radiation Dosimeter Unit Sequence (300A,0658) in the referenced RT Radiation SOP Instance. + Required if Treatment Delivery Continuation Flag (300A,0708) is YES.
- >Continuation End Meterset + >Continuation End Meterset - (0074,0121) + (0074,0121) - 1C + 1C - Meterset within the RT Radiation referenced in the Referenced RT Radiation Sequence (300A,0630) at which treatment delivery ends. - The Meterset is expressed in units specified by Radiation Dosimeter Unit Sequence (300A,0658) in the referenced RT Radiation SOP Instance. - Required if Treatment Delivery Continuation Flag (300A,0708) is YES and the Continuation End Meterset (0074,0121) is not equal to the Meterset of the last RT Control Point in the referenced RT Radiation SOP Instance. + Meterset within the RT Radiation referenced in the Referenced RT Radiation Sequence (300A,0630) at which treatment delivery ends. + The Meterset is expressed in units specified by Radiation Dosimeter Unit Sequence (300A,0658) in the referenced RT Radiation SOP Instance. + Required if Treatment Delivery Continuation Flag (300A,0708) is YES and the Continuation End Meterset (0074,0121) is not equal to the Meterset of the last RT Control Point in the referenced RT Radiation SOP Instance.
- >Radiation Order Index + >Radiation Order Index - (300A,0786) + (300A,0786) - 2 + 2 - Index defining the order in which the RT Radiations are to be delivered. - The value shall start at 1, and increase monotonically by 1. + Index defining the order in which the RT Radiations are to be delivered. + The value shall start at 1, and increase monotonically by 1.
- >Referenced RT Treatment Preparation Sequence + >Referenced RT Treatment Preparation Sequence - (300A,078B) + (300A,078B) - 2 + 2 - Reference to a RT Treatment Preparation SOP Instance that applies to this delivery. - Only a single Item shall be included in this Sequence. + Reference to a RT Treatment Preparation SOP Instance that applies to this delivery. + Only a single Item shall be included in this Sequence.
- + >>Include .
- + >Include .
- Omitted Radiation Sequence + Omitted Radiation Sequence - (300A,0787) + (300A,0787) - 1C + 1C - Subset of RT Radiations that are not to be delivered. - The delivery system shall not deliver any RT Radiations referenced in this Sequence. - Required if one or more RT Radiation SOP Instances contained in the referenced RT Radiation Set are not to be delivered. - One or more Items shall be included in this Sequence. + Subset of RT Radiations that are not to be delivered. + The delivery system shall not deliver any RT Radiations referenced in this Sequence. + Required if one or more RT Radiation SOP Instances contained in the referenced RT Radiation Set are not to be delivered. + One or more Items shall be included in this Sequence.
- >Referenced RT Radiation Sequence + >Referenced RT Radiation Sequence - (300A,0630) + (300A,0630) - 1 + 1 - The RT Radiation SOP Instance that is not to be delivered. - The reference shall contain an RT Radiation SOP Instance that has been referenced in the RT Radiation Set SOP Instance in the Referenced RT Radiation Set Sequence (300A,0702). - Only a single Item shall be included in this sequence. + The RT Radiation SOP Instance that is not to be delivered. + The reference shall contain an RT Radiation SOP Instance that has been referenced in the RT Radiation Set SOP Instance in the Referenced RT Radiation Set Sequence (300A,0702). + Only a single Item shall be included in this sequence.
- + >>Include .
- >Reason for Omission Code Sequence + >Reason for Omission Code Sequence - (300A,0788) + (300A,0788) - 1 + 1 - Reason the RT Radiation is not to be delivered. - Only a single Item shall be included in this sequence. + Reason the RT Radiation is not to be delivered. + Only a single Item shall be included in this sequence.
- + >>Include . - - D. - + + + D. +
- >Asserter Identification Sequence + >Asserter Identification Sequence - (0044,0103) + (0044,0103) - 1 + 1 - The person or device making the assertion that the RT Radiation is omitted. - Only a single Item shall be included in this sequence. + The person or device making the assertion that the RT Radiation is omitted. + Only a single Item shall be included in this sequence.
- + >>Include . - - Organizational Role B. + + Organizational Role B.
- >Reason for Omission Description + >Reason for Omission Description - (300C,0113) + (300C,0113) - 3 + 3 - User-defined description of why the RT Radiation is not to be delivered. + User-defined description of why the RT Radiation is not to be delivered.
@@ -288181,63 +291332,72 @@ RT Treatment Preparation Module Attribute Description
Treatment Preparation Instruction Description - A free-text description of the treatment preparation instruction, if present, shall be encoded in attribute Entity Description (3010,0037) of the RT Entity Labeling Macro. + A free-text description of the treatment preparation instruction, if present, shall be encoded in Attribute Entity Description (3010,0037) of the .
Patient Treatment Preparation Procedure - In , if the Patient Treatment Preparation Procedure Code Sequence (300A,0791) has the code value specified in the left column, the Template for Patient Treatment Preparation Procedure Parameter Sequence (300A,0793) shall be the one specified in the right column. + In , if the Patient Treatment Preparation Procedure Code Sequence (300A,0791) has the code value specified in the left column, the Template for Patient Treatment Preparation Procedure Parameter Sequence (300A,0793) shall be the one specified in the right column.
RT Treatment Preparation Module Attributes
- Attribute Name + Attribute Name - Tag + Tag - Type + Type - Attribute Description + Attribute Description
- + Include . - See . + See .
- RT Patient Position Scope Sequence + RT Patient Position Scope Sequence - (300A,0784) + (300A,0784) - 1 + 1 - The RT Radiation Set, RT Radiation Instances or the Treatment Position Groups to which the treatment preparation parameters apply. - Only a single Item shall be included in this Sequence. + The RT Radiation Set, RT Radiation Instances or the Treatment Position Groups to which the treatment preparation parameters apply. + Only a single Item shall be included in this Sequence.
- + >Include .
- RT Treatment Preparation Patient Position Sequence + RT Treatment Preparation Patient Position Sequence - (300A,078A) + (300A,078A) - 1 + 1 - The position of the patient at the start of the treatment preparation. - Only a single Item shall be included in this Sequence. + The position of the patient at the start of the treatment preparation. + Only a single Item shall be included in this Sequence.
- + >Include .
- Patient Treatment Preparation Method Code Sequence + Patient Treatment Preparation Method Code Sequence - (300A,078D) + (300A,078D) - 1 + 1 - Method used to prepare the Patient for treatment. - Only a single Item shall be included in this Sequence. + Method used to prepare the Patient for treatment. + Only a single Item shall be included in this Sequence.
- + >Include . - + B.
- Patient Treatment Preparation Method Description + Patient Treatment Preparation Method Description - (300A,0792) + (300A,0792) - 3 + 3 - User-defined description of patient treatment preparation technique. + User-defined description of patient treatment preparation technique.
- Referenced Patient Setup Photo Sequence + Referenced Patient Setup Photo Sequence - (300A,078C) + (300A,078C) - 3 + 3 - References to photos illustrating the patient setup. - One or more Items are permitted in this Sequence. + References to photos illustrating the patient setup. + One or more Items are permitted in this Sequence.
- + >Include @@ -288020,157 +291171,157 @@
- >Patient Setup Photo Description + >Patient Setup Photo Description - (300A,0794) + (300A,0794) - 2 + 2 - User-defined description of patient setup photo. + User-defined description of patient setup photo.
- >Referenced Patient Setup Procedure Index + >Referenced Patient Setup Procedure Index - (300A,0796) + (300A,0796) - 1C + 1C - The value of Patient Treatment Preparation Procedure Index (300A,0795) from Patient Treatment Preparation Procedure Sequence (300A,0790) corresponding to the Patient Treatment Preparation Procedure to which this Sequence Item refers. - Required if this Patient Setup Photo is associated with a Patient Treatment Preparation Procedure. + The value of Patient Treatment Preparation Procedure Index (300A,0795) from Patient Treatment Preparation Procedure Sequence (300A,0790) corresponding to the Patient Treatment Preparation Procedure to which this Sequence Item refers. + Required if this Patient Setup Photo is associated with a Patient Treatment Preparation Procedure.
- Patient Treatment Preparation Procedure Sequence + Patient Treatment Preparation Procedure Sequence - (300A,0790) + (300A,0790) - 2 + 2 - Procedures for preparing for the treatment of the patient. - Zero or more Items shall be included in this Sequence. + Procedures for preparing for the treatment of the patient. + Zero or more Items shall be included in this Sequence.
- >Patient Treatment Preparation Procedure Index + >Patient Treatment Preparation Procedure Index - (300A,0795) + (300A,0795) - 1 + 1 - Index of the Patient Treatment Preparation Procedure in this Sequence. - The value shall start at 1 and increase monotonically by 1. + Index of the Patient Treatment Preparation Procedure in this Sequence. + The value shall start at 1 and increase monotonically by 1.
- >Patient Treatment Preparation Procedure Code Sequence + >Patient Treatment Preparation Procedure Code Sequence - (300A,0791) + (300A,0791) - 1 + 1 - Procedure performed to prepare the patient for treatment. - Only a single Item shall be present in this Sequence. + Procedure performed to prepare the patient for treatment. + Only a single Item shall be present in this Sequence.
- + >>Include - + B.
- >Patient Treatment Preparation Device Sequence + >Patient Treatment Preparation Device Sequence - (300A,078F) + (300A,078F) - 3 + 3 - Devices used for preparing the patient for treatment. - Only a single Item is permitted in this Sequence. + Devices used for preparing the patient for treatment. + Only a single Item is permitted in this Sequence.
- + >>Include - + B.
- >Patient Treatment Preparation Procedure Parameter Description + >Patient Treatment Preparation Procedure Parameter Description - (300A,078E) + (300A,078E) - 2 + 2 - User-defined description of patient treatment preparation procedure parameter(s). + User-defined description of patient treatment preparation procedure parameter(s).
- >Patient Treatment Preparation Procedure Parameter Sequence + >Patient Treatment Preparation Procedure Parameter Sequence - (300A,0793) + (300A,0793) - 2 + 2 - Parameters for the Patient Treatment Preparation Procedure. - Zero or more Items shall be included in this Sequence. + Parameters for the Patient Treatment Preparation Procedure. + Zero or more Items shall be included in this Sequence.
- + >>Include - + See for Baseline TID.
- + - + No Baseline TID defined. + +
RT Treatment Preparation Module AttributesPatient Treatment Preparation Procedure Parameter Codes
- Patient Treatment Preparation Procedure Code Sequence (300A,0791) + Patient Treatment Preparation Procedure Code Sequence (300A,0791) - Patient Treatment Preparation Procedure Parameter Sequence (300A,0793) + Patient Treatment Preparation Procedure Parameter Sequence (300A,0793)
- (72641008, SCT, "Patient Sedation") + + (72641008, SCT, "Patient Sedation") + - B + B +
- (130637, DCM, "Patient Fixation Setup") + + (130637, DCM, "Patient Fixation Setup") + - B + B +
- (130638, DCM, "Patient Alignment Setup") + + (130638, DCM, "Patient Alignment Setup") + - B + B +
- All others + All others - No Baseline TID defined -
- - - + + +
@@ -288247,9 +291407,9 @@ Microscopy Bulk Simple Annotations Modules This Section describes Microscopy Bulk Simple Annotations Modules.
- Microscopy Bulk Simple Annotations Series Module + Microscopy Bulk Simple Annotations Series Module - specifies the Attributes that identify and describe general information about a Microscopy Bulk Simple Annotations Series. + specifies the Attributes of the , which identify and describe general information about a Microscopy Bulk Simple Annotations Series. @@ -288334,872 +291494,4343 @@ - +
Microscopy Bulk Simple Annotations Series Module Attributes
- Microscopy Bulk Simple Annotations Module - - specifies the Attributes that describe the Microscopy Bulk Simple Annotations. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Microscopy Bulk Simple Annotations Module Attributes
- Attribute Name - - Tag - - Type - - Attribute Description -
- - Include - - - - -
- Content Date - - (0008,0023) - - 1 - - The date the content creation started. -
- Content Time - - (0008,0033) - - 1 - - The time the content creation started. -
- Annotation Coordinate Type - - (006A,0001) - - 1 - - Whether coordinates are image-relative (2D) or volume-relative (3D). - - Enumerated Values: - - 2D - - relative to individual frame or total image matrix - - - - 3D - - relative to a Cartesian coordinate system defined by a Frame of Reference - - - -
- Pixel Origin Interpretation - - (0048,0301) - - 1C - - For image-relative coordinates, specifies whether coordinates are to be interpreted relative to the individual frame pixel origins, or relative to the Total Pixel Matrix origin (see Section C.8.12.4.1.4). - Required if Annotation Coordinate Type (006A,0001) is 2D. - - Enumerated Values: - - FRAME - - relative to individual frame - - - - VOLUME - - relative to Total Image Matrix - - - - - The use of the term "VOLUME" to refer to the Total Image Matrix is historical and inherited from Presentation States, and does not refer to 3D coordinates. - -
- Referenced Image Sequence - - (0008,1140) - - 1C - - The image to which this Annotation object applies. - Only a single Item shall be included in this Sequence. - Required if Annotation Coordinate Type (006A,0001) is 2D. May be present otherwise. -
- - >Include - - - - - - -
- Annotation Group Sequence - - (006A,0002) - - 1 - - Groups of Annotations sharing common characteristics, such as graphic type, properties or measurements. - One or more Items shall be included in this Sequence. -
- >Annotation Group Number - - (0040,A180) - - 1 - - Identification number of the Annotation Group. Uniquely identifies a Annotation Group within this SOP Instance. Shall start at a value of 1, and increase monotonically by 1. -
- >Annotation Group UID - - (006A,0003) - - 1 - - Unique identifier of the Annotation Group. -
- >Annotation Group Label - - (006A,0005) - - 1 - - User-defined label identifying this Annotation Group. This may be the same as Code Meaning (0008,0104) of Annotation Property Type Code Sequence (006A,000A). -
- >Annotation Group Description - - (006A,0006) - - 3 - - User-defined description for this Annotation Group. -
- >Annotation Group Generation Type - - (006A,0007) - - 1 - - Type of algorithm used to generate the Annotations. - - Enumerated Values: - - AUTOMATIC - - generated by algorithm without human user assistance - - - - SEMIAUTOMATIC - - generated by algorithm with human user assistance - - - - MANUAL - - generated by human user - - - -
- >Annotation Group Algorithm Identification Sequence - - (006A,0008) - - 1C - - The algorithms used to create the Annotations in this group. - One or more Items shall be included in this Sequence. - Required if Annotation Generation Type (006A,0007) is AUTOMATIC or SEMIAUTOMATIC. -
- - >>Include . - - - -
- >Annotation Property Category Code Sequence - - (006A,0009) - - 1 - - Sequence defining the general category of the property the Annotation Group represents. - Only a single Item shall be included in this Sequence. -
- - >>Include - - - - - B. - -
- >Annotation Property Type Code Sequence - - (006A,000A) - - 1 - - Sequence defining the specific property the Annotation Group represents. - Only a single Item shall be included in this Sequence. -
- - >>Include - - - - - B. - -
- >>Annotation Property Type Modifier Code Sequence - - (006A,000B) - - 3 - - Sequence defining the modifier of the property type of this Annotation Group. - One or more Items are permitted in this Sequence. -
- - >>>Include - - - - - No Baseline CID is defined. - -
- >Number of Annotations - - (006A,000C) - - 1 - - The number of Annotations in this Annotation Group. - Each point, polyline or polygon, ellipse or rectangle is counted as one Annotation. -
- >Graphic Type - - (0070,0023) - - 1 - - The shape of the Annotations in this Annotation Group. See . - - Enumerated Values: - - POINT - - a single location denoted by a single coordinate - - - - POLYLINE - - a series of connected line segments with ordered vertices denoted by coordinates forming an open polyline; the points shall be coplanar - - - - POLYGON - - a series of connected line segments with ordered vertices denoted by coordinates, where the first and last vertices are not the same but are implicitly joined to form a closed polygon; the points shall be coplanar - - - - ELLIPSE - - an ellipse defined by four coordinates, the first two points specifying the endpoints of the major axis and the second two points specifying the endpoints of the minor axis of an ellipse; the points shall be coplanar - - - - RECTANGLE - - a rectangle defined by four coordinates, the first being the top left hand corner (when viewed from the top surface of the slide towards the bottom), then the top right hand corner, then the bottom right hand corner and finally the bottom left hand corner; the points shall be coplanar - - - - - Individual Annotations in the same group are not required to be in the same plane. - -
- >Annotation Applies to All Optical Paths - - (006A,000D) - - 1 - - Whether the Annotations in this Annotation Group apply to all the optical paths within the corresponding images. - - Enumerated Values: - - YES - - the Annotations apply to all optical paths - - - - NO - - the Annotations apply only to the specified optical path(s) - - - -
- >Referenced Optical Path Identifier - - (006A,000E) - - 1C - - Identifies one or more optical paths to which this Annotation applies. - Refers to the same value in Optical Path Identifier (0048,0106) within the Optical Path Sequence (0048,0105) in the images to which this Annotation applies. - More than one value may be present if the Annotations apply to more than one (but not all) Optical Paths. - Required if Annotation Applies to All Optical Paths (006A,000D) is NO. -
- >Annotation Applies to All Z Planes - - (006A,000F) - - 1C - - Whether the Annotations in this Annotation Group apply to the full thickness of the tissue on the slide. I.e., they are applicable regardless of the focal plane, in the case that images were acquired with multiple focal planes (Z-stacks). - - Enumerated Values: - - YES - - the Annotations apply to the full thickness - - - - NO - - the Annotations apply only to the specified Z plane - - - - - When the value is NO, the Z plane will be specified either in Common Z Coordinate Value (006A,0010) if all the coordinates are in the same Z plane(s), or in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) if not. - - Required if Annotation Coordinate Type (006A,0001) is 3D. -
- >Common Z Coordinate Value - - (006A,0010) - - 1C - - The Z coordinate(s) common to all points in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), in mm in the Slide Coordinate System () associated with the Frame of Reference. - More than one value may be present if the Annotations apply to more than one (but not all) Z planes. - Required if Annotation Coordinate Type (006A,0001) is 3D, and all points in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) are in the same Z plane(s). - - This requirement means that it is mandatory to factor out the commonality, i.e., it is not permitted to send Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) with (X, Y, Z) triplets where all the Z values are the same. For Annotations of images that only have a single Z plane, or where all the points in an Annotation Group are coplanar and in the same Z plane, this condition will always be satisfied. Annotations in different Z planes can be separated into separate Annotation Groups in order to allow this condition to be satisfied, but using separate Annotation Groups is not required. - - See . -
- >Point Coordinates Data - - (0066,0016) - - 1C - - The coordinates of one or more points that define the Annotations (whether single points or polygons), encoded in (X, Y) or (X, Y, Z) order. - Required if Double Point Coordinates Data (0066,0022) is not present. - For each point, two coordinates (X, Y) shall be encoded if Common Z Coordinate Value (006A,0010) is present, otherwise three coordinates (X, Y, Z) shall be encoded. - See . -
- >Double Point Coordinates Data - - (0066,0022) - - 1C - - The coordinates of one or more points that define the Annotations (whether single points or polygons), encoded in (X, Y) or (X, Y, Z) order. - Required if Point Coordinates Data (0066,0016) is not present. - For each point, two coordinates (X, Y) shall be encoded if Common Z Coordinate Value (006A,0010) is present, otherwise three coordinates (X, Y, Z) shall be encoded. - See . -
- >Long Primitive Point Index List - - (0066,0040) - - 1C - - A list of point indices. See . - Required if Graphic Type (0070,0023) is POLYLINE or POLYGON. -
- >Recommended Display CIELab Value - - (0062,000D) - - 3 - - Default triplet value in which it is recommended that the Annotation Group be rendered. The units are specified in PCS-Values, and the value is encoded as CIELab. - See . -
- >Measurements Sequence - - (0066,0121) - - 3 - - Measurements for some or all Annotations in the Annotation Group. Each Item describes one type of measurement. - See . - One or more Items are permitted in this Sequence. -
- >>Concept Name Code Sequence - - (0040,A043) - - 1 - - Defines the type of measurement stored in this Item. - Only a single Item shall be included in this Sequence. -
- - >>>Include - - - - - D. - -
- >>Measurement Units Code Sequence - - (0040,08EA) - - 1 - - Units of measurement for the value in this Item. - Only a single Item shall be included in this Sequence. -
- - >>>Include - - - - - D. - -
- >>Measurement Values Sequence - - (0066,0132) - - 1 - - The measurement values for the Annotation Group. - One or more Items shall be included in this Sequence. -
- >>>Floating Point Values - - (0066,0125) - - 1 - - Measurement values for Annotations stored in this Annotation Group. - If Annotation Index List (006A,0011) is present, measurement values are stored for a subset of Annotations, and the number of values shall match the number and order of indices in Annotation Index List (006A,0011). - If Annotation Index List (006A,0011) is absent, measurement values are stored for every Annotation in Long Primitive Point Index List (0066,0040), if present, and the number of values shall match the number and order of Annotations in Long Primitive Point Index List (0066,0040) . - If Annotation Index List (006A,0011) and Long Primitive Point Index List (0066,0040) are absent, measurement values are stored for every Annotation stored in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), and the number of values shall match thevalue of Number of Annotations (006A,000C). - See . -
- >>>Annotation Index List - - (006A,0011) - - 1C - - List of indices referencing Annotations identified in Long Primitive Point Index List (0066,0040) or successive points stored in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) for which measurement values shall be stored. - Required if Measurement Values stored in Floating Point Values (0066,0125) are associated with only a subset of Annotations. - See . -
-
- Microscopy Bulk Simple Annotations Module Attributes -
- Type, Points, Polygons, Parameterized and Rotated Shapes and Indices - All the Annotations in a single Item of Annotation Group Sequence (006A,0002) share the same value for Graphic Type (0070,0023). - If Annotation Coordinate Type (006A,0001) is 2D, then the coordinates are interpreted as image-relative, - either relative to an individual frame or the Total Pixel Matrix, with units of pixels, - as defined in . - If Pixel Origin Interpretation (0048,0301) is FRAME, - then a single frame of a single image shall be specified in Referenced Image Sequence (0008,1140). - If Pixel Origin Interpretation (0048,0301) is VOLUME, - then a single image shall be specified in Referenced Image Sequence (0008,1140) without a subset of frames designated, - and the coordinates are relative to the Total Image Matrix of that image. - The referenced image shall not be an instance of a Concatenation; - i.e., in the case of Concatenations, references shall be relative to the SOP Instance UID of Concatenation Source (0020,0242). - - + Microscopy Bulk Simple Annotations Module + + specifies the Attributes of the , which describe the Microscopy Bulk Simple Annotations. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Microscopy Bulk Simple Annotations Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ + Include + + + + +
+ Content Date + + (0008,0023) + + 1 + + The date the content creation started. +
+ Content Time + + (0008,0033) + + 1 + + The time the content creation started. +
+ Annotation Coordinate Type + + (006A,0001) + + 1 + + Whether coordinates are image-relative (2D) or volume-relative (3D). + + Enumerated Values: + + 2D + + relative to individual frame or total image matrix + + + + 3D + + relative to a Cartesian coordinate system defined by a Frame of Reference + + + +
+ Pixel Origin Interpretation + + (0048,0301) + + 1C + + For image-relative coordinates, specifies whether coordinates are to be interpreted relative to the individual frame pixel origins, or relative to the Total Pixel Matrix origin (see Section C.8.12.4.1.4). + Required if Annotation Coordinate Type (006A,0001) is 2D. + + Enumerated Values: + + FRAME + + relative to individual frame + + + + VOLUME + + relative to Total Image Matrix + + + + + The use of the term "VOLUME" to refer to the Total Image Matrix is historical and inherited from Presentation States, and does not refer to 3D coordinates. + +
+ Referenced Image Sequence + + (0008,1140) + + 1C + + The image to which this Annotation object applies. + Only a single Item shall be included in this Sequence. + Required if Annotation Coordinate Type (006A,0001) is 2D. May be present otherwise. +
+ + >Include + + + + + + +
+ Annotation Group Sequence + + (006A,0002) + + 1 + + Groups of Annotations sharing common characteristics, such as graphic type, properties or measurements. + One or more Items shall be included in this Sequence. +
+ >Annotation Group Number + + (0040,A180) + + 1 + + Identification number of the Annotation Group. Uniquely identifies a Annotation Group within this SOP Instance. Shall start at a value of 1, and increase monotonically by 1. +
+ >Annotation Group UID + + (006A,0003) + + 1 + + Unique identifier of the Annotation Group. +
+ >Annotation Group Label + + (006A,0005) + + 1 + + User-defined label identifying this Annotation Group. This may be the same as Code Meaning (0008,0104) of Annotation Property Type Code Sequence (006A,000A). +
+ >Annotation Group Description + + (006A,0006) + + 3 + + User-defined description for this Annotation Group. +
+ >Annotation Group Generation Type + + (006A,0007) + + 1 + + Type of algorithm used to generate the Annotations. + + Enumerated Values: + + AUTOMATIC + + generated by algorithm without human user assistance + + + + SEMIAUTOMATIC + + generated by algorithm with human user assistance + + + + MANUAL + + generated by human user + + + +
+ >Annotation Group Algorithm Identification Sequence + + (006A,0008) + + 1C + + The algorithms used to create the Annotations in this group. + One or more Items shall be included in this Sequence. + Required if Annotation Generation Type (006A,0007) is AUTOMATIC or SEMIAUTOMATIC. +
+ + >>Include . + + + +
+ + >Include + + + + + May not be necessary if the anatomy is implicit in the Annotation Property Type Code Sequence (006A,000A). + + + More than one Item in Anatomic Region Sequence (0008,2218) may be used when a region of interest spans multiple anatomical locations and there is not a single pre-coordinated code describing the combination of locations. There is no requirement that the multiple locations be contiguous. + +
+ >Annotation Property Category Code Sequence + + (006A,0009) + + 1 + + Sequence defining the general category of the property the Annotation Group represents. + Only a single Item shall be included in this Sequence. +
+ + >>Include + + + + + B. + +
+ >Annotation Property Type Code Sequence + + (006A,000A) + + 1 + + Sequence defining the specific property the Annotation Group represents. + Only a single Item shall be included in this Sequence. +
+ + >>Include + + + + + B. + +
+ >>Annotation Property Type Modifier Code Sequence + + (006A,000B) + + 3 + + Sequence defining the modifier of the property type of this Annotation Group. + One or more Items are permitted in this Sequence. +
+ + >>>Include + + + + + No Baseline CID is defined. + +
+ >Number of Annotations + + (006A,000C) + + 1 + + The number of Annotations in this Annotation Group. + Each point, polyline or polygon, ellipse or rectangle is counted as one Annotation. +
+ >Graphic Type + + (0070,0023) + + 1 + + The shape of the Annotations in this Annotation Group. See . + + Enumerated Values: + + POINT + + a single location denoted by a single coordinate + + + + POLYLINE + + a series of connected line segments with ordered vertices denoted by coordinates forming an open polyline; the points shall be coplanar + + + + POLYGON + + a series of connected line segments with ordered vertices denoted by coordinates, where the first and last vertices are not the same but are implicitly joined to form a closed polygon; the points shall be coplanar + + + + ELLIPSE + + an ellipse defined by four coordinates, the first two points specifying the endpoints of the major axis and the second two points specifying the endpoints of the minor axis of an ellipse; the points shall be coplanar + + + + RECTANGLE + + a rectangle defined by four coordinates, the first being the top left hand corner (when viewed from the top surface of the slide towards the bottom), then the top right hand corner, then the bottom right hand corner and finally the bottom left hand corner; the points shall be coplanar + + + + + Individual Annotations in the same group are not required to be in the same plane. + +
+ >Annotation Applies to All Optical Paths + + (006A,000D) + + 1 + + Whether the Annotations in this Annotation Group apply to all the optical paths within the corresponding images. + + Enumerated Values: + + YES + + the Annotations apply to all optical paths + + + + NO + + the Annotations apply only to the specified optical path(s) + + + +
+ >Referenced Optical Path Identifier + + (006A,000E) + + 1C + + Identifies one or more optical paths to which this Annotation applies. + Refers to the same value in Optical Path Identifier (0048,0106) within the Optical Path Sequence (0048,0105) in the images to which this Annotation applies. + More than one value may be present if the Annotations apply to more than one (but not all) Optical Paths. + Required if Annotation Applies to All Optical Paths (006A,000D) is NO. +
+ >Annotation Applies to All Z Planes + + (006A,000F) + + 1C + + Whether the Annotations in this Annotation Group apply to the full thickness of the tissue on the slide. I.e., they are applicable regardless of the focal plane, in the case that images were acquired with multiple focal planes (Z-stacks). + + Enumerated Values: + + YES + + the Annotations apply to the full thickness + + + + NO + + the Annotations apply only to the specified Z plane + + + + + When the value is NO, the Z plane will be specified either in Common Z Coordinate Value (006A,0010) if all the coordinates are in the same Z plane(s), or in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) if not. + + Required if Annotation Coordinate Type (006A,0001) is 3D. +
+ >Common Z Coordinate Value + + (006A,0010) + + 1C + + The Z coordinate(s) common to all points in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), in mm in the Slide Coordinate System () associated with the Frame of Reference. + More than one value may be present if the Annotations apply to more than one (but not all) Z planes. + Required if Annotation Coordinate Type (006A,0001) is 3D, and all points in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) are in the same Z plane(s). + + This requirement means that it is mandatory to factor out the commonality, i.e., it is not permitted to send Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) with (X, Y, Z) triplets where all the Z values are the same. For Annotations of images that only have a single Z plane, or where all the points in an Annotation Group are coplanar and in the same Z plane, this condition will always be satisfied. Annotations in different Z planes can be separated into separate Annotation Groups in order to allow this condition to be satisfied, but using separate Annotation Groups is not required. + + See . +
+ >Point Coordinates Data + + (0066,0016) + + 1C + + The coordinates of one or more points that define the Annotations (whether single points or polygons), encoded in (X, Y) or (X, Y, Z) order. + Required if Double Point Coordinates Data (0066,0022) is not present. + For each point, two coordinates (X, Y) shall be encoded if Common Z Coordinate Value (006A,0010) is present, otherwise three coordinates (X, Y, Z) shall be encoded. + See . +
+ >Double Point Coordinates Data + + (0066,0022) + + 1C + + The coordinates of one or more points that define the Annotations (whether single points or polygons), encoded in (X, Y) or (X, Y, Z) order. + Required if Point Coordinates Data (0066,0016) is not present. + For each point, two coordinates (X, Y) shall be encoded if Common Z Coordinate Value (006A,0010) is present, otherwise three coordinates (X, Y, Z) shall be encoded. + See . +
+ >Long Primitive Point Index List + + (0066,0040) + + 1C + + A list of point indices. See . + Required if Graphic Type (0070,0023) is POLYLINE or POLYGON. +
+ >Recommended Display CIELab Value + + (0062,000D) + + 3 + + Default triplet value in which it is recommended that the Annotation Group be rendered. The units are specified in PCS-Values, and the value is encoded as CIELab. + See . +
+ >Measurements Sequence + + (0066,0121) + + 3 + + Measurements for some or all Annotations in the Annotation Group. Each Item describes one type of measurement. + See . + One or more Items are permitted in this Sequence. +
+ >>Concept Name Code Sequence + + (0040,A043) + + 1 + + Defines the type of measurement stored in this Item. + Only a single Item shall be included in this Sequence. +
+ + >>>Include + + + + + D. + +
+ >>Measurement Units Code Sequence + + (0040,08EA) + + 1 + + Units of measurement for the value in this Item. + Only a single Item shall be included in this Sequence. +
+ + >>>Include + + + + + D. + +
+ >>Measurement Values Sequence + + (0066,0132) + + 1 + + The measurement values for the Annotation Group. + One or more Items shall be included in this Sequence. +
+ >>>Floating Point Values + + (0066,0125) + + 1 + + Measurement values for Annotations stored in this Annotation Group. + If Annotation Index List (006A,0011) is present, measurement values are stored for a subset of Annotations, and the number of values shall match the number and order of indices in Annotation Index List (006A,0011). + If Annotation Index List (006A,0011) is absent, measurement values are stored for every Annotation in Long Primitive Point Index List (0066,0040), if present, and the number of values shall match the number and order of Annotations in Long Primitive Point Index List (0066,0040) . + If Annotation Index List (006A,0011) and Long Primitive Point Index List (0066,0040) are absent, measurement values are stored for every Annotation stored in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), and the number of values shall match thevalue of Number of Annotations (006A,000C). + See . +
+ >>>Annotation Index List + + (006A,0011) + + 1C + + List of indices referencing Annotations identified in Long Primitive Point Index List (0066,0040) or successive points stored in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) for which measurement values shall be stored. + Required if Measurement Values stored in Floating Point Values (0066,0125) are associated with only a subset of Annotations. + See . +
+
+ Microscopy Bulk Simple Annotations Module Attribute Descriptions +
+ Type, Points, Polygons, Parameterized and Rotated Shapes and Indices + All the Annotations in a single Item of Annotation Group Sequence (006A,0002) share the same value for Graphic Type (0070,0023). + If Annotation Coordinate Type (006A,0001) is 2D, then the coordinates are interpreted as image-relative, either relative to an individual frame or the Total Pixel Matrix, with units of pixels, as defined in . If Pixel Origin Interpretation (0048,0301) is FRAME, then a single frame of a single image shall be specified in Referenced Image Sequence (0008,1140). If Pixel Origin Interpretation (0048,0301) is VOLUME, then a single image shall be specified in Referenced Image Sequence (0008,1140) without a subset of frames designated, and the coordinates are relative to the Total Image Matrix of that image. The referenced image shall not be an instance of a Concatenation; i.e., in the case of Concatenations, references shall be relative to the SOP Instance UID of Concatenation Source (0020,0242). + + + + The referenced image need not be any particular resolution layer of a WSI pyramid. I.e., it may or may not be the highest resolution layer. The user may annotate images that are not at the highest resolution, but such Annotations may be projected onto any resolution layer that is available (or computed). If the referenced image is no longer stored or accessible, the ability to project the Annotations onto other layers may be lost. + + + A reference to a single frame means that all Annotations in this instance are on that frame; no mechanism is provided to span frames, or to specify more than one frame. + + + + If Annotation Coordinate Type (006A,0001) is 3D, then the X, Y and Z coordinates are interpreted as volume relative, with units of mm, in the Cartesian space defined by the Frame of Reference UID. + + + + A single referenced image may be specified even if Annotation Coordinate Type (006A,0001) is 3D. It need not be any particular resolution layer of a WSI pyramid, but may be interpreted as a suitable layer on which to render, select from or otherwise apply the Annotation. In particular, it may not be the highest resolution layer. Regardless, the Annotations are applicable to any image in the same Frame of Reference. + + + The use of millimeters as the unit for the Z coordinates is inconsistent with the use of microns for the Z Offset in Slide Coordinate System (0040,074A) in the . + + + + If the Annotations are points, then + + + Graphic Type (0070,0023) shall have a value of POINT. + + + All the points in the group shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), concatenated one after another, with Z factored out into Common Z Coordinate Value (006A,0010), if common. + + + Long Primitive Point Index List (0066,0040) shall not be present, because there is no need for a separate index of each Annotation. + + + Number of Annotations (006A,000C) will contain the number of points, which shall also be the number of coordinate tuples in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022). + + + If the Annotations are open polylines, then + + + Graphic Type (0070,0023) shall have a value of POLYLINE. + + + The points of each polyline shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), concatenated one after another, with Z factored out into Common Z Coordinate Value (006A,0010), if common. + + + The order of the encoded points is from the first point to the last point of the polyline. + + + The index in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) of each successive polyline is encoded in Long Primitive Point Index List (0066,0040), which shall contain Number of Annotations (006A,000C) values. + + + If the Annotations are closed polygons, then + + + Graphic Type (0070,0023) shall have a value of POLYGON. + + + The points of each polygon shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), concatenated one after another, with Z factored out into Common Z Coordinate Value (006A,0010), if common. + + + The order of the encoded points is from the first point to the last point of the polygon. The first point and the last point shall not be the same, but rather they are implicitly joined to close the polygon. + + + The index in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) of each successive polygon is encoded in Long Primitive Point Index List (0066,0040), which shall contain Number of Annotations (006A,000C) values. + + + + This closed polygon representation differs from that used in Presentation States () and Structured Reports ( and ), none of which are implicitly closed, and required replication of the first point as the last point. + + If the Annotations are circles or ellipses, then + + + Graphic Type (0070,0023) shall have a value of ELLIPSE. + + + The end points of the major and minor axes of the ellipses in the group shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), with Z factored out into Common Z Coordinate Value (006A,0010) if common. + + + Long Primitive Point Index List (0066,0040) shall not be present, because the index of each Annotation can be computed. Number of Annotations (006A,000C) will contain the number of ellipses, which shall also be one quarter of the number of coordinate tuples in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022). + + + + If the length of the major and minor axes are the same, then the ellipse is a circle; a simpler (e.g., 2 point) encoding of a circle is not defined, since the plane of the circle would be unspecified without a third point. + + If the Annotations are squares or rectangles, then + + + Graphic Type (0070,0023) shall have a value of RECTANGLE. + + + All the corner points of the rectangles in the group shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), with Z factored out into Common Z Coordinate Value (006A,0010) if common. + + + Long Primitive Point Index List (0066,0040) shall not be present, because the index of each Annotation can be computed. Number of Annotations (006A,000C) will contain the number of rectangles, which shall also be one quarter of the number of coordinate tuples in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022). + + + + If the lengths of the perpendicular edges are the same, then the rectangle is a square. This rectangle representation is the same as if the rectangle were encoded as an implicitly closed polygon, except that the number of points is fixed and Long Primitive Point Index List (0066,0040) is absent. A simpler (e.g., 2 point TLHC, BRHC) encoding of a rectangle is not defined, since the plane of the rectangle would then be unspecified without a third point. + + The index used in Long Primitive Point Index List (0066,0040) of the first value of the first coordinate tuple in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) shall be 1. + The polylines and polygons encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) shall be in the same order as Long Primitive Point Index List (0066,0040). I.e., the values of Long Primitive Point Index List (0066,0040) are strictly increasing. + + This means that the first value of Long Primitive Point Index List (0066,0040) is always 1. + + Open polylines and implicitly closed polygons shall have their vertices encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) in clockwise winding order when viewed from the top surface of the slide towards the bottom, per . The line segments shall not cross (i.e., shall be simple polygons, not complex polygons), and shall not contain holes (i.e., the keyhole technique described for RT Structure Sets (), shall not be used). + The plane of the coplanar points is not required to correspond to an image plane or be parallel to the slide surface; the points are only required to be coplanar in a geometric sense (i.e., they need not all have the same Z coordinate value). +
+
+ Measurements + For each Annotation Group, optionally one or more measurements may be defined, either for every Annotation or a subset of Annotations. Measurements are described by coded type and unit. + When there is a measurement for every Annotation, then Floating Point Values (0066,0125) contains the corresponding values for each of the Annotations. When there are measurements for only a subset of Annotations, then Floating Point Values (0066,0125) contains measurement values for the Annotations that are referenced in Annotation Index List (006A,0011). + More than one Measurements Sequence (0066,0121) Item may be used, for example to encode different types of measurements, or to encode different components of a measurement that is a tuple. + Within one Annotation Group the types of measurements are the same for all Annotations within that group. +
+
+
+
+
+
+ Inventory Modules +
+ Inventory Module + + specifies the Attributes of the . + The Attributes of the Information Entities of the Inventory Information Model (such as Study, Series, Patient, etc. - see ) are hierarchically encoded within Sequence Attributes in this Module. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Inventory Module Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Content Date + + (0008,0023) + + 1 + + With Content Time (0008,0033), time point at which the Inventory creation began. See . +
+ Content Time + + (0008,0033) + + 1 + + With Content Date (0008,0023), time point at which the Inventory creation began. See . +
+ + Include + + + + + Selection parameters for the studies that are included in the inventory. See . + +
+ Transaction UID + + (0008,1195) + + 1C + + UID of the transaction that initiated creation of this Inventory SOP Instance. + Required if Inventory creation was initiated by a transaction of the Inventory Creation SOP Class. May be present otherwise to identify a local user-initiated or system-initiated Inventory creation. +
+ Inventory Purpose + + (0008,0401) + + 2 + + Purpose for which the inventory was created. +
+ Inventory Instance Description + + (0008,0402) + + 3 + + Description of the content of this Inventory SOP Instance, such as limitation of the scope of this Instance within the Scope of Inventory. +
+ Inventory Level + + (0008,0403) + + 1 + + Information Entity level for records included in Inventory. + + Enumerated Values: + + STUDY + + Study records only + + + + SERIES + + Study and Series records only + + + + INSTANCE + + Study, Series, and Instance records + + + +
+ Inventory Completion Status + + (0008,0426) + + 1 + + Degree of completion of Inventory with respect to the defined Scope of Inventory. See . +
+ Number of Study Records in Instance + + (0008,0427) + + 1 + + Number of Items in the Inventoried Studies Sequence (0008,0423) in this SOP Instance. +
+ Total Number of Study Records + + (0008,0428) + + 1 + + Total number of Items in the Inventoried Studies Sequence (0008,0423) in this SOP Instance and in SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). + + A Study that appears multiple times among the Inventoried Studies Sequence (0008,0423) Items will be counted for each appearance. + +
+ Inventory Access End Points Sequence + + (0008,0420) + + 3 + + Baseline end point(s) for network protocols to access incorporated Inventory SOP Instances. See . + Only a single Item is permitted in this Sequence. +
+ + >Include + + + +
+ Study Access End Points Sequence + + (0008,0421) + + 3 + + Baseline end point(s) for network protocols to access inventoried Study-related SOP Instances. See . + Only a single Item is permitted in this Sequence. +
+ + >Include + + + +
+ Incorporated Inventory Instance Sequence + + (0008,0422) + + 2 + + Inventory SOP Instances whose content is included by reference. See . + Zero or more Items shall be included in this Sequence. +
+ + >Include + + + +
+ Inventoried Studies Sequence + + (0008,0423) + + 2 + + Records of Studies whose Attribute values match the Scope of Inventory. See . + Zero or more Items shall be included in this Sequence. +
+ >Specific Character Set + + (0008,0005) + + 1C + + Character Set that expands or replaces the Basic Graphic Set for this Item. + Required if an extended or replacement character set, other than those specified in the top level Data Set of the Inventory, is used in the Study level Attributes. May be present otherwise. +
+ >Study Instance UID + + (0020,000D) + + 1 + + Unique identifier for the inventoried Study. +
+ >Modalities in Study + + (0008,0061) + + 2 + + All of the distinct values used for Modality (0008,0060) in the Series of the Study. +
+ >Item Inventory DateTime + + (0008,0404) + + 1 + + DateTime of creation of the Inventory information for this Item. All Study Attributes in this Sequence Item are correct as of this DateTime. The value shall be at or after the Content Date (0008,0023) and Content Time (0008,0033) of this Inventory SOP Instance. + + This Attribute may be used for Study record reconciliation. See . + +
+ >Removed from Operational Use + + (0008,0405) + + 1C + + Flag that this Study is not to be used for operational purposes. See . + + Enumerated Values: + + Y + + Removed from use + + + + N + + Not removed from use + + + + Required if this Study is not to be used for operational purposes. May be present otherwise. +
+ >Reason for Removal Code Sequence + + (0008,0406) + + 2C + + Reason the Study was removed from operational use. + Required if Removed from Operational Use (0008,0405) value is Y. + Zero or one Item shall be included in this Sequence. +
+ + >>Include + + + + + Defined Context Group DCID 7031 Reason for Removal from Operational Use. + +
+ >Number of Study Related Series + + (0020,1206) + + 2 + + Count of stored Series in Study. See . +
+ >Number of Study Related Instances + + (0020,1208) + + 2 + + Count of stored SOP Instances in Study. See . +
+ >Study Update DateTime + + (0008,041F) + + 2 + + DateTime of last update to Study instances or metadata managed in the storage system. See . +
+ >Study ID + + (0020,0010) + + 2 + + User or equipment generated Study identifier. +
+ >Study Date + + (0008,0020) + + 2 + + Date the Study started. +
+ >Study Time + + (0008,0030) + + 2 + + Time the Study started. +
+ >Study Description + + (0008,1030) + + 2 + + Description or classification of the Study performed. +
+ >Anatomic Regions in Study Code Sequence + + (0008,0063) + + 3 + + Anatomic regions and body parts examined in the study. See . + One or more Items are permitted in this Sequence. +
+ + >>Include + + + +
+ >Procedure Code Sequence + + (0008,1032) + + 3 + + Type of procedure performed. + One or more Items are permitted in this Sequence. +
+ + >>Include + + + +
+ >Name of Physician(s) Reading Study + + (0008,1060) + + 3 + + Names of the physician(s) reading the Study. +
+ >Physician(s) Reading Study Identification Sequence + + (0008,1062) + + 3 + + Identification of the physician(s) reading the Study. + One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Name of Physician(s) Reading Study (0008,1060), if present. +
+ + >>Include + + + +
+ >Consulting Physician's Name + + (0008,009C) + + 3 + + Consulting physician(s) for this Patient Visit. +
+ >Consulting Physician Identification Sequence + + (0008,009D) + + 3 + + Identification of the consulting physician(s). + One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Consulting Physician's Name (0008,009C), if present. +
+ + >>Include + + + +
+ >Physician(s) of Record + + (0008,1048) + + 3 + + Names of the physician(s) who are responsible for overall Patient care at time of Study. +
+ >Physician(s) of Record Identification Sequence + + (0008,1049) + + 3 + + Identification of the physician(s) who are responsible for overall Patient care at time of Study. + One or more Items are permitted in this Sequence. If more than one Item, the number and order shall correspond to the value of Physician(s) of Record (0008,1048), if present. +
+ + >>Include + + + +
+ + >Include + + + + + Recording of prior Attribute values and provenance of metadata changes at the Study level. See . + +
+ >Retrieve AE Title + + (0008,0054) + + 1C + + AE Title from which this Study may be retrieved. + Required if Study SOP Instances may be retrieved using a C-MOVE or C-GET based SOP Class (see PS3.4) and Study Access End Points Sequence (0008,0421) does not include Retrieve AE Title (0008,0054). May be present otherwise. +
+ >Retrieve URL + + (0008,1190) + + 1C + + Base URI of the origin server to retrieve Study data through the Studies Service (see ). + Required if Study SOP Instances may be retrieved using the web-based Studies Service (see ) and Study Access End Points Sequence (0008,0421) does not include Retrieve URL (0008,1190). May be present otherwise. +
+ >Stored Instance Base URI + + (0008,0407) + + 3 + + Base URI for accessing Study SOP Instances through a non-DICOM protocol. See . +
+ >Instance Availability + + (0008,0056) + + 3 + + Specifies how rapidly the Study becomes available for transmission after a retrieval request. See . +
+ >File Set Access Sequence + + (0008,0419) + + 3 + + Non-DICOM protocol methods to access the set of stored SOP Instances comprising the Study. + + "File Set" as used here may not be identical to the File-set concept defined in and used in Storage Media File-set ID (0088,0130). + + Only a single Item is permitted in this Sequence. +
+ >>Folder Access URI + + (0008,0408) + + 3 + + Access URI for a folder containing all SOP Instances for this Study. See . +
+ >>File Access URI + + (0008,0409) + + 3 + + Access URI for a container file containing all SOP Instances for this Study. See . +
+ >>Container File Type + + (0008,040A) + + 1C + + Type of container file. See for Defined Terms. + Required if File Access URI (0008,0409) is present. +
+ >Storage Media File-set ID + + (0088,0130) + + 3 + + A human readable Identifier that identifies the Storage Media on which the Study resides. +
+ >Accession Number + + (0008,0050) + + 2 + + A number that identifies the order for the Study. +
+ >Issuer of Accession Number Sequence + + (0008,0051) + + 3 + + Identifier of the Assigning Authority that issued the Accession Number (0008,0050). + Only a single Item is permitted in this Sequence. +
+ +>>Include + + + +
+ >Referring Physician's Name + + (0008,0090) + + 3 + + Name of the Patient's referring physician. +
+ >Referring Physician Identification Sequence + + (0008,0096) + + 3 + + Identification of the Patient's referring physician. + Only a single Item is permitted in this Sequence. +
+ + >>Include + + + +
+ >Patient's Name + + (0010,0010) + + 2 + + Patient's full name. +
+ >Patient ID + + (0010,0020) + + 2 + + Primary identifier for the Patient. +
+ + >Include + + + + + Identifier of the Assigning Authority that issued the Patient ID (0010,0020). + +
+ >Other Patient IDs Sequence + + (0010,1002) + + 3 + + Identification numbers or codes used to identify the Patient. + One or more Items are permitted in this Sequence. +
+ >>Patient ID + + (0010,0020) + + 2 + + An identifier for the Patient. +
+ + >>Include + + + + + Identifier of the Assigning Authority that issued the Patient ID (0010,0020). + +
+ >Patient's Birth Date + + (0010,0030) + + 2 + + Birth date of the Patient. +
+ >Patient's Sex + + (0010,0040) + + 2 + + Sex of the named Patient. +
+ >Other Patient Names + + (0010,1001) + + 3 + + Other names used to identify the Patient. +
+ >Inventoried Series Sequence + + (0008,0424) + + 2C + + Records of Series whose Study and Series Attribute values match the Scope of Inventory. + See for conditions with RELATIONAL matching for Scope of Inventory in which only matching Series will be included in the Inventory. + Required if Inventory Level (0008,0403) has value SERIES or INSTANCE. + Zero or more Items shall be included in this Sequence. +
+ >>Specific Character Set + + (0008,0005) + + 1C + + Character Set that expands or replaces the Basic Graphic Set for this Item. + Required if an extended or replacement character set, other than those specified or implied for the Study level Attributes, is used in the Series level Attributes. May be present otherwise. +
+ >>Series Instance UID + + (0020,000E) + + 1 + + Unique identifier of the inventoried Series. +
+ >>Modality + + (0008,0060) + + 1 + + Type of device, process or method that originally acquired or produced the data used to create the Instances in this Series. +
+ >>Removed from Operational Use + + (0008,0405) + + 1C + + Flag that this Series is not to be used for operational purposes. See . + + Enumerated Values: + + Y + + Removed from use + + + + N + + Not removed from use + + + + Required if this Series is not to be used for operational purposes, and Removed from Operational Use (0008,0405) Attribute at Study level does not have the value Y. May be present otherwise. +
+ >>Reason for Removal Code Sequence + + (0008,0406) + + 2C + + Reason the Series was removed from operational use. + Required if Removed from Operational Use (0008,0405) value is Y. + Zero or one Item shall be included in this Sequence. +
+ + >>>Include + + + + + Defined Context Group DCID 7031 Reason for Removal from Operational Use. + +
+ >>Series Number + + (0020,0011) + + 2 + + A number that identifies this Series. +
+ >>Series Description + + (0008,103E) + + 3 + + Description of the Series. +
+ >>Series Date + + (0008,0021) + + 3 + + Date the Series started. +
+ >>Series Time + + (0008,0031) + + 3 + + Time the Series started. +
+ >>Body Part Examined + + (0018,0015) + + 3 + + Identification of the part of the body examined. See . +
+ >>Laterality + + (0020,0060) + + 3 + + Laterality of (paired) body part examined. +
+ >>Request Attributes Sequence + + (0040,0275) + + 3 + + Attributes from the Imaging Service Request. See . + One or more Items are permitted in this Sequence. +
+ + >>>Include + + + +
+ + >>Include + + + + Recording of prior Attribute values and provenance of metadata changes at the Series level. See . +
+ >>Stored Instance Base URI + + (0008,0407) + + 3 + + Base URI for accessing SOP Instances within this Series through a non-DICOM protocol. See . +
+ >>Instance Availability + + (0008,0056) + + 3 + + Specifies how rapidly the Series becomes available for transmission after a retrieval request. See . +
+ >>File Set Access Sequence + + (0008,0419) + + 3 + + Non-DICOM protocol methods to access the set of stored SOP Instances comprising this Series. + + "File Set" as used here may not be identical to the File-set concept defined in and used in Storage Media File-set ID (0088,0130). + + Only a single Item is permitted in this Sequence. +
+ >>>Folder Access URI + + (0008,0408) + + 3 + + Access URI for a folder containing all SOP Instances for the Series. See . +
+ >>>File Access URI + + (0008,0409) + + 3 + + Access URI for a container file containing all SOP Instances for the Series. See . +
+ >>>Container File Type + + (0008,040A) + + 1C + + Type of container file. See for Defined Terms. + Required if File Access URI (0008,0409) is present. +
+ >>Storage Media File-set ID + + (0088,0130) + + 3 + + A human readable Identifier that identifies the Storage Media on which the Series resides. +
+ >>Inventoried Instances Sequence + + (0008,0425) + + 2C + + Records of SOP Instances whose Study, Series and Instance Attribute values match the Scope of Inventory. + See for conditions with RELATIONAL matching for Scope of Inventory in which only matching SOP Instances will be included in the Inventory. + Required if Inventory Level (0008,0403) has value INSTANCE. + Zero or more Items shall be included in this Sequence. +
+ >>>Specific Character Set + + (0008,0005) + + 1C + + Character Set that expands or replaces the Basic Graphic Set for this Item. + Required if an extended or replacement character set, other than those specified or implied for the Series level Attributes, is used in the Instance level Attributes. May be present otherwise. +
+ >>>SOP Class UID + + (0008,0016) + + 1 + + SOP Class UID of the inventoried SOP Instance. +
+ >>>SOP Instance UID + + (0008,0018) + + 1 + + SOP Instance UID of the inventoried SOP Instance. +
+ >>>Instance Number + + (0020,0013) + + 2 + + A number that identifies the inventoried SOP Instance. +
+ >>>Related General SOP Class UID + + (0008,001A) + + 3 + + Uniquely identifies a Related General SOP Class for the SOP Class of the inventoried Instance. +
+ >>>Content Date + + (0008,0023) + + 3 + + The date that creation of the content of the inventoried SOP Instance started. +
+ >>>Content Time + + (0008,0033) + + 3 + + The time that creation of the content of the inventoried SOP Instance started. +
+ >>>Timezone Offset From UTC + + (0008,0201) + + 3 + + Offset from UTC to the timezone for all DA and TM Attributes present in the inventoried Instance, and for all DT Attributes present in the inventoried Instance that do not contain an explicitly encoded timezone offset. + See . +
+ >>>Rows + + (0028,0010) + + 3 + + Number of pixel matrix rows in the inventoried Image SOP Instance. +
+ >>>Columns + + (0028,0011) + + 3 + + Number of pixel matrix columns in the inventoried Image SOP Instance. +
+ >>>Number of Frames + + (0028,0008) + + 3 + + Number of frames in the inventoried Image SOP Instance. +
+ >>>Bits Allocated + + (0028,0100) + + 3 + + Number of bits allocated for each pixel sample in the inventoried Image SOP Instance. +
+ >>>Observation DateTime + + (0040,A032) + + 3 + + The date and time at which the root Content Item of the inventoried Document SOP Instance was completed. +
+ >>>Concept Name Code Sequence + + (0040,A043) + + 3 + + A coded description of the content or type of the inventoried SOP Instance. + Only a single Item is permitted in this Sequence. +
+ + >>>>Include + + + + + No baseline CID is defined. + +
+ >>>Content Template Sequence + + (0040,A504) + + 3 + + Attributes of the Template that describes the content structure and constraints for the inventoried Document SOP Instance. + Only a single Item is permitted in this Sequence. +
+ >>>>Template Identifier + + (0040,DB00) + + 1 + + Identifier of the Template as defined by the Mapping Resource (0008.0105). +
+ >>>>Mapping Resource + + (0008,0105) + + 1 + + Resource that defines the Template. +
+ >>>Referenced Request Sequence + + (0040,A370) + + 3 + + Requested Procedures that were fulfilled (completely or partially) by the inventoried Document SOP Instance. + One or more Items are permitted in this Sequence. +
+ + >>>>Include + + + +
+ >>>Container Identifier + + (0040,0512) + + 3 + + Identifier for the physical container that contains the specimen(s) imaged in the inventoried SOP Instance. See . + + Not to be confused with a container file as described in . + +
+ >>>Specimen Description Sequence + + (0040,0560) + + 3 + + Identifiers for the specimen(s) imaged in the inventoried SOP Instance. See . + One or more Items are permitted in this Sequence. +
+ >>>>Specimen Identifier + + (0040,0551) + + 1 + + A departmental information system identifier for the Specimen. +
+ >>>>Specimen UID + + (0040,0554) + + 1 + + Unique Identifier for Specimen. +
+ >>>Content Label + + (0070,0080) + + 3 + + A label that is used to identify the inventoried SOP Instance. +
+ >>>Content Description + + (0070,0081) + + 3 + + A description of the content of the inventoried SOP Instance. +
+ >>>Presentation Creation Date + + (0070,0082) + + 3 + + Date on which the inventoried Presentation State SOP Instance was created. +
+ >>>Presentation Creation Time + + (0070,0083) + + 3 + + Time at which the inventoried Presentation State SOP Instance was created. +
+ >>>Content Creator's Name + + (0070,0084) + + 3 + + Name of operator who created the content of the inventoried SOP Instance. +
+ >>>Removed from Operational Use + + (0008,0405) + + 1C + + Flag that the inventoried SOP Instance is not to be used for operational purposes. See . + + Enumerated Values: + + Y + + Removed from use + + + + N + + Not removed from use + + + + Required if this SOP Instance is not to be used for operational purposes, and Removed from Operational Use (0008,0405) Attribute at Study or Series level does not have the value Y. May be present otherwise. +
+ >>>Reason for Removal Code Sequence + + (0008,0406) + + 2C + + Reason the SOP Instance was removed from operational use. + Required if Removed from Operational Use (0008,0405) value is Y. + Zero or one Item shall be included in this Sequence. +
+ + >>>>Include + + + + + D + + +
+ + >>>Include + + + + + Recording of prior Attribute values and provenance of metadata changes at the Instance level. See . + +
+ >>>Instance Availability + + (0008,0056) + + 3 + + Specifies how rapidly the Instance becomes available for transmission after a retrieval request. See . +
+ >>>File Access Sequence + + (0008,041A) + + 3 + + Non-DICOM protocol methods to access the SOP Instance in the DICOM File Format. See and . + One or more Items are permitted in this Sequence. +
+ +>>>>Include + + + +
+ >>>>Expiration DateTime + + (0008,0416) + + 3 + + The date and time until which the SOP Instance is expected to be available and after which SOP Instance is expected to be unavailable via this non-DICOM protocol URI. See . +
+ >>>Storage Media File-set ID + + (0088,0130) + + 3 + + A human readable Identifier that identifies the Storage Media on which the Instance resides. +
+ >>>Alternate Representation Sequence + + (0008,3001) + + 3 + + Reference to an alternate encoding of the inventoried SOP Instance. See . + One or more Items are permitted in this Sequence. +
+ >>>>Series Instance UID + + (0020,000E) + + 1C + + Unique identifier of the Series of the alternate representation. + Required if the alternate representation is in a different Series than the inventoried SOP Instance. +
+ >>>>SOP Class UID + + (0008,0016) + + 1 + + SOP Class UID of the alternate representation SOP Instance. +
+ >>>>SOP Instance UID + + (0008,0018) + + 1 + + SOP Instance UID of the alternate representation SOP Instance. +
+ >>>>Purpose of Reference Code Sequence + + (0040,A170) + + 1 + + The nature of the alternate encoding. + One Item shall be included in this Sequence. +
+ + >>>>>Include + + + + + B + + +
+
+ Inventory Instance Module Attribute Descriptions +
+ Content Date and Content Time + Content Date (0008,0023) and Content Time (0008,0033) establish thetime point at which began the creation of the Inventory for which this SOP Instance is the root. Conceptually, all Studies received by the storage system before this DateTime, and that match the specified Scope of Inventory key Attributes, are included in the Inventory, and all Patient and Study updates through this DateTime have been applied to the Attributes as recorded in the Inventory SOP Instance(s). + While Content Date and Time specify the nominal time for creation of the Inventory, each Study record has its own Item Inventory DateTime (0008,0404) that specifies the time of creation of that record, and its Attribute values are accurate as of that time. + Whether Studies and updates received after Content Date and Timemight be included in the Inventory is implementation specific. + The Content Date and Time of SOP Instances included by reference in the Incorporated Inventory Instance Sequence (0008,0422) may differ from the values of this SOP Instance. +
+
+ Scope of Inventory + The Scope of Inventory Sequence (0008,0400) specifies the matching rules for values of Attributes that select Studies to be included in the Inventory. It specifies the selection parameters for the current Inventory SOP Instance and all its subsidiary incorporated Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). The Scope of InventorySequence (0008,0400) within those subsidiary incorporated Instances is relevant only to their respective sub-trees, and may differ. + + For example, an Inventory SOP Instance may specify in its Scope of Inventory that it includes studies from the years 2015-2019, but it does that by linking five subsidiary Inventory SOP Instances, one for each year, and which each specifies in its Scope of Inventory the year to which it applies. + + While all Studies included in the Inventory will be within the Scope of Inventory, there may be Studies that match the Scope of Inventory that are not included in the Inventory if the Inventory is incomplete. The content of an Inventory SOP Instance, together with its subsidiary incorporated Instances, is complete with respect to the Scope of Inventory only if Inventory Completion Status (0008,0426) has the value COMPLETE. +
+
+ Inventory Completion Status + Inventory Completion Status (0008,0426) is the status of the Inventory represented by this SOP Instance, including all SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). The status is defined with respect to the Scope of Inventory as of the Content Date (0008,0023) and Content Time (0008,0033), for the repository system identified in the (see ). + + Enumerated Values: + + COMPLETE + + All Studies matching the Scope of Inventory are included in the Inventory SOP Instance and its subsidiary Incorporated Inventory SOP Instances + + + + FAILURE + + Production of the Inventory failed; some Studies matching the Scope of Inventory might not be included in the Inventory + + + + CANCELED + + Production of the Inventory was canceled; some Studies matching the Scope of Inventory might not be included in the Inventory + + + + PARTIAL + + Production of the inventory is incomplete; some Studies matching the Scope of Inventory might not be included in the Inventory + + + + + + + An Inventory may be COMPLETE and have no Study records, i.e., for the Repository identified in the , at the Content Date and Content Time, no Studies match the Scope of Inventory. + + + The reason for a value other than COMPLETE may be described in Inventory Instance Description (0008,0402). + + + COMPLETE, FAILURE, and CANCELED are statuses for the corresponding terminal states of the Inventory production process (see ). PARTIAL is a status representing continuing Inventory production, and this SOP Instance might be expected to be referenced in the Incorporated Inventory Instance Sequence (0400, 06x2) of the SOP Instance at the root of an Inventory tree. + + + See additional explanatory information and examples of use in . + + + +
+
+ Inventory Access End Points Sequence and Study Access End Points Sequence + The Inventory includes Attributes describing the available network access protocol(s) for referenced SOP Instances. The Inventory Access End Points Sequence (0008,0420) provides the default end points, i.e., network addresses, for access to Inventory SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). The Study Access End Points Sequence (0008,0421) provides the default end points for access to Study-related SOP Instances referenced in the Inventoried Studies Sequence (0008,0423). + These default end points apply only to references within the current SOP Instance; they do not set defaults for references within Inventory SOP Instances referenced in the Incorporated Inventory Instance Sequence (0008,0422). +
+
+ Incorporated Inventory Instance Sequence + For implementation specific reasons, the content of an Inventory may be divided into more than one Inventory SOP Instance. The Inventory SOP Instances are organized as a tree of referenced SOP Instances, with one SOP Instance as the root. The Incorporated Inventory Instance Sequence (0008,0422) specifies the links from an Inventory SOP Instance to its subsidiary Instances in the tree. The Incorporated Inventory Instance Sequence (0008,0422) definition recursively includes itself, thus allowing representation of the complete tree of referenced Inventory SOP Instances. + Inventory SOP Instances that are incorporated by reference shall have the same Inventory Level (0008,0403) as the current SOP Instance. + The inclusion of an Inventory SOP Instance reference in the Incorporated Inventory Instance Sequence (0008,0422) means that the Items of the Inventoried Studies Sequence (0008,0423) in that referenced SOP Instance are logically included in the current SOP Instance. Therefore, all inventoried Studies in the referenced SOP Instances shall be within the Scope of Inventory of the current SOP Instance. However, the Item Inventory DateTime (0008,0404) of those Study records may be prior to the Content Date (0008,0023) and Content Time (0008,0033) of the current SOP Instance. + + + + Reasons for splitting an Inventory might include practical limits on the maximum size of an individual SOP Instance, parallel processing across multiple separate subsystems, or reuse of historical Inventories. See . + + + These requirements apply to every Inventory SOP Instance. Thus, each Inventory SOP Instance will include in its Incorporated Inventory Instance Sequence (0008,0422) the complete tree of references to the subtree of which it is the root. + + + +
+
+ Inventoried Studies Sequence + The Inventoried Studies Sequence (0008,0423) references Studies whose Attributes match the Scope of Inventory. Within the tree of incorporated Inventory SOP Instances, a given Study may be referenced multiple times among the Inventoried Studies Sequence (0008,0423) Items. The Items may have different content, but each Item shall have a complete record of the contents of the Study as known by the creator of that Item. + + + + Differences in content may occur due to changes to the metadata or content (SOP Instances) of the Study during the production of the Inventory, or due to different Series of a Study being stored on different media, or for other reasons. The application using an Inventory may need to reconcile such multiple occurrences (see ). + + + If there are multiple records for a Study among the tree of incorporated SOP Instances, the Total Number of Study Records (0008,0428) value will reflect the number of records, not the number of unique Study UIDs. + + + +
+
+
+ Inventoried Study Attributes +
+ Study Update Datetime + Study Update DateTime (0008,041F) is the DateTime of the last update to Study contents (SOP Instances) or to Study metadata within the repository system. Metadata may change either due to coercion of Study related data (Patient ID, Study Description, Accession Number, etc.) to correspond with values set by the enterprise or department master information system (HIS / EMR / RIS), or due to other updates applied by the repository system. + As this is an Attribute of the Study as managed within the repository system, the initial Study Update DateTime (0008,041F) is the time that the Study was first received in the repository system, and is updated upon each new SOP Instance received for the Study, as well as for updates of patient, procedure, and other metadata. + + + + This Attribute, like Number of Study Related Series (0020,1206) and Number of Study Related Instances (0020,1208), is defined at the Study level of the Inventory Information Model, but is not part of the Study Attributes in SOP Instances. It is an Attribute that may be managed by the repository system, and might not have a value for some or all of the Studies in the Inventory. + + + Study Update DateTime (0008,041F) is not the time of last user access to the Study contents. + + + +
+
+ Removed From Operational Use and Reason For Removal Code Sequence + The Removed from Operational Use (0008,0405) Attribute is defined at the Study, Series, and Instance levels. A value of Y indicates the inventoried Study, Series, or Instance has been removed from operational use related to patient care, although it may be retained in the repository system for other reasons (e.g., for audit of patient radiation exposure). At the Study and Series level, the Attribute indicates whether the entire Study or Series has been removed from operational use. A value of Y at the Study level supersedes any value specified for subsidiary Series and Instances, and a value of Y at the Series level supersedes any value specified for subsidiary Instances. + + + + The meaning of "operational use related to patient care" is implementation or site specific, but generally includes diagnostic, clinical, and therapeutic uses, as well as administrative uses necessary for providing care (e.g., insurance authorization). + + + Studies, Series, or Instances might be marked as removed from operational use by actions associated with the processing of specific Key Object Selection Document SOP Instances, e.g., in accordance with Image Object Change Management Integration Profile (IOCM). Those Key Object Selection Document SOP Instances, and their Series, may themselves be marked as removed from operational use. The Context Group for Reason for Removal Code Sequence (0008,0406) includes the Key Object Selection Concept Codes specified in IOCM. + + + An image SOP Instance might be marked as removed from operational use because it has been replaced by a different (e.g., compressed) encoding of the image (see ). + + + The content of the Inventory might not match the information obtained through the Query/Retrieve Service since Studies, Series, or Instances in Inventory SOP Instances marked as removed from operational use might not appear in Query/Retrieve responses (e.g., see Section 4.66.4.1.3.1 Access to Rejected Instances). + + + While defined in this specification at the Study, Series, and Instance levels, an Application Entity might not manage this Attribute at some, or any, of those levels. E.g., an AE may only manage this Attribute at the Instance level, and is not required to infer a value for the Series or Study level. + + + If the Application Entity retains records of deleted Studies, Series, or Instances, even though the actual Instances are physically deleted, it may include those records in the Inventory with an appropriate Reason for Removal Code Sequence (0008,0406) value. Such instances may have an Instance Availability (0008,0056) value "UNAVAILABLE" (see ). + + + +
+
+ Number of Study Related Series, and Number of Study Related Instances + Number of Study Related Series (0020,1206) and Number of Study Related Instances (0020,1208) shall give accurate counts of Series and SOP Instances stored in the repository, respectively. The counts of Series and Instances shall include those that are marked as removed from operational use. + + These counts are not the number of Items in the Inventoried Series Sequence (0008,0424) and Inventoried Instances Sequence (0008,0425). Those Sequence Attributes may be absent depending on the value of Inventory Level (0008,0403). Further, if the Scope of Inventory indicates Relational matching to the Series or Instance level (see ), only Series and Instances matching the Scope of Inventory will be included in the Inventoried Series Sequence (0008,0424) and Inventoried Instances Sequence (0008,0425), and others present in the repository but not matching will not be recorded in the Inventory. + +
+
+ Anatomic Regions in Study Code Sequence + The Anatomic Regions in Study Code Sequence (0008,0063) consolidates the values of Anatomic Region Sequence (0008,2218) and Body Part Examined (0018,0015) in the SOP Instances of this Study. Recognized values of Body Part Examined can be transcoded to equivalent codes, such as by using the tables of , or by implementation- or site-specific mappings for locally defined terms. +
+
+ Original Attributes Macro + The Original Attributes Sequence (0400,0561) is defined at each of the Study, Series, and Instance levels in the Inventory IOD. + Within the Inventoried Studies Sequence (0008,0423), i.e., at the Study level, the Original Attributes Sequence (0400,0561) may be used to record the prior values of updated Study, Patient, and Imaging Study Request Attributes for the referenced Study, and the provenance of such updates (see ). Within the Inventoried Series Sequence (0400,06x4), i.e., at the Series level, and within the Inventoried Instances Sequence (0008,0425), i.e., at the Instance level, the Original Attributes Sequence may be used to record the prior values of updated Series and Instance Attributes, respectively, and the provenance of such updates (see ). + In the context of an Inventory SOP Instance, the "top level Data Set" in the definition of the Original Attributes Sequence (0400,0561) is the top level Data Set of the SOP Instances of the inventoried Study. + The Original Attributes Sequences (0400,0561) in the Inventory SOP Instance might not be identical to the Original Attributes Sequence (0400,0561) in the individual SOP Instances of the Study, and updates recorded in either location are valid (see ). + + While defined in this specification at the Study, Series, and Instance levels, an Application Entity might manage the Original Attributes Sequence (0400,0561) at only the Instance level. In such case, changes to Study, Patient, Imaging Study Request, and Series Attributes would be recorded at the Instance level for all affected SOP Instances. + +
+
+ Stored Instance Base URI + Stored Instance Base URI (0008,0407) is defined at the Inventory, Study, and Series levels in the Inventory IOD. + Stored Instance Base URI (0008,0407) contains an base URI that may be merged with relative path reference URIs for non-DICOM protocol access to SOP Instances of the Study or Series (see ). The Stored Instance Base URI (0008,0407) at the Study level establishes the default base URI for all relative path reference URIs in the Study, overriding a value specified at the Inventory level. Stored Instance Base URI (0008,0407) at the Series level establishes the default base URI for all relative path reference URIs in that Series overriding a value specified at the Inventory or Study level. + + + + At the Inventory level, Stored Instance Base URI (0008,0407) is specified in the Study Access End Points Sequence (0008,0421), setting the default base URI value for all Study records in the current Inventory SOP Instance. See . + + + Stored Instance Base URI (0008,0407) is optional, and if not present the values of Folder Access URI (0008,0408) and File Access URI (0008,0409) at the Study level must be complete URIs. If Stored Instance Base URI (0008,0407) is present, those other Attributes may still provide complete URIs, rather than relative paths to be merged with the Base URI. + + + See example uses of base URI and relative path reference URI in . + + + For any relative path reference URI, the base URI is the one specified in its level, if present, or successively at the next higher levels, until a Stored Instance Base URI (0008,0407) Attribute is present with a value. + + + +
+
+ Folder Access URI and File Access URI + If all of the stored SOP Instances of the Study, as identified in this Item, are in the DICOM File Format accessible through a non-DICOM protocol, and all the files are catalogued in a single folder (see ), Folder Access URI (0008,0408) provides the URI for protocol operations on that folder. + If all of the stored SOP Instances of the Study, as identified in this Item, are in a single container file as specified in , File Access URI (0008,0409) provides the URI for accessing that file. + Folder Access URI (0008,0408) and/or File Access URI (0008,0409) may be a relative path reference beginning with the single-dot-segment "./" (see ). In this case, the URI is merged with the Stored Instance Base URI (0008,0407) applicable to this Study (see ). + See for requirements on applying metadata from the Inventory SOP Instance to stored SOP Instances of the Study. + + + + The Study may be inventoried in more than one Item (see ). Only the SOP Instances identified within this Item (and its subsidiary Inventoried Instances Sequence (0008,0425) Attributes) need to be included in the folder or container file. + + + Stored SOP Instances from other Studies may be present in the folder or container file; the only requirement is that all of the identified SOP Instances of this Study are included. + + + If the SOP Instances of the Study are split across different container files, e.g., Series 1 and 2 in one container and Series 3 in a different container, then the conditional requirement for File Access URI (0008,0409) is not met and that Attribute is not used. However, if both of those container files are in the same folder, then Folder Access URI (0008,0408) may be present. + + + Files other than stored SOP Instances may be present in the folder or container file, e.g., reports in a non-DICOM file format. + + + These URIs provide complete access paths to the referenced folders and files, unlike the Retrieve URL (0008,1190) for the Studies Service (), which requires composition of the URI using the Study, Series, and/or SOP Instance UIDs. + + + +
+
+ Container File Type + Container File Type (0008,040A) identifies the type of container file accessible through the File Access URI (0008,0409). + + Defined Terms: + + ZIP + + see + + + + + TAR + + see + + + + + GZIP + + see + + + + + TARGZIP + + see + + + + + BLOB + + see + + + + + DICM + + Single SOP Instance in DICOM File Format (see ), not in a container + + + +
+
+ Instance Availability + Instance Availability (0008,0056) is defined at each of the Study, Series, and Instance levels in the Inventory IOD. It specifies how rapidly the Study, Series, or Instance becomes available for transmission after a retrieval request. For a Study or Series, when some Instances are less rapidly available than others, the value is the availability of the least rapidly available. + + Enumerated Values: + + ONLINE + + the instance is immediately available + + + + NEARLINE + + the instance needs to be retrieved from relatively slow media such as optical disk or tape, or requires conversion that takes time + + + + OFFLINE + + the instance needs to be retrieved by manual intervention + + + + UNAVAILABLE + + the instance cannot be retrieved + + + + + + + See also . + + + A Study, Series, or Instance that is UNAVAILABLE may also be marked as removed from operational use with Reason for Removal Code Sequence (0008,0406) value (130752, DCM, "Data Not Accessible from Storage"). + + + +
+
+
+ Inventoried Series Attributes +
+ Folder Access URI and File Access URI + If all of the stored SOP Instances of the Series are in the DICOM File Format accessible through a non-DICOM protocol, and all the files are catalogued in a single folder (see ), Folder Access URI (0008,0408) provides the URI for protocol operations on that folder. + If all of the stored SOP Instances of the Series are in a single container file as specified in , File Access URI (0008,0409) provides the URI for accessing that file. + Folder Access URI (0008,0408) and/or File Access URI (0008,0409) may be a relative path reference beginning with the single-dot-segment "./" (see ). In this case, the URI is merged with the Stored Instance Base URI (0008,0407) applicable to this Series (see ). + + See also and its associated notes. + +
+
+ Body Part Examined + Defined Terms for Body Part Examined (0018,0015) are found in . + Recognized values of Body Part Examined (0018,0015) can be transcoded to their equivalent codes, such as by using the tables of or by implementation-specific or site-specific mappings for locally defined terms. Those codes may beadded to the Study level Attribute Anatomic Regions in Study Code Sequence (0008,0063) (see ). +
+
+ Request Attributes Sequence + Request Attributes Sequence (0040,0275) may be used to support Series that are related to multiple Imaging Service Requests. + + See, for example, Section 4.6.4.1.2.3 Relationship between Scheduled and Performed Procedure Steps. + +
+
+
+ Inventoried SOP Instance Attributes +
+ Optional Attributes + This Module identifies Type 3 Attributes at the Instance level, some of which are applicable only to certain SOP Classes of inventoried SOP Instances. These Attributes may still be critical for certain repository uses, such as query for SOP Instances with certain characteristics. + + + + Support of some IHE Profiles requires some of these Attributes. See, for example, : + - The referenced image need not be any particular resolution layer of a WSI pyramid. - I.e., it may or may not be the highest resolution layer. - The user may annotate images that are not at the highest resolution, - but such Annotations may be projected onto any resolution layer that is available (or computed). - If the referenced image is no longer stored or accessible, - the ability to project the Annotations onto other layers may be lost. + Table 4.14-2: Image Specific Query Matching and Return Keys, - A reference to a single frame means that all Annotations in this instance are on that frame; - no mechanism is provided to span frames, or to specify more than one frame. + Table 4.15-1: Presentation State Specific Query Matching and Return Keys, - - - If Annotation Coordinate Type (006A,0001) is 3D, then the coordinates are interpreted as volume relative, with units of mm, in the Cartesian space defined by the Frame of Reference UID. - - A single referenced image may be specified even if Annotation Coordinate Type (006A,0001) is 3D. - It need not be any particular resolution layer of a WSI pyramid, but may be interpreted as a suitable layer on which to render, - select from or otherwise apply the Annotation. - In particular, it may not be the highest resolution layer. - Regardless, the Annotations are applicable to any image in the same Frame of Reference. - - If the Annotations are points, then - - - Graphic Type (0070,0023) shall have a value of POINT. - - - All the points in the group shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), concatenated one after another, with Z factored out into Common Z Coordinate Value (006A,0010), if common. - - - Long Primitive Point Index List (0066,0040) shall not be present, because there is no need for a separate index of each Annotation. - - - Number of Annotations (006A,000C) will contain the number of points, which shall also be the number of coordinate tuples in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022). - - - If the Annotations are open polylines, then - - - Graphic Type (0070,0023) shall have a value of POLYLINE. - - - The points of each polyline shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), concatenated one after another, with Z factored out into Common Z Coordinate Value (006A,0010), if common. - - - The order of the encoded points is from the first point to the last point of the polyline. - - - The index in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) of each successive polyline is encoded in Long Primitive Point Index List (0066,0040), which shall contain Number of Annotations (006A,000C) values. - - - If the Annotations are closed polygons, then - - - Graphic Type (0070,0023) shall have a value of POLYGON. - - - The points of each polygon shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), concatenated one after another, with Z factored out into Common Z Coordinate Value (006A,0010), if common. - - - The order of the encoded points is from the first point to the last point of the polygon. The first point and the last point shall not be the same, but rather they are implicitly joined to close the polygon. - + + Table 4.30-1: Key Image Note Instance Specific Query Matching and Return Keys, and + + + Table 4.44-1: Evidence Document Instance Specific Query Matching and Return Keys. + + + + + A recommended best practice is for the Inventory to include all Attributes supported by the implementation as Matching or Return Keys for Query/Retrieve SOP Classes (see ). + + + See also . + + + +
+
+ File Access Sequence + A repository system may store a SOP Instance on multiple storage devices (e.g., fast short-term media and slower long-term media), or with different Transfer Syntaxes. The SOP Instance may therefore be accessible through a non-DICOM protocol at multiple URIs. The File Access Sequence (0008,041A) provides one Item for each URI (see ). A URI relative path reference within this Sequence shall be relative to the Stored Instance Base URI (0008,0407) applicable to the Series (see ). +
+
+ Metadata From Inventory + A stored SOP Instance accessible through a non-DICOM protocol shall be conformant to its IOD and to the DICOM File Format. However, some Attributes might not have current values (e.g., Patient Name may have been corrected or changed after the Instance was stored). The current values are encoded in the Inventory SOP Instance. For all Attributes defined in the IOD of the stored SOP Instance, and for which values are recorded in the Inventory, the values in the Inventory are authoritative and are imputed to the SOP Instance. + Items of the Original Attributes Sequences (0400,0561) in the Inventory at the Study, Series, and Instance levels (see ) are additive to any Items in the Original Attributes Sequence (0400,0561) of the stored SOP Instance. + + + + SOP Instances accessed through DICOM protocols are expected to have current values in all Attributes. + + + Depending on its function, and application accessing a stored SOP Instance through a non-DICOM protocol may not require updated metadata, e.g., if it is only accessing the pixel data for a machine learning process. Hence, there is no normative requirement that such an application must use metadata from the Inventory SOP Instance, only that the metadata is imputed (conceptually ascribed) to the SOP Instance. + + + Attributes that are not defined in the IOD of the stored SOP Instance, but that are defined in the Inventory IOD, include Study level summary Attributes, such as Modalities in Study (0008,0061) and Number of Study Related Instances (0020,1208), and access Attributes, such as Retrieve AE Title (0008,0054), Stored Instance Base URI (0008,0407), and File Access URI (0008,0409). These Attributes are not to be imputed to the stored SOP Instance. + + + Attributes that are not defined in the Inventory IOD, but that are defined in the IOD of the stored SOP Instance, may be included in the Inventory SOP Instance, especially if they have been updated, such as change of an SR Concept Name Code Sequence (0040,A043) from a SNOMED RT to a SNOMED CT coded concept. See . These Attributes are to be imputed to the stored SOP Instance. + + + An Inventory SOP Instance with Inventory Level (0008,0403) STUDY or SERIES does not include potentially updated metadata for lower levels of the information model. Users of such Inventories that access stored SOP Instances using a non-DICOM protocol, e.g., through the File Set Access Sequence (0008,0419) Attributes at the Study or Series level, should ensure that potentially outdated metadata is acceptable for their purposes. + + + An empty Type 2 Attribute in an Inventory SOP Instance, e.g., Patient's Birth Date (0010,0030), implies that an empty value should be imputed to the referenced stored SOP Instances. A creator of an Inventory SOP Instance should ensure that empty Type 2 Attributes are appropriately conveying the semantics that the value is unknown, and any value in the stored SOP Instances will be overridden. + + + As described in , when performing a coercion, correction or conversion of SOP Instance Attributes, the application may add an Item to the Original Attributes Sequence (0400,0561) describing the provenance of the change, but preserving any existing Items in the Sequence. Thus, changes to Study, Patient, or Imaging Service Request Attributes recorded in the Inventory may have the provenance of those changes recorded in the Original Attributes Sequence (0400,0561) at the Study level, changes to Series or Instance Attributes may have their provenance recorded in the Original Attributes Sequence (0400,0561) at the Series or Instance level, respectively. When those changes are applied to the stored SOP Instances of the Study, all Items in the Original Attributes Sequence (0400,0561) in the Inventory at the Study, Series, and Instance levels + are added to the Original Attributes Sequence (0400,0561) of the stored SOP Instances. See . + + + +
+
+ Expiration Datetime + A repository system may store a SOP Instance in a temporary location (e.g., on fast short-term media). If such storage has a scheduled or expected expiration time, it may be identified in the Expiration DateTime (0008,0416) Attribute. This is not a guaranteed expiration time; the SOP Instance may become unavailable at the access URI at an earlier or later time. This Expiration DateTime (0008,0416) applies only to this non-DICOM protocol access; SOP Instances may continue to be accessible through other DICOM or non-DICOM access methods. +
+
+ Alternate Representation Sequence + Alternate Representation Sequence (0008,3001) encodes a reference to an alternate encoding of the inventoried SOP Instance. This alternate encoding may utilize a different SOP Class or Transfer Syntax, but the alternate encoding of an image shall be the same image although it may have different image quality characteristics. + + + + The Alternate Representation Sequence (0008,3001) allows the Inventory record of an original image to reference a lossy compressed alternate representation, and vice versa. + + + See also . + + + An original SOP Instance that has been operationally replaced by an alternate encoded SOP Instance, and the original then deleted, may still have its Inventory record retained to provide forward referential resolution throughthe Alternate Representation Sequence (0008,3001) for other SOP Instances that reference the original. This record may have Instance Availability (0008,0056) set to UNAVAILABLE (see ), and/or may also be marked as removed from operational use with Reason for Removal Code Sequence (0008,0406) value (130754, DCM, "Replaced by Alternate Representation") (see ). + + + +
+
+
+
+ Inventory Related Macros + + See for the interpretation of the Type column when these Macros are invoked in Normalized IODs. + +
+ Scope of Inventory Macro + + specifies the Key Attribute valuesthat select the Studies included in the Inventory, i.e., the Scope of Inventory. + The full semantics of the matching process is specified in . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Scope of Inventory Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Scope of Inventory Sequence + + (0008,0400) + + 2 + + Matching Key Attribute values for the Studies to be included in the Inventory. See . + Zero or one Item shall be included in this Sequence. + An empty Sequence, or a Sequence with a single empty Item, indicates Universal Match to all Studies in the Repository. +
+ >Extended Matching Mechanisms + + (0008,040F) + + 1C + + Extended Attribute matching mechanisms applied to the Key Attributes, equivalent to mechanisms accepted during Extended Negotiation of the Query/Retrieve Service Class as specified in . See . + + Enumerated Values: + + RELATIONAL + + Relational-queries + + + + COMBINED_DT + + Date-time Matching + + + + FUZZY_SEMANTIC + + Fuzzy Semantic Matching of person names + + + + TIMEZONE_ADJUST + + Timezone Query Adjustment + + + + EMPTY_VALUE + + Empty Value Matching + + + + MULTIPLE_VALUE + + Multiple Value Matching + + + + Required if extended matching mechanisms were applied. +
+ >Specific Character Set + + (0008,0005) + + 1C + + Expanded or replacement character sets used in the Key Attributes. See . + Required if Attributes within the Sequence Item use an expanded or replacement character set. +
+ >Timezone Offset from UTC + + (0008,0201) + + 1C + + Offset from UTC to the local timezone for all DA and TM Key Attributes. See . + Required if Extended Matching Mechanisms (0008,040F) includes value TIMEZONE_ADJUST. +
+ >Query/Retrieve Level + + (0008,0052) + + 1C + + Matching level for Relational Matching mechanism. See . + + Enumerated Values: + + STUDY + + Study level + + + + SERIES + + Series level + + + + IMAGE + + SOP Instance level + + + + Required if Extended Matching Mechanisms (0008,040F) includes value RELATIONAL. +
+ >Range Matching Sequence + + (0008,0410) + + 1C + + The beginning and end values for Range Matching of date and time Key Attributes. See . + Exactly two Items shall be included in this Sequence. + Required if Range Matching is applied to any Key Attribute. +
+ + >>Any DA, DT, or TM Attributes + + + 2 + + Key Attribute values for matching. + Multiple Attributes may be present. +
+ >List of UID Matching Sequence + + (0008,0411) + + 1C + + Key Attribute values for List of UID Matching. See . + Required if List of UID Matching is applied to any Key Attribute. + One or more Items shall be included in this Sequence. +
+ + >>Any UI Key Attribute + + + 1 + + Key Attribute value for matching. +
+ >Empty Value Matching Sequence + + (0008,0412) + + 1C + + Key Attributes for Empty Value Matching. + See . + Required if Extended Matching Mechanisms (0008,040F) includes value EMPTY_VALUE and Empty Value Matching is applied to any Key Attribute. + Only a single Item is permitted in this Sequence. +
+ + >>Any Attributes + + + 2 + + Key Attributes with zero-length values. + Multiple Attributes may be present. +
+ >General Matching Sequence + + (0008,0413) + + 1C + + Key Attribute values for Single Value, Multiple Value, and Wild Card matching. See . + Required if Single Value, Multiple Value, or Wild Card matching is applied to any Key Attribute. + Only a single Item is permitted in this Sequence. +
+ + >>Any Attributes + + + 1 + + Key Attribute values for matching. + Multiple Attributes may be present. +
+
+ Scope of Inventory Macro Attribute Descriptions +
+ Scope of Inventory Sequence + The Scope of Inventory Sequence (0008,0400) specifies Key Attribute values used to select Studies to be included in an Inventory. + Selection of Studies is done by a matching process between Key Attribute values specified in the Scope of Inventory Sequence (0008,0400) and the corresponding values in Attributes of Studies in the repository. The matching process is identical to the Attribute matching specified for the Query/Retrieve Service Class in . + Any extended matching mechanisms beyond the baseline Query/Retrieve behavior used in selection of Studies for the Inventory are identified in the Extended Matching Mechanisms (0008,040F) Attribute. + + - The index in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) of each successive polygon is encoded in Long Primitive Point Index List (0066,0040), which shall contain Number of Annotations (006A,000C) values. + Attributes of Studies that may be matched include those additional Query/Retrieve Attributes that may be managed by the Repository system for managing stored SOP Instances, but are not specified in Composite IODs. See and . Of particular interest for some Inventory use cases are Study Update DateTime (0008,041F), Modalities in Study (0008,0061), and Removed from Operational Use (0008,0405). - - - This closed polygon representation differs from that used in Presentation States () - and Structured Reports ( and ), - none of which are implicitly closed, and required replication of the first point as the last point. - - If the Annotations are circles or ellipses, then - - Graphic Type (0070,0023) shall have a value of ELLIPSE. + In the Query/Retrieve Service Class (including the Repository Query SOP Class), extended matching mechanisms are requested and agreed through SOP Class Extended Negotiation. In the Inventory Creation SOP Class (), the use of extended mechanisms is requested using the Extended Matching Mechanisms (0008,040F) Attribute in the Initiate Action Request. In the Inventory SOP Instances, the actual use of such mechanisms is encoded in the Extended Matching Mechanisms (0008,040F) Attribute by the Instance creator. + + + Key Attributes for matching in the Query/Retrieve Service Class are allowed to have values that are exceptions to the VR for those Attributes in other contexts (see ), or to have multiplicities that are exceptions to the VM of those Attributes as specified in . The Scope of Inventory Sequence (0008,0400) specifies Sequence Attributes that provide equivalent encoding of Key Attributes while maintaining conformance to VR and VM specifications. + Universal matching Key Attributes, i.e., those with zero-length value or with the value "*", do not select Studies, and they shall not be included in the Scope of Inventory. Zero-length values are permitted in Key Attributes of the Range Matching Sequence (0008,0410), where they represent an unbounded beginning or end of a range, and in Key Attributes of the Empty Value Matching Sequence (0008,0412). +
+
+ Relational Matching + If Extended Matching Mechanisms (0008,040F) does not include the value RELATIONAL, only Key Attributes defined at the Study level, as specified in , shall be included in Scope of Inventory. + If Extended Matching Mechanisms (0008,040F) includes the value RELATIONAL, Studies are selected for the Inventory in accordance with the specifications for Relational-queries matching in using the Query/Retrieve Level (0008,0052) and Key Attributes specified. The Inventory Level (0008,0403) determines the level of information that is included in the Inventory and may differ from this Query/Retrieve Level (0008,0052). In the case that the Inventory Level (0008,0403) is at or lower than the Query/Retrieve Level (0008,0052), then only the records for entities matching all Key Attributes will be included in the Inventory. + + For example, specification of Relational Matching, Query/Retrieve Level (0008,0052) SERIES, and a Key Attribute Modality (0008,0060) with value CT will include in the Inventory all Studies that have at least one Series with Modality CT. If the Inventory Level (0008,0403) is INSTANCE, only those Series and Instances with modality CT will be included in the Inventory; Series and Instances with Modality PR or SR, for example, in the same Study will not be included. + Baseline (non-relational) matching of Modalities in Study (0008,0061) with value CT will also include in the Inventory all Studies that have at least one Series with Modality CT. But since that Key Attribute performs selection at the Study level, an Inventory will include all Series of any modality for that Study. + +
+
+ Range Matching Sequence + Range Matching Sequence (0008,0410) provides values for Key Attributes that use range matching of dates and times using the mechanism specified in . + The same set of Key Attributes shall be present in both Items of this Sequence. For each Key Attribute, at least one Item shall have a non-zero length value. + Values in the first Item represent the beginning of the range, and values in the second Itemrepresent the end of the range. If the first or the second value is empty, the range has an unbounded beginning or end, respectively. The range is inclusive; matched Attributes whose value is at or after the first value and before or at the second value match the range. + + In the equivalent Query/Retrieve Service Class range matching, the beginning and end values are encoded in a single Data Element, and delimited by "-". + + If Extended Matching Mechanisms (0008,040F) includes the value COMBINED_DT, related date and time Attributes, such as Study Date (0008,0020) and Study Time (0008,0030), are considered together as a datetime value for matching. + If Extended Matching Mechanisms (0008,040F) includes the value TIMEZONE_ADJUST, dates and times are adjusted for the local timezone specified in Timezone Offset from UTC (0008,0201), as specified in . +
+
+ List of UID Matching Sequence + List of UID Matching Sequence (0008,0411) provides a list of UIDs, one per Item, to be matched using the List of UID Matching mechanism specified in . + + In the equivalent Query/Retrieve Service Class List of UID Matching, the VM=1 restriction is overridden for Key Attributes. + +
+
+ Empty Value Matching Sequence + Empty Value Matching Sequence (0008,0412) specifies Key Attributes that match when the corresponding Attribute in the Study has no value, as specified in . Key Attributes identified in this Sequence shall have zero-length values. + + In the equivalent Query/Retrieve Service Class Empty Value Matching, the value consisting of exactly two QUOTATION MARK characters signifies an empty value, and its use is permitted in Key Attributes with a VR of DA, DT, or TM. + +
+
+ General Matching Sequence + General Matching Sequence (0008,0413) specifies Key Attributes that are matched using Single Value and Wild Card matching, as specified in and . + If Extended Matching Mechanisms (0008,040F) includes the value MULTIPLE_VALUE, General Matching Sequence (0008,0413) may also specify Key Attributes that are matched using Multiple Value matching, as specified in . + + If Extended Matching Mechanisms (0008,040F) does not include the value MULTIPLE_VALUE, Key Attributes with multiple values have undefined meaning. + + If Extended Matching Mechanisms (0008,040F) includes the value TIMEZONE_ADJUST, dates and time are adjusted for the local timezone specified in Timezone Offset from UTC (0008,0201), as specified in . + If Extended Matching Mechanisms (0008,040F) includes the value FUZZY_SEMANTIC, matching of Attributes with VR PN may be done using implementation-specific fuzzy semantic matching, as specified in . +
+
+
+
+ Stored File Access Macro + + specifies the Attributes of the , which describe non-DICOM protocol access to a stored SOP Instance in the DICOM File Format, possibly contained in a container file. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Stored File Access Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ File Access URI + + (0008,0409) + + 1C + + Access URI for a file containing the SOP Instance. See . + Required if the referenced SOP Instance is in the DICOM File Format, and is accessible through a non-DICOM protocol (see ). +
+ Container File Type + + (0008,040A) + + 1C + + Type of container file. See for Defined Terms. + Required if File Access URI (0008,0409) is present. +
+ Filename in Container + + (0008,040B) + + 1C + + Filename within a container file of the file containing the SOP Instance. See . + Required if Container File Type (0008,040A) is ZIP, TAR, or TARGZIP. +
+ File Offset in Container + + (0008,040C) + + 1C + + Byte offset (zero-based) within a container file for the start of the SOP Instance file. See . + Required if Container File Type (0008,040A) is BLOB. May be present otherwise. +
+ File Length in Container + + (0008,040D) + + 1C + + Length in bytes of the SOP Instance file within a container file. See . + Required if Container File Type (0008,040A) is BLOB. May be present otherwise. +
+ Stored Instance Transfer Syntax UID + + (0008,040E) + + 1C + + Transfer Syntax of the SOP Instance encoded in DICOM File Format. Equal to Transfer Syntax UID (0002,0010) in File Meta Information header of the stored Instance. + Required if File Access URI (0008,0409) is present. +
+ Lossy Image Compression Ratio + + (0028,2112) + + 3 + + Describes the approximate lossy compression ratio(s) that have been applied to this image. + See . +
+ MAC Algorithm + + (0400,0015) + + 1C + + The algorithm used for generating a Message Authentication Code. See for Defined Terms. + Required if MAC (0400,0404) is present. +
+ MAC + + (0400,0404) + + 3 + + Message Authentication Code computed across the stored instance file for verification of file integrity. See . +
+
+ Stored File Access Macro Attribute Descriptions +
+ File Access URI + File Access URI (0008,0409) provides the URI for accessing a file containing the SOP Instance in the DICOM File Format. The file may contain a single SOP Instance, or it may be a container file in which one or more SOP Instance files are included. + File Access URI (0008,0409) may be a relative path reference beginning with the single-dot-segment "./" (see ). In this case, the value is merged with a Stored Instance Base URI (0008,0407) specified for the context of this Attribute in accordance with . + + The merge of a relative path File Access URI (0008,0409) with a Stored Instance Base URI (0008,0407) involves only two Attribute values. For example, a relative path specified at the Instance level is not merged with any Study or Series level relative path values, but only with a base URI. This contrasts with the web-based Studies Service of , which might require constructing a URI from a base URI in the Retrieve URL (0008,1190), DICOM-defined strings, a Study Instance UID (0020,000D), a Series Instance UID (0020,000E), and a Referenced SOP Instance UID (0008,1155). + +
+
+ Filename in Container, File Offset in Container, and File Length in Container + If the stored SOP Instance is included in a ZIP, TAR, or TARGZIP container file as specified in , Filename in Container (0008,040B) is the filename within that container file of the file containing the SOP Instance. + If the stored SOP Instance is included in a BLOB container file, and optionally for other container formats, File Offset in Container (0008,040C) is the byte offset for the start of the file for the SOP Instance, and File Length in Container (0008,040D) is the file length. For TARGZIP container files, this is the offset within the TAR container file after extraction from the GZIP container file. + + Locating a file by filename within a container file may require parsing the entire container file (TAR) or look up in the index (ZIP). The File Offset in Container (0008,040C) and File Length in Container (0008,040D), if provided by the SCP, allows the SCU to directly access a specific file. + +
+
+ MAC + The integrity of a stored SOP Instance file may be verified by a Message Authentication Code (also known as a message digest, hash, or cryptographic checksum) computed across the SOP Instance file. The MAC (0400,0404) value is computed across the entire file as a byte stream, including the Preamble, Prefix, Meta-Information Header, and Data Set Trailing Padding (see ). For files stored in container files, the MAC is computed on the file extracted from the container. + + This differs from the MAC for Digital Signatures (see ), which is computed across an enumerated list of Attributes within the SOP Instance, not across the entire file. + +
+
+ +
+
+ Inventory Reference Macro + + specifies the Attributes of the , which describe a referenced Inventory SOP Instance, and its referenced Inventory SOP Instances in a hierarchical tree. + + Because each node in the tree of references includes its complete subsidiary tree, it is not possible to have cycles of references (a node being a descendent of itself). See also . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Inventory Reference Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Referenced SOP Class UID + + (0008,1150) + + 1 + + SOP Class UID of the Inventory SOP Instance included by reference. +
+ Referenced SOP Instance UID + + (0008,1155) + + 1 + + SOP Instance UID of the Inventory SOP Instance included by reference. +
+ Inventory Access End Points Sequence + + (0008,0420) + + 3 + + End point(s) for network protocols to access the referenced Inventory SOP Instance, and the baseline default end point(s) to access Inventory SOP Instances in the Incorporated Inventory Instance Sequence (0008,0422). See . + Only a single Item is permitted in this Sequence. +
+ + >Include + + + +
+ + Include + + + + + See + + +
+ Incorporated Inventory Instance Sequence + + (0008,0422) + + 1C + + Inventory SOP Instances whose content is included by reference. See . + Required if the referenced Inventory SOP Instance itself includes Inventory SOP Instances by reference. + One or more Items shall be included in this Sequence. +
+ + >Include + + + + + Recursive inclusion to describe a tree of referenced Inventory SOP Instances. + +
+
+ Inventory Reference Macro Attribute Descriptions +
+ Inventory Access End Points Sequence + The tree of referenced Inventory SOP Instances includes Attributes specifying the available network access mechanisms and protocol end point(s) for each referenced SOP Instance. As the protocol end point may be the same for all referenced SOP Instances in a tree or sub-tree, the value specified in any node in the tree sets the default value for all subsidiary nodes, except for a sub-tree whose root node sets a value. For example, if all referenced Inventory SOP Instances are accessible through the Inventory MOVE SOP Class at the same SCP AE Title, that AE Title only needs to be specified in the root node of the tree. + If protocol end point values are not specified in the current Item of the Incorporated Inventory Instance Sequence (0008,0422) (which invoked the ), the default values specified for the data set incorporating the Incorporated Inventory Instance Sequence (0008,0422) apply. + + - The end points of the major and minor axes of the ellipses in the group shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), with Z factored out into Common Z Coordinate Value (006A,0010) if common. + Access via Retrieve AE Title (0008,0054) or Retrieve URL (0008,1190) uses the Referenced SOP Instance UID (0008,1155) to identify the Inventory SOP Instance. Access via the Stored Instance Base URI (0008,0407) uses the File Access URI (0008,0409) to identify the stored Inventory SOP Instance file. - Long Primitive Point Index List (0066,0040) shall not be present, because the index of each Annotation can be computed. Number of Annotations (006A,000C) will contain the number of ellipses, which shall also be one quarter of the number of coordinate tuples in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022). + See for the mechanisms to construct a DICOM web-based URI from the Retrieve URL (0008,1190) and Referenced SOP Instance UID (0008,1155). - - - If the length of the major and minor axes are the same, then the ellipse is a circle; a simpler (e.g., 2 point) encoding of a circle is not defined, since the plane of the circle would be unspecified without a third point. - - If the Annotations are squares or rectangles, then - - Graphic Type (0070,0023) shall have a value of RECTANGLE. + See also . + + +
+
+ File Access URI and Stored Instance Base URI + If the referenced Inventory SOP Instance is stored in the DICOM File Format (see ) and is accessible through a non-DICOM protocol (see ), the File Access URI (0008,0409) contains an URI for non-DICOM protocol access to the Inventory SOP Instance. File Access URI (0008,0409) may be a relative path reference URI, which is merged with the Stored Instance Base URI (0008,0407) from the Inventory Access End Points Sequence (0008,0420) in accordance with . + File Access URI (0008,0409) may reference a container file that includes the Inventory SOP Instance. + + - All the corner points of the rectangles in the group shall be encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022), with Z factored out into Common Z Coordinate Value (006A,0010) if common. + The File Access URI (0008,0409) is specified in the included . - Long Primitive Point Index List (0066,0040) shall not be present, because the index of each Annotation can be computed. Number of Annotations (006A,000C) will contain the number of rectangles, which shall also be one quarter of the number of coordinate tuples in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022). + Storage in a container file (ZIP or GZIP) permits compression of the entre file using operating system applications, as an alternative to compression of the SOP Instance using DICOM applications (e.g., using the Deflated Little Endian Transfer Syntax defined in ). - - - If the lengths of the perpendicular edges are the same, then the rectangle is a square. This rectangle representation is the same as if the rectangle were encoded as an implicitly closed polygon, except that the number of points is fixed and Long Primitive Point Index List (0066,0040) is absent. A simpler (e.g., 2 point TLHC, BRHC) encoding of a rectangle is not defined, since the plane of the rectangle would then be unspecified without a third point. - - The index used in Long Primitive Point Index List (0066,0040) of the first value of the first coordinate tuple in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) shall be 1. - The polylines and polygons encoded in Point Coordinates Data (0066,0016) or Double Point Coordinates Data (0066,0022) shall be in the same order as Long Primitive Point Index List (0066,0040). I.e., the values of Long Primitive Point Index List (0066,0040) are strictly increasing. - - This means that the first value of Long Primitive Point Index List (0066,0040) is always 1. - - Open polylines and implicitly closed polygons shall have their vertices encoded in Point Coordinates Data (0066,0016) - or Double Point Coordinates Data (0066,0022) in clockwise winding order when viewed from the top surface of the slide towards the bottom, - per . - The line segments shall not cross (i.e., shall be simple polygons, not complex polygons), - and shall not contain holes (i.e., the keyhole technique described for RT Structure Sets (), shall not be used). - The plane of the coplanar points is not required to correspond to an image plane or be parallel to the slide surface; - the points are only required to be coplanar in a geometric sense (i.e., they need not all have the same Z coordinate value). -
-
- Measurements - For each Annotation Group, optionally one or more measurements may be defined, either for every Annotation or a subset of Annotations. Measurements are described by coded type and unit. - When there is a measurement for every Annotation, then Floating Point Values (0066,0125) contains the corresponding values for each of the Annotations. - When there are measurements for only a subset of Annotations, then Floating Point Values (0066,0125) contains measurement values for the Annotations that are referenced in Annotation Index List (006A,0011). - More than one Measurements Sequence (0066,0121) Item may be used, for example to encode different types of measurements, or to encode different components of a measurement that is a tuple. - Within one Annotation Group the types of measurements are the same for all Annotations within that group. -
+ +
+
+
+ Access End Points Macro + + specifies the Attributes of the , which describe the available network access protocol end point(s), i.e., network addresses, for referenced SOP Instances. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Access End Points Macro Attributes
+ Attribute Name + + Tag + + Type + + Attribute Description +
+ Retrieve AE Title + + (0008,0054) + + 3 + + AE Title end point from which SOP Instances may be retrieved using a C-MOVE or C-GET based SOP Class (see ). This AE Title is used together with one or more of Referenced SOP Instance UID (0008,1155), Study Instance UID (0020,000D), and/or and Series Instance UID (0020,000E) values. +
+ Retrieve URL + + (0008,1190) + + 3 + + Base URI end point of the origin server from which SOP Instances may be retrieved using a DICOM web-based service (see ). This base URI is used together with one or more of Referenced SOP Instance UID (0008,1155), Study Instance UID (0020,000D), and/or and Series Instance UID (0020,000E) values. +
+ Stored Instance Base URI + + (0008,0407) + + 3 + + Base URI end point from which SOP Instances may be retrieved using a non-DICOM protocol (see ). This base URI is used together with a relative path File Access URI (0008,0409) or a Folder Access URI (0008,0408) value. +
+
+
+
+ Inventory Creation Module + + specifies the Attributes of the , which are contained in an Inventory Creation Request/Response. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Inventory Creation Module Attributes
+ Attribute Name + + Tag + + Attribute Description +
+ + Include + + + + + Key Attribute values for the Studies to be included in the Inventory. + +
+ Transaction UID + + (0008,1195) + + Unique identifier of a transaction initiating the production of an Inventory. +
+ Transaction Status + + (0008,0417) + + Processing status for this transaction. (See ). + + Enumerated Values: + + PROCESSING + + Processing continuing + + + + COMPLETE + + Processing complete with completed inventory + + + + FAILURE + + Processing failure + + + + CANCELED + + Processing canceled + + + + PAUSED + + Processing paused + + + +
+ Transaction Status Comment + + (0008,0418) + + Explanation or further detail of Transaction Status (0008,0417). +
+ Expiration DateTime + + (0008,0416) + + The date and time until which the Inventory SOP Instance is expected to be available. See . +
+ Inventory Purpose + + (0008,0401) + + Purpose for which the Inventory is to be created. +
+ Inventory Level + + (0008,0403) + + Information Entity level for records to be included in Inventory. + + Enumerated Values: + + STUDY + + Study records + + + + SERIES + + Study and Series records + + + + INSTANCE + + Study, Series, and Instance records + + + +
+ Referenced SOP Class UID + + (0008,1150) + + SOP Class UID of the produced Inventory SOP Instance. +
+ Referenced SOP Instance UID + + (0008,1155) + + SOP Instance UID of the produced Inventory SOP Instance at the root of the tree of incorporated Inventory SOP Instances (see ). +
+ Retrieve AE Title + + (0008,0054) + + AE Title from which the Inventory SOP Instance may be retrieved through Inventory MOVE or Inventory GET SOP Classes (see ). +
+ Retrieve URL + + (0008,1190) + + Base URI of the origin server from which the Inventory SOP Instance may be retrieved through the Non-Patient Instance Service (see ). +
+ Stored Instance Base URI + + (0008,0407) + + Base URI for accessing the Inventory SOP Instance through a non-DICOM protocol. See . +
+ + Include + + + + + See . + +
+ Total Number of Study Records + + (0008,0428) + + Number of Studies found and processed into Inventory SOP Instances (as of time of message) that match Scope of Inventory. +
+ Requested Status Interval + + (0008,0414) + + Requested interval, in minutes, between Inventory Status notifications. Value shall be greater than 0. +
+ Retain Instances + + (0008,0415) + + Whether produced Inventory SOP Instances should be retained when Inventory production is canceled. + + Enumerated Values: + + Y + + SOP Instances are to be retained + + + + N + + SOP Instances may be deleted + + + +
+
+ Inventory Creation Module Attribute Descriptions +
+ Referenced SOP Instance UID + The content of an Inventory may be divided into more than one Inventory SOP Instance, organized as a tree of SOP Instances with one SOP Instance as the root (see and ). Only the root Inventory SOP Instance is identified in this data set in the Referenced SOP Instance UID (0008,1155); that SOP Instance includes the entire tree of references to SOP Instances comprising the Inventory. +
+
+ File Access Uriand Stored Instance Base URI + If the produced Inventory SOP Instance is stored in the DICOM File Format (see ) and is accessible through a non-DICOM protocol (see ), the File Access URI (0008,0409) contains an URI for non-DICOM protocol access to the Inventory SOP Instance. File Access URI (0008,0409) may be a relative path reference URI, which is merged with the Stored Instance Base URI (0008,0407) in accordance with . + File Access URI (0008,0409) may reference a container file that includes the Inventory SOP Instance (see notes in ). +
+
+ Expiration DateTime + A data management system may manage the storage lifecycle of the Inventory SOP Instances (e.g., by deleting older Inventory objects after a predetermined time). If there is a scheduled or expected time for SOP Inventory Instance deletion, it may be identified in the Expiration DateTime (0008,0416) Attribute. This is not a guaranteed expiration time; the SOP Instances may become unavailable at an earlier or later time. This Expiration DateTime (0008,0416) applies to all available access methods (both DICOM and non-DICOM protocols). + + See for further discussion. + +
+
@@ -289459,7 +296090,8 @@ Attributes of the Basic Directory IOD are defined with a Type designation that indicates if a specific Attribute is required for all Media Storage Operations (see ).
File-set Identification Module - This Module contains Attributes that identify a File-set. + + specifies the Attributes of the , which identify a File-set. @@ -289532,7 +296164,8 @@
Directory Information Module - This Module contains a Sequence of Directory Records forming one or more Directory Entities. This Module defines at least one Directory Entity, the Root Directory Entity (which may be empty). Each Directory Record is composed of Directory Elements (marked by a ">"). They include: + + specifies the Attributes of the , which contain a Sequence of Directory Records forming one or more Directory Entities. This Module defines at least one Directory Entity, the Root Directory Entity (which may be empty). Each Directory Record is composed of Directory Elements (marked by a ">"). They include: an offset pointer to another Directory Record of the Same Directory Entity @@ -289629,7 +296262,7 @@ The value FFFFH shall never be present. - Formerly, this Attribute was intended to signal that the directory was in an inconsistent state with a value of FFFFH. This usage has been retired. See PS3.3-2008. + Formerly, this Attribute was intended to signal that the directory was in an inconsistent state with a value of FFFFH. This usage has been retired. See PS3.3-2008. @@ -289688,7 +296321,7 @@ The value 0000H shall never be present. - Formerly, this Attribute was intended to facilitate the deletion of files, with a value 0000H signally an inactive record. This usage has been retired. See PS3.3-2008. + Formerly, this Attribute was intended to facilitate the deletion of files, with a value 0000H signally an inactive record. This usage has been retired. See PS3.3-2008. Other Values are reserved and shall not be set by File-set Creators, but if present shall be interpreted as FFFFH by File-set Readers or Updaters. @@ -289723,214 +296356,228 @@
@@ -290504,6 +297151,19 @@ PRIVATE + + + + + - + Required if an extended or replacement character set is used in one of the keys. + + - + Required if an extended or replacement character set is used in one of the keys. + + - + Required if an extended or replacement character set is used in one of the keys. + + - + Required if an extended or replacement character set is used in one of the keys. + + - + Required if an extended or replacement character set is used in one of the keys. + + - + Unique identifier of the Series. + +
File-Set Identification Module Attributes
Defines a specialized type of Directory Record by reference to its position in the Media Storage Directory Information Model (see ). - - Enumerated Values: - - PATIENT - - - - - - STUDY - - - - - - SERIES - - - - - - IMAGE - - - - - - RADIOTHERAPY - - - - - - RT DOSE - - - - - - RT STRUCTURE SET - - - - - - RT PLAN - - - - - - RT TREAT RECORD - - - - - - PRESENTATION - - - - - - WAVEFORM - - - - - - SR DOCUMENT - - - - - - KEY OBJECT DOC - - - - - - SPECTROSCOPY - - - - - - RAW DATA - - - - - - REGISTRATION - - - - - - FIDUCIAL - - - - - - HANGING PROTOCOL - - - - - - ENCAP DOC - - - - - - VALUE MAP - - - - - - STEREOMETRIC - - - - - - PALETTE - - - - - - IMPLANT - - - - - - IMPLANT GROUP - - - - - - IMPLANT ASSY - - - - - - MEASUREMENT - - - - - - SURFACE - - - - - - SURFACE SCAN - - - - - - TRACT - - - - - - ASSESSMENT - - - - - - ANNOTATION - - - - - - PRIVATE - - Privately defined record hierarchy position. Type shall be defined by Private Record UID (0004,1432). - - - + + Enumerated Values: + + PATIENT + + + + + + STUDY + + + + + + SERIES + + + + + + IMAGE + + + + + + RADIOTHERAPY + + + + + + RT DOSE + + + + + + RT STRUCTURE SET + + + + + + RT PLAN + + + + + + PLAN + + + + + + RT TREAT RECORD + + + + + + PRESENTATION + + + + + + WAVEFORM + + + + + + SR DOCUMENT + + + + + + KEY OBJECT DOC + + + + + + SPECTROSCOPY + + + + + + RAW DATA + + + + + + REGISTRATION + + + + + + FIDUCIAL + + + + + + HANGING PROTOCOL + + + + + + ENCAP DOC + + + + + + VALUE MAP + + + + + + STEREOMETRIC + + + + + + PALETTE + + + + + + IMPLANT + + + + + + IMPLANT GROUP + + + + + + IMPLANT ASSY + + + + + + MEASUREMENT + + + + + + SURFACE + + + + + + SURFACE SCAN + + + + + + TRACT + + + + + + ASSESSMENT + + + + + + ANNOTATION + + + + + + INVENTORY + + + + + + PRIVATE + + Privately defined record hierarchy position. Type shall be defined by Private Record UID (0004,1432). + + + - Enumerated Values PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined. They are now retired. See PS3.3-1998. + Enumerated Values PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined. They are now retired. See +PS3.3-1998 +. - Enumerated Values OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT and STORED PRINT were previously defined. They are now retired. See PS3.3-2004. + Enumerated Values OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT and STORED PRINT were previously defined. They are now retired. See PS3.3-2004. - Enumerated Value MRDR was previously defined, to allow indirect reference to a File by multiple Directory Records. It is now retired. FSUs and FSRs are unlikely to be capable of supporting this mechanism. See PS3.3-2004. + Enumerated Value MRDR was previously defined, to allow indirect reference to a File by multiple Directory Records. It is now retired. FSUs and FSRs are unlikely to be capable of supporting this mechanism. See PS3.3-2004. - Enumerated Value HL7 STRUC DOC was previously defined. It is now retired. See PS3.3-2018b. + Enumerated Value HL7 STRUC DOC was previously defined. It is now retired. See PS3.3-2018b. @@ -290085,7 +296732,7 @@ - PATIENT, HANGING PROTOCOL, PALETTE, IMPLANT, IMPLANT ASSY, IMPLANT GROUP, PRIVATE + PATIENT, HANGING PROTOCOL, PALETTE, IMPLANT, IMPLANT ASSY, IMPLANT GROUP, INVENTORY, PRIVATE
+ INVENTORY + + + + + + PRIVATE +
PRIVATE @@ -290522,13 +297182,15 @@ - Directory Record Types PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined. They have been retired. See PS3.3-1998. + Directory Record Types PRINT QUEUE, FILM SESSION, FILM BOX, and IMAGE BOX were previously defined. They have been retired. See +PS3.3-1998 +. - Directory Record Types OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT, STORED PRINT and MRDR were previously defined. They have been retired. See PS3.3-2004. + Directory Record Types OVERLAY, MODALITY LUT, VOI LUT, CURVE, TOPIC, VISIT, RESULTS, INTERPRETATION, STUDY COMPONENT, STORED PRINT and MRDR were previously defined. They have been retired. See PS3.3-2004. - Directory Record Type HL7 STRUC DOC was previously defined. It has been retired. See PS3.3 2018b. + Directory Record Type HL7 STRUC DOC was previously defined. It has been retired. See PS3.3-2018b. @@ -290538,7 +297200,7 @@ The following Sections specify a number of Directory Records that were introduced by the Basic Directory IOD Information Model presented in . For each one, it identifies the SOP Classes that may be referenced and the related mandatory keys. Keys are assigned a Type designation that indicates if it is required for all Media Storage Operations of the Directory (see ). Type 2 and Type 3 Keys may be changed to Type 1 and Type 2 or 3 respectively by Application Profiles defined in . Keys based on Private Data Elements, or Private Keys may also be used in addition to Standard defined Keys. However such Private keys may be ignored by any File-set Reader or Updater. - Normalized Print media storage was previously defined in DICOM. It is now retired. See PS3.3-1998. + Normalized Print media storage was previously defined in DICOM. It is now retired. See PS3.3-1998.
Patient Directory Record Definition @@ -290573,9 +297235,9 @@ 1C
- Required if an extended or replacement character set is used in one of the keys -
Patient's Name @@ -290654,9 +297316,9 @@ 1C - Required if an extended or replacement character set is used in one of the keys -
Study Date @@ -290793,9 +297455,9 @@ 1C - Required if an extended or replacement character set is used in one of the keys -
Modality @@ -290981,59 +297643,59 @@
Standalone Overlay Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Standalone Modality LUT Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Standalone VOI LUT Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Standalone Curve Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Topic Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Visit Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Results Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Interpretation Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Study Component Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Print Queue Directory Record Definition - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
Film Session Directory Record Definition - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
Film Box Directory Record Definition - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
Basic Image Box Directory Record Definition - This section was previously defined in DICOM. It is now retired. See PS3.3-1998. + This section was previously defined in DICOM. It is now retired. See PS3.3-1998.
Stored Print Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
RT Dose Directory Record Definition @@ -291304,9 +297966,9 @@ 1C
- Required if an extended or replacement character set is used in one of the keys -
Instance Number @@ -291415,9 +298077,9 @@ 1C - Required if an extended or replacement character set is used in one of the keys -
Instance Number @@ -291672,9 +298334,9 @@ 1 - Unique identifier of the Series -
>>Referenced Image Sequence @@ -291819,7 +298481,10 @@
SR Document Directory Record Definition - The Directory Record is based on the specification of . It is identified by a Directory Record Type of Value "SR DOCUMENT". lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may be found in the Modules related to the Observation IE of Structured Report IOD. This Directory Record shall be used to reference an SR Document. This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more Directory Records as defined in . + The Directory Record is based on the specification of . + It is identified by a Directory Record Type of Value "SR DOCUMENT". lists the set of keys with their associated Types for such a Directory Record Type. + The description of these keys may be found in the Modules related to the SR Document IE of Structured Report IOD. + This Directory Record shall be used to reference an SR Document. This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more Directory Records as defined in . @@ -292016,7 +298681,7 @@
SR Document Keys
- Any Attribute of the Document IE Modules + Any Attribute of the SR Document IE Modules 3 @@ -292033,7 +298698,12 @@
Key Object Document Directory Record Definition - The Directory Record is based on the specification of . It is identified by a Directory Record Type of Value "KEY OBJECT DOC". lists the set of keys with their associated Types for such a Directory Record Type. The description of these keys may be found in the Modules related to the Document IE of the Key Object Selection IOD. This Directory Record shall be used to reference a Key Object Selection Document. This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more Directory Records as defined in . + The Directory Record is based on the specification of . + It is identified by a Directory Record Type of Value "KEY OBJECT DOC". + lists the set of keys with their associated Types for such a Directory Record Type. + The description of these keys may be found in the Modules related to the SR Document IE of the Key Object Selection IOD. + This Directory Record shall be used to reference a Key Object Selection Document. + This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more Directory Records as defined in . @@ -292187,7 +298857,7 @@ - + Required if an extended or replacement character set is used in one of the keys. + + - + A number that identifies this Instance. + + - + Required if an extended or replacement character set is used in one of the keys. + + - + Name of this group. + + @@ -1373,39 +985,25 @@ - If the SCU does not provide an Attribute - that is Mandatory for the SCU, the SCP shall respond with the error code "Missing Attribute" - (0120H). - - If the SCU provides a zero-length value for - a Mandatory Attribute when zero length is not permitted, the SCP shall respond with the error - code "Missing Attribute Value" (0121H). - + If the SCU does not provide an Attribute that is Mandatory for the SCU, the SCP shall respond with the error code "Missing Attribute" (0120H). + If the SCU provides a zero-length value for a Mandatory Attribute when zero length is not permitted, the SCP shall respond with the error code "Missing Attribute Value" (0121H).
DIMSE Service N-GET, N-EVENT-REPORT - The following Requirements apply when - specifying the use of DIMSE services N-GET, N-EVENT-REPORT. - - The convention used in the table below are - as follows: - + The following Requirements apply when specifying the use of DIMSE services N-GET, N-EVENT-REPORT. + The convention used in the table below are as follows: SCU Behaviour Optional - The SCU may retrieve the - Attribute. - + The SCU may retrieve the Attribute. Undefined - The SCU's usage of the - Attribute is undefined. - + The SCU's usage of the Attribute is undefined. @@ -1414,25 +1012,19 @@ Mandatory - The SCP shall support retrieval - of the Attribute. - + The SCP shall support retrieval of the Attribute. Optional - The SCP may or may not support - retrieval of the Attribute. - + The SCP may or may not support retrieval of the Attribute. Undefined - The SCP’s support of the - Attribute is undefined. - + The SCP’s support of the Attribute is undefined. @@ -1551,55 +1143,27 @@ - If support of an Attribute by the SCP is - optional and the SCP does not support the Attribute and the Attribute is requested by the SCU, - the SCP shall respond with the error code "Invalid Attribute Value" (0106H) or "Attribute Value - out of range" (0116H). - + If support of an Attribute by the SCP is optional and the SCP does not support the Attribute and the Attribute is requested by the SCU, the SCP shall respond with the error code "Invalid Attribute Value" (0106H) or "Attribute Value out of range" (0116H).
Other Requirements - If the SCP usage type designation is - modified by a "C" (e.g., 3/1C) the specification stated above shall be modified to include the - requirement that the SCP shall support the Attribute if the specified condition is met. - - For all N-CREATE, N-SET, N-GET, N-DELETE, - N-ACTION and N-EVENT-REPORT operations, the SOP Class is conveyed in the request primitive in - Affected SOP Class UID (0000,0002). The SOP Class UID (0008,0016) Attribute shall not be present - in the Data Set. - - For N-CREATE operations and N-EVENT-REPORT - notifications, the SOP Instance is conveyed in Affected SOP Instance UID (0000,1000). The SOP - Instance UID (0008,0018) Attribute shall not be present in the Data Set. - + If the SCP usage type designation is modified by a "C" (e.g., 3/1C) the specification stated above shall be modified to include the requirement that the SCP shall support the Attribute if the specified condition is met. + For all N-CREATE, N-SET, N-GET, N-DELETE, N-ACTION and N-EVENT-REPORT operations, the SOP Class is conveyed in the request primitive in Affected SOP Class UID (0000,0002). The SOP Class UID (0008,0016) Attribute shall not be present in the Data Set. + For N-CREATE operations and N-EVENT-REPORT notifications, the SOP Instance is conveyed in Affected SOP Instance UID (0000,1000). The SOP Instance UID (0008,0018) Attribute shall not be present in the Data Set. - In some Service Classes, the SOP Class - definition may override the general provision in - - that allows the SOP Instance UID to be specified or omitted in the N-CREATE request - primitive, and require that the SCU be responsible for specifying the SOP Instance UID. - + In some Service Classes, the SOP Class definition may override the general provision in that allows the SOP Instance UID to be specified or omitted in the N-CREATE request primitive, and require that the SCU be responsible for specifying the SOP Instance UID. - For N-SET, N-GET, N-ACTION and N-DELETE - operations, the SOP Instance is conveyed in Requested SOP Instance UID (0000,1001). The SOP - Instance UID (0008,0018) Attribute shall not be present in the Data Set. - + For N-SET, N-GET, N-ACTION and N-DELETE operations, the SOP Instance is conveyed in Requested SOP Instance UID (0000,1001). The SOP Instance UID (0008,0018) Attribute shall not be present in the Data Set.
DICOM Information Model - The DICOM Information Model defines the structure and - organization of the information related to the communication of medical images. Figure 6-1 shows the - relationships between the major structures of the DICOM Information Model. - + The DICOM Information Model defines the structure and organization of the information related to the communication of medical images. Figure 6-1 shows the relationships between the major structures of the DICOM Information Model.
Information Object Definition - An Information Object Definition (IOD) is an - object-oriented abstract data model used to specify information about Real-World Objects. An IOD - provides communicating Application Entities with a common view of the information to be exchanged. - + An Information Object Definition (IOD) is an object-oriented abstract data model used to specify information about Real-World Objects. An IOD provides communicating Application Entities with a common view of the information to be exchanged.
Major Structures of DICOM Information Model @@ -1611,215 +1175,101 @@
- An IOD does not represent a specific instance of a - Real-World Object, but rather a class of Real-World Objects that share the same properties. An IOD used - to represent a single class of Real-World Objects is called a Normalized Information Object. An IOD that - includes information about related Real-World Objects is called a Composite Information Object. - + An IOD does not represent a specific instance of a Real-World Object, but rather a class of Real-World Objects that share the same properties. An IOD used to represent a single class of Real-World Objects is called a Normalized Information Object. An IOD that includes information about related Real-World Objects is called a Composite Information Object.
Composite IOD - A Composite IOD is an Information Object - Definition that represents parts of several entities in the DICOM Model of the Real-World. (see - .) Such an IOD includes - Attributes that are not inherent in the Real-World Object that the IOD represents but rather are - inherent in related Real-World Objects. - - These related Real-World Objects provide a - complete context for the exchanged information. When an instance of a Composite IOD is communicated, - this entire context is exchanged between Application Entities. Relationships between Composite IOD - Instances shall be conveyed in this contextual information. - + A Composite IOD is an Information Object Definition that represents parts of several entities in the DICOM Model of the Real-World. (see .) Such an IOD includes Attributes that are not inherent in the Real-World Object that the IOD represents but rather are inherent in related Real-World Objects. + These related Real-World Objects provide a complete context for the exchanged information. When an instance of a Composite IOD is communicated, this entire context is exchanged between Application Entities. Relationships between Composite IOD Instances shall be conveyed in this contextual information. - Actual communication of IOD - Instances is via SOP Instances. - + Actual communication of IOD Instances is via SOP Instances. - Whenever Composite SOP Instances - are in fact related, some of the contextual information is redundant (i.e., the same - information about the same Real-World Objects is contained in multiple SOP Instances). - + Whenever Composite SOP Instances are in fact related, some of the contextual information is redundant (i.e., the same information about the same Real-World Objects is contained in multiple SOP Instances). - The Composite IODs are specified in. - + The Composite IODs are specified in .
Normalized IOD - A Normalized IOD is an Information Object - Definition that generally represents a single entity in the DICOM Model of the Real-World. - - When an instance of a Normalized IOD is - communicated, the context for that instance is not actually exchanged. Instead, the context is - provided through the use of pointers to related Normalized IOD Instances. - - The Normalized IODs are specified in. - + A Normalized IOD is an Information Object Definition that generally represents a single entity in the DICOM Model of the Real-World. + When an instance of a Normalized IOD is communicated, the context for that instance is not actually exchanged. Instead, the context is provided through the use of pointers to related Normalized IOD Instances. + The Normalized IODs are specified in .
Attributes - The Attributes of an IOD describe the properties of - a Real-World Object Instance. Related Attributes are grouped into Modules that represents a higher level - of semantics documented in the Module Specifications found in. - - Attributes are encoded as Data Elements using the - rules, the Value Representation and the Value Multiplicity concepts specified in - . For specific Data Elements, the Value Representation and Value Multiplicity of Data Elements are - specified in the Data Dictionary in. - + The Attributes of an IOD describe the properties of a Real-World Object Instance. Related Attributes are grouped into Modules that represents a higher level of semantics documented in the Module Specifications found in . + Attributes are encoded as Data Elements using the rules, the Value Representation and the Value Multiplicity concepts specified in . For specific Data Elements, the Value Representation and Value Multiplicity of Data Elements are specified in the Data Dictionary in .
On-Line Communication and Media Storage Services - For on-line communication the DIMSE Services and - Web Services allow a DICOM Application Entity to invoke an operation or notification across a network or - a point-to-point interface. DIMSE Services are defined in - - and Web Services are defined in. - - For media storage interchange, Media Storage - Services allow a DICOM Application Entity to invoke media storage related operations. - - Media Storage Services are discussed in. - + For on-line communication the DIMSE Services and Web Services allow a DICOM Application Entity to invoke an operation or notification across a network or a point-to-point interface. DIMSE Services are defined in and Web Services are defined in . + For media storage interchange, Media Storage Services allow a DICOM Application Entity to invoke media storage related operations. + Media Storage Services are discussed in .
DIMSE-C Services - DIMSE-C Services are services applicable only - to a Composite IOD. DIMSE-C provides only operation services. - + DIMSE-C Services are services applicable only to a Composite IOD. DIMSE-C provides only operation services.
DIMSE-N Services - DIMSE-N Services are services applicable only - to a Normalized IOD. DIMSE-N provides both operation and notification services. - + DIMSE-N Services are services applicable only to a Normalized IOD. DIMSE-N provides both operation and notification services.
DIMSE Service Group - A DIMSE Service Group specifies one or more - operations/notifications defined in - - that are applicable to an IOD. - - DIMSE Service Groups are defined in this Part of - the DICOM Standard, in the specification of a Service-Object Pair Class. - + A DIMSE Service Group specifies one or more operations/notifications defined in that are applicable to an IOD. + DIMSE Service Groups are defined in this Part of the DICOM Standard, in the specification of a Service-Object Pair Class.
Service-Object Pair (SOP) Class - The SOP Class definitions in - - contain the rules and semantics that may restrict the use of the services in the DIMSE Service Group or - the Attributes of the IOD. - - and - - contain the rules and semantics that may restrict the Attributes of the IOD or the use of the services - in the Media Storage Services and the Web Services respectively. - - The selection of SOP Classes is used by Application - Entities to establish an agreed set of capabilities to support their interaction for SOP Classes based - on DIMSE Services. This negotiation is performed at Association establishment time as described in. An extended negotiation - allows Application Entities to further agree on specific options within a SOP Class. - + The SOP Class definitions in contain the rules and semantics that may restrict the use of the services in the DIMSE Service Group or the Attributes of the IOD. and contain the rules and semantics that may restrict the Attributes of the IOD or the use of the services in the Media Storage Services and the Web Services respectively. + The selection of SOP Classes is used by Application Entities to establish an agreed set of capabilities to support their interaction for SOP Classes based on DIMSE Services. This negotiation is performed at Association establishment time as described in . An Extended Negotiation allows Application Entities to further agree on specific options within a SOP Class. - The SOP Class as defined in the DICOM - Information Model is equivalent in ISO/OSI terminology to the Managed Object Class. Readers - familiar with object-oriented terminology will recognize the SOP Class operations (and - notifications) as comprising the methods of an object class. - + The SOP Class as defined in the DICOM Information Model is equivalent in ISO/OSI terminology to the Managed Object Class. Readers familiar with object-oriented terminology will recognize the SOP Class operations (and notifications) as comprising the methods of an object class. - SOP Class Specifications play a central - role in defining DICOM conformance. They allow DICOM Application Entities to select a - well-defined application level subset of this Standard to which they may claim conformance. - See. - + SOP Class Specifications play a central role in defining DICOM conformance. They allow DICOM Application Entities to select a well-defined application level subset of this Standard to which they may claim conformance. See .
Normalized and Composite SOP Classes - DICOM defines two types of SOP Classes, - Normalized and Composite. For DIMSE Services, Normalized SOP Classes are defined as the union of a - Normalized IOD and a set of DIMSE-N Services, while Composite SOP Classes are defined as the union - of a Composite IOD and a set of DIMSE-C Services. Media Storage Services only support Composite IODs - and Web Services support both Normalized and Composite SOP Classes. - + DICOM defines two types of SOP Classes, Normalized and Composite. For DIMSE Services, Normalized SOP Classes are defined as the union of a Normalized IOD and a set of DIMSE-N Services, while Composite SOP Classes are defined as the union of a Composite IOD and a set of DIMSE-C Services. Media Storage Services only support Composite IODs and Web Services support both Normalized and Composite SOP Classes.
Association Negotiation - Association establishment is the first phase of - communication between peer DICOM compliant Application Entities. The Application Entities shall use - Association establishment to negotiate which SOP Classes can be exchanged and how this data will be - encoded. - - Association Negotiation is defined in. - + Association establishment is the first phase of communication between peer DICOM compliant Application Entities. The Application Entities shall use Association establishment to negotiate which SOP Classes can be exchanged and how this data will be encoded. + Association Negotiation is defined in .
Service Class Specification - A Service Class Specification defines a group of - one or more SOP Classes related to a specific function that is to be accomplished by communicating - Application Entities. A Service Class Specification also defines rules that allow implementations to - state some pre-defined level of conformance to one or more SOP Classes. - Applications may conform to network SOP Classes as a Service Class User (SCU), Service Class Provider - (SCP), User Agent or Origin Server, and to media exchange SOP Classes as a File Set Creator (FSC), File - Set Reader (FSR), or File Set Updater (FSU). - - Service Class Specifications are defined in this - Part of the DICOM Standard. - + A Service Class Specification defines a group of one or more SOP Classes related to a specific function that is to be accomplished by communicating Application Entities. A Service Class Specification also defines rules that allow implementations to state some pre-defined level of conformance to one or more SOP Classes. + Applications may conform to network SOP Classes as a Service Class User (SCU), Service Class Provider (SCP), User Agent or Origin Server, and to media exchange SOP Classes as a File Set Creator (FSC), File Set Reader (FSR), or File Set Updater (FSU). + Service Class Specifications are defined in this Part of the DICOM Standard. - Network interaction between peer Application - Entities work on a 'client/server model.' + Network interaction between peer Application Entities work on a 'client/server model.' The SCU or User Agent acts as the 'client,' while the SCP or Origin Server acts as the 'server'. - For DIMSE based services the SCU/SCP roles are determined during Association establishment. - + For DIMSE based services the SCU/SCP roles are determined during Association establishment.
DICOM Model of the Real World - The DICOM view of the Real-World that identifies the - relevant Real-World Objects and their relationships within the scope of the DICOM Standard is described in - the DICOM Model of the Real-World Section of. - - This section also describes the DICOM Information Model - that identifies the various IODs specified by the DICOM Standard and their relationship. - + The DICOM view of the Real-World that identifies the relevant Real-World Objects and their relationships within the scope of the DICOM Standard is described in the DICOM Model of the Real-World Section of . + This section also describes the DICOM Information Model that identifies the various IODs specified by the DICOM Standard and their relationship. Coded Entry Usage in Service Specifications - The Macros in this Section specify the usage of the - Attributes that correspond to Coded Entries as defined by. - - Not all invocations make use of all the columns. For - example, in some invocations, only the "Requirement Type SCU/SCP" is relevant; in others, only the Matching - Key Type and Return Key Type columns are used. - + The Macros in this Section specify the usage of the Attributes that correspond to Coded Entries as defined by . + Not all invocations make use of all the columns. For example, in some invocations, only the "Requirement Type SCU/SCP" is relevant; in others, only the Matching Key Type and Return Key Type columns are used.
Key Object Document Keys
- Any Attribute of the Document IE Modules + Any Attribute of the SR Document IE Modules 3 @@ -292783,9 +299453,9 @@ 1C - Required if an extended or replacement character set is used in one of the keys -
Hanging Protocol Name @@ -293112,9 +299782,9 @@ 1 - A number that identifies this Instance -
Document Title @@ -293204,7 +299874,7 @@
HL7 Structured Document Directory Record Definition - Retired. See PS3.3 2018b. + Retired. See PS3.3-2018b.
Real World Value Mapping Directory Record Definition @@ -293388,9 +300058,9 @@ 1C
- Required if an extended or replacement character set is used in one of the keys -
Content Label @@ -293638,9 +300308,9 @@ 1 - Name of this group -
Implant Template Group Description @@ -294165,7 +300835,9 @@
- Any other Attribute of the Content Assessment Results IE Modules + +Any other Attribute of the Content Assessment Results IE Modules + 3 @@ -294274,7 +300946,7 @@
- Content Creator"s Name + Content Creator's Name (0070,0084) @@ -294286,7 +300958,9 @@
- Any other Attribute of the RT Second-Generation IE Modules + +Any other Attribute of the RT Second-Generation IE Modules + 3 @@ -294380,7 +301054,7 @@
- Any other Attribute of the Annotations IE Modules + Any other Attribute of the Annotation IE Modules @@ -294395,6 +301069,131 @@ it is not duplicated in this list of keys. +
+ Inventory Directory Record Definition + The Directory Record is based on the specification of . + It is identified by a Directory Record Type of Value "INVENTORY". + lists the set of keys with their associated Types for such a Directory Record Type. + The description of these keys may be found in the Inventory IOD. + This Directory Record shall be used to reference an Inventory SOP Instance. + This type of Directory Record may reference a Lower-Level Directory Entity that includes one or more Directory Records as defined in . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Inventory Keys
+ Key + + Tag + + Type + + Attribute Description +
+ Specific Character Set + + (0008,0005) + + 1C + + Required if an extended or replacement character set is used in one of the keys. +
+ Content Date + + (0008,0023) + + 1 + +
+ Content Time + + (0008,0033) + + 1 + +
+ Inventory Purpose + + (0008,0401) + + 2 + +
+ Inventory Level + + (0008,0403) + + 1 + +
+ + Include + + + +
+ Inventory Completion Status + + (0008,0426) + + 1 + +
+ Total Number of Study Records + + (0008,0428) + + 1 + +
+
Special Directory Records @@ -294404,14 +301203,14 @@
Multi-referenced File Directory Record Definition - Retired. See PS3.3-2004. + Retired. See PS3.3-2004.
Icon Image Key Definition - An Icon Image may be used as a key representative of an Image, RT Dose, Spectroscopy, Raw Data or Series in a corresponding Directory Record to allow an application to display icons that enable a user to select one or more from amongst several of them. It is based on the general purpose Image Pixel Macro (see ). - The Icon Image Key corresponds to Data Element (0088,0200). It is defined as a Sequence that contains a single Item encapsulating the Data Set made of the Data Elements of the Icon Image. The Data Elements are defined by the Image Pixel Macro (see ). - The Image Pixel Macro usage is restricted in a few areas to facilitate general use in Directory Record across various modality environments. These restrictions are: + An Icon Image may be used as a key representative of an Image, RT Dose, Spectroscopy, Raw Data or Series in a corresponding Directory Record to allow an application to display icons that enable a user to select one or more from amongst several of them. It is based on the general purpose . + The Icon Image Key corresponds to Data Element (0088,0200). It is defined as a Sequence that contains a single Item encapsulating the Data Set made of the Data Elements of the Icon Image. The Data Elements are defined by the . + The usage is restricted in a few areas to facilitate general use in Directory Record across various modality environments. These restrictions are: Only monochrome and palette color images shall be used. Samples per Pixel (0028,0002) shall have a Value of 1, Photometric Interpretation (0028,0004) shall have a Value of either MONOCHROME 1, MONOCHROME 2 or PALETTE COLOR, Planar Configuration (0028,0006) shall not be present. @@ -294473,4 +301272,171 @@ Clinical Trial Identification Workflow Examples (Informative) Retired. See . + + Stored File Access Through Non-DICOM Protocols (Normative) + The , and specifically the , includes optional Attributes providing a URI for SOP Instances stored in the DICOM File Format and accessible through a non-DICOM file access protocol. + Additionally, Inventory SOP Instances themselves may be stored in the DICOM File Format and be accessible through a non-DICOM file access protocol as specified in a URI in the Inventory Creation Response (see , and the ). + This Annex specifies constraints on those URIs and their target resources (files). + + See also . + +
+ Files and Sets of Files +
+ DICOM File Format + Each stored SOP Instance that is a target of an Inventory URI shall be encoded in accordance with the DICOM File Format (see ). + + Depending on the storage mechanism, this target resource may be denoted a "file" or an "object". The term "file" is used in this specification. + +
+
+ Container File Formats + SOP Instances in the DICOM File Format may be aggregated into container files in accordance with the mechanisms specified in this Section. + + Directly or indirectly executable files within container files are a security risk. + A producer of a container file should avoid including such executable files. + A reader should take actions to mitigate against such executable files when reading a container file. + See . + +
+ ZIP + Multiple SOP Instance files may be included in a ZIP container file in accordance with . + + + is a constraint on the specification, and in particular supports only uncompressed or DEFLATE compressed files, and does not permit encryption. + +
+
+ TAR + Multiple SOP Instance files may be included in a TAR container file (i.e., a file in accordance with the ustar Interchange Format) in accordance with . + + "ustar" is the formal name, derived from "Unix Standard Tape ARchive", although TAR is the common term and is used in this specification. + The specification for ustar Interchange Format is in the section "pax - portable archive interchange". + +
+
+ GZIP + A single SOP Instance file may be included in a GZIP container file in accordance with . + + The GZIP format supports compression of the contained file using DEFLATE compression. + +
+
+ TARGZIP + Multiple SOP Instance files may be included in a TAR container file in accordance with , which is then contained within a GZIP container file in accordance with . + + The TARGZIP format supports compression of the multiple SOP Instances in the TAR. + +
+
+ BLOB + Multiple SOP Instance files may be included in a container file without standardized file delimitation, typically denoted a binary large object (BLOB) or an octet-stream. + For use in DICOM, files contained in the BLOB are required to be delimited by externally managed byte offsets and file lengths. +
+
+
+ Folders for Sets of Files + The file storage mechanism may support data structures that manage references to sets of files in a folder. + + Depending on the storage mechanism,these structures may alternately be denoted "directories". + The term "folder" is used in this specification due to potential ambiguities with the term "directory". + + The storage of multiple SOP Instance files may be managed such that all SOP Instances in a Study or in a Series are contained within a single folder. + Within that folder, some or all of the files may be included in a ZIP, TAR, GZIP, TARGZIP, or BLOB container file. +
+
+
+ Access Protocols +
+ URI Format + The URI for non-DICOM protocol access to stored SOP Instances shall be inaccordance with . + If the URI is split between two data elements, a base URI and a relative path, the merger of those data elements in accordance with Section 5.2.3 "Merge Paths" shall form the conformant URI. + The split shall be at a path segment boundary, and if a slash ("/") character occurs at that boundary, it shall be placed in the base URI data element only. + The second data element comprising the relative path shall begin with a single-dot-segment "./". + Dot-segments shall not otherwise be used. +
+
+ Protocol + The non-DICOM file access protocol used in the Inventory URI link is not constrained by this Standard. + The Conformance Statement for the implementation shall specify the protocol(s) in its description of conformance to the Inventory SOP Class. + Some common protocols are listed in . + + + + Conformance specification may be facilitated by reference to IANA-registered schemes (). + + + Several protocols are layered on HTTP. While the specific protocol should be specified in the Conformance Statement, the only feature required is the ability to read an object, which is generally implemented simply as an HTTP GET in such protocols, and may be implemented with only a URI. + + + An access protocol will support technical means for access control and transport security, which must be used in accordance with institutional security policies and procedures. + See . + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Common Non-DICOM File Access Protocols (Informative)
+ + IANA-registered Scheme + + + + Protocol + + + + Further Specification + +
+ nfs + + NFS + + + + +
+ smb + + SMB + + + + +
+ https + + HTTP GET + + +, Includes various cloud storage implementations +
+
+
+ diff --git a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part04.xml b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part04.xml similarity index 66% rename from dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part04.xml rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part04.xml index c82cb59..ef4a918 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part04.xml +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part04.xml @@ -1,9 +1,7 @@ - + PS3.4 - DICOM PS3.4 2022c - Service Class Specifications + DICOM PS3.4 2022d - Service Class Specifications DICOM Standards Committee @@ -18,160 +16,73 @@ Notice and Disclaimer - The information in this publication was considered - technically sound by the consensus of persons engaged in the development and approval of the document at the - time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every - person participating in the development of this document. - - NEMA standards and guideline publications, of which the - document contained herein is one, are developed through a voluntary consensus standards development process. - This process brings together volunteers and/or seeks out the views of persons who have an interest in the - topic covered by this publication. While NEMA administers the process and establishes rules to promote - fairness in the development of consensus, it does not write the document and it does not independently test, - evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments - contained in its standards and guideline publications. - - NEMA disclaims liability for any personal injury, - property, or other damages of any nature whatsoever, whether special, indirect, consequential, or - compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on - this document. NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or - completeness of any information published herein, and disclaims and makes no warranty that the information - in this document will fulfill any of your particular purposes or needs. NEMA does not undertake to guarantee - the performance of any individual manufacturer or seller's products or services by virtue of this standard - or guide. - - In publishing and making this document available, NEMA - is not undertaking to render professional or other services for or on behalf of any person or entity, nor is - NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this - document should rely on his or her own independent judgment or, as appropriate, seek the advice of a - competent professional in determining the exercise of reasonable care in any given circumstances. - Information and other standards on the topic covered by this publication may be available from other - sources, which the user may wish to consult for additional views or information not covered by this - publication. - - NEMA has no power, nor does it undertake to police or - enforce compliance with the contents of this document. NEMA does not certify, test, or inspect products, - designs, or installations for safety or health purposes. Any certification or other statement of compliance - with any health or safety-related information in this document shall not be attributable to NEMA and is - solely the responsibility of the certifier or maker of the statement. - + The information in this publication was considered technically sound by the consensus of persons engaged in the development and approval of the document at the time it was developed. Consensus does not necessarily mean that there is unanimous agreement among every person participating in the development of this document. + NEMA standards and guideline publications, of which the document contained herein is one, are developed through a voluntary consensus standards development process. This process brings together volunteers and/or seeks out the views of persons who have an interest in the topic covered by this publication. While NEMA administers the process and establishes rules to promote fairness in the development of consensus, it does not write the document and it does not independently test, evaluate, or verify the accuracy or completeness of any information or the soundness of any judgments contained in its standards and guideline publications. + NEMA disclaims liability for any personal injury, property, or other damages of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, application, or reliance on this document. NEMA disclaims and makes no guaranty or warranty, expressed or implied, as to the accuracy or completeness of any information published herein, and disclaims and makes no warranty that the information in this document will fulfill any of your particular purposes or needs. NEMA does not undertake to guarantee the performance of any individual manufacturer or seller's products or services by virtue of this standard or guide. + In publishing and making this document available, NEMA is not undertaking to render professional or other services for or on behalf of any person or entity, nor is NEMA undertaking to perform any duty owed by any person or entity to someone else. Anyone using this document should rely on his or her own independent judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of reasonable care in any given circumstances. Information and other standards on the topic covered by this publication may be available from other sources, which the user may wish to consult for additional views or information not covered by this publication. + NEMA has no power, nor does it undertake to police or enforce compliance with the contents of this document. NEMA does not certify, test, or inspect products, designs, or installations for safety or health purposes. Any certification or other statement of compliance with any health or safety-related information in this document shall not be attributable to NEMA and is solely the responsibility of the certifier or maker of the statement. Foreword - This DICOM Standard was developed according to the - procedures of the DICOM Standards Committee. - - The DICOM Standard is structured as a multi-part - document using the guidelines established in. - - DICOM® is the registered trademark of the National - Electrical Manufacturers Association for its standards publications relating to digital communications of - medical information, all rights reserved. - - HL7® and CDA® are the registered trademarks of Health - Level Seven International, all rights reserved. - - SNOMED®, SNOMED Clinical Terms®, SNOMED CT® are the - registered trademarks of the International Health Terminology Standards Development Organisation - (IHTSDO), all rights reserved. - - LOINC® is the registered trademark of Regenstrief - Institute, Inc, all rights reserved. - + This DICOM Standard was developed according to the procedures of the DICOM Standards Committee. + The DICOM Standard is structured as a multi-part document using the guidelines established in . + DICOM® is the registered trademark of the National Electrical Manufacturers Association for its standards publications relating to digital communications of medical information, all rights reserved. + HL7® and CDA® are the registered trademarks of Health Level Seven International, all rights reserved. + SNOMED®, SNOMED Clinical Terms®, SNOMED CT® are the registered trademarks of the International Health Terminology Standards Development Organisation (IHTSDO), all rights reserved. + LOINC® is the registered trademark of Regenstrief Institute, Inc, all rights reserved. Scope and Field of Application - This Part of the DICOM Standard specifies the set of - Service Class Definitions that provide an abstract definition of real-world activities applicable to - communication of digital medical information. For each Service Class Definition, this Part specifies: - + This Part of the DICOM Standard specifies the set of Service Class Definitions that provide an abstract definition of real-world activities applicable to communication of digital medical information. For each Service Class Definition, this Part specifies: - the semantic description of the activities of - the Service Class Definition - + the semantic description of the activities of the Service Class Definition - the group of DIMSE Service operations and - notifications applicable to the Service Class Description - + the group of DIMSE Service operations and notifications applicable to the Service Class Description - one or more functionally-related Service-Object - Pair (SOP) Classes that are supported by the Service Class Definition and may be performed between - peer DICOM Application Entities - + one or more functionally-related Service-Object Pair (SOP) Classes that are supported by the Service Class Definition and may be performed between peer DICOM Application Entities - the relationship of each Service-Object Pair - (SOP) Classes to applicable Information Object Definitions specified in - . - + the relationship of each Service-Object Pair (SOP) Classes to applicable Information Object Definitions specified in . - For each Service Class Definition, this Part does not - specify: - + For each Service Class Definition, this Part does not specify: - any necessary information for the semantic - description of the IOD - + any necessary information for the semantic description of the IOD - relationships to associated real-world objects - relevant to the IOD - + relationships to associated real-world objects relevant to the IOD - Attributes that describe the characteristics of - the IOD - + Attributes that describe the characteristics of the IOD - This Part is related to other parts of the DICOM - Standard in that: - + This Part is related to other parts of the DICOM Standard in that: - - specifies the set of Information Object Definitions to which the services defined in this Part may - be applied - + specifies the set of Information Object Definitions to which the services defined in this Part may be applied - - defines the data encoding used in the DIMSE Protocol when applied to IODs defined in this Part - + defines the data encoding used in the DIMSE Protocol when applied to IODs defined in this Part - - contains an index by Tag of all IOD Attributes defined in this Part. This index includes the Value - Representation and Value Multiplicity for each Attribute - + contains an index by Tag of all IOD Attributes defined in this Part. This index includes the Value Representation and Value Multiplicity for each Attribute - - defines the DIMSE Services and Protocol that may be applied to IODs defined in this Part. - + defines the DIMSE Services and Protocol that may be applied to IODs defined in this Part. Normative References - The following standards contain provisions which, - through reference in this text, constitute provisions of this Standard. At the time of publication, the - editions indicated were valid. All standards are subject to revision, and parties to agreements based on - this Standard are encouraged to investigate the possibilities of applying the most recent editions of the - standards indicated below. - + The following standards contain provisions which, through reference in this text, constitute provisions of this Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibilities of applying the most recent editions of the standards indicated below. ISO/IEC Directives, Part 2 @@ -210,9 +121,7 @@ Information Processing Systems - Open Systems Interconnection - Service Conventions - ISO/TR 8509 has been withdrawn. See ISO/IEC 2382-26:1993 Information technology - Vocabulary - - Part 26: Open systems interconnection - + ISO/TR 8509 has been withdrawn. See ISO/IEC 2382-26:1993 Information technology - Vocabulary - Part 26: Open systems interconnection @@ -266,9 +175,7 @@ IHE International 2020 - Integrating the Healthcare Enterprise Radiology Technical Framework Volume 1 Integration - Profiles - + Integrating the Healthcare Enterprise Radiology Technical Framework Volume 1 Integration Profiles @@ -288,162 +195,131 @@ Definitions - For the purposes of this Standard the following - definitions apply. - + For the purposes of this Standard the following definitions apply. Reference Model Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Application Entity - See. - + See . Service - See. - + See . Application Entity Title AET - See. - + See . Service Conventions Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Primitive - See. - + See . DICOM Introduction and Overview Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Attribute - . - + . Command - . - + . Data Dictionary - . - + . Information Object - . - + . Message - . - + . - + Service-Object Pair Class SOP Class - . - + . DICOM Upper Layer Service Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : DICOM Upper Layer Service - . - + . DICOM Message Exchange Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : - + DICOM Message Service Element DIMSE - . - + . DIMSE-N Services - . - + . DIMSE-C Services - . - + . @@ -451,48 +327,40 @@ DSG - . - + . DICOM Information Object Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Attribute Tag - . - + . Composite IOD - . - + . DICOM Application Model - . - + . DICOM Information Model - . - + . @@ -500,128 +368,108 @@ IOD - . - + . Module - . - + . Normalized IOD - . - + . Functional Group - . - + . DICOM Conformance - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Conformance Statement - . - + . Standard SOP Class - . - + . Specialized SOP Class - . - + . Standard Extended SOP Class - . - + . Private SOP Class - . - + . Standard Attribute - . - + . Private Attribute - . - + . DICOM Data Structures and Encoding - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Data Element - . - + . Data Set - . - + . Default Character Repertoire - . - + . @@ -629,253 +477,163 @@ UID - . - + . DICOM Service Class Definitions - The following definitions are commonly used in - this Part of the DICOM Standard: - + The following definitions are commonly used in this Part of the DICOM Standard: Classic Image Storage SOP Class - An Image Storage SOP Class that is - defined by an IOD that stores a single frame and defines the majority of the Attributes in - the top-level Data Set. - + An Image Storage SOP Class that is defined by an IOD that stores a single frame and defines the majority of the Attributes in the top-level Data Set. Combined Print Image - A pixel matrix created by superimposing - an image and an overlay, the size of which is defined by the smallest rectangle enclosing - the superimposed image and overlay. - + A pixel matrix created by superimposing an image and an overlay, the size of which is defined by the smallest rectangle enclosing the superimposed image and overlay. - + Enhanced Image Storage SOP Class - An Image Storage SOP Class that is - defined by an IOD that stores multiple frames and defines the majority of the Attributes in - Functional Group Sequences. - + An Image Storage SOP Class that is defined by an IOD that stores multiple frames and defines the majority of the Attributes in Functional Group Sequences. - + Legacy Converted Enhanced Image Storage SOP Class - A modality-specific Enhanced Image - Storage SOP Class that is defined by an IOD that defines only generic Functional Group - Sequences, which does not require information that is not present in Classic Image Storage - SOP Class Instances, and is intended for storage of converted Classic Image Storage SOP - Class Instances when there is insufficient information to use a True Enhanced Image Storage - SOP Class. - + A modality-specific Enhanced Image Storage SOP Class that is defined by an IOD that defines only generic Functional Group Sequences, which does not require information that is not present in Classic Image Storage SOP Class Instances, and is intended for storage of converted Classic Image Storage SOP Class Instances when there is insufficient information to use a True Enhanced Image Storage SOP Class. - + Meta Service-Object Pair Class Meta SOP Class - A pre-defined set of SOP Classes that - may be associated under a single SOP for the purpose of negotiating the use of the set with - a single item. - + A pre-defined set of SOP Classes that may be associated under a single SOP for the purpose of negotiating the use of the set with a single item. Non-Patient Object - A SOP Instance that adheres to a - Composite Instance IOD Information Model specified in - , but does not have the Patient Information Entity as its root. - Non-Patient Object SOP Instances may still contain patient-related identifiable information, - e.g., Inventory SOP Instances - + A SOP Instance that adheres to a Composite Instance IOD Information Model specified in , but does not have the Patient Information Entity as its root. + Non-Patient Object SOP Instances may still contain patient-related identifiable information, e.g., Inventory SOP Instances - + Performed Procedure Step SOP Class - Any SOP Class that encodes the details - about the performance of a procedure step. - + Any SOP Class that encodes the details about the performance of a procedure step. - + Performed Procedure Step SOP Instance - An instance of a Performed Procedure - Step SOP Class. Note that all UPS instances are instances of the UPS Push SOP Class, which - is capable of encoding details about the performance of a procedure step (in addition to - details about the scheduled procedure step) and thus qualify as an instance of a Performed - Procedure Step SOP Class. - + An instance of a Performed Procedure Step SOP Class. Note that all UPS instances are instances of the UPS Push SOP Class, which is capable of encoding details about the performance of a procedure step (in addition to details about the scheduled procedure step) and thus qualify as an instance of a Performed Procedure Step SOP Class. Preformatted Grayscale Image - An image where all annotation, - graphics, and grayscale transformations (up to and including the VOI LUT) expected in the - printed image have been burnt in or applied before being sent to the SCP. It is a - displayable image where the polarity of the intended display is specified by Photometric - Interpretation (0028,0004). - + An image where all annotation, graphics, and grayscale transformations (up to and including the VOI LUT) expected in the printed image have been burnt in or applied before being sent to the SCP. It is a displayable image where the polarity of the intended display is specified by Photometric Interpretation (0028,0004). Preformatted Color Image - An image where all annotation, - graphics, and color transformations expected in the printed image have been burnt in or - applied before being sent to the SCP. - + An image where all annotation, graphics, and color transformations expected in the printed image have been burnt in or applied before being sent to the SCP. Real-World Activity - That which exists in the real world - that pertains to specific area of information processing within the area of interest of the - DICOM Standard. Such a Real-World Activity may be represented by one or more computer - information metaphors called SOP Classes. - + That which exists in the real world that pertains to specific area of information processing within the area of interest of the DICOM Standard. Such a Real-World Activity may be represented by one or more computer information metaphors called SOP Classes. Real-World Object - That which exists in the real world - upon which operations may be performed that are within the area of interest of the DICOM - Standard. Such a Real-World Object may be represented through a computer information - metaphor called a SOP Instance. - + That which exists in the real world upon which operations may be performed that are within the area of interest of the DICOM Standard. Such a Real-World Object may be represented through a computer information metaphor called a SOP Instance. Related General SOP Class - A SOP Class that is related to another - SOP Class as being more generalized in terms of behavior defined in the Standard, and that - may be used to identically encode an instance with the same Attributes and values, other - than the SOP Class UID. In particular, this may be the SOP Class from which a Specialized - SOP Class (see) - is derived. - + A SOP Class that is related to another SOP Class as being more generalized in terms of behavior defined in the Standard, and that may be used to identically encode an instance with the same Attributes and values, other than the SOP Class UID. In particular, this may be the SOP Class from which a Specialized SOP Class (see ) is derived. Service Class User SCU - The role played by a DICOM Application - Entity (DIMSE-Service-User) that invokes operations and performs notifications on a specific - Association. - + The role played by a DICOM Application Entity (DIMSE-Service-User) that invokes operations and performs notifications on a specific Association. Service Class Provider SCP - The role played by a DICOM Application - Entity (DIMSE-Service-User) that performs operations and invokes notifications on a specific - Association. - + The role played by a DICOM Application Entity (DIMSE-Service-User) that performs operations and invokes notifications on a specific Association. Service Class - A collection of SOP Classes and/or Meta - SOP Classes that are related in that they are described together to accomplish a single - application. - + A collection of SOP Classes and/or Meta SOP Classes that are related in that they are described together to accomplish a single application. - + Service-Object Pair Instance SOP Instance - A concrete occurrence of an Information - Object that is managed by a DICOM Application Entity and may be operated upon in a - communication context defined by a specific set of DIMSE Services (on a network or - interchange media). A SOP Instance is persistent beyond the context of its communication. - + A concrete occurrence of an Information Object that is managed by a DICOM Application Entity and may be operated upon in a communication context defined by a specific set of DIMSE Services (on a network or interchange media). A SOP Instance is persistent beyond the context of its communication. - + True Enhanced Image Storage SOP Class - A modality-specific Enhanced Image - Storage SOP Class that is defined by an IOD that defines modality-specific Functional Group - Sequences, Attributes and sets of values, and is intended for creation by acquisition - devices. - + A modality-specific Enhanced Image Storage SOP Class that is defined by an IOD that defines modality-specific Functional Group Sequences, Attributes and sets of values, and is intended for creation by acquisition devices. Device Independent Pixel Values - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : P-Value - . - + . - + Profile Connection Space Value PCS-Value - . - + . HTTP Definitions - This Part of the Standard makes use of the - following terms defined in: - + This Part of the Standard makes use of the following terms defined in : Origin-Server - See. - + See . User-Agent - See. - + See . @@ -884,114 +642,60 @@ Symbols and Abbreviations - The following symbols and abbreviations are used in - this Part of the DICOM Standard. - + The following symbols and abbreviations are used in this Part of the DICOM Standard. - ACR - American College of Radiology - + ACR American College of Radiology - ASCII - American Standard Code for Information Interchange - + ASCII American Standard Code for Information Interchange - AE - Application Entity - + AE Application Entity - ANSI - American National Standards Institute - + ANSI American National Standards Institute - CDS - Clinical Decision Support - + CDS Clinical Decision Support CEN TC251 - Comité Européen de Normalisation - - Technical Committee 251 - Medical Informatics - + Comité Européen de Normalisation - Technical Committee 251 - Medical Informatics - Chest CAD - Computer-Aided Detection and/or Computer-Aided Diagnosis for chest radiography - + Chest CAD Computer-Aided Detection and/or Computer-Aided Diagnosis for chest radiography - DICOM - Digital Imaging and Communications in Medicine - + DICOM Digital Imaging and Communications in Medicine - DIMSE - DICOM Message Service Element - + DIMSE DICOM Message Service Element - DIMSE-C - DICOM Message Service Element-Composite - + DIMSE-C DICOM Message Service Element-Composite - DIMSE-N - DICOM Message Service Element-Normalized - + DIMSE-N DICOM Message Service Element-Normalized - HL7 - Health Level 7 - + HL7 Health Level 7 - IE - Information Entity - + IE Information Entity - IEEE - Institute of Electrical and Electronics Engineers - + IEEE Institute of Electrical and Electronics Engineers - IOD - Information Object Definition - + IOD Information Object Definition - IS - Information System - + IS Information System - ISO - International Standards Organization - + ISO International Standards Organization - JIRA - Japan Medical Imaging and Radiological Systems Industries Association - + JIRA Japan Medical Imaging and Radiological Systems Industries Association - JPIP - JPEG 2000 Interactive Protocol - + JPIP JPEG 2000 Interactive Protocol - MAR - Medication Administration Record - + MAR Medication Administration Record - NEMA - National Electrical Manufacturers Association - + NEMA National Electrical Manufacturers Association - OSI - Open Systems Interconnection - + OSI Open Systems Interconnection - SCP - Service Class Provider - + SCP Service Class Provider - SCU - Service Class User - + SCU Service Class User - SOP - Service-Object Pair - + SOP Service-Object Pair - UID - Unique Identifier - + UID Unique Identifier Conventions @@ -999,11 +703,7 @@ Entity-Relationship Model
Entity - An entity is used in an Entity-Relationship - (E-R) model to represent a Real-World Object, class of Real-World Objects, or DICOM data - representation (such as IOD or Module). An entity is depicted as a box within this Part of the DICOM - Standard as shown in Figure 5-1. - + An entity is used in an Entity-Relationship (E-R) model to represent a Real-World Object, class of Real-World Objects, or DICOM data representation (such as IOD or Module). An entity is depicted as a box within this Part of the DICOM Standard as shown in Figure 5-1.
Entity Convention @@ -1018,9 +718,7 @@
Relationship - A relationship, which defines how entities are - related, is depicted as a diamond within this Standard as shown in Figure 5-2. - + A relationship, which defines how entities are related, is depicted as a diamond within this Standard as shown in Figure 5-2.
Relationship Convention @@ -1032,178 +730,102 @@
- The relationship is read from source to - destination entity as indicated by the arrows. The a and b show the source and destination - cardinality of the relationship respectively. The following cardinalities are permitted: - + The relationship is read from source to destination entity as indicated by the arrows. The a and b show the source and destination cardinality of the relationship respectively. The following cardinalities are permitted: - (a = 1, b = 1) -one source entity is - related to one destination entity - + (a = 1, b = 1) -one source entity is related to one destination entity - (a = 1, b = 0-n) -one source entity is - related to zero or more destination entities - + (a = 1, b = 0-n) -one source entity is related to zero or more destination entities - (a = 1, b = 1-n) -one source entity is - related to one or more destination entities - + (a = 1, b = 1-n) -one source entity is related to one or more destination entities - (a = 1-n, b = 1) -one or more source - entities are related to one destination entity - + (a = 1-n, b = 1) -one or more source entities are related to one destination entity - (a = 1-n, b = 0-n) -one or more source - entities are related to zero or more destination entities - + (a = 1-n, b = 0-n) -one or more source entities are related to zero or more destination entities - (a = 1-n, b = 1-n) -one or more source - entities are related to one or more destination entities - + (a = 1-n, b = 1-n) -one or more source entities are related to one or more destination entities - In a relationship where (a = 1-n, b = 1-n) the - values of the source and destination cardinalities may be different. The value "n" simply denotes - one or more. - + In a relationship where (a = 1-n, b = 1-n) the values of the source and destination cardinalities may be different. The value "n" simply denotes one or more. - DICOM has added the use of arrows to the - E-R diagramming conventions often used in other literature. This has been done to avoid the - possibility of inferring an incorrect relationship that can result from reading a relationship - in the reverse order of that intended. For example, a relationship "Cat Catches Mouse" could be - read "Mouse Catches Cat" if the arrows were not present. - + DICOM has added the use of arrows to the E-R diagramming conventions often used in other literature. This has been done to avoid the possibility of inferring an incorrect relationship that can result from reading a relationship in the reverse order of that intended. For example, a relationship "Cat Catches Mouse" could be read "Mouse Catches Cat" if the arrows were not present. - A relationship may be bi-directional (i.e., the - relationship is true in both directions). In such a case, the convention used is arrows pointing - toward both the source and the destination entities. - + A relationship may be bi-directional (i.e., the relationship is true in both directions). In such a case, the convention used is arrows pointing toward both the source and the destination entities.
Sequences - Certain tables in this Part of the DICOM Standard - denote a Sequence of Items by using the symbol: '>.' - - In, '>' is - used to identify a 'Sequence of Modules.' Nested Sequences of Modules are identified by '>>'. In - - and, '>' is used to identify a 'Sequence of - Attributes'. See - - for the complete specification of how Sequences of Items shall be encoded. - + Certain tables in this Part of the DICOM Standard denote a Sequence of Items by using the symbol: '>.' + In , '>' is used to identify a 'Sequence of Modules.' Nested Sequences of Modules are identified by '>>'. In and , '>' is used to identify a 'Sequence of Attributes'. See for the complete specification of how Sequences of Items shall be encoded. - Information Object Definitions (IODs) that - include the Sequence of Module construct are often called folders. The use of 'Sequences of - Attributes' is not limited to 'Folders.' - + Information Object Definitions (IODs) that include the Sequence of Module construct are often called folders. The use of 'Sequences of Attributes' is not limited to 'Folders.'
Response Status Values - Certain tables in this Part of the DICOM Standard - denote an implementation specific response status code by using the symbol 'xx' or 'xxx' as part of the - code. - + Certain tables in this Part of the DICOM Standard denote an implementation specific response status code by using the symbol 'xx' or 'xxx' as part of the code. - Each 'x' symbol may be replaced by an - implementation with a hexadecimal digit in the range from 0 to F. - + Each 'x' symbol may be replaced by an implementation with a hexadecimal digit in the range from 0 to F.
Usage Specification - The building blocks of SOP Classes are Modules and - DIMSE Services. The DIMSE Services associated with a SOP Class may be Mandatory (M) or Optional (U). The - usage may be different for the SCU and SCP. The usage is specified as a pair of letters: the former - indicating the SCU usage, the latter indicating the SCP usage. - + The building blocks of SOP Classes are Modules and DIMSE Services. The DIMSE Services associated with a SOP Class may be Mandatory (M) or Optional (U). The usage may be different for the SCU and SCP. The usage is specified as a pair of letters: the former indicating the SCU usage, the latter indicating the SCP usage.
Use of DIMSE Services - The meaning and behavior of the usage - specification for DIMSE Services are: - + The meaning and behavior of the usage specification for DIMSE Services are: M/M - The SCU shall support the DIMSE - Service but is not required to use it on an Association. The SCP shall support the DIMSE - Service. - + The SCU shall support the DIMSE Service but is not required to use it on an Association. The SCP shall support the DIMSE Service. U/M - The SCU may support and use the - DIMSE Service. The SCP shall support the DIMSE Service. - + The SCU may support and use the DIMSE Service. The SCP shall support the DIMSE Service. U/U - The SCU may support and use the - DIMSE Service. The SCP may support the DIMSE Service. If the SCP does not support the - DIMSE Service used by the SCU, it shall return a Failure status. - + The SCU may support and use the DIMSE Service. The SCP may support the DIMSE Service. If the SCP does not support the DIMSE Service used by the SCU, it shall return a Failure status.
Use of Attributes in Normalized Services - Modules and their usage in Composite IODs are - defined in. Normalized - IODs are also constructed from Modules but usage is specified on an Attribute basis in this Part of - the DICOM Standard. The following usage specification applies to all Attributes of Normalized IODs - unless superseded by a usage specification in a particular SOP Class Specification. - - The term ‘receive’ means the following: the - value shall be stored; under certain circumstances (e.g. coercion) the value returned may have - changed. - + Modules and their usage in Composite IODs are defined in . Normalized IODs are also constructed from Modules but usage is specified on an Attribute basis in this Part of the DICOM Standard. The following usage specification applies to all Attributes of Normalized IODs unless superseded by a usage specification in a particular SOP Class Specification. + The term ‘receive’ means the following: the value shall be stored; under certain circumstances (e.g. coercion) the value returned may have changed.
DIMSE Service N-CREATE, N-SET, N-ACTION - The following Requirements apply when - specifying the use of DIMSE services N-CREATE, N-SET, N-ACTION. - - The convention used in the table below are - as follows: - + The following Requirements apply when specifying the use of DIMSE services N-CREATE, N-SET, N-ACTION. + The convention used in the table below are as follows: SCU Behaviour Mandatory - The SCU shall provide the - Attribute. - + The SCU shall provide the Attribute. Optional - The SCU may or may not provide - the Attribute. - + The SCU may or may not provide the Attribute. Undefined - The SCU's usage of the - Attribute is undefined. - + The SCU's usage of the Attribute is undefined. @@ -1212,34 +834,25 @@ Mandatory - The SCP shall support receiving - the Attribute. - + The SCP shall support receiving the Attribute. Mandatory with Default - The SCP shall support receiving - the Attribute. Upon receiving zero-length values, the SCP shall assign values as - defined by the specification of the Service Class. - + The SCP shall support receiving the Attribute. Upon receiving zero-length values, the SCP shall assign values as defined by the specification of the Service Class. Optional - The SCP may or may not support - receiving the Attribute. - + The SCP may or may not support receiving the Attribute. Undefined - The SCP’s support of the - Attribute is undefined. - + The SCP’s support of the Attribute is undefined. @@ -1297,8 +910,7 @@ Permitted
- Mandatory with Default - + Mandatory with Default
- + @@ -1870,17 +1319,15 @@
Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning - Enhanced SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning
@@ -1844,10 +1294,9 @@
- Include - - - +Include + +
- >Include - - - +>Include + +
- + @@ -1938,21 +1379,15 @@ @@ -1964,30 +1399,15 @@ @@ -2016,21 +1436,15 @@ @@ -2042,21 +1456,15 @@ @@ -2146,8 +1554,7 @@ @@ -2210,10 +1616,9 @@ @@ -2249,9 +1654,7 @@ @@ -2266,9 +1669,7 @@ @@ -2280,18 +1681,11 @@ @@ -2320,9 +1714,7 @@ @@ -2337,9 +1729,7 @@ @@ -2414,8 +1804,7 @@ @@ -2479,10 +1867,9 @@ @@ -2519,18 +1906,14 @@ @@ -2542,18 +1925,14 @@ @@ -2565,24 +1944,14 @@ @@ -2611,18 +1980,14 @@ @@ -2634,18 +1999,14 @@ @@ -2735,8 +2096,7 @@ @@ -2798,10 +2157,9 @@ @@ -2838,9 +2196,7 @@ @@ -2855,9 +2211,7 @@ @@ -2869,21 +2223,11 @@ @@ -2912,9 +2256,7 @@ @@ -2929,9 +2271,7 @@ @@ -3006,8 +2346,7 @@ @@ -3061,10 +2399,9 @@ @@ -3097,9 +2434,7 @@ @@ -3111,9 +2446,7 @@ @@ -3125,12 +2458,7 @@ @@ -3153,9 +2481,7 @@ @@ -3167,9 +2493,7 @@ @@ -3229,8 +2553,7 @@
Basic SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning - Basic SCU/SCP Coded Entry Macro with SCU Support, Matching Key Support and Mandatory Meaning
@@ -1912,21 +1359,15 @@ 1C/1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL. RC - Required if the code value length is 16 - characters or less, and the code value is not a URN or URL. - + Required if the code value length is 16 characters or less, and the code value is not a URN or URL. 1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
1C/1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. RC - Required if Code Value (0008,0100) or - Long Code Value (0008,0119) is present. May be present otherwise. - + Required if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. 1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
1C/1C - Required if the value of Coding Scheme - Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. RC - Required if the value of Coding Scheme - Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. 1C - Required if the value of Coding Scheme - Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
1C/1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is not a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL. RC - Required if Code Value (0008,0100) is - not present, and the code value is not a URN or URL. - + Required if Code Value (0008,0100) is not present, and the code value is not a URN or URL. 1C - Required if Code Value (0008,0100) is - not present, and the code value is not a URN or URL. - + Required if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
1C/1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL. RC - Required if Code Value (0008,0100) is - not present, and the code value is a URN or URL. - + Required if Code Value (0008,0100) is not present, and the code value is a URN or URL. 1C - Require if Code Value (0008,0100) is - not present, and the code value is a URN or URL. - + Require if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Context Group Extension Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -2187,10 +1594,9 @@
- Include - - - +Include + +
- >Include - - - +>Include + +
1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present.
OC - May be present only if the value of - Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code - Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) - unambiguously. - + May be present only if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. 3 - Applicable only if the value of Coding - Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - + Applicable only if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously.
1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is not a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
1C - Shall be present only if Code Value - (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present only if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Context Group Extension Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -2455,10 +1844,9 @@
- Include - - - +Include + +
- >Include - - - +>Include + +
-/1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL. - 1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
-/1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - 1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
-/1C - Required if the value of Coding Scheme - Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. - 1C - Shall be present if the value of Coding - Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
-/1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is not a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL. - 1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is not a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
-/1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL. - 1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Context Group Extension Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -2775,10 +2135,9 @@
- Include - - - +Include + +
- >Include - - - +>Include + +
1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
RC - Required if the value of Coding Scheme - Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Required if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. 1C - Shall be present if the value of Coding - Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is not a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Context Group Extension Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -3041,10 +2380,9 @@
- Include - - - +Include + +
- >Include - - - +>Include + +
-/1C - Shall be present if the code value - length is 16 characters or less, and the code value is not a URN or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
-/1C - Shall be present if Code Value - (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
-/1C - May be present if the value of Coding - Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value - (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. - Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + May be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
-/1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is not a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
1C/1C - Shall be present if Code Value - (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Context Group Extension Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -3249,113 +2572,68 @@ Overview
Scope - The Verification Service Class defines a - service that verifies application level communication between peer DICOM AEs. This verification is - accomplished on an established Association using the C-ECHO DIMSE-C service. - + The Verification Service Class defines a service that verifies application level communication between peer DICOM AEs. This verification is accomplished on an established Association using the C-ECHO DIMSE-C service.
SCU/SCP Behavior - A DICOM AE, supporting the Verification SOP Class - SCU role, requests verification of communication to a remote DICOM AE. This request is performed using - the C-ECHO request primitive. The remote DICOM AE, supporting the Verification SOP Class SCP role, - issues an C-ECHO response primitive. Upon receipt of the C-ECHO confirmation, the SCU determines that - verification is complete. See - - for the specification of the C-ECHO primitives. - + A DICOM AE, supporting the Verification SOP Class SCU role, requests verification of communication to a remote DICOM AE. This request is performed using the C-ECHO request primitive. The remote DICOM AE, supporting the Verification SOP Class SCP role, issues an C-ECHO response primitive. Upon receipt of the C-ECHO confirmation, the SCU determines that verification is complete. See for the specification of the C-ECHO primitives.
DIMSE-C Service Group - The C-ECHO DIMSE-C service shall be the mechanism - used to verify communications between peer DICOM AEs. The C-ECHO service and protocol parameters shall - be required as defined in. - + The C-ECHO DIMSE-C service shall be the mechanism used to verify communications between peer DICOM AEs. The C-ECHO service and protocol parameters shall be required as defined in .
Verification SOP Class - The Verification SOP Class consists of the C-ECHO - DIMSE-C service. No associated Information Object Definition is defined. The SOP Class UID shall be - "1.2.840.10008.1.1". - - No Specialized SOP Classes and/or Meta SOP Classes - shall be defined for the Verification SOP Class. - + The Verification SOP Class consists of the C-ECHO DIMSE-C service. No associated Information Object Definition is defined. The SOP Class UID shall be "1.2.840.10008.1.1". + No Specialized SOP Classes and/or Meta SOP Classes shall be defined for the Verification SOP Class.
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. The following negotiation rules apply to DICOM AEs - that support the Verification SOP Class - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The following negotiation rules apply to DICOM AEs that support the Verification SOP Class - The Association-requester (verification SCU - role) in the A-ASSOCIATE request shall convey an Abstract Syntax, in a Presentation Context, for - the Verification SOP Class. The Abstract Syntax Name shall be equivalent to the Verification SOP - Class UID. - + The Association-requestor (verification SCU role) in the A-ASSOCIATE request shall convey an Abstract Syntax, in a Presentation Context, for the Verification SOP Class. The Abstract Syntax Name shall be equivalent to the Verification SOP Class UID. - The Association-acceptor (verification SCP - role) in the A-ASSOCIATE response shall accept the Abstract Syntax, in a Presentation Context, - for the supported Verification SOP Class. - + The Association-acceptor (verification SCP role) in the A-ASSOCIATE response shall accept the Abstract Syntax, in a Presentation Context, for the supported Verification SOP Class. - No Application Association Information specific to - the Verification SOP Class shall be used. - + No Application Association Information specific to the Verification SOP Class shall be used.
Conformance
Conformance Supporting the SCU Role - Implementations that conform to the - Verification SOP Class SCU role shall meet the: - + Implementations that conform to the Verification SOP Class SCU role shall meet the: - C-ECHO service requirements as defined - by the DIMSE Service Group, - + C-ECHO service requirements as defined by the DIMSE Service Group, - Association negotiation rules as - defined in - + Association negotiation rules as defined in
Conformance Supporting the SCP Role - Implementations that conform to the - Verification SOP Class SCP role shall meet the: - + Implementations that conform to the Verification SOP Class SCP role shall meet the: - C-ECHO operation rules as defined by - the DIMSE Service Group, - + C-ECHO operation rules as defined by the DIMSE Service Group, - Association negotiation rules as - defined in - + Association negotiation rules as defined in
Conformance Statement - An implementation may conform to the - Verification SOP Class as an SCU, SCP, or both. The Conformance Statement shall be in the format - defined in. - + An implementation may conform to the Verification SOP Class as an SCU, SCP, or both. The Conformance Statement shall be in the format defined in .
@@ -3365,63 +2643,30 @@ Overview
Scope - The Storage Service Class defines an - application-level class-of-service that facilitates the simple transfer of information Instances - (objects).. It allows one DICOM AE to send images, waveforms, reports, etc., to another. - - Information Object Definitions for Instances - that are transferred under the Storage Service Class shall adhere to the Composite Instance IOD - Information Model specified in, and include at least the - Patient, Study, and Series Information Entities. - + The Storage Service Class defines an application-level class-of-service that facilitates the simple transfer of information Instances (objects).. It allows one DICOM AE to send images, waveforms, reports, etc., to another. + Information Object Definitions for Instances that are transferred under the Storage Service Class shall adhere to the Composite Instance IOD Information Model specified in , and include at least the Patient, Study, and Series Information Entities.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Storage Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes - of the Storage Service Class are implemented using the C-STORE DIMSE-C service. C-STORE is described - in. A successful - completion of the C-STORE has the following semantics: - + Two peer DICOM AEs implement a SOP Class of the Storage Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Storage Service Class are implemented using the C-STORE DIMSE-C service. C-STORE is described in . A successful completion of the C-STORE has the following semantics: - Both the SCU and the SCP support the - type of information to be stored. - + Both the SCU and the SCP support the type of information to be stored. - The information is stored in some - medium. - + The information is stored in some medium. - For some time frame, the information - may be accessed. - + For some time frame, the information may be accessed. - Support for Storage SOP Classes - does not necessarily involve support for SOP Classes of the Query/Retrieve Service - Class. How the information may be accessed is implementation dependent. It is required - that some access method exists. This method may require an implementation dependent - operation at the SCP of the Storage Service Class. The duration of the storage is also - implementation dependent, but is described in the Conformance Statement of the SCP. - Storage SOP Classes are intended to be used in a variety of environments: e.g., for - modalities to transfer images to workstations or archives, for archives to transfer - images to workstations or back to modalities, for workstations to transfer processed - images to archives, etc. - + Support for Storage SOP Classes does not necessarily involve support for SOP Classes of the Query/Retrieve Service Class. How the information may be accessed is implementation dependent. It is required that some access method exists. This method may require an implementation dependent operation at the SCP of the Storage Service Class. The duration of the storage is also implementation dependent, but is described in the Conformance Statement of the SCP. Storage SOP Classes are intended to be used in a variety of environments: e.g., for modalities to transfer images to workstations or archives, for archives to transfer images to workstations or back to modalities, for workstations to transfer processed images to archives, etc. - For the JPIP Referenced Pixel Data - transfer syntaxes, transfers may result in storage of incomplete information in that the - pixel data may be partially or completely transferred by some other mechanism at the - discretion of the SCP. - + For the JPIP Referenced Pixel Data transfer syntaxes, transfers may result in storage of incomplete information in that the pixel data may be partially or completely transferred by some other mechanism at the discretion of the SCP. @@ -3429,41 +2674,22 @@
Behavior - This Section discusses the SCU and SCP behavior for - SOP Classes of the Storage Service Class. The C-STORE DIMSE-C Service shall be the mechanism used to - transfer SOP Instances between peer DICOM AEs as described in. - + This Section discusses the SCU and SCP behavior for SOP Classes of the Storage Service Class. The C-STORE DIMSE-C Service shall be the mechanism used to transfer SOP Instances between peer DICOM AEs as described in .
Behavior of an SCU - The SCU invokes a C-STORE DIMSE Service with a - SOP Instance that meets the requirements of the corresponding IOD. The SCU shall recognize the - status of the C-STORE service and take appropriate action upon the success or failure of the - service. - + The SCU invokes a C-STORE DIMSE Service with a SOP Instance that meets the requirements of the corresponding IOD. The SCU shall recognize the status of the C-STORE service and take appropriate action upon the success or failure of the service. - The appropriate action is implementation - dependent. It is required that the SCU distinguish between successful and failed C-STORE - responses. Appropriate action may differ according to application, but are described in the - Conformance Statement of the SCU. - + The appropriate action is implementation dependent. It is required that the SCU distinguish between successful and failed C-STORE responses. Appropriate action may differ according to application, but are described in the Conformance Statement of the SCU.
Behavior of an SCP - An SCP of a Storage SOP Class acts as a - performing DIMSE-service-user for the C-STORE Service. By performing this service successfully, the - SCP indicates that the SOP Instance has been successfully stored. - + An SCP of a Storage SOP Class acts as a performing DIMSE-service-user for the C-STORE Service. By performing this service successfully, the SCP indicates that the SOP Instance has been successfully stored.
Statuses - - defines the specific status code values that might be returned in a C-STORE response. General status - code values and fields related to status code values are defined for C-STORE DIMSE Service in. - + defines the specific status code values that might be returned in a C-STORE response. General status code values and fields related to status code values are defined for C-STORE DIMSE Service in . @@ -3488,8 +2714,7 @@ Failure -
C-STORE Status
- Refused: Out of resources - + Refused: Out of resources A7xx @@ -3499,10 +2724,8 @@
- Error: Data Set does not match - SOP Class - + + Error: Data Set does not match SOP Class A9xx @@ -3529,8 +2752,7 @@ Warning - Coercion of Data Elements - + Coercion of Data Elements B000 @@ -3542,9 +2764,7 @@
- Data Set does not match SOP - Class - + Data Set does not match SOP Class B007 @@ -3582,103 +2802,45 @@
- Some Failure Status Codes are implementation - specific. - - An SCP implementation shall assign specific - failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. - An SCP implementation wishing to differentiate between causes within the same Failure Meaning shall - assign those causes specific Status Code Values within valid range specified in. - - An SCU implementation shall recognize any - Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU - implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes within the same Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
Association Negotiation - SCUs and SCPs of Storage SOP Classes operate on SOP - Instances specific to the SOP Class. They may use the SOP Class Extended Negotiation Sub-Item defined in - . This Sub-Item allows DICOM - AEs to exchange application information specific to SOP Class specifications. This is achieved by - defining the Service-class-application-information field. - - SCUs may use the SOP Class Common Extended - Negotiation Sub-Item defined in. This Sub-Item allows DICOM AEs - to exchange information about the nature of the SOP Classes. - - The SOP Class Extended Negotiation Sub-Item and SOP - Class Common Extended Negotiation Sub-Item negotiation is optional for storage based SOP Classes. - - The following negotiation rules apply to all DICOM - SOP Classes and Specialized SOP Classes of the Storage Service Class. - - The Association-requester (Storage SCU role) in the - A-ASSOCIATE request shall convey: - + SCUs and SCPs of Storage SOP Classes operate on SOP Instances specific to the SOP Class. They may use the SOP Class Extended Negotiation Sub-Item defined in . This Sub-Item allows DICOM AEs to exchange application information specific to SOP Class specifications. This is achieved by defining the Service-class-application-information field. + SCUs may use the SOP Class Common Extended Negotiation Sub-Item defined in . This Sub-Item allows DICOM AEs to exchange information about the nature of the SOP Classes. + The SOP Class Extended Negotiation Sub-Item and SOP Class Common Extended Negotiation Sub-Item negotiation is optional for storage based SOP Classes. + The following negotiation rules apply to all DICOM SOP Classes and Specialized SOP Classes of the Storage Service Class. + The Association-requestor (Storage SCU role) in the A-ASSOCIATE request shall convey: - one Abstract Syntax, in a Presentation - Context, for each supported SOP Class of the Storage Service Class - + one Abstract Syntax, in a Presentation Context, for each supported SOP Class of the Storage Service Class - optionally, one SOP Class Extended - Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class - + optionally, one SOP Class Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class - optionally, one SOP Class Common Extended - Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class - + optionally, one SOP Class Common Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class - The Association-acceptor (Storage SCP role) in the - A-ASSOCIATE request shall accept: - + The Association-acceptor (Storage SCP role) in the A-ASSOCIATE request shall accept: - one Abstract Syntax, in a Presentation - Context, for each supported SOP Class of the Storage Service Class - + one Abstract Syntax, in a Presentation Context, for each supported SOP Class of the Storage Service Class - optionally, one SOP Class Extended - Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class - + optionally, one SOP Class Extended Negotiation Sub-Item, for each supported SOP Class of the Storage Service Class
Extended Negotiation - At the time of Association establishment - implementations may exchange information about their respective capabilities, as described in - - and. SCUs and SCPs may - use the SOP Class Extended Negotiation Sub-Item Structure as described in - - to exchange information about the level of conformance and options supported. SCUs may use the SOP - Class Common Extended Negotiation Sub-Item defined in - - to exchange information about the nature of the SOP Classes. - - Extended negotiation is optional. In the event - that either the SCU or the SCP does not support extended negotiation, the defaults shall apply. - + At the time of Association establishment implementations may exchange information about their respective capabilities, as described in and . SCUs and SCPs may use the SOP Class Extended Negotiation Sub-Item Structure as described in to exchange information about the level of conformance and options supported. SCUs may use the SOP Class Common Extended Negotiation Sub-Item defined in to exchange information about the nature of the SOP Classes. + Extended Negotiation is optional. In the event that either the SCU or the SCP does not support Extended Negotiation, the defaults shall apply.
Service-Class-Application-Information (A-ASSOCIATE-RQ) - The SOP Class Extended Negotiation Sub-Item - is made of a sequence of mandatory fields as defined by. - - shows the format of the Service-class-application-information field of the SOP Class Extended - Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-RQ. - + The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by . shows the format of the Service-class-application-information field of the SOP Class Extended Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-RQ. @@ -3700,22 +2862,15 @@ 1 @@ -3726,9 +2881,7 @@ Reserved @@ -3736,26 +2889,15 @@ 3 @@ -3766,9 +2908,7 @@ Reserved @@ -3779,22 +2919,11 @@ Element Coercion @@ -3805,9 +2934,7 @@ Reserved @@ -3815,14 +2942,7 @@
Service-Class-Application-Information (A-ASSOCIATE-AC) - The SOP Class Extended Negotiation Sub-Item - is made of a sequence of mandatory fields as defined by. - - shows the format of the Service-class-application-information field of the SOP Class Extended - Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-AC. - + The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by . shows the format of the Service-class-application-information field of the SOP Class Extended Negotiation Sub-Item for SOP Classes of the Storage Service Class in the A-ASSOCIATE-AC.
Service-Class-Application-Information (A-ASSOCIATE-RQ)
- Level of support + Level of Storage Support - This byte field defines the - supported storage level of the Association-requester. It shall be encoded as an - unsigned binary integer and shall use one of the following values: - - 0 - level 0 SCP - 1 - level 1 SCP - 2 - level 2 SCP - 3 - N/A - Association-requester is SCU only - - If extended negotiation is - not supported, the default shall have a value of 3. - + This byte field defines the supported Storage Level of the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values: + 0 - Storage Level 0 SCP + 1 - Storage Level 1 SCP + 2 - Storage Level 2 SCP + 3 - N/A Association-requestor is SCU only + If Extended Negotiation is not supported, the default shall have a value of 3.
- This reserved field shall - be sent with a value 00H but not tested to this value when received. - + This reserved field shall be sent with a value 00H but not tested to this value when received.
- Level of Digital Signature - support - + Level of Digital Signature Support - A Level 2 SCP may further - define its behavior in this byte field. - - 0 - The signature level is - unspecified, the AE is an SCU only, or the AE is not a level 2 SCP - - 1 - signature level 1 - - 2 - signature level 2 - - 3 - signature level 3 - - If extended negotiation is - not supported, the default shall have a value of 0. - + A Storage Level 2 SCP may further define its behavior in this byte field. + 0 - The Signature Level is unspecified, the AE is an SCU only, or the AE is not a Storage Level 2 SCP + 1 - Signature Level 1 + 2 - Signature Level 2 + 3 - Signature Level 3 + If Extended Negotiation is not supported, the default shall have a value of 0.
- This reserved field shall - be sent with a value 00H but not tested to this value when received. - + This reserved field shall be sent with a value 00H but not tested to this value when received.
- This byte field defines - whether the Association-requester may coerce Data Elements. It shall be encoded - as an unsigned binary integer and shall use one of the following values: - - 0 - does not coerce any - Data Element - - 1 - may coerce Data - Elements - - 2 - N/A - - Association-requester is SCU only - - If extended negotiation is - not supported, the default shall have a value of 2. - + This byte field defines whether the Association-requestor may coerce Data Elements. It shall be encoded as an unsigned binary integer and shall use one of the following values: + 0 - does not coerce any Data Element + 1 - may coerce Data Elements + 2 - N/A - Association-requestor is SCU only + If Extended Negotiation is not supported, the default shall have a value of 2.
- This reserved field shall - be sent with a value 00H but not tested to this value when received. - + This reserved field shall be sent with a value 00H but not tested to this value when received.
@@ -3844,24 +2964,15 @@ 1 @@ -3872,9 +2983,7 @@ Reserved @@ -3882,28 +2991,15 @@ 3 @@ -3914,9 +3010,7 @@ Reserved @@ -3927,24 +3021,11 @@ Element Coercion @@ -3955,9 +3036,7 @@ Reserved @@ -3965,32 +3044,14 @@
Service Class UID (A-ASSOCIATE-RQ) - SOP Class Common Extended Negotiation - Sub-Item allows the SCU to convey the Service Class UID of each proposed SOP Class. - - The Storage Service Class UID shall be - "1.2.840.10008.4.2". - + SOP Class Common Extended Negotiation Sub-Item allows the SCU to convey the Service Class UID of each proposed SOP Class. + The Storage Service Class UID shall be "1.2.840.10008.4.2".
Related General SOP Classes (A-ASSOCIATE-RQ) - A limited set of Standard SOP Classes in - the Storage Service Class are defined to have one or more Related General SOP Classes. The - Related General SOP Classes may be conveyed using the SOP Class Relationship Extended - Negotiation during association establishment as defined in - . - - identifies which Standard SOP Classes participate in this mechanism. If a Standard SOP Class is - not listed in this table, Related General SOP Classes shall not be included in a Related Storage - SOP Class Extended Negotiation Sub-Item. - + A limited set of Standard SOP Classes in the Storage Service Class are defined to have one or more Related General SOP Classes. The Related General SOP Classes may be conveyed using the SOP Class Relationship Extended Negotiation during association establishment as defined in . identifies which Standard SOP Classes participate in this mechanism. If a Standard SOP Class is not listed in this table, Related General SOP Classes shall not be included in a Related Storage SOP Class Extended Negotiation Sub-Item. - Implementation-defined Specialized SOP - Classes (see) of - the Storage Service Class may convey a Related General SOP Class. - + Implementation-defined Specialized SOP Classes (see ) of the Storage Service Class may convey a Related General SOP Class.
Service-Class-Application-Information (A-ASSOCIATE-AC)
- Level of support + Level of Storage Support - This byte field defines the - supported storage level of the Association-acceptor. It shall be encoded as an - unsigned binary integer and shall use one of the following values: - - 0 - level 0 SCP - 1 - level 1 SCP - 2 - level 2 SCP - 3 - N/A - - Association-acceptor is SCU only - - If extended negotiation is - not supported, no assumptions shall be made by the Association-requester about - the capabilities of the Association-acceptor based upon this extended - negotiation. - + This byte field defines the supported Storage Level of the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values: + 0 - Storage Level 0 SCP + 1 - Storage Level 1 SCP + 2 - Storage Level 2 SCP + 3 - N/A - Association-acceptor is SCU only + If Extended Negotiation is not supported, no assumptions shall be made by the Association-requestor about the capabilities of the Association-acceptor based upon this Extended Negotiation.
- This reserved field shall - be sent with a value 00H but not tested to this value when received. - + This reserved field shall be sent with a value 00H but not tested to this value when received.
- Level of Digital Signature - support - + Level of Digital Signature Support - A Level 2 SCP may further - define its behavior in this byte field. - - 0 - The signature level is - unspecified, the AE is an SCU only, or the AE is not a level 2 SCP - - 1 - signature level 1 - - 2 - signature level 2 - - 3 - signature level 3 - - If extended negotiation is - not supported, no assumptions shall be made by the Association-requester about - the capabilities of the Association-acceptor based upon this extended - negotiation. - + A Level 2 SCP may further define its behavior in this byte field. + 0 - The Signature Level is unspecified, the AE is an SCU only, or the AE is not a Storage Level 2 SCP + 1 - Signature Level 1 + 2 - Signature Level 2 + 3 - Signature Level 3 + If Extended Negotiation is not supported, no assumptions shall be made by the Association-requestor about the capabilities of the Association-acceptor based upon this Extended Negotiation.
- This reserved field shall - be sent with a value 00H but not tested to this value when received. - + This reserved field shall be sent with a value 00H but not tested to this value when received.
- This byte field defines - whether the Association-acceptor may coerce Data Elements. It shall be encoded - as an unsigned binary integer and shall use one of the following values: - - 0 - does not coerce any - Data Element - - 1 - may coerce Data - Elements - - 2 - N/A - - Association-acceptor is SCU only - - If extended negotiation is - not supported, no assumptions shall be made by the Association-requester about - the capabilities of the Association-acceptor based upon this extended - negotiation. - + This byte field defines whether the Association-acceptor may coerce Data Elements. It shall be encoded as an unsigned binary integer and shall use one of the following values: + 0 - does not coerce any Data Element + 1 - may coerce Data Elements + 2 - N/A - Association-acceptor is SCU only + If Extended Negotiation is not supported, no assumptions shall be made by the Association-requestor about the capabilities of the Association-acceptor based upon this Extended Negotiation.
- This reserved field shall - be sent with a value 00H but not tested to this value when received. - + This reserved field shall be sent with a value 00H but not tested to this value when received.
@@ -4000,71 +3061,49 @@ SOP Class Name @@ -4154,8 +3193,7 @@ @@ -4303,9 +3331,7 @@
Standard and Related General SOP Classes
- Related General SOP Class - Name - + Related General SOP Class Name
- 12-lead ECG Waveform - Storage - + 12-lead ECG Waveform Storage - General ECG Waveform - Storage - + General ECG Waveform Storage
- Digital Mammography X-Ray - Image Storage - For Presentation - + Digital Mammography X-Ray Image Storage - For Presentation - Digital X-Ray Image Storage - - For Presentation - + Digital X-Ray Image Storage - For Presentation
- Digital Mammography X-Ray - Image Storage - For Processing - + Digital Mammography X-Ray Image Storage - For Processing - Digital X-Ray Image Storage - - For Processing - + Digital X-Ray Image Storage - For Processing
- Digital Intra-Oral X-Ray - Image Storage - For Presentation - + Digital Intra-Oral X-Ray Image Storage - For Presentation - Digital X-Ray Image Storage - - For Presentation - + Digital X-Ray Image Storage - For Presentation
- Digital Intra-Oral X-Ray - Image Storage - For Processing - + Digital Intra-Oral X-Ray Image Storage - For Processing - Digital X-Ray Image Storage - - For Processing - + Digital X-Ray Image Storage - For Processing
- Simplified Adult Echo SR - + Simplified Adult Echo SR Enhanced SR @@ -4178,8 +3216,7 @@
- X-Ray Radiation Dose SR - + X-Ray Radiation Dose SR Enhanced SR @@ -4202,9 +3239,7 @@
- Radiopharmaceutical - Radiation Dose SR - + Radiopharmaceutical Radiation Dose SR Enhanced SR @@ -4227,8 +3262,7 @@
- Patient Radiation Dose SR - + Patient Radiation Dose SR Enhanced SR @@ -4251,9 +3285,7 @@
- Enhanced X-Ray Radiation - Dose SR - + Enhanced X-Ray Radiation Dose SR Enhanced SR @@ -4276,19 +3308,15 @@
- Acquisition Context SR - + Acquisition Context SR - Enhanced SR (see note) - + Enhanced SR (see note)
- Comprehensive SR (see - note) - + Comprehensive SR (see note)
- Spectacle Prescription - Report - + Spectacle Prescription Report Enhanced SR @@ -4313,9 +3339,7 @@
- Macular Grid Thickness and - Volume Report - + Macular Grid Thickness and Volume Report Enhanced SR @@ -4323,190 +3347,104 @@
- Enhanced CT Image Storage - + Enhanced CT Image Storage - Legacy Converted Enhanced - CT Image Storage - + Legacy Converted Enhanced CT Image Storage
- Enhanced MR Image Storage - + Enhanced MR Image Storage - Legacy Converted Enhanced - MR Image Storage - + Legacy Converted Enhanced MR Image Storage
- Enhanced PET Image - Storage - + Enhanced PET Image Storage - Legacy Converted Enhanced - PET Image Storage - + Legacy Converted Enhanced PET Image Storage
- The Acquisition Context SR may be - encoded as Enhanced or Comprehensive only if it does not contain stereotactic coordinates - (SCOORD3D). - + The Acquisition Context SR may be encoded as Enhanced or Comprehensive only if it does not contain stereotactic coordinates (SCOORD3D).
Conformance - An implementation that conforms to Storage SOP - Classes shall meet the: - + An implementation that conforms to Storage SOP Classes shall meet the: - C-STORE Service requirements as defined in - + C-STORE Service requirements as defined in - Association requirements as defined in - + Association requirements as defined in - No SCU or SCP behavior requirements other than - those in this section are specified. In particular, an SCP of the Storage SOP Classes may not attach - any significance to the particular association or associations over which C-STORE operations are - requested, nor the order in which C-STORE operations occur within an association. No constraints are - placed on the operations an SCU may perform during any particular association, other than those - defined during association negotiation. An SCP may not expect an SCU to perform C-STORE operations - in a particular order. - + No SCU or SCP behavior requirements other than those in this section are specified. In particular, an SCP of the Storage SOP Classes may not attach any significance to the particular association or associations over which C-STORE operations are requested, nor the order in which C-STORE operations occur within an association. No constraints are placed on the operations an SCU may perform during any particular association, other than those defined during association negotiation. An SCP may not expect an SCU to perform C-STORE operations in a particular order. - Similarly, no semantics are attached to the closing - of an Association, such as the end of a Study or Performed Procedure Step. - + Similarly, no semantics are attached to the closing of an Association, such as the end of a Study or Performed Procedure Step.
Conformance as an SCP
- Levels of Conformance - Three levels of conformance to the Storage - SOP Classes as an SCP may be provided: - + Levels of Storage Support + Three Levels of Storage Support are defined for an SCP that claims conformance to the Storage SOP Classes: - Level 0 (Local). Level 0 - conformance indicates that a user-defined subset of the Attributes of the image will be - stored, and all others will be discarded. This subset of the Attributes shall be defined - in the Conformance Statement of the implementer. - + Storage Level 0 (Local) indicates that a user-defined subset of the Attributes of the SOP INSTANCE will be stored, and all others will be discarded. This subset of the Attributes shall be defined in the Conformance Statement of the implementer. - Level 1 (Base). Level 1 conformance - indicates that all Type 1 and 2 Attributes defined in the IOD associated with the SOP - Class will be stored, and may be accessed. All other elements may be discarded. The SCP - may, but is not required to validate that the Attributes of the SOP Instance meets the - requirements of the IOD. - + Storage Level 1 (Base) indicates that all Type 1 and 2 Attributes defined in the IOD associated with the SOP Class will be stored, and may be accessed. All other Data Elements may be discarded. The SCP may, but is not required to validate that the Attributes of the SOP Instance meets the requirements of the IOD. - Level 2 (Full). Level 2 conformance - indicates that all Type 1, Type 2, and Type 3 Attributes defined in the Information - Object Definition associated with the SOP Class, as well as any Standard Extended - Attributes (including Private Attributes) included in the SOP Instance, will be stored - and may be accessed. The SCP may, but is not required to validate that the Attributes of - the SOP Instance meet the requirements of the IOD. - + Storage Level 2 (Full) indicates that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition associated with the SOP Class, as well as any Standard Extended Attributes (including Private Attributes) included in the SOP Instance, will be stored and may be accessed. The SCP may, but is not required to validate that the Attributes of the SOP Instance meet the requirements of the IOD. - A Level 2 SCP may discard (not store) - Type 3 Attributes that are empty (zero length and no Value), since the meaning of an empty - Type 3 Attribute is the same as absence of the Attribute. See - - definition of "Type 3 Optional Data Elements". - + A Storage Level 2 SCP may discard (not store) Type 3 Attributes that are empty (zero length and no Value), since the meaning of an empty Type 3 Attribute is the same as absence of the Attribute. See definition of "Type 3 Optional Data Elements".
Support of Additional SOP Classes - An SCP that claims conformance to Level 2 - (Full) support of the Storage Service Class may accept any Presentation Context negotiation of a - SOP Class that specifies the Storage Service Class during the SOP Class Common Extended - Negotiation (see), without asserting - conformance to that SOP Class in its Conformance Statement. - + An SCP that claims conformance to Storage Level 2 (Full) support of the Storage Service Class may accept any Presentation Context negotiation of a SOP Class that specifies the Storage Service Class during the SOP Class Common Extended Negotiation (see ), without asserting conformance to that SOP Class in its Conformance Statement. - The SCP may support storage of - all SOP Classes of the Storage Service Class, preserving all Attributes as a Level 2 - SCP. - + The SCP may support storage of all SOP Classes of the Storage Service Class, preserving all Attributes as a Storage Level 2 SCP. - This Extended Negotiation - allows an SCP to determine that a Private SOP Class in a proposed Presentation - Context follows the semantics of the Storage Service Class, and may be handled - accordingly. - + This Extended Negotiation allows an SCP to determine that a Private SOP Class in a proposed Presentation Context follows the semantics of the Storage Service Class, and may be handled accordingly. - An SCP that claims conformance to Level 2 - (Full) support of a Related General SOP Class may accept any Presentation Context negotiation of - a SOP Class that specifies that Related General SOP Class during the SOP Class Common Extended - Negotiation, without asserting conformance to that specialized SOP Class in its Conformance - Statement. - + An SCP that claims conformance to Storage Level 2 (Full) support of a Related General SOP Class may accept any Presentation Context negotiation of a SOP Class that specifies that Related General SOP Class during the SOP Class Common Extended Negotiation, without asserting conformance to that Specialized SOP Class in its Conformance Statement. - The term "specialized" in this - section is used generically, including both Implementation-defined Specialized SOP - Classes and Standard SOP Classes specified in. - + The term "specialized" in this section is used generically, including both Implementation-defined Specialized SOP Classes and Standard SOP Classes specified in . - The SCP may handle instances of - such specialized SOP Classes using the semantics of the Related General SOP Class, - but preserving all additional (potentially Type 1 or 2) Attributes as a Level 2 SCP. - + The SCP may handle instances of such Specialized SOP Classes using the semantics of the Related General SOP Class, but preserving all additional (potentially Type 1 or 2) Attributes as a Storage Level 2 SCP. - An SCP that has access to the - current content of - - might use that to determine acceptance of proposed Presentation Context SOP Classes. - This allows an SCP, even without Extended Negotiation, to be able to identify all - Standard SOP Classes of the Storage Service Class. Access to - - may be through private means, or to the publication of PS3 on the web site of the - DICOM Standards Committee. This provides an automated alternative to manually - editing a table of supported Storage SOP Classes. - + An SCP that has access to the current content of might use that to determine acceptance of proposed Presentation Context SOP Classes. This allows an SCP, even without Extended Negotiation, to be able to identify all Standard SOP Classes of the Storage Service Class. Access to may be through private means, or to the publication of PS3 on the web site of the DICOM Standards Committee. This provides an automated alternative to manually editing a table of supported Storage SOP Classes.
Coercion of Attributes - At any level of conformance, the SCP of the - Storage Service Class may modify the values of certain Attributes in order to coerce the SOP - Instance into the Query Model of the SCP. The Attributes that may be modified are shown in. - + At any Level of Storage Support, the SCP of the Storage Service Class may modify the Values of certain Attributes in order to coerce the SOP Instance into the Query Model of the SCP. The Attributes that may be modified are shown in . @@ -4538,9 +3476,7 @@
Attributes Subject to Coercion
- Other Patient IDs - Sequence - + Other Patient IDs Sequence (0010,1002) @@ -4564,282 +3500,151 @@
- The SCP of the Storage Service Class may - modify the values of Code Sequence Attributes to convert from one coding scheme into another. - This includes changing from deprecated values of Coding Scheme Designator (0008,0102) or Code - Value (0008,0100) to currently valid values. - - If an SCP performs such a modification, it - shall return a C-STORE response with a status of Warning. - + The SCP of the Storage Service Class may modify the Values of Code Sequence Attributes to convert from one coding scheme into another. + This includes changing from deprecated Values of Coding Scheme Designator (0008,0102) or Code Value (0008,0100) to currently valid Values. + If an SCP performs such a modification, it shall return a C-STORE response with a status of Warning. - Modification of these - Attributes may be necessary if the SCP is also an SCP of a Query/Retrieve SOP - Classes. These SOP Classes are described in this Standard. For example, an MR - scanner may be implemented to generate Study Instance UIDs for images generated on - the MR. When these images are sent to an archive that is HIS/RIS aware, it may - choose to change the UID of the study assigned to the study by the PACS. The - mechanism by which it performs this coercion is implementation dependent. - + Modification of these Attributes may be necessary if the SCP is also an SCP of a Query/Retrieve SOP Classes. These SOP Classes are described in this Standard. For example, an MR scanner may be implemented to generate Study Instance UIDs for images generated on the MR. When these images are sent to an archive that is HIS/RIS aware, it may choose to change the UID of the study assigned to the study by the PACS. The mechanism by which it performs this coercion is implementation dependent. - An SCP may, for instance, - convert retired Code Values with a Coding Scheme Designator value of "99SDM", "SNM3" - or "SRT" to the corresponding SCT Code Values and use the "SCT" Coding Scheme - Designator, in accordance with the DICOM conventions for SNOMED (see). - + An SCP may, for instance, convert retired Code Values with a Coding Scheme Designator Value of "99SDM", "SNM3" or "SRT" to the corresponding SCT Code Values and use the "SCT" Coding Scheme Designator, in accordance with the DICOM conventions for SNOMED (see ). - Modification of Attributes that - may be used to reference a SOP Instance by another SOP Instance (such as Study - Instance UID and Series Instance UID Attributes) will make that reference invalid. - Modification of these Attributes is strongly discouraged. - + Modification of Attributes that may be used to reference a SOP Instance by another SOP Instance (such as Study Instance UID and Series Instance UID Attributes) will make that reference invalid. Modification of these Attributes is strongly discouraged. - Other Attributes may be - modified/corrected by an SCP of a Storage SOP Class. - + Other Attributes may be modified/corrected by an SCP of a Storage SOP Class. - Modification of Attributes may - affect digital signatures referencing the content of the SOP Instance. - + Modification of Attributes may affect digital signatures referencing the content of the SOP Instance.
- Levels of Digital Signature - Three levels of Digital Signature support - are defined for an SCP that claims conformance to Level 2 (Full) storage support: - + Levels of Digital Signature Support + Three levels of Digital Signature Support are defined for an SCP that claims conformance to Storage Level 2 (Full): - Signature Level 1. SCP may not - preserve Digital Signatures and does not replace them. - + At Signature Level 1, the SCP may not preserve Digital Signatures and does not replace them. - Signature Level 2. SCP does not - preserve the integrity of incoming Digital Signatures, but does validate the signatures - of SOP Instances being stored, takes implementation-specific measures for insuring the - integrity of data stored, and will add replacement Digital Signatures before sending SOP - Instances elsewhere. - + At Signature Level 2, the SCP does not preserve the integrity of incoming Digital Signatures, + but does validate the Digital Signatures of SOP Instances being stored, takes implementation-specific measures for ensuring the integrity of data stored, + and will add replacement Digital Signatures before sending SOP Instances elsewhere. - Signature Level 3. SCP does - preserve the integrity of incoming Digital Signatures (i.e., is bit-preserving and - stores and retrieves all Attributes regardless of whether they are defined in the IOD). - + At Signature Level 3, the SCP does preserve the integrity of incoming Digital Signatures (i.e., is bit-preserving and stores and retrieves all Attributes regardless of whether they are defined in the IOD).
Conformance as an SCU - The SCU shall generate only C-STORE requests - with SOP Instances that meet the requirements of the IOD associated with the SOP Class. - + The SCU shall generate only C-STORE requests with SOP Instances that meet the requirements of the IOD associated with the SOP Class.
SCU Fall-Back Behavior - During Association Negotiation, an - application may propose a specialized SOP Class and its related general SOP Class in separate - Presentation Contexts as a Storage SCU. If the Association Acceptor rejects the specialized SOP - Class Presentation Context, but accepts the related general SOP Class Presentation Context, the - application may send instances of the specialized SOP Class as instances of the related general - SOP Class. In this fall-back behavior, the SOP Class UID of the instance shall be the UID of the - related general SOP Class, and any special semantics associated with the specialized SOP Class - may be lost; the SOP Instance UID shall remain the same. - + During Association Negotiation, an application may propose a Specialized SOP Class and its Related General SOP Class in separate Presentation Contexts as a Storage SCU. If the Association Acceptor rejects the Specialized SOP Class Presentation Context, but accepts the Related General SOP Class Presentation Context, the application may send instances of the Specialized SOP Class as instances of the Related General SOP Class. In this fall-back behavior, the SOP Class UID of the instance shall be the UID of the Related General SOP Class, and any special semantics associated with the Specialized SOP Class may be lost; the SOP Instance UID shall remain the same. - The SCU may include the SOP Class UID - of the original intended specialized SOP Class in the Attribute Original Specialized SOP - Class UID (0008,001B) of the instance sent under the related general SOP Class. In some - cases, e.g., when all intermediate storage applications are Level 2 SCPs, this may allow an - ultimate receiver of the instance to recast it as an instance of the specialized SOP Class - IOD. However, this transformation is not guaranteed. - + The SCU may include the SOP Class UID of the original intended Specialized SOP Class in the Attribute Original Specialized SOP Class UID (0008,001B) of the instance sent under the Related General SOP Class. + In some cases, e.g., when all intermediate storage applications are Storage Level 2 SCPs, + this may allow an ultimate receiver of the instance to recast it as an instance of the Specialized SOP Class IOD. + However, this transformation is not guaranteed.
Conformance Statement Requirements - An implementation may conform to a SOP Class of - the Storage Service Class as an SCU, SCP or both. The Conformance Statement shall be in the format - defined in. - + An implementation may conform to a SOP Class of the Storage Service Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
Conformance Statement for an SCU - The following issues shall be documented in - the Conformance Statement of any implementation claiming conformance to the Storage SOP Class as - an SCU: - + The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to the Storage SOP Class as an SCU: - The behavior of the SCU in the case - of a successful C-STORE response status shall be described. - + The behavior of the SCU in the case of a successful C-STORE response status shall be described. - The behavior of the SCU in each - case of an unsuccessful C-STORE response status shall be described. - + The behavior of the SCU in each case of an unsuccessful C-STORE response status shall be described. - The behavior of the SCU in the case - of a Warning status received in response to a C-STORE operation. - + The behavior of the SCU in the case of a Warning status received in response to a C-STORE operation. - Whether extended negotiation is - supported. - + Whether Extended Negotiation is supported. - The optional elements that may be - included in Storage SOP Instances for each IOD supported shall be listed. - + The optional elements that may be included in Storage SOP Instances for each IOD supported shall be listed. - The standard and privately defined - Functional Groups that may be included in Storage SOP Instances for each Multi-frame IOD - that support Functional Groups. - + The standard and privately defined Functional Groups that may be included in Storage SOP Instances for each Multi-frame IOD that support Functional Groups. - The behavior of the SCU in the case - of a C-STORE operation using a referenced pixel data transfer syntax such as JPIP - Referenced Pixel Data Transfer Syntax shall be described. This includes the duration of - validity of the reference - + The behavior of the SCU in the case of a C-STORE operation using a referenced pixel data transfer syntax such as JPIP Referenced Pixel Data Transfer Syntax shall be described. This includes the duration of validity of the reference
Conformance Statement for an SCP - The following issues shall be documented in - the Conformance Statement of any implementation claiming conformance to the Storage Service - Class as an SCP: - + The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to the Storage Service Class as an SCP: - The level of conformance, as - defined by, shall be stated. - + The Level of Storage Support, as defined by , shall be stated. - The level of Digital Signature - support, as defined by, shall be - stated. - + The Level of Digital Signature Support, as defined by , shall be stated. - The optional elements that will be - discarded (if any) shall be listed for each IOD supported. - + The optional Attributes that will be discarded (if any) shall be listed for each IOD supported. - The mechanisms by which additional - SOP Classes are dynamically supported, as defined by, - shall be stated. - + The mechanisms by which additional SOP Classes are dynamically supported, as defined by , shall be stated. - The Conformance Statement shall - document the policies concerning the Attribute Lossy Image Compression (0028,2110). - + The Conformance Statement shall document the policies concerning the Attribute Lossy Image Compression (0028,2110). - The behavior of the SCP in the case - of a successful C-STORE operation shall be described. This includes the following: - + The behavior of the SCP in the case of a successful C-STORE operation shall be described. This includes the following: - the access method for a - stored SOP Instance - + the access method for a stored SOP Instance - the duration of the - storage - + the duration of the storage - The meaning of each case of an - unsuccessful C-STORE response status shall be described, as well as appropriate recovery - action. - + The meaning of each case of an unsuccessful C-STORE response status shall be described, as well as appropriate recovery action. - The meaning of each case of a - warning C-STORE response status shall be described, as well as appropriate action. - + The meaning of each case of a warning C-STORE response status shall be described, as well as appropriate action. - If the SCP performs coercion on any - Attributes, this shall be stated, and the conditions under which it may occur shall be - described. - + If the SCP performs coercion on any Attributes, this shall be stated, and the conditions under which it may occur shall be described.
Specialized Conformance - Implementations may provide Specialized SOP - Class conformance by providing a proper superset of the SOP Instances to be stored. Implementations - providing Specialized SOP Class Conformance to one of the SOP Classes defined in this Annex shall be - conformant as described in the following sections and shall include within their Conformance - Statement information as described in the following sections. - - An implementation shall be permitted to conform - as a Specialization of the Standard SOP Class as an SCU, SCP or both. The Conformance Statement - shall be in the format defined in. - + Implementations may provide Specialized SOP Class conformance by providing a proper superset of the SOP Instances to be stored. Implementations providing Specialized SOP Class Conformance to one of the SOP Classes defined in this Annex shall be conformant as described in the following sections and shall include within their Conformance Statement information as described in the following sections. + An implementation shall be permitted to conform as a Specialization of the Standard SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
Specialized SOP Class Identification - Any implementation that specializes the - Standard SOP Class shall define its specialization as an Allomorphic subclass of the Standard - SOP Class. As such, the specialization shall have its own unique SOP Class identification. - - The Conformance Statement shall include a - SOP Class Identification Statement as defined in, - declaring a SOP Name and SOP Class UID that identify the Specialized SOP Class. The SOP Name is - not guaranteed to be unique (unless the implementer chooses to copyright it) but is provided for - informal identification of the SOP Class. The SOP Class UID shall uniquely identify the - Specialized SOP Class and conform to the DICOM UID requirements as specified in. - + Any implementation that specializes the Standard SOP Class shall define its specialization as an Allomorphic subclass of the Standard SOP Class. As such, the specialization shall have its own unique SOP Class identification. + The Conformance Statement shall include a SOP Class Identification Statement as defined in , declaring a SOP Name and SOP Class UID that identify the Specialized SOP Class. The SOP Name is not guaranteed to be unique (unless the implementer chooses to copyright it) but is provided for informal identification of the SOP Class. The SOP Class UID shall uniquely identify the Specialized SOP Class and conform to the DICOM UID requirements as specified in .
Specialized Information Object Definition - The Standard SOP Class may be specialized - by supporting additional private Attributes. The SCU Operations Statement shall describe these - specializations and be formatted as defined in. - Following this statement shall be the list of Attributes that may be sent or stored with SOP - Instances. - + The Standard SOP Class may be specialized by supporting additional private Attributes. The SCU Operations Statement shall describe these specializations and be formatted as defined in . Following this statement shall be the list of Attributes that may be sent or stored with SOP Instances.
Standard SOP Classes - The SOP Classes in the Storage Service Class - identify the Composite IODs to be stored. - - identifies Standard SOP Classes. - + The SOP Classes in the Storage Service Class identify the Composite IODs to be stored. identifies Standard SOP Classes. @@ -4852,11 +3657,7 @@ @@ -5032,18 +3816,16 @@ @@ -5129,8 +3909,7 @@ @@ -5202,8 +3979,7 @@ - + @@ -5993,9 +4677,7 @@ @@ -6570,8 +5188,7 @@ Basic Text SR Storage
Standard SOP Classes
- IOD Specification (defined in - ) - + IOD Specification (defined in ) @@ -4867,9 +3668,7 @@
- Computed Radiography Image - Storage - + Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 @@ -4883,9 +3682,7 @@
- Digital X-Ray Image Storage - For - Presentation - + Digital X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.1 @@ -4897,19 +3694,16 @@ - - + +
- Digital X-Ray Image Storage - For - Processing - + Digital X-Ray Image Storage - For Processing - 1.2.840.10008.5.1.4.1.1.1.1.1 - + 1.2.840.10008.5.1.4.1.1.1.1.1 @@ -4918,15 +3712,13 @@ - - + +
- Digital Mammography X-Ray Image - Storage - For Presentation - + Digital Mammography X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.2 @@ -4938,19 +3730,16 @@ - - + +
- Digital Mammography X-Ray Image - Storage - For Processing - + Digital Mammography X-Ray Image Storage - For Processing - 1.2.840.10008.5.1.4.1.1.1.2.1 - + 1.2.840.10008.5.1.4.1.1.1.2.1 @@ -4959,15 +3748,13 @@ - - + +
- Digital Intra-Oral X-Ray Image - Storage - For Presentation - + Digital Intra-Oral X-Ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.3 @@ -4979,19 +3766,16 @@ - - + +
- Digital Intra-Oral X-Ray Image - Storage - For Processing - + Digital Intra-Oral X-Ray Image Storage - For Processing - 1.2.840.10008.5.1.4.1.1.1.3.1 - + 1.2.840.10008.5.1.4.1.1.1.3.1 @@ -5000,8 +3784,8 @@ - - + +
- - + + - - + +
- Legacy Converted Enhanced CT Image - Storage - + Legacy Converted Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.2 @@ -5055,18 +3837,16 @@ - - + + - - + +
- Ultrasound Multi-frame Image - Storage - + Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 @@ -5106,11 +3886,11 @@ - - + + - - + +
- Enhanced MR Color Image Storage - + Enhanced MR Color Image Storage 1.2.840.10008.5.1.4.1.1.4.3 @@ -5142,18 +3921,16 @@ - - + + - - + +
- Legacy Converted Enhanced MR Image - Storage - + Legacy Converted Enhanced MR Image Storage 1.2.840.10008.5.1.4.1.1.4.4 @@ -5165,11 +3942,11 @@ - - + + - - + +
- Secondary Capture Image Storage - + Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 @@ -5217,9 +3993,7 @@
- Multi-frame Single Bit Secondary - Capture Image Storage - + Multi-frame Single Bit Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.1 @@ -5233,9 +4007,7 @@
- Multi-frame Grayscale Byte - Secondary Capture Image Storage - + Multi-frame Grayscale Byte Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.2 @@ -5249,9 +4021,7 @@
- Multi-frame Grayscale Word - Secondary Capture Image Storage - + Multi-frame Grayscale Word Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.3 @@ -5265,9 +4035,7 @@
- Multi-frame True Color Secondary - Capture Image Storage - + Multi-frame True Color Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.4 @@ -5284,8 +4052,7 @@ 12-lead ECG Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.1.1 - + 1.2.840.10008.5.1.4.1.1.9.1.1 @@ -5299,8 +4066,7 @@ General ECG Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.1.2 - + 1.2.840.10008.5.1.4.1.1.9.1.2 @@ -5311,12 +4077,10 @@
- Ambulatory ECG Waveform Storage - + Ambulatory ECG Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.1.3 - + 1.2.840.10008.5.1.4.1.1.9.1.3 @@ -5330,8 +4094,7 @@ Hemodynamic Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.2.1 - + 1.2.840.10008.5.1.4.1.1.9.2.1 @@ -5342,13 +4105,10 @@
- Cardiac Electrophysiology Waveform - Storage - + Cardiac Electrophysiology Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.3.1 - + 1.2.840.10008.5.1.4.1.1.9.3.1 @@ -5359,13 +4119,10 @@
- Basic Voice Audio Waveform - Storage - + Basic Voice Audio Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.4.1 - + 1.2.840.10008.5.1.4.1.1.9.4.1 @@ -5376,12 +4133,10 @@
- General Audio Waveform Storage - + General Audio Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.4.2 - + 1.2.840.10008.5.1.4.1.1.9.4.2 @@ -5392,12 +4147,10 @@
- Arterial Pulse Waveform Storage - + Arterial Pulse Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.5.1 - + 1.2.840.10008.5.1.4.1.1.9.5.1 @@ -5411,8 +4164,7 @@ Respiratory Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.6.1 - + 1.2.840.10008.5.1.4.1.1.9.6.1 @@ -5423,13 +4175,10 @@
- Multi-channel Respiratory Waveform - Storage - + Multi-channel Respiratory Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.6.2 - + 1.2.840.10008.5.1.4.1.1.9.6.2 @@ -5440,13 +4189,10 @@
- Routine Scalp Electroencephalogram - Waveform Storage - + Routine Scalp Electroencephalogram Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.7.1 - + 1.2.840.10008.5.1.4.1.1.9.7.1 @@ -5457,12 +4203,10 @@
- Electromyogram Waveform Storage - + Electromyogram Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.7.2 - + 1.2.840.10008.5.1.4.1.1.9.7.2 @@ -5473,12 +4217,10 @@
- Electrooculogram Waveform Storage - + Electrooculogram Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.7.3 - + 1.2.840.10008.5.1.4.1.1.9.7.3 @@ -5489,13 +4231,10 @@
- Sleep Electroencephalogram Waveform - Storage - + Sleep Electroencephalogram Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.7.4 - + 1.2.840.10008.5.1.4.1.1.9.7.4 @@ -5506,12 +4245,10 @@
- Body Position Waveform Storage - + Body Position Waveform Storage - 1.2.840.10008.5.1.4.1.1.9.8.1 - + 1.2.840.10008.5.1.4.1.1.9.8.1 @@ -5520,11 +4257,9 @@
- Grayscale Softcopy Presentation - State Storage - + Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1 @@ -5538,9 +4273,7 @@
- Color Softcopy Presentation State - Storage - + Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.2 @@ -5554,9 +4287,7 @@
- Pseudo-Color Softcopy Presentation - State Storage - + Pseudo-Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.3 @@ -5570,9 +4301,7 @@
- Blending Softcopy Presentation - State Storage - + Blending Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.4 @@ -5586,9 +4315,7 @@
- XA/XRF Grayscale Softcopy - Presentation State Storage - + XA/XRF Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.5 @@ -5602,14 +4329,10 @@
- Grayscale Planar MPR Volumetric - Presentation State Storage - + Grayscale Planar MPR Volumetric Presentation State Storage - - 1.2.840.10008.​5.​1.​4.​1.​1.​11.​6 - + 1.2.840.10008.​5.​1.​4.​1.​1.​11.​6 @@ -5618,20 +4341,16 @@ - - + +
- Compositing Planar MPR Volumetric - Presentation State Storage - + Compositing Planar MPR Volumetric Presentation State Storage - - 1.2.840.10008.​5.​1.​4.​1.​1.​11.​7 - + 1.2.840.10008.​5.​1.​4.​1.​1.​11.​7 @@ -5640,15 +4359,13 @@ - - + +
- Advanced Blending Presentation - State Storage - + Advanced Blending Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.8 @@ -5662,9 +4379,7 @@
- Volume Rendering Volumetric - Presentation State Storage - + Volume Rendering Volumetric Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.9 @@ -5676,19 +4391,16 @@ - - + +
- Segmented Volume Rendering - Volumetric Presentation State Storage - + Segmented Volume Rendering Volumetric Presentation State Storage - 1.2.840.10008.5.1.4.1.1.11.10 - + 1.2.840.10008.5.1.4.1.1.11.10 @@ -5697,19 +4409,16 @@ - - + +
- Multiple Volume Rendering - Volumetric Presentation State Storage - + Multiple Volume Rendering Volumetric Presentation State Storage - 1.2.840.10008.5.1.4.1.1.11.11 - + 1.2.840.10008.5.1.4.1.1.11.11 @@ -5718,14 +4427,13 @@ - - + +
- X-Ray Angiographic Image Storage - + X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 @@ -5742,8 +4450,7 @@ Enhanced XA Image Storage - 1.2.840.10008.5.1.4.1.1.12.1.1 - + 1.2.840.10008.5.1.4.1.1.12.1.1 @@ -5754,9 +4461,7 @@
- X-Ray Radiofluoroscopic Image - Storage - + X-Ray Radiofluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2 @@ -5773,8 +4478,7 @@ Enhanced XRF Image Storage - 1.2.840.10008.5.1.4.1.1.12.2.1 - + 1.2.840.10008.5.1.4.1.1.12.2.1 @@ -5785,13 +4489,10 @@
- X-Ray 3D Angiographic Image - Storage - + X-Ray 3D Angiographic Image Storage - 1.2.840.10008.5.1.4.1.1.13.1.1 - + 1.2.840.10008.5.1.4.1.1.13.1.1 @@ -5802,13 +4503,10 @@
- X-Ray 3D Craniofacial Image - Storage - + X-Ray 3D Craniofacial Image Storage - 1.2.840.10008.5.1.4.1.1.13.1.2 - + 1.2.840.10008.5.1.4.1.1.13.1.2 @@ -5819,13 +4517,10 @@
- Breast Tomosynthesis Image - Storage - + Breast Tomosynthesis Image Storage - 1.2.840.10008.5.1.4.1.1.13.1.3 - + 1.2.840.10008.5.1.4.1.1.13.1.3 @@ -5836,13 +4531,10 @@
- Breast Projection X-Ray Image - Storage - For Presentation - + Breast Projection X-Ray Image Storage - For Presentation - 1.2.840.10008.5.1.4.1.1.13.1.4 - + 1.2.840.10008.5.1.4.1.1.13.1.4 @@ -5851,19 +4543,16 @@ - - + +
- Breast Projection X-Ray Image - Storage - For Processing - + Breast Projection X-Ray Image Storage - For Processing - 1.2.840.10008.5.1.4.1.1.13.1.5 - + 1.2.840.10008.5.1.4.1.1.13.1.5 @@ -5872,15 +4561,13 @@ - - + +
- Intravascular Optical Coherence - Tomography Image Storage - For Presentation - + Intravascular Optical Coherence Tomography Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.14.1 @@ -5892,15 +4579,13 @@ - - + +
- Intravascular Optical Coherence - Tomography Image Storage - For Processing - + Intravascular Optical Coherence Tomography Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.14.2 @@ -5912,14 +4597,13 @@ - - + +
- Nuclear Medicine Image Storage - + Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 @@ -5959,8 +4643,8 @@ - - + +
- Deformable Spatial Registration - Storage - + Deformable Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.3 @@ -6051,8 +4733,7 @@
- Real World Value Mapping Storage - + Real World Value Mapping Storage 1.2.840.10008.5.1.4.1.1.67 @@ -6080,8 +4761,7 @@
- Surface Scan Point Cloud Storage - + Surface Scan Point Cloud Storage 1.2.840.10008.5.1.4.1.1.68.2 @@ -6098,8 +4778,7 @@ VL Endoscopic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.1 - + 1.2.840.10008.5.1.4.1.1.77.1.1 @@ -6110,12 +4789,10 @@
- Video Endoscopic Image Storage - + Video Endoscopic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.1.1 - + 1.2.840.10008.5.1.4.1.1.77.1.1.1 @@ -6129,8 +4806,7 @@ VL Microscopic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.2 - + 1.2.840.10008.5.1.4.1.1.77.1.2 @@ -6141,12 +4817,10 @@
- Video Microscopic Image Storage - + Video Microscopic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.2.1 - + 1.2.840.10008.5.1.4.1.1.77.1.2.1 @@ -6157,13 +4831,10 @@
- VL Slide-Coordinates Microscopic - Image Storage - + VL Slide-Coordinates Microscopic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.3 - + 1.2.840.10008.5.1.4.1.1.77.1.3 @@ -6174,12 +4845,10 @@
- VL Photographic Image Storage - + VL Photographic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.4 - + 1.2.840.10008.5.1.4.1.1.77.1.4 @@ -6190,12 +4859,10 @@
- Video Photographic Image Storage - + Video Photographic Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.4.1 - + 1.2.840.10008.5.1.4.1.1.77.1.4.1 @@ -6206,13 +4873,10 @@
- Ophthalmic Photography 8 Bit Image - Storage - + Ophthalmic Photography 8 Bit Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.1 - + 1.2.840.10008.5.1.4.1.1.77.1.5.1 @@ -6223,13 +4887,10 @@
- Ophthalmic Photography 16 Bit Image - Storage - + Ophthalmic Photography 16 Bit Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.2 - + 1.2.840.10008.5.1.4.1.1.77.1.5.2 @@ -6240,12 +4901,10 @@
- Stereometric Relationship Storage - + Stereometric Relationship Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.3 - + 1.2.840.10008.5.1.4.1.1.77.1.5.3 @@ -6256,13 +4915,10 @@
- Ophthalmic Tomography Image - Storage - + Ophthalmic Tomography Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.4 - + 1.2.840.10008.5.1.4.1.1.77.1.5.4 @@ -6273,13 +4929,10 @@
- Wide Field Ophthalmic Photography - Stereographic Projection Image Storage - + Wide Field Ophthalmic Photography Stereographic Projection Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.5 - + 1.2.840.10008.5.1.4.1.1.77.1.5.5 @@ -6290,13 +4943,10 @@
- Wide Field Ophthalmic Photography - 3D Coordinates Image Storage - + Wide Field Ophthalmic Photography 3D Coordinates Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.6 - + 1.2.840.10008.5.1.4.1.1.77.1.5.6 @@ -6307,13 +4957,10 @@
- Ophthalmic Optical Coherence - Tomography En Face Image Storage - + Ophthalmic Optical Coherence Tomography En Face Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.7 - + 1.2.840.10008.5.1.4.1.1.77.1.5.7 @@ -6324,13 +4971,10 @@
- Ophthalmic Optical Coherence - Tomography B-scan Volume Analysis Storage - + Ophthalmic Optical Coherence Tomography B-scan Volume Analysis Storage - 1.2.840.10008.5.1.4.1.1.77.1.5.8 - + 1.2.840.10008.5.1.4.1.1.77.1.5.8 @@ -6341,13 +4985,10 @@
- VL Whole Slide Microscopy Image - Storage - + VL Whole Slide Microscopy Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.6 - + 1.2.840.10008.5.1.4.1.1.77.1.6 @@ -6358,13 +4999,10 @@
- Dermoscopic Photography Image - Storage - + Dermoscopic Photography Image Storage - 1.2.840.10008.5.1.4.1.1.77.1.7 - + 1.2.840.10008.5.1.4.1.1.77.1.7 @@ -6375,8 +5013,7 @@
- Lensometry Measurements Storage - + Lensometry Measurements Storage 1.2.840.10008.5.1.4.1.1.78.1 @@ -6390,9 +5027,7 @@
- Autorefraction Measurements - Storage - + Autorefraction Measurements Storage 1.2.840.10008.5.1.4.1.1.78.2 @@ -6406,8 +5041,7 @@
- Keratometry Measurements Storage - + Keratometry Measurements Storage 1.2.840.10008.5.1.4.1.1.78.3 @@ -6421,9 +5055,7 @@
- Subjective Refraction Measurements - Storage - + Subjective Refraction Measurements Storage 1.2.840.10008.5.1.4.1.1.78.4 @@ -6437,9 +5069,7 @@
- Visual Acuity Measurements - Storage - + Visual Acuity Measurements Storage 1.2.840.10008.5.1.4.1.1.78.5 @@ -6453,9 +5083,7 @@
- Spectacle Prescription Report - Storage - + Spectacle Prescription Report Storage 1.2.840.10008.5.1.4.1.1.78.6 @@ -6469,9 +5097,7 @@
- Ophthalmic Axial Measurements - Storage - + Ophthalmic Axial Measurements Storage 1.2.840.10008.5.1.4.1.1.78.7 @@ -6485,9 +5111,7 @@
- Intraocular Lens Calculations - Storage - + Intraocular Lens Calculations Storage 1.2.840.10008.5.1.4.1.1.78.8 @@ -6501,9 +5125,7 @@
- Macular Grid Thickness and Volume - Report - + Macular Grid Thickness and Volume Report 1.2.840.10008.5.1.4.1.1.79.1 @@ -6517,9 +5139,7 @@
- Ophthalmic Visual Field Static - Perimetry Measurements Storage - + Ophthalmic Visual Field Static Perimetry Measurements Storage 1.2.840.10008.5.1.4.1.1.80.1 @@ -6533,8 +5153,7 @@
- Ophthalmic Thickness Map Storage - + Ophthalmic Thickness Map Storage 1.2.840.10008.5.1.4.1.1.81.1 @@ -6548,8 +5167,7 @@
- Corneal Topography Map Storage - + Corneal Topography Map Storage 1.2.840.10008.5.1.4.1.1.82.1 @@ -6561,8 +5179,8 @@ - - + +
- 1.2.840.10008.5.1.4.1.1.88.11 - + 1.2.840.10008.5.1.4.1.1.88.11 @@ -6585,8 +5202,7 @@ Enhanced SR Storage - 1.2.840.10008.5.1.4.1.1.88.22 - + 1.2.840.10008.5.1.4.1.1.88.22 @@ -6600,8 +5216,7 @@ Comprehensive SR Storage - 1.2.840.10008.5.1.4.1.1.88.33 - + 1.2.840.10008.5.1.4.1.1.88.33 @@ -6615,8 +5230,7 @@ Comprehensive 3D SR Storage - 1.2.840.10008.5.1.4.1.1.88.34 - + 1.2.840.10008.5.1.4.1.1.88.34 @@ -6630,8 +5244,7 @@ Extensible SR Storage - 1.2.840.10008.5.1.4.1.1.88.35 - + 1.2.840.10008.5.1.4.1.1.88.35 @@ -6645,8 +5258,7 @@ Procedure Log Storage - 1.2.840.10008.5.1.4.1.1.88.40 - + 1.2.840.10008.5.1.4.1.1.88.40 @@ -6660,8 +5272,7 @@ Mammography CAD SR Storage - 1.2.840.10008.5.1.4.1.1.88.50 - + 1.2.840.10008.5.1.4.1.1.88.50 @@ -6672,13 +5283,10 @@
- Key Object Selection Document - Storage - + Key Object Selection Document Storage - 1.2.840.10008.5.1.4.1.1.88.59 - + 1.2.840.10008.5.1.4.1.1.88.59 @@ -6692,8 +5300,7 @@ Chest CAD SR Storage - 1.2.840.10008.5.1.4.1.1.88.65 - + 1.2.840.10008.5.1.4.1.1.88.65 @@ -6704,12 +5311,10 @@
- X-Ray Radiation Dose SR Storage - + X-Ray Radiation Dose SR Storage - 1.2.840.10008.5.1.4.1.1.88.67 - + 1.2.840.10008.5.1.4.1.1.88.67 @@ -6720,13 +5325,10 @@
- Radiopharmaceutical Radiation Dose - SR Storage - + Radiopharmaceutical Radiation Dose SR Storage - 1.2.840.10008.5.1.4.1.1.88.68 - + 1.2.840.10008.5.1.4.1.1.88.68 @@ -6740,8 +5342,7 @@ Colon CAD SR Storage - 1.2.840.10008.5.1.4.1.1.88.69 - + 1.2.840.10008.5.1.4.1.1.88.69 @@ -6752,13 +5353,10 @@
- Implantation Plan SR Document - Storage - + Implantation Plan SR Document Storage - 1.2.840.10008.5.1.4.1.1.88.70 - + 1.2.840.10008.5.1.4.1.1.88.70 @@ -6769,13 +5367,10 @@
- Acquisition Context SR Storage - + Acquisition Context SR Storage - - 1.2.840.10008.5.​1.​4.​1.​1.​88.​71 - + 1.2.840.10008.5.​1.​4.​1.​1.​88.​71 @@ -6786,13 +5381,10 @@
- Simplified Adult Echo SR Storage - + Simplified Adult Echo SR Storage - - 1.2.840.10008.5.​1.​4.​1.​1.​88.​72 - + 1.2.840.10008.5.​1.​4.​1.​1.​88.​72 @@ -6803,13 +5395,10 @@
- Patient Radiation Dose SR Storage - + Patient Radiation Dose SR Storage - - 1.2.840.10008.5.​1.​4.​1.​1.​88.​73 - + 1.2.840.10008.5.​1.​4.​1.​1.​88.​73 @@ -6820,14 +5409,10 @@
- Planned Imaging Agent - Administration SR Storage - + Planned Imaging Agent Administration SR Storage - - 1.2.840.10008.5.​1.​4.​1.​1.​88.​74 - + 1.2.840.10008.5.​1.​4.​1.​1.​88.​74 @@ -6838,14 +5423,10 @@
- Performed Imaging Agent - Administration SR Storage - + Performed Imaging Agent Administration SR Storage - - 1.2.840.10008.5.​1.​4.​1.​1.​88.​75 - + 1.2.840.10008.5.​1.​4.​1.​1.​88.​75 @@ -6856,14 +5437,10 @@
- Enhanced X-Ray Radiation Dose SR - Storage - + Enhanced X-Ray Radiation Dose SR Storage - - 1.2.840.10008.5.​1.​4.​1.​1.​88.​76 - + 1.2.840.10008.5.​1.​4.​1.​1.​88.​76 @@ -6874,9 +5451,7 @@
- Content Assessment Results - Storage - + Content Assessment Results Storage 1.2.840.10008.5.1.4.1.1.90.1 @@ -6886,15 +5461,13 @@ - - + +
- Microscopy Bulk Simple Annotations - Storage - + Microscopy Bulk Simple Annotations Storage 1.2.840.10008.5.1.4.1.1.91.1 @@ -6909,8 +5482,7 @@ Encapsulated PDF Storage - 1.2.840.10008.5.1.4.1.1.104.1 - + 1.2.840.10008.5.1.4.1.1.104.1 @@ -6924,8 +5496,7 @@ Encapsulated CDA Storage - 1.2.840.10008.5.1.4.1.1.104.2 - + 1.2.840.10008.5.1.4.1.1.104.2 @@ -6939,8 +5510,7 @@ Encapsulated STL Storage - 1.2.840.10008.5.1.4.1.1.104.3 - + 1.2.840.10008.5.1.4.1.1.104.3 @@ -6954,8 +5524,7 @@ Encapsulated OBJ Storage - 1.2.840.10008.5.1.4.1.1.104.4 - + 1.2.840.10008.5.1.4.1.1.104.4 @@ -6969,8 +5538,7 @@ Encapsulated MTL Storage - 1.2.840.10008.5.1.4.1.1.104.5 - + 1.2.840.10008.5.1.4.1.1.104.5 @@ -6981,9 +5549,7 @@
- Positron Emission Tomography Image - Storage - + Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128 @@ -7009,22 +5575,19 @@ - - + + - - + +
- Legacy Converted Enhanced PET Image - Storage - + Legacy Converted Enhanced PET Image Storage - 1.2.840.10008.5.1.4.1.1.128.1 - + 1.2.840.10008.5.1.4.1.1.128.1 @@ -7039,8 +5602,7 @@
- Basic Structured Display Storage - + Basic Structured Display Storage 1.2.840.10008.5.1.4.1.1.131 @@ -7052,19 +5614,16 @@ - - + +
- CT Performed Procedure Protocol - Storage - + CT Performed Procedure Protocol Storage - 1.2.840.10008.5.1.4.1.1.200.2 - + 1.2.840.10008.5.1.4.1.1.200.2 @@ -7073,19 +5632,16 @@ - - + +
- XA Performed Procedure Protocol - Storage - + XA Performed Procedure Protocol Storage - 1.2.840.10008.5.1.4.1.1.200.8 - + 1.2.840.10008.5.1.4.1.1.200.8 @@ -7103,8 +5659,7 @@ RT Image Storage - 1.2.840.10008.5.1.4.1.1.481.1 - + 1.2.840.10008.5.1.4.1.1.481.1 @@ -7118,8 +5673,7 @@ RT Dose Storage - 1.2.840.10008.5.1.4.1.1.481.2 - + 1.2.840.10008.5.1.4.1.1.481.2 @@ -7133,8 +5687,7 @@ RT Structure Set Storage - 1.2.840.10008.5.1.4.1.1.481.3 - + 1.2.840.10008.5.1.4.1.1.481.3 @@ -7145,12 +5698,10 @@
- RT Beams Treatment Record Storage - + RT Beams Treatment Record Storage - 1.2.840.10008.5.1.4.1.1.481.4 - + 1.2.840.10008.5.1.4.1.1.481.4 @@ -7164,8 +5715,7 @@ RT Plan Storage - 1.2.840.10008.5.1.4.1.1.481.5 - + 1.2.840.10008.5.1.4.1.1.481.5 @@ -7176,13 +5726,10 @@
- RT Brachy Treatment Record - Storage - + RT Brachy Treatment Record Storage - 1.2.840.10008.5.1.4.1.1.481.6 - + 1.2.840.10008.5.1.4.1.1.481.6 @@ -7193,13 +5740,10 @@
- RT Treatment Summary Record - Storage - + RT Treatment Summary Record Storage - 1.2.840.10008.5.1.4.1.1.481.7 - + 1.2.840.10008.5.1.4.1.1.481.7 @@ -7213,8 +5757,7 @@ RT Ion Plan Storage - 1.2.840.10008.5.1.4.1.1.481.8 - + 1.2.840.10008.5.1.4.1.1.481.8 @@ -7225,13 +5768,10 @@
- RT Ion Beams Treatment Record - Storage - + RT Ion Beams Treatment Record Storage - 1.2.840.10008.5.1.4.1.1.481.9 - + 1.2.840.10008.5.1.4.1.1.481.9 @@ -7245,8 +5785,7 @@ RT Physician Intent Storage - 1.2.840.10008.5.1.4.1.1.481.10 - + 1.2.840.10008.5.1.4.1.1.481.10 @@ -7257,12 +5796,10 @@
- RT Segment Annotation Storage - + RT Segment Annotation Storage - 1.2.840.10008.5.1.4.1.1.481.11 - + 1.2.840.10008.5.1.4.1.1.481.11 @@ -7276,8 +5813,7 @@ RT Radiation Set Storage - 1.2.840.10008.5.1.4.1.1.481.12 - + 1.2.840.10008.5.1.4.1.1.481.12 @@ -7288,13 +5824,10 @@
- C-Arm Photon-Electron Radiation - Storage - + C-Arm Photon-Electron Radiation Storage - 1.2.840.10008.5.1.4.1.1.481.13 - + 1.2.840.10008.5.1.4.1.1.481.13 @@ -7305,12 +5838,10 @@
- Tomotherapeutic Radiation Storage - + Tomotherapeutic Radiation Storage - 1.2.840.10008.5.1.4.1.1.481.14 - + 1.2.840.10008.5.1.4.1.1.481.14 @@ -7321,12 +5852,10 @@
- Robotic-Arm Radiation Storage - + Robotic-Arm Radiation Storage - 1.2.840.10008.5.1.4.1.1.481.15 - + 1.2.840.10008.5.1.4.1.1.481.15 @@ -7337,12 +5866,10 @@
- RT Radiation Record Set Storage - + RT Radiation Record Set Storage - 1.2.840.10008.5.1.4.1.1.481.16 - + 1.2.840.10008.5.1.4.1.1.481.16 @@ -7353,13 +5880,10 @@
- RT Radiation Salvage Record - Storage - + RT Radiation Salvage Record Storage - 1.2.840.10008.5.1.4.1.1.481.17 - + 1.2.840.10008.5.1.4.1.1.481.17 @@ -7370,13 +5894,10 @@
- Tomotherapeutic Radiation Record - Storage - + Tomotherapeutic Radiation Record Storage - 1.2.840.10008.5.1.4.1.1.481.18 - + 1.2.840.10008.5.1.4.1.1.481.18 @@ -7387,13 +5908,10 @@
- C-Arm Photon-Electron Radiation - Record Storage - + C-Arm Photon-Electron Radiation Record Storage - 1.2.840.10008.5.1.4.1.1.481.19 - + 1.2.840.10008.5.1.4.1.1.481.19 @@ -7404,12 +5922,10 @@
- Robotic Radiation Record Storage - + Robotic Radiation Record Storage - 1.2.840.10008.5.1.4.1.1.481.20 - + 1.2.840.10008.5.1.4.1.1.481.20 @@ -7420,13 +5936,10 @@
- RT Radiation Set Delivery - Instruction Storage - + RT Radiation Set Delivery Instruction Storage - 1.2.840.10008.5.1.4.1.1.481.21 - + 1.2.840.10008.5.1.4.1.1.481.21 @@ -7437,12 +5950,10 @@
- RT Treatment Preparation Storage - + RT Treatment Preparation Storage - 1.2.840.10008.5.1.4.1.1.481.22 - + 1.2.840.10008.5.1.4.1.1.481.22 @@ -7453,9 +5964,7 @@
- RT Beams Delivery Instruction - Storage - + RT Beams Delivery Instruction Storage 1.2.840.10008.5.1.4.34.7 @@ -7469,9 +5978,7 @@
- RT Brachy Application Setup - Delivery Instruction Storage - + RT Brachy Application Setup Delivery Instruction Storage 1.2.840.10008.5.1.4.34.10 @@ -7486,131 +5993,57 @@
- The Generic Implant Template Storage, Implant - Assembly Template Storage, and Implant Template Group Storage SOP Classes were formerly specified in - this table, incorrectly since they do not use the Patient / Study / Series / Instance information - model. Those have been consolidated into the Non-Patient Object Storage Service Class (see). - + The Generic Implant Template Storage, Implant Assembly Template Storage, and Implant Template Group Storage SOP Classes were formerly specified in this table, incorrectly since they do not use the Patient / Study / Series / Instance information model. Those have been consolidated into the Non-Patient Object Storage Service Class (see ).
Specialization for Standard SOP Classes
Digital X-Ray Image Storage SOP Classes - The Digital X-Ray Image Storage - For - Presentation SOP Class shall use the DX IOD with an Enumerated Value of FOR PRESENTATION for - Presentation Intent Type (0008,0068). - - The Digital X-Ray Image Storage - For - Processing SOP Class shall use the DX IOD with an Enumerated Value of FOR PROCESSING for - Presentation Intent Type (0008,0068). - - An SCU or SCP of the Digital X-Ray Image - Storage - For Processing SOP Class shall also support the Digital X-Ray Image Storage - For - Presentation SOP Class in the same role. - + The Digital X-Ray Image Storage - For Presentation SOP Class shall use the DX IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068). + The Digital X-Ray Image Storage - For Processing SOP Class shall use the DX IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068). + An SCU or SCP of the Digital X-Ray Image Storage - For Processing SOP Class shall also support the Digital X-Ray Image Storage - For Presentation SOP Class in the same role. - The intent of this requirement - is to ensure a useful level of interoperability by avoiding the situation where an - SCU might support only the Digital X-Ray Image Storage - For Processing SOP Class - and an SCP only the Digital X-Ray Image Storage - For Presentation SOP Class, or - vice versa. The burden is therefore to support the Digital X-Ray Image Storage - For - Presentation SOP Class as a "baseline". - + The intent of this requirement is to ensure a useful level of interoperability by avoiding the situation where an SCU might support only the Digital X-Ray Image Storage - For Processing SOP Class and an SCP only the Digital X-Ray Image Storage - For Presentation SOP Class, or vice versa. The burden is therefore to support the Digital X-Ray Image Storage - For Presentation SOP Class as a "baseline". - The term "support" is used in - this section in the sense that an SCU or SCP must be capable of sending or receiving - the For Presentation SOP Class. There is no intent to imply that an SCU must always - send an instance of the For Presentation SOP Class when an instance of the For - Processing SOP Class is sent. - - Nor is there any intent to - imply that during Association establishment, that a Presentation Context for the For - Presentation SOP Class has to be proposed by the initiator. However, an association - acceptor may reject a For Presentation SOP Class Presentation Context if it accepts - a For Processing SOP Class Presentation Context, and prefers that SOP Class, in - which case it may no longer be able to "pass on" the object later as an SCU unless - it is able to generate a For Presentation object. - - It is not possible for an SCP - to determine from proposed Presentation Contexts whether or not an SCU "supports" - (is capable of sending) both For Processing and For Presentation SOP Class - Instances. Such a determination requires a priori knowledge of the information - contained in the Conformance Statement for the SCU, as well as how the SCU is - configured and operated. An SCU that supports both SOP Classes may well choose to - only propose one or the other during Association establishment, depending on which - Instances it actually intends to send over that particular association (although the - SCU must be capable of sending instances of the For Presentation SOP Class if the - SCP does not accept the For Processing). - - The intent of the requirement - is that if an SCU is only capable of sending the For Presentation SOP Class, any SCP - will be guaranteed to be able to receive it. Conversely, if an SCP is only capable - of receiving the For Presentation SOP Class, any SCU will be guaranteed to be able - to send it. - + The term "support" is used in this section in the sense that an SCU or SCP must be capable of sending or receiving the For Presentation SOP Class. There is no intent to imply that an SCU must always send an instance of the For Presentation SOP Class when an instance of the For Processing SOP Class is sent. + Nor is there any intent to imply that during Association establishment, that a Presentation Context for the For Presentation SOP Class has to be proposed by the initiator. However, an association acceptor may reject a For Presentation SOP Class Presentation Context if it accepts a For Processing SOP Class Presentation Context, and prefers that SOP Class, in which case it may no longer be able to "pass on" the object later as an SCU unless it is able to generate a For Presentation object. + It is not possible for an SCP to determine from proposed Presentation Contexts whether or not an SCU "supports" (is capable of sending) both For Processing and For Presentation SOP Class Instances. Such a determination requires a priori knowledge of the information contained in the Conformance Statement for the SCU, as well as how the SCU is configured and operated. An SCU that supports both SOP Classes may well choose to only propose one or the other during Association establishment, depending on which Instances it actually intends to send over that particular association (although the SCU must be capable of sending instances of the For Presentation SOP Class if the SCP does not accept the For Processing). + The intent of the requirement is that if an SCU is only capable of sending the For Presentation SOP Class, any SCP will be guaranteed to be able to receive it. Conversely, if an SCP is only capable of receiving the For Presentation SOP Class, any SCU will be guaranteed to be able to send it.
Digital Mammography X-Ray Image Storage SOP Classes - The Digital Mammography X-Ray Image Storage - - For Presentation SOP Class shall use the Digital Mammography IOD with an Enumerated Value of - FOR PRESENTATION for Presentation Intent Type (0008,0068). - - The Digital Mammography X-Ray Image Storage - - For Processing SOP Class shall use the Digital Mammography IOD with an Enumerated Value of FOR - PROCESSING for Presentation Intent Type (0008,0068). - - An SCU or SCP of the Digital Mammography - X-Ray Image Storage - For Processing SOP Class shall also support the Digital Mammography X-Ray - Image Storage - For Presentation SOP Class in the same role. - + The Digital Mammography X-Ray Image Storage - For Presentation SOP Class shall use the Digital Mammography IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068). + The Digital Mammography X-Ray Image Storage - For Processing SOP Class shall use the Digital Mammography IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068). + An SCU or SCP of the Digital Mammography X-Ray Image Storage - For Processing SOP Class shall also support the Digital Mammography X-Ray Image Storage - For Presentation SOP Class in the same role.
Digital Intra-Oral X-Ray Image Storage SOP Classes - The Digital Intra-Oral X-Ray Image Storage - - For Presentation SOP Class shall use the Digital Intra-Oral X-Ray IOD with an Enumerated Value - of FOR PRESENTATION for Presentation Intent Type (0008,0068). - - The Digital Intra-Oral X-Ray Image Storage - - For Processing SOP Class shall use the Digital Intra-Oral X-Ray IOD with an Enumerated Value - of FOR PROCESSING for Presentation Intent Type (0008,0068). - - An SCU or SCP of the Digital Intra-Oral - X-Ray Image Storage - For Processing SOP Class shall also support the Digital Intra-Oral X-Ray - Image Storage - For Presentation SOP Class in the same role. - + The Digital Intra-Oral X-Ray Image Storage - For Presentation SOP Class shall use the Digital Intra-Oral X-Ray IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068). + The Digital Intra-Oral X-Ray Image Storage - For Processing SOP Class shall use the Digital Intra-Oral X-Ray IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068). + An SCU or SCP of the Digital Intra-Oral X-Ray Image Storage - For Processing SOP Class shall also support the Digital Intra-Oral X-Ray Image Storage - For Presentation SOP Class in the same role.
Softcopy Presentation State Storage SOP Classes - See. - + See .
Structured Reporting Storage SOP Classes - The requirements of - - apply to the following SOP Classes: - + The requirements of apply to the following SOP Classes: Basic Text SR - Extensible SR, Enhanced SR, and SOP - Classes for which it is the Related General SOP Class - + Extensible SR, Enhanced SR, and SOP Classes for which it is the Related General SOP Class - Comprehensive 3D SR, Comprehensive - SR, and SOP Classes for which they are the Related General SOP Classes - + Comprehensive 3D SR, Comprehensive SR, and SOP Classes for which they are the Related General SOP Classes Mammography CAD SR @@ -7625,33 +6058,25 @@ X-Ray Radiation Dose SR - Radiopharmaceutical Radiation Dose - SR - + Radiopharmaceutical Radiation Dose SR Patient Radiation Dose SR - Enhanced X-Ray Radiation Dose SR - Storage - + Enhanced X-Ray Radiation Dose SR Storage - Spectacle Prescription Report - + Spectacle Prescription Report Colon CAD SR - Macular Grid Thickness and Volume - Report - + Macular Grid Thickness and Volume Report - Implantation Plan SR Document - + Implantation Plan SR Document Acquisition Context SR @@ -7661,513 +6086,245 @@ - - requirements do not apply to the Key Object Selection Document SOP Class. - + requirements do not apply to the Key Object Selection Document SOP Class.
Enhanced MR Image Storage and Legacy Converted Enhanced MR Image Storage SOP Class - An SCP of the Enhanced MR Image Storage or - Legacy Converted Enhanced MR Image Storage SOP Class shall also support the Grayscale Softcopy - Presentation State Storage SOP Class as an SCP. - + An SCP of the Enhanced MR Image Storage or Legacy Converted Enhanced MR Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP. - This requirement is present in order to - allow the exchange of graphical annotations created by an acquisition or conversion device. - + This requirement is present in order to allow the exchange of graphical annotations created by an acquisition or conversion device.
Enhanced CT Image Storage and Legacy Converted Enhanced CT Image Storage SOP Class - An SCP of the Enhanced CT Image Storage or - Legacy Converted Enhanced CT Image Storage SOP Class shall also support the Grayscale Softcopy - Presentation State Storage SOP Class as an SCP. - + An SCP of the Enhanced CT Image Storage or Legacy Converted Enhanced CT Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP. - This requirement is present in order to - allow the exchange of graphical annotations created by an acquisition or conversion device. - + This requirement is present in order to allow the exchange of graphical annotations created by an acquisition or conversion device.
Enhanced MR Color Image Storage SOP Class - An SCP of the Enhanced MR Color Image - Storage SOP Class shall also support the Color Softcopy Presentation State Storage SOP Class as - an SCP. - + An SCP of the Enhanced MR Color Image Storage SOP Class shall also support the Color Softcopy Presentation State Storage SOP Class as an SCP. - This requirement is present in order to - allow the exchange of graphical annotations created by an acquisition device. - + This requirement is present in order to allow the exchange of graphical annotations created by an acquisition device.
Basic Structured Display - An SCU of the Basic Structured Display - Storage SOP Class that creates SOP Instances of the SOP Class shall identify in its Conformance - Statement the Composite Storage SOP Classes and Softcopy Presentation State Storage SOP Classes - that are also supported by the SCU, and may be referenced by Basic Structured Display SOP - Instances it creates. It shall identify in its Conformance Statement the values it may use in - the Attributes Image Box Layout Type (0072,0304) and Type of Synchronization (0072,0434). - - An SCP of the Basic Structured Display - Storage SOP Class, when rendering SOP Instances of the SOP Class, shall preserve the aspect - ratio specified by the Nominal Screen Definition Sequence (0072,0102) Attributes Number of - Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106) without clipping. - + An SCU of the Basic Structured Display Storage SOP Class that creates SOP Instances of the SOP Class shall identify in its Conformance Statement the Composite Storage SOP Classes and Softcopy Presentation State Storage SOP Classes that are also supported by the SCU, and may be referenced by Basic Structured Display SOP Instances it creates. It shall identify in its Conformance Statement the values it may use in the Attributes Image Box Layout Type (0072,0304) and Type of Synchronization (0072,0434). + An SCP of the Basic Structured Display Storage SOP Class, when rendering SOP Instances of the SOP Class, shall preserve the aspect ratio specified by the Nominal Screen Definition Sequence (0072,0102) Attributes Number of Vertical Pixels (0072,0104) and Number of Horizontal Pixels (0072,0106) without clipping. - The SCP is not required to - display using the exact number of vertical and horizontal pixels. The SCP may use as - much of its display screen as it desires, while maintaining the Structured Display - aspect ratio. - + The SCP is not required to display using the exact number of vertical and horizontal pixels. The SCP may use as much of its display screen as it desires, while maintaining the Structured Display aspect ratio. - If the display screen has a - different aspect ratio, the positioning of the display on the screen is unspecified - (centered, left or right justified, top or bottom justified). - + If the display screen has a different aspect ratio, the positioning of the display on the screen is unspecified (centered, left or right justified, top or bottom justified). - An SCP of the Basic Structured Display - Storage SOP Class that is capable of rendering SOP Instances of the SOP Class shall identify in - its Conformance Statement the Composite Storage SOP Classes and Softcopy Presentation State - Storage SOP Classes that are also supported by the SCP, and will be rendered when referenced by - Basic Structured Display SOP Instances for display. It shall specify in its Conformance - Statement the user display controls and interactions for the values of Image Box Layout Type - (0072,0304) and Type of Synchronization (0072,0434) that it supports. It shall identify in its - Conformance Statement its behavior when encountering a referenced Presentation State or other - Composite Storage SOP Instance whose display it does not support, or an unsupported value of - Image Box Layout Type or Type of Synchronization; such behavior shall include at a minimum a - display to the user of the nature of the - incompatibility. - + An SCP of the Basic Structured Display Storage SOP Class that is capable of rendering SOP Instances of the SOP Class shall identify in its Conformance Statement the Composite Storage SOP Classes and Softcopy Presentation State Storage SOP Classes that are also supported by the SCP, and will be rendered when referenced by Basic Structured Display SOP Instances for display. It shall specify in its Conformance Statement the user display controls and interactions for the values of Image Box Layout Type (0072,0304) and Type of Synchronization (0072,0434) that it supports. It shall identify in its Conformance Statement its behavior when encountering a referenced Presentation State or other Composite Storage SOP Instance whose display it does not support, or an unsupported value of Image Box Layout Type or Type of Synchronization; such behavior shall include at a minimum a display to the user of the nature of the + incompatibility.
Implant Template Storage SOP Classes - See. - + See . - The requirements of this section have - been consolidated into the Non-Patient Object Storage Service Class (see). - + The requirements of this section have been consolidated into the Non-Patient Object Storage Service Class (see ).
Ophthalmic Axial Measurements Storage SOP Class - Ophthalmic axial measurements devices are - used in the preoperative assessment of every cataract surgery patient. Ophthalmic axial - measurements SOP Classes support ophthalmic axial measurements devices. - - For a device that is both an SCU and an SCP - of the Ophthalmic Axial Measurements Storage SOP Class, in addition to the behavior for the - Storage Service Class specified in, the - following additional requirements are specified for Ophthalmic Axial Measurements Storage SOP - Classes: - + Ophthalmic axial measurements devices are used in the preoperative assessment of every cataract surgery patient. Ophthalmic axial measurements SOP Classes support ophthalmic axial measurements devices. + For a device that is both an SCU and an SCP of the Ophthalmic Axial Measurements Storage SOP Class, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for Ophthalmic Axial Measurements Storage SOP Classes: - An SCP of this SOP Class shall - support Level 2 Conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition and Private - Attributes associated with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
IOL Calculation Storage SOP Class - IOL (intraocular lens) calculation is used - in the preoperative assessment of every cataract surgery patient. IOL Calculation SOP Classes - support IOL calculation software, which may be located either on ophthalmic axial measurement - devices or on a separate computer. - - For a device that is both an SCU and an SCP - of the IOL Calculation Storage SOP Class, in addition to the behavior for the Storage Service - Class specified in, the following - additional requirements are specified for IOL Calculation Storage SOP Classes: - + IOL (intraocular lens) calculation is used in the preoperative assessment of every cataract surgery patient. IOL Calculation SOP Classes support IOL calculation software, which may be located either on ophthalmic axial measurement devices or on a separate computer. + For a device that is both an SCU and an SCP of the IOL Calculation Storage SOP Class, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for IOL Calculation Storage SOP Classes: - An SCP of this SOP Class shall - support Level 2 Conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition and Private - Attributes associated with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
Intravascular OCT Image Storage SOP Classes - The Intravascular OCT Image Storage - For - Presentation SOP Class shall use the IVOCT IOD with an Enumerated Value of FOR PRESENTATION for - Presentation Intent Type (0008,0068). - - The Intravascular OCT Image Storage - For - Processing SOP Class shall use the IVOCT IOD with an Enumerated Value of FOR PROCESSING for - Presentation Intent Type (0008,0068). - - An SCU or SCP of the Intravascular OCT - Image Storage - For Processing SOP Class shall also support the Intravascular OCT Image Storage - - For Presentation SOP Class in the same role. - + The Intravascular OCT Image Storage - For Presentation SOP Class shall use the IVOCT IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068). + The Intravascular OCT Image Storage - For Processing SOP Class shall use the IVOCT IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068). + An SCU or SCP of the Intravascular OCT Image Storage - For Processing SOP Class shall also support the Intravascular OCT Image Storage - For Presentation SOP Class in the same role. - The intent of this requirement - is to ensure a useful level of interoperability by avoiding the situation where an - SCU might support only the Intravascular OCT Image Storage - For Processing SOP - Class and an SCP only the Intravascular OCT Image Storage - For Presentation SOP - Class, or vice versa. The burden is therefore to support the Intravascular OCT Image - Storage - For Presentation SOP Class as a "baseline". - + The intent of this requirement is to ensure a useful level of interoperability by avoiding the situation where an SCU might support only the Intravascular OCT Image Storage - For Processing SOP Class and an SCP only the Intravascular OCT Image Storage - For Presentation SOP Class, or vice versa. The burden is therefore to support the Intravascular OCT Image Storage - For Presentation SOP Class as a "baseline". - The term "support" is used in - this section in the sense that an SCU or SCP must be capable of sending or receiving - the For Presentation SOP Class. There is no intent to imply that an SCU must always - send an instance of the For Presentation SOP Class when an instance of the For - Processing SOP Class is sent. - - Nor is there any intent to - imply that during Association establishment, that a Presentation Context for the For - Presentation SOP Class has to be proposed by the initiator. However, an association - acceptor may reject a For Presentation SOP Class Presentation Context if it accepts - a For Processing SOP Class Presentation Context, and prefers that SOP Class, in - which case it may no longer be able to "pass on" the object later as an SCU unless - it is able to generate a For Presentation object. - - It is not possible for an SCP - to determine from proposed Presentation Contexts whether or not an SCU "supports" - (is capable of sending) both For Processing and For Presentation SOP Class - Instances. Such a determination requires a priori knowledge of the information - contained in the Conformance Statement for the SCU, as well as how the SCU is - configured and operated. An SCU that supports both SOP Classes may well choose to - only propose one or the other during Association establishment, depending on which - Instances it actually intends to send over that particular association (although the - SCU must be capable of sending instances of the For Presentation SOP Class if the - SCP does not accept the For Processing). - - The intent of the requirement - is that if an SCU is only capable of sending the For Presentation SOP Class, any SCP - will be guaranteed to be able to receive it. Conversely, if an SCP is only capable - of receiving the For Presentation SOP Class, any SCU will be guaranteed to be able - to send it. - + The term "support" is used in this section in the sense that an SCU or SCP must be capable of sending or receiving the For Presentation SOP Class. There is no intent to imply that an SCU must always send an instance of the For Presentation SOP Class when an instance of the For Processing SOP Class is sent. + Nor is there any intent to imply that during Association establishment, that a Presentation Context for the For Presentation SOP Class has to be proposed by the initiator. However, an association acceptor may reject a For Presentation SOP Class Presentation Context if it accepts a For Processing SOP Class Presentation Context, and prefers that SOP Class, in which case it may no longer be able to "pass on" the object later as an SCU unless it is able to generate a For Presentation object. + It is not possible for an SCP to determine from proposed Presentation Contexts whether or not an SCU "supports" (is capable of sending) both For Processing and For Presentation SOP Class Instances. Such a determination requires a priori knowledge of the information contained in the Conformance Statement for the SCU, as well as how the SCU is configured and operated. An SCU that supports both SOP Classes may well choose to only propose one or the other during Association establishment, depending on which Instances it actually intends to send over that particular association (although the SCU must be capable of sending instances of the For Presentation SOP Class if the SCP does not accept the For Processing). + The intent of the requirement is that if an SCU is only capable of sending the For Presentation SOP Class, any SCP will be guaranteed to be able to receive it. Conversely, if an SCP is only capable of receiving the For Presentation SOP Class, any SCU will be guaranteed to be able to send it.
Ophthalmic Thickness Map Storage SOP Class - The Ophthalmic Thickness Map SOP Class - encodes a topographic representation of the thickness/height measurements of the posterior eye. - - For a device that is both an SCU and an SCP - of the Ophthalmic Thickness Map Storage SOP Class, in addition to the behavior for the Storage - Service Class specified in, the following - additional requirements are specified for Ophthalmic Thickness Map Storage SOP Classes: - + The Ophthalmic Thickness Map SOP Class encodes a topographic representation of the thickness/height measurements of the posterior eye. + For a device that is both an SCU and an SCP of the Ophthalmic Thickness Map Storage SOP Class, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for Ophthalmic Thickness Map Storage SOP Classes: - An SCP of this SOP Class shall - support Level 2 Conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition and Private - Attributes associated with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
Enhanced PET Image Storage and Legacy Converted Enhanced PET Image Storage SOP Class - An SCP of the Enhanced PET Image Storage or - Legacy Converted Enhanced PET Image Storage SOP Class shall also support the Grayscale Softcopy - Presentation State Storage SOP Class as an SCP. - + An SCP of the Enhanced PET Image Storage or Legacy Converted Enhanced PET Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP. - This requirement is present in order to - allow the exchange of graphical annotations created by an acquisition or conversion device. - + This requirement is present in order to allow the exchange of graphical annotations created by an acquisition or conversion device.
Enhanced PET Image Storage SOP Classes - An SCP of the Enhanced PET Image Storage - SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an - SCP. - + An SCP of the Enhanced PET Image Storage SOP Class shall also support the Grayscale Softcopy Presentation State Storage SOP Class as an SCP. - This requirement is present in order to - allow the exchange of graphical annotations created by an acquisition device. - + This requirement is present in order to allow the exchange of graphical annotations created by an acquisition device.
Corneal Topography Map Storage SOP Class - The Corneal Topography Map SOP Class - encodes a topographic representation of the curvature and/or elevation measurements of corneal - anterior and posterior surfaces (e.g., maps that display corneal curvatures, corneal elevations, - and corneal power, etc.). - - An SCP of the Corneal Topography Map - Storage SOP Class that renders SOP Instances of this SOP Class - shall apply the image transformations (i.e., Palette Color LUT) and the Real World Value LUT to - display the annotated color scale. - The annotated color scale shall conform to the "ISO Standard 19980 - Ophthalmic instruments - - Corneal topographers, second edition, section B.4 Standardized - Colour - Scale." - - - An SCP may display a Corneal Topography Map - superimposed on the image referenced in the Source Image Sequence (0008,2112). - When displaying such, Corneal Topography Map pixels with the value of the Pixel Padding Value - (0028,0120) Attribute shall be rendered transparently so that the corresponding underlying image - pixels are visible. - For the display of the annotated color scale, the SCP shall use only those values for which a - mapping is defined in the Real World Value Mapping Sequence (0040,9096). - The colors that shall be used for both the map and the scale are defined by the Attributes of - the Palette Color Lookup Table. - + The Corneal Topography Map SOP Class encodes a topographic representation of the curvature and/or elevation measurements of corneal anterior and posterior surfaces (e.g., maps that display corneal curvatures, corneal elevations, and corneal power, etc.). + An SCP of the Corneal Topography Map Storage SOP Class that renders SOP Instances of this SOP Class + shall apply the image transformations (i.e., Palette Color LUT) and the Real World Value LUT to display the annotated color scale. + The annotated color scale shall conform to the "ISO Standard 19980 - Ophthalmic instruments - Corneal topographers, second edition, section B.4 Standardized Colour Scale." + + An SCP may display a Corneal Topography Map superimposed on the image referenced in the Source Image Sequence (0008,2112). + When displaying such, Corneal Topography Map pixels with the value of the Pixel Padding Value (0028,0120) Attribute shall be rendered transparently so that the corresponding underlying image pixels are visible. + For the display of the annotated color scale, the SCP shall use only those values for which a mapping is defined in the Real World Value Mapping Sequence (0040,9096). + The colors that shall be used for both the map and the scale are defined by the Attributes of the Palette Color Lookup Table. - The size of the Corneal - Topography Map is typically the same as that of the underlying image on which it is - superimposed, - i.e., the Rows (0028,0010) and Columns (0028,0011) Attributes have the same Values, - and the orientation and origin are the same. - In this case, there is no need to specify a Spatial Registration. - + The size of the Corneal Topography Map is typically the same as that of the underlying image on which it is superimposed, + i.e., the Rows (0028,0010) and Columns (0028,0011) Attributes have the same Values, and the orientation and origin are the same. + In this case, there is no need to specify a Spatial Registration. - A Blending Presentation State - provides additional capabilities for superimposing images, but these are typically - not required for this use case, - i.e., for rendering a Corneal Topography Map on a source image. - + A Blending Presentation State provides additional capabilities for superimposing images, but these are typically not required for this use case, + i.e., for rendering a Corneal Topography Map on a source image. - Examples for the rendering of - superimposed images and the annotated color scale can be found in - - and - . - + Examples for the rendering of superimposed images and the annotated color scale can be found in + and + . - For a device that is both an SCU and an SCP - of the Corneal Topography Map Storage SOP Class, in addition to the behavior for the Storage - Service Class specified in, the following - additional requirements are specified for Corneal Topography Map Storage SOP Classes: - + For a device that is both an SCU and an SCP of the Corneal Topography Map Storage SOP Class, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for Corneal Topography Map Storage SOP Classes: - An SCP of this SOP Class shall - support Level 2 Conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition and Private - Attributes associated with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
Breast Projection X-Ray Image Storage SOP Classes - The Breast Projection X-Ray Image Storage - - For Presentation SOP Class shall use the Breast Projection X-Ray Image IOD with an Enumerated - Value of FOR PRESENTATION for Presentation Intent Type (0008,0068). - - The Breast Projection X-Ray Image Storage - - For Processing SOP Class shall use the Breast Projection X-Ray Image IOD with an Enumerated - Value of FOR PROCESSING for Presentation Intent Type (0008,0068). - - An SCU or SCP of the Breast Projection - X-Ray Image Storage - For Processing SOP Class shall also support the Breast Projection X-Ray - Image Storage - For Presentation SOP Class in the same role. - + The Breast Projection X-Ray Image Storage - For Presentation SOP Class shall use the Breast Projection X-Ray Image IOD with an Enumerated Value of FOR PRESENTATION for Presentation Intent Type (0008,0068). + The Breast Projection X-Ray Image Storage - For Processing SOP Class shall use the Breast Projection X-Ray Image IOD with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,0068). + An SCU or SCP of the Breast Projection X-Ray Image Storage - For Processing SOP Class shall also support the Breast Projection X-Ray Image Storage - For Presentation SOP Class in the same role.
Planar MPR Volumetric Presentation State Storage SOP Classes - The requirements of - - apply to the following SOP Classes: - + The requirements of apply to the following SOP Classes: - Grayscale Planar MPR Volumetric - Presentation State Storage - + Grayscale Planar MPR Volumetric Presentation State Storage - Compositing Planar MPR Volumetric - Presentation State Storage - + Compositing Planar MPR Volumetric Presentation State Storage - The Grayscale Planar MPR Volumetric - Presentation State Storage SOP Class shall use the - - with an Enumerated Value of MONOCHROME for Pixel Presentation (0008,9205) and shall have only a - single item in the Volumetric Presentation State Input Sequence (0070,1201). - - The Compositing Planar MPR Volumetric - Presentation State Storage SOP Class shall use the - - with an Enumerated Value of TRUE COLOR for Pixel Presentation (0008,9205). - + The Grayscale Planar MPR Volumetric Presentation State Storage SOP Class shall use the with an Enumerated Value of MONOCHROME for Pixel Presentation (0008,9205) and shall have only a single item in the Volumetric Presentation State Input Sequence (0070,1201). + The Compositing Planar MPR Volumetric Presentation State Storage SOP Class shall use the with an Enumerated Value of TRUE COLOR for Pixel Presentation (0008,9205).
Content Assessment Results Storage SOP Classes - An SCU of the Content Assessment Results - Storage SOP Class that creates SOP Instances of the SOP Class shall identify in its Conformance - Statement the criteria for setting the Observation Significance (0082,0008). - + An SCU of the Content Assessment Results Storage SOP Class that creates SOP Instances of the SOP Class shall identify in its Conformance Statement the criteria for setting the Observation Significance (0082,0008).
CT and XA Performed Procedure Protocol Storage SOP Classes - The CT and XA Performed Procedure Protocol - Storage SOP Classes encode the acquisition, reconstruction and storage protocol parameter values - used during a specific performed procedure, and related details. - - For a device that is both an SCU and an SCP - of the CT or XA Performed Procedure Protocol Storage SOP Class, in addition to the behavior for - the Storage Service Class specified in, - the following additional requirements are specified for CT and XA Performed Procedure Protocol - Storage SOP Classes: - + The CT and XA Performed Procedure Protocol Storage SOP Classes encode the acquisition, reconstruction and storage protocol parameter values used during a specific performed procedure, and related details. + For a device that is both an SCU and an SCP of the CT or XA Performed Procedure Protocol Storage SOP Class, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for CT and XA Performed Procedure Protocol Storage SOP Classes: - An SCP of this SOP Class shall - support Level 2 Conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition and Private - Attributes associated with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
Raw Data Storage SOP Class - For a device that is both an SCU and an SCP - of the Raw Data Storage SOP Class, in addition to the behavior for the Storage Service Class - specified in, the following additional - requirements are specified for the Raw Data Storage SOP Class: - + For a device that is both an SCU and an SCP of the Raw Data Storage SOP Class, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for the Raw Data Storage SOP Class: - An SCP of this SOP Class shall - support Level 2 Conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition and Private - Attributes associated with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
Enhanced Multi-Frame Image SOP Classes - An SCP of any of the Enhanced Multi-Frame - Image SOP Classes that makes SOP Instances available through the Enhanced Multi-Frame Image - Conversion Extended Negotiation of the Query/Retrieve Service Class (see) shall provide Level 2 - (Full) Storage SCP Conformance. - + An SCP of any of the Enhanced Multi-Frame Image SOP Classes that makes SOP Instances available through the Enhanced Multi-Frame Image Conversion Extended Negotiation of the Query/Retrieve Service Class (see ) shall support Storage Level 2 (Full). - Effective use of the Image Conversion - option requires the storage of Type 3 Attributes. - + Effective use of the Image Conversion option requires the storage of Type 3 Attributes.
Volume Rendering Volumetric Presentation State Storage SOP Classes - The requirements of - - apply to the following SOP Classes: - + The requirements of apply to the following SOP Classes: - Volume Rendering Volumetric - Presentation State SOP Class - + Volume Rendering Volumetric Presentation State SOP Class - Segmented Volume Rendering - Volumetric Presentation State SOP Class - + Segmented Volume Rendering Volumetric Presentation State SOP Class - Multiple Volume Rendering - Volumetric Presentation State SOP Class - + Multiple Volume Rendering Volumetric Presentation State SOP Class - The Volume Rendering Volumetric - Presentation State Storage SOP Class shall use the - - and include a single item in Volumetric Presentation State Input Sequence (0070,1201) and a - single item in Volume Stream Sequence (0070,1A08). Also, the value of Crop (0070,1204) shall be - NO. - - The Segmented Volume Rendering Volumetric - Presentation State Storage SOP Class shall use the - - and include a single item in Volume Stream Sequence (0070,1A08). - - The Multiple Volume Rendering Volumetric - Presentation State Storage SOP Class shall use the - - and include two or more items in Volume Stream Sequence (0070,1A08). - + The Volume Rendering Volumetric Presentation State Storage SOP Class shall use the and include a single item in Volumetric Presentation State Input Sequence (0070,1201) and a single item in Volume Stream Sequence (0070,1A08). Also, the value of Crop (0070,1204) shall be NO. + The Segmented Volume Rendering Volumetric Presentation State Storage SOP Class shall use the and include a single item in Volume Stream Sequence (0070,1A08). + The Multiple Volume Rendering Volumetric Presentation State Storage SOP Class shall use the and include two or more items in Volume Stream Sequence (0070,1A08).
Retired Standard SOP Classes - The SOP Classes in - - were defined in previous versions of the DICOM Standard. They are now retired and have been replaced by - new Standard SOP Classes shown in. - + The SOP Classes in were defined in previous versions of the DICOM Standard. They are now retired and have been replaced by new Standard SOP Classes shown in . - Usage of the retired SOP Classes is permitted - by DICOM. However, new implementations are strongly encouraged to implement the newer SOP Classes. - + Usage of the retired SOP Classes is permitted by DICOM. However, new implementations are strongly encouraged to implement the newer SOP Classes. @@ -8184,8 +6341,7 @@
Retired Standard SOP Classes
- Nuclear Medicine Image Storage - + Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.5 @@ -8201,9 +6357,7 @@
- Ultrasound Multi-frame Image - Storage - + Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3 @@ -8211,9 +6365,7 @@
- X-Ray Angiographic Bi-plane Image - Storage - + X-Ray Angiographic Bi-plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3 @@ -8229,78 +6381,38 @@ Overview
Scope - The Query/Retrieve Service Class defines an - application-level class-of-service that facilitates the simple management of Composite Object - Instances in a manner functionally similar to ACR-NEMA 300-1988. The types of queries that are - allowed are not complex. This Service Class is not intended to provide a comprehensive generalized - database query mechanism such as SQL. Instead, the Query/Retrieve Service Class is focused towards - basic Composite Object Instance information queries using a small set of common Key Attributes. - - In addition, the Query/Retrieve Service Class - provides the ability to retrieve/transfer a well-identified set of Composite Object Instances. The - retrieve/transfer capability allows a DICOM AE to retrieve Composite Object Instances from a remote - DICOM AE or request the remote DICOM AE to initiate a transfer of Composite Object Instances to - another DICOM AE. - + The Query/Retrieve Service Class defines an application-level class-of-service that facilitates the simple management of Composite Object Instances in a manner functionally similar to ACR-NEMA 300-1988. The types of queries that are allowed are not complex. This Service Class is not intended to provide a comprehensive generalized database query mechanism such as SQL. Instead, the Query/Retrieve Service Class is focused towards basic Composite Object Instance information queries using a small set of common Key Attributes. + In addition, the Query/Retrieve Service Class provides the ability to retrieve/transfer a well-identified set of Composite Object Instances. The retrieve/transfer capability allows a DICOM AE to retrieve Composite Object Instances from a remote DICOM AE or request the remote DICOM AE to initiate a transfer of Composite Object Instances to another DICOM AE. - Functional similarity to ACR-NEMA 300-1988 - facilitates the migration to DICOM. - + Functional similarity to ACR-NEMA 300-1988 facilitates the migration to DICOM. - An Enhanced Multi-Frame Image Conversion - Extended Negotiation option allows the Query/Retrieve Service Class to access Classic single-frame - images that have been converted to Enhanced multi-frame images, or vice-versa. This is achieved by - providing alternative "views" of studies, such that: - + An Enhanced Multi-Frame Image Conversion Extended Negotiation option allows the Query/Retrieve Service Class to access Classic single-frame images that have been converted to Enhanced multi-frame images, or vice-versa. This is achieved by providing alternative "views" of studies, such that: - the default view provides the images in - the form they were received, - + the default view provides the images in the form they were received, - a Classic single-frame "view" provides - images as Classic single frame (that were received that way or have been converted from - Enhanced multi-frame), - + a Classic single-frame "view" provides images as Classic single frame (that were received that way or have been converted from Enhanced multi-frame), - an Enhanced multi-frame "view" provides - images as Enhanced multi-frame (that were received that way or have been converted to - Enhanced multi-frame). - + an Enhanced multi-frame "view" provides images as Enhanced multi-frame (that were received that way or have been converted to Enhanced multi-frame). - A query or retrieval above the IMAGE level does - not show or return duplicate information (two sets of images). The SCU may request the default, - enhanced multi-frame or Classic single frame view. For each view, referential integrity is required - to be consistent within the scope of the Patient and that view; i.e., references to UIDs will be - converted in all Instances, not only within converted images. - + A query or retrieval above the IMAGE level does not show or return duplicate information (two sets of images). The SCU may request the default, enhanced multi-frame or Classic single frame view. For each view, referential integrity is required to be consistent within the scope of the Patient and that view; i.e., references to UIDs will be converted in all Instances, not only within converted images. - The Classic single-frame view is - not intended as an alternative to the Frame Level Retrieve SOP Classes defined in. Enhanced Image Storage SOP - Classes and Frame Level Retrieve SOP Classes should be used together since they support - a unified view of the relationships between instances through a common set of UIDs. - + The Classic single-frame view is not intended as an alternative to the Frame Level Retrieve SOP Classes defined in . Enhanced Image Storage SOP Classes and Frame Level Retrieve SOP Classes should be used together since they support a unified view of the relationships between instances through a common set of UIDs. - In the Enhanced view, Instances - that have no Enhanced equivalent will be returned in their original form but with - referential integrity related changes. - + In the Enhanced view, Instances that have no Enhanced equivalent will be returned in their original form but with referential integrity related changes.
Conventions - The following conventions are used to define - the types of keys used in Query/Retrieve Information Models. - + The following conventions are used to define the types of keys used in Query/Retrieve Information Models. @@ -8343,168 +6455,72 @@
Query/Retrieve Information Model - In order to serve as an SCP of the - Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of - stored Composite Object Instances. This information is organized into a well defined Query/Retrieve - Information Model. The Query/Retrieve Information Model shall be a standard Query/Retrieve - Information Model, as defined in this Annex of the DICOM Standard. - - Queries and Retrievals are implemented against - well defined Information Models. A specific SOP Class of the Query/Retrieve Service Class consists - of an Information Model Definition and a DIMSE-C Service Group. In this Service Class, the - Information Model plays a role similar to an Information Object Definition (IOD) of most other DICOM - Service Classes. - + In order to serve as an SCP of the Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of stored Composite Object Instances. This information is organized into a well defined Query/Retrieve Information Model. The Query/Retrieve Information Model shall be a standard Query/Retrieve Information Model, as defined in this Annex of the DICOM Standard. + Queries and Retrievals are implemented against well defined Information Models. A specific SOP Class of the Query/Retrieve Service Class consists of an Information Model Definition and a DIMSE-C Service Group. In this Service Class, the Information Model plays a role similar to an Information Object Definition (IOD) of most other DICOM Service Classes.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP - Classes of the Query/Retrieve Service Class are implemented using the DIMSE-C C-FIND, C-MOVE, and - C-GET services as defined in. - - Both a baseline and extended behavior is - defined for the DIMSE-C C-FIND, C-MOVE, and C-GET services. Baseline behavior specifies a minimum - level of conformance for all implementations to facilitate interoperability. Extended behavior - enhances the baseline behavior to provide additional features that may be negotiated independently - at Association establishment time. - - The following descriptions of the DIMSE-C - C-FIND, C-MOVE, and C-GET services provide a brief overview of the SCU/SCP semantics: - + Two peer DICOM AEs implement a SOP Class of the Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Query/Retrieve Service Class are implemented using the DIMSE-C C-FIND, C-MOVE, and C-GET services as defined in . + Both a baseline and extended behavior is defined for the DIMSE-C C-FIND, C-MOVE, and C-GET services. Baseline behavior specifies a minimum level of conformance for all implementations to facilitate interoperability. Extended behavior enhances the baseline behavior to provide additional features that may be negotiated independently at Association establishment time. + The following descriptions of the DIMSE-C C-FIND, C-MOVE, and C-GET services provide a brief overview of the SCU/SCP semantics: - A C-FIND service conveys the following - semantics: - + A C-FIND service conveys the following semantics: - The SCU requests that the SCP - perform a match of all the keys specified in the Identifier of the request, against - the information it possesses, to the level (E.g. Patient, Study, Series, or - Composite Object Instance) specified in the request. - + The SCU requests that the SCP perform a match of all the keys specified in the Identifier of the request, against the information it possesses, to the level (E.g. Patient, Study, Series, or Composite Object Instance) specified in the request. - In this Annex, the term - "Identifier" refers to the Identifier service parameter of the C-FIND, C-MOVE, - or C-GET service as defined in. - + In this Annex, the term "Identifier" refers to the Identifier service parameter of the C-FIND, C-MOVE, or C-GET service as defined in . - The SCP generates a C-FIND - response for each match with an Identifier containing the values of all key fields - and all known Attributes requested. All such responses will contain a status of - Pending. A status of Pending indicates that the process of matching is not complete. - + The SCP generates a C-FIND response for each match with an Identifier containing the values of all key fields and all known Attributes requested. All such responses will contain a status of Pending. A status of Pending indicates that the process of matching is not complete. - When the process of matching is - complete a C-FIND response is sent with a status of Success and no Identifier. - + When the process of matching is complete a C-FIND response is sent with a status of Success and no Identifier. - A Refused or Failed response to - a C-FIND request indicates that the SCP is unable to process the request. - + A Refused or Failed response to a C-FIND request indicates that the SCP is unable to process the request. - The SCU may cancel the C-FIND - service by issuing a C-FIND-CANCEL request at any time during the processing of the - C-FIND service. The SCP will interrupt all matching and return a status of Canceled. - + The SCU may cancel the C-FIND service by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND service. The SCP will interrupt all matching and return a status of Canceled. - A C-MOVE service conveys the following - semantics: - + A C-MOVE service conveys the following semantics: - The SCU supplies Unique Key - values to identify an entity at the level of the retrieval. The SCP of the C-MOVE - initiates C-STORE sub-operations for the corresponding storage SOP Instances - identified by Unique Key values. These C-STORE sub-operations occur on a different - Association than the C-MOVE service. The SCP role of the Query/Retrieve SOP Class - and the SCU role of the Storage SOP Class may be performed by different applications - that may or may not reside on the same system. Initiation mechanism of C-STORE - sub-operations is outside of the scope of DICOM Standard. - + The SCU supplies Unique Key values to identify an entity at the level of the retrieval. The SCP of the C-MOVE initiates C-STORE sub-operations for the corresponding storage SOP Instances identified by Unique Key values. These C-STORE sub-operations occur on a different Association than the C-MOVE service. The SCP role of the Query/Retrieve SOP Class and the SCU role of the Storage SOP Class may be performed by different applications that may or may not reside on the same system. Initiation mechanism of C-STORE sub-operations is outside of the scope of DICOM Standard. - This does not imply that - they use the same AE Title. See - - and - - for the requirements to the C-MOVE SCP conformance. - + This does not imply that they use the same AE Title. See and for the requirements to the C-MOVE SCP conformance. - The SCP may optionally generate - responses to the C-MOVE with status equal to Pending during the processing of the - C-STORE sub-operations. These C-MOVE responses indicate the number of Remaining - C-STORE sub-operations and the number of C-STORE sub-operations returning the status - of Success, Warning, and Failed. - + The SCP may optionally generate responses to the C-MOVE with status equal to Pending during the processing of the C-STORE sub-operations. These C-MOVE responses indicate the number of Remaining C-STORE sub-operations and the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. - When the number of Remaining - C-STORE sub-operations reaches zero, the SCP generates a final response with a - status equal to Success, Warning, Failed, or Refused. This response may indicate the - number of C-STORE sub-operations returning the status of Success, Warning, and - Failed. If the status of a C-STORE sub-operation was Failed a UID List will be - returned. - + When the number of Remaining C-STORE sub-operations reaches zero, the SCP generates a final response with a status equal to Success, Warning, Failed, or Refused. This response may indicate the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. If the status of a C-STORE sub-operation was Failed a UID List will be returned. - The SCU may cancel the C-MOVE - service by issuing a C-MOVE-CANCEL request at any time during the processing of the - C-MOVE. The SCP terminates all incomplete C-STORE sub-operations and returns a - status of Canceled. - + The SCU may cancel the C-MOVE service by issuing a C-MOVE-CANCEL request at any time during the processing of the C-MOVE. The SCP terminates all incomplete C-STORE sub-operations and returns a status of Canceled. - A C-GET service conveys the following - semantics: - + A C-GET service conveys the following semantics: - The SCU supplies Unique Key - values to identify an entity at the level of the retrieval. The SCP generates - C-STORE sub-operations for the corresponding storage SOP Instances identified by the - Unique Key values. These C-STORE sub-operations occur on the same Association as the - C-GET service and the SCU/SCP roles will be reversed for the C-STORE. - + The SCU supplies Unique Key values to identify an entity at the level of the retrieval. The SCP generates C-STORE sub-operations for the corresponding storage SOP Instances identified by the Unique Key values. These C-STORE sub-operations occur on the same Association as the C-GET service and the SCU/SCP roles will be reversed for the C-STORE. - The SCP may optionally generate - responses to the C-GET with status equal to Pending during the processing of the - C-STORE sub-operations. These C-GET responses indicate the number of Remaining - C-STORE sub-operations and the number of C-STORE sub-operations returning the status - of Success, Warning, and Failed. - + The SCP may optionally generate responses to the C-GET with status equal to Pending during the processing of the C-STORE sub-operations. These C-GET responses indicate the number of Remaining C-STORE sub-operations and the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. - When the number of Remaining - C-STORE sub-operations reaches zero, the SCP generates a final response with a - status equal to Success, Warning, Failed, or Refused. This response may indicate the - number of C-STORE sub-operations returning the status of Success, Warning, and - Failed. If the status of a C-STORE sub-operation was Failed a UID List will be - returned. - + When the number of Remaining C-STORE sub-operations reaches zero, the SCP generates a final response with a status equal to Success, Warning, Failed, or Refused. This response may indicate the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. If the status of a C-STORE sub-operation was Failed a UID List will be returned. - The SCU may cancel the C-GET - service by issuing a C-GET-CANCEL request at any time during the processing of the - C-GET. The SCP terminates all incomplete C-STORE sub-operations and returns a status - of Canceled. - + The SCU may cancel the C-GET service by issuing a C-GET-CANCEL request at any time during the processing of the C-GET. The SCP terminates all incomplete C-STORE sub-operations and returns a status of Canceled. @@ -8513,20 +6529,11 @@
Query/Retrieve Information Model Definition - The Query/Retrieve Information Model is identified - by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an - Information Model and a DIMSE-C Service Group. - + The Query/Retrieve Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. - This SOP Class identifies the class of the - Query/Retrieve Information Model (i.e., not the SOP Class of the stored SOP Instances for which the - SCP has information). - + This SOP Class identifies the class of the Query/Retrieve Information Model (i.e., not the SOP Class of the stored SOP Instances for which the SCP has information). - Information Model Definitions for Standard SOP - Classes of the Query/Retrieve Service Class are defined in this Annex. A Query/Retrieve Information - Model Definition contains: - + Information Model Definitions for Standard SOP Classes of the Query/Retrieve Service Class are defined in this Annex. A Query/Retrieve Information Model Definition contains: Entity-Relationship Model Definition @@ -8537,121 +6544,57 @@
Entity-Relationship Model Definition - For any Query/Retrieve Information Model, an - Entity-Relationship Model defines a hierarchy of entities, with Attributes defined for each level in - the hierarchy (e.g., Patient, Study, Series, Composite Object Instance). - + For any Query/Retrieve Information Model, an Entity-Relationship Model defines a hierarchy of entities, with Attributes defined for each level in the hierarchy (e.g., Patient, Study, Series, Composite Object Instance).
Attributes Definition - Attributes shall be defined at each level in - the Entity-Relationship Model. An Identifier in a C-FIND, C-MOVE, or C-GET command shall contain - values to be matched against the Attributes of the Entities in a Query/Retrieve Information Model. - For any query, the set of entities for which Attributes are returned, shall be determined by the set - of Key Attributes specified in the Identifier that have corresponding matches on entities managed by - the SCP associated with the query. - + Attributes shall be defined at each level in the Entity-Relationship Model. An Identifier in a C-FIND, C-MOVE, or C-GET command shall contain values to be matched against the Attributes of the Entities in a Query/Retrieve Information Model. For any query, the set of entities for which Attributes are returned, shall be determined by the set of Key Attributes specified in the Identifier that have corresponding matches on entities managed by the SCP associated with the query.
Attribute Types - All Attributes of entities in a - Query/Retrieve Information Model shall be either a Unique Key, Required Key, or Optional Key. - The term Key Attributes refers to Unique, Required, and Optional Key Attributes. - + All Attributes of entities in a Query/Retrieve Information Model shall be either a Unique Key, Required Key, or Optional Key. The term Key Attributes refers to Unique, Required, and Optional Key Attributes.
Unique Keys - At each level in the - Entity-Relationship Model, one Attribute shall be defined as a Unique Key. A single value in - a Unique Key Attribute shall uniquely identify a single entity at a given level. That is, - two entities at the same level may not have the same Unique Key value. - - C-FIND, C-MOVE, and C-GET SCPs shall - support existence and matching of all Unique Keys defined by a Query/Retrieve Information - Model. All entities managed by C-FIND, C-MOVE, and C-GET SCPs shall have a specific non-zero - length Unique Key value. - - Unique Keys may be contained in the - Identifier of a C-FIND request. Unique Keys shall be contained in the Identifier of C-MOVE - and C-GET requests. - + At each level in the Entity-Relationship Model, one Attribute shall be defined as a Unique Key. A single value in a Unique Key Attribute shall uniquely identify a single entity at a given level. That is, two entities at the same level may not have the same Unique Key value. + C-FIND, C-MOVE, and C-GET SCPs shall support existence and matching of all Unique Keys defined by a Query/Retrieve Information Model. All entities managed by C-FIND, C-MOVE, and C-GET SCPs shall have a specific non-zero length Unique Key value. + Unique Keys may be contained in the Identifier of a C-FIND request. Unique Keys shall be contained in the Identifier of C-MOVE and C-GET requests.
Required Keys - At each level in the - Entity-Relationship Model, a set of Attributes shall be defined as Required Keys. Required - Keys imply the SCP of a C-FIND shall support matching based on a value contained in a - Required Key of the C-FIND request. Multiple entities may have the same value for Required - Keys. That is, a distinct value in a Required Key shall not necessarily identify a single - entity at the level of the key. - - C-FIND SCPs shall support existence and - matching of all Required Keys defined by a Query/Retrieve Information Model. If a C-FIND SCP - manages an entity with a Required Key of zero length, the value is considered unknown and - all matching against the zero length Required Key shall be considered a successful match. - - Required Keys may be contained in the - Identifier of a C-FIND request. Required Keys shall not be contained in the Identifier of - C-MOVE and C-GET requests. - + At each level in the Entity-Relationship Model, a set of Attributes shall be defined as Required Keys. Required Keys imply the SCP of a C-FIND shall support matching based on a value contained in a Required Key of the C-FIND request. Multiple entities may have the same value for Required Keys. That is, a distinct value in a Required Key shall not necessarily identify a single entity at the level of the key. + C-FIND SCPs shall support existence and matching of all Required Keys defined by a Query/Retrieve Information Model. If a C-FIND SCP manages an entity with a Required Key of zero length, the value is considered unknown and all matching against the zero length Required Key shall be considered a successful match. + Required Keys may be contained in the Identifier of a C-FIND request. Required Keys shall not be contained in the Identifier of C-MOVE and C-GET requests.
Optional Keys - At each level in the - Entity-Relationship Model, a set of Attributes shall be defined as Optional Keys. - - Optional Keys contained in the - Identifier of a C-FIND request may have three different types of behavior depending on - support for existence and/or matching by the C-FIND SCP. If the C-FIND SCP: - + At each level in the Entity-Relationship Model, a set of Attributes shall be defined as Optional Keys. + Optional Keys contained in the Identifier of a C-FIND request may have three different types of behavior depending on support for existence and/or matching by the C-FIND SCP. If the C-FIND SCP: - does not support the existence - of the Optional Key, then the Attribute shall not be returned in C-FIND responses - + does not support the existence of the Optional Key, then the Attribute shall not be returned in C-FIND responses - supports the existence of the - Optional Key but does not support matching on the Optional Key, then the Optional - Key shall be processed in the same manner as a zero length Required Key. That is, - the value specified to be matched for the Optional Key is ignored but a value may be - returned by the SCP for this Optional Key. - + supports the existence of the Optional Key but does not support matching on the Optional Key, then the Optional Key shall be processed in the same manner as a zero length Required Key. That is, the value specified to be matched for the Optional Key is ignored but a value may be returned by the SCP for this Optional Key. - supports the existence and - matching of the Optional Key, then the Optional Key shall be processed in the same - manner as a Required Key. - + supports the existence and matching of the Optional Key, then the Optional Key shall be processed in the same manner as a Required Key. - C-FIND SCU may not assume - an Optional Key with non-zero length will be processed in the same manner as a - Required Key. The Conformance Statement of the C-FIND SCP shall list the - Optional Keys that are supported. - + C-FIND SCU may not assume an Optional Key with non-zero length will be processed in the same manner as a Required Key. The Conformance Statement of the C-FIND SCP shall list the Optional Keys that are supported. - Optional Keys are - differentiated from Required Keys in that Optional Keys may or may not be - supported for existence and/or matching by C-FIND SCPs. Whereas, Required Keys - must always be supported by C-FIND SCPs. - + Optional Keys are differentiated from Required Keys in that Optional Keys may or may not be supported for existence and/or matching by C-FIND SCPs. Whereas, Required Keys must always be supported by C-FIND SCPs. - Optional Keys may be contained in the - Identifier of a C-FIND request. Optional Keys shall not be contained in the Identifier of - C-MOVE and C-GET requests. - + Optional Keys may be contained in the Identifier of a C-FIND request. Optional Keys shall not be contained in the Identifier of C-MOVE and C-GET requests.
Attribute Matching - The following types of matching may be - performed on Key Attributes in the Query/Retrieve Service Class: - + The following types of matching may be performed on Key Attributes in the Query/Retrieve Service Class: Single Value Matching @@ -8678,261 +6621,116 @@ Multiple Value Matching - Matching requires special characters (i.e., - "*","?","-", "=", "\", and QUOTATION MARK of the Default Character Repertoire), which need not - be part of the character repertoire for the VR of the Key Attributes. - + Matching requires special characters (i.e., "*","?","-", "=", "\", and QUOTATION MARK of the Default Character Repertoire), which need not be part of the character repertoire for the VR of the Key Attributes. - For example, the "-" character - is not valid for the DA, DT and TM VRs but is used for Range Matching. The wild card - characters "*" and "?" are not valid for the CS VR but are used for Wild Card - Matching. - + For example, the "-" character is not valid for the DA, DT and TM VRs but is used for Range Matching. The wild card characters "*" and "?" are not valid for the CS VR but are used for Wild Card Matching. - When character sets other than - the Default Character Repertoire are used, then the rules in - - apply, such as with respect to the use of the 05/12 "\" (BACKSLASH) (in ISO IR 6) or - 05/12 "¥" (YEN SIGN) (in ISO IR 14). - + When character sets other than the Default Character Repertoire are used, then the rules in apply, such as with respect to the use of the 05/12 "\" (BACKSLASH) (in ISO IR 6) or 05/12 "¥" (YEN SIGN) (in ISO IR 14). - The total length of the Key Attribute may - exceed the length as specified in the VR in. The Value - Multiplicity (VM) may be larger than the VM specified in - - for the Key Attribute, as defined for particular Matching Type. - - The Specific Character Set (0008,0005) - Attribute may be present in the Identifier but is never matched. Rather, it specifies how other - Attributes are encoded in the Request and Response Identifiers. - - It may influence how matching of other - Attributes is performed. If Specific Character Set (0008,0005) is absent, then the Default - Character Repertoire shall be used. Specific Character Set (0008,0005) shall not have a zero - length value. - - Specific Character Set (0008,0005) may have - multiple values if escape sequences are used to switch between character repertoires within - values. - - If the SCP does not support the value(s) of - Specific Character Set (0008,0005) in the Request Identifier, then the manner in which matching - is performed is undefined and shall be specified in the conformance statement. - + The total length of the Key Attribute may exceed the length as specified in the VR in . The Value Multiplicity (VM) may be larger than the VM specified in for the Key Attribute, as defined for particular Matching Type. + The Specific Character Set (0008,0005) Attribute may be present in the Identifier but is never matched. Rather, it specifies how other Attributes are encoded in the Request and Response Identifiers. + It may influence how matching of other Attributes is performed. If Specific Character Set (0008,0005) is absent, then the Default Character Repertoire shall be used. Specific Character Set (0008,0005) shall not have a zero length value. + Specific Character Set (0008,0005) may have multiple values if escape sequences are used to switch between character repertoires within values. + If the SCP does not support the value(s) of Specific Character Set (0008,0005) in the Request Identifier, then the manner in which matching is performed is undefined and shall be specified in the conformance statement. - If an SCU sends a Request - Identifier with a single byte character set not supported by the SCP, then it is - likely, but not required, that the SCP will treat unrecognized characters as wild - cards and match only on characters in the default repertoire, and return a response - in the default repertoire. - + If an SCU sends a Request Identifier with a single byte character set not supported by the SCP, then it is likely, but not required, that the SCP will treat unrecognized characters as wild cards and match only on characters in the default repertoire, and return a response in the default repertoire. - Some Specific Character Set - values are used with multi-component group person names (e.g., single-byte, - ideographic and phonetic and phonetic component groups separated by an "=" (3DH) - character), which may also affect the behavior of literal string matching. - + Some Specific Character Set values are used with multi-component group person names (e.g., single-byte, ideographic and phonetic and phonetic component groups separated by an "=" (3DH) character), which may also affect the behavior of literal string matching. - The Timezone Offset From UTC (0008,0201) - Attribute may be present in the Identifier but is not matched if Timezone query adjustment is - negotiated. If Timezone query adjustment is negotiated, it specifies how Attribute Values of VR - of DT and TM (including related Attribute Values of VR of DA, if present) are interpreted in the - Request and Response Identifiers if those values lack a specific time zone offset specification. - + The Timezone Offset From UTC (0008,0201) Attribute may be present in the Identifier but is not matched if Timezone query adjustment is negotiated. If Timezone query adjustment is negotiated, it specifies how Attribute Values of VR of DT and TM (including related Attribute Values of VR of DA, if present) are interpreted in the Request and Response Identifiers if those values lack a specific time zone offset specification.
Single Value Matching - If the value specified for a Key - Attribute in a request is non-zero length and if it is not of VR SQ and: - + If the value specified for a Key Attribute in a request is non-zero length and if it is not of VR SQ and: - of VR of AE, CS, LO, LT, PN, - SH, ST, UC, UR or UT and contains a single value with no wild card characters, - and if Extended Negotiation of Empty Value Matching is successful and it does not - have the value of exactly two QUOTATION MARK characters, - or - + of VR of AE, CS, LO, LT, PN, SH, ST, UC, UR or UT and contains a single value with no wild card characters, + and if Extended Negotiation of Empty Value Matching is successful and it does not have the value of exactly two QUOTATION MARK characters, + or - of VR of DA, TM or DT and - contains a single value with no "-" and no QUOTATION MARK characters, or - + of VR of DA, TM or DT and contains a single value with no "-" and no QUOTATION MARK characters, or of any other VR - then Single Value Matching shall be - performed. Except for Attributes with a PN VR, only entities with values that match exactly - the value specified in the request shall match. This matching is case-sensitive, i.e., - sensitive to the exact encoding of the key Attribute Value in character sets where a letter - may have multiple encodings (e.g., based on its case, its position in a word, or whether it - is accented). - + then Single Value Matching shall be performed. Except for Attributes with a PN VR, only entities with values that match exactly the value specified in the request shall match. This matching is case-sensitive, i.e., sensitive to the exact encoding of the key Attribute Value in character sets where a letter may have multiple encodings (e.g., based on its case, its position in a word, or whether it is accented).
Attributes of VR of PN - For Attributes with a PN VR (e.g., - Patient Name (0010,0010)), an application may perform literal matching that is either - case-sensitive, or that is insensitive to some or all aspects of case, position, accent, - or other character encoding variants. - + For Attributes with a PN VR (e.g., Patient Name (0010,0010)), an application may perform literal matching that is either case-sensitive, or that is insensitive to some or all aspects of case, position, accent, or other character encoding variants. - For multi-component names, the - component group delimiter "=" (3DH) may be present in the Key Attribute Value, but - may give unexpected results if the SCP does not support matching on separate - components but interprets the entire value literally as a single string. E.g., - "Wang^XiaoDong=王^小東" may or may not match "Wang^XiaoDong" or "王^小東"; Wild Card - Matching without the component group delimiter, such as "*Wang^XiaoDong*" or "*王^小東 - *" may be necessary. - + For multi-component names, the component group delimiter "=" (3DH) may be present in the Key Attribute Value, but may give unexpected results if the SCP does not support matching on separate components but interprets the entire value literally as a single string. E.g., "Wang^XiaoDong=王^小東" may or may not match "Wang^XiaoDong" or "王^小東"; Wild Card Matching without the component group delimiter, such as "*Wang^XiaoDong*" or "*王^小東 *" may be necessary. - If extended negotiation of fuzzy - semantic matching rather than literal matching of PN VR is successful, not only may - matching be insensitive to case, position, accent, and character encoding (including - combining characters), but in addition other techniques such as phonetic matching may be - applied. - + If Extended Negotiation of fuzzy semantic matching rather than literal matching of PN VR is successful, not only may matching be insensitive to case, position, accent, and character encoding (including combining characters), but in addition other techniques such as phonetic matching may be applied. - Matching of PN - Attributes may be accent-insensitive, as specified in the conformance - statement. Accent-insensitive matching would successfully match, for - instance, a query character "SMALL LETTER a" (06/01 in the default ISO-IR 6) - with - + Matching of PN Attributes may be accent-insensitive, as specified in the conformance statement. Accent-insensitive matching would successfully match, for instance, a query character "SMALL LETTER a" (06/01 in the default ISO-IR 6) with - "SMALL LETTER a - WITH GRAVE ACCENT" (14/00 in ISO-IR 100), - + "SMALL LETTER a WITH GRAVE ACCENT" (14/00 in ISO-IR 100), - "SMALL LETTER a - WITH TILDE" (14/03 in ISO-IR 100), - + "SMALL LETTER a WITH TILDE" (14/03 in ISO-IR 100), - "SMALL LETTER a - WITH BREVE" (14/03 in ISO-IR 101), and - + "SMALL LETTER a WITH BREVE" (14/03 in ISO-IR 101), and - "CAPITAL LETTER - a WITH ACUTE ACCENT" (12/01 in ISO-IR 100) (if matching is also - case-insensitive), - + "CAPITAL LETTER a WITH ACUTE ACCENT" (12/01 in ISO-IR 100) (if matching is also case-insensitive), - but would not match - 14/00 in ISO-IR 101, which is "SMALL LETTER r WITH ACUTE ACCENT". Matching - to particular bit-combinations is specific to each supported character set - (note the difference in meaning of 14/00), and should be described in the - conformance statement. - + but would not match 14/00 in ISO-IR 101, which is "SMALL LETTER r WITH ACUTE ACCENT". Matching to particular bit-combinations is specific to each supported character set (note the difference in meaning of 14/00), and should be described in the conformance statement. - An SCU application may - elect to perform additional filtering of the responses by applying the - matching rules itself. In the event that both the SCU and SCP are applying - the matching rules, this process will be successful as long as literal - matching is performed by both, and any additional SCU filtering is - insensitive to case, position, accent, or other character encoding variants. - + An SCU application may elect to perform additional filtering of the responses by applying the matching rules itself. In the event that both the SCU and SCP are applying the matching rules, this process will be successful as long as literal matching is performed by both, and any additional SCU filtering is insensitive to case, position, accent, or other character encoding variants. - However if fuzzy semantic matching - of PN Attributes has been negotiated, matching by the SCP may result in responses that - are not obviously related to the request, hence care should be taken if any additional - filtering of responses is performed by the SCU. For example, if phonetic matching is - performed, a query for "Swain" might well return "Swayne", or if name component order - insensitive matching is performed, a query for "Smith^Mary" might well return - "Mary^Smith" or "Mary Smith" or "Smith, Mary". Fuzzy semantic matching may also take - into account separate single-byte, ideographic and phonetic name component groups. - + However if fuzzy semantic matching of PN Attributes has been negotiated, matching by the SCP may result in responses that are not obviously related to the request, hence care should be taken if any additional filtering of responses is performed by the SCU. For example, if phonetic matching is performed, a query for "Swain" might well return "Swayne", or if name component order insensitive matching is performed, a query for "Smith^Mary" might well return "Mary^Smith" or "Mary Smith" or "Smith, Mary". Fuzzy semantic matching may also take into account separate single-byte, ideographic and phonetic name component groups.
Attributes of VR of AE, CS, LO, LT, PN, SH, ST, UC, UR and UT - The AE, LO, LT, PN, SH, ST, UC, UR - and UT VRs allow the presence of wild card characters "*" and "?". Wild card matching is - also defined for CS values. Single value matching against such characters is not - supported. See. - + The AE, LO, LT, PN, SH, ST, UC, UR and UT VRs allow the presence of wild card characters "*" and "?". Wild card matching is also defined for CS values. Single value matching against such characters is not supported. See .
Attributes of VR of DA, DT or TM - If the Timezone Offset From UTC - (0008,0201) Attribute is present in the Identifier and Timezone query adjustment was - negotiated, it shall be used to adjust values of Attributes of VR of TM (and associated - Attributes of VR of DA, if present) from the local timezone to UTC. It shall also adjust - values of Attributes of VR of DT that do not specify a timezone offset. The encoding and - semantics of the Timezone Offset From UTC (0008,0201) Attribute shall be as defined in - the SOP Common Module in. - - The manner in which matching is - performed is implementation dependent and shall be specified in the conformance - statement. - + If the Timezone Offset From UTC (0008,0201) Attribute is present in the Identifier and Timezone query adjustment was negotiated, it shall be used to adjust values of Attributes of VR of TM (and associated Attributes of VR of DA, if present) from the local timezone to UTC. It shall also adjust values of Attributes of VR of DT that do not specify a timezone offset. The encoding and semantics of the Timezone Offset From UTC (0008,0201) Attribute shall be as defined in the SOP Common Module in . + The manner in which matching is performed is implementation dependent and shall be specified in the conformance statement. - This definition implies - that values of VR of TM, DA and DT are matched by their meaning, not as - literal strings. For example: - + This definition implies that values of VR of TM, DA and DT are matched by their meaning, not as literal strings. For example: - the DT - "19980128103000.0000" matches "19980128103000" - + the DT "19980128103000.0000" matches "19980128103000" - the DT - "19980128103000" with no timezone offset matches "19980128073000" - with timezone offset "-0300" - + the DT "19980128103000" with no timezone offset matches "19980128073000" with timezone offset "-0300" - the TM "2230" - matches "223000" - + the TM "2230" matches "223000" - If an application is - concerned about how Single Value Matching of dates and times is performed by - another application, it may consider using Range Matching instead, which is - always performed by meaning, with both values in the range the same. - + If an application is concerned about how Single Value Matching of dates and times is performed by another application, it may consider using Range Matching instead, which is always performed by meaning, with both values in the range the same. - Exclusion of the "-" - character for Single Value Matching implies that a Key Attribute with a VR - of DT may not contain a negative offset from Universal Coordinated Time - (UTC) if Single Value Matching is intended. Use of the "-" character in - values of VR of TM, DA and DT indicates Range Matching. - + Exclusion of the "-" character for Single Value Matching implies that a Key Attribute with a VR of DT may not contain a negative offset from Universal Coordinated Time (UTC) if Single Value Matching is intended. Use of the "-" character in values of VR of TM, DA and DT indicates Range Matching. - If an application is in - a local time zone that has a negative offset then it cannot perform Single - Value Matching using a local time notation. Instead, it can convert the Key - Attribute Value to UTC and use an explicit suffix of "+0000". - + If an application is in a local time zone that has a negative offset then it cannot perform Single Value Matching using a local time notation. Instead, it can convert the Key Attribute Value to UTC and use an explicit suffix of "+0000". @@ -8940,94 +6738,38 @@
List of UID Matching - A List of UIDs is encoded by using the - value multiplicity operator, backslash ("\"), as a delimiter between UIDs. Each item in the - list shall contain a single UID value. Each UID in the list contained in the Identifier of - the request may generate a match. - + A List of UIDs is encoded by using the value multiplicity operator, backslash ("\"), as a delimiter between UIDs. Each item in the list shall contain a single UID value. Each UID in the list contained in the Identifier of the request may generate a match. - A list of single values is encoded - exactly as a VR of UI and a VM of Multiple (see - ). - + A list of single values is encoded exactly as a VR of UI and a VM of Multiple (see ).
Universal Matching - If the value specified for a Key - Attribute in a request is zero length, then all entities shall match this Attribute. An - Attribute that contains a Universal Match specification in a C-FIND request provides a - mechanism to request the selected Attribute Value be returned in corresponding C-FIND - responses. - + If the value specified for a Key Attribute in a request is zero length, then all entities shall match this Attribute. An Attribute that contains a Universal Match specification in a C-FIND request provides a mechanism to request the selected Attribute Value be returned in corresponding C-FIND responses.
Wild Card Matching - If the Attribute is of VR of AE, CS, - LO, LT, PN, SH, ST, UC, UR, UT and the value specified in the request contains any - occurrence of an "*" or a "?", then "*" shall match any sequence of characters (including a - zero length value) and "?" shall match any single character. This matching is case - sensitive, except for Attributes with a PN VR (e.g., Patient Name (0010,0010)). - - For Attributes with a PN VR, including - the case of extended negotiation of fuzzy semantic matching, Wild Card Matching is - implementation dependent and shall be specified in the conformance statement. - + If the Attribute is of VR of AE, CS, LO, LT, PN, SH, ST, UC, UR, UT and the value specified in the request contains any occurrence of an "*" or a "?", then "*" shall match any sequence of characters (including a zero length value) and "?" shall match any single character. This matching is case sensitive, except for Attributes with a PN VR (e.g., Patient Name (0010,0010)). + For Attributes with a PN VR, including the case of Extended Negotiation of fuzzy semantic matching, Wild Card Matching is implementation dependent and shall be specified in the conformance statement. - Wild card matching on a - value of "*" is equivalent to Universal Matching. - + Wild card matching on a value of "*" is equivalent to Universal Matching. - The Wild Card Matching - method specified by DICOM might not be supported by some non-DICOM multi-byte - character text processors. - + The Wild Card Matching method specified by DICOM might not be supported by some non-DICOM multi-byte character text processors. - For multi-component group - names, the component group delimiter "=" (3DH) may be present in the Key - Attribute Value, but may give unexpected results if the SCP does not support - matching on separate components but interprets the entire value literally. E.g., - "*=*" or "*=*=*" may or may not return all strings, and hence is not equivalent - to "*", nor to Universal Matching. - + For multi-component group names, the component group delimiter "=" (3DH) may be present in the Key Attribute Value, but may give unexpected results if the SCP does not support matching on separate components but interprets the entire value literally. E.g., "*=*" or "*=*=*" may or may not return all strings, and hence is not equivalent to "*", nor to Universal Matching. - Attributes with VR of AE, - LO, PN, SH and UC may contain wild card characters "*" and "?". Attempts to - match on a string explicitly containing "*" or "?" will be treated as Wild Card - Matching and thus may return multiple results rather than a single one. There is - no mechanism for Single Value Matching on values that contain characters "*" and - "?" for these VRs - such queries will always be treated as queries with Wild - Card Matching. - + Attributes with VR of AE, LO, PN, SH and UC may contain wild card characters "*" and "?". Attempts to match on a string explicitly containing "*" or "?" will be treated as Wild Card Matching and thus may return multiple results rather than a single one. There is no mechanism for Single Value Matching on values that contain characters "*" and "?" for these VRs - such queries will always be treated as queries with Wild Card Matching. - Attributes with VR of ST, - LT and UT are intended for conveying narrative text and may contain wild card - characters "*" and "?". Attempts to match on a string explicitly containing "*" - or "?" will be treated as Wild Card Matching and thus may return multiple - results rather than a single one. There is no mechanism for Single Value - Matching on values that contain characters "*" and "?" for these VRs - such - queries will always be treated as queries with Wild Card Matching. - + Attributes with VR of ST, LT and UT are intended for conveying narrative text and may contain wild card characters "*" and "?". Attempts to match on a string explicitly containing "*" or "?" will be treated as Wild Card Matching and thus may return multiple results rather than a single one. There is no mechanism for Single Value Matching on values that contain characters "*" and "?" for these VRs - such queries will always be treated as queries with Wild Card Matching. - Attributes with VR of UR - may contain wild card characters "*" and "?" as delimiters. These characters are - reserved according to - - Section 2. Attempts to match on a string explicitly containing "*" or "?" will - be treated as Wild Card Matching and thus may return multiple results rather - than a single one. There is no mechanism for Single Value Matching on values - that contain characters "*" and "?" for these VRs - such queries will always be - treated as queries with Wild Card Matching. - + Attributes with VR of UR may contain wild card characters "*" and "?" as delimiters. These characters are reserved according to Section 2. Attempts to match on a string explicitly containing "*" or "?" will be treated as Wild Card Matching and thus may return multiple results rather than a single one. There is no mechanism for Single Value Matching on values that contain characters "*" and "?" for these VRs - such queries will always be treated as queries with Wild Card Matching. @@ -9036,62 +6778,33 @@ Range Matching
Range Matching of Attributes of VR of DA - In the absence of extended - negotiation, then: - + In the absence of Extended Negotiation, then: - A string of the form "<date1> - - <date2>", where <date1> is less or equal to <date2>, shall - match all occurrences of dates that fall between <date1> and <date2> - inclusive - + A string of the form "<date1> - <date2>", where <date1> is less or equal to <date2>, shall match all occurrences of dates that fall between <date1> and <date2> inclusive - A string of the form "- - <date1>" shall match all occurrences of dates prior to and including <date1> - + A string of the form "- <date1>" shall match all occurrences of dates prior to and including <date1> - A string of the form "<date1> - -" shall match all occurrences of <date1> and subsequent dates - + A string of the form "<date1> -" shall match all occurrences of <date1> and subsequent dates
Range Matching of Attributes of VR of TM - All comparison specified in the - following shall be based on a direct comparison of times within a day. "Prior" includes - all times starting from midnight of the same day to the specified time. "Subsequent" - includes all times starting with the specified time until any time prior to midnight of - the following day. Range matching crossing midnight is not supported. - - No offset from Universal - Coordinated Time is permitted in the TM VR values. If Timezone Offset From UTC - (0008,0201) is present in the query identifier, the specified time values and the - definition of midnight are in the specified timezone. - - In the absence of extended - negotiation, then: - + All comparison specified in the following shall be based on a direct comparison of times within a day. "Prior" includes all times starting from midnight of the same day to the specified time. "Subsequent" includes all times starting with the specified time until any time prior to midnight of the following day. Range matching crossing midnight is not supported. + No offset from Universal Coordinated Time is permitted in the TM VR values. If Timezone Offset From UTC (0008,0201) is present in the query identifier, the specified time values and the definition of midnight are in the specified timezone. + In the absence of Extended Negotiation, then: - A string of the form "<time1> - - <time2>", where <time1> is less or equal to <time2>, shall - match all occurrences of times that fall between <time1> and <time2> - inclusive - + A string of the form "<time1> - <time2>", where <time1> is less or equal to <time2>, shall match all occurrences of times that fall between <time1> and <time2> inclusive - A string of the form "- - <time1>" shall match all occurrences of times prior to and including <time1> - + A string of the form "- <time1>" shall match all occurrences of times prior to and including <time1> - A string of the form "<time1> - -" shall match all occurrences of <time1> and subsequent times - + A string of the form "<time1> -" shall match all occurrences of <time1> and subsequent times
@@ -9099,155 +6812,73 @@ Range Matching of Attributes of VR of DT - A string of the form "<datetime1> - - <datetime2>", where <datetime1> is less or equal to <datetime2>, - shall match all moments in time that fall between <datetime1> and <datetime2> - inclusive - + A string of the form "<datetime1> - <datetime2>", where <datetime1> is less or equal to <datetime2>, shall match all moments in time that fall between <datetime1> and <datetime2> inclusive - A string of the form "- - <datetime1>" shall match all moments in time prior to and including <datetime1> - + A string of the form "- <datetime1>" shall match all moments in time prior to and including <datetime1> - A string of the form "<datetime1> - -" shall match all moments in time subsequent to and including <datetime1> - + A string of the form "<datetime1> -" shall match all moments in time subsequent to and including <datetime1> - The offset from Universal - Coordinated Time, if present in the Value of the Attribute, shall be taken into - account for the purposes of the match. - + The offset from Universal Coordinated Time, if present in the Value of the Attribute, shall be taken into account for the purposes of the match.
Range Matching General Rules - If extended negotiation of combined - datetime matching is successful, then a pair of Attributes that are of VR DA and TM, - both of which specify the same form of Range Matching, shall have the concatenated - string values of each Range Matching component matched as if they were a single - Attribute of VR DT. - + If Extended Negotiation of combined datetime matching is successful, then a pair of Attributes that are of VR DA and TM, both of which specify the same form of Range Matching, shall have the concatenated string values of each Range Matching component matched as if they were a single Attribute of VR DT. - For example, a Study Date of - "20060705-20060707" and a Study Time of "1000-1800" will match the time period of - July 5, 10am until July 7, 6pm, rather than the three time periods of 10am until 6pm - on each of July 5, July 6 and July 7, as would be the case without extended - negotiation. - + For example, a Study Date of "20060705-20060707" and a Study Time of "1000-1800" will match the time period of July 5, 10am until July 7, 6pm, rather than the three time periods of 10am until 6pm on each of July 5, July 6 and July 7, as would be the case without Extended Negotiation. - Regardless of other extended - negotiation, an application may use the value of Timezone Offset From UTC (0008,0201) to - adjust values of Attributes of VR TM and DT from the local timezone to UTC for matching. - See. - + Regardless of other Extended Negotiation, an application may use the value of Timezone Offset From UTC (0008,0201) to adjust values of Attributes of VR TM and DT from the local timezone to UTC for matching. See . - If extended negotiation of - combined datetime matching is successful, the timezone offset may effect a change in - date if the local time and UTC are on different sides of midnight. - + If Extended Negotiation of combined datetime matching is successful, the timezone offset may effect a change in date if the local time and UTC are on different sides of midnight. - Range matching is not defined for - types of Attributes other than dates and times. - + Range matching is not defined for types of Attributes other than dates and times.
Sequence Matching - If a Key Attribute in the Identifier of - a C-FIND request needs to be matched against an Attribute structured as a Sequence of Items - (VR of SQ), the Key Attribute shall be structured as a Sequence of Items with a single Item. - This Item may contain zero or more Item Key Attributes. Each Item Key Attribute matching - shall be performed on an Item by Item basis. The types of matching defined in - - shall be used: Single Value Matching, List of UID Matching, Universal Matching, Wild Card - Matching, Range Matching and Sequence Matching (recursive Sequence matching). - - If all the Item Key Attributes match, - for at least one of the Items of the Attribute against which the match is performed, a - successful match is generated. A sequence of matching Items containing only the requested - Attributes is returned in the corresponding C-FIND responses. - - If the Key Attribute in the Identifier - of a C-FIND request contains no Key Item Attribute (zero-length Item Tag), then all entities - shall match this Attribute. This provides a Universal Matching like mechanism to request - that the selected Key Attribute Value (the entire Sequence of Items) be returned in - corresponding C-FIND responses. - + If a Key Attribute in the Identifier of a C-FIND request needs to be matched against an Attribute structured as a Sequence of Items (VR of SQ), the Key Attribute shall be structured as a Sequence of Items with a single Item. This Item may contain zero or more Item Key Attributes. Each Item Key Attribute matching shall be performed on an Item by Item basis. The types of matching defined in shall be used: Single Value Matching, List of UID Matching, Universal Matching, Wild Card Matching, Range Matching and Sequence Matching (recursive Sequence matching). + If all the Item Key Attributes match, for at least one of the Items of the Attribute against which the match is performed, a successful match is generated. A sequence of matching Items containing only the requested Attributes is returned in the corresponding C-FIND responses. + If the Key Attribute in the Identifier of a C-FIND request contains no Key Item Attribute (zero-length Item Tag), then all entities shall match this Attribute. This provides a Universal Matching like mechanism to request that the selected Key Attribute Value (the entire Sequence of Items) be returned in corresponding C-FIND responses.
Empty Value Matching - If Extended Negotiation of Empty Value - Matching is successful, and for Attributes with VR of AE, CS, DA, DT, LO, LT, PN, SH, ST, - TM, UC, UR, or UT, a Key Attribute value of exactly two QUOTATION MARK characters (22H in - the Default Character Repertoire) specified in a request shall indicate matching to an empty - value. - Such a match is successful to entities with a zero-length value for the corresponding - Attribute, or for which the Attribute is not present. - + If Extended Negotiation of Empty Value Matching is successful, and for Attributes with VR of AE, CS, DA, DT, LO, LT, PN, SH, ST, TM, UC, UR, or UT, a Key Attribute value of exactly two QUOTATION MARK characters (22H in the Default Character Repertoire) specified in a request shall indicate matching to an empty value. + Such a match is successful to entities with a zero-length value for the corresponding Attribute, or for which the Attribute is not present. - Other quotation mark - characters defined in an expanded or replacement character set, such as double - angle quotation marks, left and right curved quotation marks, etc., are not - valid for specifying empty value matching. - + Other quotation mark characters defined in an expanded or replacement character set, such as double angle quotation marks, left and right curved quotation marks, etc., are not valid for specifying empty value matching. - VRs of AE, LO, LT, PN, SH, - ST, UC, and UT allow the QUOTATION MARK character. - Matching of a string of two QUOTATION MARK characters in those Attributes can be - done with wild card matching using the ASTERISK character (e.g., ""*). - + VRs of AE, LO, LT, PN, SH, ST, UC, and UT allow the QUOTATION MARK character. + Matching of a string of two QUOTATION MARK characters in those Attributes can be done with wild card matching using the ASTERISK character (e.g., ""*).
Multiple Value Matching - If Extended Negotiation of Multiple - Value Matching is successful, and for Attributes with VR of AE, AS, AT, CS, LO, PN, SH, or - UC and a defined VM greater than 1, a Key Attribute with multiple values specified in a - request shall indicate matching to a multi-valued entity Attribute. - Such a match is successful only if each and every value in the Key Attribute matches a value - in the corresponding Attribute in the entity. - - Key Attribute Values shall not include - wild cards. - - The order of Attribute Values in the - request need not match the order in the corresponding entity Attribute. - + If Extended Negotiation of Multiple Value Matching is successful, and for Attributes with VR of AE, AS, AT, CS, LO, PN, SH, or UC and a defined VM greater than 1, a Key Attribute with multiple values specified in a request shall indicate matching to a multi-valued entity Attribute. + Such a match is successful only if each and every value in the Key Attribute matches a value in the corresponding Attribute in the entity. + Key Attribute Values shall not include wild cards. + The order of Attribute Values in the request need not match the order in the corresponding entity Attribute. - This is a logical 'AND' - function for all values in the Key Attribute. E.g., a value of CT\PT for - Modalities in Study (0008,0061) in the Request Identifier will match only - Studies that include both a CT Series and a PT Series. - + This is a logical 'AND' function for all values in the Key Attribute. E.g., a value of CT\PT for Modalities in Study (0008,0061) in the Request Identifier will match only Studies that include both a CT Series and a PT Series. - There may be additional - values in the entity Attribute that do not match values in the Key Attribute. - + There may be additional values in the entity Attribute that do not match values in the Key Attribute. - Multiple Value Matching - does not apply to Specific Character Set (0008,0005), which is not a Key - Attribute for matching, but rather specifies the encoding of characters in the - Identifier. - + Multiple Value Matching does not apply to Specific Character Set (0008,0005), which is not a Key Attribute for matching, but rather specifies the encoding of characters in the Identifier. - In the absence of - successful Extended Negotiation for Multiple Value Matching, the semantics of - multiple values in a Key Attribute is undefined. - + In the absence of successful Extended Negotiation for Multiple Value Matching, the semantics of multiple values in a Key Attribute is undefined. @@ -9255,22 +6886,14 @@
Matching Multiple Values - When using Single Value Matching, Wild Card - Matching, or Range Matching for matching an Attribute that has a value multiplicity of greater - than one, if any of the values match, then all values shall be returned. - - When using Multiple Value Matching, if - matching is successful, then all values shall be returned. - + When using Single Value Matching, Wild Card Matching, or Range Matching for matching an Attribute that has a value multiplicity of greater than one, if any of the values match, then all values shall be returned. + When using Multiple Value Matching, if matching is successful, then all values shall be returned.
Standard Query/Retrieve Information Models - Three standard Query/Retrieve Information Models - are defined in this Annex. Each Query/Retrieve Information Model is associated with a number of SOP - Classes. The following three hierarchical Query/Retrieve Information Models are defined: - + Three standard Query/Retrieve Information Models are defined in this Annex. Each Query/Retrieve Information Model is associated with a number of SOP Classes. The following three hierarchical Query/Retrieve Information Models are defined: Patient Root @@ -9284,9 +6907,7 @@
Patient Root Query/Retrieve Information Model - The Patient Root Query/Retrieve Information - Model is based upon a four level hierarchy: - + The Patient Root Query/Retrieve Information Model is based upon a four level hierarchy: Patient @@ -9301,43 +6922,14 @@ Composite Object Instance - The patient level is the top level and contains - Attributes associated with the Patient Information Entity (IE) of the Composite IODs as defined in - . Patients IEs are - modality independent. - - The study level is below the patient level and - contains Attributes associated with the Study IE of the Composite IODs as defined in. A study belongs to a - single patient. A single patient may have multiple studies. Study IEs are modality independent. - - The series level is below the study level and - contains Attributes associated with the Series, Frame of Reference and Equipment IEs of the - Composite IODs as defined in. A series belongs to a single - study. A single study may have multiple series. Series IEs are modality dependent. To accommodate - this modality dependence, the set of Optional Keys at the series level includes all Attributes - defined at the series level from any Composite IOD defined in - . - - The lowest level is the Composite Object - Instance level and contains Attributes associated with the Composite object IE of the Composite IODs - as defined in. A - Composite Object Instance belongs to a single series. A single series may contain multiple Composite - Object Instances. Most composite object IEs are modality dependent. To accommodate this potential - modality dependence, the set of Optional Keys at the Composite Object Instance level includes all - Attributes defined at the Composite Object Instance level from any Composite IOD defined in. - + The patient level is the top level and contains Attributes associated with the Patient Information Entity (IE) of the Composite IODs as defined in . Patients IEs are modality independent. + The study level is below the patient level and contains Attributes associated with the Study IE of the Composite IODs as defined in . A study belongs to a single patient. A single patient may have multiple studies. Study IEs are modality independent. + The series level is below the study level and contains Attributes associated with the Series, Frame of Reference and Equipment IEs of the Composite IODs as defined in . A series belongs to a single study. A single study may have multiple series. Series IEs are modality dependent. To accommodate this modality dependence, the set of Optional Keys at the series level includes all Attributes defined at the series level from any Composite IOD defined in . + The lowest level is the Composite Object Instance level and contains Attributes associated with the Composite object IE of the Composite IODs as defined in . A Composite Object Instance belongs to a single series. A single series may contain multiple Composite Object Instances. Most composite object IEs are modality dependent. To accommodate this potential modality dependence, the set of Optional Keys at the Composite Object Instance level includes all Attributes defined at the Composite Object Instance level from any Composite IOD defined in .
Study Root Query/Retrieve Information Model - The Study Root Query/Retrieve Information Model - is identical to the Patient Root Query/Retrieve Information Model except the top level is the study - level. Attributes of patients are considered to be Attributes of studies. - + The Study Root Query/Retrieve Information Model is identical to the Patient Root Query/Retrieve Information Model except the top level is the study level. Attributes of patients are considered to be Attributes of studies.
Patient/Study Only Query/Retrieve Information Model @@ -9345,12 +6937,7 @@
Additional Query/Retrieve Attributes - Some optional Attributes that may be used in - Query/Retrieve Information Models that are not Attributes of an Information Object Definition and, - therefore, are not defined in. These Attributes are defined - in. - + Some optional Attributes that may be used in Query/Retrieve Information Models that are not Attributes of an Information Object Definition and, therefore, are not defined in . These Attributes are defined in .
Key Type Conventions for Query/Retrieve Information Models
@@ -9369,92 +6956,68 @@ @@ -9465,9 +7028,7 @@ (0008,0061) @@ -9478,86 +7039,45 @@ (0008,0062) @@ -9568,498 +7088,219 @@ (0008,041F) +
Additional Query/Retrieve Attributes
- Number of Patient Related - Studies - + Number of Patient Related Studies (0020,1200) - The number of studies that - match the Patient level Query/Retrieve search criteria - + The number of studies that match the Patient level Query/Retrieve search criteria
- Number of Patient Related - Series - + Number of Patient Related Series (0020,1202) - The number of series that match - the Patient level Query/Retrieve search criteria - + The number of series that match the Patient level Query/Retrieve search criteria
- Number of Patient Related - Instances - + Number of Patient Related Instances (0020,1204) - The number of Composite Object - Instances that match the Patient level Query/Retrieve search criteria - + The number of Composite Object Instances that match the Patient level Query/Retrieve search criteria
- Number of Study Related - Series - + Number of Study Related Series (0020,1206) - The number of series that match - the Study level Query/Retrieve search criteria - + The number of series that match the Study level Query/Retrieve search criteria
- Number of Series Related - Instances - + Number of Series Related Instances (0020,1209) - The number of Composite Object - Instances in a Series that match the Series level Query/Retrieve search criteria - + The number of Composite Object Instances in a Series that match the Series level Query/Retrieve search criteria
- Number of Study Related - Instances - + Number of Study Related Instances (0020,1208) - The number of Composite Object - Instances that match the Study level Query/Retrieve search criteria - + The number of Composite Object Instances that match the Study level Query/Retrieve search criteria
- All of the distinct values used - for Modality (0008,0060) in the Series of the Study. - + All of the distinct values used for Modality (0008,0060) in the Series of the Study.
- The SOP Classes contained in - the Study. - + The SOP Classes contained in the Study.
- Anatomic Regions in Study Code - Sequence - + Anatomic Regions in Study Code Sequence (0008,0063) - The anatomic regions of - interest in this Study (i.e., external anatomy, surface anatomy, or general region - of the body). - - One or more Items are permitted - in this Sequence. - + The anatomic regions of interest in this Study (i.e., external anatomy, surface anatomy, or general region of the body). + One or more Items are permitted in this Sequence. - If the Instances in the - Study contain Anatomic Region Sequence (0008,2218), then the Items of this - Sequence may be the union of the codes in the Instances. Alternatively, multiple - (usually contiguous) anatomic regions might be combined into a single code. - E.g., (51185008, - SCT, "Chest"), (113345001, SCT, "Abdomen") - and - (12921003, SCT, "Pelvis") - might be combined into (416775004, SCT, "Chest, - Abdomen and Pelvis"). - - If Instances in the Study - do not contain Anatomic Region Sequence (0008,2218) but do contain Body Part - Examined (0018,0015), then codes equivalent to recognized values of Body Part - Examined (0018,0015) may be used. See - - for standard equivalent values. E.g., if an Instance contained Body Part - Examined (0018,0015) with a value of "CHEST", then this Sequence might - contain (51185008, - SCT, "Chest"). - + If the Instances in the Study contain Anatomic Region Sequence (0008,2218), then the Items of this Sequence may be the union of the codes in the Instances. Alternatively, multiple (usually contiguous) anatomic regions might be combined into a single code. E.g., (51185008, SCT, "Chest"), (113345001, SCT, "Abdomen") and (12921003, SCT, "Pelvis") might be combined into (416775004, SCT, "Chest, Abdomen and Pelvis"). + If Instances in the Study do not contain Anatomic Region Sequence (0008,2218) but do contain Body Part Examined (0018,0015), then codes equivalent to recognized values of Body Part Examined (0018,0015) may be used. See for standard equivalent values. E.g., if an Instance contained Body Part Examined (0018,0015) with a value of "CHEST", then this Sequence might contain (51185008, SCT, "Chest").
- Alternate Representation - Sequence - + Alternate Representation Sequence (0008,3001) - A Sequence of Items, each - identifying an alternate encoding of an image that matches the Instance level - Query/Retrieve search criteria (see) - + A Sequence of Items, each identifying an alternate encoding of an image that matches the Instance level Query/Retrieve search criteria (see )
- Available Transfer Syntax UID - + Available Transfer Syntax UID (0008,3002) - Describes one or more Transfer - Syntaxes that the SCP can assure will be supported for retrieval of the SOP Instance - (see). - + Describes one or more Transfer Syntaxes that the SCP can assure will be supported for retrieval of the SOP Instance (see ).
- DateTime of last update to - Study metadata (e.g., Patient, Study or Procedure, Imaging Service Request, or - Series Attributes) or to the set of SOP Instances in the Study. - + DateTime of last update to Study metadata (e.g., Patient, Study or Procedure, Imaging Service Request, or Series Attributes) or to the set of SOP Instances in the Study. - May also reflect DateTime - of update to the storage location of Study SOP Instances if the SCP supports - Attributes for stored SOP Instance access through a non-DICOM protocol (see), - + May also reflect DateTime of update to the storage location of Study SOP Instances if the SCP supports Attributes for stored SOP Instance access through a non-DICOM protocol (see ), -
- If the SCP manages images in multiple alternate - encodings, only one of the alternate encodings of an image is included in the number of object - instances. - + If the SCP manages images in multiple alternate encodings, only one of the alternate encodings of an image is included in the number of object instances.
New Instance Creation for Enhanced Multi-Frame Image Conversion - When Query/Retrieve View (0008,0053) is present - with a value of "CLASSIC" or "ENHANCED" in a C-FIND, C-MOVE or C-GET Request Identifier, then the - Information Model against which the query or retrieval is performed and any SOP Instances that are - retrieved shall be returned, constructed or converted according to the requirements in this section. - - There are no requirements with respect to when - such instances are actually created or persisted, only that they be available on request. I.e., they - may be created in advance (cached) or they may be created dynamically as required, as long as the - process is deterministic in the sense that the same Attributes will be populated with the same - values on successive queries and retrievals (including UIDs). - + When Query/Retrieve View (0008,0053) is present with a value of "CLASSIC" or "ENHANCED" in a C-FIND, C-MOVE or C-GET Request Identifier, then the Information Model against which the query or retrieval is performed and any SOP Instances that are retrieved shall be returned, constructed or converted according to the requirements in this section. + There are no requirements with respect to when such instances are actually created or persisted, only that they be available on request. I.e., they may be created in advance (cached) or they may be created dynamically as required, as long as the process is deterministic in the sense that the same Attributes will be populated with the same values on successive queries and retrievals (including UIDs). - The UID generation process is - required to be deterministic but it is important to remember that appending a suffix to - an existing UID is not a valid approach to generating a new UID, unless the converter is - the producer (owner of the root) of the original UID and knows that this is safe and the - result will be unique. - + The UID generation process is required to be deterministic but it is important to remember that appending a suffix to an existing UID is not a valid approach to generating a new UID, unless the converter is the producer (owner of the root) of the original UID and knows that this is safe and the result will be unique. - The cross-references between - original and converted instances contain sufficient information to recover UIDs in the - alternative form. - + The cross-references between original and converted instances contain sufficient information to recover UIDs in the alternative form. - All instances for a Patient known to the SCP - shall be converted as necessary to maintain referential integrity and to avoid information loss. - + All instances for a Patient known to the SCP shall be converted as necessary to maintain referential integrity and to avoid information loss. - It is not permitted to fail to - include a subset of instances within this scope, for example, the presentation states or - key object selection documents, in the "ENHANCED" view, in order to avoid the effort of - creating new instances with updated references required to maintain referential - integrity. In other words, the total "information content" of any view will be no less - than that of the default view. - + It is not permitted to fail to include a subset of instances within this scope, for example, the presentation states or key object selection documents, in the "ENHANCED" view, in order to avoid the effort of creating new instances with updated references required to maintain referential integrity. In other words, the total "information content" of any view will be no less than that of the default view. - This does not mean that all - instances need to be converted, since if they contain no such references, they can be - left alone and included in the view. For example, a Classic single slice CT localizer - image with no references can remain unchanged in the view as a CT Image Storage SOP - Class with its existing SOP Instance UID and SOP Class and in its existing Series, and - be referenced from converted instances, such as the axial images prescribed from it. An - SCU cannot make any assumptions about what will or will not be converted, or in what - order. - + This does not mean that all instances need to be converted, since if they contain no such references, they can be left alone and included in the view. For example, a Classic single slice CT localizer image with no references can remain unchanged in the view as a CT Image Storage SOP Class with its existing SOP Instance UID and SOP Class and in its existing Series, and be referenced from converted instances, such as the axial images prescribed from it. An SCU cannot make any assumptions about what will or will not be converted, or in what order. - It is understood that the - requirements of this section are applicable to a single SCP; it is not possible to - require all SCPs that perform conversion to perform it the same way, or create the same - UIDs, etc. - + It is understood that the requirements of this section are applicable to a single SCP; it is not possible to require all SCPs that perform conversion to perform it the same way, or create the same UIDs, etc. - In addition to the general requirements in this - section, specific requirements apply to the following types of instance created: - + In addition to the general requirements in this section, specific requirements apply to the following types of instance created: - Enhanced (true or legacy converted) - multi-frame images that are created from Classic single frame images - + Enhanced (true or legacy converted) multi-frame images that are created from Classic single frame images - Classic single frame images that are - created from Enhanced (true or legacy converted) multi-frame images - + Classic single frame images that are created from Enhanced (true or legacy converted) multi-frame images - Instances that contain references to - the SOP Instance UIDs or Series Instance UIDs corresponding to either the converted single - frame images, or other instances with such references - + Instances that contain references to the SOP Instance UIDs or Series Instance UIDs corresponding to either the converted single frame images, or other instances with such references The general requirements are that: - The new Composite Instance shall have a - new SOP Instance UID. - + The new Composite Instance shall have a new SOP Instance UID. - The new Composite Instance shall be a - valid SOP Instance (i.e., will comply with the IOD, Module and Attribute requirements for - the Storage SOP Class). - + The new Composite Instance shall be a valid SOP Instance (i.e., will comply with the IOD, Module and Attribute requirements for the Storage SOP Class). - The new Composite Instance shall - contain the Contributing Equipment Sequence (0018,A001). If the source Composite Instances - already contain the Contributing Equipment Sequence with a consistent set of Item values - (excluding Contribution DateTime (0018,A002)), then a new Item shall be appended to the copy - of the sequence in the new Composite Instance; if the source Composite Instance does not - contain the Contributing Equipment Sequence or the Item values (excluding Contribution - DateTime (0018,A002)) differ between source instances, then Contributing Equipment Sequence - shall be created, containing one new Item. In either case, the new Item shall describe the - equipment that is creating the new Composite Instance, and the Purpose of Reference Code - Sequence (0040,A170) within the Item shall be (109106, DCM, - "Enhanced Multi-frame Conversion Equipment") - and the - Contribution Description (0018,A003) shall be "Legacy Enhanced Image created from Classic - Images", "Classic Image created from Enhanced Image", or "Updated UID references during - Legacy Enhanced Classic conversion" as appropriate. - + The new Composite Instance shall contain the Contributing Equipment Sequence (0018,A001). If the source Composite Instances already contain the Contributing Equipment Sequence with a consistent set of Item values (excluding Contribution DateTime (0018,A002)), then a new Item shall be appended to the copy of the sequence in the new Composite Instance; if the source Composite Instance does not contain the Contributing Equipment Sequence or the Item values (excluding Contribution DateTime (0018,A002)) differ between source instances, then Contributing Equipment Sequence shall be created, containing one new Item. In either case, the new Item shall describe the equipment that is creating the new Composite Instance, and the Purpose of Reference Code Sequence (0040,A170) within the Item shall be (109106, DCM, "Enhanced Multi-frame Conversion Equipment") and the + Contribution Description (0018,A003) shall be "Legacy Enhanced Image created from Classic Images", "Classic Image created from Enhanced Image", or "Updated UID references during Legacy Enhanced Classic conversion" as appropriate. - The new Composite Instance shall have - the same Patient and Study level information as the source Instance, including the same - Study Instance UID. - + The new Composite Instance shall have the same Patient and Study level information as the source Instance, including the same Study Instance UID. - The new Composite Instance shall have - the same spatial and temporal Frame of Reference information as the source instance, if - present (e.g., the Frame of Reference UID shall be the same). - + The new Composite Instance shall have the same spatial and temporal Frame of Reference information as the source instance, if present (e.g., the Frame of Reference UID shall be the same). - The new Composite Instance shall be - placed in a new Series (together with other new Composite Instances that share the same, new - Series level information), with a new Series Instance UID. The Series Date (0008,0021) and - Series Time (0008,0031) of all the Instances in the new Series shall be the earliest of the - values in the source Composite Instances, if present. - + The new Composite Instance shall be placed in a new Series (together with other new Composite Instances that share the same, new Series level information), with a new Series Instance UID. The Series Date (0008,0021) and Series Time (0008,0031) of all the Instances in the new Series shall be the earliest of the values in the source Composite Instances, if present. - The new Series Date and - Time shall NOT be that of when the conversion was performed, but shall reflect - the values in the source images. - + The new Series Date and Time shall NOT be that of when the conversion was performed, but shall reflect the values in the source images. - There is no standard - requirement or mechanism defined to change or preserve other Series level - Attributes, such as Series Number or Series Description. This is left to the - discretion of the implementer, particularly in cases where instances from - different Series are merged. - + There is no standard requirement or mechanism defined to change or preserve other Series level Attributes, such as Series Number or Series Description. This is left to the discretion of the implementer, particularly in cases where instances from different Series are merged. - The new Composite Instance shall have - the same Items and Values of Request Attributes Sequence (0040,0275) as the source Composite - Instances, if Request Attributes Sequence (0040,0275) is present in any of the source - Composite Instances. - + The new Composite Instance shall have the same Items and Values of Request Attributes Sequence (0040,0275) as the source Composite Instances, if Request Attributes Sequence (0040,0275) is present in any of the source Composite Instances. - If the new Composite Instance contains - references to another entity for the same Patient (including, but not limited to, references - to SOP Instances, Series, Studies or Frames of Reference), and the target of those - references is also converted, then the references shall be changed to refer to the converted - entity. - + If the new Composite Instance contains references to another entity for the same Patient (including, but not limited to, references to SOP Instances, Series, Studies or Frames of Reference), and the target of those references is also converted, then the references shall be changed to refer to the converted entity. - For example, if the source - instance refers to an instance in a Series, and the referenced instance is also - converted, and hence placed in a new Series, then both the SOP Instance UID and - the Series Reference UID in the hierarchical reference to the instance will need - to be updated, as will the SOP Class UID of the referenced instance, if that has - changed, as it likely will have. - + For example, if the source instance refers to an instance in a Series, and the referenced instance is also converted, and hence placed in a new Series, then both the SOP Instance UID and the Series Reference UID in the hierarchical reference to the instance will need to be updated, as will the SOP Class UID of the referenced instance, if that has changed, as it likely will have. - The overall intent is to - maintain referential integrity within the converted set of instances, within the - scope of the same Patient. Since it is likely that most if not all non-image - instances for a patient will reference images that will be converted, this means - that most if not all non-image instances will also have to be "converted", for - the purpose of updating such references. This referential integrity is required - regardless of whether the initial request is for a subset of instances for the - patient only, or not. - + The overall intent is to maintain referential integrity within the converted set of instances, within the scope of the same Patient. Since it is likely that most if not all non-image instances for a patient will reference images that will be converted, this means that most if not all non-image instances will also have to be "converted", for the purpose of updating such references. This referential integrity is required regardless of whether the initial request is for a subset of instances for the patient only, or not. - The UIDs referenced in - Conversion Source Attributes Sequence (0020,9172) are not converted, since by - definition, these reference instances in the "other" view; they should not exist - in the source, but will be inserted (or be replaced, if previously converted) - during conversion. - + The UIDs referenced in Conversion Source Attributes Sequence (0020,9172) are not converted, since by definition, these reference instances in the "other" view; they should not exist in the source, but will be inserted (or be replaced, if previously converted) during conversion. - The specific requirements for the conversion of - single frame images to Enhanced Multi-frame images are: - + The specific requirements for the conversion of single frame images to Enhanced Multi-frame images are: - The SOP Class of the new Composite - Instance shall be the appropriate modality-specific Enhanced Image Storage SOP Class that is - intended for de novo creation by an acquisition or post-processing device, unless the source - images do not contain sufficient information to populate mandatory Attributes with standard - Enumerated Values and Defined Terms or Coded Sequence Item values, in which case the - appropriate modality-specific Legacy Converted Enhanced Image Storage SOP Class shall be - used. The appropriate SOP Classes are defined in. - + The SOP Class of the new Composite Instance shall be the appropriate modality-specific Enhanced Image Storage SOP Class that is intended for de novo creation by an acquisition or post-processing device, unless the source images do not contain sufficient information to populate mandatory Attributes with standard Enumerated Values and Defined Terms or Coded Sequence Item values, in which case the appropriate modality-specific Legacy Converted Enhanced Image Storage SOP Class shall be used. The appropriate SOP Classes are defined in . - For example, if the source - images to be converted are of the CT Image Storage SOP Class, then the preferred - new SOP Class is the Enhanced CT Image Storage SOP Class, but if this is not - possible, the Legacy Converted Enhanced CT Image Storage SOP Class is used. - + For example, if the source images to be converted are of the CT Image Storage SOP Class, then the preferred new SOP Class is the Enhanced CT Image Storage SOP Class, but if this is not possible, the Legacy Converted Enhanced CT Image Storage SOP Class is used. - It is not intended that - images from different modalities be combined in the same new Composite Instance. - For example, it is not expected that CT and PET images would be combined in the - same Instance, since the technique Attributes and the pixel data characteristics - are quite distinct. - + It is not intended that images from different modalities be combined in the same new Composite Instance. For example, it is not expected that CT and PET images would be combined in the same Instance, since the technique Attributes and the pixel data characteristics are quite distinct. - It is expected that as many - single frame images will be combined into a single multi-frame image as is - sensible, given the constrains on what Attributes must be identical as defined - in this section, and depending on the type of images and the size of the - resulting object. Different implementations may make different choices in this - respect. For example, an application might choose to combine only images in the - same Series, or with the same slice spacing, or the same values for Image Type, - or with the same Image Orientation (Patient). - + It is expected that as many single frame images will be combined into a single multi-frame image as is sensible, given the constrains on what Attributes must be identical as defined in this section, and depending on the type of images and the size of the resulting object. Different implementations may make different choices in this respect. For example, an application might choose to combine only images in the same Series, or with the same slice spacing, or the same values for Image Type, or with the same Image Orientation (Patient). - The new Composite Instance shall not be - contained in a Concatenation. This means that it shall not contain a Concatenation UID - (0020,9161) Attribute or other Concatenation Attributes. If the existing Composite Instance - contains such Attributes, they shall not be included in the new Composite Instance. - + The new Composite Instance shall not be contained in a Concatenation. This means that it shall not contain a Concatenation UID (0020,9161) Attribute or other Concatenation Attributes. If the existing Composite Instance contains such Attributes, they shall not be included in the new Composite Instance. - The new Composite Instance contains - only one set of Attributes for the Image Pixel Module, hence the contents of the Image Pixel - Module shall either be identical in all source images, or the Pixel Data for each frame - shall be converted as necessary to match the Image Pixel Module of the new Composite - Instance. - + The new Composite Instance contains only one set of Attributes for the Image Pixel Module, hence the contents of the Image Pixel Module shall either be identical in all source images, or the Pixel Data for each frame shall be converted as necessary to match the Image Pixel Module of the new Composite Instance. - In particular this means - that the values of Rows, Columns, Bits Stored, Bits Allocated, High Bit, Pixel - Representation, Samples per Pixel, Photometric Interpretation and Planar - Configuration applicable to all of the frames needs to be the same. - In special cases, such as where Bits Stored is less than Bits Allocated but - varies per frame, it may be safe to use the largest value for all the frames and - ensure that any unused high bits are appropriately masked before encoding. - It is not expected that source images with different numbers of Rows and Columns - will be combined (by padding the periphery of images smaller than the largest); - quite apart from not being the intended use case, this has the potential to - greatly expand the size of the instance, and might also require adjustment of - the Image Position (Patient) values. - If the value of Photometric Interpretation in the source single frame images is - not permitted for the Enhanced Multi-frame image IOD, lossless conversion of the - PixelData and updating of the related Attributes is required, e.g., from - MONOCHROME1 to MONOCHROME2. - + In particular this means that the values of Rows, Columns, Bits Stored, Bits Allocated, High Bit, Pixel Representation, Samples per Pixel, Photometric Interpretation and Planar Configuration applicable to all of the frames needs to be the same. + In special cases, such as where Bits Stored is less than Bits Allocated but varies per frame, it may be safe to use the largest value for all the frames and ensure that any unused high bits are appropriately masked before encoding. + It is not expected that source images with different numbers of Rows and Columns will be combined (by padding the periphery of images smaller than the largest); quite apart from not being the intended use case, this has the potential to greatly expand the size of the instance, and might also require adjustment of the Image Position (Patient) values. + If the value of Photometric Interpretation in the source single frame images is not permitted for the Enhanced Multi-frame image IOD, lossless conversion of the PixelData and updating of the related Attributes is required, e.g., from MONOCHROME1 to MONOCHROME2. - Special attention should be - given to the Pixel Padding Value and associated Attributes, in case these vary - per frame in the source images, in which case the Pixel Data for some frames may - need to be modified to be consistent with all the other frames. - + Special attention should be given to the Pixel Padding Value and associated Attributes, in case these vary per frame in the source images, in which case the Pixel Data for some frames may need to be modified to be consistent with all the other frames. - It is possible to change - the Image Pixel Module Attributes related to compressed Transfer Syntaxes - (including lossy or irreversible compression) during conversion. - + It is possible to change the Image Pixel Module Attributes related to compressed Transfer Syntaxes (including lossy or irreversible compression) during conversion. - All mandatory Attributes of all - mandatory Modules and Functional Group Macros of the SOP Class of the new Composite Instance - shall be populated as required by the IOD. In this context, "mandatory" means either - required or conditional where the condition is satisfied. - + All mandatory Attributes of all mandatory Modules and Functional Group Macros of the SOP Class of the new Composite Instance shall be populated as required by the IOD. In this context, "mandatory" means either required or conditional where the condition is satisfied. - For example, if the source images - to be converted are of the CT Image Storage SOP Class, and the new Composite Instance is - of the Legacy Converted Enhanced CT Image Storage SOP Class, then it is required that - the Pixel Measures Functional Group be populated from Pixel Spacing, that the Plane - Position (Patient) Functional Group be populated from Image Position (Patient), etc. In - addition, if Body Part Examined is present in the source images with a standard value, - then the condition for the inclusion of the Frame Anatomy Functional Group is satisfied, - and the value therein needs to be converted to the appropriate Anatomic Region Sequence - code. - + For example, if the source images to be converted are of the CT Image Storage SOP Class, and the new Composite Instance is of the Legacy Converted Enhanced CT Image Storage SOP Class, then it is required that the Pixel Measures Functional Group be populated from Pixel Spacing, that the Plane Position (Patient) Functional Group be populated from Image Position (Patient), etc. In addition, if Body Part Examined is present in the source images with a standard value, then the condition for the inclusion of the Frame Anatomy Functional Group is satisfied, and the value therein needs to be converted to the appropriate Anatomic Region Sequence code. - All optional Attributes, Modules and - Functional Group Macros for which corresponding information is present in the source images - in Standard Attributes shall also be populated. - + All optional Attributes, Modules and Functional Group Macros for which corresponding information is present in the source images in Standard Attributes shall also be populated. - All Attributes of the Overlay Module - shall be removed and converted into a Grayscale or Color Softcopy Presentation State - (depending on the value of Photometric Interpretation); if the Overlay uses high bits in the - Pixel Data (7FE0,0010) these shall be extracted and encoded in Overlay Data (60xx,3000) in - the Presentation State and shall be set to zero in the Pixel Data (7FE0,0010) Attribute in - the converted image. - + All Attributes of the Overlay Module shall be removed and converted into a Grayscale or Color Softcopy Presentation State (depending on the value of Photometric Interpretation); if the Overlay uses high bits in the Pixel Data (7FE0,0010) these shall be extracted and encoded in Overlay Data (60xx,3000) in the Presentation State and shall be set to zero in the Pixel Data (7FE0,0010) Attribute in the converted image. - The extraction of Overlays from - multiple frames may lead to a proliferation of GSPS Instances (one per converted frame), - unless the converter recognizes commonality in the binary values of overlay bit planes - and factors it out into fewer GSPS objects that each apply to multiple frames. - + The extraction of Overlays from multiple frames may lead to a proliferation of GSPS Instances (one per converted frame), unless the converter recognizes commonality in the binary values of overlay bit planes and factors it out into fewer GSPS objects that each apply to multiple frames. - All Attributes of the Curve Module - (retired, but formerly defined in DICOM) shall be removed; they may be converted into a - Grayscale or Color Softcopy Presentation State (depending on the value of Photometric - Interpretation) or a Waveform as appropriate, but this is not required. - + All Attributes of the Curve Module (retired, but formerly defined in DICOM) shall be removed; they may be converted into a Grayscale or Color Softcopy Presentation State (depending on the value of Photometric Interpretation) or a Waveform as appropriate, but this is not required. - All Attributes of the Graphic - Annotation Sequence (0070,0001) (not defined in Classic image IODs, but sometimes used in a - Standard Extended SOP Class) shall be removed; they may be converted into a Grayscale or - Color Softcopy Presentation State (depending on the value of Photometric Interpretation), - but this is not required. - + All Attributes of the Graphic Annotation Sequence (0070,0001) (not defined in Classic image IODs, but sometimes used in a Standard Extended SOP Class) shall be removed; they may be converted into a Grayscale or Color Softcopy Presentation State (depending on the value of Photometric Interpretation), but this is not required. - All remaining Attributes in the source - images (i.e., those that have not been used to populate mandatory or optional Attributes in - Modules and Functional Groups), including Private Attributes, shall be copied into the - top-level Data Set or the Unassigned Shared Converted Attributes Sequence (0020,9170) if - they are present in all of the source images for the new Composite Instance, have the same - number of values, and have the same values, otherwise they shall be copied into the - Unassigned Per-Frame Converted Attributes Sequence (0020,9171). - + All remaining Attributes in the source images (i.e., those that have not been used to populate mandatory or optional Attributes in Modules and Functional Groups), including Private Attributes, shall be copied into the top-level Data Set or the Unassigned Shared Converted Attributes Sequence (0020,9170) if they are present in all of the source images for the new Composite Instance, have the same number of values, and have the same values, otherwise they shall be copied into the Unassigned Per-Frame Converted Attributes Sequence (0020,9171). - The semantics of Private - Attributes, or Standard Attributes used in a Standard Extended SOP Class, might not be - maintained, being unknown to the converting application; for example, referential - integrity of UIDs in Private Attributes might not be updated. - + The semantics of Private Attributes, or Standard Attributes used in a Standard Extended SOP Class, might not be maintained, being unknown to the converting application; for example, referential integrity of UIDs in Private Attributes might not be updated. - The new Composite Instance shall - contain references to the source Instances from which it was converted, encoded in the - Conversion Source Attributes Sequence (0020,9172) of the Image Frame Conversion Source - Functional Group Macro. - + The new Composite Instance shall contain references to the source Instances from which it was converted, encoded in the Conversion Source Attributes Sequence (0020,9172) of the Image Frame Conversion Source Functional Group Macro. - The specific requirements for the conversion of - Enhanced Multi-frame images to Classic single frame images are: - + The specific requirements for the conversion of Enhanced Multi-frame images to Classic single frame images are: - The SOP Class of the new Composite - Instance shall be the appropriate modality-specific (Classic) Image Storage SOP Class that - is intended for de novo creation by an acquisition or post-processing device. - + The SOP Class of the new Composite Instance shall be the appropriate modality-specific (Classic) Image Storage SOP Class that is intended for de novo creation by an acquisition or post-processing device. - For example, if the source images - to be converted are of the Enhanced CT Image Storage SOP Class or the Legacy Converted - Enhanced CT Image Storage SOP Class, then the new SOP Class is the CT Image Storage SOP - Class. - + For example, if the source images to be converted are of the Enhanced CT Image Storage SOP Class or the Legacy Converted Enhanced CT Image Storage SOP Class, then the new SOP Class is the CT Image Storage SOP Class. - All mandatory Attributes of the IOD of - the SOP Class of the new Composite Instance shall be populated. In this context, "mandatory" - means either required or conditional where the condition is satisfied. - + All mandatory Attributes of the IOD of the SOP Class of the new Composite Instance shall be populated. In this context, "mandatory" means either required or conditional where the condition is satisfied. - For example, if the source images - to be converted are of the Legacy Converted Enhanced CT Image Storage SOP Class, and the - new Composite Instance is of the CT Image Storage SOP Class, then it is required that - Pixel Spacing be populated from the Pixel Measures Functional Group, that Image Position - (Patient) be populated from the Plane Position (Patient) Functional Group, etc. - + For example, if the source images to be converted are of the Legacy Converted Enhanced CT Image Storage SOP Class, and the new Composite Instance is of the CT Image Storage SOP Class, then it is required that Pixel Spacing be populated from the Pixel Measures Functional Group, that Image Position (Patient) be populated from the Plane Position (Patient) Functional Group, etc. - All optional Attributes in Modules of - the IOD for which corresponding information is present in the source images shall also be - populated. - + All optional Attributes in Modules of the IOD for which corresponding information is present in the source images shall also be populated. - All remaining Attributes in the source - images (i.e., those that have not been used to populate mandatory or optional Attributes in - Modules), including Private Attributes, shall be copied from the top-level Data Set and the - Shared Functional Group Macro and the corresponding Item of the Per-Frame Functional Group - Macro into the top-level Data Set of the new Composite Instance, including those in the - Unassigned Shared Converted Attributes Sequence (0020,9170) and the corresponding Item of - the Unassigned Per-Frame Converted Attributes Sequence (0020,9171) (which will result in a - Standard Extended SOP Class). - + All remaining Attributes in the source images (i.e., those that have not been used to populate mandatory or optional Attributes in Modules), including Private Attributes, shall be copied from the top-level Data Set and the Shared Functional Group Macro and the corresponding Item of the Per-Frame Functional Group Macro into the top-level Data Set of the new Composite Instance, including those in the Unassigned Shared Converted Attributes Sequence (0020,9170) and the corresponding Item of the Unassigned Per-Frame Converted Attributes Sequence (0020,9171) (which will result in a Standard Extended SOP Class). - Identifying Attributes, - such as Series Number or Series Description, will be present in the Unassigned - functional groups, and UIDs will be present in the Conversion Source Attributes - Sequence, allowing, for example, the original Series organization to be - recovered, whether or not a single Series was previously converted into a single - Legacy Converted instance or it was split or merged with other Series. - + Identifying Attributes, such as Series Number or Series Description, will be present in the Unassigned functional groups, and UIDs will be present in the Conversion Source Attributes Sequence, allowing, for example, the original Series organization to be recovered, whether or not a single Series was previously converted into a single Legacy Converted instance or it was split or merged with other Series. - The integrity of the set of - Private Attributes recovered in this manner cannot be guaranteed to result in - the correct function of any applications that depend on them, but the - expectation is that this will be no better or worse than the impact of storing - instances with private Attributes on any Storage SCP that may or may not - reorganize and/or selectively preserve Private Attributes. - + The integrity of the set of Private Attributes recovered in this manner cannot be guaranteed to result in the correct function of any applications that depend on them, but the expectation is that this will be no better or worse than the impact of storing instances with private Attributes on any Storage SCP that may or may not reorganize and/or selectively preserve Private Attributes. - The new Composite Instance shall - contain references to the source Instances from which it was converted, encoded in the - Conversion Source Attributes Sequence (0020,9172) in the SOP Common Module. - + The new Composite Instance shall contain references to the source Instances from which it was converted, encoded in the Conversion Source Attributes Sequence (0020,9172) in the SOP Common Module. - The specific requirements for the conversion of - other instances are: - + The specific requirements for the conversion of other instances are: - The new Composite Instance shall be an - instance of the same SOP Class as the source Composite Instance. - + The new Composite Instance shall be an instance of the same SOP Class as the source Composite Instance. - The new Composite Instance shall - contain references to the source Instances from which it was converted, encoded in the - Conversion Source Attributes Sequence (0020,9172) in the SOP Common Module. - + The new Composite Instance shall contain references to the source Instances from which it was converted, encoded in the Conversion Source Attributes Sequence (0020,9172) in the SOP Common Module. @@ -10073,8 +7314,7 @@ True Enhanced @@ -10084,13 +7324,10 @@ CT Image Storage @@ -10098,13 +7335,10 @@ MR Image Storage @@ -10112,13 +7346,10 @@ PET Image Storage @@ -10127,9 +7358,7 @@
DIMSE-C Service Groups - Three DIMSE-C Services are used in the construction - of SOP Classes of the Query/Retrieve Service Class. The following DIMSE-C operations are used: - + Three DIMSE-C Services are used in the construction of SOP Classes of the Query/Retrieve Service Class. The following DIMSE-C operations are used: C-FIND @@ -10143,292 +7372,124 @@
C-FIND Operation - SCPs of some SOP Classes of the Query/Retrieve - Service Class may be capable of processing queries using the C-FIND operation as described in. The C-FIND operation - is the mechanism by which queries are performed. Matches against the keys present in the Identifier - are returned in C-FIND responses. - + SCPs of some SOP Classes of the Query/Retrieve Service Class may be capable of processing queries using the C-FIND operation as described in . The C-FIND operation is the mechanism by which queries are performed. Matches against the keys present in the Identifier are returned in C-FIND responses.
C-FIND Service Parameters
SOP Class UID - The SOP Class UID identifies the - Query/Retrieve Information Model against which the C-FIND is to be performed. Support for - the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by - this C-FIND operation. - + The SOP Class UID identifies the Query/Retrieve Information Model against which the C-FIND is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-FIND operation.
Priority - The Priority Attribute defines the - requested priority of the C-FIND operation with respect to other DIMSE operations being - performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. - + The Priority Attribute defines the requested priority of the C-FIND operation with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP.
Identifier - Both the C-FIND request and response - contain an Identifier encoded as a Data Set (see). - + Both the C-FIND request and response contain an Identifier encoded as a Data Set (see ). - The definition of a Data Set in - - specifically excludes the range of groups below group 0008, and this includes in - particular Meta Information Header elements such as Transfer Syntax UID (0002,0010). The - C-FIND request and identifier do not support a mechanism for ascertaining the manner in - which an SCP might have encoded a stored image whether it be by requesting Transfer - Syntax UID (0002,0010) or by any other mechanism. - + The definition of a Data Set in specifically excludes the range of groups below group 0008, and this includes in particular Meta Information Header elements such as Transfer Syntax UID (0002,0010). The C-FIND request and identifier do not support a mechanism for ascertaining the manner in which an SCP might have encoded a stored image whether it be by requesting Transfer Syntax UID (0002,0010) or by any other mechanism.
Request Identifier Structure - An Identifier in a C-FIND request - shall contain: - + An Identifier in a C-FIND request shall contain: - Key Attributes values to be - matched against the values of storage SOP Instances managed by the SCP. - + Key Attributes values to be matched against the values of storage SOP Instances managed by the SCP. - Query/Retrieve Level - (0008,0052), which defines the level of the query. - + Query/Retrieve Level (0008,0052), which defines the level of the query. - Conditionally, the - Attribute Query/Retrieve View (0008,0053). This Attribute may be included if - Enhanced Multi-Frame Image Conversion has been accepted during Association - Extended Negotiation. It shall not be included otherwise. - + Conditionally, the Attribute Query/Retrieve View (0008,0053). This Attribute may be included if Enhanced Multi-Frame Image Conversion has been accepted during Association Extended Negotiation. It shall not be included otherwise. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Request Identifier. It shall not be included otherwise. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Request Identifier. It shall not be included otherwise. - Conditionally, the - Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included - if Key Attributes of time are to be interpreted explicitly in the designated - local time zone. It shall not be present otherwise, i.e., it shall not be sent - with a zero-length value. - + Conditionally, the Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included if Key Attributes of time are to be interpreted explicitly in the designated local time zone. It shall not be present otherwise, i.e., it shall not be sent with a zero-length value. - The Key Attributes and values - allowable for the level of the query shall be defined in the SOP Class definition for - the Query/Retrieve Information Model. - + The Key Attributes and values allowable for the level of the query shall be defined in the SOP Class definition for the Query/Retrieve Information Model.
Response Identifier Structure - The C-FIND response shall not - contain Attributes that were not in the request or specified in this section. - - An Identifier in a C-FIND response - shall contain: - + The C-FIND response shall not contain Attributes that were not in the request or specified in this section. + An Identifier in a C-FIND response shall contain: - Key Attributes with values - corresponding to Key Attributes contained in the Identifier of the request. - + Key Attributes with values corresponding to Key Attributes contained in the Identifier of the request. - All Required - Keys in the Request Identifier, as well as all Optional Keys in the - Request Identifier that are supported by the SCP, will therefore be - present in the Response Identifier. - + All Required Keys in the Request Identifier, as well as all Optional Keys specified in the Information Model for the SOP Class (e.g., in , ) in the Request Identifier that are supported by the SCP, will therefore be present in the Response Identifier. - Required Keys - and supported Optional Keys in the Response Identifier will have - zero length if the SCP has no value to send; i.e., there is no - requirement that the SCP have a value for these, or create a dummy - value. - + Required Keys and supported Optional Keys in the Response Identifier will have zero length if the SCP has no value to send; i.e., there is no requirement that the SCP have a value for these, or create a dummy value. - The requirement - that unsupported Optional Keys present in the Request Identifier not - be included in the Response Identifier is specified in. - + The requirement that unsupported Optional Keys present in the Request Identifier not be included in the Response Identifier is specified in . - Private - Attributes present in the Request Identifier may be ignored by the - SCP if unrecognized (as defined for a - ), hence may or may not be present in the Response Identifier. - + Private Attributes present in the Request Identifier may be ignored by the SCP if unrecognized (as defined for a ), hence may or may not be present in the Response Identifier. - Query/Retrieve Level - (0008,0052), which defines the level of the query. The Query/Retrieve level - shall be equal to the level specified in the request. - + Query/Retrieve Level (0008,0052), which defines the level of the query. The Query/Retrieve level shall be equal to the level specified in the request. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Response Identifier. It shall not be included otherwise. The C-FIND SCP - is not required to return responses in the Specific Character Set requested by - the SCU if that character set is not supported by the SCP. The SCP may return - responses with a different Specific Character Set. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Response Identifier. It shall not be included otherwise. The C-FIND SCP is not required to return responses in the Specific Character Set requested by the SCU if that character set is not supported by the SCP. The SCP may return responses with a different Specific Character Set. - Conditionally, the - Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included - if any Attributes of time in the Response Identifier are to be interpreted - explicitly in the designated local time zone. It shall not be present otherwise, - i.e., it shall not be sent with a zero-length value. - + Conditionally, the Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included if any Attributes of time in the Response Identifier are to be interpreted explicitly in the designated local time zone. It shall not be present otherwise, i.e., it shall not be sent with a zero-length value. - The C-FIND SCP is required to - support either or both the Retrieve AE Title Data Element or the Storage Media File-Set - ID/Storage Media File Set UID Data Elements. An Identifier in a C-FIND response shall - contain: - + The C-FIND SCP is required to support either or both the Retrieve AE Title Data Element or the Storage Media File-Set ID/Storage Media File Set UID Data Elements. An Identifier in a C-FIND response shall contain: - Storage Media File-Set ID - (0088,0130), which defines a user or implementation specific human readable - Identifier that identifies the Storage Media on which the Composite Object - Instance(s); reside. This element pertains to the set of Composite Object - Instances available at the Query/Retrieve Level specified in the Identifier of - the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). - This Attribute shall be present if the Retrieve AE Title Data Element is not - present. A null value (Data Element length of 0) is valid for all levels except - the lowest level in the Information Model as defined by the SOP Class. - + Storage Media File-Set ID (0088,0130), which defines a user or implementation specific human readable Identifier that identifies the Storage Media on which the Composite Object Instance(s); reside. This element pertains to the set of Composite Object Instances available at the Query/Retrieve Level specified in the Identifier of the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). This Attribute shall be present if the Retrieve AE Title Data Element is not present. A null value (Data Element length of 0) is valid for all levels except the lowest level in the Information Model as defined by the SOP Class. - Storage Media File-Set UID - (0088,0140), which uniquely identifies the Storage Media on which the Composite - Object Instance(s) reside. This element pertains to the set of Composite Object - Instances available at the Query/Retrieve Level specified in the Identifier of - the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). - This Attribute shall be present if the Retrieve AE Title Data Element is not - present. A null value (Data Element length of 0) is valid for all levels except - the lowest level in the Information Model as defined by the SOP Class. - + Storage Media File-Set UID (0088,0140), which uniquely identifies the Storage Media on which the Composite Object Instance(s) reside. This element pertains to the set of Composite Object Instances available at the Query/Retrieve Level specified in the Identifier of the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). This Attribute shall be present if the Retrieve AE Title Data Element is not present. A null value (Data Element length of 0) is valid for all levels except the lowest level in the Information Model as defined by the SOP Class. - The File-Set concepts - are used in. - + The File-Set concepts are used in . - Retrieve AE Title - (0008,0054), which defines a list of DICOM Application Entity Title(s) that - identify the location from which the Composite Object Instance(s) may be - retrieved on the network. This element pertains to the set of Composite Object - Instances available at the Query/Retrieve Level specified in the Identifier of - the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). - This Attribute shall be present if the Storage Media File-Set ID and Storage - Media File-Set UID elements are not present. The Application Entity named in - this field shall support either the C-GET or C-MOVE SOP Class of the - Query/Retrieve Service Class. A null value (Data Element length of 0) is valid - for all levels except the lowest level in the Information Model as defined by - the SOP Class. - + Retrieve AE Title (0008,0054), which defines a list of DICOM Application Entity Title(s) that identify the location from which the Composite Object Instance(s) may be retrieved on the network. This element pertains to the set of Composite Object Instances available at the Query/Retrieve Level specified in the Identifier of the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). This Attribute shall be present if the Storage Media File-Set ID and Storage Media File-Set UID elements are not present. The Application Entity named in this field shall support either the C-GET or C-MOVE SOP Class of the Query/Retrieve Service Class. A null value (Data Element length of 0) is valid for all levels except the lowest level in the Information Model as defined by the SOP Class. - For example, a - DICOM AE with the AE Title of "A" performs a C-FIND request to a - DICOM AE with the AE Title of "B" with the Query/Retrieve level set - to "STUDY". DICOM AE "B" determines that the Composite Object - Instances for each matching study may be retrieved by itself and - sets the Data Element Retrieve AE Title to "B". - + For example, a DICOM AE with the AE Title of "A" performs a C-FIND request to a DICOM AE with the AE Title of "B" with the Query/Retrieve level set to "STUDY". DICOM AE "B" determines that the Composite Object Instances for each matching study may be retrieved by itself and sets the Data Element Retrieve AE Title to "B". - File-Sets may - not be defined at every Query/Retrieve Level. If the SCP supports - the File-Set ID/File-Set UID option but does not define these - Attributes at the Query/Retrieve Level specified in the C-FIND - request it may return these Data Elements with a length of 0 to - signify that the value is unknown. An SCU should reissue a C-FIND at - a Query/Retrieve Level lower in the hierarchy. - + File-Sets may not be defined at every Query/Retrieve Level. If the SCP supports the File-Set ID/File-Set UID option but does not define these Attributes at the Query/Retrieve Level specified in the C-FIND request it may return these Data Elements with a length of 0 to signify that the value is unknown. An SCU should reissue a C-FIND at a Query/Retrieve Level lower in the hierarchy. - The fact that - the value of the Key Attribute is unknown to the SCP of the - Query/Retrieve Service Class does not imply that it is not present - in the underlying Information Object. Thus, a subsequent retrieval - may cause a Storage of a SOP Instance that contains the value of the - Attribute. - + The fact that the value of the Key Attribute is unknown to the SCP of the Query/Retrieve Service Class does not imply that it is not present in the underlying Information Object. Thus, a subsequent retrieval may cause a Storage of a SOP Instance that contains the value of the Attribute. - The C-FIND SCP may also, but is not - required to, support the Instance Availability (0008,0056) Data Element. This Data - Element shall not be included in a C-FIND request. An Identifier in a C-FIND response - may contain: - + The C-FIND SCP may also, but is not required to, support the Instance Availability (0008,0056) Data Element. This Data Element shall not be included in a C-FIND request. An Identifier in a C-FIND response may contain: - Instance Availability - (0008,0056), which defines how rapidly Composite Object Instance(s); become - available for transmission after a C-MOVE or C-GET retrieval request. This - element pertains to the set of Composite Object Instances available at the - Query/Retrieve Level specified in the Identifier of the C-FIND request (e.g., - Patient, Study, Series, Composite Object Instance). When some composite - instances are less rapidly available than others, the availability of the least - rapidly available shall be returned. If this Data Element is not returned, the - availability is unknown or unspecified. A null value (Data Element length of 0) - is not permitted. The Enumerated Values for this Data Element are: - + Instance Availability (0008,0056), which defines how rapidly Composite Object Instance(s); become available for transmission after a C-MOVE or C-GET retrieval request. This element pertains to the set of Composite Object Instances available at the Query/Retrieve Level specified in the Identifier of the C-FIND request (e.g., Patient, Study, Series, Composite Object Instance). When some composite instances are less rapidly available than others, the availability of the least rapidly available shall be returned. If this Data Element is not returned, the availability is unknown or unspecified. A null value (Data Element length of 0) is not permitted. The Enumerated Values for this Data Element are: - "ONLINE", which - means the instances are immediately available, - + "ONLINE", which means the instances are immediately available, - "NEARLINE", which - means the instances need to be retrieved from relatively slow media such - as optical disk or tape, or require conversion that takes time, - + "NEARLINE", which means the instances need to be retrieved from relatively slow media such as optical disk or tape, or require conversion that takes time, - "OFFLINE", which - means the instances need to be retrieved by manual intervention, - + "OFFLINE", which means the instances need to be retrieved by manual intervention, - "UNAVAILABLE", - which means the instances cannot be retrieved. Note that SOP Instances - that are unavailable may have an alternate representation that is - available (see). - + "UNAVAILABLE", which means the instances cannot be retrieved. Note that SOP Instances that are unavailable may have an alternate representation that is available (see ). @@ -10438,11 +7499,7 @@
Status - - defines the specific status code values that might be returned in a C-FIND response. General - status code values and fields related to status code values are defined for C-FIND DIMSE - Service in. - + defines the specific status code values that might be returned in a C-FIND response. General status code values and fields related to status code values are defined for C-FIND DIMSE Service in .
- Legacy Converted Enhanced - + Legacy Converted Enhanced
- Enhanced CT Image Storage - + Enhanced CT Image Storage - Legacy Converted Enhanced CT - Image Storage - + Legacy Converted Enhanced CT Image Storage
- Enhanced MR Image Storage - + Enhanced MR Image Storage - Legacy Converted Enhanced MR - Image Storage - + Legacy Converted Enhanced MR Image Storage
- Enhanced PET Image Storage - + Enhanced PET Image Storage - Legacy Converted Enhanced PET - Image Storage - + Legacy Converted Enhanced PET Image Storage
@@ -10467,9 +7524,7 @@ Failure
C-FIND Response Status Values
- Refused: Out of - resources - + Refused: Out of resources A700 @@ -10480,9 +7535,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -10494,9 +7547,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -10511,9 +7562,7 @@ Cancel - Matching terminated due - to Cancel request - + Matching terminated due to Cancel request FE00 @@ -10527,9 +7576,7 @@ Success - Matching is complete - - No final Identifier is supplied. - + Matching is complete - No final Identifier is supplied. 0000 @@ -10543,10 +7590,7 @@ Pending - Matches are continuing - - Current Match is supplied and any Optional Keys were supported in the same - manner as Required Keys. - + Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF00 @@ -10557,10 +7601,7 @@
- Matches are continuing - - Warning that one or more Optional Keys were not supported for existence - and/or matching for this Identifier. - + Matches are continuing - Warning that one or more Optional Keys were not supported for existence and/or matching for this Identifier. FF01 @@ -10571,190 +7612,84 @@
- Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: - Unable to process” Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: Unable to process” Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
C-FIND SCU Behavior - This Section discusses both the baseline - and extended behavior of the C-FIND SCU. - + This Section discusses both the baseline and extended behavior of the C-FIND SCU.
Baseline Behavior of SCU - All C-FIND SCUs shall be capable of - generating query requests that meet the requirements of the Hierarchical Search. - - The Identifier contained in a C-FIND - request shall contain a single value in the Unique Key Attribute for each level above the - Query/Retrieve level. No Required or Optional Keys shall be specified that are associated - with levels above the Query/Retrieve level. - - The Unique Key Attribute associated - with the Query/Retrieve level shall be contained in the C-FIND request and may specify - Single Value Matching, Universal Value Matching, or List of UID Matching. In addition, - Required and Optional Keys associated with the Query/Retrieve level may be contained in the - Identifier. - - An SCU conveys the following semantics - using the C-FIND request: - + All C-FIND SCUs shall be capable of generating query requests that meet the requirements of the Hierarchical Search. + The Identifier contained in a C-FIND request shall contain a single value in the Unique Key Attribute for each level above the Query/Retrieve level. No Required or Optional Keys shall be specified that are associated with levels above the Query/Retrieve level. + The Unique Key Attribute associated with the Query/Retrieve level shall be contained in the C-FIND request and may specify Single Value Matching, Universal Value Matching, or List of UID Matching. In addition, Required and Optional Keys associated with the Query/Retrieve level may be contained in the Identifier. + An SCU conveys the following semantics using the C-FIND request: - The SCU requests that the SCP - perform a match of all keys specified in the Identifier of the request against the - information it possesses down to the Query/Retrieve level specified in the request. - + The SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information it possesses down to the Query/Retrieve level specified in the request. - The SCU may not - assume the SCP supports any Optional Keys. Hence, Optional Keys serve - only to reduce network related overhead when they are supported by the - SCP. - + The SCU may not assume the SCP supports any Optional Keys. Hence, Optional Keys serve only to reduce network related overhead when they are supported by the SCP. - The SCU must be - prepared to filter C-FIND responses when the SCP fails to support an - Optional Key specified in the C-FIND request. - + The SCU must be prepared to filter C-FIND responses when the SCP fails to support an Optional Key specified in the C-FIND request. - The SCU shall interpret Pending - responses to convey the Attributes of a match of an Entity at the level of the - query. - + The SCU shall interpret Pending responses to convey the Attributes of a match of an Entity at the level of the query. - The SCU shall interpret a - response with a status equal to Success, Failed or Refused to convey the end of - Pending responses. - + The SCU shall interpret a response with a status equal to Success, Failed or Refused to convey the end of Pending responses. - The SCU shall interpret a - Refused or Failed response to a C-FIND request as an indication that the SCP is - unable to process the request. - + The SCU shall interpret a Refused or Failed response to a C-FIND request as an indication that the SCP is unable to process the request. - The SCU may cancel the C-FIND - service by issuing a C-FIND-CANCEL request at any time during the processing of the - C-FIND. The SCU shall recognize a status of Canceled to indicate that the - C-FIND-CANCEL was successful. - + The SCU may cancel the C-FIND service by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND. The SCU shall recognize a status of Canceled to indicate that the C-FIND-CANCEL was successful.
Extended Behavior of SCU - Extended SCU behavior shall be - negotiated at Association establishment time. If an option within the extended behavior is - not agreed upon in the negotiation, then only baseline SCU behavior shall be performed with - respect to that option. Extended SCU behavior includes all baseline behavior with the - following option: - + Extended SCU behavior shall be negotiated at Association establishment time. If an option within the extended behavior is not agreed upon in the negotiation, then only baseline SCU behavior shall be performed with respect to that option. Extended SCU behavior includes all baseline behavior with the following option: Relational-queries - Enhanced Multi-Frame Image - Conversion - + Enhanced Multi-Frame Image Conversion - More than one option may be agreed - upon. - + More than one option may be agreed upon.
Relational-Queries - The C-FIND Service with - relational-queries allows any combination of keys at any level in the hierarchy. The - Unique Key Attribute associated with the Query/Retrieve level shall be contained in the - C-FIND request and may specify Single Value Matching, Universal Value Matching, or List - of UID Matching. Support for relational-queries removes the baseline restriction that a - Unique Key shall be specified for all levels above the Query/Retrieve level in the - C-FIND request. - + The C-FIND Service with relational-queries allows any combination of keys at any level in the hierarchy. The Unique Key Attribute associated with the Query/Retrieve level shall be contained in the C-FIND request and may specify Single Value Matching, Universal Value Matching, or List of UID Matching. Support for relational-queries removes the baseline restriction that a Unique Key shall be specified for all levels above the Query/Retrieve level in the C-FIND request.
Enhanced Multi-Frame Image Conversion - The C-FIND Service with Enhanced - Multi-Frame Image Conversion allows for selection of the default or an alternative view - of the instances represented by the Information Model. - - Support for Enhanced Multi-Frame - Image Conversion allows the SCU to specify the Query/Retrieve View (0008,0053) in the - Request Identifier with a value of either "CLASSIC" or "ENHANCED". - - If Query/Retrieve View (0008,0053) - is not present in the Request Identifier, then the SCU requests that the SCP perform a - match of all keys specified in the Identifier of the request against the information - about the instances that it possesses, as received. - - If Query/Retrieve View (0008,0053) - is present with a value of "CLASSIC", then the SCU requests that the SCP perform a match - of all keys specified in the Identifier of the request against the information about - Classic single frame Instances (converted from Enhanced multi-frame Instances if - required), as well as any instances that were converted to preserve referential - integrity, and any that did not need to be converted. - - If Query/Retrieve View (0008,0053) - is present with a value of "ENHANCED", then the SCU requests that the SCP perform a - match of all keys specified in the Identifier of the request against the information - about Enhanced multi-frame Instances (converted from Classic single frame Instances if - required), as well as any instances that were converted to preserve referential - integrity, and any that did not need to be converted. - + The C-FIND Service with Enhanced Multi-Frame Image Conversion allows for selection of the default or an alternative view of the instances represented by the Information Model. + Support for Enhanced Multi-Frame Image Conversion allows the SCU to specify the Query/Retrieve View (0008,0053) in the Request Identifier with a value of either "CLASSIC" or "ENHANCED". + If Query/Retrieve View (0008,0053) is not present in the Request Identifier, then the SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information about the instances that it possesses, as received. + If Query/Retrieve View (0008,0053) is present with a value of "CLASSIC", then the SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information about Classic single frame Instances (converted from Enhanced multi-frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. + If Query/Retrieve View (0008,0053) is present with a value of "ENHANCED", then the SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information about Enhanced multi-frame Instances (converted from Classic single frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. - The SCU may assume that - no duplicate information will be returned. For example, if an entire series - of single frame instances can be converted to a separate series of converted - instances, a STUDY level C-FIND will not return both series. - + The SCU may assume that no duplicate information will be returned. For example, if an entire series of single frame instances can be converted to a separate series of converted instances, a STUDY level C-FIND will not return both series. - The Query Information - Model is unchanged, and the same unique, required and optional keys are - equally applicable to both views, except that the values for the SERIES and - IMAGE level queries will be different and will depend on the converted - instance content. - + The Query Information Model is unchanged, and the same unique, required and optional keys are equally applicable to both views, except that the values for the SERIES and IMAGE level queries will be different and will depend on the converted instance content. - Unconverted instances, - such as for other modalities like Ultrasound, will appear identical - regardless of view. - + Unconverted instances, such as for other modalities like Ultrasound, will appear identical regardless of view. - Implementations may - apply performance optimizations, such as pre-computing or caching the - potential information against which CLASSIC and ENHANCED queries may be - performed, in order to minimize significant delays between the query request - and response caused by converting "on demand", but SCUs may need to consider - the potential for a delayed response when configuring timeouts, etc. - + Implementations may apply performance optimizations, such as pre-computing or caching the potential information against which CLASSIC and ENHANCED queries may be performed, in order to minimize significant delays between the query request and response caused by converting "on demand", but SCUs may need to consider the potential for a delayed response when configuring timeouts, etc. @@ -10763,109 +7698,51 @@
C-FIND SCP Behavior - This Section discusses both the baseline - and extended behavior of the C-FIND SCP. - + This Section discusses both the baseline and extended behavior of the C-FIND SCP.
Baseline Behavior of SCP - All C-FIND SCPs shall be capable of - processing queries that meet the requirements of the Hierarchical Search. - - An SCP conveys the following semantics - with a C-FIND response: - + All C-FIND SCPs shall be capable of processing queries that meet the requirements of the Hierarchical Search. + An SCP conveys the following semantics with a C-FIND response: - The SCP is requested to perform - a match of all the keys specified in the Identifier of the request, against the - information it possesses, to the level specified in the request. Attribute matching - is performed using the key values specified in the Identifier of the C-FIND request - as defined in. - + The SCP is requested to perform a match of all the keys specified in the Identifier of the request, against the information it possesses, to the level specified in the request. Attribute matching is performed using the key values specified in the Identifier of the C-FIND request as defined in . - The SCP generates a C-FIND - response for each match using the Hierarchical Search method. All such responses - shall contain an Identifier whose Attributes contain values from a single match. All - such responses shall contain a status of Pending. - + The SCP generates a C-FIND response for each match using the Hierarchical Search method. All such responses shall contain an Identifier whose Attributes contain values from a single match. All such responses shall contain a status of Pending. - When all matches have been - sent, the SCP generates a C-FIND response that contains a status of Success. A - status of Success shall indicate that a response has been sent for each match known - to the SCP. - + When all matches have been sent, the SCP generates a C-FIND response that contains a status of Success. A status of Success shall indicate that a response has been sent for each match known to the SCP. - When there are no matches, - then no responses with a status of Pending are sent, only a single response with - a status of Success. - + When there are no matches, then no responses with a status of Pending are sent, only a single response with a status of Success. - The SCP shall generate a - response with a status of Refused or Failed if it is unable to process the request. - A Refused or Failed response shall contain no Identifier. - + The SCP shall generate a response with a status of Refused or Failed if it is unable to process the request. A Refused or Failed response shall contain no Identifier. - If the SCP receives - C-FIND-CANCEL indication before it has completed the processing of the matches it - shall interrupt the matching process and return a status of Canceled. - + If the SCP receives C-FIND-CANCEL indication before it has completed the processing of the matches it shall interrupt the matching process and return a status of Canceled. - If the SCP manages images in - multiple alternate encodings (see), only one of the - alternate encodings of an image shall be included in the set of matches for a C-FIND - request at the Instance level. - + If the SCP manages images in multiple alternate encodings (see ), only one of the alternate encodings of an image shall be included in the set of matches for a C-FIND request at the Instance level. - For query of images with - alternate encodings, the SCP may select the appropriately encoded Instance for - the request response based on identity of the SCU or other factors. - + For query of images with alternate encodings, the SCP may select the appropriately encoded Instance for the request response based on identity of the SCU or other factors.
Hierarchical Search Method - Starting at the top level in the - Query/Retrieve Information Model, continuing until the level specified in the C-FIND - request is reached, the following procedures are used to generate matches: - + Starting at the top level in the Query/Retrieve Information Model, continuing until the level specified in the C-FIND request is reached, the following procedures are used to generate matches: - If the current level is the - level specified in the C-FIND request, then the key match strings contained in - the Identifier of the C-FIND request are matched against the values of the Key - Attributes for each entity at the current level. For each entity for which the - Attributes match all of the specified match strings, construct an Identifier. - This Identifier shall contain all of the Unique Keys at higher levels and all of - the values of the Attributes for this entity that match those in the C-FIND - request. Return a response for each such Identifier. If there are no matching - keys, then there are no matches, return a response with a status equal to - Success and with no Identifier. - + If the current level is the level specified in the C-FIND request, then the key match strings contained in the Identifier of the C-FIND request are matched against the values of the Key Attributes for each entity at the current level. For each entity for which the Attributes match all of the specified match strings, construct an Identifier. This Identifier shall contain all of the Unique Keys at higher levels and all of the values of the Attributes for this entity that match those in the C-FIND request. Return a response for each such Identifier. If there are no matching keys, then there are no matches, return a response with a status equal to Success and with no Identifier. - Otherwise, if the current - level is not the level specified in the C-FIND request and there is an entity - matching the Unique Key Attribute Value for this level specified in the C-FIND - request, perform this procedure at the next level down in the hierarchy. - + Otherwise, if the current level is not the level specified in the C-FIND request and there is an entity matching the Unique Key Attribute Value for this level specified in the C-FIND request, perform this procedure at the next level down in the hierarchy. - Otherwise there are no - matches; return a response with a status equal to Success. - + Otherwise there are no matches; return a response with a status equal to Success. - The above description - specifies a recursive procedure. It may recur upon itself multiple times as - it goes down the hierarchical levels, but at each level it recurs only once. - + The above description specifies a recursive procedure. It may recur upon itself multiple times as it goes down the hierarchical levels, but at each level it recurs only once. @@ -10873,151 +7750,67 @@
Extended Behavior of SCP - Extended SCP behavior shall be - negotiated at Association establishment time. If an option within the extended behavior is - not agreed upon in the negotiation, then only baseline SCP behavior shall be performed with - respect to that option. Extended SCP behavior includes all baseline behavior with the - following option: - + Extended SCP behavior shall be negotiated at Association establishment time. If an option within the extended behavior is not agreed upon in the negotiation, then only baseline SCP behavior shall be performed with respect to that option. Extended SCP behavior includes all baseline behavior with the following option: Relational-queries - Enhanced Multi-Frame Image - Conversion - + Enhanced Multi-Frame Image Conversion - More than one option may be agreed - upon. - + More than one option may be agreed upon.
Relational-Queries - The C-FIND Service with - relational-queries allows any combination of keys at any level in the hierarchy. At the - lowest level, a query using the relational-queries shall contain the Unique Key for that - level with either a Single Value Match, a Wild Card Match, or a Universal Match. Support - for relational-queries removes the baseline restriction that a Unique Key shall be - specified for all levels above the Query/Retrieve level in the C-FIND request. - - The C-FIND SCP shall perform - matching based on all keys specified in the C-FIND request regardless of the - Query/Retrieve level. - + The C-FIND Service with relational-queries allows any combination of keys at any level in the hierarchy. At the lowest level, a query using the relational-queries shall contain the Unique Key for that level with either a Single Value Match, a Wild Card Match, or a Universal Match. Support for relational-queries removes the baseline restriction that a Unique Key shall be specified for all levels above the Query/Retrieve level in the C-FIND request. + The C-FIND SCP shall perform matching based on all keys specified in the C-FIND request regardless of the Query/Retrieve level.
Relational Search Method - A query using the relational method - may contain any combination of keys at any level in the hierarchy. Starting at the top - level in the Query/Retrieve Information Model, continuing until the Query/Retrieve level - specified in the C-FIND request is reached, the following procedures are used to - generate matches: - + A query using the relational method may contain any combination of keys at any level in the hierarchy. Starting at the top level in the Query/Retrieve Information Model, continuing until the Query/Retrieve level specified in the C-FIND request is reached, the following procedures are used to generate matches: - The key match strings - contained in the Identifier of the C-FIND request are matched against the values - of the Key Attributes for each entity at the current level. - + The key match strings contained in the Identifier of the C-FIND request are matched against the values of the Key Attributes for each entity at the current level. - If no Key Attribute is - specified at the current level and the current level is not the level specified - in the C-FIND request, the match shall be performed as if a wild card were - specified for the Unique Key Attribute for the current level (i.e., all entities - at the current level shall match). - + If no Key Attribute is specified at the current level and the current level is not the level specified in the C-FIND request, the match shall be performed as if a wild card were specified for the Unique Key Attribute for the current level (i.e., all entities at the current level shall match). - If the current level is the - level specified in the C-FIND request, then for each matching entity (a matching - entity is one for which the Attributes match all of the specified match strings - in the Key Attributes), construct an Identifier. This Identifier shall contain - all of the Attributes generated by this procedure at higher levels on this - recursion path and all of the values of the Key Attributes for this entity that - match those in the C-FIND request. - + If the current level is the level specified in the C-FIND request, then for each matching entity (a matching entity is one for which the Attributes match all of the specified match strings in the Key Attributes), construct an Identifier. This Identifier shall contain all of the Attributes generated by this procedure at higher levels on this recursion path and all of the values of the Key Attributes for this entity that match those in the C-FIND request. - Otherwise, if the current - level is not the level specified in the C-FIND request, then for each matching - entity construct a list of Attributes containing all of the matching Key - Attributes and all Attributes that were prepared at the previous level for this - entity. Then perform this procedure at the next level down in the hierarchy for - each matching entity. - + Otherwise, if the current level is not the level specified in the C-FIND request, then for each matching entity construct a list of Attributes containing all of the matching Key Attributes and all Attributes that were prepared at the previous level for this entity. Then perform this procedure at the next level down in the hierarchy for each matching entity. - Otherwise, if there are no - matches, return a response with status equal to Success and no Identifier. - + Otherwise, if there are no matches, return a response with status equal to Success and no Identifier. - The above description - specifies a recursive procedure. It may recur upon itself multiple times as - it goes down the hierarchical levels, and at each level, it may recur - multiple times (one for each matching entity). This may result in a large - number of Identifiers being generated. - + The above description specifies a recursive procedure. It may recur upon itself multiple times as it goes down the hierarchical levels, and at each level, it may recur multiple times (one for each matching entity). This may result in a large number of Identifiers being generated. - It is not required that - the above defined procedure be used to generate matches. It is expected that - implementations will incorporate different algorithms for performing - searches of the databases. For a given query, the set of matches shall be - equivalent to that which would be generated by the above procedure. - + It is not required that the above defined procedure be used to generate matches. It is expected that implementations will incorporate different algorithms for performing searches of the databases. For a given query, the set of matches shall be equivalent to that which would be generated by the above procedure.
Enhanced Multi-Frame Image Conversion - If Query/Retrieve View (0008,0053) - is not present in the Request Identifier, then the SCP shall perform a match of all keys - specified in the Identifier of the request against the information about the instances - that it possesses, as received. - - If Query/Retrieve View (0008,0053) - is present with a value of "CLASSIC", then the SCP shall perform a match of all keys - specified in the Identifier of the request against the information about Classic single - frame Instances (converted from Enhanced multi-frame Instances if required), as well as - any instances that were converted to preserve referential integrity, and any that did - not need to be converted. - - If Query/Retrieve View (0008,0053) - is present with a value of "ENHANCED", then the SCP shall perform a match of all keys - specified in the Identifier of the request against the information about Enhanced - multi-frame Instances (converted from Classic single frame Instances if required), as - well as any instances that were converted to preserve referential integrity, and any - that did not need to be converted. - + If Query/Retrieve View (0008,0053) is not present in the Request Identifier, then the SCP shall perform a match of all keys specified in the Identifier of the request against the information about the instances that it possesses, as received. + If Query/Retrieve View (0008,0053) is present with a value of "CLASSIC", then the SCP shall perform a match of all keys specified in the Identifier of the request against the information about Classic single frame Instances (converted from Enhanced multi-frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. + If Query/Retrieve View (0008,0053) is present with a value of "ENHANCED", then the SCP shall perform a match of all keys specified in the Identifier of the request against the information about Enhanced multi-frame Instances (converted from Classic single frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. - The SCP will not return - information that is duplicated. For example, if an entire series of single - frame instances can be converted to a separate series of converted - instances, a STUDY level C-FIND will not return both series. - + The SCP will not return information that is duplicated. For example, if an entire series of single frame instances can be converted to a separate series of converted instances, a STUDY level C-FIND will not return both series. - The Query Information - Model is unchanged, and the same unique, required and optional keys are - equally applicable to both views, except that the values for the SERIES and - IMAGE level queries will be different and will depend on the converted - instance content. - + The Query Information Model is unchanged, and the same unique, required and optional keys are equally applicable to both views, except that the values for the SERIES and IMAGE level queries will be different and will depend on the converted instance content. - Unconverted instances, - such as for other modalities like Ultrasound, will appear identical - regardless of view. - + Unconverted instances, such as for other modalities like Ultrasound, will appear identical regardless of view. @@ -11027,146 +7820,70 @@
C-MOVE Operation - SCUs of some SOP Classes of the Query/Retrieve - Service Class may generate retrievals using the C-MOVE operation as described in. The C-MOVE operation - allows an application entity to instruct another application entity to transfer stored SOP Instances - to another application entity using the C-STORE operation. Support for the C-MOVE service shall be - agreed upon at Association establishment time by both the SCU and SCP of the C-MOVE in order for a - C-MOVE operation to occur over the Association. The C-STORE sub-operations shall always be - accomplished over an Association different from the Association that accomplishes the C-MOVE - operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage - Service Class. - + SCUs of some SOP Classes of the Query/Retrieve Service Class may generate retrievals using the C-MOVE operation as described in . The C-MOVE operation allows an application entity to instruct another application entity to transfer stored SOP Instances to another application entity using the C-STORE operation. Support for the C-MOVE service shall be agreed upon at Association establishment time by both the SCU and SCP of the C-MOVE in order for a C-MOVE operation to occur over the Association. The C-STORE sub-operations shall always be accomplished over an Association different from the Association that accomplishes the C-MOVE operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage Service Class. - The application entity that receives the - stored SOP Instances may or may not be the originator of the C-MOVE operation. - + The application entity that receives the stored SOP Instances may or may not be the originator of the C-MOVE operation. - A C-MOVE request may be performed to any level - of the Query/Retrieve Information Model. However, the transfer of stored SOP Instances may not be - performed at this level. The level at which the transfer is performed depends upon the SOP Class - (see). - + A C-MOVE request may be performed to any level of the Query/Retrieve Information Model. However, the transfer of stored SOP Instances may not be performed at this level. The level at which the transfer is performed depends upon the SOP Class (see ).
C-MOVE Service Parameters
SOP Class UID - The SOP Class UID identifies the - Query/Retrieve Information Model against which the C-MOVE is to be performed. Support for - the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by - this C-MOVE operation. - + The SOP Class UID identifies the Query/Retrieve Information Model against which the C-MOVE is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-MOVE operation.
Priority - The Priority Attribute defines the - requested priority of the C-MOVE operation and corresponding C-STORE sub-operations with - respect to other DIMSE operations being performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. The same - priority shall be used for all C-STORE sub-operations. - + The Priority Attribute defines the requested priority of the C-MOVE operation and corresponding C-STORE sub-operations with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP. The same priority shall be used for all C-STORE sub-operations.
Move Destination - Move Destination specifies the - Application Entity Title of the receiver of the C-STORE sub-operations. - + Move Destination specifies the Application Entity Title of the receiver of the C-STORE sub-operations.
Identifier - The C-MOVE request shall contain an - Identifier. The C-MOVE response shall conditionally contain an Identifier as required in - . - + The C-MOVE request shall contain an Identifier. The C-MOVE response shall conditionally contain an Identifier as required in . - The Identifier is specified as U in - the definition of the C-MOVE primitive in - - but is specialized for use with this service. - + The Identifier is specified as U in the definition of the C-MOVE primitive in but is specialized for use with this service.
Request Identifier Structure - An Identifier in a C-MOVE request - shall contain: - + An Identifier in a C-MOVE request shall contain: - Query/Retrieve Level - (0008,0052), which defines the level of the retrieval - + Query/Retrieve Level (0008,0052), which defines the level of the retrieval - Unique Key Attributes, - which may include Patient ID (0010,0020), Study Instance UIDs (0020,000D), - Series Instance UIDs (0020,000E), and the SOP Instance UIDs (0008,0018) - + Unique Key Attributes, which may include Patient ID (0010,0020), Study Instance UIDs (0020,000D), Series Instance UIDs (0020,000E), and the SOP Instance UIDs (0008,0018) - Conditionally, the - Attribute Query/Retrieve View (0008,0053). This Attribute may be included if - Enhanced Multi-Frame Image Conversion has been accepted during Association - Extended Negotiation. It shall not be included otherwise. - + Conditionally, the Attribute Query/Retrieve View (0008,0053). This Attribute may be included if Enhanced Multi-Frame Image Conversion has been accepted during Association Extended Negotiation. It shall not be included otherwise. - Specific Character Set (0008,0005) - shall be present if Patient ID (0010,0020) is using a character set other than the - Default Character Repertoire. - - The Unique Keys at each level of - the hierarchy and the values allowable for the level of the retrieval shall be defined - in the SOP Class definition for the Query/Retrieve Information Model. - + Specific Character Set (0008,0005) shall be present if Patient ID (0010,0020) is using a character set other than the Default Character Repertoire. + The Unique Keys at each level of the hierarchy and the values allowable for the level of the retrieval shall be defined in the SOP Class definition for the Query/Retrieve Information Model. - In the non-Relational - behavior, more than one entity may be retrieved if the Query/Retrieve Level - is IMAGE, SERIES or STUDY, using List of UID matching, but only Single Value - Matching value may be specified for Patient ID (0010,0020). - + In the non-Relational behavior, more than one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using List of UID matching, but only Single Value Matching value may be specified for Patient ID (0010,0020). - The issuer of the - Patient ID (0010,0020) is implicit; there is no provision to send the Issuer - of Patient ID (0010,0021). When there is a possibility of ambiguity of the - Patient ID (0010,0020) value, a STUDY level retrieval should be used instead - of a PATIENT level retrieval. - + The issuer of the Patient ID (0010,0020) is implicit; there is no provision to send the Issuer of Patient ID (0010,0021). When there is a possibility of ambiguity of the Patient ID (0010,0020) value, a STUDY level retrieval should be used instead of a PATIENT level retrieval.
Response Identifier Structure - The Failed SOP Instance UID List - (0008,0058) specifies a list of UIDs of the C-STORE sub-operation SOP Instances for - which this C-MOVE operation has failed. An Identifier in a C-MOVE response shall - conditionally contain the Failed SOP Instance UID List (0008,0058) based on the C-MOVE - response status value. If no C-STORE sub-operation failed, Failed SOP Instance UID List - (0008,0058) is absent and therefore no Data Set shall be sent in the C-MOVE response. - - Specific Character Set (0008,0005) - shall not be present. - - The Identifier in a C-MOVE response - with a status of: - + The Failed SOP Instance UID List (0008,0058) specifies a list of UIDs of the C-STORE sub-operation SOP Instances for which this C-MOVE operation has failed. An Identifier in a C-MOVE response shall conditionally contain the Failed SOP Instance UID List (0008,0058) based on the C-MOVE response status value. If no C-STORE sub-operation failed, Failed SOP Instance UID List (0008,0058) is absent and therefore no Data Set shall be sent in the C-MOVE response. + Specific Character Set (0008,0005) shall not be present. + The Identifier in a C-MOVE response with a status of: - Canceled, Failure, Refused, - or Warning shall contain the Failed SOP Instance UID List Attribute - + Canceled, Failure, Refused, or Warning shall contain the Failed SOP Instance UID List Attribute - Pending shall not contain - the Failed SOP Instance UID List Attribute (no Data Set) - + Pending shall not contain the Failed SOP Instance UID List Attribute (no Data Set)
@@ -11174,11 +7891,7 @@
Status - - defines the specific status code values that might be returned in a C-MOVE response. General - status code values and fields related to status code values are defined for C-MOVE DIMSE - Service in. - + defines the specific status code values that might be returned in a C-MOVE response. General status code values and fields related to status code values are defined for C-MOVE DIMSE Service in . @@ -11203,9 +7916,7 @@ Failure
C-MOVE Response Status Values
- Refused: Out of - resources - Unable to calculate number of matches - + Refused: Out of resources - Unable to calculate number of matches A701 @@ -11216,9 +7927,7 @@
- Refused: Out of - resources - Unable to perform sub-operations - + Refused: Out of resources - Unable to perform sub-operations A702 @@ -11231,9 +7940,7 @@
- Refused: Move - Destination unknown - + Refused: Move Destination unknown A801 @@ -11244,9 +7951,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -11258,9 +7963,7 @@
- Failed: Unable to - Process - + Failed: Unable to Process Cxxx @@ -11275,9 +7978,7 @@ Cancel - Sub-operations - terminated due to Cancel Indication - + Sub-operations terminated due to Cancel Indication FE00 @@ -11294,9 +7995,7 @@ Warning - Sub-operations Complete - - One or more Failures - + Sub-operations Complete - One or more Failures B000 @@ -11312,9 +8011,7 @@ Success - Sub-operations Complete - - No Failures - + Sub-operations Complete - No Failures 0000 @@ -11330,9 +8027,7 @@ Pending - Sub-operations are - continuing - + Sub-operations are continuing FF00 @@ -11346,284 +8041,142 @@
- Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: - Unable to process" Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: Unable to process" Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
Number of Remaining Sub-Operations - Inclusion of the Number of Remaining - Sub-operations is conditional based upon the status in the C-MOVE response. The Number of - Remaining Sub-operations specifies the number of Remaining C-STORE sub-operations necessary - to complete the C-MOVE operation. - - A C-MOVE response with a status of: - + Inclusion of the Number of Remaining Sub-operations is conditional based upon the status in the C-MOVE response. The Number of Remaining Sub-operations specifies the number of Remaining C-STORE sub-operations necessary to complete the C-MOVE operation. + A C-MOVE response with a status of: - Pending shall contain the - Number of Remaining Sub-operations Attribute - + Pending shall contain the Number of Remaining Sub-operations Attribute - Canceled may contain the Number - of Remaining Sub-operations Attribute - + Canceled may contain the Number of Remaining Sub-operations Attribute - Warning, Failure, or Success - shall not contain the Number of Remaining Sub-operations Attribute - + Warning, Failure, or Success shall not contain the Number of Remaining Sub-operations Attribute
Number of Completed Sub-Operations - Inclusion of the Number of Completed - Sub-operations is conditional based upon the status in the C-MOVE response. The Number of - Completed sub-operations specifies the number of C-STORE sub-operations generated by the - requested transfer that have completed successfully. - - A C-MOVE response with a status of: - + Inclusion of the Number of Completed Sub-operations is conditional based upon the status in the C-MOVE response. The Number of Completed sub-operations specifies the number of C-STORE sub-operations generated by the requested transfer that have completed successfully. + A C-MOVE response with a status of: - Pending shall contain the - Number of Completed Sub-operations Attribute - + Pending shall contain the Number of Completed Sub-operations Attribute - Canceled, Warning, Failure, or - Success may contain the Number of Completed Sub-operations Attribute - + Canceled, Warning, Failure, or Success may contain the Number of Completed Sub-operations Attribute
Number of Failed Sub-Operations - Inclusion of the Number of Failed - Sub-operations is conditional based upon the status in the C-MOVE response. The Number of - Failed sub-operations specifies the number of C-STORE sub-operations generated by the - requested transfer that have Failed. - - A C-MOVE response with a status of: - + Inclusion of the Number of Failed Sub-operations is conditional based upon the status in the C-MOVE response. The Number of Failed sub-operations specifies the number of C-STORE sub-operations generated by the requested transfer that have Failed. + A C-MOVE response with a status of: - Pending shall contain the - Number of Failed Sub-operations Attribute - + Pending shall contain the Number of Failed Sub-operations Attribute - Canceled, Warning, Failure, or - Success may contain the Number of Failed Sub-operations Attribute - + Canceled, Warning, Failure, or Success may contain the Number of Failed Sub-operations Attribute
Number of Warning Sub-Operations - Inclusion of the Number of Warning - Sub-operations is conditional based upon the status in the C-MOVE response. The Number of - Warning sub-operations specifies the number of C-STORE sub-operations generated by the - requested transfer that had a status of warning. - - A C-MOVE response with a status of: - + Inclusion of the Number of Warning Sub-operations is conditional based upon the status in the C-MOVE response. The Number of Warning sub-operations specifies the number of C-STORE sub-operations generated by the requested transfer that had a status of warning. + A C-MOVE response with a status of: - Pending shall contain the - Number of Warnings Sub-operations Attribute - + Pending shall contain the Number of Warnings Sub-operations Attribute - Canceled, Warning, Failure, or - Success may contain the Number of Warning Sub-operations Attribute - + Canceled, Warning, Failure, or Success may contain the Number of Warning Sub-operations Attribute
C-MOVE SCU Behavior - This Section discusses both the baseline - and extended behavior of the C-MOVE SCU. - + This Section discusses both the baseline and extended behavior of the C-MOVE SCU.
Baseline Behavior of SCU - An SCU conveys the following semantics - with a C-MOVE request: - + An SCU conveys the following semantics with a C-MOVE request: - The SCU shall supply a single - value in the Unique Key Attribute for each level above the Query/Retrieve level. For - the level of retrieve, the SCU shall supply a single value for one unique key if the - level of retrieve is above the STUDY level and shall supply one UID, or a list of - UIDs if a retrieval of several items is desired and the retrieve level is STUDY, - SERIES or IMAGE. The SCU shall also supply a move destination. The move destination - shall be the DICOM Application Entity Title of a DICOM Application Entity capable of - serving as the SCP of the Storage Service Class. - + The SCU shall supply a single value in the Unique Key Attribute for each level above the Query/Retrieve level. For the level of retrieve, the SCU shall supply a single value for one unique key if the level of retrieve is above the STUDY level and shall supply one UID, or a list of UIDs if a retrieval of several items is desired and the retrieve level is STUDY, SERIES or IMAGE. The SCU shall also supply a move destination. The move destination shall be the DICOM Application Entity Title of a DICOM Application Entity capable of serving as the SCP of the Storage Service Class. - The SCU shall interpret - responses to the C-MOVE with status equal to Pending during the processing of the - C-STORE sub-operations. These responses shall indicate the number of Remaining, - Completed, Failed, and Warning C-STORE sub-operations. - + The SCU shall interpret responses to the C-MOVE with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the number of Remaining, Completed, Failed, and Warning C-STORE sub-operations. - The SCU shall interpret - responses with a status equal to Success, Warning, Failure, or Refused as final - responses. The final response shall indicate the number of Successful C-STORE - sub-operations and the number of Failed C-STORE sub-operations resulting from the - C-MOVE operation. The SCU shall interpret a status of: - + The SCU shall interpret responses with a status equal to Success, Warning, Failure, or Refused as final responses. The final response shall indicate the number of Successful C-STORE sub-operations and the number of Failed C-STORE sub-operations resulting from the C-MOVE operation. The SCU shall interpret a status of: - Success to indicate - that all sub-operations were successfully completed - + Success to indicate that all sub-operations were successfully completed - Warning to indicate one - or more sub-operations were successfully completed and one or more - sub-operations were unsuccessful or had a status of warning, or all - sub-operations had a status of warning - + Warning to indicate one or more sub-operations were successfully completed and one or more sub-operations were unsuccessful or had a status of warning, or all sub-operations had a status of warning - Failure or Refused to - indicate all sub-operations were unsuccessful. - + Failure or Refused to indicate all sub-operations were unsuccessful. - The SCU may cancel the C-MOVE - service by issuing a C-MOVE-CANCEL request at any time during the processing of the - C-MOVE. The SCU shall interpret a C-MOVE response with a status of Canceled to - indicate the transfer was canceled. The C-MOVE response with a status of Canceled - shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. - If present, the Remaining sub-operations count shall contain the number of C-STORE - sub-operations that were not initiated due to the C-MOVE-CANCEL request. - + The SCU may cancel the C-MOVE service by issuing a C-MOVE-CANCEL request at any time during the processing of the C-MOVE. The SCU shall interpret a C-MOVE response with a status of Canceled to indicate the transfer was canceled. The C-MOVE response with a status of Canceled shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-MOVE-CANCEL request.
Extended Behavior of SCU - Extended SCU behavior shall be - negotiated at Association establishment time. If an option within the extended behavior is - not agreed upon in the negotiation, then only baseline SCU behavior shall be performed with - respect to that option. Extended SCU behavior includes all baseline behavior with the - following option: - + Extended SCU behavior shall be negotiated at Association establishment time. If an option within the extended behavior is not agreed upon in the negotiation, then only baseline SCU behavior shall be performed with respect to that option. Extended SCU behavior includes all baseline behavior with the following option: Relational-retrieve - Enhanced Multi-Frame Image - Conversion - + Enhanced Multi-Frame Image Conversion - More than one option may be agreed - upon. - + More than one option may be agreed upon.
Relational-Retrieve - The C-MOVE Service with - relational-retrieve removes the restriction that the SCU supply Unique Key values for - levels above the Query/Retrieve level to identify an entity at the level of the - retrieval. Hence, the Identifier of a C-MOVE request may transfer: - + The C-MOVE Service with relational-retrieve removes the restriction that the SCU supply Unique Key values for levels above the Query/Retrieve level to identify an entity at the level of the retrieval. Hence, the Identifier of a C-MOVE request may transfer: - all Composite Object - Instances related to a study by only providing a Study Instance UID (0020,000D) - + all Composite Object Instances related to a study by only providing a Study Instance UID (0020,000D) - all Composite Object - Instances related to a series by only providing a Series Instance UID - (0020,000E) - + all Composite Object Instances related to a series by only providing a Series Instance UID (0020,000E) - individual Composite Object - Instances by only providing a list of SOP Instance UIDs (0008,0018) - + individual Composite Object Instances by only providing a list of SOP Instance UIDs (0008,0018)
Enhanced Multi-Frame Image Conversion - The C-MOVE Service with Enhanced - Multi-Frame Image Conversion allows for selection of the default or an alternative view - of the instances represented by the Information Model, and hence the retrieval of either - the legacy or the converted images, together with any unconverted instances, all of - which are required to be processed to maintain referential integrity within the scope of - the Patient. - - Support for Enhanced Multi-Frame - Image Conversion allows the SCU to specify the Attribute Query/Retrieve View (0008,0053) - in the Request Identifier with a value of either "CLASSIC" or "ENHANCED". - - If Query/Retrieve View (0008,0053) - is not present in the Request Identifier, then the SCU requests that the SCP provide all - the requested instances it possesses, as received. - - If Query/Retrieve View (0008,0053) - is present with a value of "CLASSIC", then the SCU requests that the SCP provide all the - Classic single frame Instances (converted from Enhanced multi-frame Instances if - required), as well as any instances that were converted to preserve referential - integrity, and any that did not need to be converted. - - If Query/Retrieve View (0008,0053) - is present with a value of "ENHANCED", then the SCU requests that the SCP provide all - the Enhanced multi-frame Instances (converted from Classic single frame Instances if - required), as well as any instances that were converted to preserve referential - integrity, and any that did not need to be converted. - + The C-MOVE Service with Enhanced Multi-Frame Image Conversion allows for selection of the default or an alternative view of the instances represented by the Information Model, and hence the retrieval of either the legacy or the converted images, together with any unconverted instances, all of which are required to be processed to maintain referential integrity within the scope of the Patient. + Support for Enhanced Multi-Frame Image Conversion allows the SCU to specify the Attribute Query/Retrieve View (0008,0053) in the Request Identifier with a value of either "CLASSIC" or "ENHANCED". + If Query/Retrieve View (0008,0053) is not present in the Request Identifier, then the SCU requests that the SCP provide all the requested instances it possesses, as received. + If Query/Retrieve View (0008,0053) is present with a value of "CLASSIC", then the SCU requests that the SCP provide all the Classic single frame Instances (converted from Enhanced multi-frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. + If Query/Retrieve View (0008,0053) is present with a value of "ENHANCED", then the SCU requests that the SCP provide all the Enhanced multi-frame Instances (converted from Classic single frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. - The SCU may assume that - no duplicate information will be provided. For example, if an entire series - of single frame instances can be converted to a separate series of converted - instances, a STUDY level C-MOVE will not provide both series. - + The SCU may assume that no duplicate information will be provided. For example, if an entire series of single frame instances can be converted to a separate series of converted instances, a STUDY level C-MOVE will not provide both series. - The Query Information - Model is unchanged, and the same unique keys are equally applicable to both - views, except that the values for the SERIES and IMAGE level queries will be - different and will depend on the converted instance content. - + The Query Information Model is unchanged, and the same unique keys are equally applicable to both views, except that the values for the SERIES and IMAGE level queries will be different and will depend on the converted instance content. - The Query/Retrieve View - is still required in an IMAGE or SERIES level request identifier, even - though the requested unique key(s) are unambiguous, and the view is in a - sense "redundant", because the conversion that created the requested - instances may not have been executed yet. It is not permitted to specify a - view that is inconsistent with the requested unique key(s). - + The Query/Retrieve View is still required in an IMAGE or SERIES level request identifier, even though the requested unique key(s) are unambiguous, and the view is in a sense "redundant", because the conversion that created the requested instances may not have been executed yet. It is not permitted to specify a view that is inconsistent with the requested unique key(s). @@ -11632,214 +8185,96 @@
C-MOVE SCP Behavior - This section discusses both the baseline - and extended behavior of the C-MOVE SCP. - + This section discusses both the baseline and extended behavior of the C-MOVE SCP.
Baseline Behavior of SCP - An SCP conveys the following semantics - with a C-MOVE response: - + An SCP conveys the following semantics with a C-MOVE response: - The SCP shall identify a set of - Entities at the level of the transfer based upon the values in the Unique Keys in - the Identifier of the C-MOVE request. The SCP shall initiate C-STORE sub-operations - for the corresponding storage SOP Instances. These C-STORE sub-operations shall - occur on a different Association (that may already exist) from the C-MOVE operation. - The SCP of the Query/Retrieve Service Class shall serve as an SCU of the Storage - Service Class. - + The SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-MOVE request. The SCP shall initiate C-STORE sub-operations for the corresponding storage SOP Instances. These C-STORE sub-operations shall occur on a different Association (that may already exist) from the C-MOVE operation. The SCP of the Query/Retrieve Service Class shall serve as an SCU of the Storage Service Class. - The SCP shall either reuse an - established and compatible Association or establish a new Association for the - C-STORE sub-operations. The SCP shall initiate C-STORE sub-operations over that - Association for all stored SOP Instances related to the Patient ID, List of Study - Instance UIDs, List of Series Instance UIDs, or List of SOP Instance UIDs depending - on the Query/Retrieve level specified in the C-MOVE request. A sub-operation is - considered Failed if the SCP is unable to negotiate an appropriate presentation - context for a given stored SOP Instance. - + The SCP shall either reuse an established and compatible Association or establish a new Association for the C-STORE sub-operations. The SCP shall initiate C-STORE sub-operations over that Association for all stored SOP Instances related to the Patient ID, List of Study Instance UIDs, List of Series Instance UIDs, or List of SOP Instance UIDs depending on the Query/Retrieve level specified in the C-MOVE request. A sub-operation is considered Failed if the SCP is unable to negotiate an appropriate presentation context for a given stored SOP Instance. - Optionally, the SCP may - generate responses to the C-MOVE with status equal to Pending during the processing - of the C-STORE sub-operations. These responses shall indicate the Remaining, - Completed, Failed, and Warning C-STORE sub-operations. - + Optionally, the SCP may generate responses to the C-MOVE with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the Remaining, Completed, Failed, and Warning C-STORE sub-operations. - When the number of Remaining - sub-operations reaches zero, the SCP shall generate a final response with a status - equal to Success, Warning, Failure, or Refused. This response shall indicate the - number of Completed sub-operations, the number of Failed sub-operations, and the - number of sub-operations with Warning Status. The status contained in the C-MOVE - response shall contain: - + When the number of Remaining sub-operations reaches zero, the SCP shall generate a final response with a status equal to Success, Warning, Failure, or Refused. This response shall indicate the number of Completed sub-operations, the number of Failed sub-operations, and the number of sub-operations with Warning Status. The status contained in the C-MOVE response shall contain: - Success if all - sub-operations were successfully completed - + Success if all sub-operations were successfully completed - Warning if one or more - sub-operations were successfully completed and one or more sub-operations - were unsuccessful or had a warning status - + Warning if one or more sub-operations were successfully completed and one or more sub-operations were unsuccessful or had a warning status - Warning if all - sub-operations had a warning status - + Warning if all sub-operations had a warning status - Failure or Refused if - all sub-operations were unsuccessful - + Failure or Refused if all sub-operations were unsuccessful - The SCP may receive a - C-MOVE-CANCEL request at any time during the processing of the C-MOVE. The SCP shall - interrupt all C-STORE sub-operation processing and return a status of Canceled in - the C-MOVE response. The C-MOVE response with a status of Canceled shall contain the - number of Completed, Failed, and Warning C-STORE sub-operations. If present, the - Remaining sub-operations count shall contain the number of C-STORE sub-operations - that were not initiated due to the C-MOVE-CANCEL request. - + The SCP may receive a C-MOVE-CANCEL request at any time during the processing of the C-MOVE. The SCP shall interrupt all C-STORE sub-operation processing and return a status of Canceled in the C-MOVE response. The C-MOVE response with a status of Canceled shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-MOVE-CANCEL request. - If the SCP manages images in - multiple alternate encodings (see), only one of the - alternate encodings of an image shall be included in the set of object instances - retrieved by a C-MOVE request at the Patient, Study, or Series level. - + If the SCP manages images in multiple alternate encodings (see ), only one of the alternate encodings of an image shall be included in the set of object instances retrieved by a C-MOVE request at the Patient, Study, or Series level. - For retrieval of images - with alternate encodings using a C-MOVE request at the Patient, Study, or Series - level, the SCP may select the appropriately encoded Instance for the retrieval - based on identity of the SCU, transfer syntaxes accepted in the C-STORE - Association Negotiation, or other factors. - + For retrieval of images with alternate encodings using a C-MOVE request at the Patient, Study, or Series level, the SCP may select the appropriately encoded Instance for the retrieval based on identity of the SCU, transfer syntaxes accepted in the C-STORE Association Negotiation, or other factors. - If the association on which the - C-MOVE operation was issued is abnormally terminated, then it will not be possible to - issue any further pending responses nor a final response, nor will C-MOVE-CANCEL - requests be received. The behavior of the C-MOVE SCP acting as a C-STORE SCU is - undefined in this condition. Specifically, whether or not any uncompleted C-STORE - sub-operations continue is undefined. - + If the association on which the C-MOVE operation was issued is abnormally terminated, then it will not be possible to issue any further pending responses nor a final response, nor will C-MOVE-CANCEL requests be received. The behavior of the C-MOVE SCP acting as a C-STORE SCU is undefined in this condition. Specifically, whether or not any uncompleted C-STORE sub-operations continue is undefined.
Extended Behavior of SCP - Extended SCP behavior shall be - negotiated at Association establishment time. If an option within the extended behavior is - not agreed upon in the negotiation, then only baseline SCP behavior shall be performed with - respect to that option. Extended SCP behavior includes all baseline behavior with the - following option: - + Extended SCP behavior shall be negotiated at Association establishment time. If an option within the extended behavior is not agreed upon in the negotiation, then only baseline SCP behavior shall be performed with respect to that option. Extended SCP behavior includes all baseline behavior with the following option: Relational-retrieve - Enhanced Multi-Frame Image - Conversion - + Enhanced Multi-Frame Image Conversion - More than one option may be agreed - upon. - + More than one option may be agreed upon.
Relational-Retrieve - The C-MOVE Service with - relational-retrieve removes the restriction that the SCU supply Unique Key values for - levels above the Query/Retrieve level to help identify an entity at the level of the - retrieval. Hence, the Identifier of a C-MOVE request may specify the transfer of: - + The C-MOVE Service with relational-retrieve removes the restriction that the SCU supply Unique Key values for levels above the Query/Retrieve level to help identify an entity at the level of the retrieval. Hence, the Identifier of a C-MOVE request may specify the transfer of: - all Composite Object - Instances related to a study by only providing a Study Instance UID (0020,000D) - + all Composite Object Instances related to a study by only providing a Study Instance UID (0020,000D) - all Composite Object - Instances related to a series by only providing a Series Instance UID - (0020,000E) - + all Composite Object Instances related to a series by only providing a Series Instance UID (0020,000E) - individual Composite Object - Instances by only providing a list of SOP Instance UIDs (0008,0018) - + individual Composite Object Instances by only providing a list of SOP Instance UIDs (0008,0018)
Enhanced Multi-Frame Image Conversion - If Query/Retrieve View (0008,0053) - is not present in the Request Identifier, then the SCP shall identify a set of Entities - at the level of the transfer based upon the values in the Unique Keys in the Identifier - of the C-MOVE request that correspond to the instances it possesses, as received, and - shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. - - If Query/Retrieve View (0008,0053) - is present with a value of "CLASSIC", then the SCP shall identify a set of Entities at - the level of the transfer based upon the values in the Unique Keys in the Identifier of - the C-MOVE request that correspond to the Classic single frame Instances (converted from - Enhanced multi-frame Instances if required), as well as any instances that were - converted to preserve referential integrity, and any that did not need to be converted, - and shall initiate C-STORE sub-operations for all the corresponding storage SOP - Instances. - - If Query/Retrieve View (0008,0053) - is present with a value of "ENHANCED", then the SCP shall identify a set of Entities at - the level of the transfer based upon the values in the Unique Keys in the Identifier of - the C-MOVE request that correspond to the Enhanced multi-frame Instances (converted from - Classic single frame Instances if required), as well as any instances that were - converted to preserve referential integrity, and any that did not need to be converted, - and shall initiate C-STORE sub-operations for all the corresponding storage SOP - Instances. - + If Query/Retrieve View (0008,0053) is not present in the Request Identifier, then the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-MOVE request that correspond to the instances it possesses, as received, and shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. + If Query/Retrieve View (0008,0053) is present with a value of "CLASSIC", then the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-MOVE request that correspond to the Classic single frame Instances (converted from Enhanced multi-frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted, and shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. + If Query/Retrieve View (0008,0053) is present with a value of "ENHANCED", then the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-MOVE request that correspond to the Enhanced multi-frame Instances (converted from Classic single frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted, and shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. - The SCP will not send - information that is duplicated to the C-STORE SCP. For example, if an entire - series of single frame instances can be converted to a separate series of - converted instances, a STUDY level C-MOVE will not send both series. - + The SCP will not send information that is duplicated to the C-STORE SCP. For example, if an entire series of single frame instances can be converted to a separate series of converted instances, a STUDY level C-MOVE will not send both series. - The C-STORE SCP will - need to support the necessary SOP Classes for converted instances, otherwise - the C-STORE sub-operations will fail in the normal manner and this will be - reflected in the C-MOVE responses. - + The C-STORE SCP will need to support the necessary SOP Classes for converted instances, otherwise the C-STORE sub-operations will fail in the normal manner and this will be reflected in the C-MOVE responses. - The Query Information - Model is unchanged, and the same unique, required and optional keys are - equally applicable to both views, except that the values for the SERIES and - IMAGE level queries will be different and will depend on the converted - instance content. - + The Query Information Model is unchanged, and the same unique, required and optional keys are equally applicable to both views, except that the values for the SERIES and IMAGE level queries will be different and will depend on the converted instance content. - The Query/Retrieve View - is still required in an IMAGE or SERIES level request identifier, even - though the requested unique key(s) are unambiguous. - + The Query/Retrieve View is still required in an IMAGE or SERIES level request identifier, even though the requested unique key(s) are unambiguous. @@ -11849,138 +8284,66 @@
C-GET Operation - SCUs of some SOP Classes of the Query/Retrieve - Service Class may generate retrievals using the C-GET operation as described in. The C-GET operation - allows an application entity to instruct another application entity to transfer stored SOP Instances - to the initiating application entity using the C-STORE operation. Support for the C-GET service - shall be agreed upon at Association establishment time by both the SCU and SCP of the C-GET in order - for a C-GET operation to occur over the Association. The C-STORE Sub-operations shall be - accomplished on the same Association as the C-GET operation. Hence, the SCP of the Query/Retrieve - Service Class serves as the SCU of the Storage Service Class. - + SCUs of some SOP Classes of the Query/Retrieve Service Class may generate retrievals using the C-GET operation as described in . The C-GET operation allows an application entity to instruct another application entity to transfer stored SOP Instances to the initiating application entity using the C-STORE operation. Support for the C-GET service shall be agreed upon at Association establishment time by both the SCU and SCP of the C-GET in order for a C-GET operation to occur over the Association. The C-STORE Sub-operations shall be accomplished on the same Association as the C-GET operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage Service Class. - The application entity that receives the - stored SOP Instances is always the originator of the C-GET operation. - + The application entity that receives the stored SOP Instances is always the originator of the C-GET operation. - A C-GET request may be performed to any level - of the Query/Retrieve Information Model. However, the transfer of stored SOP Instances may not be - performed at this level. The level at which the transfer is performed depends upon the SOP Class. - + A C-GET request may be performed to any level of the Query/Retrieve Information Model. However, the transfer of stored SOP Instances may not be performed at this level. The level at which the transfer is performed depends upon the SOP Class.
C-GET Service Parameters
SOP Class UID - The SOP Class UID identifies the - Query/Retrieve Information Model against which the C-GET is to be performed. Support for the - SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this - C-GET operation. - + The SOP Class UID identifies the Query/Retrieve Information Model against which the C-GET is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-GET operation.
Priority - The Priority Attribute defines the - requested priority of the C-GET operation and corresponding C-STORE sub-operations with - respect to other DIMSE operations being performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. The same - priority shall be used for all C-STORE sub-operations. - + The Priority Attribute defines the requested priority of the C-GET operation and corresponding C-STORE sub-operations with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP. The same priority shall be used for all C-STORE sub-operations.
Identifier - The C-GET request shall contain an - Identifier. The C-GET response shall conditionally contain an Identifier as required in. - + The C-GET request shall contain an Identifier. The C-GET response shall conditionally contain an Identifier as required in . - The Identifier is specified as U in - the definition of the C-GET primitive in - - but is specialized for use with this service. - + The Identifier is specified as U in the definition of the C-GET primitive in but is specialized for use with this service.
Request Identifier Structure - An Identifier in a C-GET request - shall contain: - + An Identifier in a C-GET request shall contain: - Query/Retrieve Level - (0008,0052), which defines the level of the retrieval - + Query/Retrieve Level (0008,0052), which defines the level of the retrieval - Unique Key Attributes, - which may include Patient ID (0010,0020), Study Instance UIDs (0020,000D) Series - Instance UIDs (0020,000E), and SOP Instance UIDs (0008,0018) - + Unique Key Attributes, which may include Patient ID (0010,0020), Study Instance UIDs (0020,000D) Series Instance UIDs (0020,000E), and SOP Instance UIDs (0008,0018) - Conditionally, the - Attribute Query/Retrieve View (0008,0053). This Attribute may be included if - Enhanced Multi-Frame Image Conversion has been accepted during Association - Extended Negotiation. It shall not be included otherwise. - + Conditionally, the Attribute Query/Retrieve View (0008,0053). This Attribute may be included if Enhanced Multi-Frame Image Conversion has been accepted during Association Extended Negotiation. It shall not be included otherwise. - Specific Character Set (0008,0005) - shall be present if Patient ID (0010,0020) is using a character set other than the - Default Character Repertoire. - - The Unique Keys at each level of - the hierarchy and the values allowable for the level of the retrieval shall be defined - in the SOP Class definition for the Query/Retrieve Information Model. - + Specific Character Set (0008,0005) shall be present if Patient ID (0010,0020) is using a character set other than the Default Character Repertoire. + The Unique Keys at each level of the hierarchy and the values allowable for the level of the retrieval shall be defined in the SOP Class definition for the Query/Retrieve Information Model. - In the non-Relational - behavior, more than one entity may be retrieved if the Query/Retrieve Level - is IMAGE, SERIES or STUDY, using List of UID matching, but only Single Value - Matching value may be specified for Patient ID (0010,0020). - + In the non-Relational behavior, more than one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using List of UID matching, but only Single Value Matching value may be specified for Patient ID (0010,0020). - The issuer of the - Patient ID (0010,0020) is implicit; there is no provision to send the Issuer - of Patient ID (0010,0021). When there is a possibility of ambiguity of the - Patient ID (0010,0020) value, a STUDY level retrieval should be used instead - of a PATIENT level retrieval. - + The issuer of the Patient ID (0010,0020) is implicit; there is no provision to send the Issuer of Patient ID (0010,0021). When there is a possibility of ambiguity of the Patient ID (0010,0020) value, a STUDY level retrieval should be used instead of a PATIENT level retrieval.
Response Identifier Structure - The Failed SOP Instance UID List - (0008,0058) specifies a list of UIDs of the C-STORE sub-operation SOP Instances for - which this C-GET operation has failed. An Identifier in a C-GET response shall - conditionally contain the Failed SOP Instance UID List (0008,0058) based on the C-GET - response. If no C-STORE sub-operation failed, Failed SOP Instance UID List (0008,0058) - is absent and therefore no Data Set shall be sent in the C-GET response. - - Specific Character Set (0008,0005) - shall not be present. - - The Identifier in a C-GET response - with a status of: - + The Failed SOP Instance UID List (0008,0058) specifies a list of UIDs of the C-STORE sub-operation SOP Instances for which this C-GET operation has failed. An Identifier in a C-GET response shall conditionally contain the Failed SOP Instance UID List (0008,0058) based on the C-GET response. If no C-STORE sub-operation failed, Failed SOP Instance UID List (0008,0058) is absent and therefore no Data Set shall be sent in the C-GET response. + Specific Character Set (0008,0005) shall not be present. + The Identifier in a C-GET response with a status of: - Canceled, Failure, Refused, - or Warning shall contain the Failed SOP Instance UID List Attribute - + Canceled, Failure, Refused, or Warning shall contain the Failed SOP Instance UID List Attribute - Pending shall not contain - the Failed SOP Instance UID List Attribute (no Data Set) - + Pending shall not contain the Failed SOP Instance UID List Attribute (no Data Set)
@@ -11988,11 +8351,7 @@
Status - - defines the specific status code values that might be returned in a C-GET response. General - status code values and fields related to status code values are defined for C-GET DIMSE - Service in. - + defines the specific status code values that might be returned in a C-GET response. General status code values and fields related to status code values are defined for C-GET DIMSE Service in . @@ -12017,9 +8376,7 @@ Failure
C-GET Response Status Values
- Refused: Out of - resources - Unable to calculate number of matches - + Refused: Out of resources - Unable to calculate number of matches A701 @@ -12030,9 +8387,7 @@
- Refused: Out of - resources - Unable to perform sub-operations - + Refused: Out of resources - Unable to perform sub-operations A702 @@ -12045,9 +8400,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -12059,9 +8412,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -12076,9 +8427,7 @@ Cancel - Sub-operations - terminated due to Cancel Indication - + Sub-operations terminated due to Cancel Indication FE00 @@ -12095,9 +8444,7 @@ Warning - Sub-operations Complete - - One or more Failures or Warnings - + Sub-operations Complete - One or more Failures or Warnings B000 @@ -12113,9 +8460,7 @@ Success - Sub-operations Complete - - No Failures or Warnings - + Sub-operations Complete - No Failures or Warnings 0000 @@ -12131,9 +8476,7 @@ Pending - Sub-operations are - continuing - + Sub-operations are continuing FF00 @@ -12147,298 +8490,148 @@
- Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: - Unable to process” Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: Unable to process” Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
Number of Remaining Sub-Operations - Inclusion of the Number of Remaining - Sub-operations is conditional based upon the status in the C-GET response. The Number of - Remaining Sub-operations specifies the number of Remaining C-STORE sub-operations necessary - to complete the C-GET operation. - - A C-GET response with a status of: - + Inclusion of the Number of Remaining Sub-operations is conditional based upon the status in the C-GET response. The Number of Remaining Sub-operations specifies the number of Remaining C-STORE sub-operations necessary to complete the C-GET operation. + A C-GET response with a status of: - Pending shall contain the - Number of Remaining Sub-operations Attribute - + Pending shall contain the Number of Remaining Sub-operations Attribute - Canceled may contain the Number - of Remaining Sub-operations Attribute - + Canceled may contain the Number of Remaining Sub-operations Attribute - Warning, Failure, or Success - shall not contain the Number of Remaining Sub-operations Attribute. - + Warning, Failure, or Success shall not contain the Number of Remaining Sub-operations Attribute.
Number of Completed Sub-Operations - Inclusion of the Number of Completed - Sub-operations is conditional based upon the status in the C-GET response. The Number of - Completed Sub-operations specifies the number of C-STORE sub-operations generated by the - requested transfer that have completed successfully. - - A C-GET response with a status of: - + Inclusion of the Number of Completed Sub-operations is conditional based upon the status in the C-GET response. The Number of Completed Sub-operations specifies the number of C-STORE sub-operations generated by the requested transfer that have completed successfully. + A C-GET response with a status of: - Pending shall contain the - Number of Completed Sub-operations Attribute - + Pending shall contain the Number of Completed Sub-operations Attribute - Canceled, Warning, Failure, or - Success may contain the Number of Completed Sub-operations Attribute - + Canceled, Warning, Failure, or Success may contain the Number of Completed Sub-operations Attribute
Number of Failed Sub-Operations - Inclusion of the Number of Failed - Sub-operations is conditional based upon the status in the C-GET response. The Number of - Failed Sub-operations specifies the number of C-STORE sub-operations generated by the - requested transfer that have Failed. - - A C-GET response with a status of: - + Inclusion of the Number of Failed Sub-operations is conditional based upon the status in the C-GET response. The Number of Failed Sub-operations specifies the number of C-STORE sub-operations generated by the requested transfer that have Failed. + A C-GET response with a status of: - Pending shall contain the - Number of Failed Sub-operations Attribute - + Pending shall contain the Number of Failed Sub-operations Attribute - Canceled, Warning, Failure, or - Success may contain the Number of Failed Sub-operations Attribute - + Canceled, Warning, Failure, or Success may contain the Number of Failed Sub-operations Attribute
Number of Warning Sub-Operations - Inclusion of the Number of Warning - Sub-operations is conditional based upon the status in the C-GET response. The Number of - Warning Sub-operations specifies the number of C-STORE sub-operations generated by the - requested transfer that had a status of Warning. - - A C-GET response with a status of: - + Inclusion of the Number of Warning Sub-operations is conditional based upon the status in the C-GET response. The Number of Warning Sub-operations specifies the number of C-STORE sub-operations generated by the requested transfer that had a status of Warning. + A C-GET response with a status of: - Pending shall contain the - Number of Warning Sub-operations Attribute - + Pending shall contain the Number of Warning Sub-operations Attribute - Canceled, Warning, Failure, or - Success may contain the Number of Warning Sub-operations Attribute - + Canceled, Warning, Failure, or Success may contain the Number of Warning Sub-operations Attribute
C-GET SCU Behavior - This Section discusses both the baseline - and extended behavior of the C-GET SCU. - + This Section discusses both the baseline and extended behavior of the C-GET SCU.
Baseline Behavior of SCU - An SCU conveys the following semantics - with a C-GET request: - + An SCU conveys the following semantics with a C-GET request: - The SCU shall have proposed - sufficient presentation contexts at Association establishment time to accommodate - expected C-STORE sub-operations that shall occur over the same Association. The SCU - of the Query/Retrieve Service Class shall serve as the SCP of the Storage Service - Class. - + The SCU shall have proposed sufficient presentation contexts at Association establishment time to accommodate expected C-STORE sub-operations that shall occur over the same Association. The SCU of the Query/Retrieve Service Class shall serve as the SCP of the Storage Service Class. - The SCU shall supply a single - value in the Unique Key Attribute for each level above the Query/Retrieve level. For - the level of retrieve, the SCU shall supply a single value for one unique key if the - level of the retrieve is above the STUDY level and shall supply one UID, or a list - of UIDs if a retrieval of several items is desired and the retrieve level is STUDY, - SERIES or IMAGE. - + The SCU shall supply a single value in the Unique Key Attribute for each level above the Query/Retrieve level. For the level of retrieve, the SCU shall supply a single value for one unique key if the level of the retrieve is above the STUDY level and shall supply one UID, or a list of UIDs if a retrieval of several items is desired and the retrieve level is STUDY, SERIES or IMAGE. - The SCU shall interpret C-GET - responses with status equal to Pending during the processing of the C-STORE - sub-operations. These responses shall indicate the number of Remaining, Completed, - Failed, Warning C-STORE sub-operations. - + The SCU shall interpret C-GET responses with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the number of Remaining, Completed, Failed, Warning C-STORE sub-operations. - The SCU shall interpret a C-GET - response with a status equal to Success, Warning, Failure, or Refused as a final - response. The final response shall indicate the number of Completed sub-operations - and the number of Failed C-STORE sub-operations resulting from the C-GET operation. - The SCU shall interpret a status of: - + The SCU shall interpret a C-GET response with a status equal to Success, Warning, Failure, or Refused as a final response. The final response shall indicate the number of Completed sub-operations and the number of Failed C-STORE sub-operations resulting from the C-GET operation. The SCU shall interpret a status of: - Success to indicate - that all sub-operations were successfully completed - + Success to indicate that all sub-operations were successfully completed - Warning to indicate one - or more sub-operations were successfully completed and one or more - unsuccessful or all sub-operations had a status of warning - + Warning to indicate one or more sub-operations were successfully completed and one or more unsuccessful or all sub-operations had a status of warning - Failure or Refused to - indicate all sub-operations were unsuccessful - + Failure or Refused to indicate all sub-operations were unsuccessful - The SCU may cancel the C-GET - operation by issuing a C-GET-CANCEL request at any time during the processing of the - C-GET request. A C-GET response with a status of Canceled shall indicate to the SCU - that the retrieve was canceled. Optionally, the C-GET response with a status of - Canceled shall indicate the number of Completed, Failed, and Warning C-STORE - sub-operations. If present, the Remaining sub-operations count shall contain the - number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL - request. - + The SCU may cancel the C-GET operation by issuing a C-GET-CANCEL request at any time during the processing of the C-GET request. A C-GET response with a status of Canceled shall indicate to the SCU that the retrieve was canceled. Optionally, the C-GET response with a status of Canceled shall indicate the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL request.
Extended Behavior of SCU - Extended SCU behavior shall be - negotiated at Association establishment time. If an option within the extended behavior is - not agreed upon in the negotiation, then only baseline SCU behavior shall be supported with - respect to that option. Extended SCU behavior includes all baseline behavior with the - following option: - + Extended SCU behavior shall be negotiated at Association establishment time. If an option within the extended behavior is not agreed upon in the negotiation, then only baseline SCU behavior shall be supported with respect to that option. Extended SCU behavior includes all baseline behavior with the following option: Relational-retrieve - Enhanced Multi-Frame Image - Conversion - + Enhanced Multi-Frame Image Conversion - More than one option may be agreed - upon. - + More than one option may be agreed upon.
Relational-Retrieve - The C-GET Service with - relational-retrieve removes the restriction that the SCU supply Unique Key values for - levels above the Query/Retrieve level to help identify an entity at the level of the - retrieval. Hence, the Identifier of a C-GET request may retrieve: - + The C-GET Service with relational-retrieve removes the restriction that the SCU supply Unique Key values for levels above the Query/Retrieve level to help identify an entity at the level of the retrieval. Hence, the Identifier of a C-GET request may retrieve: - all Composite Object - Instances related to a study by providing a Study Instance UID (0020,000D) - + all Composite Object Instances related to a study by providing a Study Instance UID (0020,000D) - all Composite Object - Instances related to a series by providing a Series Instance UID (0020,000E) - + all Composite Object Instances related to a series by providing a Series Instance UID (0020,000E) - individual Composite Object - Instances by providing a list of SOP Instance UIDs (0008,0018) - + individual Composite Object Instances by providing a list of SOP Instance UIDs (0008,0018)
Enhanced Multi-Frame Image Conversion - The C-GET Service with Enhanced - Multi-Frame Image Conversion allows for selection of the default or an alternative view - of the instances represented by the Information Model, and hence the retrieval of either - the legacy or the converted images, together with any unconverted instances, all of - which are required to be processed to maintain referential integrity within the scope of - the Patient. - - Support for Enhanced Multi-Frame - Image Conversion allows the SCU to specify the Attribute Query/Retrieve View (0008,0053) - in the Request Identifier with a value of either "CLASSIC" or "ENHANCED". - - If Query/Retrieve View (0008,0053) - is not present in the Request Identifier, then the SCU requests that the SCP retrieve - all the requested instances it possesses, as received. - - If Query/Retrieve View (0008,0053) - is present with a value of "CLASSIC", then the SCU requests that the SCP retrieve all - the Classic single frame Instances (converted from Enhanced multi-frame Instances if - required), as well as any instances that were converted to preserve referential - integrity, and any that did not need to be converted. - - If Query/Retrieve View (0008,0053) - is present with a value of "ENHANCED", then the SCU requests that the SCP retrieve all - the Enhanced multi-frame Instances (converted from Classic single frame Instances if - required), as well as any instances that were converted to preserve referential - integrity, and any that did not need to be converted. - + The C-GET Service with Enhanced Multi-Frame Image Conversion allows for selection of the default or an alternative view of the instances represented by the Information Model, and hence the retrieval of either the legacy or the converted images, together with any unconverted instances, all of which are required to be processed to maintain referential integrity within the scope of the Patient. + Support for Enhanced Multi-Frame Image Conversion allows the SCU to specify the Attribute Query/Retrieve View (0008,0053) in the Request Identifier with a value of either "CLASSIC" or "ENHANCED". + If Query/Retrieve View (0008,0053) is not present in the Request Identifier, then the SCU requests that the SCP retrieve all the requested instances it possesses, as received. + If Query/Retrieve View (0008,0053) is present with a value of "CLASSIC", then the SCU requests that the SCP retrieve all the Classic single frame Instances (converted from Enhanced multi-frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. + If Query/Retrieve View (0008,0053) is present with a value of "ENHANCED", then the SCU requests that the SCP retrieve all the Enhanced multi-frame Instances (converted from Classic single frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted. - The C-GET SCU acting as - a C-STORE SCP may assume that no duplicate information will be provided. For - example, if an entire series of single frame instances can be converted to a - separate series of converted instances, a STUDY level C-GET will not return - both series. - + The C-GET SCU acting as a C-STORE SCP may assume that no duplicate information will be provided. For example, if an entire series of single frame instances can be converted to a separate series of converted instances, a STUDY level C-GET will not return both series. - The C-GET SCU acting as - a C-STORE SCP will need to support the necessary SOP Classes for converted - instances, otherwise the C-STORE sub-operations will fail in the normal - manner and this will be reflected in the C-GET responses. - + The C-GET SCU acting as a C-STORE SCP will need to support the necessary SOP Classes for converted instances, otherwise the C-STORE sub-operations will fail in the normal manner and this will be reflected in the C-GET responses. - The Query Information - Model is unchanged, and the same unique, required and optional keys are - equally applicable to both views, except that the values for the SERIES and - IMAGE level queries will be different and will depend on the converted - instance content. - + The Query Information Model is unchanged, and the same unique, required and optional keys are equally applicable to both views, except that the values for the SERIES and IMAGE level queries will be different and will depend on the converted instance content. - The Query/Retrieve View - is still required in an IMAGE or SERIES level request identifier, even - though the requested unique key (s) are unambiguous, and the view is in a - sense "redundant", because the conversion that created the requested - instances may not have been executed yet. It is not permitted to specify a - view that is inconsistent with the requested unique key(s). - + The Query/Retrieve View is still required in an IMAGE or SERIES level request identifier, even though the requested unique key (s) are unambiguous, and the view is in a sense "redundant", because the conversion that created the requested instances may not have been executed yet. It is not permitted to specify a view that is inconsistent with the requested unique key(s). @@ -12447,198 +8640,93 @@
C-GET SCP Behavior - This Section discusses both the baseline - and extended behavior of the C-GET SCP. - + This Section discusses both the baseline and extended behavior of the C-GET SCP.
Baseline Behavior of SCP - An SCP conveys the following semantics - with a C-GET response: - + An SCP conveys the following semantics with a C-GET response: - The SCP shall identify a set of - Entities at the level of the retrieval based upon the values in the Unique Keys in - the Identifier of the C-GET request. The SCP shall initiate C-STORE sub-operations - for the corresponding storage SOP Instances. The SCP of the Query/Retrieve Service - Class shall serve as an SCU of the Storage Service Class. - + The SCP shall identify a set of Entities at the level of the retrieval based upon the values in the Unique Keys in the Identifier of the C-GET request. The SCP shall initiate C-STORE sub-operations for the corresponding storage SOP Instances. The SCP of the Query/Retrieve Service Class shall serve as an SCU of the Storage Service Class. - The SCP shall initiate C-STORE - sub-operations over the same Association for all stored SOP Instances related to the - Patient ID, List of Study Instance UIDs, List of Series Instance UIDs, or List of - SOP Instance UIDs depending on the Query/Retrieve level specified in the C-GET - request - + The SCP shall initiate C-STORE sub-operations over the same Association for all stored SOP Instances related to the Patient ID, List of Study Instance UIDs, List of Series Instance UIDs, or List of SOP Instance UIDs depending on the Query/Retrieve level specified in the C-GET request - A sub-operation is considered - Failed if the SCP is unable to initiate a C-STORE sub-operation because the - Query/Retrieve SCU did not offer an appropriate presentation context for a given - stored SOP Instance. - + A sub-operation is considered Failed if the SCP is unable to initiate a C-STORE sub-operation because the Query/Retrieve SCU did not offer an appropriate presentation context for a given stored SOP Instance. - Optionally, the SCP may - generate responses to the C-GET with status equal to Pending during the processing - of the C-STORE sub-operations. These responses shall indicate the number of - Remaining, Completed, Failure, and Warning C-STORE sub-operations. - + Optionally, the SCP may generate responses to the C-GET with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the number of Remaining, Completed, Failure, and Warning C-STORE sub-operations. - When the number of Remaining - sub-operations reaches zero, the SCP shall generate a final response with a status - equal to Success, Warning, Failed, or Refused. The status contained in the C-GET - response shall contain: - + When the number of Remaining sub-operations reaches zero, the SCP shall generate a final response with a status equal to Success, Warning, Failed, or Refused. The status contained in the C-GET response shall contain: - Success if all - sub-operations were successfully completed - + Success if all sub-operations were successfully completed - Warning if one or more - sub-operations were successfully completed and one or more sub-operations - were unsuccessful or had a status of warning - + Warning if one or more sub-operations were successfully completed and one or more sub-operations were unsuccessful or had a status of warning - Warning if all - sub-operations had a status of Warning - + Warning if all sub-operations had a status of Warning - Failure or Refused if - all sub-operations were unsuccessful - + Failure or Refused if all sub-operations were unsuccessful - The SCP may receive a - C-GET-CANCEL request at any time during the processing of the C-GET request. The SCP - shall interrupt all C-STORE sub-operation processing and return a status of Canceled - in the C-GET response. The C-GET response with a status of Canceled shall contain - the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the - Remaining sub-operations count shall contain the number of C-STORE sub-operations - that were not initiated due to the C-GET-CANCEL request. - + The SCP may receive a C-GET-CANCEL request at any time during the processing of the C-GET request. The SCP shall interrupt all C-STORE sub-operation processing and return a status of Canceled in the C-GET response. The C-GET response with a status of Canceled shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL request. - If the SCP manages images in - multiple alternate encodings (see), only one of the - alternate encodings of an image shall be included in the set of object instances - retrieved by a C-GET request at the Patient, Study, or Series level. - + If the SCP manages images in multiple alternate encodings (see ), only one of the alternate encodings of an image shall be included in the set of object instances retrieved by a C-GET request at the Patient, Study, or Series level. - For retrieval of images - with alternate encodings using a C-GET request at the Patient, Study, or Series - level, the SCP may select the appropriately encoded Instance for the retrieval - based on identity of the SCU, transfer syntaxes accepted in the C-STORE - Association Negotiation, or other factors. - + For retrieval of images with alternate encodings using a C-GET request at the Patient, Study, or Series level, the SCP may select the appropriately encoded Instance for the retrieval based on identity of the SCU, transfer syntaxes accepted in the C-STORE Association Negotiation, or other factors.
Extended Behavior of SCP - Extended SCP behavior shall be - negotiated at Association establishment time. If an option within the extended behavior is - not agreed upon in the negotiation, then only baseline SCP behavior shall be performed with - respect to that option. Extended SCP behavior includes all baseline behavior with the - following option: - + Extended SCP behavior shall be negotiated at Association establishment time. If an option within the extended behavior is not agreed upon in the negotiation, then only baseline SCP behavior shall be performed with respect to that option. Extended SCP behavior includes all baseline behavior with the following option: Relational-retrieve - Enhanced Multi-Frame Image - Conversion - + Enhanced Multi-Frame Image Conversion - More than one option may be agreed - upon. - + More than one option may be agreed upon.
Relational-Retrieve - The C-GET Service with - relational-retrieve removes the restriction that the SCU supply Unique Key values for - levels above the Query/Retrieve level to help identify an entity at the level of the - retrieval. Hence, the Identifier of a C-GET request may retrieve: - + The C-GET Service with relational-retrieve removes the restriction that the SCU supply Unique Key values for levels above the Query/Retrieve level to help identify an entity at the level of the retrieval. Hence, the Identifier of a C-GET request may retrieve: - all Composite Object - Instances related to a study by providing a Study Instance UID - + all Composite Object Instances related to a study by providing a Study Instance UID - all Composite Object - Instances related to a series by providing a Series Instance UID - + all Composite Object Instances related to a series by providing a Series Instance UID - individual Composite Object - Instances by providing a list of SOP Instance UIDs - + individual Composite Object Instances by providing a list of SOP Instance UIDs
Enhanced Multi-Frame Image Conversion - If Query/Retrieve View (0008,0053) - is not present in the Request Identifier, then the SCP shall identify a set of Entities - at the level of the transfer based upon the values in the Unique Keys in the Identifier - of the C-GET request that correspond to the instances it possesses, as received, and - shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. - - If Query/Retrieve View (0008,0053) - is present with a value of "CLASSIC", then the SCP shall identify a set of Entities at - the level of the transfer based upon the values in the Unique Keys in the Identifier of - the C-GET request that correspond to the Classic single frame Instances (converted from - Enhanced multi-frame Instances if required), as well as any instances that were - converted to preserve referential integrity, and any that did not need to be converted, - and shall initiate C-STORE sub-operations for all the corresponding storage SOP - Instances. - - If Query/Retrieve View (0008,0053) - is present with a value of "ENHANCED", then the SCP shall identify a set of Entities at - the level of the transfer based upon the values in the Unique Keys in the Identifier of - the C-GET request that correspond to the Enhanced multi-frame Instances (converted from - Classic single frame Instances if required), as well as any instances that were - converted to preserve referential integrity, and any that did not need to be converted, - and shall initiate C-STORE sub-operations for all the corresponding storage SOP - Instances. - + If Query/Retrieve View (0008,0053) is not present in the Request Identifier, then the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-GET request that correspond to the instances it possesses, as received, and shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. + If Query/Retrieve View (0008,0053) is present with a value of "CLASSIC", then the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-GET request that correspond to the Classic single frame Instances (converted from Enhanced multi-frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted, and shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. + If Query/Retrieve View (0008,0053) is present with a value of "ENHANCED", then the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-GET request that correspond to the Enhanced multi-frame Instances (converted from Classic single frame Instances if required), as well as any instances that were converted to preserve referential integrity, and any that did not need to be converted, and shall initiate C-STORE sub-operations for all the corresponding storage SOP Instances. - The C-GET SCP acting as - a C-STORE SCU will not send information that is duplicated to the C-GET SCU - acting as a C-STORE SCP. For example, if an entire series of single frame - instances can be converted to a separate series of converted instances, a - STUDY level C-GET will not send both series. - + The C-GET SCP acting as a C-STORE SCU will not send information that is duplicated to the C-GET SCU acting as a C-STORE SCP. For example, if an entire series of single frame instances can be converted to a separate series of converted instances, a STUDY level C-GET will not send both series. - The Query Information - Model is unchanged, and the same unique, required and optional keys are - equally applicable to both views, except that the values for the SERIES and - IMAGE level queries will be different and will depend on the converted - instance content. - + The Query Information Model is unchanged, and the same unique, required and optional keys are equally applicable to both views, except that the values for the SERIES and IMAGE level queries will be different and will depend on the converted instance content. - The Query/Retrieve View - is still required in an IMAGE or SERIES level request identifier, even - though the requested unique key(s) are unambiguous. - + The Query/Retrieve View is still required in an IMAGE or SERIES level request identifier, even though the requested unique key(s) are unambiguous. @@ -12649,99 +8737,52 @@
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes - utilize Association establishment negotiation by defining the use of Application Association - Information. See - - for an overview of Association negotiation. - - SOP Classes of the Query/Retrieve Service Class, - which include query services based on the C-FIND operation, may use SOP Class Extended Negotiation - Sub-Item to negotiate options such as Relational-queries and Enhanced Multi-Frame Image Conversion. - - SOP Classes of the Query/Retrieve Service Class, - which include retrieval services based on the C-MOVE and C-GET operations, may use the SOP Class - Extended Negotiation Sub-Item to negotiate relational-retrieval and Enhanced Multi-Frame Image - Conversion. - - SOP Classes of the Query/Retrieve Service Class, - which include retrieval services based on the C-GET operation, use the SCP/SCU Role Selection Sub-Item - to identify the SOP Classes that may be used for retrieval. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes utilize Association establishment negotiation by defining the use of Application Association Information. See for an overview of Association negotiation. + SOP Classes of the Query/Retrieve Service Class, which include query services based on the C-FIND operation, may use SOP Class Extended Negotiation Sub-Item to negotiate options such as Relational-queries and Enhanced Multi-Frame Image Conversion. + SOP Classes of the Query/Retrieve Service Class, which include retrieval services based on the C-MOVE and C-GET operations, may use the SOP Class Extended Negotiation Sub-Item to negotiate relational-retrieval and Enhanced Multi-Frame Image Conversion. + SOP Classes of the Query/Retrieve Service Class, which include retrieval services based on the C-GET operation, use the SCP/SCU Role Selection Sub-Item to identify the SOP Classes that may be used for retrieval.
Association Negotiation for C-FIND SOP Classes - The following negotiation rules apply to DICOM - SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service Class that include the - C-FIND operation. - - The Association-requester (query SCU role) - shall convey in the A-ASSOCIATE request: - + The following negotiation rules apply to DICOM SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service Class that include the C-FIND operation. + The Association-requestor (query SCU role) shall convey in the A-ASSOCIATE request: - one Abstract Syntax, in a Presentation - Context, for each query based SOP Class supported - + one Abstract Syntax, in a Presentation Context, for each query based SOP Class supported - optionally, one SOP Class Extended - Negotiation Sub-Item, for each query based SOP Class - + optionally, one SOP Class Extended Negotiation Sub-Item, for each query based SOP Class - The Association-acceptor (query SCP role) of an - A-ASSOCIATE request shall accept: - + The Association-acceptor (query SCP role) of an A-ASSOCIATE request shall accept: - one Abstract Syntax, in a Presentation - Context, for each query based SOP Class supported - + one Abstract Syntax, in a Presentation Context, for each query based SOP Class supported - optionally, one SOP Class Extended - Negotiation Sub-Item, for each query based SOP Class - + optionally, one SOP Class Extended Negotiation Sub-Item, for each query based SOP Class
SOP Class Extended Negotiation - The SOP Class Extended Negotiation allows, - at Association establishment, peer DICOM AEs to exchange application Association information - defined by specific SOP Classes. + The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. - The Service-class-application-information field is used to define support for - relational-queries, combined date time matching, fuzzy semantic matching of person names, - timezone query adjustment, Enhanced Multi-Frame Image Conversion, Empty Value Matching, and - Multiple Value Matching. - - This negotiation is optional. If absent, - the default conditions shall be: - + The Service-class-application-information field is used to define support for relational-queries, combined date time matching, fuzzy semantic matching of person names, timezone query adjustment, Enhanced Multi-Frame Image Conversion, Empty Value Matching, and Multiple Value Matching. + This negotiation is optional. If absent, the default conditions shall be: no relational-query support - separate (independent) Range - Matching of date and time Attributes - + separate (independent) Range Matching of date and time Attributes - literal matching of person names - with case sensitivity unspecified - + literal matching of person names with case sensitivity unspecified - timezone query adjustment - unspecified - + timezone query adjustment unspecified - no Enhanced Multi-Frame Image - Conversion support - + no Enhanced Multi-Frame Image Conversion support no Empty Value Matching @@ -12750,93 +8791,43 @@ no Multiple Value Matching - The Association-requester, for each SOP - Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the - corresponding Abstract Syntax Name (as defined by) - followed by the Service-class-application-information field. This field defines one or more - sub-fields: - + The Association-requestor, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by ) followed by the Service-class-application-information field. This field defines one or more sub-fields: - relational-query support by the - Association-requester - + relational-query support by the Association-requestor - combined date and time Range - Matching by the Association-requester - + combined date and time Range Matching by the Association-requestor - literal or fuzzy semantic matching - of person names by the Association-requester - + literal or fuzzy semantic matching of person names by the Association-requestor - timezone query adjustment by the - Association-requester - + timezone query adjustment by the Association-requestor - Enhanced Multi-Frame Image - Conversion support by the Association-requester - + Enhanced Multi-Frame Image Conversion support by the Association-requestor - Empty Value Matching support by the - Association-requester - + Empty Value Matching support by the Association-requestor - Multiple Value Matching support by - the Association-requester - + Multiple Value Matching support by the Association-requestor - The Association-acceptor shall return a - single byte field (single sub-field) if offered a single byte field (single sub-field) by the - Association-requester. The Association-acceptor may return either a single byte field (single - sub-field) or a multiple byte field if offered a multiple byte field by the - Association-requester. A one byte response to a multiple byte request means that the missing - sub-fields shall be treated as 0 values. - + The Association-acceptor shall return a single byte field (single sub-field) if offered a single byte field (single sub-field) by the Association-requestor. The Association-acceptor may return either a single byte field (single sub-field) or a multiple byte field if offered a multiple byte field by the Association-requestor. A one byte response to a multiple byte request means that the missing sub-fields shall be treated as 0 values. - The restriction to return only a single - byte field if that was all that was offered is because the original DICOM Standard only - contained one byte and older systems may not be expecting more. - + The restriction to return only a single byte field if that was all that was offered is because the original DICOM Standard only contained one byte and older systems may not be expecting more. - The Association-acceptor, for each - sub-field of the SOP Class Extended Negotiation Sub-Item offered, either accepts the - Association-requester proposal by returning the same value (1) or turns down the proposal by - returning the value (0). - - If the SOP Class Extended Negotiation - Sub-Item is not returned by the Association-acceptor then relational-queries are not supported - over the Association (default condition). - - If the SOP Class Extended Negotiation - Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE - response. - + The Association-acceptor, for each sub-field of the SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requestor proposal by returning the same value (1) or turns down the proposal by returning the value (0). + If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then relational-queries are not supported over the Association (default condition). + If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ) - The SOP Class Extended Negotiation - Sub-Item consists of a sequence of mandatory fields as defined by - . - - defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes - and Specialized DICOM Query/Retrieve SOP Classes that include the C-FIND operation. - This field may be either one or more bytes in length (i.e., item bytes 2 through 7 are - optional). - + The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by . defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes that include the C-FIND operation. + This field may be either one or more bytes in length (i.e., item bytes 2 through 7 are optional). - + @@ -12857,20 +8847,12 @@ 1 @@ -12878,21 +8860,12 @@ 2 @@ -12900,22 +8873,12 @@ 3 @@ -12923,23 +8886,12 @@ 4 @@ -12947,23 +8899,12 @@ 5 @@ -12971,21 +8912,12 @@ 6 @@ -12993,22 +8925,12 @@ 7 @@ -13016,21 +8938,10 @@
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC) - The SOP Class Extended Negotiation - Sub-Item is made of a sequence of mandatory fields as defined by - . - - defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes - and Specialized DICOM Query/Retrieve SOP Classes that include the C-FIND operation. - This field may be either one or more bytes in length (i.e., item bytes 2 through 7 are - optional). - + The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by . defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes that include the C-FIND operation. + This field may be either one or more bytes in length (i.e., item bytes 2 through 7 are optional).
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information - Field) - A-ASSOCIATE-RQ - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
@@ -12846,8 +8837,7 @@ Field Name - Description of Field - + Description of Field
- Relational-queries - + Relational-queries - This byte field defines - relational-query support by the Association-requester. It shall be encoded - as an unsigned binary integer and shall use one of the following values - - 0 - relational queries - not supported - - 1 - relational queries - supported - + This byte field defines relational-query support by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - relational queries not supported + 1 - relational queries supported
- Date-time matching - + Date-time matching - This byte field defines - whether or not combined date and time Attribute Range Matching is requested - by the Association-requester. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - combined matching - not requested - - 1 - combined matching - requested - + This byte field defines whether or not combined date and time Attribute Range Matching is requested by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - combined matching not requested + 1 - combined matching requested
- Fuzzy semantic matching - of person names - + Fuzzy semantic matching of person names - This byte field defines - whether or not fuzzy semantic person name Attribute matching is requested by - the Association-requester. It shall be encoded as an unsigned binary integer - and shall use one of the following values - - 0 - fuzzy semantic - matching not requested - - 1 - fuzzy semantic - matching requested - + This byte field defines whether or not fuzzy semantic person name Attribute matching is requested by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - fuzzy semantic matching not requested + 1 - fuzzy semantic matching requested
- Timezone query - adjustment - + Timezone query adjustment - This byte field defines - whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be - used to adjust the query meaning for time and datetime fields in queries. It - shall be encoded as an unsigned binary integer and shall use one of the - following values - - 0 - Timezone query - adjustment not requested - - 1 - Timezone query - adjustment requested - + This byte field defines whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used to adjust the query meaning for time and datetime fields in queries. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Timezone query adjustment not requested + 1 - Timezone query adjustment requested
- Enhanced Multi-Frame - Image Conversion - + Enhanced Multi-Frame Image Conversion - This byte field defines - whether or not the Attribute Query/Retrieve View (0008,0053) shall be used - to adjust the view returned in queries to consider conversion to or from - Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - Query/Retrieve View - not supported - - 1 - Query/Retrieve View - supported - + This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Query/Retrieve View not supported + 1 - Query/Retrieve View supported
- Empty Value Matching - + Empty Value Matching - This byte field defines - whether or not Empty Value Matching support is requested by the - Association-requester. It shall be encoded as an unsigned binary integer and - shall use one of the following values - - 0 - Empty Value - Matching not requested - - 1 - Empty Value - Matching requested - + This byte field defines whether or not Empty Value Matching support is requested by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Empty Value Matching not requested + 1 - Empty Value Matching requested
- Multiple Value - Matching - + Multiple Value Matching - This byte field defines - whether or not Multiple Value Matching support is requested by the - Association-requester. It shall be encoded as an unsigned binary integer and - shall use one of the following values - - 0 - Multiple Value - Matching not requested - - 1 - Multiple Value - Matching requested - + This byte field defines whether or not Multiple Value Matching support is requested by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Multiple Value Matching not requested + 1 - Multiple Value Matching requested
- + @@ -13051,20 +8961,12 @@ 1 @@ -13072,21 +8974,12 @@ 2 @@ -13094,22 +8987,12 @@ 3 @@ -13117,23 +9000,12 @@ 4 @@ -13141,23 +9013,12 @@ 5 @@ -13165,21 +9026,12 @@ 6 @@ -13187,22 +9039,12 @@ 7 @@ -13212,121 +9054,58 @@
Association Negotiation for C-MOVE SOP Classes - The following negotiation rules apply to DICOM - SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service Class that include the - C-MOVE operation. - - The Association-requester (retrieval SCU role) - shall convey in the A-ASSOCIATE request: - + The following negotiation rules apply to DICOM SOP Classes and Specialized DICOM SOP Classes of the Query/Retrieve Service Class that include the C-MOVE operation. + The Association-requestor (retrieval SCU role) shall convey in the A-ASSOCIATE request: - one Abstract Syntax, in a Presentation - Context, for each retrieval based SOP Class supported - + one Abstract Syntax, in a Presentation Context, for each retrieval based SOP Class supported - optionally, one SOP Class Extended - Negotiation Sub-Item, for each retrieval based SOP Class - + optionally, one SOP Class Extended Negotiation Sub-Item, for each retrieval based SOP Class - The Association-acceptor (retrieval SCP role) - of an A-ASSOCIATE request shall accept: - + The Association-acceptor (retrieval SCP role) of an A-ASSOCIATE request shall accept: - one Abstract Syntax, in a Presentation - Context, for each retrieval based SOP Class supported - + one Abstract Syntax, in a Presentation Context, for each retrieval based SOP Class supported - optionally, one SOP Class Extended - Negotiation Sub-Item, for each retrieval based SOP Class - + optionally, one SOP Class Extended Negotiation Sub-Item, for each retrieval based SOP Class
SOP Class Extended Negotiation - The SOP Class Extended Negotiation allows, - at Association establishment, peer DICOM AEs to exchange application Association information - defined by specific SOP Classes. This is achieved by defining the - Service-class-application-information field. The Service-class-application-information field is - used to define support for relational-retrievals. - - This negotiation is optional. If absent, - the default condition shall be: - + The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for relational-retrievals. + This negotiation is optional. If absent, the default condition shall be: - no relational-retrieval support - + no relational-retrieval support - no Enhanced Multi-Frame Image - Conversion support - + no Enhanced Multi-Frame Image Conversion support - The Association-requester, for each SOP - Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the - corresponding Abstract Syntax Name (as defined by) - followed by the Service-class-application-information field. This field defines: - + The Association-requestor, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by ) followed by the Service-class-application-information field. This field defines: - relational-retrieval support by the - Association-requester - + relational-retrieval support by the Association-requestor - Enhanced Multi-Frame Image - Conversion support by the Association-requester - + Enhanced Multi-Frame Image Conversion support by the Association-requestor - The Association-acceptor shall return a - single byte field (single sub-field) if offered a single byte field (single sub-field) by the - Association-requester. The Association-acceptor may return either a single byte field (single - sub-field) or a multiple byte field if offered a multiple byte field by the - Association-requester. A one byte response to a multiple byte request means that the missing - sub-fields shall be treated as 0 values. - + The Association-acceptor shall return a single byte field (single sub-field) if offered a single byte field (single sub-field) by the Association-requestor. The Association-acceptor may return either a single byte field (single sub-field) or a multiple byte field if offered a multiple byte field by the Association-requestor. A one byte response to a multiple byte request means that the missing sub-fields shall be treated as 0 values. - The restriction to return only a single - byte field if that was all that was offered is because the original DICOM Standard only - contained one byte and older systems may not be expecting more. - + The restriction to return only a single byte field if that was all that was offered is because the original DICOM Standard only contained one byte and older systems may not be expecting more. - The Association-acceptor, for each SOP - Class Extended Negotiation Sub-Item offered, either accepts the Association-requester proposal - by returning the same value (1) or turns down the proposal by returning the value (0). - - If the SOP Class Extended Negotiation - Sub-Item is not returned by the Association-acceptor then relational-retrievals and Enhanced - Multi-Frame Image Conversion are not supported (default condition). - - If the SOP Class Extended Negotiation - Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE - response. - + The Association-acceptor, for each SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requestor proposal by returning the same value (1) or turns down the proposal by returning the value (0). + If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then relational-retrievals and Enhanced Multi-Frame Image Conversion are not supported (default condition). + If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ) - The SOP Class Extended Negotiation - Sub-Item consists of a sequence of mandatory fields as defined by - . - - defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes - and Specialized DICOM Query/Retrieve SOP Classes that include the C-MOVE and C-GET - operations. - + The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by . defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes that include the C-MOVE and C-GET operations.
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information - Field) - A-ASSOCIATE-AC - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
@@ -13040,8 +8951,7 @@ Field Name - Description of Field - + Description of Field
- Relational-queries - + Relational-queries - This byte field defines - relational-query support for the Association-acceptor. It shall be encoded - as an unsigned binary integer and shall use one of the following values - - 0 - relational-queries - not supported - - 1 - relational-queries - supported - + This byte field defines relational-query support for the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - relational-queries not supported + 1 - relational-queries supported
- Date-time matching - + Date-time matching - This byte field defines - whether or not combined date and time Attribute Range Matching will be - performed by the Association-acceptor. It shall be encoded as an unsigned - binary integer and shall use one of the following values - - 0 - combined matching - not performed - - 1 - combined matching - performed - + This byte field defines whether or not combined date and time Attribute Range Matching will be performed by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - combined matching not performed + 1 - combined matching performed
- Fuzzy semantic matching - of person names - + Fuzzy semantic matching of person names - This byte field defines - whether or not fuzzy semantic person name Attribute matching will be - performed by the Association-acceptor. It shall be encoded as an unsigned - binary integer and shall use one of the following values - - 0 - fuzzy semantic - matching not performed - - 1 - fuzzy semantic - matching performed - + This byte field defines whether or not fuzzy semantic person name Attribute matching will be performed by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - fuzzy semantic matching not performed + 1 - fuzzy semantic matching performed
- Timezone query - adjustment - + Timezone query adjustment - This byte field defines - whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be - used to adjust the query meaning for time and datetime fields in queries. It - shall be encoded as an unsigned binary integer and shall use one of the - following values - - 0 - Timezone adjustment - of queries not performed - - 1 - Timezone adjustment - of queries performed - + This byte field defines whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used to adjust the query meaning for time and datetime fields in queries. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Timezone adjustment of queries not performed + 1 - Timezone adjustment of queries performed
- Enhanced Multi-Frame - Image Conversion - + Enhanced Multi-Frame Image Conversion - This byte field defines - whether or not the Attribute Query/Retrieve View (0008,0053) shall be used - to adjust the view returned in queries to consider conversion to or from - Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - Query/Retrieve View - not supported - - 1 - Query/Retrieve View - supported - + This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Query/Retrieve View not supported + 1 - Query/Retrieve View supported
- Empty Value Matching - + Empty Value Matching - This byte field defines - Empty Value Matching support by the Association-acceptor. It shall be - encoded as an unsigned binary integer and shall use one of the following - values - - 0 - Empty Value - Matching not supported - - 1 - Empty Value - Matching supported - + This byte field defines Empty Value Matching support by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Empty Value Matching not supported + 1 - Empty Value Matching supported
- Multiple Value - Matching - + Multiple Value Matching - This byte field defines - Multiple Value Matching support by the Association-acceptor. It shall be - encoded as an unsigned binary integer and shall use one of the following - values - - 0 - Multiple Value - Matching not supported - - 1 - Multiple Value - Matching supported - + This byte field defines Multiple Value Matching support by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Multiple Value Matching not supported + 1 - Multiple Value Matching supported
- + @@ -13347,21 +9125,12 @@ 1 @@ -13369,23 +9138,12 @@ 2 @@ -13393,20 +9151,9 @@
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC) - The SOP Class Extended Negotiation - Sub-Item consists of a sequence of mandatory fields as defined by - . - - defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes - and Specialized DICOM Query/Retrieve SOP Classes that include the C-MOVE and C-GET - operations. - + The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by . defines the Service-class-application-information field for DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes that include the C-MOVE and C-GET operations.
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information - Field) - A-ASSOCIATE-RQ - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
@@ -13336,8 +9115,7 @@ Field Name - Description of Field - + Description of Field
- Relational-retrieval - + Relational-retrieval - This byte field defines - relational-retrieval support by the Association-requester. It shall be - encoded as an unsigned binary integer and shall use one of the following - values - - 0 - - relational-retrieval not supported - - 1 - - relational-retrieval supported - + This byte field defines relational-retrieval support by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - relational-retrieval not supported + 1 - relational-retrieval supported
- Enhanced Multi-Frame - Image Conversion - + Enhanced Multi-Frame Image Conversion - This byte field defines - whether or not the Attribute Query/Retrieve View (0008,0053) shall be used - to adjust the view returned in queries to consider conversion to or from - Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - Query/Retrieve View - not supported - - 1 - Query/Retrieve View - supported - + This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Query/Retrieve View not supported + 1 - Query/Retrieve View supported
- + @@ -13427,21 +9173,12 @@ 1 @@ -13449,23 +9186,12 @@ 2 @@ -13475,52 +9201,29 @@
Association Negotiation for C-GET SOP Classes - When an SCP performs the C-GET operation it - induces a C-STORE operation for the purpose of transmitting composite SOP Instances for Storage. - This induced C-STORE operation (called a sub-operation) requires a switch from the C-GET - Presentation Context to a Presentation Context that supports the specific C-STORE sub-operation. - - The following negotiation rules apply to - retrieval based DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes - that include the C-GET operation. - - The Association-requester (retrieve SCU role) - in the A-ASSOCIATE request shall convey: - + When an SCP performs the C-GET operation it induces a C-STORE operation for the purpose of transmitting composite SOP Instances for Storage. This induced C-STORE operation (called a sub-operation) requires a switch from the C-GET Presentation Context to a Presentation Context that supports the specific C-STORE sub-operation. + The following negotiation rules apply to retrieval based DICOM Query/Retrieve SOP Classes and Specialized DICOM Query/Retrieve SOP Classes that include the C-GET operation. + The Association-requestor (retrieve SCU role) in the A-ASSOCIATE request shall convey: C-GET operation support with: - one Abstract Syntax, in a - Presentation Context, for each SOP Class supported - + one Abstract Syntax, in a Presentation Context, for each SOP Class supported - and optionally, one SOP Class - Extended Negotiation Sub-Item, for each retrieval based SOP Class - + and optionally, one SOP Class Extended Negotiation Sub-Item, for each retrieval based SOP Class - Induced Storage sub-operation support - where the SOP Class (in the retrieval SCU role) is acting as a Storage SOP Class in the SCP - Role. See. For each supported - Storage SOP Class, the A-ASSOCIATE request contains: - + Induced Storage sub-operation support where the SOP Class (in the retrieval SCU role) is acting as a Storage SOP Class in the SCP Role. See . For each supported Storage SOP Class, the A-ASSOCIATE request contains: - one Abstract Syntax in a - Presentation Context - + one Abstract Syntax in a Presentation Context - one SCP/SCU Role Selection - Negotiation Sub-Item with the SCP-role field set to indicate support of the SCP - role. The SCP/SCU Role Selection Negotiation shall be used as defined in. - + one SCP/SCU Role Selection Negotiation Sub-Item with the SCP-role field set to indicate support of the SCP role. The SCP/SCU Role Selection Negotiation shall be used as defined in . @@ -13537,71 +9240,39 @@ - This negotiation does not place any - requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It may be set - if the Association-requester supports the Storage Service Class in the SCU role. - + This negotiation does not place any requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It may be set if the Association-requestor supports the Storage Service Class in the SCU role. - The Association-acceptor (retrieve SCP role) in - the A-ASSOCIATE response shall convey: - + The Association-acceptor (retrieve SCP role) in the A-ASSOCIATE response shall convey: C-GET operation support with: - one Abstract Syntax, in a - Presentation Context, for each SOP Class supported - + one Abstract Syntax, in a Presentation Context, for each SOP Class supported - Induced Storage sub-operation support - where the SOP Class (using the retrieval SCP role) is acting as a Storage SOP Class in the - SCU Role. See. For each supported - Storage SOP Class, the A-ASSOCIATE response contains both: - + Induced Storage sub-operation support where the SOP Class (using the retrieval SCP role) is acting as a Storage SOP Class in the SCU Role. See . For each supported Storage SOP Class, the A-ASSOCIATE response contains both: - one Abstract Syntax, in a - Presentation Context - + one Abstract Syntax, in a Presentation Context - one SCP/SCU Role Selection - Negotiation Sub-Item with the SCP-role field set to indicate the acceptance of the - Association-requester's support of the SCP role. The SCP/SCU Role Selection - Negotiation shall be used as defined in. - + one SCP/SCU Role Selection Negotiation Sub-Item with the SCP-role field set to indicate the acceptance of the Association-requestor's support of the SCP role. The SCP/SCU Role Selection Negotiation shall be used as defined in . - The negotiation does not place any - requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It may be set - if the Association-acceptor accepts the Storage SCP role. - - illustrates an example of the retrieve (C-GET) negotiation. - + The negotiation does not place any requirements on the SCU-flag of the SCP/SCU Role Selection Negotiation Sub-Item. It may be set if the Association-acceptor accepts the Storage SCP role. illustrates an example of the retrieve (C-GET) negotiation. - - illustrates an example of the retrieve (C-GET) negotiation. - + illustrates an example of the retrieve (C-GET) negotiation.
SOP Class Extended Negotiation - The SOP Class Extended Negotiation allows, - at Association establishment, peer DICOM AEs to exchange application Association information - defined by specific SOP Classes. - - This is achieved by defining the - Service-class-application-information field. The Service-class-application-information field is - used to define support for relational-retrievals and alternative views for Enhanced Multi-Frame - Image Conversion. - + The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. + This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for relational-retrievals and alternative views for Enhanced Multi-Frame Image Conversion.
An Example of the Retrieve (C-GET) Negotiation @@ -13613,17 +9284,8 @@
- Extended negotiation for SOP Classes based - on the retrieval services that include C-GET operations is identical to the negotiation defined - for C-MOVE, which is defined in - - of this Annex. - - Extended negotiation for the SOP Classes of - the Storage Service Class (for the C-STORE sub-operation) is defined in - . - + Extended Negotiation for SOP Classes based on the retrieval services that include C-GET operations is identical to the negotiation defined for C-MOVE, which is defined in of this Annex. + Extended Negotiation for the SOP Classes of the Storage Service Class (for the C-STORE sub-operation) is defined in .
@@ -13631,10 +9293,7 @@ SOP Class Definitions
Patient Root SOP Class Group - In the Patient Root Query/Retrieve Information - Model, the information is arranged into four levels that correspond to one of the four values in - element (0008,0052) shown in. - + In the Patient Root Query/Retrieve Information Model, the information is arranged into four levels that correspond to one of the four values in element (0008,0052) shown in .
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information - Field) - A-ASSOCIATE-AC - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
@@ -13416,8 +9163,7 @@ Field Name - Description of Field - + Description of Field
- Relational-retrieval - + Relational-retrieval - This byte field defines - relational-retrieval support for the Association-acceptor. It shall be - encoded as an unsigned binary integer and shall use one of the following - values - - 0 - - relational-retrievals not supported - - 1 - - relational-retrievals supported - + This byte field defines relational-retrieval support for the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - relational-retrievals not supported + 1 - relational-retrievals supported
- Enhanced Multi-Frame - Image Conversion - + Enhanced Multi-Frame Image Conversion - This byte field defines - whether or not the Attribute Query/Retrieve View (0008,0053) shall be used - to adjust the view returned in queries to consider conversion to or from - Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - Query/Retrieve View - not supported - - 1 - Query/Retrieve View - supported - + This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Query/Retrieve View not supported + 1 - Query/Retrieve View supported
@@ -13674,9 +9333,7 @@
Query/Retrieve Level Values for Patient Root
- Composite Object Instance - Information - + Composite Object Instance Information IMAGE @@ -13685,20 +9342,13 @@
- The use of the word "Images" rather than - "Composite Object Instances" is historical to allow backward compatibility with previous - editions of the standard. It should not be taken to mean that Composite Object Instances of - other than image type are not included at the level indicated by the value IMAGE. - + The use of the word "Images" rather than "Composite Object Instances" is historical to allow backward compatibility with previous editions of the standard. It should not be taken to mean that Composite Object Instances of other than image type are not included at the level indicated by the value IMAGE.
Patient Root Query/Retrieve Information Model
E/R Model - The Patient Root Query/Retrieve - Information Model may be represented by the entity relationship diagram shown in. - + The Patient Root Query/Retrieve Information Model may be represented by the entity relationship diagram shown in .
Patient Root Query/Retrieve Information Model E-R Diagram @@ -13714,37 +9364,22 @@
Patient Level - - defines the Attributes at the Patient Query/Retrieve level of the Patient Root - Query/Retrieve Information Model. - + defines the Attributes at the Patient Query/Retrieve level of the Patient Root Query/Retrieve Information Model. - A description of the - Attributes of this Information Model is contained in - - of this Part. - + A description of the Attributes of this Information Model is contained in of this Part. - Although the Patient ID may - not be globally unique, the Study Instance UID is globally unique ensuring that - no two studies may be misidentified. The scope of uniqueness of the Patient ID - may be specified using the Issuer of Patient ID (0010,0021). - + Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient ID (0010,0021). - Previously, Other Patient - IDs (0010,1000) was included in this table. This Attribute have been retired. - See PS3.4 2017a. - + Previously, Other Patient IDs (0010,1000) was included in this table. This Attribute have been retired. See PS3.4 2017a. - + @@ -14055,7 +9657,7 @@ Requirement Type - + @@ -14066,17 +9668,12 @@ (0008,0100) @@ -14130,16 +9723,12 @@ (0008,0120)
Patient Level Attributes for the Patient Root Query/Retrieve Information Model - Patient Level Attributes for the Patient Root Query/Retrieve Information Model
@@ -13783,8 +9418,7 @@
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -13795,9 +9429,7 @@
- Referenced Patient - Sequence - + Referenced Patient Sequence (0008,1120) @@ -13808,9 +9440,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -13821,9 +9451,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -13834,8 +9462,7 @@
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -13846,8 +9473,7 @@
- Patient's Birth Time - + Patient's Birth Time (0010,0032) @@ -13869,9 +9495,7 @@
- Other Patient IDs - Sequence - + Other Patient IDs Sequence (0010,1002) @@ -13882,8 +9506,7 @@
- Other Patient Names - + Other Patient Names (0010,1001) @@ -13916,9 +9539,7 @@
- Number of Patient - Related Studies - + Number of Patient Related Studies (0020,1200) @@ -13929,9 +9550,7 @@
- Number of Patient - Related Series - + Number of Patient Related Series (0020,1202) @@ -13942,9 +9561,7 @@
- Number of Patient - Related Instances - + Number of Patient Related Instances (0020,1204) @@ -13970,25 +9587,14 @@
Study Level - - defines the keys at the Study Information level of the Patient Root Query/Retrieve - Information Model. - + defines the keys at the Study Information level of the Patient Root Query/Retrieve Information Model. - A description of the - Attributes of this Information Model is contained in - - of this Part. - + A description of the Attributes of this Information Model is contained in of this Part. - Although the Patient ID may - not be globally unique, the Study Instance UID is globally unique ensuring that - no two studies may be misidentified. The scope of uniqueness of the Patient ID - may be specified using the Issuer of Patient ID (0010,0021). - + Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient ID (0010,0021). @@ -14011,17 +9617,14 @@
- Include - - - +Include + +
- Equivalent Code - Sequence - + Equivalent Code Sequence (0008,0121) @@ -14033,10 +9636,9 @@
- >Include - - - +>Include + +
- OC - May be present - only if the code value length is 16 characters or less, and the code value - is not a URN or URL. - + OC - May be present only if the code value length is 16 characters or less, and the code value is not a URN or URL.
- Coding Scheme - Designator - + Coding Scheme Designator (0008,0102) @@ -14087,8 +9684,7 @@
- Coding Scheme Version - + Coding Scheme Version (0008,0103) @@ -14116,10 +9712,7 @@ (0008,0119) - OC - May be present - only if Code Value (0008,0100) is not present, and the code value is not a - URN or URL. - + OC - May be present only if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
- OC - May be present - only if Code Value (0008,0100) is not present, and the code value is a URN - or URL. - + OC - May be present only if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Context Identifier - + Context Identifier (0008,010F) @@ -14172,8 +9761,7 @@
- Mapping Resource UID - + Mapping Resource UID (0008,0118) @@ -14184,8 +9772,7 @@
- Context Group Version - + Context Group Version (0008,0106) @@ -14196,9 +9783,7 @@
- Context Group Extension - Flag - + Context Group Extension Flag (0008,010B) @@ -14209,9 +9794,7 @@
- Context Group Local - Version - + Context Group Local Version (0008,0107) @@ -14222,9 +9805,7 @@
- Context Group Extension - Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -14297,8 +9878,7 @@
- Study Instance UID - + Study Instance UID (0020,000D) @@ -14309,8 +9889,7 @@
- Modalities in Study - + Modalities in Study (0008,0061) @@ -14321,8 +9900,7 @@
- SOP Classes in Study - + SOP Classes in Study (0008,0062) @@ -14333,9 +9911,7 @@
- Anatomic Regions in - Study Code Sequence - + Anatomic Regions in Study Code Sequence (0008,0063) @@ -14347,17 +9923,14 @@
- >Include - - - +>Include + +
- Referring Physician's - Name - + Referring Physician's Name (0008,0090) @@ -14368,8 +9941,7 @@
- Study Description - + Study Description (0008,1030) @@ -14380,9 +9952,7 @@
- Procedure Code - Sequence - + Procedure Code Sequence (0008,1032) @@ -14394,17 +9964,14 @@
- >Include - - - +>Include + +
- Name of Physician(s) - Reading Study - + Name of Physician(s) Reading Study (0008,1060) @@ -14415,9 +9982,7 @@
- Admitting Diagnoses - Description - + Admitting Diagnoses Description (0008,1080) @@ -14428,9 +9993,7 @@
- Referenced Study - Sequence - + Referenced Study Sequence (0008,1110) @@ -14441,9 +10004,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -14454,9 +10015,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -14511,9 +10070,7 @@
- Additional Patient - History - + Additional Patient History (0010,21B0) @@ -14524,8 +10081,7 @@
- Other Study Numbers - + Other Study Numbers (0020,1070) @@ -14536,9 +10092,7 @@
- Number of Study Related - Series - + Number of Study Related Series (0020,1206) @@ -14549,9 +10103,7 @@
- Number of Study Related - Instances - + Number of Study Related Instances (0020,1208) @@ -14562,8 +10114,7 @@
- Study Update DateTime - + Study Update DateTime (0008,041F) @@ -14589,13 +10140,9 @@
Series Level - - defines the keys at the Series Information level of the Patient Root Query/Retrieve - Information Model. - + defines the keys at the Series Information level of the Patient Root Query/Retrieve Information Model. - +
Series Level Attributes for the Patient Root Query/Retrieve Information Model - Series Level Attributes for the Patient Root Query/Retrieve Information Model
@@ -14634,8 +10181,7 @@
- Series Instance UID - + Series Instance UID (0020,000E) @@ -14646,9 +10192,7 @@
- Number of Series - Related Instances - + Number of Series Related Instances (0020,1209) @@ -14671,23 +10215,15 @@
- The Attribute Number of Series - Related Instances is an optional key. It is, however recognized as a broadly needed key - and return Attribute, which SCPs are strongly encouraged to support. - + The Attribute Number of Series Related Instances is an optional key. It is, however recognized as a broadly needed key and return Attribute, which SCPs are strongly encouraged to support.
Composite Object Instance Level - - defines the keys at the Composite Object Instance Information level of the Patient Root - Query/Retrieve Information Model. - + defines the keys at the Composite Object Instance Information level of the Patient Root Query/Retrieve Information Model. - +
Composite Object Instance Level Keys for the Patient Root Query/Retrieve - Information Model - Composite Object Instance Level Keys for the Patient Root Query/Retrieve Information Model
@@ -14737,9 +10273,7 @@
- Available Transfer - Syntax UID - + Available Transfer Syntax UID (0008,3002) @@ -14750,9 +10284,7 @@
- Alternate - Representation Sequence - + Alternate Representation Sequence (0008,3001) @@ -14763,9 +10295,7 @@
- >Series Instance - UID - + >Series Instance UID (0020,000E) @@ -14776,8 +10306,7 @@
- >SOP Class UID - + >SOP Class UID (0008,1150) @@ -14788,8 +10317,7 @@
- >SOP Instance UID - + >SOP Instance UID (0008,1155) @@ -14800,9 +10328,7 @@
- >Purpose of - Reference Code Sequence - + >Purpose of Reference Code Sequence (0040,A170) @@ -14814,17 +10340,14 @@
- >>Include - - - +>>Include + +
- Related General SOP - Class UID - + Related General SOP Class UID (0008,001A) @@ -14835,9 +10358,7 @@
- Concept Name Code - Sequence - + Concept Name Code Sequence (0040,A043) @@ -14849,17 +10370,14 @@
- >Include - - - +>Include + +
- Content Template - Sequence - + Content Template Sequence (0040,A504) @@ -14870,9 +10388,7 @@
- >Template - Identifier - + >Template Identifier (0040,DB00) @@ -14883,8 +10399,7 @@
- >Mapping Resource - + >Mapping Resource (0008,0105) @@ -14895,8 +10410,7 @@
- Container Identifier - + Container Identifier (0040,0512) @@ -14907,9 +10421,7 @@
- Specimen Description - Sequence - + Specimen Description Sequence (0040,0560) @@ -14920,9 +10432,7 @@
- >Specimen - Identifier - + >Specimen Identifier (0040,0551) @@ -14945,9 +10455,7 @@
- All Other Attributes at Composite Object Instance - Level - + All Other Attributes at Composite Object Instance Level @@ -14960,292 +10468,115 @@ - SOP Class UID (0008,0016) - is an optional key, but it is strongly recommended that it always be returned by - all SCPs, if matching is requested. - + SOP Class UID (0008,0016) is an optional key, but it is strongly recommended that it always be returned by all SCPs, if matching is requested. - The Concept Name Code - Sequence (0040,A043) and Content Template Sequence (0040,A504) are optional keys - that are useful for identifying instances of various Structured Reporting - Storage SOP Classes. It is strongly recommended that these keys be supported by - the SCP for query against such instances. - + The Concept Name Code Sequence (0040,A043) and Content Template Sequence (0040,A504) are optional keys that are useful for identifying instances of various Structured Reporting Storage SOP Classes. It is strongly recommended that these keys be supported by the SCP for query against such instances.
Alternate Representation Sequence - The Alternate Representation - Sequence (0008,3001) encodes a reference to an alternate encoding of the composite image - identified in the Query response item. This alternate encoding may utilize a different - SOP Class or have different image quality characteristics, but it shall be the same - image. - + The Alternate Representation Sequence (0008,3001) encodes a reference to an alternate encoding of the composite image identified in the Query response item. This alternate encoding may utilize a different SOP Class or have different image quality characteristics, but it shall be the same image. - The Alternate Representation - Sequence (0008,3001) allows the query response about an original image to reference - a lossy compressed version, and vice versa. - + The Alternate Representation Sequence (0008,3001) allows the query response about an original image to reference a lossy compressed version, and vice versa. - An image may be lossy compressed, - e.g., for long-term archive purposes, and its SOP Instance UID changed. An application - processing a SOP Instance that references the original image UID, e.g., a Structured - Report, may query the C-FIND SCP for the image. The SCP returns a reference to an - accessible version of the image even if the original SOP Instance is no longer - available. - - The Alternate Representation - Sequence (0008,3001), if present in a Query Request Identifier, shall be zero-length, or - shall contain a single zero-length Item. That is, only Universal Matching is defined for - this Attribute. - - The Alternate Representation - Sequence (0008,3001), if present in the Query Response Identifier, may include zero or - more Items. Each Alternate Representation Sequence Item in the Query Response Identifier - shall include - + An image may be lossy compressed, e.g., for long-term archive purposes, and its SOP Instance UID changed. An application processing a SOP Instance that references the original image UID, e.g., a Structured Report, may query the C-FIND SCP for the image. The SCP returns a reference to an accessible version of the image even if the original SOP Instance is no longer available. + The Alternate Representation Sequence (0008,3001), if present in a Query Request Identifier, shall be zero-length, or shall contain a single zero-length Item. That is, only Universal Matching is defined for this Attribute. + The Alternate Representation Sequence (0008,3001), if present in the Query Response Identifier, may include zero or more Items. Each Alternate Representation Sequence Item in the Query Response Identifier shall include - the Series Instance UID - (0020,000E) if the alternately encoded image is in a different Series. - + the Series Instance UID (0020,000E) if the alternately encoded image is in a different Series. - the SOP Class UID - (0008,0016) and SOP Instance UID (0008,0018) of the alternately encoded image. - + the SOP Class UID (0008,0016) and SOP Instance UID (0008,0018) of the alternately encoded image. - the Purpose of Reference - Code Sequence (0040,A170), which shall describe the nature of the alternate - encoding of the image. The Purpose of Reference Code Sequence (0040,A170) shall - include only one Item. The Baseline Context Group for this Code Sequence is CID - 7205. - + the Purpose of Reference Code Sequence (0040,A170), which shall describe the nature of the alternate encoding of the image. The Purpose of Reference Code Sequence (0040,A170) shall include only one Item. The Baseline Context Group for this Code Sequence is CID 7205.
Available SOP Transfer Syntax UID - The Available Transfer Syntax UID - (0008,3002) describes one or more Transfer Syntaxes that the SCP can assure will be - supported for retrieval of the SOP Instance. This may, but is not required to, include - the Transfer Syntax in which the SCP has stored the instance. For all Transfer Syntaxes - listed, no loss shall be involved in transcoding from whatever is stored. - - The Attribute is multi-valued, and - if more than one value is present, then the SCU may interpret those Transfer Syntaxes - listed earlier as being preferred by the SCP over those listed later. E.g., the order - might reflect the amount of effort required to convert from the stored form, and the - first listed might be the stored form. - - There is no requirement to include - every Transfer Syntax in which the instance may be retrieved without loss. E.g., the - Default Transfer Syntax as specified in, if it - is applicable, might be omitted if it is not the Transfer Syntax in which the instance - happens to be stored. - + The Available Transfer Syntax UID (0008,3002) describes one or more Transfer Syntaxes that the SCP can assure will be supported for retrieval of the SOP Instance. This may, but is not required to, include the Transfer Syntax in which the SCP has stored the instance. For all Transfer Syntaxes listed, no loss shall be involved in transcoding from whatever is stored. + The Attribute is multi-valued, and if more than one value is present, then the SCU may interpret those Transfer Syntaxes listed earlier as being preferred by the SCP over those listed later. E.g., the order might reflect the amount of effort required to convert from the stored form, and the first listed might be the stored form. + There is no requirement to include every Transfer Syntax in which the instance may be retrieved without loss. E.g., the Default Transfer Syntax as specified in , if it is applicable, might be omitted if it is not the Transfer Syntax in which the instance happens to be stored. - The value of this Attribute may - be useful, for example, to determine if the the instance is stored in a lossy - Transfer Syntax that is not supported by the SCU, and for which decompression or - conversion into a different compressed form would involve loss and be inappropriate, - and require use of an Alternate Representation. - + The value of this Attribute may be useful, for example, to determine if the the instance is stored in a lossy Transfer Syntax that is not supported by the SCU, and for which decompression or conversion into a different compressed form would involve loss and be inappropriate, and require use of an Alternate Representation.
Scope of the C-GET and C-MOVE Commands and Sub-Operations - A C-MOVE or C-GET request may be - performed to any level of the Query/Retrieve Model. However, the transfer of Stored SOP - Instances shall always take place at the Composite Object Instance level. A C-MOVE or C-GET - where the Query/Retrieve level is the: - + A C-MOVE or C-GET request may be performed to any level of the Query/Retrieve Model. However, the transfer of Stored SOP Instances shall always take place at the Composite Object Instance level. A C-MOVE or C-GET where the Query/Retrieve level is the: - PATIENT level indicates that - all Composite Object Instances related to a Patient shall be transferred. - + PATIENT level indicates that all Composite Object Instances related to a Patient shall be transferred. - STUDY level indicates that all - Composite Object Instances related to a Study shall be transferred. - + STUDY level indicates that all Composite Object Instances related to a Study shall be transferred. - SERIES level indicates that all - Composite Object Instances related to a Series shall be transferred. - + SERIES level indicates that all Composite Object Instances related to a Series shall be transferred. - IMAGE level indicates that - selected individual Composite Object Instances shall be transferred. - + IMAGE level indicates that selected individual Composite Object Instances shall be transferred. - In the Baseline behavior, more than - one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using - List of UID matching, but only Single Value Matching value may be specified for Patient - ID (0010,0020). - + In the Baseline behavior, more than one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using List of UID matching, but only Single Value Matching value may be specified for Patient ID (0010,0020).
Conformance Requirements - An implementation may conform to one of the - SOP Classes of the Patient Root SOP Class Group as an SCU, SCP or both. The Conformance - Statement shall be in the format defined in. - + An implementation may conform to one of the SOP Classes of the Patient Root SOP Class Group as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group shall support queries against - the Query/Retrieve Information Model described in - - using the baseline C-FIND SCU Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its - Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, - then it shall list the Optional Keys that it supports. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its - Conformance Statement whether it may generate Relational-queries. If it supports - Relational-queries, then it shall also support extended negotiation of - relational-queries as an SCU. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its - Conformance Statement whether or not it supports extended negotiation of combined - date-time matching, fuzzy semantic matching of person names, Empty Value Matching, - and/or Multiple Value Matching. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) and - Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses. - + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in using the baseline C-FIND SCU Behavior described in . + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, then it shall list the Optional Keys that it supports. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement whether it may generate Relational-queries. If it supports Relational-queries, then it shall also support Extended Negotiation of relational-queries as an SCU. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, Empty Value Matching, and/or Multiple Value Matching. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall support - transfers against the Query/Retrieve Information Model described in - - using the C-MOVE SCU Behavior described in. - + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall support transfers against the Query/Retrieve Information Model described in using the C-MOVE SCU Behavior described in .
C-GET SCU Conformance - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall support - retrievals against the Query/Retrieve Information Model described in - - using the C-GET SCU Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCU, which generates - retrievals using the C-GET operation, shall state in its Conformance Statement the - Storage Service Class SOP Classes under which it shall support the C-STORE - sub-operations generated by the C-GET. - + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU shall support retrievals against the Query/Retrieve Information Model described in using the C-GET SCU Behavior described in . + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCU, which generates retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group shall support queries against - the Query/Retrieve Information Model described in - - using the C-FIND SCP Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its - Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, - then it shall list the Optional Keys that it supports. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its - Conformance Statement whether it supports Relational-queries. If it supports - Relational-queries, then it shall also support extended negotiation of - relational-queries as an SCP. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its - Conformance Statement whether or not it supports extended negotiation of combined - date-time matching, fuzzy semantic matching of person names, Empty Value Matching, - and/or Multiple Value Matching. If fuzzy semantic matching of person names is supported, - then the mechanism for fuzzy semantic matching shall be specified. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its - Conformance Statement whether it supports case-insensitive matching for PN VR Attributes - and list Attributes for which this applies. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) and - Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and - encoding responses. - + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in using the C-FIND SCP Behavior described in . + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, then it shall list the Optional Keys that it supports. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Relational-queries. If it supports Relational-queries, then it shall also support Extended Negotiation of relational-queries as an SCP. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, Empty Value Matching, and/or Multiple Value Matching. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports case-insensitive matching for PN VR Attributes and list Attributes for which this applies. + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.
C-MOVE SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall support - transfers against the Query/Retrieve Information Model described in - - using the C-MOVE SCP Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP, which generates - transfers using the C-MOVE operation shall state in its Conformance Statement the - Storage Service Class SOP Classes under which it shall support the C-STORE - sub-operations generated by the C-MOVE. - + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall support transfers against the Query/Retrieve Information Model described in using the C-MOVE SCP Behavior described in . + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP, which generates transfers using the C-MOVE operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall support - retrievals against the Query/Retrieve Information Model described in - - using the C-GET SCP Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Patient Root SOP Class Group as an SCP, which generates - retrievals using the C-GET operation, shall state in its Conformance Statement the - Storage Service Class SOP Classes under which it shall support the C-STORE - sub-operations generated by the C-GET. - + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP shall support retrievals against the Query/Retrieve Information Model described in using the C-GET SCP Behavior described in . + An implementation that conforms to one of the SOP Classes of the Patient Root SOP Class Group as an SCP, which generates retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SOP Classes - The SOP Classes in the Patient Root Query - SOP Class Group of the Query/Retrieve Service Class identify the Patient Root Query/Retrieve - Information Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in - . - + The SOP Classes in the Patient Root Query SOP Class Group of the Query/Retrieve Service Class identify the Patient Root Query/Retrieve Information Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in . @@ -15261,38 +10592,26 @@ @@ -15301,10 +10620,7 @@
Study Root SOP Class Group - In the Study Root Query/Retrieve Information - Model, the information is arranged into three levels that correspond to one of the three values in - element (0008,0052) shown in. - + In the Study Root Query/Retrieve Information Model, the information is arranged into three levels that correspond to one of the three values in element (0008,0052) shown in .
SOP Classes for Patient Root Query/Retrieve
- Patient Root Query/Retrieve - Information Model - FIND - + Patient Root Query/Retrieve Information Model - FIND - - 1.2.840.10008.5.1.4.1.2.1.1 - + 1.2.840.10008.5.1.4.1.2.1.1
- Patient Root Query/Retrieve - Information Model - MOVE - + Patient Root Query/Retrieve Information Model - MOVE - - 1.2.840.10008.5.1.4.1.2.1.2 - + 1.2.840.10008.5.1.4.1.2.1.2
- Patient Root Query/Retrieve - Information Model - GET - + Patient Root Query/Retrieve Information Model - GET - - 1.2.840.10008.5.1.4.1.2.1.3 - + 1.2.840.10008.5.1.4.1.2.1.3
@@ -15336,9 +10652,7 @@
Query/Retrieve Level Values for Study Root
- Composite Object Instance - Information - + Composite Object Instance Information IMAGE @@ -15347,20 +10661,13 @@
- The use of the word "Images" rather than - "Composite Object Instances" is historical to allow backward compatibility with previous - editions of the Standard. It should not be taken to mean that Composite Object Instances of - other than image type are not included at the level indicated by the value IMAGE. - + The use of the word "Images" rather than "Composite Object Instances" is historical to allow backward compatibility with previous editions of the Standard. It should not be taken to mean that Composite Object Instances of other than image type are not included at the level indicated by the value IMAGE.
Study Root Query/Retrieve Information Model
E/R Model - The Study Root Query/Retrieve - Information Model may be represented by the entity relationship diagram shown in. - + The Study Root Query/Retrieve Information Model may be represented by the entity relationship diagram shown in .
Study Root Query/Retrieve Information Model E-R Diagram @@ -15376,31 +10683,17 @@
Study Level - - defines the keys at the Study Information level of the Study Root Query/Retrieve Information - Model. - + defines the keys at the Study Information level of the Study Root Query/Retrieve Information Model. - A description of the - Attributes of this Information Model is contained in - . - + A description of the Attributes of this Information Model is contained in . - Although the Patient ID may - not be globally unique, the Study Instance UID is globally unique ensuring that - no two studies may be misidentified. The scope of uniqueness of the Patient ID - may be specified using the Issuer of Patient ID (0010,0021). - + Although the Patient ID may not be globally unique, the Study Instance UID is globally unique ensuring that no two studies may be misidentified. The scope of uniqueness of the Patient ID may be specified using the Issuer of Patient ID (0010,0021). - Previously, Other Patient - IDs (0010,1000) was included in this table. This Attribute have been retired. - See PS3.4 2017a. - + Previously, Other Patient IDs (0010,1000) was included in this table. This Attribute have been retired. See PS3.4 2017a. @@ -15488,8 +10781,7 @@
- Study Instance UID - + Study Instance UID (0020,000D) @@ -15500,8 +10792,7 @@
- Modalities in Study - + Modalities in Study (0008,0061) @@ -15512,8 +10803,7 @@
- SOP Classes in Study - + SOP Classes in Study (0008,0062) @@ -15524,9 +10814,7 @@
- Anatomic Regions in - Study Code Sequence - + Anatomic Regions in Study Code Sequence (0008,0063) @@ -15538,17 +10826,14 @@
- >Include - - - +>Include + +
- Referring Physician's - Name - + Referring Physician's Name (0008,0090) @@ -15559,8 +10844,7 @@
- Study Description - + Study Description (0008,1030) @@ -15571,9 +10855,7 @@
- Procedure Code - Sequence - + Procedure Code Sequence (0008,1032) @@ -15585,17 +10867,14 @@
- >Include - - - +>Include + +
- Name of Physician(s) - Reading Study - + Name of Physician(s) Reading Study (0008,1060) @@ -15606,9 +10885,7 @@
- Admitting Diagnoses - Description - + Admitting Diagnoses Description (0008,1080) @@ -15619,9 +10896,7 @@
- Referenced Study - Sequence - + Referenced Study Sequence (0008,1110) @@ -15632,9 +10907,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -15645,9 +10918,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -15658,9 +10929,7 @@
- Referenced Patient - Sequence - + Referenced Patient Sequence (0008,1120) @@ -15671,9 +10940,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -15684,9 +10951,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -15697,8 +10962,7 @@
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -15709,8 +10973,7 @@
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -15721,8 +10984,7 @@
- Patient's Birth Time - + Patient's Birth Time (0010,0032) @@ -15744,9 +11006,7 @@
- Other Patient IDs - Sequence - + Other Patient IDs Sequence (0010,1002) @@ -15757,8 +11017,7 @@
- Other Patient Names - + Other Patient Names (0010,1001) @@ -15824,9 +11083,7 @@
- Additional Patient - History - + Additional Patient History (0010,21B0) @@ -15848,8 +11105,7 @@
- Other Study Numbers - + Other Study Numbers (0020,1070) @@ -15860,9 +11116,7 @@
- Number of Study Related - Series - + Number of Study Related Series (0020,1206) @@ -15873,9 +11127,7 @@
- Number of Study Related - Instances - + Number of Study Related Instances (0020,1208) @@ -15886,8 +11138,7 @@
- Study Update DateTime - + Study Update DateTime (0008,041F) @@ -15910,215 +11161,86 @@
- The use of the word "Images" rather - than "Composite Object Instances" is historical, and should not be taken to mean that - Composite Object Instances of other than image type are not included in the number. - + The use of the word "Images" rather than "Composite Object Instances" is historical, and should not be taken to mean that Composite Object Instances of other than image type are not included in the number.
Series Level - Attributes for the Series Level of the - Study Root Query/Retrieve Information Model are the same as the Attributes for the Series - Level of the Patient Root Query/Retrieve Information Model described in. - + Attributes for the Series Level of the Study Root Query/Retrieve Information Model are the same as the Attributes for the Series Level of the Patient Root Query/Retrieve Information Model described in .
Composite Object Instance Level - Attributes for the Composite Object - Instance Level of the Study Root Query/Retrieve Information Model are the same as the - Attributes for the Composite Object Instance Level of the Patient Root Query/Retrieve - Information Model described in. - + Attributes for the Composite Object Instance Level of the Study Root Query/Retrieve Information Model are the same as the Attributes for the Composite Object Instance Level of the Patient Root Query/Retrieve Information Model described in .
Scope of the Get and Move Commands and Sub-Operations - A C-MOVE or C-GET request may be - performed to any level of the Query/Retrieve Model. However, the transfer of Stored SOP - Instances shall always take place at the Composite Object Instance level. A C-MOVE or C-GET - where the Query/Retrieve level is the: - + A C-MOVE or C-GET request may be performed to any level of the Query/Retrieve Model. However, the transfer of Stored SOP Instances shall always take place at the Composite Object Instance level. A C-MOVE or C-GET where the Query/Retrieve level is the: - STUDY level indicates that all - Composite Object Instances related to a Study shall be transferred - + STUDY level indicates that all Composite Object Instances related to a Study shall be transferred - SERIES level indicates that all - Composite Object Instances related to a Series shall be transferred - + SERIES level indicates that all Composite Object Instances related to a Series shall be transferred - IMAGE level indicates that - selected individual Composite Object Instances shall be transferred - + IMAGE level indicates that selected individual Composite Object Instances shall be transferred - In the Baseline behavior, more than - one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using - List of UID matching, - + In the Baseline behavior, more than one entity may be retrieved if the Query/Retrieve Level is IMAGE, SERIES or STUDY, using List of UID matching,
Conformance Requirements - An implementation may conform to one of the - SOP Classes of the Study Hierarchy SOP Class Group as an SCU, SCP or both. The Conformance - Statement shall be in the format defined in. - + An implementation may conform to one of the SOP Classes of the Study Hierarchy SOP Class Group as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group shall support queries against - the Query/Retrieve Information Model described in - - using the C-FIND SCU behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its - Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, - then it shall list the Optional Keys that it supports. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall be capable of - generating queries using the Hierarchical Search. It shall not generate queries using - Relational-queries unless the Relational-queries option has been successfully - negotiated. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its - Conformance Statement whether it may generate Relational-queries. If it supports - Relational Search, then it shall also support extended negotiation of relational-queries - as an SCU. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its - Conformance Statement whether or not it supports extended negotiation of combined - date-time matching, fuzzy semantic matching of person names, Empty Value Matching, - and/or Multiple Value Matching. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) and - Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses. - + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in using the C-FIND SCU behavior described in . + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, then it shall list the Optional Keys that it supports. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall be capable of generating queries using the Hierarchical Search. It shall not generate queries using Relational-queries unless the Relational-queries option has been successfully negotiated. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its Conformance Statement whether it may generate Relational-queries. If it supports Relational Search, then it shall also support Extended Negotiation of relational-queries as an SCU. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its Conformance Statement whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, Empty Value Matching, and/or Multiple Value Matching. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall support - transfers against the Query/Retrieve Information Model described in - - using the C-MOVE SCU Behavior described in. - + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall support transfers against the Query/Retrieve Information Model described in using the C-MOVE SCU Behavior described in .
C-GET SCU Conformance - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU shall support - retrievals against the Query/Retrieve Information Model described in - - using the C-GET SCU Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCU, which generates - retrievals using the C-GET operation shall state in its Conformance Statement the - Storage Service Class SOP Classes under which it shall support the C-STORE - sub-operations generated by the C-GET. - + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU shall support retrievals against the Query/Retrieve Information Model described in using the C-GET SCU Behavior described in . + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCU, which generates retrievals using the C-GET operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group shall support queries against - the Query/Retrieve Information Model described in - - using the C-FIND SCP behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its - Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, - then it shall list the Optional Keys that it supports. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its - Conformance Statement whether it supports Relational Search. If it supports Relational - Search, then it shall also support extended negotiation of relational-queries as an SCP. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its - Conformance Statement whether or not it supports extended negotiation of combined - date-time matching, fuzzy semantic matching of person names, Empty Value Matching, - and/or Multiple Value Matching. If fuzzy semantic matching of person names is supported, - then the mechanism for fuzzy semantic matching shall be specified. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its - Conformance Statement whether it supports case-insensitive matching for PN VR Attributes - and list Attributes for which this applies. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) and - Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and - encoding responses. - + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group shall support queries against the Query/Retrieve Information Model described in using the C-FIND SCP behavior described in . + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Optional Keys. If it supports Optional Keys, then it shall list the Optional Keys that it supports. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports Relational Search. If it supports Relational Search, then it shall also support Extended Negotiation of relational-queries as an SCP. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its Conformance Statement whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, Empty Value Matching, and/or Multiple Value Matching. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its Conformance Statement whether it supports case-insensitive matching for PN VR Attributes and list Attributes for which this applies. + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.
C-MOVE SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall support - transfers against the Query/Retrieve Information Model described in - - using the C-MOVE SCP Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP, which generates - transfers using the C-MOVE operation shall state in its Conformance Statement the - Storage Service Class SOP Classes under which it shall support the C-STORE - sub-operations generated by the C-MOVE. - + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall support transfers against the Query/Retrieve Information Model described in using the C-MOVE SCP Behavior described in . + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP, which generates transfers using the C-MOVE operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP shall support - retrievals against the Query/Retrieve Information Model described in - - using the C-GET SCP Behavior described in. - - An implementation that conforms to - one of the SOP Classes of the Study Root SOP Class Group as an SCP, which generates - retrievals using the C-GET operation shall state in its Conformance Statement the - Storage Service Class SOP Classes under which it shall support the C-STORE - sub-operations generated by the C-GET. - + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP shall support retrievals against the Query/Retrieve Information Model described in using the C-GET SCP Behavior described in . + An implementation that conforms to one of the SOP Classes of the Study Root SOP Class Group as an SCP, which generates retrievals using the C-GET operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SOP Classes - The SOP Classes in the Study Root SOP Class - Group of the Query/Retrieve Service Class identify the Study Root Query/Retrieve Information - Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in. - + The SOP Classes in the Study Root SOP Class Group of the Query/Retrieve Service Class identify the Study Root Query/Retrieve Information Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in . @@ -16134,38 +11256,26 @@ @@ -16178,68 +11288,34 @@
Repository Query SOP Class - The Repository Query SOP Class uses the C-FIND - Service and the Study Root Query/Retrieve Information Model. - The SOP Class specifies additional semantics and behaviors for the SCU and SCP beyond those defined - for the Study Root Query/Retrieve Information Model - FIND SOP Class. - - In particular, the Repository Query SOP Class - supports incremental query/response for a large number of entities using the following features: - + The Repository Query SOP Class uses the C-FIND Service and the Study Root Query/Retrieve Information Model. + The SOP Class specifies additional semantics and behaviors for the SCU and SCP beyond those defined for the Study Root Query/Retrieve Information Model - FIND SOP Class. + In particular, the Repository Query SOP Class supports incremental query/response for a large number of entities using the following features: - Both the SCU and SCP may set limits on - the number of entity records (Pending status responses) returned in a C-FIND transaction. - + Both the SCU and SCP may set limits on the number of entity records (Pending status responses) returned in a C-FIND transaction. - If the number of responses would exceed - the SCU or SCP limit, the C-FIND query processing is terminated with a defined Warning - status response indicating an incomplete set of responses. - + If the number of responses would exceed the SCU or SCP limit, the C-FIND query processing is terminated with a defined Warning status response indicating an incomplete set of responses. - If requested by the SCU, each response - returns a unique Record Key (0008,041B) value by which the SCP orders the C-FIND responses. - + If requested by the SCU, each response returns a unique Record Key (0008,041B) value by which the SCP orders the C-FIND responses. - The SCU may include a Record Key - (0008,041B) value it received in one C-FIND transaction as the Prior Record Key (0008,041C) - in the C-FIND Request for a subsequent transaction. - The SCP processes that subsequent C-FIND beginning with the record following that Prior - Record Key (0008,041C). - + The SCU may include a Record Key (0008,041B) value it received in one C-FIND transaction as the Prior Record Key (0008,041C) in the C-FIND Request for a subsequent transaction. + The SCP processes that subsequent C-FIND beginning with the record following that Prior Record Key (0008,041C). - The Repository Query SOP Class also supports - return of URI links for access to stored SOP Instances using a non-DICOM file access protocol. - Since stored SOP Instances accessed through a non-DICOM protocol might not include all current - metadata Attributes (such as updated patient names or IDs), the Repository Query SOP Class also - supports return of current metadata Attributes whose values might differ from those in the stored - SOP Instance. - + The Repository Query SOP Class also supports return of URI links for access to stored SOP Instances using a non-DICOM file access protocol. + Since stored SOP Instances accessed through a non-DICOM protocol might not include all current metadata Attributes (such as updated patient names or IDs), the Repository Query SOP Class also supports return of current metadata Attributes whose values might differ from those in the stored SOP Instance. - See additional explanatory information in - , including discussion of the use of the - Repository Query SOP Class to produce an Inventory SOP Instance. - + See additional explanatory information in , including discussion of the use of the Repository Query SOP Class to produce an Inventory SOP Instance.
Additional Query Information Model Attributes - The Repository Query SOP Class uses the - Study Root Query/Information model specified in, but specifies - additional Key Attributes. - These Key Attributes, like those defined in, are not specified - in the Composite IODs of, but represent information that - may be used by a repository system for managing stored SOP Instances. - - defines the additional Key Attributes. - + The Repository Query SOP Class uses the Study Root Query/Information model specified in , but specifies additional Key Attributes. + These Key Attributes, like those defined in , are not specified in the Composite IODs of , but represent information that may be used by a repository system for managing stored SOP Instances. + defines the additional Key Attributes.
SOP Classes for Study Root Query/Retrieve
- Study Root Query/Retrieve - Information Model - FIND - + Study Root Query/Retrieve Information Model - FIND - - 1.2.840.10008.5.1.4.1.2.2.1 - + 1.2.840.10008.5.1.4.1.2.2.1
- Study Root Query/Retrieve - Information Model - MOVE - + Study Root Query/Retrieve Information Model - MOVE - - 1.2.840.10008.5.1.4.1.2.2.2 - + 1.2.840.10008.5.1.4.1.2.2.2
- Study Root Query/Retrieve - Information Model - GET - + Study Root Query/Retrieve Information Model - GET - - 1.2.840.10008.5.1.4.1.2.2.3 - + 1.2.840.10008.5.1.4.1.2.2.3
@@ -16254,8 +11330,7 @@ Type @@ -16271,18 +11346,12 @@ R @@ -16410,15 +11446,12 @@ - @@ -16483,20 +11509,9 @@ O @@ -16510,18 +11525,13 @@ - @@ -16690,15 +11663,8 @@ - @@ -16712,9 +11678,7 @@ - @@ -16728,21 +11692,10 @@ O @@ -16756,16 +11709,13 @@ @@ -16803,347 +11741,169 @@
Additional Keys for Repository Query
- Attribute Description - + Attribute Description
- Implementation-specific - unique identifier of the entity record. This Attribute is supported only with - Universal Matching. See. - + Implementation-specific unique identifier of the entity record. This Attribute is supported only with Universal Matching. See .
- Removed from Operational - Use - + Removed from Operational Use (0008,0405) @@ -16291,18 +11360,12 @@ O - Flag that the entity at the - Query/Retrieve Level specified in the Identifier of the C-FIND, and its set of - Composite Object Instances, have been removed from operational use related to - patient care. See. - + Flag that the entity at the Query/Retrieve Level specified in the Identifier of the C-FIND, and its set of Composite Object Instances, have been removed from operational use related to patient care. See .
- Reason for Removal Code - Sequence - + Reason for Removal Code Sequence (0008,0406) @@ -16311,35 +11374,26 @@ O - Reason the entity at the - Query/Retrieve Level specified in the Identifier of the C-FIND was removed from - operational use. - - Zero or one Item may be - included in this Sequence. - + Reason the entity at the Query/Retrieve Level specified in the Identifier of the C-FIND was removed from operational use. + Zero or one Item may be included in this Sequence.
- >Include - - + >Include + - D. - - +D. +
- File Set Access Sequence - + File Set Access Sequence (0008,0419) @@ -16348,27 +11402,14 @@ O - Description of non-DICOM - protocol access to sets of stored SOP Instances. This Attribute is defined only - at the Study and Series levels. This Attribute is supported only with Universal - Matching, i.e., if present in the Request Identifier it is zero-length or has - only a zero-length Item. See. - - See - - for additional SCP requirements. - - Zero or one Item may be - included in this Sequence in a Response Identifier. - + Description of non-DICOM protocol access to sets of stored SOP Instances. This Attribute is defined only at the Study and Series levels. This Attribute is supported only with Universal Matching, i.e., if present in the Request Identifier it is zero-length or has only a zero-length Item. See . + See for additional SCP requirements. + Zero or one Item may be included in this Sequence in a Response Identifier.
- >Stored Instance Base - URI - + >Stored Instance Base URI (0008,0407) @@ -16377,15 +11418,12 @@ - - Base URI for accessing SOP - Instances through a non-DICOM protocol. - + Base URI for accessing SOP Instances through a non-DICOM protocol.
- >Folder Access URI - + >Folder Access URI (0008,0408) @@ -16394,9 +11432,7 @@ - - Access URI for a folder - containing all SOP Instances for this Study or Series. - + Access URI for a folder containing all SOP Instances for this Study or Series.
- Access URI for a container - file containing all the SOP Instances for this Study or Series. - + Access URI for a container file containing all the SOP Instances for this Study or Series.
- >Container File Type - + >Container File Type (0008,040A) @@ -16427,8 +11460,7 @@ - - Type of container file. - + Type of container file. Defined Terms: @@ -16443,33 +11475,27 @@ - + GZIP - + TARGZIP - + BLOB - See - - for definitions of Defined Terms. - - Required in Response - Identifier if File Access URI (0008,0409) is present. - + See for definitions of Defined Terms. + Required in Response Identifier if File Access URI (0008,0409) is present.
- Description of non-DICOM - protocol access to a stored SOP Instance. This Attribute is defined only at the - Composite Instance level. This Attribute is supported only with Universal - Matching, i.e., if present in the Request Identifier it is zero-length or has - only a zero-length Item. See. - - See - - for additional SCP requirements. - - Zero or more Items may be - included in this Sequence in a Response Identifier. - + Description of non-DICOM protocol access to a stored SOP Instance. This Attribute is defined only at the Composite Instance level. This Attribute is supported only with Universal Matching, i.e., if present in the Request Identifier it is zero-length or has only a zero-length Item. See . + See for additional SCP requirements. + Zero or more Items may be included in this Sequence in a Response Identifier.
- Access URI for file - containing the SOP Instance. - - Required in Response - Identifier if File Access Sequence (0008,041A) has an Item. - + Access URI for file containing the SOP Instance. + Required in Response Identifier if File Access Sequence (0008,041A) has an Item.
- >Container File Type - + >Container File Type (0008,040A) @@ -16530,8 +11540,7 @@ - - Type of container file. - + Type of container file. Defined Terms: @@ -16561,26 +11570,17 @@ DICM - Single SOP - Instance in DICOM File Format - + Single SOP Instance in DICOM File Format - See - - for definitions of Defined Terms not described here. - - Required in Response - Identifier if File Access URI (0008,0409) is present. - + See for definitions of Defined Terms not described here. + Required in Response Identifier if File Access URI (0008,0409) is present.
- >Filename in Container - + >Filename in Container (0008,040B) @@ -16589,19 +11589,13 @@ - - Filename within a container - file of the file containing the SOP Instance. - - Required in Response - Identifier if Container File Type (0008,040A) is ZIP, TAR, or TARGZIP. - + Filename within a container file of the file containing the SOP Instance. + Required in Response Identifier if Container File Type (0008,040A) is ZIP, TAR, or TARGZIP.
- >File Offset in - Container - + >File Offset in Container (0008,040C) @@ -16610,19 +11604,13 @@ - - Byte offset (zero-based) - within a container file for the start of the SOP Instance file. - - Required in Response - Identifier if Container File Type (0008,040A) is BLOB, may be present otherwise. - + Byte offset (zero-based) within a container file for the start of the SOP Instance file. + Required in Response Identifier if Container File Type (0008,040A) is BLOB, may be present otherwise.
- >File Length in - Container - + >File Length in Container (0008,040D) @@ -16631,19 +11619,13 @@ - - Length of the SOP Instance - file within a container file. - - Required in Response - Identifier if Container File Type (0008,040A) is BLOB, may be present otherwise. - + Length of the SOP Instance file within a container file. + Required in Response Identifier if Container File Type (0008,040A) is BLOB, may be present otherwise.
- >Stored Instance - Transfer Syntax UID - + >Stored Instance Transfer Syntax UID (0008,040E) @@ -16652,20 +11634,13 @@ - - Transfer Syntax of SOP - Instance encoded in DICOM File Format. Equal to Transfer Syntax UID (0002,0010) - in File Meta Information header. - - Required in Response - Identifier if File Access Sequence (0008,041A) has an Item. - + Transfer Syntax of SOP Instance encoded in DICOM File Format. Equal to Transfer Syntax UID (0002,0010) in File Meta Information header. + Required in Response Identifier if File Access Sequence (0008,041A) has an Item.
- >Lossy Image Compression - Ratio - + >Lossy Image Compression Ratio (0028,2112) @@ -16674,9 +11649,7 @@ - - Describes the approximate - lossy compression ratio(s) that have been applied to this image. - + Describes the approximate lossy compression ratio(s) that have been applied to this image.
- The algorithm used for - generating a Message Authentication Code. See - - for Defined Terms. - - Required in Response - Identifier if MAC (0400,0404) is present. - + The algorithm used for generating a Message Authentication Code. See for Defined Terms. + Required in Response Identifier if MAC (0400,0404) is present.
- Message Authentication Code - computed across stored instance file for verification of file integrity. - + Message Authentication Code computed across stored instance file for verification of file integrity.
- All non-bulk data - Attributes at the Query/Retrieve Level that are managed by the SCP. See. - - See - - for additional SCP requirements. - - This Attribute is supported - only with Universal Matching, i.e., if present in the Request Identifier it is - zero-length or has only a zero-length Item. - - Zero or one Item may be - included in this Sequence in a Response Identifier. - + All non-bulk data Attributes at the Query/Retrieve Level that are managed by the SCP. See . + See for additional SCP requirements. + This Attribute is supported only with Universal Matching, i.e., if present in the Request Identifier it is zero-length or has only a zero-length Item. + Zero or one Item may be included in this Sequence in a Response Identifier.
- Multiple Attributes may be present in the Response - Identifier. - - +Multiple Attributes may be present in the Response Identifier. +
- Updated Metadata Sequence - + Updated Metadata Sequence (0008,041E) @@ -16774,22 +11724,10 @@ O - Non-bulk data Attributes at - the Query/Retrieve Level that are managed by the SCP, for which values are - different from the values contained in stored SOP Instance files. See. - - See - - for additional SCP requirements. - - This Attribute is supported - only with Universal Matching, i.e., if present in the Request Identifier it is - zero-length or has only a zero-length Item. - - Zero or one Item may be - included in this Sequence in a Response Identifier. - + Non-bulk data Attributes at the Query/Retrieve Level that are managed by the SCP, for which values are different from the values contained in stored SOP Instance files. See . + See for additional SCP requirements. + This Attribute is supported only with Universal Matching, i.e., if present in the Request Identifier it is zero-length or has only a zero-length Item. + Zero or one Item may be included in this Sequence in a Response Identifier.
- Multiple Attributes may be present in the Response - Identifier. - - +Multiple Attributes may be present in the Response Identifier. +
- The character "-" in the Type column is - used to indicate Attributes that are within a Sequence that is defined only with Universal - Matching. - These Attributes therefore will not be present in a Request Identifier; hence they are not - Key Attributes for matching and the Type column does not apply. - If the SCP supports the Sequence Attribute, and it is requested by the SCU, the SCP returns - these "-" Attributes in accordance with their Attribute Description. - + The character "-" in the Type column is used to indicate Attributes that are within a Sequence that is defined only with Universal Matching. + These Attributes therefore will not be present in a Request Identifier; hence they are not Key Attributes for matching and the Type column does not apply. + If the SCP supports the Sequence Attribute, and it is requested by the SCU, the SCP returns these "-" Attributes in accordance with their Attribute Description.
Record Key - Record Key (0008,041B) is defined at - the Study, Series, and Instance query levels. - It is an implementation-specific unique identifier within the level of the entity record in - the SCP. - The SCP of the Repository Query SOP Class shall return non-zero length values of Record Key - (0008,041B). - The content of Record Key (0008,041B) is opaque to applications other than the SCP. - - The SCP shall construct the Record Key - (0008,041B) value such that for each value the SCP can determine its order with respect to - all other such values. - C-FIND Response Identifiers shall be returned in the ordering of Record Key (0008,041B) - values. - The SCP shall be able to determine from a given value the next entity record to be returned - that matches the given Query Request Identifier, without repeating any records. - - Record Key (0008,041B) values are used - as the Prior Record Key (0008,041C) value in a subsequent Query Request (see). - The SCP may establish implementation specific conditions after which a Record Key - (0008,041B) value is not valid, i.e., will no longer allow continuation of a sequence of - Query operations. - The SCP shall be able to determine from a given Prior Record Key (0008,041C) value whether - that value is still valid for determining the next record to be returned. - + Record Key (0008,041B) is defined at the Study, Series, and Instance query levels. + It is an implementation-specific unique identifier within the level of the entity record in the SCP. + The SCP of the Repository Query SOP Class shall return non-zero length values of Record Key (0008,041B). + The content of Record Key (0008,041B) is opaque to applications other than the SCP. + The SCP shall construct the Record Key (0008,041B) value such that for each value the SCP can determine its order with respect to all other such values. + C-FIND Response Identifiers shall be returned in the ordering of Record Key (0008,041B) values. + The SCP shall be able to determine from a given value the next entity record to be returned that matches the given Query Request Identifier, without repeating any records. + Record Key (0008,041B) values are used as the Prior Record Key (0008,041C) value in a subsequent Query Request (see ). + The SCP may establish implementation specific conditions after which a Record Key (0008,041B) value is not valid, i.e., will no longer allow continuation of a sequence of Query operations. + The SCP shall be able to determine from a given Prior Record Key (0008,041C) value whether that value is still valid for determining the next record to be returned. - The structure, content, and - ordering method of Record Key (0008,041B) values is SCP implementation-specific, - and is opaque to the SCU, i.e., the SCU should not attempt to parse those values - for components or semantics. - Values may be permanent, or may be constructed dynamically during query - processing. - Only the SCP can determine from the value of one Record Key (0008,041B) what - would be the next appropriate record to return. - For example, an SCP may use encrypted representations of an internal database - primary key as the Record Key (0008,041B), and such may appear to the SCU to be - random unordered values. - + The structure, content, and ordering method of Record Key (0008,041B) values is SCP implementation-specific, and is opaque to the SCU, i.e., the SCU should not attempt to parse those values for components or semantics. + Values may be permanent, or may be constructed dynamically during query processing. + Only the SCP can determine from the value of one Record Key (0008,041B) what would be the next appropriate record to return. + For example, an SCP may use encrypted representations of an internal database primary key as the Record Key (0008,041B), and such may appear to the SCU to be random unordered values. - The intention of the - ordering and use requirements for the Record Key (0008,041B) is to allow an SCU - to obtain the complete inventory matching the Key Attributes in a sequence of - Queries. - See. - + The intention of the ordering and use requirements for the Record Key (0008,041B) is to allow an SCU to obtain the complete inventory matching the Key Attributes in a sequence of Queries. + See .
- +
Removed From Operational Use - The Removed from Operational Use - (0008,0405) Attribute is defined at the Study, Series, and Instance query levels. - + The Removed from Operational Use (0008,0405) Attribute is defined at the Study, Series, and Instance query levels. Enumerated Values: Y - The instances are not to be - used for operational purposes. - + The instances are not to be used for operational purposes. N - The instances may be used - for operational purposes. - + The instances may be used for operational purposes. - A value of Y indicates the Study, - Series, or Instance has been removed from operational use related to patient care, although - it may be retained in the repository system for other reasons (e.g., for audit of patient - radiation exposure). - At the Study and Series level, the Attribute indicates whether the entire Study or Series - has been removed from operational use. - A value of Y at the Study level supersedes any value specified for subsidiary Series and - Instances, and a value of Y at the Series level supersedes any value specified for - subsidiary Instances. - - While defined at the Study, Series, and - Instance levels, an SCP might not support this Attribute at some, or any, of those levels. - E.g., an SCP may only manage this Attribute at the Instance level, and is not required to - infer a value for the Series or Study level. - + A value of Y indicates the Study, Series, or Instance has been removed from operational use related to patient care, although it may be retained in the repository system for other reasons (e.g., for audit of patient radiation exposure). + At the Study and Series level, the Attribute indicates whether the entire Study or Series has been removed from operational use. + A value of Y at the Study level supersedes any value specified for subsidiary Series and Instances, and a value of Y at the Series level supersedes any value specified for subsidiary Instances. + While defined at the Study, Series, and Instance levels, an SCP might not support this Attribute at some, or any, of those levels. + E.g., an SCP may only manage this Attribute at the Instance level, and is not required to infer a value for the Series or Study level. - The meaning of "operational - userelated to patient care" is implementation or site specific, but generally - includes diagnostic, clinical, and therapeutic uses, as well as administrative - uses necessary for providing care (e.g., insurance authorization). - + The meaning of "operational userelated to patient care" is implementation or site specific, but generally includes diagnostic, clinical, and therapeutic uses, as well as administrative uses necessary for providing care (e.g., insurance authorization). - Studies, Series, or - Instances might be marked removed from operational use by actions associated - with the processing of specific Key Object Selection Document SOP Instances, - e.g., in accordance with.Image Object - Change Management Integration Profile (IOCM). - Those Key Object Selection Document SOP Instances, and their Series, may - themselves be marked as removed from operational use. - The Context Group for Reason for Removal Code Sequence (0008,0406) includes the - Key Object Selection Concept Codes specified in IOCM. - + Studies, Series, or Instances might be marked removed from operational use by actions associated with the processing of specific Key Object Selection Document SOP Instances, e.g., in accordance with .Image Object Change Management Integration Profile (IOCM). + Those Key Object Selection Document SOP Instances, and their Series, may themselves be marked as removed from operational use. + The Context Group for Reason for Removal Code Sequence (0008,0406) includes the Key Object Selection Concept Codes specified in IOCM. - The semantics of the - Removed from Operational Use (0008,0405) Attribute allows the SCP to include - such entities in the Repository Query response without constraint. An SCP might - exclude entities marked as removed from operational use from the C-FIND - Responses of other Query/Retrieve SOP Classes (e.g., see - - Section 4.66.4.1.3.1 Access to Rejected Instances). - + The semantics of the Removed from Operational Use (0008,0405) Attribute allows the SCP to include such entities in the Repository Query response without constraint. An SCP might exclude entities marked as removed from operational use from the C-FIND Responses of other Query/Retrieve SOP Classes (e.g., see Section 4.66.4.1.3.1 Access to Rejected Instances). - Removed from Operational - Use (0008,0405) is independent of Instance Availability (0008,0056). - A composite instance may have been removed from operational use but is still - accessible at the rapidity specified by Instance Availability (0008,0056). - Conversely, an instance may not have been removed from operational use but is - UNAVAILABLE for retrieval. - + Removed from Operational Use (0008,0405) is independent of Instance Availability (0008,0056). + A composite instance may have been removed from operational use but is still accessible at the rapidity specified by Instance Availability (0008,0056). + Conversely, an instance may not have been removed from operational use but is UNAVAILABLE for retrieval. - If the SCP retains records - of deleted Studies, Series, or Instances, even though the actual Instances are - physically deleted, it may include those entities in the C-FIND Response with an - appropriate Reason for Removal Code Sequence (0008,0406) value. - Such instances may have an Instance Availability (0008,0056) value "UNAVAILABLE" - (see). - + If the SCP retains records of deleted Studies, Series, or Instances, even though the actual Instances are physically deleted, it may include those entities in the C-FIND Response with an appropriate Reason for Removal Code Sequence (0008,0406) value. + Such instances may have an Instance Availability (0008,0056) value "UNAVAILABLE" (see ).
File Set Access Sequence and File Access Sequence - The SCP may support optional Attributes - providing a URI link to SOP Instances stored in the DICOM File Format (see) and accessible through a non-DICOM - file access protocol (see). - + The SCP may support optional Attributes providing a URI link to SOP Instances stored in the DICOM File Format (see ) and accessible through a non-DICOM file access protocol (see ). - See - - + See + - "File Set" as used here may - not be identical to the File-set concept defined in - - and used in Storage Media File-set ID (0088,0130). - + "File Set" as used here may not be identical to the File-set concept defined in and used in Storage Media File-set ID (0088,0130). - For a query at the Study or Series - level, Stored Instance Base URI (0008,0407) within the File Set Access Sequence (0008,0419) - establishes an - - base URI that is merged with relative path reference URIs for non-DICOM protocol access to - SOP Instances of the Study or Series. - If all of the stored SOP Instance files of that Study or Series entity are catalogued in a - single folder, Folder Access URI (0008,0408) provides the URI for protocol operations on - that folder. - If all of the stored SOP Instance files are in a single container file, File Access URI - (0008,0409) provides the URI for accessing that file. - Folder Access URI (0008,0408) and/or File Access URI (0008,0409) may be a relative path - reference URI beginning with the single-dot-segment "./", and the URI is merged with the - Stored Instance Base URI (0008,0407) in accordance with - . - + For a query at the Study or Series level, Stored Instance Base URI (0008,0407) within the File Set Access Sequence (0008,0419) establishes an base URI that is merged with relative path reference URIs for non-DICOM protocol access to SOP Instances of the Study or Series. + If all of the stored SOP Instance files of that Study or Series entity are catalogued in a single folder, Folder Access URI (0008,0408) provides the URI for protocol operations on that folder. + If all of the stored SOP Instance files are in a single container file, File Access URI (0008,0409) provides the URI for accessing that file. + Folder Access URI (0008,0408) and/or File Access URI (0008,0409) may be a relative path reference URI beginning with the single-dot-segment "./", and the URI is merged with the Stored Instance Base URI (0008,0407) in accordance with . - Stored Instance Base URI - (0008,0407) is optional. - If not present, the values of Folder Access URI (0008,0408) and File Access URI - (0008,0409) will be complete URIs. - If Stored Instance Base URI (0008,0407) is present, those other Attributes may still - provide complete URIs, rather than relative paths to be merged with the Base URI. - A complete path specified in Folder Access URI (0008,0408) or File Access URI - (0008,0409) may have a different scheme and authority than is specified in Stored - Instance Base URI (0008,0407). - + Stored Instance Base URI (0008,0407) is optional. + If not present, the values of Folder Access URI (0008,0408) and File Access URI (0008,0409) will be complete URIs. + If Stored Instance Base URI (0008,0407) is present, those other Attributes may still provide complete URIs, rather than relative paths to be merged with the Base URI. + A complete path specified in Folder Access URI (0008,0408) or File Access URI (0008,0409) may have a different scheme and authority than is specified in Stored Instance Base URI (0008,0407). - For a query at the Instance level, - Items of the File Access Sequence (0008,041A) in the Response Identifier each provide an - - URI to access the stored SOP Instance. - File Access URI (0008,0409) may be a URI relative path reference beginning with the - single-dot-segment "./", and the URI is merged with the Stored Instance Base URI (0008,0407) - specified within the File Set Access Sequence (0008,0419) at the Series level, if present, - or otherwise to the Stored Instance Base URI (0008,0407) specified within the File Set - Access Sequence (0008,0419) at the Study level. - + For a query at the Instance level, Items of the File Access Sequence (0008,041A) in the Response Identifier each provide an URI to access the stored SOP Instance. + File Access URI (0008,0409) may be a URI relative path reference beginning with the single-dot-segment "./", and the URI is merged with the Stored Instance Base URI (0008,0407) specified within the File Set Access Sequence (0008,0419) at the Series level, if present, or otherwise to the Stored Instance Base URI (0008,0407) specified within the File Set Access Sequence (0008,0419) at the Study level. - The SCP may store a SOP - Instance on multiple storage devices (e.g., fast short-term media and slower - long-term media), or with different Transfer Syntaxes. - The SOP Instance may therefore be accessible through a non-DICOM protocol at - multiple URIs. - + The SCP may store a SOP Instance on multiple storage devices (e.g., fast short-term media and slower long-term media), or with different Transfer Syntaxes. + The SOP Instance may therefore be accessible through a non-DICOM protocol at multiple URIs. - If the File Access URI - (0008,0409) for a SOP Instance is a relative path reference URI, the SCU will - need to have obtained the Stored Instance Base URI (0008,0407) from the - hierarchically superior STUDY and SERIES level queries. - I.e., the Study and Series level queries will have included a request for the - File Set Access Sequence (0008,0419). - + If the File Access URI (0008,0409) for a SOP Instance is a relative path reference URI, the SCU will need to have obtained the Stored Instance Base URI (0008,0407) from the hierarchically superior STUDY and SERIES level queries. + I.e., the Study and Series level queries will have included a request for the File Set Access Sequence (0008,0419). - See. - + See .
Metadata Sequence and Updated Metadata Sequence - An SCP may manage a set of metadata - Attributes of the SOP Instances in the repository for response to Query requests. - Metadata Sequence (0008,041D) in a Response Identifier shall contain all SOP Instance - Attributes at the Query level that are managed by the SCP, excluding bulk data elements - (such as pixel, waveform, and surface mesh data) and non-SOP Instance Attributes specified - in - - or in. - + An SCP may manage a set of metadata Attributes of the SOP Instances in the repository for response to Query requests. + Metadata Sequence (0008,041D) in a Response Identifier shall contain all SOP Instance Attributes at the Query level that are managed by the SCP, excluding bulk data elements (such as pixel, waveform, and surface mesh data) and non-SOP Instance Attributes specified in or in . - The set of Attributes managed by - the SCP is implementation dependent. - In some implementations the managed set of Attributes might include only those few - required to be supported for Query Key matching, while in other implementations the set - might include every non-bulk data Attribute. - See. - + The set of Attributes managed by the SCP is implementation dependent. + In some implementations the managed set of Attributes might include only those few required to be supported for Query Key matching, while in other implementations the set might include every non-bulk data Attribute. + See . - An SCP may manage a set of metadata - Attributes whose "updated" values differ from those in a stored SOP Instance accessible - through a non-DICOM protocol specified in the File Access URI (0008,0409) or Folder Access - URI (0008,0408). - Although a stored SOP Instance shall be conformant to its IOD (per the requirements of the - DICOM File Format), some Attributes in the file might not have current values (e.g., Patient - Name may have been corrected or changed after the Instance was stored). - Updated Metadata Sequence (0008,041E) in a Response Identifier shall contain all Attributes - at the Query level whose values are different from the values contained in the stored SOP - Instance file. - - An SCP that supports non-DICOM protocol - URI references to stored SOP Instances shall support either the Metadata Sequence - (0008,041D) or the Updated Metadata Sequence (0008,041E), or both, to provide current - metadata values for SOP Instances accessed through the non-DICOM protocol. - + An SCP may manage a set of metadata Attributes whose "updated" values differ from those in a stored SOP Instance accessible through a non-DICOM protocol specified in the File Access URI (0008,0409) or Folder Access URI (0008,0408). + Although a stored SOP Instance shall be conformant to its IOD (per the requirements of the DICOM File Format), some Attributes in the file might not have current values (e.g., Patient Name may have been corrected or changed after the Instance was stored). + Updated Metadata Sequence (0008,041E) in a Response Identifier shall contain all Attributes at the Query level whose values are different from the values contained in the stored SOP Instance file. + An SCP that supports non-DICOM protocol URI references to stored SOP Instances shall support either the Metadata Sequence (0008,041D) or the Updated Metadata Sequence (0008,041E), or both, to provide current metadata values for SOP Instances accessed through the non-DICOM protocol. - SOP Instances accessed - through DICOM protocols are expected to have current values in all Attributes. - + SOP Instances accessed through DICOM protocols are expected to have current values in all Attributes. - The SCP might not track - whether Attribute values have changed, or which specific Attributes have changed - values, and would therefore not support Updated Metadata Sequence (0008,041E). - In this case, the SCU may request the Metadata Sequence (0008,041D) that - contains all current Attribute values managed by the SCP, whether or not they - have been updated. - Determination of differences, if any, between those returned Attribute values - and values in the stored SOP Instance would be the responsibility of the SCU. - + The SCP might not track whether Attribute values have changed, or which specific Attributes have changed values, and would therefore not support Updated Metadata Sequence (0008,041E). + In this case, the SCU may request the Metadata Sequence (0008,041D) that contains all current Attribute values managed by the SCP, whether or not they have been updated. + Determination of differences, if any, between those returned Attribute values and values in the stored SOP Instance would be the responsibility of the SCU. - At any Query level,Metadata Sequence - (0008,041D) or Updated Metadata Sequence (0008,041E) may include the Original Attributes - Sequence (0400,0561) describing the provenance of changes to Attributes at that level or at - higher Query levels. - - If Metadata Sequence (0008,041D) and/or - Updated Metadata Sequence (0008,041E) are present in a Request Identifier, their absence in - the Response Identifier indicates they are not supported by the SCP (see). - - A zero-length value or a single empty - Item in Updated Metadata Sequence (0008,041E) in a Response Identifier indicates support by - the SCP, but that there are no differing metadata Attribute values. - + At any Query level,Metadata Sequence (0008,041D) or Updated Metadata Sequence (0008,041E) may include the Original Attributes Sequence (0400,0561) describing the provenance of changes to Attributes at that level or at higher Query levels. + If Metadata Sequence (0008,041D) and/or Updated Metadata Sequence (0008,041E) are present in a Request Identifier, their absence in the Response Identifier indicates they are not supported by the SCP (see ). + A zero-length value or a single empty Item in Updated Metadata Sequence (0008,041E) in a Response Identifier indicates support by the SCP, but that there are no differing metadata Attribute values.
Repository Query Request Identifier Attributes - In addition to the Attributes specified in - , a Repository Query Request - Identifier may contain the Attributes shown in - - for the SCU to request certain C-FIND response content. - + In addition to the Attributes specified in , a Repository Query Request Identifier may contain the Attributes shown in for the SCU to request certain C-FIND response content. @@ -17155,8 +11915,7 @@ Tag @@ -17169,29 +11928,18 @@ (0008,041C) @@ -17199,16 +11947,7 @@
Status Codes - The Repository Query SOP Class specifies - the status code values of - - in addition to the statuses and related fields specified in - - for C-FIND of the Query/Retrieve Service Class and in - - for the C-FIND DIMSE Service. - + The Repository Query SOP Class specifies the status code values of in addition to the statuses and related fields specified in for C-FIND of the Query/Retrieve Service Class and in for the C-FIND DIMSE Service.
Repository Query Request Identifier Additional Attributes
- Attribute Description - + Attribute Description
- Entity identifier that was - returned as a value in Record Key (0008,041B) in a prior request. Entities - returned for the current request will begin with the first matching record with - a record key subsequent to this record key. See - - for SCP processing requirements. - + Entity identifier that was returned as a value in Record Key (0008,041B) in a prior request. Entities returned for the current request will begin with the first matching record with a record key subsequent to this record key. See for SCP processing requirements.
- Maximum Number of Records - + Maximum Number of Records - (0008,041E) + (0008,0429) - Maximum number of matched - entities to be returned for this request. See - - for SCP processing requirements. - + Maximum number of matched entities to be returned for this request. See for SCP processing requirements.
@@ -17233,8 +11972,7 @@ Failure
Repository Query Additional Status Values
- Invalid Prior Record Key - + Invalid Prior Record Key A710 @@ -17248,9 +11986,7 @@ Warning - Matching reached response - limit, subsequent request may return additional matches - + Matching reached response limit, subsequent request may return additional matches B001 @@ -17264,289 +12000,141 @@
C-FIND SCU Behavior - In addition to the behaviors specified in - , the SCU shall interpret a response - with a status equal to B001 "Warning" to convey the end of Pending responses, and as an - indication that more responses are available, but the SCP is not further processing the request - in this C-FIND operation. - + In addition to the behaviors specified in , the SCU shall interpret a response with a status equal to B001 "Warning" to convey the end of Pending responses, and as an indication that more responses are available, but the SCP is not further processing the request in this C-FIND operation.
C-FIND SCP Behavior - The Repository Query SOP Class adds the - following behaviors to both Baseline and Extended Behavior of the SCP as described in. - + The Repository Query SOP Class adds the following behaviors to both Baseline and Extended Behavior of the SCP as described in .
Record Key - The SCP shall return C-FIND Responses - according to the ordering of the values of Record Key (0008,041B), if that Attribute is - included in the Request Identifier. - + The SCP shall return C-FIND Responses according to the ordering of the values of Record Key (0008,041B), if that Attribute is included in the Request Identifier. - If the Record Key - (0008,041B) is not requested, there is no requirement on ordering, and the SCU - will not be able to issue a subsequent query request with a Prior Record Key - (0008,041C). - + If the Record Key (0008,041B) is not requested, there is no requirement on ordering, and the SCU will not be able to issue a subsequent query request with a Prior Record Key (0008,041C). - The structure, content, and - ordering method of Record Key (0008,041B) values is SCP implementation-specific, - and is opaque to the SCU (see). - + The structure, content, and ordering method of Record Key (0008,041B) values is SCP implementation-specific, and is opaque to the SCU (see ).
Maximum Number of Records and Incomplete Response - The SCP shall send no more Pending - responses (i.e., returned matching records) than the number specified by the SCU in the - Maximum Number of Records (0008,041E) Attribute in the Repository Query Request Identifier. - Further, the SCP may limit the number of responses in a Query transaction to its own - implementation-defined resource limit. - If either limit is reached, and there are additional records that satisfy the Key Attribute - matching, the SCP shall send a final Status value B001 "Warning". - + The SCP shall send no more Pending responses (i.e., returned matching records) than the number specified by the SCU in the Maximum Number of Records (0008,0429) Attribute in the Repository Query Request Identifier. + Further, the SCP may limit the number of responses in a Query transaction to its own implementation-defined resource limit. + If either limit is reached, and there are additional records that satisfy the Key Attribute matching, the SCP shall send a final Status value B001 "Warning". - The SCP resource limit may be a - number of records, or a time limit on database operations, or another limit that allows - timely completion of a Repository Query transaction. - + The SCP resource limit may be a number of records, or a time limit on database operations, or another limit that allows timely completion of a Repository Query transaction.
Prior Record Key and Subsequent Response - If Prior Record Key (0008,041C) is - present in the Repository Query Request Identifier, the SCP shall return entity records, - continuing with the next record key, that satisfy the Key Attribute matching. - The SCP shall return a Failure status code A710 if the value of Prior Record Key (0008,041C) - is invalid for identifying an entity determining a point of continuation. - See. - - For a sequential set of Query - transactions with the same Key Attribute Values, and for which each C-FIND Request after the - first includes a Prior Record Key (0008,041C) value equal to the last Record Key (0008,041B) - in the C-FIND Responses of the prior Query transaction, the SCP shall return the same set of - C-FIND Responses as if the entire Query would have been completed in a single transaction. - Whether new entities and updates received by the SCP after the time of the initial Query - transaction might be included in the C-FIND Responses is implementation specific. - + If Prior Record Key (0008,041C) is present in the Repository Query Request Identifier, the SCP shall return entity records, continuing with the next record key, that satisfy the Key Attribute matching. + The SCP shall return a Failure status code A710 if the value of Prior Record Key (0008,041C) is invalid for identifying an entity determining a point of continuation. + See . + For a sequential set of Query transactions with the same Key Attribute Values, and for which each C-FIND Request after the first includes a Prior Record Key (0008,041C) value equal to the last Record Key (0008,041B) in the C-FIND Responses of the prior Query transaction, the SCP shall return the same set of C-FIND Responses as if the entire Query would have been completed in a single transaction. + Whether new entities and updates received by the SCP after the time of the initial Query transaction might be included in the C-FIND Responses is implementation specific. - For example, an entity - added after the time of the initial Query might be assigned a Record Key - (0008,041B) that precedes a Record Key (0008,041B) already sent in a C-FIND - Response; that entity will not be returned in the set of Query transactions. - However, an added entity whose Record Key (0008,041B) is after the last sent - Record Key (0008,041B) may or may not be included in the set of Query - transactions; as it was added after the initial Query transaction, the - implementation determines whether such a change is included in the responses. - + For example, an entity added after the time of the initial Query might be assigned a Record Key (0008,041B) that precedes a Record Key (0008,041B) already sent in a C-FIND Response; that entity will not be returned in the set of Query transactions. + However, an added entity whose Record Key (0008,041B) is after the last sent Record Key (0008,041B) may or may not be included in the set of Query transactions; as it was added after the initial Query transaction, the implementation determines whether such a change is included in the responses. - The SCP should not assume - that the last Record Key (0008,041B) it sent will be used as the Prior Record - Key (0008,041C) in a subsequent transaction. - Error conditions may cause the SCU to need to resume from an earlier value. - + The SCP should not assume that the last Record Key (0008,041B) it sent will be used as the Prior Record Key (0008,041C) in a subsequent transaction. + Error conditions may cause the SCU to need to resume from an earlier value. - There is no requirement for - the Key Attributes in a Request Identifier to be identical to those in a prior - Repository Query transaction, even though the presence of Prior Record Key - (0008,041C) implies a continuation of a prior transaction. + There is no requirement for the Key Attributes in a Request Identifier to be identical to those in a prior Repository Query transaction, even though the presence of Prior Record Key (0008,041C) implies a continuation of a prior transaction. Each Repository Query transaction is independent. - The SCP does not need to retain any state information between Repository Query - transactions, although it may include state information in the Record Key - (0008,041B). - + The SCP does not need to retain any state information between Repository Query transactions, although it may include state information in the Record Key (0008,041B).
Entities Removed From Operational Use - If the SCP supports Removed from - Operational Use (0008,0405) (see) - as a Key Attribute, query responses shall include all entities regardless of the value of - that Attribute, unless the SCU has explicitly included matching against that Attribute in - the C-FIND request and the SCP supports matching on that Attribute. - + If the SCP supports Removed from Operational Use (0008,0405) (see ) as a Key Attribute, query responses shall include all entities regardless of the value of that Attribute, unless the SCU has explicitly included matching against that Attribute in the C-FIND request and the SCP supports matching on that Attribute. - As the Study Root Query/Retrieve - Information Model - FIND SOP Class is typically used for operational purposes, an SCP - implementation of that SOP Class by policy might not return entities with Removed from - Operational Use (0008,0405) value "Y". - + As the Study Root Query/Retrieve Information Model - FIND SOP Class is typically used for operational purposes, an SCP implementation of that SOP Class by policy might not return entities with Removed from Operational Use (0008,0405) value "Y".
File Set Access Sequence and File Access Sequence - An SCP that supports File Set Access - Sequence (0008,0419) at the Study or Series query level shall support either Metadata - Sequence (0008,041D) or Updated Metadata Sequence (0008,041E), or both, at the same - level(s). - - An SCP that supports File Access - Sequence (0008,041A) at the Instance query level shall support either Metadata Sequence - (0008,041D) or Updated Metadata Sequence (0008,041E), or both, at that level. - - The SCP may support Metadata Sequence - (0008,041D) or Updated Metadata Sequence (0008,041E) without support of File Set Access - Sequence (0008,0419) or File Access Sequence (0008,041A). - - See - - for further explanation. - + An SCP that supports File Set Access Sequence (0008,0419) at the Study or Series query level shall support either Metadata Sequence (0008,041D) or Updated Metadata Sequence (0008,041E), or both, at the same level(s). + An SCP that supports File Access Sequence (0008,041A) at the Instance query level shall support either Metadata Sequence (0008,041D) or Updated Metadata Sequence (0008,041E), or both, at that level. + The SCP may support Metadata Sequence (0008,041D) or Updated Metadata Sequence (0008,041E) without support of File Set Access Sequence (0008,0419) or File Access Sequence (0008,041A). + See for further explanation.
Conformance Requirements - An implementation may conform to the - Repository Query SOP Class as an SCU, SCP or both. - The Conformance Statement shall be in the format defined in - . - + An implementation may conform to the Repository Query SOP Class as an SCU, SCP or both. + The Conformance Statement shall be in the format defined in .
C-FIND SCU Conformance - An implementation that conforms to the - Repository Query SOP Class as an SCU shall support queries against the Study Root - Query/Retrieve Information Model described in - - and - - using the C-FIND SCU behavior described in - - and. - - An implementation that conforms to the - Repository Query SOP Class as an SCU shall be capable of generating queries using - Hierarchical Search. - It shall not generate queries using Relational-queries unless the Relational-queries option - has been successfully negotiated. - An implementation that conforms to the Repository Query SOP Class as an SCU shall state in - its Conformance Statement whether it may generate Relational-queries. - - An implementation that conforms to the - Repository Query SOP Class as an SCU shall state in its Conformance Statement: - + An implementation that conforms to the Repository Query SOP Class as an SCU shall support queries against the Study Root Query/Retrieve Information Model described in and using the C-FIND SCU behavior described in and . + An implementation that conforms to the Repository Query SOP Class as an SCU shall be capable of generating queries using Hierarchical Search. + It shall not generate queries using Relational-queries unless the Relational-queries option has been successfully negotiated. + An implementation that conforms to the Repository Query SOP Class as an SCU shall state in its Conformance Statement whether it may generate Relational-queries. + An implementation that conforms to the Repository Query SOP Class as an SCU shall state in its Conformance Statement: - Whether or not it supports - extended negotiation of combined date-time matching, fuzzy semantic matching of - person names, empty value matching, and/or multiple value matching. - + Whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, empty value matching, and/or multiple value matching. - How it makes use of Specific - Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding - queries and interpreting responses. - + How it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses. - Any limitations it places on - the number of C-FIND responses through the Maximum Number of Records (0008,041E) - Attribute. - + Any limitations it places on the number of C-FIND responses through the Maximum Number of Records (0008,0429) Attribute.
C-FIND SCP Conformance - An implementation that conforms to the - Repository Query SOP Class as an SCP shall support queries against the Study Root - Query/Retrieve Information Model described in - - and - - using the C-FIND SCP behavior described in - - and. - - An implementation that conforms to the - Repository Query SOP Class as an SCP shall state in its Conformance Statement: - + An implementation that conforms to the Repository Query SOP Class as an SCP shall support queries against the Study Root Query/Retrieve Information Model described in and using the C-FIND SCP behavior described in and . + An implementation that conforms to the Repository Query SOP Class as an SCP shall state in its Conformance Statement: - Which Optional Keys it supports - for existence (i.e., to be returned in responses) and which for matching. - + Which Optional Keys it supports for existence (i.e., to be returned in responses) and which for matching. - Which Attributes it supports in - Items of those Key Attributes that are Sequences. - + Which Attributes it supports in Items of those Key Attributes that are Sequences. - Whether it supports Relational - Search. - If it supports Relational Search, then it shall also support extended negotiation of - Relational-queries as an SCP. - + Whether it supports Relational Search. + If it supports Relational Search, then it shall also support Extended Negotiation of Relational-queries as an SCP. - Whether or not it supports - extended negotiation of combined date-time matching, fuzzy semantic matching of - person names, empty value matching, and/or multiple value matching. - If fuzzy semantic matching of person names is supported, then the mechanism for - fuzzy semantic matching shall be specified. - + Whether or not it supports Extended Negotiation of combined date-time matching, fuzzy semantic matching of person names, empty value matching, and/or multiple value matching. + If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified. - Whether it supports - case-insensitive matching for PN VR Attributes, and list Attributes for which this - applies. - + Whether it supports case-insensitive matching for PN VR Attributes, and list Attributes for which this applies. - How it uses Specific Character - Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, - performing matching and encoding responses. - + How it uses Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses. - Any limitations it places on - the number of C-FIND responses. - + Any limitations it places on the number of C-FIND responses. - The conditions after which a - Record Key (0008,041B) value is not valid to allow resumption of a C-FIND operation. - + The conditions after which a Record Key (0008,041B) value is not valid to allow resumption of a C-FIND operation. - Any non-DICOM mechanisms used - to access SOP Instances that may be specified by a File Access URI (0008,0409), - including protocols (such as NFS, SMB, or HTTP), and use of folders and/or container - files (ZIP, TAR, GZIP, TARGZIP, BLOB) for the SOP Instances. - If such mechanisms are used, the use of Metadata Sequence (0008,041D) or Updated - Metadata Sequence (0008,041E) shall be described. - + Any non-DICOM mechanisms used to access SOP Instances that may be specified by a File Access URI (0008,0409), including protocols (such as NFS, SMB, or HTTP), and use of folders and/or container files (ZIP, TAR, GZIP, TARGZIP, BLOB) for the SOP Instances. + If such mechanisms are used, the use of Metadata Sequence (0008,041D) or Updated Metadata Sequence (0008,041E) shall be described. - Whether it provides responses - that include entities from multiple repositories (federation), and how it handles - differences in support for Attribute matching across those repositories in - constructing responses. - + Whether it provides responses that include entities from multiple repositories (federation), and how it handles differences in support for Attribute matching across those repositories in constructing responses.
SOP Classes - The UID for the Repository Query SOP Class - is listed in. - + The UID for the Repository Query SOP Class is listed in . @@ -17565,9 +12153,7 @@ Repository Query @@ -17588,13 +12174,9 @@ Procedure Step SOP Classes (Normative)
Overview - This Annex defines the Procedure Step SOP - Classes. - + This Annex defines the Procedure Step SOP Classes. - This Annex formerly defined a Study Management - Service Class that has been retired. See PS 3.4-2004. - + This Annex formerly defined a Study Management Service Class that has been retired. See PS 3.4-2004.
Scope @@ -17614,24 +12196,10 @@
Modality Performed Procedure Step Management States - The state information related to the Modality - Performed Procedure Step is specified by the Modality Performed Procedure Step IOD in the Attribute - Performed Procedure Step Status (0040,0252). - - The Performed Procedure Step Object represents - only the "performed" segment of the real-world procedure step and not the "scheduled" segment. The - number of events is therefore limited; all events are initiated by the modality. The state - "DISCONTINUED" means canceled or unsuccessfully terminated, which may happen when the performance of - a Procedure Step has been started but cannot be finished by the modality. The modality shall convey - this state change to the information system (the SCP), to allow the information system to reschedule - or cancel the related Procedure Step. The state "COMPLETED" means that the acquisition of Composite - SOP Instances has been successfully completed and the SCU has provided all required Attribute Values - for the Performed Procedure Step. - + The state information related to the Modality Performed Procedure Step is specified by the Modality Performed Procedure Step IOD in the Attribute Performed Procedure Step Status (0040,0252). + The Performed Procedure Step Object represents only the "performed" segment of the real-world procedure step and not the "scheduled" segment. The number of events is therefore limited; all events are initiated by the modality. The state "DISCONTINUED" means canceled or unsuccessfully terminated, which may happen when the performance of a Procedure Step has been started but cannot be finished by the modality. The modality shall convey this state change to the information system (the SCP), to allow the information system to reschedule or cancel the related Procedure Step. The state "COMPLETED" means that the acquisition of Composite SOP Instances has been successfully completed and the SCU has provided all required Attribute Values for the Performed Procedure Step. - - describes the valid Modality Performed Procedure Step states. - + describes the valid Modality Performed Procedure Step states.
SOP Classes for Repository Query
- - 1.2.840.10008.5.1.4.1.1.201.6 - + 1.2.840.10008.5.1.4.1.1.201.6
@@ -17650,9 +12218,7 @@ In Progress @@ -17660,9 +12226,7 @@ Discontinued @@ -17670,19 +12234,13 @@ Completed
Modality Performed Procedure Step States
- Modality Performed Procedure - Step created and execution in progress - + Modality Performed Procedure Step created and execution in progress
- Execution of Modality Performed - Procedure Step canceled by modality - + Execution of Modality Performed Procedure Step canceled by modality
- Modality Performed Procedure - Step completed - + Modality Performed Procedure Step completed
- - defines the valid state transitions for the Performed Procedure Steps. For each of the above defined - states the valid state resulting from the occurrence of events is specified. These state transitions - are managed by the Modality Performed Procedure Step SOP Class. - + defines the valid state transitions for the Performed Procedure Steps. For each of the above defined states the valid state resulting from the occurrence of events is specified. These state transitions are managed by the Modality Performed Procedure Step SOP Class. @@ -17710,9 +12268,7 @@
Modality Performed Procedure Step State Transition Diagram
- Performed Procedure Step - Discontinued - + Performed Procedure Step Discontinued Discontinued @@ -17722,9 +12278,7 @@
- Performed Procedure Step - Completed - + Performed Procedure Step Completed Completed @@ -17746,84 +12300,55 @@
Conformance Overview - The application-level services addressed by this - Service Class Definition are specified via the following distinct SOP Classes: - + The application-level services addressed by this Service Class Definition are specified via the following distinct SOP Classes: - Modality Performed Procedure Step SOP - Class - + Modality Performed Procedure Step SOP Class - Modality Performed Procedure Step - Notification SOP Class - + Modality Performed Procedure Step Notification SOP Class - Modality Performed Procedure Step Retrieve - SOP Class - + Modality Performed Procedure Step Retrieve SOP Class - Each SOP Class operates on a subset of the Modality - Performed Procedure Step IOD and specifies the Attributes, operations, notifications, and behavior - applicable to the SOP Class. Conformance of Application Entities shall be defined by selecting one or - more of the Study and Study Component Management SOP and Meta SOP Classes. For each SOP Class - conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service - Class User (SCU). - + Each SOP Class operates on a subset of the Modality Performed Procedure Step IOD and specifies the Attributes, operations, notifications, and behavior applicable to the SOP Class. Conformance of Application Entities shall be defined by selecting one or more of the Study and Study Component Management SOP and Meta SOP Classes. For each SOP Class conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU).
Association Negotiation - Association establishment is the first phase of - any instance of communication between peer DICOM AEs. The Association negotiation procedure - specified in - - shall be used to negotiate the supported SOP Classes. - - Support for the SCP/SCU Role Selection - Negotiation is mandatory. The SOP Class Extended Negotiation shall not be supported. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in shall be used to negotiate the supported SOP Classes. + Support for the SCP/SCU Role Selection Negotiation is mandatory. The SOP Class Extended Negotiation shall not be supported. - Event notification is a process that - logically extends across multiple Associations. SCP implementations should support a local table - of SCUs to which event notifications are to be sent. - + Event notification is a process that logically extends across multiple Associations. SCP implementations should support a local table of SCUs to which event notifications are to be sent.
- Detached Study Management SOP Class(Retired) + Detached Study Management SOP Class (Retired) Retired. See PS 3.4-2004.
- Study Component Management SOP Class(Retired) + Study Component Management SOP Class (Retired) Retired. See PS 3.4-2004.
- Study Management Meta SOP Class(Retired) + Study Management Meta SOP Class (Retired) Retired. See PS 3.4-2004.
- Specialized SOP Class Conformance(Retired) + Specialized SOP Class Conformance (Retired) Retired. See PS 3.4-2004.
Modality Performed Procedure Step SOP Class
DIMSE Service Group - The DIMSE Services shown in - - are applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure - Step SOP Class. - + The DIMSE Services shown in are applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure Step SOP Class.
DIMSE Service Group Applicable to Modality Performed Procedure Step
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -17849,56 +12374,23 @@
- The DIMSE Services and Protocols are specified - in - + The DIMSE Services and Protocols are specified in
Operations - The Application Entity that claims conformance - to this SOP Class as an SCU shall be permitted to invoke the following operations and the - Application Entity that claims conformance as an SCP shall be capable of providing the following - operations. - + The Application Entity that claims conformance to this SOP Class as an SCU shall be permitted to invoke the following operations and the Application Entity that claims conformance as an SCP shall be capable of providing the following operations.
Create Modality Performed Procedure Step SOP Instance - This operation allows an SCU to create an - instance of the Modality Performed Procedure Step SOP Class and provide information about a - specific real-world Performed Procedure Step that is under control of the SCU. This operation - shall be invoked through the DIMSE N-CREATE Service. - + This operation allows an SCU to create an instance of the Modality Performed Procedure Step SOP Class and provide information about a specific real-world Performed Procedure Step that is under control of the SCU. This operation shall be invoked through the DIMSE N-CREATE Service. - The modality should inform the - Information System as soon as possible that the performance of the Procedure Step has been - started by sending the N-CREATE Service Request. This allows an SCP of the Modality Worklist - SOP Class (if supported) to update the Modality Worklist. Some of the Attribute Values are - already known at the beginning of the Procedure Step, they are required to be sent in the - N-CREATE command. Other mandatory Attributes are known only at the end of the Performed - Procedure Step, they are assigned a value in the N-SET command. - + The modality should inform the Information System as soon as possible that the performance of the Procedure Step has been started by sending the N-CREATE Service Request. This allows an SCP of the Modality Worklist SOP Class (if supported) to update the Modality Worklist. Some of the Attribute Values are already known at the beginning of the Procedure Step, they are required to be sent in the N-CREATE command. Other mandatory Attributes are known only at the end of the Performed Procedure Step, they are assigned a value in the N-SET command. - The same SOP Instance UID is shared by all - three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created - and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved - using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve - SOP Class. Changes in its state can be notified by using its SOP Instance UID within the service - of the Modality Performed Procedure Step Notification SOP Class. The SOP Class UID specified in - the DIMSE N-CREATE and N-SET request primitives shall be the UID of the Modality Performed - Procedure Step SOP Class. - - The Modality Performed Procedure Step SOP - Instance UID shall not be used to identify a SOP Instance of the Study Component Service Class. - + The same SOP Instance UID is shared by all three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve SOP Class. Changes in its state can be notified by using its SOP Instance UID within the service of the Modality Performed Procedure Step Notification SOP Class. The SOP Class UID specified in the DIMSE N-CREATE and N-SET request primitives shall be the UID of the Modality Performed Procedure Step SOP Class. + The Modality Performed Procedure Step SOP Instance UID shall not be used to identify a SOP Instance of the Study Component Service Class.
Modality Performed Procedure Step Subset Specification - The Application Entity that claims - conformance to this SOP Class as an SCU must provide all Required Attributes as specified in - . Optional Attributes maintained by - the SCP may be provided as well. The Application Entity that claims conformance as an SCP to - this SOP Class shall support the subset of the Modality Performed Procedure Step Attributes - specified in. - + The Application Entity that claims conformance to this SOP Class as an SCU must provide all Required Attributes as specified in . Optional Attributes maintained by the SCP may be provided as well. The Application Entity that claims conformance as an SCP to this SOP Class shall support the subset of the Modality Performed Procedure Step Attributes specified in . @@ -17910,19 +12402,13 @@ Tag @@ -17930,17 +12416,14 @@ @@ -17976,19 +12458,13 @@ Tag @@ -18002,10 +12478,7 @@
Modality Performed Procedure Step Enhanced Code Value Macro with no N-SET
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
- Include - - - +Include + +
- Equivalent Code - Sequence - + Equivalent Code Sequence (0008,0121) @@ -17956,10 +12439,9 @@
- >Include - - - +>Include + +
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
1C/1C - Shall be present if the - code value length is 16 characters or less, and the code value is not a URN - or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL. Not allowed @@ -18014,19 +12487,14 @@
- Coding Scheme - Designator - + Coding Scheme Designator (0008,0102) 1C/1C - Shall be present if - Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be - present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. Not allowed @@ -18035,21 +12503,14 @@
- Coding Scheme Version - + Coding Scheme Version (0008,0103) 1C/1C - Shall be present if the - value of Coding Scheme Designator (0008,0102) is present and is not - sufficient to identify the Code Value (0008,0100) or Long Code Value - (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be - present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. Not allowed @@ -18080,10 +12541,7 @@ 1C/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is not a URN or - URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL. Not allowed @@ -18099,9 +12557,7 @@ 1C/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL. Not allowed @@ -18125,8 +12581,7 @@
- Mapping Resource UID - + Mapping Resource UID (0008,0118) @@ -18141,8 +12596,7 @@
- Context Group Version - + Context Group Version (0008,0106) @@ -18157,9 +12611,7 @@
- Context Group Extension - Flag - + Context Group Extension Flag (0008,010B) @@ -18174,9 +12626,7 @@
- Context Group Local - Version - + Context Group Local Version (0008,0107) @@ -18191,9 +12641,7 @@
- Context Group Extension - Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -18210,9 +12658,7 @@
- + @@ -18242,17 +12682,14 @@
Modality Performed Procedure Step Enhanced Code Value Macro with N-SET, Mandatory - Meaning - Modality Performed Procedure Step Enhanced Code Value Macro with N-SET, Mandatory Meaning
@@ -18222,19 +12668,13 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
- >Include - - - +>Include + +
- Equivalent Code - Sequence - + Equivalent Code Sequence (0008,0121) @@ -18268,19 +12705,16 @@
- >Include - - - +>Include + +
- + @@ -18317,72 +12745,45 @@ @@ -18410,17 +12811,11 @@ @@ -18433,15 +12828,11 @@ @@ -18462,8 +12853,7 @@
Modality Performed Procedure Step Simple Code Value Macro with N-SET, Mandatory - Meaning - Modality Performed Procedure Step Simple Code Value Macro with N-SET, Mandatory Meaning
@@ -18290,19 +12724,13 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
1C/1C - Shall be present if the - code value length is 16 characters or less, and the code value is not a URN - or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL. 3/1C - Shall be present if the - code value length is 16 characters or less, and the code value is not a URN - or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
- Coding Scheme - Designator - + Coding Scheme Designator (0008,0102) 1C/1C - Shall be present if - Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be - present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. 1C/1C - Shall be present if - Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be - present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
- Coding Scheme Version - + Coding Scheme Version (0008,0103) 1C/1C - Shall be present if the - value of Coding Scheme Designator (0008,0102) is present and is not - sufficient to identify the Code Value (0008,0100) or Long Code Value - (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be - present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. 1C/1C - Shall be present if the - value of Coding Scheme Designator (0008,0102) is present and is not - sufficient to identify the Code Value (0008,0100) or Long Code Value - (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be - present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
1C/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is not a URN or - URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL. 3/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is not a URN or - URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
1C/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL. 3/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Mapping Resource UID - + Mapping Resource UID (0008,0118) @@ -18478,8 +12868,7 @@
- Context Group Version - + Context Group Version (0008,0106) @@ -18494,9 +12883,7 @@
- Context Group Extension - Flag - + Context Group Extension Flag (0008,010B) @@ -18511,9 +12898,7 @@
- Context Group Local - Version - + Context Group Local Version (0008,0107) @@ -18528,9 +12913,7 @@
- Context Group Extension - Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -18547,9 +12930,7 @@
- + @@ -18579,17 +12954,14 @@
Modality Performed Procedure Step Enhanced Code Value Macro with N-SET, Optional - Meaning - Modality Performed Procedure Step Enhanced Code Value Macro with N-SET, Optional Meaning
@@ -18559,19 +12940,13 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
- >Include - - - +>Include + +
- Equivalent Code - Sequence - + Equivalent Code Sequence (0008,0121) @@ -18605,19 +12977,16 @@
- >Include - - - +>Include + +
- + @@ -18653,72 +13016,45 @@ @@ -18746,17 +13082,11 @@ @@ -18769,15 +13099,11 @@ @@ -18798,8 +13124,7 @@
Modality Performed Procedure Step Simple Code Value Macro with N-SET, Optional - Meaning - Modality Performed Procedure Step Simple Code Value Macro with N-SET, Optional Meaning
@@ -18627,19 +12996,13 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
1C/1C - Shall be present if the - code value length is 16 characters or less, and the code value is not a URN - or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL. 3/1C - Shall be present if the - code value length is 16 characters or less, and the code value is not a URN - or URL. - + Shall be present if the code value length is 16 characters or less, and the code value is not a URN or URL.
- Coding Scheme - Designator - + Coding Scheme Designator (0008,0102) 1C/1C - Shall be present if - Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be - present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise. 1C/1C - Shall be present if - Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be - present otherwise. - + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
- Coding Scheme Version - + Coding Scheme Version (0008,0103) 1C/1C - Shall be present if the - value of Coding Scheme Designator (0008,0102) is present and is not - sufficient to identify the Code Value (0008,0100) or Long Code Value - (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be - present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise. 1C/1C - Shall be present if the - value of Coding Scheme Designator (0008,0102) is present and is not - sufficient to identify the Code Value (0008,0100) or Long Code Value - (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be - present if Coding Scheme Designator (0008,0102) is absent. May be present - otherwise. - + Shall be present if the value of Coding Scheme Designator (0008,0102) is present and is not sufficient to identify the Code Value (0008,0100) or Long Code Value (0008,0119) or URN Code Value (0008,0120) unambiguously. Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
1C/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is not a URN or - URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL. 3/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is not a URN or - URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
1C/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL. 3/1C - Shall be present if - Code Value (0008,0100) is not present, and the code value is a URN or URL. - + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Mapping Resource UID - + Mapping Resource UID (0008,0118) @@ -18814,8 +13139,7 @@
- Context Group Version - + Context Group Version (0008,0106) @@ -18830,9 +13154,7 @@
- Context Group Extension - Flag - + Context Group Extension Flag (0008,010B) @@ -18847,9 +13169,7 @@
- Context Group Local - Version - + Context Group Local Version (0008,0107) @@ -18864,9 +13184,7 @@
- Context Group Extension - Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -18882,9 +13200,7 @@
- + @@ -18943,9 +13247,7 @@ @@ -19459,8 +13692,7 @@ @@ -20261,9 +14403,7 @@ @@ -20650,317 +14751,122 @@ - The requirement for the - final state is that which applies at the time that the Performed Procedure Step - Status (0040,0252) is N-SET to a value of COMPLETED or DISCONTINUED, as - described in. It is - only described if it is different from the SCP requirement for the N-CREATE. - + The requirement for the final state is that which applies at the time that the Performed Procedure Step Status (0040,0252) is N-SET to a value of COMPLETED or DISCONTINUED, as described in . It is only described if it is different from the SCP requirement for the N-CREATE. - The Performed Series - Sequence (0040,0340) may not be empty (zero length) at the time that the - Performed Procedure Step Status (0040,0252) is N-SET to a value of COMPLETED or - DISCONTINUED. In other words a Series must exist for every Performed Procedure - Step, though it may contain no Images or Non-Image Composite objects, if none - were created, as described in. - + The Performed Series Sequence (0040,0340) may not be empty (zero length) at the time that the Performed Procedure Step Status (0040,0252) is N-SET to a value of COMPLETED or DISCONTINUED. In other words a Series must exist for every Performed Procedure Step, though it may contain no Images or Non-Image Composite objects, if none were created, as described in . - Attributes (0040,1006) - Placer Order Number/Procedure and (0040,1007) Filler Order Number/Procedure were - previously defined in DICOM. They are now retired (see PS3.3-1998). - + Attributes (0040,1006) Placer Order Number/Procedure and (0040,1007) Filler Order Number/Procedure were previously defined in DICOM. They are now retired (see PS3.3-1998). - Attributes (0040,2006) and - (0040,2007) were previously defined in DICOM. They are now retired (see - PS3.3-1998). - + Attributes (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see PS3.3-1998). - Only Attributes that are - specified in a SOP Instance at N-CREATE may later be updated through the N-SET. - If an SCU wishes to use the PPS Discontinuation Reason Code Sequence - (0040,0281), it must create that Attribute (zero-length) during MPPS N-CREATE. - + Only Attributes that are specified in a SOP Instance at N-CREATE may later be updated through the N-SET. If an SCU wishes to use the PPS Discontinuation Reason Code Sequence (0040,0281), it must create that Attribute (zero-length) during MPPS N-CREATE. - The Radiation Dose Module - was previously defined in DICOM. This is now retired (see PS3.3-2017c). - + The Radiation Dose Module was previously defined in DICOM. This is now retired (see PS3.3-2017c).
Service Class User - The SCU shall specify in the N-CREATE - request primitive the SOP Class and SOP Instance UIDs of the Modality Performed Procedure - Step SOP Instance that is created and for which Attribute Values are to be provided. - + The SCU shall specify in the N-CREATE request primitive the SOP Class and SOP Instance UIDs of the Modality Performed Procedure Step SOP Instance that is created and for which Attribute Values are to be provided. - This requirement facilitates the - inclusion of relevant Attributes in the Composite SOP Instances generated during the - Performed Procedure Step. - + This requirement facilitates the inclusion of relevant Attributes in the Composite SOP Instances generated during the Performed Procedure Step. - The SCU shall provide Attribute Values - for the Modality Performed Procedure Step SOP Class Attributes as specified in. Additionally, values may be - provided for optional Modality Performed Procedure Step IOD Attributes that are supported by - the SCP. The encoding rules for Modality Performed Procedure Step Attributes are specified - in the N-CREATE request primitive specification in. - - The SCU shall be capable of providing - all required Attribute Values to the SCP in the N-CREATE request primitive. The SCU may - provide Attribute Values for optional Attributes that are not maintained by the SCP. In such - case the SCU shall function properly regardless of whether the SCP accepts values for those - Attributes or not. - - All Attributes shall be created before - they can be set. Sequence Attributes shall be created before they can be filled. Sequence - Item Attributes shall not be created at zero length. - + The SCU shall provide Attribute Values for the Modality Performed Procedure Step SOP Class Attributes as specified in . Additionally, values may be provided for optional Modality Performed Procedure Step IOD Attributes that are supported by the SCP. The encoding rules for Modality Performed Procedure Step Attributes are specified in the N-CREATE request primitive specification in . + The SCU shall be capable of providing all required Attribute Values to the SCP in the N-CREATE request primitive. The SCU may provide Attribute Values for optional Attributes that are not maintained by the SCP. In such case the SCU shall function properly regardless of whether the SCP accepts values for those Attributes or not. + All Attributes shall be created before they can be set. Sequence Attributes shall be created before they can be filled. Sequence Item Attributes shall not be created at zero length. - Not all the Attributes that can be - created can be set afterward (see). - + Not all the Attributes that can be created can be set afterward (see ). - The SCU shall only send the N-CREATE - request primitive with the value for the Attribute "Performed Procedure Step Status" - (0040,0252) set to "IN PROGRESS". - + The SCU shall only send the N-CREATE request primitive with the value for the Attribute "Performed Procedure Step Status" (0040,0252) set to "IN PROGRESS". - It is assumed but not - required that the SCU (the modality) received the Study Instance UID within the - scope of the Basic Worklist Management SOP Class. - + It is assumed but not required that the SCU (the modality) received the Study Instance UID within the scope of the Basic Worklist Management SOP Class. - If the SCU has grouped - multiple Requested Procedures into a single performed step the Study Instance - UID (0020,000D) Attribute within the Scheduled Step Attributes Sequence - (0040,0270) may be the Study Instance UID (0020,000D) for the study that - contains all images and non-image composite instances created during performance - of the current step. This value may be generated by the SCU and may be the same - for all items of the sequence. In addition, the Referenced Study Sequence - (0008,1110) may contain the Study Instance UIDs from the Requested Procedures - being grouped. If Referenced Study Sequence (0008,1110) is present with an Item, - the SOP Class UID of the Detached Study Management SOP Class (Retired) may be - used in Referenced SOP Class UID (0008,1150). - + If the SCU has grouped multiple Requested Procedures into a single performed step the Study Instance UID (0020,000D) Attribute within the Scheduled Step Attributes Sequence (0040,0270) may be the Study Instance UID (0020,000D) for the study that contains all images and non-image composite instances created during performance of the current step. This value may be generated by the SCU and may be the same for all items of the sequence. In addition, the Referenced Study Sequence (0008,1110) may contain the Study Instance UIDs from the Requested Procedures being grouped. If Referenced Study Sequence (0008,1110) is present with an Item, the SOP Class UID of the Detached Study Management SOP Class (Retired) may be used in Referenced SOP Class UID (0008,1150). - If the SCU does not have - available Scheduled Procedure Step data applicable to the current step, the SCU - may generate a value for the Study Instance UID (0020,000D) Attribute within the - Scheduled Step Attributes Sequence (0040,0270). This value of the Study Instance - UID (0020,000D) may be stored in all images and non-image composite SOP - instances created during performance of this step. All other Attributes within - the Scheduled Step Attribute Sequence (0040,0270) may be set to zero length for - 2/2 requirement types or absent for 3/3 requirement types (see). - + If the SCU does not have available Scheduled Procedure Step data applicable to the current step, the SCU may generate a value for the Study Instance UID (0020,000D) Attribute within the Scheduled Step Attributes Sequence (0040,0270). This value of the Study Instance UID (0020,000D) may be stored in all images and non-image composite SOP instances created during performance of this step. All other Attributes within the Scheduled Step Attribute Sequence (0040,0270) may be set to zero length for 2/2 requirement types or absent for 3/3 requirement types (see ).
Service Class Provider - The N-CREATE operation allows the SCU - to provide to the SCP selected Attribute Values for a specific Modality Performed Procedure - Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-CREATE - Service used in conjunction with the appropriate Modality Performed Procedure Step SOP - Instance. - - The SCP shall return, via the N-CREATE - response primitive, the N-CREATE Response Status Code applicable to the associated request. - - The SCP shall accept N-CREATE request - primitives only if the value of the Attribute "Performed Procedure Step Status" (0040,0252) - is "IN PROGRESS". If the Performed Procedure Step Status Attribute has another value, the - SCP shall set the failure status code "Invalid Attribute Value" (Code: 0106H) with an - Attribute List. - + The N-CREATE operation allows the SCU to provide to the SCP selected Attribute Values for a specific Modality Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-CREATE Service used in conjunction with the appropriate Modality Performed Procedure Step SOP Instance. + The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request. + The SCP shall accept N-CREATE request primitives only if the value of the Attribute "Performed Procedure Step Status" (0040,0252) is "IN PROGRESS". If the Performed Procedure Step Status Attribute has another value, the SCP shall set the failure status code "Invalid Attribute Value" (Code: 0106H) with an Attribute List. - The SCP may update the scheduling - information on which the Modality Worklist is based, including the values of Study Date - (0008,0020) and Study Time (0008,0030) using the earliest corresponding values of - Performed Procedure Step Date (0040,0244) and Performed Procedure Step Time (0040,0245), - in order to achieve consistency of Study level Attributes when multiple procedure steps - are performed on different devices. - + The SCP may update the scheduling information on which the Modality Worklist is based, including the values of Study Date (0008,0020) and Study Time (0008,0030) using the earliest corresponding values of Performed Procedure Step Date (0040,0244) and Performed Procedure Step Time (0040,0245), in order to achieve consistency of Study level Attributes when multiple procedure steps are performed on different devices.
Status Codes - There are no specific status codes. See - - for response status codes. - + There are no specific status codes. See for response status codes.
Set Modality Performed Procedure Step Information - This operation allows an SCU to set - Attribute Values of an instance of the Modality Performed Procedure Step SOP Class and provide - information about a specific real-world Modality Performed Procedure Step that is under control - of the SCU. This operation shall be invoked through the DIMSE N-SET Service. - + This operation allows an SCU to set Attribute Values of an instance of the Modality Performed Procedure Step SOP Class and provide information about a specific real-world Modality Performed Procedure Step that is under control of the SCU. This operation shall be invoked through the DIMSE N-SET Service.
Modality Performed Procedure Step IOD Subset Specification - The Application Entity that claims - conformance to this SOP Class as an SCU may choose to modify a subset of the Attributes - maintained by the SCP. The Application Entity that claims conformance as an SCP to this SOP - Class shall support the subset of the Modality Performed Procedure Step Attributes specified - in. - - The character set used for Attribute - Values updated using the N-SET shall be the same as that specified by the N-CREATE Request - Primitive. - + The Application Entity that claims conformance to this SOP Class as an SCU may choose to modify a subset of the Attributes maintained by the SCP. The Application Entity that claims conformance as an SCP to this SOP Class shall support the subset of the Modality Performed Procedure Step Attributes specified in . + The character set used for Attribute Values updated using the N-SET shall be the same as that specified by the N-CREATE Request Primitive.
Service Class User - The SCU shall specify in the N-SET - request primitive the UID of the Modality Performed Procedure Step SOP Instance for which it - wants to set Attribute Values. - - The SCU shall be permitted to set - Attribute Values for any Modality Performed Procedure Step SOP Class Attribute specified in - . The SCU shall specify the list of - Modality Performed Procedure Step SOP Class Attributes for which it wants to set the - Attribute Values. The SCU shall provide, with one or more N-SET request primitives, the - Attribute Values specified in. The - encoding rules for Modality Performed Procedure Step Attributes are specified in the N-SET - request primitive specification in. The SCU shall - only set Attribute Values that are already created with an N-CREATE request. - - The SCU shall not send N-SET request - primitives for a Modality Performed Procedure Step SOP Instance after a N-SET request - primitive with a value for the Attribute "Performed Procedure Step Status" (0040,0252) is - "COMPLETED" or "DISCONTINUED" has been sent. - - If Sequences are included in a N-SET - command, all Items of a Sequence are to be included in the command and not only the Items to - be updated. - - Once the Modality Performed Procedure - Step Status (0040,0252) has been set to "COMPLETED" or "DISCONTINUED" the SCU shall no - longer modify the Modality Performed Procedure Step SOP Instance, and shall not create new - Composite SOP Instances as part of the same Modality Performed Procedure Step SOP Instance. - + The SCU shall specify in the N-SET request primitive the UID of the Modality Performed Procedure Step SOP Instance for which it wants to set Attribute Values. + The SCU shall be permitted to set Attribute Values for any Modality Performed Procedure Step SOP Class Attribute specified in . The SCU shall specify the list of Modality Performed Procedure Step SOP Class Attributes for which it wants to set the Attribute Values. The SCU shall provide, with one or more N-SET request primitives, the Attribute Values specified in . The encoding rules for Modality Performed Procedure Step Attributes are specified in the N-SET request primitive specification in . The SCU shall only set Attribute Values that are already created with an N-CREATE request. + The SCU shall not send N-SET request primitives for a Modality Performed Procedure Step SOP Instance after a N-SET request primitive with a value for the Attribute "Performed Procedure Step Status" (0040,0252) is "COMPLETED" or "DISCONTINUED" has been sent. + If Sequences are included in a N-SET command, all Items of a Sequence are to be included in the command and not only the Items to be updated. + Once the Modality Performed Procedure Step Status (0040,0252) has been set to "COMPLETED" or "DISCONTINUED" the SCU shall no longer modify the Modality Performed Procedure Step SOP Instance, and shall not create new Composite SOP Instances as part of the same Modality Performed Procedure Step SOP Instance. - A Modality that wishes to continue - or resume creating Composite SOP Instances may create a new Modality Performed Procedure - Step. - + A Modality that wishes to continue or resume creating Composite SOP Instances may create a new Modality Performed Procedure Step. - Before or when Modality Performed - Procedure Step Status (0040,0252) is set to "COMPLETED" or "DISCONTINUED" the SCU shall have - created or set all the Attributes according to the requirements in the Final State column of - . - - Before or when Modality Performed - Procedure Step Status (0040,0252) is set to "COMPLETED" or "DISCONTINUED" the SCU shall have - sent to the SCP a list of all Image SOP Instances and all Non-Image Composite SOP Instances - created during the Procedure Step in Referenced Image Sequence (0008,1140) and Referenced - Non-Image Composite SOP Instance Sequence (0040,0220) respectively. - + Before or when Modality Performed Procedure Step Status (0040,0252) is set to "COMPLETED" or "DISCONTINUED" the SCU shall have created or set all the Attributes according to the requirements in the Final State column of . + Before or when Modality Performed Procedure Step Status (0040,0252) is set to "COMPLETED" or "DISCONTINUED" the SCU shall have sent to the SCP a list of all Image SOP Instances and all Non-Image Composite SOP Instances created during the Procedure Step in Referenced Image Sequence (0008,1140) and Referenced Non-Image Composite SOP Instance Sequence (0040,0220) respectively. - The intent is that a - completed or discontinued Modality Performed Procedure Step entity will contain - a complete list of all the Images and Non-Image Composite SOP Instances that - were created. - + The intent is that a completed or discontinued Modality Performed Procedure Step entity will contain a complete list of all the Images and Non-Image Composite SOP Instances that were created. - The distinction between the - list of images and non-images is present for historic reasons only, and has no - semantic significance. - + The distinction between the list of images and non-images is present for historic reasons only, and has no semantic significance. - The Modality Performed Procedure Step - Status (0040,0252) shall not be set to "COMPLETED" or "DISCONTINUED" if the list contains - neither Image references nor Non-Image Composite SOP Instance references, unless no such - Instances were created. - + The Modality Performed Procedure Step Status (0040,0252) shall not be set to "COMPLETED" or "DISCONTINUED" if the list contains neither Image references nor Non-Image Composite SOP Instance references, unless no such Instances were created.
Service Class Provider - The N-SET operation allows the SCU to - request that the SCP update selected Attribute Values for a specific Modality Performed - Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE - N-SET Service used in conjunction with the appropriate Modality Performed Procedure Step SOP - Instance. The N-SET value for Specific Character Set (0008,0005) does not replace the - previous value. The SCP shall appropriately modify its internal representation so that - subsequent operations reflect the combination of the character sets in use by the Attributes - in this N-SET and those used by Attributes that have not been modified. - + The N-SET operation allows the SCU to request that the SCP update selected Attribute Values for a specific Modality Performed Procedure Step SOP Instance. This operation shall be invoked through the use of the DIMSE N-SET Service used in conjunction with the appropriate Modality Performed Procedure Step SOP Instance. The N-SET value for Specific Character Set (0008,0005) does not replace the previous value. The SCP shall appropriately modify its internal representation so that subsequent operations reflect the combination of the character sets in use by the Attributes in this N-SET and those used by Attributes that have not been modified. - The SCP may need to convert the - text for instance to the Unicode character set. If the SCP is not able to perform a - necessary conversion it may return the Invalid Attribute Value error code (0106H). - + The SCP may need to convert the text for instance to the Unicode character set. If the SCP is not able to perform a necessary conversion it may return the Invalid Attribute Value error code (0106H). - The SCP shall return, via the N-SET - response primitive, the N-SET Response Status Code applicable to the associated request. - Contingent on the N-SET Response Status, the SCP shall update the Referenced Performed - Procedure Step Attributes. - - The SCP shall accept N-SET request - primitives only if the value of the already existing Attribute "Performed Procedure Step - Status" (0040,0252) is "IN PROGRESS". If the already existing Performed Procedure Step - Status Attribute has another value, the SCP shall set the failure status code "Processing - failure" (Code: 0110H) with a Specific Error Comment (see). - - The SCP may itself modify any - Attributes of the Modality Performed Procedure Step SOP Instance only after the "Performed - Procedure Step Status" (0040,0252) has been set to "COMPLETED" or "DISCONTINUED". - + The SCP shall return, via the N-SET response primitive, the N-SET Response Status Code applicable to the associated request. Contingent on the N-SET Response Status, the SCP shall update the Referenced Performed Procedure Step Attributes. + The SCP shall accept N-SET request primitives only if the value of the already existing Attribute "Performed Procedure Step Status" (0040,0252) is "IN PROGRESS". If the already existing Performed Procedure Step Status Attribute has another value, the SCP shall set the failure status code "Processing failure" (Code: 0110H) with a Specific Error Comment (see ). + The SCP may itself modify any Attributes of the Modality Performed Procedure Step SOP Instance only after the "Performed Procedure Step Status" (0040,0252) has been set to "COMPLETED" or "DISCONTINUED". - Such coercion of Attributes - by the SCP may be necessary to correct, for example, patient identification - information or incorrectly selected scheduling information. Such an operation is - not permitted to the SCU by the requirements described in, which might create - a new Modality Performed Procedure Step SOP Instance to achieve the same - objective. - + Such coercion of Attributes by the SCP may be necessary to correct, for example, patient identification information or incorrectly selected scheduling information. Such an operation is not permitted to the SCU by the requirements described in , which might create a new Modality Performed Procedure Step SOP Instance to achieve the same objective. - Under exceptional - circumstances, it may be necessary for the SCP to itself set the Performed - Procedure Step Status (0040,0252) to COMPLETED or DISCONTINUED, for example if - the Modality has failed. When the Modality recovers, subsequent N-SETs may fail. - + Under exceptional circumstances, it may be necessary for the SCP to itself set the Performed Procedure Step Status (0040,0252) to COMPLETED or DISCONTINUED, for example if the Modality has failed. When the Modality recovers, subsequent N-SETs may fail.
Status Codes - There are no specific status codes. The - specific Error Comment and Error ID that may be returned with a status code of Processsing - Failure in a N-SET-RSP are defined in. See - - for additional response status codes. - + There are no specific status codes. The specific Error Comment and Error ID that may be returned with a status code of Processsing Failure in a N-SET-RSP are defined in . See for additional response status codes.
Modality Performed Procedure Step SOP Class N-CREATE, N-SET and Final State - Attributes - Modality Performed Procedure Step SOP Class N-CREATE, N-SET and Final State Attributes
@@ -18894,43 +13210,31 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) - Requirement Type Final - State (see Note 1) - + Requirement Type Final State (see Note 1)
- Specific Character - Set - + Specific Character Set (0008,0005) 1C/1C - (Required if an - extended or replacement character set is used) - + (Required if an extended or replacement character set is used) 1C/1C - (Required if an - extended or replacement character set is used in an Attribute that is set) - + (Required if an extended or replacement character set is used in an Attribute that is set)
- Scheduled Step - Attribute Sequence - + Scheduled Step Attribute Sequence (0040,0270) @@ -18960,9 +13262,7 @@
- >Study Instance - UID - + >Study Instance UID (0020,000D) @@ -18977,9 +13277,7 @@
- >Referenced Study - Sequence - + >Referenced Study Sequence (0008,1110) @@ -18994,9 +13292,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -19011,9 +13307,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -19028,8 +13322,7 @@
- >Accession Number - + >Accession Number (0008,0050) @@ -19044,9 +13337,7 @@
- >Issuer of Accession - Number Sequence - + >Issuer of Accession Number Sequence (0008,0051) @@ -19061,18 +13352,14 @@
- >>Local Namespace - Entity ID - + >>Local Namespace Entity ID (0040,0031) 1C/1C - Required if Universal - Entity ID (0040,0032) is not present; may be present otherwise - + Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed @@ -19081,18 +13368,14 @@
- >>Universal - Entity ID - + >>Universal Entity ID (0040,0032) 1C/1C - Required if Local - Namespace Entity ID (0040,0031) is not present; may be present otherwise. - + Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. Not allowed @@ -19101,18 +13384,14 @@
- >>Universal - Entity ID Type - + >>Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present. Not allowed @@ -19121,9 +13400,7 @@
- >Placer Order - Number/Imaging Service Request - + >Placer Order Number/Imaging Service Request (0040,2016) @@ -19138,9 +13415,7 @@
- >Order Placer - Identifier Sequence - + >Order Placer Identifier Sequence (0040,0026) @@ -19155,18 +13430,14 @@
- >>Local Namespace - Entity ID - + >>Local Namespace Entity ID (0040,0031) 1C/1C - Required if Universal - Entity ID (0040,0032) is not present; may be present otherwise - + Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed @@ -19175,18 +13446,14 @@
- >>Universal - Entity ID - + >>Universal Entity ID (0040,0032) 1C/1C - Required if Local - Namespace Entity ID (0040,0031) is not present; may be present otherwise.. - + Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed @@ -19195,18 +13462,14 @@
- >>Universal - Entity ID Type - + >>Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present. Not allowed @@ -19215,9 +13478,7 @@
- >Filler Order - Number/Imaging Service Request - + >Filler Order Number/Imaging Service Request (0040,2017) @@ -19232,9 +13493,7 @@
- >Order Filler - Identifier Sequence - + >Order Filler Identifier Sequence (0040,0027) @@ -19249,18 +13508,14 @@
- >>Local Namespace - Entity ID - + >>Local Namespace Entity ID (0040,0031) 1C/1C - Required if Universal - Entity ID (0040,0032) is not present; may be present otherwise - + Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed @@ -19269,18 +13524,14 @@
- >>Universal - Entity ID - + >>Universal Entity ID (0040,0032) 1C/1C - Required if Local - Namespace Entity ID (0040,0031) is not present; may be present otherwise.. - + Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed @@ -19289,18 +13540,14 @@
- >>Universal - Entity ID Type - + >>Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present. Not allowed @@ -19309,9 +13556,7 @@
- >Requested Procedure - ID - + >Requested Procedure ID (0040,1001) @@ -19326,9 +13571,7 @@
- >Requested Procedure - Code Sequence - + >Requested Procedure Code Sequence (0032,1064) @@ -19344,17 +13587,14 @@
- >>Include - - - +>>Include + +
- >Requested Procedure - Description - + >Requested Procedure Description (0032,1060) @@ -19369,9 +13609,7 @@
- >Scheduled Procedure - Step ID - + >Scheduled Procedure Step ID (0040,0009) @@ -19386,9 +13624,7 @@
- >Scheduled Procedure - Step Description - + >Scheduled Procedure Step Description (0040,0007) @@ -19403,9 +13639,7 @@
- >Scheduled Protocol - Code Sequence - + >Scheduled Protocol Code Sequence (0040,0008) @@ -19421,10 +13655,9 @@
- >>Include - - - +>>Include + +
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -19475,9 +13707,7 @@
- Issuer of Patient ID - Qualifiers Sequence - + Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -19492,9 +13722,7 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) @@ -19509,18 +13737,14 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present. Not allowed @@ -19530,9 +13754,7 @@
- >All other Attributes of the Issuer of Patient ID - Qualifiers Sequence - + >All other Attributes of the Issuer of Patient ID Qualifiers Sequence @@ -19546,9 +13768,7 @@
- Other Patient IDs - Sequence - + Other Patient IDs Sequence (0010,1002) @@ -19578,9 +13798,7 @@
- >Issuer of Patient - ID - + >Issuer of Patient ID (0010,0021) @@ -19595,9 +13813,7 @@
- >Issuer of Patient - ID Qualifiers Sequence - + >Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -19613,9 +13829,7 @@
- >>All other Attributes of the Issuer of - Patient ID Qualifiers Sequence - + >>All other Attributes of the Issuer of Patient ID Qualifiers Sequence @@ -19631,9 +13845,7 @@
- >Type of Patient - ID - + >Type of Patient ID (0010,0022) @@ -19648,8 +13860,7 @@
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -19679,9 +13890,7 @@
- Referenced Patient - Sequence - + Referenced Patient Sequence (0008,1120) @@ -19696,9 +13905,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -19713,9 +13920,7 @@
- >Referenced Instance - UID - + >Referenced Instance UID (0008,1155) @@ -19745,9 +13950,7 @@
- Issuer of Admission ID - Sequence - + Issuer of Admission ID Sequence (0038,0014) @@ -19762,18 +13965,14 @@
- >Local Namespace - Entity ID - + >Local Namespace Entity ID (0040,0031) 1C/1C - Required if Universal - Entity ID (0040,0032) is not present; may be present otherwise - + Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed @@ -19782,18 +13981,14 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) 1C/1C - Required if Local - Namespace Entity ID (0040,0031) is not present; may be present otherwise.. - + Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed @@ -19802,18 +13997,14 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present. Not allowed @@ -19822,8 +14013,7 @@
- Service Episode ID - + Service Episode ID (0038,0060) @@ -19838,9 +14028,7 @@
- Issuer of Service - Episode ID Sequence - + Issuer of Service Episode ID Sequence (0038,0064) @@ -19855,18 +14043,14 @@
- >Local Namespace - Entity ID - + >Local Namespace Entity ID (0040,0031) 1C/1C - Required if Universal - Entity ID (0040,0032) is not present; may be present otherwise - + Required if Universal Entity ID (0040,0032) is not present; may be present otherwise Not allowed @@ -19875,18 +14059,14 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) 1C/1C - Required if Local - Namespace Entity ID (0040,0031) is not present; may be present otherwise.. - + Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.. Not allowed @@ -19895,18 +14075,14 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present. Not allowed @@ -19915,9 +14091,7 @@
- Service Episode - Description - + Service Episode Description (0038,0062) @@ -19939,9 +14113,7 @@
- Performed Procedure - Step ID - + Performed Procedure Step ID (0040,0253) @@ -19956,9 +14128,7 @@
- Performed Station AE - Title - + Performed Station AE Title (0040,0241) @@ -19973,9 +14143,7 @@
- Performed Station - Name - + Performed Station Name (0040,0242) @@ -19990,8 +14158,7 @@
- Performed Location - + Performed Location (0040,0243) @@ -20006,9 +14173,7 @@
- Performed Procedure - Step Start Date - + Performed Procedure Step Start Date (0040,0244) @@ -20023,9 +14188,7 @@
- Performed Procedure - Step Start Time - + Performed Procedure Step Start Time (0040,0245) @@ -20040,9 +14203,7 @@
- Performed Procedure - Step Status - + Performed Procedure Step Status (0040,0252) @@ -20057,9 +14218,7 @@
- Performed Procedure - Step Description - + Performed Procedure Step Description (0040,0254) @@ -20074,9 +14233,7 @@
- Performed Procedure - Type Description - + Performed Procedure Type Description (0040,0255) @@ -20091,9 +14248,7 @@
- Procedure Code - Sequence - + Procedure Code Sequence (0008,1032) @@ -20109,17 +14264,14 @@
- >Include - - - +>Include + +
- Reason For Performed - Procedure Code Sequence - + Reason For Performed Procedure Code Sequence (0040,1012) @@ -20135,17 +14287,14 @@
- >Include - - - +>Include + +
- Performed Procedure - Step End Date - + Performed Procedure Step End Date (0040,0250) @@ -20162,9 +14311,7 @@
- Performed Procedure - Step End Time - + Performed Procedure Step End Time (0040,0251) @@ -20181,9 +14328,7 @@
- Comments on the - Performed Procedure Step - + Comments on the Performed Procedure Step (0040,0280) @@ -20198,9 +14343,7 @@
- Performed Procedure - Step Discontinuation Reason Code Sequence - + Performed Procedure Step Discontinuation Reason Code Sequence (0040,0281) @@ -20216,10 +14359,9 @@
- >Include - - - +>Include + +
- Performed Protocol Code - Sequence - + Performed Protocol Code Sequence (0040,0260) @@ -20279,17 +14419,14 @@
- >Include - - - +>Include + +
- Performed Series - Sequence - + Performed Series Sequence (0040,0340) @@ -20307,9 +14444,7 @@
- >Performing - Physician's Name - + >Performing Physician's Name (0008,1050) @@ -20326,8 +14461,7 @@
- >Protocol Name - + >Protocol Name (0018,1030) @@ -20344,8 +14478,7 @@
- >Operators' Name - + >Operators' Name (0008,1070) @@ -20362,9 +14495,7 @@
- >Series Instance - UID - + >Series Instance UID (0020,000E) @@ -20381,9 +14512,7 @@
- >Series - Description - + >Series Description (0008,103E) @@ -20400,8 +14529,7 @@
- >Retrieve AE Title - + >Retrieve AE Title (0008,0054) @@ -20418,8 +14546,7 @@
- >Archive Requested - + >Archive Requested (0040,A494) @@ -20434,9 +14561,7 @@
- >Referenced Image - Sequence - + >Referenced Image Sequence (0008,1140) @@ -20448,16 +14573,13 @@ 2/2 - See - + See
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -20472,9 +14594,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -20489,9 +14609,7 @@
- >>Container - Identifier - + >>Container Identifier (0040,0512) @@ -20506,9 +14624,7 @@
- >>Specimen - Description Sequence - + >>Specimen Description Sequence (0040,0560) @@ -20523,9 +14639,7 @@
- >>>Specimen - Identifier - + >>>Specimen Identifier (0040,0551) @@ -20540,9 +14654,7 @@
- >>>Specimen - UID - + >>>Specimen UID (0040,0554) @@ -20557,9 +14669,7 @@
- >Referenced - Non-Image Composite SOP Instance Sequence - + >Referenced Non-Image Composite SOP Instance Sequence (0040,0220) @@ -20571,16 +14681,13 @@ 2/2 - See - + See
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -20595,9 +14702,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -20613,9 +14718,7 @@
- >All other Attributes of the Performed Series - Sequence - + >All other Attributes of the Performed Series Sequence @@ -20630,9 +14733,7 @@
- All other Attributes of the - + All other Attributes of the
@@ -20975,13 +14881,10 @@ Status Code @@ -20991,16 +14894,13 @@ Failure
N-SET Status
- Error Comment - (0000,0902) - + Error Comment (0000,0902) - Error ID (0000,0903) - + Error ID (0000,0903)
- Processing Failure - + Processing Failure 0110 - Performed Procedure - Step Object may no longer be updated - + Performed Procedure Step Object may no longer be updated A710 @@ -21013,98 +14913,46 @@
Modality Performed Procedure Step SOP Class UID - The Modality Performed Procedure Step SOP Class - shall be uniquely identified by the Modality Performed Procedure Step SOP Class UID that shall have - the value "1.2.840.10008.3.1.2.3.3". - + The Modality Performed Procedure Step SOP Class shall be uniquely identified by the Modality Performed Procedure Step SOP Class UID that shall have the value "1.2.840.10008.3.1.2.3.3".
Conformance Requirements - Implementations providing conformance to the - Modality Performed Procedure Step SOP Class shall be conformant as described in the following - sections and shall include within their Conformance Statement information as described below. - - An implementation may conform to this SOP Class - as an SCU or as an SCP. The Conformance Statement shall be in the format defined in. - + Implementations providing conformance to the Modality Performed Procedure Step SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below. + An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to - this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes. - + An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes.
Operations - Any Attributes for which Attribute - Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the - Conformance Statement. - - Any Attributes for which Attribute - Values may be provided (using the N-SET Service) by the SCU shall be enumerated in the - Conformance Statement. - - An implementation that conforms to this - SOP Class as an SCU shall specify under which conditions during the performance of the - real-world Performed Procedure Step it will create the SOP Class Instance and under which - conditions it will set the status value to COMPLETED and DISCONTINUED. - - An implementation that conforms to this - SOP Class as an SCU shall specify what strategy it applies to group Storage SOP Class - Instances referenced in a Performed Procedure Step. - + Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the Conformance Statement. + Any Attributes for which Attribute Values may be provided (using the N-SET Service) by the SCU shall be enumerated in the Conformance Statement. + An implementation that conforms to this SOP Class as an SCU shall specify under which conditions during the performance of the real-world Performed Procedure Step it will create the SOP Class Instance and under which conditions it will set the status value to COMPLETED and DISCONTINUED. + An implementation that conforms to this SOP Class as an SCU shall specify what strategy it applies to group Storage SOP Class Instances referenced in a Performed Procedure Step. - For example, whether or not - Radiation Dose SR instances are sent within the same Performed Procedure Step as the - images to which it applies, or a different Performed Procedure Step. See the discussion - of the MPPS in the DICOM real-world model in. - + For example, whether or not Radiation Dose SR instances are sent within the same Performed Procedure Step as the images to which it applies, or a different Performed Procedure Step. See the discussion of the MPPS in the DICOM real-world model in .
SCP Conformance - An implementation that is conformant to - this SOP Class as an SCP shall meet conformance requirements for the operations that it - performs. - + An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations that it performs.
Operations - Any Attributes for which Attribute - Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the - Conformance Statement. - - Any Attributes for which Attribute - Values may be updated (using the N-SET Service) by the SCU shall be enumerated in the - Conformance Statement. - - The Conformance Statement shall also - provide information on the behavior of the SCP at the following occurrences: - + Any Attributes for which Attribute Values may be provided (using the N-CREATE Service) by the SCU shall be enumerated in the Conformance Statement. + Any Attributes for which Attribute Values may be updated (using the N-SET Service) by the SCU shall be enumerated in the Conformance Statement. + The Conformance Statement shall also provide information on the behavior of the SCP at the following occurrences: - The creation of a new Instance - of the Modality Performed Procedure Step SOP Class with the status "IN PROGRESS". - The result of that process on the scheduling information and on the Attributes - values of the Modality Worklist SOP Class shall be specified. - + The creation of a new Instance of the Modality Performed Procedure Step SOP Class with the status "IN PROGRESS". The result of that process on the scheduling information and on the Attributes values of the Modality Worklist SOP Class shall be specified. - The update of the Attribute - "Performed Procedure Step Status", i.e., the change from the state "IN PROGRESS" to - "DISCONTINUED" or to "COMPLETED". - + The update of the Attribute "Performed Procedure Step Status", i.e., the change from the state "IN PROGRESS" to "DISCONTINUED" or to "COMPLETED". - Which Attributes the SCP may - coerce after the state has been set to "IN PROGRESS" or "DISCONTINUED" or to - "COMPLETED". - + Which Attributes the SCP may coerce after the state has been set to "IN PROGRESS" or "DISCONTINUED" or to "COMPLETED". - For how long the Modality - Performed Procedure Step SOP Instance will persist on the SCP. - + For how long the Modality Performed Procedure Step SOP Instance will persist on the SCP.
@@ -21115,18 +14963,13 @@ Modality Performed Procedure Step Retrieve SOP Class
DIMSE Service Group - The DIMSE Services shown in - - are applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure - Step Retrieve SOP Class. - + The DIMSE Services shown in are applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure Step Retrieve SOP Class.
DIMSE Service Group Applicable to Modality Performed Procedure Step Retrieve
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -21144,56 +14987,22 @@
- The DIMSE Services and Protocols are specified - in. If the Modality - Performed Procedure Step Object is no longer available the Request Primitive will be answered with a - Failure Status message "No such Object Instance". - + The DIMSE Services and Protocols are specified in . If the Modality Performed Procedure Step Object is no longer available the Request Primitive will be answered with a Failure Status message "No such Object Instance".
Operations - The Application Entity that claims conformance - to this SOP Class as an SCU shall be permitted to invoke the following operations and the - Application Entity that claims conformance as an SCP shall be capable of providing the following - operations. - + The Application Entity that claims conformance to this SOP Class as an SCU shall be permitted to invoke the following operations and the Application Entity that claims conformance as an SCP shall be capable of providing the following operations.
Get Performed Procedure Step Information - This operation allows an SCU to get - information about a specific real-world Performed Procedure Step that is represented as a - Modality Performed Procedure Step Retrieve SOP Instance by a Modality Performed Procedure Step - Retrieve SCP. The operation is performed on a Modality Performed Procedure Step IOD. This - operation shall be invoked through the DIMSE N-GET Service used in conjunction with the - appropriate Modality Performed Procedure Step Retrieve SOP Instance. - - The same SOP Instance UID is shared by all - three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created - and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved - using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve - SOP Class. Changes in its state can be notified by using its SOP Instance UID within the service - of the Modality Performed Procedure Step Notification SOP Class. The SOP Class UID specified in - the DIMSE N-GET request primitive shall be the UID of the Modality Performed Procedure Step - Retrieve SOP Class. - - The Modality Performed Procedure Retrieve - Step SOP Instance UID shall not be used to identify a SOP Instance of the Study Component - Service Class. - + This operation allows an SCU to get information about a specific real-world Performed Procedure Step that is represented as a Modality Performed Procedure Step Retrieve SOP Instance by a Modality Performed Procedure Step Retrieve SCP. The operation is performed on a Modality Performed Procedure Step IOD. This operation shall be invoked through the DIMSE N-GET Service used in conjunction with the appropriate Modality Performed Procedure Step Retrieve SOP Instance. + The same SOP Instance UID is shared by all three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve SOP Class. Changes in its state can be notified by using its SOP Instance UID within the service of the Modality Performed Procedure Step Notification SOP Class. The SOP Class UID specified in the DIMSE N-GET request primitive shall be the UID of the Modality Performed Procedure Step Retrieve SOP Class. + The Modality Performed Procedure Retrieve Step SOP Instance UID shall not be used to identify a SOP Instance of the Study Component Service Class. - An Application Entity may support the - SCU role of the Modality Performed Procedure Step Retrieve SOP Class in order to obtain - information about Performed Procedure Steps created by other Application Entities. - + An Application Entity may support the SCU role of the Modality Performed Procedure Step Retrieve SOP Class in order to obtain information about Performed Procedure Steps created by other Application Entities.
Modality Performed Procedure Step Retrieve IOD Subset Specifications - The Application Entity that claims - conformance to this SOP Class as an SCU may choose to interpret the Attribute Values - maintained by the SCP that the SCU receives via the operation of this SOP Class. The - Application Entity that claims conformance as an SCP to this Modality Performed Procedure - Step Retrieve SOP Class shall support the subset of the Modality Performed Procedure Step - Retrieve Attributes specified in. - + The Application Entity that claims conformance to this SOP Class as an SCU may choose to interpret the Attribute Values maintained by the SCP that the SCU receives via the operation of this SOP Class. The Application Entity that claims conformance as an SCP to this Modality Performed Procedure Step Retrieve SOP Class shall support the subset of the Modality Performed Procedure Step Retrieve Attributes specified in . @@ -21205,27 +15014,21 @@ Tag @@ -21237,9 +15040,7 @@ @@ -21614,8 +15364,7 @@ @@ -22148,9 +15826,7 @@ @@ -22388,86 +16036,36 @@ - Attributes (0040,1006) - Placer Order Number/Procedure and (0040,1007) Filler Order Number/Procedure were - previously defined in DICOM. They are now retired (see PS3.3-1998). - + Attributes (0040,1006) Placer Order Number/Procedure and (0040,1007) Filler Order Number/Procedure were previously defined in DICOM. They are now retired (see PS3.3-1998). - Attributes (0040,2006) and - (0040,2007) were previously defined in DICOM. They are now retired (see - PS3.3-1998). - + Attributes (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see PS3.3-1998). - The Radiation Dose Module - was previously defined in DICOM. This is now retired (see PS3.3-2017c). - + The Radiation Dose Module was previously defined in DICOM. This is now retired (see PS3.3-2017c).
Service Class User - The SCU uses the N-GET Service Element - to request the SCP to get a Modality Performed Procedure Step Retrieve SOP Instance. The SCU - shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved, - which is a UID of a Modality Performed Procedure Step SOP Instance. The SCU shall be - permitted to request that Attribute Values be returned for any Modality Performed Procedure - Step Retrieve SOP Class Attribute specified in. - Additionally values may be requested for optional Modality Performed Procedure Step IOD - Attributes. - - The SCU shall specify the list of - Modality Performed Procedure Step Retrieve SOP Class Attributes for which values are to be - returned. The encoding rules for Modality Performed Procedure Step Attributes are specified - in the N-GET request primitive specification in. - - In an N-GET operation, the values of - Attributes that are defined within a Sequence of Items shall not be requested by an SCU. - - The SCU shall be capable of receiving - all requested Attribute Values provided by the SCP in response to the N-GET indication - primitive. The SCU may request Attribute Values for optional Attributes that are not - maintained by the SCP. In such a case, the SCU shall function properly regardless of whether - the SCP returns values for those Attributes or not. This Service Class Specification places - no requirements on what the SCU shall do as a result of receiving this information. - + The SCU uses the N-GET Service Element to request the SCP to get a Modality Performed Procedure Step Retrieve SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved, which is a UID of a Modality Performed Procedure Step SOP Instance. The SCU shall be permitted to request that Attribute Values be returned for any Modality Performed Procedure Step Retrieve SOP Class Attribute specified in . Additionally values may be requested for optional Modality Performed Procedure Step IOD Attributes. + The SCU shall specify the list of Modality Performed Procedure Step Retrieve SOP Class Attributes for which values are to be returned. The encoding rules for Modality Performed Procedure Step Attributes are specified in the N-GET request primitive specification in . + In an N-GET operation, the values of Attributes that are defined within a Sequence of Items shall not be requested by an SCU. + The SCU shall be capable of receiving all requested Attribute Values provided by the SCP in response to the N-GET indication primitive. The SCU may request Attribute Values for optional Attributes that are not maintained by the SCP. In such a case, the SCU shall function properly regardless of whether the SCP returns values for those Attributes or not. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information. - In order to accurately interpret - the character set used for the Attribute Values returned, it is recommended that the - Attribute Value for the Specific Character Set (0008,0005) be requested in the N-GET - request primitive. - + In order to accurately interpret the character set used for the Attribute Values returned, it is recommended that the Attribute Value for the Specific Character Set (0008,0005) be requested in the N-GET request primitive.
Service Class Provider - The N-GET operation allows the SCU to - request from the SCP selected Attribute Values for a specific Modality Performed Procedure - Step SOP Instance via a Modality Performed Procedure Step Retrieve SOP Instance. This - operation shall be invoked through the use of the DIMSE N-GET Service used in conjunction - with the appropriate Modality Performed Procedure Step Retrieve SOP Instance that equals the - Modality Performed Procedure SOP Instance. The SCP shall retrieve the selected Attribute - Values from the indicated Modality Performed Procedure Step SOP Instance. - - The SCP shall return, via the N-GET - response primitive, the N-GET Response Status Code applicable to the associated request. A - Failure Code shall indicate that the SCP has not retrieved the SOP Instance. Contingent on - the N-GET Response Status, the SCP shall return, via the N-GET response primitive, Attribute - Values for all requested Attributes maintained by the SCP. - + The N-GET operation allows the SCU to request from the SCP selected Attribute Values for a specific Modality Performed Procedure Step SOP Instance via a Modality Performed Procedure Step Retrieve SOP Instance. This operation shall be invoked through the use of the DIMSE N-GET Service used in conjunction with the appropriate Modality Performed Procedure Step Retrieve SOP Instance that equals the Modality Performed Procedure SOP Instance. The SCP shall retrieve the selected Attribute Values from the indicated Modality Performed Procedure Step SOP Instance. + The SCP shall return, via the N-GET response primitive, the N-GET Response Status Code applicable to the associated request. A Failure Code shall indicate that the SCP has not retrieved the SOP Instance. Contingent on the N-GET Response Status, the SCP shall return, via the N-GET response primitive, Attribute Values for all requested Attributes maintained by the SCP.
Status Codes - - defines the specific status code values that might be returned in a N-GET response. See - - for additional response status codes. - + defines the specific status code values that might be returned in a N-GET response. See for additional response status codes.
Modality Performed Procedure Step Retrieve SOP Class N-GET Attributes
- Requirement Type - (SCU/SCP) - + Requirement Type (SCU/SCP)
- Specific Character - Set - + Specific Character Set (0008,0005) 3/1C - (Required if an - extended or replacement character set is used) - + (Required if an extended or replacement character set is used)
- Scheduled Step - Attributes Sequence - + Scheduled Step Attributes Sequence (0040,0270) @@ -21250,9 +15051,7 @@
- >Study Instance - UID - + >Study Instance UID (0020,000D) @@ -21263,9 +15062,7 @@
- >Referenced Study - Sequence - + >Referenced Study Sequence (0008,1110) @@ -21276,9 +15073,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -21289,9 +15084,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -21302,8 +15095,7 @@
- >Accession Number - + >Accession Number (0008,0050) @@ -21314,9 +15106,7 @@
- >Issuer of Accession - Number Sequence - + >Issuer of Accession Number Sequence (0008,0051) @@ -21327,9 +15117,7 @@
- >>Local Namespace - Entity ID - + >>Local Namespace Entity ID (0040,0031) @@ -21340,9 +15128,7 @@
- >>Universal - Entity ID - + >>Universal Entity ID (0040,0032) @@ -21353,9 +15139,7 @@
- >>Universal - Entity ID Type - + >>Universal Entity ID Type (0040,0033) @@ -21366,9 +15150,7 @@
- >Placer Order - Number/Imaging Service Request - + >Placer Order Number/Imaging Service Request (0040,2016) @@ -21379,9 +15161,7 @@
- >Order Placer - Identifier Sequence - + >Order Placer Identifier Sequence (0040,0026) @@ -21392,9 +15172,7 @@
- >>Local Namespace - Entity ID - + >>Local Namespace Entity ID (0040,0031) @@ -21405,9 +15183,7 @@
- >>Universal - Entity ID - + >>Universal Entity ID (0040,0032) @@ -21418,9 +15194,7 @@
- >>Universal - Entity ID Type - + >>Universal Entity ID Type (0040,0033) @@ -21431,9 +15205,7 @@
- >Filler Order - Number/Imaging Service Request - + >Filler Order Number/Imaging Service Request (0040,2017) @@ -21444,9 +15216,7 @@
- >Order Filler - Identifier Sequence - + >Order Filler Identifier Sequence (0040,0027) @@ -21457,9 +15227,7 @@
- >>Local Namespace - Entity ID - + >>Local Namespace Entity ID (0040,0031) @@ -21470,9 +15238,7 @@
- >>Universal - Entity ID - + >>Universal Entity ID (0040,0032) @@ -21483,9 +15249,7 @@
- >>Universal - Entity ID Type - + >>Universal Entity ID Type (0040,0033) @@ -21496,9 +15260,7 @@
- >Requested Procedure - Code Sequence - + >Requested Procedure Code Sequence (0032,1064) @@ -21510,17 +15272,14 @@
- >>Include - - - +>>Include + +
- >Requested Procedure - Description - + >Requested Procedure Description (0032,1060) @@ -21531,9 +15290,7 @@
- >Requested Procedure - ID - + >Requested Procedure ID (0040,1001) @@ -21544,9 +15301,7 @@
- >Scheduled Procedure - Step ID - + >Scheduled Procedure Step ID (0040,0009) @@ -21557,9 +15312,7 @@
- >Scheduled Procedure - Step Description - + >Scheduled Procedure Step Description (0040,0007) @@ -21570,9 +15323,7 @@
- >Scheduled Protocol - Code Sequence - + >Scheduled Protocol Code Sequence (0040,0008) @@ -21584,10 +15335,9 @@
- >>Include - - - +>>Include + +
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -21626,9 +15375,7 @@
- Issuer of Patient ID - Qualifiers Sequence - + Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -21639,9 +15386,7 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) @@ -21652,26 +15397,20 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) 1C/1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present.
- >All other Attributes of the Issuer of Patient ID - Qualifiers Sequence - + >All other Attributes of the Issuer of Patient ID Qualifiers Sequence @@ -21692,9 +15431,7 @@
- >Issuer of Patient - ID - + >Issuer of Patient ID (0010,0021) @@ -21705,9 +15442,7 @@
- >Issuer of Patient - ID Qualifiers Sequence - + >Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -21719,9 +15454,7 @@
- >>All other Attributes of the Issuer of - Patient ID Qualifiers Sequence - + >>All other Attributes of the Issuer of Patient ID Qualifiers Sequence @@ -21733,8 +15466,7 @@
- Patient's Birth Date - + Patient's Birth Date (0010,0032) @@ -21756,9 +15488,7 @@
- Referenced Patient - Sequence - + Referenced Patient Sequence (0008,1120) @@ -21769,9 +15499,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -21782,9 +15510,7 @@
- >Referenced Instance - UID - + >Referenced Instance UID (0008,1155) @@ -21806,9 +15532,7 @@
- Issuer of Admission ID - Sequence - + Issuer of Admission ID Sequence (0038,0014) @@ -21819,9 +15543,7 @@
- >Local Namespace - Entity ID - + >Local Namespace Entity ID (0040,0031) @@ -21832,9 +15554,7 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) @@ -21845,9 +15565,7 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) @@ -21858,8 +15576,7 @@
- Service Episode ID - + Service Episode ID (0038,0060) @@ -21870,9 +15587,7 @@
- Issuer of Service - Episode ID Sequence - + Issuer of Service Episode ID Sequence (0038,0064) @@ -21883,9 +15598,7 @@
- >Local Namespace - Entity ID - + >Local Namespace Entity ID (0040,0031) @@ -21896,9 +15609,7 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) @@ -21909,9 +15620,7 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) @@ -21922,9 +15631,7 @@
- Service Episode - Description - + Service Episode Description (0038,0062) @@ -21942,9 +15649,7 @@
- Performed Station AE - Title - + Performed Station AE Title (0040,0241) @@ -21955,9 +15660,7 @@
- Performed Station - Name - + Performed Station Name (0040,0242) @@ -21968,8 +15671,7 @@
- Performed Location - + Performed Location (0040,0243) @@ -21980,9 +15682,7 @@
- Performed Procedure - Step Start Date - + Performed Procedure Step Start Date (0040,0244) @@ -21993,9 +15693,7 @@
- Performed Procedure - Step Start Time - + Performed Procedure Step Start Time (0040,0245) @@ -22006,9 +15704,7 @@
- Performed Procedure - Step ID - + Performed Procedure Step ID (0040,0253) @@ -22019,9 +15715,7 @@
- Performed Procedure - Step Status - + Performed Procedure Step Status (0040,0252) @@ -22032,9 +15726,7 @@
- Performed Procedure - Step End Date - + Performed Procedure Step End Date (0040,0250) @@ -22045,9 +15737,7 @@
- Performed Procedure - Step End Time - + Performed Procedure Step End Time (0040,0251) @@ -22058,9 +15748,7 @@
- Performed Procedure - Step Description - + Performed Procedure Step Description (0040,0254) @@ -22071,9 +15759,7 @@
- Performed Procedure - Type Description - + Performed Procedure Type Description (0040,0255) @@ -22084,9 +15770,7 @@
- Procedure Code - Sequence - + Procedure Code Sequence (0008,1032) @@ -22098,17 +15782,14 @@
- >Include - - - +>Include + +
- Comments on the - Performed Procedure Step - + Comments on the Performed Procedure Step (0040,0280) @@ -22119,9 +15800,7 @@
- Performed Procedure - Step Discontinuation Reason Code Sequence - + Performed Procedure Step Discontinuation Reason Code Sequence (0040,0281) @@ -22133,10 +15812,9 @@
- >Include - - - +>Include + +
- Performed Series - Sequence - + Performed Series Sequence (0040,0340) @@ -22161,9 +15837,7 @@
- >Performing - Physician's Name - + >Performing Physician's Name (0008,1050) @@ -22174,8 +15848,7 @@
- >Protocol Name - + >Protocol Name (0018,1030) @@ -22186,8 +15859,7 @@
- >Operators' Name - + >Operators' Name (0008,1070) @@ -22198,9 +15870,7 @@
- >Series Instance - UID - + >Series Instance UID (0020,000E) @@ -22211,9 +15881,7 @@
- >Series - Description - + >Series Description (0008,103E) @@ -22224,8 +15892,7 @@
- >Retrieve AE Title - + >Retrieve AE Title (0008,0054) @@ -22236,9 +15903,7 @@
- >Referenced Image - Sequence - + >Referenced Image Sequence (0008,1140) @@ -22249,9 +15914,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -22262,9 +15925,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -22275,9 +15936,7 @@
- >Referenced - Non-Image Composite SOP Instance Sequence - + >Referenced Non-Image Composite SOP Instance Sequence (0040,0220) @@ -22288,9 +15947,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -22301,9 +15958,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -22315,9 +15970,7 @@
- >All other Attributes of the Performed Series - Sequence - + >All other Attributes of the Performed Series Sequence @@ -22349,9 +16002,7 @@
- Performed Protocol Code - Sequence - + Performed Protocol Code Sequence (0040,0260) @@ -22363,18 +16014,15 @@
- >Include - - - +>Include + +
- All other Attributes of the - + All other Attributes of the
@@ -22489,9 +16087,7 @@ Warning
Response Status
- Requested optional - Attributes are not supported - + Requested optional Attributes are not supported 0001 @@ -22504,102 +16100,55 @@
Modality Performed Procedure Step Retrieve SOP Class UID - The Modality Performed Procedure Step Retrieve - SOP Class shall be uniquely identified by the Modality Performed Procedure Step Retrieve SOP Class - UID that shall have the value "1.2.840.10008.3.1.2.3.4". - + The Modality Performed Procedure Step Retrieve SOP Class shall be uniquely identified by the Modality Performed Procedure Step Retrieve SOP Class UID that shall have the value "1.2.840.10008.3.1.2.3.4".
Conformance Requirements - Implementations providing conformance to the - Modality Performed Procedure Step Retrieve SOP Class shall be conformant as described in the - following sections and shall include within their Conformance Statement information as described - below. - - An implementation may conform to this SOP Class - as an SCU or as an SCP. The Conformance Statement shall be in the format defined in. - + Implementations providing conformance to the Modality Performed Procedure Step Retrieve SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below. + An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to - this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes. - + An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes.
Operations - Any Attributes for which Attribute - Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCU - Operations Statement. The SCU Operations Statement shall be formatted as defined in. - + Any Attributes for which Attribute Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCU Operations Statement. The SCU Operations Statement shall be formatted as defined in .
SCP Conformance - An implementation that is conformant to - this SOP Class as an SCP shall meet conformance requirements for the operations that it - performs. - + An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations that it performs.
Operations - Any Attributes for which Attribute - Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCP - Operations Statement. The SCP Operations Statement shall be formatted as defined in. - + Any Attributes for which Attribute Values may be requested (using the N-GET Service) by the SCU shall be enumerated in the SCP Operations Statement. The SCP Operations Statement shall be formatted as defined in .
Modality Performed Procedure Step Notification SOP Class - The Modality Performed Procedure Step Notification - SOP Class is intended for those Application Entities requiring notifications of Modality Performed - Procedure Step's changes in state. - - An Application Entity may choose to take some - actions based upon a notification or request for information but is in no way required to do so. - + The Modality Performed Procedure Step Notification SOP Class is intended for those Application Entities requiring notifications of Modality Performed Procedure Step's changes in state. + An Application Entity may choose to take some actions based upon a notification or request for information but is in no way required to do so. - For example, in one configuration, an - IS could be responsible for maintaining data related to performed procedure steps. A PACS - reviewing workstation may need to display the images for any study viewed. In order for the - PACS to link the images to the study, a PACS may receive a notification whenever a procedure - step has been performed. In such a configuration the IS is the SCP and the PACS is the SCU. - When the PACS receives this notification, it may link the images and the performed procedure - step to the study within its internal database or may choose to take no action. - + For example, in one configuration, an IS could be responsible for maintaining data related to performed procedure steps. A PACS reviewing workstation may need to display the images for any study viewed. In order for the PACS to link the images to the study, a PACS may receive a notification whenever a procedure step has been performed. In such a configuration the IS is the SCP and the PACS is the SCU. When the PACS receives this notification, it may link the images and the performed procedure step to the study within its internal database or may choose to take no action. - The terms IS and PACS used in the - previous example are provided for clarification purposes only. This document does not define - nor constrain the purpose or role of any IS, PACS or acquisition Application Entity - conforming to this Service Class Specification. - + The terms IS and PACS used in the previous example are provided for clarification purposes only. This document does not define nor constrain the purpose or role of any IS, PACS or acquisition Application Entity conforming to this Service Class Specification.
DIMSE Service Group - - shows the DIMSE-N Services applicable to the Modality Performed Procedure Step IOD under the - Modality Performed Procedure Step Notification SOP Class. - - The DIMSE-N Services and Protocol are specified - in. - + shows the DIMSE-N Services applicable to the Modality Performed Procedure Step IOD under the Modality Performed Procedure Step Notification SOP Class. + The DIMSE-N Services and Protocol are specified in .
DIMSE Service Group Applicable to Modality Performed Procedure Step Notification
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -22620,11 +16169,7 @@
Notifications - The Application Entity that claims conformance - as an SCU to this SOP Class shall be permitted to receive the following notification. The - Application Entity that claims conformance as an SCP to this SOP Class shall be capable of providing - the notifications defined in. - + The Application Entity that claims conformance as an SCU to this SOP Class shall be permitted to receive the following notification. The Application Entity that claims conformance as an SCP to this SOP Class shall be capable of providing the notifications defined in . @@ -22649,9 +16194,7 @@
Performed Procedure Step Notification Event Information
- Performed Procedure Step In - Progress - + Performed Procedure Step In Progress 1 @@ -22662,9 +16205,7 @@
- Performed Procedure Step - Completed - + Performed Procedure Step Completed 2 @@ -22675,9 +16216,7 @@
- Performed Procedure Step - Discontinued - + Performed Procedure Step Discontinued 3 @@ -22688,9 +16227,7 @@
- Performed Procedure Step - Updated - + Performed Procedure Step Updated 4 @@ -22698,16 +16235,12 @@ - An Update event shall not be - used to notify changes in Performed Procedure Step Status (0040,0252). - + An Update event shall not be used to notify changes in Performed Procedure Step Status (0040,0252).
- Performed Procedure Step - Deleted - + Performed Procedure Step Deleted 5 @@ -22719,153 +16252,77 @@
- The Notification Event Information contains - no Attributes, beyond those defined in. An SCU receiving - a Notification and requiring further information may also be an SCU of the Modality Performed - Procedure Step Retrieval SOP Class and may use the Affected SOP Instance UID (0000,1000) to - perform an N-GET of the Modality Performed Procedure Step SOP Instance. - + The Notification Event Information contains no Attributes, beyond those defined in . An SCU receiving a Notification and requiring further information may also be an SCU of the Modality Performed Procedure Step Retrieval SOP Class and may use the Affected SOP Instance UID (0000,1000) to perform an N-GET of the Modality Performed Procedure Step SOP Instance.
Receive Modality Performed Procedure Step Event Notification - This notification allows an SCU to receive - from the SCP an unsolicited notification of a change in a Modality Performed Procedure Step SOP - Instance. These notifications shall be invoked by the SCP through the use of the DIMSE - N-EVENT-REPORT Service used in conjunction with the related Modality Performed Procedure Step - SOP Instance. - - The SCU shall return, via the - N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the - associated request. The SCU shall accept all Attributes included in any notification. This - Service Class Specification places no requirements on what the SCU shall do as a result of - receiving this information. - - The same SOP Instance UID is shared by all - three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created - and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved - using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve - SOP Class. Changes in its state can be notified by using its SOP Instance UID within the request - primitive of the Modality Performed Procedure Step Notification SOP Class. - - The Modality Performed Procedure Step - Notification SOP Instance UID shall not be used to identify a SOP Instance of the Study - Component Service Class. - + This notification allows an SCU to receive from the SCP an unsolicited notification of a change in a Modality Performed Procedure Step SOP Instance. These notifications shall be invoked by the SCP through the use of the DIMSE N-EVENT-REPORT Service used in conjunction with the related Modality Performed Procedure Step SOP Instance. + The SCU shall return, via the N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the associated request. The SCU shall accept all Attributes included in any notification. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information. + The same SOP Instance UID is shared by all three Modality Performed Procedure Step SOP Classes. This means that the SOP Instance created and set using the services of the Modality Performed Procedure Step SOP Class can be retrieved using its SOP Instance UID within the service of the Modality Performed Procedure Step Retrieve SOP Class. Changes in its state can be notified by using its SOP Instance UID within the request primitive of the Modality Performed Procedure Step Notification SOP Class. + The Modality Performed Procedure Step Notification SOP Instance UID shall not be used to identify a SOP Instance of the Study Component Service Class.
Provide Modality Performed Procedure Step Event Notification - These notifications allow an SCU to receive - from the SCP an unsolicited notification of a change in the state of a real-world performed - procedure step. This notification shall be invoked by the SCP through the use of the DIMSE - N-EVENT-REPORT Service used in conjunction with the related Modality Performed Procedure Step - SOP Instance. - - The SCP shall specify in the N-EVENT-REPORT - request primitive the UID of the Modality Performed Procedure Step SOP Instance with which the - event is associated and the Event Type ID. The Affected SOP Class UID specified in the DIMSE - N-EVENT-REPORT request primitive shall be the UID of the Modality Performed Procedure Step - Notification SOP Class. - + These notifications allow an SCU to receive from the SCP an unsolicited notification of a change in the state of a real-world performed procedure step. This notification shall be invoked by the SCP through the use of the DIMSE N-EVENT-REPORT Service used in conjunction with the related Modality Performed Procedure Step SOP Instance. + The SCP shall specify in the N-EVENT-REPORT request primitive the UID of the Modality Performed Procedure Step SOP Instance with which the event is associated and the Event Type ID. The Affected SOP Class UID specified in the DIMSE N-EVENT-REPORT request primitive shall be the UID of the Modality Performed Procedure Step Notification SOP Class. - The encoding of Notification Event - Information is defined in. - + The encoding of Notification Event Information is defined in .
Status Codes - There are no specific status codes. See - - for response status codes. - + There are no specific status codes. See for response status codes.
Modality Performed Procedure Step Notification SOP Class UID - The Modality Performed Procedure Step - Notification SOP Class shall be uniquely identified by the Modality Performed Procedure Step - Notification SOP Class UID that shall have the value "1.2.840.10008.3.1.2.3.5". - + The Modality Performed Procedure Step Notification SOP Class shall be uniquely identified by the Modality Performed Procedure Step Notification SOP Class UID that shall have the value "1.2.840.10008.3.1.2.3.5".
Conformance Requirements - Implementations providing Standard SOP Class - Conformance to the Modality Performed Procedure Step Notification SOP Class shall be conformant as - described in the following sections and shall include within their Conformance Statement information - as described in the following sections. - - An implementation may conform to this SOP Class - as an SCU, SCP or both. The Conformance Statement shall be in the format defined in. - + Implementations providing Standard SOP Class Conformance to the Modality Performed Procedure Step Notification SOP Class shall be conformant as described in the following sections and shall include within their Conformance Statement information as described in the following sections. + An implementation may conform to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to - this SOP Class as an SCU shall meet conformance requirements for the: - + An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for the: - notifications that it receives - + notifications that it receives
Notifications - All standard event types for which - notifications may be requested by the SCU shall be enumerated in the SCU Notifications - Statement. The SCU Notifications Statement shall include an enumerated list of the event - types supported: - + All standard event types for which notifications may be requested by the SCU shall be enumerated in the SCU Notifications Statement. The SCU Notifications Statement shall include an enumerated list of the event types supported: - Performed Procedure Step In - Progress - + Performed Procedure Step In Progress - Performed Procedure Step - Completed - + Performed Procedure Step Completed - Performed Procedure Step - Discontinued - + Performed Procedure Step Discontinued - Performed Procedure Step - Updated - + Performed Procedure Step Updated - Performed Procedure Step - Deleted - + Performed Procedure Step Deleted
SCP Conformance - An implementation that is conformant to - this SOP Class as an SCP shall meet conformance requirements for: - + An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for: - notifications that it invokes - + notifications that it invokes
Notifications - Any optional Attributes that may be - included in Standard notifications to the SCU shall be enumerated in the SCP Notifications - Statement. The SCP Notifications Statement shall be formatted as defined in. Following - this statement shall be the list of event types and optional Attributes. - + Any optional Attributes that may be included in Standard notifications to the SCU shall be enumerated in the SCP Notifications Statement. The SCP Notifications Statement shall be formatted as defined in . Following this statement shall be the list of event types and optional Attributes.
@@ -22887,19 +16344,9 @@ Print Management Service Class (Normative)
Scope - The Print Management Service Class defines an - application-level class-of-service that facilitates the printing of images and image related data on a - hard copy medium. - + The Print Management Service Class defines an application-level class-of-service that facilitates the printing of images and image related data on a hard copy medium. - The DICOM Print Management Service Class covers - the general cases of printing medical images in standardized layouts. An application can obtain more - flexible layout, annotation, and formatting either by direct manipulation of the pixel matrices used - in DICOM Print Management, or by utilizing page descriptions written in a page description language - (such as Postscript or PDF) that are communicated to the printing system using commonly available - protocols. These other page descriptions languages are not communicated using DICOM protocols and - their use is outside the scope of the DICOM Standard. - + The DICOM Print Management Service Class covers the general cases of printing medical images in standardized layouts. An application can obtain more flexible layout, annotation, and formatting either by direct manipulation of the pixel matrices used in DICOM Print Management, or by utilizing page descriptions written in a page description language (such as Postscript or PDF) that are communicated to the printing system using commonly available protocols. These other page descriptions languages are not communicated using DICOM protocols and their use is outside the scope of the DICOM Standard.
@@ -22908,22 +16355,17 @@ Print Management Data Flow Model
Global Data Flow Model - The Print Management Data Flow Model () consists of three main processes: - + The Print Management Data Flow Model () consists of three main processes: - Film Session Management process - + Film Session Management process Print process - The Standard uses the word film as a - general name for different types of hard copy media (e.g., photographic film, paper). - + The Standard uses the word film as a general name for different types of hard copy media (e.g., photographic film, paper).
@@ -22936,71 +16378,29 @@
- The Film Session Management process is - responsible for acquiring all the information that is required to print the film session. The - film session is the atomic work package of the Print Management Application and contains one or - more films related in a user defined way (e.g., belonging to the same exam, patient) that are - originated from one host (e.g., workstation, diagnostic modality) and that are printed on one - hard copy printer. - - Each film consists of one or more images - and zero or more film related annotations. An annotation consists of one or more lines of text. - - Each image consists of pixel data and zero - or more overlay planes. The user controls the look of the film by assigning values to print - parameters. - - Print parameters are defined at film - session, film, image and annotation levels. The parameter level determines the scope of - operation of the print parameters (e.g., print parameters of the image level are valid for the - corresponding image). - - The inputs of the Film Session Management - process are: - + The Film Session Management process is responsible for acquiring all the information that is required to print the film session. The film session is the atomic work package of the Print Management Application and contains one or more films related in a user defined way (e.g., belonging to the same exam, patient) that are originated from one host (e.g., workstation, diagnostic modality) and that are printed on one hard copy printer. + Each film consists of one or more images and zero or more film related annotations. An annotation consists of one or more lines of text. + Each image consists of pixel data and zero or more overlay planes. The user controls the look of the film by assigning values to print parameters. + Print parameters are defined at film session, film, image and annotation levels. The parameter level determines the scope of operation of the print parameters (e.g., print parameters of the image level are valid for the corresponding image). + The inputs of the Film Session Management process are: - set of images and image related - data - + set of images and image related data - presentation data that describes - the visual look of the films - + presentation data that describes the visual look of the films - The output of the Film Session Management - process is the Print Job, which contains all the information to print the film session. - - The Print process prints a set of films, - based on the information in the Print Job. The Print process is implementation specific and its - management is beyond the scope of the DICOM Standard. - + The output of the Film Session Management process is the Print Job, which contains all the information to print the film session. + The Print process prints a set of films, based on the information in the Print Job. The Print process is implementation specific and its management is beyond the scope of the DICOM Standard.
Grayscale Transformations - The Print Management Service Class supports - two grayscale transformations and spatial transformations that converts an original image into a - printed image. - - The sequence of spatial transformations - (e.g., magnification and merging of annotation with images) and their relationships with the - grayscale transformations are implementation specific and fall beyond the scope of the DICOM - Standard. - - The sequence of grayscale transformations - is important for achieving consistent image quality because of the non-orthogonal nature of the - different transformations. - - describes the sequence of grayscale transformations. - + The Print Management Service Class supports two grayscale transformations and spatial transformations that converts an original image into a printed image. + The sequence of spatial transformations (e.g., magnification and merging of annotation with images) and their relationships with the grayscale transformations are implementation specific and fall beyond the scope of the DICOM Standard. + The sequence of grayscale transformations is important for achieving consistent image quality because of the non-orthogonal nature of the different transformations. describes the sequence of grayscale transformations. - This section previously described - Modality LUT and VOI LUT transformations in more detail. Since Referenced Print SOP Classes - have been retired, these descriptions no longer apply to the Print Management Service Class. - See PS 3.4-1998. - + This section previously described Modality LUT and VOI LUT transformations in more detail. Since Referenced Print SOP Classes have been retired, these descriptions no longer apply to the Print Management Service Class. See PS 3.4-1998.
@@ -23015,74 +16415,31 @@
Modality and User Specific Transformations - Examples of these transformations are - Modality LUT, Mask Subtraction, and VOI LUT. - - The Modality LUT transforms - manufacturer dependent pixel values into pixel values that are meaningful for the modality - and are manufacturer independent. - - The VOI LUT transforms the modality - pixel values into pixel values that are meaningful for the user or the application. For - example it selects of a range of pixel values to be optimized for display, such as soft - tissue or bone windows in a CT image. - + Examples of these transformations are Modality LUT, Mask Subtraction, and VOI LUT. + The Modality LUT transforms manufacturer dependent pixel values into pixel values that are meaningful for the modality and are manufacturer independent. + The VOI LUT transforms the modality pixel values into pixel values that are meaningful for the user or the application. For example it selects of a range of pixel values to be optimized for display, such as soft tissue or bone windows in a CT image.
Polarity - Polarity specifies whether minimum - input pixel values shall be displayed as black or white. If Polarity (2020,0020) is NORMAL - then the pixels will be displayed as specified by Photometric Interpretation; if Polarity is - REVERSE then the pixels will be displayed with the opposite polarity as specified by - Photometric Interpretation. - - Polarity (2020,0020) is an Attribute of - the Image Box IOD. - + Polarity specifies whether minimum input pixel values shall be displayed as black or white. If Polarity (2020,0020) is NORMAL then the pixels will be displayed as specified by Photometric Interpretation; if Polarity is REVERSE then the pixels will be displayed with the opposite polarity as specified by Photometric Interpretation. + Polarity (2020,0020) is an Attribute of the Image Box IOD.
Presentation LUT - The Presentation LUT transforms the - polarity pixel values into Presentation Values (P-Values), which are meaningful for display - of the images. P-Values are approximately related to human perceptual response. They are - intended to facilitate consistent display with common input for both hardcopy and softcopy - display devices and be independent of the specific class or characteristics of the display - device. It is used to realize image display tailored for specific modalities, applications, - and user preferences - - In the Print Management Service Class, - the Presentation LUT is part of the Presentation LUT IOD. - - Hardcopy devices convert P-Values into - optical density for printing. This conversion depends on desired image D-max and D-min. It - also depends on expected viewing conditions such as lightbox intensity for transparency - films. The conversion to printed density is specified in the Presentation LUT SOP Class. - - If the modality desires to natively - specify P-Values as its output, it can negotiate for support of the Presentation LUT, but - specify a LUT that is an identity function. The identity function informs the display device - that no further translation is necessary. - + The Presentation LUT transforms the polarity pixel values into Presentation Values (P-Values), which are meaningful for display of the images. P-Values are approximately related to human perceptual response. They are intended to facilitate consistent display with common input for both hardcopy and softcopy display devices and be independent of the specific class or characteristics of the display device. It is used to realize image display tailored for specific modalities, applications, and user preferences + In the Print Management Service Class, the Presentation LUT is part of the Presentation LUT IOD. + Hardcopy devices convert P-Values into optical density for printing. This conversion depends on desired image D-max and D-min. It also depends on expected viewing conditions such as lightbox intensity for transparency films. The conversion to printed density is specified in the Presentation LUT SOP Class. + If the modality desires to natively specify P-Values as its output, it can negotiate for support of the Presentation LUT, but specify a LUT that is an identity function. The identity function informs the display device that no further translation is necessary. - Performing this translation in the - printer prevents potential loss of precision (detail) that would occur if this - translation were to be performed on many of the existing 8-bit modalities. - + Performing this translation in the printer prevents potential loss of precision (detail) that would occur if this translation were to be performed on many of the existing 8-bit modalities.
Print Management Service Class Structure - The Print Management Service Class Structure is - shown in. - - The Print Management SCU and Print Management - SCP are peer DICOM Print Management Application Entities. The Application Entity of the Print - Management SCP corresponds with one or more hard copy printers. If the SCP Application Entity - corresponds with multiple printers then the SCP Application Entity selects for each Print Job the - printer where the Print Job will be printed. - + The Print Management Service Class Structure is shown in . + The Print Management SCU and Print Management SCP are peer DICOM Print Management Application Entities. The Application Entity of the Print Management SCP corresponds with one or more hard copy printers. If the SCP Application Entity corresponds with multiple printers then the SCP Application Entity selects for each Print Job the printer where the Print Job will be printed.
Print Management Service Class Structure @@ -23094,32 +16451,15 @@
- The Print Management SCU and Print Management - SCP establish an Association by using the Association Services of the OSI Upper Layer Service. - During Association establishment, the DICOM Print Management Application Entities negotiate the - supported SOP Classes. The negotiation procedure is defined in. - + The Print Management SCU and Print Management SCP establish an Association by using the Association Services of the OSI Upper Layer Service. During Association establishment, the DICOM Print Management Application Entities negotiate the supported SOP Classes. The negotiation procedure is defined in . - - shows alternative configurations for printing images and image related data from one host to - multiple printers. - + shows alternative configurations for printing images and image related data from one host to multiple printers. - Configuration 1: one SCU Application - Entity corresponds with the host and one SCP Application Entity corresponds with multiple - printers. The SCU has no control over the print parameters of each printer and over the - print destination of the Print Job. - + Configuration 1: one SCU Application Entity corresponds with the host and one SCP Application Entity corresponds with multiple printers. The SCU has no control over the print parameters of each printer and over the print destination of the Print Job. - Configuration 2: one SCU Application - Entity corresponds with the host and one Application Entity SCP corresponds with each - printer. The SCU has explicit control over the print parameters of each printer and over the - print destination of the Print Job. Each SCP Application Entity has one Association with the - SCU Application Entity and is identified by its Application Entity title. - + Configuration 2: one SCU Application Entity corresponds with the host and one Application Entity SCP corresponds with each printer. The SCU has explicit control over the print parameters of each printer and over the print destination of the Print Job. Each SCP Application Entity has one Association with the SCU Application Entity and is identified by its Application Entity title. @@ -23136,141 +16476,68 @@
Print Management SOP Classes - The Print Management SCU controls the Print - Process by manipulating the Print Management SOP Classes by means of the DIMSE Services. The Print - Management SOP Classes are managed by the Print Management SCP. - - The Print Management SOP Classes are classified - as follows: - + The Print Management SCU controls the Print Process by manipulating the Print Management SOP Classes by means of the DIMSE Services. The Print Management SOP Classes are managed by the Print Management SCP. + The Print Management SOP Classes are classified as follows: - Content related SOP Classes: these SOP - Classes are an abstraction of the contents of a film (e.g., pixel data, text string). The - content related SOP Classes correspond with the Image related SOP Classes, which are - described in - - of this Part. - + Content related SOP Classes: these SOP Classes are an abstraction of the contents of a film (e.g., pixel data, text string). The content related SOP Classes correspond with the Image related SOP Classes, which are described in of this Part. - Presentation related SOP Classes: these - SOP Classes are an abstraction of the presentation of a film (e.g., layout information) and - are defined by Normalized IODs and Normalized DIMSE-N Services. The presentation related SOP - Classes are defined in - - of this Part. - + Presentation related SOP Classes: these SOP Classes are an abstraction of the presentation of a film (e.g., layout information) and are defined by Normalized IODs and Normalized DIMSE-N Services. The presentation related SOP Classes are defined in of this Part. - Printer related SOP Classes: these SOP - Classes are an abstraction of the printer configuration and status and are defined by - Normalized IODs. The Printer SOP Class is defined in - - of this Part. - + Printer related SOP Classes: these SOP Classes are an abstraction of the printer configuration and status and are defined by Normalized IODs. The Printer SOP Class is defined in of this Part.
Usage Specifications - The building blocks of SOP Classes are Modules - and DIMSE Services. The Modules contain related Attributes, which are Mandatory(M) or Optional (U). - The usage may be different for the SCU and SCP. The usage is specified as a pair of letters: the - former indicating the SCU usage, the latter indicating the SCP usage. - - DIMSE Service Group may be Mandatory (M) or - Optional (U) as specified in Section 5.4 of this Part. - - The meaning and behavior of the usage - specification for Attributes for the Print Management Service Class are: - + The building blocks of SOP Classes are Modules and DIMSE Services. The Modules contain related Attributes, which are Mandatory(M) or Optional (U). The usage may be different for the SCU and SCP. The usage is specified as a pair of letters: the former indicating the SCU usage, the latter indicating the SCP usage. + DIMSE Service Group may be Mandatory (M) or Optional (U) as specified in Section 5.4 of this Part. + The meaning and behavior of the usage specification for Attributes for the Print Management Service Class are: M/M - The SCU shall provide a value for - the Attribute. If the SCU does not supply a value, the SCP shall return a Failure status - ("Missing Attribute," code 0120H). The SCP shall support at least one value of the - Attribute. If the SCP does not support the value specified by the SCU, it shall return a - Failure status ("Invalid Attribute Value," code 0106H). - + The SCU shall provide a value for the Attribute. If the SCU does not supply a value, the SCP shall return a Failure status ("Missing Attribute," code 0120H). The SCP shall support at least one value of the Attribute. If the SCP does not support the value specified by the SCU, it shall return a Failure status ("Invalid Attribute Value," code 0106H). -/M - The SCU's usage of the Attribute is - undefined. The SCP shall support at least one value of the Attribute. - + The SCU's usage of the Attribute is undefined. The SCP shall support at least one value of the Attribute. U/M - The SCU may provide a value for the - Attribute. If the SCP does not support the value specified by the SCU, it shall return - either a Failure status ("Invalid Attribute Value", code 0106H) or return a Warning - status ("Attribute Value out of range", code 0116H). In the case of Warning status, the - SCP will apply the default value as defined in the SCP Conformance Statement. - + The SCU may provide a value for the Attribute. If the SCP does not support the value specified by the SCU, it shall return either a Failure status ("Invalid Attribute Value", code 0106H) or return a Warning status ("Attribute Value out of range", code 0116H). In the case of Warning status, the SCP will apply the default value as defined in the SCP Conformance Statement. U/U - The SCU may provide a value for the - Attribute. If the SCP does not support the value specified by the SCU, but does support - the Attribute, it shall return either a Failure status ("Invalid Attribute Value", code - 0106H) or a Warning status ("Attribute Value out of range", code 0116H). In the case of - Warning status, the SCP will apply the default value as defined in the SCP Conformance - Statement. - - If the SCP does not support the - Attribute specified by the SCU, it shall return either a Failure status ("No such - Attribute", code 0105H) or return a Warning status ("Attribute list error", code 0107H). - In the case of Warning status, the behavior of the SCP is defined in the SCP Conformance - Statement. - + The SCU may provide a value for the Attribute. If the SCP does not support the value specified by the SCU, but does support the Attribute, it shall return either a Failure status ("Invalid Attribute Value", code 0106H) or a Warning status ("Attribute Value out of range", code 0116H). In the case of Warning status, the SCP will apply the default value as defined in the SCP Conformance Statement. + If the SCP does not support the Attribute specified by the SCU, it shall return either a Failure status ("No such Attribute", code 0105H) or return a Warning status ("Attribute list error", code 0107H). In the case of Warning status, the behavior of the SCP is defined in the SCP Conformance Statement. - If the usage type designation is modified by a - "C" (e.g., MC/M) the specification stated above shall be modified to include the requirement that - the Attribute shall be supported if the specified condition is met. - + If the usage type designation is modified by a "C" (e.g., MC/M) the specification stated above shall be modified to include the requirement that the Attribute shall be supported if the specified condition is met.
Status Code Categories - For every operation requested on a SOP Class of - the print management service class, a status code will be returned. These status codes are grouped - into success, warning or failure categories. - + For every operation requested on a SOP Class of the print management service class, a status code will be returned. These status codes are grouped into success, warning or failure categories. - These status codes categories are defined - in: - + These status codes categories are defined in : - Success - indicates that the SCP - performed the requested operation as requested. - + Success - indicates that the SCP performed the requested operation as requested. - Warning - indicates that the SCP - has received the request and will process it. However, immediate processing of the - request, or processing in the way specified by the SCU, may not be possible. The SCP - expects to be able to complete the request without further action by the SCU across the - DICOM interface. The exact behavior of the SCP is described in the Conformance - Statement. - + Warning - indicates that the SCP has received the request and will process it. However, immediate processing of the request, or processing in the way specified by the SCU, may not be possible. The SCP expects to be able to complete the request without further action by the SCU across the DICOM interface. The exact behavior of the SCP is described in the Conformance Statement. - Failure - indicates that the SCP is - unable to perform the request. The request will not be processed unless it is repeated - by the SCU at a later time. The exact behavior of the SCP is described in the - Conformance Statement. - + Failure - indicates that the SCP is unable to perform the request. The request will not be processed unless it is repeated by the SCU at a later time. The exact behavior of the SCP is described in the Conformance Statement. @@ -23280,99 +16547,54 @@ Print Management Conformance
Scope - Print Management conformance is defined in - terms of supported Meta SOP Classes, which correspond with the mandatory functionality, and of - supported optional SOP Classes, which correspond with additional functionality. - - A Meta SOP Class corresponds with a pre-defined - group of SOP Classes. The following Print Management Meta SOP Classes are defined: - + Print Management conformance is defined in terms of supported Meta SOP Classes, which correspond with the mandatory functionality, and of supported optional SOP Classes, which correspond with additional functionality. + A Meta SOP Class corresponds with a pre-defined group of SOP Classes. The following Print Management Meta SOP Classes are defined: - Basic Grayscale Print Management Meta - SOP Class - + Basic Grayscale Print Management Meta SOP Class - Basic Color Print Management Meta SOP - Class - + Basic Color Print Management Meta SOP Class - All SCUs and SCPs of the Print Management - Service Class shall support at least one of the Basic Print Management Meta SOP Classes. - - In addition the other Meta SOP Classes or - optional SOP Classes may be supported. - - The Meta SOP Class level negotiation is used to - define a minimum set of print functions; the SOP Class level negotiation is used to define - additional functions. - - If multiple Meta SOP Classes and one or more - optional SOP Classes are negotiated, the SCP shall support all the optional SOP Classes in - conjunction with all the Meta SOP Classes. - - At association setup, the negotiation process - between the Print Management SCU and SCP shall occur for - + All SCUs and SCPs of the Print Management Service Class shall support at least one of the Basic Print Management Meta SOP Classes. + In addition the other Meta SOP Classes or optional SOP Classes may be supported. + The Meta SOP Class level negotiation is used to define a minimum set of print functions; the SOP Class level negotiation is used to define additional functions. + If multiple Meta SOP Classes and one or more optional SOP Classes are negotiated, the SCP shall support all the optional SOP Classes in conjunction with all the Meta SOP Classes. + At association setup, the negotiation process between the Print Management SCU and SCP shall occur for - one or more of the Meta SOP Classes and - zero or more of the optional SOP Classes specified in; or - + one or more of the Meta SOP Classes and zero or more of the optional SOP Classes specified in ; or - one or more of the Printer, Print Job, - and Printer Configuration Retrieval SOP Classes. - + one or more of the Printer, Print Job, and Printer Configuration Retrieval SOP Classes. - It is possible for an SCP to support - Associations for printing and to also support additional Associations for the sole purpose of - exchanging status information about the printer. - + It is possible for an SCP to support Associations for printing and to also support additional Associations for the sole purpose of exchanging status information about the printer.
Print Management Meta SOP Classes
Description - The Basic Print Management Meta SOP Classes - correspond with the minimum functionality that an implementation of the Print Management Service - Class shall support. The Basic Print Management Meta SOP Classes support the following mandatory - features: - + The Basic Print Management Meta SOP Classes correspond with the minimum functionality that an implementation of the Print Management Service Class shall support. The Basic Print Management Meta SOP Classes support the following mandatory features: - preformatted grayscale images or - preformatted color images; preformatted images are images where annotation, graphics, - overlays are burned in - + preformatted grayscale images or preformatted color images; preformatted images are images where annotation, graphics, overlays are burned in - pre-defined film layouts (image - display formats) - + pre-defined film layouts (image display formats) - basic presentation parameters on - film session, film box and image box level - + basic presentation parameters on film session, film box and image box level basic device management - The optional SOP Classes described in - - may be used with the Basic Print Management Meta SOP Classes. - - The following features are optional for - SCUs and SCPs: - + The optional SOP Classes described in may be used with the Basic Print Management Meta SOP Classes. + The following features are optional for SCUs and SCPs: Film box annotation @@ -23386,9 +16608,7 @@ Meta SOP Class Definitions
Basic Grayscale Print Management Meta SOP Class - The Meta SOP Class is defined by the - following set of supported SOP Classes. - + The Meta SOP Class is defined by the following set of supported SOP Classes. @@ -23407,9 +16627,7 @@
SOP Classes of Basic Grayscale Print Management Meta SOP Class
- Basic Film Session SOP - Class - + Basic Film Session SOP Class @@ -23422,9 +16640,7 @@
- Basic Film Box SOP - Class - + Basic Film Box SOP Class @@ -23437,9 +16653,7 @@
- Basic Grayscale Image - Box SOP Class - + Basic Grayscale Image Box SOP Class @@ -23452,8 +16666,7 @@
- Printer SOP Class - + Printer SOP Class @@ -23467,22 +16680,14 @@
- The image pixel data are part of - the Basic Grayscale Image Box SOP Class - + The image pixel data are part of the Basic Grayscale Image Box SOP Class - The meaning of the Usage SCU/SCP is - described in. - - The Basic Grayscale Print Management - Meta SOP Class UID has the value "1.2.840.10008.5.1.1.9". - + The meaning of the Usage SCU/SCP is described in . + The Basic Grayscale Print Management Meta SOP Class UID has the value "1.2.840.10008.5.1.1.9".
Basic Color Print Management Meta SOP Class - The Meta SOP Class is defined by the - following set of supported SOP Classes. - + The Meta SOP Class is defined by the following set of supported SOP Classes. @@ -23501,9 +16706,7 @@
SOP Classes of Basic Color Print Management Meta SOP Class
- Basic Film Session SOP - Class - + Basic Film Session SOP Class @@ -23516,9 +16719,7 @@
- Basic Film Box SOP - Class - + Basic Film Box SOP Class @@ -23531,9 +16732,7 @@
- Basic Color Image Box - SOP Class - + Basic Color Image Box SOP Class @@ -23546,8 +16745,7 @@
- Printer SOP Class - + Printer SOP Class @@ -23561,34 +16759,22 @@
- The image pixel data are part of - the Basic Color Image Box SOP Class - + The image pixel data are part of the Basic Color Image Box SOP Class - The meaning of the Usage SCU/SCP is - described in. - - The Basic Color Print Management Meta - SOP Class UID has the value "1.2.840.10008.5.1.1.18". - + The meaning of the Usage SCU/SCP is described in . + The Basic Color Print Management Meta SOP Class UID has the value "1.2.840.10008.5.1.1.18".
Referenced Grayscale Print Management Meta SOP Class (Retired) - This section was previously defined in - DICOM. It is now retired. See PS 3.4-1998. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-1998.
Referenced Color Print Management Meta SOP Class (Retired) - This section was previously defined in - DICOM. It is now retired. See PS 3.4-1998. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-1998.
Pull Stored Print Management Meta SOP Class(Retired) - This section was previously defined in - DICOM. It is now retired. See PS 3.4-2004. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-2004.
@@ -23596,47 +16782,27 @@ Optional SOP Classes
Description - The optional SOP Classes address - functionality beyond that of the Print Management Meta SOP Classes. One or more optional SOP - Classes may be used in addition to the Print Management Meta SOP Classes. - - The following functionality is supported by - the optional SOP Classes: - + The optional SOP Classes address functionality beyond that of the Print Management Meta SOP Classes. One or more optional SOP Classes may be used in addition to the Print Management Meta SOP Classes. + The following functionality is supported by the optional SOP Classes: - annotation (text associated with a - sheet of film) - + annotation (text associated with a sheet of film) - tracking the printing of the print - session - + tracking the printing of the print session - retrieval of printer configuration - information - + retrieval of printer configuration information Presentation LUTs - Use of these optional SOP Classes allows an - SCU to provide information to be printed with or on an image without burning the information - into the image pixels. If these optional SOP Classes are not supported by both the SCU and SCP, - then only the information burnt in to the image pixels before they are sent to the SCP will be - printed. If the optional SOP Classes are not supported, the SCU is responsible for burning all - expected text or graphics into the image pixels. - + Use of these optional SOP Classes allows an SCU to provide information to be printed with or on an image without burning the information into the image pixels. If these optional SOP Classes are not supported by both the SCU and SCP, then only the information burnt in to the image pixels before they are sent to the SCP will be printed. If the optional SOP Classes are not supported, the SCU is responsible for burning all expected text or graphics into the image pixels.
List of Optional SOP Classes - The following optional SOP Classes may be - used in conjunction with the Basic Print Management Meta SOP Classes specified in. - + The following optional SOP Classes may be used in conjunction with the Basic Print Management Meta SOP Classes specified in . @@ -23655,9 +16821,7 @@
List of Optional SOP Classes for Basic Print Management Meta SOP Classes
- Basic Annotation Box SOP - Class - + Basic Annotation Box SOP Class @@ -23683,9 +16847,7 @@
- Presentation LUT SOP - Class - + Presentation LUT SOP Class @@ -23698,9 +16860,7 @@
- Printer Configuration - Retrieval SOP Class - + Printer Configuration Retrieval SOP Class @@ -23714,133 +16874,80 @@
- Negotiation of the Presentation LUT SOP - Class does not imply any behavior in the SCP. Behavior is explicit when the Presentation LUT - SOP Class is created and referenced at either the Film Session, Film Box, or Image Box - levels. - + Negotiation of the Presentation LUT SOP Class does not imply any behavior in the SCP. Behavior is explicit when the Presentation LUT SOP Class is created and referenced at either the Film Session, Film Box, or Image Box levels.
Conformance Statement - The implementation Conformance Statement of - these SOP Classes shall follow. - - The SCU Conformance Statement shall specify the - following items: - + The implementation Conformance Statement of these SOP Classes shall follow . + The SCU Conformance Statement shall specify the following items: - maximum number of supported - Associations at the same time - + maximum number of supported Associations at the same time - list of supported SOP Classes and Meta - SOP Classes - + list of supported SOP Classes and Meta SOP Classes - for each of the supported SOP and Meta - SOP Classes: - + for each of the supported SOP and Meta SOP Classes: - list of supported optional SOP Class - Attributes and DICOM Message Service Elements - + list of supported optional SOP Class Attributes and DICOM Message Service Elements - for each supported Attribute (mandatory - and optional Attribute), the valid range of values - + for each supported Attribute (mandatory and optional Attribute), the valid range of values - The SCP Conformance Statement shall specify the - following items: - + The SCP Conformance Statement shall specify the following items: - maximum number of supported - Associations at the same time - + maximum number of supported Associations at the same time - list of supported SOP Classes and Meta - SOP Classes - + list of supported SOP Classes and Meta SOP Classes - minimum and maximum number of printable - pixel matrix per supported film size - + minimum and maximum number of printable pixel matrix per supported film size - for each of the supported SOP - Classes: - + for each of the supported SOP Classes: - list of supported optional SOP Class - Attributes and DICOM Message Service Elements - + list of supported optional SOP Class Attributes and DICOM Message Service Elements - for each supported Attribute (mandatory - and optional Attribute): - + for each supported Attribute (mandatory and optional Attribute): valid range of values - default value if no value is supplied - by the SCU - + default value if no value is supplied by the SCU - status code (Failure or Warning) if SCU - supplies a value that is out of range - + status code (Failure or Warning) if SCU supplies a value that is out of range - for each supported DIMSE Service, the - SCP behavior for all specific status codes - + for each supported DIMSE Service, the SCP behavior for all specific status codes - description of each supported custom - Image Display Format (2010,0010) e.g., position and dimensions of each composing image box, - numbering scheme of the image positions - + description of each supported custom Image Display Format (2010,0010) e.g., position and dimensions of each composing image box, numbering scheme of the image positions - description of each supported - Annotation Display Format ID (2010,0030) e.g., position and dimensions of annotation box, - font, number of characters - + description of each supported Annotation Display Format ID (2010,0030) e.g., position and dimensions of annotation box, font, number of characters - description of each supported - configuration table (e.g., identification, content) - + description of each supported configuration table (e.g., identification, content) - if the SCP supports N-ACTION for the - Film Session SOP Class then the SCP shall specify the maximum number of collated films - + if the SCP supports N-ACTION for the Film Session SOP Class then the SCP shall specify the maximum number of collated films - in the case of grayscale printers that - print color images, the behavior of printing color images - + in the case of grayscale printers that print color images, the behavior of printing color images - if cropping of images is supported, the - algorithm for removing rows and columns from the image - + if cropping of images is supported, the algorithm for removing rows and columns from the image
@@ -23851,27 +16958,18 @@ Basic Film Session SOP Class
IOD Description - The Basic Film Session IOD describes the - presentation parameters that are common for all the films of a film session (e.g., number of - films, film destination) - - The Basic Film Session SOP Instance refers - to one or more Basic Film Box SOP Instances. - + The Basic Film Session IOD describes the presentation parameters that are common for all the films of a film session (e.g., number of films, film destination) + The Basic Film Session SOP Instance refers to one or more Basic Film Box SOP Instances.
DIMSE Service Group - The DIMSE Services applicable to the IOD - are shown in. - + The DIMSE Services applicable to the IOD are shown in .
DIMSE Service Group Applicable to Basic Film Session
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -23913,46 +17011,33 @@
- The meaning of the Usage SCU/SCP is - described in. - - This Section describes the behavior of the - DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is - specified in. - + The meaning of the Usage SCU/SCP is described in . + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-CREATE - The N-CREATE is used to create an - instance of the Basic Film Session SOP Class. - + The N-CREATE is used to create an instance of the Basic Film Session SOP Class.
Attributes - The Attribute list of the N-CREATE - is defined as shown in. - + The Attribute list of the N-CREATE is defined as shown in .
N-CREATE Attribute List
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -23963,8 +17048,7 @@
- Number of Copies - + Number of Copies (2000,0010) @@ -23975,8 +17059,7 @@
- Print Priority - + Print Priority (2000,0020) @@ -23998,8 +17081,7 @@
- Film Destination - + Film Destination (2000,0040) @@ -24010,9 +17092,7 @@
- Film Session - Label - + Film Session Label (2000,0050) @@ -24023,8 +17103,7 @@
- Memory Allocation - + Memory Allocation (2000,0060) @@ -24046,9 +17125,7 @@
- Proposed Study - Sequence - + Proposed Study Sequence (2130,00A0) @@ -24059,9 +17136,7 @@
- >Patient's - Name - + >Patient's Name (0010,0010) @@ -24072,8 +17147,7 @@
- >Patient ID - + >Patient ID (0010,0020) @@ -24084,9 +17158,7 @@
- >Patient's Birth - Date - + >Patient's Birth Date (0010,0030) @@ -24097,9 +17169,7 @@
- >Patient's Birth - Time - + >Patient's Birth Time (0010,0032) @@ -24110,8 +17180,7 @@
- >Patient's Sex - + >Patient's Sex (0010,0040) @@ -24122,8 +17191,7 @@
- >Patient's Age - + >Patient's Age (0010,1010) @@ -24134,9 +17202,7 @@
- >Other Patient - ID - + >Other Patient ID (0010,1000) @@ -24147,9 +17213,7 @@
- >Other Patient - Names - + >Other Patient Names (0010,1001) @@ -24160,8 +17224,7 @@
- >Ethnic Group - + >Ethnic Group (0010,2160) @@ -24172,9 +17235,7 @@
- >Patient - Comments - + >Patient Comments (0010,4000) @@ -24185,9 +17246,7 @@
- >Study Instance - UID - + >Study Instance UID (0020,000D) @@ -24198,8 +17257,7 @@
- >Study Date - + >Study Date (0008,0020) @@ -24210,8 +17268,7 @@
- >Study Time - + >Study Time (0008,0030) @@ -24233,9 +17290,7 @@
- >Study - Description - + >Study Description (0008,1030) @@ -24246,9 +17301,7 @@
- >Accession - Number - + >Accession Number (0008,0050) @@ -24259,9 +17312,7 @@
- >Referring - Physician’s Name - + >Referring Physician’s Name (0008,0090) @@ -24272,9 +17323,7 @@
- >Name of - Physician(s) Reading Study - + >Name of Physician(s) Reading Study (0008,1060) @@ -24285,9 +17334,7 @@
- >Admitting - Diagnoses Description - + >Admitting Diagnoses Description (0008,1080) @@ -24298,8 +17345,7 @@
- >Series Number - + >Series Number (0020,0011) @@ -24313,48 +17359,29 @@ - The memory allocation - Attribute allows the SCU to reserve sufficient memory to store the "working" - film session hierarchy as well the "copied" film session hierarchy in the - Print Job in order to prevent deadlock situations. - + The memory allocation Attribute allows the SCU to reserve sufficient memory to store the "working" film session hierarchy as well the "copied" film session hierarchy in the Print Job in order to prevent deadlock situations. - Owner ID (2100,0160) is - a user option for the Basic Film Session. - + Owner ID (2100,0160) is a user option for the Basic Film Session. - The meaning of the Usage SCU/SCP is - described in. - - Within the film session, the - allocated memory is consumed as SOP Instances are created and is freed for reuse as SOP - Instances are deleted. All the allocated memory shall be released following termination - of the Association or deletion of the Film Session SOP Instance. - + The meaning of the Usage SCU/SCP is described in . + Within the film session, the allocated memory is consumed as SOP Instances are created and is freed for reuse as SOP Instances are deleted. All the allocated memory shall be released following termination of the Association or deletion of the Film Session SOP Instance.
Status - - defines the specific status code values that may be returned in a N-CREATE or N-SET - response for this SOP Class. See - - for additional response status codes of N-CREATE and N-SET DIMSE Services. - + defines the specific status code values that may be returned in a N-CREATE or N-SET response for this SOP Class. See for additional response status codes of N-CREATE and N-SET DIMSE Services.
Status Values for Basic Film Session SOP Class
- Service Status - + Service Status - Further Meaning - + Further Meaning Status Code @@ -24367,9 +17394,7 @@ Success - Film session - successfully created - + Film session successfully created 0000 @@ -24380,9 +17405,7 @@ Warning - Memory allocation - not supported - + Memory allocation not supported B600 @@ -24391,180 +17414,90 @@
- The status code "0106H" - (Invalid Attribute Value) indicates that the requested memory allocation can not be - provided; the status code "0213H" (Resource limitation) indicates that the requested - allocation can temporarily not be provided. - + The status code "0106H" (Invalid Attribute Value) indicates that the requested memory allocation can not be provided; the status code "0213H" (Resource limitation) indicates that the requested allocation can temporarily not be provided.
Behavior - The SCU uses the N-CREATE to - request the SCP to create a Basic Film Session SOP Instance. The SCU shall initialize - Attributes of the SOP Class as specified in. - - The SCP shall create the SOP - Instance and shall initialize Attributes of the SOP Class as specified in. - - The SCP shall return the status - code of the requested SOP Instance creation. The meaning of success, warning, and - failure status codes is defined in - . - - The Basic Film Session SOP - Instances shall be created before the Film Box SOP Instances are created. - - At any time the SCU/SCP shall only - support one Basic Film Session SOP Instance on an Association. - + The SCU uses the N-CREATE to request the SCP to create a Basic Film Session SOP Instance. The SCU shall initialize Attributes of the SOP Class as specified in . + The SCP shall create the SOP Instance and shall initialize Attributes of the SOP Class as specified in . + The SCP shall return the status code of the requested SOP Instance creation. The meaning of success, warning, and failure status codes is defined in . + The Basic Film Session SOP Instances shall be created before the Film Box SOP Instances are created. + At any time the SCU/SCP shall only support one Basic Film Session SOP Instance on an Association. - Multiple film sessions may be - handled by establishing multiple Associations. - + Multiple film sessions may be handled by establishing multiple Associations. - Terminating the Association will - effectively perform an N-DELETE on an opened film session. See Note in. - + Terminating the Association will effectively perform an N-DELETE on an opened film session. See Note in .
N-SET - The N-SET may be used to update an - instance of the Basic Film Session SOP Class. - + The N-SET may be used to update an instance of the Basic Film Session SOP Class.
Attributes - All Attributes and usage in - - apply to N-SET. - + All Attributes and usage in apply to N-SET.
Status - The status values that are specific - for this SOP Class are defined in. - + The status values that are specific for this SOP Class are defined in .
Behavior - The SCU uses the N-SET to request - the SCP to update a Basic Film Session SOP Instance. The SCU shall specify the SOP - Instance UID to be updated and shall specify the list of Attributes for which the - Attribute Values are to be set. - - The SCP shall set new values for - the specified Attributes of the specified SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance update. The meaning of success, warning, and failure - status codes is defined in - + The SCU uses the N-SET to request the SCP to update a Basic Film Session SOP Instance. The SCU shall specify the SOP Instance UID to be updated and shall specify the list of Attributes for which the Attribute Values are to be set. + The SCP shall set new values for the specified Attributes of the specified SOP Instance. + The SCP shall return the status code of the requested SOP Instance update. The meaning of success, warning, and failure status codes is defined in
N-DELETE - The N-DELETE is used to delete the - complete Basic Film Session SOP Instance hierarchy. As a result, all references to Image SOP - Instances within the film session are deleted. - - The Basic Film Session SOP Instance - hierarchy consists of one Basic Film Session SOP Instance, one or more Basic Film Box SOP - Instances, one or more Image Box SOP Instances, zero or more Basic Annotation Box SOP - Instances, zero or more Presentation LUT SOP Instances, and zero or more Basic Print Image - Overlay Box SOP instances. - + The N-DELETE is used to delete the complete Basic Film Session SOP Instance hierarchy. As a result, all references to Image SOP Instances within the film session are deleted. + The Basic Film Session SOP Instance hierarchy consists of one Basic Film Session SOP Instance, one or more Basic Film Box SOP Instances, one or more Image Box SOP Instances, zero or more Basic Annotation Box SOP Instances, zero or more Presentation LUT SOP Instances, and zero or more Basic Print Image Overlay Box SOP instances. - The Basic Film Session SOP Instance - hierarchy can be visualized as a reversed tree with the Basic Film Session SOP Instance - as the root and the Image Box SOP Instances as the leaves. - + The Basic Film Session SOP Instance hierarchy can be visualized as a reversed tree with the Basic Film Session SOP Instance as the root and the Image Box SOP Instances as the leaves.
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
Behavior - The SCU uses the N-DELETE to - request the SCP to delete the Basic Film Session SOP Instance hierarchy. The SCU shall - specify in the N-DELETE request primitive of the SOP Instance UID of the Basic Film - Session (root). - - The SCP shall delete the specified - SOP Instance hierarchy. - - The SCP shall not delete SOP - Instances in the hierarchy as long as there are outstanding references to these SOP - Instances - + The SCU uses the N-DELETE to request the SCP to delete the Basic Film Session SOP Instance hierarchy. The SCU shall specify in the N-DELETE request primitive of the SOP Instance UID of the Basic Film Session (root). + The SCP shall delete the specified SOP Instance hierarchy. + The SCP shall not delete SOP Instances in the hierarchy as long as there are outstanding references to these SOP Instances - It is beyond the scope of the - Standard to specify when the SCP actually deletes SOP Instances with outstanding - references. - + It is beyond the scope of the Standard to specify when the SCP actually deletes SOP Instances with outstanding references. - The SCP shall return the status - code of the requested SOP Instance deletion. The meaning of success, warning, and - failure status codes is defined in - . - + The SCP shall return the status code of the requested SOP Instance deletion. The meaning of success, warning, and failure status codes is defined in .
N-ACTION - The N-ACTION is used to print the film - session; i.e., to print all the films that belong to the film session. - - If multiple copies of the film session - have been requested, the SCP shall collate the copies. This means that if two copies of four - films has been specified, the printed sequence is 12341234. - + The N-ACTION is used to print the film session; i.e., to print all the films that belong to the film session. + If multiple copies of the film session have been requested, the SCP shall collate the copies. This means that if two copies of four films has been specified, the printed sequence is 12341234.
Attributes - The arguments of the N-ACTION are - defined in. - - The Action Reply argument is - encoded as a DICOM Data Set. The Data Set only contains the Attribute Referenced Print - Job Sequence (2100,0500), which includes the Referenced SOP Class UID (0008,1150) and - the Referenced SOP Instance UID (0008,1155). - - If the SCP supports the Print Job - SOP Class, the Action Reply argument is contained in the N-ACTION response. Otherwise, - the Action Reply is not contained in the N-ACTION response. - + The arguments of the N-ACTION are defined in . + The Action Reply argument is encoded as a DICOM Data Set. The Data Set only contains the Attribute Referenced Print Job Sequence (2100,0500), which includes the Referenced SOP Class UID (0008,1150) and the Referenced SOP Instance UID (0008,1155). + If the SCP supports the Print Job SOP Class, the Action Reply argument is contained in the N-ACTION response. Otherwise, the Action Reply is not contained in the N-ACTION response. @@ -24577,54 +17510,42 @@ 1 @@ -24633,22 +17554,16 @@
Status - defines the specific status code - values that may be returned in a N-ACTION response. See - - for additional response status codes. - + defines the specific status code values that may be returned in a N-ACTION response. See for additional response status codes.
N-ACTION Arguments
- Action Type Name - + Action Type Name - Action Type ID - + Action Type ID - Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Referenced Print - Job Sequence - + Referenced Print Job Sequence (2100,0500) -/MC - Required if Print - Job SOP is supported - + Required if Print Job SOP is supported
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) -/MC - Required if - Referenced Print Job Sequence (2100,0500) is present - + Required if Referenced Print Job Sequence (2100,0500) is present
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) -/MC - Required if - Referenced Print Job Sequence (2100,0500) is present - + Required if Referenced Print Job Sequence (2100,0500) is present
SOP Class Status Values
- Service Status - + Service Status - Further Meaning - + Further Meaning Status Code @@ -24661,10 +17576,7 @@ Success - Film belonging to - the film session are accepted for printing; if supported, the Print Job - SOP Instance is created - + Film belonging to the film session are accepted for printing; if supported, the Print Job SOP Instance is created 0000 @@ -24675,9 +17587,7 @@ Warning - Film session - printing (collation) is not supported - + Film session printing (collation) is not supported B601 @@ -24685,9 +17595,7 @@
- Film Session SOP - Instance hierarchy does not contain Image Box SOP Instances (empty page) - + Film Session SOP Instance hierarchy does not contain Image Box SOP Instances (empty page) B602 @@ -24695,9 +17603,7 @@
- Image size is - larger than image box size, the image has been demagnified. - + Image size is larger than image box size, the image has been demagnified. B604 @@ -24705,9 +17611,7 @@
- Image size is - larger than the Image Box size. The Image has been cropped to fit. - + Image size is larger than the Image Box size. The Image has been cropped to fit. B609 @@ -24715,10 +17619,7 @@
- Image size or - Combined Print Image size is larger than the Image Box size. Image or - Combined Print Image has been decimated to fit. - + Image size or Combined Print Image size is larger than the Image Box size. Image or Combined Print Image has been decimated to fit. B60A @@ -24729,9 +17630,7 @@ Failure - Failed: Film - Session SOP Instance hierarchy does not contain Film Box SOP Instances - + Failed: Film Session SOP Instance hierarchy does not contain Film Box SOP Instances C600 @@ -24739,9 +17638,7 @@
- Failed: Unable to - create Print Job SOP Instance; print queue is full - + Failed: Unable to create Print Job SOP Instance; print queue is full C601 @@ -24749,9 +17646,7 @@
- Failed: Image size - is larger than image box size - + Failed: Image size is larger than image box size C603 @@ -24759,9 +17654,7 @@
- Failed: Combined - Print Image size is larger than the Image Box size - + Failed: Combined Print Image size is larger than the Image Box size C613 @@ -24770,81 +17663,44 @@
- Previous versions of the DICOM - Standard defined the status code of C604. This code was specified for the case of an - image position collision. Since image position collision is not a possible state, - the code has been retired. - + Previous versions of the DICOM Standard defined the status code of C604. This code was specified for the case of an image position collision. Since image position collision is not a possible state, the code has been retired.
Behavior - The SCU uses the N-ACTION to - request the SCP to print all the films belonging to the identified film session. - - The SCP shall make a copy of the - "working" Basic Film Session SOP Instance hierarchy, which contains all the information - to control the Print Process. Hence the SCU may further update the "working" SOP - Instance hierarchy without affecting the result of previous print requests. The - execution of the Print Process is monitored by the Print Job SOP Instance (if supported - by the SCP) and the Printer SOP Class. - - If the SCP supports the Print Job - SOP Class then the SCP shall create a Print Job SOP Instance, which contains the copy of - the "working" Basic Film Session SOP Instance hierarchy and shall return the Print Job - SOP Class/Instance UID pair in the Attribute Referenced Print Job Sequence of the Action - Reply argument. - + The SCU uses the N-ACTION to request the SCP to print all the films belonging to the identified film session. + The SCP shall make a copy of the "working" Basic Film Session SOP Instance hierarchy, which contains all the information to control the Print Process. Hence the SCU may further update the "working" SOP Instance hierarchy without affecting the result of previous print requests. The execution of the Print Process is monitored by the Print Job SOP Instance (if supported by the SCP) and the Printer SOP Class. + If the SCP supports the Print Job SOP Class then the SCP shall create a Print Job SOP Instance, which contains the copy of the "working" Basic Film Session SOP Instance hierarchy and shall return the Print Job SOP Class/Instance UID pair in the Attribute Referenced Print Job Sequence of the Action Reply argument. - If the SCP supports the Print - Job SOP Class, it creates a single Print Job for all the films of the film session. - + If the SCP supports the Print Job SOP Class, it creates a single Print Job for all the films of the film session. - The SCP shall return the status - code of the requested operation. The meaning of success, warning, and failure status - codes is defined in. - - The N-ACTION shall be issued only - if the Basic Film Session SOP Instance hierarchy contains at least one Film Box SOP - Instance. - + The SCP shall return the status code of the requested operation. The meaning of success, warning, and failure status codes is defined in . + The N-ACTION shall be issued only if the Basic Film Session SOP Instance hierarchy contains at least one Film Box SOP Instance.
SOP Class Definition and UID - The Basic Film Session SOP Class UID shall - have the value "1.2.840.10008.5.1.1.1". - + The Basic Film Session SOP Class UID shall have the value "1.2.840.10008.5.1.1.1".
Basic Film Box SOP Class
IOD Description - The Basic Film Box IOD is an abstraction of - the presentation of one film of the film session. The Basic Film Box IOD describes the - presentation parameters that are common for all images on a given sheet of film. - - The Basic Film Box SOP Instance refers to - one or more Image Box SOP Instances, zero or more film related Annotation Box SOP Instances, and - zero or one Presentation LUT SOP Instance. - + The Basic Film Box IOD is an abstraction of the presentation of one film of the film session. The Basic Film Box IOD describes the presentation parameters that are common for all images on a given sheet of film. + The Basic Film Box SOP Instance refers to one or more Image Box SOP Instances, zero or more film related Annotation Box SOP Instances, and zero or one Presentation LUT SOP Instance.
DIMSE Service Group - - shows DIMSE Services applicable to the IOD. - + shows DIMSE Services applicable to the IOD.
DIMSE Service Group Applicable to Basic Film Box
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -24886,46 +17742,33 @@
- The meaning of the Usage SCU/SCP is - described in. - - This Section describes the behavior of the - DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is - specified in. - + The meaning of the Usage SCU/SCP is described in . + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-CREATE - The N-CREATE is used to create an - instance of the Basic Film Box SOP Class. - + The N-CREATE is used to create an instance of the Basic Film Box SOP Class.
Attributes - The Attribute list of the N-CREATE - is shown in. - + The Attribute list of the N-CREATE is shown in .
N-CREATE Attribute List
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Image Display - Format - + Image Display Format (2010,0010) @@ -24936,9 +17779,7 @@
- Referenced Film - Session Sequence - + Referenced Film Session Sequence (2010,0500) @@ -24949,9 +17790,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -24962,9 +17801,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -24975,9 +17812,7 @@
- Referenced Image - Box Sequence - + Referenced Image Box Sequence (2010,0510) @@ -24988,9 +17823,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -25001,9 +17834,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -25014,56 +17845,43 @@
- Referenced Basic - Annotation Box Sequence - + Referenced Basic Annotation Box Sequence (2010,0520) -/MC - (Required if - optional Annotation SOP was negotiated) - + (Required if optional Annotation SOP was negotiated)
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) -/MC - (Required if - sequence is present) - + (Required if sequence is present)
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) -/MC - (Required if - sequence is present) - + (Required if sequence is present)
- Film Orientation - + Film Orientation (2010,0040) @@ -25085,9 +17903,7 @@
- Magnification - Type - + Magnification Type (2010,0060) @@ -25109,9 +17925,7 @@
- Configuration - Information - + Configuration Information (2010,0150) @@ -25122,57 +17936,43 @@
- Referenced - Presentation LUT Sequence - + Referenced Presentation LUT Sequence (2050,0500) U/MC - (Required if - Presentation LUT is supported) - + (Required if Presentation LUT is supported)
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) U/MC - (Required if - sequence is present) - + (Required if sequence is present)
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) U/MC - (Required if - sequence is present) - + (Required if sequence is present)
- Annotation Display - Format ID - + Annotation Display Format ID (2010,0030) @@ -25183,8 +17983,7 @@
- Smoothing Type - + Smoothing Type (2010,0080) @@ -25195,8 +17994,7 @@
- Border Density - + Border Density (2010,0100) @@ -25207,9 +18005,7 @@
- Empty Image - Density - + Empty Image Density (2010,0110) @@ -25249,32 +18045,24 @@ U/MC - (Required if - Presentation LUT is supported) - + (Required if Presentation LUT is supported)
- Reflected Ambient - Light - + Reflected Ambient Light (2010,0160) U/MC - (Required if - Presentation LUT is supported) - + (Required if Presentation LUT is supported)
- Requested - Resolution ID - + Requested Resolution ID (2020,0050) @@ -25296,51 +18084,31 @@
- The meaning of the Usage SCU/SCP is - described in. - - If the Illumination (2010,015E) and - Reflected Ambient Light (2010,0160) values, respectively termed L0 and La, are not - created, the following default values are recommended for grayscale printing: - + The meaning of the Usage SCU/SCP is described in . + If the Illumination (2010,015E) and Reflected Ambient Light (2010,0160) values, respectively termed L0 and La, are not created, the following default values are recommended for grayscale printing: - For transmissive film: L0 = - 2000 cd/m2. La = 10 cd/m2. - + For transmissive film: L0 = 2000 cd/m2. La = 10 cd/m2. - For reflective media: L0 = - 150 cd/m2. - + For reflective media: L0 = 150 cd/m2. - The ICC Profile (0028,2000) - Attribute shall only be used to describe the color space of images for color printing, - i.e., in conjunction with the Basic Color Image Box SOP Class. It shall not be used with - the Basic Grayscale Image Box SOP Class. - + The ICC Profile (0028,2000) Attribute shall only be used to describe the color space of images for color printing, i.e., in conjunction with the Basic Color Image Box SOP Class. It shall not be used with the Basic Grayscale Image Box SOP Class.
Status - - defines the specific status code values that may be returned in a N-CREATE or N-SET - response for this SOP Class. See - - for additional response status codes of N-CREATE and N-SET DIMSE Services. - + defines the specific status code values that may be returned in a N-CREATE or N-SET response for this SOP Class. See for additional response status codes of N-CREATE and N-SET DIMSE Services.
Status Values for Basic Film Box SOP Class
- Service Status - + Service Status - Further Meaning - + Further Meaning Status Code @@ -25353,9 +18121,7 @@ Success - Film Box - successfully created - + Film Box successfully created 0000 @@ -25366,10 +18132,7 @@ Warning - Requested Min - Density or Max Density outside of printer's operating range. The printer - will use its respective minimum or maximum density value instead. - + Requested Min Density or Max Density outside of printer's operating range. The printer will use its respective minimum or maximum density value instead. B605 @@ -25380,11 +18143,7 @@ Failure - Failed: There is an - existing Film Box that has not been printed and N-ACTION at the Film - Session level is not supported. A new Film Box will not be created when - a previous Film Box has not been printed. - + Failed: There is an existing Film Box that has not been printed and N-ACTION at the Film Session level is not supported. A new Film Box will not be created when a previous Film Box has not been printed. C616 @@ -25395,95 +18154,44 @@
Behavior - The SCU uses the N-CREATE to - request the SCP to create a Basic Film Box SOP Instance. The SCU shall initialize - Attributes of the SOP Class as specified in. - - The SCP shall create the SOP - Instance and shall initialize Attributes of the SOP Class as specified in. - + The SCU uses the N-CREATE to request the SCP to create a Basic Film Box SOP Instance. The SCU shall initialize Attributes of the SOP Class as specified in . + The SCP shall create the SOP Instance and shall initialize Attributes of the SOP Class as specified in . - If there exists a Film Box SOP - Instance that has not been printed and the SCP does not support N-ACTION on the Film - Session, then the SCP should fail the N-CREATE of the new SOP Instance. - + If there exists a Film Box SOP Instance that has not been printed and the SCP does not support N-ACTION on the Film Session, then the SCP should fail the N-CREATE of the new SOP Instance. - Upon the creation of the Basic Film - Box SOP Instance, the SCP shall append the SOP Class/Instance UID pair of the created - Basic Film Box SOP Instance to the Attribute Referenced Film Box Sequence (2000,0500) of - the parent Basic Film Session SOP Instance to link the Basic Film Box SOP Instance to - the Basic Film Session SOP Instance. - - The SCP shall create Image Box SOP - Instances of the appropriate Image Box SOP Class for each image box as defined by the - Attribute Image Display Format (2010,0010). The SOP Class of the created Image Box SOP - Instance depends on the Meta SOP Class context. For example the Grayscale Image Box SOP - Class is related to the Basic Grayscale Print Management Meta SOP Class. The Meta SOP - Class context is conveyed by the Presentation Context ID that corresponds with the Meta - SOP Class and is defined at Association setup. - - The SCP shall append the SOP - Class/Instance UID pair of the created Image Box SOP Instance to the Referenced Image - Box Sequence Attribute of the parent Basic Film Box SOP Instance to link each Image Box - SOP Instance to the Basic Film Box SOP Instance. The SCP returns the list of Image Box - SOP Class/Instance UID pairs in the Attribute Referenced Image Box Sequence (2010,0510) - of the N-CREATE response message. - - If supported, the SCP shall create - Basic Annotation Box SOP Instances for each Annotation Box defined by the Attribute - Annotation Display Format ID and shall append the SOP Class/Instance UID pair of the - created Basic Annotation Box SOP Instance to the Referenced Annotation Box Sequence - Attribute of the parent Basic Film Box SOP Instance to link each Basic Annotation Box - SOP Instance to the Basic Film Box SOP Instance. The SCP returns the list of Basic - Annotation Box SOP Class/Instance UID pairs in the Attribute Referenced Annotation Box - Sequence of the N-CREATE response message. The Annotation Boxes shall support the same - character sets as the Basic Film Box. - - The character set supported by the - Film Box shall be the same as the character set of the Basic Film Session. - - The SCP shall return the status - code of the requested SOP Instance creation. The meaning of success, warning, and - failure status codes is defined in - . - + Upon the creation of the Basic Film Box SOP Instance, the SCP shall append the SOP Class/Instance UID pair of the created Basic Film Box SOP Instance to the Attribute Referenced Film Box Sequence (2000,0500) of the parent Basic Film Session SOP Instance to link the Basic Film Box SOP Instance to the Basic Film Session SOP Instance. + The SCP shall create Image Box SOP Instances of the appropriate Image Box SOP Class for each image box as defined by the Attribute Image Display Format (2010,0010). The SOP Class of the created Image Box SOP Instance depends on the Meta SOP Class context. For example the Grayscale Image Box SOP Class is related to the Basic Grayscale Print Management Meta SOP Class. The Meta SOP Class context is conveyed by the Presentation Context ID that corresponds with the Meta SOP Class and is defined at Association setup. + The SCP shall append the SOP Class/Instance UID pair of the created Image Box SOP Instance to the Referenced Image Box Sequence Attribute of the parent Basic Film Box SOP Instance to link each Image Box SOP Instance to the Basic Film Box SOP Instance. The SCP returns the list of Image Box SOP Class/Instance UID pairs in the Attribute Referenced Image Box Sequence (2010,0510) of the N-CREATE response message. + If supported, the SCP shall create Basic Annotation Box SOP Instances for each Annotation Box defined by the Attribute Annotation Display Format ID and shall append the SOP Class/Instance UID pair of the created Basic Annotation Box SOP Instance to the Referenced Annotation Box Sequence Attribute of the parent Basic Film Box SOP Instance to link each Basic Annotation Box SOP Instance to the Basic Film Box SOP Instance. The SCP returns the list of Basic Annotation Box SOP Class/Instance UID pairs in the Attribute Referenced Annotation Box Sequence of the N-CREATE response message. The Annotation Boxes shall support the same character sets as the Basic Film Box. + The character set supported by the Film Box shall be the same as the character set of the Basic Film Session. + The SCP shall return the status code of the requested SOP Instance creation. The meaning of success, warning, and failure status codes is defined in .
N-SET - The N-SET may be used to update the - last created instance of the Basic Film Box SOP Class. - + The N-SET may be used to update the last created instance of the Basic Film Box SOP Class.
Attributes - The Attributes that may be updated - are shown in. - + The Attributes that may be updated are shown in . @@ -25666,128 +18350,67 @@
N-SET Attributes
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Magnification - Type - + Magnification Type (2010,0060) @@ -25505,9 +18213,7 @@
- Configuration - Information - + Configuration Information (2010,0150) @@ -25518,56 +18224,43 @@
- Referenced - Presentation LUT Sequence - + Referenced Presentation LUT Sequence (2050,0500) U/MC - (Required if - Presentation LUT is supported) - + (Required if Presentation LUT is supported)
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) U/MC - (Required if - sequence is present) - + (Required if sequence is present)
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) U/MC - (Required if - sequence is present) - + (Required if sequence is present)
- Smoothing Type - + Smoothing Type (2010,0080) @@ -25578,8 +18271,7 @@
- Border Density - + Border Density (2010,0100) @@ -25590,9 +18282,7 @@
- Empty Image - Density - + Empty Image Density (2010,0110) @@ -25632,25 +18322,19 @@ U/MC - (Required if - Presentation LUT is supported) - + (Required if Presentation LUT is supported)
- Reflected Ambient - Light - + Reflected Ambient Light (2010,0160) U/MC - (Required if - Presentation LUT is supported) - + (Required if Presentation LUT is supported)
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in .
Status - The status values that are specific - for this SOP Class are defined in. - + The status values that are specific for this SOP Class are defined in .
Behavior - The SCU uses the N-SET to request - the SCP to update a Basic Film Box SOP Instance. The SCU shall only specify the SOP - Instance UID of the last created Basic Film Box SOP Instance in the N-SET request - primitive, and shall specify the list of Attributes for which the Attribute Values are - to be set. - - The SCP shall set new values for - the specified Attributes of the specified SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance update. The meaning of success, warning, and failure - status codes is defined in. - + The SCU uses the N-SET to request the SCP to update a Basic Film Box SOP Instance. The SCU shall only specify the SOP Instance UID of the last created Basic Film Box SOP Instance in the N-SET request primitive, and shall specify the list of Attributes for which the Attribute Values are to be set. + The SCP shall set new values for the specified Attributes of the specified SOP Instance. + The SCP shall return the status code of the requested SOP Instance update. The meaning of success, warning, and failure status codes is defined in .
N-DELETE - The N-DELETE is used to delete the last - created Basic Film Box SOP Instance hierarchy. As a result all the information describing - the last film is deleted. - - The Basic Film Box SOP Instance - hierarchy consists of one Basic Film Box SOP Instance, one or more Image Box SOP Instances, - zero or more Basic Annotation Box SOP Instances, zero or more Presentation LUT SOP - Instances, and zero or more Basic Print Image Overlay Box SOP instances. - + The N-DELETE is used to delete the last created Basic Film Box SOP Instance hierarchy. As a result all the information describing the last film is deleted. + The Basic Film Box SOP Instance hierarchy consists of one Basic Film Box SOP Instance, one or more Image Box SOP Instances, zero or more Basic Annotation Box SOP Instances, zero or more Presentation LUT SOP Instances, and zero or more Basic Print Image Overlay Box SOP instances. - There is no provision in the DICOM - Standard to delete previously created Film Box SOP Instances. - + There is no provision in the DICOM Standard to delete previously created Film Box SOP Instances.
Behavior - The SCU uses the N-DELETE to - request the SCP to delete the Basic Film Box SOP Instance hierarchy. The SCU shall - specify in the N-DELETE request primitive the SOP Instance UID of the last created Basic - Film Box (root). - - The SCP shall delete the specified - SOP Instance hierarchy and shall remove the UID of the deleted Basic Film Box SOP - Instance from the list of SOP Instance UIDs of the Film Box UIDs Attribute of the parent - Basic Film Session SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance hierarchy deletion. The meaning of success, warning, - and failure status codes is defined in. - - The SCP shall not delete SOP - Instances in the hierarchy as long as there are outstanding references to these SOP - Instances - + The SCU uses the N-DELETE to request the SCP to delete the Basic Film Box SOP Instance hierarchy. The SCU shall specify in the N-DELETE request primitive the SOP Instance UID of the last created Basic Film Box (root). + The SCP shall delete the specified SOP Instance hierarchy and shall remove the UID of the deleted Basic Film Box SOP Instance from the list of SOP Instance UIDs of the Film Box UIDs Attribute of the parent Basic Film Session SOP Instance. + The SCP shall return the status code of the requested SOP Instance hierarchy deletion. The meaning of success, warning, and failure status codes is defined in . + The SCP shall not delete SOP Instances in the hierarchy as long as there are outstanding references to these SOP Instances - It is beyond the scope of the - Standard to specify when the SCP actually deletes the Image SOP Instances with - outstanding references. - + It is beyond the scope of the Standard to specify when the SCP actually deletes the Image SOP Instances with outstanding references.
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
N-ACTION - The N-ACTION is used to print one or - more copies of the last created instance of the Film Box. - + The N-ACTION is used to print one or more copies of the last created instance of the Film Box.
Attributes - The arguments of the N-ACTION are - defined as shown in. - - The Action Reply argument is - encoded as a DICOM Data Set. The Data Set only contains the Attribute Referenced Print - Job Sequence (2100,0500), which includes the Referenced SOP Class UID (0008,1150) and - the Referenced SOP Instance UID (0008,1155). - - If the SCP supports the Print Job - SOP Class, the Action Reply argument is contained in the N-ACTION response. Otherwise, - the Action Reply is not contained in the N-ACTION response. - + The arguments of the N-ACTION are defined as shown in . + The Action Reply argument is encoded as a DICOM Data Set. The Data Set only contains the Attribute Referenced Print Job Sequence (2100,0500), which includes the Referenced SOP Class UID (0008,1150) and the Referenced SOP Instance UID (0008,1155). + If the SCP supports the Print Job SOP Class, the Action Reply argument is contained in the N-ACTION response. Otherwise, the Action Reply is not contained in the N-ACTION response. @@ -25800,54 +18423,42 @@ 1 @@ -25856,22 +18467,16 @@
Status - - defines the specific status code values that may be returned in a N-ACTION response. See - - for additional response status codes. - + defines the specific status code values that may be returned in a N-ACTION response. See for additional response status codes.
N-ACTION Arguments
- Action Type Name - + Action Type Name - Action Type ID - + Action Type ID - Attribute Name - + Attribute Name - Tag + Tag - Usage SCU/SCP - + Usage SCU/SCP
- Referenced Print - Job Sequence - + Referenced Print Job Sequence (2100,0500) -/MC - Required if Print - Job SOP is supported - + Required if Print Job SOP is supported
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) -/MC - Required if - Referenced Print Job Sequence (2100,0500) is present - + Required if Referenced Print Job Sequence (2100,0500) is present
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) -/MC - Required if - Referenced Print Job Sequence (2100,0500) is present - + Required if Referenced Print Job Sequence (2100,0500) is present
Status Values
- Service Status - + Service Status - Further Meaning - + Further Meaning Status Code @@ -25884,9 +18489,7 @@ Success - Film accepted for - printing; if supported, the Print Job SOP Instance is created - + Film accepted for printing; if supported, the Print Job SOP Instance is created 0000 @@ -25897,9 +18500,7 @@ Warning - Film Box SOP - Instance hierarchy does not contain Image Box SOP Instances (empty page) - + Film Box SOP Instance hierarchy does not contain Image Box SOP Instances (empty page) B603 @@ -25907,9 +18508,7 @@
- Image size is - larger than image box size, the image has been demagnified. - + Image size is larger than image box size, the image has been demagnified. B604 @@ -25917,9 +18516,7 @@
- Image size is - larger than the Image Box size. The Image has been cropped to fit. - + Image size is larger than the Image Box size. The Image has been cropped to fit. B609 @@ -25927,10 +18524,7 @@
- Image size or - Combined Print Image size is larger than the Image Box size. Image or - Combined Print Image has been decimated to fit. - + Image size or Combined Print Image size is larger than the Image Box size. Image or Combined Print Image has been decimated to fit. B60A @@ -25941,9 +18535,7 @@ Failure - Failed: Unable to - create Print Job SOP Instance; print queue is full - + Failed: Unable to create Print Job SOP Instance; print queue is full C602 @@ -25951,9 +18543,7 @@
- Failed: Image size - is larger than image box size - + Failed: Image size is larger than image box size C603 @@ -25961,9 +18551,7 @@
- Failed: Combined - Print Image size is larger than the Image Box size - + Failed: Combined Print Image size is larger than the Image Box size C613 @@ -25972,45 +18560,21 @@
- Previous versions of the DICOM - Standard defined the status code of C604. This code was specified for the case of an - image position collision. Since image position collision is not a possible state, - the code has been retired. - + Previous versions of the DICOM Standard defined the status code of C604. This code was specified for the case of an image position collision. Since image position collision is not a possible state, the code has been retired.
Behavior - The SCU uses the N-ACTION to - request the SCP to print one or more copies of a single film of the film session. The - SCU shall only specify the SOP Instance UID of the last created Basic Film Box SOP - Instance in the N-ACTION request primitive. - - The SCP shall make a copy of the - "working" Basic Film Session SOP Instance and the "working" Basic Film Box SOP Instance - hierarchy, which contains all the information to control the Print Process. Hence the - SCU may further update the "working" SOP Instances without affecting the result of - previous print requests. The execution of the Print Process is monitored by the Print - Job SOP Class (if supported by the SCP) and the Printer SOP Class. - - If the SCP supports the Print Job - SOP Class then the SCP shall create a Print Job SOP Instance, which contains the copy of - the "working" Basic Film Session SOP Instance hierarchy and shall return the Print Job - SOP Class/Instance UID pair in the Attribute Referenced Print Job Sequence of the Action - Reply argument. - - The SCP shall return the status - code of the requested operation. The meaning of success, warning, and failure status - codes is defined in. - + The SCU uses the N-ACTION to request the SCP to print one or more copies of a single film of the film session. The SCU shall only specify the SOP Instance UID of the last created Basic Film Box SOP Instance in the N-ACTION request primitive. + The SCP shall make a copy of the "working" Basic Film Session SOP Instance and the "working" Basic Film Box SOP Instance hierarchy, which contains all the information to control the Print Process. Hence the SCU may further update the "working" SOP Instances without affecting the result of previous print requests. The execution of the Print Process is monitored by the Print Job SOP Class (if supported by the SCP) and the Printer SOP Class. + If the SCP supports the Print Job SOP Class then the SCP shall create a Print Job SOP Instance, which contains the copy of the "working" Basic Film Session SOP Instance hierarchy and shall return the Print Job SOP Class/Instance UID pair in the Attribute Referenced Print Job Sequence of the Action Reply argument. + The SCP shall return the status code of the requested operation. The meaning of success, warning, and failure status codes is defined in .
SOP Class Definition and UID - The Basic Film Box SOP Class UID shall have - the value "1.2.840.10008.5.1.1.2". - + The Basic Film Box SOP Class UID shall have the value "1.2.840.10008.5.1.1.2".
@@ -26019,33 +18583,19 @@ Basic Grayscale Image Box SOP Class
IOD Description - The Basic Image Box IOD is an - abstraction of the presentation of an image and image related data in the image area of a - film. The Basic Image Box IOD describes the presentation parameters and image pixel data - that apply to a single image of a sheet of film. - - The Basic Grayscale Image Box SOP - Instance is created by the SCP at the time the Basic Film Box SOP Instance is created, based - on the value of the Basic Film Box Attribute Image Display Format (2010,0010). - - The Basic Grayscale Image Box SOP - Instance refers to zero or one Image Overlay Box SOP Instance and zero or one Presentation - LUT SOP Instance. - + The Basic Image Box IOD is an abstraction of the presentation of an image and image related data in the image area of a film. The Basic Image Box IOD describes the presentation parameters and image pixel data that apply to a single image of a sheet of film. + The Basic Grayscale Image Box SOP Instance is created by the SCP at the time the Basic Film Box SOP Instance is created, based on the value of the Basic Film Box Attribute Image Display Format (2010,0010). + The Basic Grayscale Image Box SOP Instance refers to zero or one Image Overlay Box SOP Instance and zero or one Presentation LUT SOP Instance.
DIMSE Service Group - The DIMSE Services applicable to the - IOD are shown below. - + The DIMSE Services applicable to the IOD are shown below.
DIMSE Service Group Applicable to Basic Grayscale Image Box
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -26063,58 +18613,39 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in . - There is no N-CREATE because - Instances of the Basic Grayscale Image Box SOP Class are created by the SCP as a result - of the N-CREATE of the Film Box SOP Instance. - + There is no N-CREATE because Instances of the Basic Grayscale Image Box SOP Class are created by the SCP as a result of the N-CREATE of the Film Box SOP Instance. - This Section describes the behavior of - the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE - Services is specified in. - + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-SET - The N-SET may be used to update an - instance of the Basic Grayscale Image Box SOP Class. - + The N-SET may be used to update an instance of the Basic Grayscale Image Box SOP Class.
Attributes - The Attributes that may be - updated are shown in. - + The Attributes that may be updated are shown in .
N-SET Attributes
- Attribute - Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Image Box - Position - + Image Box Position - (2020,0010) - + (2020,0010) M/M @@ -26122,13 +18653,10 @@
- Basic Grayscale - Image Sequence - + Basic Grayscale Image Sequence - (2020,0110) - + (2020,0110) M/M @@ -26136,13 +18664,10 @@
- >Samples Per - Pixel - + >Samples Per Pixel - (0028,0002) - + (0028,0002) M/M @@ -26150,13 +18675,10 @@
- >Photometric - Interpretation - + >Photometric Interpretation - (0028,0004) - + (0028,0004) M/M @@ -26167,8 +18689,7 @@ >Rows - (0028,0010) - + (0028,0010) M/M @@ -26176,12 +18697,10 @@
- >Columns - + >Columns - (0028,0011) - + (0028,0011) M/M @@ -26189,30 +18708,22 @@
- >Pixel - Aspect Ratio - + >Pixel Aspect Ratio - (0028,0034) - + (0028,0034) MC/M - (Required if - the aspect ratio is not 1\1) - + (Required if the aspect ratio is not 1\1)
- >Bits - Allocated - + >Bits Allocated - (0028,0100) - + (0028,0100) M/M @@ -26220,13 +18731,10 @@
- >Bits - Stored - + >Bits Stored - (0028,0101) - + (0028,0101) M/M @@ -26234,12 +18742,10 @@
- >High Bit - + >High Bit - (0028,0102) - + (0028,0102) M/M @@ -26247,13 +18753,10 @@
- >Pixel - Representation - + >Pixel Representation - (0028,0103) - + (0028,0103) M/M @@ -26261,13 +18764,10 @@
- >Pixel - Data - + >Pixel Data - (7FE0,0010) - + (7FE0,0010) M/M @@ -26278,8 +18778,7 @@ Polarity - (2020,0020) - + (2020,0020) U/M @@ -26287,13 +18786,10 @@
- Magnification - Type - + Magnification Type - (2010,0060) - + (2010,0060) U/U @@ -26301,13 +18797,10 @@
- Smoothing - Type - + Smoothing Type - (2010,0080) - + (2010,0080) U/U @@ -26315,12 +18808,10 @@
- Min Density - + Min Density - (2010,0120) - + (2010,0120) U/U @@ -26328,12 +18819,10 @@
- Max Density - + Max Density - (2010,0130) - + (2010,0130) U/U @@ -26341,13 +18830,10 @@
- Configuration - Information - + Configuration Information - (2010,0150) - + (2010,0150) U/U @@ -26355,13 +18841,10 @@
- Requested Image - Size - + Requested Image Size - (2020,0030) - + (2020,0030) U/U @@ -26369,13 +18852,10 @@
- Requested - Decimate/Crop Behavior - + Requested Decimate/Crop Behavior - (2020,0040) - + (2020,0040) U/U @@ -26383,13 +18863,10 @@
- Referenced - Presentation LUT Sequence - + Referenced Presentation LUT Sequence - (2050,0500) - + (2050,0500) U/U @@ -26397,13 +18874,10 @@
- >Referenced - SOP Class UID - + >Referenced SOP Class UID - (0008,1150) - + (0008,1150) U/U @@ -26411,13 +18885,10 @@
- >Referenced - SOP Instance UID - + >Referenced SOP Instance UID - (0008,1155) - + (0008,1155) U/U @@ -26425,13 +18896,10 @@
- Original Image - Sequence - + Original Image Sequence - (2130,00C0) - + (2130,00C0) U/U @@ -26439,13 +18907,10 @@
- >Study - Instance UID - + >Study Instance UID - (0020,000D) - + (0020,000D) M/M @@ -26453,13 +18918,10 @@
- >Series - Instance UID - + >Series Instance UID - (0020,000E) - + (0020,000E) M/M @@ -26467,13 +18929,10 @@
- >Patient - ID - + >Patient ID - (0010,0020) - + (0010,0020) M/M @@ -26481,13 +18940,10 @@
- >Referenced - SOP Class UID - + >Referenced SOP Class UID - (0008,1150) - + (0008,1150) M/M @@ -26495,13 +18951,10 @@
- >Referenced - SOP Instance UID - + >Referenced SOP Instance UID - (0008,1155) - + (0008,1155) M/M @@ -26509,45 +18962,26 @@
- The meaning of the Usage - SCU/SCP is described in. - - The values of Magnification - Type (2010,0060) and Smoothing Type (2010,0080) of a particular image box override - the values of Magnification Type and Smoothing Type of the film box. - - Values for Referenced - Presentation LUT Sequence override any Presentation LUT that may have been set at - the Basic Film Box. Values for Min/Max Density override any Density values that may - have been set at the Basic Film Box. - + The meaning of the Usage SCU/SCP is described in . + The values of Magnification Type (2010,0060) and Smoothing Type (2010,0080) of a particular image box override the values of Magnification Type and Smoothing Type of the film box. + Values for Referenced Presentation LUT Sequence override any Presentation LUT that may have been set at the Basic Film Box. Values for Min/Max Density override any Density values that may have been set at the Basic Film Box.
Status - - defines the specific status code values that may be returned in a N-SET response. - See - - for additional response status codes. - + defines the specific status code values that may be returned in a N-SET response. See for additional response status codes. @@ -26557,9 +18991,7 @@ Success
Status Values for Basic Grayscale Image Box SOP Class
- Service - Status - + Service Status - Further - Meaning - + Further Meaning - Status Code - + Status Code
- Image - successfully stored in Image Box - + Image successfully stored in Image Box 0000 @@ -26570,9 +19002,7 @@ Warning - Image size - larger than image box size, the image has been demagnified. - + Image size larger than image box size, the image has been demagnified. B604 @@ -26580,11 +19010,7 @@
- Requested Min - Density or Max Density outside of printer's operating range. The - printer will use its respective minimum or maximum density value - instead. - + Requested Min Density or Max Density outside of printer's operating range. The printer will use its respective minimum or maximum density value instead. B605 @@ -26592,9 +19018,7 @@
- Image size is - larger than the Image Box size. The Image has been cropped to fit. - + Image size is larger than the Image Box size. The Image has been cropped to fit. B609 @@ -26602,10 +19026,7 @@
- Image size or - Combined Print Image size is larger than the Image Box size. The - Image or Combined Print Image has been decimated to fit. - + Image size or Combined Print Image size is larger than the Image Box size. The Image or Combined Print Image has been decimated to fit. B60A @@ -26616,9 +19037,7 @@ Failure - Failed: Image - size is larger than image box size - + Failed: Image size is larger than image box size C603 @@ -26626,9 +19045,7 @@
- Failed: - Insufficient memory in printer to store the image - + Failed: Insufficient memory in printer to store the image C605 @@ -26636,9 +19053,7 @@
- Failed: - Combined Print Image size is larger than the Image Box size - + Failed: Combined Print Image size is larger than the Image Box size C613 @@ -26649,72 +19064,39 @@
Behavior - The SCU uses the N-SET to - request the SCP to update a Basic Grayscale Image Box SOP Instance. The SCU shall - only specify the SOP Instance UID of a Basic Grayscale Image Box belonging to the - last created Film Box SOP Instance and shall specify the list of Attributes for - which the Attribute Values are to be set. - - To instruct the SCP to erase - the image in the image position, the SCU shall set a zero length and no value in the - Attribute Basic Grayscale Image Sequence (2020,0110). - - The SCP shall set new values - for the specified Attributes of the specified SOP Instance. - + The SCU uses the N-SET to request the SCP to update a Basic Grayscale Image Box SOP Instance. The SCU shall only specify the SOP Instance UID of a Basic Grayscale Image Box belonging to the last created Film Box SOP Instance and shall specify the list of Attributes for which the Attribute Values are to be set. + To instruct the SCP to erase the image in the image position, the SCU shall set a zero length and no value in the Attribute Basic Grayscale Image Sequence (2020,0110). + The SCP shall set new values for the specified Attributes of the specified SOP Instance. - The image in this N-SET - supersedes any image previously set in the Image Box. - + The image in this N-SET supersedes any image previously set in the Image Box. - The SCP shall return the status - code of the requested SOP Instance update. The meaning of success, warning, and - failure status codes is defined in. - - If Requested Decimate/Crop - Behavior (2020,0040) specifies DECIMATE, Magnification Type (2010,0060) specifies - NONE, and the image is too large to fit the Image Box, the SCP shall fail the N-SET. - + The SCP shall return the status code of the requested SOP Instance update. The meaning of success, warning, and failure status codes is defined in . + If Requested Decimate/Crop Behavior (2020,0040) specifies DECIMATE, Magnification Type (2010,0060) specifies NONE, and the image is too large to fit the Image Box, the SCP shall fail the N-SET.
SOP Class Definition and UID - The Basic Grayscale Image Box SOP Class - UID shall have the value "1.2.840.10008.5.1.1.4". - + The Basic Grayscale Image Box SOP Class UID shall have the value "1.2.840.10008.5.1.1.4".
Basic Color Image Box SOP Class
IOD Description - The Basic Image Box IOD is an - abstraction of the presentation of an image and image related data in the image area of a - film. The Basic Image Box IOD describes the presentation parameters and image pixel data - that apply to a single image of a sheet of film. - - The Basic Color Image Box SOP Instance - is created by the SCP at the time the Basic Film Box SOP Instance is created, based on the - value of the Basic Film Box Attribute Image Display Format (2010,0010). - - The Basic Color Image Box SOP Instance - refers to zero or one Image Overlay Box SOP Instance. - + The Basic Image Box IOD is an abstraction of the presentation of an image and image related data in the image area of a film. The Basic Image Box IOD describes the presentation parameters and image pixel data that apply to a single image of a sheet of film. + The Basic Color Image Box SOP Instance is created by the SCP at the time the Basic Film Box SOP Instance is created, based on the value of the Basic Film Box Attribute Image Display Format (2010,0010). + The Basic Color Image Box SOP Instance refers to zero or one Image Overlay Box SOP Instance.
DIMSE Service Group - The following DIMSE Services are - applicable to the IOD. - + The following DIMSE Services are applicable to the IOD.
DIMSE Service Group Applicable to Basic Color Image Box
- DIMSE Service element - + DIMSE Service element Usage SCU/SCP @@ -26732,65 +19114,41 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in . - There is no N-CREATE because - Instances of the Basic Color Image Box SOP Class are created by the SCP as a result of - the N-CREATE of the Film Box SOP Instance. - + There is no N-CREATE because Instances of the Basic Color Image Box SOP Class are created by the SCP as a result of the N-CREATE of the Film Box SOP Instance. - This Section describes the behavior of - the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE - Services is specified in. - + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-SET - The N-SET may be used to update an - instance of the Basic Color Image Box SOP Class. - + The N-SET may be used to update an instance of the Basic Color Image Box SOP Class.
Attributes - The Attributes that may be - updated are shown in. - - The meaning of the Usage - SCU/SCP is described in. - - The values of Magnification - Type (2010,0060) and Smoothing Type (2010,0080) of a particular image box override - the values of Magnification Type and Smoothing Type of the film box. - + The Attributes that may be updated are shown in . + The meaning of the Usage SCU/SCP is described in . + The values of Magnification Type (2010,0060) and Smoothing Type (2010,0080) of a particular image box override the values of Magnification Type and Smoothing Type of the film box.
N-SET Attributes
- Attribute - Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Image Box - Position - + Image Box Position - (2020,0010) - + (2020,0010) M/M @@ -26798,13 +19156,10 @@
- Basic Color - Image Sequence - + Basic Color Image Sequence - (2020,0111) - + (2020,0111) M/M @@ -26812,13 +19167,10 @@
- >Samples Per - Pixel - + >Samples Per Pixel - (0028,0002) - + (0028,0002) M/M @@ -26826,13 +19178,10 @@
- >Photometric - Interpretation - + >Photometric Interpretation - (0028,0004) - + (0028,0004) M/M @@ -26840,13 +19189,10 @@
- >Planar - Configuration - + >Planar Configuration - (0028,0006) - + (0028,0006) M/M @@ -26857,8 +19203,7 @@ >Rows - (0028,0010) - + (0028,0010) M/M @@ -26866,12 +19211,10 @@
- >Columns - + >Columns - (0028,0011) - + (0028,0011) M/M @@ -26879,30 +19222,22 @@
- >Pixel - Aspect Ratio - + >Pixel Aspect Ratio - (0028,0034) - + (0028,0034) MC/M - (Required if - the aspect ratio is not 1\1) - + (Required if the aspect ratio is not 1\1)
- >Bits - Allocated - + >Bits Allocated - (0028,0100) - + (0028,0100) M/M @@ -26910,13 +19245,10 @@
- >Bits - Stored - + >Bits Stored - (0028,0101) - + (0028,0101) M/M @@ -26924,12 +19256,10 @@
- >High Bit - + >High Bit - (0028,0102) - + (0028,0102) M/M @@ -26937,13 +19267,10 @@
- >Pixel - Representation - + >Pixel Representation - (0028,0103) - + (0028,0103) M/M @@ -26951,13 +19278,10 @@
- >Pixel - Data - + >Pixel Data - (7FE0,0010) - + (7FE0,0010) M/M @@ -26968,8 +19292,7 @@ Polarity - (2020,0020) - + (2020,0020) U/M @@ -26977,13 +19300,10 @@
- Magnification - Type - + Magnification Type - (2010,0060) - + (2010,0060) U/U @@ -26991,13 +19311,10 @@
- Smoothing - Type - + Smoothing Type - (2010,0080) - + (2010,0080) U/U @@ -27005,13 +19322,10 @@
- Requested Image - Size - + Requested Image Size - (2020,0030) - + (2020,0030) U/U @@ -27019,13 +19333,10 @@
- Requested - Decimate/Crop Behavior - + Requested Decimate/Crop Behavior - (2020,0040) - + (2020,0040) U/U @@ -27033,13 +19344,10 @@
- Original Image - Sequence - + Original Image Sequence - (2130,00C0) - + (2130,00C0) U/U @@ -27047,13 +19355,10 @@
- >Study - Instance UID - + >Study Instance UID - (0020,000D) - + (0020,000D) M/M @@ -27061,13 +19366,10 @@
- >Series - Instance UID - + >Series Instance UID - (0020,000E) - + (0020,000E) M/M @@ -27075,13 +19377,10 @@
- >Patient - ID - + >Patient ID - (0010,0020) - + (0010,0020) M/M @@ -27089,13 +19388,10 @@
- >Referenced - SOP Class UID - + >Referenced SOP Class UID - (0008,1150) - + (0008,1150) M/M @@ -27103,13 +19399,10 @@
- >Referenced - SOP Instance UID - + >Referenced SOP Instance UID - (0008,1155) - + (0008,1155) M/M @@ -27121,29 +19414,19 @@
Status - - defines the specific status code values that may be returned in a N-SET response. - See - - for additional response status codes. - + defines the specific status code values that may be returned in a N-SET response. See for additional response status codes. @@ -27153,9 +19436,7 @@ Warning
Status Values for Basic Color Image Box SOP Class
- Service - Status - + Service Status - Further - Meaning - + Further Meaning - Status Code - + Status Code
- Image size - larger than image box size, the image has been demagnified. - + Image size larger than image box size, the image has been demagnified. B604 @@ -27163,9 +19444,7 @@
- Image size is - larger than the Image Box size. The Image has been cropped to fit. - + Image size is larger than the Image Box size. The Image has been cropped to fit. B609 @@ -27173,10 +19452,7 @@
- Image size or - Combined Print Image size is larger than the Image Box size. The - Image or Combined Print Image has been decimated to fit. - + Image size or Combined Print Image size is larger than the Image Box size. The Image or Combined Print Image has been decimated to fit. B60A @@ -27187,9 +19463,7 @@ Failure - Failed: Image - size is larger than image box size - + Failed: Image size is larger than image box size C603 @@ -27197,9 +19471,7 @@
- Failed: - Insufficient memory in printer to store the image - + Failed: Insufficient memory in printer to store the image C605 @@ -27207,9 +19479,7 @@
- Failed: - Combined Print Image size is larger than the Image Box size - + Failed: Combined Print Image size is larger than the Image Box size C613 @@ -27220,83 +19490,44 @@
Behavior - The SCU uses the N-SET to - request the SCP to update a Basic Color Image Box SOP Instance. The SCU shall only - specify the SOP Instance UID of a Basic Color Image Box belonging to the last - created Film Box SOP Instance and shall specify the list of Attributes for which the - Attribute Values are to be set. - - To instruct the SCP to erase - the image in the image position, the SCU shall set a zero length and no value in the - Attribute Basic Color Image Sequence (2020,0111). - - The SCP shall set new values - for the specified Attributes of the specified SOP Instance. - + The SCU uses the N-SET to request the SCP to update a Basic Color Image Box SOP Instance. The SCU shall only specify the SOP Instance UID of a Basic Color Image Box belonging to the last created Film Box SOP Instance and shall specify the list of Attributes for which the Attribute Values are to be set. + To instruct the SCP to erase the image in the image position, the SCU shall set a zero length and no value in the Attribute Basic Color Image Sequence (2020,0111). + The SCP shall set new values for the specified Attributes of the specified SOP Instance. - The image in this N-SET - supersedes any image previously set in the Image Box. - + The image in this N-SET supersedes any image previously set in the Image Box. - The SCP shall return the status - code of the requested SOP Instance update. The meaning of success, warning, and - failure status codes is defined in. - - If Requested Decimate/Crop - Behavior (2020,0040) specifies DECIMATE, Magnification Type (2010,0060) specifies - NONE, and the image is too large to fit the Image Box, the SCP shall fail the N-SET. - - The color characteristics of - the Pixel Data (7FE0,0010) in the Basic Color Image Box may be described by an ICC - Input Device Profile specified in the Film Box, in which case the same profile shall - apply to all the Image Boxes in the same Film Box. See - - and. - + The SCP shall return the status code of the requested SOP Instance update. The meaning of success, warning, and failure status codes is defined in . + If Requested Decimate/Crop Behavior (2020,0040) specifies DECIMATE, Magnification Type (2010,0060) specifies NONE, and the image is too large to fit the Image Box, the SCP shall fail the N-SET. + The color characteristics of the Pixel Data (7FE0,0010) in the Basic Color Image Box may be described by an ICC Input Device Profile specified in the Film Box, in which case the same profile shall apply to all the Image Boxes in the same Film Box. See and .
SOP Class Definition and UID - The Basic Color Image Box SOP Class UID - shall have the value "1.2.840.10008.5.1.1.4.1". - + The Basic Color Image Box SOP Class UID shall have the value "1.2.840.10008.5.1.1.4.1".
Referenced Image Box SOP Class (Retired) - This section was previously defined in - DICOM. It is now retired. See PS 3.4-1998. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-1998.
Basic Annotation Box SOP Class
IOD Description - The Basic Annotation Box IOD is an - abstraction of the presentation of an annotation (e.g., text string) on a film. The Basic - Annotation Box IOD describes the most used text related presentation parameters. - - The Basic Annotation Box SOP Instance is - created by the SCP at the time the Basic Film Box SOP Instance is created, based on the value of - the Attribute Annotation Display Format ID (2010,0030) of the Basic Film Box. - + The Basic Annotation Box IOD is an abstraction of the presentation of an annotation (e.g., text string) on a film. The Basic Annotation Box IOD describes the most used text related presentation parameters. + The Basic Annotation Box SOP Instance is created by the SCP at the time the Basic Film Box SOP Instance is created, based on the value of the Attribute Annotation Display Format ID (2010,0030) of the Basic Film Box.
DIMSE Service Group - The DIMSE Services that are applicable to - the IOD are shown below. - + The DIMSE Services that are applicable to the IOD are shown below.
DIMSE Service Group Applicable to Basic Annotation Box
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -27314,51 +19545,36 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in . - There is no N-CREATE because the - Instances of the Basic Annotation Box SOP Class are created by the Film Box SOP Instance. - + There is no N-CREATE because the Instances of the Basic Annotation Box SOP Class are created by the Film Box SOP Instance. - This Section describes the behavior of the - DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is - specified in. - + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-SET - The N-SET is used to update the Basic - Annotation Box SOP Instance. - + The N-SET is used to update the Basic Annotation Box SOP Instance.
Attributes - The Attributes that may be updated - are shown in. - + The Attributes that may be updated are shown in .
N-SET Attributes
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Annotation - position - + Annotation position (2030,0010) @@ -27380,72 +19596,41 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in .
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
Behavior - The SCU uses the N-SET to request - the SCP to update a Basic Annotation Box SOP Instance. The SCU shall only specify the - SOP Instance UID of the Basic Annotation Box belonging to the last created Film Box SOP - Instance in the N-SET request primitive, and shall specify the list of Attributes for - which the Attribute Values are to be set. The SCU may erase the text string by setting a - zero length value in the Attribute Text String (2030,0020). - - The SCP shall set new values for - the specified Attributes of the specified SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance update. The meaning of success, warning, and failure - status codes is defined in. - + The SCU uses the N-SET to request the SCP to update a Basic Annotation Box SOP Instance. The SCU shall only specify the SOP Instance UID of the Basic Annotation Box belonging to the last created Film Box SOP Instance in the N-SET request primitive, and shall specify the list of Attributes for which the Attribute Values are to be set. The SCU may erase the text string by setting a zero length value in the Attribute Text String (2030,0020). + The SCP shall set new values for the specified Attributes of the specified SOP Instance. + The SCP shall return the status code of the requested SOP Instance update. The meaning of success, warning, and failure status codes is defined in .
SOP Class Definition and UID - The Basic Annotation Box SOP Class UID - shall have the value "1.2.840.10008.5.1.1.15". - + The Basic Annotation Box SOP Class UID shall have the value "1.2.840.10008.5.1.1.15".
Print Job SOP Class
IOD Description - The Print Job IOD is an abstraction of the - Print Job transaction and is the basic information entity to monitor the execution of the Print - Process. A Print Job contains one film or multiple films, all belonging to the same film - session. - - The Print Job SOP Class is created by - N-ACTION operation of the Film Session SOP Class, Film Box SOP Class, or Pull Print Request SOP - Class. The Print Job SOP Instance is deleted after the films are printed or after a failure - condition. - + The Print Job IOD is an abstraction of the Print Job transaction and is the basic information entity to monitor the execution of the Print Process. A Print Job contains one film or multiple films, all belonging to the same film session. + The Print Job SOP Class is created by N-ACTION operation of the Film Session SOP Class, Film Box SOP Class, or Pull Print Request SOP Class. The Print Job SOP Instance is deleted after the films are printed or after a failure condition.
DIMSE Service Group - The DIMSE Services that are applicable to - the IOD are shown below. - + The DIMSE Services that are applicable to the IOD are shown below.
DIMSE Service Group Applicable to Print Job
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -27471,51 +19656,35 @@
- The meaning of the Usage SCU/SCP is - described in. - - This Section describes the behavior of the - DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is - specified in. - + The meaning of the Usage SCU/SCP is described in . + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-EVENT-REPORT - The N-EVENT-REPORT is used to report - execution status changes to the SCU in an asynchronous way. - + The N-EVENT-REPORT is used to report execution status changes to the SCU in an asynchronous way.
Attributes - The arguments of the N-EVENT-REPORT - are defined as shown in. - + The arguments of the N-EVENT-REPORT are defined as shown in . - The encoding of Notification - Event Information is defined in. - + The encoding of Notification Event Information is defined in . @@ -27528,9 +19697,7 @@ 1
Notification Event Information
- Event Type Name - + Event Type Name - Event Type ID - + Event Type ID - Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Execution Status - Info - + Execution Status Info (2100,0030) @@ -27543,9 +19710,7 @@ - Film Session - Label - + Film Session Label (2000,0050) @@ -27575,9 +19740,7 @@ 2 - Execution Status - Info - + Execution Status Info (2100,0030) @@ -27590,9 +19753,7 @@ - Film Session - Label - + Film Session Label (2000,0050) @@ -27622,9 +19783,7 @@ 3 - Execution Status - Info - + Execution Status Info (2100,0030) @@ -27637,9 +19796,7 @@ - Film Session - Label - + Film Session Label (2000,0050) @@ -27669,9 +19826,7 @@ 4 - Execution Status - Info - + Execution Status Info (2100,0030) @@ -27684,9 +19839,7 @@ - Film Session - Label - + Film Session Label (2000,0050) @@ -27713,70 +19866,44 @@
Behavior - The SCP uses the N-EVENT-REPORT to - inform the SCU about each execution change. The SCP shall only use the N-EVENT-REPORT - within the context of the Association in which the Print Job SOP Instance was created. - + The SCP uses the N-EVENT-REPORT to inform the SCU about each execution change. The SCP shall only use the N-EVENT-REPORT within the context of the Association in which the Print Job SOP Instance was created. - If SCU wants to monitor the - complete execution process of a Print Job, then the SCU should only release the - Association after the receipt of the event type Done or Failure. - + If SCU wants to monitor the complete execution process of a Print Job, then the SCU should only release the Association after the receipt of the event type Done or Failure. - The SCU shall return the - confirmation from the N-EVENT-REPORT operation. - - If the Event Type Name = Failure or - Pending then the error/pending condition is stored in the Execution Status Info - argument. The possible values of the Execution Status Info argument are defined in. - - If the Event Type Name = Failure or - Done then the SCP shall delete the Print Job SOP Instance after receiving a confirmation - from the SCU. - + The SCU shall return the confirmation from the N-EVENT-REPORT operation. + If the Event Type Name = Failure or Pending then the error/pending condition is stored in the Execution Status Info argument. The possible values of the Execution Status Info argument are defined in . + If the Event Type Name = Failure or Done then the SCP shall delete the Print Job SOP Instance after receiving a confirmation from the SCU.
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
N-GET - The N-GET is used to retrieve an - instance of the Print Job SOP Class. - + The N-GET is used to retrieve an instance of the Print Job SOP Class.
Attributes - The Attributes that may be - retrieved are shown in. - + The Attributes that may be retrieved are shown in .
N-GET Attributes
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Execution Status - + Execution Status (2100,0020) @@ -27787,9 +19914,7 @@
- Execution Status - Info - + Execution Status Info (2100,0030) @@ -27800,8 +19925,7 @@
- Print Priority - + Print Priority (2000,0020) @@ -27812,8 +19936,7 @@
- Creation Date - + Creation Date (2100,0040) @@ -27824,8 +19947,7 @@
- Creation Time - + Creation Time (2100,0050) @@ -27858,73 +19980,45 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in .
Behavior - The SCU uses the N-GET to request - the SCP to get a Print Job SOP Instance. The SCU shall specify in the N-GET request - primitive the UID of the SOP Instance to be retrieved. - - The SCP shall return the values for - the specified Attributes of the specified SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance retrieval. The meaning of success, warning, and - failure status codes is defined in - . - + The SCU uses the N-GET to request the SCP to get a Print Job SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved. + The SCP shall return the values for the specified Attributes of the specified SOP Instance. + The SCP shall return the status code of the requested SOP Instance retrieval. The meaning of success, warning, and failure status codes is defined in .
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
Execution Status Information - Status Information is defined in. Implementation - specific warning and error codes shall be defined in the Conformance Statement. - + Status Information is defined in . Implementation specific warning and error codes shall be defined in the Conformance Statement.
SOP Class Definition and UID - The Print Job SOP Class UID shall have the - value "1.2.840.10008.5.1.1.14". - + The Print Job SOP Class UID shall have the value "1.2.840.10008.5.1.1.14".
Printer SOP Class
IOD Description - The Printer IOD is an abstraction of the - hard copy printer and is the basic Information Entity to monitor the status of the printer. - - The Printer SOP Instance is created by the - SCP during start-up of the hard copy printer and has a well-known SOP Instance UID. - + The Printer IOD is an abstraction of the hard copy printer and is the basic Information Entity to monitor the status of the printer. + The Printer SOP Instance is created by the SCP during start-up of the hard copy printer and has a well-known SOP Instance UID.
DIMSE Service Group - The DIMSE Services that are applicable to - the IOD are shown below. - + The DIMSE Services that are applicable to the IOD are shown below.
DIMSE Service Group Applicable to Printer
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -27950,51 +20044,35 @@
- The meaning of the Usage SCU/SCP is - described in. - - This Section describes the behavior of the - DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is - specified in. - + The meaning of the Usage SCU/SCP is described in . + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-EVENT-REPORT - The N-EVENT-REPORT is used to report - the changes of the printer status in an asynchronous way. - + The N-EVENT-REPORT is used to report the changes of the printer status in an asynchronous way.
Attributes - The arguments of the N-EVENT-REPORT - are defined as shown in. - + The arguments of the N-EVENT-REPORT are defined as shown in . - The encoding of Notification - Event Information is defined in. - + The encoding of Notification Event Information is defined in . @@ -28018,9 +20096,7 @@ 2
Notification Event Information
- Event Type Name - + Event Type Name - Event Type ID - + Event Type ID - Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Printer Status - Info - + Printer Status Info (2110,0020) @@ -28033,8 +20109,7 @@ - Film Destination - + Film Destination (2000,0040) @@ -28064,9 +20139,7 @@ 3 - Printer Status - Info - + Printer Status Info (2110,0020) @@ -28079,8 +20152,7 @@ - Film Destination - + Film Destination (2000,0040) @@ -28107,61 +20179,40 @@
Behavior - The SCP shall use the - N-EVENT-REPORT to inform the SCU about each execution change. The SCP shall send the - events to all SCUs with which the SCP has an Association that is using the printer for - which the status changes. - - The SCU shall return the - confirmation of the N-EVENT-REPORT operation. - - If the Event Type Name = Warning or - Failure then the warning/failure condition is stored in the Printer Status Info - argument. The possible values the Printer Status Info argument are defined in. - + The SCP shall use the N-EVENT-REPORT to inform the SCU about each execution change. The SCP shall send the events to all SCUs with which the SCP has an Association that is using the printer for which the status changes. + The SCU shall return the confirmation of the N-EVENT-REPORT operation. + If the Event Type Name = Warning or Failure then the warning/failure condition is stored in the Printer Status Info argument. The possible values the Printer Status Info argument are defined in .
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
N-GET - The N-GET is used to retrieve an - instance of the Printer SOP Class. - + The N-GET is used to retrieve an instance of the Printer SOP Class.
Attributes - The Attributes that may be - retrieved are shown in. - + The Attributes that may be retrieved are shown in .
N-GET Attributes
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Printer Status - + Printer Status (2110,0010) @@ -28172,9 +20223,7 @@
- Printer Status - Info - + Printer Status Info (2110,0020) @@ -28207,9 +20256,7 @@
- Manufacturer Model - Name - + Manufacturer Model Name (0008,1090) @@ -28220,9 +20267,7 @@
- Device Serial - Number - + Device Serial Number (0018,1000) @@ -28233,8 +20278,7 @@
- Software Versions - + Software Versions (0018,1020) @@ -28245,9 +20289,7 @@
- Date Last - Calibration - + Date Last Calibration (0018,1200) @@ -28258,8 +20300,7 @@
- Last Calibration - + Last Calibration (0018,1201) @@ -28270,134 +20311,67 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in .
Behavior - The SCU uses the N-GET to request - the SCP to get a Printer SOP Instance. The SCU shall specify in the N-GET request - primitive the UID of the SOP Instance to be retrieved. - - The SCP shall return the values for - the specified Attributes of the specified SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance retrieval. The meaning of success, warning, and - failure status codes is defined in - . - + The SCU uses the N-GET to request the SCP to get a Printer SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved. + The SCP shall return the values for the specified Attributes of the specified SOP Instance. + The SCP shall return the status code of the requested SOP Instance retrieval. The meaning of success, warning, and failure status codes is defined in .
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
Printer Status Information - Status Information is defined in. Implementation - specific warning and error codes shall be defined in the Conformance Statement. - + Status Information is defined in . Implementation specific warning and error codes shall be defined in the Conformance Statement.
SOP Class Definition and UID - The Printer SOP Class UID shall have the - value "1.2.840.10008.5.1.1.16". - + The Printer SOP Class UID shall have the value "1.2.840.10008.5.1.1.16".
Reserved Identifications - The well-known UID of the Printer SOP - Instance shall have the value "1.2.840.10008.5.1.1.17". - + The well-known UID of the Printer SOP Instance shall have the value "1.2.840.10008.5.1.1.17".
VOI LUT Box SOP Class(Retired) - This section was previously defined in DICOM. - It is now retired. See PS 3.4-1998. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-1998.
Image Overlay Box SOP Class(Retired) - This section was previously defined in DICOM. - It is now retired. See PS 3.4-1998. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-1998.
Presentation LUT SOP Class
Information Object Description - The Presentation LUT Information Object is - an abstraction of a Presentation LUT (see). The objective of - the Presentation LUT is to realize image display tailored for specific modalities, applications, - and user preferences. It is used to prepare image pixel data for display on devices that conform - to the Grayscale Standard Display Function defined in - . - + The Presentation LUT Information Object is an abstraction of a Presentation LUT (see ). The objective of the Presentation LUT is to realize image display tailored for specific modalities, applications, and user preferences. It is used to prepare image pixel data for display on devices that conform to the Grayscale Standard Display Function defined in . - The density range to be printed, Min - Density to Max Density, is specified at either the Film Box or the Image Box. As follows - from the definition for Min Density and Max Density in - , if the requested minimum density is lower than the minimum printer density, or the - requested maximum density is greater than the maximum printer density, the printer will use - its minimum or maximum density, respectively, when computing the standard response. - + The density range to be printed, Min Density to Max Density, is specified at either the Film Box or the Image Box. As follows from the definition for Min Density and Max Density in , if the requested minimum density is lower than the minimum printer density, or the requested maximum density is greater than the maximum printer density, the printer will use its minimum or maximum density, respectively, when computing the standard response. - The output of the Presentation LUT is - Presentation Values (P-Values). P-Values are approximately related to human perceptual response. - They are intended to facilitate common input for both hardcopy and softcopy display devices. - P-Values are intended to be independent of the specific class or characteristics of the display - device. - - The Presentation LUT is not intended to - alter the appearance of the pixel values, as specified as specified by the Photometric - Interpretation (0028,0004) and Polarity (2020,0020). - - The Basic Film Box Information Object, the - Basic Image Box Information Object and the Referenced Image Box Object reference the - Presentation LUT. - - If the Configuration Information - (2010,0150) Attribute of the Basic Film Box IOD contains information similar to the Presentation - LUT, then the Presentation LUT Attributes shall take precedence. - + The output of the Presentation LUT is Presentation Values (P-Values). P-Values are approximately related to human perceptual response. They are intended to facilitate common input for both hardcopy and softcopy display devices. P-Values are intended to be independent of the specific class or characteristics of the display device. + The Presentation LUT is not intended to alter the appearance of the pixel values, as specified as specified by the Photometric Interpretation (0028,0004) and Polarity (2020,0020). + The Basic Film Box Information Object, the Basic Image Box Information Object and the Referenced Image Box Object reference the Presentation LUT. + If the Configuration Information (2010,0150) Attribute of the Basic Film Box IOD contains information similar to the Presentation LUT, then the Presentation LUT Attributes shall take precedence.
Mapping of P-Values to Optical Density - The mathematical definition of the - Grayscale Standard Display Function and mapping of P-Values to optical density for - reflective and transmissive printers is contained in - . - + The mathematical definition of the Grayscale Standard Display Function and mapping of P-Values to optical density for reflective and transmissive printers is contained in .
DIMSE Service Group - The following DIMSE Services are applicable - to the association related Presentation LUT Information Object: - + The following DIMSE Services are applicable to the association related Presentation LUT Information Object:
DIMSE Service Group Applicable to Presentation LUT
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -28423,84 +20397,58 @@
- The meaning of the Usage SCU/SCP is - described in. - - This section describes the behavior of the - DIMSE Services, which are specific for this Information Object. The general behavior of the - DIMSE services is specified in. - + The meaning of the Usage SCU/SCP is described in . + This section describes the behavior of the DIMSE Services, which are specific for this Information Object. The general behavior of the DIMSE services is specified in .
N-CREATE - The N-CREATE Service Element is used to - create an instance of the Presentation LUT SOP Class. - + The N-CREATE Service Element is used to create an instance of the Presentation LUT SOP Class.
Attributes - The Attribute list of the N-CREATE - Service Element is defined as shown in. - + The Attribute list of the N-CREATE Service Element is defined as shown in .
N-CREATE Attribute List
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Presentation LUT - Sequence - + Presentation LUT Sequence (2050,0010) MC/M - (Required if - Presentation LUT Shape (2050,0020) is not present. Not allowed - otherwise.) - + (Required if Presentation LUT Shape (2050,0020) is not present. Not allowed otherwise.)
- >LUT - Descriptor - + >LUT Descriptor (0028,3002) MC/M - (Required if - sequence is present). - - See. - + (Required if sequence is present). + See .
- >LUT - Explanation - + >LUT Explanation (0028,3003) @@ -28518,81 +20466,53 @@ MC/M - (Required if - sequence is present) - + (Required if sequence is present)
- Presentation LUT - Shape - + Presentation LUT Shape (2050,0020) MC/M - (Required if - Presentation LUT Sequence (2050,0010) is not present. Not allowed - otherwise.) - - SCPs shall support - the Enumerated Values IDENTITY and LIN OD - + (Required if Presentation LUT Sequence (2050,0010) is not present. Not allowed otherwise.) + SCPs shall support the Enumerated Values IDENTITY and LIN OD
LUT Descriptor - The first value (number of - entries in the LUT) shall be equal to: - + The first value (number of entries in the LUT) shall be equal to: - 256 if Bits Stored = - 8, - + 256 if Bits Stored = 8, - 4096 if Bits Stored = - 12. - + 4096 if Bits Stored = 12. - The second value shall be equal - to 0. - - The third value (number of bits - for each LUT entry) shall be 10-16. - - See the definition in - - for further explanation. - + The second value shall be equal to 0. + The third value (number of bits for each LUT entry) shall be 10-16. + See the definition in for further explanation.
Status - - defines the specific status code values that may be returned in a N-CREATE response. See - - for additional response status codes - + defines the specific status code values that may be returned in a N-CREATE response. See for additional response status codes @@ -29704,8 +21301,7 @@
Status Values for Presentation LUT SOP Class
- Service Status - + Service Status - Further Meaning - + Further Meaning Status Code @@ -28605,9 +20525,7 @@ Success - Presentation LUT - successfully created - + Presentation LUT successfully created 0000 @@ -28618,10 +20536,7 @@ Warning - Requested Min - Density or Max Density outside of printer's operating range. The printer - will use its respective minimum or maximum density value instead. - + Requested Min Density or Max Density outside of printer's operating range. The printer will use its respective minimum or maximum density value instead. B605 @@ -28632,107 +20547,52 @@
Behavior - The SCU uses the N-CREATE Service - Element to request the SCP to create a Presentation LUT SOP Instance. The SCU shall - initialize Attributes of the SOP Class as specified in. - - The SCU shall create the - Presentation LUT prior to referencing it from the Film Box or the Image Box. - - The Presentation LUT persists in - the SCP as long as the Association in which it was created is open or an explicit - N-DELETE is issued by the SCU. - - The SCP shall return the status - code of the requested SOP Instance creation. The meaning of success, warning, and - failure status codes is defined in - . - - The SCP shall use the Grayscale - Standard Display Function as specified in - - to convert the output of the Presentation LUT to density for printing. If the SCU - specifies values for Illumination (2010,015E) and/or Reflected Ambient Light - (2010,0160), these values shall be used instead of the default or configured values of - the SCP. If these values are not supplied, the SCP shall use its default or configured - values. (see - - for suggested defaults). - + The SCU uses the N-CREATE Service Element to request the SCP to create a Presentation LUT SOP Instance. The SCU shall initialize Attributes of the SOP Class as specified in . + The SCU shall create the Presentation LUT prior to referencing it from the Film Box or the Image Box. + The Presentation LUT persists in the SCP as long as the Association in which it was created is open or an explicit N-DELETE is issued by the SCU. + The SCP shall return the status code of the requested SOP Instance creation. The meaning of success, warning, and failure status codes is defined in . + The SCP shall use the Grayscale Standard Display Function as specified in to convert the output of the Presentation LUT to density for printing. If the SCU specifies values for Illumination (2010,015E) and/or Reflected Ambient Light (2010,0160), these values shall be used instead of the default or configured values of the SCP. If these values are not supplied, the SCP shall use its default or configured values. (see for suggested defaults).
N-DELETE - The N-DELETE Service Element is used to - delete the Presentation LUT SOP Instance. - + The N-DELETE Service Element is used to delete the Presentation LUT SOP Instance.
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
Behavior - The SCU uses the N-DELETE Service - Element to request the SCP to delete the Presentation LUT SOP Instance. The SCU shall - specify the Presentation LUT SOP Instance UID. - - The SCP shall not delete a - Presentation LUT SOP Instance as long as there are outstanding references to it. - Otherwise, it shall delete the specified Presentation LUT SOP Instance. The N-DELETE of - a Presentation LUT will prevent the SCU from further referencing it. The SCU shall not - reference a previously deleted Presentation LUT. The SCP shall return the status code of - the requested Presentation LUT SOP Instance deletion. The meaning of success, warning, - and failure status codes is defined in. - + The SCU uses the N-DELETE Service Element to request the SCP to delete the Presentation LUT SOP Instance. The SCU shall specify the Presentation LUT SOP Instance UID. + The SCP shall not delete a Presentation LUT SOP Instance as long as there are outstanding references to it. Otherwise, it shall delete the specified Presentation LUT SOP Instance. The N-DELETE of a Presentation LUT will prevent the SCU from further referencing it. The SCU shall not reference a previously deleted Presentation LUT. The SCP shall return the status code of the requested Presentation LUT SOP Instance deletion. The meaning of success, warning, and failure status codes is defined in .
SOP Class Definition and UID - The Presentation LUT SOP Class UID is - "1.2.840.10008.5.1.1.23". - + The Presentation LUT SOP Class UID is "1.2.840.10008.5.1.1.23".
Pull Print Request SOP Class(Retired) - This section was previously defined in DICOM. - It is now retired. See PS 3.4-2004. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-2004.
Printer Configuration Retrieval SOP Class
IOD Description - The Printer Configuration IOD is an - abstraction of the hard copy printer and is the basic Information Entity to retrieve key imaging - characteristics of the printer - - The Printer Configuration Retrieval SOP - Instance is created by the SCP during start-up of the hard copy printer and has a well-known SOP - Instance UID. - + The Printer Configuration IOD is an abstraction of the hard copy printer and is the basic Information Entity to retrieve key imaging characteristics of the printer + The Printer Configuration Retrieval SOP Instance is created by the SCP during start-up of the hard copy printer and has a well-known SOP Instance UID.
DIMSE Service Group - The DIMSE Services that are applicable to - the IOD are shown in. - + The DIMSE Services that are applicable to the IOD are shown in .
DIMSE Service Group Applicable to Printer Configuration Retrieval
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -28750,46 +20610,33 @@
- The meaning of the Usage SCU/SCP is - described in. - - This Section describes the behavior of the - DIMSE Service that are specific for this IOD. The general behavior of the DIMSE Services is - specified in. - + The meaning of the Usage SCU/SCP is described in . + This Section describes the behavior of the DIMSE Service that are specific for this IOD. The general behavior of the DIMSE Services is specified in .
N-GET - The N-GET is used to retrieve an - instance of the Printer Configuration Retrieval SOP Class. - + The N-GET is used to retrieve an instance of the Printer Configuration Retrieval SOP Class.
Attributes - The Attributes that are retrieved - are shown in. - + The Attributes that are retrieved are shown in .
N-GET Attributes
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Printer - Configuration Sequence - + Printer Configuration Sequence (2000,001E) @@ -28800,9 +20647,7 @@
- >SOP Classes - Supported - + >SOP Classes Supported (0008,115A) @@ -28813,9 +20658,7 @@
- >Maximum Memory - Allocation - + >Maximum Memory Allocation (2000,0061) @@ -28826,9 +20669,7 @@
- >Memory Bit - Depth - + >Memory Bit Depth (2000,00A0) @@ -28839,9 +20680,7 @@
- >Printing Bit - Depth - + >Printing Bit Depth (2000,00A1) @@ -28852,9 +20691,7 @@
- >Media Installed - Sequence - + >Media Installed Sequence (2000,00A2) @@ -28865,9 +20702,7 @@
- >>Item - Number - + >>Item Number (0020,0019) @@ -28878,9 +20713,7 @@
- >>Medium - Type - + >>Medium Type (2000,0030) @@ -28891,9 +20724,7 @@
- >>Film Size - ID - + >>Film Size ID (2010,0050) @@ -28904,25 +20735,19 @@
- >>Min - Density - + >>Min Density (2010,0120) -/MC - Required if - Sequence is Present and Min Density is known - + Required if Sequence is Present and Min Density is known
- >>Max - Density - + >>Max Density (2010,0130) @@ -28933,9 +20758,7 @@
- >Other Media - Available Sequence - + >Other Media Available Sequence (2000,00A4) @@ -28946,9 +20769,7 @@
- >>Medium - Type - + >>Medium Type (2000,0030) @@ -28959,9 +20780,7 @@
- >>Film Size - ID - + >>Film Size ID (2010,0050) @@ -28972,25 +20791,19 @@
- >>Min - Density - + >>Min Density (2010,0120) -/MC - Required if - Sequence is Present and Min Density is known - + Required if Sequence is Present and Min Density is known
- >>Max - Density - + >>Max Density (2010,0130) @@ -29001,9 +20814,7 @@
- >Supported Image - Display Formats Sequence - + >Supported Image Display Formats Sequence (2000,00A8) @@ -29021,33 +20832,24 @@ -/MC - Required if all - Image Boxes in the Display Format have the same number of rows and - columns - + Required if all Image Boxes in the Display Format have the same number of rows and columns
- >>Columns - + >>Columns (0028,0011) -/MC - Required if all - Image Boxes in the Display Format have the same number of rows and - columns - + Required if all Image Boxes in the Display Format have the same number of rows and columns
- >>Image - Display Format - + >>Image Display Format (2010,0010) @@ -29058,9 +20860,7 @@
- >>Film - Orientation - + >>Film Orientation (2010,0040) @@ -29071,9 +20871,7 @@
- >>Film Size - ID - + >>Film Size ID (2010,0050) @@ -29084,9 +20882,7 @@
- >>Printer - Resolution ID - + >>Printer Resolution ID (2010,0052) @@ -29097,9 +20893,7 @@
- >>Printer - Pixel Spacing - + >>Printer Pixel Spacing (2010,0376) @@ -29110,9 +20904,7 @@
- >>Requested - Image Size Flag - + >>Requested Image Size Flag (2020,00A0) @@ -29123,9 +20915,7 @@
- >Default Printer - Resolution ID - + >Default Printer Resolution ID (2010,0054) @@ -29136,9 +20926,7 @@
- >Default - Magnification Type - + >Default Magnification Type (2010,00A6) @@ -29149,9 +20937,7 @@
- >Other - Magnification Types Available - + >Other Magnification Types Available (2010,00A7) @@ -29162,9 +20948,7 @@
- >Default - Smoothing Type - + >Default Smoothing Type (2010,00A8) @@ -29175,9 +20959,7 @@
- >Other Smoothing - Types Available - + >Other Smoothing Types Available (2010,00A9) @@ -29188,9 +20970,7 @@
- >Configuration - Information Description - + >Configuration Information Description (2010,0152) @@ -29201,9 +20981,7 @@
- >Maximum - Collated Films - + >Maximum Collated Films (2010,0154) @@ -29214,9 +20992,7 @@
- >Decimate/Crop - Result - + >Decimate/Crop Result (2020,00A2) @@ -29227,8 +21003,7 @@
- >Manufacturer - + >Manufacturer (0008,0070) @@ -29239,9 +21014,7 @@
- >Manufacturer - Model Name - + >Manufacturer Model Name (0008,1090) @@ -29252,8 +21025,7 @@
- >Printer Name - + >Printer Name (2110,0030) @@ -29264,112 +21036,64 @@
- The meaning of the Usage SCU/SCP is - described in. - + The meaning of the Usage SCU/SCP is described in .
Behavior - The SCU uses the N-GET to request - the SCP to get a Printer Configuration Retrieval SOP Instance. The SCU shall specify in - the N-GET request primitive the UID of the SOP Instance to be retrieved. - - The SCP shall return the values for - the specified Attributes of the specified SOP Instance. - - The SCP shall return the status - code of the requested SOP Instance retrieval. - - A Failure status code shall - indicate that the SCP has not retrieved the SOP Instance. - + The SCU uses the N-GET to request the SCP to get a Printer Configuration Retrieval SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance to be retrieved. + The SCP shall return the values for the specified Attributes of the specified SOP Instance. + The SCP shall return the status code of the requested SOP Instance retrieval. + A Failure status code shall indicate that the SCP has not retrieved the SOP Instance.
Status - There are no specific status codes. - See - - for response status codes. - + There are no specific status codes. See for response status codes.
SOP Class Definition and UID - The Printer Configuration Retrieval SOP - Class UID is "1.2.840.10008.5.1.1.16.376". - + The Printer Configuration Retrieval SOP Class UID is "1.2.840.10008.5.1.1.16.376".
Reserved Identifications - The well-known UID of the Printer - Configuration Retrieval SOP Instance is "1.2.840.10008.5.1.1.17.376". - + The well-known UID of the Printer Configuration Retrieval SOP Instance is "1.2.840.10008.5.1.1.17.376".
Basic Print Image Overlay Box SOP Class(Retired) - This section was previously defined in DICOM. - It is now retired. See PS 3.4-2004. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-2004.
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. The Association negotiation procedure is used to - negotiate the supported SOP Classes or Meta SOP Classes. - - specifies the Association procedures. - - The negotiation procedure is used to negotiate the - supported Meta SOP Classes and the supported optional SOP Classes. The SCU and SCP shall support at - least one Meta SOP Class UID (e.g., Basic Grayscale Print Management Meta SOP Class) and may support - additional optional SOP Classes. - - The Print Management Service Class does not support - extended negotiation. - - The SCU shall specify in the A-ASSOCIATE request - one Abstract Syntax, in a Presentation Context, for each supported SOP Class or Meta SOP Class. - - If the Association is released or aborted then all - the SOP Instances except the Print Job SOP Instance and the Printer SOP Instance are deleted. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure is used to negotiate the supported SOP Classes or Meta SOP Classes. specifies the Association procedures. + The negotiation procedure is used to negotiate the supported Meta SOP Classes and the supported optional SOP Classes. The SCU and SCP shall support at least one Meta SOP Class UID (e.g., Basic Grayscale Print Management Meta SOP Class) and may support additional optional SOP Classes. + The Print Management Service Class does not support Extended Negotiation. + The SCU shall specify in the A-ASSOCIATE request one Abstract Syntax, in a Presentation Context, for each supported SOP Class or Meta SOP Class. + If the Association is released or aborted then all the SOP Instances except the Print Job SOP Instance and the Printer SOP Instance are deleted. - Pending Print Jobs will still be printed after - the release or abortion of the Association. - + Pending Print Jobs will still be printed after the release or abortion of the Association.
Example of Print Management SCU Session (Informative)
Simple Example - Moved to - . - + Moved to .
Advanced Example(Retired) - This section was previously defined in DICOM. - It is now retired. See PS 3.4-1998. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-1998.
Example of the Pull Print Request Meta SOP Class (Informative) - This section was previously defined in DICOM. It is - now retired. See PS 3.4-2004. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-2004.
Overlay Examples (Informative) - This section was previously defined in DICOM. It is - now retired. See PS 3.4-2004. - + This section was previously defined in DICOM. It is now retired. See PS 3.4-2004.
@@ -29378,194 +21102,103 @@ Overview
Scope - The Media Storage Service Class defines an - application-level class-of-service that facilitates the simple transfer of images and associated - information between DICOM AEs by means of Storage Media. It supports: - + The Media Storage Service Class defines an application-level class-of-service that facilitates the simple transfer of images and associated information between DICOM AEs by means of Storage Media. It supports: - The Interchange of images and a wide - range of associated information. - + The Interchange of images and a wide range of associated information.
Service Definition - DICOM AEs support a SOP Class of the Media - Storage Service Class by performing one or more roles among the three roles FSC, FSR or FSU. SOP - Classes of the Media Storage Service Class use the Media Storage Services (M-WRITE, M-READ, - M-DELETE, M-INQUIRE FILE-SET and M-INQUIRE FILE). These Services are defined in. - + DICOM AEs support a SOP Class of the Media Storage Service Class by performing one or more roles among the three roles FSC, FSR or FSU. SOP Classes of the Media Storage Service Class use the Media Storage Services (M-WRITE, M-READ, M-DELETE, M-INQUIRE FILE-SET and M-INQUIRE FILE). These Services are defined in .
Behavior - This Section discusses the FSC, FSR and FSU - behavior for SOP Classes of the Media Storage Service Class. - + This Section discusses the FSC, FSR and FSU behavior for SOP Classes of the Media Storage Service Class.
Behavior of an FSC - The FSC shall be able to create a DICOMDIR File - containing the Media Storage Directory SOP Class for the created File-set and create zero or more - Files belonging to the File-set by invoking M-WRITE Operations with SOP Instances that meet the - requirements of the corresponding IOD. It is the responsibility of the FSC to ensure that the - M-WRITE results in the creation of a correctly formatted DICOM File. The manner in which this is - achieved is beyond the scope of the DICOM Standard. - - The FSC shall support the Media Storage - Operation M-INQUIRE FILE-SET and may optionally support the M-INQUIRE FILE. - + The FSC shall be able to create a DICOMDIR File containing the Media Storage Directory SOP Class for the created File-set and create zero or more Files belonging to the File-set by invoking M-WRITE Operations with SOP Instances that meet the requirements of the corresponding IOD. It is the responsibility of the FSC to ensure that the M-WRITE results in the creation of a correctly formatted DICOM File. The manner in which this is achieved is beyond the scope of the DICOM Standard. + The FSC shall support the Media Storage Operation M-INQUIRE FILE-SET and may optionally support the M-INQUIRE FILE.
Behavior of an FSR - The FSR shall be able to recognize a File-set - and the corresponding DICOMDIR containing the Media Storage Directory SOP Class. A valid File-set - may contain only a DICOMDIR and no other files. If a File-set contains other files with stored SOP - Instance, the FSR shall be capable of invoking M-READ Operations to access the content of the Files - of the File-set. The manner in which this is achieved is beyond the scope of the DICOM Standard. - - The FSR shall support the Media Storage - Operation M-INQUIRE FILE and may optionally support the M-INQUIRE FILE-SET. - + The FSR shall be able to recognize a File-set and the corresponding DICOMDIR containing the Media Storage Directory SOP Class. A valid File-set may contain only a DICOMDIR and no other files. If a File-set contains other files with stored SOP Instance, the FSR shall be capable of invoking M-READ Operations to access the content of the Files of the File-set. The manner in which this is achieved is beyond the scope of the DICOM Standard. + The FSR shall support the Media Storage Operation M-INQUIRE FILE and may optionally support the M-INQUIRE FILE-SET.
Behavior of an FSU - The FSU shall be able to recognize a File-set - and the corresponding DICOMDIR containing the Media Storage Directory SOP Class. A valid File-set - may contain only a DICOMDIR and no other files. If a File-set contains other files with stored SOP - Instances, the FSU shall be capable of invoking M-READ Operations to access the content of the Files - of the File-set. The manner in which this is achieved is beyond the scope of the DICOM Standard. - - The FSU shall support the Media Storage - Operation M-INQUIRE FILE and the M-INQUIRE FILE-SET. - - The FSU shall be able to create one or more new - Files belonging to the File-set by invoking M-WRITE Operations with SOP Instances that meet the - requirements of the corresponding IOD. It is the responsibility of the FSU to ensure that the - M-WRITE results in the creation of a correctly formatted DICOM File. The manner in which this is - achieved is beyond the scope of the DICOM Standard. The FSU shall be able to update the contents of - the DICOMDIR File by using M-DELETE and or M-WRITE Operations. - + The FSU shall be able to recognize a File-set and the corresponding DICOMDIR containing the Media Storage Directory SOP Class. A valid File-set may contain only a DICOMDIR and no other files. If a File-set contains other files with stored SOP Instances, the FSU shall be capable of invoking M-READ Operations to access the content of the Files of the File-set. The manner in which this is achieved is beyond the scope of the DICOM Standard. + The FSU shall support the Media Storage Operation M-INQUIRE FILE and the M-INQUIRE FILE-SET. + The FSU shall be able to create one or more new Files belonging to the File-set by invoking M-WRITE Operations with SOP Instances that meet the requirements of the corresponding IOD. It is the responsibility of the FSU to ensure that the M-WRITE results in the creation of a correctly formatted DICOM File. The manner in which this is achieved is beyond the scope of the DICOM Standard. The FSU shall be able to update the contents of the DICOMDIR File by using M-DELETE and or M-WRITE Operations.
Conformance
Conformance as an FSC - An implementation that conforms to one of the - SOP Classes of the Media Storage Service Class: - + An implementation that conforms to one of the SOP Classes of the Media Storage Service Class: - shall meet the requirements specified - in; - + shall meet the requirements specified in ; - shall meet the requirements specified - in; - + shall meet the requirements specified in ; - shall perform M-WRITE Operations - according to the SOP Class specification identified by the SOP Class UID in the Meta File - Information; - + shall perform M-WRITE Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information; - shall support the Media Storage - Directory SOP Class (stored in the DICOMDIR File). - + shall support the Media Storage Directory SOP Class (stored in the DICOMDIR File).
Conformance as an FSR - An implementation that conforms to one of the - SOP Classes of the Media Storage Service Class: - + An implementation that conforms to one of the SOP Classes of the Media Storage Service Class: - shall meet the requirements specified - in; - + shall meet the requirements specified in ; - shall meet the requirements specified - in; - + shall meet the requirements specified in ; - shall perform M-READ Operations - according to the SOP Class specification identified by the SOP Class UID in the Meta File - Information. M-READ of non-supported SOP Classes shall simply result in ignoring such stored - Data Sets; - + shall perform M-READ Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information. M-READ of non-supported SOP Classes shall simply result in ignoring such stored Data Sets; - shall read DICOMDIR Files without a - Directory Information Module or with a Directory Information Module including Directory - Records of a Type not supported by the implementation. - + shall read DICOMDIR Files without a Directory Information Module or with a Directory Information Module including Directory Records of a Type not supported by the implementation.
Conformance as an FSU - An implementation that conforms to one of the - SOP Classes of the Media Storage Service Class: - + An implementation that conforms to one of the SOP Classes of the Media Storage Service Class: - shall meet the requirements specified - in; - + shall meet the requirements specified in ; - shall meet the requirements specified - in; - + shall meet the requirements specified in ; - shall perform M-READ Operations - according to the SOP Class specification identified by the SOP Class UID in the Meta File - Information. M-READ of unsupported SOP Classes shall simply result in ignoring such stored - Data Sets; - + shall perform M-READ Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information. M-READ of unsupported SOP Classes shall simply result in ignoring such stored Data Sets; - shall perform M-WRITE Operations - according to the SOP Class specification identified by the SOP Class UID in the Meta File - Information; - + shall perform M-WRITE Operations according to the SOP Class specification identified by the SOP Class UID in the Meta File Information; - shall support the Media Storage - Directory SOP Class (stored in the DICOMDIR File). Directories containing a Directory - Information Module shall be updated by an FSU. Directories containing no Directory - Information Module shall not be updated by an FSU; - + shall support the Media Storage Directory SOP Class (stored in the DICOMDIR File). Directories containing a Directory Information Module shall be updated by an FSU. Directories containing no Directory Information Module shall not be updated by an FSU; - shall read DICOMDIR Files without a - Directory Information Module or with a Directory Information Module including Directory - Records of a Type not supported by the implementation. - + shall read DICOMDIR Files without a Directory Information Module or with a Directory Information Module including Directory Records of a Type not supported by the implementation.
Conformance Statement Requirements - An implementation of the Media Storage Service - Class may support one or more Roles as specified in. In addition, - the implementation may conform to one or more of the SOP Classes of the Media Storage Service Class - defined in. The Conformance Statement shall be - in the format defined by - . - + An implementation of the Media Storage Service Class may support one or more Roles as specified in . In addition, the implementation may conform to one or more of the SOP Classes of the Media Storage Service Class defined in . The Conformance Statement shall be in the format defined by . @@ -29587,9 +21220,7 @@
Allowed Combinations of Roles
- With a Directory Information - Module - + With a Directory Information Module Allowed @@ -29598,16 +21229,12 @@ Allowed - Allowed Directory shall be - updated - + Allowed Directory shall be updated
- With no Directory Information - Module - + With no Directory Information Module Allowed @@ -29616,67 +21243,41 @@ Allowed - Allowed Directory shall not be - updated - + Allowed Directory shall not be updated
- The following aspects shall be documented in - the Conformance Statement of any implementation claiming conformance to one of the Media Storage SOP - Classes: - + The following aspects shall be documented in the Conformance Statement of any implementation claiming conformance to one of the Media Storage SOP Classes: - the subset of the Basic Directory - Information Object Model supported; - + the subset of the Basic Directory Information Object Model supported; - When the Directory Information Module - is created or updated (Directory Information Module supported), the optional standard keys - that may be included in Directory Records shall be documented. Private Keys and Private - Records may also be documented; - + When the Directory Information Module is created or updated (Directory Information Module supported), the optional standard keys that may be included in Directory Records shall be documented. Private Keys and Private Records may also be documented;
Standard Extended, Specialized, and Private Conformance - In addition to Standard Media Storage SOP - Classes, implementations may support Standard Extended, Specialized and/or Private SOP Classes as - defined by. - - For all three types of SOP Classes, - implementations shall be permitted to conform as an FSC, FSR, both or as an FSU. The Conformance - Statement shall be in the format defined in. - + In addition to Standard Media Storage SOP Classes, implementations may support Standard Extended, Specialized and/or Private SOP Classes as defined by . + For all three types of SOP Classes, implementations shall be permitted to conform as an FSC, FSR, both or as an FSU. The Conformance Statement shall be in the format defined in .
Media Storage SOP Classes - The SOP Classes in the Media Storage Service Class - identify the Composite IODs to be stored. The IODs of the following SOP Classes can be stored: - + The SOP Classes in the Media Storage Service Class identify the Composite IODs to be stored. The IODs of the following SOP Classes can be stored: - all IODs of the SOP Classes specified for - the DIMSE C-STORE based Storage Service Class identified in - + all IODs of the SOP Classes specified for the DIMSE C-STORE based Storage Service Class identified in - all IODs of the SOP Classes specified for - the DIMSE C-STORE based Non-Patient Object Storage Service Class identified in - + all IODs of the SOP Classes specified for the DIMSE C-STORE based Non-Patient Object Storage Service Class identified in - the IOD of the media directory SOP Class - identified in - + the IOD of the media directory SOP Class identified in @@ -29692,11 +21293,7 @@
- IOD Specification (defined in - ) - + IOD Specification (defined in )
- Media Storage Directory Storage - + Media Storage Directory Storage 1.2.840.10008.1.3.10 @@ -29721,39 +21317,24 @@ - Except for the Media Storage Directory - SOP Class, all the SOP Classes in the Media Storage Service Class are assigned the same UID - Value as the corresponding network communication SOP Classes. This was done to simplify UID - assignment. Although these SOP Classes are based on different Services, the context of their - usage should unambiguously distinguish a SOP Class used for Media Storage from a network - communication SOP Class. - + Except for the Media Storage Directory SOP Class, all the SOP Classes in the Media Storage Service Class are assigned the same UID Value as the corresponding network communication SOP Classes. This was done to simplify UID assignment. Although these SOP Classes are based on different Services, the context of their usage should unambiguously distinguish a SOP Class used for Media Storage from a network communication SOP Class. - The storage of Normalized Print SOP - Instances on media was previously defined in DICOM. They have been retired. See PS 3.4-1998. - + The storage of Normalized Print SOP Instances on media was previously defined in DICOM. They have been retired. See PS 3.4-1998. - The storage of Detached and Standalone - SOP Instances on media was previously defined in DICOM. They have been retired. See PS - 3.4-2004 - + The storage of Detached and Standalone SOP Instances on media was previously defined in DICOM. They have been retired. See PS 3.4-2004
Specialization for Standard SOP Classes (Retired) - See. - + See .
Retired Standard SOP Classes - See. - + See .
@@ -29762,68 +21343,26 @@ Overview
Scope - The mechanism currently defined in DICOM for - network based storage of SOP Instances, the Storage Service Class, allows a Service Class User (SCU) - to transmit images and other Composite SOP Instances to a Service Class Provider (SCP). However, the - Storage Service Class does not specify that the SCP explicitly take responsibility for the - safekeeping of data into account. That is, there is no commitment that the SCP will do more than - accept the transmitted SOP Instances. In order to have medical image management in addition to - medical image communication, there is a need for a Service Class within DICOM that ensures that - there is an explicitly defined commitment to store the SOP Instances. - - The Storage Commitment Service Class defines an - application-level class-of-service that facilitates this commitment to storage. The Storage - Commitment Service Class enables an Application Entity (AE) acting as an SCU to request another - Application Entity (AE) acting as an SCP to make the commitment for the safekeeping of the SOP - Instances (i.e., that the SOP Instances will be kept for an implementation specific period of time - and can be retrieved). The AE where such SOP Instances can later be retrieved may be the SCP where - storage commitment was accepted or it may be distinct from that SCP. - - The SCP implementation defines how it provides - its commitment to storage. Certain SCPs may commit to permanently store the SOP Instances (e.g., an - archive system) while other SCPs may commit to provide storage of the SOP Instances for a limited - amount of time. The SCP is required to document in its Conformance Statement the nature of its - commitment to storage (e.g., duration of storage, retrieve capabilities and latency, capacity). - - The possession of a link to access pixel data - shall not be sufficient for the SCP to commit to storage. A copy of the entire pixel data is - required. - + The mechanism currently defined in DICOM for network based storage of SOP Instances, the Storage Service Class, allows a Service Class User (SCU) to transmit images and other Composite SOP Instances to a Service Class Provider (SCP). However, the Storage Service Class does not specify that the SCP explicitly take responsibility for the safekeeping of data into account. That is, there is no commitment that the SCP will do more than accept the transmitted SOP Instances. In order to have medical image management in addition to medical image communication, there is a need for a Service Class within DICOM that ensures that there is an explicitly defined commitment to store the SOP Instances. + The Storage Commitment Service Class defines an application-level class-of-service that facilitates this commitment to storage. The Storage Commitment Service Class enables an Application Entity (AE) acting as an SCU to request another Application Entity (AE) acting as an SCP to make the commitment for the safekeeping of the SOP Instances (i.e., that the SOP Instances will be kept for an implementation specific period of time and can be retrieved). The AE where such SOP Instances can later be retrieved may be the SCP where storage commitment was accepted or it may be distinct from that SCP. + The SCP implementation defines how it provides its commitment to storage. Certain SCPs may commit to permanently store the SOP Instances (e.g., an archive system) while other SCPs may commit to provide storage of the SOP Instances for a limited amount of time. The SCP is required to document in its Conformance Statement the nature of its commitment to storage (e.g., duration of storage, retrieve capabilities and latency, capacity). + The possession of a link to access pixel data shall not be sufficient for the SCP to commit to storage. A copy of the entire pixel data is required. - This situation may arise in the context of - a JPIP Referenced Pixel Data Transfer Syntax. - + This situation may arise in the context of a JPIP Referenced Pixel Data Transfer Syntax. - Once the SCP has accepted the commitment to - store the SOP Instances, the SCU may decide that it is appropriate to delete its copies of the SOP - Instances. These types of policies are outside the scope of this Standard, however, the SCU is - required to document these policies in its Conformance Statement. - + Once the SCP has accepted the commitment to store the SOP Instances, the SCU may decide that it is appropriate to delete its copies of the SOP Instances. These types of policies are outside the scope of this Standard, however, the SCU is required to document these policies in its Conformance Statement.
Models Overview - The request for storage commitment can be - accomplished using the Push Model. - - The Push model expects an SCU to transmit SOP - Instances to an SCP using an appropriate mechanism outside the scope of this Service Class. Storage - commitment is then initiated by transmitting a Storage Commitment Request containing references to a - set of one or more SOP Instances. Success or failure of storage commitment is subsequently indicated - via a notification from the SCP to the SCU. - + The request for storage commitment can be accomplished using the Push Model. + The Push model expects an SCU to transmit SOP Instances to an SCP using an appropriate mechanism outside the scope of this Service Class. Storage commitment is then initiated by transmitting a Storage Commitment Request containing references to a set of one or more SOP Instances. Success or failure of storage commitment is subsequently indicated via a notification from the SCP to the SCU. - A Pull Model was defined in earlier - versions, but has been retired. See PS 3.4-2001. - + A Pull Model was defined in earlier versions, but has been retired. See PS 3.4-2001. - As indicated, the mechanisms used - to transfer SOP Instances from an SCU to an SCP are outside the scope of this Service - Class. However, typical mechanisms are found in the Storage Service Class, the - Query/Retrieve Service Class, or Media Exchange. - + As indicated, the mechanisms used to transfer SOP Instances from an SCU to an SCP are outside the scope of this Service Class. However, typical mechanisms are found in the Storage Service Class, the Query/Retrieve Service Class, or Media Exchange. @@ -29831,61 +21370,29 @@
Conformance Overview - The application-level services addressed by this - Service Class are specified via the Storage Commitment Push Model SOP Class.: - - An SCP implementation of the Storage Commitment - Service Class shall support the Storage Commitment Push Model SOP Class. - - The SOP Class specifies Attributes, operations, - notifications, and behavior applicable to the SOP Class. The conformance requirements shall be specified - in terms of the Service Class Provider (SCP) and the Service Class User (SCU). - - The Storage Commitment Service Class uses the - Storage Commitment IOD as defined in - - and the N-ACTION and N-EVENT-REPORT DIMSE Services specified in. - + The application-level services addressed by this Service Class are specified via the Storage Commitment Push Model SOP Class.: + An SCP implementation of the Storage Commitment Service Class shall support the Storage Commitment Push Model SOP Class. + The SOP Class specifies Attributes, operations, notifications, and behavior applicable to the SOP Class. The conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU). + The Storage Commitment Service Class uses the Storage Commitment IOD as defined in and the N-ACTION and N-EVENT-REPORT DIMSE Services specified in .
Association Negotiation - Association establishment is the first phase of - any instance of communication between peer DICOM AEs. The Association negotiation rules as specified - in - - shall be used to negotiate the supported SOP Classes. - - Support for the SCP/SCU Role Selection - Negotiation is mandatory. The SOP Class Extended Negotiation shall not be supported. - - An SCP implementation of the Storage Commitment - Service Class shall support the Storage Commitment Push Model SOP Class. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation rules as specified in shall be used to negotiate the supported SOP Classes. + Support for the SCP/SCU Role Selection Negotiation is mandatory. The SOP Class Extended Negotiation shall not be supported. + An SCP implementation of the Storage Commitment Service Class shall support the Storage Commitment Push Model SOP Class.
Storage Commitment Push Model SOP Class - The Storage Commitment Push Model SOP Class is - intended for those Application Entities requiring storage commitment where the SCU determines the time - at which the SOP Instances are transmitted. The SCU transmits the SOP Instances to the SCP using an - appropriate mechanism. The request for storage commitment is transmitted to the SCP together with a list - of references to one or more SOP Instances. Success or failure of storage commitment is subsequently - indicated by a notification from the SCP to the SCU. - + The Storage Commitment Push Model SOP Class is intended for those Application Entities requiring storage commitment where the SCU determines the time at which the SOP Instances are transmitted. The SCU transmits the SOP Instances to the SCP using an appropriate mechanism. The request for storage commitment is transmitted to the SCP together with a list of references to one or more SOP Instances. Success or failure of storage commitment is subsequently indicated by a notification from the SCP to the SCU.
DIMSE Service Group - The DIMSE-N Services applicable to the Storage - Commitment Push Model SOP Class are shown in. - + The DIMSE-N Services applicable to the Storage Commitment Push Model SOP Class are shown in .
DIMSE Service Group Applicable to Storage Commitment Push Model
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -29911,28 +21418,17 @@
- The DIMSE-N Services and Protocol are specified - in. - + The DIMSE-N Services and Protocol are specified in .
Operations - The DICOM AEs that claim conformance to this - SOP Class as an SCU shall invoke the N-ACTION operation. The DICOM AEs that claim conformance to - this SOP Class as an SCP shall support the N-ACTION operation. - + The DICOM AEs that claim conformance to this SOP Class as an SCU shall invoke the N-ACTION operation. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support the N-ACTION operation.
Storage Commitment Request - The Storage Commitment Request operation - allows an SCU to request an SCP to commit to the safekeeping of a set of SOP Instances. This - operation shall be invoked through the N-ACTION primitive. - + The Storage Commitment Request operation allows an SCU to request an SCP to commit to the safekeeping of a set of SOP Instances. This operation shall be invoked through the N-ACTION primitive.
Action Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information - as specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in . @@ -29950,18 +21446,14 @@ Tag
Storage Commitment Request - Action Information
- Requirement Type - SCU/SCP - + Requirement Type SCU/SCP
- Request Storage - Commitment - + Request Storage Commitment 1 @@ -29980,45 +21472,35 @@ - Storage Media File-Set - ID - + Storage Media File-Set ID (0088,0130) 3/3 - See. - + See .
- Storage Media File-Set - UID - + Storage Media File-Set UID (0088,0140) 3/3 - See. - + See .
- Referenced SOP - Sequence - + Referenced SOP Sequence (0008,1199) @@ -30031,9 +21513,7 @@ - >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -30046,214 +21526,112 @@ - >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) 1/1 - See. - + See .
- >Storage Media - File-Set ID - + >Storage Media File-Set ID (0088,0130) 3/3 - See. - + See .
- >Storage Media - File-Set UID - + >Storage Media File-Set UID (0088,0140) 3/3 - See. - + See .
Storage Media File Set ID Attributes - If present, the Storage Media - File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall appear either - outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that - sequence, but not both. If they appear outside of the sequence, then all of the SOP - Instances within the sequence shall be retrievable from the specified Storage Media - File-Set. If they appear within an Item of that sequence, then the SOP Instance - referenced to by that Item shall be retrievable from the specified Storage Media - File-Set. - + If present, the Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall appear either outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that sequence, but not both. If they appear outside of the sequence, then all of the SOP Instances within the sequence shall be retrievable from the specified Storage Media File-Set. If they appear within an Item of that sequence, then the SOP Instance referenced to by that Item shall be retrievable from the specified Storage Media File-Set.
Referenced Performed Procedure Step Sequence Attribute (Retired) - Referenced Performed Procedure Step - Sequence (0008,1111) was included in earlier versions, but its use here has been - retired. See PS 3.4-2001, in which the Attribute was formerly known as Referenced Study - Component Sequence. - + Referenced Performed Procedure Step Sequence (0008,1111) was included in earlier versions, but its use here has been retired. See PS 3.4-2001, in which the Attribute was formerly known as Referenced Study Component Sequence. - This section formerly specified - a means of referencing a Study Component that has been completed and semantics that - the list of images in the commitment request represented a complete set. This - section has been retired since the Modality Performed Procedure Step SOP Classes - provide the same facility in a more appropriate service. - + This section formerly specified a means of referencing a Study Component that has been completed and semantics that the list of images in the commitment request represented a complete set. This section has been retired since the Modality Performed Procedure Step SOP Classes provide the same facility in a more appropriate service.
SOP Instance Reference - A SOP Instance may be referenced - only once within the Referenced SOP Sequence (0008,1199). - + A SOP Instance may be referenced only once within the Referenced SOP Sequence (0008,1199).
Service Class User Behavior - The SCU shall use the N-ACTION - primitive to request the SCP the safekeeping of a set of SOP Instances. The SOP Instances - are referenced in the Action Information as specified in. - The Action Type ID shall be set to 1 specifying the request for storage commitment. - - The SCU shall supply the Transaction - UID (0008,1195) Attribute to uniquely identify each Storage Commitment Request. The value of - the Transaction UID Attribute will be included by the SCP in the Storage Commitment Result - (see). Use of the Transaction UID - Attribute allows the SCU to match requests and results that may occur over the same or - different Associations. - - The N-ACTION primitive shall contain - the well-known Storage Commitment Push Model SOP Instance UID (defined in) in its Requested SOP Instance UID - parameter. - + The SCU shall use the N-ACTION primitive to request the SCP the safekeeping of a set of SOP Instances. The SOP Instances are referenced in the Action Information as specified in . The Action Type ID shall be set to 1 specifying the request for storage commitment. + The SCU shall supply the Transaction UID (0008,1195) Attribute to uniquely identify each Storage Commitment Request. The value of the Transaction UID Attribute will be included by the SCP in the Storage Commitment Result (see ). Use of the Transaction UID Attribute allows the SCU to match requests and results that may occur over the same or different Associations. + The N-ACTION primitive shall contain the well-known Storage Commitment Push Model SOP Instance UID (defined in ) in its Requested SOP Instance UID parameter. - In the usage described here, there - is no explicit creation of a SOP Instance upon which an N-ACTION primitive may operate. - Instead, the N-ACTION primitive operates upon a constant well-known SOP Instance. This - SOP Instance is conceptually created during start up of each Storage Commitment Service - Class SCP Application. - + In the usage described here, there is no explicit creation of a SOP Instance upon which an N-ACTION primitive may operate. Instead, the N-ACTION primitive operates upon a constant well-known SOP Instance. This SOP Instance is conceptually created during start up of each Storage Commitment Service Class SCP Application. - Upon receipt of a successful N-ACTION - Response Status Code from the SCP, the SCU now knows that the SCP has received the N-ACTION - request. Upon receipt of any other N-ACTION Response Status Code from the SCP, the SCU now - knows that the SCP will not process the request and therefore will not commit to the storage - of the SOP Instances referenced by the Storage Commitment Request. The actions taken by the - SCU upon receiving the status is beyond the scope of this Standard. Upon receipt of a - failure status, the Transaction UID is no longer active and shall not be reused for other - transactions. - - At any time after receipt of the - N-ACTION-Response, the SCU may release the association on which it sent the - N-ACTION-Request. - + Upon receipt of a successful N-ACTION Response Status Code from the SCP, the SCU now knows that the SCP has received the N-ACTION request. Upon receipt of any other N-ACTION Response Status Code from the SCP, the SCU now knows that the SCP will not process the request and therefore will not commit to the storage of the SOP Instances referenced by the Storage Commitment Request. The actions taken by the SCU upon receiving the status is beyond the scope of this Standard. Upon receipt of a failure status, the Transaction UID is no longer active and shall not be reused for other transactions. + At any time after receipt of the N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. - Failure of storage - commitment will be signaled via the N-EVENT-REPORT primitive. - + Failure of storage commitment will be signaled via the N-EVENT-REPORT primitive. - In situations where the SOP - Instance(s) are transferred via Media Interchange, the Storage Commitment - Request may fail because the piece of Media containing the referenced SOP - Instance(s) may not yet have been read. Attributes (0088,0130) File-Set ID and - (0088,0140) File-Set UID may or may not be present in the case of Media - Interchange. They may be provided to facilitate identification of the media - containing the transferred SOP Instance(s) by the Storage Commitment SCP. - + In situations where the SOP Instance(s) are transferred via Media Interchange, the Storage Commitment Request may fail because the piece of Media containing the referenced SOP Instance(s) may not yet have been read. Attributes (0088,0130) File-Set ID and (0088,0140) File-Set UID may or may not be present in the case of Media Interchange. They may be provided to facilitate identification of the media containing the transferred SOP Instance(s) by the Storage Commitment SCP.
Service Class Provider Behavior - Upon receipt of the N-ACTION request, - the SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code - applicable to the associated request. A success status conveys that the SCP has successfully - received the request. A failure status conveys that the SCP is not processing the request. - + Upon receipt of the N-ACTION request, the SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated request. A success status conveys that the SCP has successfully received the request. A failure status conveys that the SCP is not processing the request. - Failure of storage - commitment will be signaled via the N-EVENT-REPORT primitive. - + Failure of storage commitment will be signaled via the N-EVENT-REPORT primitive. - When a Storage Commitment - Request is received by an SCP it may immediately assess the list of references - for which Storage Commitment is requested and return an N-EVENT-REPORT. In - situations where the SOP Instance(s) are transferred via Media Interchange, the - N-EVENT-REPORT may fail because the piece of Media containing the referenced SOP - Instance(s) may not yet have been read. Attributes (0088,0130) File-Set ID and - (0088,0140) File-Set UID may or may not be present in the case of Media - Interchange. They may be used to facilitate identification of the media - containing the transferred SOP Instance(s) by the Storage Commitment SCP. - + When a Storage Commitment Request is received by an SCP it may immediately assess the list of references for which Storage Commitment is requested and return an N-EVENT-REPORT. In situations where the SOP Instance(s) are transferred via Media Interchange, the N-EVENT-REPORT may fail because the piece of Media containing the referenced SOP Instance(s) may not yet have been read. Attributes (0088,0130) File-Set ID and (0088,0140) File-Set UID may or may not be present in the case of Media Interchange. They may be used to facilitate identification of the media containing the transferred SOP Instance(s) by the Storage Commitment SCP.
Status Codes - No Service Class specific status values - are defined for the N-ACTION Service. See - - for general response status codes. - + No Service Class specific status values are defined for the N-ACTION Service. See for general response status codes.
Notifications - The DICOM AEs that claim conformance to this - SOP Class as an SCP shall invoke the N-EVENT-REPORT request. The DICOM AEs that claim conformance to - this SOP Class as an SCU shall be capable of receiving the N-EVENT-REPORT request. - + The DICOM AEs that claim conformance to this SOP Class as an SCP shall invoke the N-EVENT-REPORT request. The DICOM AEs that claim conformance to this SOP Class as an SCU shall be capable of receiving the N-EVENT-REPORT request.
Storage Commitment Result - The Storage Commitment Result notification - allows an SCP to inform the SCU whether or not it has accepted storage commitment responsibility - for the SOP Instances referenced by a Storage Commitment Request. This notification is also used - to convey error information (i.e., storage commitment could not be achieved for one or more of - the referenced SOP Instances). This notification shall be invoked through the N-EVENT-REPORT - primitive. - + The Storage Commitment Result notification allows an SCP to inform the SCU whether or not it has accepted storage commitment responsibility for the SOP Instances referenced by a Storage Commitment Request. This notification is also used to convey error information (i.e., storage commitment could not be achieved for one or more of the referenced SOP Instances). This notification shall be invoked through the N-EVENT-REPORT primitive.
Event Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Event Types and Event Information - as specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Event Types and Event Information as specified in . @@ -30271,18 +21649,14 @@ Tag
Storage Commitment Result - Event Information
- Requirement Type - SCU/SCP - + Requirement Type SCU/SCP
- Storage Commitment - Request Successful - + Storage Commitment Request Successful 1 @@ -30301,62 +21675,49 @@ - Retrieve AE Title - + Retrieve AE Title (0008,0054) -/3 - See. - + See .
- Storage Media File-Set - ID - + Storage Media File-Set ID (0088,0130) -/3 - See. - + See .
- Storage Media File-Set - UID - + Storage Media File-Set UID (0088,0140) -/3 - See. - + See .
- Referenced SOP - Sequence - + Referenced SOP Sequence (0008,1199) @@ -30369,9 +21730,7 @@ - >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -30384,9 +21743,7 @@ - >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -30399,60 +21756,47 @@ - >Retrieve AE Title - + >Retrieve AE Title (0008,0054) -/3 - See. - + See .
- >Storage Media - File-Set ID - + >Storage Media File-Set ID (0088,0130) -/3 - See. - + See .
- >Storage Media - File-Set UID - + >Storage Media File-Set UID (0088,0140) -/3 - See. - + See .
- Storage Commitment - Request Complete - Failures Exist - + Storage Commitment Request Complete - Failures Exist 2 @@ -30471,81 +21815,63 @@ - Retrieve AE Title - + Retrieve AE Title (0008,0054) -/3 - See. - + See .
- Storage Media File-Set - ID - + Storage Media File-Set ID (0088,0130) -/3 - See. - + See .
- Storage Media File-Set - UID - + Storage Media File-Set UID (0088,0140) -/3 - See. - + See .
- Referenced SOP - Sequence - + Referenced SOP Sequence (0008,1199) -/1C - This Attribute shall be - provided if storage commitment for one or more SOP Instances has been - successful - + This Attribute shall be provided if storage commitment for one or more SOP Instances has been successful
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -30558,9 +21884,7 @@ - >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -30573,61 +21897,49 @@ - >Retrieve AE Title - + >Retrieve AE Title (0008,0054) -/3 - See. - + See .
- >Storage Media - File-Set ID - + >Storage Media File-Set ID (0088,0130) -/3 - See. - + See .
- >Storage Media - File-Set UID - + >Storage Media File-Set UID (0088,0140) -/3 - See. - + See .
- Failed SOP Sequence - + Failed SOP Sequence (0008,1198) @@ -30640,9 +21952,7 @@ - >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -30655,9 +21965,7 @@ - >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -30670,8 +21978,7 @@ - >Failure Reason - + >Failure Reason (0008,1197) @@ -30684,263 +21991,120 @@
Retrieve AE Title Attribute - If present, the Retrieve AE Title - (0008,0054) shall appear either outside the Referenced SOP Sequence (0008,1199), or - within one or more Items within that sequence, but not both. If they appear outside of - the sequence, then all of the SOP Instances within the sequence shall be retrievable - from the specified Retrieve AE Title. If they appear within an Item of that sequence, - then the SOP Instance referenced to by that Item shall be retrievable from the specified - Retrieve AE Title. - + If present, the Retrieve AE Title (0008,0054) shall appear either outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that sequence, but not both. If they appear outside of the sequence, then all of the SOP Instances within the sequence shall be retrievable from the specified Retrieve AE Title. If they appear within an Item of that sequence, then the SOP Instance referenced to by that Item shall be retrievable from the specified Retrieve AE Title.
Storage Media File Set ID Attributes - If present, the Storage Media - File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall appear either - outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that - sequence, but not both. If they appear outside of the sequence, then all of the SOP - Instances within the sequence shall be retrievable from the specified Storage Media - File-Set. If they appear within an Item of that sequence, then the SOP Instance - referenced to by that Item shall be retrievable from the specified Storage Media - File-Set. - + If present, the Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall appear either outside the Referenced SOP Sequence (0008,1199), or within one or more Items within that sequence, but not both. If they appear outside of the sequence, then all of the SOP Instances within the sequence shall be retrievable from the specified Storage Media File-Set. If they appear within an Item of that sequence, then the SOP Instance referenced to by that Item shall be retrievable from the specified Storage Media File-Set.
Service Class Provider Behavior - If the SCP determines that it has - successfully completed storage commitment for all the SOP Instances referenced by a Storage - Commitment Request, the SCP shall issue an N-EVENT-REPORT with the Event Type ID set to 1 - (storage commitment request successful). This event shall include references to the - successfully stored SOP Instances. The SCP shall store the referenced SOP Instances in - accordance with Level 2 as defined in the Storage Service Class (i.e., all Attributes, - including Private Attributes). The Storage Service Class is defined in. After the - N-EVENT-REPORT has been sent, the Transaction UID is no longer active and shall not be - reused for other transactions. - - If it is determined that storage - commitment could not be achieved for one or more referenced SOP Instances, the SCP shall - issue an N-EVENT-REPORT with the Event Type ID set to 2 (storage commitment request complete - - failure exists) conveying that the SCP does not commit to store all SOP Instances. This - event shall include references to the failed SOP Instances together with references to those - SOP Instances that have been successfully stored. For each failed SOP Instance the reason - for failure shall be described by the Failure Reason Attribute. After the N-EVENT-REPORT has - been sent, the Transaction UID is no longer active and shall not be reused for other - transactions. - - The complete set of SOP Instances - referenced by the Referenced SOP Sequence (0008,1199) Attribute, in the initiating N-ACTION, - shall be present in both Event Types either in the Referenced SOP Sequence (0008,1199) or in - the Failed SOP Sequence (0008,1198). - - The N-EVENT-REPORT shall include the - same Transaction UID (0008,1195) Attribute value as contained in the initiating N-ACTION. - - An SCP shall be capable of issuing the - N-EVENT-REPORT on a different association than the one on which the N-ACTION operation was - performed. - + If the SCP determines that it has successfully completed storage commitment for all the SOP Instances referenced by a Storage Commitment Request, + the SCP shall issue an N-EVENT-REPORT with the Event Type ID set to 1 (Storage Commitment Request Successful). + This event shall include references to the successfully stored SOP Instances. + The SCP shall store the referenced SOP Instances in accordance with Storage Level 2 (Full) as defined in the Storage Service Class (i.e., shall store all Attributes, including Private Attributes). The Storage Service Class is defined in . After the N-EVENT-REPORT has been sent, the Transaction UID is no longer active and shall not be reused for other transactions. + If it is determined that storage commitment could not be achieved for one or more referenced SOP Instances, + the SCP shall issue an N-EVENT-REPORT with the Event Type ID set to 2 (Storage Commitment Request Complete - failure exists) conveying that the SCP does not commit to store all SOP Instances. + This event shall include references to the failed SOP Instances together with references to those SOP Instances that have been successfully stored. For each failed SOP Instance the reason for failure shall be described by the Failure Reason Attribute. + After the N-EVENT-REPORT has been sent, the Transaction UID is no longer active and shall not be reused for other transactions. + The complete set of SOP Instances referenced by the Referenced SOP Sequence (0008,1199) Attribute, in the initiating N-ACTION, shall be present in both Event Types either in the Referenced SOP Sequence (0008,1199) or in the Failed SOP Sequence (0008,1198). + The N-EVENT-REPORT shall include the same Transaction UID (0008,1195) Attribute Value as contained in the initiating N-ACTION. + An SCP shall be capable of issuing the N-EVENT-REPORT on a different association than the one on which the N-ACTION operation was performed. - The SCP may attempt to - issue the N-EVENT-REPORT on the same Association, but this operation may fail - because the SCU is free to release at any time the Association on which it sent - the N-ACTION-Request. As DICOM defaults the association requestor to the SCU - role, the SCP (i.e., the association requester) negotiates an SCP role using the - SCU/SCP Role Selection Negotiation (see - ). - + The SCP may attempt to issue the N-EVENT-REPORT on the same Association, but this operation may fail because the SCU is free to release at any time the Association on which it sent the N-ACTION-Request. As DICOM defaults the association requestor to the SCU role, the SCP (i.e., the association requestor) negotiates an SCP role using the SCU/SCP Role Selection Negotiation (see ). - When responding on a - different Association, the SCP must use the same AE Title as it used on the - original Association, because the DICOM Standard defines a Service between two - peer applications, each identified by an AE Title. Thus the SCP should be - consistently identified for all Associations in the particular instance of the - Storage Commitment Service. - + When responding on a different Association, the SCP must use the same AE Title as it used on the original Association, because the DICOM Standard defines a Service between two peer applications, each identified by an AE Title. Thus the SCP should be consistently identified for all Associations in the particular instance of the Storage Commitment Service. - The optional Attributes - Retrieve AE Title (0008,0054), Storage Media File-Set ID (0088,0130) and Storage - Media File-Set UID (0088,0140) within the Event Information allows an SCP to - indicate the location where it has stored SOP Instances for safekeeping. For - example, the SCP could relay SOP Instances to a third Application Entity using - this Service Class, in which case it can use the Retrieve AE Title Attribute to - indicate the real location of the data. Another example is if the SCP stores - data on media, it can indicate this using the Storage Media File-Set ID and UID - Attributes. - + The optional Attributes Retrieve AE Title (0008,0054), Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) within the Event Information allows an SCP to indicate the location where it has stored SOP Instances for safekeeping. For example, the SCP could relay SOP Instances to a third Application Entity using this Service Class, in which case it can use the Retrieve AE Title Attribute to indicate the real location of the data. Another example is if the SCP stores data on media, it can indicate this using the Storage Media File-Set ID and UID Attributes.
Service Class User Behavior - An SCU shall be capable of receiving an - N-EVENT-REPORT on a different association than the one on which the N-ACTION operation was - performed. - + An SCU shall be capable of receiving an N-EVENT-REPORT on a different association than the one on which the N-ACTION operation was performed. - To receive this N-EVENT-REPORT, the - SCU accepts an association where the SCP role is proposed by the Storage Commitment SCP - acting as an association requestor. - + To receive this N-EVENT-REPORT, the SCU accepts an association where the SCP role is proposed by the Storage Commitment SCP acting as an association requestor. - The SCU shall return, via the - N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the - associated request. The actions taken by the SCU upon receiving the N-EVENT-REPORT are - beyond the scope of this Standard but are stated in its Conformance Statement. - + The SCU shall return, via the N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the associated request. The actions taken by the SCU upon receiving the N-EVENT-REPORT are beyond the scope of this Standard but are stated in its Conformance Statement. - In the case where the SCP indicates - that it cannot achieve storage commitment for some SOP Instances, the SCU might, for - example, re-send the failed SOP Instances to the SCP (via the Storage Service Class) and - then re-transmit the N-ACTION request. However, this behavior is beyond the scope of - this Standard. - + In the case where the SCP indicates that it cannot achieve storage commitment for some SOP Instances, the SCU might, for example, re-send the failed SOP Instances to the SCP (via the Storage Service Class) and then re-transmit the N-ACTION request. However, this behavior is beyond the scope of this Standard.
Status Codes - No Service Class specific status values - are defined for the N-EVENT-REPORT Service. See - - for general response status codes. - + No Service Class specific status values are defined for the N-EVENT-REPORT Service. See for general response status codes. - This Section refers to status codes - returned by the N-EVENT-REPORT response primitive. The Failure Reason Attribute returned - in the Storage Commitment Result - Event Information (see - ) are described in the Storage Commitment IOD. - + This Section refers to status codes returned by the N-EVENT-REPORT response primitive. The Failure Reason Attribute returned in the Storage Commitment Result - Event Information (see ) are described in the Storage Commitment IOD.
Storage Commitment Push Model SOP Class UID - The Storage Commitment Push Model SOP Class - shall be uniquely identified by the Storage Commitment Push Model SOP Class UID, which shall have - the value "1.2.840.10008.1.20.1". - + The Storage Commitment Push Model SOP Class shall be uniquely identified by the Storage Commitment Push Model SOP Class UID, which shall have the value "1.2.840.10008.1.20.1".
Storage Commitment Push Model Reserved Identification - The well-known UID of the Storage Commitment - Push Model SOP Instance shall have the value "1.2.840.10008.1.20.1.1". - + The well-known UID of the Storage Commitment Push Model SOP Instance shall have the value "1.2.840.10008.1.20.1.1".
Conformance Requirements - Implementations claiming Standard SOP Class - Conformance to the Storage Commitment Push Model SOP Class shall be conformant as described in this - Section and shall include within their Conformance Statement information as described in this - Section and sub-Sections. - - An implementation may claim conformance to this - SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in. - + Implementations claiming Standard SOP Class Conformance to the Storage Commitment Push Model SOP Class shall be conformant as described in this Section and shall include within their Conformance Statement information as described in this Section and sub-Sections. + An implementation may claim conformance to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to - this SOP Class as an SCU shall meet conformance requirements for - + An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for - the operations and actions that it - invokes - + the operations and actions that it invokes - the notifications that it - receives. - + the notifications that it receives. - The mechanisms used by the SCU to transfer - SOP Instances to the SCP shall be documented. - + The mechanisms used by the SCU to transfer SOP Instances to the SCP shall be documented.
Operations - The SCU shall document in the SCU - Operations Statement the actions and behavior that cause the SCU to generate an N-ACTION - primitive (Storage Commitment Request). - - The SCU shall specify the SOP Class - UIDs for which it may request storage commitment. - - The SCU shall specify the duration of - applicability of the Transaction UID. This may be specified as a time limit or a policy that - defines the end of a transaction (e.g., how long will the SCU wait for a N-EVENT-REPORT). - - The SCU shall specify if it supports - the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these - Attributes are supported, the SCU shall also specify which Storage Media Application - Profiles are supported. - - The SCU Operations Statement shall be - formatted as defined in - + The SCU shall document in the SCU Operations Statement the actions and behavior that cause the SCU to generate an N-ACTION primitive (Storage Commitment Request). + The SCU shall specify the SOP Class UIDs for which it may request storage commitment. + The SCU shall specify the duration of applicability of the Transaction UID. This may be specified as a time limit or a policy that defines the end of a transaction (e.g., how long will the SCU wait for a N-EVENT-REPORT). + The SCU shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these Attributes are supported, the SCU shall also specify which Storage Media Application Profiles are supported. + The SCU Operations Statement shall be formatted as defined in
Notifications. - The SCU shall document in the SCU - Notifications Statement the behavior and actions taken by the SCU upon receiving an - N-EVENT-REPORT primitive (Storage Commitment Result). - - The SCU shall specify the behavior and - actions performed when a success status is received (i.e., if and when local SOP Instances - copies are deleted). - - The SCU shall specify the behavior and - actions performed when a failure status is received (i.e., recovery mechanisms, etc.). - - The SCU Notifications Statement shall - be formatted as defined in - + The SCU shall document in the SCU Notifications Statement the behavior and actions taken by the SCU upon receiving an N-EVENT-REPORT primitive (Storage Commitment Result). + The SCU shall specify the behavior and actions performed when a success status is received (i.e., if and when local SOP Instances copies are deleted). + The SCU shall specify the behavior and actions performed when a failure status is received (i.e., recovery mechanisms, etc.). + The SCU Notifications Statement shall be formatted as defined in
SCP Conformance. - An implementation that is conformant to - this SOP Class as an SCP shall meet conformance requirements for - + An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for - the operations and actions that it - performs - + the operations and actions that it performs - the notifications that it - generates. - + the notifications that it generates.
Operations - The SCP shall document in the SCP - Operations Statement the behavior and actions of the SCP upon receiving the N-ACTION - primitive (Storage Commitment Request). - - The SCP shall specify parameters - indicating the level of storage commitment, such as: - + The SCP shall document in the SCP Operations Statement the behavior and actions of the SCP upon receiving the N-ACTION primitive (Storage Commitment Request). + The SCP shall specify parameters indicating the level of storage commitment, such as: - under what conditions the SCP - would delete SOP Instances - + under what conditions the SCP would delete SOP Instances persistence of storage @@ -30952,55 +22116,31 @@ volatility - other pertinent information - + other pertinent information - The SCP shall specify the mechanisms - and characteristics of retrieval of stored SOP Instances, such as: - + The SCP shall specify the mechanisms and characteristics of retrieval of stored SOP Instances, such as: - supported query/retrieve - services - + supported query/retrieve services latency - other pertinent information - + other pertinent information - The SCP shall specify if it supports - the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these - Attributes are supported, the SCP shall also specify which Storage Media Application - Profiles are supported. - - The SCP Operations Statement shall be - formatted as defined in - + The SCP shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-ACTION. If these Attributes are supported, the SCP shall also specify which Storage Media Application Profiles are supported. + The SCP Operations Statement shall be formatted as defined in
Notifications - The SCP shall document in the SCP - Notifications Statement the behavior and actions that cause the SCP to generate an - N-EVENT-REPORT primitive (Storage Commitment Result). - - The SCP shall specify if it supports - the optional Storage Media File-Set ID & UID Attributes in the N-EVENT-REPORT and - describe the policies for how the Media is used. The SCP shall also specify which Storage - Media Application Profiles are supported. - - The SCP shall specify if it supports - the optional Retrieve AE Title (0008,0054) Attribute in the N-EVENT-REPORT and describe the - policies for how it is used. - - The SCP Notifications Statement shall - be formatted as defined in - + The SCP shall document in the SCP Notifications Statement the behavior and actions that cause the SCP to generate an N-EVENT-REPORT primitive (Storage Commitment Result). + The SCP shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-EVENT-REPORT and describe the policies for how the Media is used. The SCP shall also specify which Storage Media Application Profiles are supported. + The SCP shall specify if it supports the optional Retrieve AE Title (0008,0054) Attribute in the N-EVENT-REPORT and describe the policies for how it is used. + The SCP Notifications Statement shall be formatted as defined in
@@ -31008,14 +22148,11 @@
Storage Commitment Pull Model SOP Class(Retired) - A Pull Model was defined in earlier versions, but - has been retired. See PS 3.4-2001. - + A Pull Model was defined in earlier versions, but has been retired. See PS 3.4-2001.
Storage Commitment Examples (Informative) - Moved to - + Moved to
@@ -31025,152 +22162,70 @@ Overview
Scope - The Basic Worklist Management Service Class - defines an application-level class-of-service that facilitates the access to worklists. - - A worklist is the structure to present - information related to a particular set of tasks. It specifies particular details for each task. The - information supports the selection of the task to be performed first, and supports the performance - of that task. - + The Basic Worklist Management Service Class defines an application-level class-of-service that facilitates the access to worklists. + A worklist is the structure to present information related to a particular set of tasks. It specifies particular details for each task. The information supports the selection of the task to be performed first, and supports the performance of that task. - One example is the worklist used to present - information about scheduled imaging procedures at an imaging modality and to the operator of - that modality. Another example is the worklist presented at a radiological reporting station to - indicate which studies have been performed and are waiting to be reported. - + One example is the worklist used to present information about scheduled imaging procedures at an imaging modality and to the operator of that modality. Another example is the worklist presented at a radiological reporting station to indicate which studies have been performed and are waiting to be reported. - This annex defines a service for communicating - such worklists. The following are characteristics for this Service Class: - + This annex defines a service for communicating such worklists. The following are characteristics for this Service Class: - The worklist has to be queried by the - Application Entity (AE) associated with the application on which, or by which, the tasks - included in the worklist have to be performed. In this query, a number of search keys can be - used, defined for each particular worklist SOP Class. - + The worklist has to be queried by the Application Entity (AE) associated with the application on which, or by which, the tasks included in the worklist have to be performed. In this query, a number of search keys can be used, defined for each particular worklist SOP Class. - The worklist consists of worklist - items, each item is related to one task. A worklist item contains Attributes from different - objects related to the task. - + The worklist consists of worklist items, each item is related to one task. A worklist item contains Attributes from different objects related to the task. - This Service Class is not intended - to provide a comprehensive generalized database query mechanism such as SQL. Instead, - the Basic Worklist Management Service Class is focused towards basic queries using a - small set of common Key Attributes used as Matching Keys or Return Attributes. Basic - Worklist Information Models are not hierarchical. - + This Service Class is not intended to provide a comprehensive generalized database query mechanism such as SQL. Instead, the Basic Worklist Management Service Class is focused towards basic queries using a small set of common Key Attributes used as Matching Keys or Return Attributes. Basic Worklist Information Models are not hierarchical. - Basic Worklist Information Models - always consist of one query level, which may consist of one or more entities. There is - no distinction between hierarchical and relational use of C-Find in the Basic Worklist - Management Service Class. - + Basic Worklist Information Models always consist of one query level, which may consist of one or more entities. There is no distinction between hierarchical and relational use of C-Find in the Basic Worklist Management Service Class.
Conventions - Key Attributes serve two purposes, they may be - used as: Matching Key Attributes and Return Key Attributes. Matching Key Attributes may be used for - matching (criteria to be used in the C-FIND request to determine whether an entity matches the - query). Return Key Attributes may be used to specify desired return Attributes (what elements in - addition to the Matching Key Attributes have to be returned in the C-FIND response). - + Key Attributes serve two purposes, they may be used as: Matching Key Attributes and Return Key Attributes. Matching Key Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether an entity matches the query). Return Key Attributes may be used to specify desired return Attributes (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND response). - Matching Keys are typically used in an SQL - 'where' clause. Return Keys are typically used in an SQL 'select' clause to convey the Attribute - Values. - + Matching Keys are typically used in an SQL 'where' clause. Return Keys are typically used in an SQL 'select' clause to convey the Attribute Values. - Matching Key Attributes may be of Type - "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in - . - + Matching Key Attributes may be of Type "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in .
Worklist Information Model - In order to serve as a Service Class Provider - (SCP) of the Basic Worklist Service Class, a DICOM Application Entity (AE) possesses information - about the Attributes of a number of managed worklist entries. This information is organized into - Worklist Information Models. - - Worklists are implemented against well defined - Information Models. A specific SOP Class of the Basic Worklist Service Class consists of an - informative Overview, an Information Model Definition and a DIMSE-C Service Group. In this Service - Class, the Information Model plays a role similar to an Information Object Definition (IOD) of most - other DICOM Service Classes. - + In order to serve as a Service Class Provider (SCP) of the Basic Worklist Service Class, a DICOM Application Entity (AE) possesses information about the Attributes of a number of managed worklist entries. This information is organized into Worklist Information Models. + Worklists are implemented against well defined Information Models. A specific SOP Class of the Basic Worklist Service Class consists of an informative Overview, an Information Model Definition and a DIMSE-C Service Group. In this Service Class, the Information Model plays a role similar to an Information Object Definition (IOD) of most other DICOM Service Classes.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Basic Worklist Service Class with one serving in the SCU role and one serving in the SCP role. SOP - Classes of the Basic Worklist Service Class are implemented using the DIMSE-C C-FIND service as - defined in. - - Both a baseline and extended behavior are - defined for the DIMSE-C C-FIND. Baseline behavior specifies a minimum level of conformance for all - implementations to facilitate interoperability. Extended behavior enhances the baseline behavior to - provide additional features that may be negotiated independently at Association establishment time. - - The following description of the DIMSE-C C-FIND - service provides a brief overview of the SCU/SCP semantics. - - A C-FIND service conveys the following - semantics: - + Two peer DICOM AEs implement a SOP Class of the Basic Worklist Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Basic Worklist Service Class are implemented using the DIMSE-C C-FIND service as defined in . + Both a baseline and extended behavior are defined for the DIMSE-C C-FIND. Baseline behavior specifies a minimum level of conformance for all implementations to facilitate interoperability. Extended behavior enhances the baseline behavior to provide additional features that may be negotiated independently at Association establishment time. + The following description of the DIMSE-C C-FIND service provides a brief overview of the SCU/SCP semantics. + A C-FIND service conveys the following semantics: - The SCU requests that the SCP perform a - match for the Matching Keys and return values for the Return Keys that have been specified - in the Identifier of the request, against the information that the SCP possesses, to the - objects specified in the SOP Class. - + The SCU requests that the SCP perform a match for the Matching Keys and return values for the Return Keys that have been specified in the Identifier of the request, against the information that the SCP possesses, to the objects specified in the SOP Class. - In this Annex, the term - "Identifier" refers to the Identifier service parameter of the C-FIND service as defined - in. - + In this Annex, the term "Identifier" refers to the Identifier service parameter of the C-FIND service as defined in . - The SCP generates a C-FIND response for - each match with an Identifier containing the values of all Matching Key Attributes and all - known Return Key Attributes requested. Each response contains one worklist item. All such - responses will contain a status of Pending. A status of Pending indicates that the process - of matching is not complete. - + The SCP generates a C-FIND response for each match with an Identifier containing the values of all Matching Key Attributes and all known Return Key Attributes requested. Each response contains one worklist item. All such responses will contain a status of Pending. A status of Pending indicates that the process of matching is not complete. - When the process of matching is - complete a C-FIND response is sent with a status of Success and no Identifier. - + When the process of matching is complete a C-FIND response is sent with a status of Success and no Identifier. - A Refused or Failed response to a - C-FIND request indicates that the SCP is unable to process the request. - + A Refused or Failed response to a C-FIND request indicates that the SCP is unable to process the request. - The SCU may cancel the C-FIND service - by issuing a C-CANCEL-FIND request at any time during the processing of the C-FIND service. - The SCP will interrupt all matching and return a status of Canceled. - + The SCU may cancel the C-FIND service by issuing a C-CANCEL-FIND request at any time during the processing of the C-FIND service. The SCP will interrupt all matching and return a status of Canceled. - The SCU needs to be prepared to - receive C-FIND responses sent by the SCP until the SCP finally processed the - C-CANCEL-FIND request. - + The SCU needs to be prepared to receive C-FIND responses sent by the SCP until the SCP finally processed the C-CANCEL-FIND request. @@ -31178,18 +22233,11 @@
Worklist Information Model Definition - The Worklist Information Model is identified by the - SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information - Model and a DIMSE-C Service Group. - - Information Model Definitions for Standard SOP - Classes of the Worklist Service Class are defined in this Annex. A Worklist Information Model Definition - contains: - + The Worklist Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + Information Model Definitions for Standard SOP Classes of the Worklist Service Class are defined in this Annex. A Worklist Information Model Definition contains: - an Entity-Relationship Model Definition - + an Entity-Relationship Model Definition a Key Attributes Definition; @@ -31197,101 +22245,51 @@
Entity-Relationship Model Definition - Basic Worklist Information Models consist of a - single level, that includes all Matching Key Attributes and all Return Key Attributes, which may be - sent from the SCU to the SCP in the request and whose values are expected to be returned from the - SCP to the SCU in each of the responses (or worklist items). The Matching Key Attribute Values in - the request specify the worklist items that are to be returned in the responses. All Key Attributes - (the Matching Key Attributes and the Return Key Attributes) in the request determine which Attribute - Values are returned in the responses for that worklist. - - A Worklist Item has a one-to-one relationship - with the real-world object defining the root for the Basic Worklist Information Model. In addition - the worklist item is related to a number of other objects from the real-world model. Each of these - real-world objects is represented by a hierarchy of entities organized in an (internal) - Entity-Relationship Model. - + Basic Worklist Information Models consist of a single level, that includes all Matching Key Attributes and all Return Key Attributes, which may be sent from the SCU to the SCP in the request and whose values are expected to be returned from the SCP to the SCU in each of the responses (or worklist items). The Matching Key Attribute Values in the request specify the worklist items that are to be returned in the responses. All Key Attributes (the Matching Key Attributes and the Return Key Attributes) in the request determine which Attribute Values are returned in the responses for that worklist. + A Worklist Item has a one-to-one relationship with the real-world object defining the root for the Basic Worklist Information Model. In addition the worklist item is related to a number of other objects from the real-world model. Each of these real-world objects is represented by a hierarchy of entities organized in an (internal) Entity-Relationship Model.
Attributes Definition - Attributes are defined for each entity in the - internal Entity-Relationship Model. An Identifier in a C-FIND request shall contain values to be - matched against the Attributes of the Entities in a Worklist Information Model. For any worklist - request, the set of entities for which Attributes are returned, shall be determined by the set of - Matching and Return Key Attributes specified in the Identifier. - + Attributes are defined for each entity in the internal Entity-Relationship Model. An Identifier in a C-FIND request shall contain values to be matched against the Attributes of the Entities in a Worklist Information Model. For any worklist request, the set of entities for which Attributes are returned, shall be determined by the set of Matching and Return Key Attributes specified in the Identifier.
Attribute Types - All Attributes of entities in a Worklist - Information Model shall be specified both as a Matching Key Attribute (either required or - optional) and as a Return Key Attribute. - + All Attributes of entities in a Worklist Information Model shall be specified both as a Matching Key Attribute (either required or optional) and as a Return Key Attribute.
Matching Key Attributes - The Matching Key Attributes are Keys, - which select worklist items to be included in a requested Worklist. - + The Matching Key Attributes are Keys, which select worklist items to be included in a requested Worklist.
Required Matching Key Attributes - A Basic Worklist Management SCP - shall support matching based on values of all Required Matching Key Attributes of the - C-FIND request. Multiple entities may match a given value for a Required Key. - - If an SCP manages an entity with an - unknown Attribute Value (i.e., zero length), the unknown value shall fail to match any - Matching Key value. - + An SCP of one of the SOP Classes of the Basic Worklist Management Service Class shall support matching based on values of all Required Matching Key Attributes of the C-FIND request. Multiple entities may match a given value for a Required Key. + If an SCP manages an entity with an unknown Attribute Value (i.e., zero length), the unknown value shall fail to match any Matching Key value. - Even though there is no - means to perform matching on such entities, they may be queried as a Return - Key Attribute using a C-FIND request with a zero length value (Universal - Match) or by a single wild card (Wild Card Match). - + Even though there is no means to perform matching on such entities, they may be queried as a Return Key Attribute using a C-FIND request with a zero length value (Universal Match) or by a single wild card (Wild Card Match). - An SCU may choose to - supply any subset of Required Matching Key Attributes. - + An SCU may choose to supply any subset of Required Matching Key Attributes.
Optional Matching Key Attributes - In the Worklist Information Model, - a set of Attributes may be defined as Optional Matching Key Attributes. Optional - Matching Key Attributes contained in the Identifier of a C-FIND request may induce two - different types of behavior depending on support for matching by the SCP. If the SCP - + In the Worklist Information Model, a set of Attributes may be defined as Optional Matching Key Attributes. Optional Matching Key Attributes contained in the Identifier of a C-FIND request may induce two different types of behavior depending on support for matching by the SCP. If the SCP - does not support matching - on the Optional Matching Key Attribute, then the Optional Matching Key Attribute - shall be ignored for matching but shall be processed in the same manner as a - Return Key Attribute. - + does not support matching on the Optional Matching Key Attribute, then the Optional Matching Key Attribute shall be ignored for matching but shall be processed in the same manner as a Return Key Attribute. - supports matching of the - Optional Matching Key Attribute, then the Optional Matching Key Attribute shall - be processed in the same manner as a Required Matching Key. - + supports matching of the Optional Matching Key Attribute, then the Optional Matching Key Attribute shall be processed in the same manner as a Required Matching Key. - The Conformance - Statement of the SCP lists the Optional Matching Key Attributes that are - supported for matching. - + The Conformance Statement of the SCP lists the Optional Matching Key Attributes that are supported for matching. - An SCU can not expect - the SCP to support a match on an Optional Matching Key. - + An SCU cannot expect the SCP to support a match on an Optional Matching Key. @@ -31299,39 +22297,21 @@
Return Key Attributes - The values of Return Key Attributes to - be retrieved with the Worklist are specified with zero-length (Universal Matching) in the - C-FIND request. SCPs shall support Return Key Attributes defined by a Worklist Information - Model according to the Data Element Type (1, 1C, 2, 2C, 3) as defined in. - - Every Matching Key Attribute shall also - be considered as a Return Key Attribute. Therefore the C-FIND response shall contain in - addition to the values of the requested Return Key Attributes the values of the requested - Matching Key Attributes. - + The values of Return Key Attributes to be retrieved with the Worklist are specified with zero-length (Universal Matching) in the C-FIND request. SCPs shall support Return Key Attributes defined by a Worklist Information Model according to the Data Element Type (1, 1C, 2, 2C, 3) as defined in . + Every Matching Key Attribute shall also be considered as a Return Key Attribute. Therefore the C-FIND response shall contain in addition to the values of the requested Return Key Attributes the values of the requested Matching Key Attributes. - The Conformance Statement - of the SCP lists the Return Key Attributes of Type 3, which are supported. - + The Conformance Statement of the SCP lists the Return Key Attributes of Type 3, which are supported. - An SCU may choose to supply - any subset of Return Key Attributes. - + An SCU may choose to supply any subset of Return Key Attributes. - An SCU can not expect to - receive any Type 3 Return Key Attributes. - + An SCU can not expect to receive any Type 3 Return Key Attributes. - Return Key Attributes with - VR of SQ may be specified either with zero-length or with the zero-length item - in the sequence. - + Return Key Attributes with VR of SQ may be specified either with zero-length or with the zero-length item in the sequence. @@ -31339,15 +22319,7 @@
Attribute Matching - The following types of matching, which are - defined by the Query/Retrieve Service Class in - - may be performed on Matching Key Attributes in the Basic Worklist Service Class. Different - Matching Key Attributes may be subject for different matching types. The Worklist Information - Model defines the type of matching for each Required Matching Key Attribute. The Conformance - Statement of the SCP shall define the type of matching for each Optional Matching Key Attribute. - The types of matching are: - + The following types of matching, which are defined by the Query/Retrieve Service Class in may be performed on Matching Key Attributes in the Basic Worklist Service Class. Different Matching Key Attributes may be subject for different matching types. The Worklist Information Model defines the type of matching for each Required Matching Key Attribute. The Conformance Statement of the SCP shall define the type of matching for each Optional Matching Key Attribute. The types of matching are: Single Value Matching @@ -31365,44 +22337,25 @@ Sequence Matching - The following type of matching, which is - defined by the Query/Retrieve Service Class in - - of this Part shall be performed on Return Key Attributes in the Basic Worklist Service Class. - + The following type of matching, which is defined by the Query/Retrieve Service Class in of this Part shall be performed on Return Key Attributes in the Basic Worklist Service Class. Universal Matching - See - - and subsections for specific rules governing of Matching Key Attribute encoding for and - performing of different types of matching. - - The Specific Character Set (0008,0005) - Attribute and/or the Timezone Offset From UTC (0008,0201) Attribute may be present in the - Identifier but are never matched, i.e., they are not considered Matching Key Attributes. See - - for details. - - Single value matching of Attributes with a - VR of PN may be affected by extended negotiation of fuzzy semantic matching of person names. - + See and subsections for specific rules governing of Matching Key Attribute encoding for and performing of different types of matching. + The Specific Character Set (0008,0005) Attribute and/or the Timezone Offset From UTC (0008,0201) Attribute may be present in the Identifier but are never matched, i.e., they are not considered Matching Key Attributes. See for details. + Single value matching of Attributes with a VR of PN may be affected by Extended Negotiation of fuzzy semantic matching of person names.
Matching Multiple Values - When matching an Attribute that has a value - multiplicity of greater than one, if any of the values match, then all values shall be returned. - + When matching an Attribute that has a value multiplicity of greater than one, if any of the values match, then all values shall be returned.
Worklist Information Model - Each Worklist Information Model is associated with - one SOP Class. The following Worklist Information Model is defined: - + Each Worklist Information Model is associated with one SOP Class. The following Worklist Information Model is defined: Modality Worklist Information Model @@ -31411,9 +22364,7 @@
DIMSE-C Service Group - One DIMSE-C Service is used in the construction of - SOP Classes of the Basic Worklist Management Service Class. The following DIMSE-C operation is used. - + One DIMSE-C Service is used in the construction of SOP Classes of the Basic Worklist Management Service Class. The following DIMSE-C operation is used. C-FIND @@ -31421,128 +22372,59 @@
C-FIND Operation - SCPs of some SOP Classes of the Basic Worklist - Management Service Class are capable of processing queries using the C-FIND operation as described - in. The C-FIND operation - is the mechanism by which queries are performed. Matches against the keys present in the Identifier - are returned in C-FIND responses. - + SCPs of some SOP Classes of the Basic Worklist Management Service Class are capable of processing queries using the C-FIND operation as described in . The C-FIND operation is the mechanism by which queries are performed. Matches against the keys present in the Identifier are returned in C-FIND responses.
C-FIND Service Parameters
SOP Class UID - The SOP Class UID identifies the - Worklist Information Model against which the C-FIND is to be performed. Support for the SOP - Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this - C-FIND operation. - + The SOP Class UID identifies the Worklist Information Model against which the C-FIND is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-FIND operation.
Priority - The Priority Attribute defines the - requested priority of the C-FIND operation with respect to other DIMSE operations being - performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. - + The Priority Attribute defines the requested priority of the C-FIND operation with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP.
Identifier - Both the C-FIND request and response - contain an Identifier encoded as a Data Set (see). - + Both the C-FIND request and response contain an Identifier encoded as a Data Set (see ).
Request Identifier Structure - An Identifier in a C-FIND request - shall contain - + An Identifier in a C-FIND request shall contain - Key Attributes values to be - matched against the values of Attributes specified in that SOP Class. - + Key Attributes values to be matched against the values of Attributes specified in that SOP Class. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Request Identifier. It shall not be included otherwise. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Request Identifier. It shall not be included otherwise. - This means that - Specific Character Set (0008,0005) is included if the SCU supports expanded - or replacement character sets in the context of this service. It will not be - included if expanded or replacement character sets are not supported by the - SCU. - + This means that Specific Character Set (0008,0005) is included if the SCU supports expanded or replacement character sets in the context of this service. It will not be included if expanded or replacement character sets are not supported by the SCU. - Conditionally, the - Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included - if Key Attributes of time are to be interpreted explicitly in the designated - local time zone. It shall not be present otherwise, i.e., it shall not be sent - with a zero-length value. - + Conditionally, the Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included if Key Attributes of time are to be interpreted explicitly in the designated local time zone. It shall not be present otherwise, i.e., it shall not be sent with a zero-length value. - The Key Attributes and values - allowable for the query shall be defined in the SOP Class definition for the - corresponding Worklist Information Model. - + The Key Attributes and values allowable for the query shall be defined in the SOP Class definition for the corresponding Worklist Information Model.
Response Identifier Structure - The C-FIND response shall not - contain Attributes that were not in the request or specified in this section. - - An Identifier in a C-FIND response - shall contain: - + The C-FIND response shall not contain Attributes that were not in the request or specified in this section. + An Identifier in a C-FIND response shall contain: - Key Attributes with values - corresponding to Key Attributes contained in the Identifier of the request (Key - Attributes as defined in - .) - + Key Attributes with values corresponding to Key Attributes contained in the Identifier of the request (Key Attributes as defined in .) - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Response Identifier. It shall not be included otherwise. The C-FIND SCP - is not required to return responses in the Specific Character Set requested by - the SCU if that character set is not supported by the SCP. The SCP may return - responses with a different Specific Character Set. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Response Identifier. It shall not be included otherwise. The C-FIND SCP is not required to return responses in the Specific Character Set requested by the SCU if that character set is not supported by the SCP. The SCP may return responses with a different Specific Character Set. - This means that - Specific Character Set (0008,0005) is included if the SCP supports expanded - or replacement character sets in the context of this service. It will not be - included if expanded or replacement character sets are not supported by the - SCP. - + This means that Specific Character Set (0008,0005) is included if the SCP supports expanded or replacement character sets in the context of this service. It will not be included if expanded or replacement character sets are not supported by the SCP. - Conditionally, the - Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included - if any Attributes of time in the Response Identifier are to be interpreted - explicitly in the designated local time zone. It shall not be present otherwise, - i.e., it shall not be sent with a zero-length value. - + Conditionally, the Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included if any Attributes of time in the Response Identifier are to be interpreted explicitly in the designated local time zone. It shall not be present otherwise, i.e., it shall not be sent with a zero-length value. - Conditionally, the - Attribute HL7 Structured Document Reference Sequence (0040,A390) and its - subsidiary Sequence Items. This Attribute shall be included if HL7 Structured - Documents are referenced within the Identifier, e.g., in the Pertinent Documents - Sequence (0038,0100). - + Conditionally, the Attribute HL7 Structured Document Reference Sequence (0040,A390) and its subsidiary Sequence Items. This Attribute shall be included if HL7 Structured Documents are referenced within the Identifier, e.g., in the Pertinent Documents Sequence (0038,0100).
@@ -31550,11 +22432,7 @@
Status - - defines the status code values that might be returned in a C-FIND response. General status - code values and fields related to status code values are defined for C-FIND DIMSE Service in - . - + defines the status code values that might be returned in a C-FIND response. General status code values and fields related to status code values are defined for C-FIND DIMSE Service in . @@ -31579,9 +22457,7 @@ Failure
C-FIND Response Status Values
- Refused: Out of - resources - + Refused: Out of resources A700 @@ -31592,9 +22468,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -31606,9 +22480,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -31623,9 +22495,7 @@ Cancel - Matching terminated due - to Cancel request - + Matching terminated due to Cancel request FE00 @@ -31639,9 +22509,7 @@ Success - Matching is complete - - No final Identifier is supplied. - + Matching is complete - No final Identifier is supplied. 0000 @@ -31655,10 +22523,7 @@ Pending - Matches are continuing - - Current Match is supplied and any Optional Keys were supported in the same - manner as Required Keys. - + Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF00 @@ -31669,10 +22534,7 @@
- Matches are continuing - - Warning that one or more Optional Keys were not supported for existence - for this Identifier. - + Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier. FF01 @@ -31684,190 +22546,92 @@
- Status Codes are returned in DIMSE - response messages (see). The code values stated - in column "Status Codes" are returned in Status Command Element (0000,0900). - + Status Codes are returned in DIMSE response messages (see ). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900). - Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: - Unable to process” Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: Unable to process” Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
C-FIND SCU Behavior - All C-FIND SCUs shall be capable of - generating query requests that meet the requirements of the "Worklist" Search Method (see). - - Required Keys, and Optional Keys associated - with the Worklist may be contained in the Identifier. - - An SCU conveys the following semantics - using the C-FIND requests and responses: - + All C-FIND SCUs shall be capable of generating query requests that meet the requirements of the "Worklist" Search Method (see ). + Required Keys, and Optional Keys associated with the Worklist may be contained in the Identifier. + An SCU conveys the following semantics using the C-FIND requests and responses: - The SCU requests that the SCP - perform a match of all keys specified in the Identifier of the request against the - information it possesses of the Worklist specified in the request. - + The SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information it possesses of the Worklist specified in the request. - The SCU shall interpret Pending - responses to convey the Attributes of a match of an Entity. - + The SCU shall interpret Pending responses to convey the Attributes of a match of an Entity. - The SCU shall interpret a response - with a status equal to Success, Failed, Refused or Cancel to convey the end of Pending - responses. - + The SCU shall interpret a response with a status equal to Success, Failed, Refused or Cancel to convey the end of Pending responses. - The SCU shall interpret a Refused - or Failed response to a C-FIND request as an indication that the SCP is unable to - process the request. - + The SCU shall interpret a Refused or Failed response to a C-FIND request as an indication that the SCP is unable to process the request. - The SCU may cancel the C-FIND - service by issuing a C-FIND-CANCEL request at any time during the processing of the - C-FIND. The SCU shall recognize a status of Cancel to indicate that the C-FIND-CANCEL - was successful. - + The SCU may cancel the C-FIND service by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND. The SCU shall recognize a status of Cancel to indicate that the C-FIND-CANCEL was successful.
C-FIND SCP Behavior - All C-FIND SCPs shall be capable of - processing queries that meet the requirements of the "Worklist" Search (see). - - An SCP conveys the following semantics - using the C-FIND requests and responses: - + All C-FIND SCPs shall be capable of processing queries that meet the requirements of the "Worklist" Search (see ). + An SCP conveys the following semantics using the C-FIND requests and responses: - The SCP is requested to perform a - match of all the keys specified in the Identifier of the request, against the - information it possesses. Attribute matching is performed using the key values specified - in the Identifier of the C-FIND request as defined in. - + The SCP is requested to perform a match of all the keys specified in the Identifier of the request, against the information it possesses. Attribute matching is performed using the key values specified in the Identifier of the C-FIND request as defined in . - The SCP generates a C-FIND response - for each match using the "Worklist" Search method. All such responses shall contain an - Identifier whose Attributes contain values from a single match. All such responses shall - contain a status of Pending. - + The SCP generates a C-FIND response for each match using the "Worklist" Search method. All such responses shall contain an Identifier whose Attributes contain values from a single match. All such responses shall contain a status of Pending. - When all matches have been sent, - the SCP generates a C-FIND response that contains a status of Success. A status of - Success shall indicate that a response has been sent for each match known to the SCP. - + When all matches have been sent, the SCP generates a C-FIND response that contains a status of Success. A status of Success shall indicate that a response has been sent for each match known to the SCP. - No ID is contained in a - response with a status of Success. For a complete definition, see. - + No ID is contained in a response with a status of Success. For a complete definition, see . - When there are no - matches, then no responses with a status of Pending are sent, only a single - response with a status of Success. - + When there are no matches, then no responses with a status of Pending are sent, only a single response with a status of Success. - The SCP shall generate a response - with a status of Refused or Failed if it is unable to process the request. A Refused or - Failed response shall contain no Identifier. - + The SCP shall generate a response with a status of Refused or Failed if it is unable to process the request. A Refused or Failed response shall contain no Identifier. - If the SCP receives C-FIND-CANCEL - indication before it has completed the processing of the matches it shall interrupt the - matching process and return a status of Cancel. - + If the SCP receives C-FIND-CANCEL indication before it has completed the processing of the matches it shall interrupt the matching process and return a status of Cancel.
"Worklist" Search Method - The following procedure is used to - generate matches. - - The key match strings contained in the - Identifier of the C-FIND request are matched against the values of the Key Attributes for - each worklist entity. For each entity for which the Attributes match all of the specified - match strings, construct an Identifier. This Identifier shall contain all of the values of - the Attributes for this entity that match those in the C-FIND request. Return a response for - each such Identifier. If there are no matching keys, then there are no matches, return a - response with a status equal to Success and with no Identifier. - + The following procedure is used to generate matches. + The key match strings contained in the Identifier of the C-FIND request are matched against the values of the Key Attributes for each worklist entity. For each entity for which the Attributes match all of the specified match strings, construct an Identifier. This Identifier shall contain all of the values of the Attributes for this entity that match those in the C-FIND request. Return a response for each such Identifier. If there are no matching keys, then there are no matches, return a response with a status equal to Success and with no Identifier.
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. The Association negotiation procedure specified in - - shall be used to negotiate the supported SOP Classes or Meta SOP Classes. - - Support for the SCP/SCU Role Selection Negotiation - is optional. The SOP Class Extended Negotiation is optional. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in shall be used to negotiate the supported SOP Classes or Meta SOP Classes. + Support for the SCP/SCU Role Selection Negotiation is optional. The SOP Class Extended Negotiation is optional.
SOP Class Extended Negotiation - The SOP Class Extended Negotiation allows, at - Association establishment, peer DICOM AEs to exchange application Association information defined by - specific SOP Classes. This is achieved by defining the Service-class-application-information field. - The Service-class-application-information field is used to define support for fuzzy semantic - matching of person names. - - This negotiation is optional. If absent, the - default conditions shall be: - + The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for fuzzy semantic matching of person names. + This negotiation is optional. If absent, the default conditions shall be: - literal matching of person names with - case sensitivity unspecified - + literal matching of person names with case sensitivity unspecified - timezone query adjustment unspecified - + timezone query adjustment unspecified - The Association-requester, for each SOP Class, - may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the - corresponding Abstract Syntax Name (as defined by) followed - by the Service-class-application-information field. This field defines three or more sub-fields: - + The Association-requestor, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by ) followed by the Service-class-application-information field. This field defines three or more sub-fields: reserved; shall always be 1 @@ -31876,50 +22640,22 @@ reserved; shall always be 1 - literal or fuzzy semantic matching of - person names by the Association-requester - + literal or fuzzy semantic matching of person names by the Association-requestor - timezone query adjustment by the - Association-requester - + timezone query adjustment by the Association-requestor - The meaning of fuzzy semantic person name - matching and of timezone query adjustment is as defined in - - and. - - The Association-acceptor shall return a three - byte field (three sub-fields) if offered a three byte field (three sub-fields) by the - Association-requester. The Association-acceptor may return more than three bytes if offered more - than three bytes by the Association-requester. A three byte response to a more than three byte - request means that the missing sub-field shall be treated as 0 values. - - The Association-acceptor, for each sub-field of - the SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requester - proposal by returning the same value (1) or turns down the proposal by returning the value (0).. - - If the SOP Class Extended Negotiation Sub-Item - is not returned by the Association-acceptor then fuzzy semantic matching of person names is not - supported and timezone query adjustment is unspecified over the Association (default condition). - - If the SOP Class Extended Negotiation Sub-Items - do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response. - + The meaning of fuzzy semantic person name matching and of timezone query adjustment is as defined in and . + The Association-acceptor shall return a three byte field (three sub-fields) if offered a three byte field (three sub-fields) by the Association-requestor. The Association-acceptor may return more than three bytes if offered more than three bytes by the Association-requestor. A three byte response to a more than three byte request means that the missing sub-field shall be treated as 0 values. + The Association-acceptor, for each sub-field of the SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requestor proposal by returning the same value (1) or turns down the proposal by returning the value (0).. + If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then fuzzy semantic matching of person names is not supported and timezone query adjustment is unspecified over the Association (default condition). + If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ) - The SOP Class Extended Negotiation Sub-Item - consists of a sequence of mandatory fields as defined by - . This field shall be three or four bytes in length. - + The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by . This field shall be three or four bytes in length. - + @@ -31955,9 +22689,7 @@ reserved @@ -31965,22 +22697,12 @@ 3 @@ -31988,45 +22710,25 @@ 4
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - - A-ASSOCIATE-RQ - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
@@ -31942,9 +22678,7 @@ reserved - This byte field shall - always be 1 - + This byte field shall always be 1
- This byte field shall - always be 1 - + This byte field shall always be 1
- Fuzzy semantic matching of - person names - + Fuzzy semantic matching of person names - This byte field defines - whether or not fuzzy semantic person name Attribute is requested by the - Association-requester. It shall be encoded as an unsigned binary integer and - shall use one of the following values - - 0 - fuzzy semantic matching - not requested - - 1 - fuzzy semantic matching - requested - + This byte field defines whether or not fuzzy semantic person name Attribute is requested by the Association-requestor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - fuzzy semantic matching not requested + 1 - fuzzy semantic matching requested
- Timezone query adjustment - + Timezone query adjustment - This byte field defines - whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used - to adjust the query meaning for time and datetime fields in queries. - - 0 - Timezone query - adjustment not requested - - 1 - Timezone query - adjustment requested - + This byte field defines whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used to adjust the query meaning for time and datetime fields in queries. + 0 - Timezone query adjustment not requested + 1 - Timezone query adjustment requested
- This Sub-Item is identical to Extended - Negotiation Sub-Items as used by the Query/Retrieve SOP Classes. However, relational queries - (Byte 1) are not relevant since the worklist information models are single level, and - date-time matching (Byte 2) is already required by the worklist information models and - Enhanced Multi-Frame Image Conversion support is not applicable (Byte 5). - + This Sub-Item is identical to Extended Negotiation Sub-Items as used by the Query/Retrieve SOP Classes. However, relational queries (Byte 1) are not relevant since the worklist information models are single level, and date-time matching (Byte 2) is already required by the worklist information models and Enhanced Multi-Frame Image Conversion support is not applicable (Byte 5).
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC) - The SOP Class Extended Negotiation Sub-Item - is made of a sequence of mandatory fields as defined by. - This field shall be three or four bytes in length. - + The SOP Class Extended Negotiation Sub-Item is made of a sequence of mandatory fields as defined by . This field shall be three or four bytes in length. - + @@ -32062,9 +22762,7 @@ reserved @@ -32072,22 +22770,12 @@ 3 @@ -32095,20 +22783,12 @@ 4 @@ -32122,146 +22802,72 @@ Modality Worklist SOP Class
Modality Worklist SOP Class Overview - The Modality Worklist SOP Class defined - within the Basic Worklist Management Service Class defines an application-level class of service - that facilitates the communication of information to the imaging modality about Scheduled - Procedure Steps, and entities related to the Scheduled Procedure Steps. As will be detailed - below, part of the information carried by the worklist mechanism is intended to be used by the - imaging modality itself, but much of the information is intended to be presented to the modality - operator. - - This worklist is structured according to - Scheduled Procedure Steps. A procedure step is a unit of service in the context of a requested - imaging procedure. - - The Modality Worklist SOP Class supports - the following requirements: - + The Modality Worklist SOP Class defined within the Basic Worklist Management Service Class defines an application-level class of service that facilitates the communication of information to the imaging modality about Scheduled Procedure Steps, and entities related to the Scheduled Procedure Steps. As will be detailed below, part of the information carried by the worklist mechanism is intended to be used by the imaging modality itself, but much of the information is intended to be presented to the modality operator. + This worklist is structured according to Scheduled Procedure Steps. A procedure step is a unit of service in the context of a requested imaging procedure. + The Modality Worklist SOP Class supports the following requirements: - Verify patient (e.g., download - patient demographic information from IS to Modality, to verify that the person to be - examined is the intended subject). - + Verify patient (e.g., download patient demographic information from IS to Modality, to verify that the person to be examined is the intended subject). - Select a Scheduled Procedure Step - from the IS (e.g., download procedure step information from the IS to the Modality). The - Modality Worklist SOP Class supports two alternatives for the realization of this - requirement, supporting different organization methods of the department: - + Select a Scheduled Procedure Step from the IS (e.g., download procedure step information from the IS to the Modality). The Modality Worklist SOP Class supports two alternatives for the realization of this requirement, supporting different organization methods of the department: - The Modality may obtain the - list of Scheduled Procedure Steps from the IS. Display of the list and selection - from the list is done at the Modality. - + The Modality may obtain the list of Scheduled Procedure Steps from the IS. Display of the list and selection from the list is done at the Modality. - The list is displayed and - selection is performed on the IS. This implies, that the information is obtained - by the Modality just before the Scheduled Procedure Step starts. - + The list is displayed and selection is performed on the IS. This implies, that the information is obtained by the Modality just before the Scheduled Procedure Step starts. - Prepare the performance of a - Scheduled Procedure Step. - + Prepare the performance of a Scheduled Procedure Step. - Couple DICOM images unambiguously - with related information from the IS (e.g., patient demographics, procedure description, - ID data structure from the IS, contextual IS information). - + Couple DICOM images unambiguously with related information from the IS (e.g., patient demographics, procedure description, ID data structure from the IS, contextual IS information). - Capture all the Attributes from the - IS, that are mandatory to be inserted into the DICOM Image Object - + Capture all the Attributes from the IS, that are mandatory to be inserted into the DICOM Image Object - The Modality Worklist SOP Class is not - intended to provide access to all IS information and services that may be of interest to a - Modality operator or attending physician. Its primary focus is the efficient operation of the - image acquisition equipment. DICOM SOP Classes such as the Relevant Patient Information Query - SOP Class and non-DICOM Services that fall beyond the scope of the Modality Worklist SOP Class - may be needed. - - The Modality Worklist SOP Class does not - support the transmission of information from the Modality to the information system. - + The Modality Worklist SOP Class is not intended to provide access to all IS information and services that may be of interest to a Modality operator or attending physician. Its primary focus is the efficient operation of the image acquisition equipment. DICOM SOP Classes such as the Relevant Patient Information Query SOP Class and non-DICOM Services that fall beyond the scope of the Modality Worklist SOP Class may be needed. + The Modality Worklist SOP Class does not support the transmission of information from the Modality to the information system.
Modality Worklist Information Model
E/R Model - In response to a given C-FIND request, - the SCP might have to send several C-FIND responses, (i.e., one C-FIND response per matching - worklist item). Each worklist item focuses on one Scheduled Procedure Step and the related - information. The E-R diagram presented in - - depicts the content of one C-FIND request, that is: - + In response to a given C-FIND request, the SCP might have to send several C-FIND responses, (i.e., one C-FIND response per matching worklist item). Each worklist item focuses on one Scheduled Procedure Step and the related information. The E-R diagram presented in depicts the content of one C-FIND request, that is: - the matching Scheduled - Procedure Step, the Requested Procedure to which the Scheduled Procedure Step - contributes, the Imaging Service Request in which the associated Requested Procedure - is ordered, any associated Visit, and the Patient who is to be the subject of the - Procedure. - + the matching Scheduled Procedure Step, the Requested Procedure to which the Scheduled Procedure Step contributes, the Imaging Service Request in which the associated Requested Procedure is ordered, any associated Visit, and the Patient who is to be the subject of the Procedure. - Therefore, for a given C-FIND request, - a given Scheduled Procedure Step will appear in only one of the resulting C-FIND responses. - Obviously, information about the Requested Procedure, Imaging Service Request, Visit and - Patient may be mentioned in several of these C-FIND responses. - - The Modality Worklist Information Model - is represented by the Entity Relationship diagram shown in figure - - -1. - + Therefore, for a given C-FIND request, a given Scheduled Procedure Step will appear in only one of the resulting C-FIND responses. Obviously, information about the Requested Procedure, Imaging Service Request, Visit and Patient may be mentioned in several of these C-FIND responses. + The Modality Worklist Information Model is represented by the Entity Relationship diagram shown in figure -1. - The entities appearing in messages - related to the Modality Worklist SOP Class are required to comply to the Modality - Worklist model. However, DICOM does not define the internal structure of the database. - + The entities appearing in messages related to the Modality Worklist SOP Class are required to comply to the Modality Worklist model. However, DICOM does not define the internal structure of the database. - The entry point of the Modality - Worklist is the Scheduled Procedure Step entity. - - The Attributes of a Scheduled Procedure - Step Worklist can be found in the following Modules in - . - + The entry point of the Modality Worklist is the Scheduled Procedure Step entity. + The Attributes of a Scheduled Procedure Step Worklist can be found in the following Modules in . - Patient Relationship Module - + Patient Relationship Module - Patient Identification Module - + Patient Identification Module - Patient Demographic Module - + Patient Demographic Module Patient Medical Module - Visit Relationship Module - + Visit Relationship Module - Visit Identification Module - + Visit Identification Module Visit Status Module @@ -32270,18 +22876,13 @@ Visit Admission Module - Scheduled Procedure Step - Module - + Scheduled Procedure Step Module - Requested Procedure Module - + Requested Procedure Module - Imaging Service Request - Module - + Imaging Service Request Module @@ -32299,31 +22900,25 @@
Modality Worklist Attributes - - defines the Attributes of the Modality Worklist Information Model: - + defines the Attributes of the Modality Worklist Information Model:
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - - A-ASSOCIATE-AC - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
@@ -32049,9 +22751,7 @@ reserved - This byte field shall - always be 1 - + This byte field shall always be 1
- This byte field shall - always be 1 - + This byte field shall always be 1
- Fuzzy semantic matching of - person names - + Fuzzy semantic matching of person names - This byte field defines - whether or not fuzzy semantic person name Attribute matching will be performed - by the Association-acceptor. It shall be encoded as an unsigned binary integer - and shall use one of the following values - - 0 - fuzzy semantic matching - not performed - - 1 - fuzzy semantic matching - performed - + This byte field defines whether or not fuzzy semantic person name Attribute matching will be performed by the Association-acceptor. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - fuzzy semantic matching not performed + 1 - fuzzy semantic matching performed
- Timezone query adjustment - + Timezone query adjustment - This byte field defines - whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used - to adjust the query meaning for time and datetime fields in queries. - - 0 - Timezone adjustment of - queries not performed - - 1 - Timezone adjustment of - queries performed - + This byte field defines whether or not the Attribute Timezone Offset From UTC (0008,0201) shall be used to adjust the query meaning for time and datetime fields in queries. + 0 - Timezone adjustment of queries not performed + 1 - Timezone adjustment of queries performed
@@ -32337,9 +22932,7 @@ @@ -32450,16 +23017,12 @@ 1 @@ -33186,9 +23641,7 @@ @@ -33464,9 +23886,7 @@ @@ -33554,9 +23969,7 @@ @@ -33596,9 +24007,7 @@ @@ -33638,9 +24045,7 @@ @@ -33791,15 +24181,12 @@ 1 @@ -33879,8 +24260,7 @@ @@ -34010,9 +24372,7 @@ @@ -34127,9 +24485,7 @@ @@ -34245,53 +24589,23 @@ - Just like Series and Image - Entities specified in the Query/Retrieve Service Class either an SCU or an SCP - may support optional Matching Key Attributes and/or Type 3 Return Key Attributes - that are not included in the Worklist Information Model (i.e., Standard or - Private Attributes). This is considered a Standard Extended SOP Class (see). - + Just like Series and Image Entities specified in the Query/Retrieve Service Class either an SCU or an SCP may support optional Matching Key Attributes and/or Type 3 Return Key Attributes that are not included in the Worklist Information Model (i.e., Standard or Private Attributes). This is considered a Standard Extended SOP Class (see ). - Each Module contains a - Comment Attribute. This may be used to transmit non-structured information, - which may be displayed to the operator of the Modality. - + Each Module contains a Comment Attribute. This may be used to transmit non-structured information, which may be displayed to the operator of the Modality. - The reason for this - exclusion is to assure that the Attributes that may be present in multiple - Modules are included only once with the meaning pertaining to only one Module - (for example, Referenced Study Sequence (0008,1110) shall be included once with - the meaning as defined in the Requested Procedure Module). - + The reason for this exclusion is to assure that the Attributes that may be present in multiple Modules are included only once with the meaning pertaining to only one Module (for example, Referenced Study Sequence (0008,1110) shall be included once with the meaning as defined in the Requested Procedure Module). - The use of Specific - Character Set is discussed in - - and. - + The use of Specific Character Set is discussed in and . - The values of Study Date - (0008,0020) and Study Time (0008,0030) may be provided in order to achieve - consistency of Study level Attributes in composite instances generated in - multiple performed procedure steps on different devices, and the worklist values - may be updated by the SCP based on information received from Modality Performed - Procedure Steps or by examining the composite instances generated. - + The values of Study Date (0008,0020) and Study Time (0008,0030) may be provided in order to achieve consistency of Study level Attributes in composite instances generated in multiple performed procedure steps on different devices, and the worklist values may be updated by the SCP based on information received from Modality Performed Procedure Steps or by examining the composite instances generated. - The Attributes in - - are not part of the Worklist Information Model; their inclusion in the C-FIND request and - response identifier are governed by rules in sections - - and, respectively. - + The Attributes in are not part of the Worklist Information Model; their inclusion in the C-FIND request and response identifier are governed by rules in sections and , respectively.
Attributes for the Modality Worklist Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark / Matching - Type - + Remark / Matching Type
- Scheduled Procedure - Step Sequence - + Scheduled Procedure Step Sequence (0040,0100) @@ -32351,19 +22944,13 @@ 1 - The Attributes of the - Scheduled Procedure Step shall only be retrieved with Sequence Matching. - - The Scheduled Procedure - Step Sequence shall contain only a single Item. - + The Attributes of the Scheduled Procedure Step shall only be retrieved with Sequence Matching. + The Scheduled Procedure Step Sequence shall contain only a single Item.
- >Scheduled Station - AE Title - + >Scheduled Station AE Title (0040,0001) @@ -32375,16 +22962,12 @@ 1 - Scheduled Station AE - Title shall be retrieved with Single Value Matching only. - + Scheduled Station AE Title shall be retrieved with Single Value Matching only.
- >Scheduled Procedure - Step Start Date - + >Scheduled Procedure Step Start Date (0040,0002) @@ -32396,19 +22979,13 @@ 1 - Scheduled Step Start - Date shall be retrieved with Single Value Matching or Range Matching. - - See remark under - Scheduled Procedure Step Start Time (0040,0003). - + Scheduled Step Start Date shall be retrieved with Single Value Matching or Range Matching. + See remark under Scheduled Procedure Step Start Time (0040,0003).
- >Scheduled Procedure - Step Start Time - + >Scheduled Procedure Step Start Time (0040,0003) @@ -32420,19 +22997,9 @@ 1 - Scheduled Step Start - Time shall be retrieved with Single Value Matching or Range Matching. - Scheduled Step Start Date and Scheduled Step Start Time are subject to Range - Matching. If both keys are specified for Range Matching, e.g., the date - range July 5 to July 7 and the time range 10am to 6pm specifies the time - period starting on July 5, 10am until July 7, 6pm. - + Scheduled Step Start Time shall be retrieved with Single Value Matching or Range Matching. Scheduled Step Start Date and Scheduled Step Start Time are subject to Range Matching. If both keys are specified for Range Matching, e.g., the date range July 5 to July 7 and the time range 10am to 6pm specifies the time period starting on July 5, 10am until July 7, 6pm. - If the Information - System does not provide scheduling for individual Procedure Steps, it - may use the closest scheduling information it possesses (e.g., - Procedures are subject to scheduling instead of Procedure Steps). - + If the Information System does not provide scheduling for individual Procedure Steps, it may use the closest scheduling information it possesses (e.g., Procedures are subject to scheduling instead of Procedure Steps).
- The Modality shall be - retrieved with Single Value Matching. - + The Modality shall be retrieved with Single Value Matching.
- >Scheduled - Performing Physician's Name - + >Scheduled Performing Physician's Name (0040,0006) @@ -32471,17 +23034,12 @@ 2 - Scheduled Performing - Physician's Name shall be retrieved with Single Value Matching or Wild Card - Matching. - + Scheduled Performing Physician's Name shall be retrieved with Single Value Matching or Wild Card Matching.
- >Scheduled Procedure - Step Description - + >Scheduled Procedure Step Description (0040,0007) @@ -32493,17 +23051,12 @@ 1C - Either the Scheduled - Procedure Step Description (0040,0007) or the Scheduled Protocol Code - Sequence (0040,0008) or both shall be supported by the SCP. - + Either the Scheduled Procedure Step Description (0040,0007) or the Scheduled Protocol Code Sequence (0040,0008) or both shall be supported by the SCP.
- >Scheduled Station - Name - + >Scheduled Station Name (0040,0010) @@ -32518,9 +23071,7 @@
- >Scheduled Procedure - Step Location - + >Scheduled Procedure Step Location (0040,0011) @@ -32535,9 +23086,7 @@
- >Referenced Defined - Protocol Sequence - + >Referenced Defined Protocol Sequence (0018,990C) @@ -32554,9 +23103,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -32573,9 +23120,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -32592,9 +23137,7 @@
- >Referenced - Performed Protocol Sequence - + >Referenced Performed Protocol Sequence (0018,990D) @@ -32611,9 +23154,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -32630,9 +23171,7 @@
- >>Referenced SOP - Instance UID - + >>Referenced SOP Instance UID (0008,1155) @@ -32649,9 +23188,7 @@
- >Scheduled Protocol - Code Sequence - + >Scheduled Protocol Code Sequence (0040,0008) @@ -32663,29 +23200,21 @@ 1C - Either the Scheduled - Procedure Step Description (0040,0007) or the Scheduled Protocol Code - Sequence (0040,0008) or both shall be supported by the SCP. - - The Scheduled Protocol - Code Sequence contains one or more Items. - + Either the Scheduled Procedure Step Description (0040,0007) or the Scheduled Protocol Code Sequence (0040,0008) or both shall be supported by the SCP. + The Scheduled Protocol Code Sequence contains one or more Items.
- >>Include - - - +>>Include + +
- >>Protocol - Context Sequence - + >>Protocol Context Sequence (0040,0440) @@ -32697,16 +23226,12 @@ 3 - The Protocol Context - Sequence and its Items shall not be used for matching - + The Protocol Context Sequence and its Items shall not be used for matching
- >>>Value - Type - + >>>Value Type (0040,A040) @@ -32721,9 +23246,7 @@
- >>>Concept - Name Code Sequence - + >>>Concept Name Code Sequence (0040,A043) @@ -32739,16 +23262,14 @@
- >>>>Include - - - +>>>>Include + +
- >>>DateTime - + >>>DateTime (0040,A120) @@ -32760,16 +23281,12 @@ 1C - Required if Value Type - (0040,A040) is DATETIME. - + Required if Value Type (0040,A040) is DATETIME.
- >>>Person - Name - + >>>Person Name (0040,A123) @@ -32781,16 +23298,12 @@ 1C - Required if Value Type - (0040,A040) is PNAME. - + Required if Value Type (0040,A040) is PNAME.
- >>>Text - Value - + >>>Text Value (0040,A160) @@ -32802,16 +23315,12 @@ 1C - Required if Value Type - (0040,A040) is TEXT. - + Required if Value Type (0040,A040) is TEXT.
- >>>Concept - Code Sequence - + >>>Concept Code Sequence (0040,A168) @@ -32823,25 +23332,20 @@ 1C - Required if Value Type - (0040,A040) is CODE. - + Required if Value Type (0040,A040) is CODE.
- >>>>Include - - - +>>>>Include + +
- >>>Numeric - Value - + >>>Numeric Value (0040,A30A) @@ -32853,16 +23357,12 @@ 1C - Required if Value Type - (0040,A040) is NUMERIC. - + Required if Value Type (0040,A040) is NUMERIC.
- >>>Measurement - Units Code Sequence - + >>>Measurement Units Code Sequence (0040,08EA) @@ -32874,26 +23374,21 @@ 1C - Required if Value Type - (0040,A040) is NUMERIC. - + Required if Value Type (0040,A040) is NUMERIC.
- >>>>Include - - - +>>>>Include + +
- >>>All other Attributes of the Protocol - Context Sequence - + >>>All other Attributes of the Protocol Context Sequence @@ -32907,8 +23402,7 @@
- >Pre-Medication - + >Pre-Medication (0040,0012) @@ -32920,16 +23414,12 @@ 2C - Required if - Pre-Medication is to be applied to that Scheduled Procedure Step. - + Required if Pre-Medication is to be applied to that Scheduled Procedure Step.
- >Scheduled Procedure - Step ID - + >Scheduled Procedure Step ID (0040,0009) @@ -32944,9 +23434,7 @@
- >Requested Contrast - Agent - + >Requested Contrast Agent (0032,1070) @@ -32958,16 +23446,12 @@ 2C - Required if Contrast - Media is to be applied to that Scheduled Procedure Step. - + Required if Contrast Media is to be applied to that Scheduled Procedure Step.
- >Scheduled Procedure - Step Status - + >Scheduled Procedure Step Status (0040,0020) @@ -32983,9 +23467,7 @@
- >All other Attributes of the Scheduled Procedure - Step Sequence - + >All other Attributes of the Scheduled Procedure Step Sequence @@ -32999,9 +23481,7 @@
- Scheduled Specimen - Sequence - + Scheduled Specimen Sequence (0040,0500) @@ -33013,16 +23493,12 @@ 3 - One or more Items may - be returned in this Sequence. - + One or more Items may be returned in this Sequence.
- >Container - Identifier - + >Container Identifier (0040,0512) @@ -33037,9 +23513,7 @@
- >Container Type Code - Sequence - + >Container Type Code Sequence (0040,0518) @@ -33051,25 +23525,20 @@ 2 - Zero or one Item shall - be returned in this Sequence. - + Zero or one Item shall be returned in this Sequence.
- >>Include - - - +>>Include + +
- >Specimen - Description Sequence - + >Specimen Description Sequence (0040,0560) @@ -33081,16 +23550,12 @@ 1 - One or more Items shall - be returned in this Sequence. - + One or more Items shall be returned in this Sequence.
- >>Specimen - Identifier - + >>Specimen Identifier (0040,0551) @@ -33105,8 +23570,7 @@
- >>Specimen UID - + >>Specimen UID (0040,0554) @@ -33122,9 +23586,7 @@
- >>All other Attributes of the Specimen - Description Sequence - + >>All other Attributes of the Specimen Description Sequence @@ -33135,18 +23597,13 @@ 3 - Specimen Preparation - Sequence (0040,0610), if present, describes preparation steps already - performed, not scheduled procedure steps - + Specimen Preparation Sequence (0040,0610), if present, describes preparation steps already performed, not scheduled procedure steps
- >All other Attributes of the Scheduled Specimen - Sequence - + >All other Attributes of the Scheduled Specimen Sequence @@ -33172,9 +23629,7 @@ 3 - This may be the same as - Container Identifier (0040,0512). - + This may be the same as Container Identifier (0040,0512).
- Requested Procedure - ID - + Requested Procedure ID (0040,1001) @@ -33203,9 +23656,7 @@
- Requested Procedure - Description - + Requested Procedure Description (0032,1060) @@ -33217,17 +23668,12 @@ 1C - The Requested Procedure - Description (0032,1060) or the Requested Procedure Code Sequence (0032,1064) - or both shall be supported by the SCP. - + The Requested Procedure Description (0032,1060) or the Requested Procedure Code Sequence (0032,1064) or both shall be supported by the SCP.
- Requested Procedure - Code Sequence - + Requested Procedure Code Sequence (0032,1064) @@ -33239,29 +23685,21 @@ 1C - The Requested Procedure - Description (0032,1060) or the Requested Procedure Code Sequence (0032,1064) - or both shall be supported by the SCP. - - The Requested Procedure - Code Sequence shall contain only a single Item. - + The Requested Procedure Description (0032,1060) or the Requested Procedure Code Sequence (0032,1064) or both shall be supported by the SCP. + The Requested Procedure Code Sequence shall contain only a single Item.
- >Include - - - +>Include + +
- Requested Laterality - Code Sequence - + Requested Laterality Code Sequence (0032,1065) @@ -33273,24 +23711,20 @@ 3 - Only a single Item may - be returned in this Sequence. - + Only a single Item may be returned in this Sequence.
- >Include - + >Include
- Study Instance UID - + Study Instance UID (0020,000D) @@ -33339,9 +23773,7 @@
- Referenced Study - Sequence - + Referenced Study Sequence (0008,1110) @@ -33356,9 +23788,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -33373,9 +23803,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -33390,9 +23818,7 @@
- Requested Procedure - Priority - + Requested Procedure Priority (0040,1003) @@ -33407,9 +23833,7 @@
- Patient Transport - Arrangements - + Patient Transport Arrangements (0040,1004) @@ -33425,9 +23849,7 @@
- All other Attributes of the - + All other Attributes of the
- Issuer of Accession - Number Sequence - + Issuer of Accession Number Sequence (0008,0051) @@ -33481,8 +23901,7 @@
- Requesting Physician - + Requesting Physician (0032,1032) @@ -33497,9 +23916,7 @@
- Referring Physician's - Name - + Referring Physician's Name (0008,0090) @@ -33515,9 +23932,7 @@
- All other Attributes of the - + All other Attributes of the
- Issuer of Admission ID - Sequence - + Issuer of Admission ID Sequence (0038,0014) @@ -33572,9 +23985,7 @@
- All other Attributes of the - + All other Attributes of the
- Current Patient - Location - + Current Patient Location (0038,0300) @@ -33614,9 +24023,7 @@
- All other Attributes of the - + All other Attributes of the
- Referenced Patient - Sequence - + Referenced Patient Sequence (0008,1120) @@ -33655,9 +24060,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -33672,9 +24075,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -33690,11 +24091,7 @@
- All other Attributes of the - - except those explicitly included in this table (see Note 3) - + All other Attributes of the except those explicitly included in this table (see Note 3) @@ -33715,9 +24112,7 @@
- All Attributes from the - Visit Admission Module - + All Attributes from the Visit Admission Module @@ -33737,10 +24132,7 @@
- All Attributes from the - Patient Relationship Module except those explicitly included in this table - (see Note 3) - + All Attributes from the Patient Relationship Module except those explicitly included in this table (see Note 3) @@ -33772,9 +24164,7 @@ 1 - Patient Name shall be - retrieved with Single Value Matching or Wild Card Matching. - + Patient Name shall be retrieved with Single Value Matching or Wild Card Matching.
- Patient ID shall be - retrieved with Single Value Matching. - + Patient ID shall be retrieved with Single Value Matching.
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -33816,9 +24203,7 @@
- Issuer of Patient ID - Qualifiers Sequence - + Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -33835,9 +24220,7 @@
- Other Patient IDs - Sequence - + Other Patient IDs Sequence (0010,1002) @@ -33855,9 +24238,7 @@
- All other Attributes of the - + All other Attributes of the
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -33910,9 +24290,7 @@
- Patient's Primary - Language Code Sequence - + Patient's Primary Language Code Sequence (0010,0101) @@ -33924,30 +24302,21 @@ 3 - The languages that can - be used to communicate with the patient. - - If returned, the - Patient's Primary Language Code Sequence shall contain one or more Items. - The items are ordered by preference (most preferred language to least - preferred language). - + The languages that can be used to communicate with the patient. + If returned, the Patient's Primary Language Code Sequence shall contain one or more Items. The items are ordered by preference (most preferred language to least preferred language).
- >Include - - - +>Include + +
- >Patient's Primary - Language Modifier Code Sequence - + >Patient's Primary Language Modifier Code Sequence (0010,0102) @@ -33959,23 +24328,16 @@ 3 - A modifier for a - Patient's Primary Language. Can be used to specify a national language - variant. - - If returned, the - Patient's Primary Language Modifier Code Sequence shall contain only a - single Item. - + A modifier for a Patient's Primary Language. Can be used to specify a national language variant. + If returned, the Patient's Primary Language Modifier Code Sequence shall contain only a single Item.
- >>Include - - - +>>Include + +
- Confidentiality - constraint on patient data - + Confidentiality constraint on patient data (0040,3001) @@ -34028,9 +24388,7 @@
- All other Attributes of the - + All other Attributes of the
- Pertinent Documents - Sequence - + Pertinent Documents Sequence (0038,0100) @@ -34141,16 +24497,12 @@ 3 - Pertinent Documents - Sequence shall be retrieved with Universal Matching only - + Pertinent Documents Sequence shall be retrieved with Universal Matching only
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -34165,9 +24517,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -34182,9 +24532,7 @@
- >Purpose of - Reference Code Sequence - + >Purpose of Reference Code Sequence (0040,A170) @@ -34200,16 +24548,14 @@
- >>Include - - - +>>Include + +
- >Document Title - + >Document Title (0042,0010) @@ -34225,9 +24571,7 @@
- All other Attributes of the - + All other Attributes of the
@@ -34303,12 +24617,10 @@ Tag
Attributes for the Modality Worklist C-FIND Identifier
- Request Identifier - + Request Identifier - Response Identifier - + Response Identifier Remark Type @@ -34318,9 +24630,7 @@
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -34332,19 +24642,13 @@ 1C - This Attribute is - required if expanded or replacement character sets are used. See - - and - + This Attribute is required if expanded or replacement character sets are used. See and
- Timezone Offset From - UTC - + Timezone Offset From UTC (0008,0201) @@ -34356,20 +24660,13 @@ 1C - This Attribute is - required if times are to be interpreted explicitly in the designated local - timezone. See - - and - + This Attribute is required if times are to be interpreted explicitly in the designated local timezone. See and
- HL7 Structured Document - Reference Sequence - + HL7 Structured Document Reference Sequence (0040,A390) @@ -34381,20 +24678,14 @@ 1C - One or more Items may - be included in this sequence. - - Required if HL7 - Structured Documents are referenced within the Identifier. See - + One or more Items may be included in this sequence. + Required if HL7 Structured Documents are referenced within the Identifier. See
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -34409,9 +24700,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -34426,9 +24715,7 @@
- >HL7 Instance - Identifier - + >HL7 Instance Identifier (0040,E001) @@ -34462,76 +24749,26 @@
Conformance Requirements - An implementation may conform to the - Modality Worklist SOP Class as an SCU or an SCP. The Conformance Statement shall be in the - format defined in. - + An implementation may conform to the Modality Worklist SOP Class as an SCU or an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that conforms to the - Modality Worklist SOP Class shall support queries against the Worklist Information Model - described in - - of this Annex using the baseline C-FIND SCU Behavior described in - - of this Part. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether it - requests matching on Optional Matching Key Attributes. If it requests Type 3 Return Key - Attributes, then it shall list these Optional Return Key Attributes. It shall identify any - Templates it supports for the Protocol Context Sequence. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether or - not it supports extended negotiation of fuzzy semantic matching of person names. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCU shall state in its Conformance Statement how it makes - use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when - encoding queries and interpreting responses. - + An implementation that conforms to the Modality Worklist SOP Class shall support queries against the Worklist Information Model described in of this Annex using the baseline C-FIND SCU Behavior described in of this Part. + An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether it requests matching on Optional Matching Key Attributes. If it requests Type 3 Return Key Attributes, then it shall list these Optional Return Key Attributes. It shall identify any Templates it supports for the Protocol Context Sequence. + An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement whether or not it supports Extended Negotiation of fuzzy semantic matching of person names. + An implementation that conforms to the Modality Worklist SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses.
SCP Conformance - An implementation that conforms to the - Modality Worklist SOP Class shall support queries against the Worklist Information Model - described in - - of this Annex using the C-FIND SCP Behavior described in - - of this Part. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether it - supports matching on Optional Matching Key Attributes. If it supports Type 3 Return Key - Attributes, then it shall list the Optional Return Key Attributes that it supports. It shall - identify any Templates it supports for the Protocol Context Sequence. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether it - supports case-insensitive matching for PN VR Attributes and list Attributes for which this - applies. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether or - not it supports extended negotiation of fuzzy semantic matching of person names. If fuzzy - semantic matching of person names is supported, then the mechanism for fuzzy semantic - matching shall be specified. - - An implementation that conforms to the - Modality Worklist SOP Class as an SCP shall state in its Conformance Statement how it makes - use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when - interpreting queries, performing matching and encoding responses. - + An implementation that conforms to the Modality Worklist SOP Class shall support queries against the Worklist Information Model described in of this Annex using the C-FIND SCP Behavior described in of this Part. + An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether it supports matching on Optional Matching Key Attributes. If it supports Type 3 Return Key Attributes, then it shall list the Optional Return Key Attributes that it supports. It shall identify any Templates it supports for the Protocol Context Sequence. + An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether it supports case-insensitive matching for PN VR Attributes and list Attributes for which this applies. + An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement whether or not it supports Extended Negotiation of fuzzy semantic matching of person names. If fuzzy semantic matching of person names is supported, then the mechanism for fuzzy semantic matching shall be specified. + An implementation that conforms to the Modality Worklist SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting queries, performing matching and encoding responses.
SOP Class - The Modality Worklist SOP Class in the - Basic Worklist Service Class identifies the Modality Worklist Information Model, and the DIMSE-C - operations supported. The following Standard SOP Class is identified: - + The Modality Worklist SOP Class in the Basic Worklist Service Class identifies the Modality Worklist Information Model, and the DIMSE-C operations supported. The following Standard SOP Class is identified: @@ -34547,13 +24784,10 @@ @@ -34567,8 +24801,7 @@
Examples for the Usage of the Modality Worklist (Informative) - Moved to - + Moved to
@@ -34582,10 +24815,7 @@ Handling of Identifying Parameters (Informative) - Retired. See. - + Retired. See . Softcopy Presentation State Storage SOP Classes (Normative) @@ -34593,145 +24823,54 @@ Overview
Scope - The Softcopy Presentation State Storage SOP - Classes extend the functionality of the Storage Service class (defined in - ) to add the ability to convey an intended presentation state or record an existing presentation - state. The SOP Classes specify the information and behavior that may be used to present (display) - images that are referenced from within the SOP Classes. - - They include capabilities for specifying: - + The Softcopy Presentation State Storage SOP Classes extend the functionality of the Storage Service class (defined in ) to add the ability to convey an intended presentation state or record an existing presentation state. The SOP Classes specify the information and behavior that may be used to present (display) images that are referenced from within the SOP Classes. + They include capabilities for specifying: - the output grayscale space in - P-Values - + the output grayscale space in P-Values - the color output space as PCS-Values - + the color output space as PCS-Values - grayscale contrast transformations - including modality, VOI and presentation LUT - + grayscale contrast transformations including modality, VOI and presentation LUT - mask subtraction for multi-frame - grayscale images - + mask subtraction for multi-frame grayscale images - selection of the area of the image to - display and whether to rotate or flip it - + selection of the area of the image to display and whether to rotate or flip it - image and display relative annotations, - including graphics, text and overlays - + image and display relative annotations, including graphics, text and overlays - the blending of two image sets into a - single presentation - + the blending of two image sets into a single presentation - The grayscale softcopy presentation state - refers to the grayscale image transformations that are to be applied in an explicitly defined manner - to convert the stored image pixel data values in a Composite Image Instance to presentation values - (P-Values) when an image is displayed on a softcopy device. The P-Values are in a device independent - perceptually linear space that is formally defined in - . - - The color and pseudo-color softcopy - presentation states refer to the color image transformations that are to be applied in an explicitly - defined manner to convert the stored image pixel data values in a Composite Image Instance to - Profile Connection Space values (PCS-Values) when an image is displayed on a softcopy device. The - PCS-Values are in a device independent space that is formally defined in the ICC Profiles as CIEXYZ - or CIELab values. - - The blending presentation states specify two - sets of images, an underlying set, and a superimposed set, and the manner in which their pixel - values are blended. The underlying set is rendered as grayscale and the superimposed set is rendered - as color. The blending is not defined in a pair wise image-by-image or frame-by-frame manner, but - rather the manner in which the two sets are combined is left to the discretion of the - implementation. Specifically, matters of spatial registration, and any re-sampling and the mechanism - of interpolation are not specified. - - The Softcopy Presentation State Storage SOP - Classes may be used to store a single state per image, or a common state to be shared by multiple - selected images. All images to which the Grayscale, Color and Pseudo-Color Presentation States apply - must be a part of the same study that the stored state is a part of, and be of a single Composite - Image Storage SOP Class. - - The two sets of images to which the Blended - Presentation State applies may be in separate Studies, Each set shall be within a single study. Each - set shall be of a single Composite Image Storage SOP Class. - - How an SCU of this SOP Class records or - generates this state is beyond the scope of the Standard. - + The grayscale softcopy presentation state refers to the grayscale image transformations that are to be applied in an explicitly defined manner to convert the stored image pixel data values in a Composite Image Instance to presentation values (P-Values) when an image is displayed on a softcopy device. The P-Values are in a device independent perceptually linear space that is formally defined in . + The color and pseudo-color softcopy presentation states refer to the color image transformations that are to be applied in an explicitly defined manner to convert the stored image pixel data values in a Composite Image Instance to Profile Connection Space values (PCS-Values) when an image is displayed on a softcopy device. The PCS-Values are in a device independent space that is formally defined in the ICC Profiles as CIEXYZ or CIELab values. + The blending presentation states specify two sets of images, an underlying set, and a superimposed set, and the manner in which their pixel values are blended. The underlying set is rendered as grayscale and the superimposed set is rendered as color. The blending is not defined in a pair wise image-by-image or frame-by-frame manner, but rather the manner in which the two sets are combined is left to the discretion of the implementation. Specifically, matters of spatial registration, and any re-sampling and the mechanism of interpolation are not specified. + The Softcopy Presentation State Storage SOP Classes may be used to store a single state per image, or a common state to be shared by multiple selected images. All images to which the Grayscale, Color and Pseudo-Color Presentation States apply must be a part of the same study that the stored state is a part of, and be of a single Composite Image Storage SOP Class. + The two sets of images to which the Blended Presentation State applies may be in separate Studies, Each set shall be within a single study. Each set shall be of a single Composite Image Storage SOP Class. + How an SCU of this SOP Class records or generates this state is beyond the scope of the Standard. - For example, an acquisition device may - acquire, reconstruct and store to a workstation or archive images that are later examined by an - operator for the purpose of quality assurance or printing. At that time a selected grayscale - transformation (such as a window level/width operation) may be applied by the operator, and that - activity captured and saved as a Grayscale Softcopy Presentation State Storage SOP Instance to - the same workstation or archive, from which it is subsequently available for use by another - user. Another workstation may retrieve the state for later use. Alternatively, an automated - algorithm may derive a state from analysis of image statistics, body part examined, or other - characteristics. - + For example, an acquisition device may acquire, reconstruct and store to a workstation or archive images that are later examined by an operator for the purpose of quality assurance or printing. At that time a selected grayscale transformation (such as a window level/width operation) may be applied by the operator, and that activity captured and saved as a Grayscale Softcopy Presentation State Storage SOP Instance to the same workstation or archive, from which it is subsequently available for use by another user. Another workstation may retrieve the state for later use. Alternatively, an automated algorithm may derive a state from analysis of image statistics, body part examined, or other characteristics. - How an SCP of this SOP Class chooses between - multiple states that may apply to an image is beyond the scope of this Standard, other than to state - that a claim of conformance as an SCP of this SOP Class implies that the SCP shall make the - presentation state available to the user of the device, and if selected by the user, shall apply all - the transformations stored in the state in the manner in which they are defined in the Standard. - + How an SCP of this SOP Class chooses between multiple states that may apply to an image is beyond the scope of this Standard, other than to state that a claim of conformance as an SCP of this SOP Class implies that the SCP shall make the presentation state available to the user of the device, and if selected by the user, shall apply all the transformations stored in the state in the manner in which they are defined in the Standard. - For example, an acquisition device - may automatically store appropriate presentation states for series of images as they are - reconstructed that represent adequate defaults. A user or algorithm may subsequently - determine a more appropriate presentation state that more effectively displays the - contents of an image, or record some annotation related directly to the image, and - record that as another presentation state for an image. An application subsequently may - display the image by automatically choosing to use the more recently saved or more - specific presentation state, or may use the more general default presentation state for - all images but notify the user that alternative presentation states are available. - + For example, an acquisition device may automatically store appropriate presentation states for series of images as they are reconstructed that represent adequate defaults. A user or algorithm may subsequently determine a more appropriate presentation state that more effectively displays the contents of an image, or record some annotation related directly to the image, and record that as another presentation state for an image. An application subsequently may display the image by automatically choosing to use the more recently saved or more specific presentation state, or may use the more general default presentation state for all images but notify the user that alternative presentation states are available. - Choice of the same presentation - state to display a grayscale image on two devices claiming conformance to these SOP - Classes implies through the definition of the P-Value space that the displayed image on - both devices will be perceptually similar within the limits defined in, regardless of the - actual capabilities of the display systems. - + Choice of the same presentation state to display a grayscale image on two devices claiming conformance to these SOP Classes implies through the definition of the P-Value space that the displayed image on both devices will be perceptually similar within the limits defined in , regardless of the actual capabilities of the display systems. - Choice of the same presentation - state to display a color image on two devices claiming conformance to these SOP Classes - implies through the definition of the PCS-Value space that the displayed image on both - devices will appear similar in color regardless of the actual capabilities of the - display systems. - + Choice of the same presentation state to display a color image on two devices claiming conformance to these SOP Classes implies through the definition of the PCS-Value space that the displayed image on both devices will appear similar in color regardless of the actual capabilities of the display systems. - DICOM color images without an - embedded optional ICC profile have no defined color space, regardless of their - representation. The implementation creating a Color Softcopy Presentation State with an - ICC profile is explicitly defining a color space in which to interpret that image, even - if one was not known at the time that the image was created. Often a well-known color - space such as sRGB will be used in the presentation state under such circumstances. - + DICOM color images without an embedded optional ICC profile have no defined color space, regardless of their representation. The implementation creating a Color Softcopy Presentation State with an ICC profile is explicitly defining a color space in which to interpret that image, even if one was not known at the time that the image was created. Often a well-known color space such as sRGB will be used in the presentation state under such circumstances. @@ -34739,93 +24878,40 @@
Pixel Transformation Sequence - The Softcopy Presentation State Storage SOP Classes - support a sequence of transformations that completely define the conversion of a stored image into a - displayed image. - - The sequence of transformations from stored pixel - values into P-Values or PCS-Values is explicitly defined in a conceptual model. The actual sequence - implemented may differ but must result in the same appearance. - - describes this sequence of transformations. - + The Softcopy Presentation State Storage SOP Classes support a sequence of transformations that completely define the conversion of a stored image into a displayed image. + The sequence of transformations from stored pixel values into P-Values or PCS-Values is explicitly defined in a conceptual model. The actual sequence implemented may differ but must result in the same appearance. describes this sequence of transformations. - Even though a Composite Image Storage - SOP Class may not include some Modules that are part of the described transformations, the - Softcopy Presentation State Storage SOP Classes do include them. For example, the CT Image - Storage SOP Class includes Rescale Slope and Intercept in the CT Image Module, but does not - include the Modality LUT Module, and hence is restricted to the description of linear - transformations. A saved presentation state that refers to a CT Image Storage SOP Instance - may include a Modality LUT, and hence may apply a non-linear transformation. - + Even though a Composite Image Storage SOP Class may not include some Modules that are part of the described transformations, the Softcopy Presentation State Storage SOP Classes do include them. For example, the CT Image Storage SOP Class includes Rescale Slope and Intercept in the CT Image Module, but does not include the Modality LUT Module, and hence is restricted to the description of linear transformations. A saved presentation state that refers to a CT Image Storage SOP Instance may include a Modality LUT, and hence may apply a non-linear transformation. - For the shutter, annotation and spatial - transformations, the order in which they are applied relative to the other transformations - should not result in a different appearance. The one exception is when a spatial - transformation is applied that involves magnification implemented with interpolation. In - this case, whether the interpolation is performed before or after the contrast - transformations (such as VOI LUT) may result in a slightly different appearance. It is not - considered necessary to constrain this sequence more precisely. - + For the shutter, annotation and spatial transformations, the order in which they are applied relative to the other transformations should not result in a different appearance. The one exception is when a spatial transformation is applied that involves magnification implemented with interpolation. In this case, whether the interpolation is performed before or after the contrast transformations (such as VOI LUT) may result in a slightly different appearance. It is not considered necessary to constrain this sequence more precisely. - The transformations defined in the Softcopy - Presentation State Storage SOP Classes replace those that may be defined in the Referenced Image SOP - Instance. If a particular transformation is absent in the Softcopy Presentation State Storage SOP Class, - then it shall be assumed to be an identity transformation, and any equivalent transformation, if - present, in the Referenced Image SOP Instance shall NOT be used instead. - - Values of MONOCHROME1 and MONOCHROME2 for - Photometric Interpretation (0028,0004) in the Referenced Image SOP Instance shall be ignored, since - their effect is defined by the application of the grayscale presentation state transformations. - + The transformations defined in the Softcopy Presentation State Storage SOP Classes replace those that may be defined in the Referenced Image SOP Instance. If a particular transformation is absent in the Softcopy Presentation State Storage SOP Class, then it shall be assumed to be an identity transformation, and any equivalent transformation, if present, in the Referenced Image SOP Instance shall NOT be used instead. + Values of MONOCHROME1 and MONOCHROME2 for Photometric Interpretation (0028,0004) in the Referenced Image SOP Instance shall be ignored, since their effect is defined by the application of the grayscale presentation state transformations. - These requirements are in order to achieve - complete definition of the entire transformation in the Softcopy Presentation State Storage SOP - Classes, and not to depend on the content of the Referenced Image SOP Instance, which may change. - + These requirements are in order to achieve complete definition of the entire transformation in the Softcopy Presentation State Storage SOP Classes, and not to depend on the content of the Referenced Image SOP Instance, which may change. - The Referenced Image Storage SOP Instance may also - contain bit-mapped overlays. The Softcopy Presentation State Storage SOP Classes specify a mechanism for - turning these on or off (i.e., displaying them or not). - - The presentation related Attributes of the Softcopy - Presentation State Storage SOP Classes are immutable. They shall never be modified or updated; only a - derived SOP Instance with a new SOP Instance UID may be created to represent a different presentation. - - When a Supplemental Palette Color LUT is present in - a grayscale Referenced Image Storage SOP Instance: - + The Referenced Image Storage SOP Instance may also contain bit-mapped overlays. The Softcopy Presentation State Storage SOP Classes specify a mechanism for turning these on or off (i.e., displaying them or not). + The presentation related Attributes of the Softcopy Presentation State Storage SOP Classes are immutable. They shall never be modified or updated; only a derived SOP Instance with a new SOP Instance UID may be created to represent a different presentation. + When a Supplemental Palette Color LUT is present in a grayscale Referenced Image Storage SOP Instance: - The grayscale pipeline in any applicable - Grayscale Softcopy Presentation State Storage SOP Instance or Blended Softcopy Presentation - State Storage SOP Instance shall be applied only to the range of grayscale stored pixel values, - and the presentation state shall not affect the rendering of the indexed color values. - + The grayscale pipeline in any applicable Grayscale Softcopy Presentation State Storage SOP Instance or Blended Softcopy Presentation State Storage SOP Instance shall be applied only to the range of grayscale stored pixel values, and the presentation state shall not affect the rendering of the indexed color values. - A Color Softcopy Presentation State Storage - SOP Instance shall not be applied. - + A Color Softcopy Presentation State Storage SOP Instance shall not be applied. - A Pseudo-color Softcopy Presentation State - Storage SOP Instance may be applied, in which case the Supplemental Palette Color LUT - information shall be ignored. - + A Pseudo-color Softcopy Presentation State Storage SOP Instance may be applied, in which case the Supplemental Palette Color LUT information shall be ignored. - No mechanism for separately specifying - color consistency of the colors in the Supplemental Palette Color LUT is presently defined, only - the optional inclusion of an ICC profile in the image instance. - + No mechanism for separately specifying color consistency of the colors in the Supplemental Palette Color LUT is presently defined, only the optional inclusion of an ICC profile in the image instance. @@ -34843,336 +24929,135 @@ Grayscale Transformations
Modality LUT - The Modality LUT operation applies only to - grayscale values. - - The Modality LUT transformation transforms - the manufacturer dependent pixel values into pixel values that are meaningful for the modality - and are manufacturer independent (e.g., Hounsfield number for CT modalities, Optical Density for - film digitizers). These may represent physical units or be dimensionless. The Modality LUT in - the Presentation State is modality dependent and is analogous to the same Module in an Image. - + The Modality LUT operation applies only to grayscale values. + The Modality LUT transformation transforms the manufacturer dependent pixel values into pixel values that are meaningful for the modality and are manufacturer independent (e.g., Hounsfield number for CT modalities, Optical Density for film digitizers). These may represent physical units or be dimensionless. The Modality LUT in the Presentation State is modality dependent and is analogous to the same Module in an Image. - In some cases, such as the CT - Image Storage SOP Class, the same conceptual step as the Modality LUT is specified - in another form, for example as Rescale Slope and Rescale Intercept Attributes in - the CT Image Module, though the Modality LUT Module is not part of the CT Image IOD. - + In some cases, such as the CT Image Storage SOP Class, the same conceptual step as the Modality LUT is specified in another form, for example as Rescale Slope and Rescale Intercept Attributes in the CT Image Module, though the Modality LUT Module is not part of the CT Image IOD. - Image pixel values with a value - of Pixel Padding Value (0028,0120) in the referenced image, or within the range - specified by Pixel Padding Value (0028,0120) and Pixel Padding Range Limit - (0028,0121) (if present in the referenced image) shall be accounted for prior to - entry to the Modality LUT stage. See the definition of Pixel Padding Value in. - Neither Pixel Padding Value (0028,0120) nor Pixel Padding Range Limit (0028,0121) - are encoded in the Presentation State Instance. - + Image pixel values with a value of Pixel Padding Value (0028,0120) in the referenced image, or within the range specified by Pixel Padding Value (0028,0120) and Pixel Padding Range Limit (0028,0121) (if present in the referenced image) shall be accounted for prior to entry to the Modality LUT stage. See the definition of Pixel Padding Value in . Neither Pixel Padding Value (0028,0120) nor Pixel Padding Range Limit (0028,0121) are encoded in the Presentation State Instance. - In the case of a linear transformation, the - Modality LUT is described by the Rescale Slope (0028,1053) and Rescale Intercept (0028,1052). In - the case of a non-linear transformation, the Modality LUT is described by the Modality LUT - Sequence. The rules for application of the Modality LUT are defined in - . - - If the Modality LUT or equivalent - Attributes are part of both the Image and the Presentation State, then the Presentation State - Modality LUT shall be used instead of the Image Modality LUT or equivalent Attributes in the - Image. If the Modality LUT is not present in the Presentation State it shall be assumed to be an - identity transformation. Any Modality LUT or equivalent Attributes in the Image shall not be - used. - + In the case of a linear transformation, the Modality LUT is described by the Rescale Slope (0028,1053) and Rescale Intercept (0028,1052). In the case of a non-linear transformation, the Modality LUT is described by the Modality LUT Sequence. The rules for application of the Modality LUT are defined in . + If the Modality LUT or equivalent Attributes are part of both the Image and the Presentation State, then the Presentation State Modality LUT shall be used instead of the Image Modality LUT or equivalent Attributes in the Image. If the Modality LUT is not present in the Presentation State it shall be assumed to be an identity transformation. Any Modality LUT or equivalent Attributes in the Image shall not be used.
Mask - The Mask operation applies only to - grayscale values. - - The mask transformation may be applied in - the case of multi-frame images for which other frames at a fixed frame position or time interval - relative to the current frame may be subtracted from the current frame. Multiple mask frames may - be averaged, and sub-pixel shifted before subtraction. - - This transformation uses the Mask Module as - used in the X-Ray Angiography Image Storage SOP Class, though it may be applied to any Image - Storage SOP Instance that contains a multi-frame image. - - In the case of X-Ray images, the - subtraction is specified to take place in a space logarithmic to X-Ray intensity. If the stored - pixel values are not already in such a space, an implementation defined transformation to such a - space must be performed prior to subtraction. If a Modality LUT Module is present as well as a - Mask Module, then the Modality LUT shall specify a transformation into such a logarithmic space, - otherwise it shall not be present (even though a Modality LUT may be present in the referenced - image(s), which shall be ignored). - + The Mask operation applies only to grayscale values. + The mask transformation may be applied in the case of multi-frame images for which other frames at a fixed frame position or time interval relative to the current frame may be subtracted from the current frame. Multiple mask frames may be averaged, and sub-pixel shifted before subtraction. + This transformation uses the Mask Module as used in the X-Ray Angiography Image Storage SOP Class, though it may be applied to any Image Storage SOP Instance that contains a multi-frame image. + In the case of X-Ray images, the subtraction is specified to take place in a space logarithmic to X-Ray intensity. If the stored pixel values are not already in such a space, an implementation defined transformation to such a space must be performed prior to subtraction. If a Modality LUT Module is present as well as a Mask Module, then the Modality LUT shall specify a transformation into such a logarithmic space, otherwise it shall not be present (even though a Modality LUT may be present in the referenced image(s), which shall be ignored). - In the case of an XA or XRF - image, if the Pixel Intensity Relationship (0028,1040) in the image is LOG, then - even though a Modality LUT would be present in the image (to map pixel values back - to linear to X-Ray intensity), no Modality LUT would be present in the presentation - state (i.e., the Modality LUT would be an identity transformation) since log values - are required for subtraction. See - . - + In the case of an XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the image is LOG, then even though a Modality LUT would be present in the image (to map pixel values back to linear to X-Ray intensity), no Modality LUT would be present in the presentation state (i.e., the Modality LUT would be an identity transformation) since log values are required for subtraction. See . - In the case of an XA or XRF - image, if the Pixel Intensity Relationship (0028,1040) is LIN, then no Modality LUT - would be present in the image, but a Modality LUT would need to be present in the - presentation state since log values are required for subtraction. - + In the case of an XA or XRF image, if the Pixel Intensity Relationship (0028,1040) is LIN, then no Modality LUT would be present in the image, but a Modality LUT would need to be present in the presentation state since log values are required for subtraction. - In the case of an XA or XRF - image, if the Pixel Intensity Relationship (0028,1040) in the image is DISP, then - even though a Modality LUT may or may not be present in the image (to map pixel - values back to linear to X-Ray intensity), a different Modality LUT would be present - in the presentation state if the creator of the presentation state could create a - transformation from DISP pixel values to a logarithmic space for subtraction, or the - Modality LUT in the presentation state would be an identity transformation if the - DISP pixel values were known to already be log values required for subtraction. - + In the case of an XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the image is DISP, then even though a Modality LUT may or may not be present in the image (to map pixel values back to linear to X-Ray intensity), a different Modality LUT would be present in the presentation state if the creator of the presentation state could create a transformation from DISP pixel values to a logarithmic space for subtraction, or the Modality LUT in the presentation state would be an identity transformation if the DISP pixel values were known to already be log values required for subtraction. - The result will be a signed value with a - bit length one longer than the source frames. - - When there is no difference between - corresponding pixel values, the subtracted image pixel will have a value of 0. - - If a pixel in the current frame has a - greater value than in the mask frame, then the resulting frame shall have a positive value. If - it has a lesser value, then the resulting frame shall have a negative value. - + The result will be a signed value with a bit length one longer than the source frames. + When there is no difference between corresponding pixel values, the subtracted image pixel will have a value of 0. + If a pixel in the current frame has a greater value than in the mask frame, then the resulting frame shall have a positive value. If it has a lesser value, then the resulting frame shall have a negative value.
VOI LUT - The VOI LUT operation applies only to - grayscale values. - - The value of interest (VOI) LUT - transformation transforms the modality pixel values into pixel values that are meaningful for - the user or the application. - + The VOI LUT operation applies only to grayscale values. + The value of interest (VOI) LUT transformation transforms the modality pixel values into pixel values that are meaningful for the user or the application. - Photometric Interpretation (0028,0004) - is ignored, since its effect is defined by the application of the grayscale transformations. - + Photometric Interpretation (0028,0004) is ignored, since its effect is defined by the application of the grayscale transformations. - The Softcopy VOI LUT Module in the - Presentation State is analogous to the VOI LUT Module in an Image. - - In the case of a linear transformation, the - VOI LUT is described by the Window Center (0028,1050) and Window Width (0028,1051). In the case - of a non-linear transformation, the VOI LUT is described by the VOI LUT Sequence. A VOI LUT - Function (0028,1056) may be present to define a potentially non-linear interpretation (e.g., - SIGMOID) of the values of Window Center (0028,1050) and Window Width (0028,1051). The rules for - application of the VOI LUT are defined in. - - The VOI LUT may have sections with negative - slope. - + The Softcopy VOI LUT Module in the Presentation State is analogous to the VOI LUT Module in an Image. + In the case of a linear transformation, the VOI LUT is described by the Window Center (0028,1050) and Window Width (0028,1051). In the case of a non-linear transformation, the VOI LUT is described by the VOI LUT Sequence. A VOI LUT Function (0028,1056) may be present to define a potentially non-linear interpretation (e.g., SIGMOID) of the values of Window Center (0028,1050) and Window Width (0028,1051). The rules for application of the VOI LUT are defined in . + The VOI LUT may have sections with negative slope. - In the Basic Print Service Class a VOI - LUT may not have negative slope. - + In the Basic Print Service Class a VOI LUT may not have negative slope. - If a VOI LUT is part of both the Image and - the Presentation State then the Presentation State VOI LUT shall be used instead of the Image - VOI LUT. If a VOI LUT (that applies to the Image) is not present in the Presentation State, it - shall be assumed to be an identity transformation. Any VOI LUT or equivalent values in the Image - shall not be used. - + If a VOI LUT is part of both the Image and the Presentation State then the Presentation State VOI LUT shall be used instead of the Image VOI LUT. If a VOI LUT (that applies to the Image) is not present in the Presentation State, it shall be assumed to be an identity transformation. Any VOI LUT or equivalent values in the Image shall not be used.
Presentation LUT - The Presentation LUT operation applies only - to grayscale values. - - The Presentation LUT transformation - transforms the pixel values into P-Values, a device independent perceptually linear space as - defined in. It may be an - identity function if the output of the VOI LUT transformation is in P-Values. - + The Presentation LUT operation applies only to grayscale values. + The Presentation LUT transformation transforms the pixel values into P-Values, a device independent perceptually linear space as defined in . It may be an identity function if the output of the VOI LUT transformation is in P-Values. - If the Presentation LUT and VOI LUT - step are identity transformations, and the Mask Module is absent, then the output of the - Modality LUT must be, by definition, P-Values. - + If the Presentation LUT and VOI LUT step are identity transformations, and the Mask Module is absent, then the output of the Modality LUT must be, by definition, P-Values. - No output space other than P-Values is - defined for the Grayscale Softcopy Presentation State Storage SOP Classes. - - In the case of a linear transformation, the - Presentation LUT is described by the Presentation LUT Shape (2050,0020). In the case of a - non-linear transformation, the Presentation LUT is described by the Presentation LUT Sequence. - The rules for application of the Presentation LUT are defined in - . - + No output space other than P-Values is defined for the Grayscale Softcopy Presentation State Storage SOP Classes. + In the case of a linear transformation, the Presentation LUT is described by the Presentation LUT Shape (2050,0020). In the case of a non-linear transformation, the Presentation LUT is described by the Presentation LUT Sequence. The rules for application of the Presentation LUT are defined in . - Since the grayscale - transformation pipeline fully defines all transformations applied to the stored - pixel values in the referenced image object, the value of Photometric Interpretation - (0028,0004) in the referenced image object is ignored and overridden. This implies - that either the creator of the presentation state chose a pipeline that reflects the - Photometric Interpretation (0028,0004), or chose to ignore or override the - Photometric Interpretation, and invert the image relative to what is specified by - Photometric Interpretation. If the Modality LUT and VOI LUT do not have a negative - slope, one can achieve the effect of inversion of the polarity of an image by - choosing Presentation LUT Shape of IDENTITY or INVERSE that displays the minimum - pixel value as white rather than black in the case of a Photometric Interpretation - of MONOCHROME2, or black rather than white in the case of a Photometric - Interpretation of MONOCHROME1. If Presentation LUT Data is sent, then one can invert - the value of the entries in the LUT table to achieve inversion of polarity. - + Since the grayscale transformation pipeline fully defines all transformations applied to the stored pixel values in the referenced image object, the value of Photometric Interpretation (0028,0004) in the referenced image object is ignored and overridden. This implies that either the creator of the presentation state chose a pipeline that reflects the Photometric Interpretation (0028,0004), or chose to ignore or override the Photometric Interpretation, and invert the image relative to what is specified by Photometric Interpretation. If the Modality LUT and VOI LUT do not have a negative slope, one can achieve the effect of inversion of the polarity of an image by choosing Presentation LUT Shape of IDENTITY or INVERSE that displays the minimum pixel value as white rather than black in the case of a Photometric Interpretation of MONOCHROME2, or black rather than white in the case of a Photometric + Interpretation of MONOCHROME1. If Presentation LUT Data is sent, then one can invert the value of the entries in the LUT table to achieve inversion of polarity. - The minimum P-Value (zero) - always commands that the lowest intensity be displayed. - + The minimum P-Value (zero) always commands that the lowest intensity be displayed. - No separate Polarity - transformation is defined. - + No separate Polarity transformation is defined. - A Softcopy Presentation LUT Module is - always present in a Presentation State. If a Presentation LUT is present in the Image then the - Presentation State Presentation LUT shall be used instead of the Image Presentation LUT. - + A Softcopy Presentation LUT Module is always present in a Presentation State. If a Presentation LUT is present in the Image then the Presentation State Presentation LUT shall be used instead of the Image Presentation LUT.
Color Transformations
Profile Connection Space Transformation - The Profile Connection Space Transformation - operation applies only to color images, including true color (e.g., RGB) and pseudo-color (e.g., - PALETTE COLOR) images, grayscale images for which a Palette Color LUT has been specified in the - Presentation State, and the RGB output values of a blending operation. - - The ICC Profile is an Input Profile. That - is, it describes the color characteristics of a (possibly hypothetical) device that was used to - generate the input color values. - - The intent is that a rendering device will - use this information to achieve color consistency. Typically this will be performed by - calibration of the output device to create an ICC Display or Output Profile, the conversion of - pixel values using the ICC Input Profile into Profile Connection Space, followed by conversion - using the ICC Display or Output Profile into values suitable for rendering on the output device. - However, the exact mechanisms used are beyond the scope of the Standard to define. - + The Profile Connection Space Transformation operation applies only to color images, including true color (e.g., RGB) and pseudo-color (e.g., PALETTE COLOR) images, grayscale images for which a Palette Color LUT has been specified in the Presentation State, and the RGB output values of a blending operation. + The ICC Profile is an Input Profile. That is, it describes the color characteristics of a (possibly hypothetical) device that was used to generate the input color values. + The intent is that a rendering device will use this information to achieve color consistency. Typically this will be performed by calibration of the output device to create an ICC Display or Output Profile, the conversion of pixel values using the ICC Input Profile into Profile Connection Space, followed by conversion using the ICC Display or Output Profile into values suitable for rendering on the output device. However, the exact mechanisms used are beyond the scope of the Standard to define. - The means of achieving color - consistency depends to a large extent on the nature of the material and the intent - of the application. The process is more complicated than simply achieving - colorimetric accuracy, which is trivial but does not produce satisfactory results. - The transformations may take into account such matters as - + The means of achieving color consistency depends to a large extent on the nature of the material and the intent of the application. The process is more complicated than simply achieving colorimetric accuracy, which is trivial but does not produce satisfactory results. The transformations may take into account such matters as - physical factors such - as the ambient light of the viewing environment (viewing flare) and the - nature of different illuminants - + physical factors such as the ambient light of the viewing environment (viewing flare) and the nature of different illuminants - psychovisual factors in - the observer - + psychovisual factors in the observer - the preferences of the - observer - + the preferences of the observer - the consistency intent, - whether it be to reproduce the colors perceived by an observer of - + the consistency intent, whether it be to reproduce the colors perceived by an observer of - the original - scene, - + the original scene, - the media being - reproduced, such as a print or transparency, as viewed under - specified conditions. - + the media being reproduced, such as a print or transparency, as viewed under specified conditions. - Implementations of color - management schemes are typically provided in operating systems, libraries and tool - kits, and the exact details are usually beyond the control of the DICOM application - developer. Accordingly, it is normally sufficient to define a source of pixel - values, and a corresponding ICC Input Profile for the device that captured or - generated them. - + Implementations of color management schemes are typically provided in operating systems, libraries and tool kits, and the exact details are usually beyond the control of the DICOM application developer. Accordingly, it is normally sufficient to define a source of pixel values, and a corresponding ICC Input Profile for the device that captured or generated them. - When a color image is rendered - on grayscale display, the behavior is not defined. Since the L* value of a CIELab - representation of the PCS is not dissimilar to the Barten model used in the GSDF, a - reasonable approach would be to interpret it as a P-Value. - + When a color image is rendered on grayscale display, the behavior is not defined. Since the L* value of a CIELab representation of the PCS is not dissimilar to the Barten model used in the GSDF, a reasonable approach would be to interpret it as a P-Value. - An ICC Profile is always present in a - Color, Pseudo-Color or Blended Presentation State. If an ICC Profile is present in the Image - then the Presentation State ICC Profile shall be used instead of the Image ICC Profile. - + An ICC Profile is always present in a Color, Pseudo-Color or Blended Presentation State. If an ICC Profile is present in the Image then the Presentation State ICC Profile shall be used instead of the Image ICC Profile.
White Point (Informative) - D50 means black body radiation of an object - at 5000 degrees K, and includes lots of red, which looks "natural". D65 is bluer, more like - "cloudy days", but human eyes are more sensitive to blue. While monitors seem to be in the - D50-D100 range, light boxes are about D110 (11000K). - - The ICC PCS always uses a white point of - D50. - - In an ICC Input Profile, the - chromaticAdaptationTag encodes a conversion of an XYZ color from the actual illumination source - to the PCS illuminant (D50), and may be useful if the actual illumination source is not D50. The - actual illumination source may also be defined in the mediaWhitePointTag. However, with a - perceptual rendering intent, neither of these tags are required to be used by the color - management system, nor do they have any specified rendering behavior (as opposed to their use - with absolute and relative colorimetric rendering intents). - - It is beyond the scope of DICOM to define a - required or suggested white point for rendering, since an appropriate choice depends on a - knowledge of the display device or media characteristics and the viewing environment. - + D50 means black body radiation of an object at 5000 degrees K, and includes lots of red, which looks "natural". D65 is bluer, more like "cloudy days", but human eyes are more sensitive to blue. While monitors seem to be in the D50-D100 range, light boxes are about D110 (11000K). + The ICC PCS always uses a white point of D50. + In an ICC Input Profile, the chromaticAdaptationTag encodes a conversion of an XYZ color from the actual illumination source to the PCS illuminant (D50), and may be useful if the actual illumination source is not D50. The actual illumination source may also be defined in the mediaWhitePointTag. However, with a perceptual rendering intent, neither of these tags are required to be used by the color management system, nor do they have any specified rendering behavior (as opposed to their use with absolute and relative colorimetric rendering intents). + It is beyond the scope of DICOM to define a required or suggested white point for rendering, since an appropriate choice depends on a knowledge of the display device or media characteristics and the viewing environment.
@@ -35188,92 +25073,45 @@ - The common spatial and annotation - transformations apply to any device-independent values, whether they be grayscale P-Values or color - PCS-Values, for any type of presentation state. - - The values with which to render annotations are - encoded as device-independent values, either as grayscale P-Values or as color PCS-Values. In the - case of PCS-Values, CIELab values are encoded, and defined by reference to a D50 illuminant. - - Grayscale presentation states may specify - annotations in color for rendering on a color output device. - - The mechanism for mapping grayscale P-Values - and color PCS-values to the same display is implementation-dependent and not defined by the - Standard. - + The common spatial and annotation transformations apply to any device-independent values, whether they be grayscale P-Values or color PCS-Values, for any type of presentation state. + The values with which to render annotations are encoded as device-independent values, either as grayscale P-Values or as color PCS-Values. In the case of PCS-Values, CIELab values are encoded, and defined by reference to a D50 illuminant. + Grayscale presentation states may specify annotations in color for rendering on a color output device. + The mechanism for mapping grayscale P-Values and color PCS-values to the same display is implementation-dependent and not defined by the Standard.
Shutter - The Shutter transformation provides the - ability to exclude the perimeter outside a region of an image. A gray level may be specified to - replace the area under the shutter. - - One form of this transformation uses the - Display Shutter Module as used in the X-Ray Angiography Image Storage SOP Class, though it may - be applied to any Image Storage SOP Instance, including single frame images. - - Another form uses a bit-mapped overlay to - indicate arbitrary areas of the image that should be excluded from display by replacement with a - specified gray level, as described in the Bitmap Display Shutter Module. - + The Shutter transformation provides the ability to exclude the perimeter outside a region of an image. A gray level may be specified to replace the area under the shutter. + One form of this transformation uses the Display Shutter Module as used in the X-Ray Angiography Image Storage SOP Class, though it may be applied to any Image Storage SOP Instance, including single frame images. + Another form uses a bit-mapped overlay to indicate arbitrary areas of the image that should be excluded from display by replacement with a specified gray level, as described in the Bitmap Display Shutter Module. - Since annotations follow the - shutter operation in the pipeline, annotations in shuttered regions are not obscured - and are visible. - + Since annotations follow the shutter operation in the pipeline, annotations in shuttered regions are not obscured and are visible. - Any shutter present in the - referenced image object is ignored (i.e., not applied). - + Any shutter present in the referenced image object is ignored (i.e., not applied).
Pre-Spatial Transformation Annotation - The Pre-Spatial Transformation Annotation - transformation includes the application of bit-mapped overlays as defined in the Overlay Plane - Module, and free unformatted text or vector graphics as described in the Graphic Annotation - Module that are defined in the image pixel space (as opposed to the displayed area space). - + The Pre-Spatial Transformation Annotation transformation includes the application of bit-mapped overlays as defined in the Overlay Plane Module, and free unformatted text or vector graphics as described in the Graphic Annotation Module that are defined in the image pixel space (as opposed to the displayed area space).
Spatial Transformation - Some modalities may not deliver the image - in the desired rotation and need to specify a rotation into the desired position for - presentation. This transformation, specified in the Spatial Transformation Module, includes a - rotation of 90, 180, 270 degrees clockwise followed by a horizontal flip (L <--> R). - Rotation by an arbitrary angle is not supported. - - In addition, selection of a region of the - image pixel space to be displayed is specified in the Displayed Area Module. This may have the - effect of magnifying (or minifying) that region depending on what physical size the display is - instructed to render the selected region. If so, the method of interpolation (or sub-sampling) - is implementation dependent. - + Some modalities may not deliver the image in the desired rotation and need to specify a rotation into the desired position for presentation. This transformation, specified in the Spatial Transformation Module, includes a rotation of 90, 180, 270 degrees clockwise followed by a horizontal flip (L <--> R). Rotation by an arbitrary angle is not supported. + In addition, selection of a region of the image pixel space to be displayed is specified in the Displayed Area Module. This may have the effect of magnifying (or minifying) that region depending on what physical size the display is instructed to render the selected region. If so, the method of interpolation (or sub-sampling) is implementation dependent. - In particular the number of displayed - pixels may be different from the number of image pixels as a result of: - + In particular the number of displayed pixels may be different from the number of image pixels as a result of: - minification (e.g., 1 display - pixel for 4 image pixels), - + minification (e.g., 1 display pixel for 4 image pixels), - magnification (4 display pixels - for each image pixel), - + magnification (4 display pixels for each image pixel), - interpolation (display pixels - derived from values other than those in the image pixels), and - + interpolation (display pixels derived from values other than those in the image pixels), and sub-sampling. @@ -35283,33 +25121,15 @@
Post-Spatial Transformation Annotation - The Post-Spatial Transformation Annotation - transformation includes the application of free unformatted text or vector graphics as described - in the Graphic Annotation Module that are defined in the displayed area space (as opposed to the - image pixel space). - - This implies that the displayed area space - is defined as being the image after all Spatial Transformations have been applied. - - These annotations are rendered in the - displayed space, though they may be anchored to points in either the displayed area or image - pixel space. - + The Post-Spatial Transformation Annotation transformation includes the application of free unformatted text or vector graphics as described in the Graphic Annotation Module that are defined in the displayed area space (as opposed to the image pixel space). + This implies that the displayed area space is defined as being the image after all Spatial Transformations have been applied. + These annotations are rendered in the displayed space, though they may be anchored to points in either the displayed area or image pixel space.
Blending Transformations - The grayscale to color blending transformation - model applies only to a pair of grayscale values, one of which is first mapped to color and then - superimposed upon the other. The resulting values are device independent color PCS-Values. This - process is illustrated in. - - For the purpose of this section, pixels are - referred to as stored pixel values and transformations are defined as point operations on these - values. However, it is likely that pixels from either or both the superimposed and underlying image - sets will have been spatially resampled and hence interpolated or replicated. Such operations do not - affect the conceptual pipeline. - + The grayscale to color blending transformation model applies only to a pair of grayscale values, one of which is first mapped to color and then superimposed upon the other. The resulting values are device independent color PCS-Values. This process is illustrated in . + For the purpose of this section, pixels are referred to as stored pixel values and transformations are defined as point operations on these values. However, it is likely that pixels from either or both the superimposed and underlying image sets will have been spatially resampled and hence interpolated or replicated. Such operations do not affect the conceptual pipeline.
Grayscale to Color Blending Transformation Model @@ -35323,83 +25143,36 @@
Underlying Image Pixels - The Modality LUT and VOI LUT - transformations are applied to the stored pixel values of the underlying image. - - The output range of the VOI LUT - transformation depends either on the width of the linear window or the range of output values of - the LUT defined by the LUT Descriptor. Conceptually, for the purpose of describing the - succeeding blending operation, the smallest pixel value from the range is mapped to 0.0 and the - largest pixel value is mapped to 1.0 and all intermediate values are linearly mapped to the - [0.0..1.0] interval. - + The Modality LUT and VOI LUT transformations are applied to the stored pixel values of the underlying image. + The output range of the VOI LUT transformation depends either on the width of the linear window or the range of output values of the LUT defined by the LUT Descriptor. Conceptually, for the purpose of describing the succeeding blending operation, the smallest pixel value from the range is mapped to 0.0 and the largest pixel value is mapped to 1.0 and all intermediate values are linearly mapped to the [0.0..1.0] interval.
Superimposed Image Pixels - The Modality LUT and VOI LUT - transformations are applied to the stored pixel values of the superimposed image. - - The full output range of the preceding VOI - LUT transformation is implicitly scaled to the entire input range of the Palette Color LUT - Transformation. - - The output range of the RGB values in the - Palette Color LUT Transformation depends on the range of output values of the LUT defined by the - LUT Descriptors. Conceptually, for the purpose of describing the succeeding blending operation, - a LUT entry of 0 is mapped to 0.0 and the largest LUT entry possible is mapped to 1.0 and all - intermediate values are linearly mapped to the [0.0..1.0] interval. - + The Modality LUT and VOI LUT transformations are applied to the stored pixel values of the superimposed image. + The full output range of the preceding VOI LUT transformation is implicitly scaled to the entire input range of the Palette Color LUT Transformation. + The output range of the RGB values in the Palette Color LUT Transformation depends on the range of output values of the LUT defined by the LUT Descriptors. Conceptually, for the purpose of describing the succeeding blending operation, a LUT entry of 0 is mapped to 0.0 and the largest LUT entry possible is mapped to 1.0 and all intermediate values are linearly mapped to the [0.0..1.0] interval. - In practice, the Palette Color LUT - output for the superimposed images is encoded in 8 or 16 bits and hence will have a range of - 0 to 0xFF or 0xFFFF. - + In practice, the Palette Color LUT output for the superimposed images is encoded in 8 or 16 bits and hence will have a range of 0 to 0xFF or 0xFFFF. - The Palette Color LUT used is that encoded - in the Blending Presentation State; any Palette Color LUTs or Supplemental Palette Color LUTs in - the image instances are ignored. - + The Palette Color LUT used is that encoded in the Blending Presentation State; any Palette Color LUTs or Supplemental Palette Color LUTs in the image instances are ignored.
Blending Operation - The inputs to the blending operation are - grayscale values from 0.0 to 1.0 from the underlying image (Yu) and RGB - values from 0.0 to 1.0 from the superimposed image (RGBs), and an opacity - value from 0.0 to 1.0 (A). - - The output is a single image containing RGB - values (RGBo) blended as: - - Ro = Rs - * A + Yu * (1-A) - - Go = Gs - * A + Yu * (1-A) - - Bo = Bs - * A + Yu * (1-A) - + The inputs to the blending operation are grayscale values from 0.0 to 1.0 from the underlying image (Yu) and RGB values from 0.0 to 1.0 from the superimposed image (RGBs), and an opacity value from 0.0 to 1.0 (A). + The output is a single image containing RGB values (RGBo) blended as: + Ro = Rs * A + Yu * (1-A) + Go = Gs * A + Yu * (1-A) + Bo = Bs * A + Yu * (1-A)
Conversion to Profile Connection Space - The output of the blending operation is - implicitly scaled to the gamut of the hypothetical device described by the ICC Input Profile, - resulting in PCS-Values. - + The output of the blending operation is implicitly scaled to the gamut of the hypothetical device described by the ICC Input Profile, resulting in PCS-Values.
Angiography Grayscale Transformations - The XA/XRF Grayscale Softcopy Presentation - State Storage SOP Class supports a sequence of transformations that completely define the conversion - of a stored image into a displayed image. - - The sequence of transformations from stored - pixel values into P-Values is explicitly defined in a conceptual model. The actual sequence - implemented may differ but must result in the same appearance. - - describes this sequence of transformations. - + The XA/XRF Grayscale Softcopy Presentation State Storage SOP Class supports a sequence of transformations that completely define the conversion of a stored image into a displayed image. + The sequence of transformations from stored pixel values into P-Values is explicitly defined in a conceptual model. The actual sequence implemented may differ but must result in the same appearance. describes this sequence of transformations.
XA/XRF Grayscale Image Transformation Model @@ -35413,99 +25186,28 @@
Mask - The Mask transformation consists of mask - subtraction operations as specified by the Attributes of the XA/XRF Presentation State Mask - Module and the Attribute Mask Visibility Percentage of the XA/XRF Presentation State - Presentation Module. - - The mask transformation may be applied in - the case of multi-frame images for which other frames at a fixed frame position or time interval - relative to the current frame may be subtracted from the current frame. Multiple mask frames may - be averaged, and sub-pixel shifted before subtraction. Sub-pixel shift may be specified on a - frame-by-frame base. Different pixel-shifts may be applied to more than one region of a contrast - frame. - - In the case of X-Ray images, the - subtraction is specified to take place in a space logarithmic to X-Ray intensity. If the stored - pixel values are not in a logarithmic space then a Pixel Intensity Relationship LUT shall be - present in the XA/XRF Presentation Mask Module specifying a transformation into such a - logarithmic space, otherwise it shall not be present. If a Modality LUT or Pixel Intensity - Relationship LUT is present in the referenced image(s) it shall be ignored. The Pixel Intensity - Relationship LUT can be specified on a frame-by frame base that can be different for mask and - contrast frames. - + The Mask transformation consists of mask subtraction operations as specified by the Attributes of the XA/XRF Presentation State Mask Module and the Attribute Mask Visibility Percentage of the XA/XRF Presentation State Presentation Module. + The mask transformation may be applied in the case of multi-frame images for which other frames at a fixed frame position or time interval relative to the current frame may be subtracted from the current frame. Multiple mask frames may be averaged, and sub-pixel shifted before subtraction. Sub-pixel shift may be specified on a frame-by-frame base. Different pixel-shifts may be applied to more than one region of a contrast frame. + In the case of X-Ray images, the subtraction is specified to take place in a space logarithmic to X-Ray intensity. If the stored pixel values are not in a logarithmic space then a Pixel Intensity Relationship LUT shall be present in the XA/XRF Presentation Mask Module specifying a transformation into such a logarithmic space, otherwise it shall not be present. If a Modality LUT or Pixel Intensity Relationship LUT is present in the referenced image(s) it shall be ignored. The Pixel Intensity Relationship LUT can be specified on a frame-by frame base that can be different for mask and contrast frames. - For images of the X-Ray - Angiographic Image Storage SOP Class or X-Ray RF Image Storage SOP Class the XA/XRF - Grayscale Softcopy Presentation State allows a Pixel Intensity Relationship LUT to - be specified on a frame-by-frame base. This is an enhancement of the image Modality - LUT that is only applicable for all frames of an image. - + For images of the X-Ray Angiographic Image Storage SOP Class or X-Ray RF Image Storage SOP Class the XA/XRF Grayscale Softcopy Presentation State allows a Pixel Intensity Relationship LUT to be specified on a frame-by-frame base. This is an enhancement of the image Modality LUT that is only applicable for all frames of an image. - In the case of an XA or XRF - image, if the Pixel Intensity Relationship (0028,1040) in the image is LOG, then - even though a Modality LUT would be present in the image (to map pixel values back - to linear X-Ray intensity), no Pixel Intensity Relationship LUT would be present in - the presentation state for any frame since log values are required for subtraction. - See. - - In the case of Enhanced XA or - XRF image, if the Pixel Intensity Relationship (0028,1040) in the frame is LOG, then - even though a Pixel Intensity Relationship LUT would be present in the frame (to map - pixel values back to linear X-Ray intensity, LUT Function (0028,9474) equals - TO_LINEAR), no Pixel Intensity Relationship LUT would be present in the presentation - state for that frame since log values are required for subtraction. See. - + In the case of an XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the image is LOG, then even though a Modality LUT would be present in the image (to map pixel values back to linear X-Ray intensity), no Pixel Intensity Relationship LUT would be present in the presentation state for any frame since log values are required for subtraction. See . + In the case of Enhanced XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the frame is LOG, then even though a Pixel Intensity Relationship LUT would be present in the frame (to map pixel values back to linear X-Ray intensity, LUT Function (0028,9474) equals TO_LINEAR), no Pixel Intensity Relationship LUT would be present in the presentation state for that frame since log values are required for subtraction. See . - In the case of an XA or XRF - image if the Pixel Intensity Relationship (0028,1040) in the image is LIN, then no - Modality LUT would be present in the image, but a Pixel Intensity Relationship LUT - would need to be present (to map pixel values to log values, LUT Function - (0028,9474) equals TO_LOG) in the presentation state for all the frames since log - values are required for subtraction. - - In the case of an Enhanced XA - or XRF image, if the Pixel Intensity Relationship (0028,1040) in the frame is LIN, - then no Pixel Intensity Relationship LUT for the purpose to map pixel values back to - linear X-Ray intensity (LUT Function (0028,9474) equals TO_LINEAR) would be present - in the image, but a Pixel Intensity Relationship LUT would need to be present (to - map pixel values to log values) in the presentation state for that frame since log - values are required for subtraction. - + In the case of an XA or XRF image if the Pixel Intensity Relationship (0028,1040) in the image is LIN, then no Modality LUT would be present in the image, but a Pixel Intensity Relationship LUT would need to be present (to map pixel values to log values, LUT Function (0028,9474) equals TO_LOG) in the presentation state for all the frames since log values are required for subtraction. + In the case of an Enhanced XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the frame is LIN, then no Pixel Intensity Relationship LUT for the purpose to map pixel values back to linear X-Ray intensity (LUT Function (0028,9474) equals TO_LINEAR) would be present in the image, but a Pixel Intensity Relationship LUT would need to be present (to map pixel values to log values) in the presentation state for that frame since log values are required for subtraction. - In the case of an XA or XRF - image, if the Pixel Intensity Relationship (0028,1040) in the image is DISP, then - even though a Modality LUT may or may not be present in the image (to map pixel - values back to linear to X-Ray intensity), a different Pixel Intensity Relationship - LUT would be present in the presentation state if the creator of the presentation - state could create a transformation from DISP pixel values to a logarithmic space - for subtraction, or the Pixel Intensity Relationship LUT in the presentation state - would be an identity transformation if the DISP pixel values were known to already - be log values required for subtraction. - - In the case of an Enhanced XA - or XRF image, if the Pixel Intensity Relationship (0028,1040) in the image is OTHER, - then even though a Pixel Intensity Relationship LUT may or may not be present for - that frame (to map pixel values back to linear to X-Ray intensity), a different - Pixel Intensity Relationship LUT would be present in the presentation state for that - frame if the creator of the presentation state could create a transformation from - OTHER pixel values to a logarithmic space for subtraction, or the Pixel Intensity - Relationship LUT in the presentation state would be an identity transformation if - the OTHER pixel values were known to already be log values required for subtraction. - + In the case of an XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the image is DISP, then even though a Modality LUT may or may not be present in the image (to map pixel values back to linear to X-Ray intensity), a different Pixel Intensity Relationship LUT would be present in the presentation state if the creator of the presentation state could create a transformation from DISP pixel values to a logarithmic space for subtraction, or the Pixel Intensity Relationship LUT in the presentation state would be an identity transformation if the DISP pixel values were known to already be log values required for subtraction. + In the case of an Enhanced XA or XRF image, if the Pixel Intensity Relationship (0028,1040) in the image is OTHER, then even though a Pixel Intensity Relationship LUT may or may not be present for that frame (to map pixel values back to linear to X-Ray intensity), a different Pixel Intensity Relationship LUT would be present in the presentation state for that frame if the creator of the presentation state could create a transformation from OTHER pixel values to a logarithmic space for subtraction, or the Pixel Intensity Relationship LUT in the presentation state would be an identity transformation if the OTHER pixel values were known to already be log values required for subtraction. - Notes 2, 3 and 4 are summarized - in - + Notes 2, 3 and 4 are summarized in @@ -35514,15 +25216,10 @@
@@ -35532,8 +25229,7 @@ LIN @@ -35549,9 +25245,7 @@ DISP or OTHER @@ -35560,25 +25254,14 @@
Edge Enhancement - The Edge Enhancement transformation - consists of filter operations to enhance the display of the pixel data as specified by the - Attribute Display Filter Percentage of the XA/XRF Presentation State Presentation Module. - + The Edge Enhancement transformation consists of filter operations to enhance the display of the pixel data as specified by the Attribute Display Filter Percentage of the XA/XRF Presentation State Presentation Module.
Advanced Blending Transformations - The advanced blending transformation model - applies to multiple color inputs and uses foreground blending or equal blending. - - Several transformations in this IOD affect the - input prior to its use in blending as depicted in. - - Grayscale inputs that have no associated Color - LUT information shall have the normal grayscale processing and then be converted to a full color - image by setting R equals G equals B. - + The advanced blending transformation model applies to multiple color inputs and uses foreground blending or equal blending. + Several transformations in this IOD affect the input prior to its use in blending as depicted in . + Grayscale inputs that have no associated Color LUT information shall have the normal grayscale processing and then be converted to a full color image by setting R equals G equals B.
Color and Threshold Application @@ -35590,22 +25273,11 @@
- Padding pixels in an input are given an opacity - value zero and shall be set to 0 for Red, Green, and Blue. - - The foreground method blends two inputs. The - first input uses an opacity of Relative Opacity (0070,0403) and the second input uses an opacity of - (1 - Relative Opacity (0070,0403) ). - - If both the inputs are padding values then the - result is padding value. - - If one of the values is padding value then the - result is the non-padding value. - - If both pixels have values then result is - Relative Opacity * first value + (1 - Relative Opacity) * second value. - + Padding pixels in an input are given an opacity value zero and shall be set to 0 for Red, Green, and Blue. + The foreground method blends two inputs. The first input uses an opacity of Relative Opacity (0070,0403) and the second input uses an opacity of (1 - Relative Opacity (0070,0403) ). + If both the inputs are padding values then the result is padding value. + If one of the values is padding value then the result is the non-padding value. + If both pixels have values then result is Relative Opacity * first value + (1 - Relative Opacity) * second value.
Foreground Blending @@ -35617,23 +25289,11 @@
- The Equal blending mode blends two or more - inputs where for each pixel location the opacity is calculated as 1.0 divided by the number of - non-padding pixels. The result pixel blends all non-padding pixels using the calculated opacity. - - If an input pixel value is the padding-value - then the Relative Opacity for that input pixel is zero. - - If an input pixel value is not the padding - value then the Relative Opacity for that pixel is 1 / (number of input pixels that are non-padding - pixels). - - The result value is the sum for all input - pixels of the input pixel value * Relative Opacity. - - If all the inputs pixels are padding values - then the result is padding value. - + The Equal blending mode blends two or more inputs where for each pixel location the opacity is calculated as 1.0 divided by the number of non-padding pixels. The result pixel blends all non-padding pixels using the calculated opacity. + If an input pixel value is the padding-value then the Relative Opacity for that input pixel is zero. + If an input pixel value is not the padding value then the Relative Opacity for that pixel is 1 / (number of input pixels that are non-padding pixels). + The result value is the sum for all input pixels of the input pixel value * Relative Opacity. + If all the inputs pixels are padding values then the result is padding value.
Equal Blending @@ -35649,102 +25309,49 @@
Behavior of an SCP - In addition to the behavior for the Storage Service - Class specified in - - Behavior of an SCP, the following additional requirements are specified for the Softcopy Presentation - State Storage SOP Classes: - + In addition to the behavior for the Storage Service Class specified in Behavior of an SCP, the following additional requirements are specified for the Softcopy Presentation State Storage SOP Classes: - a display device acting as an SCP of these - SOP Classes shall make all mandatory presentation Attributes available for application to the - referenced images at the discretion of the display device user, for all Image Storage SOP - Classes defined in the Conformance Statement for which the Softcopy Presentation State Storage - SOP Class is supported. - + a display device acting as an SCP of these SOP Classes shall make all mandatory presentation Attributes available for application to the referenced images at the discretion of the display device user, for all Image Storage SOP Classes defined in the Conformance Statement for which the Softcopy Presentation State Storage SOP Class is supported. - a display device that is acting as an SCP - of these SOP Classes and that supports compound graphics types shall display the graphics - described in the Compound Graphic Sequence (0070,0209) and shall not display the Items in the - Text Object Sequence (0070,0008) and Graphic Object Sequence (0070,0009) that have the same - Compound Graphic Instance ID (0070,0226) value. - + a display device that is acting as an SCP of these SOP Classes and that supports compound graphics types shall display the graphics described in the Compound Graphic Sequence (0070,0209) and shall not display the Items in the Text Object Sequence (0070,0008) and Graphic Object Sequence (0070,0009) that have the same Compound Graphic Instance ID (0070,0226) value. - Though it is not required, a display device - acting as an SCP of the Blending Softcopy Presentation State Storage SOP Class may support the - Spatial Registration Storage SOP Class in order to transform one Frame of Reference into another or - to explicitly identify the relationship between members of two sets of images, and may be able to - resample underlying and superimposed sets of images that differ from each other in orientation and - in-plane and between-plane spatial resolution. - + Though it is not required, a display device acting as an SCP of the Blending Softcopy Presentation State Storage SOP Class may support the Spatial Registration Storage SOP Class in order to transform one Frame of Reference into another or to explicitly identify the relationship between members of two sets of images, and may be able to resample underlying and superimposed sets of images that differ from each other in orientation and in-plane and between-plane spatial resolution.
Conformance - In addition to the Conformance Statement - requirements for the Storage Service Class specified in, the following - additional requirements are specified for the Softcopy Presentation State Storage SOP Classes: - + In addition to the Conformance Statement requirements for the Storage Service Class specified in , the following additional requirements are specified for the Softcopy Presentation State Storage SOP Classes:
Conformance Statement for an SCU - The following issues shall be documented in the - Conformance Statement of any implementation claiming conformance to a Softcopy Presentation State - Storage SOP Class as an SCU: - + The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to a Softcopy Presentation State Storage SOP Class as an SCU: - For an SCU of a Softcopy Presentation - State Storage SOP Class that is creating a SOP Instance of the SOP Class, the manner in - which presentation related Attributes are derived from a displayed image, operator - intervention or defaults, and how they are included in the IOD. - + For an SCU of a Softcopy Presentation State Storage SOP Class that is creating a SOP Instance of the SOP Class, the manner in which presentation related Attributes are derived from a displayed image, operator intervention or defaults, and how they are included in the IOD. - For an SCU of a Softcopy Presentation - State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCU - and may be referenced by instances of the Softcopy Presentation State Storage SOP Class. - + For an SCU of a Softcopy Presentation State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCU and may be referenced by instances of the Softcopy Presentation State Storage SOP Class. - For an SCU of a Softcopy Presentation - State Storage SOP Class whether it supports the Compound Graphic Sequence (0070,0209) and - specifies which compound graphic types can be generated, including additional private - defined compound graphic types. - + For an SCU of a Softcopy Presentation State Storage SOP Class whether it supports the Compound Graphic Sequence (0070,0209) and specifies which compound graphic types can be generated, including additional private defined compound graphic types.
Conformance Statement for an SCP - The following issues shall be documented in the - Conformance Statement of any implementation claiming conformance to a Softcopy Presentation State - Storage SOP Class as an SCP: - + The following issues shall be documented in the Conformance Statement of any implementation claiming conformance to a Softcopy Presentation State Storage SOP Class as an SCP: - For an SCP of a Softcopy Presentation - State Storage SOP Class that is displaying an image referred to by a SOP Instance of the SOP - Class, the manner in which presentation related Attributes are used to influence the display - of an image. - + For an SCP of a Softcopy Presentation State Storage SOP Class that is displaying an image referred to by a SOP Instance of the SOP Class, the manner in which presentation related Attributes are used to influence the display of an image. - For an SCP of a Softcopy Presentation - State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCP - and may be referenced by instances of the Softcopy Presentation State Storage SOP Class. - + For an SCP of a Softcopy Presentation State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCP and may be referenced by instances of the Softcopy Presentation State Storage SOP Class. - For an SCP of a Softcopy Presentation - State Storage SOP Class whether it supports the Compound Graphic Sequence (0070,0209) and - which compound graphic types can be rendered, including additional private defined compound - graphic types. - + For an SCP of a Softcopy Presentation State Storage SOP Class whether it supports the Compound Graphic Sequence (0070,0209) and which compound graphic types can be rendered, including additional private defined compound graphic types.
@@ -35754,11 +25361,7 @@ Structured Reporting Storage SOP Classes (Normative)
Overview - The Structured Reporting Storage SOP Classes extend - the functionality of the Storage Service class (defined in) to - extend the SCP behavior and conformance requirements. - + The Structured Reporting Storage SOP Classes extend the functionality of the Storage Service class (defined in ) to extend the SCP behavior and conformance requirements.
Structured Reporting Storage SOP Class SCU and SCP Behavior @@ -35766,116 +25369,48 @@ Behavior of an SCU
CAD SR SOP Classes - Rendering Intent concept modifiers in the - Mammography CAD SR, Chest CAD SR and Colon CAD SR objects shall be consistent. Content items - marked "For Presentation" shall not be subordinate to content items marked "Not for - Presentation" or "Presentation Optional" in the content tree. Similarly, content items marked - "Presentation Optional" shall not be subordinate to content items marked "Not for Presentation" - in the content tree. - - Content items referenced from another SR - object instance, such as a prior Mammography CAD SR, Chest CAD SR or Colon CAD SR shall be - inserted by-value in the new SR object instance, with appropriate original source observation - context. It is necessary to update Rendering Intent, and referenced content item identifiers for - by-reference relationships, within content items paraphrased from another source. - + Rendering Intent concept modifiers in the Mammography CAD SR, Chest CAD SR and Colon CAD SR objects shall be consistent. Content items marked "For Presentation" shall not be subordinate to content items marked "Not for Presentation" or "Presentation Optional" in the content tree. Similarly, content items marked "Presentation Optional" shall not be subordinate to content items marked "Not for Presentation" in the content tree. + Content items referenced from another SR object instance, such as a prior Mammography CAD SR, Chest CAD SR or Colon CAD SR shall be inserted by-value in the new SR object instance, with appropriate original source observation context. It is necessary to update Rendering Intent, and referenced content item identifiers for by-reference relationships, within content items paraphrased from another source.
Extensible SR SOP Class - The concept of extensibility implies that a - recipient may encounter Content Items, Value Types and Relationship Types that are unanticipated - and unsupported and hence potentially unrenderable. - - An implementation shall identify in its - Conformance Statement which Content Items, Value Types and Relationship Types it creates. - + The concept of extensibility implies that a recipient may encounter Content Items, Value Types and Relationship Types that are unanticipated and unsupported and hence potentially unrenderable. + An implementation shall identify in its Conformance Statement which Content Items, Value Types and Relationship Types it creates.
Behavior of an SCP - An SCP intending to display or otherwise render - a Structured Report shall convey its full meaning in an unambiguous manner, except as described in - . - + An SCP intending to display or otherwise render a Structured Report shall convey its full meaning in an unambiguous manner, except as described in . - "Full meaning" includes not just the - Content Tree (i.e., the Items of the Content Sequence), but all Attributes of the Data Set that - are necessary to properly interpret the Structured Report. This includes those Attributes that - set the initial Observation Context for the Content Tree, i.e., the patient, procedure, and - observer identifiers, and the Completion status and Verification status of the Structured - Report. - + "Full meaning" includes not just the Content Tree (i.e., the Items of the Content Sequence), but all Attributes of the Data Set that are necessary to properly interpret the Structured Report. This includes those Attributes that set the initial Observation Context for the Content Tree, i.e., the patient, procedure, and observer identifiers, and the Completion status and Verification status of the Structured Report. - An Icon Image in an IMAGE reference has no - meaning, and is not required to be rendered. - - For a device, that is both an SCU and an SCP of - these Storage SOP Classes, in addition to the behavior for the Storage Service Class specified in - , the following additional requirements are - specified for Structured Reporting Storage SOP Classes: - + An Icon Image in an IMAGE reference has no meaning, and is not required to be rendered. + For a device, that is both an SCU and an SCP of these Storage SOP Classes, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for Structured Reporting Storage SOP Classes: - an SCP of this SOP Class shall support - Level 2 Conformance as defined in. - + an SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, - Type 2, and Type 3 Attributes defined in the Information Object Definition associated with the - SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition associated with the SOP Class will be stored and may be accessed.
CAD SR SOP Classes - The Mammography CAD SR, Chest CAD SR and - Colon CAD SR objects contain data not only for presentation to the clinician, but also data - solely for use in subsequent mammography CAD analyses. - - The SCU provides rendering guidelines via - "Rendering Intent" concept modifiers associated with "Individual Impression/Recommendation", - "Composite Feature" and "Single Image Finding" content items. The full meaning of the SR is - provided if all content items marked "Presentation Required" are rendered down to the first - instance of "Not for Presentation" or "Presentation Optional" for each branch of the tree. Use - of the SCU's Conformance Statement is recommended if further enhancement of the meaning of the - SR can be accomplished by rendering some or all of the data marked "Presentation Optional". Data - marked "Not for Presentation" should not be rendered by the SCP; it is embedded in the SR - content tree as input to subsequent CAD analysis work steps. - - The SCP may further interpret whether or - not to render a Single Image Finding that has Rendering Intent "Presentation Optional" by - interpreting the value of the CAD Operating Point content item that is subordinate to the - Rendering Intent, if present. If the CAD Operating Point content item is not present, then - rendering of the Single Image Finding may be based on recommendations in the creator's DICOM - Conformance Statement. For further information on the intended use of CAD Operating Point see - . - + The Mammography CAD SR, Chest CAD SR and Colon CAD SR objects contain data not only for presentation to the clinician, but also data solely for use in subsequent mammography CAD analyses. + The SCU provides rendering guidelines via "Rendering Intent" concept modifiers associated with "Individual Impression/Recommendation", "Composite Feature" and "Single Image Finding" content items. The full meaning of the SR is provided if all content items marked "Presentation Required" are rendered down to the first instance of "Not for Presentation" or "Presentation Optional" for each branch of the tree. Use of the SCU's Conformance Statement is recommended if further enhancement of the meaning of the SR can be accomplished by rendering some or all of the data marked "Presentation Optional". Data marked "Not for Presentation" should not be rendered by the SCP; it is embedded in the SR content tree as input to subsequent CAD analysis work steps. + The SCP may further interpret whether or not to render a Single Image Finding that has Rendering Intent "Presentation Optional" by interpreting the value of the CAD Operating Point content item that is subordinate to the Rendering Intent, if present. If the CAD Operating Point content item is not present, then rendering of the Single Image Finding may be based on recommendations in the creator's DICOM Conformance Statement. For further information on the intended use of CAD Operating Point see .
Extensible SR SOP Class - The concept of extensibility implies that a - recipient may encounter Content Items, Value Types and Relationship Types that are unanticipated - and unsupported and hence potentially unrenderable. - - An implementation shall identify in its - Conformance Statement which Content Items, Value Types and Relationship Types it supports. - - Since it may not be possible to render the - entire content in an unambiguous manner because of unrecognized content, an SCP intending to - display or otherwise render an Extensible SR SOP Instance - + The concept of extensibility implies that a recipient may encounter Content Items, Value Types and Relationship Types that are unanticipated and unsupported and hence potentially unrenderable. + An implementation shall identify in its Conformance Statement which Content Items, Value Types and Relationship Types it supports. + Since it may not be possible to render the entire content in an unambiguous manner because of unrecognized content, an SCP intending to display or otherwise render an Extensible SR SOP Instance - shall convey a warning in the - rendering to indicate that unsupported content is present and that this may affect the - meaning of the rendering - + shall convey a warning in the rendering to indicate that unsupported content is present and that this may affect the meaning of the rendering - shall identify in its Conformance - Statement its behavior when encountering unsupported content - + shall identify in its Conformance Statement its behavior when encountering unsupported content
@@ -35883,286 +25418,155 @@
Modification of SR Document Content - A device that is an SR Storage SOP Class SCU may - modify information in a SOP Instance that it has previously sent or received. When this SOP Instance is - modified and sent to an SCP, it shall be assigned a new SOP Instance UID if any of the following - conditions are met: - + A device that is an SR Storage SOP Class SCU may modify information in a SOP Instance that it has previously sent or received. When this SOP Instance is modified and sent to an SCP, it shall be assigned a new SOP Instance UID if any of the following conditions are met: - addition, removal or update of any - Attribute within the SR Document General Module or SR Document Content Module; - + addition, removal or update of any Attribute within the SR Document General Module or SR Document Content Module; - modification of the Series Instance UID - (0020,000E); - + modification of the Series Instance UID (0020,000E); - modification of the Study Instance UID - (0020,000D). - + modification of the Study Instance UID (0020,000D).
Conformance - In addition to the Conformance Statement - requirements for the Storage Service Class specified in, the following - additional requirements are specified for Structured Reporting Storage SOP Classes: - + In addition to the Conformance Statement requirements for the Storage Service Class specified in , the following additional requirements are specified for Structured Reporting Storage SOP Classes:
Conformance Statement for an SCU - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Structured Reporting Storage - SOP Classes as an SCU: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Structured Reporting Storage SOP Classes as an SCU: - The Image or other composite object - Storage SOP Classes that are also supported by the SCU and may be referenced by instances of - Structured Reporting Storage SOP Class. - + The Image or other composite object Storage SOP Classes that are also supported by the SCU and may be referenced by instances of Structured Reporting Storage SOP Class. - The range of Value Types and - Relationship Types that are supported by the SCU. - + The range of Value Types and Relationship Types that are supported by the SCU. - The conditions under which a new SOP - Instance UID is generated for an existing SR Document. - + The conditions under which a new SOP Instance UID is generated for an existing SR Document. - If the implementation provides - Query/Retrieve of Structured Reporting SOP Instances as an SCU, whether it supports the - Optional Keys Concept Name Code Sequence or Content Template Sequence. - + If the implementation provides Query/Retrieve of Structured Reporting SOP Instances as an SCU, whether it supports the Optional Keys Concept Name Code Sequence or Content Template Sequence. - The description of the Value Types and - Relationship Types that are supported by the SCU is particularly important for the Extensible SR - SOP Class. - + The description of the Value Types and Relationship Types that are supported by the SCU is particularly important for the Extensible SR SOP Class.
CAD SR SOP Classes - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Mammography CAD SR SOP - Class as an SCU: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Mammography CAD SR SOP Class as an SCU: - Which types of detections and/or - analyses the device is capable of performing: - + Which types of detections and/or analyses the device is capable of performing: - From detections listed in - Context Group 6014 Mammography Single Image Finding - + From detections listed in Context Group 6014 Mammography Single Image Finding - From analyses listed in - Context Group 6043 Types of Mammography CAD Analysis - + From analyses listed in Context Group 6043 Types of Mammography CAD Analysis - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Chest CAD SR SOP Class - as an SCU: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Chest CAD SR SOP Class as an SCU: - Which types of detections and/or - analyses the device is capable of performing: - + Which types of detections and/or analyses the device is capable of performing: - From detections listed in - Context ID 6101 Chest Finding or Feature, or Context ID 6102 Chest Finding or - Feature Modifier - + From detections listed in Context ID 6101 Chest Finding or Feature, or Context ID 6102 Chest Finding or Feature Modifier - From analyses listed in - Context ID 6137 Types of CAD Analysis - + From analyses listed in Context ID 6137 Types of CAD Analysis - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Colon CAD SR SOP Class - as an SCU: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Colon CAD SR SOP Class as an SCU: - Which types of detections and/or - analyses the device is capable of performing: - + Which types of detections and/or analyses the device is capable of performing: - From detections listed in - Context ID 6201 Colon Finding or Feature - + From detections listed in Context ID 6201 Colon Finding or Feature - From analyses listed in - Context ID 6137 Types of CAD Analysis - + From analyses listed in Context ID 6137 Types of CAD Analysis - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Mammography CAD SR, - Chest CAD SR or Colon CAD SR SOP Classes as an SCU that creates instances: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Mammography CAD SR, Chest CAD SR or Colon CAD SR SOP Classes as an SCU that creates instances: - Which optional content items are - supported - + Which optional content items are supported - Conditions under which content - items are assigned Rendering Intent of "Presentation Optional", and whether a CAD - Operating Point value will be included with each Single Image Finding that has Rendering - Intent of "Presentation Optional" - + Conditions under which content items are assigned Rendering Intent of "Presentation Optional", and whether a CAD Operating Point value will be included with each Single Image Finding that has Rendering Intent of "Presentation Optional" - Recommendations for the conditions - under which content items with Rendering Intent of "Presentation Optional" should be - rendered, based on CAD Operating Point or otherwise - + Recommendations for the conditions under which content items with Rendering Intent of "Presentation Optional" should be rendered, based on CAD Operating Point or otherwise - Conditions under which content - items are assigned Rendering Intent of "Not for Presentation" - + Conditions under which content items are assigned Rendering Intent of "Not for Presentation"
Ultrasound SR SOP Classes - The following shall be documented in the - Conformance Statement of any SR creator implementation claiming conformance to the Simplified - Adult Echo SR SOP Class as an SCU: - + The following shall be documented in the Conformance Statement of any SR creator implementation claiming conformance to the Simplified Adult Echo SR SOP Class as an SCU: - A list of all the measurement codes - from - - supported by the device for use in. - + A list of all the measurement codes from supported by the device for use in . - A list of initial measurement codes - supported by the device for use in Row 1 or 2 of - . - + A list of initial measurement codes supported by the device for use in Row 1 or 2 of . - Optionally, a table of the - - post-coordinated modifer values associated with each measurement code. - + Optionally, a table of the post-coordinated modifer values associated with each measurement code. - A list of any extension codes added - to, - ,, - ,. - + A list of any extension codes added to , , , , .
Conformance Statement for an SCP - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Structured Reporting Storage - SOP Class as an SCP: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Structured Reporting Storage SOP Class as an SCP: - For an SCP of a Structured Reporting - Storage SOP Class that is displaying or otherwise rendering the structured report contained - in a SOP Instance of the SOP Class, the general form in which the structured report related - Attributes are rendered. - + For an SCP of a Structured Reporting Storage SOP Class that is displaying or otherwise rendering the structured report contained in a SOP Instance of the SOP Class, the general form in which the structured report related Attributes are rendered. - For an SCP of a Structured Reporting - Storage SOP Class, the Image or other composite object Storage SOP Classes that are also - supported by the SCP and may be referenced by instances of the Structured Reporting Storage - SOP Class, and whether or not they will be displayed or otherwise rendered. - + For an SCP of a Structured Reporting Storage SOP Class, the Image or other composite object Storage SOP Classes that are also supported by the SCP and may be referenced by instances of the Structured Reporting Storage SOP Class, and whether or not they will be displayed or otherwise rendered. - For an SCP of a Structured Reporting - Storage SOP Class that is displaying or otherwise rendering an image or other composite - object referred to by a SOP Instance of the SOP Class, the manner in which the structured - report related Attributes (such as spatial coordinates and referenced presentation states) - are used to influence the display of the image or object. - + For an SCP of a Structured Reporting Storage SOP Class that is displaying or otherwise rendering an image or other composite object referred to by a SOP Instance of the SOP Class, the manner in which the structured report related Attributes (such as spatial coordinates and referenced presentation states) are used to influence the display of the image or object. - If the implementation supports - Query/Retrieve of Structured Reporting SOP Instances as an SCP, whether it supports the - Optional Keys Concept Name Code Sequence or Content Template Sequence. - + If the implementation supports Query/Retrieve of Structured Reporting SOP Instances as an SCP, whether it supports the Optional Keys Concept Name Code Sequence or Content Template Sequence.
CAD SR SOP Classes - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Mammography CAD SR, - Chest CAD SR or Colon CAD SR SOP Classes as an SCP: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Mammography CAD SR, Chest CAD SR or Colon CAD SR SOP Classes as an SCP: - Conditions under which the SCP will - render content items with Rendering Intent concept modifier set to "Presentation - Optional" - + Conditions under which the SCP will render content items with Rendering Intent concept modifier set to "Presentation Optional"
Extensible SR SOP Class - The following shall be documented in the - Conformance Statement of any implementation claiming conformance to the Extensible SR SOP Class - as an SCP: - + The following shall be documented in the Conformance Statement of any implementation claiming conformance to the Extensible SR SOP Class as an SCP: - The behavior and warnings generated - when encountering unsupported Content Items, Value Types and Relationship Types - + The behavior and warnings generated when encountering unsupported Content Items, Value Types and Relationship Types
@@ -36175,99 +25579,48 @@ Overview
Scope - The Application Event Logging Service Class - defines an application-level class-of-service that facilitates the network transfer of Event Log - Records to be logged or recorded in a central location. - - The Application Event Logging Service Class - addresses the class of application specific logs (e.g., procedural event logs) that are managed by a - medical application. The Application Event Logging Service Class does not specify the means of - accessing the central logs. - + The Application Event Logging Service Class defines an application-level class-of-service that facilitates the network transfer of Event Log Records to be logged or recorded in a central location. + The Application Event Logging Service Class addresses the class of application specific logs (e.g., procedural event logs) that are managed by a medical application. The Application Event Logging Service Class does not specify the means of accessing the central logs. - This Service Class does not address system - security or audit logs that are managed by general system logging applications and may use - non-DICOM protocols (e.g., SYSLOG). - + This Service Class does not address system security or audit logs that are managed by general system logging applications and may use non-DICOM protocols (e.g., SYSLOG).
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Application Event Logging Service Class with one serving in the SCU role and one serving in the SCP - role. SOP Classes of the Application Event Logging Service Class are implemented using the DIMSE-N - N-ACTION service as defined in. - - The N-ACTION service conveys the following - semantics: - + Two peer DICOM AEs implement a SOP Class of the Application Event Logging Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Application Event Logging Service Class are implemented using the DIMSE-N N-ACTION service as defined in . + The N-ACTION service conveys the following semantics: - The SCU notifies the SCP that an event - has occurred that the SCP should record in a log. The Action Information of the N-ACTION-RQ - contains the information about the event. - + The SCU notifies the SCP that an event has occurred that the SCP should record in a log. The Action Information of the N-ACTION-RQ contains the information about the event. - The SCP responds with a confirmation of - the status of the recording action. - + The SCP responds with a confirmation of the status of the recording action. - The association negotiation procedure is used - to negotiate the supported SOP Classes. - - specifies the association procedure. The Application Event Logging Service Class does not support - extended negotiation. - - The release of an association shall not have - any effect on the contents of the log managed by the SCP. - + The association negotiation procedure is used to negotiate the supported SOP Classes. specifies the association procedure. The Application Event Logging Service Class does not support Extended Negotiation. + The release of an association shall not have any effect on the contents of the log managed by the SCP.
Procedural Event Logging SOP Class Definition - The Procedural Event Logging SOP Class allows SCUs - to report to an SCP the events that are to be recorded in a Procedure Log SOP Instance, as described in - . This allows multiple - devices participating in a Study to cooperatively construct a log of events that occur during that - Study. - - The multiple procedural events reported through - this SOP Class are related by Patient ID, Study Instance UID, Study ID, and/or Performed Location. The - mechanism by which multiple devices obtain these shared identifiers is not defined by this SOP Class. - + The Procedural Event Logging SOP Class allows SCUs to report to an SCP the events that are to be recorded in a Procedure Log SOP Instance, as described in . This allows multiple devices participating in a Study to cooperatively construct a log of events that occur during that Study. + The multiple procedural events reported through this SOP Class are related by Patient ID, Study Instance UID, Study ID, and/or Performed Location. The mechanism by which multiple devices obtain these shared identifiers is not defined by this SOP Class. - The Modality Worklist or UPS SOP Classes may be - used for this purpose. For simple devices that cannot support worklist SOP Classes, the SCP may be - able to use Performed Location, or the SCU AE Title, to relate the use of the device to a particular - procedure. - + The Modality Worklist or UPS SOP Classes may be used for this purpose. For simple devices that cannot support worklist SOP Classes, the SCP may be able to use Performed Location, or the SCU AE Title, to relate the use of the device to a particular procedure. - The SCP may also provide for recording events for - which the SCU does not provide identifiers for matching. The mechanism by which the SCP determines the - association of such an unidentified event with the log for a specific procedure is not defined by this - SOP Class. - + The SCP may also provide for recording events for which the SCU does not provide identifiers for matching. The mechanism by which the SCP determines the association of such an unidentified event with the log for a specific procedure is not defined by this SOP Class. - The network address and/or AE Title of the SCU - may be used to identify the device as a participant in a particular procedure. - + The network address and/or AE Title of the SCU may be used to identify the device as a participant in a particular procedure.
DIMSE Service Group - The DIMSE-N Services applicable to the - Procedural Event Logging SOP Class are shown in. - + The DIMSE-N Services applicable to the Procedural Event Logging SOP Class are shown in .
Modality Worklist SOP Class
- Modality Worklist - Information Model - FIND - + Modality Worklist Information Model - FIND - 1.2.840.10008.5.1.4.31 - + 1.2.840.10008.5.1.4.31
- Pixel Intensity - Relationship (0028,1040) Attribute of the referenced SOP Instance - + Pixel Intensity Relationship (0028,1040) Attribute of the referenced SOP Instance - The contents of Pixel - Intensity Relationship LUT Sequence (0028,9422) in XA/XRF Presentation State - Mask Module - + The contents of Pixel Intensity Relationship LUT Sequence (0028,9422) in XA/XRF Presentation State Mask Module
- TO_LOG LUT provided - + TO_LOG LUT provided
- TO_LOG LUT provided, - may be an identity - + TO_LOG LUT provided, may be an identity
DIMSE Service Group Applicable to Procedural Event Logging
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -36285,22 +25638,14 @@
- The DIMSE-N Services and Protocol are specified - in. - + The DIMSE-N Services and Protocol are specified in .
Operation - The DICOM AEs that claim conformance to this - SOP Class as an SCU shall invoke the N-ACTION request. The DICOM AEs that claim conformance to this - SOP Class as an SCP shall support the N-ACTION request. - + The DICOM AEs that claim conformance to this SOP Class as an SCU shall invoke the N-ACTION request. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support the N-ACTION request.
Action Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Action Type and Action Information in - the N-ACTION-RQ as specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Type and Action Information in the N-ACTION-RQ as specified in . @@ -36318,32 +25663,27 @@ Tag @@ -36389,9 +25729,7 @@ @@ -36437,53 +25770,26 @@
Procedural Event Logging Action Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Record Procedural Event - + Record Procedural Event 1 - Specific Character Set - + Specific Character Set (0008,0005) 1C/1C - (Required if an extended or - replacement character set is used) - + (Required if an extended or replacement character set is used)
- Synchronization Frame of - Reference UID - + Synchronization Frame of Reference UID (0020,0200) @@ -36418,18 +25756,13 @@ - All other Attributes of the - - using - + All other Attributes of the using - See - + See
Study Matching Attributes - The SCU may provide Patient ID - (0010,0020), Study Instance UID (0020,000D), Study ID (0020,0010), and/or Performed Location - (0040,0243) Attributes to allow the SCP to match the N-ACTION with a Study for which a - procedure log is being created. - + The SCU may provide Patient ID (0010,0020), Study Instance UID (0020,000D), Study ID (0020,0010), and/or Performed Location (0040,0243) Attributes to allow the SCP to match the N-ACTION with a Study for which a procedure log is being created.
Synchronization Frame of Reference UID - The Synchronization Frame of Reference - UID (0020,0200) Attribute identifies the temporal frame of reference for the Observation - DateTime (0040,A032) Attributes in the Procedural Event record. If the Observation DateTime - Attribute Values are not synchronized in an identifiable Frame of Reference, the Attribute - shall be zero length. - + The Synchronization Frame of Reference UID (0020,0200) Attribute identifies the temporal frame of reference for the Observation DateTime (0040,A032) Attributes in the Procedural Event record. If the Observation DateTime Attribute Values are not synchronized in an identifiable Frame of Reference, the Attribute shall be zero length.
Constraints on Attributes of the SR Document Content Module - The Procedural Event record shall be - conveyed in a (top level) Content Item, and subsidiary Content Items, as specified by the SR - Document Content Module definition in. - - The top level and subsidiary Content - Items shall be constructed in accordance with the Procedure Log IOD Content Constraints of - . - + The Procedural Event record shall be conveyed in a (top level) Content Item, and subsidiary Content Items, as specified by the SR Document Content Module definition in . + The top level and subsidiary Content Items shall be constructed in accordance with the Procedure Log IOD Content Constraints of . - These constraints specify - use of BTID 3001 Procedure Log defined in - , and specific particular use of the Observation DateTime (0040,A032) - Attributes. - + These constraints specify use of BTID 3001 Procedure Log defined in , and specific particular use of the Observation DateTime (0040,A032) Attributes. - TID 3001 requires the - explicit identification of the Observer Context of the top level CONTAINER - through TID 1002. - + TID 3001 requires the explicit identification of the Observer Context of the top level CONTAINER through TID 1002. - There may be multiple - events (subsidiary Content Items) included in a single N-ACTION-RQ message. - + There may be multiple events (subsidiary Content Items) included in a single N-ACTION-RQ message. @@ -36491,35 +25797,18 @@
Service Class User Behavior - The SCU shall request logging of events - that occur during a Study, using the N-ACTION request primitive. - - The SCU shall receive N-ACTION responses. - The actions taken upon a response status of Failure, or upon non-response of the SCP, are - implementation dependent. - + The SCU shall request logging of events that occur during a Study, using the N-ACTION request primitive. + The SCU shall receive N-ACTION responses. The actions taken upon a response status of Failure, or upon non-response of the SCP, are implementation dependent.
Service Class Provider Behavior - The SCP shall manage the creation of SOP - Instances of the Procedure Log Storage Service. It shall receive, via the N-ACTION request - primitive, requests for logging of events that occur during a Study. The SCP shall (consonant - with application dependent constraints) incorporate those event records into a Procedure Log SOP - Instance for the specified Study. - - The SCP shall return, via the N-ACTION - response primitive, the N-ACTION Response Status Code applicable to the associated action - request. - + The SCP shall manage the creation of SOP Instances of the Procedure Log Storage Service. It shall receive, via the N-ACTION request primitive, requests for logging of events that occur during a Study. The SCP shall (consonant with application dependent constraints) incorporate those event records into a Procedure Log SOP Instance for the specified Study. + The SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated action request.
Status Codes - - defines the specific status code values that might be returned in a N-ACTION response. See - - for additional general response status codes. - + defines the specific status code values that might be returned in a N-ACTION response. See for additional general response status codes. @@ -36552,9 +25841,7 @@ Warning
Response Status
- Specified Synchronization - Frame of Reference UID does not match SCP Synchronization Frame of Reference - + Specified Synchronization Frame of Reference UID does not match SCP Synchronization Frame of Reference B101 @@ -36562,9 +25849,7 @@
- Study Instance UID - coercion; Event logged under a different Study Instance UID - + Study Instance UID coercion; Event logged under a different Study Instance UID B102 @@ -36572,9 +25857,7 @@
- IDs inconsistent in - matching a current study; Event logged - + IDs inconsistent in matching a current study; Event logged B104 @@ -36585,9 +25868,7 @@ Failure - Failed: Procedural Logging - not available for specified Study Instance UID - + Failed: Procedural Logging not available for specified Study Instance UID C101 @@ -36595,9 +25876,7 @@
- Failed: Event Information - does not match Template - + Failed: Event Information does not match Template C102 @@ -36605,9 +25884,7 @@
- Failed: Cannot match event - to a current study - + Failed: Cannot match event to a current study C103 @@ -36615,9 +25892,7 @@
- Failed: IDs inconsistent in - matching a current study; Event not logged - + Failed: IDs inconsistent in matching a current study; Event not logged C104 @@ -36628,11 +25903,7 @@
Action Reply - With any response status indicating Success - or Warning, the identifiers of the study into which the event has been logged shall be returned - in the N-ACTION-RSP Action Reply as specified in. - + With any response status indicating Success or Warning, the identifiers of the study into which the event has been logged shall be returned in the N-ACTION-RSP Action Reply as specified in . @@ -36650,16 +25921,14 @@ Tag
Procedural Event Logging Action Reply
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Record Procedural Event - + Record Procedural Event 1 @@ -36691,118 +25960,58 @@
Procedural Event Logging SOP Class UID - The Procedural Event Logging SOP Class shall be - uniquely identified by the Procedural Event Logging SOP Class UID, which shall have the value - "1.2.840.10008.1.40". - + The Procedural Event Logging SOP Class shall be uniquely identified by the Procedural Event Logging SOP Class UID, which shall have the value "1.2.840.10008.1.40".
Procedural Event Logging Instance Identification - The well-known UID of the Procedural Event - Logging SOP Instance shall have the value "1.2.840.10008.1.40.1". - + The well-known UID of the Procedural Event Logging SOP Instance shall have the value "1.2.840.10008.1.40.1".
Conformance Requirements - The DICOM AE's Conformance Statement shall be - formatted as defined in. - + The DICOM AE's Conformance Statement shall be formatted as defined in .
SCU Conformance - The SCU shall document in its Conformance - Statement the behavior and actions that cause the SCU to generate an N-ACTION primitive - (Procedural Event Notification). It shall specify the Template used for constructing the Event - Information, and the Coding Schemes used for coded entries in the Event Information. - - The SCU shall document the identifiers it - sends for matching purposes, and how it obtains those Attributes (e.g., through a Modality - Worklist query, manual entry, etc.). - - The SCU shall document the behavior and - actions performed when a success, warning, or failure status is received. - - The SCU shall document the mechanisms used - for establishing time synchronization and specifying the Synchronization Frame of Reference UID. - + The SCU shall document in its Conformance Statement the behavior and actions that cause the SCU to generate an N-ACTION primitive (Procedural Event Notification). It shall specify the Template used for constructing the Event Information, and the Coding Schemes used for coded entries in the Event Information. + The SCU shall document the identifiers it sends for matching purposes, and how it obtains those Attributes (e.g., through a Modality Worklist query, manual entry, etc.). + The SCU shall document the behavior and actions performed when a success, warning, or failure status is received. + The SCU shall document the mechanisms used for establishing time synchronization and specifying the Synchronization Frame of Reference UID.
SCP Conformance - The SCP shall document in its Conformance - Statement how it uses the identifiers it receives for matching the N-ACTION (Procedural Event - Notification) to a specific procedure. - - The SCP shall document the behavior and - actions that cause the SCP to generate a success, warning, or failure status for a received - N-ACTION. - - The SCP shall document the behavior and - actions that cause the SCP to generate a Procedure Log SOP Instance including the received Event - Information. - - The SCP shall document how it assigns the - value of the Observation Datetime (0040,A032) Attribute when the SCU-provided Synchronization - Frame of Reference UID is absent, or differs from that of the SCP. - + The SCP shall document in its Conformance Statement how it uses the identifiers it receives for matching the N-ACTION (Procedural Event Notification) to a specific procedure. + The SCP shall document the behavior and actions that cause the SCP to generate a success, warning, or failure status for a received N-ACTION. + The SCP shall document the behavior and actions that cause the SCP to generate a Procedure Log SOP Instance including the received Event Information. + The SCP shall document how it assigns the value of the Observation Datetime (0040,A032) Attribute when the SCU-provided Synchronization Frame of Reference UID is absent, or differs from that of the SCP.
Substance Administration Logging SOP Class Definition - The Substance Administration Logging SOP Class - allows an SCU to report to an SCP the events that are to be recorded in a patient's Medication - Administration Record (MAR) or similar log, whose definition is outside the scope of the Standard. This - allows devices with DICOM protocol interfaces to report administration of diagnostic agents (including - contrast) and therapeutic drugs, and implantation of devices. - - The Substance Administration reported through this - SOP Class is related to the MAR by Patient ID or Admission ID. The mechanism by which the SCU obtains - this identifier is not defined by this SOP Class. - - The log entry to the MAR is authorized by at least - one of the Operators identified in the Operator Identification Sequence. The mechanism by which the SCU - obtains these identifiers is not defined by this SOP Class. The SCP may refuse the log entry if none of - the identified Operators is authorized to add entries to the MAR. The mechanism by which the SCP - validates such authorization is not defined by this SOP Class. - + The Substance Administration Logging SOP Class allows an SCU to report to an SCP the events that are to be recorded in a patient's Medication Administration Record (MAR) or similar log, whose definition is outside the scope of the Standard. This allows devices with DICOM protocol interfaces to report administration of diagnostic agents (including contrast) and therapeutic drugs, and implantation of devices. + The Substance Administration reported through this SOP Class is related to the MAR by Patient ID or Admission ID. The mechanism by which the SCU obtains this identifier is not defined by this SOP Class. + The log entry to the MAR is authorized by at least one of the Operators identified in the Operator Identification Sequence. The mechanism by which the SCU obtains these identifiers is not defined by this SOP Class. The SCP may refuse the log entry if none of the identified Operators is authorized to add entries to the MAR. The mechanism by which the SCP validates such authorization is not defined by this SOP Class. - The SCP of this Service Class is not - necessarily the Medication Administration Record system, but may be a gateway system between - this DICOM Service and an HL7 or proprietary interface of a MAR system. Such implementation - design is beyond the scope of the DICOM Standard. - + The SCP of this Service Class is not necessarily the Medication Administration Record system, but may be a gateway system between this DICOM Service and an HL7 or proprietary interface of a MAR system. Such implementation design is beyond the scope of the DICOM Standard. - This SOP Class is not limited to only - specifying medications, although the conventional name of the destination log is the - Medication Administration Record. The SOP Class may also be used to record the implantation - of therapeutic devices, including both drug-eluting and bare stents, prosthetic and - cardiovascular devices, implantable infusion pumps, etc. - + This SOP Class is not limited to only specifying medications, although the conventional name of the destination log is the Medication Administration Record. The SOP Class may also be used to record the implantation of therapeutic devices, including both drug-eluting and bare stents, prosthetic and cardiovascular devices, implantable infusion pumps, etc. - The application level authorization of - Operators for the purpose of logging a MAR entry is distinct from any access control - mechanism at the transport layer (see User Identity Association profiles in). - + The application level authorization of Operators for the purpose of logging a MAR entry is distinct from any access control mechanism at the transport layer (see User Identity Association profiles in ).
DIMSE Service Group - The DIMSE-N Services applicable to the - Substance Administration Logging SOP Class are shown in. - + The DIMSE-N Services applicable to the Substance Administration Logging SOP Class are shown in .
DIMSE Service Group Applicable to Substance Administration Logging
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -36820,31 +26029,15 @@
- The DIMSE-N Services and Protocol are specified - in. - + The DIMSE-N Services and Protocol are specified in .
Operation - The DICOM AEs that claim conformance to this - SOP Class as an SCU shall invoke the N-ACTION request. The DICOM AEs that claim conformance to this - SOP Class as an SCP shall support the N-ACTION request. - + The DICOM AEs that claim conformance to this SOP Class as an SCU shall invoke the N-ACTION request. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support the N-ACTION request.
Substance Administration Log Action Information - This operation allows an SCU to submit a - Medication Administration Record log item or entry, providing information about a specific - real-world act of Substance Administration that is the purview of the SCU. This operation shall - be invoked through the DIMSE N-ACTION Service. - - The Action Information Attributes are - defined by the Substance Administration Log Module specified in - . The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support - the Action Type and Action Information Attributes in the N-ACTION-RQ as specified in. - + This operation allows an SCU to submit a Medication Administration Record log item or entry, providing information about a specific real-world act of Substance Administration that is the purview of the SCU. This operation shall be invoked through the DIMSE N-ACTION Service. + The Action Information Attributes are defined by the Substance Administration Log Module specified in . The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Type and Action Information Attributes in the N-ACTION-RQ as specified in . @@ -36862,33 +26055,27 @@ Tag @@ -36900,10 +26087,7 @@ @@ -36937,16 +26121,12 @@ @@ -36981,10 +26156,7 @@ @@ -37000,9 +26172,7 @@ @@ -37125,59 +26278,25 @@
Service Class User Behavior - The SCU shall request logging of substance - administration events for a specified Patient using the N-ACTION request primitive. - - The SCU shall receive N-ACTION responses. - The actions taken upon a response status of Failure, or upon non-response of the SCP, are - implementation dependent. - + The SCU shall request logging of substance administration events for a specified Patient using the N-ACTION request primitive. + The SCU shall receive N-ACTION responses. The actions taken upon a response status of Failure, or upon non-response of the SCP, are implementation dependent.
Service Class Provider Behavior - The SCP shall receive, via the N-ACTION - request primitive, requests for logging of substance administration events. The SCP shall - incorporate those event records into a Medication Administration Record or similar log for the - specified Patient. - + The SCP shall receive, via the N-ACTION request primitive, requests for logging of substance administration events. The SCP shall incorporate those event records into a Medication Administration Record or similar log for the specified Patient. - The patient's identify may be conveyed - explicitly by Patient ID (0010,0020), or implicitly by Admission (i.e., Visit) ID - (0038,0010). An institution may typically chose one or the other to use as the primary - patient identifier at the point of care, e.g., printed on a bar coded wristband, the use of - which may facilitate data entry for the log entry. However, in the "Model of the Real World - for the Purpose of Modality-IS Interface" (see), the - Visit is subsidiary to the Patient; hence the Admission ID (0038,0010) may only be unique - within the context of the patient, not within the context of the institution. The use of the - Admission ID (0038,0010) Attribute to identify the Patient is only effective if the - Admission ID (0038,0010) is unique within the context of the institution. - + The patient's identify may be conveyed explicitly by Patient ID (0010,0020), or implicitly by Admission (i.e., Visit) ID (0038,0010). An institution may typically chose one or the other to use as the primary patient identifier at the point of care, e.g., printed on a bar coded wristband, the use of which may facilitate data entry for the log entry. However, in the "Model of the Real World for the Purpose of Modality-IS Interface" (see ), the Visit is subsidiary to the Patient; hence the Admission ID (0038,0010) may only be unique within the context of the patient, not within the context of the institution. The use of the Admission ID (0038,0010) Attribute to identify the Patient is only effective if the Admission ID (0038,0010) is unique within the context of the institution. - The SCP shall support inclusion into the - Medication Administration Record or similar log of values of all Type 1 and Type 2 Attributes - for which the SCU has provided values. The SCP may convert these Attributes into a form - appropriate for the destination log. - + The SCP shall support inclusion into the Medication Administration Record or similar log of values of all Type 1 and Type 2 Attributes for which the SCU has provided values. The SCP may convert these Attributes into a form appropriate for the destination log. - The SCP may convert coded data to free - text in the log, with loss of the specific code values, if the log does not support such - coded data. - + The SCP may convert coded data to free text in the log, with loss of the specific code values, if the log does not support such coded data. - The SCP shall return, via the N-ACTION - response primitive, the N-ACTION Response Status Code applicable to the associated action - request. - + The SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated action request.
Status Codes - - defines the specific status code values that might be returned in a N-ACTION response. See - - for additional general response status codes. - + defines the specific status code values that might be returned in a N-ACTION response. See for additional general response status codes.
Substance Administration Logging N-ACTION Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Record Substance - Administration Event - + Record Substance Administration Event 1 - Specific Character Set - + Specific Character Set (0008,0005) 1C/1C - (Required if an extended or - replacement character set is used) - + (Required if an extended or replacement character set is used)
1C/1C - Either or both Patient ID - and Admission ID shall be supplied by the SCU; the SCP shall support the - Attribute if supplied - + Either or both Patient ID and Admission ID shall be supplied by the SCU; the SCP shall support the Attribute if supplied
1C/1C - Either or both Patient ID - and Admission ID shall be supplied by the SCU; the SCP shall support the - Attribute if supplied - + Either or both Patient ID and Admission ID shall be supplied by the SCU; the SCP shall support the Attribute if supplied
- Issuer of Admission ID - + Issuer of Admission ID (0038,0011) @@ -36957,19 +26137,14 @@
- Product Package - Identifier - + Product Package Identifier (0044,0001) 1C/1C - Either or both Product - Package Identifier and Product Name shall be supplied by the SCU; the SCP shall - support the Attribute if supplied - + Either or both Product Package Identifier and Product Name shall be supplied by the SCU; the SCP shall support the Attribute if supplied
1C/1C - Either or both Product - Package Identifier and Product Name shall be supplied by the SCU; the SCP shall - support the Attribute if supplied - + Either or both Product Package Identifier and Product Name shall be supplied by the SCU; the SCP shall support the Attribute if supplied
- Substance Administration - DateTime - + Substance Administration DateTime (0044,0010) @@ -37013,9 +26183,7 @@
- Substance Administration - Notes - + Substance Administration Notes (0044,0011) @@ -37026,9 +26194,7 @@
- Substance Administration - Device ID - + Substance Administration Device ID (0044,0012) @@ -37039,9 +26205,7 @@
- Administration Route Code - Sequence - + Administration Route Code Sequence (0054,0302) @@ -37053,17 +26217,14 @@
- >Include - - - +>Include + +
- Substance Administration - Parameter Sequence - + Substance Administration Parameter Sequence (0044,0019) @@ -37074,10 +26235,7 @@
- >All Attributes of the Substance Administration Parameter - Sequence - + >All Attributes of the Substance Administration Parameter Sequence @@ -37087,9 +26245,7 @@
- Operator Identification - Sequence - + Operator Identification Sequence (0008,1072) @@ -37100,9 +26256,7 @@
- >Person Identification - Code Sequence - + >Person Identification Code Sequence (0040,1101) @@ -37114,10 +26268,9 @@
- >>Include - - - +>>Include + +
@@ -37210,9 +26329,7 @@ Failure
Response Status
- Failed: Operator Refused: - Not authorized to add entry to Medication Administration Record - + Failed: Operator Refused: Not authorized to add entry to Medication Administration Record C10E @@ -37220,9 +26337,7 @@
- Failed: Patient cannot be - identified from Patient ID (0010,0020) or Admission ID (0038,0010) - + Failed: Patient cannot be identified from Patient ID (0010,0020) or Admission ID (0038,0010) C110 @@ -37230,9 +26345,7 @@
- Failed: Update of - Medication Administration Record failed - + Failed: Update of Medication Administration Record failed C111 @@ -37244,44 +26357,25 @@
Substance Administration Logging SOP Class UID - The Substance Administration Logging SOP Class - shall be uniquely identified by the Substance Administration Logging SOP Class UID, which shall have - the value "1.2.840.10008.1.42". - + The Substance Administration Logging SOP Class shall be uniquely identified by the Substance Administration Logging SOP Class UID, which shall have the value "1.2.840.10008.1.42".
Substance Administration Logging Instance UID - The well-known UID of the Substance - Administration Logging SOP Instance shall have the value "1.2.840.10008.1.42.1". - + The well-known UID of the Substance Administration Logging SOP Instance shall have the value "1.2.840.10008.1.42.1".
Conformance Requirements - The DICOM AE's Conformance Statement shall be - formatted as defined in. - + The DICOM AE's Conformance Statement shall be formatted as defined in .
SCU Conformance - The SCU shall document in its Conformance - Statement the behavior and actions that cause the SCU to generate an N-ACTION-RQ primitive. - - The SCU shall document how it obtains the - Patient ID (0010,0020) or Admission ID (0038,0010) Attribute (e.g., through a Modality Worklist - query, bar-code scan, manual entry, etc.). - - The SCU shall document the behavior and - actions performed when a success or failure status is received. - + The SCU shall document in its Conformance Statement the behavior and actions that cause the SCU to generate an N-ACTION-RQ primitive. + The SCU shall document how it obtains the Patient ID (0010,0020) or Admission ID (0038,0010) Attribute (e.g., through a Modality Worklist query, bar-code scan, manual entry, etc.). + The SCU shall document the behavior and actions performed when a success or failure status is received.
SCP Conformance - The SCP shall document in its Conformance - Statement how it uses the information it receives for adding data to a Medication Administration - Record. - - The SCP shall document the behavior and - actions that cause the SCP to generate a success or failure status for a received N-ACTION-RQ. - + The SCP shall document in its Conformance Statement how it uses the information it receives for adding data to a Medication Administration Record. + The SCP shall document the behavior and actions that cause the SCP to generate a success or failure status for a received N-ACTION-RQ.
@@ -37290,24 +26384,13 @@ Relevant Patient Information Query Service Class (Normative)
Overview - The Relevant Patient Information Query Service - Class defines an application-level class-of-service that facilitates the access to relevant patient - information such as it is known at the time of query. - - The query information model consists of two - entities with a one-to-one relationship: the Patient and the Patient Information. - - The Patient Information may be general, or specific - to a particular imaging or procedure domain. A general SOP Class is defined along with some additional - domain specific SOP Classes. - + The Relevant Patient Information Query Service Class defines an application-level class-of-service that facilitates the access to relevant patient information such as it is known at the time of query. + The query information model consists of two entities with a one-to-one relationship: the Patient and the Patient Information. + The Patient Information may be general, or specific to a particular imaging or procedure domain. A general SOP Class is defined along with some additional domain specific SOP Classes.
DIMSE-C Service Group - One DIMSE-C Service is used in the construction of - SOP Classes of the Relevant Patient Information Query Service Class. The following DIMSE-C operation is - used. - + One DIMSE-C Service is used in the construction of SOP Classes of the Relevant Patient Information Query Service Class. The following DIMSE-C operation is used. C-FIND @@ -37315,123 +26398,63 @@
C-FIND Operation - SCPs of the Relevant Patient Information Query - Service Class are capable of processing queries using the C-FIND operation as described in. The C-FIND operation - is the mechanism by which queries are performed. The SCP shall provide Relevant Patient Information - for at most one matching patient in the C-FIND response. - + SCPs of the Relevant Patient Information Query Service Class are capable of processing queries using the C-FIND operation as described in . The C-FIND operation is the mechanism by which queries are performed. The SCP shall provide Relevant Patient Information for at most one matching patient in the C-FIND response.
C-FIND Service Parameters
SOP Class UID - The SOP Class UID identifies the - Relevant Patient Information Model and Template against which the C-FIND is to be performed. - Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation - Context used by this C-FIND operation. - + The SOP Class UID identifies the Relevant Patient Information Model and Template against which the C-FIND is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-FIND operation.
Priority - The Priority Attribute defines the - requested priority of the C-FIND operation with respect to other DIMSE operations being - performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. - + The Priority Attribute defines the requested priority of the C-FIND operation with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP.
Identifier - Both the C-FIND request and response - contain an Identifier encoded as a Data Set (see). - + Both the C-FIND request and response contain an Identifier encoded as a Data Set (see ).
Request Identifier Structure - An Identifier in a C-FIND request - shall contain: - + An Identifier in a C-FIND request shall contain: - Key Attributes with values - to be matched against the values of Attributes specified in the SOP Class. - + Key Attributes with values to be matched against the values of Attributes specified in the SOP Class. - Content Template Sequence - (0040,A504), which shall include a single sequence item containing the Template - Identifier (0040,DB00) and Mapping Resource (0008,0105) Attributes, to identify - the template structure to use in the matching C-FIND responses. - + Content Template Sequence (0040,A504), which shall include a single sequence item containing the Template Identifier (0040,DB00) and Mapping Resource (0008,0105) Attributes, to identify the template structure to use in the matching C-FIND responses. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Request Identifier. It shall not be included otherwise. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Request Identifier. It shall not be included otherwise. - The Key Attributes and values - allowable for the query are defined in the SOP Class definition for the Relevant Patient - Information Model. - + The Key Attributes and values allowable for the query are defined in the SOP Class definition for the Relevant Patient Information Model.
Response Identifier Structure - The C-FIND response shall not - contain Attributes that were not in the request or specified in this section. - - An Identifier in a C-FIND response - shall contain: - + The C-FIND response shall not contain Attributes that were not in the request or specified in this section. + An Identifier in a C-FIND response shall contain: - Key Attributes with values - corresponding to Key Attributes contained in the Identifier of the request. - + Key Attributes with values corresponding to Key Attributes contained in the Identifier of the request. - Content Template Sequence - (0040,A504), which shall include a single sequence item containing the Template - Identifier (0040,DB00) and Mapping Resource (0008,0105) Attributes, to identify - the template structure used in the C-FIND response. The values shall be the same - as specified in the Request Identifier. - + Content Template Sequence (0040,A504), which shall include a single sequence item containing the Template Identifier (0040,DB00) and Mapping Resource (0008,0105) Attributes, to identify the template structure used in the C-FIND response. The values shall be the same as specified in the Request Identifier. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Response Identifier. It shall not be included otherwise. The C-FIND SCP - is not required to return responses in the Specific Character Set requested by - the SCU if that character set is not supported by the SCP. The SCP may return - responses with a different Specific Character Set. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Response Identifier. It shall not be included otherwise. The C-FIND SCP is not required to return responses in the Specific Character Set requested by the SCU if that character set is not supported by the SCP. The SCP may return responses with a different Specific Character Set.
Relevant Patient Information Templates - Templates used in the Relevant - Patient Information query are defined in. - - The template specified in the - Request Identifier shall not use by-reference relationships. - + Templates used in the Relevant Patient Information query are defined in . + The template specified in the Request Identifier shall not use by-reference relationships.
Status - - defines the status code values that might be returned in a C-FIND response. General status - code values and fields related to status code values are defined for C-FIND DIMSE Service in - . - + defines the status code values that might be returned in a C-FIND response. General status code values and fields related to status code values are defined for C-FIND DIMSE Service in . @@ -37456,9 +26479,7 @@ Failure
C-FIND Response Status Values
- Refused: Out of - resources - + Refused: Out of resources A700 @@ -37469,9 +26490,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -37483,9 +26502,7 @@
- Failed: Unable to - process - + Failed: Unable to process C000 @@ -37497,9 +26514,7 @@
- Failed: More than one - match found - + Failed: More than one match found C100 @@ -37511,9 +26526,7 @@
- Failed: Unable to - support requested template - + Failed: Unable to support requested template C200 @@ -37528,9 +26541,7 @@ Cancel - Matching terminated due - to Cancel request - + Matching terminated due to Cancel request FE00 @@ -37544,9 +26555,7 @@ Success - Success. Matching is - complete - No final Identifier is supplied. - + Success. Matching is complete - No final Identifier is supplied. 0000 @@ -37560,9 +26569,7 @@ Pending - Current Match is - supplied. - + Current Match is supplied. FF00 @@ -37574,11 +26581,7 @@
- Status Codes are returned in DIMSE - response messages (see). The code values stated - in column "Status Codes" are returned in Status Command Element (0000,0900). - + Status Codes are returned in DIMSE response messages (see ). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900).
@@ -37586,92 +26589,42 @@
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. The Association negotiation procedure specified in - - shall be used to negotiate the supported SOP Class. - - SOP Class Extended Negotiation is not defined for - this Service Class. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in shall be used to negotiate the supported SOP Class. + SOP Class Extended Negotiation is not defined for this Service Class.
DIMSE-C C-FIND Service - The DIMSE-C C-FIND service is the operation by - which relevant patient information is queried and provided. - + The DIMSE-C C-FIND service is the operation by which relevant patient information is queried and provided.
Conventions - Key Attributes in the Request Identifier serve - two purposes. They may be used as Matching Key Attributes and Return Key Attributes. Matching Key - Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether - an entity matches the query). Return Key Attributes may be used to specify desired return Attributes - (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND - response). - - Matching Key Attributes may be of Type - "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in - . - + Key Attributes in the Request Identifier serve two purposes. They may be used as Matching Key Attributes and Return Key Attributes. Matching Key Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether an entity matches the query). Return Key Attributes may be used to specify desired return Attributes (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND response). + Matching Key Attributes may be of Type "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in .
Service Definition - Two peer DICOM AEs implement this Relevant - Patient Information Query Service Class with one serving in the SCU role and one serving in the SCP - role. The SOP Class is implemented using the DIMSE-C C-FIND service as defined in. - - Only a baseline behavior of the DIMSE-C C-FIND - is used in this Service Class. - - A C-FIND service conveys the following - semantics: - + Two peer DICOM AEs implement this Relevant Patient Information Query Service Class with one serving in the SCU role and one serving in the SCP role. The SOP Class is implemented using the DIMSE-C C-FIND service as defined in . + Only a baseline behavior of the DIMSE-C C-FIND is used in this Service Class. + A C-FIND service conveys the following semantics: - The SCU requests that the SCP perform a - match for the Matching Keys and return values for the Return Keys that have been specified - in the Identifier of the request, against the Relevant Patient Information that the SCP - possesses. - + The SCU requests that the SCP perform a match for the Matching Keys and return values for the Return Keys that have been specified in the Identifier of the request, against the Relevant Patient Information that the SCP possesses. - In this Annex, the term - "Identifier" refers to the Identifier service parameter of the C-FIND service as defined - in. - + In this Annex, the term "Identifier" refers to the Identifier service parameter of the C-FIND service as defined in . - The SCP generates a C-FIND response for - at most one match with an Identifier containing the values of all Matching Key Attributes - and all known Return Key Attributes requested. The response contains one relevant patient - information instance in the form that matches the Template that was requested. This response - shall contain a status of Pending. - + The SCP generates a C-FIND response for at most one match with an Identifier containing the values of all Matching Key Attributes and all known Return Key Attributes requested. The response contains one relevant patient information instance in the form that matches the Template that was requested. This response shall contain a status of Pending. - When the process of matching is - complete, with zero or one match, a C-FIND response is sent with a status of Success and no - Identifier. - + When the process of matching is complete, with zero or one match, a C-FIND response is sent with a status of Success and no Identifier. - A Failed response to a C-FIND request - indicates that the SCP is unable to process the request. This shall be used to indicate that - the requested template is not supported by the SCP, or that more than one match was found by - the SCP. - + A Failed response to a C-FIND request indicates that the SCP is unable to process the request. This shall be used to indicate that the requested template is not supported by the SCP, or that more than one match was found by the SCP. - The SCU may cancel the C-FIND service - by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND service. - The SCP will interrupt all matching and return a status of Canceled. - + The SCU may cancel the C-FIND service by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND service. The SCP will interrupt all matching and return a status of Canceled. - The SCU needs to be prepared to - receive C-FIND responses sent by the SCP until the SCP finally processes the - C-FIND-CANCEL request. - + The SCU needs to be prepared to receive C-FIND responses sent by the SCP until the SCP finally processes the C-FIND-CANCEL request. @@ -37680,20 +26633,11 @@ Relevant Patient Information Model SOP Classes
Relevant Patient Information Model - In order to serve as a Service Class - Provider (SCP) of one or more Relevant Patient Information Model SOP Classes, a DICOM - Application Entity (AE) possesses relevant information about patients. This information is - organized into a Relevant Patient Information Model. - - The SOP Classes are composed of both the - Information Model and a DIMSE-C Service Group. - + In order to serve as a Service Class Provider (SCP) of one or more Relevant Patient Information Model SOP Classes, a DICOM Application Entity (AE) possesses relevant information about patients. This information is organized into a Relevant Patient Information Model. + The SOP Classes are composed of both the Information Model and a DIMSE-C Service Group.
E/R Model - The E/R Model consists of Patient and - Structured Information, with no relationship to other Information Entities in the DICOM - Information model. - + The E/R Model consists of Patient and Structured Information, with no relationship to other Information Entities in the DICOM Information model.
Relevant Patient Information E/R Model @@ -37705,47 +26649,31 @@
- The Patient IE includes the Attributes - of the Patient Identification and Patient Demographics Modules. - - The Structured Information IE includes - Attributes that are not inherently related to a real-world entity, but are interpreted - through their coded content. This includes the Attributes of the Structured Document Content - Module, which in the case of the Relevant Patient Information Query Service has its content - constrained by specified templates to convey patient related information. Also included in - the Structured Information IE are Attributes of the SOP Common and Common Instance Reference - Modules that support the interpretation of coded data, or support access to referenced - information objects identified in the coded data. - + The Patient IE includes the Attributes of the Patient Identification and Patient Demographics Modules. + The Structured Information IE includes Attributes that are not inherently related to a real-world entity, but are interpreted through their coded content. This includes the Attributes of the Structured Document Content Module, which in the case of the Relevant Patient Information Query Service has its content constrained by specified templates to convey patient related information. Also included in the Structured Information IE are Attributes of the SOP Common and Common Instance Reference Modules that support the interpretation of coded data, or support access to referenced information objects identified in the coded data.
Relevant Patient Information Attributes - - defines the Attributes of the Relevant Patient Information Model: - + defines the Attributes of the Relevant Patient Information Model: @@ -37786,23 +26714,16 @@ 1 @@ -37875,9 +26788,7 @@ @@ -37893,15 +26804,13 @@ @@ -37977,16 +26879,12 @@ 2
Attributes for the Relevant Patient Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark / Matching - Type - + Remark / Matching Type
- Shall be present in the - Request Identifier. - - Shall be retrieved with - Single Value Matching. - + Shall be present in the Request Identifier. + Shall be retrieved with Single Value Matching. - Since only one - response is expected, this is a unique key. - + Since only one response is expected, this is a unique key.
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -37814,19 +26735,13 @@ 2 - Shall be retrieved with - Single Value Matching. - - In situations where - there are multiple issuers, this key constrains matching of Patient ID - (0010,0020) to a domain in which the Patient ID (0010,0020) is unique. - + Shall be retrieved with Single Value Matching. + In situations where there are multiple issuers, this key constrains matching of Patient ID (0010,0020) to a domain in which the Patient ID (0010,0020) is unique.
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -37857,9 +26772,7 @@
- All other Attributes of the - + All other Attributes of the
- All other Attributes of the - + All other Attributes of the
- Structured Information (SR Document Content Module) - + Structured Information (SR Document Content Module)
- Observation DateTime - + Observation DateTime (0040,A032) @@ -37928,16 +26837,12 @@ 1 - See. - + See .
- Concept Name Code - Sequence - + Concept Name Code Sequence (0040,A043) @@ -37949,18 +26854,15 @@ 1 - See. - + See .
- >Include - - - +>Include + +
- See. - + See .
- >All Attributes of - the Content Sequence - + >All Attributes of the Content Sequence @@ -37996,17 +26894,12 @@ - - Content Items as - provided by the SCP. Requirements on Content Item Attribute Types shall be - in accordance with the definitions in the SR Document Content Module. - + Content Items as provided by the SCP. Requirements on Content Item Attribute Types shall be in accordance with the definitions in the SR Document Content Module.
- HL7 Structured Document - Reference Sequence - + HL7 Structured Document Reference Sequence (0040,A390) @@ -38021,9 +26914,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -38038,9 +26929,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -38055,9 +26944,7 @@
- >HL7 Instance - Identifier - + >HL7 Instance Identifier (0040,E001) @@ -38088,17 +26975,13 @@
- Structured Information (Common Instance Reference - Module) - + Structured Information (Common Instance Reference Module)
- Studies Containing - Other Referenced Instances Sequence - + Studies Containing Other Referenced Instances Sequence (0008,1200) @@ -38110,17 +26993,12 @@ 1C - Required if Content - Sequence (0040,A390) includes Content Items that reference SOP Instances - that use the Patient/Study/Series/Instance information model. - + Required if Content Sequence (0040,A390) includes Content Items that reference SOP Instances that use the Patient/Study/Series/Instance information model.
- >Referenced Series - Sequence - + >Referenced Series Sequence (0008,1115) @@ -38135,9 +27013,7 @@
- >>Series Instance - UID - + >>Series Instance UID (0020,000E) @@ -38152,9 +27028,7 @@
- >>Referenced - Instance Sequence - + >>Referenced Instance Sequence (0008,114A) @@ -38169,9 +27043,7 @@
- >>>Referenced - SOP Class UID - + >>>Referenced SOP Class UID (0008,1150) @@ -38186,9 +27058,7 @@
- >>>Referenced - SOP Instance UID - + >>>Referenced SOP Instance UID (0008,1155) @@ -38203,13 +27073,7 @@
- The Attributes in - - are not part of the Information Model; their inclusion in the C-FIND request and response - identifier are governed by rules in sections - - and, respectively. - + The Attributes in are not part of the Information Model; their inclusion in the C-FIND request and response identifier are governed by rules in sections and , respectively. @@ -38221,14 +27085,10 @@ Tag @@ -38313,82 +27163,30 @@
Relevant Patient Information Attribute Descriptions - Concept Name Code Sequence (0040,A043) - in a C-FIND Response shall have one sequence item that identifies the Root node concept of - the returned structure. This shall be the same as the Concept Name of the first row of the - template identified in the Content Template Sequence (0040,A504) in the Identifier. The - Concept Name Code Sequence (0040,A043) shall always be sent zero length in the Request - Identifier. - - The Value Type (0040,A040) applies to - the Concept Name Code Sequence (0040,A043), and shall be the same as the Value Type - (0040,A040) of the first row of the template identified in the Content Template Sequence - (0040,A504) in the Identifier. - - The Content Sequence (0040,A730) is a - potentially recursively nested Sequence of Items, as described in - , SR Document Content Module. The Content Sequence shall always be sent zero length in the - Request Identifier. The Content Sequence in the Data Set of the Response shall contain the - content items of the requested template. - + Concept Name Code Sequence (0040,A043) in a C-FIND Response shall have one sequence item that identifies the Root node concept of the returned structure. This shall be the same as the Concept Name of the first row of the template identified in the Content Template Sequence (0040,A504) in the Identifier. The Concept Name Code Sequence (0040,A043) shall always be sent zero length in the Request Identifier. + The Value Type (0040,A040) applies to the Concept Name Code Sequence (0040,A043), and shall be the same as the Value Type (0040,A040) of the first row of the template identified in the Content Template Sequence (0040,A504) in the Identifier. + The Content Sequence (0040,A730) is a potentially recursively nested Sequence of Items, as described in , SR Document Content Module. The Content Sequence shall always be sent zero length in the Request Identifier. The Content Sequence in the Data Set of the Response shall contain the content items of the requested template.
Conformance Requirements - An implementation may conform to the - Relevant Patient Information Model SOP Classes as an SCU and/or as an SCP. - - The Conformance Statement shall be in the - format defined in. - + An implementation may conform to the Relevant Patient Information Model SOP Classes as an SCU and/or as an SCP. + The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that conforms to one - or more of the Relevant Patient Information Model SOP Classes shall support queries against - the Relevant Patient Information Model described in - - using the baseline C-FIND SCU Behavior described in. - - An implementation that conforms to one - or more of the Relevant Patient Information Model SOP Classes as an SCU shall state in its - Conformance Statement which SOP Class(es) it supports, and which Root template(s) it may - request in a query if not specified by the SOP Class. The Conformance Statement shall also - state the definition of any supported template extensions. - + An implementation that conforms to one or more of the Relevant Patient Information Model SOP Classes shall support queries against the Relevant Patient Information Model described in using the baseline C-FIND SCU Behavior described in . + An implementation that conforms to one or more of the Relevant Patient Information Model SOP Classes as an SCU shall state in its Conformance Statement which SOP Class(es) it supports, and which Root template(s) it may request in a query if not specified by the SOP Class. The Conformance Statement shall also state the definition of any supported template extensions.
SCP Conformance - An implementation that conforms to one - or more of the Relevant Patient Information Model SOP Classes shall support queries against - the Relevant Patient Information Model described in - - using the baseline C-FIND SCP Behavior described in. - - An implementation that conforms to one - or more of the Relevant Patient Information Model SOP Classes as an SCP shall state in its - Conformance Statement which SOP Class(es) it supports, and which Root template(s) it will - support in a query response if not specified by the SOP Class. The Conformance Statement - shall also state the definition of any supported template extensions. - - An implementation that conforms to one - or more of the Relevant Patient Information Model SOP Classes as an SCP shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) when - interpreting queries, performing matching, and encoding responses. - + An implementation that conforms to one or more of the Relevant Patient Information Model SOP Classes shall support queries against the Relevant Patient Information Model described in using the baseline C-FIND SCP Behavior described in . + An implementation that conforms to one or more of the Relevant Patient Information Model SOP Classes as an SCP shall state in its Conformance Statement which SOP Class(es) it supports, and which Root template(s) it will support in a query response if not specified by the SOP Class. The Conformance Statement shall also state the definition of any supported template extensions. + An implementation that conforms to one or more of the Relevant Patient Information Model SOP Classes as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching, and encoding responses.
SOP Classes - The Relevant Patient Information Model SOP - Classes in the Relevant Patient Information Query Service Class identify the Relevant Patient - Information Model, and the DIMSE-C operation supported. In some instances a Root template is - specified. The Standard SOP Classes are defined in: - + The Relevant Patient Information Model SOP Classes in the Relevant Patient Information Query Service Class identify the Relevant Patient Information Model, and the DIMSE-C operation supported. In some instances a Root template is specified. The Standard SOP Classes are defined in :
Additional C-FIND Identifier Attributes
- Type in Request - Identifier - + Type in Request Identifier - Type in Response - Identifier - + Type in Response Identifier Remark @@ -38238,9 +27098,7 @@
- Content Template - Sequence - + Content Template Sequence (0040,A504) @@ -38255,8 +27113,7 @@
- >Mapping Resource - + >Mapping Resource (0008,0105) @@ -38271,9 +27128,7 @@
- >Template - Identifier - + >Template Identifier (0040,DB00) @@ -38288,9 +27143,7 @@
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -38302,10 +27155,7 @@ 1C - Required if expanded or - replacement character sets are used. See, - + Required if expanded or replacement character sets are used. See ,
@@ -38407,69 +27205,49 @@
SOP Classes for the Relevant Patient Information Model
- General Relevant Patient - Information Query - + General Relevant Patient Information Query - 1.2.840.10008.5.1.4.37.1 - + 1.2.840.10008.5.1.4.37.1 - TID 9007 General Relevant - Patient Information, or from the list in - + TID 9007 General Relevant Patient Information, or from the list in
- Breast Imaging Relevant - Patient Information Query - + Breast Imaging Relevant Patient Information Query - 1.2.840.10008.5.1.4.37.2 - + 1.2.840.10008.5.1.4.37.2 - TID 9000 Relevant Patient - Information for Breast Imaging - + TID 9000 Relevant Patient Information for Breast Imaging
- Cardiac Relevant Patient - Information Query - + Cardiac Relevant Patient Information Query - 1.2.840.10008.5.1.4.37.3 - + 1.2.840.10008.5.1.4.37.3 - TID 3802 Cardiovascular - Patient History - + TID 3802 Cardiovascular Patient History
- The list of Root templates for the - General Relevant Patient Information Query is extensible. - + The list of Root templates for the General Relevant Patient Information Query is extensible.
Relevant Patient Information Query Example (Informative) - Moved to. - + Moved to .
@@ -38478,51 +27256,20 @@ Overview
Scope - The Instance Availability Notification Service - Class defines an application-level class-of-service that allows one DICOM AE to notify another DICOM - AE of the presence and availability of SOP instances that may be retrieved. The AE from which such - SOP Instances can later be retrieved may or may not be the SCU performing the notification. - + The Instance Availability Notification Service Class defines an application-level class-of-service that allows one DICOM AE to notify another DICOM AE of the presence and availability of SOP instances that may be retrieved. The AE from which such SOP Instances can later be retrieved may or may not be the SCU performing the notification. - An example of usage of this Service Class - is for the receiver of the instances to provide notification of their arrival and availability - for subsequent workflow steps to a different entity, such as a separate workflow manager. - + An example of usage of this Service Class is for the receiver of the instances to provide notification of their arrival and availability for subsequent workflow steps to a different entity, such as a separate workflow manager. - The SCU implementation defines the conditions - under which it provides the notification. Certain SCUs may provide notification for arbitrary sets - of SOP Instances, while other SCUs may provide notification when they determine that the instances - associated with a Procedure Step or a Requested Procedure are available. The SCU is required to - document in its Conformance Statement the nature of its notification decisions (e.g., frequency of - notifications, retrieve capabilities and latency, etc.). - - Once the SCU has provided notification about - availability of the SOP Instances, the SCP may use that information in directing further workflow, - such as in populating the Input Information Sequence when forming a Unified Procedure Step. These - types of policies are outside the scope of this Standard, however, the SCP is required to document - these policies in its Conformance Statement. - - The SCU of this Service Class is not required - to assure that the study, procedure step or any workflow-related entity is "complete"; indeed no - semantics other than the concept of "availability" is expressed or implied by the use of this - service. - + The SCU implementation defines the conditions under which it provides the notification. Certain SCUs may provide notification for arbitrary sets of SOP Instances, while other SCUs may provide notification when they determine that the instances associated with a Procedure Step or a Requested Procedure are available. The SCU is required to document in its Conformance Statement the nature of its notification decisions (e.g., frequency of notifications, retrieve capabilities and latency, etc.). + Once the SCU has provided notification about availability of the SOP Instances, the SCP may use that information in directing further workflow, such as in populating the Input Information Sequence when forming a Unified Procedure Step. These types of policies are outside the scope of this Standard, however, the SCP is required to document these policies in its Conformance Statement. + The SCU of this Service Class is not required to assure that the study, procedure step or any workflow-related entity is "complete"; indeed no semantics other than the concept of "availability" is expressed or implied by the use of this service. - The Performed Workitem Code - Sequence (0040,4019) Attribute of a referenced GP-PPS instance may provide the specific - description of the work item that triggered the Instance Availability Notification. - + The Performed Workitem Code Sequence (0040,4019) Attribute of a referenced GP-PPS instance may provide the specific description of the work item that triggered the Instance Availability Notification. - The Instance Availability - Notification is typically a service of the composite instance Storage SCP, since that - application is responsible for making the instances available. The Instance Availability - Notification allows that application to report the specific Retrieve AE Title, which may - differ from the Storage Service AE Title, and may vary with different instance SOP - Classes, or may vary over time. - + The Instance Availability Notification is typically a service of the composite instance Storage SCP, since that application is responsible for making the instances available. The Instance Availability Notification allows that application to report the specific Retrieve AE Title, which may differ from the Storage Service AE Title, and may vary with different instance SOP Classes, or may vary over time. @@ -38530,36 +27277,21 @@
Conformance Overview - The Instance Availability Notification Service - Class consists of a single SOP Class: the Instance Availability Notification SOP Class. - - The SOP Class specifies Attributes, operations, and - behavior applicable to the SOP Class. The conformance requirements shall be specified in terms of the - Service Class Provider (SCP) and the Service Class User (SCU). - - The Instance Availability Notification Service - Class uses the Instance Availability Notification IOD as defined in - - and the N-CREATE DIMSE Service specified in. - + The Instance Availability Notification Service Class consists of a single SOP Class: the Instance Availability Notification SOP Class. + The SOP Class specifies Attributes, operations, and behavior applicable to the SOP Class. The conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU). + The Instance Availability Notification Service Class uses the Instance Availability Notification IOD as defined in and the N-CREATE DIMSE Service specified in .
Instance Availability Notification SOP Class
DIMSE Service Group - The DIMSE Services shown in - - are applicable to the Instance Availability Notification IOD under the Instance Availability - Notification SOP Class. - + The DIMSE Services shown in are applicable to the Instance Availability Notification IOD under the Instance Availability Notification SOP Class.
DIMSE Service Group Applicable to Instance Availability Notification
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -38577,35 +27309,20 @@
- The DIMSE Services and Protocols are specified - in. - + The DIMSE Services and Protocols are specified in . - Though the terminology "notification" is - used for this Service Class, the notification is in fact performed through Operations rather - than Notifications. - + Though the terminology "notification" is used for this Service Class, the notification is in fact performed through Operations rather than Notifications.
Operations - The Application Entity that claims conformance - to this SOP Class as an SCU shall be permitted to invoke the following operations and the - Application Entity that claims conformance as an SCP shall be capable of providing the following - operations. - + The Application Entity that claims conformance to this SOP Class as an SCU shall be permitted to invoke the following operations and the Application Entity that claims conformance as an SCP shall be capable of providing the following operations.
N-CREATE Instance Availability Notification SOP Instance - This operation allows an SCU to create an - instance of the Instance Availability Notification SOP Class and to provide availability - information about Instances that are under the control of the SCU. This operation shall be - invoked through the DIMSE N-CREATE Service. - + This operation allows an SCU to create an instance of the Instance Availability Notification SOP Class and to provide availability information about Instances that are under the control of the SCU. This operation shall be invoked through the DIMSE N-CREATE Service.
Attributes - The Attribute list of the N-CREATE is - defined as shown in. - + The Attribute list of the N-CREATE is defined as shown in . @@ -38617,35 +27334,27 @@ Tag @@ -38655,9 +27364,7 @@ - - - - - - - + + + + + + +
Instance Availability Notification SOP Class N-CREATE Attributes
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP)
- Specific Character - Set - + Specific Character Set (0008,0005) 1C/1C - (Required if an - extended or replacement character set is used) - + (Required if an extended or replacement character set is used)
- All other Attributes of the - + All other Attributes of the
- Referenced Performed - Procedure Step Sequence - + Referenced Performed Procedure Step Sequence (0008,1111) @@ -38668,9 +27375,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -38681,9 +27386,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -38693,31 +27396,27 @@
- >Performed Workitem - Code Sequence - - - (0040,4019) - - 2/2 -
- - >>Include - - - -
+ >Performed Workitem Code Sequence + + (0040,4019) + + 2/2 +
+ +>>Include + + +
- Study Instance UID - + Study Instance UID (0020,000D) @@ -38728,9 +27427,7 @@
- Referenced Series - Sequence - + Referenced Series Sequence (0008,1115) @@ -38741,9 +27438,7 @@
- >Series Instance - UID - + >Series Instance UID (0020,000E) @@ -38754,9 +27449,7 @@
- >Referenced SOP - Sequence - + >Referenced SOP Sequence (0008,1199) @@ -38767,9 +27460,7 @@
- >>Referenced SOP - Class UID - + >>Referenced SOP Class UID (0008,1150) @@ -38780,9 +27471,7 @@
- >>Reference SOP - Instance UID - + >>Reference SOP Instance UID (0008,1155) @@ -38793,9 +27482,7 @@
- >>Instance - Availability - + >>Instance Availability (0008,0056) @@ -38806,9 +27493,7 @@
- >>Retrieve AE - Title - + >>Retrieve AE Title (0008,0054) @@ -38819,9 +27504,7 @@
- >>Retrieve - Location UID - + >>Retrieve Location UID (0040,E011) @@ -38832,8 +27515,7 @@
- >>Retrieve URI - + >>Retrieve URI (0040,E010) @@ -38844,8 +27526,7 @@
- >>Retrieve URL - + >>Retrieve URL (0008,1190) @@ -38856,9 +27537,7 @@
- >>Storage Media - File-Set ID - + >>Storage Media File-Set ID (0088,0130) @@ -38869,9 +27548,7 @@
- >>Storage Media - File-Set UID - + >>Storage Media File-Set UID (0088,0140) @@ -38885,115 +27562,53 @@
Service Class User - The SCU shall specify in the N-CREATE - request primitive the SOP Class and SOP Instance UIDs of the Instance Availability - Notification SOP Instance that is created and for which Attribute Values are to be provided. - - The SCU shall provide Attribute Values - for the Instance Availability Notification SOP Class Attributes as specified in. - - The use of additional optional - Attributes by the SCU is forbidden. - + The SCU shall specify in the N-CREATE request primitive the SOP Class and SOP Instance UIDs of the Instance Availability Notification SOP Instance that is created and for which Attribute Values are to be provided. + The SCU shall provide Attribute Values for the Instance Availability Notification SOP Class Attributes as specified in . + The use of additional optional Attributes by the SCU is forbidden. - The reason for forbidding optional - Attributes is to prevent the use of Standard Extended SOP Classes that might add - contextual information such as patient and procedure identifiers. - + The reason for forbidding optional Attributes is to prevent the use of Standard Extended SOP Classes that might add contextual information such as patient and procedure identifiers. - The encoding rules for Instance - Availability Notification Attributes are specified in the N-CREATE request primitive - specification in - . - - There are no requirements on when - N-CREATE requests are required to be performed. - - In particular, there are no - requirements that notification about the availability of the first instance of a Performed - Procedure Step or Study be provided upon its reception, nor that availability notification - be provided when an entire set of instances comprising a completed Performed Procedure Step - or Study are available, though these are typical and common scenarios. - + The encoding rules for Instance Availability Notification Attributes are specified in the N-CREATE request primitive specification in . + There are no requirements on when N-CREATE requests are required to be performed. + In particular, there are no requirements that notification about the availability of the first instance of a Performed Procedure Step or Study be provided upon its reception, nor that availability notification be provided when an entire set of instances comprising a completed Performed Procedure Step or Study are available, though these are typical and common scenarios.
Service Class Provider - The SCP shall return, via the N-CREATE - response primitive, the N-CREATE Response Status Code applicable to the associated request. - + The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request.
Status Codes - There are no specific status codes. See - - for response status codes. - + There are no specific status codes. See for response status codes.
Instance Availability Notification SOP Class UID - The Instance Availability Notification SOP - Class shall be uniquely identified by the Instance Availability Notification SOP Class UID, which - shall have the value "1.2.840.10008.5.1.4.33". - + The Instance Availability Notification SOP Class shall be uniquely identified by the Instance Availability Notification SOP Class UID, which shall have the value "1.2.840.10008.5.1.4.33".
Conformance Requirements - Implementations shall include within their - Conformance Statement information as described below. - - An implementation may conform to this SOP Class - as an SCU or as an SCP. The Conformance Statement shall be in the format defined in. - + Implementations shall include within their Conformance Statement information as described below. + An implementation may conform to this SOP Class as an SCU or as an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to - this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes. - + An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for the operations that it invokes.
Operations - Any Attributes for which Attribute - Values may be provided (using the N-CREATE) by the SCU shall be enumerated in the SCU - Conformance Statement. The SCU Conformance Statement shall be formatted as defined in. - - An implementation that conforms to this - SOP Class as an SCU shall specify under which conditions during the performance of - real-world activities it will create the SOP Class Instance. - - The SCU Conformance Statement shall - specify what is meant by each reported value of Instance Availability (0008,0056). - - The SCU Conformance Statement shall - describe the relationship between the Instance Availability Notification and the Performed - Procedure Step SOP Classes, if the latter are supported. - + Any Attributes for which Attribute Values may be provided (using the N-CREATE) by the SCU shall be enumerated in the SCU Conformance Statement. The SCU Conformance Statement shall be formatted as defined in . + An implementation that conforms to this SOP Class as an SCU shall specify under which conditions during the performance of real-world activities it will create the SOP Class Instance. + The SCU Conformance Statement shall specify what is meant by each reported value of Instance Availability (0008,0056). + The SCU Conformance Statement shall describe the relationship between the Instance Availability Notification and the Performed Procedure Step SOP Classes, if the latter are supported.
SCP Conformance - An implementation that is conformant to - this SOP Class as an SCP shall meet conformance requirements for the operations that it - performs. - + An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for the operations that it performs.
Operations - The SCP Conformance Statement shall be - formatted as defined in. - - The SCP Conformance Statement shall - provide information on the behavior of the SCP (in terms of real world activities) for each - reported value of Instance Availability (0008,0056). - - The SCP Conformance Statement shall - describe the behavioral relationship between the Instance Availability Notification and the - Performed Procedure Step SOP Classes, if the latter are supported. - + The SCP Conformance Statement shall be formatted as defined in . + The SCP Conformance Statement shall provide information on the behavior of the SCP (in terms of real world activities) for each reported value of Instance Availability (0008,0056). + The SCP Conformance Statement shall describe the behavioral relationship between the Instance Availability Notification and the Performed Procedure Step SOP Classes, if the latter are supported.
@@ -39005,130 +27620,59 @@ Overview
Scope - The Media Creation Management Service Class - defines a mechanism by which an SCU can instruct a device to create Interchange Media containing a - set of Composite SOP Instances that have already been transferred to the media creation device using - the Storage Service Class. - - This Service Class does not address archival - storage requirements. It is intended only for the management of media creation devices. There is no - requirement by the Standard that an SCP of this Service Class will commit to taking responsibility - for archival of Composite Instances, such that an SCU may then discard them. Such behavior is - entirely outside the scope of the Standard. In other words, Media Creation does not imply Storage - Commitment. - - The application profile(s) for the set of - instances, which implies the form of the media created (i.e., CD, DVD or MOD), can either be left to - the discretion of the SCP, or explicitly specified in the media creation request. In the latter - case, if the device is unable to create the requested profiles, an error shall be returned. - + The Media Creation Management Service Class defines a mechanism by which an SCU can instruct a device to create Interchange Media containing a set of Composite SOP Instances that have already been transferred to the media creation device using the Storage Service Class. + This Service Class does not address archival storage requirements. It is intended only for the management of media creation devices. There is no requirement by the Standard that an SCP of this Service Class will commit to taking responsibility for archival of Composite Instances, such that an SCU may then discard them. Such behavior is entirely outside the scope of the Standard. In other words, Media Creation does not imply Storage Commitment. + The application profile(s) for the set of instances, which implies the form of the media created (i.e., CD, DVD or MOD), can either be left to the discretion of the SCP, or explicitly specified in the media creation request. In the latter case, if the device is unable to create the requested profiles, an error shall be returned. - More than one profile may be - requested or used by default, since the requested set of instances may not be compatible - with a single profile. DICOM media may always contain instances written by more than one - profile. See - . - + More than one profile may be requested or used by default, since the requested set of instances may not be compatible with a single profile. DICOM media may always contain instances written by more than one profile. See . - It is the responsibility of the SCU - to negotiate and store instances with an appropriate Transfer Syntax should a specific - Transfer Syntax be required by a requested profile. The SCP is not required to support - compression or decompression of stored instances in order to convert stored instances - into a form suitable for a requested profile. It may do so, if so requested, but the - level of lossy compression would be at the discretion of the SCP. If the degree of - compression is important to the application, then the SCU may compress the images before - sending them to the SCP. - + It is the responsibility of the SCU to negotiate and store instances with an appropriate Transfer Syntax should a specific Transfer Syntax be required by a requested profile. The SCP is not required to support compression or decompression of stored instances in order to convert stored instances into a form suitable for a requested profile. It may do so, if so requested, but the level of lossy compression would be at the discretion of the SCP. If the degree of compression is important to the application, then the SCU may compress the images before sending them to the SCP. - The request controls whether or not a label is - to be generated on the media, be it from information contained in the instances (such as patient - demographics) or from text explicitly specified in the request. - + The request controls whether or not a label is to be generated on the media, be it from information contained in the instances (such as patient demographics) or from text explicitly specified in the request. - An SCP may or may not be physically - capable of labeling the media. This capability is outside the scope of conformance to - the Standard. Inability to create a label is not an error. - + An SCP may or may not be physically capable of labeling the media. This capability is outside the scope of conformance to the Standard. Inability to create a label is not an error. - De-identification of instances (and - labels), such as for teaching file media or clinical trial media is the responsibility - of the SCU and is outside the scope of this service. That is, the SCU must de-identify - the composite instances before sending them, prior to the media creation request. - + De-identification of instances (and labels), such as for teaching file media or clinical trial media is the responsibility of the SCU and is outside the scope of this service. That is, the SCU must de-identify the composite instances before sending them, prior to the media creation request. - The Service Class contains a limited capability - to return status information. A media creation request may initially either fail or be accepted. - Subsequently, the SCP may be polled as to the status of the request (idle, pending/creating, - successful or failed) by the SCU on the same or on a separate Association. There is no asynchronous - notification. There is no dependence on the duration or persistence of an Association. - + The Service Class contains a limited capability to return status information. A media creation request may initially either fail or be accepted. Subsequently, the SCP may be polled as to the status of the request (idle, pending/creating, successful or failed) by the SCU on the same or on a separate Association. There is no asynchronous notification. There is no dependence on the duration or persistence of an Association. - There is no requirement to manage the - handling of transient failures (such as an empty supply of blank media or labels or ink). - Whether or not the SCP queues stored instances and requests in such cases, or fails to accept - the request, is outside the scope of the Standard. - + There is no requirement to manage the handling of transient failures (such as an empty supply of blank media or labels or ink). Whether or not the SCP queues stored instances and requests in such cases, or fails to accept the request, is outside the scope of the Standard.
Conformance Overview - The application-level services addressed by this - Service Class are specified via the Media Creation Management SOP Class. - - The Media Creation Management SOP Class specifies - Attributes, operations and behavior applicable to the SOP Class. The conformance requirements shall be - specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU). - - The Media Creation Management Service Class uses - the Media Creation Management IOD as defined in - - and the N-CREATE, N-ACTION and N-GET Services specified in. - + The application-level services addressed by this Service Class are specified via the Media Creation Management SOP Class. + The Media Creation Management SOP Class specifies Attributes, operations and behavior applicable to the SOP Class. The conformance requirements shall be specified in terms of the Service Class Provider (SCP) and the Service Class User (SCU). + The Media Creation Management Service Class uses the Media Creation Management IOD as defined in and the N-CREATE, N-ACTION and N-GET Services specified in .
Association Negotiation - Association establishment is the first phase of - any instance of communication between peer DICOM AEs. The Association negotiation rules as specified - in - - shall be used to negotiate the supported SOP Classes. - - Support for the SCP/SCU Role Selection - Negotiation is not applicable. The SOP Class Extended Negotiation is not defined for this Service - Class. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation rules as specified in shall be used to negotiate the supported SOP Classes. + Support for the SCP/SCU Role Selection Negotiation is not applicable. The SOP Class Extended Negotiation is not defined for this Service Class.
Media Creation Management SOP Class - The SCU transmits the SOP Instances to the SCP - using the Storage Service Class. The request for media creation is transmitted to the SCP and contains a - list of references to one or more SOP Instances. Success or failure of media creation is subsequently - indicated by the SCU requesting the status from the SCP on the same or a separate association. - + The SCU transmits the SOP Instances to the SCP using the Storage Service Class. The request for media creation is transmitted to the SCP and contains a list of references to one or more SOP Instances. Success or failure of media creation is subsequently indicated by the SCU requesting the status from the SCP on the same or a separate association.
DIMSE Service Group - The following DIMSE-N Services are applicable - to the Media Creation Management SOP Class. - + The following DIMSE-N Services are applicable to the Media Creation Management SOP Class.
DIMSE Service Group Applicable to Media Creation Management
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -39162,33 +27706,17 @@
- The DIMSE-N Services and Protocol are specified - in. - + The DIMSE-N Services and Protocol are specified in .
Operations - The DICOM AEs that claim conformance to this - SOP Class as an SCU shall invoke the N-CREATE and the N-ACTION operations. The DICOM AEs that claim - conformance to this SOP Class as an SCP shall support the N-CREATE, the N-ACTION and the N-GET - operations. - + The DICOM AEs that claim conformance to this SOP Class as an SCU shall invoke the N-CREATE and the N-ACTION operations. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support the N-CREATE, the N-ACTION and the N-GET operations.
Create a Media Creation Request - The Create a Media Creation Request - operation allows an SCU to create an instance of the Media Creation Management SOP Class and - initialize Attributes of the SOP Class. The SCP uses this operation to create a new media - creation request containing the set of SOP Instances that shall be included in the Interchange - Media. This operation shall be invoked through the N-CREATE primitive - + The Create a Media Creation Request operation allows an SCU to create an instance of the Media Creation Management SOP Class and initialize Attributes of the SOP Class. The SCP uses this operation to create a new media creation request containing the set of SOP Instances that shall be included in the Interchange Media. This operation shall be invoked through the N-CREATE primitive
Attributes - The DICOM AEs that claim conformance to - this SOP Class as an SCU may choose to provide a subset of the Attributes maintained by the - SCP. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support a subset - of the Media Creation Management specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU may choose to provide a subset of the Attributes maintained by the SCP. The DICOM AEs that claim conformance to this SOP Class as an SCP shall support a subset of the Media Creation Management specified in . @@ -39200,74 +27728,56 @@ Tag @@ -39279,24 +27789,19 @@ @@ -39308,109 +27813,90 @@
Media Creation Management - N-CREATE Attributes
- Requirement Type - SCU/SCP - + Requirement Type SCU/SCP
- Specific Character - Set - + Specific Character Set (0008,0005) - 1C/1C (Required if - expanded or replacement character set is used) - + 1C/1C (Required if expanded or replacement character set is used)
- Storage Media File-Set - ID - + Storage Media File-Set ID (0088,0130) 3/3 - See. - + See .
- Storage Media File-Set - UID - + Storage Media File-Set UID (0088,0140) 3/3 - See. - + See .
- Label Using Information - Extracted From Instances - + Label Using Information Extracted From Instances (2200,0001) 3/1C - See. - + See .
3/1C - See. - + See .
- Label Style Selection - + Label Style Selection (2200,0003) 3/1C - See. - + See .
3/3 - See - + See
- Barcode Symbology - + Barcode Symbology (2200,0006) 3/3 - See - + See
- Media Disposition - + Media Disposition (2200,0004) 3/3 - See. - + See .
- Allow Media Splitting - + Allow Media Splitting (2200,0007) 3/1C - See - + See
- Allow Lossy - Compression - + Allow Lossy Compression (2200,000F) 3/1C - See - + See
- Include Non-DICOM - Objects - + Include Non-DICOM Objects (2200,0008) 3/1C - See - + See
- Include Display - Application - + Include Display Application (2200,0009) 3/1C - See - + See
- Preserve Composite - Instances After Media Creation - + Preserve Composite Instances After Media Creation (2200,000A) @@ -39421,9 +27907,7 @@
- Referenced SOP - Sequence - + Referenced SOP Sequence (0008,1199) @@ -39434,9 +27918,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -39447,9 +27929,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -39460,398 +27940,185 @@
- >Requested Media - Application Profile - + >Requested Media Application Profile (2200,000C) 3/1 - See. - + See .
- >Icon Image - Sequence - + >Icon Image Sequence (0088,0200) 3/1C - See. - + See .
Storage Media File-Set Attributes - If present, the Storage Media - File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall be used on the - media created. If absent, the media shall contain values generated by the SCP. - - If the media request will not fit - on a single volume (single piece or side of media), then whether or not the SCP ignores - Storage Media File-Set ID (0088,0130), or uses it as a prefix and appends information to - distinguish volumes, is implementation dependent. Different values of Storage Media - File-Set UID (0088,0140) shall be used for different volumes. - - If multiple copies are requested, - the same Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID - (0088,0140) shall be used on all copies. - + If present, the Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall be used on the media created. If absent, the media shall contain values generated by the SCP. + If the media request will not fit on a single volume (single piece or side of media), then whether or not the SCP ignores Storage Media File-Set ID (0088,0130), or uses it as a prefix and appends information to distinguish volumes, is implementation dependent. Different values of Storage Media File-Set UID (0088,0140) shall be used for different volumes. + If multiple copies are requested, the same Storage Media File-Set ID (0088,0130) and Storage Media File-Set UID (0088,0140) shall be used on all copies. - Care should be taken with - multiple copies written to rewritable media that their contents do not diverge even - though their identifiers are identical. - + Care should be taken with multiple copies written to rewritable media that their contents do not diverge even though their identifiers are identical.
Requested Media Application Profile - The Requested Media Application - Profile (2200,000C), if present, shall be used by the SCP for the specified SOP - Instance. If absent for a particular instance, the choice of Media Application Profile - for that instance shall be at the discretion of the SCP. - + The Requested Media Application Profile (2200,000C), if present, shall be used by the SCP for the specified SOP Instance. If absent for a particular instance, the choice of Media Application Profile for that instance shall be at the discretion of the SCP. - Different Media - Application Profiles may be used for different instances on the same piece - of media. - + Different Media Application Profiles may be used for different instances on the same piece of media. - The form of the - DICOMDIR directory records that the SCP must create may be significantly - influenced by the media application profiles used. - + The form of the DICOMDIR directory records that the SCP must create may be significantly influenced by the media application profiles used.
Icon Image Sequence - The Icon Image Sequence - (0088,0200), if present: - + The Icon Image Sequence (0088,0200), if present: - shall be used by the SCP - for inclusion in the instance-level DICOM Directory Record for the specified SOP - Instance, if the Media Application Profile requires its inclusion, and the icon - supplied by the SCU meets the requirements of the profile - + shall be used by the SCP for inclusion in the instance-level DICOM Directory Record for the specified SOP Instance, if the Media Application Profile requires its inclusion, and the icon supplied by the SCU meets the requirements of the profile - may be used by the SCP for - inclusion in the instance-level DICOM Directory Record for the specified SOP - Instance, if the Media Application Profile does not require its inclusion - + may be used by the SCP for inclusion in the instance-level DICOM Directory Record for the specified SOP Instance, if the Media Application Profile does not require its inclusion - If absent for a particular - instance, the choice of Media Application Profile for that instance dictates whether or - not the SCP is required to create its own Icon Image Sequence (0088,0200) from the - contents of the SOP Instance. - + If absent for a particular instance, the choice of Media Application Profile for that instance dictates whether or not the SCP is required to create its own Icon Image Sequence (0088,0200) from the contents of the SOP Instance. - Some Media Application - Profiles require the inclusion of an Icon Image Sequence (0088,0200) in the - directory records. - + Some Media Application Profiles require the inclusion of an Icon Image Sequence (0088,0200) in the directory records. - Some Media Application - Profiles specify constraints on the form of the Icon Image Sequence - (0088,0200). - + Some Media Application Profiles specify constraints on the form of the Icon Image Sequence (0088,0200). - The SCP may choose to - extend the Media Application Profile by generating and including icons - anyway. - + The SCP may choose to extend the Media Application Profile by generating and including icons anyway.
Labeling - The SCP may or may not have the - capability to print a label on (or for) the media. If it does, then the following SCP - behavior shall apply and the specified Attributes are required to be supported by the - SCP. - - The Label Using Information - Extracted From Instances (2200,0001) Attribute is a flag that instructs the SCP whether - or not to create any label using the Patient and Study information contained within the - instances themselves. - + The SCP may or may not have the capability to print a label on (or for) the media. If it does, then the following SCP behavior shall apply and the specified Attributes are required to be supported by the SCP. + The Label Using Information Extracted From Instances (2200,0001) Attribute is a flag that instructs the SCP whether or not to create any label using the Patient and Study information contained within the instances themselves. - The SCP may implement whatever - it considers to be an appropriate subset of any Attributes of any Modules at the - Patient, Specimen and Study entities in the DICOM Information Model specified in - . - Typically included are such Attributes as Patient Name (0010,0010), Patient ID - (0010,0020), Study ID (0020,0010), and Study Date (0008,0020). - + The SCP may implement whatever it considers to be an appropriate subset of any Attributes of any Modules at the Patient, Specimen and Study entities in the DICOM Information Model specified in . Typically included are such Attributes as Patient Name (0010,0010), Patient ID (0010,0020), Study ID (0020,0010), and Study Date (0008,0020). - The Label Text (2200,0002) - Attribute is additional text that the SCP shall include on any label, either in addition - to or instead of any extracted demographics, depending on the value of Label Using - Information Extracted From Instances (2200,0001). - - The Label Style Selection - (2200,0003) Attribute is a code string, which if present, may be used by the SCP to - choose one or more implementation-dependent styles of labeling. - - The Barcode Value (2200,0005) and - the Barcode Symbology (2200,0006), if present, may be used by the SCP to print a barcode - on the label. - - Note It is SCU responsibility to - convey a value for the Barcode Value (2200,0005) Attribute consistent in length and - content with the requested Barcode Symbology (2200,0006). - + The Label Text (2200,0002) Attribute is additional text that the SCP shall include on any label, either in addition to or instead of any extracted demographics, depending on the value of Label Using Information Extracted From Instances (2200,0001). + The Label Style Selection (2200,0003) Attribute is a code string, which if present, may be used by the SCP to choose one or more implementation-dependent styles of labeling. + The Barcode Value (2200,0005) and the Barcode Symbology (2200,0006), if present, may be used by the SCP to print a barcode on the label. + Note It is SCU responsibility to convey a value for the Barcode Value (2200,0005) Attribute consistent in length and content with the requested Barcode Symbology (2200,0006).
Media Disposition - The Media Disposition (2200,0004), - if present, may be used by the SCP to determine where and to whom to send the media when - completed. - + The Media Disposition (2200,0004), if present, may be used by the SCP to determine where and to whom to send the media when completed. - For example, it may contain the - name and address of a referring doctor, and be used to print a label for an envelope - or mailer, or as additional material to be printed on the media label. - + For example, it may contain the name and address of a referring doctor, and be used to print a label for an envelope or mailer, or as additional material to be printed on the media label.
Allow Media Splitting - The SCP may or may not have the - capability to split a request over more than one piece of media (e.g., if it doesn't fit - on one). If it does, then the following SCP behavior shall apply and the specified - Attributes are required to be supported by the SCP. - - The Allow Media Splitting - (2200,0007) Attribute shall be used by the SCP to determine if it is permitted to split - this request over more than one piece of media. - + The SCP may or may not have the capability to split a request over more than one piece of media (e.g., if it doesn't fit on one). If it does, then the following SCP behavior shall apply and the specified Attributes are required to be supported by the SCP. + The Allow Media Splitting (2200,0007) Attribute shall be used by the SCP to determine if it is permitted to split this request over more than one piece of media. - If the file-set size - exceeds the media storage capacity, and this flag has been set to NO, the - SCP shall refuse to process the request. - + If the file-set size exceeds the media storage capacity, and this flag has been set to NO, the SCP shall refuse to process the request. - If the requested Media - Application Profile allows for lossless compression, and images are not - already compressed, such compression may be applied by the SCP in order to - fit all instances on a single piece of media. This also applies to lossy - compression if it has not been allowed by the value of Allow Lossy - Compression (2200,000F). - + If the requested Media Application Profile allows for lossless compression, and images are not already compressed, such compression may be applied by the SCP in order to fit all instances on a single piece of media. This also applies to lossy compression if it has not been allowed by the value of Allow Lossy Compression (2200,000F).
Include Non-DICOM Objects - The SCP may or may not have the - capability to include on the created media additional Non-DICOM objects (e.g., HTML - files, JPEG images) that are a rendering of the DICOM instances. If it does, then the - following SCP behavior shall apply and the specified Attributes are required to be - supported by the SCP. - - The Include Non-DICOM Objects - (2200,0008) shall be used to request the SCP to add additional Non-DICOM objects onto - the created media. - - An SCP is not required to be able - to add such files. Inability to add Non-DICOM objects is not an error. - - If Include Non-DICOM Objects - (2200,0008) is set to NO, the SCP shall not include additional non-DICOM objects on the - media. - + The SCP may or may not have the capability to include on the created media additional Non-DICOM objects (e.g., HTML files, JPEG images) that are a rendering of the DICOM instances. If it does, then the following SCP behavior shall apply and the specified Attributes are required to be supported by the SCP. + The Include Non-DICOM Objects (2200,0008) shall be used to request the SCP to add additional Non-DICOM objects onto the created media. + An SCP is not required to be able to add such files. Inability to add Non-DICOM objects is not an error. + If Include Non-DICOM Objects (2200,0008) is set to NO, the SCP shall not include additional non-DICOM objects on the media.
Include Display Application - The SCP may or may not have the - capability to include on the created media an application for displaying DICOM - instances. If it does, then the following SCP behavior shall apply and the specified - Attributes are required to be supported by the SCP. - - The Include Display Application - (2200,0009) shall be used to request the SCP to add an application for displaying DICOM - instances onto the created media. - - An SCP is not required to be able - to add such an application. Inability to add a display application is not an error. - - Whether the display application is - capable of displaying all stored instances is beyond the scope of the Standard. - - Whether the display application - automatically executes when media is inserted for reading is beyond the scope of the - Standard. - - Which platforms are supported by - the display application(s) is beyond the scope of the Standard. - + The SCP may or may not have the capability to include on the created media an application for displaying DICOM instances. If it does, then the following SCP behavior shall apply and the specified Attributes are required to be supported by the SCP. + The Include Display Application (2200,0009) shall be used to request the SCP to add an application for displaying DICOM instances onto the created media. + An SCP is not required to be able to add such an application. Inability to add a display application is not an error. + Whether the display application is capable of displaying all stored instances is beyond the scope of the Standard. + Whether the display application automatically executes when media is inserted for reading is beyond the scope of the Standard. + Which platforms are supported by the display application(s) is beyond the scope of the Standard. - Multiple files may need to be - included in the media to support the display application, rather than a single - executable file, and these may be present, even if the Include Non-DICOM Objects - (2200,0008) Attribute has a value of NO. - + Multiple files may need to be included in the media to support the display application, rather than a single executable file, and these may be present, even if the Include Non-DICOM Objects (2200,0008) Attribute has a value of NO. - If Include Display Application - (2200,0009) is set to NO, the SCP shall not include a display application on the media. - + If Include Display Application (2200,0009) is set to NO, the SCP shall not include a display application on the media.
Allow Lossy Compression - If Allow Lossy Compression - (2200,000F) has a value of YES, the SCP is allowed to perform lossy compression under - the following circumstances: - + If Allow Lossy Compression (2200,000F) has a value of YES, the SCP is allowed to perform lossy compression under the following circumstances: - if it receives uncompressed - or lossless compressed images yet is requested to use a profile that requires - lossy compression, or - + if it receives uncompressed or lossless compressed images yet is requested to use a profile that requires lossy compression, or - if Allow Media Splitting - (2200,0007) is NO, and the request would otherwise need to be split across - media. - + if Allow Media Splitting (2200,0007) is NO, and the request would otherwise need to be split across media. - If Allow Lossy Compression - (2200,000F) has a value of YES but the requested profile does not permit lossy - compression, lossy compression shall not be performed. - - The level of compression is at the - SCP's discretion. - - The SCP shall not decompress and - recompress already lossy compressed images, but may use images that have already been - lossy compressed. - - The SCP is never required to - perform lossy compression. - - If Allow Lossy Compression - (2200,000F) has a value of NO, the SCP is not allowed to perform lossy compression. If - Allow Lossy Compression (2200,000F) has a value of NO and the requested profile requires - lossy compression, an error shall be returned. - + If Allow Lossy Compression (2200,000F) has a value of YES but the requested profile does not permit lossy compression, lossy compression shall not be performed. + The level of compression is at the SCP's discretion. + The SCP shall not decompress and recompress already lossy compressed images, but may use images that have already been lossy compressed. + The SCP is never required to perform lossy compression. + If Allow Lossy Compression (2200,000F) has a value of NO, the SCP is not allowed to perform lossy compression. If Allow Lossy Compression (2200,000F) has a value of NO and the requested profile requires lossy compression, an error shall be returned.
Service Class User Behavior - The SCU shall use the N-CREATE - primitive to inform the SCP that a new media creation request has been placed and to convey - the proprieties of this request. The request proprieties (e.g., the set of SOP Instances - that the creating interchange media shall contain) are referenced in the IOD Attributes as - specified in. - - Upon receipt of a successful N-CREATE - Response Status Code from the SCP, the SCU now knows that the SCP has received the N-CREATE - request and a new media creation request has been created. - - Upon receipt of a failure N-CREATE - Response Status Code from the SCP, the SCU now knows that the SCP will not process the - request. The actions taken by the SCU upon receiving the status is beyond the scope of this - Standard. - - At any time after receipt of the - N-CREATE-Response, the SCU may release the association on which it sent the - N-CREATE-Request. - + The SCU shall use the N-CREATE primitive to inform the SCP that a new media creation request has been placed and to convey the proprieties of this request. The request proprieties (e.g., the set of SOP Instances that the creating interchange media shall contain) are referenced in the IOD Attributes as specified in . + Upon receipt of a successful N-CREATE Response Status Code from the SCP, the SCU now knows that the SCP has received the N-CREATE request and a new media creation request has been created. + Upon receipt of a failure N-CREATE Response Status Code from the SCP, the SCU now knows that the SCP will not process the request. The actions taken by the SCU upon receiving the status is beyond the scope of this Standard. + At any time after receipt of the N-CREATE-Response, the SCU may release the association on which it sent the N-CREATE-Request. - An N-GET of the corresponding of - the Media Creation Management SOP Class may be performed on the same or subsequent - associations. - + An N-GET of the corresponding of the Media Creation Management SOP Class may be performed on the same or subsequent associations.
Service Class Provider Behavior - Upon receipt of the N-CREATE request, - the SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code - applicable to the associated request. A success status conveys that the SCP has successfully - received the N-CREATE request. - - Warning statuses shall not be - returned. - - Any other status (i.e., a failure - status) conveys that the SCP is not processing the media creation request. - + Upon receipt of the N-CREATE request, the SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request. A success status conveys that the SCP has successfully received the N-CREATE request. + Warning statuses shall not be returned. + Any other status (i.e., a failure status) conveys that the SCP is not processing the media creation request. - It is not specified by the - Standard what checks the SCP shall accomplish after the N-CREATE request - primitive reception and before returning the N-CREATE response. Implementations - are discouraged from performing extended validation of the contents of the - N-CREATE request, such as availability of the referenced Composite SOP - Instances, support for the requested profiles, etc. In case of N-CREATE failure, - the SCU would not be able to perform an N-GET to determine the detailed reasons - for failure, and allow operators to apply suitable correction actions to make - the request processable (e.g., resending any missing Composite SOP Instances). - Such checks are better deferred until after receipt of the N-ACTION request, - after which an N-GET may be performed. - + It is not specified by the Standard what checks the SCP shall accomplish after the N-CREATE request primitive reception and before returning the N-CREATE response. Implementations are discouraged from performing extended validation of the contents of the N-CREATE request, such as availability of the referenced Composite SOP Instances, support for the requested profiles, etc. In case of N-CREATE failure, the SCU would not be able to perform an N-GET to determine the detailed reasons for failure, and allow operators to apply suitable correction actions to make the request processable (e.g., resending any missing Composite SOP Instances). Such checks are better deferred until after receipt of the N-ACTION request, after which an N-GET may be performed. - The Standard does not - require the SCP to queue multiple requests, though implementations are - encouraged to do so. As a consequence, a new request before a previous request - has been completed may fail immediately, or may return a successful response and - be queued. The size of any such queue is beyond the scope of the Standard. - + The Standard does not require the SCP to queue multiple requests, though implementations are encouraged to do so. As a consequence, a new request before a previous request has been completed may fail immediately, or may return a successful response and be queued. The size of any such queue is beyond the scope of the Standard. - How long the instance of - the Media Creation Management SOP Class persists once the Execution Status - (2100,0020) has been set to IDLE is beyond the scope of the Standard. - + How long the instance of the Media Creation Management SOP Class persists once the Execution Status (2100,0020) has been set to IDLE is beyond the scope of the Standard. - The N-CREATE implicitly creates the - Execution Status (2100,0020) and Execution Status Info (2100,0030) Attributes, which may - subsequently be retrieved by an N-GET. - + The N-CREATE implicitly creates the Execution Status (2100,0020) and Execution Status Info (2100,0030) Attributes, which may subsequently be retrieved by an N-GET.
Status Codes. - - defines the specific status code values that might be returned in a N-CREATE response. See - - for general response status codes. - + defines the specific status code values that might be returned in a N-CREATE response. See for general response status codes. @@ -39873,9 +28140,7 @@ Failure
SOP Class Status Values
- Failed: An Initiate - Media Creation action has already been received for this SOP Instance. - + Failed: An Initiate Media Creation action has already been received for this SOP Instance. A510 @@ -39887,17 +28152,10 @@
Initiate Media Creation - The Initiate Media Creation operation - allows an SCU to request an SCP to create Interchange Media according to an already created - Media Creation Management SOP Instance. An SCP shall use this operation to schedule the creation - of Interchange Media. This operation shall be invoked through the N-ACTION primitive. - + The Initiate Media Creation operation allows an SCU to request an SCP to create Interchange Media according to an already created Media Creation Management SOP Instance. An SCP shall use this operation to schedule the creation of Interchange Media. This operation shall be invoked through the N-ACTION primitive.
Action Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information - as specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in . @@ -39915,18 +28173,14 @@ Tag @@ -39959,115 +28212,55 @@
Media Creation Request - Action Information
- Requirement Type - SCU/SCP - + Requirement Type SCU/SCP
- Initiate Media - Creation - + Initiate Media Creation 1 @@ -39950,8 +28204,7 @@ 3/3 - See - + See
Priority - The Request Priority (2200,0020), - if present, may be used by the SCP to prioritize a higher priority request over other - pending lower priority requests. - + The Request Priority (2200,0020), if present, may be used by the SCP to prioritize a higher priority request over other pending lower priority requests.
Service Class User Behavior - The SCU shall use the N-ACTION - primitive to request the SCP to create Interchange Media according to an already created - Media Creation Management SOP Instance. Action Information is specified in Table S. - 3.2.2.1-1. - - Upon receipt of a successful N-ACTION - Response Status Code from the SCP, the SCU now knows that the SCP has received the N-ACTION - Initiate Media Creation request and will process the request. - - Upon receipt of a failure N-ACTION - Response Status Code from the SCP, the SCU now knows that the SCP will not process the - Initiate Media Creation request. The actions taken by the SCU upon receiving the status is - beyond the scope of this Standard. - - At any time after receipt of the - N-ACTION-Response, the SCU may release the association on which it sent the - N-ACTION-Request. - + The SCU shall use the N-ACTION primitive to request the SCP to create Interchange Media according to an already created Media Creation Management SOP Instance. Action Information is specified in Table S. 3.2.2.1-1. + Upon receipt of a successful N-ACTION Response Status Code from the SCP, the SCU now knows that the SCP has received the N-ACTION Initiate Media Creation request and will process the request. + Upon receipt of a failure N-ACTION Response Status Code from the SCP, the SCU now knows that the SCP will not process the Initiate Media Creation request. The actions taken by the SCU upon receiving the status is beyond the scope of this Standard. + At any time after receipt of the N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. - An N-GET of the - corresponding of the Media Creation Management SOP Class may be performed on the - same or subsequent associations. - + An N-GET of the corresponding of the Media Creation Management SOP Class may be performed on the same or subsequent associations. - The duration for which the - SOP Instance UID of an instance of the Media Creation Management SOP Class - remains active once the request has been completed or has failed is - implementation dependent, but should be sufficiently long to allow an SCU to - determine the ultimate outcome of the request. - + The duration for which the SOP Instance UID of an instance of the Media Creation Management SOP Class remains active once the request has been completed or has failed is implementation dependent, but should be sufficiently long to allow an SCU to determine the ultimate outcome of the request.
Service Class Provider Behavior - Upon receipt of the N-ACTION Initiate - Media Creation request, the SCP shall return, via the N-ACTION response primitive, the - N-ACTION Response Status Code applicable to the associated request. A success status conveys - that the SCP has successfully scheduled the request. - + Upon receipt of the N-ACTION Initiate Media Creation request, the SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated request. A success status conveys that the SCP has successfully scheduled the request. - The extent of validation of - the contents of the request, the availability of the referenced Composite SOP - Instances, support for the requested profiles and other checks that may - determine the ultimate success or failure of the request are not specified by - the Standard. In particular, a request may be immediately accepted successfully, - but subsequently fail for some reason, or the N-ACTION response primitive may - contain a status that reflects a more thorough (and prolonged) check. - + The extent of validation of the contents of the request, the availability of the referenced Composite SOP Instances, support for the requested profiles and other checks that may determine the ultimate success or failure of the request are not specified by the Standard. In particular, a request may be immediately accepted successfully, but subsequently fail for some reason, or the N-ACTION response primitive may contain a status that reflects a more thorough (and prolonged) check. - How long any Composite - Instances that have been transferred via the Storage Service Class to the SCP - for the purpose of a Media Creation Request persist, is beyond the scope of the - Standard. The Preserve Composite Instances After Media Creation (2200,000A) flag - is provided as a hint only. Even if this flag is set, a subsequent request - referencing some or all of the same instances may fail if the SCP had reason to - flush its cache of instances in the interim, and the SCU may need to be prepared - to re-send them. - + How long any Composite Instances that have been transferred via the Storage Service Class to the SCP for the purpose of a Media Creation Request persist, is beyond the scope of the Standard. The Preserve Composite Instances After Media Creation (2200,000A) flag is provided as a hint only. Even if this flag is set, a subsequent request referencing some or all of the same instances may fail if the SCP had reason to flush its cache of instances in the interim, and the SCU may need to be prepared to re-send them. - How long the instance of - the Media Creation Management SOP Class persists once the Execution Status - (2100,0020) has been set to DONE or FAILED is beyond the scope of the Standard. - + How long the instance of the Media Creation Management SOP Class persists once the Execution Status (2100,0020) has been set to DONE or FAILED is beyond the scope of the Standard. - The N-ACTION implicitly creates or - updates the Execution Status (2100,0020), Execution Status Info (2100,0030), Total Number of - Pieces of Media Created (2200,000B), Failed SOP Sequence (0008,1198) and Referenced Storage - Media Sequence (2200,000D) Attributes, which may subsequently be retrieved by an N-GET. - + The N-ACTION implicitly creates or updates the Execution Status (2100,0020), Execution Status Info (2100,0030), Total Number of Pieces of Media Created (2200,000B), Failed SOP Sequence (0008,1198) and Referenced Storage Media Sequence (2200,000D) Attributes, which may subsequently be retrieved by an N-GET.
Status Codes - There are no specific status codes. See - - for response status codes. - + There are no specific status codes. See for response status codes.
Cancel Media Creation - The Cancel Media Creation operation allows - an SCU to request an SCP to cancel a media creation request, whether or not it has begun to be - processed. This operation shall be invoked through the N-ACTION primitive. - + The Cancel Media Creation operation allows an SCU to request an SCP to cancel a media creation request, whether or not it has begun to be processed. This operation shall be invoked through the N-ACTION primitive.
Action Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information - as specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in . @@ -40085,17 +28278,14 @@ Tag
Media Creation Request - Action Information
- Requirement Type - SCU/SCP - + Requirement Type SCU/SCP
- Cancel Media Creation - + Cancel Media Creation 2 @@ -40109,58 +28299,25 @@
Service Class User Behavior - The SCU shall use the N-ACTION - primitive to request the SCP to cancel the media creation request corresponding to the - Affected SOP Instance UID in the N-ACTION request primitive, whether or not it has been - initiated with an N-ACTION Initiate Media Creation request, and whether or not it has begun - to be processed (i.e., is pending or in progress). - - Upon receipt of a successful N-ACTION - Response Status Code from the SCP, the SCU knows that the SCP has received the N-ACTION - Cancel Media Creation request, has canceled any pending or in progress media creation, and - deleted the Media Creation Management SOP Instance. - + The SCU shall use the N-ACTION primitive to request the SCP to cancel the media creation request corresponding to the Affected SOP Instance UID in the N-ACTION request primitive, whether or not it has been initiated with an N-ACTION Initiate Media Creation request, and whether or not it has begun to be processed (i.e., is pending or in progress). + Upon receipt of a successful N-ACTION Response Status Code from the SCP, the SCU knows that the SCP has received the N-ACTION Cancel Media Creation request, has canceled any pending or in progress media creation, and deleted the Media Creation Management SOP Instance. - Successful cancellation implies - that a subsequent N-GET of the corresponding Media Creation Management SOP Instance - would fail. - + Successful cancellation implies that a subsequent N-GET of the corresponding Media Creation Management SOP Instance would fail. - Upon receipt of a failure N-ACTION - Response Status Code from the SCP, the SCU knows that the SCP will not process the Cancel - Media Creation request. The actions taken by the SCU upon receiving the status is beyond the - scope of this Standard. - + Upon receipt of a failure N-ACTION Response Status Code from the SCP, the SCU knows that the SCP will not process the Cancel Media Creation request. The actions taken by the SCU upon receiving the status is beyond the scope of this Standard. - Cancellation failure implies that - media creation has already completed (successfully or not), or will proceed. The status - of the media creation request may still be obtained with an N-GET, unless the reason for - failure was that the SOP Instance did not exist. - + Cancellation failure implies that media creation has already completed (successfully or not), or will proceed. The status of the media creation request may still be obtained with an N-GET, unless the reason for failure was that the SOP Instance did not exist.
Service Class Provider Behavior - Upon receipt of the N-ACTION Cancel - Media Creation request, the SCP shall return, via the N-ACTION response primitive, the - N-ACTION Response Status Code applicable to the associated request. A success status conveys - that the SCP has successfully canceled the request. - - A failure status conveys that the SCP - has failed to cancel the request, in which case the Execution Status (2100,0020), Execution - Status Info (2100,0030), Total Number of Pieces of Media Created (2200,000B), Failed SOP - Sequence (0008,1198) and Referenced Storage Media Sequence (2200,000D) Attributes may - subsequently be retrieved by an N-GET. - + Upon receipt of the N-ACTION Cancel Media Creation request, the SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated request. A success status conveys that the SCP has successfully canceled the request. + A failure status conveys that the SCP has failed to cancel the request, in which case the Execution Status (2100,0020), Execution Status Info (2100,0030), Total Number of Pieces of Media Created (2200,000B), Failed SOP Sequence (0008,1198) and Referenced Storage Media Sequence (2200,000D) Attributes may subsequently be retrieved by an N-GET.
Status Codes - - defines the specific status code values that might be returned in a N-ACTION response. See - - for general response status codes. - + defines the specific status code values that might be returned in a N-ACTION response. See for general response status codes. @@ -40182,9 +28339,7 @@ Failure
Response Statuses
- Failed: Media creation - request already completed. - + Failed: Media creation request already completed. C201 @@ -40192,9 +28347,7 @@
- Failed: Media creation - request already in progress and cannot be interrupted. - + Failed: Media creation request already in progress and cannot be interrupted. C202 @@ -40202,9 +28355,7 @@
- Failed: Cancellation - denied for unspecified reason. - + Failed: Cancellation denied for unspecified reason. C203 @@ -40216,19 +28367,10 @@
Get Media Creation Result - The Get Media Creation Result operation - allows an SCU to request of an SCP the status of a media creation request. This operation shall - be invoked through the N-GET primitive used in conjunction with the appropriate Media Creation - Management SOP Instance corresponding to the creation request. - + The Get Media Creation Result operation allows an SCU to request of an SCP the status of a media creation request. This operation shall be invoked through the N-GET primitive used in conjunction with the appropriate Media Creation Management SOP Instance corresponding to the creation request.
Attributes - The Application Entity that claims - conformance to this SOP Class as an SCU may choose to interpret the Attributes maintained by - the SCP that the SCU receives via the operations of the SOP Class. The Application Entity - that claims conformance as an SCP to this SOP Class shall support the Attributes specified - in. - + The Application Entity that claims conformance to this SOP Class as an SCU may choose to interpret the Attributes maintained by the SCP that the SCU receives via the operations of the SOP Class. The Application Entity that claims conformance as an SCP to this SOP Class shall support the Attributes specified in . @@ -40240,27 +28382,21 @@ Tag @@ -40276,8 +28412,7 @@ @@ -40343,65 +28471,25 @@
Service Class User - The SCU shall specify in the N-GET - request primitive the UID of the Media Creation Management SOP Instance for which Attribute - Values are to be returned. The SCU shall be permitted to request that Attribute Values be - returned for any Media Creation Management SOP Class Attribute specified in. Additionally, values may be - requested for optional Media Creation Management Module Attributes. - - The SCU shall specify the list of Media - Creation Management SOP Class Attributes for which the Attribute Values are to be returned. - The encoding rules for this list are specified in the N-GET request primitive specified in - . - - In an N-GET operation, Sequence - Attributes can only be requested in their entirety, and only the top level Sequence - Attribute can be included in the request. - - The SCU shall be capable of receiving - all requested Attribute Values provided by the SCP in response to the N-GET indication - primitive. The SCU may request Attribute Values for optional Attributes that are not - maintained by the SCP. In such a case the SCU shall function properly regardless of whether - the SCP returns values for those Attributes or not. This Service Class Specification places - no requirements on what the SCU shall do as a result of receiving this information. - + The SCU shall specify in the N-GET request primitive the UID of the Media Creation Management SOP Instance for which Attribute Values are to be returned. The SCU shall be permitted to request that Attribute Values be returned for any Media Creation Management SOP Class Attribute specified in . Additionally, values may be requested for optional Media Creation Management Module Attributes. + The SCU shall specify the list of Media Creation Management SOP Class Attributes for which the Attribute Values are to be returned. The encoding rules for this list are specified in the N-GET request primitive specified in . + In an N-GET operation, Sequence Attributes can only be requested in their entirety, and only the top level Sequence Attribute can be included in the request. + The SCU shall be capable of receiving all requested Attribute Values provided by the SCP in response to the N-GET indication primitive. The SCU may request Attribute Values for optional Attributes that are not maintained by the SCP. In such a case the SCU shall function properly regardless of whether the SCP returns values for those Attributes or not. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information. - In order to interpret accurately - the character set used for Attribute Values returned, it is recommended that the - Attribute Value for Specific Character Set (0008,0005) be requested in the N-GET request - primitive. - + In order to interpret accurately the character set used for Attribute Values returned, it is recommended that the Attribute Value for Specific Character Set (0008,0005) be requested in the N-GET request primitive.
Service Class Provider - This operation allows the SCU to - request from the SCP, selected Attribute Values for a specific Media Creation Management SOP - Instance. This operation shall be invoked through the use of the DIMSE N-GET Service used in - conjunction with the appropriate Media Creation Management SOP Instance. - - The SCP shall return, via the N-GET - response primitive, the N-GET Response Status Code applicable to the associated request. - Contingent on the N-GET Response Status, the SCP shall return, via the N-GET Response - Primitive, Attribute Values for all requested Attributes maintained by the SCP (see). The SCP shall not return - Data Elements for optional Attributes that are not maintained by the SCP. - - The SCP shall return the entire content - of a Sequence if a Sequence Attribute is requested. - + This operation allows the SCU to request from the SCP, selected Attribute Values for a specific Media Creation Management SOP Instance. This operation shall be invoked through the use of the DIMSE N-GET Service used in conjunction with the appropriate Media Creation Management SOP Instance. + The SCP shall return, via the N-GET response primitive, the N-GET Response Status Code applicable to the associated request. Contingent on the N-GET Response Status, the SCP shall return, via the N-GET Response Primitive, Attribute Values for all requested Attributes maintained by the SCP (see ). The SCP shall not return Data Elements for optional Attributes that are not maintained by the SCP. + The SCP shall return the entire content of a Sequence if a Sequence Attribute is requested.
Status Codes - - defines the specific status code values that might be returned in a N-GET response. - - See - - for general response status codes. - + defines the specific status code values that might be returned in a N-GET response. + See for general response status codes.
Media Creation Management SOP Class N-GET Attributes
- Requirement Type - (SCU/SCP) - + Requirement Type (SCU/SCP)
- Specific Character - Set - + Specific Character Set (0008,0005) 3/1C - (Required if expanded - or replacement character set is used) - + (Required if expanded or replacement character set is used)
- Execution Status Info - + Execution Status Info (2100,0030) @@ -40288,9 +28423,7 @@
- Total Number of Pieces - of Media Created - + Total Number of Pieces of Media Created (2200,000B) @@ -40301,8 +28434,7 @@
- Failed SOP Sequence - + Failed SOP Sequence (0008,1198) @@ -40313,9 +28445,7 @@
- Referenced Storage - Media Sequence - + Referenced Storage Media Sequence (2200,000D) @@ -40327,9 +28457,7 @@
- All Other Attributes of the - + All Other Attributes of the
@@ -40413,8 +28501,7 @@ Further Meaning @@ -40424,9 +28511,7 @@ Warning
Response Statuses
- Response Status Codes - + Response Status Codes
- Requested optional - Attributes are not supported - + Requested optional Attributes are not supported 0001 @@ -40439,220 +28524,108 @@
Media Creation Management SOP Class UID - The Media Creation Management SOP Class shall - be uniquely identified by the Media Creation Management SOP Class UID, which shall have the value - "1.2.840.10008.5.1.1.33". - + The Media Creation Management SOP Class shall be uniquely identified by the Media Creation Management SOP Class UID, which shall have the value "1.2.840.10008.5.1.1.33".
Conformance Requirements - Implementations claiming Standard SOP Class - Conformance to the Media Creation Management SOP Class shall be conformant as described in this Section - and shall include within their Conformance Statement information as described in this Section and - sub-Sections. - - An implementation may claim conformance to this SOP - Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in. - + Implementations claiming Standard SOP Class Conformance to the Media Creation Management SOP Class shall be conformant as described in this Section and shall include within their Conformance Statement information as described in this Section and sub-Sections. + An implementation may claim conformance to this SOP Class as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to this - SOP Class as an SCU shall meet conformance requirements for - + An implementation that is conformant to this SOP Class as an SCU shall meet conformance requirements for - the operations and actions that it - invokes - + the operations and actions that it invokes - The mechanisms used by the SCU to transfer SOP - Instances to the SCP using the Storage Service Class prior to initiating a request operation shall - also be documented, and in particular the Transfer Syntaxes that may be proposed. - + The mechanisms used by the SCU to transfer SOP Instances to the SCP using the Storage Service Class prior to initiating a request operation shall also be documented, and in particular the Transfer Syntaxes that may be proposed.
Operations - The SCU shall document in the Conformance - Statement the actions and behavior that cause the SCU to generate an N-CREATE primitive (Create - Media Creation Request), an N-ACTION primitive (Initiate Media Creation and Cancel Media - Creation) or an N-GET primitive (Get Media Creation Result). - - The SCU shall specify the SOP Class UIDs - for which it may request media creation. - - The SCU shall specify the Media Application - Profiles for which it may request media creation. - - The SCU shall specify if it supports the - optional Storage Media File-Set ID & UID Attributes in the N-CREATE. - - The SCU shall specify if it supports the - optional Icon Image Sequence Attributes in the N-CREATE. - - The SCU shall describe its use of expanded - or replacement character sets, both in the N-CREATE, the N-GET and in its use of the Storage - Service Class for composite instances. - - The SCU shall specify whether or not it - retries failed requests. - + The SCU shall document in the Conformance Statement the actions and behavior that cause the SCU to generate an N-CREATE primitive (Create Media Creation Request), an N-ACTION primitive (Initiate Media Creation and Cancel Media Creation) or an N-GET primitive (Get Media Creation Result). + The SCU shall specify the SOP Class UIDs for which it may request media creation. + The SCU shall specify the Media Application Profiles for which it may request media creation. + The SCU shall specify if it supports the optional Storage Media File-Set ID & UID Attributes in the N-CREATE. + The SCU shall specify if it supports the optional Icon Image Sequence Attributes in the N-CREATE. + The SCU shall describe its use of expanded or replacement character sets, both in the N-CREATE, the N-GET and in its use of the Storage Service Class for composite instances. + The SCU shall specify whether or not it retries failed requests. - This allows the reader of a Conformance - Statement to determine whether or not human intervention will be needed in the event of - transient failures, or whether the SCU may be able to recover automatically. - + This allows the reader of a Conformance Statement to determine whether or not human intervention will be needed in the event of transient failures, or whether the SCU may be able to recover automatically. - The Conformance Statement shall be - formatted as defined in - + The Conformance Statement shall be formatted as defined in
SCP Conformance - An implementation that is conformant to this - SOP Class as an SCP shall meet conformance requirements for - + An implementation that is conformant to this SOP Class as an SCP shall meet conformance requirements for - the operations and actions that it - performs - + the operations and actions that it performs - The Storage Service Class mechanisms accepted - by the SCP prior to receiving a request operation shall also be documented, and in particular the - Transfer Syntaxes that may be accepted. - + The Storage Service Class mechanisms accepted by the SCP prior to receiving a request operation shall also be documented, and in particular the Transfer Syntaxes that may be accepted.
Operations - The SCP shall document in the Conformance - Statement the behavior and actions of the SCP upon receiving the N-CREATE primitive (Create - Media Creation Request), N-ACTION primitive (Initiate Media Creation and Cancel Media Creation) - or the N-GET primitive (Get Media Creation Result). - - The SCP shall specify the SOP Class UIDs - for which it will accept media creation requests. - - The SCP shall specify the Media Application - Profiles for which it will accept media creation requests, and what default profiles it will use - in the event that they are not specified by the SCU. - + The SCP shall document in the Conformance Statement the behavior and actions of the SCP upon receiving the N-CREATE primitive (Create Media Creation Request), N-ACTION primitive (Initiate Media Creation and Cancel Media Creation) or the N-GET primitive (Get Media Creation Result). + The SCP shall specify the SOP Class UIDs for which it will accept media creation requests. + The SCP shall specify the Media Application Profiles for which it will accept media creation requests, and what default profiles it will use in the event that they are not specified by the SCU. - The forms of media that can be created - are implicit in the list of Media Application Profiles supported, each of which is - media-specific. - + The forms of media that can be created are implicit in the list of Media Application Profiles supported, each of which is media-specific. - The SCP shall specify whether or not it - supports creation of optional Icon Image Sequence Attributes in the DICOMDIR if none are - supplied by the SCU. - - The SCP shall specify the manner of use of - label information, and in particular which: - + The SCP shall specify whether or not it supports creation of optional Icon Image Sequence Attributes in the DICOMDIR if none are supplied by the SCU. + The SCP shall specify the manner of use of label information, and in particular which: - Attributes are extracted from the - Composite Instances when so instructed - + Attributes are extracted from the Composite Instances when so instructed - barcode symbologies - if any - are - supported - + barcode symbologies - if any - are supported - The SCP shall describe its use of expanded - or replacement character sets, both in the N-CREATE, the N-GET and in its extraction of - information from the Composite Instances for incorporation in the DICOMDIR and on the media - label. The SCP shall describe its use of the Attributes both in the N-CREATE, and N-ACTION and - the Composite Instances to create the media label. - - The SCP shall specify if and how it - supports the following optional Attributes in the N-CREATE and N-ACTION: - + The SCP shall describe its use of expanded or replacement character sets, both in the N-CREATE, the N-GET and in its extraction of information from the Composite Instances for incorporation in the DICOMDIR and on the media label. The SCP shall describe its use of the Attributes both in the N-CREATE, and N-ACTION and the Composite Instances to create the media label. + The SCP shall specify if and how it supports the following optional Attributes in the N-CREATE and N-ACTION: - Storage Media File-Set ID - (0088,0130) & Storage Media File-Set UID (0088,0140) - + Storage Media File-Set ID (0088,0130) & Storage Media File-Set UID (0088,0140) - Media Disposition (2200,0004) - + Media Disposition (2200,0004) Priority (2000,0020) - Preserve Composite Instances After - Media Creation (2200,000A) - + Preserve Composite Instances After Media Creation (2200,000A) - The SCP shall specify the duration of - persistence of received Composite Instances after a request has been processed successfully or - unsuccessfully. - - The SCP shall specify how long it will - maintain: - + The SCP shall specify the duration of persistence of received Composite Instances after a request has been processed successfully or unsuccessfully. + The SCP shall specify how long it will maintain: - the result of the creation of media - after the request has succeeded or failed - + the result of the creation of media after the request has succeeded or failed - the Media Creation Management - Instances whose status is IDLE. - + the Media Creation Management Instances whose status is IDLE. - The SCP shall specify the action taken when - a permanent failure (e.g., a media writing failure) or a transient failure (e.g., no empty media - available) occurs, and their relationship with the media creation request status transaction. - + The SCP shall specify the action taken when a permanent failure (e.g., a media writing failure) or a transient failure (e.g., no empty media available) occurs, and their relationship with the media creation request status transaction. - For example, how many times the SCP - will retry writing a new piece of media before setting the Execution Status (2100,0020) to - FAILURE, how many media creation requests the SCP is able to queue, the SCP behavior when - the request queue, if any, is full. - + For example, how many times the SCP will retry writing a new piece of media before setting the Execution Status (2100,0020) to FAILURE, how many media creation requests the SCP is able to queue, the SCP behavior when the request queue, if any, is full. - The SCP shall specify if it is able to - split a media creation request over more than one piece of media, if the file-set doesn't fit on - one. - - The SCP shall specify if it is able to add - to the created media Non-DICOM objects (e.g., html files, JPEG images), how these objects are - organized, and how it interprets the Include Non-DICOM Objects (2200,0008) Attribute. - - The SCP shall specify if it is able to add - to the created media DICOM display applications, and how it interprets the Include Display - Application (2200,0009) Attribute. - - The Conformance Statement shall be - formatted as defined in. - + The SCP shall specify if it is able to split a media creation request over more than one piece of media, if the file-set doesn't fit on one. + The SCP shall specify if it is able to add to the created media Non-DICOM objects (e.g., html files, JPEG images), how these objects are organized, and how it interprets the Include Non-DICOM Objects (2200,0008) Attribute. + The SCP shall specify if it is able to add to the created media DICOM display applications, and how it interprets the Include Display Application (2200,0009) Attribute. + The Conformance Statement shall be formatted as defined in .
Hanging Protocol Storage Service Class - See. - + See . - The requirements of this section have been - consolidated into the Non-Patient Object Storage Service Class (see). - + The requirements of this section have been consolidated into the Non-Patient Object Storage Service Class (see ). @@ -40661,125 +28634,65 @@ Overview
Scope - The Hanging Protocol Query/Retrieve Service - Class defines an application-level class-of-service that facilitates access to Hanging Protocol - composite objects. It provides query and retrieve/transfer capabilities similar to the Basic - Worklist Management Service Class and Query/Retrieve Service Class. - + The Hanging Protocol Query/Retrieve Service Class defines an application-level class-of-service that facilitates access to Hanging Protocol composite objects. It provides query and retrieve/transfer capabilities similar to the Basic Worklist Management Service Class and Query/Retrieve Service Class.
Conventions - See Conventions for the Basic Worklist - Management Service (K.1.2). - + See Conventions for the Basic Worklist Management Service (K.1.2).
Query/Retrieve Information Model - In order to serve as an SCP of the Hanging - Protocol Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a - number of Hanging Protocol composite SOP Instances. The information is organized into a Hanging - Protocol Information Model. - + In order to serve as an SCP of the Hanging Protocol Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of Hanging Protocol composite SOP Instances. The information is organized into a Hanging Protocol Information Model.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Hanging Protocol Query/Retrieve Service Class with one serving in the SCU role and one serving in - the SCP role. SOP Classes of the Hanging Protocol Query/Retrieve Service Class are implemented using - the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in. - - The semantics of the C-FIND and C-GET services - are the same as those defined in the Service Definition of the Basic Worklist Management Service - Class. - - The semantics of the C-MOVE service are the - same as those defined in the Service Definition of the Query/Retrieve Service Class, with the - exception that there is only one level of retrieval. - + Two peer DICOM AEs implement a SOP Class of the Hanging Protocol Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Hanging Protocol Query/Retrieve Service Class are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in . + The semantics of the C-FIND and C-GET services are the same as those defined in the Service Definition of the Basic Worklist Management Service Class. + The semantics of the C-MOVE service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval.
Hanging Protocol Information Model Definition - The Hanging Protocol Information Model is - identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of - both an Information Model and a DIMSE-C Service Group. - - The Hanging Protocol Information Model is defined, - with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined - in the Worklist Information Model Definition of the Basic Worklist Management Service. - + The Hanging Protocol Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + The Hanging Protocol Information Model is defined, with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model Definition of the Basic Worklist Management Service.
Hanging Protocol Information Model - The Hanging Protocol Information Model is based - upon a one level entity: - + The Hanging Protocol Information Model is based upon a one level entity: Hanging Protocol object instance - The Hanging Protocol object instance contains - Attributes associated with the Hanging Protocol object IE of the Composite IODs as defined in. - + The Hanging Protocol object instance contains Attributes associated with the Hanging Protocol object IE of the Composite IODs as defined in .
DIMSE-C Service Groups
C-FIND Operation - See the C-FIND Operation definition for the - Basic Worklist Management Service Class (K.4.1), and substitute "Hanging Protocol" for "Worklist. - The "Worklist" Search Method shall be used. - - The SOP Class UID identifies the Hanging - Protocol Information Model against which the C-FIND is to be performed. The Key Attributes and - values allowable for the query are defined in the SOP Class definition for the Hanging Protocol - Information Model. - + See the C-FIND Operation definition for the Basic Worklist Management Service Class (K.4.1), and substitute "Hanging Protocol" for "Worklist. The "Worklist" Search Method shall be used. + The SOP Class UID identifies the Hanging Protocol Information Model against which the C-FIND is to be performed. The Key Attributes and values allowable for the query are defined in the SOP Class definition for the Hanging Protocol Information Model.
C-MOVE Operation - See the C-MOVE Operation definition for the - Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the - Hanging Protocol Query/Retrieve Service Class. - - Query/Retrieve Level (0008,0052) is not - relevant to the Hanging Protocol Query/Retrieve Service Class, and therefore shall not be present in - the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID - (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-MOVE Operation definition for the Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the Hanging Protocol Query/Retrieve Service Class. + Query/Retrieve Level (0008,0052) is not relevant to the Hanging Protocol Query/Retrieve Service Class, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
C-GET Operation - See the C-GET Operation definition for the - Query/Retrieve Service Class (C.4.3). No Extended Behavior or Relational-Retrieve is defined for the - Hanging Protocol Query/Retrieve Service Class. - - Query/Retrieve Level (0008,0052) is not - relevant to the Hanging Protocol Query/Retrieve Service Class, and therefore shall not be present in - the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID - (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-GET Operation definition for the Query/Retrieve Service Class (C.4.3). No Extended Behavior or Relational-Retrieve is defined for the Hanging Protocol Query/Retrieve Service Class. + Query/Retrieve Level (0008,0052) is not relevant to the Hanging Protocol Query/Retrieve Service Class, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
Association Negotiation - See the Association Negotiation definition for the - Basic Worklist Management Service Class (K.5). - + See the Association Negotiation definition for the Basic Worklist Management Service Class (K.5).
SOP Class Definitions @@ -40787,10 +28700,7 @@ Hanging Protocol Information Model
E/R Model - The Hanging Protocol Information Model - consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Hanging Protocol Instance. - + The Hanging Protocol Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Hanging Protocol Instance.
Hanging Protocol Information Model E-R Diagram @@ -40806,9 +28716,7 @@
Hanging Protocol Attributes - - defines the Attributes of the Hanging Protocol Information Model: - + defines the Attributes of the Hanging Protocol Information Model: @@ -40826,8 +28734,7 @@ Return Key Type @@ -40841,8 +28748,7 @@ @@ -40900,8 +28802,7 @@ @@ -41023,16 +28910,12 @@ 2 @@ -41072,16 +28952,12 @@ 2
Attributes for the Hanging Protocol Information Model
- Remark / Matching Type - + Remark / Matching Type
- Specific Character Set - + Specific Character Set (0008,0005) @@ -40854,11 +28760,7 @@ 1C - This Attribute is required - if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- Hanging Protocol Name - + Hanging Protocol Name (0072,0002) @@ -40913,16 +28814,12 @@ 1 - This Attribute shall be - retrieved with Single Value, Wild Card or Universal matching. - + This Attribute shall be retrieved with Single Value, Wild Card or Universal matching.
- Hanging Protocol - Description - + Hanging Protocol Description (0072,0004) @@ -40937,8 +28834,7 @@
- Hanging Protocol Level - + Hanging Protocol Level (0072,0006) @@ -40950,15 +28846,12 @@ 1 - This Attribute shall be - retrieved with Single Value or Universal matching. - + This Attribute shall be retrieved with Single Value or Universal matching.
- Hanging Protocol Creator - + Hanging Protocol Creator (0072,0008) @@ -40973,9 +28866,7 @@
- Hanging Protocol Creation - DateTime - + Hanging Protocol Creation DateTime (0072,000A) @@ -40990,9 +28881,7 @@
- Hanging Protocol Definition - Sequence - + Hanging Protocol Definition Sequence (0072,000C) @@ -41004,9 +28893,7 @@ 1 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- This Attribute shall be - retrieved with Single Value or Universal matching. - + This Attribute shall be retrieved with Single Value or Universal matching.
- >Anatomic Region - Sequence - + >Anatomic Region Sequence (0008,2218) @@ -41044,18 +28927,15 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >>Include - - - +>>Include + +
- This Attribute shall be - retrieved with Single Value or Universal matching. - + This Attribute shall be retrieved with Single Value or Universal matching.
- >Procedure Code - Sequence - + >Procedure Code Sequence (0008,1032) @@ -41093,25 +28969,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >>Include - - - +>>Include + +
- >Reason for Requested - Procedure Code Sequence - + >Reason for Requested Procedure Code Sequence (0040,100A) @@ -41123,25 +28994,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >>Include - - - +>>Include + +
- Number of Priors - Referenced - + Number of Priors Referenced (0072,0014) @@ -41153,16 +29019,12 @@ 1 - This Attribute shall be - retrieved with Single Value or Universal matching. - + This Attribute shall be retrieved with Single Value or Universal matching.
- Hanging Protocol User - Identification Code Sequence - + Hanging Protocol User Identification Code Sequence (0072,000E) @@ -41174,25 +29036,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Hanging Protocol User Group - Name - + Hanging Protocol User Group Name (0072,0010) @@ -41229,9 +29086,7 @@
- Nominal Screen Definition - Sequence - + Nominal Screen Definition Sequence (0072,0102) @@ -41246,9 +29101,7 @@
- >Number of Vertical - Pixels - + >Number of Vertical Pixels (0072,0104) @@ -41263,9 +29116,7 @@
- >Number of Horizontal - Pixels - + >Number of Horizontal Pixels (0072,0106) @@ -41280,9 +29131,7 @@
- >Display Environment - Spatial Position - + >Display Environment Spatial Position (0072,0108) @@ -41297,9 +29146,7 @@
- >Screen Minimum - Grayscale Bit Depth - + >Screen Minimum Grayscale Bit Depth (0072,010A) @@ -41311,16 +29158,12 @@ 1C - Required if Screen Minimum - Color Bit Depth (0072,010C) is not present. - + Required if Screen Minimum Color Bit Depth (0072,010C) is not present.
- >Screen Minimum Color - Bit Depth - + >Screen Minimum Color Bit Depth (0072,010C) @@ -41332,16 +29175,12 @@ 1C - Required if Screen Minimum - Grayscale Bit Depth (0072,010A) is not present. - + Required if Screen Minimum Grayscale Bit Depth (0072,010A) is not present.
- >Application Maximum - Repaint Time - + >Application Maximum Repaint Time (0072,010E) @@ -41359,114 +29198,47 @@
Conformance Requirements - An implementation may conform to one of the - Hanging Protocol Information Model SOP Classes as an SCU, SCP or both. The Conformance Statement - shall be in the format defined in. - + An implementation may conform to one of the Hanging Protocol Information Model SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes shall support queries against - the Hanging Protocol Information Model using the C-FIND SCU Behavior described for the - Basic Worklist Management Service Class (see - - and). - - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCU shall state in its - Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list - these Optional Return Key Attributes. - - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCU shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) when - encoding queries and interpreting responses. - + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes shall support queries against the Hanging Protocol Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see and ). + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCU shall support - transfers against the Hanging Protocol Information Model using the C-MOVE SCU baseline - behavior described for the Query/Retrieve Service Class (see - - and). - + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCU shall support transfers against the Hanging Protocol Information Model using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
C-GET SCU Conformance - An implementation that conforms to - the Hanging Protocol Information Model - GET SOP Class as an SCU shall support transfers - against the Hanging Protocol Information Model using the C-GET SCU baseline behavior - described for the Query/Retrieve Service Class (see - - and). - + An implementation that conforms to the Hanging Protocol Information Model - GET SOP Class as an SCU shall support transfers against the Hanging Protocol Information Model using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCP shall support - queries against the Hanging Protocol Information Model using the C-FIND SCP Behavior - described for the Basic Worklist Management Service Class (see). - - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCP shall state in its - Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list - these Optional Return Key Attributes. - - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCP shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) when - interpreting queries, performing matching and encoding responses. - + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall support queries against the Hanging Protocol Information Model using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see ). + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall state in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.
C-MOVE SCP Conformance - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCP shall support - transfers against the Hanging Protocol Information Model using the C-MOVE SCP baseline - behavior described for the Query/Retrieve Service Class (see). - - An implementation that conforms to - one of the Hanging Protocol Information Model SOP Classes as an SCP, which generates - transfers using the C-MOVE operation, shall state in its Conformance Statement the - Hanging Protocol Storage Service Class SOP Class under which it shall support the - C-STORE sub-operations generated by the C-MOVE. - + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP shall support transfers against the Hanging Protocol Information Model using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see ). + An implementation that conforms to one of the Hanging Protocol Information Model SOP Classes as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement the Hanging Protocol Storage Service Class SOP Class under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - the Hanging Protocol Information Model - GET SOP Class as an SCP shall support transfers - against the Hanging Protocol Information Model using the C-GET SCP baseline behavior - described for the Query/Retrieve Service Class (see). - - An implementation that conforms to - the Hanging Protocol Information Model - GET SOP Class as an SCP, which generates - transfers using the C-GET operation, shall state in its Conformance Statement the - Hanging Protocol Storage Service Class SOP Class under which it will support the C-STORE - sub-operations generated by the C-GET. - + An implementation that conforms to the Hanging Protocol Information Model - GET SOP Class as an SCP shall support transfers against the Hanging Protocol Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class (see ). + An implementation that conforms to the Hanging Protocol Information Model - GET SOP Class as an SCP, which generates transfers using the C-GET operation, shall state in its Conformance Statement the Hanging Protocol Storage Service Class SOP Class under which it will support the C-STORE sub-operations generated by the C-GET.
SOP Classes - The SOP Classes of the Hanging Protocol - Information Model in the Hanging Protocol Query/Retrieve Service Class identify the Hanging - Protocol Information Model, and the DIMSE-C operations supported. The following Standard SOP - Classes are identified: - + The SOP Classes of the Hanging Protocol Information Model in the Hanging Protocol Query/Retrieve Service Class identify the Hanging Protocol Information Model, and the DIMSE-C operations supported. The following Standard SOP Classes are identified: @@ -41482,35 +29254,26 @@ @@ -41525,149 +29288,69 @@ Overview
Scope - The Substance Administration Query Service - Class defines an application-level class-of-service that facilitates obtaining detailed information - about substances or devices used in imaging, image-guided treatment, and related procedures. It also - facilitates obtaining approval for the administration of a specific contrast agent or drug to a - specific patient. - - This Service Class is intended as part of a - larger workflow that addresses patient safety in the imaging environment. This Service addresses - only the communication protocol that allows a point of care device (imaging modality) to interrogate - an SCP Application for information about an administered substance, or for verification of - appropriateness of the substance for the patient. The SCP Application uses patient safety related - data, such as allergies, current medications, appropriate dosages, patient condition indicated by - lab results, etc., to respond to the queries; however, the mechanism of such use is beyond the scope - of this Standard. How the point of care device uses the responses to the queries, e.g., by display - to a user, or by locking of certain device functions, is also beyond the scope of this Standard. - + The Substance Administration Query Service Class defines an application-level class-of-service that facilitates obtaining detailed information about substances or devices used in imaging, image-guided treatment, and related procedures. It also facilitates obtaining approval for the administration of a specific contrast agent or drug to a specific patient. + This Service Class is intended as part of a larger workflow that addresses patient safety in the imaging environment. This Service addresses only the communication protocol that allows a point of care device (imaging modality) to interrogate an SCP Application for information about an administered substance, or for verification of appropriateness of the substance for the patient. The SCP Application uses patient safety related data, such as allergies, current medications, appropriate dosages, patient condition indicated by lab results, etc., to respond to the queries; however, the mechanism of such use is beyond the scope of this Standard. How the point of care device uses the responses to the queries, e.g., by display to a user, or by locking of certain device functions, is also beyond the scope of this Standard. - The SCP of this Service Class is - not necessarily a clinical decision support (CDS) system, but may be a gateway system - between this DICOM Service and an HL7 or proprietary interface of a CDS system. Such - implementation design is beyond the scope of the DICOM Standard. - + The SCP of this Service Class is not necessarily a clinical decision support (CDS) system, but may be a gateway system between this DICOM Service and an HL7 or proprietary interface of a CDS system. Such implementation design is beyond the scope of the DICOM Standard. - The Service will result in a Query - response containing zero or one items. However, to facilitate implementation, the - Service uses the general query mechanism supporting multiple item responses, as used in - other DICOM query service classes. - + The Service will result in a Query response containing zero or one items. However, to facilitate implementation, the Service uses the general query mechanism supporting multiple item responses, as used in other DICOM query service classes.
Conventions - Key Attributes serve two purposes; they may be - used as Matching Key Attributes and Return Key Attributes. Matching Key Attributes may be used for - matching (criteria to be used in the C-FIND request to determine whether an entity matches the - query). Return Key Attributes may be used to specify desired return Attributes (what elements in - addition to the Matching Key Attributes have to be returned in the C-FIND response). - - Matching Key Attributes may be of Type - "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in - . - + Key Attributes serve two purposes; they may be used as Matching Key Attributes and Return Key Attributes. Matching Key Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether an entity matches the query). Return Key Attributes may be used to specify desired return Attributes (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND response). + Matching Key Attributes may be of Type "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in .
Substance Administration Query Information Model - In order to serve as a Service Class Provider - (SCP) of the Substance Administration Query Service Class, a DICOM Application Entity (AE) must be - able to return information about the Attributes of a substance, device, or a substance - administration act. This information is organized into well defined Substance Administration Query - Information Models. - - A specific SOP Class of the Substance - Administration Query Service Class consists of an informative Overview, an Information Model - Definition and a DIMSE-C Service Group. In this Service Class, the Information Model plays a role - similar to an Information Object Definition (IOD) of other DICOM Service Classes. - + In order to serve as a Service Class Provider (SCP) of the Substance Administration Query Service Class, a DICOM Application Entity (AE) must be able to return information about the Attributes of a substance, device, or a substance administration act. This information is organized into well defined Substance Administration Query Information Models. + A specific SOP Class of the Substance Administration Query Service Class consists of an informative Overview, an Information Model Definition and a DIMSE-C Service Group. In this Service Class, the Information Model plays a role similar to an Information Object Definition (IOD) of other DICOM Service Classes.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Substance Administration Query Service Class with one serving in the SCU role and one serving in the - SCP role. SOP Classes of the Substance Administration Query Service Class are implemented using the - DIMSE-C C-FIND service as defined in. - - Only a baseline behavior of the DIMSE-C C-FIND - is used in the Service Class. Extended negotiation is not used. - - The following description of the DIMSE-C C-FIND - service provides a brief overview of the SCU/SCP semantics. - - A C-FIND service conveys the following - semantics: - + Two peer DICOM AEs implement a SOP Class of the Substance Administration Query Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Substance Administration Query Service Class are implemented using the DIMSE-C C-FIND service as defined in . + Only a baseline behavior of the DIMSE-C C-FIND is used in the Service Class. Extended Negotiation is not used. + The following description of the DIMSE-C C-FIND service provides a brief overview of the SCU/SCP semantics. + A C-FIND service conveys the following semantics: - The SCU requests that the SCP perform a - match for the Matching Keys and return values for the Return Keys that have been specified - in the Identifier of the request, against the information that the SCP possesses relating to - the Information Model specified in the SOP Class. - + The SCU requests that the SCP perform a match for the Matching Keys and return values for the Return Keys that have been specified in the Identifier of the request, against the information that the SCP possesses relating to the Information Model specified in the SOP Class. - In this Annex, the term "Identifier" refers - to the Identifier service parameter of the C-FIND service as defined in - . - + In this Annex, the term "Identifier" refers to the Identifier service parameter of the C-FIND service as defined in . - The SCP generates at most one C-FIND - response for a match with an Identifier containing the values of all Matching Key Attributes - and all known Return Key Attributes requested. This response shall contain a status of - Pending. - + The SCP generates at most one C-FIND response for a match with an Identifier containing the values of all Matching Key Attributes and all known Return Key Attributes requested. This response shall contain a status of Pending. - When the process of matching is - complete, with zero or one match, a C-FIND response is sent with a status of Success and no - Identifier. - + When the process of matching is complete, with zero or one match, a C-FIND response is sent with a status of Success and no Identifier. - A Failure response to a C-FIND request - indicates that the SCP is unable to process the request. - + A Failure response to a C-FIND request indicates that the SCP is unable to process the request. - The SCU may cancel the C-FIND service - by issuing a C-CANCEL-FIND request at any time during the processing of the C-FIND service. - The SCP will interrupt all matching and return a status of Canceled. - + The SCU may cancel the C-FIND service by issuing a C-CANCEL-FIND request at any time during the processing of the C-FIND service. The SCP will interrupt all matching and return a status of Canceled. - The SCU needs to be prepared to receive - C-FIND responses sent by the SCP until the SCP finally processed the C-CANCEL-FIND request. - + The SCU needs to be prepared to receive C-FIND responses sent by the SCP until the SCP finally processed the C-CANCEL-FIND request.
Substance Administration Query Information Model Definition - The Substance Administration Query Information - Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is - composed of both an Information Model and a DIMSE-C Service Group. - - Information Model Definitions for Standard SOP - Classes of the Substance Administration Query Service Class are defined in this Annex. A Substance - Administration Query Information Model Definition contains: - + The Substance Administration Query Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + Information Model Definitions for Standard SOP Classes of the Substance Administration Query Service Class are defined in this Annex. A Substance Administration Query Information Model Definition contains: - an Entity-Relationship Model Definition - + an Entity-Relationship Model Definition a Key Attributes Definition. @@ -41675,76 +29358,39 @@
Entity-Relationship Model Definition - Substance Administration Query Information - Models consist of a single level that includes all Matching Key Attributes and all Return Key - Attributes that may be sent from the SCU to the SCP in the request, and whose values are expected to - be returned from the SCP to the SCU in the response (or Query items). The Matching Key Attribute - Values in the request specify the Query items that are to be returned in the response. All Key - Attributes (the Matching Key Attributes and the Return Key Attributes) in the request determine - which Attribute Values are returned in the response for that Query. - + Substance Administration Query Information Models consist of a single level that includes all Matching Key Attributes and all Return Key Attributes that may be sent from the SCU to the SCP in the request, and whose values are expected to be returned from the SCP to the SCU in the response (or Query items). The Matching Key Attribute Values in the request specify the Query items that are to be returned in the response. All Key Attributes (the Matching Key Attributes and the Return Key Attributes) in the request determine which Attribute Values are returned in the response for that Query.
Attributes Definition - Attributes are defined for each entity in the - internal Entity-Relationship Model. An Identifier in a C-FIND request shall contain values to be - matched against the Attributes of the Entities in a Substance Administration Query Information - Model. For any Query request, the set of entities for which Attributes are returned shall be - determined by the set of Matching and Return Key Attributes specified in the Identifier. - + Attributes are defined for each entity in the internal Entity-Relationship Model. An Identifier in a C-FIND request shall contain values to be matched against the Attributes of the Entities in a Substance Administration Query Information Model. For any Query request, the set of entities for which Attributes are returned shall be determined by the set of Matching and Return Key Attributes specified in the Identifier.
Attribute Types - All Attributes of entities in a Substance - Administration Query Information Model shall be specified both as a Matching Key Attribute - (either required or optional) and as a Return Key Attribute. - + All Attributes of entities in a Substance Administration Query Information Model shall be specified both as a Matching Key Attribute (either required or optional) and as a Return Key Attribute.
Matching Key Attributes - The Matching Key Attributes are Keys, - which select Query items to be included in a requested Query. - + The Matching Key Attributes are Keys, which select Query items to be included in a requested Query.
Required Matching Key Attributes - A Substance Administration Query - Service SCP shall support matching based on values of all Required Matching Key - Attributes of the C-FIND request. - + A Substance Administration Query Service SCP shall support matching based on values of all Required Matching Key Attributes of the C-FIND request.
Optional Matching Key Attributes - In the Substance Administration - Query Information Model, a set of Attributes may be defined as Optional Matching Key - Attributes. Optional Matching Key Attributes contained in the Identifier of a C-FIND - request may induce two different types of behavior depending on support for matching by - the SCP. If the SCP - + In the Substance Administration Query Information Model, a set of Attributes may be defined as Optional Matching Key Attributes. Optional Matching Key Attributes contained in the Identifier of a C-FIND request may induce two different types of behavior depending on support for matching by the SCP. If the SCP - does not support matching - on the Optional Matching Key Attribute, then the Optional Matching Key Attribute - shall be ignored for matching but shall be processed in the same manner as a - Return Key Attribute. - + does not support matching on the Optional Matching Key Attribute, then the Optional Matching Key Attribute shall be ignored for matching but shall be processed in the same manner as a Return Key Attribute. - supports matching of the - Optional Matching Key Attribute, then the Optional Matching Key Attribute shall - be processed in the same manner as a Required Matching Key. - + supports matching of the Optional Matching Key Attribute, then the Optional Matching Key Attribute shall be processed in the same manner as a Required Matching Key. - The Conformance - Statement of the SCP lists the Optional Matching Key Attributes that are - supported for matching. - + The Conformance Statement of the SCP lists the Optional Matching Key Attributes that are supported for matching. - An SCU can not expect - the SCP to support a match on an Optional Matching Key. - + An SCU can not expect the SCP to support a match on an Optional Matching Key. @@ -41752,39 +29398,21 @@
Return Key Attributes - The values of Return Key Attributes to - be retrieved with the Query are specified with zero-length (Universal Matching) in the - C-FIND request. SCPs shall support Return Key Attributes defined by a Substance - Administration Query Information Model according to the Data Element Type (1, 1C, 2, 2C, 3) - as defined in. - - Every Matching Key Attribute shall also - be considered as a Return Key Attribute. Therefore the C-FIND response shall contain, in - addition to the values of the requested Return Key Attributes, the values of the requested - Matching Key Attributes. - + The values of Return Key Attributes to be retrieved with the Query are specified with zero-length (Universal Matching) in the C-FIND request. SCPs shall support Return Key Attributes defined by a Substance Administration Query Information Model according to the Data Element Type (1, 1C, 2, 2C, 3) as defined in . + Every Matching Key Attribute shall also be considered as a Return Key Attribute. Therefore the C-FIND response shall contain, in addition to the values of the requested Return Key Attributes, the values of the requested Matching Key Attributes. - The Conformance Statement - of the SCP lists the Return Key Attributes of Type 3 that are supported. - + The Conformance Statement of the SCP lists the Return Key Attributes of Type 3 that are supported. - An SCU may choose to supply - any subset of Return Key Attributes. - + An SCU may choose to supply any subset of Return Key Attributes. - An SCU can not expect to - receive any Type 3 Return Key Attributes. - + An SCU can not expect to receive any Type 3 Return Key Attributes. - Return Key Attributes with - VR of SQ may be specified either with zero-length, or with a zero-length item in - the sequence. - + Return Key Attributes with VR of SQ may be specified either with zero-length, or with a zero-length item in the sequence. @@ -41792,15 +29420,7 @@
Attribute Matching - The following types of matching, which are - defined by the Query/Retrieve Service Class in, may be - performed on Matching Key Attributes in the Substance Administration Query Service Class. - Different Matching Key Attributes may be subject for different matching types. The Substance - Administration Query Information Model defines the type of matching for each Required Matching - Key Attribute. The Conformance Statement of the SCP shall define the type of matching for each - Optional Matching Key Attribute. The types of matching are: - + The following types of matching, which are defined by the Query/Retrieve Service Class in , may be performed on Matching Key Attributes in the Substance Administration Query Service Class. Different Matching Key Attributes may be subject for different matching types. The Substance Administration Query Information Model defines the type of matching for each Required Matching Key Attribute. The Conformance Statement of the SCP shall define the type of matching for each Optional Matching Key Attribute. The types of matching are: Single Value Matching @@ -41809,56 +29429,32 @@ Sequence Matching - The following type of matching, which is - defined by the Query/Retrieve Service Class in - - of this Part, shall be performed on Return Key Attributes in the Substance Administration Query - Service Class. - + The following type of matching, which is defined by the Query/Retrieve Service Class in of this Part, shall be performed on Return Key Attributes in the Substance Administration Query Service Class. Universal Matching - See - - and subsections for specific rules governing of Matching Key Attribute encoding for and - performing of different types of matching. - - The Specific Character Set (0008,0005) - Attribute may be present in the Identifier but is never matched, i.e., it is not considered a - Matching Key Attribute. See - - for details. - + See and subsections for specific rules governing of Matching Key Attribute encoding for and performing of different types of matching. + The Specific Character Set (0008,0005) Attribute may be present in the Identifier but is never matched, i.e., it is not considered a Matching Key Attribute. See for details.
Query Information Models - Each Substance Administration Query Information - Model is associated with one SOP Class. The following Substance Administration Query Information Models - are defined: - + Each Substance Administration Query Information Model is associated with one SOP Class. The following Substance Administration Query Information Models are defined: - Product Characteristics Query Information - Model - + Product Characteristics Query Information Model - Substance Approval Query Information - Model - + Substance Approval Query Information Model
DIMSE-C Service Group - One DIMSE-C Service is used in the construction of - SOP Classes of the Substance Administration Query Service Class. The following DIMSE-C operation is - used. - + One DIMSE-C Service is used in the construction of SOP Classes of the Substance Administration Query Service Class. The following DIMSE-C operation is used. C-FIND @@ -41866,113 +29462,55 @@
C-FIND Operation - SCPs of SOP Classes of the Substance - Administration Query Service Class are capable of processing queries using the C-FIND operation as - described in. The C-FIND - operation is the mechanism by which queries are performed. Matches against the keys present in the - Identifier are returned in C-FIND responses. - + SCPs of SOP Classes of the Substance Administration Query Service Class are capable of processing queries using the C-FIND operation as described in . The C-FIND operation is the mechanism by which queries are performed. Matches against the keys present in the Identifier are returned in C-FIND responses.
C-FIND Service Parameters
SOP Class UID - The SOP Class UID identifies the - Substance Administration Query Information Model against which the C-FIND is to be - performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the - Presentation Context used by this C-FIND operation. - + The SOP Class UID identifies the Substance Administration Query Information Model against which the C-FIND is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-FIND operation.
Priority - The Priority Attribute defines the - requested priority of the C-FIND operation with respect to other DIMSE operations being - performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. - + The Priority Attribute defines the requested priority of the C-FIND operation with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP.
Identifier - Both the C-FIND request and response - contain an Identifier encoded as a Data Set (see). - + Both the C-FIND request and response contain an Identifier encoded as a Data Set (see ).
Request Identifier Structure - An Identifier in a C-FIND request - shall contain - + An Identifier in a C-FIND request shall contain - Key Attributes values to be - matched against the values of Attributes specified in that SOP Class. - + Key Attributes values to be matched against the values of Attributes specified in that SOP Class. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Request Identifier. It shall not be included otherwise. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Request Identifier. It shall not be included otherwise. - This means that Specific - Character Set (0008,0005) is included if the SCU supports expanded or replacement - character sets in the context of this service. It will not be included if expanded - or replacement character sets are not supported by the SCU. - + This means that Specific Character Set (0008,0005) is included if the SCU supports expanded or replacement character sets in the context of this service. It will not be included if expanded or replacement character sets are not supported by the SCU. - The Key Attributes and values - allowable for the query shall be defined in the SOP Class definition for the - corresponding Substance Administration Query Information Model. - + The Key Attributes and values allowable for the query shall be defined in the SOP Class definition for the corresponding Substance Administration Query Information Model.
Response Identifier Structure - The C-FIND response shall not - contain Attributes that were not in the request or specified in this section. - - An Identifier in a C-FIND response - shall contain: - + The C-FIND response shall not contain Attributes that were not in the request or specified in this section. + An Identifier in a C-FIND response shall contain: - Key Attributes with values - corresponding to Key Attributes contained in the Identifier of the request (Key - Attributes as defined in - .) - + Key Attributes with values corresponding to Key Attributes contained in the Identifier of the request (Key Attributes as defined in .) - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Response Identifier. It shall not be included otherwise. The C-FIND SCP - is not required to return responses in the Specific Character Set requested by - the SCU if that character set is not supported by the SCP. The SCP may return - responses with a different Specific Character Set. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Response Identifier. It shall not be included otherwise. The C-FIND SCP is not required to return responses in the Specific Character Set requested by the SCU if that character set is not supported by the SCP. The SCP may return responses with a different Specific Character Set. - This means that Specific - Character Set (0008,0005) is included if the SCP supports expanded or replacement - character sets in the context of this service. It will not be included if expanded - or replacement character sets are not supported by the SCP. - + This means that Specific Character Set (0008,0005) is included if the SCP supports expanded or replacement character sets in the context of this service. It will not be included if expanded or replacement character sets are not supported by the SCP. - Conditionally, the - Attribute HL7 Structured Document Reference Sequence (0040,A390) and its - subsidiary Sequence Items as specified in the SOP Common Module (see). - This Attribute shall be included if HL7 Structured Documents are referenced - within the Identifier, e.g., in the Pertinent Documents Sequence (0038,0100). - + Conditionally, the Attribute HL7 Structured Document Reference Sequence (0040,A390) and its subsidiary Sequence Items as specified in the SOP Common Module (see ). This Attribute shall be included if HL7 Structured Documents are referenced within the Identifier, e.g., in the Pertinent Documents Sequence (0038,0100).
@@ -41980,11 +29518,7 @@
Status - - defines the status code values that might be returned in a C-FIND response. General status - code values and fields related to status code values are defined for C-FIND DIMSE Service in - . - + defines the status code values that might be returned in a C-FIND response. General status code values and fields related to status code values are defined for C-FIND DIMSE Service in .
Hanging Protocol SOP Classes
- Hanging Protocol - Information Model - FIND - + Hanging Protocol Information Model - FIND - 1.2.840.10008.5.1.4.38.2 - + 1.2.840.10008.5.1.4.38.2
- Hanging Protocol - Information Model - MOVE - + Hanging Protocol Information Model - MOVE - 1.2.840.10008.5.1.4.38.3 - + 1.2.840.10008.5.1.4.38.3
- Hanging Protocol - Information Model - GET - + Hanging Protocol Information Model - GET - 1.2.840.10008.5.1.4.38.4 - + 1.2.840.10008.5.1.4.38.4
@@ -42009,9 +29543,7 @@ Failure
C-FIND Response Status Values
- Refused: Out of - resources - + Refused: Out of resources A700 @@ -42022,9 +29554,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -42036,9 +29566,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -42053,9 +29581,7 @@ Cancel - Matching terminated due - to Cancel request - + Matching terminated due to Cancel request FE00 @@ -42069,9 +29595,7 @@ Success - Matching is complete - - No final Identifier is supplied. - + Matching is complete - No final Identifier is supplied. 0000 @@ -42085,10 +29609,7 @@ Pending - Matches are continuing - - Current Match is supplied and any Optional Keys were supported in the same - manner as Required Keys. - + Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF00 @@ -42099,10 +29620,7 @@
- Matches are continuing - - Warning that one or more Optional Keys were not supported for existence - for this Identifier. - + Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier. FF01 @@ -42114,164 +29632,81 @@
- Status Codes are returned in DIMSE - response messages (see). The code values stated - in column "Status Codes" are returned in Status Command Element (0000,0900). - + Status Codes are returned in DIMSE response messages (see ). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900). - Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: - Unable to process" Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: Unable to process" Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
C-FIND SCU Behavior - All C-FIND SCUs shall be capable of - generating query requests that meet the requirements of the Query Search Method (see). - - Required Keys and Optional Keys associated - with the Query may be contained in the Identifier. - - An SCU conveys the following semantics - using the C-FIND requests and responses: - + All C-FIND SCUs shall be capable of generating query requests that meet the requirements of the Query Search Method (see ). + Required Keys and Optional Keys associated with the Query may be contained in the Identifier. + An SCU conveys the following semantics using the C-FIND requests and responses: - The SCU requests that the SCP - perform a match of all keys specified in the Identifier of the request against the - information it possesses of the Query specified in the request. - + The SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information it possesses of the Query specified in the request. - The SCU shall interpret Pending - responses to convey the Attributes of a match of an item. - + The SCU shall interpret Pending responses to convey the Attributes of a match of an item. - The SCU shall interpret a response - with a status equal to Success, Failure, or Cancel to convey the end of Pending - responses. - + The SCU shall interpret a response with a status equal to Success, Failure, or Cancel to convey the end of Pending responses. - The SCU shall interpret a Failure - response to a C-FIND request as an indication that the SCP is unable to process the - request. - + The SCU shall interpret a Failure response to a C-FIND request as an indication that the SCP is unable to process the request. - The SCU may cancel the C-FIND - service by issuing a C-FIND-CANCEL request at any time during the processing of the - C-FIND. The SCU shall recognize a status of Cancel to indicate that the C-FIND-CANCEL - was successful. - + The SCU may cancel the C-FIND service by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND. The SCU shall recognize a status of Cancel to indicate that the C-FIND-CANCEL was successful.
C-FIND SCP Behavior - All C-FIND SCPs shall be capable of - processing queries that meet the requirements of the Query Search (see). - - An SCP conveys the following semantics - using the C-FIND requests and responses: - + All C-FIND SCPs shall be capable of processing queries that meet the requirements of the Query Search (see ). + An SCP conveys the following semantics using the C-FIND requests and responses: - The SCP is requested to perform a - match of all the keys specified in the Identifier of the request, against the - information it possesses. Attribute matching is performed using the key values specified - in the Identifier of the C-FIND request as defined in. - + The SCP is requested to perform a match of all the keys specified in the Identifier of the request, against the information it possesses. Attribute matching is performed using the key values specified in the Identifier of the C-FIND request as defined in . - The SCP generates at most one - C-FIND response for a match using the "Query" Search method. Such a response shall - contain an Identifier whose Attributes contain values from the match. The response shall - contain a status of Pending. - + The SCP generates at most one C-FIND response for a match using the "Query" Search method. Such a response shall contain an Identifier whose Attributes contain values from the match. The response shall contain a status of Pending. - When matching is complete and any - match has been sent, the SCP generates a C-FIND response that contains a status of - Success. A status of Success shall indicate that a response has been sent for any match - known to the SCP. - + When matching is complete and any match has been sent, the SCP generates a C-FIND response that contains a status of Success. A status of Success shall indicate that a response has been sent for any match known to the SCP. - No Identifier is contained in a - response with a status of Success. For a complete definition, see. - + No Identifier is contained in a response with a status of Success. For a complete definition, see . - When there are no matches, then - no responses with a status of Pending are sent, only a single response with a status - of Success. - + When there are no matches, then no responses with a status of Pending are sent, only a single response with a status of Success. - The SCP shall generate a response - with a status of Failure if it is unable to process the request. A Failure response - shall contain no Identifier. - + The SCP shall generate a response with a status of Failure if it is unable to process the request. A Failure response shall contain no Identifier. - If the SCP receives a C-FIND-CANCEL - indication before it has completed the processing of the matches it shall interrupt the - matching process and return a status of Cancel. - + If the SCP receives a C-FIND-CANCEL indication before it has completed the processing of the matches it shall interrupt the matching process and return a status of Cancel.
Query Search Method - The following procedure is used to - generate matches. - - The key match Attributes contained in - the Identifier of the C-FIND request are matched against the values of the Key Attributes - for each Query entity. For each entity for which the Attributes match all of the specified - match Attributes, construct an Identifier. This Identifier shall contain all of the values - of the Attributes for this entity that match those in the C-FIND request. Return a response - for each such Identifier. If there are no matching keys, then there are no matches; return a - response with a status equal to Success and with no Identifier. - + The following procedure is used to generate matches. + The key match Attributes contained in the Identifier of the C-FIND request are matched against the values of the Key Attributes for each Query entity. For each entity for which the Attributes match all of the specified match Attributes, construct an Identifier. This Identifier shall contain all of the values of the Attributes for this entity that match those in the C-FIND request. Return a response for each such Identifier. If there are no matching keys, then there are no matches; return a response with a status equal to Success and with no Identifier.
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. The Association negotiation procedure specified in - - shall be used to negotiate the supported SOP Classes. - - Support for the SCP/SCU Role Selection Negotiation - is optional. The SOP Class Extended Negotiation is not used by this Service Class. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in shall be used to negotiate the supported SOP Classes. + Support for the SCP/SCU Role Selection Negotiation is optional. The SOP Class Extended Negotiation is not used by this Service Class.
SOP Class Definitions @@ -42279,33 +29714,17 @@ Product Characteristics Query SOP Class
Product Characteristics Query SOP Class Overview - The Product Characteristics Query SOP Class - defines an application-level class of service that facilitates the communication of detailed - information about drugs, contrast agents, or devices identified by a bar code or similar - identifier. The detailed information is intended to be used both for automated processing and - for presentation to a system operator. - - The Product Characteristics Query SOP Class - supports the following example use cases: - + The Product Characteristics Query SOP Class defines an application-level class of service that facilitates the communication of detailed information about drugs, contrast agents, or devices identified by a bar code or similar identifier. The detailed information is intended to be used both for automated processing and for presentation to a system operator. + The Product Characteristics Query SOP Class supports the following example use cases: - Obtain the active ingredient, - concentration, or other parameters of a contrast agent for inclusion in the image SOP - Instances created during use of the agent, or for setting up image acquisition - parameters (e.g., ultrasound transducer frequency) - + Obtain the active ingredient, concentration, or other parameters of a contrast agent for inclusion in the image SOP Instances created during use of the agent, or for setting up image acquisition parameters (e.g., ultrasound transducer frequency) - Obtain the size parameters of a - device (e.g., a catheter) for use in calibrating images that show that device - + Obtain the size parameters of a device (e.g., a catheter) for use in calibrating images that show that device - Obtain a network reference for an - online copy of the "product label" (regulated prescribing and use data) for a drug, - contrast agent, or device. - + Obtain a network reference for an online copy of the "product label" (regulated prescribing and use data) for a drug, contrast agent, or device.
@@ -42313,11 +29732,7 @@ Product Characteristics Query Information Model
E/R Model - The Product Characteristics Query - Information Model is represented by the Entity Relationship diagram shown in figure - - -1. - + The Product Characteristics Query Information Model is represented by the Entity Relationship diagram shown in figure -1.
Product Characteristics E-R Diagram @@ -42329,54 +29744,42 @@
- There is only one Information Entity in - the model, which is the Product. The Attributes of a Product can be found in the following - Module in. - + There is only one Information Entity in the model, which is the Product. The Attributes of a Product can be found in the following Module in . - Product Characteristics - Module - + Product Characteristics Module
Product Characteristics Query Attributes - - defines the Attributes of the Product Characteristics Query Information Model: - + defines the Attributes of the Product Characteristics Query Information Model: @@ -42436,9 +29834,7 @@ @@ -42552,70 +29935,31 @@
Attributes for the Product Characteristics Query Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Product Package - Identifier - + Product Package Identifier (0044,0001) @@ -42388,16 +29791,12 @@ 1 - Shall be retrieved with - Single Value Matching only. - + Shall be retrieved with Single Value Matching only.
- Product Type Code - Sequence - + Product Type Code Sequence (0044,0007) @@ -42413,10 +29812,9 @@
- >Include - - - +>Include + +
- Product Expiration - DateTime - + Product Expiration DateTime (0044,000B) @@ -42453,9 +29849,7 @@
- Product Parameter - Sequence - + Product Parameter Sequence (0044,0013) @@ -42485,9 +29879,7 @@
- >Concept Name Code - Sequence - + >Concept Name Code Sequence (0040,A043) @@ -42503,18 +29895,15 @@
- >>Include - - - +>>Include + +
- >All other Attributes of the Product Parameter - Sequence - + >All other Attributes of the Product Parameter Sequence @@ -42525,19 +29914,13 @@ 1C - Conditional on value of - Value Type (0040,A040); See - - Content Item Macro. - + Conditional on value of Value Type (0040,A040); See Content Item Macro.
- All other Attributes of the - + All other Attributes of the
- The Product Package Identifier - (0044,0001) might not be globally unique and might conflict with other identifiers used - within the scope of the institution. - + The Product Package Identifier (0044,0001) might not be globally unique and might conflict with other identifiers used within the scope of the institution. - The package identifiers are - typically unique within the scope of the substance administration management systems. - This is a warning that they are not UIDs. - + The package identifiers are typically unique within the scope of the substance administration management systems. This is a warning that they are not UIDs.
Conformance Requirements - An implementation may conform to the - Product Characteristics Query SOP Class as an SCU or an SCP. The Conformance Statement shall be - in the format defined in. - + An implementation may conform to the Product Characteristics Query SOP Class as an SCU or an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that conforms to the - Product Characteristics Query SOP Class shall support queries against the Information Model - described in - - using the baseline C-FIND SCU Behavior described in. - - An implementation that conforms to the - Product Characteristics Query SOP Class as an SCU shall state in its Conformance Statement - the Return Key Attributes it requests, and how those Attributes are used in the application. - - An implementation that conforms to the - Product Characteristics Query SOP Class as an SCU shall state in its Conformance Statement - how it makes use of Specific Character Set (0008,0005) when encoding queries and - interpreting responses. - + An implementation that conforms to the Product Characteristics Query SOP Class shall support queries against the Information Model described in using the baseline C-FIND SCU Behavior described in . + An implementation that conforms to the Product Characteristics Query SOP Class as an SCU shall state in its Conformance Statement the Return Key Attributes it requests, and how those Attributes are used in the application. + An implementation that conforms to the Product Characteristics Query SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
SCP Conformance - An implementation that conforms to the - Product Characteristics Query SOP Class shall support queries against the Product - Characteristics Query Information Model described in - - using the C-FIND SCP Behavior described in. - - An implementation that conforms to the - Product Characteristics Query SOP Class as an SCP shall state in its Conformance Statement - the Return Key Attributes that it supports. - - An implementation that conforms to the - Product Characteristics Query SOP Class as an SCP shall state in its Conformance Statement - how it makes use of Specific Character Set (0008,0005) when encoding responses. - + An implementation that conforms to the Product Characteristics Query SOP Class shall support queries against the Product Characteristics Query Information Model described in using the C-FIND SCP Behavior described in . + An implementation that conforms to the Product Characteristics Query SOP Class as an SCP shall state in its Conformance Statement the Return Key Attributes that it supports. + An implementation that conforms to the Product Characteristics Query SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding responses.
SOP Class - The Product Characteristics Query SOP Class - in the Substance Administration Service Class identifies the Product Characteristics Query - Information Model, and the DIMSE-C operations supported. The following Standard SOP Class is - identified: - + The Product Characteristics Query SOP Class in the Substance Administration Service Class identifies the Product Characteristics Query Information Model, and the DIMSE-C operations supported. The following Standard SOP Class is identified: @@ -42631,13 +29975,10 @@ @@ -42648,44 +29989,23 @@ Substance Approval Query SOP Class
Substance Approval Query SOP Class Overview - The Substance Approval Query SOP Class - defines an application-level class of service that allows a device at the point of care to - obtain verification of the appropriateness of contrast agents and other drugs administered - during a procedure, based on the substance label barcode and the patient ID. The response is an - authorization to proceed, or a warning, or a contra-indication for presentation to the system - operator. - - The Substance Approval Query SOP Class - supports the following example use cases: - + The Substance Approval Query SOP Class defines an application-level class of service that allows a device at the point of care to obtain verification of the appropriateness of contrast agents and other drugs administered during a procedure, based on the substance label barcode and the patient ID. The response is an authorization to proceed, or a warning, or a contra-indication for presentation to the system operator. + The Substance Approval Query SOP Class supports the following example use cases: - Obtain verification that - administration of a specific drug or contrast agent for an image acquisition is - appropriate for the patient - + Obtain verification that administration of a specific drug or contrast agent for an image acquisition is appropriate for the patient - Obtain verification that the - implantation of a specific device under imaging guidance is appropriate for the patient - + Obtain verification that the implantation of a specific device under imaging guidance is appropriate for the patient - The Substance Approval Query SOP Class does - not specify the mechanism used by the SCP to verify such appropriateness of administration - (e.g., by comparison to allergy information in the patient's electronic health record). The - duration of validity of an approval beyond the time of the response is not defined by the - Standard. - + The Substance Approval Query SOP Class does not specify the mechanism used by the SCP to verify such appropriateness of administration (e.g., by comparison to allergy information in the patient's electronic health record). The duration of validity of an approval beyond the time of the response is not defined by the Standard.
Substance Approval Query Information Model
E/R Model - The Substance Approval Query - Information Model is represented by the Entity Relationship diagram shown in. - + The Substance Approval Query Information Model is represented by the Entity Relationship diagram shown in .
Substance Approval E-R Diagram @@ -42700,89 +30020,43 @@ - The Attributes of the Information - Entities can be found in the following Modules in. - + The Attributes of the Information Entities can be found in the following Modules in . - Patient Identification Module - + Patient Identification Module - Patient Demographics Module - + Patient Demographics Module - Visit Identification Module - + Visit Identification Module - Substance Administration - Module - + Substance Administration Module - Substance Approval Module - + Substance Approval Module - Product Characteristics - Module - + Product Characteristics Module - Only selected Attributes of these - Modules are used in the Substance Approval Query Information Model. - - The Information Model is used in a - bottom-up manner in the query; i.e., given a Product and a Patient, or alternatively a - Product and a Visit, for a proposed Substance Administration act at the current time, find - the Approval. - - The Visit IE is included in the - Information Model to support those institutions that identify patients (e.g., on a bar coded - wristband) by Admission ID (i.e., the ID of the Visit), rather than Patient ID. This allows - automation of query construction using a scan of the Admission ID. The Admission ID can be - mapped to the Patient ID by the SCP for the purpose of the performing the query matching. - + Only selected Attributes of these Modules are used in the Substance Approval Query Information Model. + The Information Model is used in a bottom-up manner in the query; i.e., given a Product and a Patient, or alternatively a Product and a Visit, for a proposed Substance Administration act at the current time, find the Approval. + The Visit IE is included in the Information Model to support those institutions that identify patients (e.g., on a bar coded wristband) by Admission ID (i.e., the ID of the Visit), rather than Patient ID. This allows automation of query construction using a scan of the Admission ID. The Admission ID can be mapped to the Patient ID by the SCP for the purpose of the performing the query matching. - The Visit is identified by - the Admission ID (0038,0010) Attribute, but in the "Model of the Real World for - the Purpose of Modality-IS Interface" (see - ), the Visit is subsidiary to the Patient; hence the Admission ID may only be - unique within the context of the patient, not within the context of the - institution. The use of the Admission ID Attribute to identify the Visit (and - hence the Patient) is only effective if the Admission ID is unique within the - context of the institution. - + The Visit is identified by the Admission ID (0038,0010) Attribute, but in the "Model of the Real World for the Purpose of Modality-IS Interface" (see ), the Visit is subsidiary to the Patient; hence the Admission ID may only be unique within the context of the patient, not within the context of the institution. The use of the Admission ID Attribute to identify the Visit (and hence the Patient) is only effective if the Admission ID is unique within the context of the institution. - Certain institutions, e.g., - ambulatory imaging centers that do not "admit" patients, may use the Imaging - Service Request Identifier, or Accession Number, as an equivalent of the - Admission ID. The SCU of this Query Service does not need to know the true - origin or nature of the identifier, only that it is passed in the Query in the - Admission ID (0038,0010) Attribute. - + Certain institutions, e.g., ambulatory imaging centers that do not "admit" patients, may use the Imaging Service Request Identifier, or Accession Number, as an equivalent of the Admission ID. The SCU of this Query Service does not need to know the true origin or nature of the identifier, only that it is passed in the Query in the Admission ID (0038,0010) Attribute. - There is conceptually a - datetime of administration Attribute of the Substance Administration act, which - is implicitly assumed to be approximately the time of the query in this SOP - Class. - + There is conceptually a datetime of administration Attribute of the Substance Administration act, which is implicitly assumed to be approximately the time of the query in this SOP Class. - There is conceptually a - dose Attribute of the Product entity, which is the entire product identified by - the bar code, and the request is for approval of administration of the entire - product. - + There is conceptually a dose Attribute of the Product entity, which is the entire product identified by the bar code, and the request is for approval of administration of the entire product. @@ -42790,30 +30064,25 @@
Substance Approval Query Attributes - - defines the Attributes of the Substance Approval Query Information Model. - + defines the Attributes of the Substance Approval Query Information Model.
Product Characteristics Query SOP Classes
- Product Characteristics - Query Information Model - FIND - + Product Characteristics Query Information Model - FIND - 1.2.840.10008.5.1.4.41 - + 1.2.840.10008.5.1.4.41
@@ -42854,19 +30123,13 @@ 1 @@ -43061,9 +30300,7 @@ @@ -43089,9 +30324,7 @@ @@ -43126,9 +30356,7 @@
Attributes for the Substance Approval Query Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Shall be retrieved with - Single Value Matching only. - - One or both of Patient - ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching - Key in the Query - + Shall be retrieved with Single Value Matching only. + One or both of Patient ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching Key in the Query
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -42881,9 +30144,7 @@
- Issuer of Patient ID - Qualifiers Sequence - + Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -42898,9 +30159,7 @@
- >All Attributes of - the Issuer of Patient ID Qualifiers Sequence - + >All Attributes of the Issuer of Patient ID Qualifiers Sequence @@ -42913,8 +30172,7 @@
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -42963,20 +30221,13 @@ 2 - Shall be retrieved with - Single Value Matching only. - - One or both of Patient - ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching - Key in the Query - + Shall be retrieved with Single Value Matching only. + One or both of Patient ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching Key in the Query
- Issuer of Admission ID - Sequence - + Issuer of Admission ID Sequence (0038,0014) @@ -42991,9 +30242,7 @@
- >Local Namespace - Entity ID - + >Local Namespace Entity ID (0040,0031) @@ -43005,16 +30254,12 @@ 1C - Required if Universal - Entity ID (0040,0032) is not present; may be present otherwise - + Required if Universal Entity ID (0040,0032) is not present; may be present otherwise
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) @@ -43026,16 +30271,12 @@ 1C - Required if Local - Namespace Entity ID (0040,0031) is not present; may be present otherwise. - + Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) @@ -43047,9 +30288,7 @@ 1C - Required if Universal - Entity ID (0040,0032) is present. - + Required if Universal Entity ID (0040,0032) is present.
- Product Package - Identifier - + Product Package Identifier (0044,0001) @@ -43075,9 +30312,7 @@ 1 - Shall be retrieved with - Single Value Matching only. Shall be present as a Matching Key in the Query. - + Shall be retrieved with Single Value Matching only. Shall be present as a Matching Key in the Query.
- Administration Route - Code Sequence - + Administration Route Code Sequence (0054,0302) @@ -43103,18 +30336,15 @@ 1 - Shall be present as a - Matching Key in the Query. - + Shall be present as a Matching Key in the Query.
- >Include - - - +>Include + +
- Substance - Administration Approval - + Substance Administration Approval (0044,0002) @@ -43143,9 +30371,7 @@
- Approval Status Further - Description - + Approval Status Further Description (0044,0003) @@ -43160,9 +30386,7 @@
- Approval Status - DateTime - + Approval Status DateTime (0044,0004) @@ -43177,109 +30401,42 @@
- One or both of Patient ID (0010,0020) - and Admission ID (0038,0010) shall be present as a Matching Key in the Query. - - Product Package Identifier (0044,0001) - shall be present as a Matching Key in the Query. The Product Package Identifier might not be - globally unique and might conflict with other identifiers used within the scope of the - institution. - + One or both of Patient ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching Key in the Query. + Product Package Identifier (0044,0001) shall be present as a Matching Key in the Query. The Product Package Identifier might not be globally unique and might conflict with other identifiers used within the scope of the institution. - The package identifiers are - typically unique within the scope of the substance administration management systems. - This is a warning that they are not UIDs. - + The package identifiers are typically unique within the scope of the substance administration management systems. This is a warning that they are not UIDs. - Administration Route Code Sequence - (0054,0302) shall be present as a Matching Key in the Query, and a single Item shall be - present in that Sequence with Code Value (0008,0100) and Coding Scheme Designator - (0008,0102) as Matching Keys. - + Administration Route Code Sequence (0054,0302) shall be present as a Matching Key in the Query, and a single Item shall be present in that Sequence with Code Value (0008,0100) and Coding Scheme Designator (0008,0102) as Matching Keys.
Substance Approval Query Responses - A Query response may have a status of - Success or Failure (see). A - Failure Query response carries no semantics about the existence or status of approval of the - Substance Administration. - - A successful Query response will - contain zero or one Pending response items. The case of zero Pending responses carries the - semantics of no matching Approval Information Entity found, i.e., that the SCP cannot - determine an approval, rather than that the substance administration is approved or - disapproved. In this case a decision on substance administration needs to be made by the - healthcare provider. - + A Query response may have a status of Success or Failure (see ). A Failure Query response carries no semantics about the existence or status of approval of the Substance Administration. + A successful Query response will contain zero or one Pending response items. The case of zero Pending responses carries the semantics of no matching Approval Information Entity found, i.e., that the SCP cannot determine an approval, rather than that the substance administration is approved or disapproved. In this case a decision on substance administration needs to be made by the healthcare provider. - Zero Pending responses may occur - due do inability of the SCP to match the patient ID, product ID or route of - administration. - + Zero Pending responses may occur due do inability of the SCP to match the patient ID, product ID or route of administration. - In the case of one Pending response, - the matching Approval Information Entity will explicitly convey the Substance Administration - Approval (0044,0002) value of APPROVED, WARNING, or CONTRA_INDICATED. - + In the case of one Pending response, the matching Approval Information Entity will explicitly convey the Substance Administration Approval (0044,0002) value of APPROVED, WARNING, or CONTRA_INDICATED.
Conformance Requirements - An implementation may conform to the - Substance Approval Query SOP Class as an SCU or an SCP. The Conformance Statement shall be in - the format defined in. - + An implementation may conform to the Substance Approval Query SOP Class as an SCU or an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that conforms to the - Substance Approval Query SOP Class shall support queries against the Information Model - described in - - using the baseline C-FIND SCU Behavior described in. - - An implementation that conforms to the - Substance Approval Query SOP Class as an SCU shall state in its Conformance Statement how - the Query Attributes are used in the application, and how the application displays the - returned Attributes, in particular the values of Substance Administration Approval - (0044,0002) and Approval Status Further Description (0044,0003). It shall state how it - indicates a Query response with zero Pending items, or a Failure status. - - An implementation that conforms to the - Substance Approval Query SOP Class as an SCU shall state in its Conformance Statement how it - makes use of Specific Character Set (0008,0005) when encoding queries and interpreting - responses. - + An implementation that conforms to the Substance Approval Query SOP Class shall support queries against the Information Model described in using the baseline C-FIND SCU Behavior described in . + An implementation that conforms to the Substance Approval Query SOP Class as an SCU shall state in its Conformance Statement how the Query Attributes are used in the application, and how the application displays the returned Attributes, in particular the values of Substance Administration Approval (0044,0002) and Approval Status Further Description (0044,0003). It shall state how it indicates a Query response with zero Pending items, or a Failure status. + An implementation that conforms to the Substance Approval Query SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
SCP Conformance - An implementation that conforms to the - Substance Approval Query SOP Class shall support queries against the Substance Approval - Query Information Model described in - - using the C-FIND SCP Behavior described in. It shall - support all of the Attributes specified in the Information Model. - - An implementation that conforms to the - Substance Approval Query SOP Class as an SCP shall state in its Conformance Statement how it - processes Required and Optional Matching Key Attributes. It shall state how it obtains the - values for the Return Key Attributes. - - An implementation that conforms to the - Substance Approval Query SOP Class as an SCP shall state in its Conformance Statement how it - makes use of Specific Character Set (0008,0005) when interpreting queries, performing - matching and encoding responses. - + An implementation that conforms to the Substance Approval Query SOP Class shall support queries against the Substance Approval Query Information Model described in using the C-FIND SCP Behavior described in . It shall support all of the Attributes specified in the Information Model. + An implementation that conforms to the Substance Approval Query SOP Class as an SCP shall state in its Conformance Statement how it processes Required and Optional Matching Key Attributes. It shall state how it obtains the values for the Return Key Attributes. + An implementation that conforms to the Substance Approval Query SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.
SOP Class - The Substance Approval Query SOP Class in - the Substance Administration Service Class identifies the Substance Approval Query Information - Model, and the DIMSE-C operations supported. The following Standard SOP Class is identified: - + The Substance Approval Query SOP Class in the Substance Administration Service Class identifies the Substance Approval Query Information Model, and the DIMSE-C operations supported. The following Standard SOP Class is identified: @@ -43295,13 +30452,10 @@ @@ -43312,14 +30466,9 @@ Color Palette Storage Service Class - See. - + See . - The requirements of this section have been - consolidated into the Non-Patient Object Storage Service Class (see). - + The requirements of this section have been consolidated into the Non-Patient Object Storage Service Class (see ). @@ -43328,122 +30477,65 @@ Overview
Scope - The Color Palette Query/Retrieve Service Class - defines an application-level class-of-service that facilitates access to Color Palette composite - objects. - + The Color Palette Query/Retrieve Service Class defines an application-level class-of-service that facilitates access to Color Palette composite objects.
Conventions - See Conventions for the Basic Worklist - Management Service (K.1.2). - + See Conventions for the Basic Worklist Management Service (K.1.2).
Query/Retrieve Information Model - In order to serve as an SCP of the Color - Palette Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a - number of Color Palette composite SOP Instances. The information is organized into a Color Palette - Information Model. - + In order to serve as an SCP of the Color Palette Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of Color Palette composite SOP Instances. The information is organized into a Color Palette Information Model.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Color Palette Query/Retrieve Service Class with one serving in the SCU role and one serving in the - SCP role. SOP Classes of the Color Palette Query/Retrieve Service Class are implemented using the - DIMSE-C C-FIND, C-MOVE and C-GET services as defined in. - - The semantics of the C-FIND service are the - same as those defined in the Service Definition of the Basic Worklist Management Service Class. - - The semantics of the C-MOVE and C-GET services - are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with - the exception that there is only one level of retrieval. - + Two peer DICOM AEs implement a SOP Class of the Color Palette Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Color Palette Query/Retrieve Service Class are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in . + The semantics of the C-FIND service are the same as those defined in the Service Definition of the Basic Worklist Management Service Class. + The semantics of the C-MOVE and C-GET services are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval.
Color Palette Information Model Definition - The Color Palette Information Model is identified - by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an - Information Model and a DIMSE-C Service Group. - - The Color Palette Information Model is defined, - with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined - in the Worklist Information Model Definition of the Basic Worklist Management Service. - + The Color Palette Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + The Color Palette Information Model is defined, with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model Definition of the Basic Worklist Management Service.
Color Palette Information Model - The Color Palette Information Model is based upon a - one level entity: - + The Color Palette Information Model is based upon a one level entity: Color Palette object instance - The Color Palette object instance contains - Attributes associated with the Color Palette object IE of the Composite IODs as defined in. - + The Color Palette object instance contains Attributes associated with the Color Palette object IE of the Composite IODs as defined in .
DIMSE-C Service Groups
C-FIND Operation - See the C-FIND Operation definition for the - Basic Worklist Management Service Class (K.4.1), and substitute "Color Palette" for "Worklist. The - "Worklist" Search Method shall be used. - - The SOP Class UID identifies the Color Palette - Information Model against which the C-FIND is to be performed. The Key Attributes and values - allowable for the query are defined in the SOP Class definition for the Color Palette Information - Model. - + See the C-FIND Operation definition for the Basic Worklist Management Service Class (K.4.1), and substitute "Color Palette" for "Worklist. The "Worklist" Search Method shall be used. + The SOP Class UID identifies the Color Palette Information Model against which the C-FIND is to be performed. The Key Attributes and values allowable for the query are defined in the SOP Class definition for the Color Palette Information Model.
C-MOVE Operation - See the C-MOVE Operation definition for the - Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the - Color Palette Query/Retrieve Service Class. - - Query/Retrieve Level (0008,0052) is not - relevant to the Color Palette Query/Retrieve Service Class, and therefore shall not be present in - the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID - (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-MOVE Operation definition for the Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the Color Palette Query/Retrieve Service Class. + Query/Retrieve Level (0008,0052) is not relevant to the Color Palette Query/Retrieve Service Class, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
C-GET Operation - See the C-GET Operation definition for the - Query/Retrieve Service Class (C.4.3). No Extended Behavior or Relational-Retrieve is defined for the - Color Palette Query/Retrieve Service Class. - - Query/Retrieve Level (0008,0052) is not - relevant to the Color Palette Query/Retrieve Service Class, and therefore shall not be present in - the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID - (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-GET Operation definition for the Query/Retrieve Service Class (C.4.3). No Extended Behavior or Relational-Retrieve is defined for the Color Palette Query/Retrieve Service Class. + Query/Retrieve Level (0008,0052) is not relevant to the Color Palette Query/Retrieve Service Class, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
Association Negotiation - See the Association Negotiation definition for the - Basic Worklist Management Service Class (K.5). - + See the Association Negotiation definition for the Basic Worklist Management Service Class (K.5).
SOP Class Definitions @@ -43451,10 +30543,7 @@ Color Palette Information Model
E/R Model - The Color Palette Information Model - consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Color Palette Instance. - + The Color Palette Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Color Palette Instance.
Color Palette Information Model E-R Diagram @@ -43470,9 +30559,7 @@
Color Palette Attributes - - defines the Attributes of the Color Palette Information Model: - + defines the Attributes of the Color Palette Information Model:
Substance Approval Query SOP Classes
- Substance Approval Query - Information Model - FIND - + Substance Approval Query Information Model - FIND - 1.2.840.10008.5.1.4.42 - + 1.2.840.10008.5.1.4.42
@@ -43490,8 +30577,7 @@ Return Key Type @@ -43505,8 +30591,7 @@ @@ -43539,9 +30620,7 @@ 1 @@ -43558,9 +30637,7 @@ 1 @@ -43584,9 +30661,7 @@ 1 @@ -43606,8 +30681,7 @@ @@ -43684,114 +30752,47 @@
Conformance Requirements - An implementation may conform to one of the - Color Palette Information Model SOP Classes as an SCU, SCP or both. The Conformance Statement - shall be in the format defined in. - + An implementation may conform to one of the Color Palette Information Model SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - one of the Color Palette Information Model SOP Classes shall support queries against the - Color Palette Information Model using the C-FIND SCU Behavior described for the Basic - Worklist Management Service Class (see - - and). - - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCU shall state in its - Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list - these Optional Return Key Attributes. - - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCU shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) when - encoding queries and interpreting responses. - + An implementation that conforms to one of the Color Palette Information Model SOP Classes shall support queries against the Color Palette Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see and ). + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCU shall support transfers - against the Color Palette Information Model using the C-MOVE SCU baseline behavior - described for the Query/Retrieve Service Class (see - - and). - + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCU shall support transfers against the Color Palette Information Model using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
C-GET SCU Conformance - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCU shall support transfers - against the Color Palette Information Model using the C-GET SCU baseline behavior - described for the Query/Retrieve Service Class (see - - and). - + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCU shall support transfers against the Color Palette Information Model using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP shall support queries - against the Color Palette Information Model using the C-FIND SCP Behavior described for - the Basic Worklist Management Service Class (see). - - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP shall state in its - Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list - these Optional Return Key Attributes. - - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) when - interpreting queries, performing matching and encoding responses. - + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP shall support queries against the Color Palette Information Model using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see ). + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP shall state in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.
C-MOVE SCP Conformance - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP shall support transfers - against the Color Palette Information Model using the C-MOVE SCP baseline behavior - described for the Query/Retrieve Service Class (see). - - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP, which generates - transfers using the C-MOVE operation, shall state in its Conformance Statement the Color - Palette Storage Service Class SOP Class under which it shall support the C-STORE - sub-operations generated by the C-MOVE. - + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP shall support transfers against the Color Palette Information Model using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see ). + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement the Color Palette Storage Service Class SOP Class under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP shall support transfers - against the Color Palette Information Model using the C-GET SCP baseline behavior - described for the Query/Retrieve Service Class (see). - - An implementation that conforms to - one of the Color Palette Information Model SOP Classes as an SCP, which generates - transfers using the C-GET operation, shall state in its Conformance Statement the Color - Palette Storage Service Class SOP Class under which it shall support the C-STORE - sub-operations generated by the C-GET. - + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP shall support transfers against the Color Palette Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class (see ). + An implementation that conforms to one of the Color Palette Information Model SOP Classes as an SCP, which generates transfers using the C-GET operation, shall state in its Conformance Statement the Color Palette Storage Service Class SOP Class under which it shall support the C-STORE sub-operations generated by the C-GET.
SOP Classes - The SOP Classes of the Color Palette - Information Model in the Color Palette Query/Retrieve Service Class identify the Color Palette - Information Model, and the DIMSE-C operations supported. The following Standard SOP Classes are - identified: - + The SOP Classes of the Color Palette Information Model in the Color Palette Query/Retrieve Service Class identify the Color Palette Information Model, and the DIMSE-C operations supported. The following Standard SOP Classes are identified:
Attributes for the Color Palette Information Model
- Remark / Matching Type - + Remark / Matching Type
- Specific Character Set - + Specific Character Set (0008,0005) @@ -43518,11 +30603,7 @@ 1C - This Attribute is required - if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- This Attribute shall be - retrieved with Single Value matching. - + This Attribute shall be retrieved with Single Value matching.
- This Attribute shall be - retrieved with Single Value matching. - + This Attribute shall be retrieved with Single Value matching.
- This Attribute shall be - retrieved with Single Value, Wild Card or Universal matching. - + This Attribute shall be retrieved with Single Value, Wild Card or Universal matching.
- Content Creator's Name - + Content Creator's Name (0070,0084) @@ -43622,9 +30696,7 @@
- Alternate Content - Description Sequence - + Alternate Content Description Sequence (0070,0087) @@ -43639,8 +30711,7 @@
- >Content Description - + >Content Description (0070,0081) @@ -43655,9 +30726,7 @@
- >Language Code - Sequence - + >Language Code Sequence (0008,0006) @@ -43673,10 +30742,9 @@
- >>Include - - - +>>Include + +
@@ -43807,35 +30808,26 @@ @@ -43850,119 +30842,49 @@ Overview
Scope - Composite Instance Root Retrieve Service is a - service within the DICOM Query/Retrieve Service class defined in - .The retrieve capability of this service allows a DICOM AE to retrieve Composite Instances or - selected frames from a remote DICOM AE over a single Association or request the remote DICOM AE to - initiate a transfer of Composite Object Instances or selected frames from image objects to another - DICOM AE. - - The Enhanced Multi-Frame Image Conversion - Extended Negotiation Option of the DICOM Query/Retrieve Service class defined in - - is also supported for the Composite Instance Root Retrieve Service. - + Composite Instance Root Retrieve Service is a service within the DICOM Query/Retrieve Service class defined in .The retrieve capability of this service allows a DICOM AE to retrieve Composite Instances or selected frames from a remote DICOM AE over a single Association or request the remote DICOM AE to initiate a transfer of Composite Object Instances or selected frames from image objects to another DICOM AE. + The Enhanced Multi-Frame Image Conversion Extended Negotiation Option of the DICOM Query/Retrieve Service class defined in is also supported for the Composite Instance Root Retrieve Service.
Composite Instance Root Retrieve Information Model - Retrievals are implemented against the - Composite Instance Root Retrieve Information Model, as defined in this Annex of the DICOM Standard. - A specific SOP Class of the Query/Retrieve Service Class consists of an Information Model Definition - and a DIMSE-C Service Group. - + Retrievals are implemented against the Composite Instance Root Retrieve Information Model, as defined in this Annex of the DICOM Standard. A specific SOP Class of the Query/Retrieve Service Class consists of an Information Model Definition and a DIMSE-C Service Group.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Composite Instance Root Retrieve Service with one serving in the SCU role and one serving in the SCP - role. SOP Classes of the Composite Instance Root Retrieve Service are implemented using the DIMSE-C - C-MOVE and C-GET services as defined in. - - The following descriptions of the DIMSE-C C-GET - and C-MOVE services provide a brief overview of the SCU/SCP semantics: - + Two peer DICOM AEs implement a SOP Class of the Composite Instance Root Retrieve Service with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Composite Instance Root Retrieve Service are implemented using the DIMSE-C C-MOVE and C-GET services as defined in . + The following descriptions of the DIMSE-C C-GET and C-MOVE services provide a brief overview of the SCU/SCP semantics: - A C-MOVE service conveys the following - semantics: - + A C-MOVE service conveys the following semantics: - The SCU supplies Unique and - Frame Range Key values to identify the requested SOP Instance(s). The SCP creates - new SOP instances if necessary and then initiates C-STORE sub-operations for the - corresponding storage SOP Instances. These C-STORE sub-operations occur on a - different Association than the C-MOVE service. The SCP role of the Retrieve SOP - Class and the SCU role of the Storage SOP Class may be performed by different - applications that may or may not reside on the same system. Initiation mechanism of - C-STORE sub-operations is outside of the scope of DICOM Standard. - + The SCU supplies Unique and Frame Range Key values to identify the requested SOP Instance(s). The SCP creates new SOP instances if necessary and then initiates C-STORE sub-operations for the corresponding storage SOP Instances. These C-STORE sub-operations occur on a different Association than the C-MOVE service. The SCP role of the Retrieve SOP Class and the SCU role of the Storage SOP Class may be performed by different applications that may or may not reside on the same system. Initiation mechanism of C-STORE sub-operations is outside of the scope of DICOM Standard. - The SCP may optionally generate - responses to the C-MOVE with status equal to Pending during the processing of the - C-STORE sub-operations. These C-MOVE responses indicate the number of Remaining - C-STORE sub-operations and the number of C-STORE sub-operations returning the status - of Success, Warning, and Failed. - + The SCP may optionally generate responses to the C-MOVE with status equal to Pending during the processing of the C-STORE sub-operations. These C-MOVE responses indicate the number of Remaining C-STORE sub-operations and the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. - When the number of Remaining - C-STORE sub-operations reaches zero, the SCP generates a final response with a - status equal to Success, Warning, Failed, or Refused. This response shall indicate - the number of C-STORE sub-operations returning the status of Success, Warning, and - Failed. If any of the sub-operations was successful then a Successful UID list shall - be returned. If the status of a C-STORE sub-operation was Failed a UID List shall be - returned. - + When the number of Remaining C-STORE sub-operations reaches zero, the SCP generates a final response with a status equal to Success, Warning, Failed, or Refused. This response shall indicate the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. If any of the sub-operations was successful then a Successful UID list shall be returned. If the status of a C-STORE sub-operation was Failed a UID List shall be returned. - The SCU may cancel the C-MOVE - service by issuing a C-MOVE-CANCEL request at any time during the processing of the - C-MOVE. The SCP terminates all incomplete C-STORE sub-operations and returns a - status of Canceled. - + The SCU may cancel the C-MOVE service by issuing a C-MOVE-CANCEL request at any time during the processing of the C-MOVE. The SCP terminates all incomplete C-STORE sub-operations and returns a status of Canceled. - A C-GET service conveys the following - semantics: - + A C-GET service conveys the following semantics: - The SCU supplies Unique and - Frame Range Key values to identify the requested SOP Instance(s). The SCP creates - new SOP instances if necessary and then generates C-STORE sub-operations for the - corresponding storage SOP Instances. These C-STORE sub-operations occur on the same - Association as the C-GET service and the SCU/SCP roles are reversed for the C-STORE. - + The SCU supplies Unique and Frame Range Key values to identify the requested SOP Instance(s). The SCP creates new SOP instances if necessary and then generates C-STORE sub-operations for the corresponding storage SOP Instances. These C-STORE sub-operations occur on the same Association as the C-GET service and the SCU/SCP roles are reversed for the C-STORE. - The SCP may optionally generate - responses to the C-GET with status equal to Pending during the processing of the - C-STORE sub-operations. These C-GET responses indicate the number of remaining - C-STORE sub-operations and the number of C-STORE sub-operations returning the status - of Success, Warning, and Failed. - + The SCP may optionally generate responses to the C-GET with status equal to Pending during the processing of the C-STORE sub-operations. These C-GET responses indicate the number of remaining C-STORE sub-operations and the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. - When the number of Remaining - C-STORE sub-operations reaches zero, the SCP generates a final response with a - status equal to Success, Warning, Failed, or Refused. This response shall indicate - the number of C-STORE sub-operations returning the status of Success, Warning, and - Failed. If the status of any C-STORE sub-operation was Failed a UID List shall be - returned. - + When the number of Remaining C-STORE sub-operations reaches zero, the SCP generates a final response with a status equal to Success, Warning, Failed, or Refused. This response shall indicate the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. If the status of any C-STORE sub-operation was Failed a UID List shall be returned. - The SCU may cancel the C-GET - service by issuing a C-GET-CANCEL request at any time during the processing of the - C-GET. The SCP terminates all incomplete C-STORE sub-operations and returns a status - of Canceled. - + The SCU may cancel the C-GET service by issuing a C-GET-CANCEL request at any time during the processing of the C-GET. The SCP terminates all incomplete C-STORE sub-operations and returns a status of Canceled. @@ -43971,20 +30893,11 @@
Composite Instance Root Retrieve Information Model Definition - The Composite Instance Root Retrieve Information - Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is - composed of both an Information Model and a DIMSE-C Service Group. - + The Composite Instance Root Retrieve Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. - This SOP Class identifies the class of the - Composite Instance Root Retrieve Information Model (i.e., not the SOP Class of the stored SOP - Instances for which the SCP has information). - + This SOP Class identifies the class of the Composite Instance Root Retrieve Information Model (i.e., not the SOP Class of the stored SOP Instances for which the SCP has information). - Information Model Definitions for Standard SOP - Classes of the Composite Instance Root Retrieve Service are defined in this Annex. A Composite Instance - Root Retrieve Information Model Definition contains: - + Information Model Definitions for Standard SOP Classes of the Composite Instance Root Retrieve Service are defined in this Annex. A Composite Instance Root Retrieve Information Model Definition contains: Entity-Relationship Model Definition @@ -43995,25 +30908,17 @@
Entity-Relationship Model Definition - For any Composite Instance Root Retrieve - Information Model, an Entity-Relationship Model defines a hierarchy of entities, with Attributes - defined for each level in the hierarchy (e.g., Composite Instance, Frame).. - + For any Composite Instance Root Retrieve Information Model, an Entity-Relationship Model defines a hierarchy of entities, with Attributes defined for each level in the hierarchy (e.g., Composite Instance, Frame)..
Attributes Definition - Attributes and matching shall be as defined in - + Attributes and matching shall be as defined in
Standard Composite Instance Root Retrieve Information Model - One standard Composite Instance Root Retrieve - Information Model is defined in this Annex. The Composite Instance Root Retrieve Information Model is - associated with a number of SOP Classes. The following hierarchical Composite Instance Root Retrieve - Information Model is defined: - + One standard Composite Instance Root Retrieve Information Model is defined in this Annex. The Composite Instance Root Retrieve Information Model is associated with a number of SOP Classes. The following hierarchical Composite Instance Root Retrieve Information Model is defined: Composite Instance Root @@ -44021,9 +30926,7 @@
Composite Instance Root Information Model - The Composite Instance Root Information Model - is based upon a two level hierarchy: - + The Composite Instance Root Information Model is based upon a two level hierarchy: Composite Instance @@ -44032,145 +30935,73 @@ Frame - The Composite Instance level is the top level - and contains only the SOP Instance UID. The Frame level is below the Composite Instance level and - contains only the Attributes that refer to a selection of the frames from a single multi-frame image - object. - + The Composite Instance level is the top level and contains only the SOP Instance UID. The Frame level is below the Composite Instance level and contains only the Attributes that refer to a selection of the frames from a single multi-frame image object.
Construction and Interpretation of Frame Range Keys - The following rules for the use of Frame Range - Keys apply to both an SCU creating such keys and to an SCP interpreting them. - + The following rules for the use of Frame Range Keys apply to both an SCU creating such keys and to an SCP interpreting them.
Frame List definitions - The selection of frames to be included in a - new created SOP Instance made in response to a FRAME level Composite Instance Root Retrieve - request shall be defined by one of the mechanisms defined in this section, and the list of - frames so specified shall be referred to as the "Frame List". - + The selection of frames to be included in a new created SOP Instance made in response to a FRAME level Composite Instance Root Retrieve request shall be defined by one of the mechanisms defined in this section, and the list of frames so specified shall be referred to as the "Frame List". - Re-ordering of frames is not - supported, and order of the frames in the Frame List will always be the same as in - the original SOP Instance. - + Re-ordering of frames is not supported, and order of the frames in the Frame List will always be the same as in the original SOP Instance. - New allowable frame selection - mechanisms may be defined in the future by the addition of new SOP Classes - + New allowable frame selection mechanisms may be defined in the future by the addition of new SOP Classes
Simple Frame List - Simple Frame List (0008,1161) is a - multi-valued Attribute containing a list of frame numbers, each specifying a frame to be - included in the returned object. The first frame of the source instance shall be denoted as - frame number 1. - - The frame numbers in the list shall not - contain any duplicates, and shall increase monotonically. - + Simple Frame List (0008,1161) is a multi-valued Attribute containing a list of frame numbers, each specifying a frame to be included in the returned object. The first frame of the source instance shall be denoted as frame number 1. + The frame numbers in the list shall not contain any duplicates, and shall increase monotonically. - Due to the use of UL for this - element, a maximum of 16383 values may be specified, as only a 2 byte length is - available when an explicit VR Transfer Syntax is used. - + Due to the use of UL for this element, a maximum of 16383 values may be specified, as only a 2 byte length is available when an explicit VR Transfer Syntax is used.
Calculated Frame List - Calculated Frame List (0008,1162) is a - multi-valued Attribute containing a list of 3-tuples, each representing a sub-range of - frames to be included in the returned object. The first frame of the source instance shall - be denoted as frame number 1.For each 3-tuple: . - + Calculated Frame List (0008,1162) is a multi-valued Attribute containing a list of 3-tuples, each representing a sub-range of frames to be included in the returned object. The first frame of the source instance shall be denoted as frame number 1.For each 3-tuple: . - The first number shall be the - frame number of the first frame of the sub-range. - + The first number shall be the frame number of the first frame of the sub-range. - The second number shall be the - upper limit of the sub-range, and shall be greater than or equal to the first - number. - + The second number shall be the upper limit of the sub-range, and shall be greater than or equal to the first number. - The third number shall be the - increment between requested frames of the sub-range. This shall be greater than - zero. - + The third number shall be the increment between requested frames of the sub-range. This shall be greater than zero. - The difference between the first and - second numbers is not required to be an exact multiple of the increment. - - If the difference between the first and - second numbers is an exact multiple of the increment, then the last frame of the sub-range - shall be the second number. - - If the first number is greater than the - number of frames in the referenced SOP Instance then that sub-range shall be ignored. - - The sub-ranges shall be non-overlapping - such that the sequence of frame numbers determined by concatenating all the sub-ranges shall - not contain any duplicates, and shall increase monotonically. A value of FFFFFFFFH or any - value greater than the number of frames in the referenced SOP Instance as the second value - shall denote the end of the set of frames in the referenced SOP Instance, and may only occur - in the last 3-tuple. - + The difference between the first and second numbers is not required to be an exact multiple of the increment. + If the difference between the first and second numbers is an exact multiple of the increment, then the last frame of the sub-range shall be the second number. + If the first number is greater than the number of frames in the referenced SOP Instance then that sub-range shall be ignored. + The sub-ranges shall be non-overlapping such that the sequence of frame numbers determined by concatenating all the sub-ranges shall not contain any duplicates, and shall increase monotonically. A value of FFFFFFFFH or any value greater than the number of frames in the referenced SOP Instance as the second value shall denote the end of the set of frames in the referenced SOP Instance, and may only occur in the last 3-tuple. - For example, if the Calculated - Frame List contains 6 values, 2, 9, 3, 12, FFFFFFFFH, 5 and is applied to an Instance - containing 25 frames. The resulting Frame List will contain the values 2, 5, 8, 12, 17 - and 22. - + For example, if the Calculated Frame List contains 6 values, 2, 9, 3, 12, FFFFFFFFH, 5 and is applied to an Instance containing 25 frames. The resulting Frame List will contain the values 2, 5, 8, 12, 17 and 22.
Time Range - Time Range (0008,1163) contains the - start and end times to be included in the returned object. Times are in seconds, relative to - the value of the Content Time (0008,0033) in the parent object. - - The range shall include all frames - between the specified times including any frames at the specified times. - - The range may be expanded as a - consequence of the format in which the information is stored. Where such expansion occurs, - any embedded audio data shall be similarly selected. Under all circumstances, the returned - Composite SOP Instance shall retain the relationship between image and audio data. - + Time Range (0008,1163) contains the start and end times to be included in the returned object. Times are in seconds, relative to the value of the Content Time (0008,0033) in the parent object. + The range shall include all frames between the specified times including any frames at the specified times. + The range may be expanded as a consequence of the format in which the information is stored. Where such expansion occurs, any embedded audio data shall be similarly selected. Under all circumstances, the returned Composite SOP Instance shall retain the relationship between image and audio data. - For MPEG-2, MPEG-4 AVC/H.264 and - HEVC/H.265 this would be to the nearest surrounding Key Frames. - + For MPEG-2, MPEG-4 AVC/H.264 and HEVC/H.265 this would be to the nearest surrounding Key Frames. - For JPEG 2000 Part 2, this would be to - nearest surrounding precinct or tile boundary - - Time Range shall only be used to - specify extraction from SOP instances where the times of frames can be ascertained using one - or more of the following Attributes: - + For JPEG 2000 Part 2, this would be to nearest surrounding precinct or tile boundary + Time Range shall only be used to specify extraction from SOP instances where the times of frames can be ascertained using one or more of the following Attributes: Frame Time (0018,1063) - Frame Time Vector (0018,1065) - + Frame Time Vector (0018,1065) - Frame Reference DateTime - (0018,9151) in the Frame Content Sequence (0020,9111) - + Frame Reference DateTime (0018,9151) in the Frame Content Sequence (0020,9111)
@@ -44178,125 +31009,62 @@
New Instance Creation At the Frame Level - When a C-MOVE or C-GET operation is performed - on a source Composite Instance at the FRAME level then the SCP shall create a new Composite Instance - according to the following rules: - + When a C-MOVE or C-GET operation is performed on a source Composite Instance at the FRAME level then the SCP shall create a new Composite Instance according to the following rules: - The new Composite Instance shall be - extracted from the source Composite Instance specified by the SOP Instance UID Unique Key - present at the Composite Instance Level. - + The new Composite Instance shall be extracted from the source Composite Instance specified by the SOP Instance UID Unique Key present at the Composite Instance Level. - The new Composite Instance shall be an - instance of the same SOP Class as the source Composite Instance. - + The new Composite Instance shall be an instance of the same SOP Class as the source Composite Instance. - The new Composite Instance shall have a - new SOP Instance UID. - + The new Composite Instance shall have a new SOP Instance UID. - The new Composite Instance shall be a - valid SOP Instance. - + The new Composite Instance shall be a valid SOP Instance. - The new Composite Instance is required to - be internally consistent and valid. This may require the SCP to make consistent modification of - any Attributes that reference frames or the relationship between them such as start time, time - offsets, and modifying the Per-frame Functional Group Sequence (5200,9230). - + The new Composite Instance is required to be internally consistent and valid. This may require the SCP to make consistent modification of any Attributes that reference frames or the relationship between them such as start time, time offsets, and modifying the Per-frame Functional Group Sequence (5200,9230). - The new Composite Instance shall - contain the frames from the source Composite Object as requested in the Requested Frame - List. The Requested Frame List shall be interpreted according to the rules in. The frames shall be in the same - order as in the source Composite Instance. - + The new Composite Instance shall contain the frames from the source Composite Object as requested in the Requested Frame List. The Requested Frame List shall be interpreted according to the rules in . The frames shall be in the same order as in the source Composite Instance. - The new Composite Instance shall - include the Frame Extraction Module, which shall contain appropriate Attributes from the - identifier of the C-GET or C-MOVE request that caused this instance to be created. If the - Frame Extraction Module already exists in the source Composite Instance, then a new item - shall be appended as an additional item into the Frame Extraction Sequence. - + The new Composite Instance shall include the Frame Extraction Module, which shall contain appropriate Attributes from the identifier of the C-GET or C-MOVE request that caused this instance to be created. If the Frame Extraction Module already exists in the source Composite Instance, then a new item shall be appended as an additional item into the Frame Extraction Sequence. - The new Composite Instance shall - contain the Contributing Equipment Sequence (0018,A001). If the source Composite Object - contains the Contributing Equipment Sequence, then a new Item shall be appended to the copy - of the sequence in the new Composite Instance, and if the source Composite Object does not - contain the Contributing Equipment Sequence, then it shall be created, containing one new - Item. In either case, the new Item shall describe the equipment that is extracting the - frames, and the Purpose of Reference Code Sequence (0040,A170) within the Item shall - be (109105, DCM, "Frame Extracting - Equipment"). - + The new Composite Instance shall contain the Contributing Equipment Sequence (0018,A001). If the source Composite Object contains the Contributing Equipment Sequence, then a new Item shall be appended to the copy of the sequence in the new Composite Instance, and if the source Composite Object does not contain the Contributing Equipment Sequence, then it shall be created, containing one new Item. In either case, the new Item shall describe the equipment that is extracting the frames, and the Purpose of Reference Code Sequence (0040,A170) within the Item shall be (109105, DCM, "Frame Extracting Equipment"). - The existing General Equipment Module - cannot be used to hold details of the creating equipment, as it is a Series level Module. The - new Composite Instance is part of the same Series as the source Instance, and therefore the - Series level information cannot be altered. - + The existing General Equipment Module cannot be used to hold details of the creating equipment, as it is a Series level Module. The new Composite Instance is part of the same Series as the source Instance, and therefore the Series level information cannot be altered. - The new Composite Instance shall have - the same Patient, Study and Series level information as the source Instance, including Study - and Series Instance UIDs. - + The new Composite Instance shall have the same Patient, Study and Series level information as the source Instance, including Study and Series Instance UIDs. - The new Composite Instance shall have - the same values for the Attributes of the Image Pixel Module of the source Composite - Instance except that the Pixel Data Provider URL (0028,7FE0) Attribute shall not be - present,Pixel Data (7FE0,0010) shall be replaced by the subset of frames, as specified in - , and Number of Frames (0028,0008) - shall contain the number of frames in the new Composite Instance. - + The new Composite Instance shall have the same values for the Attributes of the Image Pixel Module of the source Composite Instance except that the Pixel Data Provider URL (0028,7FE0) Attribute shall not be present,Pixel Data (7FE0,0010) shall be replaced by the subset of frames, as specified in , and Number of Frames (0028,0008) shall contain the number of frames in the new Composite Instance. - The new Composite Instance shall have - the same values for other Type 1 and Type 2 Image level Attributes that are not otherwise - specified. Other Attributes may be included in the new Composite Instance if consistent with - the new Composite Instance. - + The new Composite Instance shall have the same values for other Type 1 and Type 2 Image level Attributes that are not otherwise specified. Other Attributes may be included in the new Composite Instance if consistent with the new Composite Instance. - In most cases private Attributes should not - be copied unless their full significance is known. See - - for more guidance. - + In most cases private Attributes should not be copied unless their full significance is known. See for more guidance. - The new Composite Instance shall not be - contained in a Concatenation. This means that it shall not contain a Concatenation UID - (0020,9161) Attribute or other Concatenation Attributes. If the existing Composite Instance - contains such Attributes, they shall not be included in the new Composite Instance. - + The new Composite Instance shall not be contained in a Concatenation. This means that it shall not contain a Concatenation UID (0020,9161) Attribute or other Concatenation Attributes. If the existing Composite Instance contains such Attributes, they shall not be included in the new Composite Instance.
DIMSE-C Service Groups - A single DIMSE-C Service is used in the - construction of SOP Classes of the Composite Instance Root Retrieve Service. The following DIMSE-C - operation is used: - + A single DIMSE-C Service is used in the construction of SOP Classes of the Composite Instance Root Retrieve Service. The following DIMSE-C operation is used: C-MOVE @@ -44307,109 +31075,53 @@
C-MOVE Operation - SCUs of the Composite Instance Root Retrieve - Service shall generate retrievals using the C-MOVE operation as described in - .The C-MOVE operation allows an application entity to instruct another application entity to - transfer stored SOP Instances or new SOP Instances extracted from such stored SOP Instances to - another application entity using the C-STORE operation. Support for the C-MOVE service shall be - agreed upon at Association establishment time by both the SCU and SCP of the C-MOVE in order for a - C-MOVE operation to occur over the Association. The C-STORE sub-operations shall always be - accomplished over an Association different from the Association that accomplishes the CMOVE - operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage - Service Class. - + SCUs of the Composite Instance Root Retrieve Service shall generate retrievals using the C-MOVE operation as described in .The C-MOVE operation allows an application entity to instruct another application entity to transfer stored SOP Instances or new SOP Instances extracted from such stored SOP Instances to another application entity using the C-STORE operation. Support for the C-MOVE service shall be agreed upon at Association establishment time by both the SCU and SCP of the C-MOVE in order for a C-MOVE operation to occur over the Association. The C-STORE sub-operations shall always be accomplished over an Association different from the Association that accomplishes the CMOVE operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage Service Class. - The application entity that receives the - stored SOP Instances may or may not be the originator of the C-MOVE operation. - + The application entity that receives the stored SOP Instances may or may not be the originator of the C-MOVE operation. - A C-MOVE request may be performed to any level - of the Composite Object Instance Root Retrieve Information Model,and the expected SCP behavior - depends on the level selected. - + A C-MOVE request may be performed to any level of the Composite Object Instance Root Retrieve Information Model,and the expected SCP behavior depends on the level selected.
C-MOVE Service Parameters
SOP Class UID - The SOP Class UID identifies the - Query/Retrieve Information Model against which the C-MOVE is to be performed. Support for - the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by - this C-MOVE operation. - + The SOP Class UID identifies the Query/Retrieve Information Model against which the C-MOVE is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-MOVE operation.
Priority - The Priority Attribute defines the - requested priority of the C-MOVE operation and corresponding C-STORE sub-operations with - respect to other DIMSE operations being performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. The same - priority shall be used for all C-STORE sub-operations. - + The Priority Attribute defines the requested priority of the C-MOVE operation and corresponding C-STORE sub-operations with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP. The same priority shall be used for all C-STORE sub-operations.
Identifier - The C-MOVE request shall contain an - Identifier. The C-MOVE response shall conditionally contain an Identifier as required in - . - + The C-MOVE request shall contain an Identifier. The C-MOVE response shall conditionally contain an Identifier as required in . - The Identifier is specified as U in - the definition of the C-MOVE primitive in - - but is specialized for use with this service. - + The Identifier is specified as U in the definition of the C-MOVE primitive in but is specialized for use with this service.
Request Identifier Structure - An Identifier in a C-MOVE request - shall contain: - + An Identifier in a C-MOVE request shall contain: - the Query/Retrieve Level - (0008,0052) that defines the level of the retrieval - + the Query/Retrieve Level (0008,0052) that defines the level of the retrieval - SOP Instance UID(s) - (0008,0018) - + SOP Instance UID(s) (0008,0018) - One of the Frame Range Keys - if present in the Information Model for the level of the Retrieval - + One of the Frame Range Keys if present in the Information Model for the level of the Retrieval - Conditionally, the - Attribute Query/Retrieve View (0008,0053). This Attribute may be included if - Enhanced Multi-Frame Image Conversion has accepted during Association Extended - Negotiation. It shall not be included otherwise. - + Conditionally, the Attribute Query/Retrieve View (0008,0053). This Attribute may be included if Enhanced Multi-Frame Image Conversion has accepted during Association Extended Negotiation. It shall not be included otherwise. - Specific Character Set (0008,0005) - shall not be present. - - The Keys at each level of the - hierarchy and the values allowable for the level of the retrieval shall be defined in - the SOP Class definition for the Query/Retrieve Information Model. - + Specific Character Set (0008,0005) shall not be present. + The Keys at each level of the hierarchy and the values allowable for the level of the retrieval shall be defined in the SOP Class definition for the Query/Retrieve Information Model.
Status - - defines the status code values that might be returned in a C-MOVE response. General status - code values and fields related to status code values are defined for C-MOVE DIMSE Service in - . - + defines the status code values that might be returned in a C-MOVE response. General status code values and fields related to status code values are defined for C-MOVE DIMSE Service in .
Color Palette SOP Classes
- Color Palette Information - Model - FIND - + Color Palette Information Model - FIND - 1.2.840.10008.5.1.4.39.2 - + 1.2.840.10008.5.1.4.39.2
- Color Palette Information - Model - MOVE - + Color Palette Information Model - MOVE - 1.2.840.10008.5.1.4.39.3 - + 1.2.840.10008.5.1.4.39.3
- Color Palette Information - Model - GET - + Color Palette Information Model - GET - 1.2.840.10008.5.1.4.39.4 - + 1.2.840.10008.5.1.4.39.4
@@ -44434,9 +31146,7 @@ Failure
C-MOVE Response Status Values for Composite Instance Root Retrieve
- Refused: Out of - resources - Unable to calculate number of matches - + Refused: Out of resources - Unable to calculate number of matches A701 @@ -44447,9 +31157,7 @@
- Refused: Out of - resources - Unable to perform sub-operations - + Refused: Out of resources - Unable to perform sub-operations A702 @@ -44463,9 +31171,7 @@
- Refused: Move - Destination unknown - + Refused: Move Destination unknown A801 @@ -44476,9 +31182,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -44490,9 +31194,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -44504,9 +31206,7 @@
- Failed: None of the - frames requested were found in the SOP Instance - + Failed: None of the frames requested were found in the SOP Instance AA00 @@ -44517,9 +31217,7 @@
- Failed: Unable to - create new object for this SOP Class - + Failed: Unable to create new object for this SOP Class AA01 @@ -44530,9 +31228,7 @@
- Failed: Unable to - extract frames - + Failed: Unable to extract frames AA02 @@ -44543,9 +31239,7 @@
- Failed: Time-based - request received for a non-time-based original SOP Instance. - + Failed: Time-based request received for a non-time-based original SOP Instance. AA03 @@ -44556,9 +31250,7 @@
- Failed: Invalid - Request - + Failed: Invalid Request AA04 @@ -44573,9 +31265,7 @@ Cancel - Sub-operations - terminated due to Cancel Indication - + Sub-operations terminated due to Cancel Indication FE00 @@ -44592,9 +31282,7 @@ Warning - Sub-operations Complete - - One or more Failures or Warnings - + Sub-operations Complete - One or more Failures or Warnings B000 @@ -44611,9 +31299,7 @@ Success - Sub-operations Complete - - No Failures or Warnings - + Sub-operations Complete - No Failures or Warnings 0000 @@ -44630,9 +31316,7 @@ Pending - Sub-operations are - continuing - + Sub-operations are continuing FF00 @@ -44646,340 +31330,172 @@
- Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: - Unable to process" Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: Unable to process" Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
Number of Remaining Sub-Operations - Inclusion of the Number of Remaining - Sub-operations shall be as specified in - + Inclusion of the Number of Remaining Sub-operations shall be as specified in
Number of Completed Sub-Operations - Inclusion of the Number of Completed - Sub-operations shall be as specified in - + Inclusion of the Number of Completed Sub-operations shall be as specified in
Number of Failed Sub-Operations - Inclusion of the Number of Failed - Sub-operations shall be as specified in - + Inclusion of the Number of Failed Sub-operations shall be as specified in
Number of Warning Sub-Operations - Inclusion of the Number of Warning - Sub-operations shall be as specified in. - + Inclusion of the Number of Warning Sub-operations shall be as specified in .
C-MOVE SCU Behavior
Baseline Behavior of SCU - An SCU conveys the following semantics - with a C-MOVE request: - + An SCU conveys the following semantics with a C-MOVE request: - If the Retrieve Level - (0000,0052) is IMAGE, the SCU shall specify one SOP Instance UID or a list of SOP - Instance UIDs. - + If the Retrieve Level (0000,0052) is IMAGE, the SCU shall specify one SOP Instance UID or a list of SOP Instance UIDs. - If the Retrieve Level - (0000,0052) is FRAME, the SCU shall specify the single SOP Instance UID of the item - from which the new Composite SOP Instance should be extracted and the requested - Frame List. The Requested Frame List shall be constructed as defined in. - + If the Retrieve Level (0000,0052) is FRAME, the SCU shall specify the single SOP Instance UID of the item from which the new Composite SOP Instance should be extracted and the requested Frame List. The Requested Frame List shall be constructed as defined in . - The SCU shall accept C-MOVE - responses with status equal to Pending during the processing of the C-STORE - sub-operations. These responses indicate the number of Remaining, Completed, Failed - and Warning C-STORE sub-operations. - + The SCU shall accept C-MOVE responses with status equal to Pending during the processing of the C-STORE sub-operations. These responses indicate the number of Remaining, Completed, Failed and Warning C-STORE sub-operations. - The SCU shall interpret a - C-MOVE response with a status equal to Success, Warning, Failure, or Refused as a - final response. The final response indicates the number of Completed sub-operations - and the number of Failed C-STORE sub-operations resulting from the C-MOVE operation. - The SCU shall interpret a status of: - + The SCU shall interpret a C-MOVE response with a status equal to Success, Warning, Failure, or Refused as a final response. The final response indicates the number of Completed sub-operations and the number of Failed C-STORE sub-operations resulting from the C-MOVE operation. The SCU shall interpret a status of: - Success to indicate - that all sub-operations were successfully completed - + Success to indicate that all sub-operations were successfully completed - Failure or Refused to - indicate all sub-operations were unsuccessful - + Failure or Refused to indicate all sub-operations were unsuccessful - Warning in all other - cases. The Number of Completed Sub-Operations (0000,1021), Number of Warning - Sub-Operations (0000,1023), Number of Failed Sub-Operations (0000,1022) can - be used to obtain more detailed information. - + Warning in all other cases. The Number of Completed Sub-Operations (0000,1021), Number of Warning Sub-Operations (0000,1023), Number of Failed Sub-Operations (0000,1022) can be used to obtain more detailed information. - The SCU may cancel the C-MOVE - operation by issuing a C-MOVE-CANCEL request at any time during the processing of - the C-MOVE request. A C-MOVE response with a status of Canceled shall indicate to - the SCU that the retrieve was canceled. Optionally, the C-MOVE response with a - status of Canceled shall indicate the number of Completed, Failed, and Warning - C-STORE sub-operations. If present, the Remaining sub-operations count shall contain - the number of C-STORE sub-operations that were not initiated due to the - C-MOVE-CANCEL request. - + The SCU may cancel the C-MOVE operation by issuing a C-MOVE-CANCEL request at any time during the processing of the C-MOVE request. A C-MOVE response with a status of Canceled shall indicate to the SCU that the retrieve was canceled. Optionally, the C-MOVE response with a status of Canceled shall indicate the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-MOVE-CANCEL request. - For FRAME level C-MOVE operations, - the application receiving the C-STORE sub-operations will receive a new SOP Instance - with a different SOP Instance UID from the one included in the C-MOVE request. If it is - required to link the received instance to the request, then it may be necessary to - inspect the Frame Extraction Sequence of the instance received, to compare the original - Instance UID and Requested Frame List to those in the request. - + For FRAME level C-MOVE operations, the application receiving the C-STORE sub-operations will receive a new SOP Instance with a different SOP Instance UID from the one included in the C-MOVE request. If it is required to link the received instance to the request, then it may be necessary to inspect the Frame Extraction Sequence of the instance received, to compare the original Instance UID and Requested Frame List to those in the request.
Extended Behavior of SCU - The extended behavior of the SCU shall - be as specified in, except that - Relational-retrieve shall not be supported. - + The extended behavior of the SCU shall be as specified in , except that Relational-retrieve shall not be supported.
C-MOVE SCP Behavior
Baseline Behavior of SCP - An SCP conveys the following semantics - with a C-MOVE response: - + An SCP conveys the following semantics with a C-MOVE response: - If the Retrieve Level - (0000,0052) is IMAGE the SCP shall identify a set of Entities at the level of the - transfer based upon the values in the Unique Keys in the Identifier of the C-MOVE - request. - + If the Retrieve Level (0000,0052) is IMAGE the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-MOVE request. - If the Retrieve Level - (0000,0052) is FRAME, the SCP shall create a new Composite Instance according to the - rules in. The newly created - SOP Instance shall be treated in the same manner as the set of Entities identified - above. - + If the Retrieve Level (0000,0052) is FRAME, the SCP shall create a new Composite Instance according to the rules in . The newly created SOP Instance shall be treated in the same manner as the set of Entities identified above. - The SCP shall either re-use an - established and compatible Association or establish a new Association for the - C-STORE sub-operations - + The SCP shall either re-use an established and compatible Association or establish a new Association for the C-STORE sub-operations - The SCP shall initiate C-STORE - sub-operations over the Association for the identified or newly created SOP - Instances. - + The SCP shall initiate C-STORE sub-operations over the Association for the identified or newly created SOP Instances. - A sub-operation is considered a - Failure if the SCP is required to create new SOP Instance, but is unable to do so - due to inconsistencies in the Frame Range Keys, or if the resulting SOP Instance - would not be valid. - + A sub-operation is considered a Failure if the SCP is required to create new SOP Instance, but is unable to do so due to inconsistencies in the Frame Range Keys, or if the resulting SOP Instance would not be valid. - Optionally, the SCP may - generate responses to the C-MOVE with status equal to Pending during the processing - of the C-STORE sub-operations. These responses shall indicate the number of - Remaining, Completed, Failure, and Warning C-STORE sub-operations. - + Optionally, the SCP may generate responses to the C-MOVE with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the number of Remaining, Completed, Failure, and Warning C-STORE sub-operations. - When the number of Remaining - sub-operations reaches zero, the SCP shall generate a final response with a status - equal to Success, Warning or Failed. The status contained in the C-MOVE response - shall contain: - + When the number of Remaining sub-operations reaches zero, the SCP shall generate a final response with a status equal to Success, Warning or Failed. The status contained in the C-MOVE response shall contain: - Success if all - sub-operations were successfully completed - + Success if all sub-operations were successfully completed - Failure if all - sub-operations were unsuccessful - + Failure if all sub-operations were unsuccessful - Warning in all other - cases. - + Warning in all other cases. - The SCP may receive a - C-MOVE-CANCEL request at any time during the processing of the C-MOVE request. The - SCP shall interrupt all C-STORE sub-operation processing and return a status of - Canceled in the C-MOVE response. The C-MOVE response with a status of Canceled shall - contain the number of Completed, Failed, and Warning C-STORE sub-operations. If - present, the Remaining sub-operations count shall contain the number of C-STORE - sub-operations that were not initiated due to the C-MOVE-CANCEL request. - + The SCP may receive a C-MOVE-CANCEL request at any time during the processing of the C-MOVE request. The SCP shall interrupt all C-STORE sub-operation processing and return a status of Canceled in the C-MOVE response. The C-MOVE response with a status of Canceled shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-MOVE-CANCEL request. - If the SCP manages images in - multiple alternate encodings (see), only one of the - alternate encodings of an image shall be used as the existing SOP Instance from - which frames are to be extracted. - + If the SCP manages images in multiple alternate encodings (see ), only one of the alternate encodings of an image shall be used as the existing SOP Instance from which frames are to be extracted.
Extended Behavior of SCP - The extended behavior of the SCP shall - be as specified in, except that - Relational-retrieve shall not be supported. - + The extended behavior of the SCP shall be as specified in , except that Relational-retrieve shall not be supported.
C-GET Operation - SCUs of the Composite Instance Root Retrieve - Service shall generate retrievals using the C-GET operation as described in - . The C-GET operation allows an application entity to instruct another application entity to - transfer stored SOP Instances or new SOP Instances derived from such stored SOP Instances to the - initiating application entity using the C-STORE operation. Support for the C-GET service shall be - agreed upon at Association establishment time by both the SCU and SCP of the C-GET in order for a - C-GET operation to occur over the Association. The C-STORE Sub-operations shall be accomplished on - the same Association as the C-GET operation. Hence, the SCP of the Query/Retrieve Service Class - serves as the SCU of the Storage Service Class. - + SCUs of the Composite Instance Root Retrieve Service shall generate retrievals using the C-GET operation as described in . The C-GET operation allows an application entity to instruct another application entity to transfer stored SOP Instances or new SOP Instances derived from such stored SOP Instances to the initiating application entity using the C-STORE operation. Support for the C-GET service shall be agreed upon at Association establishment time by both the SCU and SCP of the C-GET in order for a C-GET operation to occur over the Association. The C-STORE Sub-operations shall be accomplished on the same Association as the C-GET operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage Service Class. - The Application Entity that receives the - stored SOP Instances is always the originator of the C-GET operation. - + The Application Entity that receives the stored SOP Instances is always the originator of the C-GET operation. - A C-GET request may be performed to any level - of the Composite Instance Root Retrieve Information Model, and the expected SCP behavior depends on - the level selected. - + A C-GET request may be performed to any level of the Composite Instance Root Retrieve Information Model, and the expected SCP behavior depends on the level selected.
C-GET Service Parameters
SOP Class UID - The SOP Class UID identifies the - Query/Retrieve Information Model against which the C-GET is to be performed. Support for the - SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this - C-GET operation. - + The SOP Class UID identifies the Query/Retrieve Information Model against which the C-GET is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-GET operation.
Priority - The Priority Attribute defines the - requested priority of the C-GET operation and corresponding C-STORE sub-operations with - respect to other DIMSE operations being performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. The same - priority shall be used for all C-STORE sub-operations. - + The Priority Attribute defines the requested priority of the C-GET operation and corresponding C-STORE sub-operations with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP. The same priority shall be used for all C-STORE sub-operations.
Identifier - The C-GET request shall contain an - Identifier. The C-GET response shall conditionally contain an Identifier as required in. - + The C-GET request shall contain an Identifier. The C-GET response shall conditionally contain an Identifier as required in . - The Identifier is specified as U in - the definition of the C-GET primitive in - - but is specialized for use with this service. - + The Identifier is specified as U in the definition of the C-GET primitive in but is specialized for use with this service.
Request Identifier Structure - An Identifier in a C-GET request - shall contain: - + An Identifier in a C-GET request shall contain: - the Query/Retrieve Level - (0008,0052) that defines the level of the retrieval - + the Query/Retrieve Level (0008,0052) that defines the level of the retrieval - SOP Instance UID(s) - (0008,0018) - + SOP Instance UID(s) (0008,0018) - One of the Frame Range Keys - if present in the Information Model for the level of the Retrieval - + One of the Frame Range Keys if present in the Information Model for the level of the Retrieval - Conditionally, the - Attribute Query/Retrieve View (0008,0053). This Attribute may be included if - Enhanced Multi-Frame Image Conversion has accepted during Association Extended - Negotiation. It shall not be included otherwise. - + Conditionally, the Attribute Query/Retrieve View (0008,0053). This Attribute may be included if Enhanced Multi-Frame Image Conversion has accepted during Association Extended Negotiation. It shall not be included otherwise. - Specific Character Set (0008,0005) - shall not be present. - - The Keys at each level of the - hierarchy and the values allowable for the level of the retrieval shall be defined in - the SOP Class definition for the Query/Retrieve Information Model. - + Specific Character Set (0008,0005) shall not be present. + The Keys at each level of the hierarchy and the values allowable for the level of the retrieval shall be defined in the SOP Class definition for the Query/Retrieve Information Model.
Status - The status code values that might be - returned in a C-GET response shall be as specified in - + The status code values that might be returned in a C-GET response shall be as specified in @@ -45005,9 +31521,7 @@ Failure
C-GET Response Status Values for Composite Instance Root Retrieve
- Refused: Out of - resources - Unable to calculate number of matches - + Refused: Out of resources - Unable to calculate number of matches A701 @@ -45018,9 +31532,7 @@
- Refused: Out of - resources - Unable to perform sub-operations - + Refused: Out of resources - Unable to perform sub-operations A702 @@ -45034,9 +31546,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -45048,9 +31558,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -45062,9 +31570,7 @@
- Failed: None of the - frames requested were found in the SOP Instance - + Failed: None of the frames requested were found in the SOP Instance AA00 @@ -45075,9 +31581,7 @@
- Failed: Unable to - create new object for this SOP Class - + Failed: Unable to create new object for this SOP Class AA01 @@ -45088,9 +31592,7 @@
- Failed: Unable to - extract frames - + Failed: Unable to extract frames AA02 @@ -45101,9 +31603,7 @@
- Failed: Time-based - request received for a non-time-based original SOP Instance. - + Failed: Time-based request received for a non-time-based original SOP Instance. AA03 @@ -45114,9 +31614,7 @@
- Failed: Invalid - Request - + Failed: Invalid Request AA04 @@ -45131,9 +31629,7 @@ Cancel - Sub-operations - terminated due to Cancel Indication - + Sub-operations terminated due to Cancel Indication FE00 @@ -45150,9 +31646,7 @@ Warning - Sub-operations Complete - - One or more Failures or Warnings - + Sub-operations Complete - One or more Failures or Warnings B000 @@ -45169,9 +31663,7 @@ Success - Sub-operations Complete - - No Failures or Warnings - + Sub-operations Complete - No Failures or Warnings 0000 @@ -45188,9 +31680,7 @@ Pending - Sub-operations are - continuing - + Sub-operations are continuing FF00 @@ -45207,323 +31697,162 @@
Number of Remaining Sub-Operations - Inclusion of the Number of Remaining - Sub-operations shall be as specified in - + Inclusion of the Number of Remaining Sub-operations shall be as specified in
Number of Completed Sub-Operations - Inclusion of the Number of Completed - Sub-operations shall be as specified in - + Inclusion of the Number of Completed Sub-operations shall be as specified in
Number of Failed Sub-Operations - Inclusion of the Number of Failed - Sub-operations shall be as specified in - + Inclusion of the Number of Failed Sub-operations shall be as specified in
Number of Warning Sub-Operations - Inclusion of the Number of Warning - Sub-operations shall be as specified in. - + Inclusion of the Number of Warning Sub-operations shall be as specified in .
C-GET SCU Behavior
Baseline Behavior of SCU - An SCU conveys the following semantics - with a C-GET request: - + An SCU conveys the following semantics with a C-GET request: - If the Retrieve Level - (0000,0052) is IMAGE, the SCU shall specify one SOP Instance UID or a list of SOP - Instance UIDs. - + If the Retrieve Level (0000,0052) is IMAGE, the SCU shall specify one SOP Instance UID or a list of SOP Instance UIDs. - If the Retrieve Level - (0000,0052) is FRAME, the SCU shall specify the single SOP Instance UID of the item - from which the new Composite SOP Instance should be extracted and the Requested - Frame List. The Requested Frame List shall be constructed as a Frame List as defined - in. - + If the Retrieve Level (0000,0052) is FRAME, the SCU shall specify the single SOP Instance UID of the item from which the new Composite SOP Instance should be extracted and the Requested Frame List. The Requested Frame List shall be constructed as a Frame List as defined in . - The SCU shall have proposed - sufficient presentation contexts at Association establishment time to accommodate - expected C-STORE sub-operations that will occur over the same Association. The SCU - of the Query/Retrieve Service Class shall serve as the SCP of the Storage Service - Class. - + The SCU shall have proposed sufficient presentation contexts at Association establishment time to accommodate expected C-STORE sub-operations that will occur over the same Association. The SCU of the Query/Retrieve Service Class shall serve as the SCP of the Storage Service Class. - The SCU shall accept C-GET - responses with status equal to Pending during the processing of the C-STORE - sub-operations. These responses indicate the number of Remaining, Completed, Failed - and Warning C-STORE sub-operations. - + The SCU shall accept C-GET responses with status equal to Pending during the processing of the C-STORE sub-operations. These responses indicate the number of Remaining, Completed, Failed and Warning C-STORE sub-operations. - The SCU shall interpret a C-GET - response with a status equal to Success, Warning, Failure, or Refused as a final - response. The final response indicates the number of Completed sub-operations and - the number of Failed C-STORE sub-operations resulting from the C-GET operation. The - SCU shall interpret a status of: - + The SCU shall interpret a C-GET response with a status equal to Success, Warning, Failure, or Refused as a final response. The final response indicates the number of Completed sub-operations and the number of Failed C-STORE sub-operations resulting from the C-GET operation. The SCU shall interpret a status of: - Success to indicate - that all sub-operations were successfully completed - + Success to indicate that all sub-operations were successfully completed - Failure or Refused to - indicate all sub-operations were unsuccessful - + Failure or Refused to indicate all sub-operations were unsuccessful - Warning in all other - cases. The Number of Completed Sub-Operations (0000,1021), Number of Warning - Sub-Operations (0000,1023), Number of Failed Sub-Operations (0000,1022) can - be used to obtain more detailed information. - + Warning in all other cases. The Number of Completed Sub-Operations (0000,1021), Number of Warning Sub-Operations (0000,1023), Number of Failed Sub-Operations (0000,1022) can be used to obtain more detailed information. - The SCU may cancel the C-GET - operation by issuing a C-GET-CANCEL request at any time during the processing of the - C-GET request. A C-GET response with a status of Canceled shall indicate to the SCU - that the retrieve was canceled. Optionally, the C-GET response with a status of - Canceled shall indicate the number of Completed, Failed, and Warning C-STORE - sub-operations. If present, the Remaining sub-operations count shall contain the - number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL - request. - + The SCU may cancel the C-GET operation by issuing a C-GET-CANCEL request at any time during the processing of the C-GET request. A C-GET response with a status of Canceled shall indicate to the SCU that the retrieve was canceled. Optionally, the C-GET response with a status of Canceled shall indicate the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL request.
Extended Behavior of SCU - The extended behavior of the SCU shall - be as specified in, except that - Relational-retrieve shall not be supported. - + The extended behavior of the SCU shall be as specified in , except that Relational-retrieve shall not be supported.
C-GET SCP Behavior
Baseline Behavior of SCP - An SCP conveys the following semantics - with a C-GET response: - + An SCP conveys the following semantics with a C-GET response: - If the Retrieve Level - (0000,0052) is IMAGE the SCP shall identify a set of Entities at the level of the - transfer based upon the values in the Unique Keys in the Identifier of the C-GET - request. - + If the Retrieve Level (0000,0052) is IMAGE the SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-GET request. - If the Retrieve Level - (0000,0052) is FRAME, the SCP shall create a new Composite Instance according to the - rules in. The newly created - SOP Instance shall be treated in the same manner as the set of Entities identified - above. - + If the Retrieve Level (0000,0052) is FRAME, the SCP shall create a new Composite Instance according to the rules in . The newly created SOP Instance shall be treated in the same manner as the set of Entities identified above. - The SCP shall initiate C-STORE - sub-operations for the identified or newly created SOP Instances. The SCP of the - Query/Retrieve Service Class shall serve as an SCU of the Storage Service Class. - + The SCP shall initiate C-STORE sub-operations for the identified or newly created SOP Instances. The SCP of the Query/Retrieve Service Class shall serve as an SCU of the Storage Service Class. - The SCP shall initiate C-STORE - sub-operations over the same Association for all identified or newly created SOP - Instances specified in the C-GET request. - + The SCP shall initiate C-STORE sub-operations over the same Association for all identified or newly created SOP Instances specified in the C-GET request. - A sub-operation is considered a - Failure if the SCP is required to create new SOP Instance, but is unable to do so - due to inconsistencies in the Frame Range Keys, or if the resulting SOP Instance - would not be valid. - + A sub-operation is considered a Failure if the SCP is required to create new SOP Instance, but is unable to do so due to inconsistencies in the Frame Range Keys, or if the resulting SOP Instance would not be valid. - A sub-operation is considered a - Failure if the SCP is unable to initiate a C-STORE sub-operation because the - Query/Retrieve SCU did not offer an appropriate presentation context for a given - stored SOP Instance. - + A sub-operation is considered a Failure if the SCP is unable to initiate a C-STORE sub-operation because the Query/Retrieve SCU did not offer an appropriate presentation context for a given stored SOP Instance. - Optionally, the SCP may - generate responses to the C-GET with status equal to Pending during the processing - of the C-STORE sub-operations. These responses shall indicate the number of - Remaining, Completed, Failure, and Warning C-STORE sub-operations. - + Optionally, the SCP may generate responses to the C-GET with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the number of Remaining, Completed, Failure, and Warning C-STORE sub-operations. - When the number of Remaining - sub-operations reaches zero, the SCP shall generate a final response with a status - equal to Success, Warning or Failed. The status contained in the C-GET response - shall contain: - + When the number of Remaining sub-operations reaches zero, the SCP shall generate a final response with a status equal to Success, Warning or Failed. The status contained in the C-GET response shall contain: - Success if all - sub-operations were successfully completed - + Success if all sub-operations were successfully completed - Failure if all - sub-operations were unsuccessful - + Failure if all sub-operations were unsuccessful - Warning in all other - cases. - + Warning in all other cases. - The SCP may receive a - C-GET-CANCEL request at any time during the processing of the C-GET request. The SCP - shall interrupt all C-STORE sub-operation processing and return a status of Canceled - in the C-GET response. The C-GET response with a status of Canceled shall contain - the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the - Remaining sub-operations count shall contain the number of C-STORE sub-operations - that were not initiated due to the C-GET-CANCEL request. - + The SCP may receive a C-GET-CANCEL request at any time during the processing of the C-GET request. The SCP shall interrupt all C-STORE sub-operation processing and return a status of Canceled in the C-GET response. The C-GET response with a status of Canceled shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL request. - If the SCP manages images in - multiple alternate encodings (see), only one of the - alternate encodings of an image shall be used as the existing SOP Instance from - which frames are to be extracted. - + If the SCP manages images in multiple alternate encodings (see ), only one of the alternate encodings of an image shall be used as the existing SOP Instance from which frames are to be extracted.
Extended Behavior of SCP - The extended behavior of the SCP shall - be as specified in, except that - Relational-retrieve shall not be supported. - + The extended behavior of the SCP shall be as specified in , except that Relational-retrieve shall not be supported.
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes - utilize Association establishment negotiation by defining the use of Application Association - Information. See - - for an overview of Association negotiation. - - SOP Classes of the Composite Instance Root Retrieve - Service, which include retrieval services based on the C-MOVE and C-GET operations, use the SCP/SCU Role - Selection Sub-Item to identify the SOP Classes that may be used for retrieval. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes utilize Association establishment negotiation by defining the use of Application Association Information. See for an overview of Association negotiation. + SOP Classes of the Composite Instance Root Retrieve Service, which include retrieval services based on the C-MOVE and C-GET operations, use the SCP/SCU Role Selection Sub-Item to identify the SOP Classes that may be used for retrieval.
Association Negotiation for C-MOVE and C-GET SOP Classes - Rules are as specified in, except that the extended negotiation sub-item, - if used, shall be used as defined in. - + Rules are as specified in , except that the Extended Negotiation sub-item, if used, shall be used as defined in . - Though converted images may be - specified by their SOP Instance UID in the Request Identifier, which is always at or - below the instance level, there remains a need for extended negotiation and - specification of the Query/Retrieve View in order to assure that referential integrity - is maintained within the returned SOP Instances (e.g., that a reference to a SOP - Instance UID is to a converted image or not, as appropriate). - + Though converted images may be specified by their SOP Instance UID in the Request Identifier, which is always at or below the instance level, there remains a need for Extended Negotiation and specification of the Query/Retrieve View in order to assure that referential integrity is maintained within the returned SOP Instances (e.g., that a reference to a SOP Instance UID is to a converted image or not, as appropriate). - Relational-retrieval is not - applicable to these SOP Classes, hence the Extended Negotiation Sub-Item does not - include the use of that byte. - + Relational-retrieval is not applicable to these SOP Classes, hence the Extended Negotiation Sub-Item does not include the use of that byte.
SOP Class Extended Negotiation - The SOP Class Extended Negotiation allows, - at Association establishment, peer DICOM AEs to exchange application Association information - defined by specific SOP Classes. This is achieved by defining the - Service-class-application-information field. The Service-class-application-information field is - used to define support for Enhanced Multi-Frame Image Conversion. - - This negotiation is optional. If absent, - the default condition shall be: - + The SOP Class Extended Negotiation allows, at Association establishment, peer DICOM AEs to exchange application Association information defined by specific SOP Classes. This is achieved by defining the Service-class-application-information field. The Service-class-application-information field is used to define support for Enhanced Multi-Frame Image Conversion. + This negotiation is optional. If absent, the default condition shall be: - no Enhanced Multi-Frame Image - Conversion support - + no Enhanced Multi-Frame Image Conversion support - The Association-requester, for each SOP - Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the - corresponding Abstract Syntax Name (as defined by) - followed by the Service-class-application-information field. This field defines: - + The Association-requestor, for each SOP Class, may use one SOP Class Extended Negotiation Sub-Item. The SOP Class is identified by the corresponding Abstract Syntax Name (as defined by ) followed by the Service-class-application-information field. This field defines: - Enhanced Multi-Frame Image - Conversion support by the Association-requester - + Enhanced Multi-Frame Image Conversion support by the Association-requestor - The Association-acceptor, for each SOP - Class Extended Negotiation Sub-Item offered, either accepts the Association-requester proposal - by returning the same value (1) or turns down the proposal by returning the value (0). - - If the SOP Class Extended Negotiation - Sub-Item is not returned by the Association-acceptor then Enhanced Multi-Frame Image Conversion - is not supported (default condition). - - If the SOP Class Extended Negotiation - Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE - response. - + The Association-acceptor, for each SOP Class Extended Negotiation Sub-Item offered, either accepts the Association-requestor proposal by returning the same value (1) or turns down the proposal by returning the value (0). + If the SOP Class Extended Negotiation Sub-Item is not returned by the Association-acceptor then Enhanced Multi-Frame Image Conversion is not supported (default condition). + If the SOP Class Extended Negotiation Sub-Items do not exist in the A-ASSOCIATE indication they shall be omitted in the A-ASSOCIATE response.
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-RQ) - The SOP Class Extended Negotiation - Sub-Item consists of a sequence of mandatory fields as defined by - . - - defines the Service-class-application-information field for the C-MOVE and C-GET operations. - + The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by . defines the Service-class-application-information field for the C-MOVE and C-GET operations. - + @@ -45547,8 +31875,7 @@ Unused @@ -45556,23 +31883,12 @@ 2 @@ -45580,18 +31896,9 @@
SOP Class Extended Negotiation Sub-Item Structure (A-ASSOCIATE-AC) - The SOP Class Extended Negotiation - Sub-Item consists of a sequence of mandatory fields as defined by - . - - defines the Service-class-application-information field for the C-MOVE and C-GET operations. - + The SOP Class Extended Negotiation Sub-Item consists of a sequence of mandatory fields as defined by . defines the Service-class-application-information field for the C-MOVE and C-GET operations.
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information - Field) - A-ASSOCIATE-RQ - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-RQ
@@ -45533,8 +31862,7 @@ Field Name - Description of Field - + Description of Field
- Reserved - shall be 0 - + Reserved - shall be 0
- Enhanced Multi-Frame - Image Conversion - + Enhanced Multi-Frame Image Conversion - This byte field defines - whether or not the Attribute Query/Retrieve View (0008,0053) shall be used - to adjust the view returned in queries to consider conversion to or from - Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - Query/Retrieve View - not supported - - 1 - Query/Retrieve View - supported - + This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Query/Retrieve View not supported + 1 - Query/Retrieve View supported
- + @@ -45615,9 +31921,7 @@ Unused @@ -45625,23 +31929,12 @@ 2 @@ -45654,10 +31947,7 @@ SOP Class Definitions
Composite Instance Root SOP Class Group - In the Composite Instance Root Retrieve Only - Information Model, the information is arranged into two levels that correspond to one of the two - values in element (0008,0052) shown in. - + In the Composite Instance Root Retrieve Only Information Model, the information is arranged into two levels that correspond to one of the two values in element (0008,0052) shown in .
SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information - Field) - A-ASSOCIATE-AC - SOP Class Extended Negotiation Sub-Item (Service-Class-Application-Information Field) - A-ASSOCIATE-AC
@@ -45601,8 +31908,7 @@ Field Name - Description of Field - + Description of Field
- Reserved - shall not be - tested. - + Reserved - shall not be tested.
- Enhanced Multi-Frame - Image Conversion - + Enhanced Multi-Frame Image Conversion - This byte field defines - whether or not the Attribute Query/Retrieve View (0008,0053) shall be used - to adjust the view returned in queries to consider conversion to or from - Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary - integer and shall use one of the following values - - 0 - Query/Retrieve View - not supported - - 1 - Query/Retrieve View - supported - + This byte field defines whether or not the Attribute Query/Retrieve View (0008,0053) shall be used to adjust the view returned in queries to consider conversion to or from Enhanced Multi-Frame Images. It shall be encoded as an unsigned binary integer and shall use one of the following values + 0 - Query/Retrieve View not supported + 1 - Query/Retrieve View supported
@@ -45690,19 +31980,13 @@
Retrieve Level Values for Composite Instance Root Retrieve
- The use of the word "IMAGE" rather than - "Composite Instance" is historical to allow backward compatibility with previous editions of the - Standard. It should not be taken to mean that Composite Instances of other than image type are - not included at the level indicated by the value IMAGE. - + The use of the word "IMAGE" rather than "Composite Instance" is historical to allow backward compatibility with previous editions of the Standard. It should not be taken to mean that Composite Instances of other than image type are not included at the level indicated by the value IMAGE.
Composite Instance Root Retrieve Only Information Model
E/R Model - The Composite Instance Root Retrieve - Only Information Model may be represented by the entity relationship diagram shown in - + The Composite Instance Root Retrieve Only Information Model may be represented by the entity relationship diagram shown in
@@ -45719,14 +32003,9 @@
Composite Instance Level - - defines the keys at the Composite Instance level of the Composite Instance Root - Query/Retrieve Information model. - + defines the keys at the Composite Instance level of the Composite Instance Root Query/Retrieve Information model. - + @@ -45759,15 +32037,9 @@
Frame Level - - defines the keys at the Frame level of the Composite Instance Root Query/Retrieve - Information Model. One and only one of the frame level keys listed in - - shall be present in a FRAME level request - + defines the keys at the Frame level of the Composite Instance Root Query/Retrieve Information Model. One and only one of the frame level keys listed in shall be present in a FRAME level request
Composite Instance Level Keys for the Composite Instance Root Retrieve Information - Model - Composite Instance Level Keys for the Composite Instance Root Retrieve Information Model
@@ -45736,8 +32015,7 @@ Tag - Matching Key Type - + Matching Key Type
- + @@ -45818,9 +32084,7 @@ (0008,1163) @@ -45828,111 +32092,46 @@
Scope of the C-MOVE or C-GET Commands and Sub-Operations - A C-MOVE or C-GET request may be - performed to any level of the Query/Retrieve Model. A C-MOVE or C-GET where the - Query/Retrieve level is the: - - IMAGE level indicates that selected - individual Composite Instances shall be transferred - - FRAME level indicates that a single new - Composite Instance shall be created and transferred - + A C-MOVE or C-GET request may be performed to any level of the Query/Retrieve Model. A C-MOVE or C-GET where the Query/Retrieve level is the: + IMAGE level indicates that selected individual Composite Instances shall be transferred + FRAME level indicates that a single new Composite Instance shall be created and transferred - More than one entity may be - retrieved if the Query/Retrieve Level is IMAGE using List of UID matching, but if the - Query/Retrieve Level is FRAME then only a single entity may be retrieved. - + More than one entity may be retrieved if the Query/Retrieve Level is IMAGE using List of UID matching, but if the Query/Retrieve Level is FRAME then only a single entity may be retrieved.
Conformance Requirements - An implementation may conform to one of the - Composite Instance Root Retrieve SOP Classes as an SCU, SCP or both. The Conformance Statement - shall be in the format defined in. - + An implementation may conform to one of the Composite Instance Root Retrieve SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-MOVE SCU Conformance - An implementation that conforms to - one of the Composite Instance Root Retrieve SOP Classes as an SCU shall support - transfers against the Retrieve Information Model described in - - using the C-MOVE SCU Behavior described in. An - implementation that conforms to one of the SOP Classes of the Composite Instance Root - SOP Class Group as an SCU, and that generates retrievals using the C-MOVE operation, - shall state in its Conformance Statement the Storage Service Class SOP Classes under - which it shall support the C-STORE sub-operations generated by the C- MOVE. - + An implementation that conforms to one of the Composite Instance Root Retrieve SOP Classes as an SCU shall support transfers against the Retrieve Information Model described in using the C-MOVE SCU Behavior described in . An implementation that conforms to one of the SOP Classes of the Composite Instance Root SOP Class Group as an SCU, and that generates retrievals using the C-MOVE operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C- MOVE.
C-GET SCU Conformance - An implementation that conforms to - one of the Composite Instance Root Retrieve SOP Classes as an SCU shall support - retrievals against the Retrieve Information Model described in - - using the C-GET SCU Behavior described in. An - implementation that conforms to one of the SOP Classes of the Composite Instance Root - SOP Class Group as an SCU, which generates retrievals using the C-GET operation shall - state in its Conformance Statement the Storage Service Class SOP Classes under which it - shall support the C-STORE sub-operations generated by the C-GET. - + An implementation that conforms to one of the Composite Instance Root Retrieve SOP Classes as an SCU shall support retrievals against the Retrieve Information Model described in using the C-GET SCU Behavior described in . An implementation that conforms to one of the SOP Classes of the Composite Instance Root SOP Class Group as an SCU, which generates retrievals using the C-GET operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SCP Conformance - An implementation that conforms to one - of the Composite Instance Root Retrieve SOP Classes as an SCP for C-GET operations shall:1) - support both levels of the Composite Instance Root Retrieve Only Information Model - - 2) support all three Frame Level keys - - 3) describe in its conformance - statement the transformations it applies to a multi-frame Composite Instance when creating a - new Composite Instance as defined in. - + An implementation that conforms to one of the Composite Instance Root Retrieve SOP Classes as an SCP for C-GET operations shall:1) support both levels of the Composite Instance Root Retrieve Only Information Model + 2) support all three Frame Level keys + 3) describe in its conformance statement the transformations it applies to a multi-frame Composite Instance when creating a new Composite Instance as defined in .
C-MOVE SCP Conformance - An implementation that conforms to - one of the Composite Instance Root Retrieve SOP Classes as an SCP shall support - retrievals against both levels of the Retrieve Information Model described in - - using the C-MOVE SCP Behavior described in. An - implementation that conforms to one of the SOP Classes of the Composite Instance Root - SOP Class Group as an SCP, which satisfies retrievals using the C- MOVE operation shall - state in its Conformance Statement the Storage Service Class SOP Classes under which it - shall support the C-STORE sub-operations generated by the C- MOVE. - + An implementation that conforms to one of the Composite Instance Root Retrieve SOP Classes as an SCP shall support retrievals against both levels of the Retrieve Information Model described in using the C-MOVE SCP Behavior described in . An implementation that conforms to one of the SOP Classes of the Composite Instance Root SOP Class Group as an SCP, which satisfies retrievals using the C- MOVE operation shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C- MOVE.
C-GET SCP Conformance - An implementation that conforms to - one of the Composite Instance Root Retrieve SOP Classes as an SCP shall support - retrievals against both levels of the Retrieve Information Model described in - - using the C-GET SCP Behavior described in. An - implementation that conforms to one of the SOP Classes of the Composite Instance Root - SOP Class Group as an SCP, and that satisfies retrievals using the C-GET operation, - shall state in its Conformance Statement the Storage Service Class SOP Classes under - which it shall support the C-STORE sub-operations generated by the C-GET. - + An implementation that conforms to one of the Composite Instance Root Retrieve SOP Classes as an SCP shall support retrievals against both levels of the Retrieve Information Model described in using the C-GET SCP Behavior described in . An implementation that conforms to one of the SOP Classes of the Composite Instance Root SOP Class Group as an SCP, and that satisfies retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SOP Classes - The SOP Classes in the Composite Instance - Root SOP Class Group of the Query/Retrieve Service Class identify the Composite Instance Root - Retrieve Only Information Model, and the DIMSE-C operations supported. The Standard SOP Classes - are listed in. - + The SOP Classes in the Composite Instance Root SOP Class Group of the Query/Retrieve Service Class identify the Composite Instance Root Retrieve Only Information Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in .
Frame Level Keys for the Composite Instance Root Retrieve Information Model - Frame Level Keys for the Composite Instance Root Retrieve Information Model
@@ -45784,30 +32056,24 @@
- Simple Frame List - + Simple Frame List (0008,1161) - Required if Calculated - Frame List and Time Range are not present - + Required if Calculated Frame List and Time Range are not present
- Calculated Frame List - + Calculated Frame List (0008,1162) - Required if Simple - Frame List and Approximate Frame Range are not present - + Required if Simple Frame List and Approximate Frame Range are not present
- Required if Simple - Frame List and Calculated Frame List are not present - + Required if Simple Frame List and Calculated Frame List are not present
@@ -45948,26 +32147,18 @@ @@ -45982,31 +32173,16 @@ Overview
Scope - Composite Instance Retrieve Without Bulk Data - Service is a service within the DICOM Query/Retrieve Service class defined in.The retrieve capability of this service - allows a DICOM AE to retrieve Composite Instances without retrieving their pixel data or other - potentially large Attributes as defined in. - - The Enhanced Multi-Frame Image Conversion - Extended Negotiation Option of the DICOM Query/Retrieve Service class defined in - - is also supported for the Composite Instance Retrieve Without Bulk Data Service. - + Composite Instance Retrieve Without Bulk Data Service is a service within the DICOM Query/Retrieve Service class defined in .The retrieve capability of this service allows a DICOM AE to retrieve Composite Instances without retrieving their pixel data or other potentially large Attributes as defined in . + The Enhanced Multi-Frame Image Conversion Extended Negotiation Option of the DICOM Query/Retrieve Service class defined in is also supported for the Composite Instance Retrieve Without Bulk Data Service.
Composite Instance Retrieve Without Bulk Data Information Model - Retrievals are implemented against the - Composite Instance Retrieve Without Bulk Data Information Model, as defined in this Annex of the - DICOM Standard. A specific SOP Class of the Query/Retrieve Service Class consists of an Information - Model Definition and a DIMSE-C Service Group. - + Retrievals are implemented against the Composite Instance Retrieve Without Bulk Data Information Model, as defined in this Annex of the DICOM Standard. A specific SOP Class of the Query/Retrieve Service Class consists of an Information Model Definition and a DIMSE-C Service Group.
Attributes Not Included - The Attributes that shall not be included in - the top level of the Data set sent by an SCP of this Service are as defined in - + The Attributes that shall not be included in the top level of the Data set sent by an SCP of this Service are as defined in
SOP Classes for Composite Instance Root Retrieve
- Composite Instance Root - Retrieve - MOVE - + Composite Instance Root Retrieve - MOVE - - 1.2.840.10008.5.1.4.1.2.4.2 - + 1.2.840.10008.5.1.4.1.2.4.2
- Composite Instance Root - Retrieve - GET - + Composite Instance Root Retrieve - GET - - 1.2.840.10008.5.1.4.1.2.4.3 - + 1.2.840.10008.5.1.4.1.2.4.3
@@ -46096,87 +32272,37 @@
Attributes Not to Be Included in Instances Sent
- This implies that the pixel data within - Icon Image Sequence (0088,0200) Items will be preserved. - + This implies that the pixel data within Icon Image Sequence (0088,0200) Items will be preserved. - The Waveform Data (5400,1010) Attribute shall - not be included within the Waveform Sequence (5400,0100). - - Private Attributes may be preserved or - discarded by a Storage SCP, as defined in. A - Storage SCP that claims conformance to Level 2 (Full) support of the Storage Service Class may - choose to return Private Attributes in the2 Retrieve Without Bulk Data Service or not. Whether or - not particular Private Attributes are returned shall be documented in the Conformance Statement. - + The Waveform Data (5400,1010) Attribute shall not be included within the Waveform Sequence (5400,0100). + Private Attributes may be preserved or discarded by a Storage SCP, as defined in . + A Storage SCP that claims conformance to Storage Level 2 (Full) support of the Storage Service Class may choose to return Private Attributes in the Retrieve Without Bulk Data Service or not. Whether or not particular Private Attributes are returned shall be documented in the Conformance Statement. - The decision as to whether or not to return - a particular Private Attribute may be dependent on its size. - + The decision as to whether or not to return a particular Private Attribute may be dependent on its size.
Service Definition - Two peer DICOM AEs implement a SOP Class of the - Composite Instance Retrieve Without Bulk Data Service with one serving in the SCU role and one - serving in the SCP role. SOP Classes of the Composite Instance Retrieve Without Bulk Data Service - are implemented using the DIMSE-C C-GET service as defined in - . - - The following descriptions of the DIMSE-C C-GET - service provide a brief overview of the SCU/SCP semantics: - + Two peer DICOM AEs implement a SOP Class of the Composite Instance Retrieve Without Bulk Data Service with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Composite Instance Retrieve Without Bulk Data Service are implemented using the DIMSE-C C-GET service as defined in . + The following descriptions of the DIMSE-C C-GET service provide a brief overview of the SCU/SCP semantics: - A C-GET service conveys the following - semantics: - + A C-GET service conveys the following semantics: - The SCP shall identify a set of - Entities at the level of the retrieval based upon the values in the Unique Keys in - the Identifier of the C-GET request. The SCP shall then generate C-STORE - sub-operations for the corresponding storage SOP Instances, but shall not include - Attributes as described in - - in the data sent during those sub-operations. These C-STORE sub-operations occur on - the same Association as the C-GET service and the SCU/SCP roles are reversed for the - C-STORE. - + The SCP shall identify a set of Entities at the level of the retrieval based upon the values in the Unique Keys in the Identifier of the C-GET request. The SCP shall then generate C-STORE sub-operations for the corresponding storage SOP Instances, but shall not include Attributes as described in in the data sent during those sub-operations. These C-STORE sub-operations occur on the same Association as the C-GET service and the SCU/SCP roles are reversed for the C-STORE. - If the source instance does - not contain any of the Attributes described in - - then, the version sent via the C-STORE sub-operation would be identical to the - original data. This is not an error. - + If the source instance does not contain any of the Attributes described in then, the version sent via the C-STORE sub-operation would be identical to the original data. This is not an error. - The SCP may optionally generate - responses to the C-GET with status equal to Pending during the processing of the - C-STORE sub-operations. These C-GET responses indicate the number of remaining - C-STORE sub-operations and the number of C-STORE sub-operations returning the status - of Success, Warning, and Failed. - + The SCP may optionally generate responses to the C-GET with status equal to Pending during the processing of the C-STORE sub-operations. These C-GET responses indicate the number of remaining C-STORE sub-operations and the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. - When the number of Remaining - C-STORE sub-operations reaches zero, the SCP generates a final response with a - status equal to Success, Warning, Failed, or Refused. This response shall indicate - the number of C-STORE sub-operations returning the status of Success, Warning, and - Failed. If the status of any C-STORE sub-operation was Failed a UID List shall be - returned. - + When the number of Remaining C-STORE sub-operations reaches zero, the SCP generates a final response with a status equal to Success, Warning, Failed, or Refused. This response shall indicate the number of C-STORE sub-operations returning the status of Success, Warning, and Failed. If the status of any C-STORE sub-operation was Failed a UID List shall be returned. - The SCU may cancel the C-GET - service by issuing a C-GET-CANCEL request at any time during the processing of the - C-GET. The SCP terminates all incomplete C-STORE sub-operations and returns a status - of Canceled. - + The SCU may cancel the C-GET service by issuing a C-GET-CANCEL request at any time during the processing of the C-GET. The SCP terminates all incomplete C-STORE sub-operations and returns a status of Canceled. @@ -46185,20 +32311,11 @@
Composite Instance Retrieve Without Bulk Data Information Model Definition - The Composite Instance Retrieve Without Bulk Data - Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP - Class is composed of both an Information Model and a DIMSE-C Service Group. - + The Composite Instance Retrieve Without Bulk Data Information Model is identified by the SOP Class negotiated at Association establishment time. The SOP Class is composed of both an Information Model and a DIMSE-C Service Group. - This SOP Class identifies the class of the - Composite Instance Retrieve Without Bulk Data Information Model (i.e., not the SOP Class of the - stored SOP Instances for which the SCP has information). - + This SOP Class identifies the class of the Composite Instance Retrieve Without Bulk Data Information Model (i.e., not the SOP Class of the stored SOP Instances for which the SCP has information). - Information Model Definitions for Standard SOP - Classes of the Composite Instance Retrieve Without Bulk Data Service are defined in this Annex. A - Composite Instance Retrieve Without Bulk Data Information Model Definition contains: - + Information Model Definitions for Standard SOP Classes of the Composite Instance Retrieve Without Bulk Data Service are defined in this Annex. A Composite Instance Retrieve Without Bulk Data Information Model Definition contains: Entity-Relationship Model Definition @@ -46209,25 +32326,17 @@
Entity-Relationship Model Definition - For any Composite Instance Retrieve Without - Bulk Data Information Model, an Entity-Relationship Model defines a hierarchy of entities, with - Attributes defined for each level in the hierarchy (e.g., Composite Instance, Frame).. - + For any Composite Instance Retrieve Without Bulk Data Information Model, an Entity-Relationship Model defines a hierarchy of entities, with Attributes defined for each level in the hierarchy (e.g., Composite Instance, Frame)..
Attributes Definition - Attributes and matching shall be as defined in - + Attributes and matching shall be as defined in
Standard Composite Instance Retrieve Without Bulk Data Information Model - One standard Composite Instance Retrieve Without - Bulk Data Information Model is defined in this Annex. The Composite Instance Retrieve Without Bulk Data - Information Model is associated with a single SOP Class. The following Composite Instance Retrieve - Without Bulk Data Information Model is defined: - + One standard Composite Instance Retrieve Without Bulk Data Information Model is defined in this Annex. The Composite Instance Retrieve Without Bulk Data Information Model is associated with a single SOP Class. The following Composite Instance Retrieve Without Bulk Data Information Model is defined: Retrieve Without Bulk Data @@ -46235,19 +32344,13 @@
Composite Instance Retrieve Without Bulk Data Information Model - The Composite Instance Retrieve Without Bulk - Data Information Model is based upon a one level hierarchy: - + The Composite Instance Retrieve Without Bulk Data Information Model is based upon a one level hierarchy: Composite Instance - The Retrieve Without Bulk Data Information - Model may be represented by the entity relationship diagram shown in - . - + The Retrieve Without Bulk Data Information Model may be represented by the entity relationship diagram shown in .
Retrieve Without Bulk Data Information Model E-R Diagram @@ -46259,17 +32362,12 @@
- The Composite Instance level is the only level - and contains only the SOP Instance UID. - + The Composite Instance level is the only level and contains only the SOP Instance UID.
DIMSE-C Service Groups - A single DIMSE-C Service is used in the - construction of SOP Classes of the Composite Instance Retrieve Without Bulk Data Service. The following - DIMSE-C operation is used: - + A single DIMSE-C Service is used in the construction of SOP Classes of the Composite Instance Retrieve Without Bulk Data Service. The following DIMSE-C operation is used: C-GET @@ -46277,105 +32375,52 @@
C-GET Operation - SCUs of the Composite Instance Retrieve Without - Bulk Data Service shall generate retrievals using the C-GET operation as described in. The C-GET operation - allows an application entity to instruct another application entity to transfer SOP Instances - without the Attributes as described in - - to the initiating application entity using the C-STORE operation. Support for the C-GET service - shall be agreed upon at Association establishment time by both the SCU and SCP of the C-GET in order - for a C-GET operation to occur over the Association. The C-STORE Sub-operations shall be - accomplished on the same Association as the C-GET operation. Hence, the SCP of the Query/Retrieve - Service Class serves as the SCU of the Storage Service Class. - + SCUs of the Composite Instance Retrieve Without Bulk Data Service shall generate retrievals using the C-GET operation as described in . The C-GET operation allows an application entity to instruct another application entity to transfer SOP Instances without the Attributes as described in to the initiating application entity using the C-STORE operation. Support for the C-GET service shall be agreed upon at Association establishment time by both the SCU and SCP of the C-GET in order for a C-GET operation to occur over the Association. The C-STORE Sub-operations shall be accomplished on the same Association as the C-GET operation. Hence, the SCP of the Query/Retrieve Service Class serves as the SCU of the Storage Service Class. - The Application Entity that receives the - stored SOP Instances is always the originator of the C-GET operation. - + The Application Entity that receives the stored SOP Instances is always the originator of the C-GET operation.
C-GET Service Parameters
SOP Class UID - The SOP Class UID identifies the - Query/Retrieve Information Model against which the C-GET is to be performed. Support for the - SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this - C-GET operation. - + The SOP Class UID identifies the Query/Retrieve Information Model against which the C-GET is to be performed. Support for the SOP Class UID is implied by the Abstract Syntax UID of the Presentation Context used by this C-GET operation.
Priority - The Priority Attribute defines the - requested priority of the C-GET operation and corresponding C-STORE sub-operations with - respect to other DIMSE operations being performed by the same SCP. - - Processing of priority requests is not - required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the - different priority levels shall be stated in the Conformance Statement of the SCP. The same - priority shall be used for all C-STORE sub-operations. - + The Priority Attribute defines the requested priority of the C-GET operation and corresponding C-STORE sub-operations with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing, and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP. The same priority shall be used for all C-STORE sub-operations.
Identifier - The C-GET request shall contain an - Identifier. The C-GET response shall conditionally contain an Identifier as required in. - + The C-GET request shall contain an Identifier. The C-GET response shall conditionally contain an Identifier as required in . - The Identifier is specified as U in - the definition of the C-GET primitive in - - but is specialized for use with this service. - + The Identifier is specified as U in the definition of the C-GET primitive in but is specialized for use with this service.
Request Identifier Structure - An Identifier in a C-GET request - shall contain: - + An Identifier in a C-GET request shall contain: - the Query/Retrieve Level - (0008,0052) that defines the level of the retrieval - + the Query/Retrieve Level (0008,0052) that defines the level of the retrieval - SOP Instance UID(s) - (0008,0018) - + SOP Instance UID(s) (0008,0018) - Conditionally, the - Attribute Query/Retrieve View (0008,0053). This Attribute may be included if - Enhanced Multi-Frame Image Conversion has accepted during Association Extended - Negotiation. It shall not be included otherwise. - + Conditionally, the Attribute Query/Retrieve View (0008,0053). This Attribute may be included if Enhanced Multi-Frame Image Conversion has accepted during Association Extended Negotiation. It shall not be included otherwise. - Query/Retrieve Level (0008,0052) - shall be IMAGE. - - Specific Character Set (0008,0005) - shall not be present. - - The Keys at each level of the - hierarchy and the values allowable for the level of the retrieval are defined in the SOP - Class definition for the Query/Retrieve Information Model. - + Query/Retrieve Level (0008,0052) shall be IMAGE. + Specific Character Set (0008,0005) shall not be present. + The Keys at each level of the hierarchy and the values allowable for the level of the retrieval are defined in the SOP Class definition for the Query/Retrieve Information Model.
Status - - defines the status code values that might be returned in a C-GET response. General status - code values and fields related to status code values are defined for C-GET DIMSE Service in - . - + defines the status code values that might be returned in a C-GET response. General status code values and fields related to status code values are defined for C-GET DIMSE Service in . - +
C-GET Response Status Values for Composite Instance Retrieve Without Bulk Data - C-GET Response Status Values for Composite Instance Retrieve Without Bulk Data
@@ -46398,9 +32443,7 @@ Failure - Refused: Out of - resources - Unable to calculate number of matches - + Refused: Out of resources - Unable to calculate number of matches A701 @@ -46411,9 +32454,7 @@
- Refused: Out of - resources - Unable to perform sub-operations - + Refused: Out of resources - Unable to perform sub-operations A702 @@ -46427,9 +32468,7 @@
- Error: Data Set does - not match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -46441,9 +32480,7 @@
- Failed: Unable to - process - + Failed: Unable to process Cxxx @@ -46458,9 +32495,7 @@ Cancel - Sub-operations - terminated due to Cancel Indication - + Sub-operations terminated due to Cancel Indication FE00 @@ -46477,9 +32512,7 @@ Warning - Sub-operations Complete - - One or more Failures or Warnings - + Sub-operations Complete - One or more Failures or Warnings B000 @@ -46496,9 +32529,7 @@ Success - Sub-operations Complete - - No Failures or Warnings - + Sub-operations Complete - No Failures or Warnings 0000 @@ -46515,9 +32546,7 @@ Pending - Sub-operations are - continuing - + Sub-operations are continuing FF00 @@ -46531,286 +32560,147 @@
- Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign - specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the - range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: - Unable to process" Failure Meaning shall assign those causes specific Status Code Values - within valid range specified in. - - An SCU implementation shall recognize - any Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an - SCU implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of "Failed: Unable to process" Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
Number of Remaining Sub-Operations - Inclusion of the Number of Remaining - Sub-operations shall be as specified in - + Inclusion of the Number of Remaining Sub-operations shall be as specified in
Number of Completed Sub-Operations - Inclusion of the Number of Completed - Sub-operations shall be as specified in - + Inclusion of the Number of Completed Sub-operations shall be as specified in
Number of Failed Sub-Operations - Inclusion of the Number of Failed - Sub-operations shall be as specified in - + Inclusion of the Number of Failed Sub-operations shall be as specified in
Number of Warning Sub-Operations - Inclusion of the Number of Warning - Sub-operations shall be as specified in. - + Inclusion of the Number of Warning Sub-operations shall be as specified in .
C-GET SCU and C-STORE SCP Behavior
Baseline Behavior of SCU - An SCU conveys the following semantics - with a C-GET request: - + An SCU conveys the following semantics with a C-GET request: - The SCU shall specify one - Instance UID or a list of Instance UIDs. - + The SCU shall specify one Instance UID or a list of Instance UIDs. - The SCU shall have proposed - sufficient presentation contexts at Association establishment time to accommodate - expected C-STORE sub-operations that will occur over the same Association. The SCU - of the Query/Retrieve Service Class shall serve as the SCP of the Storage Service - Class. - + The SCU shall have proposed sufficient presentation contexts at Association establishment time to accommodate expected C-STORE sub-operations that will occur over the same Association. The SCU of the Query/Retrieve Service Class shall serve as the SCP of the Storage Service Class. - The SCP of the Storage Service - Class shall not store the incomplete SOP Instance; rather the behavior is - implementation defined. - + The SCP of the Storage Service Class shall not store the incomplete SOP Instance; rather the behavior is implementation defined. - The SCU shall accept C-GET - responses with status equal to Pending during the processing of the C-STORE - sub-operations. These responses indicate the number of Remaining, Completed, Failed - and Warning C-STORE sub-operations. - + The SCU shall accept C-GET responses with status equal to Pending during the processing of the C-STORE sub-operations. These responses indicate the number of Remaining, Completed, Failed and Warning C-STORE sub-operations. - The SCU shall interpret a C-GET - response with a status equal to Success, Warning, Failure, or Refused as a final - response. The final response indicates the number of Completed sub-operations and - the number of Failed C-STORE sub-operations resulting from the C-GET operation. The - SCU shall interpret a status of: - + The SCU shall interpret a C-GET response with a status equal to Success, Warning, Failure, or Refused as a final response. The final response indicates the number of Completed sub-operations and the number of Failed C-STORE sub-operations resulting from the C-GET operation. The SCU shall interpret a status of: - Success to indicate - that all sub-operations were successfully completed - + Success to indicate that all sub-operations were successfully completed - Failure or Refused to - indicate all sub-operations were unsuccessful - + Failure or Refused to indicate all sub-operations were unsuccessful - Warning in all other - cases. The Number of Completed Sub-Operations (0000,1021), Number of Warning - Sub-Operations (0000,1023), Number of Failed Sub-Operations (0000,1022) can - be used to obtain more detailed information. - + Warning in all other cases. The Number of Completed Sub-Operations (0000,1021), Number of Warning Sub-Operations (0000,1023), Number of Failed Sub-Operations (0000,1022) can be used to obtain more detailed information. - The SCU may cancel the C-GET - operation by issuing a C-GET-CANCEL request at any time during the processing of the - C-GET request. A C-GET response with a status of Canceled shall indicate to the SCU - that the retrieve was canceled. Optionally, the C-GET response with a status of - Canceled shall indicate the number of Completed, Failed, and Warning C-STORE - sub-operations. If present, the Remaining sub-operations count shall contain the - number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL - request. - + The SCU may cancel the C-GET operation by issuing a C-GET-CANCEL request at any time during the processing of the C-GET request. A C-GET response with a status of Canceled shall indicate to the SCU that the retrieve was canceled. Optionally, the C-GET response with a status of Canceled shall indicate the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL request. - The SCP of the Storage Service - Class shall not return a status of "Error: Data Set does not match SOP Class" (A9xx) - or "Warning: Data Set does not match SOP Class" (B007) due to the absence of the - Attributes described in. - + The SCP of the Storage Service Class shall not return a status of "Error: Data Set does not match SOP Class" (A9xx) or "Warning: Data Set does not match SOP Class" (B007) due to the absence of the Attributes described in .
Extended Behavior of SCU - The extended behavior of the SCU shall - be as specified in, except that - Relational-retrieve shall not be supported. - + The extended behavior of the SCU shall be as specified in , except that Relational-retrieve shall not be supported.
C-GET SCP and C-STORE SCU Behavior
Baseline Behavior of SCP - An SCP conveys the following semantics - with a C-GET response: - + An SCP conveys the following semantics with a C-GET response: - The SCP shall identify a set of - Entities at the level of the transfer based upon the values in the Unique Keys in - the Identifier of the C-GET request. - + The SCP shall identify a set of Entities at the level of the transfer based upon the values in the Unique Keys in the Identifier of the C-GET request. - The SCP shall initiate C-STORE - sub-operations for the identified SOP Instances, but shall not include in this - C-STORE sub-operation the Attributes described in. - The SCP of the Query/Retrieve Service Class shall serve as an SCU of the Storage - Service Class. - + The SCP shall initiate C-STORE sub-operations for the identified SOP Instances, but shall not include in this C-STORE sub-operation the Attributes described in . The SCP of the Query/Retrieve Service Class shall serve as an SCU of the Storage Service Class. - Apart from the Attributes - listed in, the SOP Instance - sent via the C-STORE sub-operation shall be unchanged, and no corresponding changes - to other Attributes shall be made. - + Apart from the Attributes listed in , the SOP Instance sent via the C-STORE sub-operation shall be unchanged, and no corresponding changes to other Attributes shall be made. - In particular, the Study, Series - and SOP Instance UIDs and SOP Class UID will not be altered. - + In particular, the Study, Series and SOP Instance UIDs and SOP Class UID will not be altered. - The SCP shall initiate C-STORE - sub-operations over the same Association for all SOP Instances specified in the - C-GET request. - + The SCP shall initiate C-STORE sub-operations over the same Association for all SOP Instances specified in the C-GET request. - A sub-operation is considered a - Failure if the SCP is unable to initiate a C-STORE sub-operation because the - Query/Retrieve SCU did not offer an appropriate presentation context for a given - stored SOP Instance. - + A sub-operation is considered a Failure if the SCP is unable to initiate a C-STORE sub-operation because the Query/Retrieve SCU did not offer an appropriate presentation context for a given stored SOP Instance. - Optionally, the SCP may - generate responses to the C-GET with status equal to Pending during the processing - of the C-STORE sub-operations. These responses shall indicate the number of - Remaining, Completed, Failure, and Warning C-STORE sub-operations. - + Optionally, the SCP may generate responses to the C-GET with status equal to Pending during the processing of the C-STORE sub-operations. These responses shall indicate the number of Remaining, Completed, Failure, and Warning C-STORE sub-operations. - When the number of Remaining - sub-operations reaches zero, the SCP shall generate a final response with a status - equal to Success, Warning or Failed. The status contained in the C-GET response - shall contain: - + When the number of Remaining sub-operations reaches zero, the SCP shall generate a final response with a status equal to Success, Warning or Failed. The status contained in the C-GET response shall contain: - Success if all - sub-operations were successfully completed - + Success if all sub-operations were successfully completed - Failure if all - sub-operations were unsuccessful - + Failure if all sub-operations were unsuccessful - Warning in all other - cases. - + Warning in all other cases. - The SCP may receive a - C-GET-CANCEL request at any time during the processing of the C-GET request. The SCP - shall interrupt all C-STORE sub-operation processing and return a status of Canceled - in the C-GET response. The C-GET response with a status of Canceled shall contain - the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the - Remaining sub-operations count shall contain the number of C-STORE sub-operations - that were not initiated due to the C-GET-CANCEL request. - + The SCP may receive a C-GET-CANCEL request at any time during the processing of the C-GET request. The SCP shall interrupt all C-STORE sub-operation processing and return a status of Canceled in the C-GET response. The C-GET response with a status of Canceled shall contain the number of Completed, Failed, and Warning C-STORE sub-operations. If present, the Remaining sub-operations count shall contain the number of C-STORE sub-operations that were not initiated due to the C-GET-CANCEL request. - If the SCP manages images in - multiple alternate encodings (see), only one of the - alternate encodings of an image shall be used as the existing SOP Instance from - which frames are to be extracted. - + If the SCP manages images in multiple alternate encodings (see ), only one of the alternate encodings of an image shall be used as the existing SOP Instance from which frames are to be extracted.
Extended Behavior of SCP - The extended behavior of the SCP shall - be as specified in, except that - Relational-retrieve shall not be supported. - + The extended behavior of the SCP shall be as specified in , except that Relational-retrieve shall not be supported.
Association Negotiation - Association establishment is the first phase of any - instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes - utilize Association establishment negotiation by defining the use of Application Association - Information. See - - for an overview of Association negotiation. - - SOP Classes of the Composite Instance Retrieve - Without Bulk Data Service, which include retrieval services based on the C-GET operation, use the - SCP/SCU Role Selection Sub-Item to identify the SOP Classes that may be used for retrieval. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. AEs supporting DICOM Query/Retrieve SOP Classes utilize Association establishment negotiation by defining the use of Application Association Information. See for an overview of Association negotiation. + SOP Classes of the Composite Instance Retrieve Without Bulk Data Service, which include retrieval services based on the C-GET operation, use the SCP/SCU Role Selection Sub-Item to identify the SOP Classes that may be used for retrieval.
Association Negotiation for C-GET SOP Classes - Rules are as specified in, except that the extended negotiation sub-item, - if used, shall be used as defined in. - + Rules are as specified in , except that the Extended Negotiation sub-item, if used, shall be used as defined in . - Though converted images may be - specified by their SOP Instance UID in the Request Identifier, which is always at the - instance level, there remains a need for extended negotiation and specification of the - Query/Retrieve View in order to assure that referential integrity is maintained within - the returned SOP Instances (e.g., that a reference to a SOP Instance UID is to a - converted image or not, as appropriate). - + Though converted images may be specified by their SOP Instance UID in the Request Identifier, which is always at the instance level, there remains a need for Extended Negotiation and specification of the Query/Retrieve View in order to assure that referential integrity is maintained within the returned SOP Instances (e.g., that a reference to a SOP Instance UID is to a converted image or not, as appropriate). - Relational-retrieval is not - applicable to this SOP Class, hence the Extended Negotiation Sub-Item does not include - the use of that byte. - + Relational-retrieval is not applicable to this SOP Class, hence the Extended Negotiation Sub-Item does not include the use of that byte. @@ -46820,9 +32710,7 @@ SOP Class Definitions
Composite Instance Retrieve Without Bulk Data SOP Class Group - In the Composite Instance Retrieve Without Bulk - Data Only Information Model, only a single Retrieve Level is used. - + In the Composite Instance Retrieve Without Bulk Data Only Information Model, only a single Retrieve Level is used. @@ -46847,31 +32735,20 @@
Retrieve Level Value for Composite Instance Retrieve Without Bulk Data
- The use of the word "IMAGE" rather than - "Composite Instance" is historical to allow backward compatibility with previous editions of the - Standard. It should not be taken to mean that Composite Instances of other than image type are - not included at the level indicated by the value IMAGE. - + The use of the word "IMAGE" rather than "Composite Instance" is historical to allow backward compatibility with previous editions of the Standard. It should not be taken to mean that Composite Instances of other than image type are not included at the level indicated by the value IMAGE.
Composite Instance Retrieve Without Bulk Data Information Model
E/R Model - The Composite Instance Retrieve Without - Bulk Data Only Information Model has only a single level: IMAGE. - + The Composite Instance Retrieve Without Bulk Data Only Information Model has only a single level: IMAGE.
Composite Instance Level - - defines the keys at the Composite Instance level of the Composite Instance Retrieve Without - Bulk Data Query/Retrieve Information model. - + defines the keys at the Composite Instance level of the Composite Instance Retrieve Without Bulk Data Query/Retrieve Information model. - + @@ -46903,59 +32779,24 @@
Scope of the C-GET Commands and Sub-Operations - A C-GET request may only be performed - at the IMAGE level of the Query/Retrieve Model. A C-GET indicates that selected individual - Composite Instances, without bulk data Attributes shall be transferred. - + A C-GET request may only be performed at the IMAGE level of the Query/Retrieve Model. A C-GET indicates that selected individual Composite Instances, without bulk data Attributes shall be transferred.
Conformance Requirements - An implementation may conform to one of the - SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as an SCU, SCP - or both. The Conformance Statement shall be in the format defined in - . - + An implementation may conform to one of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that conforms to one - of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as - an SCU shall support retrievals against the Query/Retrieve Information Model described in - - using the C-GET SCU Behavior described in. An - implementation that conforms to one of the SOP Classes of the Composite Instance Retrieve - Without Bulk Data SOP Class Group as an SCU, and that generates retrievals using the C-GET - operation, shall state in its Conformance Statement the Storage Service Class SOP Classes - under which it shall support the C-STORE sub-operations generated by the C-GET. - + An implementation that conforms to one of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as an SCU shall support retrievals against the Query/Retrieve Information Model described in using the C-GET SCU Behavior described in . An implementation that conforms to one of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as an SCU, and that generates retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SCP Conformance - An implementation that conforms to one - of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as - an SCP shall support retrievals against both levels of the Retrieve Information Model - described in - - using the C-GET SCP Behavior described in. An - implementation that conforms to one of the SOP Classes of the Composite Instance Retrieve - Without Bulk Data SOP Class Group as an SCP, and that satisfies retrievals using the C-GET - operation, shall state in its Conformance Statement the Storage Service Class SOP Classes - under which it shall support the C-STORE sub-operations generated by the C-GET. - + An implementation that conforms to one of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as an SCP shall support retrievals against both levels of the Retrieve Information Model described in using the C-GET SCP Behavior described in . An implementation that conforms to one of the SOP Classes of the Composite Instance Retrieve Without Bulk Data SOP Class Group as an SCP, and that satisfies retrievals using the C-GET operation, shall state in its Conformance Statement the Storage Service Class SOP Classes under which it shall support the C-STORE sub-operations generated by the C-GET.
SOP Classes - The SOP Classes in the Composite Instance - Retrieve Without Bulk Data SOP Class Group of the Query/Retrieve Service Class identify the - Composite Instance Retrieve Without Bulk Data Only Information Model, and the DIMSE-C operations - supported. The Standard SOP Classes are listed in. - + The SOP Classes in the Composite Instance Retrieve Without Bulk Data SOP Class Group of the Query/Retrieve Service Class identify the Composite Instance Retrieve Without Bulk Data Only Information Model, and the DIMSE-C operations supported. The Standard SOP Classes are listed in .
Composite Instance Level Keys for the Composite Instance Retrieve Without Bulk Data - Information Model - Composite Instance Level Keys for the Composite Instance Retrieve Without Bulk Data Information Model
@@ -46881,8 +32758,7 @@ Tag - Matching Key Type - + Matching Key Type
@@ -46971,14 +32812,10 @@ @@ -46991,32 +32828,18 @@ Ophthalmic Refractive Measurements Storage SOP Classes (Normative)
Scope - Refractive instruments are the most commonly used - instruments in eye care. At present many of them have the capability for digital output, but their data - is most often addressed by manual input into a paper or electronic record. Lensometry, Autorefraction, - Keratometry, Subjective Refraction, and Visual Acuity Measurements Storage SOP Classes support devices - such as lensometers, auto-refractors, keratometers, autophoropters, and autoprojectors. - + Refractive instruments are the most commonly used instruments in eye care. At present many of them have the capability for digital output, but their data is most often addressed by manual input into a paper or electronic record. Lensometry, Autorefraction, Keratometry, Subjective Refraction, and Visual Acuity Measurements Storage SOP Classes support devices such as lensometers, auto-refractors, keratometers, autophoropters, and autoprojectors.
Behavior of an SCP - For a device that is both an SCU and an SCP of the - aforementioned Storage SOP Classes, in addition to the behavior for the Storage Service Class specified - in, the following additional requirements are - specified for Structured Reporting Storage SOP Classes: - + For a device that is both an SCU and an SCP of the aforementioned Storage SOP Classes, in addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for Ophthalmic Refractive Measurements SOP Classes: - An SCP of these SOP Classes shall support - Level 2 Conformance as defined in. - + An SCP of these SOP Classes shall support Storage Level 2 (Full) as defined in . - This requirement means that all Type 1, Type 2, - and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated - with the SOP Class will be stored and may be accessed. - + This requirement means that all Type 1, Type 2, and Type 3 Attributes defined in the Information Object Definition and Private Attributes associated with the SOP Class will be stored and may be accessed.
@@ -47026,180 +32849,92 @@ Overview
Scope - The Implant Template Query/Retrieve Service - Classes define application-level classes-of-service that facilitate access to Implant Template and - Implant Assembly Template composite objects. - + The Implant Template Query/Retrieve Service Classes define application-level classes-of-service that facilitate access to Implant Template and Implant Assembly Template composite objects.
Conventions - Key Attributes serve two purposes; they may be - used as Matching Key Attributes or as Return Key Attributes. Matching Key Attributes may be used for - matching (criteria to be used in the C-FIND request to determine whether an entity matches the - query). Return Key Attributes may be used to specify desired return Attributes (what elements in - addition to the Matching Key Attributes have to be returned in the C-FIND response). - + Key Attributes serve two purposes; they may be used as Matching Key Attributes or as Return Key Attributes. Matching Key Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether an entity matches the query). Return Key Attributes may be used to specify desired return Attributes (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND response). - Matching Keys are typically used in an SQL - 'where' clause. Return Keys are typically used in an SQL 'select' clause to convey the Attribute - Values. - + Matching Keys are typically used in an SQL 'where' clause. Return Keys are typically used in an SQL 'select' clause to convey the Attribute Values. - Matching Key Attributes may be of Type - "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in - . - + Matching Key Attributes may be of Type "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in .
Query/Retrieve Information Model - In order to serve as an SCP of the Implant - Template Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a - number of Implant Template or Implant Assembly Template composite SOP Instances. The information is - organized into an Information Model. The Information Models for the different SOP Classes specified - in this Annex are defined in. - + In order to serve as an SCP of the Implant Template Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of Implant Template or Implant Assembly Template composite SOP Instances. The information is organized into an Information Model. The Information Models for the different SOP Classes specified in this Annex are defined in .
Service Definition - Two peer DICOM AEs implement a SOP Class of an - Implant Template or Implant Assembly Template Query/Retrieve Service Class with one serving in the - SCU role and one serving in the SCP role. SOP Classes of the Implant Template and Implant Assembly - Template Query/Retrieve Service Classes are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET - services as defined in. - - An SCP of this SOP Class shall support Level-2 - conformance as defined in. - - The semantics of the C-FIND service are the - same as those defined in the Service Definition of the Basic Worklist Management Service Class. - - The semantics of the C-MOVE service are the - same as those defined in the Service Definition of the Query/Retrieve Service Class, with the - exception that there is only one level of retrieval. - - The semantics of the C-GET service are the same - as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception - that there is only one level of retrieval. - + Two peer DICOM AEs implement a SOP Class of an Implant Template or Implant Assembly Template Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Implant Template and Implant Assembly Template Query/Retrieve Service Classes are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in . + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . + The semantics of the C-FIND service are the same as those defined in the Service Definition of the Basic Worklist Management Service Class. + The semantics of the C-MOVE service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval. + The semantics of the C-GET service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval.
Implant Template Information Models Definitions - The Implant Template, Implant Assembly Template, - and Implant Template Group Information Models are identified by the SOP Class negotiated at Association - establishment time. Each SOP Class is composed of both an Information Model and a DIMSE-C Service Group. - - The Implant Template, Implant Assembly Template, - and Implant Template Group Information Models are defined in, with the - Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined in the - Worklist Information Model Definition of the Basic Worklist Management Service. - + The Implant Template, Implant Assembly Template, and Implant Template Group Information Models are identified by the SOP Class negotiated at Association establishment time. Each SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + The Implant Template, Implant Assembly Template, and Implant Template Group Information Models are defined in , with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model Definition of the Basic Worklist Management Service.
Implant Template Information Models - The Implant Template Information Models are based - upon a one level entity: - + The Implant Template Information Models are based upon a one level entity: Implant Template object instance. - The Implant Template object instance contains - Attributes associated with the Implant Template object IE of the Composite IODs as defined in. - - The Implant Assembly Template Information Model is - based upon a one level entity: - + The Implant Template object instance contains Attributes associated with the Implant Template object IE of the Composite IODs as defined in . + The Implant Assembly Template Information Model is based upon a one level entity: - Implant Assembly Template object - instance. - + Implant Assembly Template object instance. - The Implant Assembly Template object instance - contains Attributes associated with the Implant Assembly Template object IE of the Composite IODs as - defined in. - - The Implant Assembly Group Information Model is - based upon a one level entity: - + The Implant Assembly Template object instance contains Attributes associated with the Implant Assembly Template object IE of the Composite IODs as defined in . + The Implant Assembly Group Information Model is based upon a one level entity: - Implant Template Group object instance. - + Implant Template Group object instance. - The Implant Template Group object instance contains - Attributes associated with the Implant Template Group object IE of the Composite IODs as defined in - . - + The Implant Template Group object instance contains Attributes associated with the Implant Template Group object IE of the Composite IODs as defined in .
DIMSE-C Service Groups
C-FIND Operation - See the C-FIND Operation definition for the - Basic Worklist Management Service Class (K.4.1), and substitute "Implant Template" for "Worklist". - The "Worklist" Search Method shall be used. - - The SOP Class UID identifies the Implant - Template or Implant Assembly Template, respectively Information Model against which the C-FIND is to - be performed. The Key Attributes and values allowable for the query are defined in the SOP Class - definitions for the Implant Template and Implant Assembly Template Information Model. - + See the C-FIND Operation definition for the Basic Worklist Management Service Class (K.4.1), and substitute "Implant Template" for "Worklist". The "Worklist" Search Method shall be used. + The SOP Class UID identifies the Implant Template or Implant Assembly Template, respectively Information Model against which the C-FIND is to be performed. The Key Attributes and values allowable for the query are defined in the SOP Class definitions for the Implant Template and Implant Assembly Template Information Model.
Service Class User Behavior - When receiving several Implant Template - Instances with the same Implant Part Number, the receiving application shall use Effective - DateTime (0068,6226) to determine the appropriate Instance. - + When receiving several Implant Template Instances with the same Implant Part Number, the receiving application shall use Effective DateTime (0068,6226) to determine the appropriate Instance.
Service Class Provider Behavior - An SCP of this SOP Class shall support - Level-2 conformance as defined in. - + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in .
C-MOVE Operation - See the C-MOVE Operation definition for the - Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the - Implant Template and Implant Assembly Template Query/Retrieve Service Classes. - - Query/Retrieve Level (0008,0052) is not - relevant to the Implant Template and Implant Assembly Template Query/Retrieve Service Classes, and - therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier - shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-MOVE Operation definition for the Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the Implant Template and Implant Assembly Template Query/Retrieve Service Classes. + Query/Retrieve Level (0008,0052) is not relevant to the Implant Template and Implant Assembly Template Query/Retrieve Service Classes, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
C-GET Operation - See the C-GET Operation definition for the - Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the - Implant Template and Implant Assembly Template Query/Retrieve Service Classes. - + See the C-GET Operation definition for the Query/Retrieve Service Class (C.4.2). No Extended Behavior or Relational-Retrieve is defined for the Implant Template and Implant Assembly Template Query/Retrieve Service Classes. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
Association Negotiation - See the Association Negotiation definition for the - Basic Worklist Management Service Class (K.5). - + See the Association Negotiation definition for the Basic Worklist Management Service Class (K.5).
SOP Class Definitions @@ -47207,10 +32942,7 @@ Implant Template Information Model
E/R Models - The Implant Template Information Model - consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Implant Template Instance. - + The Implant Template Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Implant Template Instance.
Implant Template Information Model E-R Diagram @@ -47222,10 +32954,7 @@
- The Implant Assembly Template Information - Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Implant Assembly Template Instance. - + The Implant Assembly Template Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Implant Assembly Template Instance.
Implant Assembly Template Information Model E-R Diagram @@ -47237,10 +32966,7 @@
- The Implant Template Group Information - Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Implant Template Group Instance. - + The Implant Template Group Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Implant Template Group Instance.
Implant Template Group Information Model E-R Diagram @@ -47258,31 +32984,25 @@
Generic Implant Template Attributes - - defines the Attributes of the Generic Implant Template Information Model: - + defines the Attributes of the Generic Implant Template Information Model:
SOP Classes for Composite Instance Retrieve Without Bulk Data
- Composite Instance Retrieve - Without Bulk Data - GET - + Composite Instance Retrieve Without Bulk Data - GET - - 1.2.840.10008.5.1.4.1.2.5.3 - + 1.2.840.10008.5.1.4.1.2.5.3
@@ -47296,9 +33016,7 @@ @@ -47368,9 +33082,7 @@ 1 @@ -47387,9 +33099,7 @@ 1 @@ -47406,15 +33116,12 @@ 2 @@ -47787,31 +33429,25 @@
Implant Assembly Template Attributes - - defines the Attributes of the Implant Assembly Template Information Model: - + defines the Attributes of the Implant Assembly Template Information Model:
Attributes for the Implant Template Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark / Matching - Type - + Remark / Matching Type
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -47310,11 +33028,7 @@ 1C - This Attribute is - required if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Implant Part Number - + Implant Part Number (0022,1097) @@ -47426,16 +33133,12 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Replaced Implant - Template Sequence - + Replaced Implant Template Sequence (0068,6222) @@ -47447,16 +33150,12 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -47468,16 +33167,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -47489,16 +33184,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Derivation Implant - Template Sequence - + Derivation Implant Template Sequence (0068,6224) @@ -47510,16 +33201,12 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -47531,16 +33218,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -47552,15 +33235,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Effective DateTime - + Effective DateTime (0068,6226) @@ -47572,16 +33252,12 @@ 1 - Shall be retrieved with - Single Value or Range Matching. - + Shall be retrieved with Single Value or Range Matching.
- Original Implant - Template Sequence - + Original Implant Template Sequence (0068,6225) @@ -47593,16 +33269,12 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -47614,16 +33286,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -47635,16 +33303,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Implant Target Anatomy - Sequence - + Implant Target Anatomy Sequence (0068,6230) @@ -47656,16 +33320,12 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Anatomic Region - Sequence - + >Anatomic Region Sequence (0008,2218) @@ -47677,25 +33337,20 @@ 1 - This Attribute shall be - retrieved with Single Value or Universal matching. - + This Attribute shall be retrieved with Single Value or Universal matching.
- >>Include - - - +>>Include + +
- Implant Regulatory - Disapproval Code Sequence - + Implant Regulatory Disapproval Code Sequence (0068,62A0) @@ -47707,25 +33362,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Material Code - Sequence - + Material Code Sequence (0068,63A0) @@ -47737,25 +33387,20 @@ 1 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Coating Materials Code - Sequence - + Coating Materials Code Sequence (0068,63A4) @@ -47767,18 +33412,15 @@ 1 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
@@ -47825,9 +33461,7 @@ @@ -47885,9 +33515,7 @@ @@ -47916,16 +33542,12 @@ 1 @@ -48166,31 +33746,25 @@
Implant Template Group Attributes - - defines the Attributes of the Implant Template Group Information Model: - + defines the Attributes of the Implant Template Group Information Model:
Attributes for the Implant Assembly Template Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark / Matching - Type - + Remark / Matching Type
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -47839,11 +33473,7 @@ 1C - This Attribute is - required if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- Implant Assembly - Template Name - + Implant Assembly Template Name @@ -47897,9 +33525,7 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Procedure Type Code - Sequence - + Procedure Type Code Sequence (0076,0020) @@ -47937,25 +33559,20 @@ 1 - This Attribute shall be - retrieved with Single Value or Universal matching. - + This Attribute shall be retrieved with Single Value or Universal matching.
- >Include - - - +>Include + +
- Replaced Implant - Assembly Template Sequence - + Replaced Implant Assembly Template Sequence (0076,0008) @@ -47967,16 +33584,12 @@ 1 - Shall be retrieved with - Sequence or Universal Matching. - + Shall be retrieved with Sequence or Universal Matching.
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -47988,16 +33601,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -48009,16 +33618,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Original Implant - Assembly Template Sequence - + Original Implant Assembly Template Sequence (0076,000C) @@ -48030,16 +33635,12 @@ 1 - Shall be retrieved with - Sequence or Universal Matching. - + Shall be retrieved with Sequence or Universal Matching.
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -48051,16 +33652,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -48072,16 +33669,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Derivation Implant - Assembly Template Sequence - + Derivation Implant Assembly Template Sequence (0076,000E) @@ -48093,16 +33686,12 @@ 1 - Shall be retrieved with - Sequence or Universal Matching. - + Shall be retrieved with Sequence or Universal Matching.
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -48114,16 +33703,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -48135,15 +33720,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Surgical Technique - + Surgical Technique (0076,0030) @@ -48155,9 +33737,7 @@ 2 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
@@ -48204,9 +33778,7 @@ @@ -48264,9 +33832,7 @@ @@ -48410,124 +33953,46 @@
Conformance Requirements - An implementation may conform to one of the - Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP - Classes as an SCU, SCP, any combination of two of these, or all three. The Conformance Statement - shall be in the format defined in. - + An implementation may conform to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCU, SCP, any combination of two of these, or all three. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes shall support queries against the appropriate Information - Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service - Class (see - - and). - - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCU shall state in its Conformance Statement whether - it requests Type 3 Return Key Attributes, and shall list these Optional Return Key - Attributes. - - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCU shall state in its Conformance Statement how it - makes use of Specific Character Set (0008,0005) when encoding queries and interpreting - responses. - + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes shall support queries against the appropriate Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see and ). + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCU shall support transfers against the appropriate - Information Model, using the C-MOVE SCU baseline behavior described for the - Query/Retrieve Service Class (see - - and). - + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCU shall support transfers against the appropriate Information Model, using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
C-GET SCU Conformance - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCU shall support transfers against the appropriate - Information Model, using the C-GET SCU baseline behavior described for the - Query/Retrieve Service Class (see). - + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCU shall support transfers against the appropriate Information Model, using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see ).
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCP shall support queries against the appropriate - Template Information Model, using the C-FIND SCP Behavior described for the Basic - Worklist Management Service Class (see). - - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCP shall state in its Conformance Statement whether - it supports Type 3 Return Key Attributes, and shall list these Optional Return Key - Attributes. - - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCP shall state in its Conformance Statement how it - makes use of Specific Character Set (0008,0005) when interpreting queries, performing - matching and encoding responses. - + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCP shall support queries against the appropriate Template Information Model, using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see ). + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCP shall state in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.
C-MOVE SCP Conformance - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCP shall support transfers against the appropriate - Information Model, using the C-MOVE SCP baseline behavior described for the - Query/Retrieve Service Class (see). - - An implementation that conforms to - one of the Implant Template, Implant Assembly Template, or Implant Template Group - Information Model SOP Classes as an SCP, which generates transfers using the C-MOVE - operation, shall state in its Conformance Statement appropriate Storage Service Class, - under which it shall support the C-STORE sub-operations generated by the C-MOVE. - + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCP shall support transfers against the appropriate Information Model, using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see ). + An implementation that conforms to one of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Classes as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement appropriate Storage Service Class, under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - one of the SOP Classes of the Implant Template, Implant Assembly Template, or Implant - Template Group Information Model SOP Class Group as an SCP shall support retrievals - against the Query/Retrieve Information Model described in - - using the C-GET SCP Behavior described in. - + An implementation that conforms to one of the SOP Classes of the Implant Template, Implant Assembly Template, or Implant Template Group Information Model SOP Class Group as an SCP shall support retrievals against the Query/Retrieve Information Model described in using the C-GET SCP Behavior described in .
SOP Classes - The SOP Classes of the Implant Template - Information Models in the Implant Template Query/Retrieve Service Class identify the Implant - Template Information Models, and the DIMSE-C operations supported. The SOP Classes of the - Implant Assembly Template Information Models in the Implant Assembly Template Query/Retrieve - Service Class identify the Implant Assembly Template Information Models, and the DIMSE-C - operations supported. The SOP Classes of the Implant Template Group Information Models in the - Implant Template Group Query/Retrieve Service Class identify the Implant Template Group - Information Models, and the DIMSE-C operations supported. The following Standard SOP Classes are - identified: - + The SOP Classes of the Implant Template Information Models in the Implant Template Query/Retrieve Service Class identify the Implant Template Information Models, and the DIMSE-C operations supported. The SOP Classes of the Implant Assembly Template Information Models in the Implant Assembly Template Query/Retrieve Service Class identify the Implant Assembly Template Information Models, and the DIMSE-C operations supported. The SOP Classes of the Implant Template Group Information Models in the Implant Template Group Query/Retrieve Service Class identify the Implant Template Group Information Models, and the DIMSE-C operations supported. The following Standard SOP Classes are identified:
Attributes for the Implant Template Group Information Model
- Description / Module - + Description / Module Tag - Matching Key Type - + Matching Key Type Return Key Type - Remark / Matching - Type - + Remark / Matching Type
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -48218,11 +33790,7 @@ 1C - This Attribute is - required if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- Implant Template Group - Name - + Implant Template Group Name (0078,0000) @@ -48278,16 +33844,12 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Implant Template Group - Description - + Implant Template Group Description (0078,0010) @@ -48302,9 +33864,7 @@
- Implant Template Group - Issuer - + Implant Template Group Issuer (0078,0020) @@ -48316,15 +33876,12 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Effective DateTime - + Effective DateTime (0068,6226) @@ -48336,16 +33893,12 @@ 1 - Shall be retrieved with - Single Value or Range Matching. - + Shall be retrieved with Single Value or Range Matching.
- Replaced Implant - Template Group Sequence - + Replaced Implant Template Group Sequence (0078,0026) @@ -48357,16 +33910,12 @@ 2 - Shall be retrieved with - Sequence or Universal Matching - + Shall be retrieved with Sequence or Universal Matching
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -48378,16 +33927,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -48399,9 +33944,7 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
@@ -48543,101 +34008,74 @@ @@ -48650,125 +34088,51 @@ Unified Procedure Step Service and SOP Classes (Normative)
Overview - This Annex defines the Service and SOP Classes - associated with a Unified Worklist and Procedure Step. - - The Unified Procedure Step Service Class provides - for management of simple worklists, including creating new worklist items, querying the worklist, and - communicating progress and results. - - A worklist is a list of Unified Procedure Step - (UPS) instances. Each UPS instance unifies the worklist details for a single requested procedure step - together with the result details of the corresponding performed procedure step. There is a one to one - relationship between the procedure step request and the procedure step performed. - - Unified Procedure Step instances may be used to - represent a variety of scheduled tasks such as: Image Processing, Quality Control, Computer Aided - Detection, Interpretation, Transcription, Report Verification, or Printing. - - The UPS instance can contain details of the - requested task such as when it is scheduled to be performed or Workitem Codes describing the requested - actions. The UPS may also contain details of the input information the performer needs to do the task - and the output the performer produced, such as: Current Images, Prior Images, Reports, Films, - Presentation States, or Audio recordings. - - The Unified Worklist and Procedure Step Service - Class includes five SOP Classes associated with UPS instances. The SOP Class UID for any UPS Instance - always specifies the UPS Push SOP Class. The separate SOP Classes facilitate better negotiation and - logical implementation groups of functionalities. - - The UPS Push SOP Class allows an SCU to instruct - the SCP to create a new UPS instance, effectively letting a system push a new work item onto the SCP's - worklist. It is important to note that the SCP could be a Worklist Manager that maintains the worklist - for other systems that will perform the work, or the SCP could be a performing system itself that - manages an internal worklist. - - The UPS Pull SOP Class allows an SCU to query a - Worklist Manager (the SCP) for matching UPS instances, and instruct the SCP to update the status and - contents of selected items (UPS instances). The SCU effectively pulls work instructions from the - worklist. As work progresses, the SCU records details of the activities performed and the results - created in the UPS instance. - - The UPS Query SOP Class allows an SCU to query a - Worklist Manager (the SCP), but does not otherwise interact with the UPS instances - - The UPS Watch SOP Class allows an SCU to subscribe - for status update events and retrieve the details of work items (UPS instances) managed by the SCP. - - The UPS Event SOP Class allows an SCP to provide - the actual status update events for work items it manages to relevant (i.e., subscribed) SCUs. - - Each of these services has an equivalent HTTP - operation defined by the UPS-RS Worklist Service (see - ). - - While a Unified Worklist and Procedure Step Service - Class SCP is not required to support UPS-RS, an SCP may choose to support one or more of the UPS-RS - services as an Origin-Server. In this scenario, an SCP/Origin Server shall follow the same internal - behavior for all Workitems irrespective of whether they originated with a DIMSE request or an HTTP - request. A DIMSE request and its equivalent HTTP request with the same parameters shall yield the same - response. - + This Annex defines the Service and SOP Classes associated with a Unified Worklist and Procedure Step. + The Unified Procedure Step Service Class provides for management of simple worklists, including creating new worklist items, querying the worklist, and communicating progress and results. + A worklist is a list of Unified Procedure Step (UPS) instances. Each UPS instance unifies the worklist details for a single requested procedure step together with the result details of the corresponding performed procedure step. There is a one to one relationship between the procedure step request and the procedure step performed. + Unified Procedure Step instances may be used to represent a variety of scheduled tasks such as: Image Processing, Quality Control, Computer Aided Detection, Interpretation, Transcription, Report Verification, or Printing. + The UPS instance can contain details of the requested task such as when it is scheduled to be performed or Workitem Codes describing the requested actions. The UPS may also contain details of the input information the performer needs to do the task and the output the performer produced, such as: Current Images, Prior Images, Reports, Films, Presentation States, or Audio recordings. + The Unified Worklist and Procedure Step Service Class includes five SOP Classes associated with UPS instances. The SOP Class UID for any UPS Instance always specifies the UPS Push SOP Class. The separate SOP Classes facilitate better negotiation and logical implementation groups of functionalities. + The UPS Push SOP Class allows an SCU to instruct the SCP to create a new UPS instance, effectively letting a system push a new work item onto the SCP's worklist. It is important to note that the SCP could be a Worklist Manager that maintains the worklist for other systems that will perform the work, or the SCP could be a performing system itself that manages an internal worklist. + The UPS Pull SOP Class allows an SCU to query a Worklist Manager (the SCP) for matching UPS instances, and instruct the SCP to update the status and contents of selected items (UPS instances). The SCU effectively pulls work instructions from the worklist. As work progresses, the SCU records details of the activities performed and the results created in the UPS instance. + The UPS Query SOP Class allows an SCU to query a Worklist Manager (the SCP), but does not otherwise interact with the UPS instances + The UPS Watch SOP Class allows an SCU to subscribe for status update events and retrieve the details of work items (UPS instances) managed by the SCP. + The UPS Event SOP Class allows an SCP to provide the actual status update events for work items it manages to relevant (i.e., subscribed) SCUs. + Each of these services has an equivalent HTTP operation defined by the UPS-RS Worklist Service (see ). + While a Unified Worklist and Procedure Step Service Class SCP is not required to support UPS-RS, an SCP may choose to support one or more of the UPS-RS services as an Origin-Server. In this scenario, an SCP/Origin Server shall follow the same internal behavior for all Workitems irrespective of whether they originated with a DIMSE request or an HTTP request. A DIMSE request and its equivalent HTTP request with the same parameters shall yield the same response. For example: - A Workitem instance created via DIMSE - N-CREATE can be retrieved via HTTP requests and vice-versa - + A Workitem instance created via DIMSE N-CREATE can be retrieved via HTTP requests and vice-versa - A Workitem instance created via DIMSE - N-CREATE can be updated, have its state changed or be canceled via HTTP requests and vice-versa - + A Workitem instance created via DIMSE N-CREATE can be updated, have its state changed or be canceled via HTTP requests and vice-versa - A C-FIND request and an HTTP SearchForUPS - request with the same parameters shall return the same set of results - + A C-FIND request and an HTTP SearchForUPS request with the same parameters shall return the same set of results - An N-EVENT-REPORT SCU that also supports - HTTP subscriptions will record whether a given subscriber uses DIMSE or WebSockets and send the - appropriate form of notification to that subscriber - + An N-EVENT-REPORT SCU that also supports HTTP subscriptions will record whether a given subscriber uses DIMSE or WebSockets and send the appropriate form of notification to that subscriber - A change made to a Workitem instance will - result in the same event notifications regardless of whether the change was requested via DIMSE - or HTTP - + A change made to a Workitem instance will result in the same event notifications regardless of whether the change was requested via DIMSE or HTTP - A Global Subscription request or a Filtered - Global Subscription request will subscribe an SCU (or User-Agent) to instances created both via - DIMSE and via HTTP requests - + A Global Subscription request or a Filtered Global Subscription request will subscribe an SCU (or User-Agent) to instances created both via DIMSE and via HTTP requests - A DIMSE event subscriber will receive - notifications for relevant changes made via HTTP requests - + A DIMSE event subscriber will receive notifications for relevant changes made via HTTP requests - An HTTP event subscriber will receive - notifications for relevant changes made via DIMSE requests - + An HTTP event subscriber will receive notifications for relevant changes made via DIMSE requests - The mapping between UPS DIMSE operations and UPS-RS - services is defined in. - + The mapping between UPS DIMSE operations and UPS-RS services is defined in .
Unified Procedure Step States - , - - and - - specify how changes in the state of a Unified Procedure Step shall be managed. - + , and specify how changes in the state of a Unified Procedure Step shall be managed.
Unified Procedure Step State Diagram @@ -48780,101 +34144,35 @@
- The following interactions represent an example - sequence of events and state transitions. Observe that the DIMSE Services described here operate on - the same IOD. The multiple UPS SOP Classes thus act in a coordinated manner as specified in this - Annex. - - To create a UPS, an SCU uses an N-CREATE to - push a UPS onto the SCP's worklist. The SCP responds to such requests by creating a Unified - Procedure Step (UPS) with an initial state of SCHEDULED. - + The following interactions represent an example sequence of events and state transitions. Observe that the DIMSE Services described here operate on the same IOD. The multiple UPS SOP Classes thus act in a coordinated manner as specified in this Annex. + To create a UPS, an SCU uses an N-CREATE to push a UPS onto the SCP's worklist. The SCP responds to such requests by creating a Unified Procedure Step (UPS) with an initial state of SCHEDULED. - All UPS Instances are instances of the UPS - Push SOP Class, although the other three SOP Classes (UPS Pull, UPS Watch and UPS Event) may - also operate on the Instance. - + All UPS Instances are instances of the UPS Push SOP Class, although the other three SOP Classes (UPS Pull, UPS Watch and UPS Event) may also operate on the Instance. - To subscribe to receive N-EVENT-REPORTs for a - UPS, or to unsubscribe to stop receiving N-EVENT-REPORTS, an SCU uses an N-ACTION request. The SCU - may be the system that created the UPS as a Push SCU, or may be some other system with a reason to - track the progress and results of a scheduled step. - - To inform interested systems of the state of a - UPS or the SCP itself, an SCP issues N-EVENT-REPORTs to SCUs that have subscribed. - - To find a UPS of interest, an SCU uses a C-FIND - to query the SCP for relevant UPS instances. - - To "claim" and start work on a UPS, an SCU - (which will be referred to here as the "Performing SCU") uses an N-ACTION Change State request to - set the UPS state to IN PROGRESS and provide a transaction UID (which will be referred to here as - the Locking UID). For a SCHEDULED UPS, the SCP responds by changing the UPS state to IN PROGRESS and - recording the transaction UID for future use. For a UPS with other status, the SCP rejects the - request. - - The SCP does not permit the status of a - SCHEDULED UPS to be set to COMPLETED or CANCELED without first being set to IN PROGRESS. - - To modify details of the performed procedure, - the Performing SCU uses an N-SET request to the SCP (providing the Locking UID for the UPS). N-SET - requests on an IN PROGRESS UPS where the Locking UID in the N-SET Data Set does not match the - Locking UID in the UPS are rejected by the SCP. - - To modify the status of the procedure step, the - Performing SCU uses an N-ACTION Change State request to the SCP (providing the Locking UID for the - UPS). N-ACTION Change State requests where the Locking UID in the N-ACTION Data Set does not match - the Locking UID in the UPS are rejected by the SCP. - - The Locking UID effectively limits control of - the state of an IN PROGRESS UPS to only the SCP and the Performing SCU. The SCP does not check - whether IP addresses, AE-Titles, or parameters other than the Locking UID match to determine if the - SCU has permission. - - When the Performing SCU completes work on the - UPS, it N-SETs any values necessary to meet the Final State requirements in, then uses an N-ACTION request - (providing the Locking UID for the UPS during both steps) for the SCP to change the UPS state to - COMPLETED. - - When the Performing SCU abandons work on an - incomplete UPS, it N-SETs any values necessary to meet the Final State requirements in, then uses an N-ACTION request - (providing the Locking UID for the UPS) for the SCP to change the UPS state to CANCELED. - - To request cancellation of a UPS, - non-performing SCUs use an N-ACTION Request Cancel (see - - and - - for example cases). - + To subscribe to receive N-EVENT-REPORTs for a UPS, or to unsubscribe to stop receiving N-EVENT-REPORTS, an SCU uses an N-ACTION request. The SCU may be the system that created the UPS as a Push SCU, or may be some other system with a reason to track the progress and results of a scheduled step. + To inform interested systems of the state of a UPS or the SCP itself, an SCP issues N-EVENT-REPORTs to SCUs that have subscribed. + To find a UPS of interest, an SCU uses a C-FIND to query the SCP for relevant UPS instances. + To "claim" and start work on a UPS, an SCU (which will be referred to here as the "Performing SCU") uses an N-ACTION Change State request to set the UPS state to IN PROGRESS and provide a transaction UID (which will be referred to here as the Locking UID). For a SCHEDULED UPS, the SCP responds by changing the UPS state to IN PROGRESS and recording the transaction UID for future use. For a UPS with other status, the SCP rejects the request. + The SCP does not permit the status of a SCHEDULED UPS to be set to COMPLETED or CANCELED without first being set to IN PROGRESS. + To modify details of the performed procedure, the Performing SCU uses an N-SET request to the SCP (providing the Locking UID for the UPS). N-SET requests on an IN PROGRESS UPS where the Locking UID in the N-SET Data Set does not match the Locking UID in the UPS are rejected by the SCP. + To modify the status of the procedure step, the Performing SCU uses an N-ACTION Change State request to the SCP (providing the Locking UID for the UPS). N-ACTION Change State requests where the Locking UID in the N-ACTION Data Set does not match the Locking UID in the UPS are rejected by the SCP. + The Locking UID effectively limits control of the state of an IN PROGRESS UPS to only the SCP and the Performing SCU. The SCP does not check whether IP addresses, AE-Titles, or parameters other than the Locking UID match to determine if the SCU has permission. + When the Performing SCU completes work on the UPS, it N-SETs any values necessary to meet the Final State requirements in , then uses an N-ACTION request (providing the Locking UID for the UPS during both steps) for the SCP to change the UPS state to COMPLETED. + When the Performing SCU abandons work on an incomplete UPS, it N-SETs any values necessary to meet the Final State requirements in , then uses an N-ACTION request (providing the Locking UID for the UPS) for the SCP to change the UPS state to CANCELED. + To request cancellation of a UPS, non-performing SCUs use an N-ACTION Request Cancel (see and for example cases). - If the UPS is still in the SCHEDULED - state, the SCP first changes the UPS state to IN PROGRESS, and then to CANCELED, issuing the - appropriate N-EVENT-REPORTS. - + If the UPS is still in the SCHEDULED state, the SCP first changes the UPS state to IN PROGRESS, and then to CANCELED, issuing the appropriate N-EVENT-REPORTS. - If the UPS is already IN PROGRESS and - the SCP is itself performing the UPS, it may, at its own discretion, choose to cancel the - UPS as described in the previous paragraph. - + If the UPS is already IN PROGRESS and the SCP is itself performing the UPS, it may, at its own discretion, choose to cancel the UPS as described in the previous paragraph. - If the UPS is already IN PROGRESS and - the SCP is not the performer, it does not change the UPS state to CANCELED, but rather - responds by issuing an N-EVENT-REPORT of the cancellation request to all subscribed SCUs. If - the Performing SCU is listening to N-EVENT-REPORTs it may, at its own discretion, choose to - cancel the UPS as described above. - + If the UPS is already IN PROGRESS and the SCP is not the performer, it does not change the UPS state to CANCELED, but rather responds by issuing an N-EVENT-REPORT of the cancellation request to all subscribed SCUs. If the Performing SCU is listening to N-EVENT-REPORTs it may, at its own discretion, choose to cancel the UPS as described above. - - describes the valid UPS states - + describes the valid UPS states
Implant Template SOP Classes
- Generic Implant Template - Information Model - FIND - + Generic Implant Template Information Model - FIND - 1.2.840.10008.5.1.4.43.2 - + 1.2.840.10008.5.1.4.43.2
- Generic Implant Template - Information Model - MOVE - + Generic Implant Template Information Model - MOVE - 1.2.840.10008.5.1.4.43.3 - + 1.2.840.10008.5.1.4.43.3
- Generic Implant Template - Information Model - GET - + Generic Implant Template Information Model - GET - 1.2.840.10008.5.1.4.43.4 - + 1.2.840.10008.5.1.4.43.4
- Implant Assembly Template - Information Model - FIND - + Implant Assembly Template Information Model - FIND - 1.2.840.10008.5.1.4.44.2 - + 1.2.840.10008.5.1.4.44.2
- Implant Assembly Template - Information Model - MOVE - + Implant Assembly Template Information Model - MOVE - 1.2.840.10008.5.1.4.44.3 - + 1.2.840.10008.5.1.4.44.3
- Implant Assembly Template - Information Model - GET - + Implant Assembly Template Information Model - GET - 1.2.840.10008.5.1.4.44.4 - + 1.2.840.10008.5.1.4.44.4
- Implant Template Group - Information Model - FIND - + Implant Template Group Information Model - FIND - 1.2.840.10008.5.1.4.45.2 - + 1.2.840.10008.5.1.4.45.2
- Implant Template Group - Information Model - MOVE - + Implant Template Group Information Model - MOVE - 1.2.840.10008.5.1.4.45.3 - + 1.2.840.10008.5.1.4.45.3
- Implant Template Group - Information Model - GET - + Implant Template Group Information Model - GET - 1.2.840.10008.5.1.4.45.4 - + 1.2.840.10008.5.1.4.45.4
@@ -48893,9 +34191,7 @@ SCHEDULED @@ -48903,9 +34199,7 @@ IN PROGRESS @@ -48913,11 +34207,7 @@ CANCELED @@ -48925,22 +34215,14 @@ COMPLETED
Unified Procedure Step (UPS) States
- The UPS is scheduled to be - performed. - + The UPS is scheduled to be performed.
- The UPS has been claimed and a - Locking UID has been set. Performance of the UPS has likely started. - + The UPS has been claimed and a Locking UID has been set. Performance of the UPS has likely started.
- The UPS has been permanently - stopped before or during performance of the step. This may be due to voluntary or - involuntary action by a human or machine. Any further UPS-driven work required to - complete the scheduled task must be performed by scheduling another (different) UPS. - + The UPS has been permanently stopped before or during performance of the step. This may be due to voluntary or involuntary action by a human or machine. Any further UPS-driven work required to complete the scheduled task must be performed by scheduling another (different) UPS.
- The UPS has been completed. - + The UPS has been completed.
- COMPLETED and CANCELED are "Final States" that - involve specific requirements on the UPS as described in. - + COMPLETED and CANCELED are "Final States" that involve specific requirements on the UPS as described in . - - describes the valid state transitions (a row in the table defines what should happen in response to - a certain event for each initial state). Details on how the Operations listed in the table should be - carried out are described in. - + describes the valid state transitions (a row in the table defines what should happen in response to a certain event for each initial state). Details on how the Operations listed in the table should be carried out are described in . @@ -48978,14 +34260,10 @@
Unified Procedure Step State Transition Table
- N-CREATE received for this SOP - Instance UID - + N-CREATE received for this SOP Instance UID - Create SOP Instance with empty - transaction UID, Change State to SCHEDULED - + Create SOP Instance with empty transaction UID, Change State to SCHEDULED error @@ -49006,18 +34284,14 @@
- N-ACTION to Change State to IN - PROGRESS with correct transaction UID - + N-ACTION to Change State to IN PROGRESS with correct transaction UID error C307 - Report state change, Record - transaction UID, Change State to IN PROGRESS - + Report state change, Record transaction UID, Change State to IN PROGRESS error @@ -49034,9 +34308,7 @@
- N-ACTION to Change State to IN - PROGRESS without correct transaction UID - + N-ACTION to Change State to IN PROGRESS without correct transaction UID error @@ -49061,9 +34333,7 @@
- N-ACTION to Change State to - SCHEDULED - + N-ACTION to Change State to SCHEDULED error @@ -49088,9 +34358,7 @@
- N-ACTION to Change State to - COMPLETED, with correct transaction UID - + N-ACTION to Change State to COMPLETED, with correct transaction UID error @@ -49101,9 +34369,7 @@ C310 - If Final State Requirements - met, (Report state change, Change State to COMPLETED); Else C304 - + If Final State Requirements met, (Report state change, Change State to COMPLETED); Else C304 warning @@ -49116,9 +34382,7 @@
- N-ACTION to Change State to - COMPLETED, without correct transaction UID - + N-ACTION to Change State to COMPLETED, without correct transaction UID error @@ -49143,22 +34407,17 @@
- N-ACTION to Request Cancel - + N-ACTION to Request Cancel error C307 - Report state change to - IN-PROGRESS, Report state change to CANCELED, Change State to CANCELED - + Report state change to IN-PROGRESS, Report state change to CANCELED, Change State to CANCELED - Report that an Application - Entity requested a cancel. - + Report that an Application Entity requested a cancel. error @@ -49171,9 +34430,7 @@
- N-ACTION to Change State to - CANCELED, with correct transaction UID - + N-ACTION to Change State to CANCELED, with correct transaction UID error @@ -49184,9 +34441,7 @@ C310 - If Final State Requirements - met, (Report state change, Change State to CANCELED); Else C304. - + If Final State Requirements met, (Report state change, Change State to CANCELED); Else C304. error @@ -49199,9 +34454,7 @@
- N-ACTION to Change State to - CANCELED, without correct transaction UID - + N-ACTION to Change State to CANCELED, without correct transaction UID error @@ -49230,23 +34483,13 @@
DIMSE Service Groups - The DIMSE Services shown in,,, - - and - - are applicable to the Unified Procedure Step (UPS) IOD under the UPS Push, UPS Pull, UPS Watch, UPS - Event and UPS Query SOP Classes respectively. - + The DIMSE Services shown in , , , and are applicable to the Unified Procedure Step (UPS) IOD under the UPS Push, UPS Pull, UPS Watch, UPS Event and UPS Query SOP Classes respectively.
DIMSE Service Group Applicable to UPS Push
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -49264,8 +34507,7 @@
- N-ACTION - Request UPS Cancel - + N-ACTION - Request UPS Cancel U/M @@ -49286,8 +34528,7 @@
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -49334,8 +34575,7 @@
- DICOM Message Service Element - + DICOM Message Service Element SCU/SCP @@ -49369,8 +34609,7 @@
- N-ACTION - Request UPS Cancel - + N-ACTION - Request UPS Cancel U/M @@ -49383,8 +34622,7 @@
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -49407,8 +34645,7 @@
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -49428,16 +34665,10 @@
Change UPS State (N-ACTION) - This operation allows an SCU to ask the SCP to - change the state of a Unified Procedure Step (UPS) instance. This operation shall be invoked by the - SCU through the DIMSE N-ACTION Service. - + This operation allows an SCU to ask the SCP to change the state of a Unified Procedure Step (UPS) instance. This operation shall be invoked by the SCU through the DIMSE N-ACTION Service.
Action Information - DICOM AEs that claim conformance to the UPS - Pull SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as - specified in. - + DICOM AEs that claim conformance to the UPS Pull SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in . @@ -49455,8 +34686,7 @@ Tag @@ -49494,147 +34724,56 @@
Service Class User Behavior - An SCU uses N-ACTION to ask the SCP to - change the state of a UPS Instance as shown in. Since all UPSs - are created as instances of the UPS Push SOP Class, the Requested SOP Class UID (0000,0003) in - the N-ACTION request shall be the UID of the UPS Push SOP Class. See - - for further details. - - To take control of a SCHEDULED UPS, an SCU - shall generate a Transaction UID and submit a state change to IN PROGRESS including the - Transaction UID in the submission. The SCU shall record and use the Transaction UID in future - N-ACTION and N-SET requests for that UPS instance. - + An SCU uses N-ACTION to ask the SCP to change the state of a UPS Instance as shown in . Since all UPSs are created as instances of the UPS Push SOP Class, the Requested SOP Class UID (0000,0003) in the N-ACTION request shall be the UID of the UPS Push SOP Class. See for further details. + To take control of a SCHEDULED UPS, an SCU shall generate a Transaction UID and submit a state change to IN PROGRESS including the Transaction UID in the submission. The SCU shall record and use the Transaction UID in future N-ACTION and N-SET requests for that UPS instance. - The performing SCU may wish to - record the Transaction UID in non-volatile storage. This would allow the SCU to - retain control over the UPS after recovering from a crash. - + The performing SCU may wish to record the Transaction UID in non-volatile storage. This would allow the SCU to retain control over the UPS after recovering from a crash. - If two SCUs try to take control - of a UPS, the second SCU will get an error since the first SCU established the - correct Transaction UID, so the Transaction UID provided by the second SCU is - incorrect. - + If two SCUs try to take control of a UPS, the second SCU will get an error since the first SCU established the correct Transaction UID, so the Transaction UID provided by the second SCU is incorrect. - Upon completion of an IN PROGRESS UPS it - controls, an SCU shall submit a state change to COMPLETED and include the Transaction UID for - the UPS instance. - - To cancel an IN PROGRESS UPS for which it - has the Transaction UID, an SCU shall submit a state change to CANCELED and include the - Transaction UID for the UPS instance. - + Upon completion of an IN PROGRESS UPS it controls, an SCU shall submit a state change to COMPLETED and include the Transaction UID for the UPS instance. + To cancel an IN PROGRESS UPS for which it has the Transaction UID, an SCU shall submit a state change to CANCELED and include the Transaction UID for the UPS instance. - Prior to submitting the state - change to CANCELED, the performing SCU can N-SET the values of Reason For - Cancellation, Procedure Step Discontinuation Reason Code Sequence, Contact Display - Name or Contact URI to provide information to observing SCUs about the context of - the cancellation. - + Prior to submitting the state change to CANCELED, the performing SCU can N-SET the values of Reason For Cancellation, Procedure Step Discontinuation Reason Code Sequence, Contact Display Name or Contact URI to provide information to observing SCUs about the context of the cancellation. - To request cancellation of an - IN PROGRESS UPS for which it does not have the Transaction UID, an SCU uses the - Request UPS Cancel action as described in, rather - than a Change UPS State action. - + To request cancellation of an IN PROGRESS UPS for which it does not have the Transaction UID, an SCU uses the Request UPS Cancel action as described in , rather than a Change UPS State action. - Prior to submitting a state change to - COMPLETED or CANCELED for a UPS instance it controls, the SCU shall perform any N-SETs necessary - for the UPS to meet Final State requirements as described in. - - At any time after receipt of the - N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. - + Prior to submitting a state change to COMPLETED or CANCELED for a UPS instance it controls, the SCU shall perform any N-SETs necessary for the UPS to meet Final State requirements as described in . + At any time after receipt of the N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request.
Service Class Provider Behavior - The SCP shall perform the submitted state - change for the identified UPS instance by setting the Procedure Step State (0074,1000) to the - requested value, or shall report the appropriate failure response code. - - Upon successfully changing the state of a - UPS instance to IN PROGRESS, the SCP shall record the Transaction UID provided by the SCU in the - Transaction UID (0008,1195) of the UPS instance. - - Upon completion of the N-ACTION request, - the SCP shall return, via the N-ACTION response primitive, the N-ACTION Status Code applicable - to the associated request as shown in. - - The SCP shall only perform legal state - changes as described in. - - The SCP shall refuse requests to change the - state of an IN PROGRESS UPS unless the Transaction UID of the UPS instance is provided in the - request. - - The SCP shall refuse requests to change the - state of an IN PROGRESS UPS to COMPLETED or CANCELED if the Final State requirements described - in - - have not been met. - - After the state of the UPS instance has - been changed to COMPLETED or CANCELED, the SCP shall not delete the instance until all deletion - locks have been removed. - + The SCP shall perform the submitted state change for the identified UPS instance by setting the Procedure Step State (0074,1000) to the requested value, or shall report the appropriate failure response code. + Upon successfully changing the state of a UPS instance to IN PROGRESS, the SCP shall record the Transaction UID provided by the SCU in the Transaction UID (0008,1195) of the UPS instance. + Upon completion of the N-ACTION request, the SCP shall return, via the N-ACTION response primitive, the N-ACTION Status Code applicable to the associated request as shown in . + The SCP shall only perform legal state changes as described in . + The SCP shall refuse requests to change the state of an IN PROGRESS UPS unless the Transaction UID of the UPS instance is provided in the request. + The SCP shall refuse requests to change the state of an IN PROGRESS UPS to COMPLETED or CANCELED if the Final State requirements described in have not been met. + After the state of the UPS instance has been changed to COMPLETED or CANCELED, the SCP shall not delete the instance until all deletion locks have been removed. - See - - for a description of how SCUs place and remove deletion locks and see - - Reliable Watchers and Deletion Locks for further discussion. - + See for a description of how SCUs place and remove deletion locks and see Reliable Watchers and Deletion Locks for further discussion. - The SCP may also modify the Procedure Step - State (0074,1000) of a UPS instance independently of an N-ACTION request, e.g., if the SCP is - performing the procedure step itself, or if it has been determined that the performing SCU has - been disabled. - + The SCP may also modify the Procedure Step State (0074,1000) of a UPS instance independently of an N-ACTION request, e.g., if the SCP is performing the procedure step itself, or if it has been determined that the performing SCU has been disabled. - If the SCP is not performing the - procedure step, this should be done with caution. - + If the SCP is not performing the procedure step, this should be done with caution. - Upon successfully changing the state of a - UPS instance, the SCP shall carry out the appropriate N-EVENT-REPORT behavior as described in - - if it supports the UPS Event SOP Class as an SCP. - - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting - authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP - Class. - + Upon successfully changing the state of a UPS instance, the SCP shall carry out the appropriate N-EVENT-REPORT behavior as described in if it supports the UPS Event SOP Class as an SCP. + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP Class.
Status Codes - - defines the status code values that might be returned in a N-ACTION response. General status - code values and fields related to status code values are defined for N-ACTION DIMSE Service in - - . - + defines the status code values that might be returned in a N-ACTION response. General status code values and fields related to status code values are defined for N-ACTION DIMSE Service in .
Change UPS State - Action Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
@@ -49656,9 +34795,7 @@ Success
N-ACTION Response Status Values [for Change UPS State]
- The requested state change - was performed - + The requested state change was performed 0000 @@ -49669,9 +34806,7 @@ Warning - The UPS is already in the - requested state of CANCELED - + The UPS is already in the requested state of CANCELED B304 @@ -49679,9 +34814,7 @@
- The UPS is already in the - requested state of COMPLETED - + The UPS is already in the requested state of COMPLETED B306 @@ -49692,9 +34825,7 @@ Failure - Failed: The UPS may no - longer be updated - + Failed: The UPS may no longer be updated C300 @@ -49702,9 +34833,7 @@
- Failed: The correct - Transaction UID was not provided - + Failed: The correct Transaction UID was not provided C301 @@ -49712,9 +34841,7 @@
- Failed: The UPS is already - IN PROGRESS - + Failed: The UPS is already IN PROGRESS C302 @@ -49722,9 +34849,7 @@
- Failed: The UPS may only - become SCHEDULED via N-CREATE, not N-SET or N-ACTION - + Failed: The UPS may only become SCHEDULED via N-CREATE, not N-SET or N-ACTION C303 @@ -49732,9 +34857,7 @@
- Failed: The UPS has not met - final state requirements for the requested state change - + Failed: The UPS has not met final state requirements for the requested state change C304 @@ -49742,9 +34865,7 @@
- Failed: Specified SOP - Instance UID does not exist or is not a UPS Instance managed by this SCP - + Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP C307 @@ -49752,9 +34873,7 @@
- Failed: The UPS is not yet - in the "IN PROGRESS" state - + Failed: The UPS is not yet in the "IN PROGRESS" state C310 @@ -49766,19 +34885,10 @@
Request UPS Cancel (N-ACTION) - This operation allows an SCU that does not - control a given Unified Procedure Step (UPS) instance to request to the SCP that the instance be - canceled. This operation shall be invoked by the SCU through the DIMSE N-ACTION Service. - + This operation allows an SCU that does not control a given Unified Procedure Step (UPS) instance to request to the SCP that the instance be canceled. This operation shall be invoked by the SCU through the DIMSE N-ACTION Service.
Action Information - DICOM AEs that claim conformance to the UPS - Push SOP Class as an SCU or an SCP shall support the Action Types and Action Information as - specified in. DICOM AEs that claim - conformance to the UPS Watch SOP Class as an SCP or claim conformance to the UPS Watch SOP Class - as an SCU and choose to implement Request UPS Cancel shall support the Action Types and Action - Information as specified in. - + DICOM AEs that claim conformance to the UPS Push SOP Class as an SCU or an SCP shall support the Action Types and Action Information as specified in . DICOM AEs that claim conformance to the UPS Watch SOP Class as an SCP or claim conformance to the UPS Watch SOP Class as an SCU and choose to implement Request UPS Cancel shall support the Action Types and Action Information as specified in . @@ -49796,8 +34906,7 @@ Tag @@ -49810,8 +34919,7 @@ 2 @@ -49869,92 +34974,31 @@
Service Class User Behavior - An SCU uses N-ACTION to request to the SCP - that the state of a UPS Instance be changed to CANCELED as shown in. Since all UPSs are created as - instances of the UPS Push SOP Class, the Requested SOP Class UID (0000,0003) in the N-ACTION - request shall be the UID of the UPS Push SOP Class. See - - for further details. - - The SCU may include a Reason For - Cancellation and/or a proposed Procedure Step Discontinuation Reason Code Sequence. - - The SCU may also provide a Contact Display - Name and/or a Contact URI for the person with whom the cancel request may be discussed. - + An SCU uses N-ACTION to request to the SCP that the state of a UPS Instance be changed to CANCELED as shown in . Since all UPSs are created as instances of the UPS Push SOP Class, the Requested SOP Class UID (0000,0003) in the N-ACTION request shall be the UID of the UPS Push SOP Class. See for further details. + The SCU may include a Reason For Cancellation and/or a proposed Procedure Step Discontinuation Reason Code Sequence. + The SCU may also provide a Contact Display Name and/or a Contact URI for the person with whom the cancel request may be discussed. - An N-ACTION Status Code indicating - success means that the Request was accepted, not that the UPS has been canceled. The system - performing the UPS is not obliged to honor the request to cancel and in some scenarios, may - not even receive notification of the request. See. - + An N-ACTION Status Code indicating success means that the Request was accepted, not that the UPS has been canceled. The system performing the UPS is not obliged to honor the request to cancel and in some scenarios, may not even receive notification of the request. See . - At any time after receipt of the - N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. - - To cancel an IN PROGRESS UPS that the SCU - is itself performing, the SCU shall instead use the Change UPS State action as described in. - + At any time after receipt of the N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. + To cancel an IN PROGRESS UPS that the SCU is itself performing, the SCU shall instead use the Change UPS State action as described in .
Service Class Provider Behavior - The SCP shall send appropriate "UPS Cancel - Requested" N-EVENT-REPORT messages, as described in - - or shall report the appropriate failure response code. - + The SCP shall send appropriate "UPS Cancel Requested" N-EVENT-REPORT messages, as described in or shall report the appropriate failure response code. - If provided, the Reason For - Cancellation, a proposed Procedure Step Discontinuation Reason Code Sequence, a Contact - Display Name and a Contact URI of someone responsible for the Cancel request might be useful - in deciding to cancel the UPS or might be displayed to an operator so they can make contact - for the purpose of clarifying or confirming the Cancel request. If the SCP is the performer - and chooses to actually Cancel the UPS, it may at its own discretion set the Procedure Step - Discontinuation Reason Code Sequence in the UPS instance based on the corresponding values - provided. - + If provided, the Reason For Cancellation, a proposed Procedure Step Discontinuation Reason Code Sequence, a Contact Display Name and a Contact URI of someone responsible for the Cancel request might be useful in deciding to cancel the UPS or might be displayed to an operator so they can make contact for the purpose of clarifying or confirming the Cancel request. If the SCP is the performer and chooses to actually Cancel the UPS, it may at its own discretion set the Procedure Step Discontinuation Reason Code Sequence in the UPS instance based on the corresponding values provided. - If the Procedure Step State (0074,1000) of - the UPS instance is still SCHEDULED, the SCP shall change the Procedure Step State, as described - in, first to IN PROGRESS and then to - CANCELED, ensuring that the Final State requirements, described in, are met. - - If the Procedure Step State (0074,1000) of - the UPS instance is IN PROGRESS, and the SCP is itself the performer of the UPS, the SCP may, at - its own discretion, choose to cancel the UPS as described in. - - If the SCP is the performer of the UPS and - chooses not to cancel, or if there is no possibility that the performing SCU will be informed of - the cancel request (e.g., the subscription list for the UPS is empty, or the SCP has determined - that the performing SCU has been disabled), the SCP may return a failure. - - Upon completion of the N-ACTION request, - the SCP shall return, via the N-ACTION response primitive, the N-ACTION Status Code applicable - to the associated request as shown in. - - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting - authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP - Class. - + If the Procedure Step State (0074,1000) of the UPS instance is still SCHEDULED, the SCP shall change the Procedure Step State, as described in , first to IN PROGRESS and then to CANCELED, ensuring that the Final State requirements, described in , are met. + If the Procedure Step State (0074,1000) of the UPS instance is IN PROGRESS, and the SCP is itself the performer of the UPS, the SCP may, at its own discretion, choose to cancel the UPS as described in . + If the SCP is the performer of the UPS and chooses not to cancel, or if there is no possibility that the performing SCU will be informed of the cancel request (e.g., the subscription list for the UPS is empty, or the SCP has determined that the performing SCU has been disabled), the SCP may return a failure. + Upon completion of the N-ACTION request, the SCP shall return, via the N-ACTION response primitive, the N-ACTION Status Code applicable to the associated request as shown in . + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP Class.
Status Codes - - defines the status code values that might be returned in a N-ACTION response. General status - code values and fields related to status code values are defined for N-ACTION DIMSE Service in - . - + defines the status code values that might be returned in a N-ACTION response. General status code values and fields related to status code values are defined for N-ACTION DIMSE Service in .
Request UPS Cancel - Action Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Reason For Cancellation - + Reason For Cancellation (0074,1238) @@ -49822,9 +34930,7 @@
- Procedure Step - Discontinuation Reason Code Sequence - + Procedure Step Discontinuation Reason Code Sequence (0074,100e) @@ -49836,10 +34942,9 @@
- >Include - - - +>Include + +
@@ -49976,9 +35020,7 @@ Success
N-ACTION Response Status Values [for Request UPS Cancel]
- The cancel request is - acknowledged - + The cancel request is acknowledged 0000 @@ -49989,9 +35031,7 @@ Warning - The UPS is already in the - requested state of CANCELED - + The UPS is already in the requested state of CANCELED B304 @@ -50002,9 +35042,7 @@ Failure - Failed: The UPS is already - COMPLETED - + Failed: The UPS is already COMPLETED C311 @@ -50012,9 +35050,7 @@
- Failed: Performer chooses - not to cancel - + Failed: Performer chooses not to cancel C313 @@ -50022,9 +35058,7 @@
- Failed: Specified SOP - Instance UID does not exist or is not a UPS Instance managed by this SCP - + Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP C307 @@ -50032,9 +35066,7 @@
- Failed: The performer - cannot be contacted - + Failed: The performer cannot be contacted C312 @@ -50046,17 +35078,10 @@
Subscribe/Unsubscribe to Receive UPS Event Reports (N-ACTION) - This operation allows an SCU to subscribe with - an SCP in order to receive N-EVENT-REPORTS of subsequent changes to the state of a UPS instance, or - to unsubscribe in order to no longer receive such N-EVENT-REPORTs. This operation shall be invoked - by the SCU through the DIMSE N-ACTION Service. - + This operation allows an SCU to subscribe with an SCP in order to receive N-EVENT-REPORTS of subsequent changes to the state of a UPS instance, or to unsubscribe in order to no longer receive such N-EVENT-REPORTs. This operation shall be invoked by the SCU through the DIMSE N-ACTION Service.
Action Information - DICOM AEs that claim conformance to the UPS - Watch SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as - specified in. - + DICOM AEs that claim conformance to the UPS Watch SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in . @@ -50074,17 +35099,14 @@ Tag
Subscribe/Unsubscribe to Receive UPS Event Reports - Action Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Subscribe to Receive UPS - Event Reports - + Subscribe to Receive UPS Event Reports 3 @@ -50112,9 +35134,7 @@
- Match Keys (see) - + Match Keys (see ) 1/1 @@ -50122,9 +35142,7 @@
- Unsubscribe from Receiving - UPS Event Reports - + Unsubscribe from Receiving UPS Event Reports 4 @@ -50141,9 +35159,7 @@
- Suspend Global - Subscription - + Suspend Global Subscription 5 @@ -50160,46 +35176,15 @@
- Each AE may be in one of three UPS - Subscription States for each existing UPS Instance: Not Subscribed, Subscribed with Deletion - Lock, or Subscribed w/o Deletion Lock. The UPS Subscription State determines whether - N-EVENT-REPORTs relating to a UPS Instance will be sent to the AE. - - Each AE may also be in one of three Global - Subscription States for a given SCP: No Global Subscription, Globally Subscribed with Deletion - Lock, Globally Subscribed w/o Deletion Lock. The Global Subscription State mainly determines the - initial UPS Subscription State for an AE and new UPS Instances created by the SCP. Changes to - the Global Subscription State can also change the UPS Subscription State for existing UPS - Instances as described in. - - The three Subscription actions in - - are used to manage the UPS Subscription State and Global Subscription State of an AE. - + Each AE may be in one of three UPS Subscription States for each existing UPS Instance: Not Subscribed, Subscribed with Deletion Lock, or Subscribed w/o Deletion Lock. The UPS Subscription State determines whether N-EVENT-REPORTs relating to a UPS Instance will be sent to the AE. + Each AE may also be in one of three Global Subscription States for a given SCP: No Global Subscription, Globally Subscribed with Deletion Lock, Globally Subscribed w/o Deletion Lock. The Global Subscription State mainly determines the initial UPS Subscription State for an AE and new UPS Instances created by the SCP. Changes to the Global Subscription State can also change the UPS Subscription State for existing UPS Instances as described in . + The three Subscription actions in are used to manage the UPS Subscription State and Global Subscription State of an AE. - - describes the UPS Subscription State transitions of an AE for a given UPS Instance. Each row in - the table defines what should happen in response to a Subscription Action, or a UPS creation - event, given the initial state. The table also shows when an initial event message should be - sent to the AE describing the "Current UPS State". - + describes the UPS Subscription State transitions of an AE for a given UPS Instance. Each row in the table defines what should happen in response to a Subscription Action, or a UPS creation event, given the initial state. The table also shows when an initial event message should be sent to the AE describing the "Current UPS State". - In general, instance specific - instructions take precedence over global instructions. The exception is the Unsubscribe - Globally instruction, which removes all subscriptions, global and specific. To simply stop - globally subscribing to new instances without removing specific subscriptions, use the - Suspend Global Subscription message. - + In general, instance specific instructions take precedence over global instructions. The exception is the Unsubscribe Globally instruction, which removes all subscriptions, global and specific. To simply stop globally subscribing to new instances without removing specific subscriptions, use the Suspend Global Subscription message. - Most actions affect only the UPS - Subscription State of a single UPS Instance. However, Global actions potentially affect all - existing UPS Instances managed by the SCP and this is indicated in the following table by "All". - For example, in the "AE Subscribes Globally with Lock" row, the content of the "Not Subscribed" - cell means that in addition to setting the Global Subscription State for the AE to "Global - Subscription with Lock", all existing UPS Instances whose UPS Subscription State for the - Receiving AE is "Not Subscribed" will each have their UPS Subscription State changed to - "Subscribed with Lock" and an event will be sent to the Receiving AE for each Instance. - + Most actions affect only the UPS Subscription State of a single UPS Instance. However, Global actions potentially affect all existing UPS Instances managed by the SCP and this is indicated in the following table by "All". For example, in the "AE Subscribes Globally with Lock" row, the content of the "Not Subscribed" cell means that in addition to setting the Global Subscription State for the AE to "Global Subscription with Lock", all existing UPS Instances whose UPS Subscription State for the Receiving AE is "Not Subscribed" will each have their UPS Subscription State changed to "Subscribed with Lock" and an event will be sent to the Receiving AE for each Instance. @@ -50234,9 +35219,7 @@
UPS Subscription State Transition Table
- A UPS is Created when the - AE Global Subscription State is "No Global Subscription" - + A UPS is Created when the AE Global Subscription State is "No Global Subscription" Go to Not Subscribed @@ -50259,14 +35242,10 @@
- A UPS is Created when the - AE Global Subscription State is "Global Subscription with Lock" - + A UPS is Created when the AE Global Subscription State is "Global Subscription with Lock" - Go to Subscribed with Lock; - Send initial event - + Go to Subscribed with Lock; Send initial event @@ -50286,14 +35265,10 @@
- A UPS is Created when the - AE Global Subscription State is "Global Subscription w/o Lock" - + A UPS is Created when the AE Global Subscription State is "Global Subscription w/o Lock" - Go to Subscribed w/o Lock; - Send initial event - + Go to Subscribed w/o Lock; Send initial event @@ -50313,9 +35288,7 @@
- AE Subscribes Globally with - Lock - + AE Subscribes Globally with Lock @@ -50324,33 +35297,26 @@ - AE Global State is now "Global Sub. with Lock"; - - - All Go to Subscribed with - Lock; All Send initial event + AE Global State is now "Global Sub. with Lock"; + All Go to Subscribed with Lock; All Send initial event - AE Global State is now "Global Sub. with Lock"; - + AE Global State is now "Global Sub. with Lock"; No UPS state change; - AE Global State is now "Global Sub. with Lock"; - + AE Global State is now "Global Sub. with Lock"; No UPS state change;
- AE Subscribes Globally w/o - Lock - + AE Subscribes Globally w/o Lock @@ -50359,17 +35325,12 @@ - AE Global State is now "Global Sub. w/o Lock" - ; - - All Go to Subscribed w/o - Lock; - + AE Global State is now "Global Sub. w/o Lock"; + All Go to Subscribed w/o Lock; - AE Global State is now "Global Sub. w/o Lock"; - + AE Global State is now "Global Sub. w/o Lock"; No UPS state change; @@ -50377,17 +35338,14 @@ - AE Global State is now "Global Sub. w/o Lock"; - + AE Global State is now "Global Sub. w/o Lock"; No UPS state change;
- AE Subscribes to Specific - UPS with Lock - + AE Subscribes to Specific UPS with Lock @@ -50395,26 +35353,18 @@ - Go to Subscribed with Lock; - Send initial event - + Go to Subscribed with Lock; Send initial event - No UPS state change; Send - initial event - + No UPS state change; Send initial event - Go to Subscribed with Lock; - Send initial event - + Go to Subscribed with Lock; Send initial event
- AE Subscribes to Specific - UPS without Lock - + AE Subscribes to Specific UPS without Lock @@ -50422,26 +35372,18 @@ - Go to Subscribed w/o Lock; - Send initial event - + Go to Subscribed w/o Lock; Send initial event - Go to Subscribed w/o Lock; - Send initial event - + Go to Subscribed w/o Lock; Send initial event - No UPS state change; Send - initial event - + No UPS state change; Send initial event
- AE Unsubscribes from - Specific UPS - + AE Unsubscribes from Specific UPS @@ -50460,8 +35402,7 @@
- AE Unsubscribes Globally - + AE Unsubscribes Globally @@ -50470,33 +35411,25 @@ - AE Global State is now "No Global - Subscription"; - + AE Global State is now "No Global Subscription"; No UPS state change; - AE Global State is now "No Global Subscription"; - - - All Go to Not Subscribed; + AE Global State is now "No Global Subscription"; + All Go to Not Subscribed; - AE Global State is now "No Global Subscription"; - - - All Go to Not Subscribed; + AE Global State is now "No Global Subscription"; + All Go to Not Subscribed;
- AE Suspends Global - Subscription - + AE Suspends Global Subscription @@ -50505,257 +35438,89 @@ - AE Global State is now "No Global Subscription"; - + AE Global State is now "No Global Subscription"; No UPS state change; - AE Global State is now "No Global Subscription"; - + AE Global State is now "No Global Subscription"; No UPS state change; - AE Global State is now "No Global Subscription"; - + AE Global State is now "No Global Subscription"; No UPS state change;
- See - - Reliable Watchers and Deletion Locks for further discussion of deletion locks. - + See Reliable Watchers and Deletion Locks for further discussion of deletion locks.
Service Class User Behavior - The SCU subscribing to track the progress - and results of the scheduled procedure step may be the system that created the UPS as an SCU of - the UPS Push SOP Class, or it may be some other interested observer. - - An SCU shall use the N-ACTION primitive to - request the SCP to subscribe an AE (usually the requesting SCU) to receive event reports - relating to UPS instances managed by the SCP. Since all UPSs are created as instances of the UPS - Push SOP Class, the Requested SOP Class UID (0000,0003) in the N-ACTION request shall be the UID - of the UPS Push SOP Class. See - - for further details. - - An SCU shall also use the N-ACTION - primitive to request the SCP to unsubscribe an AE to stop receiving event reports relating to - UPS instances managed by the SCP. Action Information is specified in. The SCU shall always provide the - AE-TITLE that is to receive (or stop receiving) the N-EVENT-REPORTs. - - To subscribe for events relating to a - single specific UPS instance managed by the SCP, the SCU shall use Action Type ID 3 (Subscribe - to Receive UPS Event Reports) and provide the SOP Instance UID of the specific UPS instance in - the N-ACTION primitive request. The SCU shall indicate a need for the UPS instance to persist - after its state has changed to COMPLETED or CANCELED by setting the value of the Deletion Lock - to TRUE. Otherwise the SCU shall set the value of the Deletion Lock to FALSE. - - To unsubscribe for events relating to a - single specific UPS instance managed by the SCP, the SCU shall use Action Type ID 4 (Unsubscribe - from Receiving UPS Event Reports) and provide the SOP Instance UID of the specific UPS instance - in the N-ACTION primitive request. - - To subscribe for events relating to all - current and subsequently created UPS instances managed by the SCP, the SCU shall use Action Type - ID 3 (Subscribe to Receive UPS Event Reports) and provide the well-known UID - 1.2.840.10008.5.1.4.34.5 in the N-ACTION primitive request. The SCU shall indicate a need for - UPS instances to persist after their states have changed to COMPLETED or CANCELED by setting the - value of the Deletion Lock to TRUE. Otherwise the SCU shall set the value of the Deletion Lock - to FALSE. - + The SCU subscribing to track the progress and results of the scheduled procedure step may be the system that created the UPS as an SCU of the UPS Push SOP Class, or it may be some other interested observer. + An SCU shall use the N-ACTION primitive to request the SCP to subscribe an AE (usually the requesting SCU) to receive event reports relating to UPS instances managed by the SCP. Since all UPSs are created as instances of the UPS Push SOP Class, the Requested SOP Class UID (0000,0003) in the N-ACTION request shall be the UID of the UPS Push SOP Class. See for further details. + An SCU shall also use the N-ACTION primitive to request the SCP to unsubscribe an AE to stop receiving event reports relating to UPS instances managed by the SCP. Action Information is specified in . The SCU shall always provide the AE-TITLE that is to receive (or stop receiving) the N-EVENT-REPORTs. + To subscribe for events relating to a single specific UPS instance managed by the SCP, the SCU shall use Action Type ID 3 (Subscribe to Receive UPS Event Reports) and provide the SOP Instance UID of the specific UPS instance in the N-ACTION primitive request. The SCU shall indicate a need for the UPS instance to persist after its state has changed to COMPLETED or CANCELED by setting the value of the Deletion Lock to TRUE. Otherwise the SCU shall set the value of the Deletion Lock to FALSE. + To unsubscribe for events relating to a single specific UPS instance managed by the SCP, the SCU shall use Action Type ID 4 (Unsubscribe from Receiving UPS Event Reports) and provide the SOP Instance UID of the specific UPS instance in the N-ACTION primitive request. + To subscribe for events relating to all current and subsequently created UPS instances managed by the SCP, the SCU shall use Action Type ID 3 (Subscribe to Receive UPS Event Reports) and provide the well-known UID 1.2.840.10008.5.1.4.34.5 in the N-ACTION primitive request. The SCU shall indicate a need for UPS instances to persist after their states have changed to COMPLETED or CANCELED by setting the value of the Deletion Lock to TRUE. Otherwise the SCU shall set the value of the Deletion Lock to FALSE. - This "global subscription" is useful - for SCUs that wish to monitor all activities without having to issue regular C-FINDs to - identify new UPS instances. - + This "global subscription" is useful for SCUs that wish to monitor all activities without having to issue regular C-FINDs to identify new UPS instances. - To subscribe for events relating to a - filtered subset of all current and subsequently created UPS instances (Filtered Global - Subscription) managed by the SCP, the SCU shall use Action Type ID 3 (Subscribe to Receive UPS - Event Reports) and provide both the well-known UID 1.2.840.10008.5.1.4.34.5.1 and a set of - Matching Keys and values in the N-ACTION primitive request (see - ). The SCU shall indicate a need for UPS instances to persist after their states have changed to - COMPLETED or CANCELED by setting the value of the Deletion Lock to TRUE. Otherwise the SCU shall - set the value of the Deletion Lock to FALSE. - + To subscribe for events relating to a filtered subset of all current and subsequently created UPS instances (Filtered Global Subscription) managed by the SCP, the SCU shall use Action Type ID 3 (Subscribe to Receive UPS Event Reports) and provide both the well-known UID 1.2.840.10008.5.1.4.34.5.1 and a set of Matching Keys and values in the N-ACTION primitive request (see ). The SCU shall indicate a need for UPS instances to persist after their states have changed to COMPLETED or CANCELED by setting the value of the Deletion Lock to TRUE. Otherwise the SCU shall set the value of the Deletion Lock to FALSE. - The well-known UID for a Filtered - Global Subscription is distinct from the Global Subscription well-known UID. - + The well-known UID for a Filtered Global Subscription is distinct from the Global Subscription well-known UID. - To unsubscribe for events relating to all - current UPS instances managed by the SCP and also stop being subscribed to subsequently created - UPS instances, the SCU shall use Action Type ID 4 (Unsubscribe from Receiving UPS Event Reports) - and provide the well-known UID 1.2.840.10008.5.1.4.34.5 in the N-ACTION primitive request. - + To unsubscribe for events relating to all current UPS instances managed by the SCP and also stop being subscribed to subsequently created UPS instances, the SCU shall use Action Type ID 4 (Unsubscribe from Receiving UPS Event Reports) and provide the well-known UID 1.2.840.10008.5.1.4.34.5 in the N-ACTION primitive request. - This "global unsubscription" is useful - for SCUs that wish to stop monitoring all activities and release all deletion locks (if any) - placed for this subscriber. - + This "global unsubscription" is useful for SCUs that wish to stop monitoring all activities and release all deletion locks (if any) placed for this subscriber. - To just stop being subscribed to - subsequently created UPS instances, but still continue to receive events for currently - subscribed instances managed by the SCP, the SCU shall use Action Type ID 5 (Suspend Global - Subscription) and provide the well-known UID 1.2.840.10008.5.1.4.34.5 in the N-ACTION primitive - request. - - For each UPS instance on which the SCU has - placed a deletion lock, either explicitly on the specific instance or implicitly via a global - subscription with lock, the SCU shall remove the deletion lock once any needed final state - information for the instance has been obtained. The deletion lock may be removed either by - unsubscribing or by subscribing with the value of the Deletion Lock set to FALSE. - + To just stop being subscribed to subsequently created UPS instances, but still continue to receive events for currently subscribed instances managed by the SCP, the SCU shall use Action Type ID 5 (Suspend Global Subscription) and provide the well-known UID 1.2.840.10008.5.1.4.34.5 in the N-ACTION primitive request. + For each UPS instance on which the SCU has placed a deletion lock, either explicitly on the specific instance or implicitly via a global subscription with lock, the SCU shall remove the deletion lock once any needed final state information for the instance has been obtained. The deletion lock may be removed either by unsubscribing or by subscribing with the value of the Deletion Lock set to FALSE. - The SCP will retain COMPLETED or - CANCELED UPS Instances until all deletion locks have been released. Failure by SCUs to - release the deletion lock may cause problems for the SCP. SCUs that do not have a - significant need for the final state information, or who cannot dependably remove deletion - locks should not use deletion locks. - + The SCP will retain COMPLETED or CANCELED UPS Instances until all deletion locks have been released. Failure by SCUs to release the deletion lock may cause problems for the SCP. SCUs that do not have a significant need for the final state information, or who cannot dependably remove deletion locks should not use deletion locks. - The successful N-ACTION Response Status - Code indicates that the SCP has received the N-ACTION request and the Subscription State for the - AE has been successfully modified. - + The successful N-ACTION Response Status Code indicates that the SCP has received the N-ACTION request and the Subscription State for the AE has been successfully modified. - When subscribing to a specific - instance, the SCU can also expect to receive an initial N-EVENT-REPORT containing - the current state of the UPS instance. When subscribing globally with the Deletion - Lock set to TRUE, the SCU can expect to receive initial N-EVENT-REPORTs for every - instance currently managed by the SCP. Initial N-EVENT-REPORTs for newly created - instances, received as a result of a global subscription, will appear as transitions - to the SCHEDULED state. - + When subscribing to a specific instance, the SCU can also expect to receive an initial N-EVENT-REPORT containing the current state of the UPS instance. When subscribing globally with the Deletion Lock set to TRUE, the SCU can expect to receive initial N-EVENT-REPORTs for every instance currently managed by the SCP. Initial N-EVENT-REPORTs for newly created instances, received as a result of a global subscription, will appear as transitions to the SCHEDULED state. - The UPS-RS User-Agent is - responsible for opening the N-EVENT-REPORT communication channel (see). The UPS-RS User-Agent is - also responsible for re-establishing the N-EVENT-REPORT communication channel if it - is disconnected. This differs from the DIMSE approach where the UPS SCP opens an - Association for N-EVENT-REPORT messages as necessary. - + The UPS-RS User-Agent is responsible for opening the N-EVENT-REPORT communication channel (see ). The UPS-RS User-Agent is also responsible for re-establishing the N-EVENT-REPORT communication channel if it is disconnected. This differs from the DIMSE approach where the UPS SCP opens an Association for N-EVENT-REPORT messages as necessary. - A warning N-ACTION Response Status Code of - "Deletion Lock not granted", indicates that the AE subscription requested by the SCU was - successful, but the deletion lock has not been set. - - A failure N-ACTION Response Status Code - indicates that the subscription state change requested will not be processed and no subscription - states have been changed. The action taken by the SCU upon receiving this status is beyond the - scope of this Standard. - - At any time after receipt of the - N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. - + A warning N-ACTION Response Status Code of "Deletion Lock not granted", indicates that the AE subscription requested by the SCU was successful, but the deletion lock has not been set. + A failure N-ACTION Response Status Code indicates that the subscription state change requested will not be processed and no subscription states have been changed. The action taken by the SCU upon receiving this status is beyond the scope of this Standard. + At any time after receipt of the N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request.
Service Class Provider Behavior - Upon receipt of the N-ACTION request, the - SCP shall attempt to update the Global Subscription State and/or UPS Subscription State of the - specified AE with respect to the specified SOP Instance UID as described in - - and then return, via the N-ACTION response primitive, the appropriate N-ACTION Response Status - Code. - - The SCP may optionally allow an Application - Entity to subscribe globally to a filtered set of UPS Instances. In this case, the Application - Entity will only be subscribed to existing and future UPS Instances that match the search - criteria specified by the Matching Keys of the N-ACTION request (see). If the SCP does not support - Filtered Global Subscription it will return a Failure response with a Code of C307 (see). - - A success status conveys that the Global - Subscription State and/or UPS Subscription State for the AE specified in Receiving AE - (0074,1234) was successfully modified by the SCP. The AE-TITLE in Receiving AE (0074,1234) may - be different than the AE-TITLE used by the SCU for the association negotiation. The SCP shall - use the AE-TITLE specified in Receiving AE (0074,1234). This allows systems to subscribe other - systems they know would be interested in events for a certain UPS. - - For all UPS instances managed by the SCP, - the SCP shall send N-EVENT-REPORTS (as described in) to AEs - that have a UPS Subscription State of "Subscribed with Lock" or "Subscribed w/o Lock". If the - SCP also supports the HTTP CreateSubscription service as an Origin-Server, the SCP shall also - send HTTP SendEventReport messages (see). - - Upon successfully processing a subscription - action, the SCP shall send initial UPS State Report N-EVENT-REPORTs, as indicated in, providing the current status of - the UPS Instance to the Receiving AE. - - The SCP may also refuse both specific and - global Subscription requests by returning a failure N-ACTION Response Status Code for "Refused: - Refused: Not authorized" if the refusal depends on permissions related to the tasks or the - requestor, or "Refused: SCP does not support Event Reports" if the SCP does not support sending - the events. The SCP must document in its conformance statement if it might refuse Subscription - requests. - - The SCP may remove existing Deletion Locks - by changing the UPS Subscription State for the AE from "Subscribed with Lock" to "Subscribed w/o - Lock" and/or by changing the Global Subscription State for an AE from "Global Subscription with - Lock" to "Global Subscription w/o Lock". This is intended to allow the SCP to deal with SCU - malfunctions. The SCP must document in its conformance statement if it might remove a Deletion - Lock. - - The SCP may also refuse the Deletion Lock - portion of a specific or global Subscription request. For example, a request to modify the UPS - Subscription State for the AE to "Subscribed with Lock" would instead result in a UPS - Subscription State of "Subscribed w/o Lock" and a Warning status (see) returned to the requesting SCU. - This is intended to deal with Security and related policy restrictions. The SCP must document in - its conformance statement if it might refuse a Deletion Lock. - - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting - authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP - Class. - + Upon receipt of the N-ACTION request, the SCP shall attempt to update the Global Subscription State and/or UPS Subscription State of the specified AE with respect to the specified SOP Instance UID as described in and then return, via the N-ACTION response primitive, the appropriate N-ACTION Response Status Code. + The SCP may optionally allow an Application Entity to subscribe globally to a filtered set of UPS Instances. In this case, the Application Entity will only be subscribed to existing and future UPS Instances that match the search criteria specified by the Matching Keys of the N-ACTION request (see ). If the SCP does not support Filtered Global Subscription it will return a Failure response with a Code of C307 (see ). + A success status conveys that the Global Subscription State and/or UPS Subscription State for the AE specified in Receiving AE (0074,1234) was successfully modified by the SCP. The AE-TITLE in Receiving AE (0074,1234) may be different than the AE-TITLE used by the SCU for the association negotiation. The SCP shall use the AE-TITLE specified in Receiving AE (0074,1234). This allows systems to subscribe other systems they know would be interested in events for a certain UPS. + For all UPS instances managed by the SCP, the SCP shall send N-EVENT-REPORTS (as described in ) to AEs that have a UPS Subscription State of "Subscribed with Lock" or "Subscribed w/o Lock". If the SCP also supports the HTTP CreateSubscription service as an Origin-Server, the SCP shall also send HTTP SendEventReport messages (see ). + Upon successfully processing a subscription action, the SCP shall send initial UPS State Report N-EVENT-REPORTs, as indicated in , providing the current status of the UPS Instance to the Receiving AE. + The SCP may also refuse both specific and global Subscription requests by returning a failure N-ACTION Response Status Code for "Refused: Refused: Not authorized" if the refusal depends on permissions related to the tasks or the requestor, or "Refused: SCP does not support Event Reports" if the SCP does not support sending the events. The SCP must document in its conformance statement if it might refuse Subscription requests. + The SCP may remove existing Deletion Locks by changing the UPS Subscription State for the AE from "Subscribed with Lock" to "Subscribed w/o Lock" and/or by changing the Global Subscription State for an AE from "Global Subscription with Lock" to "Global Subscription w/o Lock". This is intended to allow the SCP to deal with SCU malfunctions. The SCP must document in its conformance statement if it might remove a Deletion Lock. + The SCP may also refuse the Deletion Lock portion of a specific or global Subscription request. For example, a request to modify the UPS Subscription State for the AE to "Subscribed with Lock" would instead result in a UPS Subscription State of "Subscribed w/o Lock" and a Warning status (see ) returned to the requesting SCU. This is intended to deal with Security and related policy restrictions. The SCP must document in its conformance statement if it might refuse a Deletion Lock. + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP Class.
Filtered Global Subscription - An SCP that supports Filtered Global - Subscription shall create an instance subscription for each UPS Instance that would match a - C-FIND request with the Matching Keys provided in the subscription request. - - The SCP shall support the same matching - logic used for C-FIND (see). - + An SCP that supports Filtered Global Subscription shall create an instance subscription for each UPS Instance that would match a C-FIND request with the Matching Keys provided in the subscription request. + The SCP shall support the same matching logic used for C-FIND (see ).
Status Codes - - defines the status code values that might be returned in a N-ACTION response. General status - code values and fields related to status code values are defined for N-ACTION DIMSE Service in - . - + defines the status code values that might be returned in a N-ACTION response. General status code values and fields related to status code values are defined for N-ACTION DIMSE Service in . - +
N-ACTION Response Status Values [for Subscribe/Unsubscribe to Receive UPS sEvent - Reports] - N-ACTION Response Status Values [for Subscribe/Unsubscribe to Receive UPS sEvent Reports]
@@ -50775,9 +35540,7 @@ Success - The requested change of - subscription state was performed - + The requested change of subscription state was performed 0000 @@ -50788,9 +35551,7 @@ Warning - Deletion Lock not - granted. - + Deletion Lock not granted. B301 @@ -50801,9 +35562,7 @@ Failure - Failed: Specified SOP - Instance UID does not exist or is not a UPS Instance managed by this SCP - + Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP C307 @@ -50811,9 +35570,7 @@
- Failed: Receiving AE-TITLE - is Unknown to this SCP - + Failed: Receiving AE-TITLE is Unknown to this SCP C308 @@ -50821,9 +35578,7 @@
- Failed: Specified action - not appropriate for specified instance - + Failed: Specified action not appropriate for specified instance C314 @@ -50831,9 +35586,7 @@
- Failed: SCP does not - support Event Reports - + Failed: SCP does not support Event Reports C315 @@ -50845,16 +35598,10 @@
Report a Change in UPS Status (N-EVENT-REPORT) - This operation allows an SCP to notify an SCU - of a change in state of a UPS instance or a change in state of the SCP itself. This operation shall - be invoked by the SCP through the DIMSE N-EVENT-REPORT Service. - + This operation allows an SCP to notify an SCU of a change in state of a UPS instance or a change in state of the SCP itself. This operation shall be invoked by the SCP through the DIMSE N-EVENT-REPORT Service.
Event Report Information - DICOM AEs that claim conformance to the UPS - Event SOP Class as an SCU and/or an SCP shall support the Event Type IDs and Event Report - Attributes as specified in. - + DICOM AEs that claim conformance to the UPS Event SOP Class as an SCU and/or an SCP shall support the Event Type IDs and Event Report Attributes as specified in . @@ -50896,8 +35643,7 @@ @@ -50959,42 +35701,34 @@ @@ -51006,9 +35740,7 @@ @@ -51020,9 +35752,7 @@ @@ -51033,9 +35763,7 @@ 3
Report a Change in UPS Status - Event Report Information
- Input Readiness State - + Input Readiness State (0040,4041) @@ -50908,8 +35654,7 @@
- Reason For Cancellation - + Reason For Cancellation (0074,1238) @@ -50920,9 +35665,7 @@
- Procedure Step - Discontinuation Reason Code Sequence - + Procedure Step Discontinuation Reason Code Sequence (0074,100e) @@ -50934,10 +35677,9 @@
- >Include - - - +>Include + +
- Reason For Cancellation - + Reason For Cancellation (0074,1238) -/1C - Required if provided in the - triggering N-ACTION - + Required if provided in the triggering N-ACTION
- Procedure Step - Discontinuation Reason Code Sequence - + Procedure Step Discontinuation Reason Code Sequence (0074,100e) -/1C - Required if provided in the - triggering N-ACTION - + Required if provided in the triggering N-ACTION
- >Include - - - +>Include + +
-/1C - Required if provided in the - triggering N-ACTION - + Required if provided in the triggering N-ACTION
-/1C - Required if provided in the - triggering N-ACTION - + Required if provided in the triggering N-ACTION
- Progress Information - Sequence - + Progress Information Sequence (0074,1002) @@ -51046,9 +35774,7 @@
- >Procedure Step - Progress - + >Procedure Step Progress (0074,1004) @@ -51059,9 +35785,7 @@
- >Procedure Step Progress - Description - + >Procedure Step Progress Description (0074,1006) @@ -51072,9 +35796,7 @@
- >Procedure Step Progress - Parameters Sequence - + >Procedure Step Progress Parameters Sequence (0074,1007) @@ -51085,9 +35807,7 @@
- >Procedure Step - Communications URI Sequence - + >Procedure Step Communications URI Sequence (0074,1008) @@ -51109,9 +35829,7 @@
- >>Contact Display - Name - + >>Contact Display Name (0074,100c) @@ -51139,8 +35857,7 @@
- Subscription List Status - + Subscription List Status (0074,1244) @@ -51151,9 +35868,7 @@
- Unified Procedure Step List - Status - + Unified Procedure Step List Status (0074,1246) @@ -51170,332 +35885,145 @@ 5 - Scheduled Station Name Code - Sequence - + Scheduled Station Name Code Sequence (0040,4025) -/1C - Required if populated in - the UPS Instance - + Required if populated in the UPS Instance
- >Include - - - +>Include + +
- Human Performer Code - Sequence - + Human Performer Code Sequence (0040,4009) -/1C - Required if populated in - the UPS Instance - + Required if populated in the UPS Instance
- >Include - - - +>Include + +
- Human Performer's - Organization - + Human Performer's Organization (0040,4036) -/1C - Required if populated in - the UPS Instance - + Required if populated in the UPS Instance
- The meanings of the Progress - Information Attribute Values in the context of a specific task are undefined, and the values - may be obsolete when the UPS has moved to the COMPLETED or CANCELED state. - + The meanings of the Progress Information Attribute Values in the context of a specific task are undefined, and the values may be obsolete when the UPS has moved to the COMPLETED or CANCELED state.
Service Class User Behavior - The SCU shall return, via the - N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the - associated request. See - - for general response status codes. - - The SCU shall accept all Attributes - included in any notification. No requirements are placed on what the SCU will do as a result of - receiving this information. - + The SCU shall return, via the N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to the associated request. See for general response status codes. + The SCU shall accept all Attributes included in any notification. No requirements are placed on what the SCU will do as a result of receiving this information. - An SCU may receive N-EVENT-REPORTs with - an Event Type ID of 1 (UPS State Report) either due to a state change to the UPS, or in - response to initial subscription to the UPS (possibly when the UPS is initially created). - See. - + An SCU may receive N-EVENT-REPORTs with an Event Type ID of 1 (UPS State Report) either due to a state change to the UPS, or in response to initial subscription to the UPS (possibly when the UPS is initially created). See . - If an SCU performing a UPS receives an - N-EVENT-REPORT for that instance with an Event Type ID of 2 (UPS Cancel Requested), then this - SCU may, at its own discretion, choose to cancel the UPS as described in. - + If an SCU performing a UPS receives an N-EVENT-REPORT for that instance with an Event Type ID of 2 (UPS Cancel Requested), then this SCU may, at its own discretion, choose to cancel the UPS as described in . - A UPS Cancel Requested - notification includes the AE of the Requesting SCU, which could be useful to the - performing SCU in deciding the significance/authority of the Cancel Request. - + A UPS Cancel Requested notification includes the AE of the Requesting SCU, which could be useful to the performing SCU in deciding the significance/authority of the Cancel Request. - The Reason For Cancellation, a - proposed Procedure Step Discontinuation Reason Code Sequence, a Contact Display Name - and a Contact URI of someone responsible for the Cancel Request may also be provided - in the notification. Some performing SCUs might find this information useful in - deciding to cancel the UPS or might provide the information to an operator so they - can make contact for the purpose of clarifying or confirming the Cancel Request. If - the performing SCU chooses to Cancel the UPS, it may at its own discretion set the - Procedure Step Discontinuation Reason Code Sequence in the UPS instance based on the - corresponding values provided. - + The Reason For Cancellation, a proposed Procedure Step Discontinuation Reason Code Sequence, a Contact Display Name and a Contact URI of someone responsible for the Cancel Request may also be provided in the notification. Some performing SCUs might find this information useful in deciding to cancel the UPS or might provide the information to an operator so they can make contact for the purpose of clarifying or confirming the Cancel Request. If the performing SCU chooses to Cancel the UPS, it may at its own discretion set the Procedure Step Discontinuation Reason Code Sequence in the UPS instance based on the corresponding values provided. - If an SCU receives an N-EVENT-REPORT for an - instance with an Event Type ID of 5 (UPS Assigned) and the device or human specified in the - notification correspond to the SCU, then the UPS has been assigned to that SCU. - - An SCU that wishes to start/stop receiving - N-EVENT-REPORTs about UPS instances may subscribe/unsubscribe as described in. - - If an SCU receives an N-EVENT-REPORT with - an Event Type ID of 4 (SCP Status Change), it is not required to act on that information, - however the SCU may want to consider actions such as: re-subscribing if the subscription list - has been Cold Started, verifying (and recreating if necessary) scheduled UPSs if the UPS list - has been Cold Started, etc. - + If an SCU receives an N-EVENT-REPORT for an instance with an Event Type ID of 5 (UPS Assigned) and the device or human specified in the notification correspond to the SCU, then the UPS has been assigned to that SCU. + An SCU that wishes to start/stop receiving N-EVENT-REPORTs about UPS instances may subscribe/unsubscribe as described in . + If an SCU receives an N-EVENT-REPORT with an Event Type ID of 4 (SCP Status Change), it is not required to act on that information, however the SCU may want to consider actions such as: re-subscribing if the subscription list has been Cold Started, verifying (and recreating if necessary) scheduled UPSs if the UPS list has been Cold Started, etc. - An SCU may receive SCP State Change - Events from any SCP with which it is currently subscribed either globally or for any - specific UPS. - + An SCU may receive SCP State Change Events from any SCP with which it is currently subscribed either globally or for any specific UPS.
Service Class Provider Behavior - The SCP shall specify in the N-EVENT-REPORT - Request Primitive the Event Type ID and the UID of the UPS Instance with which the event is - associated. Since all UPSs are created as instances of the UPS Push SOP Class, the Affected SOP - Class UID (0000,0002) in the N-EVENT-REPORT request shall be the UID of the UPS Push SOP Class. - See - - for further details. The SCP shall additionally include Attributes related to the event as - defined in. - - Each time the SCP completes a Subscribe to - Receive UPS Event Reports Action (see) - for a specific UPS instance, the SCP shall send to the Receiving AE a UPS State Report Event and - provide the current value of the Procedure Step State (0074,1000) and Input Readiness State - (0040,4041) Attributes for the UPS instance. - - Each time the SCP completes a Subscribe to - Receive UPS Event Reports Action (see) - for the well-known UID 1.2.840.10008.5.1.4.34.5 with the value of the Deletion Lock set to TRUE - (i.e., a Global Subscription with Lock), the SCP shall send to the Receiving AE a UPS State - Report Event for every UPS Instance managed by the SCP and provide the current value of the - Procedure Step State (0074,1000) and Input Readiness State (0040,4041) Attributes. - - Each time the SCP creates a new UPS - instance, the SCP shall send a UPS State Report Event, indicating a change of status to - SCHEDULED and the initial value of and Input Readiness State (0040,4041), to all AEs with a - Global Subscription State of "Global Subscription with Lock" or "Global Subscription w/o Lock". - (see) - - Each time the SCP creates a new UPS - instance and either the Scheduled Station Name Code Sequence (0040,4025) or the Scheduled Human - Performers Sequence (0040,4034) is populated, the SCP shall also send a UPS Assigned Event, with - the current contents of the Scheduled Station Name Code Sequence (0040,4025) and the Scheduled - Human Performers Sequence (0040,4034), to all AEs with a Global Subscription State of "Global - Subscription with Lock" or "Global Subscription w/o Lock". - - In the following text "Subscribed SCUs" - means all AEs where the UPS Subscription State of the UPS Instance in question is "Subscribed - with Lock" or "Subscribed w/o Lock" (see - ). If the SCP also supports the HTTP CreateSubscription service as an Origin-Server, "Subscribed - SCUs" also includes all CreateSubscription User-Agents where the UPS Subscription State of the - UPS Instance in question is "Subscribed with Lock" or "Subscribed w/o Lock" (see). - - Each time the SCP changes the Procedure - Step State (0074,1000) Attribute for a UPS instance, the SCP shall send a UPS State Report Event - to subscribed SCUs. - - Each time the SCP changes the Input - Readiness State (0040,4041) Attribute for a UPS instance, the SCP shall send a UPS State Report - Event to subscribed SCUs. - - Each time the SCP receives an N-ACTION with - an Action Type ID of 2 (Request UPS Cancel), the SCP shall send a UPS Cancel Requested Event to - subscribed SCUs. The SCP shall include the AE Title of the triggering N-ACTION SCU in the - Requesting AE Attribute. The SCP shall include the Reason For Cancellation, Contact Display Name - and Contact URI Attributes if they were provided in the triggering N-ACTION. - - Each time the SCP updates the Scheduled - Station Name Code Sequence (0040,4025) or the Scheduled Human Performers Sequence (0040,4034) - for a UPS instance, the SCP shall send a UPS Assigned Event, with the current contents of the - Scheduled Station Name Code Sequence (0040,4025) and the Scheduled Human Performers Sequence - (0040,4034), to subscribed SCUs. - - Each time the SCP updates the Procedure - Step Progress (0074,1004), the Procedure Step Progress Description (0074,1006), or the contents - of the Procedure Step Communications URI Sequence (0074,1008) for a UPS instance, the SCP shall - send a UPS Progress Event, with the current contents of the Progress Information Sequence - (0074,1002), to subscribed SCUs. - - Each time the SCP is restarted, the SCP - shall send an SCP Status Change Event. The SCP, if it knows it is going down, may send an - additional SCP Status Change Event before it is shut down. Since the subscription lists may be - incomplete or missing in the event of a restart, the SCP shall maintain a fallback list of AEs - (for example as a configuration file, or from an LDAP server). The SCP shall send the SCP Status - Change Events to: - + The SCP shall specify in the N-EVENT-REPORT Request Primitive the Event Type ID and the UID of the UPS Instance with which the event is associated. Since all UPSs are created as instances of the UPS Push SOP Class, the Affected SOP Class UID (0000,0002) in the N-EVENT-REPORT request shall be the UID of the UPS Push SOP Class. See for further details. The SCP shall additionally include Attributes related to the event as defined in . + Each time the SCP completes a Subscribe to Receive UPS Event Reports Action (see ) for a specific UPS instance, the SCP shall send to the Receiving AE a UPS State Report Event and provide the current value of the Procedure Step State (0074,1000) and Input Readiness State (0040,4041) Attributes for the UPS instance. + Each time the SCP completes a Subscribe to Receive UPS Event Reports Action (see ) for the well-known UID 1.2.840.10008.5.1.4.34.5 with the value of the Deletion Lock set to TRUE (i.e., a Global Subscription with Lock), the SCP shall send to the Receiving AE a UPS State Report Event for every UPS Instance managed by the SCP and provide the current value of the Procedure Step State (0074,1000) and Input Readiness State (0040,4041) Attributes. + Each time the SCP creates a new UPS instance, the SCP shall send a UPS State Report Event, indicating a change of status to SCHEDULED and the initial value of and Input Readiness State (0040,4041), to all AEs with a Global Subscription State of "Global Subscription with Lock" or "Global Subscription w/o Lock". (see ) + Each time the SCP creates a new UPS instance and either the Scheduled Station Name Code Sequence (0040,4025) or the Scheduled Human Performers Sequence (0040,4034) is populated, the SCP shall also send a UPS Assigned Event, with the current contents of the Scheduled Station Name Code Sequence (0040,4025) and the Scheduled Human Performers Sequence (0040,4034), to all AEs with a Global Subscription State of "Global Subscription with Lock" or "Global Subscription w/o Lock". + In the following text "Subscribed SCUs" means all AEs where the UPS Subscription State of the UPS Instance in question is "Subscribed with Lock" or "Subscribed w/o Lock" (see ). If the SCP also supports the HTTP CreateSubscription service as an Origin-Server, "Subscribed SCUs" also includes all CreateSubscription User-Agents where the UPS Subscription State of the UPS Instance in question is "Subscribed with Lock" or "Subscribed w/o Lock" (see ). + Each time the SCP changes the Procedure Step State (0074,1000) Attribute for a UPS instance, the SCP shall send a UPS State Report Event to subscribed SCUs. + Each time the SCP changes the Input Readiness State (0040,4041) Attribute for a UPS instance, the SCP shall send a UPS State Report Event to subscribed SCUs. + Each time the SCP receives an N-ACTION with an Action Type ID of 2 (Request UPS Cancel), the SCP shall send a UPS Cancel Requested Event to subscribed SCUs. The SCP shall include the AE Title of the triggering N-ACTION SCU in the Requesting AE Attribute. The SCP shall include the Reason For Cancellation, Contact Display Name and Contact URI Attributes if they were provided in the triggering N-ACTION. + Each time the SCP updates the Scheduled Station Name Code Sequence (0040,4025) or the Scheduled Human Performers Sequence (0040,4034) for a UPS instance, the SCP shall send a UPS Assigned Event, with the current contents of the Scheduled Station Name Code Sequence (0040,4025) and the Scheduled Human Performers Sequence (0040,4034), to subscribed SCUs. + Each time the SCP updates the Procedure Step Progress (0074,1004), the Procedure Step Progress Description (0074,1006), or the contents of the Procedure Step Communications URI Sequence (0074,1008) for a UPS instance, the SCP shall send a UPS Progress Event, with the current contents of the Progress Information Sequence (0074,1002), to subscribed SCUs. + Each time the SCP is restarted, the SCP shall send an SCP Status Change Event. The SCP, if it knows it is going down, may send an additional SCP Status Change Event before it is shut down. Since the subscription lists may be incomplete or missing in the event of a restart, the SCP shall maintain a fallback list of AEs (for example as a configuration file, or from an LDAP server). The SCP shall send the SCP Status Change Events to: - all AEs on the fallback list and, - + all AEs on the fallback list and, - all AEs with a Global Subscription - State of "Global Subscription with Lock" or "Global Subscription w/o Lock" and, - + all AEs with a Global Subscription State of "Global Subscription with Lock" or "Global Subscription w/o Lock" and, - all AEs with a UPS Subscription - State of "Subscribed with Lock" or "Subscribed w/o Lock" for any UPS Instance managed by - the SCP - + all AEs with a UPS Subscription State of "Subscribed with Lock" or "Subscribed w/o Lock" for any UPS Instance managed by the SCP - The SCP may choose to not send - duplicate messages to an AE. - + The SCP may choose to not send duplicate messages to an AE. - The value of SCP Status (0074,1242) shall - be RESTARTED if the SCP is sending this message due to being restarted and GOING DOWN if the SCP - will be shut down soon. - + The value of SCP Status (0074,1242) shall be RESTARTED if the SCP is sending this message due to being restarted and GOING DOWN if the SCP will be shut down soon. - SCPs that report they are GOING DOWN - might stop accepting new interactions from SCUs until after they have restarted. - + SCPs that report they are GOING DOWN might stop accepting new interactions from SCUs until after they have restarted. - When SCP Status (0074,1242) is RESTARTED, - the value of Subscription List Status (0074,1244) shall be WARM START if the SCP preserved the - Subscription List to the best of its knowledge, and COLD STARTED if the SCP has not preserved - the Subscription List. - - When SCP Status (0074,1242) is RESTARTED, - the value of Unified Procedure Step List Status (0074,1246) shall be WARM START if the SCP - preserved the UPS List to the best of its knowledge, and COLD START if the SCP has not preserved - the UPS List. - - If the SCP is unable to successfully - complete an N-EVENT-REPORT to any given SCU, the SCP has no obligation to queue or retry, and it - should not imply any effect on the subscription list or deletion locks. - + When SCP Status (0074,1242) is RESTARTED, the value of Subscription List Status (0074,1244) shall be WARM START if the SCP preserved the Subscription List to the best of its knowledge, and COLD STARTED if the SCP has not preserved the Subscription List. + When SCP Status (0074,1242) is RESTARTED, the value of Unified Procedure Step List Status (0074,1246) shall be WARM START if the SCP preserved the UPS List to the best of its knowledge, and COLD START if the SCP has not preserved the UPS List. + If the SCP is unable to successfully complete an N-EVENT-REPORT to any given SCU, the SCP has no obligation to queue or retry, and it should not imply any effect on the subscription list or deletion locks.
Status Codes - No Service Class specific status values are - defined for the N-EVENT-REPORT Service. See - - for general response status codes. - + No Service Class specific status values are defined for the N-EVENT-REPORT Service. See for general response status codes.
Create a Unified Procedure Step (N-CREATE) - This operation allows an SCU to instruct an SCP - to create a Unified Procedure Step. This operation shall be invoked by the SCU through the DIMSE - N-CREATE Service. - + This operation allows an SCU to instruct an SCP to create a Unified Procedure Step. This operation shall be invoked by the SCU through the DIMSE N-CREATE Service.
Unified Procedure Step Attribute Specification - An Application Entity that claims - conformance to the UPS Push SOP Class as an SCU shall provide all Required Attributes as - specified in. Additional Attributes - defined by the UPS IOD may be provided as well. - - An Application Entity that claims - conformance to the UPS Push SOP Class as an SCP shall support all required Attributes as - specified in. Additional Attributes - defined by the UPS IOD may be supported as well. - + An Application Entity that claims conformance to the UPS Push SOP Class as an SCU shall provide all Required Attributes as specified in . Additional Attributes defined by the UPS IOD may be provided as well. + An Application Entity that claims conformance to the UPS Push SOP Class as an SCP shall support all required Attributes as specified in . Additional Attributes defined by the UPS IOD may be supported as well.
UPS Final State Requirements - COMPLETED and CANCELED are Final States - for a UPS instance. The Attributes and values of the UPS instance must meet certain - requirements before it may be placed in either of the Final States. - + COMPLETED and CANCELED are Final States for a UPS instance. The Attributes and values of the UPS instance must meet certain requirements before it may be placed in either of the Final States. - A UPS instance is in the SCHEDULED - state when created. See - - for rules governing state transitions. - + A UPS instance is in the SCHEDULED state when created. See for rules governing state transitions. - Attributes shall be valued as indicated - by the Final State Codes in the Final State Column of - - before the Procedure Step State (0074,1000) may be set to COMPLETED or CANCELED (i.e., Final - State). - - Performing systems are encouraged to - ensure that the values for all Attributes reasonably reflect what was done and the Final - State of the UPS. This may include blanking Attributes that are permitted to be empty and - for which no reasonable value can be determined. The UPS contents should make it clear - whether the step was completed, what work was done, what results were produced and whether - the results are usable. See - - for a discussion of methods to convey things like partial completion. - + Attributes shall be valued as indicated by the Final State Codes in the Final State Column of before the Procedure Step State (0074,1000) may be set to COMPLETED or CANCELED (i.e., Final State). + Performing systems are encouraged to ensure that the values for all Attributes reasonably reflect what was done and the Final State of the UPS. This may include blanking Attributes that are permitted to be empty and for which no reasonable value can be determined. The UPS contents should make it clear whether the step was completed, what work was done, what results were produced and whether the results are usable. See for a discussion of methods to convey things like partial completion. - The SCU may choose not to - distribute, or otherwise make available, some or all instances created during the - procedure step and referenced in the Output Information Sequence (0040,4033). - + The SCU may choose not to distribute, or otherwise make available, some or all instances created during the procedure step and referenced in the Output Information Sequence (0040,4033). @@ -51515,9 +36043,7 @@ R @@ -51525,10 +36051,7 @@ RC @@ -51536,10 +36059,7 @@ P @@ -51547,10 +36067,7 @@ X @@ -51558,9 +36075,7 @@ O @@ -51568,22 +36083,9 @@
UPS Macros - To reduce the size and complexity of - , a macro notation is used. - - For example, in, a table entry specifying "Include - " should be - interpreted as including the following table of text as a substitution. The nesting level - for the sequence inclusion is indicated by the nesting level on the reference to the macro. - Where the matching key type requirement is "*" it should be replaced with the matching key - type requirement of the sequence Attribute that incorporates this macro. - - For code sequences that have - requirements for N-CREATE, N-SET, N-GET, or C-FIND behavior that differ from the Macro, the - code sequence contents are explicitly listed in the Table rather than specifying inclusion - of the Macro. - + To reduce the size and complexity of , a macro notation is used. + For example, in , a table entry specifying "Include " should be interpreted as including the following table of text as a substitution. The nesting level for the sequence inclusion is indicated by the nesting level on the reference to the macro. Where the matching key type requirement is "*" it should be replaced with the matching key type requirement of the sequence Attribute that incorporates this macro. + For code sequences that have requirements for N-CREATE, N-SET, N-GET, or C-FIND behavior that differ from the Macro, the code sequence contents are explicitly listed in the Table rather than specifying inclusion of the Macro.
Final State Codes
- The UPS State shall not - be set to COMPLETED or CANCELED if this Attribute does not have a value. - + The UPS State shall not be set to COMPLETED or CANCELED if this Attribute does not have a value.
- The UPS State shall not - be set to COMPLETED or CANCELED if the condition is met and this Attribute - does not have a value. - + The UPS State shall not be set to COMPLETED or CANCELED if the condition is met and this Attribute does not have a value.
- The UPS State shall not - be set to COMPLETED if this Attribute does not have a value, but may be set - to CANCELED. - + The UPS State shall not be set to COMPLETED if this Attribute does not have a value, but may be set to CANCELED.
- The UPS State shall not - be set to CANCELED if this Attribute does not have a value, but may be set - to COMPLETED. - + The UPS State shall not be set to CANCELED if this Attribute does not have a value, but may be set to COMPLETED.
- The UPS State may be - set to either COMPLETED or CANCELED if this Attribute does not have a value. - + The UPS State may be set to either COMPLETED or CANCELED if this Attribute does not have a value.
@@ -51595,22 +36097,16 @@ Tag @@ -51649,20 +36144,13 @@ 1C @@ -51751,9 +36228,7 @@ 1 @@ -51780,13 +36255,8 @@ 1C @@ -51813,12 +36283,8 @@ 1C @@ -51850,8 +36316,7 @@ @@ -52058,9 +36509,7 @@ 1 @@ -52183,12 +36627,8 @@ 1C @@ -52215,12 +36655,8 @@ 1C @@ -52247,12 +36683,8 @@ 1C @@ -52279,12 +36711,8 @@ 1C @@ -52311,12 +36739,8 @@ 1C @@ -52343,18 +36767,13 @@ 1C @@ -52422,19 +36836,13 @@ 1C @@ -52494,22 +36895,16 @@ Tag @@ -52995,9 +37336,7 @@ @@ -53136,9 +37462,7 @@ 1 @@ -53154,22 +37478,16 @@ Tag - +
UPS Code Sequence Macro
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -51619,8 +36115,7 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Code Value shall be - retrieved with Single Value Matching. - - Required if the code - value length is 16 characters or less, and the code value is not a URN or - URL. - + Code Value shall be retrieved with Single Value Matching. + Required if the code value length is 16 characters or less, and the code value is not a URN or URL.
- Coding Scheme - Designator - + Coding Scheme Designator (0008,0102) @@ -51684,19 +36172,13 @@ 1C - Coding Scheme - Designator shall be retrieved with Single Value Matching. - - Shall be present if - Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be - present otherwise. - + Coding Scheme Designator shall be retrieved with Single Value Matching. + Shall be present if Code Value (0008,0100) or Long Code Value (0008,0119) is present. May be present otherwise.
- Coding Scheme Version - + Coding Scheme Version (0008,0103) @@ -51718,13 +36200,8 @@ 1C - Required if the value - of Coding Scheme Designator (0008,0102) is not sufficient to identify the - Code Value (0008,0100) unambiguously. - - Shall not be present if - Coding Scheme Designator (0008,0102) is absent. May be present otherwise. - + Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously. + Shall not be present if Coding Scheme Designator (0008,0102) is absent. May be present otherwise.
- Code Meaning shall not - be used as Matching Key. - + Code Meaning shall not be used as Matching Key.
- Long Code Value shall - be retrieved with Single Value Matching. - - Shall be present if - Code Value (0008,0100) is not present, and the code value is not a URN or - URL. - + Long Code Value shall be retrieved with Single Value Matching. + Shall be present if Code Value (0008,0100) is not present, and the code value is not a URN or URL.
- Long Code Value shall - be retrieved with Single Value Matching. - - Shall be present if - Code Value (0008,0100) is not present, and the code value is a URN or URL. - + Long Code Value shall be retrieved with Single Value Matching. + Shall be present if Code Value (0008,0100) is not present, and the code value is a URN or URL.
- Mapping Resource UID - + Mapping Resource UID (0008,0118) @@ -51878,8 +36343,7 @@
- Context Group Version - + Context Group Version (0008,0106) @@ -51906,9 +36370,7 @@
- Context Group Extension - Flag - + Context Group Extension Flag (0008,010B) @@ -51935,9 +36397,7 @@
- Context Group Local - Version - + Context Group Local Version (0008,0107) @@ -51964,9 +36424,7 @@
- Context Group Extension - Creator UID - + Context Group Extension Creator UID (0008,010D) @@ -52004,22 +36462,16 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -52028,8 +36480,7 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- The type of the value - encoded in this name-value Item. - + The type of the value encoded in this name-value Item. Enumerated Values: @@ -52116,9 +36565,7 @@
- Concept Name Code - Sequence - + Concept Name Code Sequence (0040,A043) @@ -52140,16 +36587,13 @@ 1 - Coded concept name of - this name-value Item. - + Coded concept name of this name-value Item.
- >Include - + >Include - Datetime value for this - name-value Item. - - Required if Value Type - (0040,A040) is DATETIME. - + Datetime value for this name-value Item. + Required if Value Type (0040,A040) is DATETIME.
- Date value for this - name-value Item. - - Required if Value Type - (0040,A040) is DATE. - + Date value for this name-value Item. + Required if Value Type (0040,A040) is DATE.
- Time value for this - name-value Item. - - Required if Value Type - (0040,A040) is TIME. - + Time value for this name-value Item. + Required if Value Type (0040,A040) is TIME.
- Person name value for - this name-value Item. - - Required if Value Type - (0040,A040) is PNAME. - + Person name value for this name-value Item. + Required if Value Type (0040,A040) is PNAME.
- UID value for this - name-value Item. - - Required if Value Type - (0040,A040) is UIDREF. - + UID value for this name-value Item. + Required if Value Type (0040,A040) is UIDREF.
- Text value for this - name-value Item. - - Required if Value Type - (0040,A040) is TEXT. - + Text value for this name-value Item. + Required if Value Type (0040,A040) is TEXT.
- Concept Code Sequence - + Concept Code Sequence (0040,A168) @@ -52376,19 +36795,14 @@ 1C - Coded concept value of - this name-value Item. - - Required if Value Type - (0040,A040) is CODE. - + Coded concept value of this name-value Item. + Required if Value Type (0040,A040) is CODE.
- >Include - + >Include - Numeric value for this - name-value Item. - - Required if Value Type - (0040,A040) is NUMERIC. - + Numeric value for this name-value Item. + Required if Value Type (0040,A040) is NUMERIC.
- Measurement Units Code - Sequence - + Measurement Units Code Sequence (0040,08EA) @@ -52456,27 +36864,20 @@ 1C - Units of measurement - for a numeric value in this name-value Item. - - Required if Value Type - (0040,A040) is NUMERIC. - + Units of measurement for a numeric value in this name-value Item. + Required if Value Type (0040,A040) is NUMERIC.
- >Include - + >Include - Baseline - + Baseline - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -52518,16 +36913,14 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Type of Instances - + Type of Instances (0040,E020) @@ -52552,8 +36945,7 @@
- Study Instance UID - + Study Instance UID (0020,000D) @@ -52575,16 +36967,12 @@ 1C - Required if Type of - Instances (0040,E020) is DICOM and the Information Model of the referenced - instance contains the Study IE - + Required if Type of Instances (0040,E020) is DICOM and the Information Model of the referenced instance contains the Study IE
- Series Instance UID - + Series Instance UID (0020,000E) @@ -52606,17 +36994,12 @@ 1C - Required if Type of - Instances (0040,E020) is DICOM and the Information Model of the referenced - instance contains the Series IE - + Required if Type of Instances (0040,E020) is DICOM and the Information Model of the referenced instance contains the Series IE
- Referenced SOP - Sequence - + Referenced SOP Sequence (0008,1199) @@ -52641,9 +37024,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -52668,9 +37049,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -52695,9 +37074,7 @@
- >HL7 Instance - Identifier - + >HL7 Instance Identifier (0040,E001) @@ -52719,16 +37096,12 @@ 1C - Required if Type of - Instances (0040,E020) is CDA. - + Required if Type of Instances (0040,E020) is CDA.
- >Referenced Frame - Number - + >Referenced Frame Number (0008,1160) @@ -52750,18 +37123,12 @@ 1C - Required if the - Referenced SOP Instance is a multi-frame image and the reference does not - apply to all frames, and Referenced Segment Number (0062,000B) is not - present. - + Required if the Referenced SOP Instance is a multi-frame image and the reference does not apply to all frames, and Referenced Segment Number (0062,000B) is not present.
- >Referenced Segment - Number - + >Referenced Segment Number (0062,000B) @@ -52783,17 +37150,12 @@ 1C - Required if the - Referenced SOP Instance is a Segmentation and the reference does not apply - to all segments and Referenced Frame Number (0008,1160) is not present. - + Required if the Referenced SOP Instance is a Segmentation and the reference does not apply to all segments and Referenced Frame Number (0008,1160) is not present.
- DICOM Retrieval - Sequence - + DICOM Retrieval Sequence (0040,E021) @@ -52815,17 +37177,12 @@ 1C - Required if DICOM Media - Retrieval Sequence (0040,E022), WADO Retrieval Sequence (0040,E023), WADO-RS - Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are - not present. May be present otherwise. - + Required if DICOM Media Retrieval Sequence (0040,E022), WADO Retrieval Sequence (0040,E023), WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
- >Retrieve AE Title - + >Retrieve AE Title (0008,0054) @@ -52850,9 +37207,7 @@
- DICOM Media Retrieval - Sequence - + DICOM Media Retrieval Sequence (0040,E022) @@ -52874,18 +37229,12 @@ 1C - Required if DICOM - Retrieval Sequence (0040,E021), WADO Retrieval Sequence (0040,E023), WADO-RS - Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are - not present. May be present otherwise. - + Required if DICOM Retrieval Sequence (0040,E021), WADO Retrieval Sequence (0040,E023), WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
- >Storage Media - File-Set ID - + >Storage Media File-Set ID (0088,0130) @@ -52910,9 +37259,7 @@
- >Storage Media - File-Set UID - + >Storage Media File-Set UID (0088,0140) @@ -52937,9 +37284,7 @@
- WADO Retrieval - Sequence - + WADO Retrieval Sequence (0040,E023) @@ -52961,11 +37306,7 @@ 1C - Required if DICOM - Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), - WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence - (0040,E024) are not present. May be present otherwise. - + Required if DICOM Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), WADO-RS Retrieval Sequence (0040,E025) and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
- XDS Retrieval - Sequence - + XDS Retrieval Sequence (0040,E024) @@ -53019,18 +37358,12 @@ 1C - Required if DICOM - Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), - WADO-RS Retrieval Sequence (0040,E025) and WADO Retrieval Sequence - (0040,E023) are not present. May be present otherwise. - + Required if DICOM Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), WADO-RS Retrieval Sequence (0040,E025) and WADO Retrieval Sequence (0040,E023) are not present. May be present otherwise.
- >Repository Unique - ID - + >Repository Unique ID (0040,E030) @@ -53055,8 +37388,7 @@
- >Home Community ID - + >Home Community ID (0040,E031) @@ -53081,9 +37413,7 @@
- WADO-RS Retrieval - Sequence - + WADO-RS Retrieval Sequence (0040,E025) @@ -53105,11 +37435,7 @@ 1C - Required if DICOM - Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), - WADO Retrieval Sequence (0040,E023), and XDS Retrieval Sequence (0040,E024) - are not present. May be present otherwise. - + Required if DICOM Retrieval Sequence (0040,E021), DICOM Media Retrieval Sequence (0040,E022), WADO Retrieval Sequence (0040,E023), and XDS Retrieval Sequence (0040,E024) are not present. May be present otherwise.
- URL specifying the - location of the referenced instance(s). - + URL specifying the location of the referenced instance(s).
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -53178,17 +37496,14 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Local Namespace Entity - ID - + Local Namespace Entity ID (0040,0031) @@ -53210,18 +37525,13 @@ 1C - Creation required if - Universal Entity ID (0040,0032) is not present; may be present otherwise. - - Return Key required if - set. - + Creation required if Universal Entity ID (0040,0032) is not present; may be present otherwise. + Return Key required if set.
- Universal Entity ID - + Universal Entity ID (0040,0032) @@ -53243,20 +37553,13 @@ 1C - Creation required if - Local Namespace Entity ID (0040,0031) is not present; may be present - otherwise. - - Return Key required if - set. - + Creation required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise. + Return Key required if set.
- Universal Entity ID - Type - + Universal Entity ID Type (0040,0033) @@ -53278,15 +37581,11 @@ 1C - Creation required if - Universal Entity ID (0040,0032) is present. - - Return Key required if - set. - + Creation required if Universal Entity ID (0040,0032) is present. + Return Key required if set.
@@ -53300,22 +37599,16 @@ Tag @@ -53523,9 +37799,7 @@ @@ -53634,22 +37894,16 @@ Tag @@ -53917,8 +38144,7 @@
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -53324,16 +37617,14 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Issuer of Patient ID - + Issuer of Patient ID (0010,0021) @@ -53360,9 +37651,7 @@
- Issuer of Patient ID - Qualifiers Sequence - + Issuer of Patient ID Qualifiers Sequence (0010,0024) @@ -53389,9 +37678,7 @@
- >Universal Entity - ID - + >Universal Entity ID (0040,0032) @@ -53418,9 +37705,7 @@
- >Universal Entity ID - Type - + >Universal Entity ID Type (0040,0033) @@ -53444,16 +37729,12 @@ 1C - Required if Universal - Entity ID (0040,0032) is present in this item with a value. - + Required if Universal Entity ID (0040,0032) is present in this item with a value.
- >Identifier Type - Code - + >Identifier Type Code (0040,0035) @@ -53480,9 +37761,7 @@
- >Assigning Facility - Sequence - + >Assigning Facility Sequence (0040,0036) @@ -53506,16 +37785,13 @@ 2 - The Attributes of the - Assigning Facility Sequence shall only be retrieved with Sequence Matching. - + The Attributes of the Assigning Facility Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include
- >Assigning - Jurisdiction Code Sequence - + >Assigning Jurisdiction Code Sequence (0040,0039) @@ -53549,35 +37823,25 @@ 2 - The Attributes of the - Assigning Jurisdiction Code Sequence shall only be retrieved with Sequence - Matching. - + The Attributes of the Assigning Jurisdiction Code Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include - Baseline - - for country codes. - + Baseline for country codes.
- >Assigning Agency or - Department Code Sequence - + >Assigning Agency or Department Code Sequence (0040,003A) @@ -53601,17 +37865,13 @@ 2 - The Attributes of the - Assigning Agency or Department Code Sequence shall only be retrieved with - Sequence Matching. - + The Attributes of the Assigning Agency or Department Code Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -53658,17 +37912,14 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Referenced SOP Class - UID - + Referenced SOP Class UID (0008,1150) @@ -53695,9 +37946,7 @@
- Referenced SOP Instance - UID - + Referenced SOP Instance UID (0008,1155) @@ -53735,22 +37984,16 @@ Tag - Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -53759,17 +38002,14 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- Referenced SOP Class - UID - + Referenced SOP Class UID (0008,1150) @@ -53791,16 +38031,12 @@ 1C - Required if the storage - request only applies to a specific SOP Class. - + Required if the storage request only applies to a specific SOP Class.
- DICOM Storage - Sequence - + DICOM Storage Sequence (0040,4071) @@ -53822,16 +38058,12 @@ 1C - Required if STOW-RS - Storage Sequence (0040,4072) and XDS Storage Sequence (0040,4074) are not - present. May be present otherwise. - + Required if STOW-RS Storage Sequence (0040,4072) and XDS Storage Sequence (0040,4074) are not present. May be present otherwise.
- >Destination AE - + >Destination AE (0040,4071) @@ -53858,9 +38090,7 @@
- STOW-RS Storage - Sequence - + STOW-RS Storage Sequence (0040,4072) @@ -53882,10 +38112,7 @@ 1C - Required if DICOM - Storage Sequence (0040,4071) and XDS Storage Sequence (0040,4074) are not - present. May be present otherwise. - + Required if DICOM Storage Sequence (0040,4071) and XDS Storage Sequence (0040,4074) are not present. May be present otherwise.
- XDS Storage Sequence - + XDS Storage Sequence (0040,4074) @@ -53940,17 +38166,12 @@ 1C - Required if DICOM - Storage Sequence (0040,4071) and STOW-RS Storage Sequence (0040,4072) are - not present. May be present otherwise. - + Required if DICOM Storage Sequence (0040,4071) and STOW-RS Storage Sequence (0040,4072) are not present. May be present otherwise.
- >Repository Unique - ID - + >Repository Unique ID (0040,E030) @@ -53977,8 +38198,7 @@
- >Home Community ID - + >Home Community ID (0040,E031) @@ -54008,24 +38228,10 @@
UPS Attribute Service Requirements - This table combines the Attribute - requirements for multiple DIMSE services (N-CREATE, N-SET, N-GET, C-FIND) to facilitate - consistency between the requirements. - - See PS3.4 for the meaning of the - requirement codes used in the N-CREATE, N-SET, N-GET and Return Key columns in the following - table. - - See - - for the meaning of the requirement codes used in the Match Key column in the following - table. - - See - - for the meaning of the requirement codes used in the Final State column of the following - table. - + This table combines the Attribute requirements for multiple DIMSE services (N-CREATE, N-SET, N-GET, C-FIND) to facilitate consistency between the requirements. + See PS3.4 for the meaning of the requirement codes used in the N-CREATE, N-SET, N-GET and Return Key columns in the following table. + See for the meaning of the requirement codes used in the Match Key column in the following table. + See for the meaning of the requirement codes used in the Final State column of the following table. @@ -54037,22 +38243,16 @@ Tag @@ -54079,9 +38278,7 @@ Shall be empty @@ -54109,9 +38305,7 @@ @@ -54148,8 +38340,7 @@ (0008,0016) @@ -54186,24 +38372,18 @@ @@ -54253,17 +38427,13 @@ @@ -55030,9 +39103,7 @@ @@ -55117,30 +39188,22 @@ 2 @@ -55353,9 +39409,7 @@ @@ -56251,9 +40230,7 @@ @@ -56349,8 +40324,7 @@ 2C @@ -56379,8 +40353,7 @@ 2C @@ -56409,16 +40382,13 @@ 2C @@ -56453,9 +40423,7 @@ @@ -56490,9 +40458,7 @@ @@ -56527,9 +40493,7 @@ @@ -56557,24 +40521,20 @@ @@ -56946,26 +40877,20 @@ @@ -57486,98 +41361,39 @@
UPS SOP Class N-CREATE/N-SET/N-GET/C-FIND Attributes
- Req. Type N-CREATE - (SCU/SCP) - + Req. Type N-CREATE (SCU/SCP) - Req. Type N-SET - (SCU/SCP) - + Req. Type N-SET (SCU/SCP) Final State - Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP) Match Key Type @@ -54061,8 +38261,7 @@ Return Key Type - Remark/Matching Type - + Remark/Matching Type
- (see) - + (see ) O @@ -54096,8 +38293,7 @@ - - Cannot be queried. - + Cannot be queried.
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -54135,9 +38329,7 @@ 1C - Required if extended or - replacement character set is used - + Required if extended or replacement character set is used
- See - + See @@ -54168,13 +38359,8 @@ 1 - Uniquely identifies the - SOP Class of the Unified Procedure Step. - - See - - for further explanation. - + Uniquely identifies the SOP Class of the Unified Procedure Step. + See for further explanation.
Not allowed. - SOP Instance is - conveyed in the Affected SOP Instance UID (0000,1000) - + SOP Instance is conveyed in the Affected SOP Instance UID (0000,1000) Not allowed. - SOP Instance is - conveyed in the Requested SOP Instance UID (0000,1001) - + SOP Instance is conveyed in the Requested SOP Instance UID (0000,1001) R Not allowed. - SOP Instance is - conveyed in the Requested SOP Instance UID (0000,1001) - + SOP Instance is conveyed in the Requested SOP Instance UID (0000,1001) U @@ -54212,20 +38392,14 @@ 1 - Uniquely identifies the - SOP Instance of the UPS. - - SOP Instance UID shall - be retrieved with Single Value Matching. - + Uniquely identifies the SOP Instance of the UPS. + SOP Instance UID shall be retrieved with Single Value Matching.
- All other Attributes of the - + All other Attributes of the
- Unified Procedure Step Scheduled Procedure Information - Module - + Unified Procedure Step Scheduled Procedure Information Module
- Scheduled Procedure - Step Priority - + Scheduled Procedure Step Priority (0074,1200) @@ -54287,31 +38457,23 @@ 1 - Scheduled Procedure - Step Priority shall be retrieved with Single Value Matching. - + Scheduled Procedure Step Priority shall be retrieved with Single Value Matching.
- Scheduled Procedure - Step Modification DateTime - + Scheduled Procedure Step Modification DateTime (0040,4010) -/1 - SCP shall use time of - CREATE - + SCP shall use time of CREATE -/1 - SCP shall use time of - SET - + SCP shall use time of SET R @@ -54326,16 +38488,12 @@ 3 - Scheduled Procedure - Step Modification DateTime shall be retrieved with Single Value Matching or - Range Matching. - + Scheduled Procedure Step Modification DateTime shall be retrieved with Single Value Matching or Range Matching.
- Procedure Step Label - + Procedure Step Label (0074,1204) @@ -54369,10 +38527,7 @@ 2/1 - If a value is not - provided by the SCU, the SCP shall fill in the Worklist Label, e.g., using a - default value or by assigning the UPS instance to a logical worklist. - + If a value is not provided by the SCU, the SCP shall fill in the Worklist Label, e.g., using a default value or by assigning the UPS instance to a logical worklist. 3/1 @@ -54393,9 +38548,7 @@
- Scheduled Processing - Parameters Sequence - + Scheduled Processing Parameters Sequence (0074,1210) @@ -54423,17 +38576,14 @@
- >Include - + >Include
- Scheduled Station Name - Code Sequence - + Scheduled Station Name Code Sequence (0040,4025) @@ -54457,31 +38607,23 @@ 2 - The Attributes of the - Scheduled Station Name Code Sequence shall only be retrieved with Sequence - Matching. - + The Attributes of the Scheduled Station Name Code Sequence shall only be retrieved with Sequence Matching. - In Push Scenario, - the SCP-Performer has to create empty but could self fill later. - + In Push Scenario, the SCP-Performer has to create empty but could self fill later.
- >Include - + >Include
- Scheduled Station Class - Code Sequence - + Scheduled Station Class Code Sequence (0040,4026) @@ -54505,26 +38647,20 @@ 2 - The Attributes of the - Scheduled Station Class Code Sequence shall only be retrieved with Sequence - Matching. - + The Attributes of the Scheduled Station Class Code Sequence shall only be retrieved with Sequence Matching.
- >Include - + >Include
- Scheduled Station - Geographic Location Code Sequence - + Scheduled Station Geographic Location Code Sequence (0040,4027) @@ -54548,26 +38684,20 @@ 2 - The Attributes of the - Scheduled Station Geographic Location Code Sequence shall only be retrieved - with Sequence Matching. - + The Attributes of the Scheduled Station Geographic Location Code Sequence shall only be retrieved with Sequence Matching.
- >Include - + >Include
- Scheduled Human - Performers Sequence - + Scheduled Human Performers Sequence (0040,4034) @@ -54591,20 +38721,13 @@ 2 - The Attributes of the - Scheduled Human Performers Sequence shall only be retrieved with Sequence - Matching. - - Required if a Human - Performer is specified. - + The Attributes of the Scheduled Human Performers Sequence shall only be retrieved with Sequence Matching. + Required if a Human Performer is specified.
- >Human Performer - Code Sequence - + >Human Performer Code Sequence (0040,4009) @@ -54628,26 +38751,20 @@ 1 - The Attributes of the - Scheduled Human Performers Code Sequence shall only be retrieved with - Sequence Matching. - + The Attributes of the Scheduled Human Performers Code Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include
- >Human Performer's - Name - + >Human Performer's Name (0040,4037) @@ -54674,9 +38791,7 @@
- >Human Performer's - Organization - + >Human Performer's Organization (0040,4036) @@ -54703,9 +38818,7 @@
- Scheduled Procedure - Step Start DateTime - + Scheduled Procedure Step Start DateTime (0040,4005) @@ -54729,17 +38842,12 @@ 1 - Scheduled Procedure - Step Start DateTime shall be retrieved with Single Value Matching or Range - Matching. - + Scheduled Procedure Step Start DateTime shall be retrieved with Single Value Matching or Range Matching.
- Expected Completion - DateTime - + Expected Completion DateTime (0040,4011) @@ -54763,16 +38871,12 @@ 3 - Expected Completion - DateTime shall be retrieved with Single Value Matching or Range Matching. - + Expected Completion DateTime shall be retrieved with Single Value Matching or Range Matching.
- Scheduled Procedure - Step Expiration DateTime - + Scheduled Procedure Step Expiration DateTime (0040,4008) @@ -54796,17 +38900,12 @@ 3 - Scheduled Procedure - Step Expiration DateTime shall be retrieved with Single Value Matching or - Range Matching. - + Scheduled Procedure Step Expiration DateTime shall be retrieved with Single Value Matching or Range Matching.
- Scheduled Workitem Code - Sequence - + Scheduled Workitem Code Sequence (0040,4018) @@ -54830,26 +38929,20 @@ 2 - The Attributes of the - Scheduled Workitem Code Sequence shall only be retrieved with Sequence - Matching. - + The Attributes of the Scheduled Workitem Code Sequence shall only be retrieved with Sequence Matching.
- >Include - + >Include
- Comments on the - Scheduled Procedure Step - + Comments on the Scheduled Procedure Step (0040,0400) @@ -54876,8 +38969,7 @@
- Input Readiness State - + Input Readiness State (0040,4041) @@ -54901,16 +38993,12 @@ 1 - Input Readiness State - shall be retrieved with Single Value Matching. - + Input Readiness State shall be retrieved with Single Value Matching.
- Input Information - Sequence - + Input Information Sequence (0040,4021) @@ -54934,24 +39022,20 @@ 2 - The Attributes of the - Input Information Sequence shall only be retrieved with Sequence Matching. - + The Attributes of the Input Information Sequence shall only be retrieved with Sequence Matching.
- >Include - + >Include
- Study Instance UID - + Study Instance UID (0020,000D) @@ -54975,21 +39059,13 @@ 2 - Required if the - Workitem is expected to result in the creation of any DICOM Composite - Instances whose IOD contains the Study IE. - - There may be situations - where the performer does not use the Study Instance UID suggested by the - Scheduler. - + Required if the Workitem is expected to result in the creation of any DICOM Composite Instances whose IOD contains the Study IE. + There may be situations where the performer does not use the Study Instance UID suggested by the Scheduler.
- Output Destination - Sequence - + Output Destination Sequence (0040,4070) @@ -55013,16 +39089,13 @@ 3 - The Attributes of the - Output Destination Sequence shall only be retrieved with Sequence Matching. - + The Attributes of the Output Destination Sequence shall only be retrieved with Sequence Matching.
- >Include - + >Include
- All other Attributes of the - + All other Attributes of the - Required if the subject - of the workitem requires identification or if the workitem is expected to - result in the creation of objects that identify the subject. - - See - + Required if the subject of the workitem requires identification or if the workitem is expected to result in the creation of objects that identify the subject. + See
- Include - + Include
- Other Patient IDs - Sequence - + Other Patient IDs Sequence (0010,1002) @@ -55195,17 +39258,14 @@
- >Include - + >Include
- >Type of Patient - ID - + >Type of Patient ID (0010,0022) @@ -55232,8 +39292,7 @@
- Patient's Birth Date - + Patient's Birth Date (0010,0030) @@ -55288,9 +39347,7 @@
- Referenced Patient - Photo Sequence - + Referenced Patient Photo Sequence (0010,1100) @@ -55318,8 +39375,7 @@
- >Include - + >Include
- Issuer of Admission ID - Sequence - + Issuer of Admission ID Sequence (0038,0014) @@ -55383,17 +39437,14 @@
- >Include - + >Include
- Admitting Diagnoses - Description - + Admitting Diagnoses Description (0008,1080) @@ -55420,9 +39471,7 @@
- Admitting Diagnoses - Code Sequence - + Admitting Diagnoses Code Sequence (0008,1084) @@ -55446,27 +39495,19 @@ 2 - The Attributes of the - Admitting Diagnoses Code Sequence shall only be retrieved with Sequence - Matching. - + The Attributes of the Admitting Diagnoses Code Sequence shall only be retrieved with Sequence Matching.
- >Include - . - + >Include .
- Referenced Request - Sequence - + Referenced Request Sequence (0040,A370) @@ -55490,16 +39531,12 @@ 2 - Could be "changed" - while SCHEDULED by canceling and re-creating with the "correct" values. - + Could be "changed" while SCHEDULED by canceling and re-creating with the "correct" values.
- >Study Instance - UID - + >Study Instance UID (0020,000D) @@ -55526,8 +39563,7 @@
- >Accession Number - + >Accession Number (0008,0050) @@ -55554,9 +39590,7 @@
- >Issuer of Accession - Number Sequence - + >Issuer of Accession Number Sequence (0008,0051) @@ -55580,25 +39614,20 @@ 2 - The Issuer of Accession - Number Sequence shall only be retrieved with Sequence Matching. - + The Issuer of Accession Number Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include
- >Placer Order - Number/Imaging Service Request - + >Placer Order Number/Imaging Service Request (0040,2016) @@ -55627,9 +39656,7 @@
- >Order Placer - Identifier Sequence - + >Order Placer Identifier Sequence (0040,0026) @@ -55653,25 +39680,20 @@ 2 - The Order Placer - Identifier Sequence shall only be retrieved with Sequence Matching. - + The Order Placer Identifier Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include
- >Filler Order - Number/Imaging Service Request - + >Filler Order Number/Imaging Service Request (0040,2017) @@ -55700,9 +39722,7 @@
- >Order Filler - Identifier Sequence - + >Order Filler Identifier Sequence (0040,0027) @@ -55726,25 +39746,20 @@ 2 - The Order Filler - Identifier Sequence shall only be retrieved with Sequence Matching. - + The Order Filler Identifier Sequence shall only be retrieved with Sequence Matching.
- >>Include - + >>Include
- >Requested Procedure - ID - + >Requested Procedure ID (0040,1001) @@ -55771,9 +39786,7 @@
- >Requested Procedure - Description - + >Requested Procedure Description (0032,1060) @@ -55800,9 +39813,7 @@
- >Requested Procedure - Code Sequence - + >Requested Procedure Code Sequence (0032,1064) @@ -55830,17 +39841,14 @@
- >>Include - + >>Include
- >Reason for the - Requested Procedure - + >Reason for the Requested Procedure (0040,1002) @@ -55867,9 +39875,7 @@
- >Reason for - Requested Procedure Code Sequence - + >Reason for Requested Procedure Code Sequence (0040,100A) @@ -55897,17 +39903,14 @@
- >>Include - + >>Include
- >Requested Procedure - Comments - + >Requested Procedure Comments (0040,1400) @@ -55936,9 +39939,7 @@
- >Confidentiality - Code - + >Confidentiality Code (0040,1008) @@ -55965,9 +39966,7 @@
- >Names of Intended - Recipients of Results - + >Names of Intended Recipients of Results (0040,1010) @@ -55994,9 +39993,7 @@
- >Imaging Service - Request Comments - + >Imaging Service Request Comments (0040,2400) @@ -56023,9 +40020,7 @@
- >Requesting - Physician - + >Requesting Physician (0032,1032) @@ -56052,9 +40047,7 @@
- >Requesting - Service - + >Requesting Service (0032,1033) @@ -56081,9 +40074,7 @@
- >Requesting Service - Code Sequence - + >Requesting Service Code Sequence (0032,1034) @@ -56113,17 +40104,14 @@
- >>Include - + >>Include
- >Issue Date of - Imaging Service Request - + >Issue Date of Imaging Service Request (0040,2004) @@ -56150,9 +40138,7 @@
- >Issue Time of - Imaging Service Request - + >Issue Time of Imaging Service Request (0040,2005) @@ -56179,9 +40165,7 @@
- >Referring - Physician's Name - + >Referring Physician's Name (0008,0090) @@ -56208,9 +40192,7 @@
- Replaced Procedure Step - Sequence - + Replaced Procedure Step Sequence (0074,1224) @@ -56234,16 +40216,13 @@ 3 - Required if the UPS - replaces another Procedure Step. - + Required if the UPS replaces another Procedure Step.
- >Include - + >Include
- All other Attributes of the Unified Procedure Step - Relationship Module - + All other Attributes of the Unified Procedure Step Relationship Module @@ -56289,9 +40266,7 @@
- All Attributes of the - + All Attributes of the - Required if present. - + Required if present.
- Required if present. - + Required if present.
- Required if present. - + Required if present.
- All other Attributes of the - + All other Attributes of the
- All Attributes of the - + All Attributes of the
- All Attributes of the - + All Attributes of the
- All Attributes of the - + All Attributes of the
- Unified Procedure Step Progress Information Module - + Unified Procedure Step Progress Information Module
- Procedure Step State - + Procedure Step State (0074,1000) 1/1 - Shall be created with a - value of "SCHEDULED" - + Shall be created with a value of "SCHEDULED" Not Allowed. @@ -56593,16 +40553,12 @@ 1 - Procedure Step State - shall be retrieved with Single Value Matching - + Procedure Step State shall be retrieved with Single Value Matching
- Progress Information - Sequence - + Progress Information Sequence (0074,1002) @@ -56628,9 +40584,7 @@
- >Procedure Step - Progress - + >Procedure Step Progress (0074,1004) @@ -56657,9 +40611,7 @@
- >Procedure Step - Progress Description - + >Procedure Step Progress Description (0074,1006) @@ -56686,9 +40638,7 @@
- >Procedure Step - Progress Parameters Sequence - + >Procedure Step Progress Parameters Sequence (0074,1007) @@ -56716,17 +40666,14 @@
- >>Include - + >>Include
- >>Content Item - Modifier Sequence - + >>Content Item Modifier Sequence (0040,0441) @@ -56754,17 +40701,14 @@
- >>>Include - + >>>Include
- >Procedure Step - Communications URI Sequence - + >Procedure Step Communications URI Sequence (0074,1008) @@ -56791,8 +40735,7 @@
- >>Contact URI - + >>Contact URI (0074,100a) @@ -56819,9 +40762,7 @@
- >>Contact Display - Name - + >>Contact Display Name (0074,100c) @@ -56848,9 +40789,7 @@
- >Procedure Step - Cancellation DateTime - + >Procedure Step Cancellation DateTime (0040,4052) @@ -56874,17 +40813,12 @@ - - If changing the UPS - State (0074,1000) to CANCELED and this Attribute has no value, the SCP shall - fill it with the current datetime. - + If changing the UPS State (0074,1000) to CANCELED and this Attribute has no value, the SCP shall fill it with the current datetime.
- >Reason For - Cancellation - + >Reason For Cancellation (0074,1238) @@ -56911,9 +40845,7 @@
- >Procedure Step - Discontinuation Reason Code Sequence - + >Procedure Step Discontinuation Reason Code Sequence (0074,100e) @@ -56937,8 +40869,7 @@
- >>Include - + >>Include
- Unified Procedure Step Performed Procedure Information - Module - + Unified Procedure Step Performed Procedure Information Module
- Unified Procedure Step - Performed Procedure Sequence - + Unified Procedure Step Performed Procedure Sequence (0074,1216) 2/2 - Shall be created - empty - + Shall be created empty 3/2 @@ -56983,16 +40908,12 @@ - - See. - + See .
- >Actual Human - Performers Sequence - + >Actual Human Performers Sequence (0040,4035) @@ -57016,23 +40937,14 @@ 1C - Shall be provided if - known. - - Return Key required if - set. - - The Attributes of the - Actual Human Performers Sequence shall only be retrieved with Sequence - Matching. - + Shall be provided if known. + Return Key required if set. + The Attributes of the Actual Human Performers Sequence shall only be retrieved with Sequence Matching.
- >>Human Performer - Code Sequence - + >>Human Performer Code Sequence (0040,4009) @@ -57056,25 +40968,20 @@ - - Shall be provided if - known. - + Shall be provided if known.
- >>>Include - + >>>Include
- >>Human - Performer's Name - + >>Human Performer's Name (0040,4037) @@ -57098,16 +41005,12 @@ - - Shall be provided if - known - + Shall be provided if known
- >>Human - Performer's Organization - + >>Human Performer's Organization (0040,4036) @@ -57134,9 +41037,7 @@
- >Performed Station - Name Code Sequence - + >Performed Station Name Code Sequence (0040,4028) @@ -57164,17 +41065,14 @@
- >>Include - + >>Include
- >Performed Station - Class Code Sequence - + >Performed Station Class Code Sequence (0040,4029) @@ -57202,17 +41100,14 @@
- >>Include - + >>Include
- >Performed Station - Geographic Location Code Sequence - + >Performed Station Geographic Location Code Sequence (0040,4030) @@ -57240,17 +41135,14 @@
- >>Include - + >>Include
- >Performed Procedure - Step Start DateTime - + >Performed Procedure Step Start DateTime (0040,4050) @@ -57277,9 +41169,7 @@
- >Performed Procedure - Step Description - + >Performed Procedure Step Description (0040,0254) @@ -57306,9 +41196,7 @@
- >Comments on the - Performed Procedure Step - + >Comments on the Performed Procedure Step (0040,0280) @@ -57335,9 +41223,7 @@
- >Performed Workitem - Code Sequence - + >Performed Workitem Code Sequence (0040,4019) @@ -57365,17 +41251,14 @@
- >>Include - + >>Include
- >Performed - Processing Parameters Sequence - + >Performed Processing Parameters Sequence (0074,1212) @@ -57403,17 +41286,14 @@
- >>Include - + >>Include
- >Performed Procedure - Step End DateTime - + >Performed Procedure Step End DateTime (0040,4051) @@ -57442,9 +41322,7 @@
- >Output Information - Sequence - + >Output Information Sequence (0040,4033) @@ -57468,16 +41346,13 @@ - - If there are no - relevant output objects, then this sequence may have no items. - + If there are no relevant output objects, then this sequence may have no items.
- >Include - + >Include
UPS SOP Class UID - The SOP Class UID shall be set to - 1.2.840.10008.5.1.4.34.6.1 by SCP - + The SOP Class UID shall be set to 1.2.840.10008.5.1.4.34.6.1 by SCP
Unified Procedure Step Performed Procedure Sequence - The Attributes of the UPS Performed - Procedure Sequence shall only be retrieved with Sequence Matching. - + The Attributes of the UPS Performed Procedure Sequence shall only be retrieved with Sequence Matching. - Since this Attribute may be - created empty and has a Final State requirement of X, a UPS in the SCHEDULED state - may be canceled with two N-ACTIONS (IN PROGRESS then CANCELED) and no N-SETs. - + Since this Attribute may be created empty and has a Final State requirement of X, a UPS in the SCHEDULED state may be canceled with two N-ACTIONS (IN PROGRESS then CANCELED) and no N-SETs.
Service Class User Behavior - An SCU uses N-CREATE to request the SCP - schedule a new UPS. - - The SCU shall specify in the N-CREATE - request primitive the UPS Push SOP Class UID and the SOP Instance UID for the UPS that is to be - created and for which Attribute Values are to be provided. See - - for further discussion of UPS SOP Class UIDs. - - The SCU shall provide Attribute Values in - the N-CREATE request primitive for all required UPS Attributes as specified in. Additionally, values may be - provided for optional Attributes as specified in. - - The SCU shall specify a value of - "SCHEDULED" for the Attribute Procedure Step State (0074,1000) in the N-CREATE request - primitive. - + An SCU uses N-CREATE to request the SCP schedule a new UPS. + The SCU shall specify in the N-CREATE request primitive the UPS Push SOP Class UID and the SOP Instance UID for the UPS that is to be created and for which Attribute Values are to be provided. See for further discussion of UPS SOP Class UIDs. + The SCU shall provide Attribute Values in the N-CREATE request primitive for all required UPS Attributes as specified in . Additionally, values may be provided for optional Attributes as specified in . + The SCU shall specify a value of "SCHEDULED" for the Attribute Procedure Step State (0074,1000) in the N-CREATE request primitive.
Service Class Provider Behavior - The SCP shall create and maintain UPS - instances as instructed by creation requests and as specified by - . - - The SCP shall return, via the N-CREATE - response primitive, the N-CREATE Response Status Code applicable to the associated request. - - The SCP shall accept creation requests only - if the value of the Procedure Step State (0074,1000) Attribute is "SCHEDULED". If the Procedure - Step State Attribute has another value, the SCP shall fail the request. - - The SCP may modify Attributes of a UPS - instance, e.g., to correct invalid Attribute Values. A description of the modifications the SCP - may perform shall be documented in the conformance statement of the SCP. - - The SCP may also create and maintain UPS - instances without receiving a UPS instance N-CREATE request, e.g., based on internal logic, - operator inputs or HL7 messages. The contents of the instance created by the SCP must still - comply with the N-CREATE requirements in. - - Upon creating a new UPS Instance, the SCP - shall update UPS Subscription Status of the Instance for each AE with a Global Subscription as - described in. Optionally, the SCP may - create a UPS Subscription for the N-CREATE SCU AE; such behavior shall be documented in the - Conformance Statement. - - Upon creating a new UPS Instance, the SCP - shall send UPS State Reports (if it supports the UPS Event SOP Class) as described in - - regardless of whether the creation was based on an N-CREATE or on internal logic. - - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. There are no specific requirements to - perform authorization. - + The SCP shall create and maintain UPS instances as instructed by creation requests and as specified by . + The SCP shall return, via the N-CREATE response primitive, the N-CREATE Response Status Code applicable to the associated request. + The SCP shall accept creation requests only if the value of the Procedure Step State (0074,1000) Attribute is "SCHEDULED". If the Procedure Step State Attribute has another value, the SCP shall fail the request. + The SCP may modify Attributes of a UPS instance, e.g., to correct invalid Attribute Values. A description of the modifications the SCP may perform shall be documented in the conformance statement of the SCP. + The SCP may also create and maintain UPS instances without receiving a UPS instance N-CREATE request, e.g., based on internal logic, operator inputs or HL7 messages. The contents of the instance created by the SCP must still comply with the N-CREATE requirements in . + Upon creating a new UPS Instance, the SCP shall update UPS Subscription Status of the Instance for each AE with a Global Subscription as described in . Optionally, the SCP may create a UPS Subscription for the N-CREATE SCU AE; such behavior shall be documented in the Conformance Statement. + Upon creating a new UPS Instance, the SCP shall send UPS State Reports (if it supports the UPS Event SOP Class) as described in regardless of whether the creation was based on an N-CREATE or on internal logic. + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. There are no specific requirements to perform authorization.
Status Codes - - defines the status code values that might be returned in a N-CREATE response. General status - code values and fields related to status code values are defined for N-CREATE DIMSE Service in - . - + defines the status code values that might be returned in a N-CREATE response. General status code values and fields related to status code values are defined for N-CREATE DIMSE Service in . @@ -57599,9 +41415,7 @@ Success
N-CREATE Response Status Values [for Create a Unified Procedure Step]
- The UPS was created as - requested - + The UPS was created as requested 0000 @@ -57612,9 +41426,7 @@ Warning - The UPS was created with - modifications - + The UPS was created with modifications B300 @@ -57625,9 +41437,7 @@ Failure - Failed: The provided value - of UPS State was not "SCHEDULED". - + Failed: The provided value of UPS State was not "SCHEDULED". C309 @@ -57639,120 +41449,42 @@
Set Unified Procedure Step Information (N-SET) - This operation allows an SCU to set Attribute - Values of a UPS Instance and provide information about a specific real-world UPS that is under - control of the SCU. This operation shall be invoked by the SCU through the DIMSE N-SET Service. - + This operation allows an SCU to set Attribute Values of a UPS Instance and provide information about a specific real-world UPS that is under control of the SCU. This operation shall be invoked by the SCU through the DIMSE N-SET Service.
Unified Procedure Step IOD Subset Specification - The Application Entity that claims - conformance to the UPS Pull SOP Class as an SCU may choose to modify a subset of the Attributes - maintained by the SCP. The Application Entity that claims conformance as an SCP to the UPS Pull - SOP Class shall support Attributes specified in - + The Application Entity that claims conformance to the UPS Pull SOP Class as an SCU may choose to modify a subset of the Attributes maintained by the SCP. The Application Entity that claims conformance as an SCP to the UPS Pull SOP Class shall support Attributes specified in
Service Class User Behavior - The SCU shall specify in the N-SET request - primitive the UID of the UPS Instance for which it wants to set Attribute Values. Since all UPSs - are created as instances of the UPS Push SOP Class, the Requested SOP Class UID in the N-SET - request shall be the UID of the UPS Push SOP Class. See - - for further details. - - To N-SET a UPS instance currently in the - SCHEDULED state, the Transaction UID Attribute shall not be present in the request. For a UPS - instance in the IN PROGRESS state, the SCU shall provide the current Transaction UID (0008,1195) - as an Attribute. - - The SCU shall be permitted to set Attribute - Values as specified in. The SCU shall - specify the list of Attributes for which it wants to set the Attribute Values. The SCU shall - provide, with one or more N-SET request primitives, the Attribute Values specified in. - - When modifying a sequence, the SCU shall - include in the N-SET request all Items in the sequence, not just the Items to be modified. - - N-SET requests shall be atomic - (indivisible) and idempotent (repeat executions have no additional effect). Since it is possible - for an N-GET to occur between two N-SET requests, any given N-SET shall leave the UPS instance - in an internally consistent state (i.e., when multiple Attributes need updating as a group, do - this as multiple Attributes in a single N-SET request, not as multiple N-SET requests) - - The SCU shall not set the value of the - Procedure Step State (0074,1000) Attribute using N-SET. Procedure Step State is managed using - N-ACTION as described in - - - The SCU shall create or set all Attributes - to meet Final State requirements prior to using N-ACTION to set the value of Procedure Step - State (0074,1000) to "COMPLETED" or "CANCELED". See - - for further details. - - Once the Procedure Step State (0074,1000) - has been set to "COMPLETED" or "CANCELED" the SCU shall no longer modify the UPS SOP Instance. - + The SCU shall specify in the N-SET request primitive the UID of the UPS Instance for which it wants to set Attribute Values. Since all UPSs are created as instances of the UPS Push SOP Class, the Requested SOP Class UID in the N-SET request shall be the UID of the UPS Push SOP Class. See for further details. + To N-SET a UPS instance currently in the SCHEDULED state, the Transaction UID Attribute shall not be present in the request. For a UPS instance in the IN PROGRESS state, the SCU shall provide the current Transaction UID (0008,1195) as an Attribute. + The SCU shall be permitted to set Attribute Values as specified in . The SCU shall specify the list of Attributes for which it wants to set the Attribute Values. The SCU shall provide, with one or more N-SET request primitives, the Attribute Values specified in . + When modifying a sequence, the SCU shall include in the N-SET request all Items in the sequence, not just the Items to be modified. + N-SET requests shall be atomic (indivisible) and idempotent (repeat executions have no additional effect). Since it is possible for an N-GET to occur between two N-SET requests, any given N-SET shall leave the UPS instance in an internally consistent state (i.e., when multiple Attributes need updating as a group, do this as multiple Attributes in a single N-SET request, not as multiple N-SET requests) + The SCU shall not set the value of the Procedure Step State (0074,1000) Attribute using N-SET. Procedure Step State is managed using N-ACTION as described in + + The SCU shall create or set all Attributes to meet Final State requirements prior to using N-ACTION to set the value of Procedure Step State (0074,1000) to "COMPLETED" or "CANCELED". See for further details. + Once the Procedure Step State (0074,1000) has been set to "COMPLETED" or "CANCELED" the SCU shall no longer modify the UPS SOP Instance. - The SCU can only set Attribute Values - that have already been created with an N-CREATE request. - + The SCU can only set Attribute Values that have already been created with an N-CREATE request.
Service Class Provider Behavior - The SOP Class UID of the specified UPS - instance will always be the UPS Push SOP Class UID, which might not match the UPS SOP Class - negotiated with the SCU. See - - for further details. - - The SCP shall support the Attribute changes - to the UPS instance specified by the SCU in the set request as specified in. - - The SCP shall refuse set requests on an IN - PROGRESS UPS and not modify the UPS if the set request does not include the Transaction UID - (0008,1195) Attribute with the same value as currently recorded in the UPS instance. - - The SCP shall refuse set requests on a - COMPLETED or CANCELED UPS. - - The SCP shall use the Specific Character - Set (0008,0005) value to appropriately modify its internal representation so that subsequent - operations reflect the combination of the character sets in use by the Attributes in this - request and those used by Attributes that have not been modified. - - The SCP shall return, via the N-SET - response primitive, the N-SET Response Status Code applicable to the associated request as - specified in. - - The SCP may itself modify any Attributes of - a UPS instance independently of an N-SET request, e.g., if the SCP is performing the procedure - step itself, if it has been determined that the performing SCU has been disabled, or if it is - necessary to correct Attribute Values after completion of the procedure in order to carry out - reconciliation of the data. A description of the coercions the SCP may perform shall be - documented in the conformance statement of the SCP. - - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. There are no specific requirements to - perform authorization. - + The SOP Class UID of the specified UPS instance will always be the UPS Push SOP Class UID, which might not match the UPS SOP Class negotiated with the SCU. See for further details. + The SCP shall support the Attribute changes to the UPS instance specified by the SCU in the set request as specified in . + The SCP shall refuse set requests on an IN PROGRESS UPS and not modify the UPS if the set request does not include the Transaction UID (0008,1195) Attribute with the same value as currently recorded in the UPS instance. + The SCP shall refuse set requests on a COMPLETED or CANCELED UPS. + The SCP shall use the Specific Character Set (0008,0005) value to appropriately modify its internal representation so that subsequent operations reflect the combination of the character sets in use by the Attributes in this request and those used by Attributes that have not been modified. + The SCP shall return, via the N-SET response primitive, the N-SET Response Status Code applicable to the associated request as specified in . + The SCP may itself modify any Attributes of a UPS instance independently of an N-SET request, e.g., if the SCP is performing the procedure step itself, if it has been determined that the performing SCU has been disabled, or if it is necessary to correct Attribute Values after completion of the procedure in order to carry out reconciliation of the data. A description of the coercions the SCP may perform shall be documented in the conformance statement of the SCP. + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. There are no specific requirements to perform authorization.
Status Codes - - defines the status code values that might be returned in a N-SET response. General status code - values and fields related to status code values are defined for N-SET DIMSE Service in. - + defines the status code values that might be returned in a N-SET response. General status code values and fields related to status code values are defined for N-SET DIMSE Service in . @@ -57774,9 +41506,7 @@ Success
N-SET Response Status Values [for Set Unified Procedure Step Information]
- The requested modification - of the Attribute Values is performed - + The requested modification of the Attribute Values is performed 0000 @@ -57787,9 +41517,7 @@ Warning - Requested optional - Attributes are not supported. - + Requested optional Attributes are not supported. 0001 @@ -57797,9 +41525,7 @@
- Coerced invalid values to - valid values - + Coerced invalid values to valid values B305 @@ -57810,9 +41536,7 @@ Failure - Failed: The UPS is not in - the "IN PROGRESS" state - + Failed: The UPS is not in the "IN PROGRESS" state C310 @@ -57820,9 +41544,7 @@
- Failed: The correct - Transaction UID was not provided - + Failed: The correct Transaction UID was not provided C301 @@ -57830,9 +41552,7 @@
- Failed: The UPS may no - longer be updated - + Failed: The UPS may no longer be updated C300 @@ -57840,9 +41560,7 @@
- Failed: Specified SOP - Instance UID does not exist or is not a UPS Instance managed by this SCP - + Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP C307 @@ -57854,118 +41572,42 @@
Get Unified Procedure Step Information (N-GET) - This operation allows an SCU to get information - from an SCP about a specific real-world Procedure Step that is represented as a Unified Procedure - Step Instance. This operation shall be invoked by the SCU through the DIMSE N-GET Service. - + This operation allows an SCU to get information from an SCP about a specific real-world Procedure Step that is represented as a Unified Procedure Step Instance. This operation shall be invoked by the SCU through the DIMSE N-GET Service.
Unified Procedure Step IOD Subset Specification - The Application Entity that claims - conformance to the UPS Pull or UPS Watch SOP Classes as an SCU may choose to retrieve a subset - of the Attribute Values maintained by the SCP. The Application Entity that claims conformance as - an SCP to these SOP Classes shall support the Attributes specified in. - + The Application Entity that claims conformance to the UPS Pull or UPS Watch SOP Classes as an SCU may choose to retrieve a subset of the Attribute Values maintained by the SCP. The Application Entity that claims conformance as an SCP to these SOP Classes shall support the Attributes specified in .
Service Class User Behavior - The SCU uses the N-GET to request the SCP - to provide Attributes and values of a Unified Procedure Step Instance. Since all UPSs are - created as instances of the UPS Push SOP Class, the Affected SOP Class UID (0000,0002) in the - N-GET request shall be the UID of the UPS Push SOP Class. See - - for further details. - - The SCU shall specify in the N-GET Service - Element the UID of the SOP Instance from which Attributes are to be retrieved. - - The SCU shall specify the list of Unified - Procedure Step Attributes for which values are to be returned. The SCU shall not specify - Attributes that are defined within a Sequence, but rather specify the sequence itself to be - retrieved in its entirety. - - The SCU shall not request the value of the - Transaction UID (0008,1195) Attribute. - - The SCU may request Attribute Values for - optional Attributes that are not maintained by the SCP. In such a case, the SCU shall function - properly regardless of whether the SCP returns values for those Attributes or not. This Service - Class Specification places no requirements on what the SCU shall do as a result of receiving - this information. - + The SCU uses the N-GET to request the SCP to provide Attributes and values of a Unified Procedure Step Instance. Since all UPSs are created as instances of the UPS Push SOP Class, the Affected SOP Class UID (0000,0002) in the N-GET request shall be the UID of the UPS Push SOP Class. See for further details. + The SCU shall specify in the N-GET Service Element the UID of the SOP Instance from which Attributes are to be retrieved. + The SCU shall specify the list of Unified Procedure Step Attributes for which values are to be returned. The SCU shall not specify Attributes that are defined within a Sequence, but rather specify the sequence itself to be retrieved in its entirety. + The SCU shall not request the value of the Transaction UID (0008,1195) Attribute. + The SCU may request Attribute Values for optional Attributes that are not maintained by the SCP. In such a case, the SCU shall function properly regardless of whether the SCP returns values for those Attributes or not. This Service Class Specification places no requirements on what the SCU shall do as a result of receiving this information. - In order to accurately interpret the - character set used for the Attribute Values returned, it is recommended that the Attribute - Value for the Specific Character Set (0008,0005) be requested in the N-GET request - primitive. - + In order to accurately interpret the character set used for the Attribute Values returned, it is recommended that the Attribute Value for the Specific Character Set (0008,0005) be requested in the N-GET request primitive. - The SCU shall be permitted to request and - shall be capable of receiving values for any Attribute as specified in. Additionally, values may be - requested for optional Attributes. - - The SCU shall be capable of receiving all - requested Attribute Values provided by the SCP in response to the N-GET indication primitive. - + The SCU shall be permitted to request and shall be capable of receiving values for any Attribute as specified in . Additionally, values may be requested for optional Attributes. + The SCU shall be capable of receiving all requested Attribute Values provided by the SCP in response to the N-GET indication primitive. - If the SCU or the user will need access - to the final state Attributes it is the responsibility of the SCU to Subscribe (see) in order to receive State Change - Events and then N-GET the necessary Attributes promptly upon notification of a state change - to COMPLETED or CANCELED. If the SCU sets the Deletion Lock when subscribing, a COMPLETED or - CANCELED instance will continue to persist on the SCP, using resources. It is important that - the SCU remove the lock (e.g., by unsubscribing) after doing the N-GET on the COMPLETED or - CANCELED instance. - + If the SCU or the user will need access to the final state Attributes it is the responsibility of the SCU to Subscribe (see ) in order to receive State Change Events and then N-GET the necessary Attributes promptly upon notification of a state change to COMPLETED or CANCELED. If the SCU sets the Deletion Lock when subscribing, a COMPLETED or CANCELED instance will continue to persist on the SCP, using resources. It is important that the SCU remove the lock (e.g., by unsubscribing) after doing the N-GET on the COMPLETED or CANCELED instance.
Service Class Provider Behavior - The SOP Class UID of the specified UPS - instance will always be the UPS Push SOP Class UID, which might not match the UPS SOP Classes - negotiated with the SCU. See - - for further details. - - The SCP shall return, via the N-GET - response primitive, the selected Attribute Values from the indicated Unified Procedure Step - Instance to the SCU. - + The SOP Class UID of the specified UPS instance will always be the UPS Push SOP Class UID, which might not match the UPS SOP Classes negotiated with the SCU. See for further details. + The SCP shall return, via the N-GET response primitive, the selected Attribute Values from the indicated Unified Procedure Step Instance to the SCU. - The requirement for the SCP to respond - to N-GET requests for UPS Instances that have moved to the COMPLETED or CANCELED state is - limited. See - - Service Class Provider Behavior. - + The requirement for the SCP to respond to N-GET requests for UPS Instances that have moved to the COMPLETED or CANCELED state is limited. See Service Class Provider Behavior. - The SCP shall not return the Transaction - UID (0008,1195) Attribute. This is necessary to preserve this Attribute's role as an access - lock. - - The SCP shall return, via the N-GET - response primitive, the N-GET Response Status Code applicable to the associated request. A - Failure Code shall indicate that the SCP has not retrieved the SOP Instance. - - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting - authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP - Class. - + The SCP shall not return the Transaction UID (0008,1195) Attribute. This is necessary to preserve this Attribute's role as an access lock. + The SCP shall return, via the N-GET response primitive, the N-GET Response Status Code applicable to the associated request. A Failure Code shall indicate that the SCP has not retrieved the SOP Instance. + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP Class.
Status Codes - - defines the status code values that might be returned in a N-GET response. General status code - values and fields related to status code values are defined for N-GET DIMSE Service in. - + defines the status code values that might be returned in a N-GET response. General status code values and fields related to status code values are defined for N-GET DIMSE Service in . @@ -57987,9 +41629,7 @@ Warning
N-GET Response Status Values [for Get Unified Procedure Step Information]
- Requested optional - Attributes are not supported - + Requested optional Attributes are not supported 0001 @@ -58000,9 +41640,7 @@ Failure - Failed: Specified SOP - Instance UID does not exist or is not a UPS Instance managed by this SCP - + Failed: Specified SOP Instance UID does not exist or is not a UPS Instance managed by this SCP C307 @@ -58014,28 +41652,14 @@
Search for Unified Procedure Step (C-FIND) - This operation allows an SCU to locate and get - information about Unified Procedure Step instances of interest that are managed by an SCP. This - operation shall be invoked by the SCU through the DIMSE C-FIND Service. The SCP processes such - queries, matches UPS instances it manages against the keys present in the Identifier and returns - C-FIND responses. - - The SCU might be searching for UPS instance - with the intention of starting work on one of them or perhaps with the intention of subscribing to - monitor the progress of an instance. - + This operation allows an SCU to locate and get information about Unified Procedure Step instances of interest that are managed by an SCP. This operation shall be invoked by the SCU through the DIMSE C-FIND Service. The SCP processes such queries, matches UPS instances it manages against the keys present in the Identifier and returns C-FIND responses. + The SCU might be searching for UPS instance with the intention of starting work on one of them or perhaps with the intention of subscribing to monitor the progress of an instance.
Operation
E/R Model - In response to a given C-FIND request, - the SCP might send several C-FIND responses, (i.e., one C-FIND response per matching - worklist item). Each worklist item describes a single task and its related information. - - The Unified Procedure Step Query - Information Model is represented by the Entity Relationship diagram shown in. - + In response to a given C-FIND request, the SCP might send several C-FIND responses, (i.e., one C-FIND response per matching worklist item). Each worklist item describes a single task and its related information. + The Unified Procedure Step Query Information Model is represented by the Entity Relationship diagram shown in .
Unified Procedure Step E-R Diagram @@ -58047,306 +41671,152 @@
- There is only one Information Entity in - the model, which is the Unified Procedure Step. The Attributes of a Unified Procedure Step - can be found in. - + There is only one Information Entity in the model, which is the Unified Procedure Step. The Attributes of a Unified Procedure Step can be found in .
C-FIND Service Parameters
SOP Class UID - The Affected SOP Class UID of the - C-FIND DIMSE request shall always be the UPS SOP Class negotiated for the Presentation - Context under which the service is requested. This will always be the UPS Pull SOP - Class, the UPS Watch SOP Class, or the UPS Query SOP Class. See - - for further details. - - The C-FIND is performed against the - Unified Procedure Step Information Model shown in. - + The Affected SOP Class UID of the C-FIND DIMSE request shall always be the UPS SOP Class negotiated for the Presentation Context under which the service is requested. This will always be the UPS Pull SOP Class, the UPS Watch SOP Class, or the UPS Query SOP Class. See for further details. + The C-FIND is performed against the Unified Procedure Step Information Model shown in .
Priority - The Priority Attribute defines the - requested priority of the C-FIND operation with respect to other DIMSE operations being - performed by the same SCP. - - Processing of priority requests is - not required of SCPs. Whether or not an SCP supports priority processing and the meaning - of the different priority levels shall be stated in the Conformance Statement of the - SCP. - + The Priority Attribute defines the requested priority of the C-FIND operation with respect to other DIMSE operations being performed by the same SCP. + Processing of priority requests is not required of SCPs. Whether or not an SCP supports priority processing and the meaning of the different priority levels shall be stated in the Conformance Statement of the SCP.
Identifier - Both the C-FIND request and response - contain an Identifier encoded as a Data Set (see). - + Both the C-FIND request and response contain an Identifier encoded as a Data Set (see ).
Request Identifier Structure - An Identifier in a C-FIND request - shall contain: - + An Identifier in a C-FIND request shall contain: - Key Attributes values to be - matched against the values of Attributes specified in the SOP Class identified - by the Affected SOP Class UID. - + Key Attributes values to be matched against the values of Attributes specified in the SOP Class identified by the Affected SOP Class UID. - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Request Identifier. It shall not be included otherwise. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Request Identifier. It shall not be included otherwise. - Conditionally, the - Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included - if Key Attributes of time are to be interpreted explicitly in the designated - local time zone. It shall not be present otherwise, i.e., it shall not be sent - with a zero-length value. - + Conditionally, the Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included if Key Attributes of time are to be interpreted explicitly in the designated local time zone. It shall not be present otherwise, i.e., it shall not be sent with a zero-length value. - This means that Specific - Character Set (0008,0005) is included if the SCU supports expanded or replacement - character sets in the context of this service. It will not be included if expanded - or replacement character sets are not supported by the SCU. - + This means that Specific Character Set (0008,0005) is included if the SCU supports expanded or replacement character sets in the context of this service. It will not be included if expanded or replacement character sets are not supported by the SCU. - The Key Attributes and values - allowable for the query shall be defined in the SOP Class definition corresponding to - the Affected SOP Class UID for the corresponding Unified Worklist And Procedure Step - Information Model. - + The Key Attributes and values allowable for the query shall be defined in the SOP Class definition corresponding to the Affected SOP Class UID for the corresponding Unified Worklist And Procedure Step Information Model.
Response Identifier Structure - The C-FIND response shall not - contain Attributes that were not in the request or specified in this section. - - An Identifier in a C-FIND response - shall contain: - + The C-FIND response shall not contain Attributes that were not in the request or specified in this section. + An Identifier in a C-FIND response shall contain: - Key Attributes with values - corresponding to Key Attributes contained in the Identifier of the request (Key - Attributes as defined in.) - + Key Attributes with values corresponding to Key Attributes contained in the Identifier of the request (Key Attributes as defined in .) - Conditionally, the - Attribute Specific Character Set (0008,0005). This Attribute shall be included - if expanded or replacement character sets may be used in any of the Attributes - in the Response Identifier. It shall not be included otherwise. The C-FIND SCP - is not required to return responses in the Specific Character Set requested by - the SCU if that character set is not supported by the SCP. The SCP may return - responses with a different Specific Character Set. - + Conditionally, the Attribute Specific Character Set (0008,0005). This Attribute shall be included if expanded or replacement character sets may be used in any of the Attributes in the Response Identifier. It shall not be included otherwise. The C-FIND SCP is not required to return responses in the Specific Character Set requested by the SCU if that character set is not supported by the SCP. The SCP may return responses with a different Specific Character Set. - Conditionally, the - Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included - if any Attributes of time in the Response Identifier are to be interpreted - explicitly in the designated local time zone. It shall not be present otherwise, - i.e., it shall not be sent with a zero-length value. - + Conditionally, the Attribute Timezone Offset From UTC (0008,0201). This Attribute shall be included if any Attributes of time in the Response Identifier are to be interpreted explicitly in the designated local time zone. It shall not be present otherwise, i.e., it shall not be sent with a zero-length value. - This means that Specific - Character Set (0008,0005) is included if the SCP supports expanded or replacement - character sets in the context of this service. It will not be included if expanded - or replacement character sets are not supported by the SCP. - + This means that Specific Character Set (0008,0005) is included if the SCP supports expanded or replacement character sets in the context of this service. It will not be included if expanded or replacement character sets are not supported by the SCP.
Service Class User Behavior - All C-FIND SCUs shall be capable of - generating query requests that meet the requirements of the "Worklist" Search Method (see). - - Required Keys and Optional Keys, identified - in, associated with the Query may be - contained in the Identifier. - - An SCU conveys the following semantics - using the C-FIND requests and responses: - + All C-FIND SCUs shall be capable of generating query requests that meet the requirements of the "Worklist" Search Method (see ). + Required Keys and Optional Keys, identified in , associated with the Query may be contained in the Identifier. + An SCU conveys the following semantics using the C-FIND requests and responses: - The SCU requests that the SCP - perform a match of all keys specified in the Identifier of the request against the - information it possesses of the Query specified in the request. - + The SCU requests that the SCP perform a match of all keys specified in the Identifier of the request against the information it possesses of the Query specified in the request. - The SCU shall interpret Pending - responses to convey the Attributes of a match of an item. - + The SCU shall interpret Pending responses to convey the Attributes of a match of an item. - The SCU shall interpret a response - with a status equal to Success, Failure, or Cancel to convey the end of Pending - responses. - + The SCU shall interpret a response with a status equal to Success, Failure, or Cancel to convey the end of Pending responses. - The SCU shall interpret a Failure - response to a C-FIND request as an indication that the SCP is unable to process the - request. - + The SCU shall interpret a Failure response to a C-FIND request as an indication that the SCP is unable to process the request. - The SCU may cancel the C-FIND - service by issuing a C-FIND-CANCEL request at any time during the processing of the - C-FIND. The SCU shall recognize a status of Cancel to indicate that the C-FIND-CANCEL - was successful. - + The SCU may cancel the C-FIND service by issuing a C-FIND-CANCEL request at any time during the processing of the C-FIND. The SCU shall recognize a status of Cancel to indicate that the C-FIND-CANCEL was successful.
Service Class Provider Behavior - All C-FIND SCPs shall be capable of - processing queries that meet the requirements of the "Worklist" Search (see). This does not imply that an SCP - that supports the UPS Watch SOP Class or the UPS Query SOP Class must also be an SCP of the UPS - Pull SOP Class. - - The SCP shall support Attribute matching as - described in. - - An SCP conveys the following semantics - using the C-FIND requests and responses: - + All C-FIND SCPs shall be capable of processing queries that meet the requirements of the "Worklist" Search (see ). This does not imply that an SCP that supports the UPS Watch SOP Class or the UPS Query SOP Class must also be an SCP of the UPS Pull SOP Class. + The SCP shall support Attribute matching as described in . + An SCP conveys the following semantics using the C-FIND requests and responses: - The SCP is requested to perform a - match of all the keys specified in the Identifier of the request, against the - information it possesses. Attribute matching is performed using the key values specified - in the Identifier of the C-FIND request as defined in. - + The SCP is requested to perform a match of all the keys specified in the Identifier of the request, against the information it possesses. Attribute matching is performed using the key values specified in the Identifier of the C-FIND request as defined in . - The SCP generates a C-FIND response - for each match using the "Worklist" Search method. All such responses shall contain an - Identifier whose Attributes contain values from a single match. All such responses shall - contain a status of Pending. - + The SCP generates a C-FIND response for each match using the "Worklist" Search method. All such responses shall contain an Identifier whose Attributes contain values from a single match. All such responses shall contain a status of Pending. - When all matches have been sent, - the SCP generates a C-FIND response that contains a status of Success. A status of - Success shall indicate that a response has been sent for each match known to the SCP. - + When all matches have been sent, the SCP generates a C-FIND response that contains a status of Success. A status of Success shall indicate that a response has been sent for each match known to the SCP. - No Identifier is contained in a - response with a status of Success. For a complete definition, see. - + No Identifier is contained in a response with a status of Success. For a complete definition, see . - When there are no matches, then - no responses with a status of Pending are sent, only a single response with a status - of Success. - + When there are no matches, then no responses with a status of Pending are sent, only a single response with a status of Success. - The SCP shall generate a response - with a status of Failure if it is unable to process the request. A Failure response - shall contain no Identifier. - + The SCP shall generate a response with a status of Failure if it is unable to process the request. A Failure response shall contain no Identifier. - If the SCP receives C-FIND-CANCEL - indication before it has completed the processing of the matches it shall interrupt the - matching process and return a status of Cancel. - + If the SCP receives C-FIND-CANCEL indication before it has completed the processing of the matches it shall interrupt the matching process and return a status of Cancel. - Bi-directional Authentication of - machines/users/applications is possible at association time (see - - and). - - provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting - authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP - Class. - + Bi-directional Authentication of machines/users/applications is possible at association time (see and ). provides a "Refused: Refused: Not authorized" error code. Further requiring or documenting authentication and/or authorization features from the SCU or SCP is beyond the scope of this SOP Class.
Worklist Search Method - The following steps are used to - generate match responses. - + The following steps are used to generate match responses. - Match the key match Attributes - contained in the Identifier of the C-FIND request against the values of the Key - Attributes for each worklist entity. - + Match the key match Attributes contained in the Identifier of the C-FIND request against the values of the Key Attributes for each worklist entity. - If there are no matching keys, - then there are no matches, return a response with a status equal to Success and with - no Identifier. - + If there are no matching keys, then there are no matches, return a response with a status equal to Success and with no Identifier. Otherwise, - For each entity for - which the Attributes match all of the specified matching key Attributes, - construct an Identifier. This Identifier shall contain all of the values of - the Attributes for this entity that correspond to the return keys specified - in the C-FIND request. - + For each entity for which the Attributes match all of the specified matching key Attributes, construct an Identifier. This Identifier shall contain all of the values of the Attributes for this entity that correspond to the return keys specified in the C-FIND request. - Return a response for - each remaining Identifier. - + Return a response for each remaining Identifier. - - defines the Attributes of the Unified Procedure Step Information Model, the requirements for - key matching, and the requirements for return keys. - + defines the Attributes of the Unified Procedure Step Information Model, the requirements for key matching, and the requirements for return keys.
Status Codes - - defines the status code values that might be returned in a C-FIND response. General status code - values and fields related to status code values are defined for C-FIND DIMSE Service in. - + defines the status code values that might be returned in a C-FIND response. General status code values and fields related to status code values are defined for C-FIND DIMSE Service in . @@ -58371,8 +41841,7 @@ Failure
C-FIND Response Status Values [for Search for Unified Procedure Step]
- Refused: Out of resources - + Refused: Out of resources A700 @@ -58383,9 +41852,7 @@
- Error: Data Set does not - match SOP Class - + Error: Data Set does not match SOP Class A900 @@ -58397,9 +41864,7 @@
- Refused: SOP Class not - supported - + Refused: SOP Class not supported 0122 @@ -58408,8 +41873,7 @@
- Failed: Unable to process - + Failed: Unable to process Cxxx @@ -58424,9 +41888,7 @@ Cancel - Matching terminated due to - Cancel request - + Matching terminated due to Cancel request FE00 @@ -58440,9 +41902,7 @@ Success - Matching is complete - No - final Identifier is supplied. - + Matching is complete - No final Identifier is supplied. 0000 @@ -58456,10 +41916,7 @@ Pending - Matches are continuing - - Current Match is supplied and any Optional Keys were supported in the same - manner as Required Keys. - + Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF00 @@ -58470,10 +41927,7 @@
- Matches are continuing - - Warning that one or more Optional Keys were not supported for existence for this - Identifier. - + Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier. FF01 @@ -58485,372 +41939,186 @@
- Status Codes are returned in DIMSE - response messages (see). The code values stated in - column "Status Codes" are returned in Status Command Element (0000,0900). - + Status Codes are returned in DIMSE response messages (see ). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900). - Some Failure Status Codes are - implementation specific. - - An SCP implementation shall assign specific - failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 - to F. An SCP implementation wishing to differentiate between causes of “Failed: Unable to - process” Failure Meaning shall assign those causes specific Status Code Values within valid - range specified in. - - An SCU implementation shall recognize any - Failure Status Code within the value range specified in - - as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU - implementation to differentiate between specific Status Codes within the valid range. - + Some Failure Status Codes are implementation specific. + An SCP implementation shall assign specific failure status codes by replacing each 'x' symbol with a hexadecimal digit in the range from 0 to F. An SCP implementation wishing to differentiate between causes of “Failed: Unable to process” Failure Meaning shall assign those causes specific Status Code Values within valid range specified in . + An SCU implementation shall recognize any Failure Status Code within the value range specified in as an indicator of the Failure Meaning stated in the table. There is no requirement for an SCU implementation to differentiate between specific Status Codes within the valid range.
UPS SOP Classes - There are five UPS SOP Classes associated with the - Unified Procedure Step IOD. Each SOP Class supports different interactions with a UPS Instance (also - referred to as a worklist item). - - The UPS Push SOP Class allows SCU systems to: - + There are five UPS SOP Classes associated with the Unified Procedure Step IOD. Each SOP Class supports different interactions with a UPS Instance (also referred to as a worklist item). + The UPS Push SOP Class allows SCU systems to: - create (push) a new worklist item (i.e., - instance) onto a worklist - + create (push) a new worklist item (i.e., instance) onto a worklist - submit a cancellation request for a - worklist item - + submit a cancellation request for a worklist item - The UPS Pull SOP Class allows SCU systems to: - + The UPS Pull SOP Class allows SCU systems to: query a worklist for matching items - take responsibility for performing a - worklist item - + take responsibility for performing a worklist item - add/modify progress/status/result details - for the worklist item - + add/modify progress/status/result details for the worklist item - finalize a controlled worklist item as - Completed or Canceled. - + finalize a controlled worklist item as Completed or Canceled. - The UPS Watch SOP Class allows SCU systems to: - + The UPS Watch SOP Class allows SCU systems to: query for worklist items of interest - subscribe/unsubscribe for event - notifications of changes to a given worklist item - + subscribe/unsubscribe for event notifications of changes to a given worklist item - subscribe/unsubscribe for event - notifications of all worklist items - + subscribe/unsubscribe for event notifications of all worklist items - get details for a given worklist item - + get details for a given worklist item - submit a cancellation request for a given - worklist item - + submit a cancellation request for a given worklist item - The UPS Event SOP Class allows SCU systems to: - + The UPS Event SOP Class allows SCU systems to: - receive event notifications of changes to a - worklist item - + receive event notifications of changes to a worklist item - The UPS Query SOP Class allows SCU systems to: - + The UPS Query SOP Class allows SCU systems to: query a worklist for matching items - The DICOM AEs that claim conformance to one or more - of these SOP Classes shall support all services listed as "M" in the corresponding,,, - - and. - + The DICOM AEs that claim conformance to one or more of these SOP Classes shall support all services listed as "M" in the corresponding , , , and .
Service Class and SOP Class UIDs - All UPS Instances shall be created with the - value of SOP Class UID set to "1.2.840.10008.5.1.4.34.6.1" (i.e., that of the UPS Push SOP Class). - + All UPS Instances shall be created with the value of SOP Class UID set to "1.2.840.10008.5.1.4.34.6.1" (i.e., that of the UPS Push SOP Class). - UPS Instances are all based on the Unified - Procedure Step IOD and are all created either internally by the SCP, or in response to an - N-CREATE issued as part of the UPS Push SOP Class. - + UPS Instances are all based on the Unified Procedure Step IOD and are all created either internally by the SCP, or in response to an N-CREATE issued as part of the UPS Push SOP Class. - Once created, UPS instances may be operated on - by DIMSE services from any of the UPS SOP Classes defined in the Unified Worklist and Procedure Step - Service Class. - - During association negotiation, the Abstract - Syntax UID shall be the implemented SOP Class as shown in the following list: - + Once created, UPS instances may be operated on by DIMSE services from any of the UPS SOP Classes defined in the Unified Worklist and Procedure Step Service Class. + During association negotiation, the Abstract Syntax UID shall be the implemented SOP Class as shown in the following list: - 1.2.840.10008.5.1.4.34.6.1 (UPS Push - SOP Class) - + 1.2.840.10008.5.1.4.34.6.1 (UPS Push SOP Class) - 1.2.840.10008.5.1.4.34.6.2 (UPS Watch - SOP Class) - + 1.2.840.10008.5.1.4.34.6.2 (UPS Watch SOP Class) - 1.2.840.10008.5.1.4.34.6.3 (UPS Pull - SOP Class) - + 1.2.840.10008.5.1.4.34.6.3 (UPS Pull SOP Class) - 1.2.840.10008.5.1.4.34.6.4 (UPS Event - SOP Class) - + 1.2.840.10008.5.1.4.34.6.4 (UPS Event SOP Class) - 1.2.840.10008.5.1.4.34.6.5 (UPS Query - SOP Class) - + 1.2.840.10008.5.1.4.34.6.5 (UPS Query SOP Class)
DIMSE Implications for UPS (Informative) - A SOP Instance may be created with one SOP - Class UID (UPS Push) and later DIMSE Services may refer to it over an association negotiated for - a different SOP Class UID. Further details on this can be found in - . - - For DIMSE-N Services, the Affected SOP - Class UID (0000,0002) or Requested SOP Class UID (0000,0003), when present, will be the UID of - the UPS Push SOP Class regardless of the negotiated Abstract Syntax UID. The SCU and SCP will - not reject DIMSE-N messages on the basis of the Affected/Requested SOP Class UID being that of - the UPS Push SOP Class, rather than one of the other four SOP Class UIDs as listed in the - Abstract Syntax UID during association negotiation. The SCU and SCP may reject the DIMSE-N - messages if the instance is not a UPS Push SOP Class Instance. - - For DIMSE-C Services (C-FIND), the Affected - SOP Class UID will always match the negotiated Abstract Syntax UID for the Presentation Context - under which the request is made. This will be UPS Watch, UPS Pull or UPS Query. All of these SOP - Classes represent the UPS Information Model described in. - - For example, in a typical "Pull Workflow" - message exchange, the C-FIND query from a "performing SCU" would use the UPS Pull SOP Class UID - for both the negotiated Abstract Syntax UID and the Affected SOP Class UID (0000,0002), however - the SOP Class UID (0008,0016) of the C-FIND responses themselves will be set to the UPS Push SOP - Class UID by the SCP. All the subsequent N-ACTION, N-SET, and N-GET messages, would then use the - UPS Pull SOP Class UID for the negotiated Abstract Syntax UID, and the UPS Push SOP Class UID - for the Affected SOP Class UID (0000,0002). - + A SOP Instance may be created with one SOP Class UID (UPS Push) and later DIMSE Services may refer to it over an association negotiated for a different SOP Class UID. Further details on this can be found in . + For DIMSE-N Services, the Affected SOP Class UID (0000,0002) or Requested SOP Class UID (0000,0003), when present, will be the UID of the UPS Push SOP Class regardless of the negotiated Abstract Syntax UID. The SCU and SCP will not reject DIMSE-N messages on the basis of the Affected/Requested SOP Class UID being that of the UPS Push SOP Class, rather than one of the other four SOP Class UIDs as listed in the Abstract Syntax UID during association negotiation. The SCU and SCP may reject the DIMSE-N messages if the instance is not a UPS Push SOP Class Instance. + For DIMSE-C Services (C-FIND), the Affected SOP Class UID will always match the negotiated Abstract Syntax UID for the Presentation Context under which the request is made. This will be UPS Watch, UPS Pull or UPS Query. All of these SOP Classes represent the UPS Information Model described in . + For example, in a typical "Pull Workflow" message exchange, the C-FIND query from a "performing SCU" would use the UPS Pull SOP Class UID for both the negotiated Abstract Syntax UID and the Affected SOP Class UID (0000,0002), however the SOP Class UID (0008,0016) of the C-FIND responses themselves will be set to the UPS Push SOP Class UID by the SCP. All the subsequent N-ACTION, N-SET, and N-GET messages, would then use the UPS Pull SOP Class UID for the negotiated Abstract Syntax UID, and the UPS Push SOP Class UID for the Affected SOP Class UID (0000,0002).
Global Instance Subscription UID - The well-known UID for - subscribing/unsubscribing to events for all UPS Instances managed by an SCP shall have the value - "1.2.840.10008.5.1.4.34.5". - + The well-known UID for subscribing/unsubscribing to events for all UPS Instances managed by an SCP shall have the value "1.2.840.10008.5.1.4.34.5".
Association Negotiation - Association establishment is the first phase of - any instance of communication between peer DICOM AEs. The Association negotiation procedure - specified in - - shall be used to negotiate the supported SOP Classes. - - See the Association Negotiation definition for - the Basic Worklist Management Service Class (). - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. The Association negotiation procedure specified in shall be used to negotiate the supported SOP Classes. + See the Association Negotiation definition for the Basic Worklist Management Service Class ().
Conformance Requirements - Implementations providing conformance to any of the - UPS SOP Classes (UPS Pull, UPS Push, UPS Watch, UPS Event and UPS Query) shall be conformant as - described in the following sections and shall include within their Conformance Statement information as - described below. - - An implementation may conform to any of the UPS SOP - Classes as an SCU or as an SCP. The Conformance Statement shall be in the format defined in. - + Implementations providing conformance to any of the UPS SOP Classes (UPS Pull, UPS Push, UPS Watch, UPS Event and UPS Query) shall be conformant as described in the following sections and shall include within their Conformance Statement information as described below. + An implementation may conform to any of the UPS SOP Classes as an SCU or as an SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation, which is conformant to any - of the UPS SOP Classes as an SCU, shall meet conformance requirements for the operations that it - invokes. - + An implementation, which is conformant to any of the UPS SOP Classes as an SCU, shall meet conformance requirements for the operations that it invokes.
Operations - The SCU Conformance Statement shall be - formatted as defined in. - - An implementation, that conforms to any of - the UPS Push, UPS Pull or UPS Watch SOP Classes as an SCU, shall specify under which conditions - it will request the modification of the value of the Procedure Step State (0074,1000) Attribute - to "IN PROGRESS", "COMPLETED", and "CANCELED". - - An implementation that conforms to the UPS - Pull, UPS Watch or UPS Query SOP Classes as an SCU shall state in its Conformance Statement - + The SCU Conformance Statement shall be formatted as defined in . + An implementation, that conforms to any of the UPS Push, UPS Pull or UPS Watch SOP Classes as an SCU, shall specify under which conditions it will request the modification of the value of the Procedure Step State (0074,1000) Attribute to "IN PROGRESS", "COMPLETED", and "CANCELED". + An implementation that conforms to the UPS Pull, UPS Watch or UPS Query SOP Classes as an SCU shall state in its Conformance Statement - Whether it requests matching on - Optional Matching Key Attributes for C-FIND. - + Whether it requests matching on Optional Matching Key Attributes for C-FIND. - Whether it requests Type 3 Return - Key Attributes. If it requests Type 3 Return Key Attributes, then it shall list these - Optional Return Key Attributes. - + Whether it requests Type 3 Return Key Attributes. If it requests Type 3 Return Key Attributes, then it shall list these Optional Return Key Attributes. - Whether or not it supports extended - negotiation of fuzzy semantic matching of person names for C-FIND. - + Whether or not it supports Extended Negotiation of fuzzy semantic matching of person names for C-FIND. - How it makes use of Specific - Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries - and interpreting responses for C-FIND. - + How it makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when encoding queries and interpreting responses for C-FIND. - What access mechanisms the SCP is - capable of using for retrieving input data and/or making output data available. (see - - for details on the different Retrieval Sequences). - + What access mechanisms the SCP is capable of using for retrieving input data and/or making output data available. (see for details on the different Retrieval Sequences).
SCP Conformance - An implementation that is conformant to any of - the UPS SOP Classes as an SCP shall meet conformance requirements for the operations that it - performs. - + An implementation that is conformant to any of the UPS SOP Classes as an SCP shall meet conformance requirements for the operations that it performs.
Operations - The SCP Conformance Statement shall be - formatted as defined in. - - The SCP Conformance Statement shall provide - information on the behavior of the SCP at the following occurrences: - + The SCP Conformance Statement shall be formatted as defined in . + The SCP Conformance Statement shall provide information on the behavior of the SCP at the following occurrences: - The creation of a new Instance of - the UPS Push SOP Class with the status "SCHEDULED". The result of that process on the - scheduling information and on the Attribute Values of the Unified Procedure Step shall - be specified. Any automatic UPS Subscription created in response to the Instance - creation shall be specified. - + The creation of a new Instance of the UPS Push SOP Class with the status "SCHEDULED". The result of that process on the scheduling information and on the Attribute Values of the Unified Procedure Step shall be specified. Any automatic UPS Subscription created in response to the Instance creation shall be specified. - The conditions for the update of - the Attribute "Procedure Step State" (0074,1000), i.e., the change to the state "IN - PROGRESS" or to "CANCELED" or to "COMPLETED". - + The conditions for the update of the Attribute "Procedure Step State" (0074,1000), i.e., the change to the state "IN PROGRESS" or to "CANCELED" or to "COMPLETED". - Which Attributes the SCP may update - after the state has been set to "IN PROGRESS" or "CANCELED" or "COMPLETED". - + Which Attributes the SCP may update after the state has been set to "IN PROGRESS" or "CANCELED" or "COMPLETED". - For how long the UPS Instance will - persist on the SCP, and how long it will be available for N-GETs once its state has been - set to "COMPLETED" or "CANCELED". - + For how long the UPS Instance will persist on the SCP, and how long it will be available for N-GETs once its state has been set to "COMPLETED" or "CANCELED". - Whether the SCP supports priority - for C-FIND. If the SCP supports priority for C-FIND, then the meaning of the different - priority levels shall be specified. - + Whether the SCP supports priority for C-FIND. If the SCP supports priority for C-FIND, then the meaning of the different priority levels shall be specified. - Whether the SCP supports - case-insensitive matching for PN VR Attributes for C-FIND. If the SCP supports - case-insensitive matching of PN VR Attributes, then the Attributes for which this - applies shall be specified. - + Whether the SCP supports case-insensitive matching for PN VR Attributes for C-FIND. If the SCP supports case-insensitive matching of PN VR Attributes, then the Attributes for which this applies shall be specified. - Whether the SCP supports extended - negotiation of fuzzy semantic matching of person names for C-FIND. If the SCP supports - extended negotiation of fuzzy semantic matching of person names, then the mechanism for - fuzzy semantic matching shall be specified. - + Whether the SCP supports Extended Negotiation of fuzzy semantic matching of person names for C-FIND. If the SCP supports Extended Negotiation of fuzzy semantic matching of person names, then the mechanism for fuzzy semantic matching shall be specified. - How the SCP makes use of Specific - Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting - C-FIND queries, performing matching and encoding responses. - + How the SCP makes use of Specific Character Set (0008,0005) and Timezone Offset From UTC (0008,0201) when interpreting C-FIND queries, performing matching and encoding responses. - What rules the SCP may use to - perform additional filtering during a C-FIND (e.g., limiting returns based on the - requesting user and the confidentiality settings of the workitems, or limiting the - return to a single item already selected on the SCP) and under what conditions those - rules are invoked. - + What rules the SCP may use to perform additional filtering during a C-FIND (e.g., limiting returns based on the requesting user and the confidentiality settings of the workitems, or limiting the return to a single item already selected on the SCP) and under what conditions those rules are invoked. - Whether the SCP might refuse - Subscription requests and/or Deletion Locks and for what reasons. - + Whether the SCP might refuse Subscription requests and/or Deletion Locks and for what reasons. - What access mechanisms the SCP is - capable of using for retrieving input data and/or making output data available. (see - - for details on the different Retrieval Sequences). - + What access mechanisms the SCP is capable of using for retrieving input data and/or making output data available. (see for details on the different Retrieval Sequences).
@@ -58861,48 +42129,20 @@ RT Machine Verification Service Classes (Normative)
Scope - The RT Machine Verification Service Classes define - an application-level class-of-service that facilitates the independent verification of geometric and - dosimetric settings on a radiation delivery system prior to delivery of a radiation treatment. The - service classes are intended for use with both conventional (e.g., photon, electron) as well as particle - therapy (e.g., proton, ion) treatments. - + The RT Machine Verification Service Classes define an application-level class-of-service that facilitates the independent verification of geometric and dosimetric settings on a radiation delivery system prior to delivery of a radiation treatment. The service classes are intended for use with both conventional (e.g., photon, electron) as well as particle therapy (e.g., proton, ion) treatments.
RT Machine Verification Model
RT Machine Verification Data Flow - In the RT Machine Verification Model, the - Service Class User (SCU) of the applicable Machine Verification Service Class is the radiation - delivery system used to administer the treatment. The Machine Parameter Verifier (MPV) acts in the - role of Service Class Provider (SCP). - - The communication states between the SCU and - SCP can be described in two levels shown in - : A) the Plan Level and B) the Beam Level. - - The first level (A in the diagram) is the Plan - Level. The SCU initializes external verification of a new plan using the N-CREATE command. The MPV - then retrieves the data necessary to perform verification through DICOM or other means. In general, - there is a close relationship between an MPV and a Treatment Management System (TMS) or Archive. If - DICOM is the protocol used to retrieve this data, this might be done using one or more C-MOVEs on - the Archive. - - The second level (B in the diagram) is the Beam - Level. The SCU uses the N-SET command request to instruct the SCP on the specified Attributes to be - verified. The SCU then requests that the verification start using an N-ACTION command. The SCP - compares the values of the specified Attributes against the values of the Attributes from the - referenced plan, and signals the status of the verification using N-EVENT-REPORT command with the - Treatment Verification Status (3008,002C) Attribute indicating the verification result. The MPV's - use of tolerance values in the verification process shall be described in a Conformance Statement. - The SCU may then optionally request the beam's verification parameters using an N-GET. - - Finally, when all beams have been delivered or - abandoned, the SCU terminates the verification session at the Plan Level using an N-DELETE. - + In the RT Machine Verification Model, the Service Class User (SCU) of the applicable Machine Verification Service Class is the radiation delivery system used to administer the treatment. The Machine Parameter Verifier (MPV) acts in the role of Service Class Provider (SCP). + The communication states between the SCU and SCP can be described in two levels shown in : A) the Plan Level and B) the Beam Level. + The first level (A in the diagram) is the Plan Level. The SCU initializes external verification of a new plan using the N-CREATE command. The MPV then retrieves the data necessary to perform verification through DICOM or other means. In general, there is a close relationship between an MPV and a Treatment Management System (TMS) or Archive. If DICOM is the protocol used to retrieve this data, this might be done using one or more C-MOVEs on the Archive. + The second level (B in the diagram) is the Beam Level. The SCU uses the N-SET command request to instruct the SCP on the specified Attributes to be verified. The SCU then requests that the verification start using an N-ACTION command. The SCP compares the values of the specified Attributes against the values of the Attributes from the referenced plan, and signals the status of the verification using N-EVENT-REPORT command with the Treatment Verification Status (3008,002C) Attribute indicating the verification result. The MPV's use of tolerance values in the verification process shall be described in a Conformance Statement. The SCU may then optionally request the beam's verification parameters using an N-GET. + Finally, when all beams have been delivered or abandoned, the SCU terminates the verification session at the Plan Level using an N-DELETE.
- RT Verification Data Flow + RT Verification Data Flow @@ -58917,24 +42157,18 @@ Machine Verification SOP Class Definitions
IOD Description - The Machine Verification IODs are abstractions - of the information needed to verify the correct setup of a treatment delivery system prior to - radiation treatment. - + The Machine Verification IODs are abstractions of the information needed to verify the correct setup of a treatment delivery system prior to radiation treatment.
DIMSE Service Group - - shows DIMSE Services applicable to the IODs. - + shows DIMSE Services applicable to the IODs.
DIMSE Service Group Applicable to Machine Verification
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -58992,38 +42226,18 @@
- The meaning of the Usage SCU/SCP is described - in. - - This Section describes the behavior of the - DIMSE Services that are specific for this IOD. The general behavior of the DIMSE services is - specified in. - + The meaning of the Usage SCU/SCP is described in . + This Section describes the behavior of the DIMSE Services that are specific for this IOD. The general behavior of the DIMSE services is specified in .
N-CREATE and N-SET - The N-CREATE is used to create an instance - of the applicable Machine Verification SOP Class. - - The N-SET is used to communicate parameters - for verification to an MPV by setting Attributes on an instance of the applicable Machine - Verification SOP Class. - - All Attributes in the table relating to the - number of a certain item (e.g., Number of Wedges, Number of Control Points) specify the number - in the N-SET command. The numbering in the Beams Verification Request is not necessarily the - same as the numbering in the referenced RT Plan. - + The N-CREATE is used to create an instance of the applicable Machine Verification SOP Class. + The N-SET is used to communicate parameters for verification to an MPV by setting Attributes on an instance of the applicable Machine Verification SOP Class. + All Attributes in the table relating to the number of a certain item (e.g., Number of Wedges, Number of Control Points) specify the number in the N-SET command. The numbering in the Beams Verification Request is not necessarily the same as the numbering in the referenced RT Plan.
Attributes - The Attribute list of the N-CREATE and - N-SET for the RT Conventional Machine Verification SOP Class is shown in. See Section 5.4 for usage - notation. - + The Attribute list of the N-CREATE and N-SET for the RT Conventional Machine Verification SOP Class is shown in . See Section 5.4 for usage notation. - + @@ -59048,26 +42259,21 @@ @@ -59914,39 +43005,30 @@ @@ -60387,10 +43412,7 @@
N-CREATE and N-SET Attribute List - RT Conventional Machine Verification SOP - Class - N-CREATE and N-SET Attribute List - RT Conventional Machine Verification SOP Class
@@ -59033,13 +42247,10 @@ Tag - N-CREATE Usage - SCU/SCP - + N-CREATE Usage SCU/SCP - N-SET Usage SCU/SCP - + N-SET Usage SCU/SCP
- RT General Machine Verification Module - + RT General Machine Verification Module
- Referenced RT Plan - Sequence - + Referenced RT Plan Sequence (300C,0002) 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted) Not allowed @@ -59075,9 +42281,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -59091,9 +42295,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -59107,18 +42309,14 @@
- Referenced Fraction - Group Number - + Referenced Fraction Group Number (300C,0022) 1C/1 - (required if plan has - more than one fraction group) - + (required if plan has more than one fraction group) Not allowed @@ -59141,17 +42339,14 @@
- Include - + Include
- Treatment Verification - Status - + Treatment Verification Status (3008,002C) @@ -59165,9 +42360,7 @@
- Failed Parameters - Sequence - + Failed Parameters Sequence (0074,1048) @@ -59181,9 +42374,7 @@
- Overridden Parameters - Sequence - + Overridden Parameters Sequence (0074,104A) @@ -59197,31 +42388,23 @@
- General Machine - Verification Sequence - + General Machine Verification Sequence (0074,1042) 2/2 - (sequence shall contain - zero items) - + (sequence shall contain zero items) 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted)
- >Specified Primary - Meterset - + >Specified Primary Meterset (3008,0032) @@ -59235,9 +42418,7 @@
- >Specified Secondary - Meterset - + >Specified Secondary Meterset (3008,0033) @@ -59251,9 +42432,7 @@
- >Specified Treatment - Time - + >Specified Treatment Time (3008,003A) @@ -59267,9 +42446,7 @@
- >Beam Limiting - Device Leaf Pairs Sequence - + >Beam Limiting Device Leaf Pairs Sequence (3008,00A0) @@ -59283,9 +42460,7 @@
- >>RT Beam - Limiting Device Type - + >>RT Beam Limiting Device Type (300A,00B8) @@ -59299,9 +42474,7 @@
- >>Number of - Leaf/Jaw Pairs - + >>Number of Leaf/Jaw Pairs (300A,00BC) @@ -59315,9 +42488,7 @@
- >Recorded Wedge - Sequence - + >Recorded Wedge Sequence (3008,00B0) @@ -59327,16 +42498,12 @@ 2C/2C - (required if MPV is - capable of verifying wedges). See. - + (required if MPV is capable of verifying wedges). See .
- >>Wedge Number - + >>Wedge Number (300A,00D2) @@ -59364,8 +42531,7 @@
- >>Wedge Angle - + >>Wedge Angle (300A,00D5) @@ -59379,9 +42545,7 @@
- >>Wedge - Orientation - + >>Wedge Orientation (300A,00D8) @@ -59395,9 +42559,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -59411,9 +42573,7 @@
- >Recorded - Compensator Sequence - + >Recorded Compensator Sequence (3008,00C0) @@ -59423,17 +42583,12 @@ 2C/2C - (required if MPV is - capable of verifying compensators). See. - + (required if MPV is capable of verifying compensators). See .
- >>Compensator - ID - + >>Compensator ID (300A,00E5) @@ -59447,9 +42602,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -59463,9 +42616,7 @@
- >>Referenced - Compensator Number - + >>Referenced Compensator Number (300C,00D0) @@ -59479,9 +42630,7 @@
- >Recorded Block - Sequence - + >Recorded Block Sequence (3008,00D0) @@ -59491,16 +42640,12 @@ 2C/2C - (required if MPV is - capable of verifying blocks). See. - + (required if MPV is capable of verifying blocks). See .
- >>Block Tray ID - + >>Block Tray ID (300A,00F5) @@ -59514,9 +42659,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -59530,9 +42673,7 @@
- >>Referenced - Block Number - + >>Referenced Block Number (300C,00E0) @@ -59546,9 +42687,7 @@
- >Treatment Machine - Name - + >Treatment Machine Name (300A,00B2) @@ -59576,8 +42715,7 @@
- >Radiation Type - + >Radiation Type (300A,00C6) @@ -59591,8 +42729,7 @@
- >Number of Wedges - + >Number of Wedges (300A,00D0) @@ -59606,9 +42743,7 @@
- >Number of - Compensators - + >Number of Compensators (300A,00E0) @@ -59622,8 +42757,7 @@
- >Number of Boli - + >Number of Boli (300A,00ED) @@ -59637,8 +42771,7 @@
- >Number of Blocks - + >Number of Blocks (300A,00F0) @@ -59652,9 +42785,7 @@
- >Applicator - Sequence - + >Applicator Sequence (300A,0107) @@ -59664,17 +42795,12 @@ 2C/2C - (required if MPV is - capable of verifying applicators). See. - + (required if MPV is capable of verifying applicators). See .
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -59688,8 +42814,7 @@
- >>Applicator ID - + >>Applicator ID (300A,0108) @@ -59703,9 +42828,7 @@
- >>Applicator - Type - + >>Applicator Type (300A,0109) @@ -59719,9 +42842,7 @@
- >Number of Control - Points - + >Number of Control Points (300A,0110) @@ -59731,15 +42852,12 @@ 1/1 - (value shall be 1) - + (value shall be 1)
- >Patient Setup - Sequence - + >Patient Setup Sequence (300A,0180) @@ -59749,16 +42867,12 @@ 3/3 - (one or more Items may - be included) - + (one or more Items may be included)
- >>Patient Setup - Number - + >>Patient Setup Number (300A,0182) @@ -59772,9 +42886,7 @@
- >>Fixation Device - Sequence - + >>Fixation Device Sequence (300A,0190) @@ -59784,18 +42896,12 @@ 2C/2C - (required if MPV is - capable of verifying fixation devices). See - . - + (required if MPV is capable of verifying fixation devices). See .
- >>>Accessory - Code - + >>>Accessory Code (300A,00F9) @@ -59809,9 +42915,7 @@
- >>>Fixation - Device Type - + >>>Fixation Device Type (300A,0192) @@ -59825,9 +42929,7 @@
- >Referenced Beam - Number - + >Referenced Beam Number (300C,0006) @@ -59841,9 +42943,7 @@
- >Referenced Bolus - Sequence - + >Referenced Bolus Sequence (300C,00B0) @@ -59853,17 +42953,12 @@ 2C/2C - (required if MPV is - capable of verifying bolus). See. - + (required if MPV is capable of verifying bolus). See .
- >>Referenced ROI - Number - + >>Referenced ROI Number (3006,0084) @@ -59877,9 +42972,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -59894,9 +42987,7 @@
- All other Attributes of the - + All other Attributes of the - RT Conventional Machine Verification Module - + RT Conventional Machine Verification Module
- Conventional Machine - Verification Sequence - + Conventional Machine Verification Sequence (0074,1044) 2/2 - (sequence shall contain - zero items) - + (sequence shall contain zero items) 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted)
- >Conventional - Control Point Verification Sequence - + >Conventional Control Point Verification Sequence (0074,104C) @@ -59956,16 +43038,12 @@ 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted)
- >>Nominal Beam - Energy - + >>Nominal Beam Energy (300A,0114) @@ -59979,8 +43057,7 @@
- >>Dose Rate Set - + >>Dose Rate Set (300A,0115) @@ -59994,9 +43071,7 @@
- >>Wedge Position - Sequence - + >>Wedge Position Sequence (300A,0116) @@ -60006,16 +43081,12 @@ 1C/1C - (required if Number of - Wedges (300A,00D0) is non-zero,one or more Items may be included) - + (required if Number of Wedges (300A,00D0) is non-zero,one or more Items may be included)
- >>>Wedge - Position - + >>>Wedge Position (300A,0118) @@ -60029,9 +43100,7 @@
- >>>Referenced - Wedge Number - + >>>Referenced Wedge Number (300C,00C0) @@ -60045,9 +43114,7 @@
- >>Beam Limiting - Device Position Sequence - + >>Beam Limiting Device Position Sequence (300A,011A) @@ -60057,17 +43124,12 @@ 1C/1C - (required if Beam - Limiting Device Leaf Pairs Sequence (3008,00A0) is sent,one or more Items - may be included) - + (required if Beam Limiting Device Leaf Pairs Sequence (3008,00A0) is sent,one or more Items may be included)
- >>>RT Beam - Limiting Device Type - + >>>RT Beam Limiting Device Type (300A,00B8) @@ -60081,9 +43143,7 @@
- >>>Leaf/Jaw - Positions - + >>>Leaf/Jaw Positions (300A,011C) @@ -60097,8 +43157,7 @@
- >>Gantry Angle - + >>Gantry Angle (300A,011E) @@ -60112,9 +43171,7 @@
- >>Gantry Rotation - Direction - + >>Gantry Rotation Direction (300A,011F) @@ -60128,9 +43185,7 @@
- >>Beam Limiting - Device Angle - + >>Beam Limiting Device Angle (300A,0120) @@ -60144,9 +43199,7 @@
- >>Beam Limiting - Device Rotation Direction - + >>Beam Limiting Device Rotation Direction (300A,0121) @@ -60160,9 +43213,7 @@
- >>Patient Support - Angle - + >>Patient Support Angle (300A,0122) @@ -60176,9 +43227,7 @@
- >>Patient Support - Rotation Direction - + >>Patient Support Rotation Direction (300A,0123) @@ -60192,9 +43241,7 @@
- >>Table Top - Eccentric Axis Distance - + >>Table Top Eccentric Axis Distance (300A,0124) @@ -60208,9 +43255,7 @@
- >>Table Top - Eccentric Angle - + >>Table Top Eccentric Angle (300A,0125) @@ -60224,9 +43269,7 @@
- >>Table Top - Eccentric Rotation Direction - + >>Table Top Eccentric Rotation Direction (300A,0126) @@ -60240,9 +43283,7 @@
- >>Table Top - Vertical Position - + >>Table Top Vertical Position (300A,0128) @@ -60256,9 +43297,7 @@
- >>Table Top - Longitudinal Position - + >>Table Top Longitudinal Position (300A,0129) @@ -60272,9 +43311,7 @@
- >>Table Top - Lateral Position - + >>Table Top Lateral Position (300A,012A) @@ -60288,9 +43325,7 @@
- >>Table Top Pitch - Angle - + >>Table Top Pitch Angle (300A,0140) @@ -60304,9 +43339,7 @@
- >>Table Top Pitch - Rotation Direction - + >>Table Top Pitch Rotation Direction (300A,0142) @@ -60320,9 +43353,7 @@
- >>Table Top Roll - Angle - + >>Table Top Roll Angle (300A,0144) @@ -60336,9 +43367,7 @@
- >>Table Top Roll - Rotation Direction - + >>Table Top Roll Rotation Direction (300A,0146) @@ -60352,9 +43381,7 @@
- >>Referenced - Control Point Index - + >>Referenced Control Point Index (300C,00F0) @@ -60369,9 +43396,7 @@
- All other Attributes of the - + All other Attributes of the
- The Attribute list of the N-CREATE and - N-SET for the RT Ion Machine Verification SOP Class is shown in. - + The Attribute list of the N-CREATE and N-SET for the RT Ion Machine Verification SOP Class is shown in . @@ -60402,13 +43424,10 @@ Tag @@ -60417,26 +43436,21 @@ @@ -61293,31 +44190,23 @@ @@ -62291,9 +45033,7 @@ @@ -62440,22 +45164,13 @@
N-CREATE and N-SET Attribute List - RT Ion Machine Verification SOP Class
- N-CREATE Usage - SCU/SCP - + N-CREATE Usage SCU/SCP - N-SET Usage SCU/SCP - + N-SET Usage SCU/SCP
- RT General Machine Verification Module - + RT General Machine Verification Module
- Referenced RT Plan - Sequence - + Referenced RT Plan Sequence (300C,0002) 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted) Not allowed @@ -60444,9 +43458,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -60460,9 +43472,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -60476,18 +43486,14 @@
- Referenced Fraction - Group Number - + Referenced Fraction Group Number (300C,0022) 1C/1 - (required if plan has - more than one fraction group) - + (required if plan has more than one fraction group) Not allowed @@ -60510,17 +43516,14 @@
- Include - + Include
- Treatment Verification - Status - + Treatment Verification Status (3008,002C) @@ -60534,9 +43537,7 @@
- Failed Parameters - Sequence - + Failed Parameters Sequence (0074,1048) @@ -60550,9 +43551,7 @@
- Overridden Parameters - Sequence - + Overridden Parameters Sequence (0074,104A) @@ -60566,31 +43565,23 @@
- General Machine - Verification Sequence - + General Machine Verification Sequence (0074,1042) 2/2 - (sequence shall contain - zero items) - + (sequence shall contain zero items) 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted)
- >Specified Primary - Meterset - + >Specified Primary Meterset (3008,0032) @@ -60604,9 +43595,7 @@
- >Specified Secondary - Meterset - + >Specified Secondary Meterset (3008,0033) @@ -60620,9 +43609,7 @@
- >Specified Treatment - Time - + >Specified Treatment Time (3008,003A) @@ -60636,9 +43623,7 @@
- >Beam Limiting - Device Leaf Pairs Sequence - + >Beam Limiting Device Leaf Pairs Sequence (3008,00A0) @@ -60648,16 +43633,12 @@ 3/3 - See. - + See .
- >>RT Beam - Limiting Device Type - + >>RT Beam Limiting Device Type (300A,00B8) @@ -60671,9 +43652,7 @@
- >>Number of - Leaf/Jaw Pairs - + >>Number of Leaf/Jaw Pairs (300A,00BC) @@ -60687,9 +43666,7 @@
- >Recorded Wedge - Sequence - + >Recorded Wedge Sequence (3008,00B0) @@ -60699,16 +43676,12 @@ 2C/2C - (required if MPV is - capable of verifying wedges). See. - + (required if MPV is capable of verifying wedges). See .
- >>Wedge Number - + >>Wedge Number (300A,00D2) @@ -60736,8 +43709,7 @@
- >>Wedge Angle - + >>Wedge Angle (300A,00D5) @@ -60751,9 +43723,7 @@
- >>Wedge - Orientation - + >>Wedge Orientation (300A,00D8) @@ -60767,9 +43737,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -60783,9 +43751,7 @@
- >Recorded - Compensator Sequence - + >Recorded Compensator Sequence (3008,00C0) @@ -60795,17 +43761,12 @@ 2C/2C - (required if MPV is - capable of verifying compensators). See. - + (required if MPV is capable of verifying compensators). See .
- >>Compensator - ID - + >>Compensator ID (300A,00E5) @@ -60819,9 +43780,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -60835,9 +43794,7 @@
- >>Referenced - Compensator Number - + >>Referenced Compensator Number (300C,00D0) @@ -60851,9 +43808,7 @@
- >Recorded Block - Sequence - + >Recorded Block Sequence (3008,00D0) @@ -60863,16 +43818,12 @@ 2C/2C - (required if MPV is - capable of verifying blocks). See. - + (required if MPV is capable of verifying blocks). See .
- >>Block Tray ID - + >>Block Tray ID (300A,00F5) @@ -60886,9 +43837,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -60902,9 +43851,7 @@
- >>Referenced - Block Number - + >>Referenced Block Number (300C,00E0) @@ -60918,9 +43865,7 @@
- >Treatment Machine - Name - + >Treatment Machine Name (300A,00B2) @@ -60948,8 +43893,7 @@
- >Radiation Type - + >Radiation Type (300A,00C6) @@ -60963,8 +43907,7 @@
- >Number of Wedges - + >Number of Wedges (300A,00D0) @@ -60978,9 +43921,7 @@
- >Number of - Compensators - + >Number of Compensators (300A,00E0) @@ -60994,8 +43935,7 @@
- >Number of Boli - + >Number of Boli (300A,00ED) @@ -61009,8 +43949,7 @@
- >Number of Blocks - + >Number of Blocks (300A,00F0) @@ -61024,9 +43963,7 @@
- >Applicator - Sequence - + >Applicator Sequence (300A,0107) @@ -61036,17 +43973,12 @@ 2C/2C - (required if MPV is - capable of verifying applicators). See. - + (required if MPV is capable of verifying applicators). See .
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -61060,8 +43992,7 @@
- >>Applicator ID - + >>Applicator ID (300A,0108) @@ -61075,9 +44006,7 @@
- >>Applicator - Type - + >>Applicator Type (300A,0109) @@ -61091,9 +44020,7 @@
- >Number of Control - Points - + >Number of Control Points (300A,0110) @@ -61103,15 +44030,12 @@ 1/1 - (value shall be 1) - + (value shall be 1)
- >Patient Setup - Sequence - + >Patient Setup Sequence (300A,0180) @@ -61121,16 +44045,12 @@ 3/3 - See. - + See .
- >>Patient Setup - Number - + >>Patient Setup Number (300A,0182) @@ -61144,9 +44064,7 @@
- >>Fixation Device - Sequence - + >>Fixation Device Sequence (300A,0190) @@ -61156,18 +44074,12 @@ 2C/2C - (required if MPV is - capable of verifying fixation devices). See - . - + (required if MPV is capable of verifying fixation devices). See .
- >>>Accessory - Code - + >>>Accessory Code (300A,00F9) @@ -61181,9 +44093,7 @@
- >>>Fixation - Device Type - + >>>Fixation Device Type (300A,0192) @@ -61197,9 +44107,7 @@
- >Referenced Beam - Number - + >Referenced Beam Number (300C,0006) @@ -61213,9 +44121,7 @@
- >Referenced Bolus - Sequence - + >Referenced Bolus Sequence (300C,00B0) @@ -61225,17 +44131,12 @@ 2C/2C - (required if MPV is - capable of verifying bolus). See. - + (required if MPV is capable of verifying bolus). See .
- >>Referenced ROI - Number - + >>Referenced ROI Number (3006,0084) @@ -61249,9 +44150,7 @@
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -61266,9 +44165,7 @@
- All other Attributes of the - + All other Attributes of the
- Ion Machine - Verification Sequence - + Ion Machine Verification Sequence (0074,1046) 2/2 - (sequence shall contain - zero items) - + (sequence shall contain zero items) 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted)
- >Ion Control Point - Verification Sequence - + >Ion Control Point Verification Sequence (0074,104E) @@ -61327,16 +44216,12 @@ 1/1 - (only a single Item - shall be permitted) - + (only a single Item shall be permitted)
- >>Meterset Rate - Set - + >>Meterset Rate Set (3008,0045) @@ -61350,9 +44235,7 @@
- >>Nominal Beam - Energy - + >>Nominal Beam Energy (300A,0114) @@ -61366,9 +44249,7 @@
- >>Beam Limiting - Device Position Sequence - + >>Beam Limiting Device Position Sequence (300A,011A) @@ -61378,17 +44259,12 @@ 1C/1C - (required if Beam - Limiting Device Leaf Pairs Sequence (3008,00A0) is sent,one or more Items - may be included) - + (required if Beam Limiting Device Leaf Pairs Sequence (3008,00A0) is sent,one or more Items may be included)
- >>>RT Beam - Limiting Device Type - + >>>RT Beam Limiting Device Type (300A,00B8) @@ -61402,9 +44278,7 @@
- >>>Leaf/Jaw - Positions - + >>>Leaf/Jaw Positions (300A,011C) @@ -61418,8 +44292,7 @@
- >>Gantry Angle - + >>Gantry Angle (300A,011E) @@ -61433,9 +44306,7 @@
- >>Gantry Rotation - Direction - + >>Gantry Rotation Direction (300A,011F) @@ -61449,9 +44320,7 @@
- >>Beam Limiting - Device Angle - + >>Beam Limiting Device Angle (300A,0120) @@ -61465,9 +44334,7 @@
- >>Beam Limiting - Device Rotation Direction - + >>Beam Limiting Device Rotation Direction (300A,0121) @@ -61481,9 +44348,7 @@
- >>Patient Support - Angle - + >>Patient Support Angle (300A,0122) @@ -61497,9 +44362,7 @@
- >>Patient Support - Rotation Direction - + >>Patient Support Rotation Direction (300A,0123) @@ -61513,9 +44376,7 @@
- >>Table Top - Vertical Position - + >>Table Top Vertical Position (300A,0128) @@ -61529,9 +44390,7 @@
- >>Table Top - Longitudinal Position - + >>Table Top Longitudinal Position (300A,0129) @@ -61545,9 +44404,7 @@
- >>Table Top - Lateral Position - + >>Table Top Lateral Position (300A,012A) @@ -61561,9 +44418,7 @@
- >>Table Top Pitch - Angle - + >>Table Top Pitch Angle (300A,0140) @@ -61577,9 +44432,7 @@
- >>Table Top Pitch - Rotation Direction - + >>Table Top Pitch Rotation Direction (300A,0142) @@ -61593,9 +44446,7 @@
- >>Table Top Roll - Angle - + >>Table Top Roll Angle (300A,0144) @@ -61609,9 +44460,7 @@
- >>Table Top Roll - Rotation Direction - + >>Table Top Roll Rotation Direction (300A,0146) @@ -61625,9 +44474,7 @@
- >>Head Fixation - Angle - + >>Head Fixation Angle (300A,0148) @@ -61641,9 +44488,7 @@
- >>Gantry Pitch - Angle - + >>Gantry Pitch Angle (300A,014A) @@ -61657,9 +44502,7 @@
- >>Gantry Pitch - Rotation Direction - + >>Gantry Pitch Rotation Direction (300A,014C) @@ -61673,9 +44516,7 @@
- >>Snout - Position - + >>Snout Position (300A,030D) @@ -61689,9 +44530,7 @@
- >>Range Shifter - Settings Sequence - + >>Range Shifter Settings Sequence (300A,0360) @@ -61701,16 +44540,12 @@ 1C/1C - (required if Number of - Range Shifters (300A,0312) is non-zero,one or more Items may be included) - + (required if Number of Range Shifters (300A,0312) is non-zero,one or more Items may be included)
- >>>Range - Shifter Setting - + >>>Range Shifter Setting (300A,0362) @@ -61724,9 +44559,7 @@
- >>>Referenced - Range Shifter Number - + >>>Referenced Range Shifter Number (300C,0100) @@ -61740,9 +44573,7 @@
- >>Lateral - Spreading Device Settings Sequence - + >>Lateral Spreading Device Settings Sequence (300A,0370) @@ -61752,17 +44583,12 @@ 1C/1C - (required if Number of - Lateral Spreading Devices (300A,0330) is non-zero,one or more Items may be - included) - + (required if Number of Lateral Spreading Devices (300A,0330) is non-zero,one or more Items may be included)
- >>>Lateral - Spreading Device Setting - + >>>Lateral Spreading Device Setting (300A,0372) @@ -61776,9 +44602,7 @@
- >>>Referenced - Lateral Spreading Device Number - + >>>Referenced Lateral Spreading Device Number (300C,0102) @@ -61792,9 +44616,7 @@
- >>Range Modulator - Settings Sequence - + >>Range Modulator Settings Sequence (300A,0380) @@ -61804,16 +44626,12 @@ 1C/1C - (required if Number of - Range Modulators (300A,0340) is non-zero,one or more Items may be included) - + (required if Number of Range Modulators (300A,0340) is non-zero,one or more Items may be included)
- >>>Range - Modulator Gating Start Value - + >>>Range Modulator Gating Start Value (300A,0382) @@ -61827,9 +44645,7 @@
- >>>Range - Modulator Gating Stop Value - + >>>Range Modulator Gating Stop Value (300A,0384) @@ -61843,9 +44659,7 @@
- >>>Referenced - Range Modulator Number - + >>>Referenced Range Modulator Number (300C,0104) @@ -61859,9 +44673,7 @@
- >>Ion Wedge - Position Sequence - + >>Ion Wedge Position Sequence (300A,03AC) @@ -61871,16 +44683,12 @@ 1C/1C - (required if Number of - Wedges (300A,00D0) is non-zero,one or more Items may be included) - + (required if Number of Wedges (300A,00D0) is non-zero,one or more Items may be included)
- >>>Wedge Thin - Edge Position - + >>>Wedge Thin Edge Position (300A,00DB) @@ -61890,17 +44698,12 @@ 1C/1C - (required if Wedge Type - (300A,00D3) of the wedge referenced by Referenced Wedge Number (300C,00C0) - is PARTIAL_STANDARD or PARTIAL_MOTORIZ) - + (required if Wedge Type (300A,00D3) of the wedge referenced by Referenced Wedge Number (300C,00C0) is PARTIAL_STANDARD or PARTIAL_MOTORIZ)
- >>>Wedge - Position - + >>>Wedge Position (300A,0118) @@ -61914,9 +44717,7 @@
- >>Referenced - Control Point Index - + >>Referenced Control Point Index (300C,00F0) @@ -61930,9 +44731,7 @@
- >Recorded Snout - Sequence - + >Recorded Snout Sequence (3008,00F0) @@ -61942,17 +44741,12 @@ 1C/1C - (required if Snout - Sequence is included in the RT Ion Plan referenced within the Referenced RT - Plan Sequence (300C,0002); only a single Item is permitted in this sequence) - + (required if Snout Sequence is included in the RT Ion Plan referenced within the Referenced RT Plan Sequence (300C,0002); only a single Item is permitted in this sequence)
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -61980,9 +44774,7 @@
- >Recorded Range - Shifter Sequence - + >Recorded Range Shifter Sequence (3008,00F2) @@ -61992,17 +44784,12 @@ 2C/2C - (required if MPV is - capable of verifying range shifters). See. - + (required if MPV is capable of verifying range shifters). See .
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -62016,9 +44803,7 @@
- >>Range Shifter - ID - + >>Range Shifter ID (300A,0318) @@ -62032,9 +44817,7 @@
- >>Referenced - Range Shifter Number - + >>Referenced Range Shifter Number (300C,0100) @@ -62048,9 +44831,7 @@
- >Recorded Lateral - Spreading Device Sequence - + >Recorded Lateral Spreading Device Sequence (3008,00F4) @@ -62060,17 +44841,12 @@ 2C/2C - (required if MPV is - capable of verifying lateral spreading devices). See. - + (required if MPV is capable of verifying lateral spreading devices). See .
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -62084,9 +44860,7 @@
- >>Lateral - Spreading Device ID - + >>Lateral Spreading Device ID (300A,0336) @@ -62100,9 +44874,7 @@
- >>Referenced - Lateral Spreading Device Number - + >>Referenced Lateral Spreading Device Number (300C,0102) @@ -62116,9 +44888,7 @@
- >Recorded Range - Modulator Sequence - + >Recorded Range Modulator Sequence (3008,00F6) @@ -62128,18 +44898,12 @@ 2C/2C - (required if MPV is - capable of verifying range modulators). See - . - + (required if MPV is capable of verifying range modulators). See .
- >>Accessory - Code - + >>Accessory Code (300A,00F9) @@ -62153,9 +44917,7 @@
- >>Range Modulator - ID - + >>Range Modulator ID (300A,0346) @@ -62169,9 +44931,7 @@
- >>Range Modulator - Type - + >>Range Modulator Type (300A,0348) @@ -62185,9 +44945,7 @@
- >>Beam Current - Modulation ID - + >>Beam Current Modulation ID (300A,034C) @@ -62197,16 +44955,12 @@ 1C/1C - (required if Range - Modulator Type (300A,0348) is WHL_MODWEIGHTS) - + (required if Range Modulator Type (300A,0348) is WHL_MODWEIGHTS)
- >>Referenced - Range Modulator Number - + >>Referenced Range Modulator Number (300C,0104) @@ -62220,9 +44974,7 @@
- >Radiation Mass - Number - + >Radiation Mass Number (300A,0302) @@ -62232,16 +44984,12 @@ 1C/1C - (required if Radiation - Type (300A,00C6) is ION) - + (required if Radiation Type (300A,00C6) is ION)
- >Radiation Atomic - Number - + >Radiation Atomic Number (300A,0304) @@ -62251,16 +44999,12 @@ 1C/1C - (required if Radiation - Type (300A,00C6) is ION) - + (required if Radiation Type (300A,00C6) is ION)
- >Radiation Charge - State - + >Radiation Charge State (300A,0306) @@ -62270,9 +45014,7 @@ 1C/1C - (required if Radiation - Type (300A,00C6) is ION) - + (required if Radiation Type (300A,00C6) is ION)
- >Number of Range - Shifters - + >Number of Range Shifters (300A,0312) @@ -62307,9 +45047,7 @@
- >Number of Lateral - Spreading Devices - + >Number of Lateral Spreading Devices (300A,0330) @@ -62323,9 +45061,7 @@
- >Number of Range - Modulators - + >Number of Range Modulators (300A,0340) @@ -62339,9 +45075,7 @@
- >Patient Support - Type - + >Patient Support Type (300A,0350) @@ -62355,9 +45089,7 @@
- >Patient Support - ID - + >Patient Support ID (300A,0352) @@ -62371,9 +45103,7 @@
- >Patient Support - Accessory Code - + >Patient Support Accessory Code (300A,0354) @@ -62387,9 +45117,7 @@
- >Fixation Light - Azimuthal Angle - + >Fixation Light Azimuthal Angle (300A,0356) @@ -62403,9 +45131,7 @@
- >Fixation Light - Polar Angle - + >Fixation Light Polar Angle (300A,0358) @@ -62420,9 +45146,7 @@
- All other Attributes of the - + All other Attributes of the
Beam Modifiers - If the MPV is not capable of - performing the type of verification required by the Attribute, then the Attribute shall - not be present. If the MPV is capable of performing the type of verification required by - the Attribute, then the Attribute will be zero length if there are no such modifiers, - and valued with one or more items if there are one or more such modifiers. - + If the MPV is not capable of performing the type of verification required by the Attribute, then the Attribute shall not be present. If the MPV is capable of performing the type of verification required by the Attribute, then the Attribute will be zero length if there are no such modifiers, and valued with one or more items if there are one or more such modifiers.
Status - - defines the status code values that might be returned in a N-CREATE response. General status - code values and fields related to status code values are defined for N-CREATE DIMSE Service - in. - + defines the status code values that might be returned in a N-CREATE response. General status code values and fields related to status code values are defined for N-CREATE DIMSE Service in . @@ -62477,9 +45192,7 @@ Success
RT Ion Machine Verification SOP Class N-CREATE Status Values
- Machine Verification - successfully created - + Machine Verification successfully created 0000 @@ -62490,9 +45203,7 @@ Failure - Failed: No such object - instance - Referenced RT Plan not found - + Failed: No such object instance - Referenced RT Plan not found C227 @@ -62500,9 +45211,7 @@
- Failed: The Referenced - Fraction Group Number does not exist in the referenced plan - + Failed: The Referenced Fraction Group Number does not exist in the referenced plan C221 @@ -62510,9 +45219,7 @@
- Failed: No beams exist - within the referenced fraction group - + Failed: No beams exist within the referenced fraction group C222 @@ -62520,9 +45227,7 @@
- Failed: SCU already - verifying and cannot currently process this request. - + Failed: SCU already verifying and cannot currently process this request. C223 @@ -62530,9 +45235,7 @@
- The status values for N-SET that are - specific for these SOP Classes are defined as follows: - + The status values for N-SET that are specific for these SOP Classes are defined as follows: @@ -62554,9 +45257,7 @@ Success
RT Ion Machine Verification SOP Class N-SET Status Values
- Machine Verification - successfully updated - + Machine Verification successfully updated 0000 @@ -62567,9 +45268,7 @@ Failure - Failed: Referenced Beam - Number not found within the referenced Fraction Group - + Failed: Referenced Beam Number not found within the referenced Fraction Group C224 @@ -62577,9 +45276,7 @@
- Failed: Referenced - device or accessory not supported - + Failed: Referenced device or accessory not supported C225 @@ -62587,9 +45284,7 @@
- Failed: Referenced - device or accessory not found within the referenced beam - + Failed: Referenced device or accessory not found within the referenced beam C226 @@ -62602,63 +45297,25 @@ Behavior
N-CREATE - The SCU uses N-CREATE to request - the SCP to create an applicable Machine Verification SOP Instance. The SCP shall create - the SOP Instance and shall initialize Attributes of the SOP Class. - - The General Machine Verification - Sequence, Conventional Machine Verification Sequence, and Ion Machine Verification - Sequence are created with an empty value, and specification of the contained Attributes - is deferred until the N-SET operation. - - The SCP shall return the status - code of the requested SOP Instance creation. The meaning of success, warning and failure - status codes is defined in. - + The SCU uses N-CREATE to request the SCP to create an applicable Machine Verification SOP Instance. The SCP shall create the SOP Instance and shall initialize Attributes of the SOP Class. + The General Machine Verification Sequence, Conventional Machine Verification Sequence, and Ion Machine Verification Sequence are created with an empty value, and specification of the contained Attributes is deferred until the N-SET operation. + The SCP shall return the status code of the requested SOP Instance creation. The meaning of success, warning and failure status codes is defined in .
N-SET - The SCU uses the N-SET to request - the SCP to update an applicable Machine Verification instance. The SCU shall specify the - SOP Instance to be updated and shall specify the list of Attributes for which the - Attribute Values are to be set. The Attributes in the Conventional/Ion Control Point - Verification Sequence represent the Treatment Delivery System's actual geometric values - at the time the N-SET request is issued and therefore, the Conventional/Ion Control - Point Verification Sequence shall always contain one sequence item. The Referenced - Control Point Index shall be zero for NORMAL treatments, and may be greater than zero - for CONTINUATION treatments. - - Within an Attribute sequence such - as the General Machine Verification Sequence, Conventional Machine Verification - Sequence, and Ion Machine Verification Sequence, values for all required Attributes must - be supplied with each N-SET, or else the missing Attributes will have any previously set - values removed from the SOP Instance. Existing parameters may be cleared by sending an - empty sequence or Attribute. The MPV's Conformance Statement shall specify the set of - Attributes that it requires for verification. - - The SCU shall set the new values - for the specified Attributes of the specified SOP Instance. The SCP shall then compare - the values of Attributes of the specified SOP Instance to the values of the same - Attributes found in the RT Plan referenced in N-CREATE. Values shall be compared using - the tolerance values also found in the referenced RT Plan. The result of this comparison - shall be available for use when the SCU requests the Treatment Verification Status using - an N-GET. - + The SCU uses the N-SET to request the SCP to update an applicable Machine Verification instance. The SCU shall specify the SOP Instance to be updated and shall specify the list of Attributes for which the Attribute Values are to be set. The Attributes in the Conventional/Ion Control Point Verification Sequence represent the Treatment Delivery System's actual geometric values at the time the N-SET request is issued and therefore, the Conventional/Ion Control Point Verification Sequence shall always contain one sequence item. The Referenced Control Point Index shall be zero for NORMAL treatments, and may be greater than zero for CONTINUATION treatments. + Within an Attribute sequence such as the General Machine Verification Sequence, Conventional Machine Verification Sequence, and Ion Machine Verification Sequence, values for all required Attributes must be supplied with each N-SET, or else the missing Attributes will have any previously set values removed from the SOP Instance. Existing parameters may be cleared by sending an empty sequence or Attribute. The MPV's Conformance Statement shall specify the set of Attributes that it requires for verification. + The SCU shall set the new values for the specified Attributes of the specified SOP Instance. The SCP shall then compare the values of Attributes of the specified SOP Instance to the values of the same Attributes found in the RT Plan referenced in N-CREATE. Values shall be compared using the tolerance values also found in the referenced RT Plan. The result of this comparison shall be available for use when the SCU requests the Treatment Verification Status using an N-GET.
N-GET - The N-GET is used to get the verification - status and results of the applicable Machine Verification SOP Class. - + The N-GET is used to get the verification status and results of the applicable Machine Verification SOP Class.
Parameters Selector Attribute Macro - - describes N-GET support requirements for the Selector Attribute Macro. See Section 5.4 for - requirements type code meaning. - + describes N-GET support requirements for the Selector Attribute Macro. See Section 5.4 for requirements type code meaning. @@ -62670,17 +45327,14 @@ Tag
Verification Parameters Selector Attribute Macro
- Req. Type N-GET - (SCU/SCP) - + Req. Type N-GET (SCU/SCP)
- Selector Attribute - + Selector Attribute (0072,0026) @@ -62691,8 +45345,7 @@
- Selector Value Number - + Selector Value Number (0072,0028) @@ -62703,9 +45356,7 @@
- Selector Sequence - Pointer - + Selector Sequence Pointer (0072,0052) @@ -62716,9 +45367,7 @@
- Selector Sequence - Pointer Private Creator - + Selector Sequence Pointer Private Creator (0072,0054) @@ -62729,9 +45378,7 @@
- Selector Sequence - Pointer Items - + Selector Sequence Pointer Items (0074,1057) @@ -62742,9 +45389,7 @@
- Selector Attribute - Private Creator - + Selector Attribute Private Creator (0072,0056) @@ -62758,15 +45403,9 @@
Attributes - The Attribute list of the N-GET for the - RT Conventional Machine Verification SOP Class and RT Ion Machine Verification SOP Class is - shown in. See Section 5.4 for - usage notation. - + The Attribute list of the N-GET for the RT Conventional Machine Verification SOP Class and RT Ion Machine Verification SOP Class is shown in . See Section 5.4 for usage notation. - +
N-GET Attribute List- RT Conventional Machine Verification SOP Class and RT Ion - Machine Verification SOP Class - N-GET Attribute List- RT Conventional Machine Verification SOP Class and RT Ion Machine Verification SOP Class
@@ -62783,9 +45422,7 @@
- Referenced RT Plan - Sequence - + Referenced RT Plan Sequence (300C,0002) @@ -62796,9 +45433,7 @@
- >Referenced SOP - Class UID - + >Referenced SOP Class UID (0008,1150) @@ -62809,9 +45444,7 @@
- >Referenced SOP - Instance UID - + >Referenced SOP Instance UID (0008,1155) @@ -62822,9 +45455,7 @@
- Referenced Fraction - Group Number - + Referenced Fraction Group Number (300C,0022) @@ -62847,17 +45478,14 @@
- Include - + Include
- Treatment Verification - Status - + Treatment Verification Status (3008,002C) @@ -62868,60 +45496,47 @@
- Failed Parameters - Sequence - + Failed Parameters Sequence (0074,1048) -/2 - (zero or more items - shall be included in this Sequence) - + (zero or more items shall be included in this Sequence)
- >Include - + >Include
- Overridden Parameters - Sequence - + Overridden Parameters Sequence (0074,104A) -/2 - (zero or more items - shall be included in this Sequence) - + (zero or more items shall be included in this Sequence)
- >Include - + >Include
- >Operators' Name - + >Operators' Name (0008,1070) @@ -62932,8 +45547,7 @@
- >Override Reason - + >Override Reason (3008,0066) @@ -62961,15 +45575,9 @@
Status - - defines the status code values that might be returned in a N-GET response. General status - code values and fields related to status code values are defined for N-GET DIMSE Service in - . - + defines the status code values that might be returned in a N-GET response. General status code values and fields related to status code values are defined for N-GET DIMSE Service in . - +
RT Conventional Machine and RT Ion Machine Verification SOP Class N-GET Status - Values - RT Conventional Machine and RT Ion Machine Verification SOP Class N-GET Status Values
@@ -62989,10 +45597,7 @@ Success - Treatment Verification - Status of the applicable Machine Verification instance successfully - returned. - + Treatment Verification Status of the applicable Machine Verification instance successfully returned. 0000 @@ -63003,9 +45608,7 @@ Failure - Failed: Applicable - Machine Verification instance not found - + Failed: Applicable Machine Verification instance not found C112 @@ -63016,58 +45619,24 @@
Behavior - The SCU uses N-GET to retrieve from the - SCP the verification status and results of the applicable Machine Verification SOP Instance. - - The SCP shall return the Treatment - Verification Status (3008,002C) Attribute as well as the status code of the requested SOP - Instance update. Treatment Verification Status shall have one of the following values: - + The SCU uses N-GET to retrieve from the SCP the verification status and results of the applicable Machine Verification SOP Instance. + The SCP shall return the Treatment Verification Status (3008,002C) Attribute as well as the status code of the requested SOP Instance update. Treatment Verification Status shall have one of the following values: VERIFIED = treatment verified - VERIFIED_OVR = treatment verified with - at least one out-of-range value overridden - - NOT_VERIFIED = verification of - treatment was not successful - - The VERIFIED state indicates that all - required parameters have been checked and no out-of-range values have been detected. The - VERIFIED_OVR state indicates that the treatment failed to verify due to one or more - out-of-range values that were then overridden. NOT_VERIFIED indicates that one of more of - the out-of-range values has not yet been overridden and the treatment cannot go ahead. This - could be because at least one out-of-range value was detected, or one or more values - required for verification were not supplied. The site- and vendor-specific configuration of - the MPV determines the Attributes and ranges required for successful verification. - - If the Treatment Verification Status is - VERIFIED_OVR, one or more parameter occurrences shall be returned in Overridden Parameters - Sequence (0074,104A), otherwise the sequence shall be empty. - - If the Treatment Verification Status is - NOT_VERIFIED, one or more parameter occurrences shall be returned in Failed Parameters - Sequence (0074,1048), otherwise the sequence shall be empty. - - See - - for specification of how the Attribute tags and position within a sequence are encoded. - - The SCP shall return the status code of - the requested action. The meanings of success, warning and failure status codes are defined - in. - + VERIFIED_OVR = treatment verified with at least one out-of-range value overridden + NOT_VERIFIED = verification of treatment was not successful + The VERIFIED state indicates that all required parameters have been checked and no out-of-range values have been detected. The VERIFIED_OVR state indicates that the treatment failed to verify due to one or more out-of-range values that were then overridden. NOT_VERIFIED indicates that one of more of the out-of-range values has not yet been overridden and the treatment cannot go ahead. This could be because at least one out-of-range value was detected, or one or more values required for verification were not supplied. The site- and vendor-specific configuration of the MPV determines the Attributes and ranges required for successful verification. + If the Treatment Verification Status is VERIFIED_OVR, one or more parameter occurrences shall be returned in Overridden Parameters Sequence (0074,104A), otherwise the sequence shall be empty. + If the Treatment Verification Status is NOT_VERIFIED, one or more parameter occurrences shall be returned in Failed Parameters Sequence (0074,1048), otherwise the sequence shall be empty. + See for specification of how the Attribute tags and position within a sequence are encoded. + The SCP shall return the status code of the requested action. The meanings of success, warning and failure status codes are defined in .
N-ACTION - The N-ACTION is used to initiate parameter - verification of an instance of the applicable Machine Verification SOP Class. - + The N-ACTION is used to initiate parameter verification of an instance of the applicable Machine Verification SOP Class.
Attributes - The action types of the N-ACTION are - defined as shown in. - + The action types of the N-ACTION are defined as shown in . @@ -63092,9 +45661,7 @@
Action Event Information
- Request Beam - Verification - + Request Beam Verification 1 @@ -63115,15 +45682,9 @@
Status - - defines the status code values that might be returned in a N-ACTION response. General status - code values and fields related to status code values are defined for N-ACTION DIMSE Service - in. - + defines the status code values that might be returned in a N-ACTION response. General status code values and fields related to status code values are defined for N-ACTION DIMSE Service in . - +
RT Conventional Machine and RT Ion Machine Verification SOP Class N-ACTION Status - Values - RT Conventional Machine and RT Ion Machine Verification SOP Class N-ACTION Status Values
@@ -63143,10 +45704,7 @@ Success - Machine Parameter - Verification of the applicable Machine Verification instance successfully - initiated. - + Machine Parameter Verification of the applicable Machine Verification instance successfully initiated. 0000 @@ -63157,9 +45715,7 @@ Failure - Failed: Machine - Verification requested instance not found. - + Failed: Machine Verification requested instance not found. C112 @@ -63170,63 +45726,34 @@
Behavior - The SCU uses N-ACTION to instruct the - SCP to initiate machine parameter verification of the applicable Machine Verification SOP - Instance. - + The SCU uses N-ACTION to instruct the SCP to initiate machine parameter verification of the applicable Machine Verification SOP Instance.
N-DELETE - The N-DELETE is used to delete an instance - of the applicable Machine Verification SOP Class. - + The N-DELETE is used to delete an instance of the applicable Machine Verification SOP Class.
Attributes - There are no specific Attributes. - + There are no specific Attributes.
Status - There are no specific status codes. See - - for response status codes. - + There are no specific status codes. See for response status codes.
Behavior - The SCU uses the N-DELETE to request - the SCP to delete an applicable Machine Verification SOP Instance. The SCU shall specify in - the N-DELETE request primitive the SOP Instance UID of the applicable Machine Verification - instance. - - The SCP shall delete the specified SOP - Instance, such that subsequent operations of the same SOP Instance will fail. - - The SCP shall return the status code of - the requested SOP Instance deletion. The meanings of success, warning, and failure status - classes are defined in. - - If an N-DELETE is not issued, the SOP - Class instance may be deleted on the SCP by a manual or automatic operation. This behavior - is beyond the scope of the Standard. - + The SCU uses the N-DELETE to request the SCP to delete an applicable Machine Verification SOP Instance. The SCU shall specify in the N-DELETE request primitive the SOP Instance UID of the applicable Machine Verification instance. + The SCP shall delete the specified SOP Instance, such that subsequent operations of the same SOP Instance will fail. + The SCP shall return the status code of the requested SOP Instance deletion. The meanings of success, warning, and failure status classes are defined in . + If an N-DELETE is not issued, the SOP Class instance may be deleted on the SCP by a manual or automatic operation. This behavior is beyond the scope of the Standard.
N-EVENT-REPORT - The N-EVENT-REPORT is used by the MPV to - notify the TDS of the status of the verification task (successful or otherwise), or to notify - the TDS that a verification is pending (in progress). The encoding of Notification Event - Information is defined in. - + The N-EVENT-REPORT is used by the MPV to notify the TDS of the status of the verification task (successful or otherwise), or to notify the TDS that a verification is pending (in progress). The encoding of Notification Event Information is defined in .
Attributes - The arguments of the N-EVENT-REPORT are - defined as shown in. - + The arguments of the N-EVENT-REPORT are defined as shown in . @@ -63274,9 +45801,7 @@ 2
Notification Event Information
- Treatment Verification - Status - + Treatment Verification Status (3008,002C) @@ -63290,31 +45815,13 @@
Status - There are no specific status codes. See - - for response status codes. - + There are no specific status codes. See for response status codes.
Behavior - The SCP uses the N-EVENT-REPORT to - inform the SCU of the verification status. See - . - - If the Event Type ID = 1 then the - verification is still in progress, and the SCU must wait until another event is received. - See. - - If the Event Type ID = 2 then the - verification process has been completed. The SCU may use the returned value of the Treatment - Verification Status (3008,002C) to determine whether or not the beam is ready to be - delivered, or if a machine adjustment or override needs to be made. See. - + The SCP uses the N-EVENT-REPORT to inform the SCU of the verification status. See . + If the Event Type ID = 1 then the verification is still in progress, and the SCU must wait until another event is received. See . + If the Event Type ID = 2 then the verification process has been completed. The SCU may use the returned value of the Treatment Verification Status (3008,002C) to determine whether or not the beam is ready to be delivered, or if a machine adjustment or override needs to be made. See .
@@ -63325,9 +45832,7 @@ Display System Management Service Class (Normative)
Scope - The Display System Service Class allows service - users retrieve parameters related to the Display Subsystem(s). - + The Display System Service Class allows service users retrieve parameters related to the Display Subsystem(s).
Display System Management Data Flow @@ -63344,25 +45849,17 @@ Display System SOP Class
IOD Description - The Display System IOD is an abstraction of the - soft-copy display system and is the basic Information Entity to monitor the status of a Display - System. The Display System SOP Instance is created by the SCP during start-up of the Display System - and has a well-known SOP Instance UID. - + The Display System IOD is an abstraction of the soft-copy display system and is the basic Information Entity to monitor the status of a Display System. The Display System SOP Instance is created by the SCP during start-up of the Display System and has a well-known SOP Instance UID.
DIMSE Service Group - The DIMSE Service shown in - - is applicable to the Display System IOD under the Display System SOP Class. - + The DIMSE Service shown in is applicable to the Display System IOD under the Display System SOP Class.
DIMSE Service Group Applicable to Display System
- DICOM Message Service Element - + DICOM Message Service Element Usage SCU/SCP @@ -63380,46 +45877,34 @@
- This section describes the behavior of the - DIMSE services that are specific for this IOD. The general behavior of the DIMSE services is - specified in. - + This section describes the behavior of the DIMSE services that are specific for this IOD. The general behavior of the DIMSE services is specified in .
N-GET - N-GET is used to retrieve information from - an instance of the Display System SOP Class. - + N-GET is used to retrieve information from an instance of the Display System SOP Class.
Attributes
Display Subsystem Macros - To reduce the size and complexity - of, a macro notation - is used. - + To reduce the size and complexity of , a macro notation is used.
Table Result Context Macro
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Performed Procedure - Step Start DateTime - + Performed Procedure Step Start DateTime (0040,4050) @@ -63430,9 +45915,7 @@
- Performed Procedure - Step End DateTime - + Performed Procedure Step End DateTime (0040,4051) @@ -63443,9 +45926,7 @@
- Actual Human - Performer Sequence - + Actual Human Performer Sequence (0040,4035) @@ -63456,51 +45937,39 @@
- >Human Performer - Code Sequence - + >Human Performer Code Sequence (0040,4009) -/1C - (Required if Human - Performer's Name (0040,4037) is not present.) - + (Required if Human Performer's Name (0040,4037) is not present.)
- >>Include - + >>Include
- >Human - Performer's Name - + >Human Performer's Name (0040,4037) -/1C - (Required if Human - Performer Code Sequence (0040,4009) is not present.) - + (Required if Human Performer Code Sequence (0040,4009) is not present.)
- >Human - Performer's Organization - + >Human Performer's Organization (0040,4036) @@ -63511,9 +45980,7 @@
- Measurement - Equipment Sequence - + Measurement Equipment Sequence (0028,7012) @@ -63524,9 +45991,7 @@
- >Measurement - Functions - + >Measurement Functions (0028,7013) @@ -63537,9 +46002,7 @@
- >Measured - Characteristics - + >Measured Characteristics (0028,7026) @@ -63550,9 +46013,7 @@
- >Measurement - Equipment Type - + >Measurement Equipment Type (0028,7014) @@ -63563,8 +46024,7 @@
- >Manufacturer - + >Manufacturer (0008,0070) @@ -63575,9 +46035,7 @@
- >Manufacturer's - Model Name - + >Manufacturer's Model Name (0008,1090) @@ -63588,9 +46046,7 @@
- >Device Serial - Number - + >Device Serial Number (0018,1000) @@ -63601,9 +46057,7 @@
- >DateTime of - Last Calibration - + >DateTime of Last Calibration (0018,1202) @@ -63617,41 +46071,33 @@
Display System N-GET Attribute Requirements - The Attributes that may be - retrieved are shown in. - + The Attributes that may be retrieved are shown in . @@ -63674,8 +46120,7 @@ @@ -64433,9 +46759,7 @@ @@ -65011,124 +47232,76 @@
SCU Behavior - The SCU uses the N-GET to request the - SCP to provide the contents of a Display System SOP Instance. The SCU shall specify in the - N-GET request primitive the UID of the SOP Instance from which Attributes are to be - returned. - - The SCU shall specify the list of - Display System Attributes for which values are to be returned. The SCU shall not specify - Attributes which are defined within a Sequence, but rather specify the sequence itself to be - returned in its entirety. - - The SCU shall specify in the N-GET - request primitive the well-known UID of the SOP Instance. - + The SCU uses the N-GET to request the SCP to provide the contents of a Display System SOP Instance. The SCU shall specify in the N-GET request primitive the UID of the SOP Instance from which Attributes are to be returned. + The SCU shall specify the list of Display System Attributes for which values are to be returned. The SCU shall not specify Attributes which are defined within a Sequence, but rather specify the sequence itself to be returned in its entirety. + The SCU shall specify in the N-GET request primitive the well-known UID of the SOP Instance.
SCP Behavior - The SCP shall return the values for the - specified Attributes of the Display System SOP Instance. - - The SCP shall return the status code - for the requested SOP Instance retrieval. The meaning of success, warning, and failure - status codes are defined in. - + The SCP shall return the values for the specified Attributes of the Display System SOP Instance. + The SCP shall return the status code for the requested SOP Instance retrieval. The meaning of success, warning, and failure status codes are defined in .
SOP Class Definitions and UIDs - The SOP Class UID of the Display System SOP - Class shall have the value of "1.2.840.10008.5.1.1.40". - + The SOP Class UID of the Display System SOP Class shall have the value of "1.2.840.10008.5.1.1.40".
Reserved Identifications - The well-known UID of the Display System SOP - Instance shall have the value of "1.2.840.10008.5.1.1.40.1". - + The well-known UID of the Display System SOP Instance shall have the value of "1.2.840.10008.5.1.1.40.1".
Conformance
Conformance Statement - The implementation conformance statement of - this SOP Class shall follow. - - The SCU Conformance Statement shall specify the - following items: - + The implementation conformance statement of this SOP Class shall follow . + The SCU Conformance Statement shall specify the following items: - Maximum number of associations to be - supported at the same time - + Maximum number of associations to be supported at the same time List of SOP Classes supported - For each of the supported SOP - Classes: - + For each of the supported SOP Classes: - List of supported SOP Class - Attributes and DICOM Message Service Elements - + List of supported SOP Class Attributes and DICOM Message Service Elements - For each supported Attribute - (mandatory and optional), a valid value range - + For each supported Attribute (mandatory and optional), a valid value range - The SCP Conformance Statement shall specify the - following items: - + The SCP Conformance Statement shall specify the following items: - Maximum number of associations to be - supported at the same time - + Maximum number of associations to be supported at the same time List of SOP Classes supported - For each of the supported SOP - Classes: - + For each of the supported SOP Classes: - List of supported SOP Class - Attributes and DICOM Message Service Elements - + List of supported SOP Class Attributes and DICOM Message Service Elements - For each supported Attribute - (mandatory and optional) - + For each supported Attribute (mandatory and optional) - Valid value range - + Valid value range - Default value if no - value is supplied by the SCU - + Default value if no value is supplied by the SCU - Status code (Failure or - Warning) if the SCU supplies a value that is out of range - + Status code (Failure or Warning) if the SCU supplies a value that is out of range @@ -65138,9 +47311,7 @@ For each supported DIMSE service - SCP behavior for all specific - status codes - + SCP behavior for all specific status codes @@ -65155,184 +47326,84 @@ Overview
Scope - The Volumetric Presentation State Storage SOP - Classes extend the functionality of the Storage Service class (defined in - ) to add the ability to convey an intended Volumetric Presentation State or record an existing - Volumetric Presentation State. The SOP Classes specify the information and behavior that may be used - to present (display) images that are referenced from within the SOP Classes. - - They include capabilities for specifying: - + The Volumetric Presentation State Storage SOP Classes extend the functionality of the Storage Service class (defined in ) to add the ability to convey an intended Volumetric Presentation State or record an existing Volumetric Presentation State. The SOP Classes specify the information and behavior that may be used to present (display) images that are referenced from within the SOP Classes. + They include capabilities for specifying: - spatial registration on the input - datasets - + spatial registration on the input datasets - cropping of the volume datasets by a - bounding box, oblique planes and segmentation objects - + cropping of the volume datasets by a bounding box, oblique planes and segmentation objects - the generation geometry of volumetric - views - + the generation geometry of volumetric views shading models - scalar to P-Value or RGB Value - conversions - + scalar to P-Value or RGB Value conversions - compositing of multiple MPR - renderings - + compositing of multiple MPR renderings - compositing of multiple volume streams - and one volume stream with segmentation - + compositing of multiple volume streams and one volume stream with segmentation - clinical description of the specified - view - + clinical description of the specified view - volume and display relative - annotations, including graphics, text and overlays plus optional references to structured - content providing clinical context for annotations - + volume and display relative annotations, including graphics, text and overlays plus optional references to structured content providing clinical context for annotations - membership to a collection of related - Volumetric Presentation States intended to be processed or displayed together - + membership to a collection of related Volumetric Presentation States intended to be processed or displayed together - the position within a set of - sequentially related Volumetric Presentation States - + the position within a set of sequentially related Volumetric Presentation States animation of the view - reference to an image depicting the - view described by the Volumetric Presentation State - + reference to an image depicting the view described by the Volumetric Presentation State - Each Volumetric Presentation State corresponds - to a single view (equivalent to an Image Box in a Hanging Protocol or Structured Display). If - multiple Volumetric Presentation States are intended to be displayed together (e.g., a set of - orthogonal MPR views) these Presentation States can be grouped by assigning them to a Display - Collection. However, any detailed information about how a set of views should be presented can only - be described by a Structured Display instance or a Hanging Protocol. - - The Planar MPR Volumetric Presentation State - refers to the multi-planar geometry and grayscale or color image transformations that are to be - applied in an explicitly defined manner to convert the stored image pixel data values in a Composite - Image Instance to presentation values (P-Values) or Profile Connection Space values (PCS-Values) - when an image is displayed on a softcopy device. - - The Volume Rendering Volumetric Presentation - State specifies a volume rendered view of volume data. Volume Rendering is a data visualization - method in which voxels (volume sample points) are assigned a color and an opacity (alpha), and a 2D - view is created by accumulating a set of non-transparent samples along a ray through the volume - behind each pixel of the view. Ray samples are calculated by interpolating the voxel values in the - neighborhood of each sample. - - Volume Rendering generally consists of a number - of steps, many of which are parametrically specified in the Volume Rendering SOP Classes. The - processing steps are: - + Each Volumetric Presentation State corresponds to a single view (equivalent to an Image Box in a Hanging Protocol or Structured Display). If multiple Volumetric Presentation States are intended to be displayed together (e.g., a set of orthogonal MPR views) these Presentation States can be grouped by assigning them to a Display Collection. However, any detailed information about how a set of views should be presented can only be described by a Structured Display instance or a Hanging Protocol. + The Planar MPR Volumetric Presentation State refers to the multi-planar geometry and grayscale or color image transformations that are to be applied in an explicitly defined manner to convert the stored image pixel data values in a Composite Image Instance to presentation values (P-Values) or Profile Connection Space values (PCS-Values) when an image is displayed on a softcopy device. + The Volume Rendering Volumetric Presentation State specifies a volume rendered view of volume data. Volume Rendering is a data visualization method in which voxels (volume sample points) are assigned a color and an opacity (alpha), and a 2D view is created by accumulating a set of non-transparent samples along a ray through the volume behind each pixel of the view. Ray samples are calculated by interpolating the voxel values in the neighborhood of each sample. + Volume Rendering generally consists of a number of steps, many of which are parametrically specified in the Volume Rendering SOP Classes. The processing steps are: - Segmentation, or separating the volume - data into groups that will share a particular color palette. Segmentation objects are - specified as cropping inputs to the Volumetric Presentation State. - + Segmentation, or separating the volume data into groups that will share a particular color palette. Segmentation objects are specified as cropping inputs to the Volumetric Presentation State. - Gradient Computation, or finding edges - or boundaries between different types of tissue in the volumetric data. The gradient - computation method used is an implementation decision outside the scope of the Volumetric - Presentation State. - + Gradient Computation, or finding edges or boundaries between different types of tissue in the volumetric data. The gradient computation method used is an implementation decision outside the scope of the Volumetric Presentation State. - Resampling of the volumetric data to - create new samples along the imaginary ray behind each pixel in the output two-dimensional - view, generally using some interpolation of the values of voxels in the neighborhood of the - new sample. The interpolation method used is an implementation decision outside the scope of - the Volumetric Presentation State. - + Resampling of the volumetric data to create new samples along the imaginary ray behind each pixel in the output two-dimensional view, generally using some interpolation of the values of voxels in the neighborhood of the new sample. The interpolation method used is an implementation decision outside the scope of the Volumetric Presentation State. - Classification of samples to assign a - color and opacity to each sample. - + Classification of samples to assign a color and opacity to each sample. - Shading or the application of a - lighting model to samples indicating the effect of ambient, diffuse, and specular light on - the sample. - + Shading or the application of a lighting model to samples indicating the effect of ambient, diffuse, and specular light on the sample. - Compositing or the accumulation of - samples on each ray into the final value of the pixel corresponding to that ray. The - specific algorithms used are outside the scope of the Volumetric Presentation State. - + Compositing or the accumulation of samples on each ray into the final value of the pixel corresponding to that ray. The specific algorithms used are outside the scope of the Volumetric Presentation State. - Conversion to presentation Profile - Connection Space values (PCS-Values) when an image is displayed on a softcopy device. - + Conversion to presentation Profile Connection Space values (PCS-Values) when an image is displayed on a softcopy device. - The result of applying a Volumetric - Presentation State is not expected to be exactly reproducible on different systems. It is difficult - to describe the display and rendering algorithms in enough detail in an interoperable manner such - that a presentation produced at a later time is indistinguishable from that of the original - presentation. While Volumetric Presentation States use established DICOM concepts of grayscale and - color matching (GSDF and ICC color profiles) and provide a generic description of the different - types of display algorithms possible, variations in algorithm implementations within display devices - are inevitable and an exact match of volume presentation on multiple devices cannot be guaranteed. - Nevertheless, reasonable consistency is provided by specification of inputs, geometric descriptions - of spatial views, type of processing to be used, color mapping and blending, input fusion, and many - generic rendering parameters, producing what is expected to be a clinically acceptable result. - - The P-Values are in a device independent - perceptually linear space that is formally defined in - . The PCS-Values are in a device independent space that is formally defined in the ICC Profiles as - CIEXYZ or CIELab values. - - How an SCP of these SOP Classes chooses between - multiple Presentation State instances that may apply to an image is beyond the scope of this - Standard. - - A claim of conformance as an SCP of the SOP - Class implies that the SCP shall make the Presentation State available to the user of the device, - and if selected by the user, shall apply all the transformations stored in the state in the manner - in which they are defined in the Standard. - - How an SCP of these SOP Classes chooses to - display multiple states that are part of a Display Collection is beyond the scope of this Standard. - + The result of applying a Volumetric Presentation State is not expected to be exactly reproducible on different systems. It is difficult to describe the display and rendering algorithms in enough detail in an interoperable manner such that a presentation produced at a later time is indistinguishable from that of the original presentation. While Volumetric Presentation States use established DICOM concepts of grayscale and color matching (GSDF and ICC color profiles) and provide a generic description of the different types of display algorithms possible, variations in algorithm implementations within display devices are inevitable and an exact match of volume presentation on multiple devices cannot be guaranteed. Nevertheless, reasonable consistency is provided by specification of inputs, geometric descriptions of spatial views, type of processing to be used, color mapping and blending, input fusion, and many + generic rendering parameters, producing what is expected to be a clinically acceptable result. + The P-Values are in a device independent perceptually linear space that is formally defined in . The PCS-Values are in a device independent space that is formally defined in the ICC Profiles as CIEXYZ or CIELab values. + How an SCP of these SOP Classes chooses between multiple Presentation State instances that may apply to an image is beyond the scope of this Standard. + A claim of conformance as an SCP of the SOP Class implies that the SCP shall make the Presentation State available to the user of the device, and if selected by the user, shall apply all the transformations stored in the state in the manner in which they are defined in the Standard. + How an SCP of these SOP Classes chooses to display multiple states that are part of a Display Collection is beyond the scope of this Standard. - For example, if a user selects a state that - is part of a four state Spatial Collection, an SCP may choose to display all four together, to - display the single state selected by the user or to display two of the four states deemed - appropriate by the SCP. - + For example, if a user selects a state that is part of a four state Spatial Collection, an SCP may choose to display all four together, to display the single state selected by the user or to display two of the four states deemed appropriate by the SCP.
@@ -65340,29 +47411,12 @@ Volume Transformation Processes
Volumetric Transformations - The transformations defined in the Volumetric - Presentation State Storage SOP Classes replace those that may be defined in the Referenced Image SOP - Instances. If a particular transformation is absent in a Volume Rendering Volumetric Presentation - State Storage SOP Instance, then it shall be assumed to be an identity transformation and any - equivalent transformation, if present, in the Referenced Image SOP Instances shall not be used. - - The presentation-related Attributes of the - Volume Rendering Volumetric Presentation State Storage SOP Classes are immutable. They shall never - be modified or updated; only a derived SOP Instance with a new SOP Instance UID may be created to - represent a different presentation. - + The transformations defined in the Volumetric Presentation State Storage SOP Classes replace those that may be defined in the Referenced Image SOP Instances. If a particular transformation is absent in a Volume Rendering Volumetric Presentation State Storage SOP Instance, then it shall be assumed to be an identity transformation and any equivalent transformation, if present, in the Referenced Image SOP Instances shall not be used. + The presentation-related Attributes of the Volume Rendering Volumetric Presentation State Storage SOP Classes are immutable. They shall never be modified or updated; only a derived SOP Instance with a new SOP Instance UID may be created to represent a different presentation.
Planar MPR Volumetric Transformations - The Planar MPR Volumetric Presentation - State Storage SOP Classes support a set of transformations to produce derived volumetric views - of volume input data. - - The Grayscale Planar MPR Volumetric - Presentation State Storage SOP Class defines a grayscale volumetric view from a single volume - input. The sequence of transformations from volumetric inputs into P-Values is explicitly - defined in the reference pipeline described in. - + The Planar MPR Volumetric Presentation State Storage SOP Classes support a set of transformations to produce derived volumetric views of volume input data. + The Grayscale Planar MPR Volumetric Presentation State Storage SOP Class defines a grayscale volumetric view from a single volume input. The sequence of transformations from volumetric inputs into P-Values is explicitly defined in the reference pipeline described in .
Grayscale Planar MPR Volumetric Pipeline @@ -65375,14 +47429,7 @@
- The Compositing Planar MPR Volumetric - Presentation State Storage SOP Class defines a true color volumetric view from one or more - volume inputs. The sequence of transformations from volumetric inputs into PCS-Values is - explicitly defined in the reference pipeline described in. The - actual sequence implemented may differ (such as classifying and compositing prior to creating - the MPR view) but must result in similar appearance. - + The Compositing Planar MPR Volumetric Presentation State Storage SOP Class defines a true color volumetric view from one or more volume inputs. The sequence of transformations from volumetric inputs into PCS-Values is explicitly defined in the reference pipeline described in . The actual sequence implemented may differ (such as classifying and compositing prior to creating the MPR view) but must result in similar appearance.
Compositing Planar MPR Volumetric Pipeline @@ -65394,48 +47441,17 @@
- The planar MPR transformation requires a - volume that is in the Volumetric Presentation State Reference Coordinate System (VPS-RCS). - - MPR generation is based on the Attributes - of the Multi-Planar Reconstruction Geometry Module (see - ). If the MPR Thickness Type (0070,1502) is SLAB then the Rendering Method (0070,120D) is also - used. - - If Pixel Presentation (0008,9205) is - MONOCHROME, then Presentation LUT Shape (2050,0020) provides the transform to output P-Values. - - If Pixel Presentation (0008,9205) is - TRUE_COLOR, then Presentation State Classification Component Sequence (0070,1801) describes the - conversion of each processed input into an RGB data stream, and Presentation State Compositor - Component Sequence (0070,1805) describes the compositing of these separate RGBA data streams - into a single RGB data stream. This single RGB data stream is then processed as described by ICC - Profile (0028,2000) to produce output PCS-Values. - + The planar MPR transformation requires a volume that is in the Volumetric Presentation State Reference Coordinate System (VPS-RCS). + MPR generation is based on the Attributes of the Multi-Planar Reconstruction Geometry Module (see ). If the MPR Thickness Type (0070,1502) is SLAB then the Rendering Method (0070,120D) is also used. + If Pixel Presentation (0008,9205) is MONOCHROME, then Presentation LUT Shape (2050,0020) provides the transform to output P-Values. + If Pixel Presentation (0008,9205) is TRUE_COLOR, then Presentation State Classification Component Sequence (0070,1801) describes the conversion of each processed input into an RGB data stream, and Presentation State Compositor Component Sequence (0070,1805) describes the compositing of these separate RGBA data streams into a single RGB data stream. This single RGB data stream is then processed as described by ICC Profile (0028,2000) to produce output PCS-Values.
Volume Rendering Volumetric Transformations
Volume Rendering Pipelines - The Volume Rendering Volumetric - Presentation State Storage SOP Classes support a set of transformations to produce derived - volumetric views of volume input data. Attributes comprising the Volume Rendering Volumetric - Presentation States are defined in the context of the reference pipelines described in this - section. While the reference pipelines imply a certain order of the volume rendering - operations of classification, resampling, shading, and compositing, the specific order in - which these operations are applied by any device claiming conformance to this Standard are - implementation-dependent and beyond the scope of this Standard. It is the responsibility of - the viewing application to transform the Standard Attributes into parameters appropriate for - the particular order of operations implemented in the viewing application. - - The Volume Rendering Volumetric - Presentation State Storage SOP Class defines a volumetric view from a single volume input to - produce a volume rendered view. The sequence of transformations from volumetric inputs into - PCS-Values is explicitly defined in the reference pipeline described in. - + The Volume Rendering Volumetric Presentation State Storage SOP Classes support a set of transformations to produce derived volumetric views of volume input data. Attributes comprising the Volume Rendering Volumetric Presentation States are defined in the context of the reference pipelines described in this section. While the reference pipelines imply a certain order of the volume rendering operations of classification, resampling, shading, and compositing, the specific order in which these operations are applied by any device claiming conformance to this Standard are implementation-dependent and beyond the scope of this Standard. It is the responsibility of the viewing application to transform the Standard Attributes into parameters appropriate for the particular order of operations implemented in the viewing application. + The Volume Rendering Volumetric Presentation State Storage SOP Class defines a volumetric view from a single volume input to produce a volume rendered view. The sequence of transformations from volumetric inputs into PCS-Values is explicitly defined in the reference pipeline described in .
Volume Rendering Volumetric Pipeline @@ -65447,22 +47463,9 @@
- The Segmented Volume Rendering - Volumetric Presentation State Storage SOP Class defines a volumetric view from a single - volume dataset with optional segmentation croppings, each colored separately and blended - into the volume to be rendered. The sequence of transformations from volumetric inputs into - PCS-Values is explicitly defined in the reference pipeline described in. - - There is a single item in the Volume - Stream Sequence (0070,1A08) for instances of this SOP Class. - - The classified segmented volumes shall - be blended in lowest to highest priority order using B-over-A blending of the RGB data and - the corresponding opacity (alpha) data. The first item in the Presentation State - Classification Component Sequence (0070,1801) is the base upon which subsequent items are - cropped and B-over-A blended with it. - + The Segmented Volume Rendering Volumetric Presentation State Storage SOP Class defines a volumetric view from a single volume dataset with optional segmentation croppings, each colored separately and blended into the volume to be rendered. The sequence of transformations from volumetric inputs into PCS-Values is explicitly defined in the reference pipeline described in . + There is a single item in the Volume Stream Sequence (0070,1A08) for instances of this SOP Class. + The classified segmented volumes shall be blended in lowest to highest priority order using B-over-A blending of the RGB data and the corresponding opacity (alpha) data. The first item in the Presentation State Classification Component Sequence (0070,1801) is the base upon which subsequent items are cropped and B-over-A blended with it.
Segmented Volume Rendering Volumetric Pipeline @@ -65474,22 +47477,9 @@
- The Multiple Volume Rendering - Volumetric Presentation State Storage SOP Class defines a volumetric view from more than one - volume input. The sequence of transformations from volumetric inputs into PCS-Values is - explicitly defined in the reference pipeline described in. - The specific algorithms for volume rendering may differ, but must result in a similar - appearance. - - It is expected that all volume inputs - are spatially registered to the Volumetric Presentation State - Reference Coordinate System. - The specific step in the processing at which resampling is performed to achieve this spatial - registration is an implementation decision. - - Each item in the Volume Stream Sequence - (0070,1A08) produces one input to a RGBA Compositor. - + The Multiple Volume Rendering Volumetric Presentation State Storage SOP Class defines a volumetric view from more than one volume input. The sequence of transformations from volumetric inputs into PCS-Values is explicitly defined in the reference pipeline described in . The specific algorithms for volume rendering may differ, but must result in a similar appearance. + It is expected that all volume inputs are spatially registered to the Volumetric Presentation State - Reference Coordinate System. The specific step in the processing at which resampling is performed to achieve this spatial registration is an implementation decision. + Each item in the Volume Stream Sequence (0070,1A08) produces one input to a RGBA Compositor.
Multiple Volume Rendering Volumetric Pipeline @@ -65501,165 +47491,77 @@
- Transformation to PCS-Values is - performed after Volume Rendering. - + Transformation to PCS-Values is performed after Volume Rendering.
Volume Rendering Component - This component transforms an RGBA - volume into a volume rendered view according to the parameters in the Render Geometry - Module. This component is implementation dependent, but generally includes processing steps - such as gradient computation to find normals of use in the shading operation, resampling of - volume data, shading according to the parameters in the Render Shading Module, and - compositing of the resampled data to produce the final volume rendered view. - + This component transforms an RGBA volume into a volume rendered view according to the parameters in the Render Geometry Module. This component is implementation dependent, but generally includes processing steps such as gradient computation to find normals of use in the shading operation, resampling of volume data, shading according to the parameters in the Render Shading Module, and compositing of the resampled data to produce the final volume rendered view.
Graphic Projection Component - This component converts the volumetric - annotation specified in the Volumetric Graphic Annotation module into a graphic overlay for - the 2D volume rendered view. It is the role of this component to evaluate the volumetric - graphic annotations, determine which graphics are visible in the volume rendered view, and - provide graphics that are layered on the view. - - Inputs to the Graphic Projection - component are: - + This component converts the volumetric annotation specified in the Volumetric Graphic Annotation module into a graphic overlay for the 2D volume rendered view. It is the role of this component to evaluate the volumetric graphic annotations, determine which graphics are visible in the volume rendered view, and provide graphics that are layered on the view. + Inputs to the Graphic Projection component are: - Volumetric Graphic Annotation - Module - + Volumetric Graphic Annotation Module - RGBA volume input to the Volume - Rendering component - + RGBA volume input to the Volume Rendering component - Volume Render Geometry Module - + Volume Render Geometry Module - Input-specific Cropping - Specification Index (0070,1205) values - + Input-specific Cropping Specification Index (0070,1205) values - Volume Cropping Module - Attributes - + Volume Cropping Module Attributes - The Graphic Projection transform - algorithm considers whether each volumetric graphic annotation is visible in the current - volume rendered view, considering the volume data, Volume Render Geometry, and the value of - Annotation Clipping (0070,1907). - - If Annotation Clipping (0070,1907) is - YES, then the annotation shall be visible only if it is present in the field of view and not - obscured by opaque structures that may lie between the annotation and the viewpoint. In the - case of the Volumetric Presentation Input Annotation Sequence (0070,1905), annotation text - shall be visible only if some part of the specified segmentation is visible. - - If Annotation Clipping (0070,1907) is - NO, then the annotation shall always be visible. A particular implementation may display - annotations that lie behind opaque structures in a different style (such as a softer gray), - but the decision to provide such display style is outside the scope of this Standard. - - The output of the Graphic Projection - component is displayed on the 2D presentation view in the graphic layers specified by the - corresponding values of Graphic Layer (0070,0002). - + The Graphic Projection transform algorithm considers whether each volumetric graphic annotation is visible in the current volume rendered view, considering the volume data, Volume Render Geometry, and the value of Annotation Clipping (0070,1907). + If Annotation Clipping (0070,1907) is YES, then the annotation shall be visible only if it is present in the field of view and not obscured by opaque structures that may lie between the annotation and the viewpoint. In the case of the Volumetric Presentation Input Annotation Sequence (0070,1905), annotation text shall be visible only if some part of the specified segmentation is visible. + If Annotation Clipping (0070,1907) is NO, then the annotation shall always be visible. A particular implementation may display annotations that lie behind opaque structures in a different style (such as a softer gray), but the decision to provide such display style is outside the scope of this Standard. + The output of the Graphic Projection component is displayed on the 2D presentation view in the graphic layers specified by the corresponding values of Graphic Layer (0070,0002).
Volumetric Inputs, Registration and Cropping - A Volumetric Presentation State can take - multiple volumes as input. A volume is defined in - . The same source data can be referenced in more than one input. - - For each input volume, the Modality LUT or - Rescale Slope and Rescale Intercept transformation(s) as specified in the source image(s) is applied - first to the pixel data, otherwise an identity transformation shall be assumed. - + A Volumetric Presentation State can take multiple volumes as input. A volume is defined in . The same source data can be referenced in more than one input. + For each input volume, the Modality LUT or Rescale Slope and Rescale Intercept transformation(s) as specified in the source image(s) is applied first to the pixel data, otherwise an identity transformation shall be assumed. - In enhanced multi-frame IODs this is - specified in the Pixel Value Transformation Functional Group. - + In enhanced multi-frame IODs this is specified in the Pixel Value Transformation Functional Group. - The VOI LUT encoded in the Volumetric - Presentation State, if any, is next applied to the input data, otherwise an identity transformation - shall be assumed. - - The input volumes may or may not be in the - Volumetric Presentation State Reference Coordinate System (VPS-RCS). If they are not, they shall be - registered into the VPS-RCS. - - Two methods of cropping the input volumes are - provided: - + The VOI LUT encoded in the Volumetric Presentation State, if any, is next applied to the input data, otherwise an identity transformation shall be assumed. + The input volumes may or may not be in the Volumetric Presentation State Reference Coordinate System (VPS-RCS). If they are not, they shall be registered into the VPS-RCS. + Two methods of cropping the input volumes are provided: - All inputs to the Volumetric - Presentation State may be cropped using the common cropping methods specified by Global Crop - (0070,120B) and items in the Volume Cropping Sequence (0070,1301). - + All inputs to the Volumetric Presentation State may be cropped using the common cropping methods specified by Global Crop (0070,120B) and items in the Volume Cropping Sequence (0070,1301). - In addition, cropping may be specified - independently for each input to the Volumetric Presentation State as specified by the value - of Crop (0070,1204) and items in the Volume Cropping Sequence (0070,1301). - + In addition, cropping may be specified independently for each input to the Volumetric Presentation State as specified by the value of Crop (0070,1204) and items in the Volume Cropping Sequence (0070,1301). - Combinations of cropping methods may be - specified. For example, all inputs could be cropped using global bounding box cropping in - addition to another cropping method applied to one of more individual inputs to the Volumetric - Presentation State. - + Combinations of cropping methods may be specified. For example, all inputs could be cropped using global bounding box cropping in addition to another cropping method applied to one of more individual inputs to the Volumetric Presentation State.
Volumetric Presentation State Display
Volumetric Presentation State Display Overview - The MPR Volumetric Presentation State - Display Module defines the algorithms used to transform the result of the MultiPlanar - Reconstruction volumetric processing on the input data into an output of P-Values or PCS-Values - for display. - - The Render Display Module defines the - algorithms used to transform the result of the Volume Rendering processing on the input data - into output RGBA values. Presentation State Classification Component Sequence (0070,1801) - describes the conversion of each cropped input into an RGBA volumetric data stream. Volume - Stream Sequence (0070,1209) describes RGBA volumetric data streams which are overlayed using - ordered "B over A" blending into a volumetric data stream. Presentation State Compositor - Component Sequence (0070,1805) describes how the “B over A” blended volumetric data streams are - to be composited together into a single RGBA volumetric data stream. This single RGBA data - stream is an input to the Volume Rendering component. - + The MPR Volumetric Presentation State Display Module defines the algorithms used to transform the result of the MultiPlanar Reconstruction volumetric processing on the input data into an output of P-Values or PCS-Values for display. + The Render Display Module defines the algorithms used to transform the result of the Volume Rendering processing on the input data into output RGBA values. Presentation State Classification Component Sequence (0070,1801) describes the conversion of each cropped input into an RGBA volumetric data stream. Volume Stream Sequence (0070,1209) describes RGBA volumetric data streams which are overlayed using ordered "B over A" blending into a volumetric data stream. Presentation State Compositor Component Sequence (0070,1805) describes how the “B over A” blended volumetric data streams are to be composited together into a single RGBA volumetric data stream. This single RGBA data stream is an input to the Volume Rendering component.
Description of Display Components
Classification Component Components - There are two classification component - types currently defined for conversion from scalar input data to RGBA. The defined - components are: - + There are two classification component types currently defined for conversion from scalar input data to RGBA. The defined components are: - One Input -> RGBA: This - component accepts reconstructed data from one input in the Volumetric Presentation - State Input Sequence (0070,1201) and generates an RGB and an Alpha output. This - classification component would be specified in an item of the Presentation State - Classification Component Sequence (0070,1801): - + One Input -> RGBA: This component accepts reconstructed data from one input in the Volumetric Presentation State Input Sequence (0070,1201) and generates an RGB and an Alpha output. This classification component would be specified in an item of the Presentation State Classification Component Sequence (0070,1801):
One Input -> RGBA Component @@ -65673,13 +47575,7 @@ - Two Inputs -> RGBA: This - component accepts reconstructed data from two inputs in the Volumetric Presentation - State Input Sequence (0070,1201) and generates an RGB and an Alpha output. This - component is used in the case where a two-dimensional color mapping needs to be - performed. This classification component would be specified in an item of the - Presentation State Classification Component Sequence (0070,1801): - + Two Inputs -> RGBA: This component accepts reconstructed data from two inputs in the Volumetric Presentation State Input Sequence (0070,1201) and generates an RGB and an Alpha output. This component is used in the case where a two-dimensional color mapping needs to be performed. This classification component would be specified in an item of the Presentation State Classification Component Sequence (0070,1801):
Two Inputs ->RGBA Component @@ -65692,28 +47588,17 @@
- An example for the use of - this component is to combine Ultrasound Flow Velocity and Ultrasound Flow - Variance to produce a color range from red-blue based on flow velocity and - adding a yellow-green tinge based on flow variance) - + An example for the use of this component is to combine Ultrasound Flow Velocity and Ultrasound Flow Variance to produce a color range from red-blue based on flow velocity and adding a yellow-green tinge based on flow variance)
Compositor Components - There are two compositor component - types defined for compositing of two input RGBA (or one RGBA and one RGB) data sources. The - defined components are: - + There are two compositor component types defined for compositing of two input RGBA (or one RGBA and one RGB) data sources. The defined components are: - RGB Compositor: This component - accepts two RGBA inputs (with one Alpha input optional) and composites the data into - a single RGB output. Each item of Presentation State Compositor Component Sequence - (0070,1805) specifies one RGB Compositor component: - + RGB Compositor: This component accepts two RGBA inputs (with one Alpha input optional) and composites the data into a single RGB output. Each item of Presentation State Compositor Component Sequence (0070,1805) specifies one RGB Compositor component:
RGB Compositor Component @@ -65727,10 +47612,7 @@ - RGBA Compositor: This component - accepts two RGBA inputs and composites the data into a single RGB output and a - single Alpha output. - + RGBA Compositor: This component accepts two RGBA inputs and composites the data into a single RGB output and a single Alpha output.
RGBA Compositor Component @@ -65750,17 +47632,10 @@ Internal Structure of Components
Internal Structure of Classification Components - Component Type (0070,1802) specifies - the component defined in each item of Presentation State Classification Component Sequence - (0070,1801), which in turn controls by conditions the rest of the content of the item to - provide the necessary specification of the component. The internal structure of each - component in block diagram form is as follows: - + Component Type (0070,1802) specifies the component defined in each item of Presentation State Classification Component Sequence (0070,1801), which in turn controls by conditions the rest of the content of the item to provide the necessary specification of the component. The internal structure of each component in block diagram form is as follows: - One Input -> RGBA: Specified - by Component Type (0070,1802) = ONE_TO_RGBA: - + One Input -> RGBA: Specified by Component Type (0070,1802) = ONE_TO_RGBA:
Internal Structure of One Input -> RGBA Component @@ -65774,9 +47649,7 @@ - Two Inputs -> RGBA: If - Component Type (0070,1802) = TWO_TO_RGBA: - + Two Inputs -> RGBA: If Component Type (0070,1802) = TWO_TO_RGBA:
Internal Structure of Two Input -> RGBA Component @@ -65790,27 +47663,12 @@ - The number of most significant bits - extracted from each input is specified by the value of Bits Mapped to Color Lookup Table - (0028,1403) in the Component Input Sequence (0070,1803) item for that input. - - If Component Type (0070,1802) = - TWO_TO_RGBA, there shall be two items in Component Input Sequence (0070,1803) with the first - item defining the source of the most significant bits of the Palette Color Lookup Table - input and the second item defining the source of the least significant bits of the Palette - Color Lookup Table input - + The number of most significant bits extracted from each input is specified by the value of Bits Mapped to Color Lookup Table (0028,1403) in the Component Input Sequence (0070,1803) item for that input. + If Component Type (0070,1802) = TWO_TO_RGBA, there shall be two items in Component Input Sequence (0070,1803) with the first item defining the source of the most significant bits of the Palette Color Lookup Table input and the second item defining the source of the least significant bits of the Palette Color Lookup Table input
Internal Structure of RGB and RGBA Compositor Components - Weighting transfer functions that - compute the weighting factors used by the Compositor Function as a function of Alpha - 1 - and Alpha2 values are specified as weighting look-up - tables (LUTs) in the RGB and RGBA Compositor components. The RGB and RGBA Compositor - components are identical except for the compositing of the additional Alpha component in the - RGBA Compositor: - + Weighting transfer functions that compute the weighting factors used by the Compositor Function as a function of Alpha1 and Alpha2 values are specified as weighting look-up tables (LUTs) in the RGB and RGBA Compositor components. The RGB and RGBA Compositor components are identical except for the compositing of the additional Alpha component in the RGBA Compositor:
Internal Structure of RGB Compositor Component @@ -65833,65 +47691,23 @@
- Because each Weighting LUT uses both - Alpha values in determining a weighting factor, they allow compositing functions that would - not be possible if each weighting factor were based only on that input's Alpha value. See - - for typical usage of the Weighting LUTs. - - The input bits to the Weighting LUTs - are obtained by combining the two Alpha inputs, with half the input bits obtained from each - Alpha input: - + Because each Weighting LUT uses both Alpha values in determining a weighting factor, they allow compositing functions that would not be possible if each weighting factor were based only on that input's Alpha value. See for typical usage of the Weighting LUTs. + The input bits to the Weighting LUTs are obtained by combining the two Alpha inputs, with half the input bits obtained from each Alpha input: - In the case of the first - compositor component corresponding to the first item in Presentation State - Compositor Component Sequence (0070,1805), the Alpha from the classification - component corresponding to the first item in the Presentation State Classification - Component Sequence (0070,1805) provides the most significant bits of the Weighting - LUT inputs, while the Alpha from the classification component corresponding to the - second item in the Presentation State Classification Component Sequence (0070,1805) - provides the least significant bits of the Weighting LUT inputs. - + In the case of the first compositor component corresponding to the first item in Presentation State Compositor Component Sequence (0070,1805), the Alpha from the classification component corresponding to the first item in the Presentation State Classification Component Sequence (0070,1805) provides the most significant bits of the Weighting LUT inputs, while the Alpha from the classification component corresponding to the second item in the Presentation State Classification Component Sequence (0070,1805) provides the least significant bits of the Weighting LUT inputs. - In the case of subsequent - compositor components, the Alpha from the classification component corresponding to - the next item in the Presentation State Classification Component Sequence - (0070,1805) provides the least significant bits of the Weighting LUT inputs, while - the most significant bits of the Weighting LUT inputs are computed as one minus the - Alpha from the classification component corresponding to the next item in the - Presentation State Classification Component Sequence (0070,1805). - + In the case of subsequent compositor components, the Alpha from the classification component corresponding to the next item in the Presentation State Classification Component Sequence (0070,1805) provides the least significant bits of the Weighting LUT inputs, while the most significant bits of the Weighting LUT inputs are computed as one minus the Alpha from the classification component corresponding to the next item in the Presentation State Classification Component Sequence (0070,1805). - The integer outputs of the Weighting - LUTs are normalized to the range 0.0 to 1.0, and the Compositor Function combines the - normalized R, G, B and Alpha (each component called "Color" = Cx) - input values as follows: - + The integer outputs of the Weighting LUTs are normalized to the range 0.0 to 1.0, and the Compositor Function combines the normalized R, G, B and Alpha (each component called "Color" = Cx) input values as follows: - Cout = (C - 1*Weight1) + (C - 2*Weight2) - - - The sum of the normalized Weight - 1 - and Weight2 shall be no greater than 1.0. - - The color input values are normalized - because the number of output bits from the RGB Palette Color Lookup Tables and the Alpha - Palette Color Lookup Table may be different in each classification component. - - The output of the compositor shall be - range-limited ("clamped") to ensure that the outputs are guaranteed to be within a valid - range of color values regardless of the validity of the weighting transfer functions. This - isolates subsequent compositor components and the Profile Connection Space Transform from - overflow errors. + Cout = (C1*Weight1) + (C2*Weight2) + The sum of the normalized Weight1 and Weight2 shall be no greater than 1.0. + The color input values are normalized because the number of output bits from the RGB Palette Color Lookup Tables and the Alpha Palette Color Lookup Table may be different in each classification component. + The output of the compositor shall be range-limited ("clamped") to ensure that the outputs are guaranteed to be within a valid range of color values regardless of the validity of the weighting transfer functions. This isolates subsequent compositor components and the Profile Connection Space Transform from overflow errors.
@@ -65899,105 +47715,35 @@ Additional Volumetric Considerations
Annotations in Volumetric Presentations States - The Volumetric Presentation States provide - two ways for annotating views: - + The Volumetric Presentation States provide two ways for annotating views: - Annotations on the Volumetric - Presentation View - + Annotations on the Volumetric Presentation View - Annotations described by - coordinates in the Volumetric Presentation State Reference Coordinate System (VPS-RCS) - with optional references to Structured Reports providing context. - + Annotations described by coordinates in the Volumetric Presentation State Reference Coordinate System (VPS-RCS) with optional references to Structured Reports providing context. - Annotations on the view provide the - application of free unformatted text or vector graphics as described in the. Since the Graphic Annotation Module - allows only the addition of graphics to the 2D view defined by the Presentation State without - attached clinical meaning, Volumetric Graphic Annotations provide a mechanism to create - annotations in the VPS-RCS with optional references to other objects which can have structured - context attached. - - Volumetric Graphic Annotations can be - specified in two variants: either via Graphic Types with 3D coordinates, as defined in, or via a reference to inputs of the - Presentation State. The latter is intended to be used to display annotation labels for - segmentations of the volume data; for example, when a lesion has been marked via a Segmentation - IOD and this segmentation is rendered together with the anatomical data. - - Since annotations which are added via the - Graphic Annotation Module are defined within the display space, they should not be used to point - to clinical relevant structures which would be positioned on a different anatomy after - manipulation. - - In contrast since Volumetric Graphic - Annotations have coordinates in the VPS-RCS, applications can still show them after a user has - manipulated the initial view which has been defined by the Presentation State. - - The exact visual representation of the - annotations is at the discretion of the display application, as well as the mechanisms which may - be employed to ensure that Volumetric Graphic Annotations are sufficiently visible, even if the - location in the volume is not visible in the current view. E.g. for a Graphic Type POINT a - display application might render a crosshair at the specified position in the volume or a sphere - with an arrow pointing to it instead of rendering Volumetric Graphic Annotations directly within - the volume a projection of the annotations may be rendered as an overlay on top of the view. - - However, annotations can be grouped into - Graphic Layers and it is suggested that applications provide mechanisms to define rendering - styles per Graphic Layer. - - See - - and - - for examples of Volumetric Graphic Annotations. - + Annotations on the view provide the application of free unformatted text or vector graphics as described in the . Since the Graphic Annotation Module allows only the addition of graphics to the 2D view defined by the Presentation State without attached clinical meaning, Volumetric Graphic Annotations provide a mechanism to create annotations in the VPS-RCS with optional references to other objects which can have structured context attached. + Volumetric Graphic Annotations can be specified in two variants: either via Graphic Types with 3D coordinates, as defined in , or via a reference to inputs of the Presentation State. The latter is intended to be used to display annotation labels for segmentations of the volume data; for example, when a lesion has been marked via a Segmentation IOD and this segmentation is rendered together with the anatomical data. + Since annotations which are added via the Graphic Annotation Module are defined within the display space, they should not be used to point to clinical relevant structures which would be positioned on a different anatomy after manipulation. + In contrast since Volumetric Graphic Annotations have coordinates in the VPS-RCS, applications can still show them after a user has manipulated the initial view which has been defined by the Presentation State. + The exact visual representation of the annotations is at the discretion of the display application, as well as the mechanisms which may be employed to ensure that Volumetric Graphic Annotations are sufficiently visible, even if the location in the volume is not visible in the current view. E.g. for a Graphic Type POINT a display application might render a crosshair at the specified position in the volume or a sphere with an arrow pointing to it instead of rendering Volumetric Graphic Annotations directly within the volume a projection of the annotations may be rendered as an overlay on top of the view. + However, annotations can be grouped into Graphic Layers and it is suggested that applications provide mechanisms to define rendering styles per Graphic Layer. + See and for examples of Volumetric Graphic Annotations.
Volumetric Animation - Several different styles of animation are - defined in Volumetric Presentation States. In general, an animation style will vary either the - input, processing, or view geometry in order to produce a varying presentation view. This - section describes each of the animation styles and how it produces an animated view. - + Several different styles of animation are defined in Volumetric Presentation States. In general, an animation style will vary either the input, processing, or view geometry in order to produce a varying presentation view. This section describes each of the animation styles and how it produces an animated view.
Input Sequence Animation - A Presentation Animation Style - (0070,1A01) value of INPUT_SEQ indicates that Input Sequence Animation is being specified. - In this animation style, a single Volumetric Presentation State is defined which includes - input items in the Volumetric Presentation State Input Sequence (0070,1201) with different - values of Input Sequence Position Index (0070,1203). The animated presentation view is - produced by sequencing through values of Input Sequence Position Index (0070,1203) at a - specified animation rate Recommended Animation Rate (0070,1A03), where each value of the - index produces one 'frame' of the animated view from inputs that have that value of Input - Sequence Position Index (0070,1203). See. - + A Presentation Animation Style (0070,1A01) value of INPUT_SEQ indicates that Input Sequence Animation is being specified. In this animation style, a single Volumetric Presentation State is defined which includes input items in the Volumetric Presentation State Input Sequence (0070,1201) with different values of Input Sequence Position Index (0070,1203). The animated presentation view is produced by sequencing through values of Input Sequence Position Index (0070,1203) at a specified animation rate Recommended Animation Rate (0070,1A03), where each value of the index produces one 'frame' of the animated view from inputs that have that value of Input Sequence Position Index (0070,1203). See . - For example, a set of inputs could - be temporally related volumes of a moving anatomical structure like the heart. - + For example, a set of inputs could be temporally related volumes of a moving anatomical structure like the heart. - There may be more than one input item - in Volumetric Presentation State Input Sequence (0070,1201) with the same value of Input - Sequence Position Index (0070,1203), in which case the inputs are processed together to - produce the frame of the animated view. - + There may be more than one input item in Volumetric Presentation State Input Sequence (0070,1201) with the same value of Input Sequence Position Index (0070,1203), in which case the inputs are processed together to produce the frame of the animated view. - For example, pairs of input items - could represent the same volume input at a point in time with two different segmentation - croppings (representing different organ structures) that are blended together into a - single view. - + For example, pairs of input items could represent the same volume input at a point in time with two different segmentation croppings (representing different organ structures) that are blended together into a single view.
@@ -66013,28 +47759,11 @@
Presentation Sequence Animation - A Presentation Animation Style - (0070,1A01) value of PRESENTATION_SEQ indicates that Presentation Sequence Animation is - being specified. In this animation style, a set of Volumetric Presentation States are - applied sequentially. See. - + A Presentation Animation Style (0070,1A01) value of PRESENTATION_SEQ indicates that Presentation Sequence Animation is being specified. In this animation style, a set of Volumetric Presentation States are applied sequentially. See . - One example of the use of - presentation sequence animation is a view of a moving heart wherein a stent is at a - stationary position at the center of the view. Because the geometry of each view frame - is slightly different, separate Volumetric Presentation State instances are required for - each view frame. - + One example of the use of presentation sequence animation is a view of a moving heart wherein a stent is at a stationary position at the center of the view. Because the geometry of each view frame is slightly different, separate Volumetric Presentation State instances are required for each view frame. - Each Volumetric Presentation State of - the set is identified by having the same value of Presentation Sequence Collection UID - (0070,1102). The order of application of these Presentation States is determined by the - value of Presentation Sequence Position Index (0070,1103) defined in the Presentation State. - The animated presentation view is produced by sequencing through values of presentation - sequence position index at a specified animation rate Recommended Animation Rate - (0070,1A03), where each value of the index produces one 'frame' of the animated view - produced by that Volumetric Presentation State. - + Each Volumetric Presentation State of the set is identified by having the same value of Presentation Sequence Collection UID (0070,1102). The order of application of these Presentation States is determined by the value of Presentation Sequence Position Index (0070,1103) defined in the Presentation State. The animated presentation view is produced by sequencing through values of presentation sequence position index at a specified animation rate Recommended Animation Rate (0070,1A03), where each value of the index produces one 'frame' of the animated view produced by that Volumetric Presentation State.
Presentation Sequence Animation @@ -66049,18 +47778,9 @@
Crosscurve Animation - A Presentation Animation Style - (0070,1A01) value of CROSSCURVE indicates that Crosscurve Animation is being specified. In - this animation style, a Presentation State defines a Planar MPR view at the beginning of a - curve defined in Animation Curve Sequence (0070,1A04). The Planar MPR view is stepped a - distance Animation Step Size (0070,1A05) along the curve defined in Animation Curve Sequence - (0070,1A04) at the rate specified by Recommended Animation Rate (0070,1A03) in steps per - second. See. - + A Presentation Animation Style (0070,1A01) value of CROSSCURVE indicates that Crosscurve Animation is being specified. In this animation style, a Presentation State defines a Planar MPR view at the beginning of a curve defined in Animation Curve Sequence (0070,1A04). The Planar MPR view is stepped a distance Animation Step Size (0070,1A05) along the curve defined in Animation Curve Sequence (0070,1A04) at the rate specified by Recommended Animation Rate (0070,1A03) in steps per second. See . - A typical application of this - animation style is motion along a curve centered within the colon or a blood vessel. - + A typical application of this animation style is motion along a curve centered within the colon or a blood vessel.
@@ -66076,12 +47796,7 @@
Flythrough Animation - A Presentation Animation Style - (0070,1A01) value of FLYTHROUGH indicates that Flythrough Animation is being specified. In - this animation style, the Volumetric Presentation State defines an initial volume rendered - view and a specified movement of the view along a path through the volume. See. - + A Presentation Animation Style (0070,1A01) value of FLYTHROUGH indicates that Flythrough Animation is being specified. In this animation style, the Volumetric Presentation State defines an initial volume rendered view and a specified movement of the view along a path through the volume. See .
Flythrough Animation @@ -66096,169 +47811,83 @@
Swivel Animation - A Presentation Animation Style - (0070,1A01) value of SWIVEL indicates that Swivel Animation is being specified. In this - animation style, a Presentation State defines an initial volume rendered using Viewpoint - Position (0070,1603), Viewpoint LookAt Point (0070,1604) and Viewpoint Up Direction - (0070,1605). When the animation begins, the view begins to rotate back and forth about an - axis parallel to the Viewpoint Up Direction (0070,1605) that intersects the Viewpoint LookAt - Point (0070,1604). The extent of the arc of rotation is defined by Swivel Range (0070,1A06) - and the maximum rate of rotation is specified by Recommended Animation Rate (0070,1A03) in - degrees per second, although it is recommended that the changes of direction at the ends of - the swivel range be smooth which implies a slowing of the rotation as the endpoints are - approached. - + A Presentation Animation Style (0070,1A01) value of SWIVEL indicates that Swivel Animation is being specified. In this animation style, a Presentation State defines an initial volume rendered using Viewpoint Position (0070,1603), Viewpoint LookAt Point (0070,1604) and Viewpoint Up Direction (0070,1605). When the animation begins, the view begins to rotate back and forth about an axis parallel to the Viewpoint Up Direction (0070,1605) that intersects the Viewpoint LookAt Point (0070,1604). The extent of the arc of rotation is defined by Swivel Range (0070,1A06) and the maximum rate of rotation is specified by Recommended Animation Rate (0070,1A03) in degrees per second, although it is recommended that the changes of direction at the ends of the swivel range be smooth which implies a slowing of the rotation as the endpoints are approached.
Display Layout - The layout of multiple Volumetric - Presentation States is not specified by the Volumetric Transformation process. However, there - are Attributes within Volumetric Presentation States that can influence the overall display - layout. - + The layout of multiple Volumetric Presentation States is not specified by the Volumetric Transformation process. However, there are Attributes within Volumetric Presentation States that can influence the overall display layout. For instance: - Anatomic Region Sequence - (0008,2218) specifies the anatomic region covered by the Volumetric Presentation State - + Anatomic Region Sequence (0008,2218) specifies the anatomic region covered by the Volumetric Presentation State - View Code Sequence (0054,0220) - describes the view of the anatomic region of interest (e.g., Coronal, Oblique - transverse, etc.) - + View Code Sequence (0054,0220) describes the view of the anatomic region of interest (e.g., Coronal, Oblique transverse, etc.) - Presentation Display Collection UID - (0070,1101) identifies the Presentation State as one of a set of views intended to be - displayed together - + Presentation Display Collection UID (0070,1101) identifies the Presentation State as one of a set of views intended to be displayed together - SOP Class UID (0008,0016) - identifies that the Presentation State describes the volumetric view - + SOP Class UID (0008,0016) identifies that the Presentation State describes the volumetric view - The use of these Attributes allows a - display application to create an appropriate presentation of multiple Volumetric Presentation - States, whether through the application of a Hanging Protocol instance, a Structured Display - instance or by means of an application-specific algorithm. - - For an example of their use, see. - + The use of these Attributes allows a display application to create an appropriate presentation of multiple Volumetric Presentation States, whether through the application of a Hanging Protocol instance, a Structured Display instance or by means of an application-specific algorithm. + For an example of their use, see .
Behavior of An SCP - In addition to the behavior for the Storage Service - Class specified in, the following - additional requirements are specified for the Volumetric Presentation State Storage SOP Classes: - + In addition to the behavior for the Storage Service Class specified in , the following additional requirements are specified for the Volumetric Presentation State Storage SOP Classes: - a display device acting as an SCP of these - SOP Classes shall make all mandatory presentation Attributes available for application to the - referenced volumetric data at the discretion of the display device user, for all Image Storage - SOP Classes defined in the Conformance Statement for which the Volumetric Presentation State - Storage SOP Class is supported. - + a display device acting as an SCP of these SOP Classes shall make all mandatory presentation Attributes available for application to the referenced volumetric data at the discretion of the display device user, for all Image Storage SOP Classes defined in the Conformance Statement for which the Volumetric Presentation State Storage SOP Class is supported. - a display device acting as an SCP of the - Volumetric Presentation State Storage SOP Classes shall support the Segmentation SOP Class for - cropping and the Spatial Registration SOP Class for registration. - + a display device acting as an SCP of the Volumetric Presentation State Storage SOP Classes shall support the Segmentation SOP Class for cropping and the Spatial Registration SOP Class for registration. - a display device acting as an SCP of a - Volume Rendering Volumetric Presentation State Storage SOP Class shall perform an unshaded - volume rendering if the Render Shading Module is absent from the SOP Instance. - + a display device acting as an SCP of a Volume Rendering Volumetric Presentation State Storage SOP Class shall perform an unshaded volume rendering if the Render Shading Module is absent from the SOP Instance. - a display device acting as an SCP of the - Volumetric Presentation State Storage SOP Classes is not required to support the Presentation - Animation Module. - + a display device acting as an SCP of the Volumetric Presentation State Storage SOP Classes is not required to support the Presentation Animation Module. - a display device acting as an SCP of any of - the Volumetric Presentation State Storage SOP Classes is not required to support Structured - Reporting Storage SOP Classes. - + a display device acting as an SCP of any of the Volumetric Presentation State Storage SOP Classes is not required to support Structured Reporting Storage SOP Classes.
Conformance - In addition to the Conformance Statement - requirements for the Storage Service Class specified in, - the following additional requirements are specified for the Volumetric Presentation State Storage SOP - Classes: - + In addition to the Conformance Statement requirements for the Storage Service Class specified in , the following additional requirements are specified for the Volumetric Presentation State Storage SOP Classes:
Conformance Statement For An SCU - The following behavior shall be documented in - the Conformance Statement of any implementation claiming conformance to a Volumetric Presentation - State Storage SOP Class as an SCU: - + The following behavior shall be documented in the Conformance Statement of any implementation claiming conformance to a Volumetric Presentation State Storage SOP Class as an SCU: - For an SCU of a Volumetric Presentation - State Storage SOP Class that is creating a SOP Instance of the SOP Class, the manner in - which presentation related Attributes are derived from a displayed image, operator - intervention or defaults, and how they are included in the IOD. - + For an SCU of a Volumetric Presentation State Storage SOP Class that is creating a SOP Instance of the SOP Class, the manner in which presentation related Attributes are derived from a displayed image, operator intervention or defaults, and how they are included in the IOD. - For an SCU of a Volumetric Presentation - State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCU - and which may be referenced by instances of the Volumetric Presentation State Storage SOP - Class. - + For an SCU of a Volumetric Presentation State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCU and which may be referenced by instances of the Volumetric Presentation State Storage SOP Class.
Conformance Statement For An SCP - The following behavior shall be documented in - the Conformance Statement of any implementation claiming conformance to a Volumetric Presentation - State Storage SOP Class as an SCP: - + The following behavior shall be documented in the Conformance Statement of any implementation claiming conformance to a Volumetric Presentation State Storage SOP Class as an SCP: - For an SCP of a Volumetric Presentation - State Storage SOP Class that is displaying an image referred to by a SOP Instance of the SOP - Class, the manner in which presentation related Attributes are used to influence the display - of an image. - + For an SCP of a Volumetric Presentation State Storage SOP Class that is displaying an image referred to by a SOP Instance of the SOP Class, the manner in which presentation related Attributes are used to influence the display of an image. - For an SCP of a Volumetric Presentation - State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCP - and which may be referenced by instances of the Volumetric Presentation State Storage SOP - Class. - + For an SCP of a Volumetric Presentation State Storage SOP Class, the Image Storage SOP Classes that are also supported by the SCP and which may be referenced by instances of the Volumetric Presentation State Storage SOP Class. - For an SCP of a Volumetric Presentation - State Storage SOP Class, whether the Presentation Animation Module is supported, and if not - supported, any notifications or lack of notifications to the user that the context - information is not displayed. - + For an SCP of a Volumetric Presentation State Storage SOP Class, whether the Presentation Animation Module is supported, and if not supported, any notifications or lack of notifications to the user that the context information is not displayed. - For an SCP of a Volumetric Presentation - State Storage SOP Class, whether references to Structured Report instances are supported, - and if not supported, any notifications or lack of notifications to the user that the - context information is not displayed. - + For an SCP of a Volumetric Presentation State Storage SOP Class, whether references to Structured Report instances are supported, and if not supported, any notifications or lack of notifications to the user that the context information is not displayed.
@@ -66270,64 +47899,34 @@ Overview
Scope - The Non-Patient Object Storage Service Class - defines an application-level class-of-service that allows one DICOM AE to send a SOP Instance of a - non-patient-root information object to another DICOM AE. - - A Non-Patient Object SOP Instance adheres to a - Composite Instance IOD Information Model specified in - - that does not have at its root the Patient Information Entity. - Non-Patient Object SOP Instances may still contain patient-related identifiable information, e.g., - Inventory SOP Instances - + The Non-Patient Object Storage Service Class defines an application-level class-of-service that allows one DICOM AE to send a SOP Instance of a non-patient-root information object to another DICOM AE. + A Non-Patient Object SOP Instance adheres to a Composite Instance IOD Information Model specified in that does not have at its root the Patient Information Entity. + Non-Patient Object SOP Instances may still contain patient-related identifiable information, e.g., Inventory SOP Instances
Service Definition - The Non-Patient Object Storage Service Class - includes several SOP Classes, each using an IOD defined in - - (see). The Non-Patient Object Storage Service - Class uses the C-STORE DIMSE Service specified in. A - successful completion of the C-STORE has the following semantics: - + The Non-Patient Object Storage Service Class includes several SOP Classes, each using an IOD defined in (see ). The Non-Patient Object Storage Service Class uses the C-STORE DIMSE Service specified in . A successful completion of the C-STORE has the following semantics: - Both the SCU and the SCP support the - type of information to be stored. - + Both the SCU and the SCP support the type of information to be stored. - The transferred information is stored - in some medium. - + The transferred information is stored in some medium. - For some time frame, the stored - information may be accessed. - + For some time frame, the stored information may be accessed. - Support for the Non-Patient Object - Storage Service Class does not imply support for any related Query/Retrieve Service - Classes. - + Support for the Non-Patient Object Storage Service Class does not imply support for any related Query/Retrieve Service Classes. - The duration of the storage is also - implementation dependent, but is described in the Conformance Statement of the SCP. - + The duration of the storage is also implementation dependent, but is described in the Conformance Statement of the SCP. - The Non-Patient Object Storage - Service Class is intended to be used in a variety of environments: e.g., for - workstations to transfer SOP Instances to other workstations or archives, for archives - to transfer SOP Instances to workstations, etc. - + The Non-Patient Object Storage Service Class is intended to be used in a variety of environments: e.g., for workstations to transfer SOP Instances to other workstations or archives, for archives to transfer SOP Instances to workstations, etc. @@ -66335,18 +47934,11 @@
Association Negotiation - The Association negotiation rules as defined in - - apply to the SOP Classes of this Service Class. No SOP Class specific application information (extended - negotiation) is used. - + The Association negotiation rules as defined in apply to the SOP Classes of this Service Class. No SOP Class specific application information (Extended Negotiation) is used.
SOP Classes - The application-level services addressed by the - Non-Patient Object Storage Service Class definition are specified in the SOP Classes specified in. - + The application-level services addressed by the Non-Patient Object Storage Service Class definition are specified in the SOP Classes specified in .
Display System N-GET Attributes
- Attribute Name - + Attribute Name Tag - Usage SCU/SCP - + Usage SCU/SCP
- Specific Character - Set - + Specific Character Set (0008,0005) -/1C - (Required if an - extended or replacement character set is used) - + (Required if an extended or replacement character set is used)
- Institution Name - + Institution Name (0008,0080) @@ -63686,9 +46131,7 @@
- Institution - Address - + Institution Address (0008,0081) @@ -63699,9 +46142,7 @@
- Device Serial - Number - + Device Serial Number (0018,1000) @@ -63723,9 +46164,7 @@
- Institutional - Department Name - + Institutional Department Name (0008,1040) @@ -63736,9 +46175,7 @@
- Institutional - Department Type Code Sequence - + Institutional Department Type Code Sequence (0008,1041) @@ -63749,9 +46186,7 @@
- Manufacturer's - Model Name - + Manufacturer's Model Name (0008,1090) @@ -63762,9 +46197,7 @@
- Equipment - Administrator Sequence - + Equipment Administrator Sequence (0028,7000) @@ -63775,8 +46208,7 @@
- >Person Name - + >Person Name (0040,A123) @@ -63787,9 +46219,7 @@
- >Person - Identification Code Sequence - + >Person Identification Code Sequence (0040,1101) @@ -63801,18 +46231,14 @@
- >>Include - + >>Include
- >Person's - Address - + >Person's Address (0040,1102) @@ -63823,9 +46249,7 @@
- >Person's - Telephone Numbers - + >Person's Telephone Numbers (0040,1103) @@ -63836,26 +46260,19 @@
- >Institution - Name - + >Institution Name (0008,0080) -/1C - (Required if - Institution Code Sequence (0008,0082) is not present. May be present - otherwise.) - + (Required if Institution Code Sequence (0008,0082) is not present. May be present otherwise.)
- >Institution - Address - + >Institution Address (0008,0081) @@ -63866,35 +46283,27 @@
- >Institution - Code Sequence - + >Institution Code Sequence (0008,0082) -/1C - (Required if - Institution Name (0008,0080) is not present.May be present otherwise.) - + (Required if Institution Name (0008,0080) is not present.May be present otherwise.)
- >>Include - + >>Include
- Number of Display - Subsystems - + Number of Display Subsystems (0028,7001) @@ -63905,9 +46314,7 @@
- Display Subsystem - Sequence - + Display Subsystem Sequence (0028,7023) @@ -63918,9 +46325,7 @@
- >Display - Subsystem ID - + >Display Subsystem ID (0028,7003) @@ -63931,9 +46336,7 @@
- >Display - Subsystem Name - + >Display Subsystem Name (0028,7004) @@ -63944,9 +46347,7 @@
- >Display - Subsystem Description - + >Display Subsystem Description (0028,7005) @@ -63957,9 +46358,7 @@
- >Display Device - Type Code Sequence - + >Display Device Type Code Sequence (0028,7022) @@ -63971,17 +46370,14 @@
- >>Include - + >>Include
- >Manufacturer - + >Manufacturer (0008,0070) @@ -63992,9 +46388,7 @@
- >Device Serial - Number - + >Device Serial Number (0018,1000) @@ -64005,9 +46399,7 @@
- >Manufacturer's - Model Name - + >Manufacturer's Model Name (0008,1090) @@ -64018,8 +46410,7 @@
- >System Status - + >System Status (0028,7006) @@ -64030,9 +46421,7 @@
- >System Status - Comment - + >System Status Comment (0028,7007) @@ -64043,9 +46432,7 @@
- >Display - Subsystem Configuration Sequence - + >Display Subsystem Configuration Sequence (0028,700A) @@ -64056,9 +46443,7 @@
- >>Configuration - ID - + >>Configuration ID (0028,700B) @@ -64069,9 +46454,7 @@
- >>Configuration - Name - + >>Configuration Name (0028,700C) @@ -64082,9 +46465,7 @@
- >>Configuration - Description - + >>Configuration Description (0028,700D) @@ -64095,9 +46476,7 @@
- >>Referenced - Target Luminance Characteristics ID - + >>Referenced Target Luminance Characteristics ID (0028,700E) @@ -64108,9 +46487,7 @@
- >Current - Configuration ID - + >Current Configuration ID (0028,7002) @@ -64121,9 +46498,7 @@
- >Measurement - Equipment Sequence - + >Measurement Equipment Sequence (0028,7012) @@ -64134,9 +46509,7 @@
- >>Measurement - Functions - + >>Measurement Functions (0028,7013) @@ -64147,9 +46520,7 @@
- >>Measured - Characteristics - + >>Measured Characteristics (0028,7026) @@ -64160,9 +46531,7 @@
- >>Measurement - Equipment Type - + >>Measurement Equipment Type (0028,7014) @@ -64184,9 +46553,7 @@
- >>Manufacturer's - Model Name - + >>Manufacturer's Model Name (0008,1090) @@ -64197,9 +46564,7 @@
- >>Device - Serial Number - + >>Device Serial Number (0018,1000) @@ -64210,9 +46575,7 @@
- >>DateTime of - Last Calibration - + >>DateTime of Last Calibration (0018,1202) @@ -64230,9 +46593,7 @@
- Target Luminance - Characteristics Sequence - + Target Luminance Characteristics Sequence (0028,7008) @@ -64243,9 +46604,7 @@
- >Luminance - Characteristics ID - + >Luminance Characteristics ID (0028,7009) @@ -64256,9 +46615,7 @@
- >Display - Function Type - + >Display Function Type (0028,7019) @@ -64269,9 +46626,7 @@
- >Target Minimum - Luminance - + >Target Minimum Luminance (0028,701D) @@ -64282,9 +46637,7 @@
- >Target Maximum - Luminance - + >Target Maximum Luminance (0028,701E) @@ -64295,55 +46648,43 @@
- >Gamma Value - + >Gamma Value (0028,701A) -/1C - (Required if the - value of Display Function Type (0028,7019) is GAMMA) - + (Required if the value of Display Function Type (0028,7019) is GAMMA)
- >Number of - Luminance Points - + >Number of Luminance Points (0028,701B) -/1C - (Required if the - value of Display Function Type (0028,7019) is USER_DEFINED) - + (Required if the value of Display Function Type (0028,7019) is USER_DEFINED)
- >Luminance - Response Sequence - + >Luminance Response Sequence (0028,701C) -/1C - (Required if the - value of Display Function Type (0028,7019) is USER_DEFINED) - + (Required if the value of Display Function Type (0028,7019) is USER_DEFINED)
- >>DDL Value - + >>DDL Value (0028,7017) @@ -64354,9 +46695,7 @@
- >>Luminance - Value - + >>Luminance Value (0028,701F) @@ -64367,26 +46706,19 @@
- >Luminance - Response Description - + >Luminance Response Description (0028,7020) -/1C - (Required if the - value of Display Function Type (0028,7019) is USER_DEFINED. May be - present otherwise.) - + (Required if the value of Display Function Type (0028,7019) is USER_DEFINED. May be present otherwise.)
- >CIExy White - Point - + >CIExy White Point (0028,7018) @@ -64397,9 +46729,7 @@
- >Reflected - Ambient Light - + >Reflected Ambient Light (2010,0160) @@ -64410,18 +46740,14 @@
- >Ambient Light - Value Source - + >Ambient Light Value Source (0028,7025) -/1C - (Required if - Reflected Ambient Light (2010,0160) is present.) - + (Required if Reflected Ambient Light (2010,0160) is present.)
- QA Results - Sequence - + QA Results Sequence (0028,700F) @@ -64446,9 +46770,7 @@
- >Display - Subsystem ID - + >Display Subsystem ID (0028,7003) @@ -64459,9 +46781,7 @@
- >Display - Subsystem QA Results Sequence - + >Display Subsystem QA Results Sequence (0028,7010) @@ -64472,9 +46792,7 @@
- >>Configuration - ID - + >>Configuration ID (0028,700B) @@ -64485,9 +46803,7 @@
- >>Configuration - QA Results Sequence - + >>Configuration QA Results Sequence (0028,7011) @@ -64498,9 +46814,7 @@
- >>>Display - Calibration Result Sequence - + >>>Display Calibration Result Sequence (0028,7016) @@ -64512,18 +46826,14 @@
- >>>>Include - + >>>>Include
- >>>>Luminance - Characteristics ID - + >>>>Luminance Characteristics ID (0028,7009) @@ -64534,9 +46844,7 @@
- >>>Visual - Evaluation Result Sequence - + >>>Visual Evaluation Result Sequence (0028,7015) @@ -64548,18 +46856,14 @@
- >>>>Include - + >>>>Include
- >>>>Visual - Evaluation Test Sequence - + >>>>Visual Evaluation Test Sequence (0028,7028) @@ -64570,9 +46874,7 @@
- >>>>>Test - Result - + >>>>>Test Result (0028,7029) @@ -64583,9 +46885,7 @@
- >>>>>Test - Result Comment - + >>>>>Test Result Comment (0028,702A) @@ -64596,9 +46896,7 @@
- >>>>>Test - Pattern Code Sequence - + >>>>>Test Pattern Code Sequence (0028,702C) @@ -64610,35 +46908,26 @@
- >>>>>>Include - + >>>>>>Include
- >>>>>Referenced - Image Sequence - + >>>>>Referenced Image Sequence (0008,1140) -/1C - (Required if Test - Pattern Code Sequence (0028,702C) is absent in this item.May be present - otherwise.) - + (Required if Test Pattern Code Sequence (0028,702C) is absent in this item.May be present otherwise.)
- >>>>>>Referenced - SOP Class UID - + >>>>>>Referenced SOP Class UID (0008,1150) @@ -64649,9 +46938,7 @@
- >>>>>>Referenced - SOP Instance UID - + >>>>>>Referenced SOP Instance UID (0008,1151) @@ -64662,45 +46949,31 @@
- >>>>>>Referenced - Frame Number - + >>>>>>Referenced Frame Number (0008,1160) -/1C - (Required if the - Referenced SOP Instance is a multi-frame image and the reference does - not apply to all frames, and Referenced Segment Number (0062,000B) is - not present.) - + (Required if the Referenced SOP Instance is a multi-frame image and the reference does not apply to all frames, and Referenced Segment Number (0062,000B) is not present.)
- >>>>>>Referenced - Segment Number - + >>>>>>Referenced Segment Number (0062,000B) -/1C - (Required if the - Referenced SOP Instance is a Segmentation or Surface Segmentation and - the reference does not apply to all segments and Referenced Frame Number - (0008,1160) is not present.) - + (Required if the Referenced SOP Instance is a Segmentation or Surface Segmentation and the reference does not apply to all segments and Referenced Frame Number (0008,1160) is not present.)
- >>>>>>Test - Image Validation - + >>>>>>Test Image Validation (0028,702B) @@ -64711,9 +46984,7 @@
- >>>>Visual - Evaluation Method Code Sequence - + >>>>Visual Evaluation Method Code Sequence (0028,702E) @@ -64725,18 +46996,14 @@
- >>>>>Include - + >>>>>Include
- >>>Luminance - Uniformity Result Sequence - + >>>Luminance Uniformity Result Sequence (0028,7027) @@ -64748,18 +47015,14 @@
- >>>>Include - + >>>>Include
- >>>>Number - of Luminance Points - + >>>>Number of Luminance Points (0028,701B) @@ -64770,9 +47033,7 @@
- >>>>Measurement - Pattern Code Sequence - + >>>>Measurement Pattern Code Sequence (0028,702D) @@ -64784,18 +47045,14 @@
- >>>>>Include - + >>>>>Include
- >>>>DDL - Value - + >>>>DDL Value (0028,7017) @@ -64806,9 +47063,7 @@
- >>>>White - Point Flag - + >>>>White Point Flag (0028,7021) @@ -64819,9 +47074,7 @@
- >>>>Luminance - Response Sequence - + >>>>Luminance Response Sequence (0028,701C) @@ -64832,9 +47085,7 @@
- >>>>>Luminance - Value - + >>>>>Luminance Value (0028,701F) @@ -64845,25 +47096,19 @@
- >>>>>CIExy - White Point - + >>>>>CIExy White Point (0028,7018) -/1C - (Required if the - value of White Point Flag (0028,7021) is YES.) - + (Required if the value of White Point Flag (0028,7021) is YES.)
- >>>>Reflected - Ambient Light - + >>>>Reflected Ambient Light (2010,0160) @@ -64874,25 +47119,19 @@
- >>>>>Ambient - Light Value Source - + >>>>>Ambient Light Value Source (0028,7025) -/1C - (Required if - Reflected Ambient Light (2010,0160) is present.) - + (Required if Reflected Ambient Light (2010,0160) is present.)
- >>>Luminance - Result Sequence - + >>>Luminance Result Sequence (0028,7024) @@ -64904,18 +47143,14 @@
- >>>>Include - + >>>>Include
- >>>>Number - of Luminance Points - + >>>>Number of Luminance Points (0028,701B) @@ -64926,9 +47161,7 @@
- >>>>Luminance - Response Sequence - + >>>>Luminance Response Sequence (0028,701C) @@ -64939,9 +47172,7 @@
- >>>>>DDL - Value - + >>>>>DDL Value (0028,7017) @@ -64952,9 +47183,7 @@
- >>>>>Luminance - Value - + >>>>>Luminance Value (0028,701F) @@ -64965,9 +47194,7 @@
- >>>>>CIExy - White Point - + >>>>>CIExy White Point (0028,7018) @@ -64978,9 +47205,7 @@
- >>>>Reflected - Ambient Light - + >>>>Reflected Ambient Light (2010,0160) @@ -64991,18 +47216,14 @@
- >>>>Ambient - Light Value Source - + >>>>Ambient Light Value Source (0028,7025) -/1C - (Required if - Reflected Ambient Light (2010,0160) is present.) - + (Required if Reflected Ambient Light (2010,0160) is present.)
@@ -66359,11 +47951,7 @@ @@ -66397,8 +47985,7 @@ @@ -1915,14 +1963,17 @@ + Alternatively, in the context of a Query with Empty Value Matching (see ), a string of two QUOTATION MARK characters, representing an empty key Value. @@ -1933,7 +1984,7 @@ @@ -2041,7 +2095,7 @@ Long String @@ -2326,7 +2383,7 @@ Unlimited Characters @@ -2464,10 +2524,10 @@ - For attributes that were present in ACR-NEMA 1.0 and 2.0 and that have been retired, the specifications of Value Representation and Value Multiplicity provided are recommendations for the purpose of interpreting their values in objects created in accordance with earlier versions of this Standard. These recommendations are suggested as most appropriate for a particular attribute; however, there is no guarantee that historical objects will not violate some requirements or specified VR and/or VM. + For Data Elements that were present in ACR-NEMA 1.0 and 2.0 and that have been retired, the specifications of Value Representation and Value Multiplicity provided are recommendations for the purpose of interpreting their Values in objects created in accordance with earlier versions of this Standard. These recommendations are suggested as most appropriate for a particular Data Element; however, there is no guarantee that historical objects will not violate some requirements or specified VR and/or VM. - The length of the value of UC, UR and UT VRs is limited only by the size of the maximum unsigned integer representable in a 32 bit VL field minus two, since FFFFFFFFH is reserved and lengths are required to be even. + The length of the Value of UC, UR and UT VRs is limited only by the size of the maximum unsigned integer representable in a 32 bit VL field minus two, since FFFFFFFFH is reserved and lengths are required to be even. In previous editions of the Standard (see PS3.5 2015a), the TAB character was not listed as permitted for the ST, LT and UT VRs. It has been added for the convenience of formatting and the encoding of XML text. @@ -2530,47 +2590,52 @@ Character strings representing person names are encoded using a convention for PN Value Representation based on component groups with 5 components. For the purpose of writing names in ideographic characters and in phonetic characters, up to 3 component groups may be used. The delimiter of the component group shall be the equals character "=" (3DH). The three component groups in their order of occurrence are: an alphabetic representation, an ideographic representation, and a phonetic representation. Any component group may be absent, including the first component group. In this case, the person name may start with one or more "=" delimiters. Delimiters are also required for interior null component groups. Trailing null component groups and their delimiters may be omitted. - The first component group (identified by DICOM as "alphabetic") shall be encoded using the character set specified by the Attribute Specific Character Set (0008,0005), value 1. + The first component group (identified by DICOM as "alphabetic") shall be encoded using the character set specified by the Attribute Specific Character Set (0008,0005), Value 1. If Attribute Specific Character Set (0008,0005) is not present, the Default Character Repertoire ISO-IR 6 shall be used. escapes for Code Extension shall not be used in this component group. - When Specific Character Set (0008,0005) value 1 specifies a multi-byte character set without Code Extension (i.e., Unicode in UTF-8, or ), the characters of this component group may be encoded with multiple bytes, + When Specific Character Set (0008,0005) Value 1 specifies a multi-byte character set without Code Extension (i.e., Unicode in UTF-8, or ), the characters of this component group may be encoded with multiple bytes, but shall be drawn from the code points U+0020 through U+1FFF of , or the following code points: U+3001, U+3002, U+300C, U+300D, U+3099 through U+309C, and U+30A0 through U+30FF - The second group shall be used for ideographic characters. The character sets used will usually be those from Attribute Specific Character Set (0008,0005), value 2 through n, and may use escapes. - The third group shall be used for phonetic characters. The character sets used shall be those from Attribute Specific Character Set (0008,0005), value 1 through n, and may use escapes. - Delimiter characters "^" and "=" are taken from the character set specified by value 1 of the Attribute Specific Character Set (0008,0005). If Attribute Specific Character Set (0008,0005), value 1 is not present, the Default Character Repertoire ISO-IR 6 shall be used. - At the beginning of the value of the Person Name data element, the following initial condition is assumed: if Attribute Specific Character Set (0008,0005), value 1 is not present, the Default Character Repertoire ISO-IR 6 is invoked, and if the Attribute Specific Character Set (0008,0005), value 1 is present, the character set specified by value 1 of the Attribute is invoked. - At the end of the value of the Person Name data element, and before the component delimiters "^" and "=", the character set shall be switched to the Default Character Repertoire ISO-IR 6, if value 1 of the Attribute Specific Character Set (0008,0005) is not present. If value 1 of the Attribute Specific Character Set (0008,0005) is present, the character set shall be switched to that specified by value 1 of the Attribute. - The value length of each component group is 64 characters maximum, including the delimiter for the component group. Each combining character (e.g., diacritics or vowel marks) shall be considered a separate character for this maximum length, regardless of how an application may display such combining characters (i.e., combined into the glyph for the base character, or rendered separately). + The second group shall be used for ideographic characters. The character sets used will usually be those from Attribute Specific Character Set (0008,0005), Value 2 through n, and may use escapes. + The third group shall be used for phonetic characters. The character sets used shall be those from Attribute Specific Character Set (0008,0005), Value 1 through n, and may use escapes. + Delimiter characters "^" and "=" are taken from the character set specified by Value 1 of the Attribute Specific Character Set (0008,0005). If Attribute Specific Character Set (0008,0005), Value 1 is not present, the Default Character Repertoire ISO-IR 6 shall be used. + At the beginning of the Value of the Person Name Data Element, the following initial condition is assumed: if Attribute Specific Character Set (0008,0005), Value 1 is not present, the Default Character Repertoire ISO-IR 6 is invoked, and if the Attribute Specific Character Set (0008,0005), Value 1 is present, the character set specified by Value 1 of the Attribute is invoked. + At the end of the Value of the Person Name Data Element, and before the component delimiters "^" and "=", the character set shall be switched to the Default Character Repertoire ISO-IR 6, if Value 1 of the Attribute Specific Character Set (0008,0005) is not present. If Value 1 of the Attribute Specific Character Set (0008,0005) is present, the character set shall be switched to that specified by Value 1 of the Attribute. + The Value Length of each component group is 64 characters maximum, including the delimiter for the component group. Each combining character (e.g., diacritics or vowel marks) shall be considered a separate character for this maximum length, regardless of how an application may display such combining characters (i.e., combined into the glyph for the base character, or rendered separately).
Unknown (UN) Value Representation - The Unknown (UN) VR shall only be used for Private Attribute Data Elements and Standard Data Elements previously encoded as some DICOM VR other than UN using the DICOM Default Little Endian Transfer Syntax (Implicit VR), and whose Value Representation is currently unknown, - or whose known Value Representation is none of OB, OD, OF, OL, OW, SQ, UC, UR or UT and whose value length exceeds 65534 (216-2) and therefore cannot be encoded as a 16-bit unsigned integer in the Value Length Field defined for the known Value Representation (see ). - As long as the VR is unknown the Value Field is insensitive to byte ordering and shall not be 'byte-swapped' (see ). In the case of undefined length sequences, the value shall remain in implicit VR form. See for a description of Private Data Attribute Elements and section 10 and for a discussion of Transfer Syntaxes. + The Unknown (UN) VR shall only be used for Private Data Elements and Standard Data Elements previously encoded as some DICOM VR other than UN using Implicit VR encoding, and whose Value Representation is currently unknown, + or whose known Value Representation is one of those that have a 16-bit Value Length Field (see ) when using Explicit VR encoding + and whose Value Length exceeds 65534 (216-2). + As long as the VR is unknown the Value Field is insensitive to byte ordering and shall not be 'byte-swapped' (see ). + In the case of Undefined Length Sequences, the Value shall remain in Implicit VR form. + See for a description of Private Data Attribute Elements and + and + for a discussion of Transfer Syntaxes. The UN VR shall not be used for Private Creator Data Elements (i.e., the VR is equal to LO, see ). The UN VR shall not be used for File Meta Information Data Elements (any Tag (0002,xxxx), see ). - All other (non-default) DICOM Transfer Syntaxes employ explicit VR in their encoding, and therefore any Private and/or Standard Data Element Value Field Attribute value encoded and decoded using any Transfer Syntax other than the DICOM Default Little Endian Transfer Syntax, and not having been translated to the DICOM Default Little Endian Transfer Syntax in the interim, will have a known VR. + All other (non-default) DICOM Transfer Syntaxes employ Explicit VR in their encoding, and therefore any Private and/or Standard Data Element Value Field encoded and decoded using any Transfer Syntax other than the DICOM Default Little Endian Transfer Syntax, and not having been translated to the DICOM Default Little Endian Transfer Syntax in the interim, will have a known VR. - If at some point an application knows the actual VR for an Attribute of VR UN (e.g., has its own applicable data dictionary), it can assume that the Value Field of the Attribute is encoded in Little Endian byte ordering with implicit VR encoding, irrespective of the current Transfer Syntax. + If at some point an application knows the actual VR for a Data Element of VR UN (e.g., has its own applicable data dictionary), it can assume that the Value Field of the Data Element is encoded in Little Endian byte ordering with Implicit VR encoding, irrespective of the current Transfer Syntax. - This VR of UN is needed when an explicit VR must be given to a Data Element whose Value Representation is unknown (e.g., store and forward). + This VR of UN is needed when an Explicit VR must be given to a Data Element whose Value Representation is unknown (e.g., store and forward). - This VR of UN is also needed for the encoding of Data Elements with explicit VR whose value length exceeds 65534 (216-2) (FFFEH, the largest even length unsigned 16 bit number) but which are defined to have a 16 bit explicit VR length field. + This VR of UN is also needed for the encoding of Data Elements with Explicit VR whose Value Length exceeds 65534 (216-2) (FFFEH, the largest even length unsigned 16 bit number) but which are defined to have a 16 bit Explicit VR Value Length Field. - The length field of the Value Representation of UN may contain the value of Undefined Length, in which case the contents can be assumed to be encoded with implicit VR. See to determine how to parse Data Elements with an Undefined Length. + The Value Length Field of VR UN may contain Undefined Length (FFFFFFFFH), in which case the contents can be assumed to be encoded with Implicit VR. See to determine how to parse Data Elements with an Undefined Length. An example of a Standard Data Element using a UN VR is a Type 3 or Type U Standard Attribute added to an SOP Class definition. An existing application that does not support that new Attribute (and encounters it) could convert the VR to UN. @@ -2590,37 +2655,37 @@
Enumerated Values and Defined Terms - The value of certain Data Elements may be chosen among a set of explicit Values satisfying its VR. These explicit Values are either Enumerated Values or Defined Terms and are specified in and . - Enumerated Values are used when the specified explicit Values are the only Values allowed for a Data Element. A Data Element with Enumerated Values that does not have a Value equivalent to one of the Values specified in this Standard has an invalid value within the scope of a specific Information Object/SOP Class definition. + The Value of certain Data Elements may be chosen among a set of explicit Values satisfying its VR. These explicit Values are either Enumerated Values or Defined Terms and are specified in and . + Enumerated Values are used when the specified explicit Values are the only Values allowed for a Data Element. A Data Element with Enumerated Values that does not have a Value equivalent to one of the Values specified in this Standard has an invalid Value within the scope of a specific Information Object/SOP Class definition. Patient Sex (0010, 0040) is an example of a Data Element having Enumerated Values. It is defined to have a Value that is either "M", "F", or "O" (see ). No other Value shall be given to this Data Element. - Future modifications of this Standard may add to the set of allowed values for Data Elements with Enumerated Values. Such additions by themselves may or may not require a change in SOP Class UIDs, depending on the semantics of the Data Element. + Future modifications of this Standard may add to the set of allowed Values for Data Elements with Enumerated Values. Such additions by themselves may or may not require a change in SOP Class UIDs, depending on the semantics of the Data Element. - Defined Terms are used when the specified explicit Values may be extended by implementers to include additional new Values. These new Values shall be specified in the Conformance Statement (see ) and shall not have the same meaning as currently defined Values in this Standard. A Data Element with Defined Terms that does not contain a Value equivalent to one of the Values currently specified in this Standard shall not be considered to have an invalid value. An empty (zero length) value is not a valid new Value for a Defined Term; empty values shall be considered invalid unless the Standard specifically permits empty values. New Values shall not have a meaning of unknown, since that concept, if permitted by the Standard, shall be conveyed explicitly either by allowing the Data Element to be zero length or by provision of a standard Defined Term with such a meaning. + Defined Terms are used when the specified explicit Values may be extended by implementers to include additional new Values. These new Values shall be specified in the Conformance Statement (see ) and shall not have the same meaning as currently defined Values in this Standard. A Data Element with Defined Terms that does not contain a Value equivalent to one of the Values currently specified in this Standard shall not be considered to have an invalid Value. An empty (zero length) Value is not a valid new Value for a Defined Term; empty Values shall be considered invalid unless the Standard specifically permits empty Values. New Values shall not have a meaning of unknown, since that concept, if permitted by the Standard, shall be conveyed explicitly either by allowing the Data Element to be zero length or by provision of a standard Defined Term with such a meaning. Reporting Priority (0040,1009) is an example of a Data Element having Defined Terms. It is defined to have a Value that may be one of the set of standard Values; HIGH, ROUTINE, MEDIUM, or LOW (see ). Because this Data Element has Defined Terms other reporting priorities may be defined by the implementer. - The validity of empty values is usually specified by the attribute being defined as Type 2 (see ). However, in the context of a required Type 1 attribute with multiple values, some (but not all) values may be allowed to be empty (see ); in this case the Standard explicitly specifies the validity of empty values in the list of Defined Terms for each value. Specific Character Set (0008,0005) is an example of a Data Element for which the Standard specifically permits the first value to be empty when multiple values are present. Image Type (0008,0008) is an example of a Data Element that in some IODs defined in is required to be present with multiple values, but if an empty value is not explicitly listed in the Defined Terms for Value 3 by an IOD an empty value is invalid. + The validity of empty Values is usually specified by the Attribute being defined as Type 2 (see ). However, in the context of a required Type 1 Attribute with multiple Values, some (but not all) Values may be allowed to be empty (see ); in this case the Standard explicitly specifies the validity of empty Values in the list of Defined Terms for each Value. Specific Character Set (0008,0005) is an example of a Data Element for which the Standard specifically permits the first Value to be empty when multiple Values are present. Image Type (0008,0008) is an example of a Data Element that in some IODs defined in is required to be present with multiple Values, but if an empty Value is not explicitly listed in the Defined Terms for Value 3 by an IOD an empty Value is invalid. - The Value Representation may affect the interpretation of Defined Terms and Enumerated Values for numeric values. For binary Value Representations, the textual representation of the Value in the Standard does not affect the interpretation. For string Value Representations (IS and DS), the meaning of the Value in the Standard shall be used, not the literal string. + The Value Representation may affect the interpretation of Defined Terms and Enumerated Values for numeric Values. For binary Value Representations, the textual representation of the Value in the Standard does not affect the interpretation. For string Value Representations (IS and DS), the meaning of the Value in the Standard shall be used, not the literal string. - For example, an Enumerated Value of "1" expressed in the text of the Standard matches an IS or DS value encoded as "001", or a DS value encoded as "1.0" or "1." or "1.0000E+00" or any permitted encoding. Leading and trailing spaces are defined in not to be significant and hence do not affect the interpretation. + For example, an Enumerated Value of "1" expressed in the text of the Standard matches an IS or DS Value encoded as "001", or a DS Value encoded as "1.0" or "1." or "1.0000E+00" or any permitted encoding. Leading and trailing spaces are defined in not to be significant and hence do not affect the interpretation.
Value Multiplicity (VM) and Delimitation - The Value Multiplicity of a Data Element specifies the number of Values that can be encoded in the Value Field of that Data Element. The VM of each Data Element is specified explicitly in . If the number of Values that may be encoded in an element is variable, it shall be represented by two numbers separated by a dash; e.g., "1-10" means that there may be 1 to 10 Values in the element. + The Value Multiplicity of a Data Element specifies the number of Values that can be encoded in the Value Field of that Data Element. The VM of each Data Element is specified explicitly in . If the number of Values that may be encoded in a Data Element is variable, it shall be represented by two numbers separated by a dash; e.g., "1-10" means that there may be 1 to 10 Values in the Data Element. Elements having a multiplicity of "S", which represented "single", in older versions of this Standard, will have a multiplicity of "1" in this version of this Standard. @@ -2636,18 +2701,18 @@ Multiple binary Values of fixed length shall be a series of concatenated Values without any delimiter. - Each string Value in a multi-valued character string may be of even or odd length, but the length of the entire Value Field (including "\" delimiters) shall be of even length. If padding is required to make the Value Field of even length, a single padding character shall be applied to the end of the Value Field (to the last Value), in which case the length of the last Value may exceed the Length of Value by 1. + Each string Value in a multi-valued character string may be of even or odd length, but the length of the entire Value Field (including "\" delimiters) shall be of even length. If padding is required to make the Value Field of even length, a single padding character shall be applied to the end of the Value Field (to the last Value), in which case the length of the last Value may exceed the length of Value by 1. - A padding character may need to be appended to a fixed length character string value in the above case. + A padding character may need to be appended to a fixed length character string Value in the above case. Only the last UID Value in a multi-valued Data Element with a VR of UI shall be padded with a single trailing NULL (00H) character when necessary to ensure that the entire Value Field (including "\" delimiters) is of even length. - Data Elements with a VR of LT, OB, OD, OF, OL, OW, SQ, ST, UN, UR or UT shall always have a Value Multiplicity of one. See . + Data Elements with a VR of LT, OB, OD, OF, OL, OV, OW, SQ, ST, UN, UR or UT shall always have a Value Multiplicity of one. See .
The Data Set A Data Set represents an instance of a real world Information Object. A Data Set is constructed of Data Elements. Data Elements contain the encoded Values of Attributes of that object. The specific content and semantics of these Attributes are specified in Information Object Definitions (see ). - The construction, characteristics, and encoding of a Data Set and its Data Elements are discussed in this section. Pixel Data, Overlays, and Curves are Data Elements whose interpretation depends on other related elements. + The construction, characteristics, and encoding of a Data Set and its Data Elements are discussed in this section. Pixel Data, Overlays, and Curves are Data Elements whose interpretation depends on other related Data Elements.
Data Elements A Data Element is uniquely identified by a Data Element Tag. The Data Elements in a Data Set shall be ordered by increasing Data Element Tag Number and shall occur at most once in a Data Set. @@ -2710,7 +2775,7 @@ a 16 or 32-bit (dependent on VR and whether VR is explicit or implicit) unsigned integer containing the Explicit Length of the Value Field as the number of bytes (even) that make up the Value. It does not include the length of the Data Element Tag, Value Representation, and Value Length Fields. - a 32-bit Length Field set to Undefined Length (FFFFFFFFH). Undefined Lengths may be used for Data Elements having the Value Representation (VR) Sequence of Items (SQ) and Unknown (UN). For Data Elements with Value Representation OW or OB Undefined Length may be used depending on the negotiated Transfer Syntax (see and ). + a 32-bit Value Length Field set to Undefined Length (FFFFFFFFH). Undefined Lengths may be used for Data Elements having the Value Representation (VR) Sequence of Items (SQ) and Unknown (UN). For Data Elements with Value Representation OW or OB Undefined Length may be used depending on the negotiated Transfer Syntax (see and ). @@ -2719,7 +2784,7 @@ The decoder of a Data Set should support both Explicit and Undefined Lengths for VRs of SQ and UN and, when applicable, for VRs of OW and OB. - The 32-bit Value Length Field limits the maximum size of large data values such as Pixel Data sent in a Native Format (encoded in Transfer Syntaxes that use only the unencapsulated form). + The 32-bit Value Length Field limits the maximum size of large data Value Fields such as Pixel Data sent in a Native Format (encoded in Transfer Syntaxes that use only the unencapsulated form). @@ -2730,7 +2795,7 @@ An even number of bytes containing the Value(s) of the Data Element. The data type of Value(s) stored in this field is specified by the Data Element's VR. The VR for a given Data Element Tag can be determined using the Data Dictionary in , or using the VR Field if it is contained explicitly within the Data Element. The VR of Standard Data Elements shall agree with those specified in the Data Dictionary. - The Value Multiplicity specifies how many Values with this VR can be placed in the Value Field. If the VM is greater than one, multiple values shall be delimited within the Value Field as defined previously in . The VMs of Standard Data Elements are specified in the Data Dictionary in . + The Value Multiplicity specifies how many Values with this VR can be placed in the Value Field. If the VM is greater than one, multiple Values shall be delimited within the Value Field as defined previously in . The VMs of Standard Data Elements are specified in the Data Dictionary in . Value Fields with Undefined Length are delimited through the use of Sequence Delimitation Items and Item Delimitation Data Elements, which are described further in . @@ -2754,7 +2819,7 @@ - VRs of SV, UC, UR, UV and UT may not have an Undefined Length, i.e.,a Value Length of FFFFFFFFH. + VRs of SV, UC, UR, UV and UT may not have an Undefined Length, i.e., a Value Length of FFFFFFFFH. @@ -2960,14 +3025,14 @@
Group Length Group Length (gggg,0000) Data Elements were implicitly defined for Standard and Private Data Element groups with a Value Representation of UL and a Value Multiplicity of 1, but have been retired. See PS3.5-2007. - All implementations shall be able to parse Group Length elements, and may discard and not insert or re-insert them; if present they shall be consistent with the encoding of the Data Set even if the Transfer Syntax is changed resulting in a change in the actual length of a group of elements. No implementation shall require the presence of Group Length elements. + All implementations shall be able to parse Group Length Data Elements, and may discard and not insert or re-insert them; if present they shall be consistent with the encoding of the Data Set even if the Transfer Syntax is changed resulting in a change in the actual length of a group of Data Elements. No implementation shall require the presence of Group Length Data Elements. Elements in groups 0, 2, 4 and 6 are not Standard Data Elements. Mandatory requirements for Group Length for groups 0 and 2 are specified elsewhere in the Standard. - It is recommended that Group Length elements be removed during storage or transfer in order to avoid the risk of inconsistencies arising during coercion of data element values and changes in Transfer Syntax. + It is recommended that Group Length Data Elements be removed during storage or transfer in order to avoid the risk of inconsistencies arising during coercion of Data Element Values and changes in Transfer Syntax. @@ -2986,7 +3051,7 @@ Big Endian byte ordering was previously described but has been retired, See PS3.5 2016b. - The packing of bits within values of OB or OW Value Representation for Pixel Data and Overlay Data is described in . + The packing of bits within Values of OB or OW Value Representation for Pixel Data and Overlay Data is described in . The OL and OV Value Representations are not used for Pixel Data or Overlay Data. Byte ordering is a component of an agreed upon Transfer Syntax (see ). The default DICOM Transfer Syntax, which shall be supported by all AEs, uses Little Endian encoding and is specified in . Alternate Little Endian Transfer Syntaxes are also specified in . @@ -3011,15 +3076,15 @@
Data Element Type - An attribute, encoded as a Data Element, may or may not be required in a Data Set, depending on that Attribute's Data Element Type. + An Attribute, encoded as a Data Element, may or may not be required in a Data Set, depending on that Attribute's Data Element Type. The Data Element Type of an Attribute of an Information Object Definition or an Attribute of a SOP Class Definition is used to specify whether that Attribute is mandatory or optional. The Data Element Type also indicates if an Attribute is conditional (only mandatory under certain conditions). The Data Element Types of Attributes of Composite IODs are specified in . The Data Element Types of Attributes of Normalized IODs are specified as Attributes of SOP Classes in .
Type 1 Required Data Elements - IODs and SOP Classes define Type 1 Data Elements that shall be included and are mandatory elements. The Value Field shall contain valid data as defined by the elements VR and VM as specified in . The Length of the Value Field shall not be zero. Absence of a valid Value in a Type 1 Data Element is a protocol violation. + IODs and SOP Classes define Type 1 Data Elements that shall be included and are mandatory Data Elements. The Value Field shall contain valid data as defined by the Data Element's VR and VM as specified in . The Length of the Value Field shall not be zero. Absence of a valid Value in a Type 1 Data Element is a protocol violation. - For data elements with a string (CS, SH, LO) rather than binary, text or sequence Value Representation, and for which multiple Values are allowed, the presence of a single Value is sufficient to satisfy the Type 1 requirement, unless specified otherwise in the Attribute description, and other Values may be empty, unless otherwise specified by the IOD. The presence of one or more delimiter (BACKSLASH) characters alone, without any Values, is not sufficient to satisfy the Type 1 requirement, since even though the Value Length is greater than zero, there is no valid Value present. + For Data Elements with a string (CS, SH, LO) rather than binary, text or sequence Value Representation, and for which multiple Values are allowed, the presence of a single Value is sufficient to satisfy the Type 1 requirement, unless specified otherwise in the Attribute description, and other Values may be empty, unless otherwise specified by the IOD. The presence of one or more delimiter (BACKSLASH) characters alone, without any Values, is not sufficient to satisfy the Type 1 requirement, since even though the Value Length is greater than zero, there is no valid Value present. A Type 1 Sequence Data Element will contain one or more Items, as defined by the IOD (irrespective of the VM of the Sequence, which is always one ()). Whether or not those Items may be empty (contain no Data Elements) depends on the IOD definition of the Data Set for each Item. @@ -3029,16 +3094,16 @@
Type 1C Conditional Data Elements - IODs and SOP Classes define Data Elements that shall be included under certain specified conditions. Type 1C elements have the same requirements as Type 1 elements under these conditions. It is a protocol violation if the specified conditions are met and the Data Element is not included. - When the specified conditions are not met, Type 1C elements shall not be included in the Data Set. + IODs and SOP Classes define Data Elements that shall be included under certain specified conditions. Type 1C Data Elements have the same requirements as Type 1 Data Elements under these conditions. It is a protocol violation if the specified conditions are met and the Data Element is not included. + When the specified conditions are not met, Type 1C Data Elements shall not be included in the Data Set.
Type 2 Required Data Elements - IODs and SOP Classes define Type 2 Data Elements that shall be included and are mandatory Data Elements. However, it is permissible that if a Value for a Type 2 element is unknown it can be encoded with zero Value Length and no Value. If the Value is known the Value Field shall contain that value as defined by the elements VR and VM as specified in . These Data Elements shall be included in the Data Set and their absence is a protocol violation. + IODs and SOP Classes define Type 2 Data Elements that shall be included and are mandatory Data Elements. However, it is permissible that if a Value for a Type 2 Data Element is unknown it can be encoded with zero Value Length and no Value. If the Value is known the Value Field shall contain that Value as defined by the Data Element's VR and VM as specified in . These Data Elements shall be included in the Data Set and their absence is a protocol violation. - The intent of Type 2 Data Elements is to allow a zero length to be conveyed when the operator or application does not know its value or has a specific reason for not specifying its value. It is the intent that the device should support these Data Elements. + The intent of Type 2 Data Elements is to allow a zero length to be conveyed when the operator or application does not know its Value or has a specific reason for not specifying its Value. It is the intent that the device should support these Data Elements. A Type 2 Sequence Data Element will contain zero or more Items, as defined by the IOD (irrespective of the VM of the Sequence, which is always one ()). An empty Type 2 Sequence is one with no Items, as opposed to an Item that is present but empty. Whether or not Items may be empty (contain no Data Elements) depends on the IOD definition of the Data Set for each Item, rather than the Type of the enclosing Sequence Data Element. @@ -3048,19 +3113,19 @@
Type 2C Conditional Data Elements - IODs and SOP Classes define Type 2C elements that have the same requirements as Type 2 elements under certain specified conditions. It is a protocol violation if the specified conditions are met and the Data Element is not included. - When the specified conditions are not met, Type 2C elements shall not be included in the Data Set. + IODs and SOP Classes define Type 2C Data Elements that have the same requirements as Type 2 Data Elements under certain specified conditions. It is a protocol violation if the specified conditions are met and the Data Element is not included. + When the specified conditions are not met, Type 2C Data Elements shall not be included in the Data Set. An example of a Type 2C Data Element is Inversion Time (0018,0082). For several SOP Class Definitions, this Data Element is required only if the Scanning Sequence (0018,0020) has the Value "IR." It is not required otherwise. See .
Type 3 Optional Data Elements - IODs and SOP Classes define Type 3 Data Elements that are optional Data Elements. Absence of a Type 3 element from a Data Set does not convey any significance and is not a protocol violation. Type 3 elements may also be encoded with zero length and no Value. The meaning of a zero length Type 3 Data Element shall be precisely the same as that element being absent from the Data Set. + IODs and SOP Classes define Type 3 Data Elements that are optional Data Elements. Absence of a Type 3 Data Element from a Data Set does not convey any significance and is not a protocol violation. Type 3 Data Elements may also be encoded with zero length and no Value. The meaning of a zero length Type 3 Data Element shall be precisely the same as that Data Element being absent from the Data Set.
Data Element Types Within A Sequence - When an IOD defines a Sequence Data Element (see ), the Type of the Sequence attribute defines whether the Sequence attribute itself must be present, and the Attribute Description of the Sequence attribute may define whether and how many Items shall be present in the Sequence. The Types of the attributes of the Data Set included in the Sequence, including any conditionality, are specified within the scope of each Data Set, i.e., for each Item present in the Sequence. + When an IOD defines a Sequence Data Element (see ), the Type of the Sequence Attribute defines whether the Sequence Attribute itself must be present, and the Attribute Description of the Sequence Attribute may define whether and how many Items shall be present in the Sequence. The Types of the Attributes of the Data Set included in the Sequence, including any conditionality, are specified within the scope of each Data Set, i.e., for each Item present in the Sequence. @@ -3070,10 +3135,10 @@ Historically, many IODs declared Type 1 and Type 2 Data Elements of the Sequence to be Type 1C and Type 2C, respectively, with the condition that an Item is present. This is exactly the same as simply defining them as Type 1 and Type 2. - In particular, the conditionality constraint "Required if Sequence is sent" on the Type 1C or Type 2C Data Elements subsidiary to a Type 2 or 3 Sequence attribute does not imply that an Item must be present in the Sequence. These conditions are meant to be equivalent to "Required if a Sequence Item is present", and the conditionality is not strictly necessary. Any Type 2 or Type 3 Sequence attribute may be sent with zero length. + In particular, the conditionality constraint "Required if Sequence is sent" on the Type 1C or Type 2C Data Elements subsidiary to a Type 2 or 3 Sequence Attribute does not imply that an Item must be present in the Sequence. These conditions are meant to be equivalent to "Required if a Sequence Item is present", and the conditionality is not strictly necessary. Any Type 2 or Type 3 Sequence Attribute may be sent with zero length. - In particular, the conditionality constraint "Required if <name-of-parent-sequence-attribute> is sent" on the Type 1C or Type 2C Data Elements subsidiary to a Type 2 or 3 Sequence attribute does not imply that an Item must be present in the Sequence. These conditions are meant to be equivalent to "Required if a Sequence Item is present", and the conditionality is not strictly necessary. Any Type 2 or Type 3 Sequence attribute may be sent with zero length. + In particular, the conditionality constraint "Required if <name-of-parent-sequence-attribute> is sent" on the Type 1C or Type 2C Data Elements subsidiary to a Type 2 or 3 Sequence Attribute does not imply that an Item must be present in the Sequence. These conditions are meant to be equivalent to "Required if a Sequence Item is present", and the conditionality is not strictly necessary. Any Type 2 or Type 3 Sequence Attribute may be sent with zero length. @@ -3082,7 +3147,7 @@
Nesting of Data Sets The VR identified "SQ" shall be used for Data Elements with a Value consisting of a Sequence of zero or more Items, where each Item contains a set of Data Elements. SQ provides a flexible encoding scheme that may be used for simple structures of repeating sets of Data Elements, or the encoding of more complex Information Object Definitions often called folders. SQ Data Elements can also be used recursively to contain multi-level nested structures. - Items present in an SQ Data Element shall be an ordered set where each Item may be referenced by its ordinal position. Each Item shall be implicitly assigned an ordinal position starting with the value 1 for the first Item in the Sequence, and incremented by 1 with each subsequent Item. The last Item in the Sequence shall have an ordinal position equal to the number of Items in the Sequence. + Items present in an SQ Data Element shall be an ordered set where each Item may be referenced by its ordinal position. Each Item shall be implicitly assigned an ordinal position starting with the Value 1 for the first Item in the Sequence, and incremented by 1 with each subsequent Item. The last Item in the Sequence shall have an ordinal position equal to the number of Items in the Sequence. @@ -3097,13 +3162,13 @@ There are three special SQ related Data Elements that are not ruled by the VR encoding rules conveyed by the Transfer Syntax. They shall be encoded as Implicit VR. These special Data Elements are Item (FFFE,E000), Item Delimitation Item (FFFE,E00D), and Sequence Delimitation Item (FFFE,E0DD). However, the Data Set within the Value Field of the Data Element Item (FFFE,E000) shall be encoded according to the rules conveyed by the Transfer Syntax.
Item Encoding Rules - Each Item of a Data Element of Value Representation SQ shall be encoded as a DICOM Standard Data Element with a specific Data Element Tag of Value (FFFE,E000). The Item Tag is followed by a 4 byte Item Length field encoded in one of the following two ways: + Each Item of a Data Element of Value Representation SQ shall be encoded as a DICOM Standard Data Element with a specific Data Element Tag of Value (FFFE,E000). The Item Tag is followed by a 4 byte Value (Item) Length field encoded in one of the following two ways: - Explicit Length: The number of bytes (even) contained in the Sequence Item Value (following but not including the Item Length Field) is encoded as a 32-bit unsigned integer value (see ). This length shall include the total length of all Data Elements conveyed by this Item. This Item Length shall be equal to 00000000H if the Item contains no Data Set. + Explicit Length: The number of bytes (even) contained in the Sequence Item Value (following but not including the Value (Item) Length Field) is encoded as a 32-bit unsigned integer value (see ). This length shall include the total length of all Data Elements conveyed by this Item. This Value (Item) Length Field shall be equal to 00000000H if the Item contains no Data Set. - Undefined Length: The Item Length Field shall contain the value FFFFFFFFH to indicate an undefined Item length. It shall be used in conjunction with an Item Delimitation Data Element. This Item Delimitation Data Element has a Data Element Tag of (FFFE,E00D) and shall follow the Data Elements encapsulated in the Item. No Value shall be present in the Item Delimitation Data Element and its Length shall be 00000000H. An Item containing no Data Set is encoded by an Item Delimitation Data Element only. + Undefined Length: The Value (Item) Length Field shall contain the value FFFFFFFFH to indicate an Undefined Length. It shall be used in conjunction with an Item Delimitation Data Element. This Item Delimitation Data Element has a Data Element Tag of (FFFE,E00D) and shall follow the Data Elements encapsulated in the Item. No Value shall be present in the Item Delimitation Data Element and its Value (Item) Length shall be 00000000H. An Item containing no Data Set is encoded by an Item Delimitation Data Element only. The encoder of a Data Set may choose either one of the two ways of encoding. Both ways of encoding shall be supported by decoders of Data Sets. Data Element Tags (FFFF,eeee) are reserved by this Standard and shall not be used. @@ -3120,15 +3185,15 @@ Delimitation of the last Item of a Sequence of Items, encapsulated in a Data Element of Value Representation SQ, shall be in one of the two following ways: - Explicit Length: The number of bytes (even) contained in the Data Element Value (following but not including the Data Element Length Field) is encoded as a 32-bit unsigned integer value (see ). This length shall include the total length resulting from the sequence of zero or more items conveyed by this Data Element. This Data Element Length shall be equal to 00000000H if the sequence of Items contains zero Items. + Explicit Length: The number of bytes (even) contained in the Data Element Value (following but not including the Value (Sequence) Length Field) is encoded as a 32-bit unsigned integer value (see ). This length shall include the total length resulting from the sequence of zero or more items conveyed by this Data Element. This Data Element Length shall be equal to 00000000H if the sequence of Items contains zero Items. - Undefined Length: The Data Element Length Field shall contain a Value FFFFFFFFH to indicate an Undefined Sequence length. It shall be used in conjunction with a Sequence Delimitation Item. A Sequence Delimitation Item shall be included after the last Item in the sequence. Its Item Tag shall be (FFFE,E0DD) with an Item Length of 00000000H. No Value shall be present. A Sequence containing zero Items is encoded by a Sequence Delimitation Item only. + Undefined Length: The Value (Sequence) Length Field shall contain a Value FFFFFFFFH to indicate a Sequence of Undefined Length. It shall be used in conjunction with a Sequence Delimitation Item. A Sequence Delimitation Item shall be included after the last Item in the sequence. Its Item Tag shall be (FFFE,E0DD) with a Value (Item) Length Field of 00000000H. No Value shall be present. A Sequence containing zero Items is encoded by a Sequence Delimitation Item only. The encoder of a Sequence of Items may choose either one of the two ways of encoding. Both ways of encoding shall be supported by decoders of the Sequence of Items. - The Sequence Delimitation Item Tag (FFFE,E0DD) is different from the Item Delimitation Tag (FFFE,E00D) introduced above in that it indicates the end of a Sequence of Items whose Length was left undefined. If an undefined length Item is the last Item of a Sequence of Items of undefined length, then an Item Delimitation Tag will be followed by a Sequence Delimitation Tag. + The Sequence Delimitation Item Tag (FFFE,E0DD) is different from the Item Delimitation Tag (FFFE,E00D) introduced above in that it indicates the end of a Sequence of Items whose Length was left undefined. If an Undefined Length Item is the last Item of a Sequence of Items of Undefined Length, then an Item Delimitation Tag will be followed by a Sequence Delimitation Tag. For an example of an SQ Data Element of Explicit Length encapsulating Items of Explicit Length see . For an example of an SQ Data Element of Undefined Length encapsulating Items of Explicit Length see . @@ -3282,7 +3347,7 @@ 0000H Reserved
@@ -3737,7 +3802,7 @@
Encoding of Private Elements - The Value Representations used for Private Data Elements shall be the same as those VRs specified for Standard Data Elements in . The encoding shall conform to the requirements for those VRs and shall be in accordance with the negotiated Transfer Syntax. A Private Data Element with SQ VR (a Private Data Sequence) may include Items with both Standard and Private Data Elements. Standard Data Elements used within a Private Data Sequence shall use the VRs as defined in for those data elements. + The Value Representations used for Private Data Elements shall be the same as those VRs specified for Standard Data Elements in . The encoding shall conform to the requirements for those VRs and shall be in accordance with the negotiated Transfer Syntax. A Private Data Element with SQ VR (a Private Data Sequence) may include Items with both Standard and Private Data Elements. Standard Data Elements used within a Private Data Sequence shall use the VRs as defined in for those Data Elements. The semantics of Standard Data Elements within a Private Data Sequence, and the definition of Attribute Values, are implementation dependent. For a Standard Extended SOP Class the Attributes Pixel Data (7FE0,0010), Float Pixel Data (7FE0,0008), Double Float Pixel Data (7FE0,0009), Waveform Data (5400,1010) and Overlay Data (60xx,3000) shall not be included within a Private Sequence Item, nor within a standard Sequence Item nested directly or indirectly within a Private Sequence Item.
@@ -3747,13 +3812,13 @@ Encoding of Pixel, Overlay and Waveform Data
Pixel and Overlay Data, and Related Data Elements - Pixel Data (7FE0,0010), Float Pixel Data (7FE0,0008), Double Float Pixel Data (7FE0,0009) and Overlay Data (60xx,3000) shall be used for the exchange of encoded graphical image data. These elements along with additional Data Elements, specified as Attributes of the Image Information Entities defined in , shall be used to describe the way in which the Pixel Data and Overlay Data are encoded and shall be interpreted. Finally, depending on the negotiated Transfer Syntax (see and ), Pixel Data may be compressed. + Pixel Data (7FE0,0010), Float Pixel Data (7FE0,0008), Double Float Pixel Data (7FE0,0009) and Overlay Data (60xx,3000) shall be used for the exchange of encoded graphical image data. These Data Elements along with additional Data Elements, specified as Attributes of the Image Information Entities defined in , shall be used to describe the way in which the Pixel Data and Overlay Data are encoded and shall be interpreted. Finally, depending on the negotiated Transfer Syntax (see and ), Pixel Data may be compressed. Pixel Data (7FE0,0010) and Overlay Data (60xx,3000) have a VR of OW or OB, depending on the negotiated Transfer Syntax (see ). The only difference between OW and OB being that OB, an octet-stream, shall be unaffected by Byte Ordering (see ). Float Pixel Data (7FE0,0008) has a Value Representation of OF. Double Float Pixel Data (7FE0,0009) has a Value Representation of OD. - For Pixel Data values encoded in OF + For Pixel Data Values encoded in OF and OD, any value that is permitted by the IEEE 754:1985 may be used, including NaN, +ve Infinity and -ve Infinity. See @@ -3807,13 +3872,13 @@ Restrictions are placed on acceptable Values for Bits Allocated (0028,0100) for Float Pixel Data (7FE0,0008) and Double Float Pixel Data (7FE0,0009), such that only a single Pixel Cell entirely occupies the allocated bits specified by Bits Allocated (0028,0100), hence Bits Stored (0028,0101) and High Bit (0028,0102) are not sent. Also, the Value Field containing Pixel Data, like all other Value Fields in DICOM, shall be an even number of bytes in length. This means that the Value Field may need to be padded with data that is not part of the image and shall not be considered significant. If needed, the padding bits shall be appended to the end of the Value Field, and shall be used only to extend the data to the next even byte increment of length. - The 32-bit Value Length Field limits the maximum size of large data values such as Pixel Data sent in a Native Format (encoded in Transfer Syntaxes that use only the unencapsulated form). + The 32-bit Value Length Field limits the maximum size of large data Value Fields such as Pixel Data sent in a Native Format (encoded in Transfer Syntaxes that use only the unencapsulated form). In a multi-frame object that is transmitted in Native Format, the individual frames are not padded. The individual frames shall be concatenated and padding bits (if necessary) applied to the complete Value Field. At least one frame shall be present. - Receiving applications should be aware that some older applications may send Pixel Data with excess padding, which was not explicitly prohibited in earlier versions of the Standard. Applications should be prepared to accept such Pixel Data elements, but may delete the excess padding. In no case should a sending application place private data in the padding data. + Receiving applications should be aware that some older applications may send Pixel Data with excess padding, which was not explicitly prohibited in earlier versions of the Standard. Applications should be prepared to accept such Pixel Data Data Elements, but may delete the excess padding. In no case should a sending application place private data in the padding data. - The field of bits representing the value of a Pixel Sample shall be a binary 2's complement integer or an unsigned integer, as specified by the Data Element Pixel Representation (0028,0103). The sign bit shall be the High Bit in a Pixel Sample Value that is a 2's complement integer. The minimum actual Pixel Sample Value encountered in the Pixel Data is specified by Smallest Image Pixel Value (0028,0106) while the maximum value is specified by Largest Image Pixel Value (0028,0107). + The field of bits representing the value of a Pixel Sample shall be a binary 2's complement integer or an unsigned integer, as specified by the Data Element Pixel Representation (0028,0103). The sign bit shall be the High Bit in a Pixel Sample Value that is a 2's complement integer. The minimum actual Pixel Sample Value encountered in the Pixel Data is specified by Smallest Image Pixel Value (0028,0106) while the maximum Value is specified by Largest Image Pixel Value (0028,0107).
Overlay Data Encoding of Related Data Elements @@ -3832,7 +3897,7 @@ There is no Data Element analogous to Bits Stored (0028,0101) since Overlay Planes always have a bit depth of 1. - Restrictions on the allowed values for these Data Elements are defined in . Formerly overlay data stored in unused bits of Pixel Data (7FE0,0010) was described, and these attributes had meaningful values but this usage has been retired. See PS3.5-2004. For overlays encoded in Overlay Data (60xx,3000), Overlay Bits Allocated (60xx,0100) is always 1 and Overlay Bit Position (60xx,0102) is always 0. + Restrictions on the allowed Values for these Data Elements are defined in . Formerly overlay data stored in unused bits of Pixel Data (7FE0,0010) was described, and these Attributes had meaningful Values but this usage has been retired. See PS3.5-2004. For overlays encoded in Overlay Data (60xx,3000), Overlay Bits Allocated (60xx,0100) is always 1 and Overlay Bit Position (60xx,0102) is always 0. @@ -3865,7 +3930,7 @@ - These values are not permitted because they are not encodable in an uncompressed form. + These Values are not permitted because they are not encodable in an uncompressed form. Pixel Data conveyed in the Float Pixel Data (7FE0,0008) or Double Float Pixel Data (7FE0,0009) shall be in a Native (uncompressed) Format if encoded in a Standard Transfer Syntax. @@ -3878,14 +3943,14 @@ - If Pixel Data (7FE0,0010) is sent in a Native Format, the Value Representation OW is most often required. The Value Representation OB may also be used for Pixel Data (7FE0,0010) in cases where Bits Allocated has a value less than or equal to 8, but only with Transfer Syntaxes where the Value Representation is explicitly conveyed (see ). + If Pixel Data (7FE0,0010) is sent in a Native Format, the Value Representation OW is most often required. The Value Representation OB may also be used for Pixel Data (7FE0,0010) in cases where Bits Allocated has a Value less than or equal to 8, but only with Transfer Syntaxes where the Value Representation is explicitly conveyed (see ). The DICOM Default Little Endian Transfer Syntax (Implicit VR Little Endian) does not explicitly convey Value Representation and therefore the VR of OB may not be used for Pixel Data (7FE0,0010) when using the Default Transfer Syntax. - The 32-bit Value Length Field limits the maximum size of large data values such as Pixel Data sent in a Native Format. + The 32-bit Value Length Field limits the maximum size of large data Value Fields such as Pixel Data sent in a Native Format. @@ -3919,13 +3984,33 @@ - If sent in an Encapsulated Format (i.e., other than the Native Format) the Value Representation OB is used. The Pixel Cells are encoded according to the encoding process defined by one of the negotiated Transfer Syntaxes (see ). The encapsulated pixel stream of encoded pixel data is segmented into one or more Fragments, each of which conveys its own explicit length. The sequence of Fragments of the encapsulated pixel stream is terminated by a delimiter, thus allowing the support of encoding processes where the resulting length of the entire pixel stream is not known until it is entirely encoded. This Encapsulated Format supports both Single-Frame and Multi-Frame images (as defined in ). At least one frame shall be present, and hence at least one fragment will be present. + If sent in an Encapsulated Format (i.e., other than the Native Format) the Value Representation OB is used. + The Pixel Cells are encoded according to the encoding process defined by one of the negotiated Transfer Syntaxes (see ). + A Fragmentable Encapsulated Transfer Syntax allows the encapsulated pixel stream of encoded pixel data to be split into one or more Fragments. + A Non-Fragmentable Encapsulated Transfer Syntax requires the entire encapsulated pixel stream of encoded pixel data to be encoded in a single Fragment. + Each Fragment conveys its own explicit even length (see ). + The Sequence of Fragments of the encapsulated pixel stream is terminated by a Sequence Delimiter Item, + thus allowing the support of encoding processes where the resulting length of the entire pixel stream is not known until it is entirely encoded. + Encapsulated Formats support both Single-Frame and Multi-Frame images (as defined in ). + At least one Frame shall be present, and hence at least one Fragment will be present. - Depending on the Transfer Syntax, a frame may be entirely contained within a single fragment, or may span multiple fragments to support buffering during compression or to avoid exceeding the maximum size of a fixed length fragment. A recipient can detect fragmentation of frames by comparing the number of fragments (the number of Items minus one for the Basic Offset Table) with the number of frames. Some performance optimizations may be available to a recipient in the absence of fragmentation of frames, but an implementation that fails to support such fragmentation does not conform to the Standard. + + + Depending on the Fragmentable Encapsulated Transfer Syntax, + a frame may be entirely contained within a single fragment, or may span multiple fragments to support buffering during compression or to avoid exceeding the maximum size of a fixed length fragment. + A recipient can detect fragmentation of frames by comparing the number of fragments (the number of Items minus one for the Basic Offset Table) with the number of frames. + Some performance optimizations may be available to a recipient in the absence of fragmentation of frames, + but an implementation that fails to support such fragmentation does not conform to the Standard. + + + The total size of the encapsulated pixel stream, not including any trailing padding in the last Fragment, if known, may be encoded in Encapsulated Pixel Data Value Total Length (7FE0,0003); + see and . + +
JPEG Image Compression - DICOM provides a mechanism for supporting the use of JPEG Image Compression through the Encapsulated Format (see ). defines a number of Transfer Syntaxes that reference the JPEG Standard and provide a number of lossless (bit preserving) and lossy compression schemes. + DICOM provides a mechanism for supporting the use of JPEG Image Compression through the Encapsulated Format. defines a number of Transfer Syntaxes that reference the JPEG Standard and provide a number of lossless (bit preserving) and lossy compression schemes. The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for JPEG lossy compression is also beyond the scope of this Standard. @@ -3944,8 +4029,8 @@ The DICOM conformance statement shall differentiate whether or not the implementation is capable of simply receiving or receiving and processing JPEG encoded images (see ). - The use of the DICOM Encapsulated Format to support JPEG Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream. - The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from ) are specified in and . No other Standard Photometric Interpretation values shall be used. + The use of the DICOM Encapsulated Format to support JPEG Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream. + The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from ) are specified in and . No other Standard Photometric Interpretation Values shall be used.
Standard SOP Classes
- IOD Specification (defined in - ) - + IOD Specification (defined in )
- Generic Implant Template Storage - + Generic Implant Template Storage 1.2.840.10008.5.1.4.43.1 @@ -66411,8 +47998,7 @@
- Implant Assembly Template Storage - + Implant Assembly Template Storage 1.2.840.10008.5.1.4.44.1 @@ -66425,8 +48011,7 @@
- Implant Template Group Storage - + Implant Template Group Storage 1.2.840.10008.5.1.4.45.1 @@ -66439,13 +48024,10 @@
- CT Defined Procedure Protocol - Storage - + CT Defined Procedure Protocol Storage - 1.2.840.10008.5.1.4.1.1.200.1 - + 1.2.840.10008.5.1.4.1.1.200.1 @@ -66458,8 +48040,7 @@ Protocol Approval Storage - 1.2.840.10008.5.1.4.1.1.200.3 - + 1.2.840.10008.5.1.4.1.1.200.3 @@ -66469,13 +48050,10 @@
- XA Defined Procedure Protocol - Storage - + XA Defined Procedure Protocol Storage - 1.2.840.10008.5.1.4.1.1.200.7 - + 1.2.840.10008.5.1.4.1.1.200.7 @@ -66488,8 +48066,7 @@ Inventory Storage - 1.2.840.10008.5.1.4.1.1.201.1 - + 1.2.840.10008.5.1.4.1.1.201.1 @@ -66502,61 +48079,22 @@
Behavior - This Section defines the SCU and SCP behavior for - the Non-Patient Object Storage Service. The C-STORE DIMSE-C Service shall be the mechanism used to - transfer SOP Instances between peer DICOM AEs as described in. - - In addition to the behaviors specified in this - section, there may be SOP Class specific behavior requirements, as described in - . - + This Section defines the SCU and SCP behavior for the Non-Patient Object Storage Service. The C-STORE DIMSE-C Service shall be the mechanism used to transfer SOP Instances between peer DICOM AEs as described in . + In addition to the behaviors specified in this section, there may be SOP Class specific behavior requirements, as described in .
Service Class User - A DICOM AE that claims conformance to any of - the Non-Patient Object Storage SOP Classes as an SCU shall be capable of sending a SOP Instance that - meets the requirements of the related IOD. The Service shall be invoked by the SCU through the use - of the DIMSE C-STORE request used in conjunction with the SOP Class. - - The SCU shall recognize the status of the - C-STORE service and take appropriate action based on the success or failure of the service. The - Non-Patient Object Storage Service places no further requirements on what the SCU shall do other - than that it shall distinguish between successful and failed C-STORE responses. This behavior shall - be documented as part of the Conformance Statement. - + A DICOM AE that claims conformance to any of the Non-Patient Object Storage SOP Classes as an SCU shall be capable of sending a SOP Instance that meets the requirements of the related IOD. The Service shall be invoked by the SCU through the use of the DIMSE C-STORE request used in conjunction with the SOP Class. + The SCU shall recognize the status of the C-STORE service and take appropriate action based on the success or failure of the service. The Non-Patient Object Storage Service places no further requirements on what the SCU shall do other than that it shall distinguish between successful and failed C-STORE responses. This behavior shall be documented as part of the Conformance Statement.
Service Class Provider - A DICOM AE that claims conformance to any of - the Non-Patient Object Storage SOP Classes as an SCP shall receive and store a SOP Instance through - the use of the DIMSE C-STORE service used in conjunction with the specific SOP Class. - - The SCP shall store and provide access to all - Type 1, Type 2, and Type 3 Attributes defined in the IOD, as well as any Standard Extended - Attributes (including Private Attributes) included in the SOP Instance. The SCP may, but is not - required to validate that the Attributes of the SOP Instance meet the requirements of the associated - IOD. - - The SCP shall not modify the values of any - Attributes in the SOP Instance without assigning a new SOP Instance UID, except that the SCP may - modify values of, or add, Type 3 and Private Attributes that do not change the semantics or - interpretation of the SOP Instance. - + A DICOM AE that claims conformance to any of the Non-Patient Object Storage SOP Classes as an SCP shall receive and store a SOP Instance through the use of the DIMSE C-STORE service used in conjunction with the specific SOP Class. + The SCP shall store and provide access to all Type 1, Type 2, and Type 3 Attributes defined in the IOD, as well as any Standard Extended Attributes (including Private Attributes) included in the SOP Instance. The SCP may, but is not required to validate that the Attributes of the SOP Instance meet the requirements of the associated IOD. + The SCP shall not modify the values of any Attributes in the SOP Instance without assigning a new SOP Instance UID, except that the SCP may modify values of, or add, Type 3 and Private Attributes that do not change the semantics or interpretation of the SOP Instance. - E.g., an SCP may add values to Alternate - Content Description Sequence (0070,0087), to provide an additional description in another - language. - + E.g., an SCP may add values to Alternate Content Description Sequence (0070,0087), to provide an additional description in another language. - The SCP shall return, via the C-STORE response - primitive, the Response Status Code applicable to the associated request. By performing this service - successfully, the SCP indicates that the SOP Instance has been successfully stored. - - defines the specific response status code values that might be returned in a C-STORE response. - General status code values and fields related to status code values are defined for C-STORE DIMSE - Service in. - + The SCP shall return, via the C-STORE response primitive, the Response Status Code applicable to the associated request. By performing this service successfully, the SCP indicates that the SOP Instance has been successfully stored. defines the specific response status code values that might be returned in a C-STORE response. General status code values and fields related to status code values are defined for C-STORE DIMSE Service in . @@ -66581,8 +48119,7 @@ Failure
C-STORE Response Status Values
- Refused: Out of resources - + Refused: Out of resources A700 @@ -66593,9 +48130,7 @@
- Error: Data Set does not match - SOP Class - + Error: Data Set does not match SOP Class A900 @@ -66632,145 +48167,85 @@
- Status Codes are returned in DIMSE response - messages (see). The - code values stated in column "Status Codes" are returned in Status Command Element (0000,0900). - + Status Codes are returned in DIMSE response messages (see ). The code values stated in column "Status Codes" are returned in Status Command Element (0000,0900).
Conformance Statement Requirements - An implementation may conform to any of the - Non-Patient Object Storage SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the - format defined in. - + An implementation may conform to any of the Non-Patient Object Storage SOP Classes as an SCU, SCP or both. The Conformance Statement shall be in the format defined in .
SCU Conformance Requirements - An implementation that conforms to a SOP Class - of the Non-Patient Object Storage Service as an SCU shall state in its Conformance Statement: - + An implementation that conforms to a SOP Class of the Non-Patient Object Storage Service as an SCU shall state in its Conformance Statement: - Whether the implementation is a SOP - Instance creator for the SOP Class. - + Whether the implementation is a SOP Instance creator for the SOP Class. - There may be SOP Class specific - Conformance Statement requirements for creators of SOP Instances. See. - + There may be SOP Class specific Conformance Statement requirements for creators of SOP Instances. See . - The behavior of the SCU in the case of - a success C-STORE response status. - + The behavior of the SCU in the case of a success C-STORE response status. - The behavior of the SCU in each case of - a failure C-STORE response status. - + The behavior of the SCU in each case of a failure C-STORE response status.
SCP Conformance Requirements - An implementation that conforms to a SOP Class - of the Non-Patient Object Storage Service as an SCP shall state in its Conformance Statement: - + An implementation that conforms to a SOP Class of the Non-Patient Object Storage Service as an SCP shall state in its Conformance Statement: - The behavior of the SCP in the case of - a successful C-STORE operation, including the access method for a stored SOP Instance, and - the duration of the storage. - + The behavior of the SCP in the case of a successful C-STORE operation, including the access method for a stored SOP Instance, and the duration of the storage. - The meaning of each case of a failure - C-STORE response status, as well as appropriate recovery action. - + The meaning of each case of a failure C-STORE response status, as well as appropriate recovery action. - There may be SOP Class specific Conformance - Statement requirements for applications that interpret the SOP Instances for display or further - processing. See. - + There may be SOP Class specific Conformance Statement requirements for applications that interpret the SOP Instances for display or further processing. See .
Application Behavior for Standard SOP Classes - This section specifies SOP Class specific behaviors - for conformant applications. - + This section specifies SOP Class specific behaviors for conformant applications.
Hanging Protocol SOP Class
Instance Creator - An implementation that conforms to the - Hanging Protocol Storage SOP Class as an SCU and is a SOP Instance creator shall state in its - Conformance Statement: - + An implementation that conforms to the Hanging Protocol Storage SOP Class as an SCU and is a SOP Instance creator shall state in its Conformance Statement: - The manner in which the values of - the Hanging Protocol IOD Attributes are derived from displayed images, layouts, operator - intervention or defaults. - + The manner in which the values of the Hanging Protocol IOD Attributes are derived from displayed images, layouts, operator intervention or defaults. - Any Private Attributes that are - used as the value of Selector Attribute (0072,0026) in the Image Set Selector Sequence, - Filter Operations Sequence or Sorting Operations Sequence. - + Any Private Attributes that are used as the value of Selector Attribute (0072,0026) in the Image Set Selector Sequence, Filter Operations Sequence or Sorting Operations Sequence. - The optional Attributes that may be - included in a Hanging Protocol SOP Instance. - + The optional Attributes that may be included in a Hanging Protocol SOP Instance.
Display Application - An implementation that conforms to the - Hanging Protocol Storage SOP Class as an SCP and interprets the contents of instances of the SOP - Class to control the display of images, shall apply all mandatory Hanging Protocol and - presentation intent Attributes to the sets of displayed images. Such an implementation shall - state in its Conformance Statement: - + An implementation that conforms to the Hanging Protocol Storage SOP Class as an SCP and interprets the contents of instances of the SOP Class to control the display of images, shall apply all mandatory Hanging Protocol and presentation intent Attributes to the sets of displayed images. Such an implementation shall state in its Conformance Statement: - The range of display environments - that the application will support (e.g., number of screens, size of screens, overlapping - image boxes). - + The range of display environments that the application will support (e.g., number of screens, size of screens, overlapping image boxes). - The optional Attributes of the - Hanging Protocol IOD that it is capable of interpreting and those that are not - supported. - + The optional Attributes of the Hanging Protocol IOD that it is capable of interpreting and those that are not supported. - Description of application behavior - when the value of Partial Data Display Handling (0072,0208) is ADAPT_LAYOUT or zero - length. - + Description of application behavior when the value of Partial Data Display Handling (0072,0208) is ADAPT_LAYOUT or zero length. - Description of application behavior - when the display environment of the Hanging Protocol Instance differs from the display - environment of the application, with respect to preserving layout versus spatial - resolution. - + Description of application behavior when the display environment of the Hanging Protocol Instance differs from the display environment of the application, with respect to preserving layout versus spatial resolution. - The Image Storage SOP Classes for - which the Hanging Protocol Storage SOP Class is supported for display control. - + The Image Storage SOP Classes for which the Hanging Protocol Storage SOP Class is supported for display control.
@@ -66779,76 +48254,45 @@ Color Palette Storage SOP Class
Instance Creator - An implementation that conforms to the - Color Palette Storage SOP Class as an SCU and is a SOP Instance creator shall state in its - Conformance Statement: - + An implementation that conforms to the Color Palette Storage SOP Class as an SCU and is a SOP Instance creator shall state in its Conformance Statement: - The optional Attributes that may be - included in a Color Palette SOP Instance. - + The optional Attributes that may be included in a Color Palette SOP Instance.
Display Application - An implementation that conforms to the - Color Palette Storage SOP Class as an SCP and interprets the contents of instances of the SOP - Class to affect the display of images, shall apply all mandatory Color Palette and presentation - intent Attributes to the applicable displayed images. - - An implementation that conforms to the - Color Palette Storage SOP Class as an SCP and interprets the contents of instances of the SOP - Class to affect the display of images shall state in its Conformance Statement: - + An implementation that conforms to the Color Palette Storage SOP Class as an SCP and interprets the contents of instances of the SOP Class to affect the display of images, shall apply all mandatory Color Palette and presentation intent Attributes to the applicable displayed images. + An implementation that conforms to the Color Palette Storage SOP Class as an SCP and interprets the contents of instances of the SOP Class to affect the display of images shall state in its Conformance Statement: - The optional Attributes of the - Color Palette IOD that it is capable of interpreting and those that are not supported. - + The optional Attributes of the Color Palette IOD that it is capable of interpreting and those that are not supported. - The Image Storage SOP Classes for - which application of the Color Palette Storage SOP Class is supported - + The Image Storage SOP Classes for which application of the Color Palette Storage SOP Class is supported
Template Storage SOP Classes - An implementation that is a Generic Implant - Template Storage, Implant Assembly Template Storage, or Implant Template Group Storage SOP Class SCU - may modify information in a SOP Instance that it has previously sent or received. When this SOP - Instance is modified and sent to an SCP, it shall be assigned a new SOP Instance UID if there is - addition, removal or update of any Attribute within: - + An implementation that is a Generic Implant Template Storage, Implant Assembly Template Storage, or Implant Template Group Storage SOP Class SCU may modify information in a SOP Instance that it has previously sent or received. When this SOP Instance is modified and sent to an SCP, it shall be assigned a new SOP Instance UID if there is addition, removal or update of any Attribute within: - Generic Implant Template Description - Module - + Generic Implant Template Description Module - Generic Implant Template 2D Drawings - Module - + Generic Implant Template 2D Drawings Module - Generic Implant Template 3D Models - Module - + Generic Implant Template 3D Models Module - Generic Implant Template Mating - Features Module - + Generic Implant Template Mating Features Module - Generic Implant Template Planning - Landmarks Module - + Generic Implant Template Planning Landmarks Module Implant Assembly Template Module @@ -66860,75 +48304,45 @@ Surface Mesh Module - Referential integrity between sets of related - SOP instances shall be maintained. - + Referential integrity between sets of related SOP instances shall be maintained.
CT and XA Defined Procedure Protocol Storage SOP Class - An implementation that conforms to the CT - and/or XA Defined Procedure Protocol Storage SOP Classes as an SCP shall not modify constraints for - which the value of the Modifiable Constraint Flag (0082,0038) is NO. - - Modifying protocol constraints changes the - semantics of a CT or XA Defined Procedure Protocol Storage SOP Instance. - + An implementation that conforms to the CT and/or XA Defined Procedure Protocol Storage SOP Classes as an SCP shall not modify constraints for which the value of the Modifiable Constraint Flag (0082,0038) is NO. + Modifying protocol constraints changes the semantics of a CT or XA Defined Procedure Protocol Storage SOP Instance.
Protocol Approval Storage SOP Class - Approvals are based on assertions. Receipt or - generation of an assertion will interact with organizational authentication and authorization - policies. For example, an approval may be received by mistake as part of the transfer of a patient - record. - + Approvals are based on assertions. Receipt or generation of an assertion will interact with organizational authentication and authorization policies. For example, an approval may be received by mistake as part of the transfer of a patient record.
Inventory Storage SOP Class
Instance Creator - An implementation that conforms to the - Inventory Storage SOP Class as an SCU and is a SOP Instance creator shall state in its - Conformance Statement: - + An implementation that conforms to the Inventory Storage SOP Class as an SCU and is a SOP Instance creator shall state in its Conformance Statement: - The mechanisms by which creation of - Inventory SOP Instances is initiated. - + The mechanisms by which creation of Inventory SOP Instances is initiated. - Policies/parameters for splitting a - logical inventory across multiple Inventory SOP Instances. - + Policies/parameters for splitting a logical inventory across multiple Inventory SOP Instances. - Any limitations on the Inventory - Level (0008,0403) of the Inventory SOP Instances. - + Any limitations on the Inventory Level (0008,0403) of the Inventory SOP Instances. - Any non-DICOM mechanisms used to - access Inventoried SOP Instances that may be specified by a Stored Instance URI, - including protocols (such as NFS, SMB, or HTTP), and use of folders and/or container - files (ZIP, TAR, GZIP, TARGZIP, BLOB) for the SOP Instances. - + Any non-DICOM mechanisms used to access Inventoried SOP Instances that may be specified by a Stored Instance URI, including protocols (such as NFS, SMB, or HTTP), and use of folders and/or container files (ZIP, TAR, GZIP, TARGZIP, BLOB) for the SOP Instances. - Policies/parameters for duration of - retention, or for deletion, of created Inventory SOP Instances. - + Policies/parameters for duration of retention, or for deletion, of created Inventory SOP Instances. - Whether it provides records for - entities in multiple repositories (federation), and how it handles differences in - support for Attribute matching across those repositories in constructing Inventory SOP - Instances. - + Whether it provides records for entities in multiple repositories (federation), and how it handles differences in support for Attribute matching across those repositories in constructing Inventory SOP Instances. -
+
- + @@ -66938,153 +48352,78 @@ Overview
Scope - The Defined Procedure Protocol Query/Retrieve - Service Classes define application-level classes-of-service that facilitate access to Defined - Procedure Protocol composite objects. - + The Defined Procedure Protocol Query/Retrieve Service Classes define application-level classes-of-service that facilitate access to Defined Procedure Protocol composite objects.
Conventions - Key Attributes serve two purposes; they may be - used as Matching Key Attributes or as Return Key Attributes. Matching Key Attributes may be used for - matching (criteria to be used in the C-FIND request to determine whether an entity matches the - query). Return Key Attributes may be used to specify desired return Attributes (what elements in - addition to the Matching Key Attributes have to be returned in the C-FIND response). - + Key Attributes serve two purposes; they may be used as Matching Key Attributes or as Return Key Attributes. Matching Key Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether an entity matches the query). Return Key Attributes may be used to specify desired return Attributes (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND response). - Matching Keys are typically used in an SQL - 'WHERE' clause. Return Keys are typically used in an SQL 'SELECT' clause to convey the Attribute - Values. - + Matching Keys are typically used in an SQL 'WHERE' clause. Return Keys are typically used in an SQL 'SELECT' clause to convey the Attribute Values. - Matching Key Attributes may be of Type - "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in - . - + Matching Key Attributes may be of Type "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in .
Query/Retrieve Information Model - In order to serve as an SCP of the Defined - Procedure Protocol Query/Retrieve Service Class, a DICOM AE possesses information about the - Attributes of a number of Defined Procedure Protocol composite SOP Instances. The information is - organized into an Information Model. The Information Models for the different SOP Classes specified - in this Annex are defined in. - + In order to serve as an SCP of the Defined Procedure Protocol Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of Defined Procedure Protocol composite SOP Instances. The information is organized into an Information Model. The Information Models for the different SOP Classes specified in this Annex are defined in .
Service Definition - Two peer DICOM AEs implement a SOP Class of a - Defined Procedure Protocol Query/Retrieve Service Class with one serving in the SCU role and one - serving in the SCP role. SOP Classes of the Defined Procedure Protocol Query/Retrieve Service - Classes are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in. - - An SCP of this SOP Class shall support Level-2 - conformance as defined in. - - The semantics of the C-FIND service are the - same as those defined in the Service Definition of the Basic Worklist Management Service Class. - - The semantics of the C-MOVE service are the - same as those defined in the Service Definition of the Query/Retrieve Service Class, with the - exception that there is only one level of retrieval. - - The semantics of the C-GET service are the same - as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception - that there is only one level of retrieval. - + Two peer DICOM AEs implement a SOP Class of a Defined Procedure Protocol Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Defined Procedure Protocol Query/Retrieve Service Classes are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in . + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . + The semantics of the C-FIND service are the same as those defined in the Service Definition of the Basic Worklist Management Service Class. + The semantics of the C-MOVE service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval. + The semantics of the C-GET service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval.
Defined Procedure Protocol Information Models Definitions - The Defined Procedure Protocol Information Models - are identified by the SOP Class negotiated at Association establishment time. Each SOP Class is composed - of both an Information Model and a DIMSE-C Service Group. - - The Defined Procedure Protocol Information Models - are defined in, with the Entity-Relationship Model - Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model - Definition of the Basic Worklist Management Service. - + The Defined Procedure Protocol Information Models are identified by the SOP Class negotiated at Association establishment time. Each SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + The Defined Procedure Protocol Information Models are defined in , with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model Definition of the Basic Worklist Management Service.
Defined Procedure Protocol Information Models - The Defined Procedure Protocol Information Models - are based upon a one level entity: - + The Defined Procedure Protocol Information Models are based upon a one level entity: - Defined Procedure Protocol object - instance. - + Defined Procedure Protocol object instance. - The Defined Procedure Protocol object instance - contains Attributes associated with the Procedure Protocol IE of the Composite IODs as defined in. - + The Defined Procedure Protocol object instance contains Attributes associated with the Procedure Protocol IE of the Composite IODs as defined in .
DIMSE-C Service Groups
C-FIND Operation - See the C-FIND Operation definition for the - , and substitute "Defined - Procedure Protocol" for "Worklist". The "Worklist" Search Method shall be used. - - The SOP Class UID identifies the Defined - Procedure Protocol Information Model against which the C-FIND is to be performed. The Key Attributes - and values allowable for the query are defined in the SOP Class definitions for the Defined - Procedure Protocol Information Model. - + See the C-FIND Operation definition for the , and substitute "Defined Procedure Protocol" for "Worklist". The "Worklist" Search Method shall be used. + The SOP Class UID identifies the Defined Procedure Protocol Information Model against which the C-FIND is to be performed. The Key Attributes and values allowable for the query are defined in the SOP Class definitions for the Defined Procedure Protocol Information Model.
Service Class User Behavior - No SOP Class specific SCU behavior is - defined. - + No SOP Class specific SCU behavior is defined.
Service Class Provider Behavior - No SOP Class specific SCP behavior is - defined. - + No SOP Class specific SCP behavior is defined.
C-MOVE Operation - See the C-MOVE Operation definition for the - . No Extended Behavior or - Relational-Retrieve is defined for the Defined Procedure Protocol Query/Retrieve Service Classes. - - Query/Retrieve Level (0008,0052) is not - relevant to the Defined Procedure Protocol Query/Retrieve Service Classes, and therefore shall not - be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance - UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-MOVE Operation definition for the . No Extended Behavior or Relational-Retrieve is defined for the Defined Procedure Protocol Query/Retrieve Service Classes. + Query/Retrieve Level (0008,0052) is not relevant to the Defined Procedure Protocol Query/Retrieve Service Classes, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
C-GET Operation - See the C-GET Operation definition for the. No Extended Behavior or - Relational-Retrieve is defined for the Defined Procedure Protocol Query/Retrieve Service Classes. - + See the C-GET Operation definition for the . No Extended Behavior or Relational-Retrieve is defined for the Defined Procedure Protocol Query/Retrieve Service Classes. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
Association Negotiation - See the Association Negotiation definition for the - . - + See the Association Negotiation definition for the .
SOP Class Definitions @@ -67092,10 +48431,7 @@ Defined Procedure Protocol Information Model
E/R Models - The Defined Procedure Protocol Information - Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Defined Procedure Protocol Instance. - + The Defined Procedure Protocol Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Defined Procedure Protocol Instance.
Defined Procedure Protocol Information Model E-R Diagram @@ -67110,9 +48446,7 @@
Defined Procedure Protocol Attributes - - defines the Attributes of the Defined Procedure Protocol Information Model. - + defines the Attributes of the Defined Procedure Protocol Information Model. @@ -67130,8 +48464,7 @@ Return Key Type @@ -67145,8 +48478,7 @@ @@ -67204,9 +48532,7 @@ @@ -67308,16 +48624,12 @@ 1 @@ -67574,9 +48843,7 @@ @@ -67638,9 +48899,7 @@ @@ -67821,119 +49057,52 @@
Conformance Requirements - An implementation may conform to one or - more of the Defined Procedure Protocol Query/Retrieve SOP Classes as an SCU or SCP. The - Conformance Statement shall be in the format defined in. - + An implementation may conform to one or more of the Defined Procedure Protocol Query/Retrieve SOP Classes as an SCU or SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - the Defined Procedure Protocol Information Model - FIND SOP Class shall support queries - against the Defined Procedure Protocol Information Model using the C-FIND SCU Behavior - described for the Basic Worklist Management Service Class (see - - and). - - An implementation that conforms to - the Defined Procedure Protocol Information Model - FIND SOP Class as an SCU shall state - in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall - list these Optional Return Key Attributes. - - An implementation that conforms to - the Defined Procedure Protocol Information Model - FIND SOP Class as an SCU shall state - in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when - encoding queries and interpreting responses. - + An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class shall support queries against the Defined Procedure Protocol Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see and ). + An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCU shall - support transfers against the Defined Procedure Protocol Information Model, using the - C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see - - and). - + An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCU shall support transfers against the Defined Procedure Protocol Information Model, using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
C-GET SCU Conformance - An implementation that conforms to - the Defined Procedure Protocol Information Model - GET SOP Class as an SCU shall support - transfers against the Defined Procedure Protocol Information Model, using the C-GET SCU - baseline behavior described for the Query/Retrieve Service Class (see). - + An implementation that conforms to the Defined Procedure Protocol Information Model - GET SOP Class as an SCU shall support transfers against the Defined Procedure Protocol Information Model, using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see ).
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall - support queries against the Defined Procedure Protocol Information Model, using the - C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see). - + An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall support queries against the Defined Procedure Protocol Information Model, using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see ). - The contents of the Model - Specification Sequence (0018,9912) would be useful to index for systems that support - query or selection of appropriate Protocols for specific systems. - + The contents of the Model Specification Sequence (0018,9912) would be useful to index for systems that support query or selection of appropriate Protocols for specific systems. - An implementation that conforms to - the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall state - in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall - list these Optional Return Key Attributes. - - An implementation that conforms to - the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall state - in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when - interpreting queries, performing matching and encoding responses. - + An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall state in its Conformance Statement whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to the Defined Procedure Protocol Information Model - FIND SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.
C-MOVE SCP Conformance - An implementation that conforms to - the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP shall - support transfers against the Defined Procedure Protocol Information Model, using the - C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see). - + An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP shall support transfers against the Defined Procedure Protocol Information Model, using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see ). - It is expected that a device - that does not match the contents of the Model Specification Sequence (0018,9912) - will not execute the Protocol. - + It is expected that a device that does not match the contents of the Model Specification Sequence (0018,9912) will not execute the Protocol. - An implementation that conforms to - the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP, which - generates transfers using the C-MOVE operation, shall state in its Conformance Statement - appropriate Storage Service Class, under which it shall support the C-STORE - sub-operations generated by the C-MOVE. - + An implementation that conforms to the Defined Procedure Protocol Information Model - MOVE SOP Class as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement appropriate Storage Service Class, under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - the Defined Procedure Protocol Information Model - GET SOP Class as an SCP shall support - retrievals against the Defined Procedure Protocol Information Model using the C-GET SCP - baseline behavior described for the Query/Retrieve Service Class in. - + An implementation that conforms to the Defined Procedure Protocol Information Model - GET SOP Class as an SCP shall support retrievals against the Defined Procedure Protocol Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class in .
SOP Classes - The SOP Classes of the Defined Procedure - Protocol Query/Retrieve Service Class identify the Information Models, and the DIMSE-C - operations supported. - + The SOP Classes of the Defined Procedure Protocol Query/Retrieve Service Class identify the Information Models, and the DIMSE-C operations supported.
Attributes for the Defined Procedure Protocol Information Model
- Remark / Matching Type - + Remark / Matching Type
- Specific Character Set - + Specific Character Set (0008,0005) @@ -67158,11 +48490,7 @@ 1C - This Attribute is required - if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- Custodial Organization - Sequence - + Custodial Organization Sequence (0040,A07C) @@ -67236,9 +48562,7 @@
- >Institution Code - Sequence - + >Institution Code Sequence (0008,0082) @@ -67250,25 +48574,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >>Include - - - +>>Include + +
- Responsible Group Code - Sequence - + Responsible Group Code Sequence (0008,0220) @@ -67280,18 +48599,15 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Potential Scheduled - Protocol Code Sequence - + Potential Scheduled Protocol Code Sequence (0018,9906) @@ -67329,25 +48641,20 @@ 1 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Potential Requested - Procedure Code Sequence - + Potential Requested Procedure Code Sequence (0018,9907) @@ -67359,25 +48666,20 @@ 1 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Potential Reasons for - Procedure - + Potential Reasons for Procedure (0018,9908) @@ -67392,9 +48694,7 @@
- Potential Reasons for - Procedure Code Sequence - + Potential Reasons for Procedure Code Sequence (0018,9909) @@ -67406,25 +48706,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Potential Diagnostic - Tasks - + Potential Diagnostic Tasks (0018,990A) @@ -67439,9 +48734,7 @@
- Predecessor Protocol - Sequence - + Predecessor Protocol Sequence (0018,990E) @@ -67456,9 +48749,7 @@
- >Referenced SOP Class - UID - + >Referenced SOP Class UID (0008,1150) @@ -67470,16 +48761,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP Instance - UID - + >Referenced SOP Instance UID (0008,1155) @@ -67491,15 +48778,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- Content Creator's Name - + Content Creator's Name (0070,0084) @@ -67511,15 +48795,12 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Instance Creation Date - + Instance Creation Date (0008,0012) @@ -67531,18 +48812,13 @@ 1 - Shall be retrieved with - Single Value or Range Matching. - - See Instance Creation Time - for further details. - + Shall be retrieved with Single Value or Range Matching. + See Instance Creation Time for further details.
- Instance Creation Time - + Instance Creation Time (0008,0013) @@ -67554,15 +48830,8 @@ 1 - Shall be retrieved with - Single Value or Range Matching. - - If both Instance Creation - Date and Instance Creation Time are specified for Range Matching, they are to be - treated as as if they were a single DateTime Attribute e.g.,the date range July - 5 to July 7 and the time range 10am to 6pm specifies the time period starting on - July 5, 10am until July 7, 6pm. - + Shall be retrieved with Single Value or Range Matching. + If both Instance Creation Date and Instance Creation Time are specified for Range Matching, they are to be treated as as if they were a single DateTime Attribute e.g.,the date range July 5 to July 7 and the time range 10am to 6pm specifies the time period starting on July 5, 10am until July 7, 6pm.
- Clinical Trial Sponsor - Name - + Clinical Trial Sponsor Name (0012,0010) @@ -67588,16 +48855,12 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Clinical Trial Protocol - ID - + Clinical Trial Protocol ID (0012,0020) @@ -67609,9 +48872,7 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- Model Specification - Sequence - + Model Specification Sequence (0018,9912) @@ -67667,16 +48926,12 @@ 1 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- >Manufacturer's Related - Model Group - + >Manufacturer's Related Model Group (0008,0222) @@ -67688,16 +48943,12 @@ 2 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- >Manufacturer's Model - Name - + >Manufacturer's Model Name (0008,1090) @@ -67709,15 +48960,12 @@ 2 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- >Software Versions - + >Software Versions (0018,1020) @@ -67729,15 +48977,12 @@ 2 - Shall be retrieved with - Single Value, Wild Card, or Universal Matching. - + Shall be retrieved with Single Value, Wild Card, or Universal Matching.
- >Device Serial Number - + >Device Serial Number (0018,1000) @@ -67759,8 +49004,7 @@
- Anatomic Region Sequence - + Anatomic Region Sequence (0008,2218) @@ -67772,25 +49016,20 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
- Primary Anatomic Structure - Sequence - + Primary Anatomic Structure Sequence (0008,2228) @@ -67802,18 +49041,15 @@ 2 - This Attribute shall be - retrieved with Sequence or Universal matching. - + This Attribute shall be retrieved with Sequence or Universal matching.
- >Include - - - +>Include + +
@@ -67949,35 +49118,26 @@ @@ -67992,155 +49152,78 @@ Overview
Scope - The Protocol Approval Query/Retrieve Service - Classes define application-level classes-of-service that facilitate access to Protocol Approval - composite objects. - + The Protocol Approval Query/Retrieve Service Classes define application-level classes-of-service that facilitate access to Protocol Approval composite objects.
Conventions - Key Attributes serve two purposes; they may be - used as Matching Key Attributes or as Return Key Attributes. Matching Key Attributes may be used for - matching (criteria to be used in the C-FIND request to determine whether an entity matches the - query). Return Key Attributes may be used to specify desired return Attributes (what elements in - addition to the Matching Key Attributes have to be returned in the C-FIND response). - + Key Attributes serve two purposes; they may be used as Matching Key Attributes or as Return Key Attributes. Matching Key Attributes may be used for matching (criteria to be used in the C-FIND request to determine whether an entity matches the query). Return Key Attributes may be used to specify desired return Attributes (what elements in addition to the Matching Key Attributes have to be returned in the C-FIND response). - Matching Keys are typically used in an SQL - 'where' clause. Return Keys are typically used in an SQL 'select' clause to convey the Attribute - Values. - + Matching Keys are typically used in an SQL 'where' clause. Return Keys are typically used in an SQL 'select' clause to convey the Attribute Values. - Matching Key Attributes may be of Type - "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in - . - + Matching Key Attributes may be of Type "required" (R) or "optional" (O). Return Key Attributes may be of Type 1, 1C, 2, 2C, 3 as defined in .
Query/Retrieve Information Model - In order to serve as an SCP of the Protocol - Approval Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a - number of Protocol Approval composite SOP Instances. The information is organized into an - Information Model. The Information Models for the different SOP Classes specified in this Annex are - defined in. - + In order to serve as an SCP of the Protocol Approval Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of Protocol Approval composite SOP Instances. The information is organized into an Information Model. The Information Models for the different SOP Classes specified in this Annex are defined in .
Service Definition - Two peer DICOM AEs implement a SOP Class of a - Protocol Approval Query/Retrieve Service Class with one serving in the SCU role and one serving in - the SCP role. SOP Classes of the Protocol Approval Query/Retrieve Service Classes are implemented - using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in - . - - An SCP of this SOP Class shall support Level-2 - conformance as defined in. - - The semantics of the C-FIND service are the - same as those defined in the Service Definition of the Basic Worklist Management Service Class. - - The semantics of the C-MOVE service are the - same as those defined in the Service Definition of the Query/Retrieve Service Class, with the - exception that there is only one level of retrieval. - - The semantics of the C-GET service are the same - as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception - that there is only one level of retrieval. - + Two peer DICOM AEs implement a SOP Class of a Protocol Approval Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. SOP Classes of the Protocol Approval Query/Retrieve Service Classes are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in . + An SCP of this SOP Class shall support Storage Level 2 (Full) as defined in . + The semantics of the C-FIND service are the same as those defined in the Service Definition of the Basic Worklist Management Service Class. + The semantics of the C-MOVE service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval. + The semantics of the C-GET service are the same as those defined in the Service Definition of the Query/Retrieve Service Class, with the exception that there is only one level of retrieval.
Protocol Approval Information Models Definitions - The Protocol Approval Information Models are - identified by the SOP Class negotiated at Association establishment time. Each SOP Class is composed of - both an Information Model and a DIMSE-C Service Group. - - The Protocol Approval Information Models are - defined in, with the Entity-Relationship Model - Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model - Definition of the Basic Worklist Management Service. - + The Protocol Approval Information Models are identified by the SOP Class negotiated at Association establishment time. Each SOP Class is composed of both an Information Model and a DIMSE-C Service Group. + The Protocol Approval Information Models are defined in , with the Entity-Relationship Model Definition and Key Attributes Definition analogous to those defined in the Worklist Information Model Definition of the Basic Worklist Management Service.
Protocol Approval Information Models - The Protocol Approval Information Models are based - upon a one level entity: - + The Protocol Approval Information Models are based upon a one level entity: Protocol Approval object instance. - The Protocol Approval object instance contains - Attributes associated with the Approval IE of the Composite IODs as defined in - . - + The Protocol Approval object instance contains Attributes associated with the Approval IE of the Composite IODs as defined in .
DIMSE-C Service Groups
C-FIND Operation - See the C-FIND Operation definition for the - Basic Worklist Management Service Class (), - and substitute "Approval" for "Worklist". The "Worklist" Search Method shall be used. - - The SOP Class UID identifies the Protocol - Approval Information Model against which the C-FIND is to be performed. The Key Attributes and - values allowable for the query are defined in the SOP Class definitions for the Protocol Approval - Information Model. - + See the C-FIND Operation definition for the Basic Worklist Management Service Class (), and substitute "Approval" for "Worklist". The "Worklist" Search Method shall be used. + The SOP Class UID identifies the Protocol Approval Information Model against which the C-FIND is to be performed. The Key Attributes and values allowable for the query are defined in the SOP Class definitions for the Protocol Approval Information Model.
Service Class User Behavior - No SOP Class specific SCU behavior is - defined. - + No SOP Class specific SCU behavior is defined.
Service Class Provider Behavior - No SOP Class specific SCP behavior is - defined. - + No SOP Class specific SCP behavior is defined.
C-MOVE Operation - See the C-MOVE Operation definition for the - Query/Retrieve Service Class (). No Extended - Behavior or Relational-Retrieve is defined for the Protocol Approval Query/Retrieve Service Classes. - - Query/Retrieve Level (0008,0052) is not - relevant to the Protocol Approval Query/Retrieve Service Classes, and therefore shall not be present - in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID - (0008,0018). The SCU shall supply one UID or a list of UIDs. - + See the C-MOVE Operation definition for the Query/Retrieve Service Class (). No Extended Behavior or Relational-Retrieve is defined for the Protocol Approval Query/Retrieve Service Classes. + Query/Retrieve Level (0008,0052) is not relevant to the Protocol Approval Query/Retrieve Service Classes, and therefore shall not be present in the Identifier. The only Unique Key Attribute of the Identifier shall be SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
C-GET Operation - See the C-GET Operation definition for the - Query/Retrieve Service Class (). No Extended - Behavior or Relational-Retrieve is defined for the Protocol Approval Query/Retrieve Service Classes. - + See the C-GET Operation definition for the Query/Retrieve Service Class (). No Extended Behavior or Relational-Retrieve is defined for the Protocol Approval Query/Retrieve Service Classes. - More than one entity may be retrieved, - using List of UID matching. - + More than one entity may be retrieved, using List of UID matching.
Association Negotiation - See the Association Negotiation definition for the - Basic Worklist Management Service Class (). - + See the Association Negotiation definition for the Basic Worklist Management Service Class ().
SOP Class Definitions @@ -68148,10 +49231,7 @@ Protocol Approval Information Model
E/R Models - The Protocol Approval Information Model - consists of a single entity. In response to a given C-FIND request, the SCP shall send one - C-FIND response per matching Protocol Approval Instance. - + The Protocol Approval Information Model consists of a single entity. In response to a given C-FIND request, the SCP shall send one C-FIND response per matching Protocol Approval Instance.
Protocol Approval Information Model E-R Diagram @@ -68166,15 +49246,9 @@
Protocol Approval Attributes - - defines the Attributes of the Protocol Approval Information Model. - + defines the Attributes of the Protocol Approval Information Model. - Since protocol approvals are generally - relevant only in the context of the protocol instance being approved, many searches will be - looking for approvals that list a particular protocol instance in the Approval Subject - Sequence (0044,0109). - + Since protocol approvals are generally relevant only in the context of the protocol instance being approved, many searches will be looking for approvals that list a particular protocol instance in the Approval Subject Sequence (0044,0109).
Defined Procedure Protocol SOP Classes
- Defined Procedure Protocol - Information Model - FIND - + Defined Procedure Protocol Information Model - FIND - 1.2.840.10008.5.1.4.20.1 - + 1.2.840.10008.5.1.4.20.1
- Defined Procedure Protocol - Information Model - MOVE - + Defined Procedure Protocol Information Model - MOVE - 1.2.840.10008.5.1.4.20.2 - + 1.2.840.10008.5.1.4.20.2
- Defined Procedure Protocol - Information Model - GET - + Defined Procedure Protocol Information Model - GET - 1.2.840.10008.5.1.4.20.3 - + 1.2.840.10008.5.1.4.20.3
@@ -68193,8 +49267,7 @@ Return Key Type @@ -68208,8 +49281,7 @@ @@ -68260,8 +49328,7 @@ @@ -68316,8 +49371,7 @@ @@ -68389,9 +49435,7 @@ @@ -68430,9 +49473,7 @@ @@ -68575,9 +49609,7 @@
Attributes for the Protocol Approval Information Model
- Remark / Matching Type - + Remark / Matching Type
- Specific Character Set - + Specific Character Set (0008,0005) @@ -68221,11 +49293,7 @@ 1C - This Attribute is required - if expanded or replacement character sets are used. See - - and. - + This Attribute is required if expanded or replacement character sets are used. See and .
- Instance Creation Date - + Instance Creation Date (0008,0012) @@ -68273,18 +49340,13 @@ 1 - Shall be retrieved with - Single Value or Range Matching. - - See Instance Creation Time - for further details. - + Shall be retrieved with Single Value or Range Matching. + See Instance Creation Time for further details.
- Instance Creation Time - + Instance Creation Time (0008,0013) @@ -68296,15 +49358,8 @@ 1 - Shall be retrieved with - Single Value or Range Matching. - - If both Instance Creation - Date and Instance Creation Time are specified for Range Matching, they are to be - treated as as if they were a single DateTime Attribute e.g.,the date range July - 5 to July 7 and the time range 10am to 6pm specifies the time period starting on - July 5, 10am until July 7, 6pm. - + Shall be retrieved with Single Value or Range Matching. + If both Instance Creation Date and Instance Creation Time are specified for Range Matching, they are to be treated as as if they were a single DateTime Attribute e.g.,the date range July 5 to July 7 and the time range 10am to 6pm specifies the time period starting on July 5, 10am until July 7, 6pm.
- Approval Subject Sequence - + Approval Subject Sequence (0044,0109) @@ -68332,9 +49386,7 @@
- >Referenced SOP Class - UID - + >Referenced SOP Class UID (0008,1150) @@ -68346,16 +49398,12 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Referenced SOP Instance - UID - + >Referenced SOP Instance UID (0008,1155) @@ -68367,9 +49415,7 @@ 1 - Shall be retrieved with - List of UID Matching. - + Shall be retrieved with List of UID Matching.
- >Assertion Code - Sequence - + >Assertion Code Sequence (0044,0101) @@ -68407,10 +49451,9 @@
- >>Include - - - +>>Include + +
- >Asserter Identification - Sequence - + >Asserter Identification Sequence (0044,0103) @@ -68447,8 +49488,7 @@
- >>Observer Type - + >>Observer Type (0040,A084) @@ -68478,9 +49518,7 @@
- >>Person - Identification Code Sequence - + >>Person Identification Code Sequence (0040,1101) @@ -68496,17 +49534,14 @@
- >>>Include - - - +>>>Include + +
- >>Organizational Role - Code Sequence - + >>Organizational Role Code Sequence (0044,010A) @@ -68522,10 +49557,9 @@
- >>>Include - - - +>>>Include + +
- >>Manufacturer's - Model Name - + >>Manufacturer's Model Name (0008,1090) @@ -68592,8 +49624,7 @@
- >>Station AE Title - + >>Station AE Title (0008,0055) @@ -68608,8 +49639,7 @@
- >>Institution Name - + >>Institution Name (0008,0080) @@ -68624,9 +49654,7 @@
- >>Institution Code - Sequence - + >>Institution Code Sequence (0008,0082) @@ -68642,17 +49670,14 @@
- >>>Include - - - +>>>Include + +
- >>Institutional - Department Name - + >>Institutional Department Name (0008,1040) @@ -68667,9 +49692,7 @@
- >>Institutional - Department Type Code Sequence - + >>Institutional Department Type Code Sequence (0008,1041) @@ -68684,16 +49707,14 @@
- >>>Include - - - +>>>Include + +
- >Assertion DateTime - + >Assertion DateTime (0044,0104) @@ -68705,16 +49726,12 @@ 1 - This Attribute shall be - retrieved with Single Value or Range Matching. - + This Attribute shall be retrieved with Single Value or Range Matching.
- >Assertion Expiration - DateTime - + >Assertion Expiration DateTime (0044,0105) @@ -68726,15 +49743,12 @@ 2 - This Attribute shall be - retrieved with Single Value or Range Matching. - + This Attribute shall be retrieved with Single Value or Range Matching.
- >Assertion Comments - + >Assertion Comments (0044,0106) @@ -68749,9 +49763,7 @@
- >Related Assertion - Sequence - + >Related Assertion Sequence (0044,0107) @@ -68766,9 +49778,7 @@
- >>Referenced - Assertion UID - + >>Referenced Assertion UID (0044,0108) @@ -68805,8 +49815,7 @@
- Manufacturer's Model Name - + Manufacturer's Model Name (0008,1090) @@ -68837,137 +49846,65 @@
- The Enhanced General Equipment Module - describes the equipment that created the Protocol Approval instance, not the equipment on - which a referenced Protocol will be performed. - + The Enhanced General Equipment Module describes the equipment that created the Protocol Approval instance, not the equipment on which a referenced Protocol will be performed.
Conformance Requirements - An implementation may conform to one or - more of the Protocol Approval Query/Retrieve SOP Classes as an SCU or SCP. The Conformance - Statement shall be in the format defined in. - + An implementation may conform to one or more of the Protocol Approval Query/Retrieve SOP Classes as an SCU or SCP. The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to - the Protocol Approval Information Model - FIND SOP Class shall support queries against - the Protocol Approval Information Model using the C-FIND SCU Behavior described for the - Basic Worklist Management Service Class (see - - and). - - An implementation that conforms to - the Protocol Approval Information Model - FIND SOP Class as an SCU shall state in its - Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list - these Optional Return Key Attributes. - - An implementation that conforms to - the Protocol Approval Information Model - FIND SOP Class as an SCU shall state in its - Conformance Statement how it makes use of Specific Character Set (0008,0005) when - encoding queries and interpreting responses. - + An implementation that conforms to the Protocol Approval Information Model - FIND SOP Class shall support queries against the Protocol Approval Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see and ). + An implementation that conforms to the Protocol Approval Information Model - FIND SOP Class as an SCU shall state in its Conformance Statement whether it requests Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. + An implementation that conforms to the Protocol Approval Information Model - FIND SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.
C-MOVE SCU Conformance - An implementation that conforms to - the Protocol Approval Information Model - MOVE SOP Class as an SCU shall support - transfers against the Protocol Approval Information Model, using the C-MOVE SCU baseline - behavior described for the Query/Retrieve Service Class (see - - and). - + An implementation that conforms to the Protocol Approval Information Model - MOVE SOP Class as an SCU shall support transfers against the Protocol Approval Information Model, using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
C-GET SCU Conformance - An implementation that conforms to - the Protocol Approval Information Model - GET SOP Class as an SCU shall support - transfers against the Protocol Approval Information Model, using the C-GET SCU baseline - behavior described for the Query/Retrieve Service Class (see - ). - + An implementation that conforms to the Protocol Approval Information Model - GET SOP Class as an SCU shall support transfers against the Protocol Approval Information Model, using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see ).
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to - the Protocol Approval Information Model - FIND SOP Class as an SCP shall support queries - against the Protocol Approval Information Model, using the C-FIND SCP Behavior described - for the Basic Worklist Management Service Class (see). - + An implementation that conforms to the Protocol Approval Information Model - FIND SOP Class as an SCP shall support queries against the Protocol Approval Information Model, using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see ). - The contents of the Referenced - SOP Instance UID (0008,1155) in the Approval Subject Sequence (0044,0109) would be - useful to index since querying for approvals of a specific Protocol instance will be - very common. - + The contents of the Referenced SOP Instance UID (0008,1155) in the Approval Subject Sequence (0044,0109) would be useful to index since querying for approvals of a specific Protocol instance will be very common. - An implementation that conforms to - the Protocol Approval Information Model - FIND SOP Class as an SCP shall state in its - Conformance Statement: - + An implementation that conforms to the Protocol Approval Information Model - FIND SOP Class as an SCP shall state in its Conformance Statement: - whether it supports Type 3 - Return Key Attributes, and shall list these Optional Return Key Attributes. - + whether it supports Type 3 Return Key Attributes, and shall list these Optional Return Key Attributes. - how it makes use of - Specific Character Set (0008,0005) when interpreting queries, performing - matching and encoding responses. - + how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses. - any behaviors that involve - not returning matching instances (e.g. not returning an older approval instance - that has been superceded/overridden by a newer approval instance). - + any behaviors that involve not returning matching instances (e.g. not returning an older approval instance that has been superceded/overridden by a newer approval instance).
C-MOVE SCP Conformance - An implementation that conforms to - the Protocol Approval Information Model - MOVE SOP Class as an SCP shall support - transfers against the Protocol Approval Information Model, using the C-MOVE SCP baseline - behavior described for the Query/Retrieve Service Class (see). - - An implementation that conforms to - the Protocol Approval Information Model - MOVE SOP Class as an SCP, which generates - transfers using the C-MOVE operation, shall state in its Conformance Statement - appropriate Storage Service Class, under which it shall support the C-STORE - sub-operations generated by the C-MOVE. - + An implementation that conforms to the Protocol Approval Information Model - MOVE SOP Class as an SCP shall support transfers against the Protocol Approval Information Model, using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see ). + An implementation that conforms to the Protocol Approval Information Model - MOVE SOP Class as an SCP, which generates transfers using the C-MOVE operation, shall state in its Conformance Statement appropriate Storage Service Class, under which it shall support the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to - the Protocol Approval Information Model - GET SOP Class as an SCP shall support - retrievals against the Protocol Approval Information Model using the C-GET SCP baseline - behavior described for the Query/Retrieve Service Class in - . - + An implementation that conforms to the Protocol Approval Information Model - GET SOP Class as an SCP shall support retrievals against the Protocol Approval Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class in .
SOP Classes - The SOP Classes of the Protocol Approval - Query/Retrieve Service Class identify the Information Models, and the DIMSE-C operations - supported. - + The SOP Classes of the Protocol Approval Query/Retrieve Service Class identify the Information Models, and the DIMSE-C operations supported. @@ -68983,38 +49920,26 @@ @@ -69029,57 +49954,29 @@ Overview
Scope - The Inventory Query/Retrieve Service Class - defines an application-level class-of-service that facilitates discovery of and access to Inventory - composite objects. - + The Inventory Query/Retrieve Service Class defines an application-level class-of-service that facilitates discovery of and access to Inventory composite objects.
Conventions - See Conventions for the Basic Worklist - Management Service (see). - + See Conventions for the Basic Worklist Management Service (see ).
Service Definition - The SOP Classes of the Inventory Query/Retrieve - Service Class are each composed of an Information Model and a DIMSE-C Service Group. - - In order to serve as an SCP of the Inventory - Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of - Inventory composite SOP Instances. - The information is organized into an Inventory Query/Retrieve Information Model. - - Two peer DICOM AEs implement a SOP Class of the - Inventory Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP - role. - SOP Classes of the Inventory Query/Retrieve Service Class are implemented using the DIMSE-C C-FIND, - C-MOVE and C-GET services as defined in. - - The semantics of the C-FIND service are the - same as those defined in the Service Definition of the Basic Worklist Management Service Class (see - ). - - The semantics of the C-MOVE and C-GET services - are the same as those defined in the Service Definition of the Query/Retrieve Service Class (see - ), with the exception that there is only one - level of retrieval. - + The SOP Classes of the Inventory Query/Retrieve Service Class are each composed of an Information Model and a DIMSE-C Service Group. + In order to serve as an SCP of the Inventory Query/Retrieve Service Class, a DICOM AE possesses information about the Attributes of a number of Inventory composite SOP Instances. + The information is organized into an Inventory Query/Retrieve Information Model. + Two peer DICOM AEs implement a SOP Class of the Inventory Query/Retrieve Service Class with one serving in the SCU role and one serving in the SCP role. + SOP Classes of the Inventory Query/Retrieve Service Class are implemented using the DIMSE-C C-FIND, C-MOVE and C-GET services as defined in . + The semantics of the C-FIND service are the same as those defined in the Service Definition of the Basic Worklist Management Service Class (see ). + The semantics of the C-MOVE and C-GET services are the same as those defined in the Service Definition of the Query/Retrieve Service Class (see ), with the exception that there is only one level of retrieval.
Inventory Q/R Information Model - The Inventory Query/Retrieve (Q/R) Information - Model is based on an Entity-Relationship Model Definition and a Key Attributes Definition analogous to - those defined in the Worklist Information Model Definition of the Basic Worklist Management Service (see - ) - + The Inventory Query/Retrieve (Q/R) Information Model is based on an Entity-Relationship Model Definition and a Key Attributes Definition analogous to those defined in the Worklist Information Model Definition of the Basic Worklist Management Service (see )
E-R Model - The Inventory Q/R Information Model is a single - level entity: - + The Inventory Q/R Information Model is a single level entity: Inventory Information Entity @@ -69095,19 +49992,12 @@ - While the Inventory Composite SOP Instances - that are the subject of this Service Class contain Attributes associated with the several IEs (see - ), - the Inventory Q/R Information Model operates only on the Attributes of the Inventory IE of the - Inventory IOD. - + While the Inventory Composite SOP Instances that are the subject of this Service Class contain Attributes associated with the several IEs (see ), the Inventory Q/R Information Model operates only on the Attributes of the Inventory IE of the Inventory IOD.
Inventory Q/R Information Model Attributes - - defines the Attributes of the Inventory Q/R Information Model. - + defines the Attributes of the Inventory Q/R Information Model.
Protocol Approval SOP Classes
- Protocol Approval - Information Model - FIND - + Protocol Approval Information Model - FIND - - 1.2.840.10008.5.1.4.1.1.200.4 - + 1.2.840.10008.5.1.4.1.1.200.4
- Protocol Approval - Information Model - MOVE - + Protocol Approval Information Model - MOVE - - 1.2.840.10008.5.1.4.1.1.200.5 - + 1.2.840.10008.5.1.4.1.1.200.5
- Protocol Approval - Information Model - GET - + Protocol Approval Information Model - GET - - 1.2.840.10008.5.1.4.1.1.200.6 - + 1.2.840.10008.5.1.4.1.1.200.6
@@ -69174,10 +50064,7 @@ 1C @@ -69212,8 +50099,7 @@ @@ -69247,9 +50131,7 @@
Attributes for the Inventory Q/R Information Model
- Required if Inventory SOP - Instance was created by an Inventory Creation SOP Class transaction, may be present - otherwise. - + Required if Inventory SOP Instance was created by an Inventory Creation SOP Class transaction, may be present otherwise.
- Scope of Inventory Sequence - + Scope of Inventory Sequence (0008,0400) @@ -69225,9 +50111,7 @@ 2 - May only be requested with - Universal matching. - + May only be requested with Universal matching.
- Inventory Instance - Description - + Inventory Instance Description (0008,0402) @@ -69279,8 +50161,7 @@
- Inventory Completion Status - + Inventory Completion Status (0008,0426) @@ -69295,8 +50176,7 @@
- Total Number of Study Records - + Total Number of Study Records (0008,0428) @@ -69312,73 +50192,44 @@
- - - See also the additional returned - Attributes in the Response Identifier specified in. - - - - Further definition of these - Attributes is specified in - - - - + + + See also the additional returned Attributes in the Response Identifier specified in . + + + Further definition of these Attributes is specified in + + + -
+
DIMSE-C Service Groups
C-FIND Operation - See the C-FIND Operation definition for the - Basic Worklist Management Service Class (), - and substitute "Inventory" for "Worklist". The "Worklist" Search Method shall be used. - - The C-FIND is to be performed against the - Inventory Q/R Information Model (). The Key - Attributes and values allowable for the query are defined in the Inventory Q/R Information Model. - + See the C-FIND Operation definition for the Basic Worklist Management Service Class (), and substitute "Inventory" for "Worklist". The "Worklist" Search Method shall be used. + The C-FIND is to be performed against the Inventory Q/R Information Model (). The Key Attributes and values allowable for the query are defined in the Inventory Q/R Information Model.
C-MOVE Operation - See the C-MOVE Operation definition for the - Query/Retrieve Service Class (). - No Extended Behavior or Relational-Retrieve is defined for the Inventory Query/Retrieve Service - Class. - - Query/Retrieve Level (0008,0052) is not - relevant to the Inventory Query/Retrieve Service Class, and therefore shall not be present in the - Identifier. + See the C-MOVE Operation definition for the Query/Retrieve Service Class (). + No Extended Behavior or Relational-Retrieve is defined for the Inventory Query/Retrieve Service Class. + Query/Retrieve Level (0008,0052) is not relevant to the Inventory Query/Retrieve Service Class, and therefore shall not be present in the Identifier. The Unique Key Attribute of the Identifier is the SOP Instance UID (0008,0018). - The SCU shall supply one UID or a list of UIDs. - + The SCU shall supply one UID or a list of UIDs. - More than one Inventory SOP Instance may be - retrieved, using List of UID Matching. - + More than one Inventory SOP Instance may be retrieved, using List of UID Matching.
C-GET Operation - See the C-GET Operation definition for the - Query/Retrieve Service Class (). - No Extended Behavior or Relational-Retrieve is defined for the Inventory Query/Retrieve Service - Class. - - Query/Retrieve Level (0008,0052) is not - relevant to the Inventory Query/Retrieve Service Class, and therefore shall not be present in the - Identifier. - The Unique Key Attribute of the Identifier is the SOP Instance UID (0008,0018). The SCU shall supply - one UID or a list of UIDs. - + See the C-GET Operation definition for the Query/Retrieve Service Class (). + No Extended Behavior or Relational-Retrieve is defined for the Inventory Query/Retrieve Service Class. + Query/Retrieve Level (0008,0052) is not relevant to the Inventory Query/Retrieve Service Class, and therefore shall not be present in the Identifier. + The Unique Key Attribute of the Identifier is the SOP Instance UID (0008,0018). The SCU shall supply one UID or a list of UIDs. - More than one Inventory SOP Instance may be - retrieved, using List of UID Matching. - + More than one Inventory SOP Instance may be retrieved, using List of UID Matching.
@@ -69386,12 +50237,8 @@ SOP Class Definitions
SOP Classes - The SOP Classes of the Inventory Query/Retrieve - Service Class identify the Inventory Q/R Information Model, and the DIMSE-C operations supported. - The Standard SOP Classes in - - are identified. - + The SOP Classes of the Inventory Query/Retrieve Service Class identify the Inventory Q/R Information Model, and the DIMSE-C operations supported. + The Standard SOP Classes in are identified. @@ -69410,8 +50257,7 @@ Inventory FIND @@ -69419,8 +50265,7 @@ Inventory MOVE @@ -69428,8 +50273,7 @@ Inventory GET @@ -69437,68 +50281,31 @@
Conformance Requirements - An implementation may conform to one of the - Inventory Query/Retrieve Service SOP Classes as an SCU, SCP or both. - The Conformance Statement shall be in the format defined in. - + An implementation may conform to one of the Inventory Query/Retrieve Service SOP Classes as an SCU, SCP or both. + The Conformance Statement shall be in the format defined in .
SCU Conformance
C-FIND SCU Conformance - An implementation that conforms to the - Inventory FIND SOP Class as an SCU shall support queries against the Inventory Q/R - Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management - Service Class (see - - and). - + An implementation that conforms to the Inventory FIND SOP Class as an SCU shall support queries against the Inventory Q/R Information Model using the C-FIND SCU Behavior described for the Basic Worklist Management Service Class (see and ).
C-MOVE SCU Conformance - An implementation that conforms to the - Inventory MOVE SOP Class as an SCU shall support transfers against the Inventory Q/R - Information Model using the C-MOVE SCU baseline behavior described for the Query/Retrieve - Service Class (see - - and). - + An implementation that conforms to the Inventory MOVE SOP Class as an SCU shall support transfers against the Inventory Q/R Information Model using the C-MOVE SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
C-GET SCU Conformance - An implementation that conforms to the - Inventory GET SOP Class as an SCU shall support transfers against the Inventory Q/R - Information Model using the C-GET SCU baseline behavior described for the Query/Retrieve - Service Class (see - - and). - + An implementation that conforms to the Inventory GET SOP Class as an SCU shall support transfers against the Inventory Q/R Information Model using the C-GET SCU baseline behavior described for the Query/Retrieve Service Class (see and ).
SCP Conformance
C-FIND SCP Conformance - An implementation that conforms to the - Inventory FIND SOP Class as an SCP shall support queries against the Inventory Q/R - Information Model using the C-FIND SCP Behavior described for the Basic Worklist Management - Service Class (see - - and). - - The implementation shall support the - additional Attributes in the Response Identifier as specified in - - to support character set specification and access to Inventory SOP Instances. - + An implementation that conforms to the Inventory FIND SOP Class as an SCP shall support queries against the Inventory Q/R Information Model using the C-FIND SCP Behavior described for the Basic Worklist Management Service Class (see and ). + The implementation shall support the additional Attributes in the Response Identifier as specified in to support character set specification and access to Inventory SOP Instances. - Compare - - for the similar specification of non-key Attributes that are to be returned in the - Query/Retrieve C-FIND SOP Classes to support character set specification and access to - the referenced SOP Instances. - + Compare for the similar specification of non-key Attributes that are to be returned in the Query/Retrieve C-FIND SOP Classes to support character set specification and access to the referenced SOP Instances.
Inventory Q/R Service SOP Classes
- 1.2.840.10008.5.1.4.1.1.201.2 - + 1.2.840.10008.5.1.4.1.1.201.2
- 1.2.840.10008.5.1.4.1.1.201.3 - + 1.2.840.10008.5.1.4.1.1.201.3
- 1.2.840.10008.5.1.4.1.1.201.4 - + 1.2.840.10008.5.1.4.1.1.201.4
@@ -69521,9 +50328,7 @@ @@ -69566,17 +50365,12 @@ 1C
Inventory FIND Additional Returned Attributes
- Specific Character - Set - + Specific Character Set (0008,0005) @@ -69532,15 +50337,12 @@ 1C - Required if expanded or - replacement character sets are used in any Attributes of the Query response. - + Required if expanded or replacement character sets are used in any Attributes of the Query response.
- Retrieve AE Title - + Retrieve AE Title (0008,0054) @@ -69549,10 +50351,7 @@ 1C - Required if Inventory - SOP instance is available through Inventory MOVE or Inventory GET SOP - Classes. - + Required if Inventory SOP instance is available through Inventory MOVE or Inventory GET SOP Classes.
- Required if Inventory - SOP instance is available through the Non-Patient Instance Service (see - ). - + Required if Inventory SOP instance is available through the Non-Patient Instance Service (see ).
- File Access Sequence - + File Access Sequence (0008,041A) @@ -69585,19 +50379,12 @@ 1C - Required if Inventory - SOP instance is in the DICOM File Format, and is available through a - non-DICOM protocol (see - ). - + Required if Inventory SOP instance is in the DICOM File Format, and is available through a non-DICOM protocol (see ).
- >Stored Instance - Base URI - + >Stored Instance Base URI (0008,0407) @@ -69606,15 +50393,12 @@ 1C - Required if File Access - URI (0008,0409) is a relative path reference URI. - + Required if File Access URI (0008,0409) is a relative path reference URI.
- >File Access URI - + >File Access URI (0008,0409) @@ -69626,9 +50410,7 @@
- >Container File - Type - + >Container File Type (0008,040A) @@ -69640,9 +50422,7 @@
- >Filename in - Container - + >Filename in Container (0008,040B) @@ -69651,16 +50431,12 @@ 1C - Required if Container - File Type (0008,040A) is ZIP, TAR, or TARGZIP. - + Required if Container File Type (0008,040A) is ZIP, TAR, or TARGZIP.
- >Stored Instance - Transfer Syntax UID - + >Stored Instance Transfer Syntax UID (0008,040E) @@ -69672,8 +50448,7 @@
- >MAC Algorithm - + >MAC Algorithm (0400,0015) @@ -69698,81 +50473,48 @@
- Further definition of these - Attributes, including Defined Terms and Enumerated Values, is specified in. - In that Section, the Attributes apply to stored patient-related Composite SOP Instances, - such as images, while here they apply to Inventory SOP Instances. - + Further definition of these Attributes, including Defined Terms and Enumerated Values, is specified in . + In that Section, the Attributes apply to stored patient-related Composite SOP Instances, such as images, while here they apply to Inventory SOP Instances.
C-MOVE SCP Conformance - An implementation that conforms to the - Inventory MOVE Class as an SCP shall support transfers against the Inventory Q/R Information - Model using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class - (see). - The implementation shall support the Inventory Storage SOP Class (see) for the C-STORE sub-operations - generated by the C-MOVE. - + An implementation that conforms to the Inventory MOVE Class as an SCP shall support transfers against the Inventory Q/R Information Model using the C-MOVE SCP baseline behavior described for the Query/Retrieve Service Class (see ). + The implementation shall support the Inventory Storage SOP Class (see ) for the C-STORE sub-operations generated by the C-MOVE.
C-GET SCP Conformance - An implementation that conforms to the - Inventory GET SOP Class as an SCP shall support transfers against the Inventory Q/R - Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve - Service Class (see). - The implementation shall support the Inventory Storage SOP Class (see) for the C-STORE sub-operations - generated by the C-GET. - + An implementation that conforms to the Inventory GET SOP Class as an SCP shall support transfers against the Inventory Q/R Information Model using the C-GET SCP baseline behavior described for the Query/Retrieve Service Class (see ). + The implementation shall support the Inventory Storage SOP Class (see ) for the C-STORE sub-operations generated by the C-GET.
- + Storage Management Service Class - The Storage Management Service Class defines an - application-level class-of-service that facilitates peer-to-peer controls for management of persistent - storage of Composite SOP Instances. - The Service Class allows asynchronous operations between the Service Class User (SCU) and the Service Class - Provider (SCP). - + The Storage Management Service Class defines an application-level class-of-service that facilitates peer-to-peer controls for management of persistent storage of Composite SOP Instances. + The Service Class allows asynchronous operations between the Service Class User (SCU) and the Service Class Provider (SCP).
Overview
Use Cases - DICOM supports all manner of peer-to-peer - interactions for systems within the biomedical imaging domain. - In many enterprises, one or more systems are responsible for long-term management of stored SOP - Instances. - This Service Class supports the interoperability use cases associated with such long-term storage - management. - + DICOM supports all manner of peer-to-peer interactions for systems within the biomedical imaging domain. + In many enterprises, one or more systems are responsible for long-term management of stored SOP Instances. + This Service Class supports the interoperability use cases associated with such long-term storage management.
SOP Classes - Each SOP Class of the Storage Management - Service Classis formed from a combination of a common DIMSE Service Group and a specific Information - Object Definition. - + Each SOP Class of the Storage Management Service Classis formed from a combination of a common DIMSE Service Group and a specific Information Object Definition.
DIMSE Service Group - The DIMSE-N Services applicable to all SOP - Classes of the Storage Management Service Class are shown in. - + The DIMSE-N Services applicable to all SOP Classes of the Storage Management Service Class are shown in .
DIMSE Service Group Applicable to Storage Management
- DICOM Message Service - Element - + DICOM Message Service Element Usage SCU/SCP @@ -69798,18 +50540,11 @@
- The DIMSE-N Services and Protocol are - specified in. Additional constraints on - these services, such as specific action and event types, are specified for each SOP Class. - + The DIMSE-N Services and Protocol are specified in . Additional constraints on these services, such as specific action and event types, are specified for each SOP Class.
Information Object Definitions - The SOP Classes of the Storage Management - Service Class are defined using the IODs specified in. - + The SOP Classes of the Storage Management Service Class are defined using the IODs specified in . @@ -69821,9 +50556,7 @@ SOP Class UID @@ -69833,103 +50566,57 @@ Inventory Creation
Storage Management Service SOP Classes
- IOD Specification (defined - in) - + IOD Specification (defined in )
- - 1.2.840.10008.5.1.4.1.1.201.5 - + 1.2.840.10008.5.1.4.1.1.201.5 - - + +
- Additional constraints on these IODs, such - as specific Attributes required for the different action types, are specified for each SOP - Class. - + Additional constraints on these IODs, such as specific Attributes required for the different action types, are specified for each SOP Class.
Service Protocol
Association Negotiation - Association establishment is the first - phase of any instance of communication between peer DICOM AEs. - The Association negotiation rules as specified in - - are used to negotiate the supported SOP Classes and peer AE roles. - + Association establishment is the first phase of any instance of communication between peer DICOM AEs. + The Association negotiation rules as specified in are used to negotiate the supported SOP Classes and peer AE roles. - Implementations may restrict - Association establishment subject to exchange of security related information, such as - application identity and authorization, either within DICOM Association negotiation or - outside the scope of the DICOM protocol. - See. - + Implementations may restrict Association establishment subject to exchange of security related information, such as application identity and authorization, either within DICOM Association negotiation or outside the scope of the DICOM protocol. + See . - Support for the SCP/SCU Role Selection - Negotiation is mandatory. - The SOP Class Extended Negotiation is not defined for this Service Class. - - The SCU will open an Association when it - desires to request a storage management operation by the SCP. - - The SCP will typically open an Association - when it is reporting status, or has completed a requested operation or reached some other - termination condition, such as a failure. - This Association establishment includes negotiation of SCP/SCU role. - + Support for the SCP/SCU Role Selection Negotiation is mandatory. + The SOP Class Extended Negotiation is not defined for this Service Class. + The SCU will open an Association when it desires to request a storage management operation by the SCP. + The SCP will typically open an Association when it is reporting status, or has completed a requested operation or reached some other termination condition, such as a failure. + This Association establishment includes negotiation of SCP/SCU role. - The SCP may attempt to issue an - N-EVENT-REPORT on the same Association as the initiating N-ACTION, but this - operation may fail because the SCU is free to release at any time the Association on - which it sent the N-ACTION-Request. - + The SCP may attempt to issue an N-EVENT-REPORT on the same Association as the initiating N-ACTION, but this operation may fail because the SCU is free to release at any time the Association on which it sent the N-ACTION-Request. - As DICOM defaults the - Association-requestor to the SCU role, the SCP (i.e., the Association-requestor) - negotiates an SCP role using the SCU/SCP role negotiation (see). - + As DICOM defaults the Association-requestor to the SCU role, the SCP (i.e., the Association-requestor) negotiates an SCP role using the SCU/SCP role negotiation (see ). - When responding on a different - Association, the SCP uses the same AE Title as it used on the original Association, - because the DICOM Standard defines a Service between two peer applications, each - identified by an AE Title. - Thus, the SCP should be consistently identified for all transactions with a - particular peer in a SOP Class. - + When responding on a different Association, the SCP uses the same AE Title as it used on the original Association, because the DICOM Standard defines a Service between two peer applications, each identified by an AE Title. + Thus, the SCP should be consistently identified for all transactions with a particular peer in a SOP Class.
Operations and Notifications - Following Association establishment, - peer-to-peer communication between the SCU and SCP uses the DIMSE N-ACTION and N-EVENT-REPORT - (see). - - The N-ACTION and N-EVENT-REPORT primitives - shall contain the well-known Storage Management SOP Instance specified in - - in their Requested SOP Instance UID and Affected SOP Instance UID parameters. - + Following Association establishment, peer-to-peer communication between the SCU and SCP uses the DIMSE N-ACTION and N-EVENT-REPORT (see ). + The N-ACTION and N-EVENT-REPORT primitives shall contain the well-known Storage Management SOP Instance specified in in their Requested SOP Instance UID and Affected SOP Instance UID parameters. - In the usage described here, there is - no explicit creation of a SOP Instance (using N-CREATE) upon which an N-ACTION may operate. + In the usage described here, there is no explicit creation of a SOP Instance (using N-CREATE) upon which an N-ACTION may operate. Instead, the N-ACTION operates upon a well-known SOP Instance. - This SOP Instance is conceptually created during start-up of each Storage Management Service - Class SCP Application. - + This SOP Instance is conceptually created during start-up of each Storage Management Service Class SCP Application. @@ -69946,38 +50633,22 @@
Storage Management SOP Instance UID
- - 1.2.840.10008.5.1.4.1.1.201.1.1 - + 1.2.840.10008.5.1.4.1.1.201.1.1 - Storage Management SOP - Instance - + Storage Management SOP Instance
- The SCP requests a storage management - operation using the N-ACTION-Request primitive of one of the Storage Management Service SOP - Classes. - The request includes a Transaction UID for tracking purposes. - - If the SCP accepts the N-ACTION request for - processing, it sends a Success N-ACTION Response Status Code. - If it does not accept the N-ACTION request for processing, it sends an Error N-ACTION Response - Status Code. - The actions taken by the SCU upon receiving the status is beyond the scope of this Standard. - - At any time after receipt of the - N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. - - The SCP notifies the SCU using the - N-EVENT-REPORT primitive when it has completed the requested operation or reached some other - termination condition, such as a failure or a time-out. - The notification includes the Transaction UID of the request. Upon completion or termination, - the Transaction UID is no longer active and shall not be reused. - + The SCP requests a storage management operation using the N-ACTION-Request primitive of one of the Storage Management Service SOP Classes. + The request includes a Transaction UID for tracking purposes. + If the SCP accepts the N-ACTION request for processing, it sends a Success N-ACTION Response Status Code. + If it does not accept the N-ACTION request for processing, it sends an Error N-ACTION Response Status Code. + The actions taken by the SCU upon receiving the status is beyond the scope of this Standard. + At any time after receipt of the N-ACTION-Response, the SCU may release the association on which it sent the N-ACTION-Request. + The SCP notifies the SCU using the N-EVENT-REPORT primitive when it has completed the requested operation or reached some other termination condition, such as a failure or a time-out. + The notification includes the Transaction UID of the request. Upon completion or termination, the Transaction UID is no longer active and shall not be reused.
@@ -69985,30 +50656,16 @@ Inventory Creation SOP Class
Overview - The Inventory Creation SOP Class allows an SCU - Application Entity to request a peer SCP Application Entity to produce an Inventory of the Studies, - Series, and Instances that it manages. - The request for the Inventory may include a set of matching keys to limit the Scope of Inventory to - Studies with corresponding Attribute values. - The Inventory produced is encoded in one or more SOP Instances of the Inventory SOP Class (see). + The Inventory Creation SOP Class allows an SCU Application Entity to request a peer SCP Application Entity to produce an Inventory of the Studies, Series, and Instances that it manages. + The request for the Inventory may include a set of matching keys to limit the Scope of Inventory to Studies with corresponding Attribute values. + The Inventory produced is encoded in one or more SOP Instances of the Inventory SOP Class (see ). Success or failure of Inventory production is indicated by a notification from the SCP to the SCU. - The SCU may then access the Inventory SOP Instances by a mechanism supported by the SCP, including - Query/Retrieve (see), Non-Patient Instance - Services (see), or a non-DICOM file access - protocol. - See additional explanatory information in. - + The SCU may then access the Inventory SOP Instances by a mechanism supported by the SCP, including Query/Retrieve (see ), Non-Patient Instance Services (see ), or a non-DICOM file access protocol. + See additional explanatory information in .
Inventory Production States - The SOP Class defines five states for the - Inventory production with associated state transitions (see). - Some of the transitions are associated with receipt and processing of N-ACTION requests (labeled - arrows in the figure). - + The SOP Class defines five states for the Inventory production with associated state transitions (see ). + Some of the transitions are associated with receipt and processing of N-ACTION requests (labeled arrows in the figure).
Inventory Production States and State Transitions @@ -70020,33 +50677,19 @@
- After the Initiate request, production is - in the PROCESSING state. - Production will proceed and reach one of two terminal states without further N-ACTION operations - - COMPLETE or FAILURE. - - Production may be PAUSED, either due to an - N-ACTION request or due to conditions internal to the SCP, for example, a temporary shortage of - resources. - Production may be returned to the PROCESSING state by a Resume request or by SCP internal - actions. - - From either the PROCESSING or PAUSED state - the production may be changed to the CANCELED terminal state by a Cancel request or by SCP - internal actions. - + After the Initiate request, production is in the PROCESSING state. + Production will proceed and reach one of two terminal states without further N-ACTION operations - COMPLETE or FAILURE. + Production may be PAUSED, either due to an N-ACTION request or due to conditions internal to the SCP, for example, a temporary shortage of resources. + Production may be returned to the PROCESSING state by a Resume request or by SCP internal actions. + From either the PROCESSING or PAUSED state the production may be changed to the CANCELED terminal state by a Cancel request or by SCP internal actions.
Operations
Action Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as - specified in. - Descriptions of the Attributes of the Action Information are specified in. - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Action Types and Action Information as specified in . + Descriptions of the Attributes of the Action Information are specified in . @@ -70064,11 +50707,10 @@ Tag - + @@ -70090,9 +50732,7 @@
Inventory Creation Requests - Action Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Scope of Inventory - Sequence - + Scope of Inventory Sequence (0008,0400) @@ -70103,9 +50743,7 @@
- >Extended Matching - Mechanisms - + >Extended Matching Mechanisms (0008,040F) @@ -70116,9 +50754,7 @@
- >Specific Character - Set - + >Specific Character Set (0008,0005) @@ -70129,9 +50765,7 @@
- >Timezone Offset from - UTC - + >Timezone Offset from UTC (0008,0201) @@ -70142,9 +50776,7 @@
- >Range Matching - Sequence - + >Range Matching Sequence (0008,0410) @@ -70165,9 +50797,7 @@
- >List of UID Matching - Sequence - + >List of UID Matching Sequence (0008,0411) @@ -70188,9 +50818,7 @@
- >Empty Value Matching - Sequence - + >Empty Value Matching Sequence (0008,0412) @@ -70211,9 +50839,7 @@
- >General Matching - Sequence - + >General Matching Sequence (0008,0413) @@ -70256,8 +50882,7 @@
- Requested Status Interval - + Requested Status Interval (0008,0414) @@ -70285,8 +50910,7 @@
- Requested Status Interval - + Requested Status Interval (0008,0414) @@ -70361,105 +50985,47 @@
Scope of Inventory Sequence - The Scope of Inventory Sequence - (0008,0400) specifies constraints on Studies to be included in the Inventory. - See the Attribute descriptions for the Scope of Inventory Sequence (0008,0400) in. - - The Attributes are similar to Key - Attributes used for Attribute matching in the Query/Retrieve Service Class (see). - The Attribute values provided in the N-ACTION shall be matched against the values of - Attributes of Studies managed by the SCP, in accordance with the requirements of this - section, with matching Studies to be included in the produced Inventory. - Studies that match all specified keys shall be included in the produced Inventory. - - The Scope of Inventory Sequence - (0008,0400) may be zero-length to indicate universal match to all Studies in the repository - (i.e., a comprehensive Inventory). - + The Scope of Inventory Sequence (0008,0400) specifies constraints on Studies to be included in the Inventory. + See the Attribute descriptions for the Scope of Inventory Sequence (0008,0400) in . + The Attributes are similar to Key Attributes used for Attribute matching in the Query/Retrieve Service Class (see ). + The Attribute values provided in the N-ACTION shall be matched against the values of Attributes of Studies managed by the SCP, in accordance with the requirements of this section, with matching Studies to be included in the produced Inventory. + Studies that match all specified keys shall be included in the produced Inventory. + The Scope of Inventory Sequence (0008,0400) may be zero-length to indicate universal match to all Studies in the repository (i.e., a comprehensive Inventory).
Inventory Level - Inventory Level (0008,0403) specifies - the types of records requested for inclusion in the produced Inventory SOP Instances. - Inventories may be requested with Study level records, with Study and Series level records, - or with Study, Series, and Instance level records. - -
+ Inventory Level (0008,0403) specifies the types of records requested for inclusion in the produced Inventory SOP Instances. + Inventories may be requested with Study level records, with Study and Series level records, or with Study, Series, and Instance level records. +
Service Class User Behavior - The SCU shall use the N-ACTION primitive - containing the well-known Storage Management SOP Instance UID (defined in) in its Requested SOP Instance UID - parameter. - - The SCU shall supply the Transaction UID - (0008,1195) to uniquely identify each Storage Management Request. - The value of the Transaction UID (0008,1195) will be included by the SCP in N-EVENT-REPORT - primitives (see). - Use of the Transaction UID (0008,1195) Attribute allows the SCU to match requests and results - that may occur over the same or different Associations. - - The SCU shall use the N-ACTION primitive - with Action Type "Initiate" (Action Type ID = 11) to request the SCP to produce an Inventory of - Instances managed by the SCP. - The SCU shall supply the Inventory Level (0008,0403) to indicate whether the produced Inventory - should include records for Series and Instances. - The SCU shall supply the Scope of Inventory Sequence (0008,0400) to specify Key Attributes for - Studies to be included in the Inventory. - The SCU shall specify in Extended Matching Mechanisms (0008,040F) any requested matching - mechanisms or matching semantics beyond the baseline specified for Query in. - The SCU may request the SCP to regularly report on the progress of producing the Inventory - associated with the Transaction UID (0008,1195) at the interval specified by Requested Status - Interval (0008,0414). - - The SCU shall use the N-ACTION primitive - with Action Type "Request Status" (Action Type ID = 12) to request the SCP to report on the - progress of producing the Inventory associated with the Transaction UID (0008,1195). - The SCU may request the SCP to change the interval for progress reports as specified by - Requested Status Interval (0008,0414). - + The SCU shall use the N-ACTION primitive containing the well-known Storage Management SOP Instance UID (defined in ) in its Requested SOP Instance UID parameter. + The SCU shall supply the Transaction UID (0008,1195) to uniquely identify each Storage Management Request. + The value of the Transaction UID (0008,1195) will be included by the SCP in N-EVENT-REPORT primitives (see ). + Use of the Transaction UID (0008,1195) Attribute allows the SCU to match requests and results that may occur over the same or different Associations. + The SCU shall use the N-ACTION primitive with Action Type "Initiate" (Action Type ID = 11) to request the SCP to produce an Inventory of Instances managed by the SCP. + The SCU shall supply the Inventory Level (0008,0403) to indicate whether the produced Inventory should include records for Series and Instances. + The SCU shall supply the Scope of Inventory Sequence (0008,0400) to specify Key Attributes for Studies to be included in the Inventory. + The SCU shall specify in Extended Matching Mechanisms (0008,040F) any requested matching mechanisms or matching semantics beyond the baseline specified for Query in . + The SCU may request the SCP to regularly report on the progress of producing the Inventory associated with the Transaction UID (0008,1195) at the interval specified by Requested Status Interval (0008,0414). + The SCU shall use the N-ACTION primitive with Action Type "Request Status" (Action Type ID = 12) to request the SCP to report on the progress of producing the Inventory associated with the Transaction UID (0008,1195). + The SCU may request the SCP to change the interval for progress reports as specified by Requested Status Interval (0008,0414). - Status of inventory production, - including failure, will be signaled by the SCP via the N-EVENT-REPORT primitive. - + Status of inventory production, including failure, will be signaled by the SCP via the N-EVENT-REPORT primitive. - The SCU shall use the N-ACTION primitive - with Action Type "Cancel" (Action Type ID = 13) to request the SCP to stop producing the - Inventory associated with the Transaction UID (0008,1195). - - The SCU shall use the N-ACTION primitive - with Action Type "Pause" (Action Type ID = 14) to request the SCP to pause production of the - Inventory associated with the Transaction UID (0008,1195). - It shall use the N-ACTION primitive with Action Type "Resume" (Action Type ID = 15) to request - the SCP to resume producing the Inventory from a PAUSED state. - + The SCU shall use the N-ACTION primitive with Action Type "Cancel" (Action Type ID = 13) to request the SCP to stop producing the Inventory associated with the Transaction UID (0008,1195). + The SCU shall use the N-ACTION primitive with Action Type "Pause" (Action Type ID = 14) to request the SCP to pause production of the Inventory associated with the Transaction UID (0008,1195). + It shall use the N-ACTION primitive with Action Type "Resume" (Action Type ID = 15) to request the SCP to resume producing the Inventory from a PAUSED state.
Service Class Provider Behavior - Upon receipt of the N-ACTION request, the - SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code - applicable to the associated request (see). + Upon receipt of the N-ACTION request, the SCP shall return, via the N-ACTION response primitive, the N-ACTION Response Status Code applicable to the associated request (see ). A success status conveys that the SCP has successfully received the request. - A warning status conveys that the SCP has successfully received the request, but might not - process some of the requested parameters. - A failure status conveys that the SCP is not processing the request. - - For Action Type "Initiate" (Action Type ID - = 11), the SCP shall return a failure status 0212H (Mistyped argument) if the SCP does not - support all of the character sets identified in Specific Character Set (0008,0005), or all of - the matching mechanisms identified in Extended Matching Mechanisms (0008,040F), or the - identified Inventory Level (0008,0403); additional explanation may be returned in Error Comment - (0000,0902). - The SCP shall return a warning status B010H if one or more of the Key Attributes specified in - the Scope of Inventory Sequence (0008,0400) are not supported for matching, and shall return the - list of unsupported Attributes in Attribute Identifier List (0000,1005). - + A warning status conveys that the SCP has successfully received the request, but might not process some of the requested parameters. + A failure status conveys that the SCP is not processing the request. + For Action Type "Initiate" (Action Type ID = 11), the SCP shall return a failure status 0212H (Mistyped argument) if the SCP does not support all of the character sets identified in Specific Character Set (0008,0005), or all of the matching mechanisms identified in Extended Matching Mechanisms (0008,040F), or the identified Inventory Level (0008,0403); additional explanation may be returned in Error Comment (0000,0902). + The SCP shall return a warning status B010H if one or more of the Key Attributes specified in the Scope of Inventory Sequence (0008,0400) are not supported for matching, and shall return the list of unsupported Attributes in Attribute Identifier List (0000,1005). @@ -70495,8 +51061,7 @@
N-ACTION Response Status Values
- Refused: Not authorized - + Refused: Not authorized 0124 @@ -70507,9 +51072,7 @@
- Mistyped argument -one of - the parameters supplied has not been agreed for use - + Mistyped argument -one of the parameters supplied has not been agreed for use 0212 @@ -70534,9 +51097,8 @@ Other failure status as specified in - - + + @@ -70547,9 +51109,7 @@ Warning - Attribute list error - One - or more of Key Attributes are not supported for matching - + Attribute list error - One or more of Key Attributes are not supported for matching B010 @@ -70573,66 +51133,27 @@
- See - - for definition of the Related Fields. - + See for definition of the Related Fields. - If the SCP conveys a success or warning - status for Action Type "Initiate" (Action Type ID = 11), it shall initiate production of an - Inventory and periodic status reporting in accordance with the parameters of the Scope of - Inventory Sequence (0008,0400) and Inventory Level (0008,0403) provided in the N-ACTION request. - The Scope of Inventory in the produced Inventory SOP Instances shall include only those Key - Attributes that were supported for matching. - Any value provided by the SCU for Inventory Purpose (0008,0401) shall be included in the - produced Inventory SOP Instances. - The SCP shall produce at least one Inventory SOP Instance upon reaching the COMPLETE state. - - If the SCP encounters a failure when - producing the Inventory, it may attempt to complete the encoding into an Inventory SOP Instance - of Study records already obtained, and set Inventory Completion Status (0008,0426) in that SOP - Instance to "FAILURE". - - If the SCP conveys a success status for - Action Type "Request Status" (Action Type ID = 12), it shall initiate sending an N-EVENT-REPORT - with Event Type "Inventory Status" (Event Type ID = 12). - + If the SCP conveys a success or warning status for Action Type "Initiate" (Action Type ID = 11), it shall initiate production of an Inventory and periodic status reporting in accordance with the parameters of the Scope of Inventory Sequence (0008,0400) and Inventory Level (0008,0403) provided in the N-ACTION request. + The Scope of Inventory in the produced Inventory SOP Instances shall include only those Key Attributes that were supported for matching. + Any value provided by the SCU for Inventory Purpose (0008,0401) shall be included in the produced Inventory SOP Instances. + The SCP shall produce at least one Inventory SOP Instance upon reaching the COMPLETE state. + If the SCP encounters a failure when producing the Inventory, it may attempt to complete the encoding into an Inventory SOP Instance of Study records already obtained, and set Inventory Completion Status (0008,0426) in that SOP Instance to "FAILURE". + If the SCP conveys a success status for Action Type "Request Status" (Action Type ID = 12), it shall initiate sending an N-EVENT-REPORT with Event Type "Inventory Status" (Event Type ID = 12). - The N-EVENT-REPORT may be sent on the - same or a different Association as the N-ACTION request (see - ). - + The N-EVENT-REPORT may be sent on the same or a different Association as the N-ACTION request (see ). - If the SCP conveys a success status for - Action Type "Cancel" (Action Type ID = 13), it shall stop production of the Inventory associated - with the Transaction UID (0008,1195). - If the Cancel request includes Retain Instances (0008,0415) with value "N", the SCP may delete - any Inventory SOP Instances associated with the Transaction UID (0008,1195). - If the Cancel request includes Retain Instances (0008,0415) with value "Y", the SCP shall - complete the encoding into an Inventory SOP Instance of Study records already obtained, and set - Inventory Completion Status (0008,0426) to "CANCELED". - Some Study records may be only partially complete at the time of the Cancel request, e.g., not - all the subsidiary Series and Instance records had been compiled. - Whether such partial Study records are completed and included in the Inventory SOP Instance is - implementation specific. Partial Study records shall not be included in an Inventory. - - If the SCP conveys a success status for - Action Type "Pause" (Action Type ID = 14), it shall pause production of the Inventory associated - with the Transaction UID (0008,1195). - The SCP may complete any processing necessary to reach a stable state for pausing the Inventory - production to allow efficient resumption. - - If the SCP conveys a success status for - Action Type "Resume" (Action Type ID = 15), it shall resume production of the Inventory - associated with the Transaction UID (0008,1195). - + If the SCP conveys a success status for Action Type "Cancel" (Action Type ID = 13), it shall stop production of the Inventory associated with the Transaction UID (0008,1195). + If the Cancel request includes Retain Instances (0008,0415) with value "N", the SCP may delete any Inventory SOP Instances associated with the Transaction UID (0008,1195). + If the Cancel request includes Retain Instances (0008,0415) with value "Y", the SCP shall complete the encoding into an Inventory SOP Instance of Study records already obtained, and set Inventory Completion Status (0008,0426) to "CANCELED". + Some Study records may be only partially complete at the time of the Cancel request, e.g., not all the subsidiary Series and Instance records had been compiled. + Whether such partial Study records are completed and included in the Inventory SOP Instance is implementation specific. Partial Study records shall not be included in an Inventory. + If the SCP conveys a success status for Action Type "Pause" (Action Type ID = 14), it shall pause production of the Inventory associated with the Transaction UID (0008,1195). + The SCP may complete any processing necessary to reach a stable state for pausing the Inventory production to allow efficient resumption. + If the SCP conveys a success status for Action Type "Resume" (Action Type ID = 15), it shall resume production of the Inventory associated with the Transaction UID (0008,1195). - The SCP may return an error status - Refused: Not authorized (0124H) or Resource Limitation (0213H) if the conditions that caused - the Pause have not been corrected and the production is not resumed. - + The SCP may return an error status Refused: Not authorized (0124H) or Resource Limitation (0213H) if the conditions that caused the Pause have not been corrected and the production is not resumed.
@@ -70640,14 +51161,8 @@ Notifications
Event Information - The DICOM AEs that claim conformance to - this SOP Class as an SCU and/or an SCP shall support the Event Types and Event Information as - specified in. - Descriptions of the Attributes of the Event Information are specified in - . - + The DICOM AEs that claim conformance to this SOP Class as an SCU and/or an SCP shall support the Event Types and Event Information as specified in . + Descriptions of the Attributes of the Event Information are specified in . @@ -70665,17 +51180,14 @@ Tag
Inventory Creation Responses - Event Information
- Requirement Type SCU/SCP - + Requirement Type SCU/SCP
- Inventory Terminated with - Instances - + Inventory Terminated with Instances 11 @@ -70703,9 +51215,7 @@
- Transaction Status - Comment - + Transaction Status Comment (0008,0418) @@ -70716,8 +51226,7 @@
- Referenced SOP Class UID - + Referenced SOP Class UID (0008,1150) @@ -70728,9 +51237,7 @@
- Referenced SOP Instance - UID - + Referenced SOP Instance UID (0008,1155) @@ -70776,8 +51283,7 @@
- Stored Instance Base URI - + Stored Instance Base URI (0008,0407) @@ -70801,8 +51307,7 @@
- Filename in Container - + Filename in Container (0008,040B) @@ -70814,8 +51319,7 @@
- File Offset in Container - + File Offset in Container (0008,040C) @@ -70827,8 +51331,7 @@
- File Length in Container - + File Length in Container (0008,040D) @@ -70840,9 +51343,7 @@
- Stored Instance Transfer - Syntax UID - + Stored Instance Transfer Syntax UID (0008,040E) @@ -70887,9 +51388,7 @@
- Total Number of Study - Records - + Total Number of Study Records (0008,0428) @@ -70928,9 +51427,7 @@
- Transaction Status - Comment - + Transaction Status Comment (0008,0418) @@ -70941,9 +51438,7 @@
- Total Number of Study - Records - + Total Number of Study Records (0008,0428) @@ -70954,9 +51449,7 @@
- Inventory Terminated - without Instances - + Inventory Terminated without Instances 13 @@ -70984,9 +51477,7 @@
- Transaction Status - Comment - + Transaction Status Comment (0008,0418) @@ -70999,220 +51490,117 @@
Inventory Terminated With Instances - Within the Inventory Terminated with - Instances Event Information, either Retrieve AE Title (0008,0054) or Retrieve URL - (0008,1190), or both, shall be present. - - File Access URI (0008,0409) provides a - non-DICOM Protocol access method (see) - to a produced Inventory SOP Instance encodedin accordance with the DICOM File Format (see - ). Stored Instance Base URI - (0008,0407) shall be present if File Access URI (0008,0409) is a relative path reference - URI. Stored Instance Transfer Syntax UID (0008,040E) and Container File Type (0008,040A) - shall be present if File Access URI (0008,0409) is present. Filename in Container - (0008,040B) shall be present if Container File Type (0008,040A) is ZIP, TAR, or TARGZIP. - File Offset in Container (0008,040C) and File Length in Container (0008,040D) shall be - present if Container File Type (0008,040A) is BLOB. - + Within the Inventory Terminated with Instances Event Information, either Retrieve AE Title (0008,0054) or Retrieve URL (0008,1190), or both, shall be present. + File Access URI (0008,0409) provides a non-DICOM Protocol access method (see ) to a produced Inventory SOP Instance encodedin accordance with the DICOM File Format (see ). Stored Instance Base URI (0008,0407) shall be present if File Access URI (0008,0409) is a relative path reference URI. Stored Instance Transfer Syntax UID (0008,040E) and Container File Type (0008,040A) shall be present if File Access URI (0008,0409) is present. Filename in Container (0008,040B) shall be present if Container File Type (0008,040A) is ZIP, TAR, or TARGZIP. File Offset in Container (0008,040C) and File Length in Container (0008,040D) shall be present if Container File Type (0008,040A) is BLOB.
Service Class Provider Behavior - The SCP shall use the N-EVENT-REPORT - primitive containing the well-known Storage Management SOP Instance UID (defined in) in its Affected SOP Instance UID - parameter. - The SCP shall supply the Transaction UID (0008,1195) corresponding to the Inventory Creation - N-ACTION Initiate request. - - At any time during the production of the - Inventory, the SCP may send an N-EVENT-REPORT primitive with Event Type "Inventory Status" - (Event Type ID = 12), with an indication of process status in the Transaction Status (0008,0417) - Attribute. - The SCP shall send an N-EVENT-REPORT "Inventory Status" if production of the Inventory changes - state. - The SCP shall send an N-EVENT-REPORT "Inventory Status" in response to an N-ACTION "Request - Status". - - When production of the Inventory reaches a - terminal state (COMPLETE, FAILURE, or CANCELED) and Inventory SOP Instances are available, the - SCP shall send an N-EVENT-REPORT primitive with Event Type "Inventory Terminated with Instances" - (Event Type ID = 11). - The Event Information shall include Attributes specifying at least one method of accessing the - root SOP Instance of the Inventory, i.e., it shall include at least one of the Attributes - Retrieve AE Title (0008,0054) or Retrieve URL (0008,1190), and may optionally include File - Access URI (0008,0409). - See - - for conditionally required Attributes. - The Event Information may also include an Expiration DateTime (0008,0416) Attribute to indicate - the expected DateTime until which the Inventory SOP Instance is available for access by the SCU. - - If production of the inventory reaches a - terminal state and Inventory SOP Instances are not available (i.e., FAILURE or CANCELED), the - SCP shall send an N-EVENT-REPORT primitive with Event Type "Inventory Terminated without - Instances" (Event Type ID = 13). - + The SCP shall use the N-EVENT-REPORT primitive containing the well-known Storage Management SOP Instance UID (defined in ) in its Affected SOP Instance UID parameter. + The SCP shall supply the Transaction UID (0008,1195) corresponding to the Inventory Creation N-ACTION Initiate request. + At any time during the production of the Inventory, the SCP may send an N-EVENT-REPORT primitive with Event Type "Inventory Status" (Event Type ID = 12), with an indication of process status in the Transaction Status (0008,0417) Attribute. + The SCP shall send an N-EVENT-REPORT "Inventory Status" if production of the Inventory changes state. + The SCP shall send an N-EVENT-REPORT "Inventory Status" in response to an N-ACTION "Request Status". + When production of the Inventory reaches a terminal state (COMPLETE, FAILURE, or CANCELED) and Inventory SOP Instances are available, the SCP shall send an N-EVENT-REPORT primitive with Event Type "Inventory Terminated with Instances" (Event Type ID = 11). + The Event Information shall include Attributes specifying at least one method of accessing the root SOP Instance of the Inventory, i.e., it shall include at least one of the Attributes Retrieve AE Title (0008,0054) or Retrieve URL (0008,1190), and may optionally include File Access URI (0008,0409). + See for conditionally required Attributes. + The Event Information may also include an Expiration DateTime (0008,0416) Attribute to indicate the expected DateTime until which the Inventory SOP Instance is available for access by the SCU. + If production of the inventory reaches a terminal state and Inventory SOP Instances are not available (i.e., FAILURE or CANCELED), the SCP shall send an N-EVENT-REPORT primitive with Event Type "Inventory Terminated without Instances" (Event Type ID = 13).
Service Class User Behavior - Upon receipt of an - N-EVENT-REPORTnotification, the SCU shall return, via the N-EVENT-REPORT response primitive, the - N-EVENT-REPORT Response Status Code applicable to its processing of the associated notification. + Upon receipt of an N-EVENT-REPORTnotification, the SCU shall return, via the N-EVENT-REPORT response primitive, the N-EVENT-REPORT Response Status Code applicable to its processing of the associated notification. A success status conveys that the SCU has successfully received the notification. - An error status conveys that the SCU is not processing the notification. - + An error status conveys that the SCU is not processing the notification. - The action of the SCP upon an error - status for the N-EVENT-REPORT is outside the scope of this Standard. - + The action of the SCP upon an error status for the N-EVENT-REPORT is outside the scope of this Standard.
Conformance - An implementation may claim conformance to this - SOP Class as an SCU, SCP or both. - The Conformance Statement shall be in the format defined in. - + An implementation may claim conformance to this SOP Class as an SCU, SCP or both. + The Conformance Statement shall be in the format defined in .
SCU Conformance - An implementation that is conformant to the - Inventory Creation SOP Class as an SCU shall meet conformance requirements for: - + An implementation that is conformant to the Inventory Creation SOP Class as an SCU shall meet conformance requirements for: - the operations and actions that it - invokes, - + the operations and actions that it invokes, - the notifications that it - receives. - + the notifications that it receives.
Operations - The SCU shall document in the SCU - Operations Statement: - + The SCU shall document in the SCU Operations Statement: - the behavior and actions that - cause the SCU to generate an N-ACTION primitive (Initiate, Request Status, Cancel, - Pause, or Resume), - + the behavior and actions that cause the SCU to generate an N-ACTION primitive (Initiate, Request Status, Cancel, Pause, or Resume), - the behavior and actions taken - by the SCU upon receiving an N-ACTION error status. - + the behavior and actions taken by the SCU upon receiving an N-ACTION error status.
Notifications - The SCU shall document in the SCU - Notifications Statement: - + The SCU shall document in the SCU Notifications Statement: - the behavior and actions taken - by the SCU upon receiving an N-EVENT-REPORT primitive (Inventory Terminated with - Instances, Inventory Status, or Inventory Terminated without Instances). - + the behavior and actions taken by the SCU upon receiving an N-EVENT-REPORT primitive (Inventory Terminated with Instances, Inventory Status, or Inventory Terminated without Instances).
SCP Conformance - An implementation that is conformant to the - Inventory Creation SOP Class as an SCP shall meet conformance requirements for: - + An implementation that is conformant to the Inventory Creation SOP Class as an SCP shall meet conformance requirements for: - the operations and actions that it - performs, - + the operations and actions that it performs, - the notifications that it - generates. - + the notifications that it generates. -
+
Operations - The SCP shall document in the SCP - Operations Statement: - - - - the behavior and actions of the - SCP upon receiving an N-ACTION primitive (Initiate, Request Status, Cancel, Pause, - or Resume). - - - - the range of values that it - supports for the Requested Status Interval (0008,0414), and the default value for - periodic reporting of status if that Attribute is not provided by the SCU - - - - character repertoires supported - in Specific Character Set (0008,0005) in the Scope of Inventory Sequence (0008,0400) - - - - support for Extended Matching - Mechanisms (0008,040F) in the Scope of Inventory Sequence (0008,0400) - - - - the values supported for - Inventory Level (0008,0403) - - - - Key Attributes supported for - matching in the Scope of Inventory Sequence (0008,0400) - - - + The SCP shall document in the SCP Operations Statement: + + + the behavior and actions of the SCP upon receiving an N-ACTION primitive (Initiate, Request Status, Cancel, Pause, or Resume). + + + the range of values that it supports for the Requested Status Interval (0008,0414), and the default value for periodic reporting of status if that Attribute is not provided by the SCU + + + character repertoires supported in Specific Character Set (0008,0005) in the Scope of Inventory Sequence (0008,0400) + + + support for Extended Matching Mechanisms (0008,040F) in the Scope of Inventory Sequence (0008,0400) + + + the values supported for Inventory Level (0008,0403) + + + Key Attributes supported for matching in the Scope of Inventory Sequence (0008,0400) + + - Conformance requirements for the - SCP with respect to the created Inventory SOP Instances are detailed in. - + Conformance requirements for the SCP with respect to the created Inventory SOP Instances are detailed in . -
+
Notifications - The SCP shall document in the SCP - Notifications Statement: - + The SCP shall document in the SCP Notifications Statement: - the behavior and actions that - cause the SCP to generate an N-EVENT-REPORT primitive (Inventory Terminated with - Instances, Inventory Status, or Inventory Terminated without Instances), and in - particular the conditions that cause a transition to the PAUSED or FAILURE - processing status and the generation of the associated N-EVENT-REPORT. - + the behavior and actions that cause the SCP to generate an N-EVENT-REPORT primitive (Inventory Terminated with Instances, Inventory Status, or Inventory Terminated without Instances), and in particular the conditions that cause a transition to the PAUSED or FAILURE processing status and the generation of the associated N-EVENT-REPORT. - the supported access mechanisms - to Inventory SOP Instances referenced in the Inventory Terminated with Instances - Notification, including the specific non-DICOM protocols (if any) referenced in the - File Access URI (0008,0409). - + the supported access mechanisms to Inventory SOP Instances referenced in the Inventory Terminated with Instances Notification, including the specific non-DICOM protocols (if any) referenced in the File Access URI (0008,0409).
diff --git a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part05.xml b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part05.xml similarity index 93% rename from dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part05.xml rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part05.xml index f2590ea..fc0633f 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part05.xml +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part05.xml @@ -1,14 +1,13 @@ - + PS3.5 - DICOM PS3.5 2021d - Data Structures and Encoding + DICOM PS3.5 2022d - Data Structures and Encoding DICOM Standards Committee - 2021 + 2022 NEMA @@ -71,7 +70,7 @@ the structure and usage of a Data Set - Data Element usage and relationships to other elements + Data Element usage and relationships to other Data Elements the construction and usage of Nested Data Sets @@ -934,7 +933,7 @@ Code String - A string of characters identifying a controlled concept, including Defined Terms and Enumerated Values when represented as character strings. The scope of the controlled concept is limited to the attribute for which the string provides the value; i.e., the attribute defines the allowed set of values for the Code String, and a particular string may have different meanings in different attributes. A Code String is formally an arbitrary code representing a semantic concept; however, English language words (using the constrained character set of the CS Value Representation) are often used as codes for the semantics of those words. + A string of characters identifying a controlled concept, including Defined Terms and Enumerated Values when represented as character strings. The scope of the controlled concept is limited to the Attribute for which the string provides the Value; i.e., the Attribute defines the allowed set of Values for the Code String, and a particular string may have different meanings in different Attributes. A Code String is formally an arbitrary code representing a semantic concept; however, English language words (using the constrained character set of the CS Value Representation) are often used as codes for the semantics of those words. @@ -949,6 +948,12 @@ A unique identifier for a Data Element composed of an ordered pair of numbers (a Group Number followed by an Element Number). + + Data Element Tag Field + + The field within a Data Element structure that contains the Data Element Tag. + + Data Element Type @@ -961,10 +966,16 @@ Exchanged information consisting of a structured set of Attribute values directly or indirectly related to Information Objects. The value of each Attribute in a Data Set is expressed as a Data Element. A collection of Data Elements ordered by increasing Data Element Tag number that is an encoding of the values of Attributes of a real world object. + + Default Character Repertoire + + The Basic G0 Set of the International Reference Version of (ISO-IR 6) used as the default repertoire for character strings in DICOM. + + Defined Term - The Value of a Data Element is a Defined Term when the Value of the element may be one of an explicitly specified set of standard values, and these values may be extended by implementers. + The Value of a Data Element is a Defined Term when the Value of the Data Element may be one of an explicitly specified set of standard Values, and these Values may be extended by implementers. @@ -976,7 +987,13 @@ Enumerated Value - The Value of a Data Element is an Enumerated Value when the value of the element must be one of an explicitly specified set of standard values, and these values shall not be extended by implementers. + The Value of a Data Element is an Enumerated Value when the Value of the Data Element must be one of an explicitly specified set of standard Values, and these Values shall not be extended by implementers. + + + + Explicit VR + + An encoding of a Data Element structure where the Value Representation of that Data Element is specified explicitly in the Value Representation Field. @@ -992,6 +1009,13 @@ The first number in the ordered pair of numbers that makes up a Data Element Tag. + + Implicit VR + + An encoding of a Data Element structure where the Value Representation of that Data Element is specified implicitly, i.e. not in the Value Representation Field. + This encoding is used for the DICOM Default Little Endian Transfer Syntax (see ). + + Item @@ -1037,13 +1061,13 @@ Private Data Element - Additional Data Element, defined by an implementer, to communicate information that is not contained in Standard Data Elements. Private Data elements have odd Group Numbers. + Additional Data Element, defined by an implementer, to communicate information that is not contained in Standard Data Elements. Private Data Elements have odd Group Numbers. Repeating Group - Standard Data Elements within a particular range of Group Numbers where elements that have identical Element Numbers have the same meaning within each Group (and the same VR, VM, and Data Element Type). Repeating Groups shall only exist for Curves and Overlay Planes (Group Numbers (50xx,eeee) and (60xx,eeee), respectively) and are a remnant of older versions of this Standard. + Standard Data Elements within a particular range of Group Numbers where Data Elements that have identical Element Numbers have the same meaning within each Group (and the same VR, VM, and Data Element Type). Repeating Groups shall only exist for Curves and Overlay Planes (Group Numbers (50xx,eeee) and (60xx,eeee), respectively) and are a remnant of older versions of this Standard. @@ -1079,7 +1103,7 @@ Undefined Length - The ability to specify an unknown length for a Data Element Value (of Value Representation SQ, UN, OW, or OB) or Item. Data Elements and Items of Undefined Length are delimited with Sequence Delimitation Items and Item Delimiter Data Elements, respectively. + The ability to specify an unknown length for a Data Element Value (of Value Representation SQ, UN, OW, or OB) or Item. Data Elements and Items of Undefined Length are delimited with Sequence Delimitation Items and Item Delimitation Data Elements, respectively. @@ -1098,13 +1122,19 @@ Value Field - The field within a Data Element that contains the Value(s) of that Data Element. + The field within a Data Element structure that contains the Value(s) of that Data Element. Value Length - The field within a Data Element that contains the length of the Value Field of the Data Element. + The length of the Value Field of the Data Element. + + + + Value Length Field + + The field within a Data Element structure that contains the Value Length. @@ -1121,10 +1151,10 @@ Specifies the data type and format of the Value(s) contained in the Value Field of a Data Element. - - Value Representation Field + + Value Representation (VR) Field - The field where the Value Representation of a Data Element is stored in the encoding of a Data Element structure with explicit VR. + The field where the Value Representation of a Data Element is stored in the encoding of a Data Element structure with Explicit VR. @@ -1348,47 +1378,61 @@ Value Encoding - A Data Set is constructed by encoding the values of Attributes specified in the Information Object Definition (IOD) of a Real-World Object. The specific content and semantics of these Attributes are specified in Information Object Definitions (see ). The range of possible data types of these values and their encoding are specified in this section. The structure of a Data Set, which is composed of Data Elements containing these values, is specified in . + A Data Set is constructed by encoding the Values of Attributes specified in the Information Object Definition (IOD) of a Real-World Object. The specific content and semantics of these Attributes are specified in Information Object Definitions (see ). The range of possible data types of these Values and their encoding are specified in this section. The structure of a Data Set, which is composed of Data Elements containing these Values, is specified in . Throughout this Part, as well as other parts of the DICOM Standard, Tags are used to identify both specific Attributes and their corresponding Data Elements.
Support of Character Repertoires Values that are text or character strings can be composed of Graphic and Control Characters. The Graphic Character set, independent of its encoding, is referred to as a Character Repertoire. Depending on the native language context in which Application Entities wish to exchange data using the DICOM Standard, different Character Repertoires will be used. The Character Repertoires supported by DICOM are: - 8-bit single-byte coded graphic character sets + + 8-bit single-byte coded graphic character sets - Code for Information Interchange + + Code for Information Interchange - Code for the Japanese Graphic Character set for information interchange + + Code for the Japanese Graphic Character set for information interchange - Code of the supplementary Japanese Graphic Character set for information interchange + + Code of the supplementary Japanese Graphic Character set for information interchange - (registered as ISO-IR 149) for Korean Language + + (registered as ISO-IR 149) for Korean Language - Thai Characters Code for Information Interchange + + Thai Characters Code for Information Interchange - for the Unicode character set + + for the Unicode character set - + + + - + + + - + + + - corresponds to the Unicode character set. The ISO IR 192 corresponds to the use of the UTF-8 encoding for this character set. + + corresponds to the Unicode character set. The ISO IR 192 corresponds to the use of the UTF-8 encoding for this character set. The character set is harmonized with the Unicode character set on a regular basis, to reflect updates from both the Chinese language and from Unicode extensions to support other languages. @@ -1424,7 +1468,8 @@ - does not differentiate between a code element, e.g., G0, and the area in the code table, e.g., GL, where it is invoked. The term "G0" specifies the code element as well as the area in the code table. In ISO/IEC 2022 there is a clear distinction between the code elements (G0, G1, G2, and G3) and the areas in which the code elements are invoked (GL or GR). In this Standard the nomenclature of ISO/IEC 2022 is used. + + does not differentiate between a code element, e.g., G0, and the area in the code table, e.g., GL, where it is invoked. The term "G0" specifies the code element as well as the area in the code table. In ISO/IEC 2022 there is a clear distinction between the code elements (G0, G1, G2, and G3) and the areas in which the code elements are invoked (GL or GR). In this Standard the nomenclature of ISO/IEC 2022 is used. The Control Character set C0 shall be invoked in CL and the Graphic Character sets G0 and G1 in GL and GR respectively. Only some Control Characters from the C0 set are used in DICOM (see ), and characters from the C1 set shall not be used.
@@ -1444,14 +1489,14 @@ The Attribute Specific Character Set (0008,0005) is encoded using a subset of characters from ISO-IR 6. See the definition for the Value Representation (VR) of Code String (CS) in . - For Data Elements with Value Representations of SH (Short String), LO (Long String), UC (Unlimited Characters), ST (Short Text), LT (Long Text), UT (Unlimited Text) or PN (Person Name) the Default Character Repertoire may be extended or replaced (these Value Representations are described in more detail in ). If such an extension or replacement is used, the relevant "Specific Character Set" shall be defined as an attribute of the SOP Common Module (0008,0005) (see ) and shall be stated in the Conformance Statement. gives conformance guidelines. + For Data Elements with Value Representations of SH (Short String), LO (Long String), UC (Unlimited Characters), ST (Short Text), LT (Long Text), UT (Unlimited Text) or PN (Person Name) the Default Character Repertoire may be extended or replaced (these Value Representations are described in more detail in ). If such an extension or replacement is used, the relevant "Specific Character Set" shall be defined as an Attribute of the SOP Common Module (0008,0005) (see ) and shall be stated in the Conformance Statement. gives conformance guidelines. Preferred repertoires as defined in ENV 41 503 and ENV 41 508 for the use in Western and Eastern Europe, respectively, are: ISO-IR 100, ISO-IR 101, ISO-IR 144, ISO-IR 126. See . - Information Object Definitions using different character sets cannot rely per se on lexical ordering or string comparison of data elements represented as character strings. These operations can only be carried out within a given character repertoire and not across repertoire boundaries. + Information Object Definitions using different character sets cannot rely per se on lexical ordering or string comparison of Data Elements represented as character strings. These operations can only be carried out within a given character repertoire and not across repertoire boundaries. @@ -1462,7 +1507,7 @@ This replacement character repertoire does not apply to other textual Value Representations (AE and CS). - The replacement character repertoire shall be specified in value 1 of the Attribute Specific Character Set (0008,0005). Defined Terms for the Attribute Specific Character Set are specified in . + The replacement character repertoire shall be specified in Value 1 of the Attribute Specific Character Set (0008,0005). Defined Terms for the Attribute Specific Character Set are specified in . @@ -1478,16 +1523,16 @@ Two character codes of the single-byte character sets invoked in the GL area of the code table, 02/00 and 05/12, have special significance in the DICOM Standard. The character SPACE, represented by bit combination 02/00, shall be used for the padding of Data Element Values that are character strings. The Graphic Character represented by the bit combination 05/12, "\" (BACKSLASH) in the repertoire ISO-IR 6, shall only be used in character strings with Value Representations of UT, ST and LT (see ). Otherwise the character code 05/12 is used as a separator for multi-valued Data Elements (see ). - When the value of the Attribute Specific Character Set (0008,0005) is either "ISO_IR 13" or "ISO 2022 IR 13", the graphic character represented by the bit combination 05/12 is a "¥" (YEN SIGN) in the character set of ISO-IR 14. + When the Value of the Attribute Specific Character Set (0008,0005) is either "ISO_IR 13" or "ISO 2022 IR 13", the graphic character represented by the bit combination 05/12 is a "¥" (YEN SIGN) in the character set of ISO-IR 14. The character DELETE (bit combination 07/15) shall not be used in DICOM character strings. - The replacement Character Repertoire specified in value 1 of the Attribute Specific Character Set (0008,0005) (or the Default Character Repertoire if value 1 is empty) may be further extended with additional Coded Character Sets, if needed and permitted by the replacement Character Repertoire. The additional Coded Character Sets and extension mechanism shall be specified in additional values of the Attribute Specific Character Set. If Attribute Specific Character Set (0008,0005) has a single value, the DICOM SOP Instance supports only one code table and no Code Extension techniques. If Attribute Specific Character Set (0008,0005) has multiple values, the DICOM SOP Instance supports Code Extension techniques as described in ISO/IEC 2022:1994. + The replacement Character Repertoire specified in Value 1 of the Attribute Specific Character Set (0008,0005) (or the Default Character Repertoire if Value 1 is empty) may be further extended with additional Coded Character Sets, if needed and permitted by the replacement Character Repertoire. The additional Coded Character Sets and extension mechanism shall be specified in additional Values of the Attribute Specific Character Set. If Attribute Specific Character Set (0008,0005) has a single Value, the DICOM SOP Instance supports only one code table and no Code Extension techniques. If Attribute Specific Character Set (0008,0005) has multiple Values, the DICOM SOP Instance supports Code Extension techniques as described in ISO/IEC 2022:1994. The Character Repertoires that prohibit extension are identified in Part 3. Considerations on the Handling of Unsupported Character Sets: - In DICOM, character sets are not negotiated between Application Entities but are indicated by a conditional attribute of the SOP Common Module. Therefore, implementations may be confronted with character sets that are unknown to them. + In DICOM, character sets are not negotiated between Application Entities but are indicated by a conditional Attribute of the SOP Common Module. Therefore, implementations may be confronted with character sets that are unknown to them. The Unicode Standard includes a substantial discussion of the recommended means for display and print for characters that lack font support. These same recommendations may apply to the mechanisms for unsupported character sets. The machine should print or display such characters by replacing all unknown characters with the four characters "\nnn", where "nnn" is the three digit octal representation of each byte. An example of this for an ASCII based machine would be as follows: @@ -1502,7 +1547,7 @@ The Unicode standard and the standard define mechanisms for print and display of characters that are missing from the available fonts. If GBK is specified in Specific Character Set (0008,0005), the rules of print and display of characters shall apply. The DICOM Standard does not specify user interface behavior since it does not affect network or media data exchange. - The Unicode and standards have distinct Yen symbol, backslash, and several forms of reverse solidus. The separator for multi-valued data elements in DICOM is the character valued 05/12 regardless of what glyph is used to enter or display this character. The other reverse solidus characters that have a very similar appearance are not separators. The choice of font can affect the appearance of 05/12 significantly. Multi-byte encoding systems, such as , and , may generate encodings that contain a byte valued 05/12. Only the character that encodes as a single byte valued 05/12 is a delimiter. + The Unicode and standards have distinct Yen symbol, backslash, and several forms of reverse solidus. The separator for multi-valued Data Elements in DICOM is the character valued 05/12 regardless of what glyph is used to enter or display this character. The other reverse solidus characters that have a very similar appearance are not separators. The choice of font can affect the appearance of 05/12 significantly. Multi-byte encoding systems, such as , and , may generate encodings that contain a byte valued 05/12. Only the character that encodes as a single byte valued 05/12 is a delimiter. For multi-valued Data Elements, existing implementations that are expecting only single-byte replacement character sets may misinterpret the Value Multiplicity of the Data Element as a consequence of interpreting 05/12 bytes in multi-byte characters or escape sequences as delimiters, and this may affect the integrity of store-and-forward operations. Applications that do not explicitly state support for , or in their conformance statement, might exhibit such behavior. @@ -1510,8 +1555,8 @@
Code Extension Techniques - For Data Elements with Value Representations of SH (Short String), LO (Long String), UC (Unlimited Characters), ST (Short Text), LT (Long Text), UT (Unlimited Text) or PN (Person Name), the Default Character Repertoire or the character repertoire specified by value 1 of Attribute Specific Character Set (0008,0005), may be extended using the Code Extension techniques specified by ISO/IEC 2022:1994. - If such Code Extension techniques are used, the related Specific Character Set or Sets shall be specified by value 2 to value n of the Attribute Specific Character Set (0008,0005) of the SOP Common Module (see ), and shall be stated in the Conformance Statement. + For Data Elements with Value Representations of SH (Short String), LO (Long String), UC (Unlimited Characters), ST (Short Text), LT (Long Text), UT (Unlimited Text) or PN (Person Name), the Default Character Repertoire or the character repertoire specified by Value 1 of Attribute Specific Character Set (0008,0005), may be extended using the Code Extension techniques specified by ISO/IEC 2022:1994. + If such Code Extension techniques are used, the related Specific Character Set or Sets shall be specified by Value 2 to Value n of the Attribute Specific Character Set (0008,0005) of the SOP Common Module (see ), and shall be stated in the Conformance Statement. @@ -1521,7 +1566,7 @@ Support for Japanese kanji (ideographic), hiragana (phonetic), katakana (phonetic), Korean (Hangul phonetic and Hanja ideographic) and Chinese characters is defined in . - The Chinese Character Set (GB18030) and Unicode do not allow the use of Code Extension Techniques. If either of these character sets is used, no other character set may be specified in the Specific Character Set (0008,0005) attribute, that is, it may have only one value. + The Chinese Character Set (GB18030) and Unicode do not allow the use of Code Extension Techniques. If either of these character sets is used, no other character set may be specified in the Specific Character Set (0008,0005) Attribute, that is, it may have only one Value. @@ -1556,8 +1601,8 @@
Requirements - The character set specified by value 1 of the Attribute Specific Character Set (0008,0005), or the Default Character Repertoire if value 1 is missing, shall be active at the beginning of each textual Data Element value, and at the beginning of each line (i.e., after a CR and/or LF) or page (i.e., after an FF). - If within a textual value a character set other than the one specified in value 1 of the Attribute Specific Character Set (0008,0005), or the Default Character Repertoire if value 1 is missing, has been invoked, the character set specified in the value 1, or the Default Character Repertoire if value 1 is missing, shall be active in the following instances: + The character set specified by Value 1 of the Attribute Specific Character Set (0008,0005), or the Default Character Repertoire if Value 1 is missing, shall be active at the beginning of each textual Data Element Value, and at the beginning of each line (i.e., after a CR and/or LF) or page (i.e., after an FF). + If within a textual Value a character set other than the one specified in Value 1 of the Attribute Specific Character Set (0008,0005), or the Default Character Repertoire if Value 1 is missing, has been invoked, the character set specified in the Value 1, or the Default Character Repertoire if Value 1 is missing, shall be active in the following instances: before the end of line (i.e., before the CR and/or LF) @@ -1569,13 +1614,13 @@ before any other Control Character other than ESC (e.g., before any TAB) - before the end of a Data Element value (e.g., before the 05/12 character code that separates multiple textual Data Element Values - 05/12 corresponds to "\" (BACKSLASH) in the case of default repertoire IR-6 or "¥" (YEN SIGN) in the case of IR-14). + before the end of a Data Element Value (e.g., before the 05/12 character code that separates multiple textual Data Element Values - 05/12 corresponds to "\" (BACKSLASH) in the case of default repertoire IR-6 or "¥" (YEN SIGN) in the case of IR-14). before the "^" and "=" delimiters separating name components and name component groups in Data Elements with a VR of PN. - If within a textual value a character set other than the one specified in value 1 of the Attribute Specific Character Set (0008,0005), or the Default Character Repertoire if value 1 is missing, is used, the Escape Sequence of this character set must be inserted explicitly in the following instances: + If within a textual Value a character set other than the one specified in Value 1 of the Attribute Specific Character Set (0008,0005), or the Default Character Repertoire if Value 1 is missing, is used, the Escape Sequence of this character set must be inserted explicitly in the following instances: before the first use of the character set in the line @@ -1584,14 +1629,14 @@ before the first use of the character set in the page - before the first use of the character set in the Data Element value + before the first use of the character set in the Data Element Value before the first use of the character set in the name component and name component group in Data Element with a VR of PN - These requirements allow an application to skip lines, values, or components in a textual data element and start the new line with a defined character set without the need to track the character set changes in the text skipped. A similar restriction appears in the RFCs describing the use of multi-byte character sets over the Internet. An Escape Sequence switching to the value 1 or default Specific Character Set is not needed within a line, value, or component if no Code Extensions are present. Nor is a switch needed to the value 1 or default Specific Character Set if this character set has only the G0 Code Element defined, and the G0 Code Element is still active. + These requirements allow an application to skip lines, values, or components in a textual Data Element and start the new line with a defined character set without the need to track the character set changes in the text skipped. A similar restriction appears in the RFCs describing the use of multi-byte character sets over the Internet. An Escape Sequence switching to the Value 1 or default Specific Character Set is not needed within a line, value, or component if no Code Extensions are present. Nor is a switch needed to the Value 1 or default Specific Character Set if this character set has only the G0 Code Element defined, and the G0 Code Element is still active.
@@ -1615,7 +1660,7 @@ - Attribute Specific Character Set (0008,0005) single value other than "ISO_IR 192", "GB18030" or "GBK": + Attribute Specific Character Set (0008,0005) single Value other than "ISO_IR 192", "GB18030" or "GBK": 8-bit code @@ -1624,7 +1669,7 @@ Implementation level: Level 1 - Elementary 8-bit code (code-level identifier 11) - Initial designation: One of the defined character sets, or the 8-bit code table of specified by value 1 of the Attribute Specific Character Set (0008,0005), as G0 and G1. + Initial designation: One of the defined character sets, or the 8-bit code table of specified by Value 1 of the Attribute Specific Character Set (0008,0005), as G0 and G1. Code Extension shall not be used. @@ -1641,15 +1686,15 @@ Implementation level: Level 4 - Redesignation of Graphic Character Sets within a Code (code-level identifier 14) - Initial designation: One of the defined character sets, or the 8-bit code table of specified by value 1 of the Attribute Specific Character Set (0008,0005), as G0 and G1. If value 1 of the Attribute Specific Character Set (0008,0005) is empty, ISO-IR 6 (ASCII) is assumed as G0, and G1 is undefined. + Initial designation: One of the defined character sets, or the 8-bit code table of specified by Value 1 of the Attribute Specific Character Set (0008,0005), as G0 and G1. If Value 1 of the Attribute Specific Character Set (0008,0005) is empty, ISO-IR 6 (ASCII) is assumed as G0, and G1 is undefined. - All character sets specified in the various values of Attribute Specific Character Set (0008,0005), including value 1, may participate in Code Extension. + All character sets specified in the various Values of Attribute Specific Character Set (0008,0005), including Value 1, may participate in Code Extension. - Attribute Specific Character Set (0008,0005) single value "ISO_IR 192", "GB18030" or "GBK": + Attribute Specific Character Set (0008,0005) single Value "ISO_IR 192", "GB18030" or "GBK": variable length code @@ -1658,7 +1703,7 @@ Implementation level: not specified (not compatible with ) - Initial designation: as specified by value 1 of the Attribute Specific Character Set (0008,0005) + Initial designation: as specified by Value 1 of the Attribute Specific Character Set (0008,0005) Code Extension shall not be used. @@ -1769,7 +1814,7 @@ Value Representation (VR) The Value Representation of a Data Element describes the data type and format of that Data Element's Value(s). lists the VR of each Data Element by Data Element Tag. Values with VRs constructed of character strings, except in the case of the VR UI, shall be padded with SPACE characters (20H, in the Default Character Repertoire) when necessary to achieve even length. Values with a VR of UI shall be padded with a single trailing NULL (00H) character when necessary to achieve even length. Values with a VR of OB shall be padded with a single trailing NULL byte value (00H) when necessary to achieve even length. - All new VRs defined in future versions of DICOM shall be of the same Data Element Structure as defined in with reserved bytes after the VR and a 32-bit unsigned integer VL (i.e., following the format for VRs such as OB or UT), and may or may not permit undefined length. + All new VRs defined in future versions of DICOM shall be of the same Data Element Structure as defined in with reserved bytes after the VR and a 32-bit unsigned integer VL (i.e., following the format for VRs such as OB or UT), and may or may not permit Undefined Length. @@ -1782,13 +1827,13 @@ If the endianness of the Transfer Syntaxes is the same, the Value of the Data Element may be copied unchanged and if the target Transfer Syntax is Explicit VR, the VR bytes copied unchanged. In practice this only applies to Little Endian Transfer Syntaxes, since there was only one Big Endian Transfer Syntax defined. - If the source Transfer Syntax is Little Endian and the target Transfer Syntax is the (retired) Big Endian Explicit VR Transfer Syntax, then the Value of the Data Element may be copied unchanged and the VR changed to UN, since being unrecognized, whether or not byte swapping is required is unknown. If the VR were copied unchanged, the byte order of the value might or might not be incorrect. + If the source Transfer Syntax is Little Endian and the target Transfer Syntax is the (retired) Big Endian Explicit VR Transfer Syntax, then the Value of the Data Element may be copied unchanged and the VR changed to UN, since being unrecognized, whether or not byte swapping is required is unknown. If the VR were copied unchanged, the byte order of the Value might or might not be incorrect. - If the source Transfer Syntax is the (retired) Big Endian Explicit VR Transfer Syntax, then the Data Element cannot be copied, because whether or not byte swapping is required is unknown, and there is no equivalent of the UN VR to use when the value is big endian rather than little endian. + If the source Transfer Syntax is the (retired) Big Endian Explicit VR Transfer Syntax, then the Data Element cannot be copied, because whether or not byte swapping is required is unknown, and there is no equivalent of the UN VR to use when the Value is big endian rather than little endian. - The issues of whether or not the element may be copied, and what VR to use if copying, do not arise when converting a Data Set from Implicit VR Little Endian Transfer Syntax, since the VR would not be present to be unrecognized, and if the data element VR is not known from a data dictionary, then UN would be used. + The issues of whether or not the Data Element may be copied, and what VR to use if copying, do not arise when converting a Data Set from Implicit VR Little Endian Transfer Syntax, since the VR would not be present to be unrecognized, and if the Data Element VR is not known from a data dictionary, then UN would be used. @@ -1830,7 +1875,7 @@ Application Entity
- A string of characters that identifies an Application Entity with leading and trailing spaces (20H) being non-significant. A value consisting solely of spaces shall not be used. + A string of characters that identifies an Application Entity with leading and trailing spaces (20H) being non-significant. A Value consisting solely of spaces shall not be used. Default Character Repertoire excluding character code 5CH (the BACKSLASH "\" in ISO-IR 6), and all control characters. @@ -1861,10 +1906,10 @@ Attribute Tag - Ordered pair of 16-bit unsigned integers that is the value of a Data Element Tag. + Ordered pair of 16-bit unsigned integers that is the Value of a Data Element Tag. Example: A Data Element Tag of (0018,00FF) would be encoded as a series of 4 bytes in a Little-Endian Transfer Syntax as 18H,00H,FFH,00H. - The encoding of an AT value is exactly the same as the encoding of a Data Element Tag as defined in . + The encoding of an AT Value is exactly the same as the encoding of a Data Element Tag as defined in . @@ -1881,12 +1926,15 @@ A string of characters identifying a controlled concept. Leading or trailing spaces (20H) are not significant. + Alternatively, in the context of a Query with Empty Value Matching (see ), a string of two QUOTATION MARK characters, representing an empty key Value. Uppercase characters, "0"-"9", the SPACE character, and underscore "_", of the Default Character Repertoire + In the context of a Query with Empty Value Matching (see ), the QUOTATION MARK character is allowed. 16 bytes maximum + In the context of a Query with Empty Value Matching (see ), the length is 2 bytes fixed.
"0"-"9" of Default Character Repertoire - In the context of a Query with range matching (see ), the character "-" is allowed, and a trailing SPACE character is allowed for padding. + In the context of a Query with Range Matching (see ), the character "-" is allowed, and a trailing SPACE character is allowed for padding. + In the context of a Query with Empty Value Matching (see ), the QUOTATION MARK character is allowed. 8 bytes fixed - In the context of a Query with range matching (see ), the length is 18 bytes maximum. + In the context of a Query with Range Matching (see ), the length is 18 bytes maximum. + In the context of a Query with Empty Value Matching (see ), the length is 2 bytes fixed.
A string of characters representing either a fixed point number or a floating point number. A fixed point number shall contain only the characters 0-9 with an optional leading "+" or "-" and an optional "." to mark the decimal point. A floating point number shall be conveyed as defined in ANSI X3.9, with an "E" or "e" to indicate the start of the exponent. Decimal Strings may be padded with leading or trailing spaces. Embedded spaces are not allowed. - Data Elements with multiple values using this VR may not be properly encoded if Explicit-VR Transfer Syntax is used and the VL of this attribute exceeds 65534 bytes. + Data Elements with multiple Values using this VR may not be properly encoded if Explicit-VR Transfer Syntax is used and the VL of this Data Element exceeds 65534 bytes. @@ -1957,9 +2008,10 @@ The year, month, and day shall be interpreted as a date of the Gregorian calendar system. A 24-hour clock is used. Midnight shall be represented by only "0000" since "2400" would violate the hour range. The Fractional Second component, if present, shall contain 1 to 6 digits. If Fractional Second is unspecified the preceding "." shall not be included. The offset suffix, if present, shall contain 4 digits. The string may be padded with trailing SPACE characters. Leading and embedded spaces are not allowed. - A component that is omitted from the string is termed a null component. Trailing null components of Date Time indicate that the value is not precise to the precision of those components. The YYYY component shall not be null. Non-trailing null components are prohibited. The optional suffix is not considered as a component. - A Date Time value without the optional suffix is interpreted to be in the local time zone of the application creating the Data Element, unless explicitly specified by the Timezone Offset From UTC (0008,0201). - UTC offsets are calculated as "local time minus UTC". The offset for a Date Time value in UTC shall be +0000. + A component that is omitted from the string is termed a null component. Trailing null components of Date Time indicate that the Value is not precise to the precision of those components. The YYYY component shall not be null. Non-trailing null components are prohibited. The optional suffix is not considered as a component. + A Date Time Value without the optional suffix is interpreted to be in the local time zone of the application creating the Data Element, unless explicitly specified by the Timezone Offset From UTC (0008,0201). + UTC offsets are calculated as "local time minus UTC". The offset for a Date Time Value in UTC shall be +0000. + Alternatively, in the context of a Query with Empty Value Matching (see ), a string of two QUOTATION MARK characters, representing an empty key Value. @@ -1969,23 +2021,25 @@ The RFC 2822 use of -0000 as an offset to indicate local time is not allowed. - A Date Time value of 195308 means August 1953, not specific to particular day. A Date Time value of 19530827111300.0 means August 27, 1953, 11;13 a.m. accurate to 1/10th second. + A Date Time Value of 195308 means August 1953, not specific to particular day. A Date Time Value of 19530827111300.0 means August 27, 1953, 11;13 a.m. accurate to 1/10th second. - The Second component may have a value of 60 only for a leap second. + The Second component may have a Value of 60 only for a leap second. - The offset may be included regardless of null components; e.g., 2007-0500 is a legal value. + The offset may be included regardless of null components; e.g., 2007-0500 is a legal Value. "0"-"9", "+", "-", "." and the SPACE character of Default Character Repertoire + In the context of a Query with Empty Value Matching (see ), the QUOTATION MARK character is allowed. 26 bytes maximum - In the context of a Query with range matching (see ), the length is 54 bytes maximum. + In the context of a Query with Range Matching (see ), the length is 54 bytes maximum. + In the context of a Query with Empty Value Matching (see ), the length is 2 bytes fixed.
- A character string that may be padded with leading and/or trailing spaces. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between values in multi-valued data elements. The string shall not have Control Characters except for ESC. + A character string that may be padded with leading and/or trailing spaces. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between Values in multi-valued Data Elements. The string shall not have Control Characters except for ESC. Default Character Repertoire and/or as defined by (0008,0005) excluding character code 5CH (the BACKSLASH "\" in ISO-IR 6), and all Control Characters except ESC when used for escape sequences. @@ -2161,7 +2215,7 @@ Person Name - A character string encoded using a 5 component convention. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between values in multi-valued data elements. The string may be padded with trailing spaces. For human use, the five components in their order of occurrence are: family name complex, given name complex, middle name, name prefix, name suffix. + A character string encoded using a 5 component convention. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between Values in multi-valued Data Elements. The string may be padded with trailing spaces. For human use, the five components in their order of occurrence are: family name complex, given name complex, middle name, name prefix, name suffix. HL7 prohibits leading spaces within a component; DICOM allows leading and trailing spaces and considers them insignificant. @@ -2187,7 +2241,7 @@ Short String - A character string that may be padded with leading and/or trailing spaces. The character code 05CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between values for multiple data elements. The string shall not have Control Characters except ESC. + A character string that may be padded with leading and/or trailing spaces. The character code 05CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between Values for multi-valued Data Elements. The string shall not have Control Characters except ESC. Default Character Repertoire and/or as defined by (0008,0005) excluding character code 5CH (the BACKSLASH "\" in ISO-IR 6) and all Control Characters except ESC when used for escape sequences. @@ -2283,7 +2337,7 @@ A string of characters of the format HHMMSS.FFFFFF; where HH contains hours (range "00" - "23"), MM contains minutes (range "00" - "59"), SS contains seconds (range "00" - "60"), and FFFFFF contains a fractional part of a second as small as 1 millionth of a second (range "000000" - "999999"). A 24-hour clock is used. Midnight shall be represented by only "0000" since "2400" would violate the hour range. The string may be padded with trailing spaces. Leading and embedded spaces are not allowed. - One or more of the components MM, SS, or FFFFFF may be unspecified as long as every component to the right of an unspecified component is also unspecified, which indicates that the value is not precise to the precision of those unspecified components. + One or more of the components MM, SS, or FFFFFF may be unspecified as long as every component to the right of an unspecified component is also unspecified, which indicates that the Value is not precise to the precision of those unspecified components. The FFFFFF component, if present, shall contain 1 to 6 digits. If FFFFFF is unspecified the preceding "." shall not be included. Examples: @@ -2294,7 +2348,7 @@ "1010" represents a time of 10 hours, and 10 minutes. - "021 " is an invalid value. + "021 " is an invalid Value. @@ -2306,18 +2360,21 @@ See also DT VR in this table. - The SS component may have a value of 60 only for a leap second. + The SS component may have a Value of 60 only for a leap second. + Alternatively, in the context of a Query with Empty Value Matching (see ), a string of two QUOTATION MARK characters, representing an empty key Value. "0"-"9", "." and the SPACE character of Default Character Repertoire - In the context of a Query with range matching (see ), the character "-" is allowed. + In the context of a Query with Range Matching (see ), the character "-" is allowed. + In the context of a Query with Empty Value Matching (see ), the QUOTATION MARK character is allowed. 14 bytes maximum - In the context of a Query with range matching (see ), the length is 28 bytes maximum. + In the context of a Query with Range Matching (see ), the length is 28 bytes maximum. + In the context of a Query with Empty Value Matching (see ), the length is 2 bytes fixed.
- A character string that may be of unlimited length that may be padded with trailing spaces. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between values in multi-valued data elements. The string shall not have Control Characters except for ESC. + A character string that may be of unlimited length that may be padded with trailing spaces. The character code 5CH (the BACKSLASH "\" in ISO-IR 6) shall not be present, as it is used as the delimiter between Values in multi-valued Data Elements. The string shall not have Control Characters except for ESC. Default Character Repertoire and/or as defined by (0008,0005) excluding character code 5CH (the BACKSLASH "\" in ISO-IR 6), and all Control Characters except ESC when used for escape sequences. @@ -2393,21 +2450,24 @@ Leading spaces are not allowed. Trailing spaces shall be ignored. Data Elements with this VR shall not be multi-valued. + Alternatively, in the context of a Query with Empty Value Matching (see ), a string of two QUOTATION MARK characters, representing an empty key Value. -Both absolute and relative URIs are permitted. If the URI is relative, then it is relative to the base URI of the object within which it is contained. - + Both absolute and relative URIs are permitted. + If the URI is relative, then it is relative to the base URI of the object within which it is contained, or to a base URI in another Attribute as specified by the Information Object Definition. + The subset of the Default Character Repertoire required for the URI as defined in IETF RFC3986 Section 2, plus the space (20H) character permitted only as trailing padding. Characters outside the permitted character set must be "percent encoded". -The Backslash (5CH) character is among those disallowed in URIs. - + The Backslash (5CH) character is among those disallowed in URIs. + + In the context of a Query with Empty Value Matching (see ), the QUOTATION MARK character is allowed. 232-2 bytes maximum. - See - + See . + In the context of a Query with Empty Value Matching (see ), the length is 2 bytes fixed.
- FFFF FFFFH undefined length + FFFF FFFFH Undefined Length @@ -3396,7 +3461,7 @@ (gggg, eeee) with VR of SQ - FFFF FFFFH undefined length + FFFF FFFFH Undefined Length @@ -3428,7 +3493,7 @@ Item Tag (FFFE, E000) - Item Length FFFF FFFFH undefined length + Item Length FFFF FFFFH Undefined Length Item Value Data Set @@ -3469,7 +3534,7 @@ 4 bytes - undefined length + Undefined Length 4 bytes @@ -3489,16 +3554,16 @@
Sequence Inheritance - An encapsulated Data Set shall only include the Specific Character Set (0008,0005) data element if the Attribute Specific Character Set is defined in the IOD for that sequence of items. + An encapsulated Data Set shall only include the Specific Character Set (0008,0005) Data Element if the Attribute Specific Character Set is defined in the IOD for that sequence of items. - An encapsulated Data Set does not include the Specific Character Set data element unless the Specific Character Set Attribute is defined as part of the IOD for that sequence. + An encapsulated Data Set does not include the Specific Character Set Data Element unless the Specific Character Set Attribute is defined as part of the IOD for that sequence. - If an encapsulated Data Set includes the Specific Character Set Attribute, it shall apply only to the encapsulated Data Set. If the Attribute Specific Character Set is not explicitly included in an encapsulated Data Set, then the Specific Character Set value of the encapsulating Data Set applies. + If an encapsulated Data Set includes the Specific Character Set Attribute, it shall apply only to the encapsulated Data Set. If the Attribute Specific Character Set is not explicitly included in an encapsulated Data Set, then the Specific Character Set Value of the encapsulating Data Set applies.
Repeating Groups - Multiple Overlay Planes and Curves are often associated with a single Image (see ). Standard Data Elements with even Group Numbers (5000-501E,eeee) represent Curves, while elements with even Group Numbers (6000-601E,eeee) represent Overlay Planes. Both of these ranges of Group numbers are known as Repeating Groups. This use of group numbers is a remnant of older versions of this Standard, which associated a semantic meaning with particular Groups. + Multiple Overlay Planes and Curves are often associated with a single Image (see ). Standard Data Elements with even Group Numbers (5000-501E,eeee) represent Curves, while Data Elements with even Group Numbers (6000-601E,eeee) represent Overlay Planes. Both of these ranges of Group numbers are known as Repeating Groups. This use of group numbers is a remnant of older versions of this Standard, which associated a semantic meaning with particular Groups. In each of these ranges of Group Numbers, Standard Data Elements that have identical Element Numbers have the same meaning within each Group (and the same VR, VM, and Data Element Type). The notation (50xx,eeee) and (60xx,eeee) are used for the Group Number in Data Element Tags when referring to a common Data Element across these groups (see ). Groups (50xx,eeee) and (60xx,eeee) are called Repeating Groups because of these characteristics. Repeating Groups shall only be allowed in the even Groups (6000-601E,eeee) and even Groups (5000-501E,eeee) cases. In the future, Data Elements with VRs of SQ shall be used to serve a similar purpose. @@ -3512,7 +3577,7 @@
Private Data Elements Implementations may require communication of information that cannot be contained in Standard Data Elements. Private Data Elements are intended to be used to contain such information. Such Private Data Elements shall not change the semantics of the Information Object Definition or SOP Class Definition. - Private Data Elements have the same structure as Standard Data Elements specified earlier in (i.e., Data Element Tag field, optional VR field, length field, and value field). The Group Number used in the Element Tag of Private Data Elements shall be an odd number. Private Data Elements shall be contained in the Data Set in increasing numeric order of Data Element Tag. The Value Field of a Private data element shall have one of the VRs specified by this Standard in . + Private Data Elements have the same structure as Standard Data Elements specified earlier in (i.e., Data Element Tag Field, optional VR Field, Value Length Field, and Value Field). The Group Number used in the Element Tag of Private Data Elements shall be an odd number. Private Data Elements shall be contained in the Data Set in increasing numeric order of Data Element Tag. The Value Field of a Private Data Element shall have one of the VRs specified by this Standard in . For each Information Object Definition or SOP Class Definition, certain Data Elements are required (Data Element Type 1, 1C, 2, or 2C) as specified in and . Private Data Elements shall not be used in place of required Standard Data Elements.
Private Data Element Tags @@ -3524,7 +3589,7 @@ - If an implementer needs repetitions of a private element, a private Sequence attribute (see ) may be used to contain each of the repeated elements in separate items. + If an implementer needs repetitions of a Private Data Element, a private Sequence Data Element (see ) may be used to contain each of the repeated Private Data Elements in separate items. Each item needs to claim the corresponding private block of Elements, as described below. @@ -3540,7 +3605,7 @@ - Private Creator Data Element (gggg,0010) is required in order to identify elements (gggg,1000-10FF) if present, Private Creator Data Element (gggg,0011) is required in order to identify elements (gggg,1100-11FF) if present, through Private Creator Data Element (gggg,00FF), which identifies elements (gggg,FF00-FFFF) if present. + Private Creator Data Element (gggg,0010) is required in order to identify Data Elements (gggg,1000-10FF) if present, Private Creator Data Element (gggg,0011) is required in order to identify Data Elements (gggg,1100-11FF) if present, through Private Creator Data Element (gggg,00FF), which identifies Data Elements (gggg,FF00-FFFF) if present. Encoders of Private Data Elements shall be able to dynamically assign private data to any available (unreserved) block(s) within the Private group, and specify this assignment through the blocks corresponding Private Creator Data Element(s). Decoders of Private Data shall be able to accept reserved blocks with a given Private Creator identification code at any position within the Private group specified by the blocks corresponding Private Creator Data Element. @@ -3550,10 +3615,10 @@ Older versions of this Standard described shadow groups. These were groups with a group number one greater than the standard groups. Elimination of conflicts in Private Data Element Tags have made this distinction obsolete and this terminology has been retired. - Older versions of this Standard specified private group element numbers (gggg,10FF-7FFF) reserved for manufacturers and private group element numbers (gggg, 8100-FFFF) reserved for users. Elimination of conflicts in Private Data Element Tags has made this distinction obsolete and this specification has been retired. + Older versions of this Standard specified private group Data Element numbers (gggg,10FF-7FFF) reserved for manufacturers and private group Data Element numbers (gggg, 8100-FFFF) reserved for users. Elimination of conflicts in Private Data Element Tags has made this distinction obsolete and this specification has been retired. - The requirements of this section do not allow any use of elements in the ranges (gggg,0001-000F) and (gggg,0100-0FFF) where gggg is odd. + The requirements of this section do not allow any use of Data Elements in the ranges (gggg,0001-000F) and (gggg,0100-0FFF) where gggg is odd. @@ -3615,7 +3680,7 @@
- Sequence containing repeating attributes + Sequence containing repeating Attributes
@@ -4234,12 +4319,12 @@
Valid Values of Pixel Data Related Attributes for JPEG Lossy Transfer Syntaxes using Standard Photometric Interpretations
The Pixel Data characteristics included in the JPEG Interchange Format shall be used to decode the compressed data stream. - If APP2 marker segments with an identifier of "ICC_PROFILE" (as defined in Annex B of ) are present in the compressed data stream, their concatenated value shall be identical to the value of ICC Profile (0028,2000) Attribute, if present, excluding padding. + If APP2 marker segments with an identifier of "ICC_PROFILE" (as defined in Annex B of ) are present in the compressed data stream, their concatenated value shall be identical to the Value of ICC Profile (0028,2000) Attribute, if present, excluding padding. These requirements were formerly specified in terms of the "uncompressed pixel data from which the compressed data stream was derived". However, since the form of the "original" uncompressed data stream could vary between different implementations, this requirement is now specified in terms of consistency with what is encapsulated. - When decompressing, should the characteristics explicitly specified in the compressed data stream (e.g., spatial subsampling or number of components or planar configuration) be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream (e.g., spatial subsampling or number of components or planar configuration) be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. Those characteristics not explicitly specified in the compressed data stream (e.g., the color space of the compressed components, which is not specified in the JPEG Interchange Format), or implied by the definition of the compression scheme (e.g., always unsigned in JPEG), can therefore be determined from the DICOM Data Element in the enclosing Data Set. For example a Photometric Interpretation of "YBR_FULL_422" would describe the color space that is commonly used to lossy compress images using JPEG. @@ -4253,7 +4338,7 @@ Should the compression process be incapable of encoding a particular form of pixel data representation (e.g., JPEG cannot encode signed integers, only unsigned integers), then ideally only the appropriate form should be "fed" into the compression process. However, for certain characteristics described in DICOM Data Elements but not explicitly described in the compressed data stream (such as Pixel Representation), then the DICOM Data Element should be considered to describe what has been compressed (e.g., the pixel data really is to be interpreted as signed if Pixel Representation so specifies). - DICOM Data Elements should not describe characteristics that are beyond the capability of the compression scheme used. For example, JPEG lossy processes are limited to 12 bits, hence the value of Bits Stored should be 12 or less. Bits Allocated is irrelevant, and is likely to be constrained by the Information Object Definition in to values of 8 or 16. Also, JPEG compressed data streams are always color-by-pixel and should be specified as such (a decoder can essentially ignore this element however as the value for JPEG compressed data is already known). + DICOM Data Elements should not describe characteristics that are beyond the capability of the compression scheme used. For example, JPEG lossy processes are limited to 12 bits, hence the Value of Bits Stored should be 12 or less. Bits Allocated is irrelevant, and is likely to be constrained by the Information Object Definition in to Values of 8 or 16. Also, JPEG compressed data streams are always color-by-pixel and should be specified as such (a decoder can essentially ignore this Data Element however as the value for JPEG compressed data is already known). If JPEG Compressed Pixel Data is decompressed and re-encoded in Native (uncompressed) form, then the Data Elements that are related to the Pixel Data encoding are updated accordingly. If color components are converted from YBR_FULL_422 to RGB during decompression and Native re-encoding, the Photometric Interpretation will be changed to RGB in the Data Set with the Native encoding. @@ -4267,8 +4352,8 @@ The RLE Image Compression algorithm described in is the compression used in the TIFF 6.0 specification known as the "PackBits" scheme. - The use of the DICOM Encapsulated Format to support RLE Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the compressed data. - The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from PS.3. C.7.6.3.1.2) are specified in . No other Standard Photometric Interpretation values shall be used. + The use of the DICOM Encapsulated Format to support RLE Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the compressed data. + The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from PS.3. C.7.6.3.1.2) are specified in . No other Standard Photometric Interpretation Values shall be used. @@ -4411,12 +4496,12 @@
JPEG-LS Image Compression - DICOM provides a mechanism for supporting the use of JPEG-LS Image Compression through the Encapsulated Format (see ). defines a number of Transfer Syntaxes that reference the JPEG-LS Standard and provide a number of lossless (bit preserving) and lossy (near-lossless) compression schemes. + DICOM provides a mechanism for supporting the use of JPEG-LS Image Compression through the Encapsulated Format. defines a number of Transfer Syntaxes that reference the JPEG-LS Standard and provide a number of lossless (bit preserving) and lossy (near-lossless) compression schemes. The context where the usage of lossy (near-lossless) compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for JPEG-LS lossy (near-lossless) compression is also beyond the scope of this Standard. - The use of the DICOM Encapsulated Format to support JPEG-LS Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream. The Pixel Data characteristics included in the JPEG-LS Interchange Format shall be used to decode the compressed data stream. - The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from PS.3. C.7.6.3.1.2) are specified in . No other Standard Photometric Interpretation values shall be used. + The use of the DICOM Encapsulated Format to support JPEG-LS Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream. The Pixel Data characteristics included in the JPEG-LS Interchange Format shall be used to decode the compressed data stream. + The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from PS.3. C.7.6.3.1.2) are specified in . No other Standard Photometric Interpretation Values shall be used.
Valid Values of Pixel Data Related Attributes for RLE Compression using Standard Photometric Interpretations
@@ -4592,16 +4677,16 @@ - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the JPEG-LS bit stream as component, line or sample interleaved, hence it shall be set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the JPEG-LS bit stream as component, line or sample interleaved, hence it shall be set to 0.
JPEG 2000 Image Compression - DICOM provides a mechanism for supporting the use of JPEG 2000 Image Compression through the Encapsulated Format (see ). defines a number of Transfer Syntaxes that reference the JPEG 2000 Standard and provide lossless (bit preserving) and lossy compression schemes. + DICOM provides a mechanism for supporting the use of JPEG 2000 Image Compression through the Encapsulated Format. defines a number of Transfer Syntaxes that reference the JPEG 2000 Standard and provide lossless (bit preserving) and lossy compression schemes. The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for JPEG 2000 lossy compression are also beyond the scope of this Standard. - The use of the DICOM Encapsulated Format to support JPEG 2000 Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream. The Pixel Data characteristics included in the JPEG 2000 bit stream shall be used to decode the compressed data stream. - The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from PS.3. C.7.6.3.1.2) are specified in . No other Standard Photometric Interpretation values shall be used. + The use of the DICOM Encapsulated Format to support JPEG 2000 Compressed Pixel Data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream. The Pixel Data characteristics included in the JPEG 2000 bit stream shall be used to decode the compressed data stream. + The requirements when using a Standard Photometric Interpretation (i.e., a Defined Term from PS.3. C.7.6.3.1.2) are specified in . No other Standard Photometric Interpretation Values shall be used.
Valid Values of Pixel Data Related Attributes for JPEG-LS Compression using Standard Photometric Interpretations
@@ -4824,7 +4909,7 @@ These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived.When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. - The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms.The JPEG 2000 bit stream specifies whether or not a reversible or irreversible multi-component (color) transformation [ISO 15444-1 Annex G], if any, has been applied. If no multi-component transformation has been applied, then the components shall correspond to those specified by the DICOM Attribute Photometric Interpretation (0028,0004). If the JPEG 2000 Part 1 reversible multi-component transformation has been applied then the DICOM Attribute Photometric Interpretation (0028,0004) shall be YBR_RCT. If the JPEG 2000 Part 1 irreversible multi-component transformation has been applied then the DICOM Attribute Photometric Interpretation (0028,0004) shall be YBR_ICT. @@ -4832,7 +4917,7 @@ For example, single component may be present, and the Photometric Interpretation (0028,0004) may be MONOCHROME2. - The application of a JPEG 2000 Part 1 reversible multi-component transformation is signaled in the JPEG 2000 bit stream by a value of 1 rather than 0 in the SGcod Multiple component transformation type of the COD marker segment [ISO 15444-1 Table A.17]. No other value of Photometric Interpretation than YBR_RCT or YBR_ICT is permitted when SGcod Multiple component transformation type is 1. + The application of a JPEG 2000 Part 1 reversible multi-component transformation is signaled in the JPEG 2000 bit stream by a value of 1 rather than 0 in the SGcod Multiple component transformation type of the COD marker segment [ISO 15444-1 Table A.17]. No other Value of Photometric Interpretation than YBR_RCT or YBR_ICT is permitted when SGcod Multiple component transformation type is 1. Though it would be unusual, would not take advantage of correlation between the red, green and blue components, and would not achieve effective compression, a Photometric Interpretation of RGB could be specified as long as no multi-component transformation [ISO 15444-1 Annex G] was specified by the JPEG 2000 bit stream. @@ -4840,10 +4925,10 @@ Alternative methods of decorrelation of the color components than those specified in [ISO 15444-1 Annex G] are permitted as defined in PS3.3, such as a Photometric Interpretation of YBR_FULL; this may be useful when converting existing YBR_FULL Pixel Data (e.g., in a different Transfer Syntax) without further loss. In either case (Photometric Interpretation of RGB or YBR_FULL), the value of SGcod Multiple component transformation type would be 0. - may constrain the values of Photometric Interpretation for specific IODs. + may constrain the Values of Photometric Interpretation for specific IODs. - Despite the application of a multi-component color transformation and its reflection in the Photometric Interpretation attribute, the "color space" remains undefined. There is currently no means of conveying "standard color spaces" either by fixed values (such as sRGB) or by ICC profiles. Note in particular that the JP2 file header is not sent in the JPEG 2000 bit stream that is encapsulated in DICOM. + Despite the application of a multi-component color transformation and its reflection in the Photometric Interpretation Attribute, the "color space" remains undefined. There is currently no means of conveying "standard color spaces" either by fixed values (such as sRGB) or by ICC profiles. Note in particular that the JP2 file header is not sent in the JPEG 2000 bit stream that is encapsulated in DICOM. If JPEG 2000 Compressed Pixel Data is decompressed and re-encoded in Native (uncompressed) form, then the Data Elements that are related to the Pixel Data encoding are updated accordingly. If color components are converted from YBR_ICT or YBR_RCT to RGB during decompression and Native re-encoding, the Photometric Interpretation will be changed to RGB in the Data Set with the Native encoding. @@ -4853,20 +4938,20 @@ - The JPEG 2000 bit stream is capable of encoding both signed and unsigned pixel values, hence the value of Pixel Representation (0028,0103) may be either 0 or 1 for monochrome Photometric Interpretations depending on what has been encoded (as specified in the SIZ marker segment in the precision and sign of component parameter). - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the JPEG 2000 standard, hence it shall be set to 0. + The JPEG 2000 bit stream is capable of encoding both signed and unsigned pixel values, hence the Value of Pixel Representation (0028,0103) may be either 0 or 1 for monochrome Photometric Interpretations depending on what has been encoded (as specified in the SIZ marker segment in the precision and sign of component parameter). + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the JPEG 2000 standard, hence it shall be set to 0.
MPEG2 Main Profile / Main Level Video Compression - DICOM provides a mechanism for supporting the use of MPEG2 Main Profile / Main Level Video Compression through the Encapsulated Format (see ). defines a Transfer Syntax that references the MPEG2 Main Profile / Main Level Standard. + DICOM provides a mechanism for supporting the use of MPEG2 Main Profile / Main Level Video Compression through the Encapsulated Format. defines Non-Fragmentable and Fragmentable Encapsulated Transfer Syntaxes that reference the MPEG2 Main Profile / Main Level Standard. MPEG2 compression is inherently lossy. The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for MPEG2 Main Profile / Main Level are also beyond the scope of this Standard. - The use of the DICOM Encapsulated Format to support MPEG2 Main Profile / Main Level compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG2 Main Profile / Main Level bit stream shall be used to decode the compressed data stream. + The use of the DICOM Encapsulated Format to support MPEG2 Main Profile / Main Level compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG2 Main Profile / Main Level bit stream shall be used to decode the compressed data stream. These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived. - When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. The MPEG2 Main Profile / Main Level bit stream specifies whether or not a reversible or irreversible multi-component (color) transformation, if any, has been applied. If no multi-component transformation has been applied, then the components shall correspond to those specified by the DICOM Attribute Photometric Interpretation (0028,0004). MPEG2 Main Profile / Main Level applies an irreversible multi-component transformation, so DICOM Attribute Photometric Interpretation (0028,0004) shall be YBR_PARTIAL_420 in the case of multi-component data, and MONOCHROME2 in the case of single component data (even though the MPEG2 bit stream itself is always encoded as three components, one luminance and two chrominance). @@ -4878,7 +4963,7 @@ - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG2 Main Profile / Main Level standard, hence it shall be set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG2 Main Profile / Main Level standard, hence it shall be set to 0. In summary: @@ -4978,7 +5063,7 @@ - Although different combinations of values for Rows and Columns values are possible while respecting the maximum values listed above, it is recommended that the typical 4:3 ratio of image width to height be maintained in order to avoid image deformation by MPEG2 decoders. A common way to maintain the ratio of width to height is to pad the image with black areas on either side. + Although different combinations of Values for Rows and Columns are possible while respecting the maximum values listed above, it is recommended that the typical 4:3 ratio of image width to height be maintained in order to avoid image deformation by MPEG2 decoders. A common way to maintain the ratio of width to height is to pad the image with black areas on either side. "Half" definition of pictures (240x352 and 288x352 for NTSC and PAL, respectively) are always supported by decoders. @@ -4994,14 +5079,15 @@ - One fragment shall contain the whole MPEG2 stream. + For the Non-Fragmentable Encapsulated Transfer Syntax, one Fragment shall contain the whole MPEG2 stream. + For the Fragmentable Encapsulated Transfer Syntax, the stream may be segmented into multiple Fragments. - If a video stream exceeds the maximum length of one fragment, it may be sent as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. + If a video stream exceeds the maximum length of one fragment (2^32-2 bytes), it may be sent using a Fragmentable Encapsulated Transfer Syntax. Alternatively, it may be sent using a Non-Fragmentable Encapsulated Transfer Syntax as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. - This constraint limits the length of the compressed bit stream to no longer than 232-2 bytes. + Fragmentable Encapsulated Transfer Syntaxes allow for streams of essentially unlimited length; the only limit imposed is the maximum Number of Frames (0028,0008), which is 2^31-1 frames (largest positive Value in an Integer String VR). @@ -5043,15 +5129,15 @@
MPEG2 Main Profile / High Level Video Compression - MPEG2 Main Profile / High Level corresponds to what is commonly known as HDTV ('High Definition Television'). DICOM provides a mechanism for supporting the use of MPEG2 Main Profile / High Level Video Compression through the Encapsulated Format (see ). defines a Transfer Syntax that references the MPEG2 Main Profile / High Level Standard. + MPEG2 Main Profile / High Level corresponds to what is commonly known as HDTV ('High Definition Television'). DICOM provides a mechanism for supporting the use of MPEG2 Main Profile / High Level Video Compression through the Encapsulated Format. defines Non-Fragmentable and Fragmentable Encapsulated Transfer Syntaxes that reference the MPEG2 Main Profile / High Level Standard. MPEG2 compression is inherently lossy. The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for MPEG2 Main Profile / High Level are also beyond the scope of this Standard. - The use of the DICOM Encapsulated Format to support MPEG2 Main Profile / High Level compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG2 Main Profile / High Level bit stream shall be used to decode the compressed data stream. + The use of the DICOM Encapsulated Format to support MPEG2 Main Profile / High Level compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG2 Main Profile / High Level bit stream shall be used to decode the compressed data stream. These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived. - When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. If MPEG2 Compressed Pixel Data is decompressed and re-encoded in Native (uncompressed) form, then the Data Elements that are related to the Pixel Data encoding are updated accordingly. If color components are converted from YBR_PARTIAL_420 to RGB during decompression and Native re-encoding, the Photometric Interpretation will be changed to RGB in the Data Set with the Native encoding. @@ -5060,7 +5146,7 @@ Planar Configuration (0028,0006) shall be 0 - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG2 standard, hence it is set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG2 standard, hence it is set to 0. @@ -5091,7 +5177,7 @@ The value of MPEG2 aspect_ratio_information shall be 0011 in the encapsulated MPEG2 data stream corresponding to a 'Display Aspect Ratio' (DAR) of 16:9. - The DICOM attribute Pixel Aspect Ratio (0028,0034) shall be absent. This corresponds to a 'Sampling Aspect Ratio' (SAR) of 1:1. + The DICOM Attribute Pixel Aspect Ratio (0028,0034) shall be absent. This corresponds to a 'Sampling Aspect Ratio' (SAR) of 1:1. Cine Rate (0018,0040) and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be consistent with the limitations of Main Profile / High Level, as specified in . @@ -5376,14 +5462,15 @@
Valid Values of Pixel Data Related Attributes for JPEG 2000 Transfer Syntaxes using Standard Photometric Interpretations
- One fragment shall contain the whole MPEG2 bit stream. + For the Non-Fragmentable Encapsulated Transfer Syntax, one Fragment shall contain the whole MPEG2 bit stream. + For the Fragmentable Encapsulated Transfer Syntax, the stream may be segmented into multiple Fragments. - If a video stream exceeds the maximum length of one fragment (approximately 4 GB), it may be sent as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. + If a video stream exceeds the maximum length of one fragment (2^32-2 bytes), it may be sent using a Fragmentable Encapsulated Transfer Syntax. Alternatively, it may be sent using a Non-Fragmentable Encapsulated Transfer Syntax as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. - This constraint limits the length of the compressed bit stream to no longer than 232-2 bytes. + Fragmentable Encapsulated Transfer Syntaxes allow for streams of essentially unlimited length; the only limit imposed is the maximum Number of Frames (0028,0008), which is 2^31-1 frames (largest positive Value in an Integer String VR). @@ -5401,15 +5488,15 @@
MPEG-4 AVC/H.264 High Profile / Level 4.1 Video Compression - MPEG-4 AVC/H.264 High Profile / Level 4.1 corresponds to what is commonly known as HDTV ('High Definition Television'). DICOM provides a mechanism for supporting the use of MPEG-4 AVC/H.264 Image Compression through the Encapsulated Format (see ). defines a Transfer Syntax that references the MPEG-4 AVC/H.264 Standard. + MPEG-4 AVC/H.264 High Profile / Level 4.1 corresponds to what is commonly known as HDTV ('High Definition Television'). DICOM provides a mechanism for supporting the use of MPEG-4 AVC/H.264 Image Compression through the Encapsulated Format. defines Non-Fragmentable and Fragmentable Encapsulated Transfer Syntaxes that reference the MPEG-4 AVC/H.264 Standard. MPEG-4 AVC/H.264 compression / High Profile compression is inherently lossy. The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for MPEG-4 AVC/H.264 High Profile / Level 4.1 are also beyond the scope of this Standard. - The use of the DICOM Encapsulated Format to support MPEG-4 AVC/H.264 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG-4 AVC/H.264 bit stream shall be used to decode the compressed data stream. + The use of the DICOM Encapsulated Format to support MPEG-4 AVC/H.264 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG-4 AVC/H.264 bit stream shall be used to decode the compressed data stream. These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived. - When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. If MPEG-4 Compressed Pixel Data is decompressed and re-encoded in Native (uncompressed) form, then the Data Elements that are related to the Pixel Data encoding are updated accordingly. If color components are converted from YBR_PARTIAL_420 to RGB during decompression and Native re-encoding, the Photometric Interpretation will be changed to RGB in the Data Set with the Native encoding. @@ -5443,13 +5530,13 @@ Pixel Aspect Ratio (0028,0034) shall be absent. This corresponds to a 'Sampling Aspect Ratio' (SAR) of 1:1. - The possible values for Rows (0028,0010), Columns (0028,0011), Cine Rate (0018,0040), and Frame Time (0018,1063) or Frame Time Vector (0018,1065) depend on the used Transfer Syntax. + The possible Values for Rows (0028,0010), Columns (0028,0011), Cine Rate (0018,0040), and Frame Time (0018,1063) or Frame Time Vector (0018,1065) depend on the used Transfer Syntax. - For MPEG-4 AVC/H.264 High Profile / Level 4.1 Transfer Syntax, the values for these data elements shall be compliant with the High Profile / Level 4.1 of the MPEG-4 AVC/H.264 standard () and restricted to a square pixel aspect ratio. + For MPEG-4 AVC/H.264 High Profile / Level 4.1 Transfer Syntax, the Values for these Data Elements shall be compliant with the High Profile / Level 4.1 of the MPEG-4 AVC/H.264 standard () and restricted to a square pixel aspect ratio. - For MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 Transfer Syntax, the values for these data elements shall be as specified in . + For MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 Transfer Syntax, the Values for these Data Elements shall be as specified in . @@ -5627,7 +5714,7 @@ - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG-4 AVC/H.264 standard, hence it is set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG-4 AVC/H.264 standard, hence it is set to 0. The limitation on rows and columns are to maximize interoperability between software environments and commonly available hardware MPEG-4 AVC/H.264 encoder/decoder implementations. Source pictures that have a lower value should be re-formatted by scaling and/or pixel padding prior to MPEG-4 AVC/H.264 encoding. @@ -5737,24 +5824,32 @@
- One fragment shall contain the whole MPEG-4 AVC/H.264 bit stream. + For the Non-Fragmentable Encapsulated Transfer Syntax, one Fragment shall contain the whole MPEG-4 AVC/H.264 bit stream. + For the Fragmentable Encapsulated Transfer Syntax, the stream may be segmented into multiple Fragments. - If a video stream exceeds the maximum length of one fragment (approximately 4 GB), it may be sent as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. + + + If a video stream exceeds the maximum length of one fragment (2^32-2 bytes), it may be sent using a Fragmentable Encapsulated Transfer Syntax. Alternatively, it may be sent using a Non-Fragmentable Encapsulated Transfer Syntax as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. + + + Fragmentable Encapsulated Transfer Syntaxes allow for streams of essentially unlimited length; the only limit imposed is the maximum Number of Frames (0028,0008), which is 2^31-1 frames (largest positive Value in an Integer String VR). + + The container format for the video bit stream shall be MPEG-2 Transport Stream, a.k.a. MPEG-TS (see ) or MPEG-4, a.k.a. MP4 container (see and ). The PTS/DTS of the transport stream shall be used in the MPEG coding. Any audio components included in the data container shall follow the constraints detailed in .
MPEG-4 AVC/H.264 High Profile / Level 4.2 Video Compression - DICOM provides a mechanism for supporting the use of MPEG-4 AVC/H.264 Image Compression through the Encapsulated Format (see ). defines Transfer Syntaxes that reference the MPEG-4 AVC/H.264 Standard. + DICOM provides a mechanism for supporting the use of MPEG-4 AVC/H.264 Image Compression through the Encapsulated Format. defines Transfer Syntaxes that reference the MPEG-4 AVC/H.264 Standard. MPEG-4 AVC/H.264 compression / High Profile compression is inherently lossy. The context where the usage of lossy compression of medical images is clinically acceptable is beyond the scope of the DICOM Standard. The policies associated with the selection of appropriate compression parameters (e.g., compression ratio) for MPEG-4 AVC/H.264 High Profile / Level 4.2 are also beyond the scope of this Standard. - The use of the DICOM Encapsulated Format to support MPEG-4 AVC/H.264 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG-4 AVC/H.264 bit stream shall be used to decode the compressed data stream. + The use of the DICOM Encapsulated Format to support MPEG-4 AVC/H.264 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the MPEG-4 AVC/H.264 bit stream shall be used to decode the compressed data stream. These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived. - When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. If MPEG-4 Compressed Pixel Data is decompressed and re-encoded in Native (uncompressed) form, then the Data Elements that are related to the Pixel Data encoding are updated accordingly. If color components are converted from YBR_PARTIAL_420 to RGB during decompression and Native re-encoding, the Photometric Interpretation will be changed to RGB in the Data Set with the Native encoding. @@ -5788,13 +5883,13 @@ Pixel Aspect Ratio (0028,0034) shall be absent. This corresponds to a 'Sampling Aspect Ratio' (SAR) of 1:1. - The values for Rows (0028,0010), Columns (0028,0011), Cine Rate (0018,0040), and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be compliant with the High Profile / Level 4.2 of the MPEG-4 AVC/H.264 standard () and restricted to a square pixel aspect ratio. + The Values for Rows (0028,0010), Columns (0028,0011), Cine Rate (0018,0040), and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be compliant with the High Profile / Level 4.2 of the MPEG-4 AVC/H.264 standard () and restricted to a square pixel aspect ratio. - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG-4 AVC/H.264 standard, hence it is set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the MPEG-4 AVC/H.264 standard, hence it is set to 0. The frame rate of the acquiring camera for '30 Hz HD' MPEG-4 AVC/H.264 may be either 30 or 30/1.001 (approximately 29.97) frames/sec. Similarly, the frame rate in the case of 60 Hz may be either 60 or 60/1.001 (approximately 59.94) frames/sec. This may lead to small inconsistencies between the video timebase and real time. The relationship between frame rate and frame time is shown in . @@ -5916,16 +6011,24 @@
- One fragment shall contain the whole MPEG-4 AVC/H.264 bit stream. + For the Non-Fragmentable Encapsulated Transfer Syntax, one Fragment shall contain the whole MPEG-4 AVC/H.264 bit stream. + For the Fragmentable Encapsulated Transfer Syntax, the stream may be segmented into multiple Fragments. - If a video stream exceeds the maximum length of one fragment (approximately 4 GB), it may be sent as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. + + + If a video stream exceeds the maximum length of one fragment (2^32-2 bytes), it may be sent using a Fragmentable Encapsulated Transfer Syntax. Alternatively, it may be sent using a Non-Fragmentable Encapsulated Transfer Syntax as multiple SOP Instances, but each SOP Instance will contain an independent and playable bit stream, and not depend on the encoded bit stream in other (previous) instances. The manner in which such separate instances are related is not specified in the Standard, but mechanisms such as grouping into the same Series, and references to earlier instances using Referenced Image Sequence may be used. + + + Fragmentable Encapsulated Transfer Syntaxes allow for streams of essentially unlimited length; the only limit imposed is the maximum Number of Frames (0028,0008), which is 2^31-1 frames (largest positive Value in an Integer String VR). + + The container format for the video bit stream shall be MPEG-2 Transport Stream, a.k.a. MPEG-TS (see ) or MPEG-4, a.k.a. MP4 container (see and ). The PTS/DTS of the transport stream shall be used in the MPEG coding. Any audio components included in the data container shall follow the constraints detailed in .
MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 Video Compression - DICOM provides a mechanism for supporting the use of MPEG-4 AVC/H.264 Image Compression through the Encapsulated Format (see ). defines a Transfer Syntax that references the MPEG-4 AVC/H.264 Standard. + DICOM provides a mechanism for supporting the use of MPEG-4 AVC/H.264 Image Compression through the Encapsulated Format. defines Non-Fragmentable and Fragmentable Encapsulated Transfer Syntaxes that reference the MPEG-4 AVC/H.264 Standard. MPEG-4 AVC/H.264 Stereo High Profile can achieve better compression by additionally making use of prediction between the base and dependent stereoscopic views. The base view frames make use of intra and inter prediction as in MPEG-4 AVC/H.264 High Profile. This makes it possible for decoders which do not know how to decode the stereoscopic data to decode only the base view. The dependent view is encoded to make use of redundancy due to prediction based upon similarities between the base and the dependent views. MPEG-4 AVC/H.264 Stereo High Profile makes use of the Level table A-1 of the MPEG-4 specification to set through-put limits. The properties required by the MPEG-4 AVC/H.264 Stereo High Profile Compression are identical to the properties defined in , except that Stereo Pairs Present (0022,0028) shall always be YES. The container format for the video bit stream shall be MPEG-2 Transport Stream, a.k.a. MPEG-TS (see ) or MPEG-4, a.k.a. MP4 container (see and ). The PTS/DTS of the transport stream shall be used in the MPEG coding. @@ -5933,15 +6036,15 @@
HEVC/H.265 Main Profile / Level 5.1 Video Compression - HEVC/H.265 Main Profile / Level 5.1 Main tier is designed for the compression of 4:2:0 video formats up to 4k at 60 frames per second with a bit depth of 8 bits. DICOM provides a mechanism for supporting the use of HEVC/H.265 Image Compression through the Encapsulated Format (see ). defines a Transfer Syntax that references the HEVC/H.265 Standard. - The use of the DICOM Encapsulated Format to support HEVC/H.265 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the HEVC/H.265 bit stream shall be used to decode the compressed data stream. + HEVC/H.265 Main Profile / Level 5.1 Main tier is designed for the compression of 4:2:0 video formats up to 4k at 60 frames per second with a bit depth of 8 bits. DICOM provides a mechanism for supporting the use of HEVC/H.265 Image Compression through the Encapsulated Format. defines a Fragmentable Encapsulated Transfer Syntax that references the HEVC/H.265 Standard. + The use of the DICOM Encapsulated Format to support HEVC/H.265 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the HEVC/H.265 bit stream shall be used to decode the compressed data stream. These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived. - When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. @@ -5975,13 +6078,13 @@ Pixel Aspect Ratio (0028,0034) shall be absent. This corresponds to a 'Sampling Aspect Ratio' (SAR) of 1:1. - The values for Rows (0028,0010), Columns (0028,0011), Cine Rate (0018,0040) and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be compliant with the Main Profile / Level 5.1 of the HEVC/H.265 standard and restricted to a square pixel aspect ratio. + The Values for Rows (0028,0010), Columns (0028,0011), Cine Rate (0018,0040) and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be compliant with the Main Profile / Level 5.1 of the HEVC/H.265 standard and restricted to a square pixel aspect ratio. - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the HEVC/H.265 standard, hence it is set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the HEVC/H.265 standard, hence it is set to 0. The limitation on rows and columns are to maximize interoperability between software environments and commonly available hardware HEVC/H.265 encoder/decoder implementations. Source pictures that have a lower value should be re-formatted by scaling and/or pixel padding prior to HEVC/H.265 encoding. @@ -5994,24 +6097,24 @@ - The encapsulated pixel data stream may be segmented into more than one fragment. + The encapsulated pixel data stream may be segmented into multiple fragments. - The recipient is expected to concatenate the fragments while decoding them. This allows for essentially unlimited length streams; the only limit imposed is the maximum size of frames (0028,0008) which is 2^31-1. + The recipient is expected to concatenate the fragments while decoding them. This allows for essentially unlimited length streams; the only limit imposed is the maximum Value for Number of Frames (0028,0008) which is 2^31-1 frames (largest positive Value in an Integer String VR). The container format for the video bit stream shall be MPEG-2 Transport Stream, a.k.a. MPEG-TS (see ) or MPEG-4, a.k.a. MP4 container (see and ). The PTS/DTS of the transport stream shall be used in the MPEG coding. Any audio components included in the data container shall follow the constraints detailed in .
HEVC/H.265 Main 10 Profile / Level 5.1 Video Compression - HEVC/H.265 Main 10 Profile / Level 5.1 Main tier is designed for the compression of 4:2:0 video formats up to 4k at 60 frames per second with a bit depth of 10 bits. DICOM provides a mechanism for supporting the use of HEVC/H.265 Image Compression through the Encapsulated Format (see ). defines a Transfer Syntax that references the HEVC/H.265 Standard. - The use of the DICOM Encapsulated Format to support HEVC/H.265 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the HEVC/H.265 bit stream shall be used to decode the compressed data stream. + HEVC/H.265 Main 10 Profile / Level 5.1 Main tier is designed for the compression of 4:2:0 video formats up to 4k at 60 frames per second with a bit depth of 10 bits. DICOM provides a mechanism for supporting the use of HEVC/H.265 Image Compression through the Encapsulated Format. defines a Fragmentable Encapsulated Transfer Syntax that references the HEVC/H.265 Standard. + The use of the DICOM Encapsulated Format to support HEVC/H.265 compressed pixel data requires that the Data Elements that are related to the Pixel Data encoding (e.g., Photometric Interpretation, Samples per Pixel, Planar Configuration, Bits Allocated, Bits Stored, High Bit, Pixel Representation, Rows, Columns, etc.) shall contain Values that are consistent with the characteristics of the compressed data stream, with some specific exceptions noted here. The Pixel Data characteristics included in the HEVC/H.265 bit stream shall be used to decode the compressed data stream. These requirements are specified in terms of consistency with what is encapsulated, rather than in terms of the uncompressed pixel data from which the compressed data stream may have been derived. - When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM data elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. + When decompressing, should the characteristics explicitly specified in the compressed data stream be inconsistent with those specified in the DICOM Data Elements, those explicitly specified in the compressed data stream should be used to control the decompression. The DICOM Data Elements, if inconsistent, can be regarded as suggestions as to the form in which an uncompressed Data Set might be encoded, subject to the general and IOD-specific rules for uncompressed Photometric Interpretation and Planar Configuration, which may require that decompressed data be converted to one of the permitted forms. @@ -6045,13 +6148,13 @@ Pixel Aspect Ratio (0028,0034) shall be absent. This corresponds to a 'Sampling Aspect Ratio' (SAR) of 1:1. - The values for Rows (0028,0010) , Columns (0028,0011), Cine Rate (0018,0040) , and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be compliant with the Main 10 Profile / Level 5.1 of the HEVC/H.265 standard and restricted to a square pixel aspect ratio. + The Values for Rows (0028,0010) , Columns (0028,0011), Cine Rate (0018,0040) , and Frame Time (0018,1063) or Frame Time Vector (0018,1065) shall be compliant with the Main 10 Profile / Level 5.1 of the HEVC/H.265 standard and restricted to a square pixel aspect ratio. - The value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the HEVC/H.265 standard, hence it is set to 0. + The Value of Planar Configuration (0028,0006) is irrelevant since the manner of encoding components is specified in the HEVC/H.265 standard, hence it is set to 0. The limitation on rows and columns are to maximize interoperability between software environments and commonly available hardware HEVC/H.265 encoder/decoder implementations. Source pictures that have a lower value should be re-formatted by scaling and/or pixel padding prior to HEVC/H.265 encoding. @@ -6064,9 +6167,9 @@ - The encapsulated pixel data stream may be segmented into more than one fragment. + The encapsulated pixel data stream may be segmented into multiple fragments. - The recipient is expected to concatenate the fragments while decoding them. This allows for essentially unlimited length streams; the only limit imposed is the maximum size of frames (0028,0008) which is 2^31-1. + The recipient is expected to concatenate the fragments while decoding them. This allows for essentially unlimited length streams; the only limit imposed is the maximum Value for Number of Frames (0028,0008) which is 2^31-1 frames (largest positive Value in an Integer String VR). The container format for the video bit stream shall be MPEG-2 Transport Stream, a.k.a. MPEG-TS (see ) or MPEG-4, a.k.a. MP4 container (see and ). The PTS/DTS of the transport stream shall be used in the MPEG coding. Any audio components included in the data container shall follow the constraints detailed in . @@ -6298,7 +6401,7 @@
Constraints For SMPTE ST 2110-20 Uncompressed Active Video For DICOM-RTV This section describes the constraints applying to pixel data carried in the DICOM-RTV Flow (separated from DICOM-RTV Metadata Flow) and fully described in . - The following table describes constraints on the Video Flow in terms of the valid values for the corresponding DICOM Attributes in the DICOM-RTV Metadata Flow: + The following table describes constraints on the Video Flow in terms of the valid Values for the corresponding DICOM Attributes in the DICOM-RTV Metadata Flow: Samples per pixel @@ -6532,8 +6635,8 @@ Per , an IOD supporting multiple sets of Waveform Data will encapsulate Waveform Data (5400,1010) within a Sequence. - Encoded Waveform Data of various bit depths is accommodated through the Waveform Bits Allocated (5400,1004) Data Element. This element defines the size of each waveform data sample within the Waveform Data (5400,1010). Allowed values are 8, 16, 32 and 64 bits. - The Value Representation of the Waveform Data (5400,1010) shall be OW; OB shall be used in cases where Waveform Bits Allocated has a value of 8, but only with Transfer Syntaxes where the Value Representation is explicitly conveyed. + Encoded Waveform Data of various bit depths is accommodated through the Waveform Bits Allocated (5400,1004) Data Element. This Data Element defines the size of each waveform data sample within the Waveform Data (5400,1010). Allowed Values are 8, 16, 32 and 64 bits. + The Value Representation of the Waveform Data (5400,1010) shall be OW; OB shall be used in cases where Waveform Bits Allocated has a Value of 8, but only with Transfer Syntaxes where the Value Representation is explicitly conveyed. @@ -6544,7 +6647,7 @@ - The following data elements related to Waveform Data shall be encoded with the same VR as Waveform Data: Channel Minimum Value (5400,0110), Channel Maximum Value (5400,0112) and Waveform Padding Value (5400,100A). + The following Data Elements related to Waveform Data shall be encoded with the same VR as Waveform Data: Channel Minimum Value (5400,0110), Channel Maximum Value (5400,0112) and Waveform Padding Value (5400,100A).
Pixel Data Provider Service @@ -6565,12 +6668,12 @@ URL Generated by the application = http://server.xxx/jpipserver.cgi?target=imgxyz.jp2&fsiz=200,200 The JPIP client shall only request a JPEG 2000 bit stream. The JPIP server shall return a Content-type of image/jp2, image/jpp-stream or image/jpt-stream, all of which shall be supported by the JPIP client. - The Number of Frames (0028,0008) attribute, if present in the Data Set, identifies the number of frames available for this image. Each frame is accessible as a separate JPIP code stream. Code streams referenced in the URL Target shall be sequentially numbered starting with stream 1. + The Number of Frames (0028,0008) Attribute, if present in the Data Set, identifies the number of frames available for this image. Each frame is accessible as a separate JPIP code stream. Code streams referenced in the URL Target shall be sequentially numbered starting with stream 1. For example, a JPIP request for a 200 by 200 pixel rendition of frame 17 of a multi-frame image can be constructed from Pixel Data Provider URL as follows: Pixel Data Provider URL (0028,7FE0) = http://server.xxx/multiframeimage.jp2 URL Generated by the application = http://server.xxx/multiframeimage.jp2?fsiz=200,200&stream=17 - A valid stream query parameter value is always less than or equal to the value in the Number of Frames (0028,0008). + A valid stream query parameter Value is always less than or equal to the Value in the Number of Frames (0028,0008). The syntax of the Pixel Data Provider URL (0028,7FE0) is defined in Annex C (Client Request). That standard respects the URI recommendations . The transport protocol shall be HTTP or HTTPS. @@ -6608,7 +6711,7 @@ Unique Identifiers (UIDs) Unique Identifiers (UIDs) provide the capability to uniquely identify a wide variety of items. They guarantee uniqueness across multiple countries, sites, vendors and equipment. Different classes of objects, instance of objects and information entities can be distinguished from one another across the DICOM universe of discourse irrespective of any semantic context. - For example the same UID value cannot be used to identify both a study instance (Study Instance UID) and a series instance (Series Instance UID) within that study or a different study. Implementers also need to be cautioned against building new UID values by derivation (for example by adding a suffix) from a UID assigned by another implementation. + For example the same UID cannot be used to identify both a study instance (Study Instance UID) and a series instance (Series Instance UID) within that study or a different study. Implementers also need to be cautioned against building new UIDs by derivation (for example by adding a suffix) from a UID assigned by another implementation. The UID identification scheme is based on the OSI Object Identification (numeric form) as defined by the standard. All Unique Identifiers, used within the context of the DICOM Standard, are registered values as defined by to ensure global uniqueness. The uses of such UIDs are defined in the various Parts of the DICOM Standard. Each UID is composed of two parts, an <org root> and a <suffix>: @@ -6688,7 +6791,7 @@ If an Application Entity receives an A-ASSOCIATE indication corresponding to a request that follows the requirements specified in (a), every Presentation Context related to a given Abstract Syntax cannot be rejected in an A-ASSOCIATE response for the reason that none of the Transfer Syntaxes are supported. - When Abstract Syntax (AS1) is offered in three Presentation Contexts with Transfer Syntaxes (TS1), (TS2) and (TSD), the DICOM Default Little Endian Transfer Syntax (TSD) can be rejected if at least one of the other Presentation Contexts for Abstract Syntax (AS1) is accepted. + When Abstract Syntax (AS1) is offered in three Presentation Contexts with Transfer Syntaxes (TS1), (TS2) and (TSD), the DICOM Default Little Endian Transfer Syntax (TSD) can be rejected if at least one of the other Presentation Contexts for Abstract Syntax (AS1) is accepted. @@ -6715,7 +6818,7 @@ If an Application Entity that supports one or more lossless JPEG Transfer Syntax receives an A-ASSOCIATE indication corresponding to a request that follows the requirements specified in (a), every Presentation Context related to a given Abstract Syntax cannot be rejected in an A-ASSOCIATE response for the reason that the DICOM Default Lossless JPEG Compression Transfer Syntax is not supported. - When Abstract Syntax (AS1) is offered in four Presentation Contexts with Transfer Syntaxes JPEG lossless (JL1) and (JL2) as well as (JLD) and (TSD), both the DICOM Default Lossless JPEG Compression Transfer Syntax (JLD) and the DICOM Default Little Endian Transfer Syntax (TSD) can be rejected if at least one of the other Presentation Contexts for Abstract Syntax (AS1) is accepted. + When Abstract Syntax (AS1) is offered in four Presentation Contexts with Transfer Syntaxes JPEG lossless (JL1) and (JL2) as well as (JLD) and (TSD), both the DICOM Default Lossless JPEG Compression Transfer Syntax (JLD) and the DICOM Default Little Endian Transfer Syntax (TSD) can be rejected if at least one of the other Presentation Contexts for Abstract Syntax (AS1) is accepted. @@ -6732,7 +6835,7 @@ Offering Abstract Syntax (AS1) in two Presentation Contexts with Transfer Syntaxes JPEG lossy (JL1) and (JL2) is not valid, but offering AS1-JL1, AS1-JL2 and AS1-JLD is valid because the DICOM Default Lossy JPEG Transfer Syntax (JLD) is present in at least one of the Presentation Contexts that are based on Abstract Syntax (AS1). - The DICOM Default Little Endian Transfer Syntax (uncompressed) may be offered if the sender has access to the original pixel data in an uncompressed or lossless compressed form. + The DICOM Default Little Endian Transfer Syntax (uncompressed) may be offered if the sender has access to the original pixel data in an uncompressed or lossless compressed form. @@ -6747,7 +6850,7 @@ The 12 bit Default Transfer Syntax 1.2.840.10008.1.2.4.51 can also be used to encode 8 bit images, but the bit stream required is not identical to that used in the 8 bit Default Transfer Syntax 1.2.840.10008.1.2.4.50 (see ). - When Abstract Syntax (AS1) is offered in three Presentation Contexts with Transfer Syntaxes JPEG lossy (JL1) and (JL2) as well as (JLD), the DICOM Default JPEG Lossy Compression Transfer Syntax (JLD) can be rejected if at least one of the other Presentation Contexts for Abstract Syntax (AS1) is accepted. + When Abstract Syntax (AS1) is offered in three Presentation Contexts with Transfer Syntaxes JPEG lossy (JL1) and (JL2) as well as (JLD), the DICOM Default JPEG Lossy Compression Transfer Syntax (JLD) can be rejected if at least one of the other Presentation Contexts for Abstract Syntax (AS1) is accepted. @@ -6788,7 +6891,7 @@
Transfer Syntax for MPEG2 Main Profile / Main Level Video Compression - One Transfer Syntax is specified for MPEG2 Main Profile / Main Level Video Compression. + Two Transfer Syntaxes are specified for MPEG2 Main Profile / Main Level Video Compression.
Transfer Syntax for JPIP Referenced Pixel Data @@ -6798,22 +6901,22 @@
Transfer Syntax for MPEG2 Main Profile / High Level Video Compression - One Transfer Syntax is specified for MPEG2 Main Profile / High Level Video Compression. + Two Transfer Syntaxes are specified for MPEG2 Main Profile / High Level Video Compression.
Transfer Syntax for MPEG-4 AVC/H.264 High Profile / Level 4.1 Video Compression - One Transfer Syntax is specified for MPEG-4 AVC/H.264 High Profile / Level 4.1 Video Compression and one Transfer Syntax is specified for MPEG-4 AVC/H.264 BD-compliant High Profile / Level 4.1. Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.1 corresponds to the ITU-T H.264 standard's profile and level specifications. Transfer Syntax MPEG-4 AVC/H.264 BD-compliant High Profile / Level 4.1 corresponds to a restricted set of spatial and temporal resolutions described Table 8-4. This Transfer Syntax limits the ITU-T H.264 High Profile / Level 4.1 to HD video formats that are supported by Blu-ray™ (BDRWP 2.B). + Two Transfer Syntaxes are specified for MPEG-4 AVC/H.264 High Profile / Level 4.1 Video Compression and two Transfer Syntaxes are specified for MPEG-4 AVC/H.264 BD-compliant High Profile / Level 4.1. Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.1 corresponds to the ITU-T H.264 standard's profile and level specifications. Transfer Syntax MPEG-4 AVC/H.264 BD-compliant High Profile / Level 4.1 corresponds to a restricted set of spatial and temporal resolutions described Table 8-4. This Transfer Syntax limits the ITU-T H.264 High Profile / Level 4.1 to HD video formats that are supported by Blu-ray™ (BDRWP 2.B).
Transfer Syntaxes for MPEG-4 AVC/H.264 High Profile / Level 4.2 Video Compression - One Transfer Syntax is specified for MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video Compression and one Transfer Syntax is specified for MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video Compression. + Two Transfer Syntaxes are specified for MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video Compression and two Transfer Syntaxes are specified for MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video Compression. Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video Compression corresponds to the ITU-T H.264 standard's profile and level specifications except that the use of frame packing formats for 3D video is not allowed as defined in . Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video Compression corresponds to the ITU-T H.264 standard's profile and level specifications. It should be used for transmitting stereoscopic 3D content with frame packing formats as defined in .
Transfer Syntax for MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 Video Compression - One Transfer Syntax is specified for MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 Video Compression. + Two Transfer Syntaxes are specified for MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 Video Compression. Transfer Syntax MPEG-4 AVC/H.264 Stereo High Profile corresponds to the ITU-T H.264 standard's profile and level specifications.
@@ -6884,13 +6987,13 @@ Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202), Blue Color Palette Lookup Table Data (0028,1203) and Alpha Palette Color Lookup Table Data (0028,1204) have the Value Representation OW and shall be encoded in Little Endian. - Previous versions of the Standard either did not specify the encoding of Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202) and Blue Color Palette Lookup Table Data (0028,1203) in this Part, but specified a VR of US or SS in PS3.6-1993, or specified OW in this Part but a VR of US, SS or OW in PS3.6-1996. The actual encoding of the values and their byte order would be identical in each case. + Previous versions of the Standard either did not specify the encoding of Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202) and Blue Color Palette Lookup Table Data (0028,1203) in this Part, but specified a VR of US or SS in PS3.6-1993, or specified OW in this Part but a VR of US, SS or OW in PS3.6-1996. The actual encoding of the Values and their byte order would be identical in each case. - Red Palette Color Lookup Table Descriptor (0028,1101), Green Palette Color Lookup Table Descriptor (0028,1102) and Blue Palette Color Lookup Table Descriptor (0028,1103) have the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third values are always interpreted as unsigned, regardless of the Value Representation. + Red Palette Color Lookup Table Descriptor (0028,1101), Green Palette Color Lookup Table Descriptor (0028,1102) and Blue Palette Color Lookup Table Descriptor (0028,1103) have the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third Values are always interpreted as unsigned, regardless of the Value Representation. Data Elements (0028,1221),(0028,1222),(0028,1223) Segmented Red, Green, Blue Palette Color Lookup Table Data have the Value Representation OW and shall be encoded in Little Endian. @@ -6898,13 +7001,13 @@ LUT Data (0028,3006) has the Value Representation US or OW and shall be encoded in Little Endian. - Previous versions of the Standard did not specify the encoding of these Data Elements in this Part, but specified a VR of US or SS in PS3.6-1998. A VR of OW has been added to support explicit VR Transfer Syntaxes. Moreover this element is always unsigned, therefore the VR of SS has been removed. The actual encoding of the values and their byte order would be identical in each case. + Previous versions of the Standard did not specify the encoding of these Data Elements in this Part, but specified a VR of US or SS in PS3.6-1998. A VR of OW has been added to support Explicit VR Transfer Syntaxes. Moreover this Data Element is always unsigned, therefore the VR of SS has been removed. The actual encoding of the Values and their byte order would be identical in each case. - LUT Descriptor (0028,3002) has the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third values are always interpreted as unsigned, regardless of the Value Representation. + LUT Descriptor (0028,3002) has the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third Values are always interpreted as unsigned, regardless of the Value Representation. Blending Lookup Table Data (0028,1408) has the Value Representation OW and shall be encoded in Little Endian. @@ -6924,7 +7027,7 @@ Vertex Point Index List (0066,0025), Edge Point Index List (0066,0024), Triangle Point Index List (0066,0023) and Primitive Point Index List (0066,0029) were previously defined with a Value Representation of OW and always interpreted as unsigned, but have been retired. - These have been replaced by corresponding OL data elements, which allow values larger + These have been replaced by corresponding OL Data Elements, which allow Values larger than 65535 to index the full range of points that can be encoded in Point Coordinates Data (0066,0016). See PS3.5-2015c. @@ -6955,10 +7058,10 @@ Pixel Data (7FE0,0010) - where Bits Allocated (0028,0100) has a value greater than 8 shall have Value Representation OW and shall be encoded in Little Endian; + where Bits Allocated (0028,0100) has a Value greater than 8 shall have Value Representation OW and shall be encoded in Little Endian; - where Bits Allocated (0028,0100) has a value less than or equal to 8 shall have the Value Representation OB or OW and shall be encoded in Little Endian. + where Bits Allocated (0028,0100) has a Value less than or equal to 8 shall have the Value Representation OB or OW and shall be encoded in Little Endian. @@ -6978,7 +7081,7 @@ shall have the Value Representation OB or OW and shall be encoded in Little Endian. - Previous versions of the Standard specified that the choice of OB or OW VR was based on whether or not Overlay Bits Allocated (60xx,0100) was greater than, or less than or equal to, 8. However, since only one bit plane can be encoded in each Overlay Data (60xx,3000) Element, no value of Overlay Bits Allocated other than 1 makes sense. Such a restriction is now present in . + Previous versions of the Standard specified that the choice of OB or OW VR was based on whether or not Overlay Bits Allocated (60xx,0100) was greater than, or less than or equal to, 8. However, since only one bit plane can be encoded in each Overlay Data (60xx,3000) Element, no Value of Overlay Bits Allocated other than 1 makes sense. Such a restriction is now present in . @@ -6989,11 +7092,11 @@ Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202), Blue Color Palette Lookup Table Data (0028,1203) and Alpha Palette Color Lookup Table Data (0028,1204) have the Value Representation OW and shall be encoded in Little Endian. - Previous versions of the Standard either did not specify the encoding of Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202) and Blue Color Palette Lookup Table Data (0028,1203) in this Part, but specified a VR of US or SS in PS3.6-1993, or specified OW in this Part but a VR of US, SS or OW in PS3.6-1996. The actual encoding of the values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. However, an explicit VR of US or SS cannot be used to encode a table of 216 elements, since the Value Length is restricted to 16 bits. + Previous versions of the Standard either did not specify the encoding of Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202) and Blue Color Palette Lookup Table Data (0028,1203) in this Part, but specified a VR of US or SS in PS3.6-1993, or specified OW in this Part but a VR of US, SS or OW in PS3.6-1996. The actual encoding of the Values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. However, an Explicit VR of US or SS cannot be used to encode a table of 216 entries, since the Value Length is restricted to 16 bits. - Red Palette Color Lookup Table Descriptor (0028,1101), Green Palette Color Lookup Table Descriptor (0028,1102) and Blue Palette Color Lookup Table Descriptor (0028,1103) have the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third values are always interpreted as unsigned, regardless of the Value Representation. + Red Palette Color Lookup Table Descriptor (0028,1101), Green Palette Color Lookup Table Descriptor (0028,1102) and Blue Palette Color Lookup Table Descriptor (0028,1103) have the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third Values are always interpreted as unsigned, regardless of the Value Representation. Segmented Red Palette Color Lookup Table Data (0028,1221), Segmented Green Palette Color Lookup Table Data (0028,1222) and Segmented Blue Palette Color Lookup Table Data (0028,1223) have the Value Representation OW and shall be encoded in Little Endian. @@ -7001,11 +7104,11 @@ LUT Data (0028,3006) has the Value Representation US or OW and shall be encoded in Little Endian. - Previous versions of the Standard did not specify the encoding of these Data Elements in this Part, but specified a VR of US or SS in PS3.6-1998. However, an explicit VR of US or SS cannot be used to encode a table of 216 elements, since the Value Length is restricted to 16 bits. Hence a VR of OW has been added. Moreover this element is always unsigned, therefore the VR of SS has been removed. The actual encoding of the values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. + Previous versions of the Standard did not specify the encoding of these Data Elements in this Part, but specified a VR of US or SS in PS3.6-1998. However, an Explicit VR of US or SS cannot be used to encode a table of 216 entries, since the Value Length is restricted to 16 bits. Hence a VR of OW has been added. Moreover this Data Element is always unsigned, therefore the VR of SS has been removed. The actual encoding of the Values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. - LUT Descriptor (0028,3002) has the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third values are always interpreted as unsigned, regardless of the Value Representation. + LUT Descriptor (0028,3002) has the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third Values are always interpreted as unsigned, regardless of the Value Representation. Blending Lookup Table Data (0028,1408) has the Value Representation OW and shall be encoded in Little Endian. @@ -7030,7 +7133,7 @@ Vertex Point Index List (0066,0025), Edge Point Index List (0066,0024), Triangle Point Index List (0066,0023) and Primitive Point Index List (0066,0029) were previously defined with a Value Representation of OW and always interpreted as unsigned, but have been retired. - These have been replaced by corresponding OL data elements, which allow values larger + These have been replaced by corresponding OL Data Elements, which allow Values larger than 65535 to index the full range of points that can be encoded in Point Coordinates Data (0066,0016). See PS3.5-2015c. @@ -7067,15 +7170,15 @@ Pixel Data (7FE0,0010) may be encapsulated or native. It shall be encapsulated if present in the top-level Data Set (i.e., not nested within a Sequence Data Element). - The distinction between fixed value length (native) and undefined value length (encapsulated) is present so that the top level Data Set Pixel Data can be compressed (and hence encapsulated), but the Pixel Data within an Icon Image Sequence may or may not be compressed. + The distinction between defined Value Length (native) and undefined Value Length (encapsulated) is present so that the top level Data Set Pixel Data can be compressed (and hence encapsulated), but the Pixel Data within an Icon Image Sequence may or may not be compressed. If native, it shall have a defined Value Length, and be encoded as follows: - where Bits Allocated (0028,0100) has a value greater than 8 shall have Value Representation OW and shall be encoded in Little Endian; + where Bits Allocated (0028,0100) has a Value greater than 8 shall have Value Representation OW and shall be encoded in Little Endian; - where Bits Allocated (0028,0100) has a value less than or equal to 8 shall have the Value Representation OB or OW and shall be encoded in Little Endian. + where Bits Allocated (0028,0100) has a Value less than or equal to 8 shall have the Value Representation OB or OW and shall be encoded in Little Endian. @@ -7094,7 +7197,7 @@ The Length of the Data Element (7FE0,0010) shall be set to the Value for Undefined Length (FFFFFFFFH). - Each Data Stream Fragment encoded according to the specific encoding process shall be encapsulated as a DICOM Item with a specific Data Element Tag of Value (FFFE,E000). The Item Tag is followed by a 4 byte Item Length field encoding the explicit number of bytes of the Item. + Each Data Stream Fragment encoded according to the specific encoding process shall be encapsulated as a DICOM Item with a specific Data Element Tag of Value (FFFE,E000). The Item Tag is followed by a 4 byte Value (Item) Length Field encoding the explicit number of bytes of the Item. Whether more than one fragment per frame is permitted or not is defined per Transfer Syntax. @@ -7137,7 +7240,7 @@ - This Sequence of Items is terminated by a Sequence Delimiter Item with the Tag (FFFE,E0DD) and an Item Length Field of Value (00000000H) (i.e., no Value Field shall be present). + This Sequence of Items is terminated by a Sequence Delimiter Item with the Tag (FFFE,E0DD) and an Value (Item) Length Field of Value (00000000H) (i.e., no Value Field shall be present). @@ -7155,11 +7258,11 @@ Red Palette Color Lookup Table Data (0028,1201), Green Palette Color Lookup Table Data (0028,1202), Blue Color Palette Lookup Table Data (0028,1203) and Alpha Palette Color Lookup Table Data (0028,1204) have the Value Representation OW and shall be encoded in Little Endian. - Previous versions of the Standard either did not specify the encoding of Data Elements 0028,1201), (0028,1202), (0028,1203) in this Part, but specified a VR of US or SS in PS3.6-1993, or specified OW in this Part but a VR of US, SS or OW in PS3.6-1996. The actual encoding of the values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. However, an explicit VR of US or SS cannot be used to encode a table of 216 elements, since the Value Length is restricted to 16 bits. + Previous versions of the Standard either did not specify the encoding of Data Elements 0028,1201), (0028,1202), (0028,1203) in this Part, but specified a VR of US or SS in PS3.6-1993, or specified OW in this Part but a VR of US, SS or OW in PS3.6-1996. The actual encoding of the Values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. However, an Explicit VR of US or SS cannot be used to encode a table of 216 entries, since the Value Length is restricted to 16 bits. - Red Palette Color Lookup Table Descriptor (0028,1101), Green Palette Color Lookup Table Descriptor (0028,1102) and Blue Palette Color Lookup Table Descriptor (0028,1103) have the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third values are always interpreted as unsigned, regardless of the Value Representation. + Red Palette Color Lookup Table Descriptor (0028,1101), Green Palette Color Lookup Table Descriptor (0028,1102) and Blue Palette Color Lookup Table Descriptor (0028,1103) have the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third Values are always interpreted as unsigned, regardless of the Value Representation. Segmented Red Palette Color Lookup Table Data (0028,1221), Segmented Green Palette Color Lookup Table Data (0028,1222) and Segmented Blue Palette Color Lookup Table Data (0028,1223) have the Value Representation OW and shall be encoded in Little Endian. @@ -7167,11 +7270,11 @@ LUT Data (0028,3006) has the Value Representation US or OW and shall be encoded in Little Endian. - Previous versions of the Standard did not specify the encoding of these Data Elements in this Part, but specified a VR of US or SS in PS3.6-1998. However, an explicit VR of US or SS cannot be used to encode a table of 216 elements, since the Value Length is restricted to 16 bits. Hence a VR of OW has been added. Moreover this element is always unsigned, therefore the VR of SS has been removed. The actual encoding of the values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. + Previous versions of the Standard did not specify the encoding of these Data Elements in this Part, but specified a VR of US or SS in PS3.6-1998. However, an Explicit VR of US or SS cannot be used to encode a table of 216 entries, since the Value Length is restricted to 16 bits. Hence a VR of OW has been added. Moreover this Data Element is always unsigned, therefore the VR of SS has been removed. The actual encoding of the Values and their byte order would be identical in each case, though the explicitly encoded VR field would be different. - LUT Descriptor (0028,3002) has the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third values are always interpreted as unsigned, regardless of the Value Representation. + LUT Descriptor (0028,3002) has the Value Representation SS or US (depending on rules specified in the IOD in ), and shall be encoded in Little Endian. The first and third Values are always interpreted as unsigned, regardless of the Value Representation. Blending Lookup Table Data (0028,1408) has the Value Representation OW and shall be encoded in Little Endian. @@ -7196,7 +7299,7 @@ Vertex Point Index List (0066,0025), Edge Point Index List (0066,0024), Triangle Point Index List (0066,0023) and Primitive Point Index List (0066,0029) were previously defined with a Value Representation of OW and always interpreted as unsigned, but have been retired. - These have been replaced by corresponding OL data elements, which allow values larger + These have been replaced by corresponding OL Data Elements, which allow Values larger than 65535 to index the full range of points that can be encoded in Point Coordinates Data (0066,0016). See PS3.5-2015c. @@ -7240,7 +7343,7 @@ 0000H Reserved
- FFFF FFFFH undefined length + FFFF FFFFH Undefined Length @@ -7491,7 +7594,7 @@ 0000H Reserved - FFFF FFFFH undefined length + FFFF FFFFH Undefined Length @@ -7718,7 +7821,7 @@
JPEG Image Compression The International Standards Organization ISO/IEC JTC1 has developed an International Standard, ISO 10918-1 (JPEG Part 1) and an International Standard, ISO 10918-2 (JPEG Part 2), known as the JPEG Standard, for digital compression and coding of continuous-tone still images (see for further details). - A DICOM Transfer Syntax for JPEG Image Compression shall be identified by a UID value, appropriate to its JPEG coding process, chosen from . + A DICOM Transfer Syntax for JPEG Image Compression shall be identified by a UID, appropriate to its JPEG coding process, chosen from . @@ -7815,12 +7918,12 @@
RLE Image Compression - defines a RLE Image Compression Transfer Syntax. This transfer Syntax is identified by the UID value "1.2.840.10008.1.2.5". If the object allows multi-frame images in the pixel data field, then each frame shall be encoded separately. Each frame shall be encoded in one and only one Fragment (see ). + defines a RLE Image Compression Transfer Syntax. This transfer Syntax is identified by the UID "1.2.840.10008.1.2.5". If the object allows multi-frame images in the pixel data field, then each frame shall be encoded separately. Each frame shall be encoded in one and only one Fragment (see ).
JPEG-LS Image Compression The International Standards Organization ISO/IEC JTC1 has developed an International Standard, (JPEG-LS Part 1), for digital compression and coding of continuous-tone still images (see for further details). - A DICOM Transfer Syntax for JPEG-LS Image Compression shall be identified by a UID value, appropriate to its JPEG-LS coding process. + A DICOM Transfer Syntax for JPEG-LS Image Compression shall be identified by a UID, appropriate to its JPEG-LS coding process. Two Transfer Syntaxes are specified for JPEG-LS: @@ -7839,7 +7942,7 @@
JPEG 2000 Image Compression The International Standards Organization ISO/IEC JTC1 has developed an International Standard, (JPEG 2000 Part 1), for digital compression and coding of continuous-tone still images (see for further details). - A DICOM Transfer Syntax for JPEG 2000 Image Compression shall be identified by a UID value, appropriate to the choice of JPEG 2000 coding process. + A DICOM Transfer Syntax for JPEG 2000 Image Compression shall be identified by a UID, appropriate to the choice of JPEG 2000 coding process. Two Transfer Syntaxes are specified for JPEG 2000 Part 1: @@ -7875,7 +7978,7 @@ For all images, including all frames of a multi-frame image, the JPEG 2000 bit stream specified in shall be used. The optional JP2 file format header shall NOT be included. - The role of the JP2 file format header is fulfilled by the non-pixel data attributes in the DICOM Data Set. + The role of the JP2 file format header is fulfilled by the non-pixel data Attributes in the DICOM Data Set. The International Standards Organization ISO/IEC JTC1 has also developed JPEG 2000 Part 2 (), which includes Extensions to the compression techniques described in Part 1 of the JPEG 2000 Standard. Annex J of JPEG 2000 Part 2 describes extensions to the ICT and RCT multiple component transformations allowed in Part 1. Two types of multiple component transformations are defined in Annex J of Part 2 of JPEG 2000: @@ -7930,27 +8033,39 @@
MPEG2 Video Compression The International Standards Organization ISO/IEC MPEG2 has developed an International Standard, 'Information Technology - Generic coding of moving pictures and associated audio information: video -- part 2', referred to as "MPEG-2". - A DICOM Transfer Syntax for MPEG2 Video Compression shall be identified by a UID value of either: + A DICOM Transfer Syntax for MPEG2 Video Compression shall be identified by a UID of one of: - 1.2.840.10008.1.2.4.100 corresponding to MPEG2 Main Profile / Main Level option of the ISO/IEC MPEG2 Video standard + 1.2.840.10008.1.2.4.100 corresponding to MPEG2 Main Profile / Main Level option of the ISO/IEC MPEG2 Video standard encoded in a single Fragment, - 1.2.840.10008.1.2.4.101 corresponding to the MPEG2 Main Profile / High Level option of the ISO/IEC MPEG2 Video standard. + 1.2.840.10008.1.2.4.101 corresponding to the MPEG2 Main Profile / High Level option of the ISO/IEC MPEG2 Video standard encoded in a single Fragment, + + 1.2.840.10008.1.2.4.100.1 corresponding to MPEG2 Main Profile / Main Level option of the ISO/IEC MPEG2 Video standard encoded in one or more Fragments, + + + 1.2.840.10008.1.2.4.101.1 corresponding to the MPEG2 Main Profile / High Level option of the ISO/IEC MPEG2 Video standard encoded in one or more Fragments. +
MPEG-4 AVC/H.264 High Profile / Level 4.1 Video Compression The International Standards Organization ISO/IEC MPEG4 has developed an International Standard, (MPEG-4 Part 10), for the video compression of generic coding of moving pictures and associated audio information. This standard is jointly maintained and has identical technical content as the ITU-T H.264 standard. - A DICOM Transfer Syntax for MPEG-4 AVC/H.264 Video Compression shall be identified by a UID value of either: + A DICOM Transfer Syntax for MPEG-4 AVC/H.264 Video Compression shall be identified by a UID of one of: - 1.2.840.10008.1.2.4.102 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.1 of the ITU-T H.264 Video standard + 1.2.840.10008.1.2.4.102 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.1 of the ITU-T H.264 Video standard encoded in a single Fragment, - 1.2.840.10008.1.2.4.103 corresponding to the MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 of the ITU-T H.264 Video standard with the temporal and spatial resolution restrictions defined in . + 1.2.840.10008.1.2.4.103 corresponding to the MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 of the ITU-T H.264 Video standard with the temporal and spatial resolution restrictions defined in encoded in a single Fragment, + + 1.2.840.10008.1.2.4.102.1 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.1 of the ITU-T H.264 Video standard encoded in one or more Fragments, + + + 1.2.840.10008.1.2.4.103.1 corresponding to the MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 of the ITU-T H.264 Video standard with the temporal and spatial resolution restrictions defined in encoded in one or more Fragments. +
@@ -7958,20 +8073,29 @@ The International Standards Organization ISO/IEC MPEG4 has developed an International Standard, (MPEG-4 Part 10), for the video compression of generic coding of moving pictures and associated audio information. This standard is jointly maintained and has identical technical content as the ITU-T H.264 standard. - A DICOM Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video Compression shall be identified by a UID value of: + A DICOM Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video Compression shall be identified by a UID of one of: - - 1.2.840.10008.1.2.4.104 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.2 of the ITU-T H.264 Video standard - with the restriction that frame packing for stereoscopic 3D content shall not be used as defined in - . - + + 1.2.840.10008.1.2.4.104 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.2 of the ITU-T H.264 Video standard + with the restriction that frame packing for stereoscopic 3D content shall not be used as defined in + , encoded in a single Fragment, + + + 1.2.840.10008.1.2.4.104.1 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.2 of the ITU-T H.264 Video standard + with the restriction that frame packing for stereoscopic 3D content shall not be used as defined in + , encoded in one or more Fragments. + - A DICOM Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video Compression shall be identified by a UID value of: + A DICOM Transfer Syntax MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video Compression shall be identified by a UID of one of: - - 1.2.840.10008.1.2.4.105 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.2 of the ITU-T H.264 Video standard. - It should be used for transmitting stereoscopic 3D content with frame packing formats as defined in . - + + 1.2.840.10008.1.2.4.105 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.2 of the ITU-T H.264 Video standard. + It should be used for transmitting stereoscopic 3D content with frame packing formats as defined in , encoded in a single Fragment, + + + 1.2.840.10008.1.2.4.105.1 corresponding to the MPEG-4 AVC/H.264 High Profile / Level 4.2 of the ITU-T H.264 Video standard. + It should be used for transmitting stereoscopic 3D content with frame packing formats as defined in , encoded in one or more Fragments. +
@@ -7979,17 +8103,20 @@ The International Standards Organization ISO/IEC MPEG4 has developed an International Standard, (MPEG-4 Part 10), for the video compression of generic coding of moving pictures and associated audio information. This standard is jointly maintained and has identical technical content as the ITU-T H.264 standard. - A DICOM Transfer Syntax for MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 Video Compression shall be identified by a UID value of: + A DICOM Transfer Syntax for MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 Video Compression shall be identified by a UID of one of: - - 1.2.840.10008.1.2.4.106 corresponding to the MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 of the ITU-T H.264 Video standard. - + + 1.2.840.10008.1.2.4.106 corresponding to the MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 of the ITU-T H.264 Video standard, encoded in a single Fragment, + + + 1.2.840.10008.1.2.4.106.1 corresponding to the MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 of the ITU-T H.264 Video standard, encoded in one or more Fragments. +
HEVC/H.265 Main Profile / Level 5.1 Video Compression The International Standards Organization ISO/IEC MPEG has developed an International Standard, (HEVC), for the video compression of generic coding of moving pictures and associated audio information. This standard is jointly maintained and has identical technical content as the HEVC standard. - A DICOM Transfer Syntax for HEVC/H.265 Main Profile / Level 5.1 Video Compression shall be identified by a UID value of: + A DICOM Transfer Syntax for HEVC/H.265 Main Profile / Level 5.1 Video Compression shall be identified by a UID of: 1.2.840.10008.1.2.4.107 corresponding to the HEVC/H.265 Main Profile / Level 5.1 of the HEVC Video standard. @@ -7999,7 +8126,7 @@
HEVC/H.265 Main 10 Profile / Level 5.1 Video Compression The International Standards Organization ISO/IEC MPEG has developed an International Standard, (HEVC), for the video compression of generic coding of moving pictures and associated audio information. This standard is jointly maintained and has identical technical content as the HEVC standard. - A DICOM Transfer Syntax for HEVC/H.265 Main 10 Profile / Level 5.1 Video Compression shall be identified by a UID value of: + A DICOM Transfer Syntax for HEVC/H.265 Main 10 Profile / Level 5.1 Video Compression shall be identified by a UID of: 1.2.840.10008.1.2.4.108 corresponding to the HEVC/H.265 Main 10 Profile / Level 5.1 of the HEVC Video standard. @@ -8008,7 +8135,7 @@
Encapsulated Uncompressed Explicit VR Little Endian - The DICOM Transfer Syntax for Encapsulated Uncompressed Explicit VR Little Endian encodes a stream of one or more frames of uncompressed pixel data as Encapsulated fragments, and shall be identified by a UID value of "1.2.840.10008.1.2.1.98". + The DICOM Transfer Syntax for Encapsulated Uncompressed Explicit VR Little Endian encodes a stream of one or more frames of uncompressed pixel data as Encapsulated fragments, and shall be identified by a UID of "1.2.840.10008.1.2.1.98". If the object allows multi-frame images in the pixel data field, then each frame shall be encoded separately. Each frame shall be encoded​ in one and only one Fragment (see ). Within the Item Value of each Fragment (frame), the PixelData shall be encoded in the same manner as if it were encoded in Native format, including byte order, and padding to an even Item Length. OB VR shall be used, as required for all Encapsulated Format Transfer Syntaxes.
@@ -8021,7 +8148,7 @@ - The Pixel Data in Pixel Data (7FE0,0010), Float Pixel Data (7FE0,0008) or Double Float Pixel Data (7FE0,0009) is not handled in any special manner. The pixel data is first encoded as sequential uncompressed frames without encapsulation, and then is handled as part of the byte stream fed to the "deflate" compressor in the same manner as the value of any other attribute. + The Pixel Data in Pixel Data (7FE0,0010), Float Pixel Data (7FE0,0008) or Double Float Pixel Data (7FE0,0009) is not handled in any special manner. The pixel data is first encoded as sequential uncompressed frames without encapsulation, and then is handled as part of the byte stream fed to the "deflate" compressor in the same manner as the Value Field of any other Data Element. This Transfer Syntax is particularly useful for compression of objects without pixel data, such as structured reports. It is not particularly effective at image compression, since any benefit obtained from compressing the non-pixel data is offset by less effective compression of the much larger pixel data. @@ -8080,7 +8207,7 @@ Overlay data, if present, shall only be encoded in the Overlay Data (60xx,3000) Element, which shall have the Value Representation OB or OW and shall be encoded in Little Endian. - Data Element (0028,0004) Photometric Interpretation shall be limited to the values: MONOCHROME1, MONOCHROME2, YBR_ICT and YBR_RCT. + Data Element (0028,0004) Photometric Interpretation shall be limited to the Values: MONOCHROME1, MONOCHROME2, YBR_ICT and YBR_RCT. @@ -8118,7 +8245,7 @@ are still applicable with some accommodations below. - As DICOM Photometric Interpretation (0028,0004) values YBR_FULL, YBR_FULL_422, YBR_PARTIAL_420 are based on CCIR 601 (aka BT.601), DICOM-RTV supports only the following: + As DICOM Photometric Interpretation (0028,0004) Values YBR_FULL, YBR_FULL_422, YBR_PARTIAL_420 are based on CCIR 601 (aka BT.601), DICOM-RTV supports only the following: @@ -8257,7 +8384,7 @@ C'R00 (10 bits) |0|0|0|0|0|0| -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ]]> - A DICOM Transfer Syntax for SMPTE ST 2110-20 Uncompressed Progressive Active Video shall be identified by a UID value of + A DICOM Transfer Syntax for SMPTE ST 2110-20 Uncompressed Progressive Active Video shall be identified by a UID of 1.2.840.10008.1.2.7.1 corresponding to for the progressive video. @@ -8268,7 +8395,7 @@ SMPTE ST 2110-20 Uncompressed Interlaced Active Video Transfer Syntax This Transfer Syntax is used in a DICOM-RTV Metadata Flow in order to describe the accompanying Video Flow. The parameters are similar to the ones described in the Uncompressed Progressive Active Video (), but the frames are interlaced, one frame containing only odd lines and the next one containing only even lines. - A DICOM Transfer Syntax for SMPTE ST 2110-20 Uncompressed Interlaced Active Video shall be identified by a UID value of: + A DICOM Transfer Syntax for SMPTE ST 2110-20 Uncompressed Interlaced Active Video shall be identified by a UID of: 1.2.840.10008.1.2.7.2 corresponding to for the interlaced video. @@ -8524,7 +8651,7 @@ Number of Waveform Channels is limited to 15 - A DICOM Transfer Syntax for SMPTE ST 2110-30 PCM Digital Audio shall be identified by a UID value of: + A DICOM Transfer Syntax for SMPTE ST 2110-30 PCM Digital Audio shall be identified by a UID of: 1.2.840.10008.1.2.7.3 corresponding to the SMPTE ST 2110-30 Professional Media over IP Networks: PCM Digital Audio. @@ -8688,9 +8815,9 @@ A Pixel Cell is the container for a Pixel Sample Value and optionally additional bits. These additional bits are used to place Pixels on certain boundaries (byte, word, etc.). A Pixel Cell exists for every individual Pixel Sample Value in the Pixel Data. The size of the Pixel Cells is specified by Bits Allocated (0028,0100) and is greater than or equal to the Bits Stored (0028,0101). The placement of the Pixel Sample Values within the Pixel Cells is specified by High Bit (0028,0102). Any restrictions on the characteristics of a Pixel Cell and the Pixel Sample Value contained therein are specific to the Information Object Definition (e.g., Image Object) containing the Pixel Data Element (see ). The Pixel Data Element, as specified by the DICOM Default Little Endian Transfer Syntax in , has a Value Representation of OW (Other Word). The Pixel Data in DICOM, as it was in ACR-NEMA 2.0, is packed, except that Bits Allocated is always either 1, or a multiple of 8 (see Figure ). One way to visualize this packed encoding is to imagine encoding the Pixel Cells as a concatenated stream of bits from the least significant bit of the first Pixel Cell up through the most significant bit of the last Pixel Cell. Within this stream, the most significant bit of any Pixel Cell is followed by the least significant bit of the next Pixel Cell. The Pixel Data can then be broken up into a stream of physical 16-bit words, each of which is subject to the byte ordering constraints of the Transfer Syntax. - All other (non-default) DICOM Transfer Syntaxes make use of explicit VR encoding. For these Transfer Syntaxes, all Pixel Data where Bits Allocated is less than or equal to 8 may be encoded with an explicit VR of OB (see ). As in the OW case, Pixel Cells are packed together, but in this case the Pixel Data is broken up into a stream of physical 8-bit words. + All other (non-default) DICOM Transfer Syntaxes make use of Explicit VR encoding. For these Transfer Syntaxes, all Pixel Data where Bits Allocated is less than or equal to 8 may be encoded with an Explicit VR of OB (see ). As in the OW case, Pixel Cells are packed together, but in this case the Pixel Data is broken up into a stream of physical 8-bit words. - For Pixel Data encoded with an explicit VR of OB, the encoding of the Pixel Data is unaffected by byte ordering. + For Pixel Data encoded with an Explicit VR of OB, the encoding of the Pixel Data is unaffected by byte ordering.
@@ -8753,7 +8880,7 @@
- As a last pair of examples, for Pixel Data having the Value Representation OW and the following attributes: 8 bits allocated, 8 bits stored, and a high bit of 7; the resulting byte streams pictured in are as they would be transmitted across a network and/or stored on media. For Pixel Data having the same attributes, but having the explicit Value Representation OB; the resulting byte streams are unaffected by byte ordering and are pictured in . + As a last pair of examples, for Pixel Data having the Value Representation OW and the following Attributes: 8 bits allocated, 8 bits stored, and a high bit of 7; the resulting byte streams pictured in are as they would be transmitted across a network and/or stored on media. For Pixel Data having the same Attributes, but having the explicit Value Representation OB; the resulting byte streams are unaffected by byte ordering and are pictured in .
Sample Pixel Data Byte Streams for 8-bits Allocated and 8-bits Stored (VR = OW) @@ -8779,7 +8906,7 @@
Various Additional Examples of Pixel and Overlay Data Cells - The following examples further illustrate the use of the data elements for Bits Allocated (0028,0100), Bits Stored (0028,0101) and High Bit (0028,0102) in the encoding of Pixel and Overlay Data. All examples show sample Pixel Cells before being encoded in byte streams (and before being affected by a particular Transfer Syntax). + The following examples further illustrate the use of the Data Elements for Bits Allocated (0028,0100), Bits Stored (0028,0101) and High Bit (0028,0102) in the encoding of Pixel and Overlay Data. All examples show sample Pixel Cells before being encoded in byte streams (and before being affected by a particular Transfer Syntax).
Example 1 of Pixel and Overlay Data Cells @@ -9827,7 +9954,7 @@
DICOM Transfer Syntax UIDs for JPEG
The different coding processes specified in the JPEG Standard are closely related. By extending the capability of an implementation, increasingly more 'lower level' processes can also be executed by the implementation. This is shown in for Huffman Coding. - Inclusion of a JPEG-coded image in a DICOM message is facilitated by the use of specific Transfer Syntaxes that are defined in . Independent of the JPEG coding processes, the same syntax applies. The only distinction for different processes in the syntax (apart from different SOF marker segments in the JPEG bit stream) is the UID value. lists the UID values in the Transfer Syntax for the various JPEG coding processes for reference. + Inclusion of a JPEG-coded image in a DICOM message is facilitated by the use of specific Transfer Syntaxes that are defined in . Independent of the JPEG coding processes, the same syntax applies. The only distinction for different processes in the syntax (apart from different SOF marker segments in the JPEG bit stream) is the UID. lists the UIDs in the Transfer Syntax for the various JPEG coding processes for reference. @@ -10019,7 +10146,7 @@ Encapsulated RLE Compressed Images (Normative)
Summary - This annex describes how to apply RLE Image Compression to an image or an individual frame of a multi-frame image. This method can be used for any image, independent of the values of the data elements that describe the image (i.e., Photometric Interpretation (0028,0004) and Bits Stored (0028,0101)). + This annex describes how to apply RLE Image Compression to an image or an individual frame of a multi-frame image. This method can be used for any image, independent of the Values of the Data Elements that describe the image (i.e., Photometric Interpretation (0028,0004) and Bits Stored (0028,0101)). RLE Image Compression consists of the following steps: @@ -10317,7 +10444,7 @@ 0000H
Relationship Between the Lossy JPEG Huffman Coding Processes
- FFFF FFFFH undefined length + FFFF FFFFH Undefined Length (FFFE,E000) @@ -10621,7 +10748,8 @@ The purpose of this section is to explain the character sets for the Japanese language.
JIS X 0201 - has the following code elements: + + has the following code elements: ISO-IR 13 Japanese katakana (phonetic) characters (94 characters) @@ -10630,7 +10758,8 @@ ISO-IR 14 Japanese romaji (alphanumeric) characters (94 characters) - defines a 7-bit romaji code table (ISO-IR 14), a 7-bit katakana code table (ISO-IR 13), and the combination of romaji and katakana as an 8-bit code table (ISO-IR 14 as G0, ISO-IR 13 as G1). + + defines a 7-bit romaji code table (ISO-IR 14), a 7-bit katakana code table (ISO-IR 13), and the combination of romaji and katakana as an 8-bit code table (ISO-IR 14 as G0, ISO-IR 13 as G1). The 7-bit romaji (ISO-IR 14) is identical to ASCII (ISO-IR 6) except that bit combination 05/12 represents a yen sign and bit combination 07/14 represents an over-line. These are national Graphic Character allocations in . The Escape Sequence for ISO/IEC 2022 is shown for reference in (for the Defined Terms, see ). @@ -10690,14 +10819,15 @@ does not include the G2 and G3 sets that are not used in DICOM. See . - Defined Terms ISO_IR 13 and ISO 2022 IR 13 for the value of the Specific Character Set (0008,0005) support the G0 set for ISO-IR 14 and G1 set for ISO-IR 13. See . + Defined Terms ISO_IR 13 and ISO 2022 IR 13 for the Value of the Specific Character Set (0008,0005) support the G0 set for ISO-IR 14 and G1 set for ISO-IR 13. See .
JIS X 0208 - has the following code element: + + has the following code element: ISO-IR 87: Japanese kanji (ideographic), hiragana (phonetic), and katakana (phonetic) characters (942 characters, 2-byte). @@ -10706,7 +10836,8 @@
JIS X 0212 - has the following code element: + + has the following code element: ISO-IR 159: Supplementary Japanese kanji (ideographic) characters (942 characters, 2-byte) @@ -10772,7 +10903,7 @@ The table does not include the G2 and G3 sets that are not used in DICOM. See . - Defined Term ISO 2022 IR 87 for the value of the Specific Character Set (0008,0005) supports the G0 set for ISO-IR 87, and Defined Term ISO 2022 IR 159 supports the G0 set for ISO-IR 159. See . + Defined Term ISO 2022 IR 87 for the Value of the Specific Character Set (0008,0005) supports the G0 set for ISO-IR 87, and Defined Term ISO 2022 IR 159 supports the G0 set for ISO-IR 159. See . @@ -10808,27 +10939,42 @@
@@ -10984,7 +11130,9 @@ GL @@ -11010,7 +11158,8 @@ GL @@ -11034,7 +11183,9 @@ GL @@ -11061,7 +11212,8 @@ GL @@ -11085,7 +11237,9 @@ GL @@ -11204,7 +11358,8 @@ GR @@ -11225,7 +11380,8 @@ GL @@ -11252,7 +11408,8 @@ GL @@ -11276,7 +11433,8 @@ GL @@ -11303,7 +11461,8 @@ GL @@ -11327,7 +11486,8 @@ GL @@ -11340,7 +11500,8 @@ Character Sets and Person Name Value Representation in the Korean Language (Informative)
Character Sets For The Korean Language in DICOM - (registered as ISO-IR 149) is used as a Korean character set in DICOM. This character set is the one most broadly used for the representation of Korean characters. It can be encoded by code extension techniques, and is registered in . + + (registered as ISO-IR 149) is used as a Korean character set in DICOM. This character set is the one most broadly used for the representation of Korean characters. It can be encoded by code extension techniques, and is registered in . The Escape Sequence is shown for reference in (see )
ASCII (ISO-IR 6) - Katakana (ISO-IR 13) - Romaji (ISO-IR 14) - Kanji (ISO-IR 87) - Kanji (ISO-IR 159) + + Katakana (ISO-IR 13) + + Romaji (ISO-IR 14) + + Kanji (ISO-IR 87) + + Kanji (ISO-IR 159) ASCII (ISO-IR 6) - Romaji (ISO-IR 14) - -1978 Kanji (ISO-IR 42) - -1983 Kanji (ISO-IR 87) + + Romaji (ISO-IR 14) + +-1978 Kanji (ISO-IR 42) + +-1983 Kanji (ISO-IR 87) ASCII (ISO-IR 6) - (ISO-IR 100) - Greek (ISO-IR 126) - Romaji (ISO-IR 14) - -1978 Kanji (ISO-IR 42) - -1983 Kanji (ISO-IR 87) - Kanji (ISO-IR 159) - (ISO-IR 58) - (ISO-IR 149) + + (ISO-IR 100) + + Greek (ISO-IR 126) + + Romaji (ISO-IR 14) + +-1978 Kanji (ISO-IR 42) + +-1983 Kanji (ISO-IR 87) + + Kanji (ISO-IR 159) + + (ISO-IR 58) + + (ISO-IR 149)
- + + +
- : + +: Japanese kanji, hiragana, katakana
- + + + for delimiters
- : + +: Japanese hiragana, and katakana
- + + + for delimiters
- : + +: Japanese katakana
- : + +: Japanese romaji for delimiters
- : + +: Japanese kanji, hiragana, katakana
- : + +: Japanese romaji for delimiters
- : + +: Japanese hiragana, and katakana
- : + +: Japanese romaji for delimiters
@@ -11537,7 +11698,9 @@ GL @@ -11559,7 +11722,8 @@ GL @@ -11583,7 +11747,8 @@ GR @@ -11606,7 +11771,8 @@ GL @@ -11630,7 +11796,8 @@ GR @@ -11650,14 +11817,14 @@ - Some healthcare information systems may encode a "westernized" name with other patient aliases in a separate attribute, e.g., Other Patient Names (0010,1091). + Some healthcare information systems may encode a "westernized" name with other patient aliases in a separate Attribute, e.g., Other Patient Names (0010,1091). Some environments using Chinese language may use the third name component, e.g., for the Yi or Mongolian script, with or without the first name component. This would be similar to the Japanese and Korean name component usage. - In the example below, the Specific Character Set attribute (0008,0005) would contain: + In the example below, the Specific Character Set Attribute (0008,0005) would contain: (0008,0005) ISO_IR 192 @@ -11773,7 +11940,7 @@ See notes to . - In the example below, the Specific Character Set attribute (0008,0005) would contain: + In the example below, the Specific Character Set Attribute (0008,0005) would contain: (0008,0005) GB18030 @@ -11885,7 +12052,7 @@ A previous edition of DICOM required the first name component group to use a single byte character set (see PS3.5-2008). Unicode in UTF-8 may now be used in that component group simply as a matter of a different character set encoding, but with the same application use of that component group. - Healthcare information systems will use specific scripts in one, two, or three of the Person Name component groups in accordance with local policy. Conformant DICOM Application Entities that receive name attributes must accept multiple name component groups. An Application Entity that is configurable to allow the use of local script for names in either the first or the third component group, and a transliteration script in the other, would support all these typical representations. + Healthcare information systems will use specific scripts in one, two, or three of the Person Name component groups in accordance with local policy. Conformant DICOM Application Entities that receive name Attributes must accept multiple name component groups. An Application Entity that is configurable to allow the use of local script for names in either the first or the third component group, and a transliteration script in the other, would support all these typical representations. The transliteration (from a local script) may be a non-Latin script, e.g., Cyrillic. The same principles apply, and the Cyrillized name might be encoded in the first component group and the local script (which may in fact be a Latin-derived script) in the third component group. @@ -11898,7 +12065,8 @@ Character Sets and Person Name Value Representation in the Chinese Language with Code Extensions (Informative)
Character Sets for the Chinese Language in DICOM - (registered as ISO-IR 58) is used as a Chinese character set in DICOM. This character set is the one most broadly used for the representation of Chinese characters. It can be encoded by code extension techniques. + + (registered as ISO-IR 58) is used as a Chinese character set in DICOM. This character set is the one most broadly used for the representation of Chinese characters. It can be encoded by code extension techniques. The Escape Sequence is shown for reference in (see )
ISO/IEC 2022 Escape Sequence for ISO-IR 149
- + + +
- : + +: For delimiters
- : + +: Hangul and Hanja
- : + +: For delimiters
- : + +: Hangul and Hanja
@@ -11987,10 +12155,10 @@ The underlined byte codes correspond to double byte characters, the bold byte codes to escape sequences. - The multi-byte character set (ISO-IR 58) and single-byte character set can be used intermixed without any explicit escape sequence after the initial escape sequence, up to the next delimiter (^ or =) or the end of the value field. + The multi-byte character set (ISO-IR 58) and single-byte character set can be used intermixed without any explicit escape sequence after the initial escape sequence, up to the next delimiter (^ or =) or the end of the Value Field. Once has been designated to G0 and ISO-IR 58 to G1, each character set has a different code area, thus can be used intermixed. The decoder will check the most significant bit of a character to know whether it is a two byte character in the G1 area (high bit one) or a one byte character in the G0 area (high bit zero). - There does not need to be an explicit escape to invoke into G0 at the end of the string prior to a delimiter (^ or =) or the end of the value field. + There does not need to be an explicit escape to invoke into G0 at the end of the string prior to a delimiter (^ or =) or the end of the Value Field. However, there does need to be a new invocation of ISO-IR 58 in each name component in which it is used. @@ -12141,7 +12309,9 @@ G0 @@ -12192,7 +12362,8 @@ G0 diff --git a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part06.xml b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part06.xml similarity index 97% rename from dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part06.xml rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part06.xml index 230a70a..af979ac 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/dicom-standard-xml/part06.xml +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-gradleplugin/src/main/resources/dicom-standard-xml/part06.xml @@ -1,13 +1,13 @@ PS3.6 - DICOM PS3.6 2021d - Data Dictionary + DICOM PS3.6 2022d - Data Dictionary DICOM Standards Committee - 2021 + 2022 NEMA @@ -113,7 +113,7 @@ <glossdiv label="3.1" status="2" xml:id="sect_3.1"> <title>DICOM Introduction and Overview Definition - This Part of the Standard makes use of the following term defined in : + This Part of the Standard makes use of the following terms defined in : Attribute @@ -603,6 +603,26 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -61394,7 +62930,7 @@ LO + + + + + + + + @@ -79964,22 +81496,34 @@ @@ -80004,22 +81548,34 @@ @@ -81550,6 +83106,26 @@ + + + + + + + + @@ -91440,22 +93028,34 @@ @@ -92020,22 +93620,34 @@ @@ -94052,542 +95664,542 @@ @@ -95270,6 +96882,306 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -104797,7 +106749,7 @@ @@ -104825,7 +106777,7 @@ @@ -104853,7 +106805,7 @@ @@ -104881,7 +106833,7 @@ @@ -104909,7 +106861,7 @@ @@ -104956,7 +106908,7 @@ @@ -104984,7 +106936,7 @@ @@ -105012,7 +106964,7 @@ @@ -105040,7 +106992,7 @@ @@ -105068,7 +107020,7 @@ @@ -105096,7 +107048,7 @@ @@ -105124,7 +107076,7 @@ @@ -105152,7 +107104,7 @@ @@ -105180,7 +107132,7 @@ @@ -105355,177 +107307,310 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -105597,7 +107682,7 @@ @@ -105853,7 +107938,7 @@ @@ -105946,7 +108031,7 @@ @@ -105974,7 +108059,7 @@ @@ -106320,6 +108405,44 @@ + + + + + + + + + + + + + + @@ -106391,7 +108514,7 @@ @@ -106419,7 +108542,7 @@ @@ -106436,7 +108559,7 @@ @@ -106464,7 +108587,7 @@ @@ -106560,7 +108683,7 @@ @@ -106588,7 +108711,7 @@ @@ -106616,7 +108739,7 @@ @@ -106644,7 +108767,7 @@ @@ -106767,7 +108890,7 @@ @@ -106814,7 +108937,7 @@ @@ -106905,7 +109028,7 @@ Printer​Instance @@ -107041,7 +109164,7 @@ @@ -107069,7 +109192,7 @@ @@ -107086,18 +109209,18 @@ @@ -107114,7 +109237,7 @@ @@ -107153,7 +109276,7 @@ @@ -107181,7 +109304,7 @@ @@ -107198,7 +109321,7 @@ @@ -107226,7 +109349,7 @@ @@ -107254,7 +109377,7 @@ @@ -107540,7 +109663,7 @@ @@ -107682,7 +109805,7 @@ @@ -107710,7 +109833,7 @@ @@ -107871,7 +109994,7 @@ @@ -107899,7 +110022,7 @@ @@ -107927,7 +110050,7 @@ @@ -108240,7 +110363,7 @@ @@ -108268,7 +110391,7 @@ @@ -108581,7 +110704,7 @@ @@ -109016,7 +111139,7 @@ @@ -109055,7 +111178,7 @@ @@ -109634,7 +111757,7 @@ @@ -109651,7 +111774,7 @@ @@ -109679,7 +111802,7 @@ @@ -109718,7 +111841,7 @@ @@ -110278,7 +112401,7 @@ @@ -110472,6 +112595,139 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + @@ -111181,7 +113437,7 @@ @@ -111209,7 +113465,7 @@ @@ -111237,7 +113493,7 @@ @@ -111398,7 +113654,7 @@ @@ -111426,7 +113682,7 @@ @@ -111454,7 +113710,7 @@ @@ -111482,7 +113738,7 @@ @@ -111529,7 +113785,7 @@ @@ -111557,7 +113813,7 @@ @@ -111585,7 +113841,7 @@ @@ -111602,7 +113858,7 @@ @@ -111630,7 +113886,7 @@ @@ -111669,7 +113925,7 @@ @@ -111697,7 +113953,7 @@ @@ -111725,7 +113981,7 @@ @@ -113695,6 +115951,20 @@ See . + + + + + + @@ -129090,7 +131364,9 @@ @@ -136493,7 +138775,7 @@ @@ -136511,7 +138793,7 @@ @@ -136529,7 +138811,7 @@ @@ -136547,7 +138829,7 @@ @@ -136565,7 +138847,7 @@ @@ -136583,7 +138865,7 @@ @@ -136601,7 +138883,7 @@ @@ -136619,7 +138901,7 @@ @@ -136637,7 +138919,7 @@ @@ -136655,7 +138937,7 @@ @@ -136673,7 +138955,7 @@ @@ -136691,7 +138973,7 @@ @@ -136709,7 +138991,7 @@ @@ -136727,7 +139009,7 @@ @@ -136745,7 +139027,7 @@ @@ -136763,7 +139045,7 @@ @@ -136781,7 +139063,7 @@ @@ -136799,7 +139081,7 @@ @@ -136817,7 +139099,7 @@ @@ -136835,7 +139117,7 @@ @@ -136853,7 +139135,7 @@ @@ -136871,7 +139153,7 @@ @@ -136889,7 +139171,7 @@ @@ -136907,7 +139189,7 @@ @@ -136925,7 +139207,7 @@ @@ -136943,7 +139225,7 @@ @@ -136961,7 +139243,7 @@ @@ -136979,7 +139261,7 @@ @@ -136997,7 +139279,7 @@ @@ -137015,7 +139297,7 @@ @@ -137033,7 +139315,7 @@ @@ -137051,7 +139333,7 @@ @@ -137069,7 +139351,7 @@ @@ -137087,7 +139369,7 @@ @@ -137105,7 +139387,7 @@ @@ -137123,7 +139405,7 @@ @@ -137141,7 +139423,7 @@ @@ -137159,7 +139441,7 @@ @@ -137177,7 +139459,7 @@ @@ -137195,7 +139477,7 @@ @@ -137213,7 +139495,7 @@ @@ -137231,7 +139513,7 @@ @@ -137249,7 +139531,7 @@ @@ -137267,7 +139549,7 @@ @@ -137285,7 +139567,7 @@ @@ -137303,7 +139585,7 @@ @@ -137321,7 +139603,7 @@ @@ -137339,7 +139621,7 @@ @@ -137357,7 +139639,7 @@ @@ -137375,7 +139657,7 @@ @@ -137393,7 +139675,7 @@ @@ -137411,7 +139693,7 @@ @@ -137429,280 +139711,837 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + -
ISO/IEC 2022 Escape Sequence for ISO-IR 58
- + + +
- : + +: For delimiters
+ (0008,0017) + + Acquisition UID + + Acquisition​UID + + UI + + 1 + + +
(0008,0018) @@ -623,6 +643,26 @@
+ (0008,0019) + + Pyramid UID + + Pyramid​UID + + UI + + 1 + + +
(0008,001A) @@ -2579,6 +2619,846 @@
+ (0008,0400) + + Scope of Inventory Sequence + + Scope​Of​Inventory​Sequence + + SQ + + 1 + + +
+ (0008,0401) + + Inventory Purpose + + Inventory​Purpose + + LT + + 1 + + +
+ (0008,0402) + + Inventory Instance Description + + Inventory​Instance​Description + + LT + + 1 + + +
+ (0008,0403) + + Inventory Level + + Inventory​Content​Level + + CS + + 1 + + +
+ (0008,0404) + + Item Inventory DateTime + + Item​Inventory​Date​Time + + DT + + 1 + + +
+ (0008,0405) + + Removed from Operational Use + + Removed​From​Operational​Use + + CS + + 1 + + +
+ (0008,0406) + + Reason for Removal Code Sequence + + Reason​For​Removal​Code​Sequence + + SQ + + 1 + + +
+ (0008,0407) + + Stored Instance Base URI + + Stored​Instance​Base​URI + + UR + + 1 + + +
+ (0008,0408) + + Folder Access URI + + Folder​Access​URI + + UR + + 1 + + +
+ (0008,0409) + + File Access URI + + File​Access​URI + + UR + + 1 + + +
+ (0008,040A) + + Container File Type + + Container​File​Type + + CS + + 1 + + +
+ (0008,040B) + + Filename in Container + + Filename​In​Container + + UR + + 1 + + +
+ (0008,040C) + + File Offset in Container + + File​Offset​In​Container + + UV + + 1 + + +
+ (0008,040D) + + File Length in Container + + File​Length​In​Container + + UV + + 1 + + +
+ (0008,040E) + + Stored Instance Transfer Syntax UID + + Stored​Instance​Transfer​Syntax​UID + + UI + + 1 + + +
+ (0008,040F) + + Extended Matching Mechanisms + + Extended​Matching​Mechanisms + + CS + + 1-n + + +
+ (0008,0410) + + Range Matching Sequence + + Range​Matching​Sequence + + SQ + + 1 + + +
+ (0008,0411) + + List of UID Matching Sequence + + UID​List​Matching​Sequence + + SQ + + 1 + + +
+ (0008,0412) + + Empty Value Matching Sequence + + Empty​Value​Matching​Sequence + + SQ + + 1 + + +
+ (0008,0413) + + General Matching Sequence + + General​Matching​Sequence + + SQ + + 1 + + +
+ (0008,0414) + + Requested Status Interval + + Requested​Status​Interval + + US + + 1 + + +
+ (0008,0415) + + Retain Instances + + Retain​Instances + + CS + + 1 + + +
+ (0008,0416) + + Expiration DateTime + + Expiration​Date​Time + + DT + + 1 + + +
+ (0008,0417) + + Transaction Status + + Transaction​Status + + CS + + 1 + + +
+ (0008,0418) + + Transaction Status Comment + + Transaction​Status​Comment + + LT + + 1 + + +
+ (0008,0419) + + File Set Access Sequence + + File​Set​Access​Sequence + + SQ + + 1 + + +
+ (0008,041A) + + File Access Sequence + + File​Access​Sequence + + SQ + + 1 + + +
+ (0008,041B) + + Record Key + + Record​Key + + OB + + 1 + + +
+ (0008,041C) + + Prior Record Key + + Prior​Record​Key + + OB + + 1 + + +
+ (0008,041D) + + Metadata Sequence + + Metadata​Sequence + + SQ + + 1 + + +
+ (0008,041E) + + Updated Metadata Sequence + + Updated​Metadata​Sequence + + SQ + + 1 + + +
+ (0008,041F) + + Study Update DateTime + + Study​Update​Date​Time + + DT + + 1 + + +
+ (0008,0420) + + Inventory Access End Points Sequence + + Inventory​Access​End​Points​Sequence + + SQ + + 1 + + +
+ (0008,0421) + + Study Access End Points Sequence + + Study​Access​End​Points​Sequence + + SQ + + 1 + + +
+ (0008,0422) + + Incorporated Inventory Instance Sequence + + Incorporated​Inventory​Instance​Sequence + + SQ + + 1 + + +
+ (0008,0423) + + Inventoried Studies Sequence + + Inventoried​Studies​Sequence + + SQ + + 1 + + +
+ (0008,0424) + + Inventoried Series Sequence + + Inventoried​Series​Sequence + + SQ + + 1 + + +
+ (0008,0425) + + Inventoried Instances Sequence + + Inventoried​Instances​Sequence + + SQ + + 1 + + +
+ (0008,0426) + + Inventory Completion Status + + Inventory​Completion​Status + + CS + + 1 + + +
+ (0008,0427) + + Number of Study Records in Instance + + Number​Of​Study​Records​In​Instance + + UL + + 1 + + +
+ (0008,0428) + + Total Number of Study Records + + Total​Number​Of​Study​Records + + UV + + 1 + + +
+ (0008,0429) + + Maximum Number of Records + + Maximum​Number​Of​Records + + UV + + 1 + + +
@@ -2951,6 +3831,26 @@
+ (0008,1088) + + Pyramid Description + + Pyramid​Description + + LO + + 1 + + +
(0008,1090) @@ -6891,6 +7791,26 @@
+ (0012,0054) + + Clinical Trial Time Point Type Code Sequence + + Clinical​Trial​Time​Point​Type​Code​Sequence + + SQ + + 1 + + +
(0012,0060) @@ -7667,6 +8587,166 @@ DICONDE
+ (0014,0200) + + Data Element Label Sequence + + Data​Element​Label​Sequence + + SQ + + 1 + + DICONDE +
+ (0014,0201) + + Data Element Label Item Sequence + + Data​Element​Label​Item​Sequence + + SQ + + 1 + + DICONDE +
+ (0014,0202) + + Data Element + + Data​Element + + AT + + 1 + + DICONDE +
+ (0014,0203) + + Data Element Name + + Data​Element​Name + + LO + + 1 + + DICONDE +
+ (0014,0204) + + Data Element Description + + Data​Element​Description + + LO + + 1 + + DICONDE +
+ (0014,0205) + + Data Element Conditionality + + Data​Element​Conditionality + + CS + + 1 + + DICONDE +
+ (0014,0206) + + Data Element Minimum Characters + + Data​Element​Minimum​Characters + + IS + + 1 + + DICONDE +
+ (0014,0207) + + Data Element Maximum Characters + + Data​Element​Maximum​Characters + + IS + + 1 + + DICONDE +
(0014,1010) @@ -17272,6 +18352,26 @@
+ (0018,1203) + + Calibration DateTime + + Calibration​Date​Time + + DT + + 1 + + +
(0018,1210) @@ -31510,6 +32610,26 @@
+ (0020,0027) + + Pyramid Label + + PyramidLabel + + LO + + 1 + + +
@@ -45896,6 +47016,26 @@
+ (0032,1065) + + Requested Laterality Code Sequence + + Requested​Laterality​Code​Sequence + + SQ + + 1 + + +
(0032,1066) @@ -47837,6 +48977,366 @@
+ (003A,0317) + + Waveform Amplifier Type + + Waveform​Amplifier​Type + + CS + + 1 + + +
+ (003A,0318) + + Filter Low Frequency Characteristics Sequence + + Filter​Low​Frequency​Characteristics​Sequence + + SQ + + 1 + + +
+ (003A,0319) + + Filter High Frequency Characteristics Sequence + + Filter​High​Frequency​Characteristics​Sequence + + SQ + + 1 + + +
+ (003A,0320) + + Summarized Filter Lookup Table Sequence + + Summarized​Filter​Lookup​Table + + SQ + + 1 + + +
+ (003A,0321) + + Notch Filter Characteristics Sequence + + Notch​Filter​Characteristics​Sequence + + SQ + + 1 + + +
+ (003A,0322) + + Waveform Filter Type + + Waveform​Filter​Type + + CS + + 1 + + +
+ (003A,0323) + + Analog Filter Characteristics Sequence + + Analog​Filter​Characteristics​Sequence + + SQ + + 1 + + +
+ (003A,0324) + + Analog Filter Roll Off + + Analog​Filter​Roll​Off + + DS + + 1 + + +
+ (003A,0325) + + Analog Filter Type Code Sequence + + Analog​Filter​Type + + SQ + + 1 + + +
+ (003A,0326) + + Digital Filter Characteristics Sequence + + Digital​Filter​Characteristics​Sequence + + SQ + + 1 + + +
+ (003A,0327) + + Digital Filter Order + + Digital​Filter​Order + + IS + + 1 + + +
+ (003A,0328) + + Digital Filter Type Code Sequence + + Digital​Filter​Type​Code​Sequence + + SQ + + 1 + + +
+ (003A,0329) + + Waveform Filter Description + + Waveform​Filter​Description + + ST + + 1 + + +
+ (003A,032A) + + Filter Lookup Table Sequence + + Filter​Lookup​Table​Sequence + + SQ + + 1 + + +
+ (003A,032B) + + Filter Lookup Table Description + + Filter​Lookup​Table​Description + + ST + + 1 + + +
+ (003A,032C) + + Frequency Encoding Code Sequence + + Frequency​Encoding​Code​Sequence + + SQ + + 1 + + +
+ (003A,032D) + + Magnitude Encoding Code Sequence + + Magnitude​Encoding​Code​Sequence + + SQ + + 1 + + +
+ (003A,032E) + + Filter Lookup Table Data + + Filter​Lookup​Table​Data + + OD + + 1 + + +
(0040,0001) @@ -54871,7 +56371,7 @@ Number of Table Columns - Numbe​Of​Table​Columns + Number​Of​Table​Columns UL @@ -58377,62 +59877,98 @@
- (0048,0200) + +(0048,0200) + - Referenced Image Navigation Sequence + +Referenced Image Navigation Sequence + - Referenced​Image​Navigation​Sequence + +Referenced​Image​Navigation​Sequence + - SQ + +SQ + - 1 + +1 + - RET (2021c) + +RET (2021c) +
- (0048,0201) + +(0048,0201) + - Top Left Hand Corner of Localizer Area + +Top Left Hand Corner of Localizer Area + - Top​Left​Hand​Corner​Of​Localizer​Area + +Top​Left​Hand​Corner​Of​Localizer​Area + - US + +US + - 2 + +2 + - RET (2021c) + +RET (2021c) +
- (0048,0202) + +(0048,0202) + - Bottom Right Hand Corner of Localizer Area + +Bottom Right Hand Corner of Localizer Area + - Bottom​Right​Hand​Corner​Of​Localizer​Area + +Bottom​Right​Hand​Corner​Of​Localizer​Area + - US + +US + - 2 + +2 + - RET (2021c) + +RET (2021c) +
- 1 + 1-n @@ -67036,6 +68572,26 @@
+ (0070,0315) + + Used RT Structure Set ROI Sequence + + Used​RT​Structure​Set​ROI​Sequence + + SQ + + 1 + + +
(0070,0318) @@ -77864,66 +79420,42 @@
- - (2130,00A0) - + (2130,00A0) - - Proposed Study Sequence - + Proposed Study Sequence - - Proposed​Study​Sequence - + Proposed​Study​Sequence - - SQ - + SQ - - 1 - + 1 - - RET (2004) - +
- - (2130,00C0) - + (2130,00C0) - - Original Image Sequence - + Original Image Sequence - - Original​Image​Sequence - + Original​Image​Sequence - - SQ - + SQ - - 1 - + 1 - - RET (2004) - +
- (3006,0085) + +(3006,0085) + - ROI Observation Label + +ROI Observation Label + - ROI​Observation​Label + +ROI​Observation​Label + - SH + +SH + - 1 + +1 + - + +RET (2022b) +
- (3006,0088) + +(3006,0088) + - ROI Observation Description + +ROI Observation Description + - ROI​Observation​Description + +ROI​Observation​Description + - ST + +ST + - 1 + +1 + - + +RET (2022b) +
+ (3008,00D1) + + Recorded Block Slab Sequence + + Recorded​Block​Slab​Sequence + + SQ + + 1 + + +
(3008,00E0) @@ -82472,22 +84048,34 @@
- (300A,000B) + +(300A,000B) + - Treatment Sites + +Treatment Sites + - Treatment​Sites + +Treatment​Sites + - LO + +LO + - 1-n + +1-n + - + + RET (2021e) +
- (300A,0632) + +(300A,0632) + - Referenced RT Patient Setup Sequence + +Referenced RT Patient Setup Sequence + - Referenced​RTPatient​Setup​Sequence + +Referenced​RTPatient​Setup​Sequence + - SQ + +SQ + - 1 + +1 + - RET (2021c) + +RET (2021c) +
- (300A,0650) + +(300A,0650) + - Patient Setup UID + +Patient Setup UID + - Patient​Setup​UID + +Patient​Setup​UID + - UI + +UI + - 1 + +1 + - RET (2021c) + +RET (2021c) +
- (300A,0784) + (300A,0784) - RT Patient Position Scope Sequence + RT Patient Position Scope Sequence - RT​Patient​Position​Scope​Sequence + RT​Patient​Position​Scope​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0785) + (300A,0785) - Referenced Treatment Position Group UID + Referenced Treatment Position Group UID - Referenced​Treatment​Position​Group​UID + Referenced​Treatment​Position​Group​UID - UI + UI - 1 + 1 - +
- (300A,0786) + (300A,0786) - Radiation Order Index + Radiation Order Index - Radiation​Order​Index + Radiation​Order​Index - US + US - 1 + 1 - +
- (300A,0787) + (300A,0787) - Omitted Radiation Sequence + Omitted Radiation Sequence - Omitted​Radiation​Sequence + Omitted​Radiation​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0788) + (300A,0788) - Reason for Omission Code Sequence + Reason for Omission Code Sequence - Reasonfor​Omission​Code​Sequence + Reason​For​Omission​Code​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0789) + (300A,0789) - RT Delivery Start Patient Position Sequence + RT Delivery Start Patient Position Sequence - RT​Delivery​Start​Patient​Position​Sequence + RT​Delivery​Start​Patient​Position​Sequence - SQ + SQ - 1 + 1 - +
- (300A,078A) + (300A,078A) - RT Treatment Preparation Patient Position Sequence + RT Treatment Preparation Patient Position Sequence - RT​Treatment​Preparation​Patient​Position​Sequence + RT​Treatment​Preparation​Patient​Position​Sequence - SQ + SQ - 1 + 1 - +
- (300A,078B) + (300A,078B) - Referenced RT Treatment Preparation Sequence + Referenced RT Treatment Preparation Sequence - Referenced​RT​Treatment​Preparation​Sequence + Referenced​RT​Treatment​Preparation​Sequence - SQ + SQ - 1 + 1 - +
- (300A,078C) + (300A,078C) - Referenced Patient Setup Photo Sequence + Referenced Patient Setup Photo Sequence - Referenced​Patient​Setup​Photo​Sequence + Referenced​Patient​Setup​Photo​Sequence - SQ + SQ - 1 + 1 - +
- (300A,078D) + (300A,078D) - Patient Treatment Preparation Method Code Sequence + Patient Treatment Preparation Method Code Sequence - Patient​Treatment​Preparation​Method​Code​Sequence + Patient​Treatment​Preparation​Method​Code​Sequence - SQ + SQ - 1 + 1 - +
- (300A,078E) + (300A,078E) - Patient Treatment Preparation Procedure Parameter Description + Patient Treatment Preparation Procedure Parameter Description - Patient​Treatment​Preparation​Procedure​Parameter​Description + Patient​Treatment​Preparation​Procedure​Parameter​Description - LT + LT - 1 + 1 - +
- (300A,078F) + (300A,078F) - Patient Treatment Preparation Device Sequence + Patient Treatment Preparation Device Sequence - Patient​Treatment​Preparation​Device​Sequence + Patient​Treatment​Preparation​Device​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0790) + (300A,0790) - Patient Treatment Preparation Procedure Sequence + Patient Treatment Preparation Procedure Sequence - Patient​Treatment​Preparation​Procedure​Sequence + Patient​Treatment​Preparation​Procedure​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0791) + (300A,0791) - Patient Treatment Preparation Procedure Code Sequence + Patient Treatment Preparation Procedure Code Sequence - Patient​Treatment​Preparation​Procedure​Code​Sequence + Patient​Treatment​Preparation​Procedure​Code​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0792) + (300A,0792) - Patient Treatment Preparation Method Description + Patient Treatment Preparation Method Description - Patient​Treatment​Preparation​Method​Description + Patient​Treatment​Preparation​Method​Description - LT + LT - 1 + 1 - +
- (300A,0793) + (300A,0793) - Patient Treatment Preparation Procedure Parameter Sequence + Patient Treatment Preparation Procedure Parameter Sequence - Patient​Treatment​Preparation​Procedure​Parameter​Sequence + Patient​Treatment​Preparation​Procedure​Parameter​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0794) + (300A,0794) - Patient Setup Photo Description + Patient Setup Photo Description - Patient​Setup​Photo​Description + Patient​Setup​Photo​Description - LT + LT - 1 + 1 - +
- (300A,0795) + (300A,0795) - Patient Treatment Preparation Procedure Index + Patient Treatment Preparation Procedure Index - Patient​Treatment​Preparation​Procedure​Index + Patient​Treatment​Preparation​Procedure​Index - US + US - 1 + 1 - +
- (300A,0796) + (300A,0796) - Referenced Patient Setup Procedure Index + Referenced Patient Setup Procedure Index - Referenced​Patient​Setup​Procedure​Index + Referenced​Patient​Setup​Procedure​Index - US + US - 1 + 1 - +
- (300A,0797) + (300A,0797) - RT Radiation Task Sequence + RT Radiation Task Sequence - RT​Radiation​Task​Sequence + RT​Radiation​Task​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0798) + (300A,0798) - RT Patient Position Displacement Sequence + RT Patient Position Displacement Sequence - RT​Patient​Position​Displacement​Sequence + RT​Patient​Position​Displacement​Sequence - SQ + SQ - 1 + 1 - +
- (300A,0799) + (300A,0799) - RT Patient Position Sequence + RT Patient Position Sequence - RT​Patient​Position​Sequence + RT​Patient​Position​Sequence - SQ + SQ - 1 + 1 - +
- (300A,079A) + (300A,079A) - Displacement Reference Label + Displacement Reference Label - Displacement​Reference​Label + Displacement​Reference​Label - LO + LO - 1 + 1 - +
- (300A,079B) + (300A,079B) - Displacement Matrix + Displacement Matrix - Displacement​Matrix + Displacement​Matrix - FD + FD - 16 + 16 - +
- (300A,079C) + (300A,079C) - Patient Support Displacement Sequence + Patient Support Displacement Sequence - Patient​Support​Displacement​Sequence + Patient​Support​Displacement​Sequence - SQ + SQ - 1 + 1 - +
- (300A,079D) + (300A,079D) - Displacement Reference Location Code Sequence + Displacement Reference Location Code Sequence - Displacement​Reference​Location​Code​Sequence + Displacement​Reference​Location​Code​Sequence - SQ + SQ - 1 + 1 - +
- (300A,079E) + (300A,079E) - RT Radiation Set Delivery Usage + RT Radiation Set Delivery Usage - RT​Radiation​Set​Delivery​Usage + RT​Radiation​Set​Delivery​Usage - CS + CS - 1 + 1 - +
+ (300C,0114) + + Prescription Overview Sequence + + Prescription​Overview​Sequence + + SQ + + 1 + + +
+ (300C,0115) + + Total Prescription Dose + + Total​Prescription​Dose + + FL + + 1 + + +
+ (300C,0116) + + Plan Overview Sequence + + Plan​Overview​Sequence + + SQ + + 1 + + +
+ (300C,0117) + + Plan Overview Index + + Plan​Overview​Index + + US + + 1 + + +
+ (300C,0118) + + Referenced Plan Overview Index + + Referenced​Plan​Overview​Index + + US + + 1 + + +
+ (300C,0119) + + Number of Fractions Included + + Number​Of​Fractions​Included + + US + + 1 + + +
+ (300C,0120) + + Dose Calibration Conditions Sequence + + Dose​Calibration​Conditions​Sequence + + SQ + + 1 + + +
+ (300C,0121) + + Absorbed Dose to Meterset Ratio + + Absorbed​Dose​To​Meterset​Ratio + + FD + + 1 + + +
+ (300C,0122) + + Delineated Radiation Field Size + + Delineated​Radiation​Field​Size + + FD + + 2 + + +
+ (300C,0123) + + Dose Calibration Conditions Verified Flag + + Dose​Calibration​Conditions​Verified​Flag + + CS + + 1 + + +
+ (300C,0124) + + Calibration Reference Point Depth + + Calibration​Reference​Point​Depth + + FD + + 1 + + +
+ (300C,0125) + + Gating Beam Hold Transition Sequence + + Gating​Beam​Hold​Transition​Sequence + + SQ + + 1 + + +
+ (300C,0126) + + Beam Hold Transition + + Beam​Hold​Transition + + CS + + 1 + + +
+ (300C,0127) + + Beam Hold Transition DateTime + + Beam​Hold​Transition​Date​Time + + DT + + 1 + + +
+ (300C,0128) + + Beam Hold Originating Device Sequence + + Beam​Hold​OriginatingD​evice​Sequence + + SQ + + 1 + + +
(300E,0002) @@ -98290,6 +100202,26 @@
+ (3010,00A0) + + Conceptual Volume Identification Sequence + + Conceptual​Volume​Identification​Sequence + + SQ + + 1 + + +
@@ -103170,6 +105102,26 @@
+ (7FE0,0003) + + Encapsulated Pixel Data Value Total Length + + Encapsulated​Pixel​Data​Value​Total​Length + + UV + + 1 + + +
(7FE0,0008) @@ -104731,7 +106683,7 @@ - (2011) + (2011)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- (2001) + (2001)
- 1.2.840.10008.1.2.​4.​100 - - MPEG2 Main Profile / Main Level - - MPEG2​MPML - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.​101 - - MPEG2 Main Profile / High Level - - MPEG2​MPHL - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.​102 - - MPEG-4 AVC/H.264 High Profile / Level 4.1 - - MPEG4​HP41 - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.​103 - - MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 - - MPEG4​HP41BD - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.​104 - - MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video - - MPEG4​HP422D - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.​105 - - MPEG-4 AVC/H.264 High Profile / Level 4.2 For 3D Video - - MPEG4​HP423D - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.​106 - - MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 - - MPEG4​HP42STEREO - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.107 - - HEVC/H.265 Main Profile / Level 5.1 - - HEVC​MP51 - - Transfer Syntax - - - - -
- 1.2.840.10008.1.2.​4.108 - - HEVC/H.265 Main 10 Profile / Level 5.1 - - HEVC​M10P51 - - Transfer Syntax - - - - -
+ 1.2.840.10008.1.2.​4.​100 + + MPEG2 Main Profile / Main Level + + MPEG2​MPML + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​100.1 + + Fragmentable MPEG2 Main Profile / Main Level + + MPEG2​MPMLF + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​101 + + MPEG2 Main Profile / High Level + + MPEG2​MPHL + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​101.1 + + Fragmentable MPEG2 Main Profile / High Level + + MPEG2​MPHLF + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​102 + + MPEG-4 AVC/H.264 High Profile / Level 4.1 + + MPEG4​HP41 + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​102.1 + + Fragmentable MPEG-4 AVC/H.264 High Profile / Level 4.1 + + MPEG4​HP41F + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​103 + + MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 + + MPEG4​HP41BD + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​103.1 + + Fragmentable MPEG-4 AVC/H.264 BD-compatible High Profile / Level 4.1 + + MPEG4​HP41BDF + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​104 + + MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video + + MPEG4​HP422D + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​104.1 + + Fragmentable MPEG-4 AVC/H.264 High Profile / Level 4.2 For 2D Video + + MPEG4​HP422DF + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​105 + + MPEG-4 AVC/H.264 High Profile / Level 4.2 For 3D Video + + MPEG4​HP423D + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​105.1 + + Fragmentable MPEG-4 AVC/H.264 High Profile / Level 4.2 For 3D Video + + MPEG4​HP423DF + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​106 + + MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 + + MPEG4​HP42STEREO + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.​106.1 + + Fragmentable MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 + + MPEG4​HP42STEREOF + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.107 + + HEVC/H.265 Main Profile / Level 5.1 + + HEVC​MP51 + + Transfer Syntax + + + + +
+ 1.2.840.10008.1.2.​4.108 + + HEVC/H.265 Main 10 Profile / Level 5.1 + + HEVC​M10P51 + + Transfer Syntax + + + + +
1.2.840.10008.1.​2.​5 @@ -105569,7 +107654,7 @@ - (2018b) + (2018b)
- (2018b) + (2018b)
- (2004) + (2004)
- (2001) + (2001)
- (2001) + (2001)
+ 1.2.840.10008.2.​16.​17 + + Unified numbering system (UNS) for metals and alloys + + UNS + + Coding Scheme + + + + +
+ 1.2.840.10008.2.​16.​18 + + Research Resource Identification + + RRID + + Coding Scheme + + + + +
1.2.840.10008.3.1.​1.​1 @@ -106352,7 +108475,7 @@ -Detached​Patient​Management +Detached​Patient​Management @@ -106363,7 +108486,7 @@ - (2004) + (2004)
- (2004) + (2004)
- (2004) + (2004)
-Detached​Study​Management +Detached​Study​Management @@ -106447,7 +108570,7 @@ - (2004) + (2004)
-Study​Component​Management +Study​Component​Management @@ -106475,7 +108598,7 @@ - (2004) + (2004)
- (2004) + (2004)
- (2004) + (2004)
- (2004) + (2004)
- (2004) + (2004)
- (1998) + (1998)
- (1998) + (1998)
- Well-known Printer SOP Instance + Well-known SOP Instance @@ -106924,7 +109047,7 @@ Printer​Configuration​Retrieval​Instance - Well-known Printer SOP Instance + Well-known SOP Instance @@ -106975,7 +109098,7 @@ - (1998) + (1998)
- (1998) + (1998)
- (2004) + (2004)
-Print​Queue + Print​Queue​Instance - Well-known Print Queue SOP Instance + Well-known SOP Instance - (2004) + (2004)
-Print​Queue​Management +Print​Queue​Management @@ -107125,7 +109248,7 @@ - (2004) + (2004)
- (2004) + (2004)
- (2004) + (2004)
-Hardcopy​Color​Image​Storage +Hardcopy​Color​Image​Storage @@ -107209,7 +109332,7 @@ - (2004) + (2004)
-Pull​Print​Request +Pull​Print​Request @@ -107237,7 +109360,7 @@ - (2004) + (2004)
-Pull​Stored​Print​Management​Meta +Pull​Stored​Print​Management​Meta @@ -107265,7 +109388,7 @@ - (2004) + (2004)
- (1993) + (1993)
- (1993) + (1993)
- (1993) + (1993)
- (2004) + (2004)
- (2004) + (2004)
- (2007) + (2007)
- (2004) + (2004)
- (2004) + (2004)
- (1998) + (1998)
-VL​Image​Storage​Trial +VL​Image​Storage​Trial @@ -109027,7 +111150,7 @@ - (1998) + (1998)
- (1998) + (1998)
- (2007) + (2007)
-Audio​SR​Storage​Trial +Audio​SR​Storage​Trial @@ -109662,7 +111785,7 @@ - (2007) + (2007)
-Detail​SR​Storage​Trial +Detail​SR​Storage​Trial @@ -109690,7 +111813,7 @@ - (2007) + (2007)
- (2007) + (2007)
- (2004) + (2004)
+ 1.2.840.10008.5.1.4.1.1.201.1 + + Inventory Storage + + Inventory​Storage + + SOP Class + + + + +
+ 1.2.840.10008.5.1.4.1.1.201.2 + + Inventory - FIND + + Inventory​Find + + SOP Class + + + + +
+ 1.2.840.10008.5.1.4.1.1.201.3 + + Inventory - MOVE + + Inventory​Move + + SOP Class + + + + +
+ 1.2.840.10008.5.1.4.1.1.201.4 + + Inventory - GET + + Inventory​Get + + SOP Class + + + + +
+ 1.2.840.10008.5.1.4.1.1.201.5 + + Inventory Creation + + Inventory​Creation + + SOP Class + + + + +
+ 1.2.840.10008.5.1.4.1.1.201.6 + + Repository Query + + Repository​Query + + SOP Class + + + + +
+ 1.2.840.10008.5.1.4.1.1.201.1.1 + + Storage Management SOP Instance + + Storage​Management​Instance + + Well-known SOP Instance + + + + +
1.2.840.10008.​5.​1.​4.​1.​1.​481.​1 @@ -110854,38 +113110,38 @@
- 1.2.840.10008.​5.​1.​4.​1.​1.​481.​21 + 1.2.840.10008.​5.​1.​4.​1.​1.​481.​21 - RT Radiation Set Delivery Instruction Storage + RT Radiation Set Delivery Instruction Storage - RT​Radiation​Set​Delivery​Instruction​Storage + RT​Radiation​Set​Delivery​Instruction​Storage - SOP Class + SOP Class - +
- 1.2.840.10008.​5.​1.​4.​1.​1.​481.​22 + 1.2.840.10008.​5.​1.​4.​1.​1.​481.​22 - RT Treatment Preparation Storage + RT Treatment Preparation Storage - RT​Treatment​Preparation​Storage + RT​Treatment​Preparation​Storage - SOP Class + SOP Class - + - (2004) + (2004)
- (2004) + (2004)
- (2004) + (2004)
- (2011) + (2011)
- (2011) + (2011)
- (2011) + (2011)
- (2011) + (2011)
- (2009) + (2009)
- (2009) + (2009)
- (2009) + (2009)
-Unified​Worklist​And​Procedure​Step​Trial +Unified​Worklist​And​Procedure​Step​Trial @@ -111613,7 +113869,7 @@ - (2009) + (2009)
-Unified​Procedure​Step​Push​Trial +Unified​Procedure​Step​Push​Trial @@ -111641,7 +113897,7 @@ - (2009) + (2009)
- (2009) + (2009)
- (2009) + (2009)
- (2009) + (2009)
+ 1.2.840.10008.1.4.3.3 + + IEC 61217 Table Top Coordinate System Frame of Reference + + IEC​61217​Table​Top​Coordinate​System + + Table top coordinate system ("t") of . +
1.2.840.10008.1.4.4.1 @@ -128104,7 +130374,9 @@
- 1.2.840.10008.6.​1.​888 + +1.2.840.10008.6.​1.​888 + @@ -128113,7 +130385,9 @@ - + +Retired +
- 1.2.840.10008.6.​1.​945 + +1.2.840.10008.6.​1.​945 + @@ -129099,12 +131375,16 @@ - + +Retired +
- 1.2.840.10008.6.​1.​946 + +1.2.840.10008.6.​1.​946 + @@ -129113,7 +131393,9 @@ - + +Retired +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- +
- 1.2.840.10008.6.​1.​1411 + 1.2.840.10008.6.​1.​1411 - + - + - +
- 1.2.840.10008.6.​1.​1412 + 1.2.840.10008.6.​1.​1412 - + - + - +
- 1.2.840.10008.6.​1.​1413 + 1.2.840.10008.6.​1.​1413 - + - + - +
- 1.2.840.10008.6.​1.​1414 + 1.2.840.10008.6.​1.​1414 - + - + - +
- 1.2.840.10008.6.​1.​1415 + 1.2.840.10008.6.​1.​1415 - + - + - +
- 1.2.840.10008.6.​1.​1416 + 1.2.840.10008.6.​1.​1416 - + - + - +
- 1.2.840.10008.6.​1.​1417 + 1.2.840.10008.6.​1.​1417 - + - + - +
- 1.2.840.10008.6.1.1418 + 1.2.840.10008.6.1.1418 - + - + - +
- 1.2.840.10008.6.1.1419 + 1.2.840.10008.6.1.1419 - + - + - +
- 1.2.840.10008.6.1.1420 + 1.2.840.10008.6.1.1420 - + - + - +
- 1.2.840.10008.6.1.1421 + 1.2.840.10008.6.1.1421 - + - + - +
- 1.2.840.10008.6.1.1422 + 1.2.840.10008.6.1.1422 - + - + - +
- 1.2.840.10008.6.1.1423 + 1.2.840.10008.6.1.1423 - + - + - +
- 1.2.840.10008.6.1.1424 + 1.2.840.10008.6.1.1424 - + - + - +
- 1.2.840.10008.6.1.1425 + 1.2.840.10008.6.1.1425 - + - + - + +
+ 1.2.840.10008.6.1.1426 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1427 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1428 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1429 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1430 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1431 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1432 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1433 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1434 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1435 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1436 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1437 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1438 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1439 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1440 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1441 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1442 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1443 + + + + + + + + + + +
+ 1.2.840.10008.6.1.1444 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1445 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1446 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1447 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1448 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1449 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1450 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1451 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1452 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1453 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1454 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1455 + + + + + + + + + + +
+ 1.2.840.10008.6.​1.1456 + + + + + + + + + +
diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/build.gradle.kts b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/build.gradle.kts new file mode 100644 index 0000000..d216430 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/build.gradle.kts @@ -0,0 +1,49 @@ +plugins { + `java-library` + id("org.dcm4che.typeddicom-publisher") +} + +typeddicomPublisher { + pomName.set("dcm4che-typeddicom-java-generator-lib") + pomDescription.set("This library provides classes and methods to generate java code from a typeddicom yaml file. " + + "It is used in the dcm4che-typeddicom-java-generator-gradleplugin but could also be used on its own."); +} + +repositories { + mavenCentral() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } +} + +dependencies { + implementation("org.dcm4che:dcm4che-typeddicom-parser-dtos:$version") + + implementation("com.github.spullara.mustache.java:compiler:0.9.10") + + implementation("org.apache.commons:commons-text:1.9") + implementation("com.github.davidmoten:word-wrap:0.1.9") + + implementation("org.apache.commons:commons-lang3:3.12.0") + + implementation("org.dcm4che:dcm4che-core:5.29.0") + + implementation("org.jsoup:jsoup:1.14.3") + + implementation("com.fasterxml.jackson.core:jackson-core:2.14.2") + implementation("com.fasterxml.jackson.core:jackson-databind:2.14.2") + implementation("com.fasterxml.jackson.core:jackson-annotations:2.14.2") + implementation("com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.14.2") + + testImplementation("org.junit.jupiter:junit-jupiter-api:5.7.0") + testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.7.0") +} + +java { + sourceCompatibility = JavaVersion.VERSION_11 + targetCompatibility = JavaVersion.VERSION_11 +} + +tasks.test { + useJUnitPlatform() +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/JavaGenerator.java b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/JavaGenerator.java new file mode 100644 index 0000000..e8f44de --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/JavaGenerator.java @@ -0,0 +1,188 @@ +package org.dcm4che.typeddicom.generator; + +import com.fasterxml.jackson.databind.ObjectReader; +import com.fasterxml.jackson.databind.exc.MismatchedInputException; +import com.fasterxml.jackson.dataformat.yaml.YAMLFactory; +import com.fasterxml.jackson.dataformat.yaml.YAMLMapper; +import com.github.mustachejava.DefaultMustacheFactory; +import com.github.mustachejava.Mustache; +import com.github.mustachejava.MustacheNotFoundException; +import com.github.mustachejava.MustacheResolver; +import com.github.mustachejava.reflect.ReflectionObjectHandler; +import org.dcm4che.typeddicom.generator.model.mustache.DataElementMustacheModel; +import org.dcm4che.typeddicom.generator.model.mustache.InformationObjectDefinitionMustacheModel; +import org.dcm4che.typeddicom.parser.metamodel.dto.*; +import org.slf4j.Logger; +import org.slf4j.LoggerFactory; +import org.yaml.snakeyaml.LoaderOptions; + +import java.io.*; +import java.nio.charset.StandardCharsets; +import java.util.List; +import java.util.Map; + +public class JavaGenerator { + public static final String JAVA_FILE_EXTENSION = ".java"; + private static final Logger LOGGER = LoggerFactory.getLogger(JavaGenerator.class); + public static final int MAX_YAML_FILE_SIZE = 15<<20; // 15 MiB + + private final DefaultMustacheFactory mustacheFactory; + private final String stdMetaModelYamlFileResourcePath; + private final List privateMetamodelYamlFiles; + private final File javaOutputDirectory; + private final YAMLMapper yamlMapper; + + public JavaGenerator(String stdMetaModelYamlFileResourcePath, List privateMetamodelYamlFiles, File javaOutputDirectory) { + this.stdMetaModelYamlFileResourcePath = stdMetaModelYamlFileResourcePath; + this.privateMetamodelYamlFiles = privateMetamodelYamlFiles; + this.javaOutputDirectory = javaOutputDirectory; + MustacheResolver mustacheResolver = resourceName -> getInputStreamReaderForTemplate(resourceName); + mustacheFactory = new DefaultMustacheFactory(mustacheResolver); + mustacheFactory.setObjectHandler(new MapMethodReflectionHandler()); + + LoaderOptions loaderOptions = new LoaderOptions(); + loaderOptions.setCodePointLimit(MAX_YAML_FILE_SIZE); + yamlMapper = new YAMLMapper(YAMLFactory.builder().loaderOptions(loaderOptions).build()); + } + + private InputStreamReader getInputStreamReaderForTemplate(String resourceName) { + InputStream mustacheFile = this.getClass().getClassLoader().getResourceAsStream("templates" + "/" + resourceName + ".java.mustache"); + if (mustacheFile == null) { + throw new MustacheNotFoundException(resourceName); + } else { + return new InputStreamReader(mustacheFile); + } + } + + public void generateSources() { + try { + DicomMetaModelDTO dicomMetaModelDTO = loadYamlFiles(privateMetamodelYamlFiles); + generateJavaSources(dicomMetaModelDTO); + } catch (IOException e) { + throw new RuntimeException("Wasn't able to generate the Sources", e); + } + } + + private DicomMetaModelDTO loadYamlFiles(List privateMetamodelYamlFiles) throws IOException { + DicomMetaModelDTO dicomMetaModelDTO = loadStdMetaModel(); + updateWithPrivateMetaModelYamlFiles(dicomMetaModelDTO, privateMetamodelYamlFiles); + return dicomMetaModelDTO; + } + + private DicomMetaModelDTO loadStdMetaModel() throws IOException { + DicomMetaModelDTO dicomMetaModelDTO; + try (InputStream stdMetaModelYamlInputStream = this.getClass().getClassLoader().getResourceAsStream(stdMetaModelYamlFileResourcePath)) { + dicomMetaModelDTO = this.yamlMapper.readValue(stdMetaModelYamlInputStream, DicomMetaModelDTO.class); + } + return dicomMetaModelDTO; + } + + private void updateWithPrivateMetaModelYamlFiles(DicomMetaModelDTO dicomMetaModelDTO, List privateMetamodelYamlFiles) throws IOException { + ObjectReader updateReader = this.yamlMapper.readerForUpdating(dicomMetaModelDTO); + for (File metamodelYamlFile : privateMetamodelYamlFiles) { + try { + updateReader.readValue(metamodelYamlFile); + } catch (MismatchedInputException e) { + LOGGER.warn("Invalid yaml file {}", metamodelYamlFile.getPath()); + } + } + } + + private void generateJavaSources(DicomMetaModelDTO dicomMetaModelDTO) throws IOException { + generateValueRepresentationSingleInterfaces(dicomMetaModelDTO.getValueRepresentations()); + generateValueRepresentationMultiInterfaces(dicomMetaModelDTO.getValueRepresentations()); + LOGGER.info("Generated {} Value Representation interfaces", dicomMetaModelDTO.getValueRepresentations().size() * 2); + + generateDataElementWrapperClasses(dicomMetaModelDTO.getDataElements()); + LOGGER.info("Generated {} Data Element classes", dicomMetaModelDTO.getDataElements().size()); + + generateModuleInterfaces(dicomMetaModelDTO.getModules()); + LOGGER.info("Generated {} Module interfaces", dicomMetaModelDTO.getModules().size()); + + generateIODClasses(dicomMetaModelDTO.getIods()); + LOGGER.info("Generated {} IOD classes", dicomMetaModelDTO.getIods().size()); + } + + private void generateValueRepresentationSingleInterfaces(Map valueRepresentations) throws IOException { + Mustache mustache = mustacheFactory.compile("ValueRepresentationSingle"); + File valueRepresentationDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/valuerepresentations"); + //noinspection ResultOfMethodCallIgnored + valueRepresentationDir.mkdirs(); + for (Map.Entry valueRepresentationEntry : valueRepresentations.entrySet()) { + String filename = valueRepresentationEntry.getKey() + "Wrapper" + JAVA_FILE_EXTENSION; + File javaFile = new File(valueRepresentationDir, filename); + try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { + mustache.execute(javaFileWriter, valueRepresentationEntry); + } + } + } + + private void generateValueRepresentationMultiInterfaces(Map valueRepresentations) throws IOException { + Mustache mustache = mustacheFactory.compile("ValueRepresentationMulti"); + File valueRepresentationDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/valuerepresentations"); + //noinspection ResultOfMethodCallIgnored + valueRepresentationDir.mkdirs(); + for (Map.Entry valueRepresentationEntry : valueRepresentations.entrySet()) { + String filename = valueRepresentationEntry.getKey() + "MultiWrapper" + JAVA_FILE_EXTENSION; + File javaFile = new File(valueRepresentationDir, filename); + try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { + mustache.execute(javaFileWriter, valueRepresentationEntry); + } + } + } + + private void generateDataElementWrapperClasses(Map dataElements) throws IOException { + Mustache mustache = mustacheFactory.compile("DataElement"); + File dataElementDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/dataelements"); + //noinspection ResultOfMethodCallIgnored + dataElementDir.mkdirs(); + for (Map.Entry dataElementMetaInfoEntry : dataElements.entrySet()) { + String filename = dataElementMetaInfoEntry.getKey() + JAVA_FILE_EXTENSION; + File javaFile = new File(dataElementDir, filename); + try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { + mustache.execute(javaFileWriter, new DataElementMustacheModel(dataElementMetaInfoEntry.getKey(), dataElementMetaInfoEntry.getValue())); + } + } + } + + private void generateIODClasses(Map iods) throws IOException { + Mustache mustache = mustacheFactory.compile("InformationObjectDefinition"); + File dataElementDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/iods"); + //noinspection ResultOfMethodCallIgnored + dataElementDir.mkdirs(); + for (Map.Entry iodEntry : iods.entrySet()) { + String filename = iodEntry.getKey() + JAVA_FILE_EXTENSION; + File javaFile = new File(dataElementDir, filename); + try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { + mustache.execute(javaFileWriter, new InformationObjectDefinitionMustacheModel(iodEntry.getKey(), iodEntry.getValue())); + } + } + } + + private void generateModuleInterfaces(Map moduleMetaInfoSet) throws IOException { + Mustache mustache = mustacheFactory.compile("Module"); + File dataElementDir = new File(javaOutputDirectory, "org/dcm4che/typeddicom/modules"); + //noinspection ResultOfMethodCallIgnored + dataElementDir.mkdirs(); + for (Map.Entry moduleMetaInfo : moduleMetaInfoSet.entrySet()) { + String filename = moduleMetaInfo.getKey() + JAVA_FILE_EXTENSION; + File javaFile = new File(dataElementDir, filename); + try (FileWriter javaFileWriter = new FileWriter(javaFile, StandardCharsets.UTF_8)) { + mustache.execute(javaFileWriter, moduleMetaInfo); + } + } + } + + /** + * Extended reflection handler that can access map methods. + */ + private static class MapMethodReflectionHandler extends ReflectionObjectHandler { + + @Override + protected boolean areMethodsAccessible(Map map) { + return true; + } + } + + +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/model/mustache/DataElementMustacheModel.java b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/model/mustache/DataElementMustacheModel.java new file mode 100644 index 0000000..bec4cae --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/model/mustache/DataElementMustacheModel.java @@ -0,0 +1,280 @@ +package org.dcm4che.typeddicom.generator.model.mustache; + + +import com.fasterxml.jackson.annotation.JsonIgnore; +import org.davidmoten.text.utils.WordWrap; +import org.dcm4che.typeddicom.parser.metamodel.dto.AdditionalAttributeInfoContextsDTO; +import org.dcm4che.typeddicom.parser.metamodel.dto.AdditionalAttributeInfoDTO; +import org.dcm4che.typeddicom.parser.metamodel.dto.DataElementMetaInfoDTO; +import org.jsoup.Jsoup; +import org.jsoup.nodes.Document; +import org.jsoup.nodes.Element; + +import java.util.List; +import java.util.Objects; +import java.util.stream.Collectors; + +public final class DataElementMustacheModel { + private static final String LINE_BREAK = "
"; + private static final String JAVA_DOC_NEWLINE = "\n * "; + private static final int MAX_LINE_LENGTH = 120; + public static final String ZERO_WIDTH_CHARACTERS_REGEX = "[\n\r]"; + private final String keyword; + private final String name; + private final String privateCreatorConstant; + private final String tag; + private final String tagConstant; + private final String valueRepresentation; + private final String valueMultiplicity; + private final String comment; + private final boolean retired; + private final String retiredSince; + private final List additionalAttributeInfo; + private final List contains; + + public DataElementMustacheModel( + String keyword, + String name, + String privateCreatorConstant, + String tag, + String tagConstant, + String valueRepresentation, + String valueMultiplicity, + String comment, + boolean retired, + String retiredSince, + List additionalAttributeInfo, + List contains + ) { + this.keyword = keyword; + this.name = name; + this.privateCreatorConstant = privateCreatorConstant; + this.tag = tag; + this.tagConstant = tagConstant; + this.valueRepresentation = valueRepresentation; + this.valueMultiplicity = valueMultiplicity; + this.comment = comment; + this.retired = retired; + this.retiredSince = retiredSince; + this.additionalAttributeInfo = additionalAttributeInfo; + this.contains = contains; + } + + public DataElementMustacheModel(String keyword, DataElementMetaInfoDTO dto) { + this( + keyword, + dto.getName(), + dto.getPrivateCreatorConstant(), + dto.getTag(), + dto.getTagConstant(), + dto.getValueRepresentation(), + dto.getValueMultiplicity(), + dto.getComment(), + dto.getRetired(), + dto.getRetiredSince(), + dto.getAdditionalAttributeInfo(), + dto.getContains() + ); + } + + @JsonIgnore + public boolean isSequence() { + return valueRepresentation.equals("Sequence"); + } + + @JsonIgnore + public String getValueRepresentationWrapper() { + if (valueMultiplicity().equals("1")) { + return valueRepresentation + "Wrapper"; + } else { + return valueRepresentation + "MultiWrapper"; + } + } + + @JsonIgnore + public String implementsBuilderInterfaces() { + return contains.stream() + .map(key -> key + ".Builder") + .collect(Collectors.joining(", ")); + } + + @JsonIgnore + public String implementsHolderInterfaces() { + return contains.stream().map(key -> key + ".Holder").collect(Collectors.joining(", ")); + } + + @JsonIgnore + public String classJavaDoc() { + StringBuilder htmlBuilder = new StringBuilder(); + appendGeneralInfo(htmlBuilder); + appendContextInfo(htmlBuilder); + Document jsoupDoc = Jsoup.parse(htmlBuilder.toString()); + Document.OutputSettings outputSettings = new Document.OutputSettings(); + outputSettings.prettyPrint(true); + jsoupDoc.select("br").after("\\n"); + jsoupDoc.select("p").before("\\n"); + jsoupDoc.outputSettings(outputSettings); + Element body = jsoupDoc.body(); + sanitizeJDocHtml(body); + String htmlString = body.html(); + htmlString = htmlString.replace("\\n", "\n"); + htmlString = htmlString.replace("\n
", "
\n"); + htmlString = htmlString.replaceAll("

(?!\\n)", "

\n"); + if (retired) { + htmlString += "\n\n@deprecated "; + htmlString += comment; + } + return javaDocify(htmlString, 0); + } + + private void appendGeneralInfo(StringBuilder html) { + html.append("Name: ").append(name).append(LINE_BREAK); + html.append("Keyword: ").append(keyword).append(LINE_BREAK); + html.append("Tag: ").append(tag).append(LINE_BREAK); + html.append("Value Representation: ").append(valueRepresentation).append(LINE_BREAK); + html.append("Value Multiplicity: ").append(valueMultiplicity).append(LINE_BREAK); + if (comment != null && comment.length() > 0) { + html.append("Comment: ").append(comment).append(LINE_BREAK); + } + } + + private void appendContextInfo(StringBuilder html) { + if (!additionalAttributeInfo.isEmpty()) { + html.append("
    "); + for (AdditionalAttributeInfoContextsDTO additionalAttributeInfoSetEntry : additionalAttributeInfo) { + html.append("
  • Described in the contexts:
      "); + html.append(additionalAttributeInfoSetEntry.getContextsHTML()); + html.append("
    as follows:").append(LINE_BREAK); + AdditionalAttributeInfoDTO additionalAttributeInfo = additionalAttributeInfoSetEntry.getAdditionalAttributeInfoDTO(); + html.append("Attribute Name: ").append(additionalAttributeInfo.getName()).append(LINE_BREAK); + html.append("Type: ").append(additionalAttributeInfo.getType()).append(LINE_BREAK); + html.append("Attribute Description: ") + .append(additionalAttributeInfo.getAttributeDescription()).append(LINE_BREAK); + html.append("
    • "); + } + html.append("
"); + } + } + + private void sanitizeJDocHtml(Element body) { + for (Element element : body.select("dl > p")) { + assert element.parent() != null; // should always have a parent + element.parent().before(element); + } + for (Element element : body.select("p:empty")) { + element.remove(); + } + for (Element element : body.select("dd:empty, dd:matchesOwn((?is))")) { + element.remove(); + } + } + + private String javaDocify(String html, int indentationLevel) { + String jdoc = WordWrap.from(html) + .maxWidth(MAX_LINE_LENGTH + - JAVA_DOC_NEWLINE.replaceAll(ZERO_WIDTH_CHARACTERS_REGEX, "").length() + - indentationLevel) + .extraWordChars("0123456789-._~:/?#[]@!$&'()*+,;%=\"<>") + .newLine(JAVA_DOC_NEWLINE) + .breakWords(false) + .wrap(); + jdoc = "/**\n * " + jdoc + "\n */"; + jdoc = indent(jdoc, indentationLevel); + return jdoc; + } + + private String indent(String text, int indentationLevel) { + String indent = " ".repeat(indentationLevel * 4); + return indent + text.replace("\n", "\n" + indent); + } + + public String keyword() { + return keyword; + } + + public String name() { + return name; + } + + public String privateCreatorConstant() { + return privateCreatorConstant == null || privateCreatorConstant.isBlank() ? "null" : privateCreatorConstant; + } + + public String tag() { + return tag; + } + + public String tagConstant() { + return tagConstant; + } + + public String valueRepresentation() { + return valueRepresentation; + } + + public String valueMultiplicity() { + return valueMultiplicity; + } + + public String comment() { + return comment; + } + + public boolean retired() { + return retired; + } + + public String retiredSince() { + return retiredSince; + } + + public List additionalAttributeInfo() { + return additionalAttributeInfo; + } + + public List contains() { + return contains; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (DataElementMustacheModel) obj; + return Objects.equals(this.keyword, that.keyword) && + Objects.equals(this.name, that.name) && + Objects.equals(this.privateCreatorConstant, that.privateCreatorConstant) && + Objects.equals(this.tag, that.tag) && + Objects.equals(this.tagConstant, that.tagConstant) && + Objects.equals(this.valueRepresentation, that.valueRepresentation) && + Objects.equals(this.valueMultiplicity, that.valueMultiplicity) && + Objects.equals(this.comment, that.comment) && + this.retired == that.retired && + Objects.equals(this.retiredSince, that.retiredSince) && + Objects.equals(this.additionalAttributeInfo, that.additionalAttributeInfo) && + Objects.equals(this.contains, that.contains); + } + + @Override + public int hashCode() { + return Objects.hash(keyword, name, privateCreatorConstant, tag, tagConstant, valueRepresentation, valueMultiplicity, comment, retired, retiredSince, additionalAttributeInfo, contains); + } + + @Override + public String toString() { + return "DataElementMustacheModel[" + + "keyword=" + keyword + ", " + + "name=" + name + ", " + + "privateCreatorConstant=" + privateCreatorConstant + ", " + + "tag=" + tag + ", " + + "tagConstant=" + tagConstant + ", " + + "valueRepresentation=" + valueRepresentation + ", " + + "valueMultiplicity=" + valueMultiplicity + ", " + + "comment=" + comment + ", " + + "retired=" + retired + ", " + + "retiredSince=" + retiredSince + ", " + + "additionalAttributeInfo=" + additionalAttributeInfo + ", " + + "contains=" + contains + ']'; + } + +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/model/mustache/InformationObjectDefinitionMustacheModel.java b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/model/mustache/InformationObjectDefinitionMustacheModel.java new file mode 100644 index 0000000..c8a4934 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/java/org/dcm4che/typeddicom/generator/model/mustache/InformationObjectDefinitionMustacheModel.java @@ -0,0 +1,102 @@ +package org.dcm4che.typeddicom.generator.model.mustache; + +import org.dcm4che.typeddicom.parser.metamodel.dto.InformationObjectDefinitionMetaInfoDTO; +import org.dcm4che.typeddicom.parser.metamodel.dto.SOPClassDTO; + +import java.util.List; +import java.util.Objects; +import java.util.stream.Collectors; + +public final class InformationObjectDefinitionMustacheModel { + private final String keyword; + private final String name; + private final String href; + private final String sectionId; + private final List sopClasses; + private final List modules; + + public InformationObjectDefinitionMustacheModel( + String keyword, + String name, + String href, + String sectionId, + List sopClasses, + List modules + ) { + this.keyword = keyword; + this.name = name; + this.href = href; + this.sectionId = sectionId; + this.sopClasses = sopClasses; + this.modules = modules; + } + + public InformationObjectDefinitionMustacheModel(String key, InformationObjectDefinitionMetaInfoDTO dto) { + this(key, dto.getName(), dto.getHref(), dto.getSectionId(), dto.getSopClasses(), dto.getModules()); + } + + public String getImplementsModules() { + return String.join(", ", modules); + } + + public String getImplementsModuleBuilders() { + return modules.stream() + .map(module -> module + ".Builder") + .collect(Collectors.joining(", ")); + } + + public String keyword() { + return keyword; + } + + public String name() { + return name; + } + + public String href() { + return href; + } + + public String sectionId() { + return sectionId; + } + + public List sopClasses() { + return sopClasses; + } + + public List modules() { + return modules; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (InformationObjectDefinitionMustacheModel) obj; + return Objects.equals(this.keyword, that.keyword) && + Objects.equals(this.name, that.name) && + Objects.equals(this.href, that.href) && + Objects.equals(this.sectionId, that.sectionId) && + Objects.equals(this.sopClasses, that.sopClasses) && + Objects.equals(this.modules, that.modules); + } + + @Override + public int hashCode() { + return Objects.hash(keyword, name, href, sectionId, sopClasses, modules); + } + + @Override + public String toString() { + return "InformationObjectDefinitionMustacheModel[" + + "keyword=" + keyword + ", " + + "name=" + name + ", " + + "href=" + href + ", " + + "sectionId=" + sectionId + ", " + + "sopClasses=" + sopClasses + ", " + + "modules=" + modules + ']'; + } + + +} diff --git a/dcm4che-typeddicom-lib/src/main/resources/templates/AdditionalAttributeInfoInContext.java.mustache b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/AdditionalAttributeInfoInContext.java.mustache similarity index 61% rename from dcm4che-typeddicom-lib/src/main/resources/templates/AdditionalAttributeInfoInContext.java.mustache rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/AdditionalAttributeInfoInContext.java.mustache index bd7841a..fd89128 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/templates/AdditionalAttributeInfoInContext.java.mustache +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/AdditionalAttributeInfoInContext.java.mustache @@ -7,11 +7,11 @@ *
  • {{{contextHTML}}}
    • {{/value}} * - * as follows:
    - * Attribute Name: {{key.name}}
    - * Type: {{key.type}}
    - * Attribute Description: {{{key.attributeDescription}}}
    + * as follows:
    + * Attribute Name: {{key.name}}
    + * Type: {{key.type}}
    + * Attribute Description: {{{key.attributeDescription}}}
    * {{/entrySet}} * -{{/entrySet.empty}} \ No newline at end of file +{{/entrySet.empty}} diff --git a/dcm4che-typeddicom-lib/src/main/resources/templates/DataElement.java.mustache b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/DataElement.java.mustache similarity index 87% rename from dcm4che-typeddicom-lib/src/main/resources/templates/DataElement.java.mustache rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/DataElement.java.mustache index f716723..a8be8bf 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/templates/DataElement.java.mustache +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/DataElement.java.mustache @@ -29,7 +29,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key * The Private Creator * associated with this class. */ - public static final String PRIVATE_CREATOR = null; + public static final String PRIVATE_CREATOR = {{privateCreatorConstant}}; /** * The DICOM Tag * associated with this class. @@ -40,7 +40,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key /** * Creates a new {{name}} object which wraps the provided attributes. * - * @param attributes The {@link Attributes} object to be wrapped. + * @param attributes the {@link Attributes} object to be wrapped. */ public {{keyword}}(Attributes attributes) { super(attributes); @@ -56,7 +56,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key /** * Returns a new {{name}} which wraps a copy of the Attributes wrapped in this {{name}}. (see {@link Attributes#Attributes(Attributes)} * - * @return a new {{name}} which wraps a copy of the Attributes wrapped in this {{name}}. + * @return a new {{name}} which wraps a copy of the Attributes wrapped in this {{name}}. */ public {{keyword}} copy() { return super.copy({{keyword}}.class); @@ -68,7 +68,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key /** * Creates a new {{name}} object which wraps the provided sequence. * - * @param sequence The {@link Sequence} object to be linked. + * @param sequence the {@link Sequence} object to be linked. */ public {{keyword}}(Sequence sequence) { super(sequence, {{keyword}}.Item.class); @@ -86,7 +86,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key } {{#sequence}} - public static class Item extends AbstractSequenceItemWrapper {{^subDataElementMetaInfos.isEmpty}}implements {{{implementsHolderInterfaces}}} {{/subDataElementMetaInfos.isEmpty}}{ + public static class Item extends AbstractSequenceItemWrapper {{^contains.isEmpty}}implements {{{implementsHolderInterfaces}}} {{/contains.isEmpty}}{ /** * @return a {@link Builder} to create {{name}} Items with a fluent API. */ @@ -95,7 +95,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key } /** - * @param attributes The Attributes to be wrapped by the {@link Builder}. + * @param attributes the Attributes to be wrapped by the {@link Builder}. * * @return a {@link Builder} to create {{name}} Items with a fluent API. Instead of creating new Attributes it wraps the provided Attributes. */ @@ -106,7 +106,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key /** * Creates a new {{name}} Item object which wraps the provided attributes. * - * @param attributes The {@link Attributes} object to be wrapped. + * @param attributes the {@link Attributes} object to be wrapped. */ public Item(Attributes attributes) { super(attributes); @@ -122,13 +122,13 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key /** * Returns a new {{name}} Item which wraps a copy of the Attributes wrapped in this {{name}}. (see {@link Attributes#Attributes(Attributes)} * - * @return a new {{name}} Item which wraps a copy of the Attributes wrapped in this {{name}}. + * @return a new {{name}} Item which wraps a copy of the Attributes wrapped in this {{name}}. */ public Item copy() { return super.copy(Item.class); } - public static class Builder extends AbstractAttributesWrapper implements org.dcm4che.typeddicom.Builder{{^subDataElementMetaInfos.isEmpty}}, {{{implementsBuilderInterfaces}}} {{/subDataElementMetaInfos.isEmpty}}{ + public static class Builder extends AbstractAttributesWrapper implements org.dcm4che.typeddicom.Builder{{^contains.isEmpty}}, {{{implementsBuilderInterfaces}}} {{/contains.isEmpty}}{ private Builder() { super(); } @@ -150,8 +150,8 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key */ public interface Holder extends AttributesWrapper { /** - * @param attributes An attributes object containing the {{name}} (see {@link {{keyword}}}) - * @return A wrapper object implementing the {@link Holder} interface. + * @param attributes an attributes object containing the {{name}} (see {@link {{keyword}}}) + * @return a wrapper object implementing the {@link Holder} interface. */ static Holder wrap(Attributes attributes) { return AttributesWrapper.wrap(attributes, SimpleHolder.class); @@ -165,7 +165,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key } /** - * @param attributes The Attributes to be wrapped by the {@link Builder}. + * @param attributes the Attributes to be wrapped by the {@link Builder}. * * @return a {@link Builder} to create {{name}} Items with a fluent API. Instead of creating new Attributes it wraps the provided Attributes. */ @@ -194,6 +194,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key * Adds a new {{name}}. (see {@link {{keyword}}}) * * @param initialCapacity the initial capacity for the new {{name}} + * @return the newly created {{keyword}}. */ default {{keyword}} new{{keyword}}(int initialCapacity) { return new {{keyword}}(getAttributes().newSequence(PRIVATE_CREATOR, TAG, initialCapacity)); @@ -203,9 +204,9 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key * Adds a new {{name}} (see {@link {{keyword}}}) if it does not already exist. * (see {@link Attributes#ensureSequence(int, int)} * - * @param initialCapacity The initial capacity (see {@link java.util.ArrayList#ArrayList(int)}) if a new + * @param initialCapacity the initial capacity (see {@link java.util.ArrayList#ArrayList(int)}) if a new * {{name}} is created. - * @return Either the already existing {{name}} (see {@link {{keyword}}}) or a new one with capacity + * @return either the already existing {{name}} (see {@link {{keyword}}}) or a new one with capacity * initialCapacity. */ default {{keyword}} ensure{{keyword}}(int initialCapacity) { @@ -216,7 +217,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key * Adds a new {{name}} (see {@link {{keyword}}}) with initial capacity 1 (see {@link #ensure{{keyword}}(int)}) * if it does not already exist. * - * @return Either the already existing {{name}} (see {@link {{keyword}}}) or a new one with capacity 1. + * @return either the already existing {{name}} (see {@link {{keyword}}}) or a new one with capacity 1. */ default {{keyword}} ensure{{keyword}}() { return ensure{{keyword}}(1); @@ -224,7 +225,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key {{/sequence}} /** - * @return Whether it contains the {{name}} (see {@link {{keyword}}}) + * @return whether it contains the {{name}} (see {@link {{keyword}}}) */ default boolean contains{{keyword}}() { return getAttributes().contains(PRIVATE_CREATOR, TAG); @@ -261,6 +262,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key {{#sequence}} public interface Builder, T extends {{keyword}}.Holder> extends org.dcm4che.typeddicom.Builder { + @SuppressWarnings("unchecked") // SELF should always be the Builder itself default SELF set{{keyword}}(Item.Builder... itemBuilders) { final SimpleHolder simpleHolder = new SimpleHolder(this.getAttributes()); simpleHolder.remove{{keyword}}(); @@ -280,6 +282,7 @@ public class {{keyword}} extends {{#sequence}}SequenceWrapper<{{keyword}}, {{key * on its .asXXXX() methods. This allows fluent object creation in the form of
    * {@code XXXIOD xxxIOD = new XXXIOD().setYYYY().asYYYY(xxxxValue).setZZZZ().asZZZZ(zzzzValue);} */ + @SuppressWarnings("unchecked") // SELF should always be the Builder itself default {{valueRepresentationWrapper}}.Setter set{{keyword}}() { return new {{valueRepresentationWrapper}}.Setter<>((SELF) this, new {{keyword}}(this.getAttributes())); } diff --git a/dcm4che-typeddicom-lib/src/main/resources/templates/InformationObjectDefinition.java.mustache b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/InformationObjectDefinition.java.mustache similarity index 79% rename from dcm4che-typeddicom-lib/src/main/resources/templates/InformationObjectDefinition.java.mustache rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/InformationObjectDefinition.java.mustache index 25273ce..35b2953 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/templates/InformationObjectDefinition.java.mustache +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/InformationObjectDefinition.java.mustache @@ -5,17 +5,17 @@ import org.dcm4che.typeddicom.SOPClass; import org.dcm4che3.data.Attributes; import org.dcm4che.typeddicom.AbstractAttributesWrapper; import org.dcm4che.typeddicom.AbstractInformationObjectDefinition; -{{#moduleReferences}} -import org.dcm4che.typeddicom.modules.{{moduleMetaInfo.keyword}}; -{{/moduleReferences}} +{{#modules}} +import org.dcm4che.typeddicom.modules.{{.}}; +{{/modules}} import java.util.Collections; import java.util.HashSet; import java.util.Set; /** - * Name: {{name}}
    - * Description: {{{description}}}
    + * Name: {{name}}
    + * Description: {{{description}}}
    * * @see DICOM Standard Part 5 - {{name}} */ @@ -32,17 +32,17 @@ public class {{keyword}} extends AbstractInformationObjectDefinition implements /** * @return a {@link Builder} to create {{name}}s with a fluent API. */ - public static Builder builder() { - return new Builder(); + public static Builder builder() { + return new Builder(); } /** - * @param attributes The Attributes to be wrapped by the {@link Builder}. + * @param attributes the Attributes to be wrapped by the {@link Builder}. * * @return a {@link Builder} to create {{name}} Items with a fluent API. Instead of creating new Attributes it wraps the provided Attributes. */ - public static Builder builder(Attributes attributes) { - return new Builder(attributes); + public static Builder builder(Attributes attributes) { + return new Builder(attributes); } public {{keyword}}(Attributes attributes) { @@ -71,4 +71,4 @@ public class {{keyword}} extends AbstractInformationObjectDefinition implements return super.copy({{keyword}}.class); } } -} \ No newline at end of file +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/Module.java.mustache b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/Module.java.mustache new file mode 100644 index 0000000..4465f15 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/Module.java.mustache @@ -0,0 +1,17 @@ +// Auto generated +package org.dcm4che.typeddicom.modules; + +{{#value.contains}} +import org.dcm4che.typeddicom.dataelements.{{.}}; +{{/value.contains}} + +/** + * {{name}} + * + * @see DICOM Standard Part 3 - {{value.name}} + * + */ +public interface {{key}} extends {{{value.implementsHolderInterfaces}}} { + interface Builder, T extends {{key}}> extends {{{value.implementsBuilderInterfaces}}} { + } +} diff --git a/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/ValueRepresentationMulti.java.mustache b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/ValueRepresentationMulti.java.mustache new file mode 100644 index 0000000..6749598 --- /dev/null +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/ValueRepresentationMulti.java.mustache @@ -0,0 +1,35 @@ +// Auto generated +package org.dcm4che.typeddicom.valuerepresentations; + +import org.dcm4che.typeddicom.AbstractSetter; +import org.dcm4che.typeddicom.AttributesWrapper; +import org.dcm4che.typeddicom.Builder; +import org.dcm4che3.data.VR; + +/** + * Name: {{value.name}}
    + * Tag: {{value.tag}}
    + * Definition: {{{value.definition}}}
    + * Character Repertoire: {{{value.characterRepertoire}}}
    + * Length of Value: {{{value.lengthOfValue}}}
    + * + * @see DICOM Standard Part 5 - {{value.name}} + */ +public interface {{key}}MultiWrapper extends {{value.implementsMultiInterfaces}} { + /** + * The DICOM Value + * Representation (VR) associated with this interface. + */ + VR VALUE_REPRESENTATION = VR.{{value.tag}}; + + @Override + default VR getValueRepresentation() { + return VALUE_REPRESENTATION; + } + + class Setter, D extends {{key}}MultiWrapper> extends AbstractSetter implements {{{value.setterImplementsMultiInterfaces}}} { + public Setter(B builder, D dataElementWrapper) { + super(builder, dataElementWrapper); + } + } +} diff --git a/dcm4che-typeddicom-lib/src/main/resources/templates/ValueRepresentation.java.mustache b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/ValueRepresentationSingle.java.mustache similarity index 54% rename from dcm4che-typeddicom-lib/src/main/resources/templates/ValueRepresentation.java.mustache rename to dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/ValueRepresentationSingle.java.mustache index 877e975..ac8c87d 100644 --- a/dcm4che-typeddicom-lib/src/main/resources/templates/ValueRepresentation.java.mustache +++ b/dcm4che-typeddicom-generator/dcm4che-typeddicom-java-generator-lib/src/main/resources/templates/ValueRepresentationSingle.java.mustache @@ -7,29 +7,29 @@ import org.dcm4che.typeddicom.Builder; import org.dcm4che3.data.VR; /** - * Name: {{name}}
    - * Tag: {{tag}}
    - * Definition: {{{definition}}}
    - * Character Repertoire: {{{characterRepertoire}}}
    - * Length of Value: {{{lengthOfValue}}}
    + * Name: {{value.name}}
    + * Tag: {{value.tag}}
    + * Definition: {{{value.definition}}}
    + * Character Repertoire: {{{value.characterRepertoire}}}
    + * Length of Value: {{{value.lengthOfValue}}}
    * - * @see DICOM Standard Part 5 - {{name}} + * @see DICOM Standard Part 5 - {{value.name}} */ -public interface {{keyword}} extends {{implementsInterfaces}} { +public interface {{key}}Wrapper extends {{value.implementsInterfaces}} { /** * The DICOM Value * Representation (VR) associated with this interface. */ - VR VALUE_REPRESENTATION = VR.{{tag}}; + VR VALUE_REPRESENTATION = VR.{{value.tag}}; @Override default VR getValueRepresentation() { return VALUE_REPRESENTATION; } - class Setter, D extends {{keyword}}> extends AbstractSetter implements {{{setterImplementsInterfaces}}} { + class Setter, D extends {{key}}Wrapper> extends AbstractSetter implements {{{value.setterImplementsInterfaces}}} { public Setter(B builder, D dataElementWrapper) { super(builder, dataElementWrapper); } } -} \ No newline at end of file +} diff --git a/dcm4che-typeddicom-generator/settings.gradle.kts b/dcm4che-typeddicom-generator/settings.gradle.kts new file mode 100644 index 0000000..6541bd3 --- /dev/null +++ b/dcm4che-typeddicom-generator/settings.gradle.kts @@ -0,0 +1,19 @@ +pluginManagement { + repositories { + mavenLocal() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } + gradlePluginPortal() + } +} + +rootProject.name = "dcm4che-typeddicom-generator" +includeBuild("../dcm4che-typeddicom-publisher") +includeBuild("../dcm4che-typeddicom-parser") { + dependencySubstitution { + substitute(module("org.dcm4che:dcm4che-typeddicom-parser-dtos")).using(project(":dcm4che-typeddicom-parser-dtos")) + } +} +include("dcm4che-typeddicom-java-generator-lib") +include("dcm4che-typeddicom-java-generator-gradleplugin") diff --git a/dcm4che-typeddicom-lib/build.gradle.kts b/dcm4che-typeddicom-lib/build.gradle.kts index d8a3fc1..8ac21e1 100644 --- a/dcm4che-typeddicom-lib/build.gradle.kts +++ b/dcm4che-typeddicom-lib/build.gradle.kts @@ -1,150 +1,15 @@ -val typeddicomVersion by extra { project.version } - - -plugins { - `java-library` - `maven-publish` - signing - id("org.dcm4che.typeddicom.gradleplugin.sourcegeneration") -} - -processDicomXml { - dicomStandardXmlDirectory.set(layout.projectDirectory.dir("src/main/resources/dicom-standard-xml")) - mustacheTemplateDirectory.set(layout.projectDirectory.dir("src/main/resources/templates")) - generatedJavaOutputDirectory.set(layout.buildDirectory.dir("java")) -} - -publishing { - publications { - create("mavenJava") { - groupId = rootProject.group.toString() - artifactId = rootProject.name - version = rootProject.version.toString() - - from(components["java"]) - - pom { - name.set("dcm4che-typeddicom") - description.set("This library provides Java classes to wrap dcm4che Attributes and provide type safety for standard DICOM tags.") - url.set("https://github.com/dcm4che/dcm4che-typeddicom") - properties.set(mapOf( - "project.build.sourceEncoding" to "UTF-8" - )) - licenses { - name.set("Mozilla Public License Version 2.0") - url.set("https://www.mozilla.org/en-US/MPL/2.0/") - } - developers { - developer { - id.set("Nirostar") - name.set("Niklas Roth") - email.set("36939232+nirostar@users.noreply.github.com") - } - } - scm { - url.set("https://github.com/dcm4che/dcm4che-typeddicom") - connection.set("scm:git:git://github.com:dcm4che/dcm4che-typeddicom.git") - developerConnection.set("scm:git:git@github.com:dcm4che/dcm4che-typeddicom.git") - } - issueManagement { - url.set("https://github.com/dcm4che/dcm4che-typeddicom/issues") - system.set("GitHub Issues") - } - } - } - } - repositories { - /** - * use `./gradlew publish -Pdcm4cheMavenUsername=DCM4CHE_USERNAME -Pdcm4cheMavenPassword=DCM4CHE_PASSWORD -Psigning.keyId=GPG_KEY_ID -Psigning.password=GPG_KEY_PASSWORD -Psigning.secretKeyRingFile=GPG_KEYRING_FILE` to publish - * or set the corresponding env variables before running `./gradlew publish`: - * ORG_GRADLE_PROJECT_dcm4cheMavenUsername=DCM4CHE_MAVEN_SSH_USERNAME - * ORG_GRADLE_PROJECT_dcm4cheMavenPassword=DCM4CHE_MAVEN_SSH_PASSWORD - * ORG_GRADLE_PROJECT_signingKey=GPG_PRIVATE_KEY - * ORG_GRADLE_PROJECT_signingPassword=GPG_KEY_PASSWORD - */ - maven { - name = "dcm4cheMaven" - url = uri("sftp://dcm4che.org:22/home/maven2") - credentials(PasswordCredentials::class) - } - } -} - -signing { - val signingKey: String? by project - val signingPassword: String? by project - useInMemoryPgpKeys(signingKey, signingPassword) - sign(publishing.publications["mavenJava"]) -} - -java.sourceSets["main"].java { - srcDir("build/java") -} - -repositories { - mavenCentral() - maven { - url = uri("https://www.dcm4che.org/maven2/") - } -} - -dependencies { - implementation("org.dcm4che:dcm4che-core:5.25.0") - - testImplementation("org.junit.jupiter:junit-jupiter-api:5.8.2") - testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.8.2") -} - -java { - sourceCompatibility = JavaVersion.VERSION_1_8 - targetCompatibility = JavaVersion.VERSION_1_8 - withJavadocJar() - withSourcesJar() -} - -tasks.test { - useJUnitPlatform() -} - -tasks.compileJava { - dependsOn(tasks.generateJavaSourceFiles) -} - -tasks.named("jar").configure { - archiveFileName.set("${project.name}.jar") -} - -tasks.named("javadocJar").configure { - archiveFileName.set("${project.name}-javadoc.jar") -} - -tasks.named("sourcesJar").configure { - archiveFileName.set("${project.name}-sources.jar") +tasks.register("publishAllPublicationsToDcm4cheMavenRepository") { + dependsOn(project.getTasksByName("publishAllPublicationsToDcm4cheMavenRepository", true).filter { it != this }) } -tasks.withType { - dependsOn(tasks.generateJavaSourceFiles) - exclude("dicom-standard-xml/") - exclude("templates/") - manifest { - attributes["Manifest-Version"] = "1.0" - attributes["Bundle-ManifestVersion"] = "2" - attributes["Bundle-Name"] = "org.dcm4che.typeddicom" - attributes["Bundle-SymbolicName"] = "org.dcm4che.typeddicom;singleton:=true" - attributes["Bundle-Version"] = typeddicomVersion - attributes["Bundle-Vendor"] = "AGFA" - attributes["Bundle-ClassPath"] = "." - attributes["Bundle-ActivationPolicy"] = "lazy" - attributes["Export-Package"] = - "org.dcm4che.typeddicom, org.dcm4che.typeddicom.dataelements, org.dcm4che.typeddicom.iods, org.dcm4che.typeddicom.modules, org.dcm4che.typeddicom.valuerepresentations" - attributes["Import-Package"] = "org.dcm4che3.data" - } +tasks.register("publishToMavenLocal") { + dependsOn(project.getTasksByName("publishToMavenLocal", true).filter { it != this }) } -tasks.withType { - options.encoding = "UTF-8" +tasks.register("clean") { + dependsOn(project.getTasksByName("clean", true).filter { it != this }) } -tasks.withType { - options.encoding = "UTF-8" +tasks.register("build") { + dependsOn(project.getTasksByName("build", true).filter { it != this }) } diff --git a/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/build.gradle.kts b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/build.gradle.kts new file mode 100644 index 0000000..75437d2 --- /dev/null +++ b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/build.gradle.kts @@ -0,0 +1,64 @@ +plugins { + `java-library` + id("org.dcm4che.typeddicom-java-generator") + id("org.dcm4che.typeddicom-publisher") +} + +generateTypeddicomJavaSources { + privateDicomMetamodelYamlDirectory.set(java.sourceSets.getByName("main").resources.sourceDirectories.single()) + generatedJavaOutputDirectory.set(layout.buildDirectory.dir("typeddicom")) +} + + +typeddicomPublisher { + pomName.set("dcm4che-typeddicom-lib-std") + pomDescription.set("This library provides Java classes to wrap dcm4che Attributes and provide type safety for " + + "standard DICOM tags."); +} + +repositories { + mavenCentral() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } +} + +dependencies { + implementation("org.dcm4che:dcm4che-core:5.29.0") + + testImplementation("org.junit.jupiter:junit-jupiter-api:5.8.2") + testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.8.2") +} + +java { + sourceCompatibility = JavaVersion.VERSION_11 + targetCompatibility = JavaVersion.VERSION_11 +} + +tasks.test { + useJUnitPlatform() +} + +tasks.withType { + manifest { + attributes["Manifest-Version"] = "1.0" + attributes["Bundle-ManifestVersion"] = "2" + attributes["Bundle-Name"] = "org.dcm4che.typeddicom" + attributes["Bundle-SymbolicName"] = "org.dcm4che.typeddicom;singleton:=true" + attributes["Bundle-Version"] = version + attributes["Bundle-Vendor"] = "dcm4che" + attributes["Bundle-ClassPath"] = "." + attributes["Bundle-ActivationPolicy"] = "lazy" + attributes["Export-Package"] = + "org.dcm4che.typeddicom, org.dcm4che.typeddicom.dataelements, org.dcm4che.typeddicom.iods, org.dcm4che.typeddicom.modules, org.dcm4che.typeddicom.valuerepresentations" + attributes["Import-Package"] = "org.dcm4che3.data" + } +} + +tasks.withType { + options.encoding = "UTF-8" +} + +tasks.withType { + options.encoding = "UTF-8" +} diff --git a/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/main/resources/std-adaptations.dicom-meta-model.yaml b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/main/resources/std-adaptations.dicom-meta-model.yaml new file mode 100644 index 0000000..e69de29 diff --git a/dcm4che-typeddicom-lib/src/test/java/SimpleTests.java b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/java/SimpleTests.java similarity index 100% rename from dcm4che-typeddicom-lib/src/test/java/SimpleTests.java rename to dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/java/SimpleTests.java diff --git a/dcm4che-typeddicom-lib/src/test/resources/CRImage_PS.dcm b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/resources/CRImage_PS.dcm similarity index 100% rename from dcm4che-typeddicom-lib/src/test/resources/CRImage_PS.dcm rename to dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/resources/CRImage_PS.dcm diff --git a/dcm4che-typeddicom-lib/src/test/resources/GSPS.dcm b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/resources/GSPS.dcm similarity index 100% rename from dcm4che-typeddicom-lib/src/test/resources/GSPS.dcm rename to dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/resources/GSPS.dcm diff --git a/dcm4che-typeddicom-lib/src/test/resources/GSPS_PS.dcm b/dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/resources/GSPS_PS.dcm similarity index 100% rename from dcm4che-typeddicom-lib/src/test/resources/GSPS_PS.dcm rename to dcm4che-typeddicom-lib/dcm4che-typeddicom-lib-std/src/test/resources/GSPS_PS.dcm diff --git a/dcm4che-typeddicom-lib/settings.gradle.kts b/dcm4che-typeddicom-lib/settings.gradle.kts new file mode 100644 index 0000000..63cc5c2 --- /dev/null +++ b/dcm4che-typeddicom-lib/settings.gradle.kts @@ -0,0 +1,18 @@ +pluginManagement { + repositories { + mavenLocal() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } + gradlePluginPortal() + } +} + +rootProject.name = "dcm4che-typeddicom-lib" +include("dcm4che-typeddicom-lib-std") +includeBuild("../dcm4che-typeddicom-generator") +includeBuild("../dcm4che-typeddicom-skeleton") { + dependencySubstitution { + substitute(module("org.dcm4che:dcm4che-typeddicom-skeleton")).using(project(":")) + } +} diff --git a/dcm4che-typeddicom-lib/src/main/resources/templates/Module.java.mustache b/dcm4che-typeddicom-lib/src/main/resources/templates/Module.java.mustache deleted file mode 100644 index 4ee568c..0000000 --- a/dcm4che-typeddicom-lib/src/main/resources/templates/Module.java.mustache +++ /dev/null @@ -1,17 +0,0 @@ -// Auto generated -package org.dcm4che.typeddicom.modules; - -{{#subDataElementMetaInfos}} -import org.dcm4che.typeddicom.dataelements.{{keyword}}; -{{/subDataElementMetaInfos}} - -/** - * {{name}} - * - * @see DICOM Standard Part 3 - {{name}} - * - */ -public interface {{keyword}} extends {{{implementsHolderInterfaces}}} { - interface Builder, T extends {{keyword}}> extends {{{implementsBuilderInterfaces}}} { - } -} diff --git a/dcm4che-typeddicom-parser/build.gradle.kts b/dcm4che-typeddicom-parser/build.gradle.kts new file mode 100644 index 0000000..8ac21e1 --- /dev/null +++ b/dcm4che-typeddicom-parser/build.gradle.kts @@ -0,0 +1,15 @@ +tasks.register("publishAllPublicationsToDcm4cheMavenRepository") { + dependsOn(project.getTasksByName("publishAllPublicationsToDcm4cheMavenRepository", true).filter { it != this }) +} + +tasks.register("publishToMavenLocal") { + dependsOn(project.getTasksByName("publishToMavenLocal", true).filter { it != this }) +} + +tasks.register("clean") { + dependsOn(project.getTasksByName("clean", true).filter { it != this }) +} + +tasks.register("build") { + dependsOn(project.getTasksByName("build", true).filter { it != this }) +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/.gitignore b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/.gitignore new file mode 100644 index 0000000..b63da45 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/.gitignore @@ -0,0 +1,42 @@ +.gradle +build/ +!gradle/wrapper/gradle-wrapper.jar +!**/src/main/**/build/ +!**/src/test/**/build/ + +### IntelliJ IDEA ### +.idea/modules.xml +.idea/jarRepositories.xml +.idea/compiler.xml +.idea/libraries/ +*.iws +*.iml +*.ipr +out/ +!**/src/main/**/out/ +!**/src/test/**/out/ + +### Eclipse ### +.apt_generated +.classpath +.factorypath +.project +.settings +.springBeans +.sts4-cache +bin/ +!**/src/main/**/bin/ +!**/src/test/**/bin/ + +### NetBeans ### +/nbproject/private/ +/nbbuild/ +/dist/ +/nbdist/ +/.nb-gradle/ + +### VS Code ### +.vscode/ + +### Mac OS ### +.DS_Store \ No newline at end of file diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/build.gradle.kts b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/build.gradle.kts new file mode 100644 index 0000000..89542ca --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/build.gradle.kts @@ -0,0 +1,25 @@ +plugins { + id("java") + id("org.dcm4che.typeddicom-publisher") +} + +typeddicomPublisher { + pomName.set("dcm4che-typeddicom-parser-dtos") + pomDescription.set("This library provides the Java dtos needed to parse the YAML file generated by the " + + "dcm4che-typeddicom-parser-gradleplugin"); +} + +repositories { + mavenCentral() +} + +dependencies { + implementation("com.fasterxml.jackson.core:jackson-annotations:2.14.2") + + testImplementation(platform("org.junit:junit-bom:5.9.1")) + testImplementation("org.junit.jupiter:junit-jupiter") +} + +tasks.test { + useJUnitPlatform() +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/AdditionalAttributeInfoContextsDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/AdditionalAttributeInfoContextsDTO.java new file mode 100644 index 0000000..56e844b --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/AdditionalAttributeInfoContextsDTO.java @@ -0,0 +1,78 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonIgnore; +import com.fasterxml.jackson.annotation.JsonMerge; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.List; +import java.util.Objects; + +public final class AdditionalAttributeInfoContextsDTO { + private final AdditionalAttributeInfoDTO additionalAttributeInfoDTO; + @JsonMerge + private final List> contexts; + + public AdditionalAttributeInfoContextsDTO( + @JsonProperty("additionalAttributeInfoDTO") AdditionalAttributeInfoDTO additionalAttributeInfoDTO, + @JsonProperty("contexts") List> contexts + ) { + this.additionalAttributeInfoDTO = additionalAttributeInfoDTO; + this.contexts = contexts; + } + + @JsonIgnore + public String getContextsHTML() { + StringBuilder html = new StringBuilder(); + for (int i = 0; i < getContexts().size(); i++) { + html.append("
  • ").append(getSingleContextHTML(i)).append("
    • "); + } + return html.toString(); + } + + private String getSingleContextHTML(int contextIndex) { + List context = contexts.get(contextIndex); + StringBuilder html = new StringBuilder(); + for (int i = 0; i < context.size(); i++) { + html.append(""); + html.append(context.get(i).getContextName()); + html.append(""); + if (i < context.size() - 1) { + html.append(" > "); + } + } + return html.toString(); + } + + public AdditionalAttributeInfoDTO getAdditionalAttributeInfoDTO() { + return additionalAttributeInfoDTO; + } + + public List> getContexts() { + return contexts; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (AdditionalAttributeInfoContextsDTO) obj; + return Objects.equals(this.additionalAttributeInfoDTO, that.additionalAttributeInfoDTO) && + Objects.equals(this.contexts, that.contexts); + } + + @Override + public int hashCode() { + return Objects.hash(additionalAttributeInfoDTO, contexts); + } + + @Override + public String toString() { + return "AdditionalAttributeInfoContextsDTO[" + + "additionalAttributeInfoDTO=" + additionalAttributeInfoDTO + ", " + + "contexts=" + contexts + ']'; + } + + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/AdditionalAttributeInfoDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/AdditionalAttributeInfoDTO.java new file mode 100644 index 0000000..0097c37 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/AdditionalAttributeInfoDTO.java @@ -0,0 +1,57 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.Objects; + +public final class AdditionalAttributeInfoDTO { + private final String name; + private final String type; + private final String attributeDescription; + + public AdditionalAttributeInfoDTO( + @JsonProperty("name") String name, + @JsonProperty("type") String type, + @JsonProperty("attributeDescription") String attributeDescription + ) { + this.name = name; + this.type = type; + this.attributeDescription = attributeDescription; + } + + public String getName() { + return name; + } + + public String getType() { + return type; + } + + public String getAttributeDescription() { + return attributeDescription; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (AdditionalAttributeInfoDTO) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.type, that.type) && + Objects.equals(this.attributeDescription, that.attributeDescription); + } + + @Override + public int hashCode() { + return Objects.hash(name, type, attributeDescription); + } + + @Override + public String toString() { + return "AdditionalAttributeInfoDTO[" + + "name=" + name + ", " + + "type=" + type + ", " + + "attributeDescription=" + attributeDescription + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ContextEntryDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ContextEntryDTO.java new file mode 100644 index 0000000..c2713b1 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ContextEntryDTO.java @@ -0,0 +1,51 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonIgnore; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.Objects; + +public final class ContextEntryDTO { + private final String contextName; + private final String href; + + public ContextEntryDTO(@JsonProperty("contextName") String contextName, @JsonProperty("href") String href) { + this.contextName = contextName; + this.href = href; + } + + @JsonIgnore + public String getContextHTML() { + return "" + this.getContextName() + ""; + } + + public String getContextName() { + return contextName; + } + + public String getHref() { + return href; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (ContextEntryDTO) obj; + return Objects.equals(this.contextName, that.contextName) && + Objects.equals(this.href, that.href); + } + + @Override + public int hashCode() { + return Objects.hash(contextName, href); + } + + @Override + public String toString() { + return "ContextEntryDTO[" + + "contextName=" + contextName + ", " + + "href=" + href + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/DataElementMetaInfoDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/DataElementMetaInfoDTO.java new file mode 100644 index 0000000..c210ce2 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/DataElementMetaInfoDTO.java @@ -0,0 +1,133 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonMerge; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.ArrayList; +import java.util.List; +import java.util.Objects; + +public final class DataElementMetaInfoDTO { + private final String name; + private final String privateCreatorConstant; + private final String tag; + private final String tagConstant; + private final String valueRepresentation; + private final String valueMultiplicity; + private final String comment; + private final boolean retired; + private final String retiredSince; + @JsonMerge + private final List additionalAttributeInfo; + @JsonMerge + private final List contains; + + public DataElementMetaInfoDTO( + @JsonProperty("name") String name, + @JsonProperty("privateCreatorConstant") String privateCreatorConstant, + @JsonProperty("tag") String tag, + @JsonProperty("tagConstant") String tagConstant, + @JsonProperty("valueRepresentation") String valueRepresentation, + @JsonProperty("valueMultiplicity") String valueMultiplicity, + @JsonProperty("comment") String comment, + @JsonProperty("retired") boolean retired, + @JsonProperty("retiredSince") String retiredSince, + @JsonProperty("additionalAttributeInfo") List additionalAttributeInfo, + @JsonProperty("contains") List contains + ) { + this.name = name; + this.privateCreatorConstant = privateCreatorConstant; + this.tag = tag; + this.tagConstant = tagConstant; + this.valueRepresentation = valueRepresentation; + this.valueMultiplicity = valueMultiplicity; + this.comment = comment; + this.retired = retired; + this.retiredSince = retiredSince; + this.additionalAttributeInfo = additionalAttributeInfo != null ? additionalAttributeInfo : new ArrayList<>(); + this.contains = contains != null ? contains : new ArrayList<>(); + } + + public String getName() { + return name; + } + + public String getPrivateCreatorConstant() { + return privateCreatorConstant; + } + + public String getTag() { + return tag; + } + + public String getTagConstant() { + return tagConstant; + } + + public String getValueRepresentation() { + return valueRepresentation; + } + + public String getValueMultiplicity() { + return valueMultiplicity; + } + + public String getComment() { + return comment; + } + + public boolean getRetired() { + return retired; + } + + public String getRetiredSince() { + return retiredSince; + } + + public List getAdditionalAttributeInfo() { + return additionalAttributeInfo; + } + + public List getContains() { + return contains; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (DataElementMetaInfoDTO) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.privateCreatorConstant, that.privateCreatorConstant) && + Objects.equals(this.tag, that.tag) && + Objects.equals(this.tagConstant, that.tagConstant) && + Objects.equals(this.valueRepresentation, that.valueRepresentation) && + Objects.equals(this.valueMultiplicity, that.valueMultiplicity) && + Objects.equals(this.comment, that.comment) && + this.retired == that.retired && + Objects.equals(this.retiredSince, that.retiredSince) && + Objects.equals(this.additionalAttributeInfo, that.additionalAttributeInfo) && + Objects.equals(this.contains, that.contains); + } + + @Override + public int hashCode() { + return Objects.hash(name, privateCreatorConstant, tag, tagConstant, valueRepresentation, valueMultiplicity, comment, retired, retiredSince, additionalAttributeInfo, contains); + } + + @Override + public String toString() { + return "DataElementMetaInfoDTO[" + + "name=" + name + ", " + + "privateCreatorConstant=" + privateCreatorConstant + ", " + + "tag=" + tag + ", " + + "tagConstant=" + tagConstant + ", " + + "valueRepresentation=" + valueRepresentation + ", " + + "valueMultiplicity=" + valueMultiplicity + ", " + + "comment=" + comment + ", " + + "retired=" + retired + ", " + + "retiredSince=" + retiredSince + ", " + + "additionalAttributeInfo=" + additionalAttributeInfo + ", " + + "contains=" + contains + ']'; + } +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/DicomMetaModelDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/DicomMetaModelDTO.java new file mode 100644 index 0000000..e0f5ddf --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/DicomMetaModelDTO.java @@ -0,0 +1,105 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonMerge; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.HashMap; +import java.util.Map; +import java.util.Objects; + +public final class DicomMetaModelDTO { + @JsonMerge + private final Map valueRepresentations; + @JsonMerge + private final Map dataElements; + @JsonMerge + private final Map modules; + @JsonMerge + private final Map iods; + + public DicomMetaModelDTO( + @JsonProperty Map valueRepresentations, + @JsonProperty Map dataElements, + @JsonProperty Map modules, + @JsonProperty Map iods + ) { + this.valueRepresentations = valueRepresentations; + this.dataElements = dataElements; + this.modules = modules; + this.iods = iods; + } + + public DicomMetaModelDTO() { + this(new HashMap<>(), new HashMap<>(), new HashMap<>(), new HashMap<>()); + } + + public void addOrUpdate(String keyword, ValueRepresentationMetaInfoDTO newValue) { + ValueRepresentationMetaInfoDTO oldValue = valueRepresentations.putIfAbsent(keyword, newValue); + if (oldValue != null) { + throw new IllegalStateException("There are multiple ValueRepresentationMetaInfoDTOs with the same keyword: " + keyword); + } + } + + public void addOrUpdate(String keyword, DataElementMetaInfoDTO newValue) { + DataElementMetaInfoDTO oldValue = dataElements.putIfAbsent(keyword, newValue); + if (oldValue != null) { + throw new IllegalStateException("There are multiple DataElementMetaInfoDTOs with the same keyword: " + keyword); + } + } + + public void addOrUpdate(String keyword, ModuleMetaInfoDTO newValue) { + ModuleMetaInfoDTO oldValue = modules.putIfAbsent(keyword, newValue); + if (oldValue != null) { + throw new IllegalStateException("There are multiple ModuleMetaInfoDTOs with the same keyword: " + keyword); + } + } + + public void addOrUpdate(String keyword, InformationObjectDefinitionMetaInfoDTO newValue) { + InformationObjectDefinitionMetaInfoDTO oldValue = iods.putIfAbsent(keyword, newValue); + if (oldValue != null) { + throw new IllegalStateException("There are multiple InformationObjectDefinitionMetaInfoDTOs with the same keyword: " + keyword); + } + } + + public Map getValueRepresentations() { + return valueRepresentations; + } + + public Map getDataElements() { + return dataElements; + } + + public Map getModules() { + return modules; + } + + public Map getIods() { + return iods; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (DicomMetaModelDTO) obj; + return Objects.equals(this.valueRepresentations, that.valueRepresentations) && + Objects.equals(this.dataElements, that.dataElements) && + Objects.equals(this.modules, that.modules) && + Objects.equals(this.iods, that.iods); + } + + @Override + public int hashCode() { + return Objects.hash(valueRepresentations, dataElements, modules, iods); + } + + @Override + public String toString() { + return "DicomMetaModelDTO[" + + "valueRepresentations=" + valueRepresentations + ", " + + "dataElements=" + dataElements + ", " + + "modules=" + modules + ", " + + "iods=" + iods + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/InformationObjectDefinitionMetaInfoDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/InformationObjectDefinitionMetaInfoDTO.java new file mode 100644 index 0000000..d7e1759 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/InformationObjectDefinitionMetaInfoDTO.java @@ -0,0 +1,79 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonMerge; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.List; +import java.util.Objects; + +public final class InformationObjectDefinitionMetaInfoDTO { + private final String name; + private final String href; + private final String sectionId; + @JsonMerge + private final List sopClasses; + @JsonMerge + private final List modules; + + public InformationObjectDefinitionMetaInfoDTO( + @JsonProperty("name") String name, + @JsonProperty("href") String href, + @JsonProperty("sectionId") String sectionId, + @JsonProperty("sopClasses") List sopClasses, + @JsonProperty("modules") List modules + ) { + this.name = name; + this.href = href; + this.sectionId = sectionId; + this.sopClasses = sopClasses; + this.modules = modules; + } + + public String getName() { + return name; + } + + public String getHref() { + return href; + } + + public String getSectionId() { + return sectionId; + } + + public List getSopClasses() { + return sopClasses; + } + + public List getModules() { + return modules; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (InformationObjectDefinitionMetaInfoDTO) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.href, that.href) && + Objects.equals(this.sectionId, that.sectionId) && + Objects.equals(this.sopClasses, that.sopClasses) && + Objects.equals(this.modules, that.modules); + } + + @Override + public int hashCode() { + return Objects.hash(name, href, sectionId, sopClasses, modules); + } + + @Override + public String toString() { + return "InformationObjectDefinitionMetaInfoDTO[" + + "name=" + name + ", " + + "href=" + href + ", " + + "sectionId=" + sectionId + ", " + + "sopClasses=" + sopClasses + ", " + + "modules=" + modules + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ModuleMetaInfoDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ModuleMetaInfoDTO.java new file mode 100644 index 0000000..210d9ae --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ModuleMetaInfoDTO.java @@ -0,0 +1,81 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonIgnore; +import com.fasterxml.jackson.annotation.JsonMerge; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.List; +import java.util.Objects; +import java.util.stream.Collectors; + +public final class ModuleMetaInfoDTO { + private final String name; + private final String sectionId; + private final String href; + @JsonMerge + private final List contains; + + public ModuleMetaInfoDTO( + @JsonProperty("name") String name, + @JsonProperty("sectionId") String sectionId, + @JsonProperty("href") String href, + @JsonProperty("contains") List contains + ) { + this.name = name; + this.sectionId = sectionId; + this.href = href; + this.contains = contains; + } + + @JsonIgnore + public String implementsBuilderInterfaces() { + return contains.stream().map(key -> key + ".Builder").collect(Collectors.joining(", ")); + } + + @JsonIgnore + public String implementsHolderInterfaces() { + return contains.stream().map(key -> key + ".Holder").collect(Collectors.joining(", ")); + } + + public String getName() { + return name; + } + + public String getSectionId() { + return sectionId; + } + + public String getHref() { + return href; + } + + public List getContains() { + return contains; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (ModuleMetaInfoDTO) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.sectionId, that.sectionId) && + Objects.equals(this.href, that.href) && + Objects.equals(this.contains, that.contains); + } + + @Override + public int hashCode() { + return Objects.hash(name, sectionId, href, contains); + } + + @Override + public String toString() { + return "ModuleMetaInfoDTO[" + + "name=" + name + ", " + + "sectionId=" + sectionId + ", " + + "href=" + href + ", " + + "contains=" + contains + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/SOPClassDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/SOPClassDTO.java new file mode 100644 index 0000000..6ad18be --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/SOPClassDTO.java @@ -0,0 +1,45 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.Objects; + +public final class SOPClassDTO { + private final String name; + private final String uid; + + public SOPClassDTO(@JsonProperty("name") String name, @JsonProperty("uid") String uid) { + this.name = name; + this.uid = uid; + } + + public String getName() { + return name; + } + + public String getUid() { + return uid; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (SOPClassDTO) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.uid, that.uid); + } + + @Override + public int hashCode() { + return Objects.hash(name, uid); + } + + @Override + public String toString() { + return "SOPClassDTO[" + + "name=" + name + ", " + + "uid=" + uid + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ValueRepresentationMetaInfoDTO.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ValueRepresentationMetaInfoDTO.java new file mode 100644 index 0000000..3960bef --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-dtos/src/main/java/org/dcm4che/typeddicom/parser/metamodel/dto/ValueRepresentationMetaInfoDTO.java @@ -0,0 +1,131 @@ +package org.dcm4che.typeddicom.parser.metamodel.dto; + +import com.fasterxml.jackson.annotation.JsonIgnore; +import com.fasterxml.jackson.annotation.JsonMerge; +import com.fasterxml.jackson.annotation.JsonProperty; + +import java.util.List; +import java.util.Objects; +import java.util.stream.Collectors; +import java.util.stream.Stream; + +public final class ValueRepresentationMetaInfoDTO { + private final String name; + private final String tag; + private final String definition; + private final String characterRepertoire; + private final String lengthOfValue; + private final String href; + @JsonMerge + private final List dataTypes; + + public ValueRepresentationMetaInfoDTO( + @JsonProperty("name") String name, + @JsonProperty("tag") String tag, + @JsonProperty("definition") String definition, + @JsonProperty("characterRepertoire") String characterRepertoire, + @JsonProperty("lengthOfValue") String lengthOfValue, + @JsonProperty("href") String href, + @JsonProperty("dataTypes") List dataTypes + ) { + this.name = name; + this.tag = tag; + this.definition = definition; + this.characterRepertoire = characterRepertoire; + this.lengthOfValue = lengthOfValue; + this.href = href; + this.dataTypes = dataTypes; + } + + @JsonIgnore + public String getImplementsInterfaces() { + return Stream.concat( + dataTypes.stream().map(s -> s + "Wrapper"), + Stream.of("BytesDataElementWrapper") + ).collect(Collectors.joining(", ")); + } + + @JsonIgnore + public String getSetterImplementsInterfaces() { + return Stream.concat( + dataTypes.stream().map(s -> s + "Wrapper.Setter"), + Stream.of("BytesDataElementWrapper.Setter") + ).collect(Collectors.joining(", ")); + } + + @JsonIgnore + public String getImplementsMultiInterfaces() { + return Stream.concat( + dataTypes.stream().map(s -> s + "MultiWrapper"), + Stream.of("BytesDataElementWrapper") + ).collect(Collectors.joining(", ")); + } + + @JsonIgnore + public String getSetterImplementsMultiInterfaces() { + return Stream.concat( + dataTypes.stream().map(s -> s + "MultiWrapper.Setter"), + Stream.of("BytesDataElementWrapper.Setter") + ).collect(Collectors.joining(", ")); + } + + public String getName() { + return name; + } + + public String getTag() { + return tag; + } + + public String getDefinition() { + return definition; + } + + public String getCharacterRepertoire() { + return characterRepertoire; + } + + public String getLengthOfValue() { + return lengthOfValue; + } + + public String getHref() { + return href; + } + + public List getDataTypes() { + return dataTypes; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (ValueRepresentationMetaInfoDTO) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.tag, that.tag) && + Objects.equals(this.definition, that.definition) && + Objects.equals(this.characterRepertoire, that.characterRepertoire) && + Objects.equals(this.lengthOfValue, that.lengthOfValue) && + Objects.equals(this.href, that.href) && + Objects.equals(this.dataTypes, that.dataTypes); + } + + @Override + public int hashCode() { + return Objects.hash(name, tag, definition, characterRepertoire, lengthOfValue, href, dataTypes); + } + + @Override + public String toString() { + return "ValueRepresentationMetaInfoDTO[" + + "name=" + name + ", " + + "tag=" + tag + ", " + + "definition=" + definition + ", " + + "characterRepertoire=" + characterRepertoire + ", " + + "lengthOfValue=" + lengthOfValue + ", " + + "href=" + href + ", " + + "dataTypes=" + dataTypes + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/build.gradle.kts b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/build.gradle.kts new file mode 100644 index 0000000..7435fdf --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/build.gradle.kts @@ -0,0 +1,33 @@ +plugins { + `java-gradle-plugin` +} + +gradlePlugin { + plugins { + create("dicomXmlParser") { + id = "org.dcm4che.typeddicom-xml-parser" + implementationClass = "org.dcm4che.typeddicom.parser.gradleplugin.DicomXmlParserPlugin" + } + } +} + +repositories { + mavenCentral() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } +} + +dependencies { + implementation(project(":dcm4che-typeddicom-parser-javalib")) +} + +java { + sourceCompatibility = JavaVersion.VERSION_11 + targetCompatibility = JavaVersion.VERSION_11 +} + + +tasks.test { + useJUnitPlatform() +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/DicomXmlParserPlugin.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/DicomXmlParserPlugin.java new file mode 100644 index 0000000..755385e --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/DicomXmlParserPlugin.java @@ -0,0 +1,27 @@ +package org.dcm4che.typeddicom.parser.gradleplugin; + +import org.gradle.api.Plugin; +import org.gradle.api.Project; +import org.gradle.api.file.ProjectLayout; +import org.gradle.api.tasks.SourceSetContainer; +import org.gradle.api.tasks.TaskProvider; + +public class DicomXmlParserPlugin implements Plugin { + public void apply(final Project target) { + final DicomXmlParserPluginExtension extension = target.getExtensions().create("processDicomXml", DicomXmlParserPluginExtension.class); + ProjectLayout layout = target.getLayout(); + extension.getDicomStandardXmlDirectory() + .convention(layout.getProjectDirectory().dir("src/main/resources/dicom-standard-xml")); + extension.getGeneratedYamlMetamodelOutputDirectory() + .convention(layout.getBuildDirectory().dir("typeddicom-generated/resources")); + TaskProvider generateYamlFilesTasksProvider = + target.getTasks().register("generateYamlFiles", GenerateMetamodelYamlTask.class, task -> { + task.getDicomStandardXmlDirectory().set(extension.getDicomStandardXmlDirectory()); + task.getGeneratedYamlMetamodelOutputDirectory().set(extension.getGeneratedYamlMetamodelOutputDirectory()); + }); + target.getPluginManager().withPlugin("java", javaPlugin -> { + SourceSetContainer sourceSets = (SourceSetContainer) target.getProperties().get("sourceSets"); + sourceSets.getByName("main").getResources().srcDir(generateYamlFilesTasksProvider); + }); + } +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/DicomXmlParserPluginExtension.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/DicomXmlParserPluginExtension.java new file mode 100644 index 0000000..2a8b57f --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/DicomXmlParserPluginExtension.java @@ -0,0 +1,9 @@ +package org.dcm4che.typeddicom.parser.gradleplugin; + +import org.gradle.api.file.DirectoryProperty; + +public interface DicomXmlParserPluginExtension { + DirectoryProperty getDicomStandardXmlDirectory(); + + DirectoryProperty getGeneratedYamlMetamodelOutputDirectory(); +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/GenerateJavaSourcesTask.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/GenerateMetamodelYamlTask.java similarity index 73% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/GenerateJavaSourcesTask.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/GenerateMetamodelYamlTask.java index e0c2efe..c702587 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/gradleplugin/GenerateJavaSourcesTask.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-gradleplugin/src/main/java/org/dcm4che/typeddicom/parser/gradleplugin/GenerateMetamodelYamlTask.java @@ -1,6 +1,6 @@ -package org.dcm4che.typeddicom.gradleplugin; +package org.dcm4che.typeddicom.parser.gradleplugin; -import org.dcm4che.typeddicom.DicomXmlParser; +import org.dcm4che.typeddicom.parser.DicomXmlParser; import org.gradle.api.DefaultTask; import org.gradle.api.file.DirectoryProperty; import org.gradle.api.tasks.InputDirectory; @@ -15,21 +15,17 @@ import java.nio.file.SimpleFileVisitor; import java.nio.file.attribute.BasicFileAttributes; -abstract public class GenerateJavaSourcesTask extends DefaultTask { +public abstract class GenerateMetamodelYamlTask extends DefaultTask { @InputDirectory - abstract public DirectoryProperty getDicomStandardXmlDirectory(); - - @InputDirectory - abstract public DirectoryProperty getMustacheTemplateDirectory(); + public abstract DirectoryProperty getDicomStandardXmlDirectory(); @OutputDirectory - abstract public DirectoryProperty getGeneratedJavaOutputDirectory(); + public abstract DirectoryProperty getGeneratedYamlMetamodelOutputDirectory(); @TaskAction public void generateJavaSources() { File dicomXmlDirectory = this.getDicomStandardXmlDirectory().get().getAsFile(); - File mustacheTemplateDirectory = this.getMustacheTemplateDirectory().get().getAsFile(); - File javaDirectory = this.getGeneratedJavaOutputDirectory().get().getAsFile(); + File javaDirectory = this.getGeneratedYamlMetamodelOutputDirectory().get().getAsFile(); if (javaDirectory.exists()) { @@ -58,7 +54,7 @@ public FileVisitResult visitFile( //noinspection ResultOfMethodCallIgnored javaDirectory.mkdirs(); - DicomXmlParser dicomXmlParser = new DicomXmlParser(dicomXmlDirectory, mustacheTemplateDirectory, javaDirectory); - dicomXmlParser.generateSources(); + DicomXmlParser dicomXmlParser = new DicomXmlParser(dicomXmlDirectory, javaDirectory); + dicomXmlParser.generateYamlMetamodel(); } } diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/build.gradle.kts b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/build.gradle.kts new file mode 100644 index 0000000..cf76fda --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/build.gradle.kts @@ -0,0 +1,40 @@ +plugins { + id("java-library") +} + +repositories { + mavenCentral() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } +} + +dependencies { + implementation(project(":dcm4che-typeddicom-parser-dtos")) + + implementation("org.apache.commons:commons-text:1.9") + implementation("com.github.davidmoten:word-wrap:0.1.9") + + implementation("org.apache.commons:commons-lang3:3.12.0") + + implementation("org.dcm4che:dcm4che-core:5.29.0") + + implementation("org.jsoup:jsoup:1.14.3") + + implementation("com.fasterxml.jackson.core:jackson-core:2.14.2") + implementation("com.fasterxml.jackson.core:jackson-databind:2.14.2") + implementation("com.fasterxml.jackson.dataformat:jackson-dataformat-yaml:2.14.2") + + testImplementation("org.junit.jupiter:junit-jupiter-api:5.7.0") + testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.7.0") +} + +java { + sourceCompatibility = JavaVersion.VERSION_11 + targetCompatibility = JavaVersion.VERSION_11 +} + + +tasks.test { + useJUnitPlatform() +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/AbstractDicomPartHandler.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/AbstractDicomPartHandler.java similarity index 79% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/AbstractDicomPartHandler.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/AbstractDicomPartHandler.java index e707c8e..7a2d65a 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/AbstractDicomPartHandler.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/AbstractDicomPartHandler.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom; +package org.dcm4che.typeddicom.parser; import org.apache.commons.text.StringEscapeUtils; import org.xml.sax.Attributes; @@ -14,10 +14,10 @@ * This class records HTML or Text after calling the start methods and stops after calling the corresponding getters. */ public abstract class AbstractDicomPartHandler extends DefaultHandler { - protected static final String DICOM_STANDARD_HTML_URL = "http://dicom.nema.org/medical/dicom/current/output/html"; private final StringBuilder currentText = new StringBuilder(); private final Pattern partNumberPattern = Pattern.compile("PS3\\.(?\\d+)"); private final StringBuilder currentHTML = new StringBuilder(); + private String dicomStandardHtmlUrl = "https://dicom.nema.org/medical/dicom/current/output/html"; private boolean recordText = false; private boolean recordHTML; private boolean inVariableList; @@ -28,6 +28,10 @@ protected void startRecordingText() { this.recordText = true; } + protected String getDicomStandardHtmlUrl() { + return dicomStandardHtmlUrl; + } + protected String getRecordedText() { this.recordText = false; return this.currentText.toString().trim().replaceAll(" +", " "); @@ -47,6 +51,9 @@ protected String getRecordedHTML() { @Override public void startElement(String uri, String localName, String qName, Attributes attributes) throws SAXException { super.startElement(uri, localName, qName, attributes); + if ("subtitle".equals(qName)) { + this.recordText = true; + } if ("section".equals(qName)) { this.currentSectionId = attributes.getValue("xml:id"); } @@ -58,6 +65,10 @@ public void startElement(String uri, String localName, String qName, Attributes @Override public void endElement(String uri, String localName, String qName) throws SAXException { super.endElement(uri, localName, qName); + if ("subtitle".equals(qName)) { + String version = this.currentText.toString().replaceAll("DICOM PS\\d\\.\\d+ (\\d\\d\\d\\d[a-z]) - .*", "$1"); + this.dicomStandardHtmlUrl = "https://dicom.nema.org/medical/dicom/" + version + "/output/html"; + } if ("section".equals(qName)) { this.currentSectionId = null; } @@ -68,17 +79,29 @@ public void endElement(String uri, String localName, String qName) throws SAXExc private boolean convertToAndAppendHTML(String qName, Attributes attributes, boolean close) { switch (qName) { - case "para" -> appendTag("p", close); - case "itemizedlist" -> appendTag("ul", close); - case "emphasis" -> appendTag("em", close); - case "superscript" -> appendTag("sup", close); - case "subscript" -> appendTag("sub", close); - case "orderedlist" -> appendTag("ol", close); - case "variablelist" -> { + case "para": + appendTag("p", close); + break; + case "itemizedlist": + appendTag("ul", close); + break; + case "emphasis": + appendTag("em", close); + break; + case "superscript": + appendTag("sup", close); + break; + case "subscript": + appendTag("sub", close); + break; + case "orderedlist": + appendTag("ol", close); + break; + case "variablelist": appendTag("dl", close); inVariableList = !close; - } - case "title" -> { + break; + case "title": if (!close) { appendTag("p", false); appendTag("strong", false); @@ -86,16 +109,18 @@ private boolean convertToAndAppendHTML(String qName, Attributes attributes, bool appendTag("strong", true); appendTag("p", true); } - } - case "term" -> appendTag("dt", close); - case "listitem" -> { + break; + case "term": + appendTag("dt", close); + break; + case "listitem": if (inVariableList) { appendTag("dd", close); } else { appendTag("li", close); } - } - case "xref" -> { + break; + case "xref": if (!close) { String xmlId = attributes.getValue("linkend"); appendTag( @@ -107,11 +132,10 @@ private boolean convertToAndAppendHTML(String qName, Attributes attributes, bool } else { appendTag("a", true); } - } - case "varlistentry" -> { + break; + case "varlistentry": return true; - } - case "note" -> { + case "note": if (!close) { appendTag("div", false, Map.of("class", "note", "style", "font-style: italic; margin-left: 0.5in;"), ""); appendTag("strong", false, Collections.emptyMap(), "Note"); @@ -119,8 +143,8 @@ private boolean convertToAndAppendHTML(String qName, Attributes attributes, bool } else { appendTag("div", true); } - } - case "olink" -> { + break; + case "olink": if (!close) { String targetptr = attributes.getValue("targetptr"); String targetdoc = attributes.getValue("targetdoc"); @@ -133,8 +157,8 @@ private boolean convertToAndAppendHTML(String qName, Attributes attributes, bool } else { appendTag("a", true); } - } - case "link" -> { + break; + case "link": if (!close) { appendTag( "a", @@ -145,11 +169,10 @@ private boolean convertToAndAppendHTML(String qName, Attributes attributes, bool } else { appendTag("a", true); } - } - default -> { + break; + default: System.out.println("Unknown text tag: " + qName); return false; - } } return true; } @@ -159,7 +182,7 @@ private String getUrlFromTarget(String targetdoc, String targetptr) { Matcher matcher = partNumberPattern.matcher(targetdoc); if (matcher.find()) { partNumber = Integer.parseInt(matcher.group("part")); - return String.format("%s/part%02d.html#%s", DICOM_STANDARD_HTML_URL, partNumber, targetptr); + return String.format("%s/part%02d.html#%s", getDicomStandardHtmlUrl(), partNumber, targetptr); }else { throw new IllegalArgumentException("Invalid targetdoc " + targetptr + ". " + "Needs to be of form 'PS3\\.(\\d+)'."); diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart03Handler.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart03Handler.java similarity index 93% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart03Handler.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart03Handler.java index 7887e21..7cc78cd 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart03Handler.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart03Handler.java @@ -1,9 +1,9 @@ -package org.dcm4che.typeddicom; +package org.dcm4che.typeddicom.parser; import org.apache.commons.text.StringEscapeUtils; -import org.dcm4che.typeddicom.metamodel.*; -import org.dcm4che.typeddicom.table.*; -import org.dcm4che.typeddicom.utils.KeywordUtils; +import org.dcm4che.typeddicom.parser.metamodel.*; +import org.dcm4che.typeddicom.parser.table.*; +import org.dcm4che.typeddicom.parser.utils.KeywordUtils; import org.xml.sax.Attributes; import org.xml.sax.SAXException; @@ -12,7 +12,7 @@ /** * This class parses the 3th part of the DICOM Standard XML - * (http://dicom.nema.org/medical/dicom/current/source/docbook/part03/part03.xml) + * (https://dicom.nema.org/medical/dicom/current/source/docbook/part03/part03.xml) */ public class DicomPart03Handler extends MemorizeTablesDicomPartHandler { private static final String FUNCTIONAL_GROUP_MACRO_REFERENCE = "FUNCTIONAL GROUP MACRO"; @@ -87,8 +87,8 @@ public void endElement(String uri, String localName, String qName) throws SAXExc if ("caption".equals(qName)) { // check for table caption of module definitions String recordedText = getRecordedText(); - // ignore the weird stuff happening in http://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.36.25-2 - // because it would ruin the module derived from http://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.36.25-1 + // ignore the weird stuff happening in https://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.36.25-2 + // because it would ruin the module derived from https://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.36.25-1 // (same caption) as well as the example tables if (!currentTableId.equals("table_C.36.25-2") && !recordedText.contains("Example Module Table") && @@ -140,7 +140,7 @@ public void endElement(String uri, String localName, String qName) throws SAXExc @Override public String getBaseHrefUrl() { - return "http://dicom.nema.org/medical/dicom/current/output/html/part03.html"; + return getDicomStandardHtmlUrl() + "/part03.html"; } @Override @@ -187,7 +187,7 @@ private void putReferenceForAllSuperSectionsIfNoClash(Map.*$", "$1"); + return html.replaceAll("(?s).*?.*$", "$1"); } private Iterable resolveMacrosRecursively(TableEntry tableEntry, Context context) { - if (tableEntry instanceof MacroTableEntry macroTableEntry) { + if (tableEntry instanceof MacroTableEntry) { + MacroTableEntry macroTableEntry = (MacroTableEntry) tableEntry; String tableId = macroTableEntry.getTableId(); Set matchingMacroTables = getMatchingMacroTables(tableId); if (matchingMacroTables.isEmpty()) { @@ -277,7 +278,8 @@ private Iterable resolveMacrosRecursively(TableEntry tableE } } return macroMetaInfo.getSubDataElementMetaInfos(); - } else if (tableEntry instanceof AttributeTableEntry attributeTableEntry) { + } else if (tableEntry instanceof AttributeTableEntry) { + AttributeTableEntry attributeTableEntry = (AttributeTableEntry) tableEntry; Set dataElementMetaInfos = this.dataElementMetaInfos.get(attributeTableEntry.getTag()); if (dataElementMetaInfos == null) { System.out.println("Invalid attribute tag: " + attributeTableEntry.getTag()); diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart04Handler.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart04Handler.java similarity index 89% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart04Handler.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart04Handler.java index a613afe..6790eb8 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart04Handler.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart04Handler.java @@ -1,8 +1,8 @@ -package org.dcm4che.typeddicom; +package org.dcm4che.typeddicom.parser; -import org.dcm4che.typeddicom.metamodel.InformationObjectDefinitionMetaInfo; -import org.dcm4che.typeddicom.table.Table; -import org.dcm4che.typeddicom.table.TableCell; +import org.dcm4che.typeddicom.parser.metamodel.InformationObjectDefinitionMetaInfo; +import org.dcm4che.typeddicom.parser.table.Table; +import org.dcm4che.typeddicom.parser.table.TableCell; import org.xml.sax.Attributes; import org.xml.sax.SAXException; @@ -17,7 +17,7 @@ public class DicomPart04Handler extends MemorizeTablesDicomPartHandler { @Override public String getBaseHrefUrl() { - return AbstractDicomPartHandler.DICOM_STANDARD_HTML_URL + "/part04.html"; + return getDicomStandardHtmlUrl() + "/part04.html"; } public DicomPart04Handler(Set iods) { @@ -66,7 +66,7 @@ private void handleSOPClassesTableRow(Table standardSOPClassesTable, int row) { sopClassName = cleanHTMLText(sopClassName); String sopClassUID = standardSOPClassesTable.getTableCell(row, "SOP Class UID").getContent(); sopClassUID = cleanHTMLText(sopClassUID); - final String iodTargetPtr = getIODTargetPointer(standardSOPClassesTable.getTableCell(row, "IOD Specification (defined in\n )")); + final String iodTargetPtr = getIODTargetPointer(standardSOPClassesTable.getTableCell(row, "IOD Specification (defined in )")); InformationObjectDefinitionMetaInfo matchingIOD = this.iods.stream() .filter(iod -> iodTargetPtr.equals(getParentSectionId(iod))) .findFirst() @@ -76,7 +76,7 @@ private void handleSOPClassesTableRow(Table standardSOPClassesTable, int row) { private String getIODTargetPointer(TableCell tableCell) { String iodTargetPtr = tableCell.getContent(); - iodTargetPtr = iodTargetPtr.replaceAll(".*href=\"http://dicom.nema.org/medical/dicom/current/output/html/part03.html#(sect_[^\"]+)\".*", "$1"); + iodTargetPtr = iodTargetPtr.replaceAll(".*href=\"" + getDicomStandardHtmlUrl() + "/part03.html#(sect_[^\"]+)\".*", "$1"); iodTargetPtr = cleanHTMLText(iodTargetPtr); return iodTargetPtr; } diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart05Handler.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart05Handler.java similarity index 66% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart05Handler.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart05Handler.java index 162c2d2..4bdce2d 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart05Handler.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart05Handler.java @@ -1,7 +1,7 @@ -package org.dcm4che.typeddicom; +package org.dcm4che.typeddicom.parser; -import org.dcm4che.typeddicom.metamodel.ValueRepresentationMetaInfo; -import org.dcm4che.typeddicom.utils.KeywordUtils; +import org.dcm4che.typeddicom.parser.metamodel.ValueRepresentationMetaInfo; +import org.dcm4che.typeddicom.parser.utils.KeywordUtils; import org.dcm4che3.data.VR; import org.xml.sax.Attributes; import org.xml.sax.SAXException; @@ -13,18 +13,15 @@ import java.util.LinkedList; import java.util.List; import java.util.Set; -import java.util.stream.Collectors; -import java.util.stream.Stream; /** * This class parses the 5th part of the DICOM Standard XML - * (http://dicom.nema.org/medical/dicom/current/source/docbook/part05/part05.xml) and extracts the Value Representations + * (https://dicom.nema.org/medical/dicom/current/source/docbook/part05/part05.xml) and extracts the Value Representations * from there. */ public class DicomPart05Handler extends AbstractDicomPartHandler { private final List columns = new LinkedList<>(); private final Set valueRepresentations = new HashSet<>(); - private final Set multiValueRepresentations = new HashSet<>(); private boolean isInVRTable; private boolean isInVRTableBody; private String rowHref = null; @@ -33,13 +30,9 @@ public Set getValueRepresentations() { return valueRepresentations; } - public Set getMultiValueRepresentations() { - return multiValueRepresentations; - } - @Override public String getBaseHrefUrl() { - return AbstractDicomPartHandler.DICOM_STANDARD_HTML_URL + "/part05.html"; + return getDicomStandardHtmlUrl() + "/part05.html"; } @Override @@ -87,57 +80,32 @@ private void handleEndOfRow() { if (tag.equals("SQ")) { return; } - Set implementsInterfaces = new HashSet<>(); + Set dataTypes = new HashSet<>(); VR vr = VR.valueOf(tag); if (vr.isTemporalType()) { - implementsInterfaces.add("DateDataElement"); + dataTypes.add("DateDataElement"); } if (isDoubleType(vr)) { - implementsInterfaces.add("DoubleDataElement"); + dataTypes.add("DoubleDataElement"); } if (isFloatType(vr)) { - implementsInterfaces.add("FloatDataElement"); + dataTypes.add("FloatDataElement"); } if (isIntType(vr)) { - implementsInterfaces.add("IntDataElement"); + dataTypes.add("IntDataElement"); } if (isStringType(vr)) { - implementsInterfaces.add("StringDataElement"); + dataTypes.add("StringDataElement"); } valueRepresentations.add(new ValueRepresentationMetaInfo( tag, name, - KeywordUtils.sanitizeAsJavaIdentifier(name) + "Wrapper", - columns.get(1), - columns.get(2), - columns.get(3), - rowHref, - Stream.concat( - implementsInterfaces.stream().map(s -> s + "Wrapper"), - Stream.of("BytesDataElementWrapper") - ).collect(Collectors.joining(", ")), - Stream.concat( - implementsInterfaces.stream().map(s -> s + "Wrapper.Setter"), - Stream.of("BytesDataElementWrapper.Setter") - ).collect(Collectors.joining(", ")) - )); - - multiValueRepresentations.add(new ValueRepresentationMetaInfo( - tag, - name, - KeywordUtils.sanitizeAsJavaIdentifier(name) + "MultiWrapper", + KeywordUtils.sanitizeAsJavaIdentifier(name), columns.get(1), columns.get(2), columns.get(3), rowHref, - Stream.concat( - implementsInterfaces.stream().map(s -> s + "MultiWrapper"), - Stream.of("BytesDataElementWrapper") - ).collect(Collectors.joining(", ")), - Stream.concat( - implementsInterfaces.stream().map(s -> s + "MultiWrapper.Setter"), - Stream.of("BytesDataElementWrapper.Setter") - ).collect(Collectors.joining(", ")) + dataTypes )); } diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart06Handler.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart06Handler.java similarity index 78% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart06Handler.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart06Handler.java index 4caad5a..1ce60a1 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/DicomPart06Handler.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomPart06Handler.java @@ -1,7 +1,7 @@ -package org.dcm4che.typeddicom; +package org.dcm4che.typeddicom.parser; -import org.dcm4che.typeddicom.metamodel.DataElementMetaInfo; -import org.dcm4che.typeddicom.metamodel.ValueRepresentationMetaInfo; +import org.dcm4che.typeddicom.parser.metamodel.DataElementMetaInfo; +import org.dcm4che.typeddicom.parser.metamodel.ValueRepresentationMetaInfo; import org.dcm4che3.data.Tag; import org.xml.sax.Attributes; import org.xml.sax.SAXException; @@ -16,11 +16,10 @@ /** * This class parses the 6th part of the DICOM Standard XML - * (http://dicom.nema.org/medical/dicom/current/source/docbook/part06/part06.xml) + * (https://dicom.nema.org/medical/dicom/current/source/docbook/part06/part06.xml) */ public class DicomPart06Handler extends AbstractDicomPartHandler { private final Map valueRepresentationsMap; - private final Map multiValueRepresentationsMap; private final Set dataElements; private boolean inAttributeRegistryTable = false; private int currentColumn = 0; @@ -28,13 +27,12 @@ public class DicomPart06Handler extends AbstractDicomPartHandler { private boolean inAttributeRegistryTableBody = false; private Map tagConstants; - public DicomPart06Handler(Map valueRepresentationsMap, Map multiValueRepresentationsMap) { - this(valueRepresentationsMap, multiValueRepresentationsMap, new HashSet<>()); + public DicomPart06Handler(Map valueRepresentationsMap) { + this(valueRepresentationsMap, new HashSet<>()); } - public DicomPart06Handler(Map valueRepresentationsMap, Map multiValueRepresentationsMap, Set dataElements) { + public DicomPart06Handler(Map valueRepresentationsMap, Set dataElements) { this.valueRepresentationsMap = valueRepresentationsMap; - this.multiValueRepresentationsMap = multiValueRepresentationsMap; this.dataElements = dataElements; } @@ -89,13 +87,26 @@ public void endElement(String uri, String localName, String qName) throws SAXExc endOfDataElement(); } else if (this.currentDataElementMetaInfo != null && "td".equals(qName)) { switch (currentColumn) { - case 1 -> this.currentDataElementMetaInfo.setTag(getRecordedText()); - case 2 -> this.currentDataElementMetaInfo.setName(getRecordedText()); - case 3 -> this.currentDataElementMetaInfo.setKeyword(getRecordedText().replace("\u200B", "").trim()); - case 4 -> this.currentDataElementMetaInfo.setValueRepresentation(getRecordedText()); - case 5 -> this.currentDataElementMetaInfo.setValueMultiplicity(getRecordedText()); - case 6 -> this.currentDataElementMetaInfo.setComment(getRecordedText()); - default -> throw new IllegalStateException("Unexpected value: " + currentColumn); + case 1: + this.currentDataElementMetaInfo.setTag(getRecordedText()); + break; + case 2: + this.currentDataElementMetaInfo.setName(getRecordedText()); + break; + case 3: + this.currentDataElementMetaInfo.setKeyword(getRecordedText().replace("\u200B", "").trim()); + break; + case 4: + this.currentDataElementMetaInfo.setValueRepresentation(getRecordedText()); + break; + case 5: + this.currentDataElementMetaInfo.setValueMultiplicity(getRecordedText()); + break; + case 6: + this.currentDataElementMetaInfo.setComment(getRecordedText()); + break; + default: + throw new IllegalStateException("Unexpected value: " + currentColumn); } } super.endElement(uri, localName, qName); @@ -133,12 +144,12 @@ private void endOfDataElement() { for (String vr : valueRepresentations) { DataElementMetaInfo dataElement = new DataElementMetaInfo(currentDataElementMetaInfo); dataElement.setValueRepresentation(vr); - dataElement.setValueRepresentationWrapper(valueRepresentationsMap, multiValueRepresentationsMap); + dataElement.setValueRepresentationWrapper(valueRepresentationsMap); dataElement.setKeyword(dataElement.getKeyword() + "As" + vr); this.dataElements.add(dataElement); } } else { - currentDataElementMetaInfo.setValueRepresentationWrapper(valueRepresentationsMap, multiValueRepresentationsMap); + currentDataElementMetaInfo.setValueRepresentationWrapper(valueRepresentationsMap); this.dataElements.add(this.currentDataElementMetaInfo); } } @@ -151,7 +162,7 @@ public Set getDataElements() { @Override public String getBaseHrefUrl() { - return "http://dicom.nema.org/medical/dicom/current/output/html/part03.html"; + return getDicomStandardHtmlUrl() + "/part06.html"; } @Override @@ -160,13 +171,14 @@ protected String getLabelPrefix() { } private String getTagConstant(String keyword, String tag) { - String tagHexRegex = tag.replace("x,", "[02468ACE],").replace("x", "[0-9A-F]"); - tagHexRegex = tagHexRegex.replace("(", "").replace(",", "").replace(")", ""); - tagHexRegex = tagHexRegex.toLowerCase(); Integer tagInt = tagConstants.get(keyword); String constant; if (tagInt != null) { + String tagHexRegex = tag.replace("x,", "[02468ACE],").replace("x", "[0-9A-F]"); + tagHexRegex = tagHexRegex.replace("(", "").replace(",", "").replace(")", ""); + tagHexRegex = tagHexRegex.toLowerCase(); + String tagHex = Integer.toString(tagInt, 16); tagHex = "0".repeat(8 - tagHex.length()) + tagHex; if (tagHex.matches(tagHexRegex)) { @@ -180,5 +192,4 @@ private String getTagConstant(String keyword, String tag) { } return constant; } - } diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomXmlParser.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomXmlParser.java new file mode 100644 index 0000000..afa799d --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/DicomXmlParser.java @@ -0,0 +1,98 @@ +package org.dcm4che.typeddicom.parser; + +import com.fasterxml.jackson.dataformat.yaml.YAMLFactory; +import com.fasterxml.jackson.dataformat.yaml.YAMLGenerator; +import com.fasterxml.jackson.dataformat.yaml.YAMLMapper; +import org.dcm4che.typeddicom.parser.metamodel.DataElementMetaInfo; +import org.dcm4che.typeddicom.parser.metamodel.DicomMetaModel; +import org.dcm4che.typeddicom.parser.metamodel.InformationObjectDefinitionMetaInfo; +import org.dcm4che.typeddicom.parser.metamodel.ValueRepresentationMetaInfo; +import org.dcm4che.typeddicom.parser.metamodel.dto.DicomMetaModelDTO; +import org.dcm4che.typeddicom.parser.metamodel.DicomMetaModelMapper; +import org.xml.sax.SAXException; + +import javax.xml.parsers.ParserConfigurationException; +import javax.xml.parsers.SAXParser; +import javax.xml.parsers.SAXParserFactory; +import java.io.File; +import java.io.IOException; +import java.util.HashMap; +import java.util.HashSet; +import java.util.Map; +import java.util.Set; +import java.util.function.Function; +import java.util.stream.Collectors; + +public class DicomXmlParser { + private final SAXParser saxParser; + private final File dicomXmlDirectory; + private final File yamlOutputDirectory; + + public DicomXmlParser(File dicomXmlDirectory, File yamlOutputDirectory) { + try { + this.dicomXmlDirectory = dicomXmlDirectory; + this.yamlOutputDirectory = yamlOutputDirectory; + SAXParserFactory saxParserFactory = SAXParserFactory.newInstance(); + saxParser = saxParserFactory.newSAXParser(); + } catch (ParserConfigurationException | SAXException e) { + throw new RuntimeException("Wasn't able to create the DICOM XML Parser", e); + } + } + + public void generateYamlMetamodel() { + try { + DicomMetaModel dicomMetaModel = new DicomMetaModel(); + DicomPart05Handler handlerPart5 = new DicomPart05Handler(); + saxParser.parse(new File(dicomXmlDirectory, "part05.xml"), handlerPart5); + Set valueRepresentations = handlerPart5.getValueRepresentations(); + + dicomMetaModel.addValueRepresentations(valueRepresentations); + + Map valueRepresentationsMap = + valueRepresentations.stream().collect(Collectors.toMap( + ValueRepresentationMetaInfo::tag, + Function.identity()) + ); + + DicomPart06Handler handlerPart6 = new DicomPart06Handler(valueRepresentationsMap); + saxParser.parse(new File(dicomXmlDirectory, "part06.xml"), handlerPart6); + Set dataElements = handlerPart6.getDataElements(); + dicomMetaModel.addDataElements(dataElements); + + Map> dataElementMetaInfoMap = new HashMap<>(); + for (DataElementMetaInfo dataElement : dataElements) { + dataElementMetaInfoMap.computeIfAbsent(dataElement.getTag(), (key) -> new HashSet<>()); + dataElementMetaInfoMap.get(dataElement.getTag()).add(dataElement); + } + + DicomPart03Handler handlerPart3 = new DicomPart03Handler(dataElementMetaInfoMap); + saxParser.parse(new File(dicomXmlDirectory, "part03.xml"), handlerPart3); + dicomMetaModel.addModules(handlerPart3.getModules()); + Set iods = handlerPart3.getIODs(); + dicomMetaModel.addIods(iods); + + DicomPart04Handler handlerPart4 = new DicomPart04Handler(iods); + saxParser.parse(new File(dicomXmlDirectory, "part04.xml"), handlerPart4); + + generateYamlFile(dicomMetaModel); + } catch (SAXException | IOException e) { + throw new RuntimeException("Wasn't able to generate the Sources", e); + } + } + + private void generateYamlFile(DicomMetaModel dicomMetaModel) { + DicomMetaModelMapper dtoMapper = new DicomMetaModelMapper(); + DicomMetaModelDTO dicomMetaModelDTO = dtoMapper.mapDicomMetaModelToDicomMetaModelDTO(dicomMetaModel); + + YAMLMapper yamlMapper = new YAMLMapper(new YAMLFactory()); + yamlMapper.configure(YAMLGenerator.Feature.WRITE_DOC_START_MARKER, false); + yamlMapper.configure(YAMLGenerator.Feature.SPLIT_LINES, false); + yamlMapper.configure(YAMLGenerator.Feature.LITERAL_BLOCK_STYLE, true); + yamlMapper.configure(YAMLGenerator.Feature.MINIMIZE_QUOTES, true); + try { + yamlMapper.writeValue(new File(yamlOutputDirectory, "std.dicom-meta-model.yaml"), dicomMetaModelDTO); + } catch (IOException e) { + throw new RuntimeException("Wasn't able to generate the YAML file", e); + } + } +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/MemorizeTablesDicomPartHandler.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/MemorizeTablesDicomPartHandler.java similarity index 94% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/MemorizeTablesDicomPartHandler.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/MemorizeTablesDicomPartHandler.java index 7ab593e..93c3eac 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/MemorizeTablesDicomPartHandler.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/MemorizeTablesDicomPartHandler.java @@ -1,7 +1,7 @@ -package org.dcm4che.typeddicom; +package org.dcm4che.typeddicom.parser; -import org.dcm4che.typeddicom.table.Table; -import org.dcm4che.typeddicom.table.TableCell; +import org.dcm4che.typeddicom.parser.table.Table; +import org.dcm4che.typeddicom.parser.table.TableCell; import org.xml.sax.Attributes; import org.xml.sax.SAXException; diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/AdditionalAttributeInfo.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/AdditionalAttributeInfo.java new file mode 100644 index 0000000..5594c70 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/AdditionalAttributeInfo.java @@ -0,0 +1,51 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import java.util.Objects; + +public final class AdditionalAttributeInfo { + private final String name; + private final String type; + private final String attributeDescription; + + public AdditionalAttributeInfo(String name, String type, String attributeDescription) { + this.name = name; + this.type = type; + this.attributeDescription = attributeDescription; + } + + public String name() { + return name; + } + + public String type() { + return type; + } + + public String attributeDescription() { + return attributeDescription; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (AdditionalAttributeInfo) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.type, that.type) && + Objects.equals(this.attributeDescription, that.attributeDescription); + } + + @Override + public int hashCode() { + return Objects.hash(name, type, attributeDescription); + } + + @Override + public String toString() { + return "AdditionalAttributeInfo[" + + "name=" + name + ", " + + "type=" + type + ", " + + "attributeDescription=" + attributeDescription + ']'; + } + +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/Context.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/Context.java similarity index 73% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/Context.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/Context.java index 193a1ca..44950a2 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/Context.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/Context.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.metamodel; +package org.dcm4che.typeddicom.parser.metamodel; import java.util.ArrayList; import java.util.Collections; @@ -30,20 +30,6 @@ private Context(List parentContext, ContextEntry addedContextEntry context.add(addedContextEntry); } - public String getContextHTML() { - StringBuilder html = new StringBuilder(); - for (int i = 0; i < this.context.size(); i++) { - html.append(""); - html.append(this.context.get(i).contextName()); - html.append(""); - if (i < this.context.size() - 1 ) { - html.append(" > "); - } - } - return html.toString(); - } public List getContext() { return context; diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ContextEntry.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ContextEntry.java new file mode 100644 index 0000000..7a7ad5f --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ContextEntry.java @@ -0,0 +1,43 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import java.util.Objects; + +public final class ContextEntry { + private final String contextName; + private final String href; + + public ContextEntry(String contextName, String href) { + this.contextName = contextName; + this.href = href; + } + + public String contextName() { + return contextName; + } + + public String href() { + return href; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (ContextEntry) obj; + return Objects.equals(this.contextName, that.contextName) && + Objects.equals(this.href, that.href); + } + + @Override + public int hashCode() { + return Objects.hash(contextName, href); + } + + @Override + public String toString() { + return "ContextEntry[" + + "contextName=" + contextName + ", " + + "href=" + href + ']'; + } + +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/DataElementMetaInfo.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DataElementMetaInfo.java similarity index 52% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/DataElementMetaInfo.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DataElementMetaInfo.java index bcffc90..a5a738d 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/DataElementMetaInfo.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DataElementMetaInfo.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.metamodel; +package org.dcm4che.typeddicom.parser.metamodel; import org.davidmoten.text.utils.WordWrap; import org.jsoup.Jsoup; @@ -9,7 +9,6 @@ import java.util.stream.StreamSupport; public class DataElementMetaInfo extends DataElementMetaInfoContainer { - private static final String LINE_BREAK = "
    "; private String tag; private String name; private String keyword; @@ -44,100 +43,20 @@ public DataElementMetaInfo(DataElementMetaInfo other) { this.setTagConstant(other.getTagConstant()); } - public boolean isSequence() { - return "SQ".equals(valueRepresentation); - } - public void addAdditionalAttributeInfoForContext(AdditionalAttributeInfo additionalAttributeInfo, Context context) { this.contextsOfAdditionalAttributeInfo .computeIfAbsent(additionalAttributeInfo, info -> new HashSet<>()) .add(context); } - public void setValueRepresentationWrapper(Map valueRepresentationsMap, Map multiValueRepresentationsMap) { + public void setValueRepresentationWrapper(Map valueRepresentationsMap) { if (!valueRepresentation.equals("SQ")) { - if (getValueMultiplicity().equals("1")) { - this.valueRepresentationWrapper = valueRepresentationsMap.get(valueRepresentation).keyword(); - } else { - this.valueRepresentationWrapper = multiValueRepresentationsMap.get(valueRepresentation).keyword(); - } - } - } - - - public String classJavaDoc() { - StringBuilder htmlBuilder = new StringBuilder(); - appendGeneralInfo(htmlBuilder); - appendContextInfo(htmlBuilder); - Element body = Jsoup.parse(htmlBuilder.toString()).body(); - sanitizeJDocHtml(body); - String htmlString = body.html(); - htmlString = htmlString.replace("\n
    ", "
    \n"); - if (retired) { - htmlString += "\n\n@deprecated "; - htmlString += comment; - } - return javaDocify(htmlString, 0); - } - - private void appendGeneralInfo(StringBuilder html) { - html.append("Name: ").append(name).append(LINE_BREAK); - html.append("Keyword: ").append(keyword).append(LINE_BREAK); - html.append("Tag: ").append(tag).append(LINE_BREAK); - html.append("Value Representation: ").append(valueRepresentation).append(LINE_BREAK); - html.append("Value Multiplicity: ").append(valueMultiplicity).append(LINE_BREAK); - if (comment.length() > 0) { - html.append("Comment: ").append(comment).append(LINE_BREAK); - } - } - - private void appendContextInfo(StringBuilder html) { - if (!contextsOfAdditionalAttributeInfo.isEmpty()) { - html.append("
      "); - for (Map.Entry> additionalAttributeInfoSetEntry : contextsOfAdditionalAttributeInfo.entrySet()) { - html.append("
    • Described in the contexts:
        "); - for (Context context : additionalAttributeInfoSetEntry.getValue()) { - html.append("
      • ").append(context.getContextHTML()).append("
        • "); - } - html.append("
      as follows:
      "); - AdditionalAttributeInfo additionalAttributeInfo = additionalAttributeInfoSetEntry.getKey(); - html.append("Attribute Name: ").append(additionalAttributeInfo.name()).append(LINE_BREAK); - html.append("Type: ").append(additionalAttributeInfo.type()).append(LINE_BREAK); - html.append("Attribute Description: ") - .append(additionalAttributeInfo.attributeDescription()).append(LINE_BREAK); - html.append("
      • "); - } - html.append("
    "); + this.valueRepresentationWrapper = valueRepresentationsMap.get(valueRepresentation).keyword(); + } else { + this.valueRepresentationWrapper = "Sequence"; } } - private void sanitizeJDocHtml(Element body) { - for (Element element : body.select("dl > p")) { - assert element.parent() != null; // should always have a parent - element.parent().before(element); - } - for (Element element : body.select("dd:empty, p:empty, dd:matchesOwn((?is) )")) { - element.remove(); - } - } - - private String javaDocify(String html, int indentationLevel) { - String jdoc = WordWrap.from(html) - .maxWidth(117 - indentationLevel) - .extraWordChars("0123456789-._~:/?#[]@!$&'()*+,;%=\"<>") - .newLine("\n * ") - .breakWords(false) - .wrap(); - jdoc = "/**\n * " + jdoc + "\n */"; - jdoc = indent(jdoc, indentationLevel); - return jdoc; - } - - private String indent(String text, int indentationLevel) { - String indent = " ".repeat(indentationLevel * 4); - return indent + text.replace("\n", "\n" + indent); - } - public String getTag() { return tag; } @@ -235,11 +154,4 @@ public boolean equals(Object o) { public int hashCode() { return Objects.hash(super.hashCode(), tag, name, keyword, valueRepresentation, valueMultiplicity, comment, retired, retiredSince, tagConstant, valueRepresentationWrapper); } - - @Override - public String implementsBuilderInterfaces() { - return StreamSupport.stream(getSubDataElementMetaInfos().spliterator(), false) - .map(dataElementMetaInfo -> dataElementMetaInfo.getKeyword() + ".Builder") - .collect(Collectors.joining(", ")); - } } diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/DataElementMetaInfoContainer.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DataElementMetaInfoContainer.java similarity index 76% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/DataElementMetaInfoContainer.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DataElementMetaInfoContainer.java index bb94511..a26f90b 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/DataElementMetaInfoContainer.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DataElementMetaInfoContainer.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.metamodel; +package org.dcm4che.typeddicom.parser.metamodel; import java.io.Serializable; @@ -34,12 +34,4 @@ public boolean addDataElementMetaInfo(Iterable attributeMet public Iterable getSubDataElementMetaInfos() { return subDataElementMetaInfos; } - - public String implementsHolderInterfaces() { - return StreamSupport.stream(getSubDataElementMetaInfos().spliterator(), false) - .map(dataElementMetaInfo -> dataElementMetaInfo.getKeyword() + ".Holder") - .collect(Collectors.joining(", ")); - } - - public abstract String implementsBuilderInterfaces(); } diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DicomMetaModel.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DicomMetaModel.java new file mode 100644 index 0000000..8c462c0 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DicomMetaModel.java @@ -0,0 +1,46 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import java.util.Collection; +import java.util.HashSet; +import java.util.Set; + +public final class DicomMetaModel { + private final Set valueRepresentations = new HashSet<>(); + private final Set dataElements = new HashSet<>(); + private final Set modules = new HashSet<>(); + private final Set iods = new HashSet<>(); + + public Set getValueRepresentations() { + return valueRepresentations; + } + + public void addValueRepresentations(Collection valueRepresentations) { + this.valueRepresentations.addAll(valueRepresentations); + } + + public Set getDataElements() { + return dataElements; + } + + public void addDataElements(Collection dataElements) { + this.dataElements.addAll(dataElements); + } + + public Set getModules() { + return modules; + } + + public void addModules(Collection modules) { + this.modules.addAll(modules); + } + + public Set getIods() { + return iods; + } + + + public void addIods(Collection iods) { + this.iods.addAll(iods); + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DicomMetaModelMapper.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DicomMetaModelMapper.java new file mode 100644 index 0000000..e3bfa07 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/DicomMetaModelMapper.java @@ -0,0 +1,107 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import org.dcm4che.typeddicom.parser.metamodel.dto.*; + +import java.util.*; +import java.util.stream.Collectors; +import java.util.stream.StreamSupport; + +public class DicomMetaModelMapper { + public DicomMetaModelDTO mapDicomMetaModelToDicomMetaModelDTO(DicomMetaModel dicomMetaModel) { + DicomMetaModelDTO dicomMetaModelDTO = new DicomMetaModelDTO(); + for (ValueRepresentationMetaInfo valueRepresentation : dicomMetaModel.getValueRepresentations()) { + dicomMetaModelDTO.addOrUpdate(valueRepresentation.keyword(), mapValueRepresentationMetaInfoToValueRepresentationMetaInfoDTO(valueRepresentation)); + } + for (DataElementMetaInfo dataElementMetaInfo : dicomMetaModel.getDataElements()) { + dicomMetaModelDTO.addOrUpdate(dataElementMetaInfo.getKeyword(), mapDataElementMetaInfoToDataElementMetaInfoDTO(dataElementMetaInfo)); + } + for (ModuleMetaInfo moduleMetaInfo : dicomMetaModel.getModules()) { + dicomMetaModelDTO.addOrUpdate(moduleMetaInfo.getKeyword(), mapModuleMetaInfoToModuleMetaInfoDTO(moduleMetaInfo)); + } + for (InformationObjectDefinitionMetaInfo informationObjectDefinitionMetaInfo : dicomMetaModel.getIods()) { + dicomMetaModelDTO.addOrUpdate(informationObjectDefinitionMetaInfo.getKeyword(), mapInformationObjectDefinitionMetaInfoToInformationObjectDefinitionMetaInfoDTO(informationObjectDefinitionMetaInfo)); + } + return dicomMetaModelDTO; + } + + private ValueRepresentationMetaInfoDTO mapValueRepresentationMetaInfoToValueRepresentationMetaInfoDTO(ValueRepresentationMetaInfo valueRepresentationMetaInfo) { + return new ValueRepresentationMetaInfoDTO( + valueRepresentationMetaInfo.name(), + valueRepresentationMetaInfo.tag(), + valueRepresentationMetaInfo.definition(), + valueRepresentationMetaInfo.characterRepertoire(), + valueRepresentationMetaInfo.lengthOfValue(), + valueRepresentationMetaInfo.href(), + new ArrayList<>(valueRepresentationMetaInfo.dataTypes()) + ); + } + + private DataElementMetaInfoDTO mapDataElementMetaInfoToDataElementMetaInfoDTO(DataElementMetaInfo dataElementMetaInfo) { + return new DataElementMetaInfoDTO( + dataElementMetaInfo.getName(), + null, + dataElementMetaInfo.getTag(), + dataElementMetaInfo.getTagConstant(), + dataElementMetaInfo.getValueRepresentationWrapper(), + dataElementMetaInfo.getValueMultiplicity(), + dataElementMetaInfo.getComment(), + dataElementMetaInfo.isRetired(), + dataElementMetaInfo.getRetiredSince(), + dataElementMetaInfo.getContextsOfAdditionalAttributeInfo().entrySet().stream() + .map(this::mapAdditionalAttributeInfoContextsEntryToAdditionalAttributeInfoContextsDTO) + .collect(Collectors.toList()), + StreamSupport.stream(dataElementMetaInfo.getSubDataElementMetaInfos().spliterator(), false) + .map(DataElementMetaInfo::getKeyword) + .collect(Collectors.toList()) + ); + } + + private AdditionalAttributeInfoContextsDTO mapAdditionalAttributeInfoContextsEntryToAdditionalAttributeInfoContextsDTO(Map.Entry> additionalAttributeInfoContextsEntry) { + return new AdditionalAttributeInfoContextsDTO( + mapAdditionalAttributeInfoToAdditionalAttributeInfoDTO(additionalAttributeInfoContextsEntry.getKey()), + additionalAttributeInfoContextsEntry.getValue().stream() + .map(this::mapContextToContextEntryDTOs) + .collect(Collectors.toList()) + ); + } + + private List mapContextToContextEntryDTOs(Context context) { + return context.getContext().stream().map(this::mapContextEntryToContextEntryDTO).collect(Collectors.toList()); + } + + private ContextEntryDTO mapContextEntryToContextEntryDTO(ContextEntry contextEntry) { + return new ContextEntryDTO(contextEntry.contextName(), contextEntry.href()); + } + + private static AdditionalAttributeInfoDTO mapAdditionalAttributeInfoToAdditionalAttributeInfoDTO(AdditionalAttributeInfo additionalAttributeInfo) { + return new AdditionalAttributeInfoDTO(additionalAttributeInfo.name(), additionalAttributeInfo.type(), additionalAttributeInfo.attributeDescription()); + } + + private ModuleMetaInfoDTO mapModuleMetaInfoToModuleMetaInfoDTO(ModuleMetaInfo moduleMetaInfo) { + return new ModuleMetaInfoDTO( + moduleMetaInfo.getName(), + moduleMetaInfo.getSectionId(), + moduleMetaInfo.getHref(), + StreamSupport.stream(moduleMetaInfo.getSubDataElementMetaInfos().spliterator(), false) + .map(DataElementMetaInfo::getKeyword).collect(Collectors.toList()) + ); + } + + private InformationObjectDefinitionMetaInfoDTO mapInformationObjectDefinitionMetaInfoToInformationObjectDefinitionMetaInfoDTO(InformationObjectDefinitionMetaInfo informationObjectDefinitionMetaInfo) { + return new InformationObjectDefinitionMetaInfoDTO( + informationObjectDefinitionMetaInfo.getName(), + informationObjectDefinitionMetaInfo.getHref(), + informationObjectDefinitionMetaInfo.getSectionId(), + informationObjectDefinitionMetaInfo.getSopClasses().stream() + .map(this::mapSopClassToSopClassDTO) + .collect(Collectors.toList()), + informationObjectDefinitionMetaInfo.getModuleReferences().stream() + .map(ref -> ref.moduleMetaInfo().getKeyword()) + .collect(Collectors.toList()) + ); + } + + private SOPClassDTO mapSopClassToSopClassDTO(SOPClass sopClass) { + return new SOPClassDTO(sopClass.name(), sopClass.uid()); + } +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/IODModuleReference.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/IODModuleReference.java new file mode 100644 index 0000000..833f05e --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/IODModuleReference.java @@ -0,0 +1,35 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import java.util.Objects; + +public final class IODModuleReference { + private final ModuleMetaInfo moduleMetaInfo; + + public IODModuleReference(ModuleMetaInfo moduleMetaInfo) { + this.moduleMetaInfo = moduleMetaInfo; + } + + public ModuleMetaInfo moduleMetaInfo() { + return moduleMetaInfo; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (IODModuleReference) obj; + return Objects.equals(this.moduleMetaInfo, that.moduleMetaInfo); + } + + @Override + public int hashCode() { + return Objects.hash(moduleMetaInfo); + } + + @Override + public String toString() { + return "IODModuleReference[" + + "moduleMetaInfo=" + moduleMetaInfo + ']'; + } + +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/InformationObjectDefinitionMetaInfo.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/InformationObjectDefinitionMetaInfo.java similarity index 85% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/InformationObjectDefinitionMetaInfo.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/InformationObjectDefinitionMetaInfo.java index 8c37f30..4a1518f 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/InformationObjectDefinitionMetaInfo.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/InformationObjectDefinitionMetaInfo.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.metamodel; +package org.dcm4che.typeddicom.parser.metamodel; import java.util.ArrayList; import java.util.HashSet; @@ -22,11 +22,6 @@ public InformationObjectDefinitionMetaInfo(String name, String keyword, String h this.sectionId = sectionId; } - public String getImplementsModules() { - return moduleReferences.stream() - .map(ref -> ref.moduleMetaInfo().getKeyword()) - .collect(Collectors.joining(", ")); - } public String getImplementsModuleBuilders() { return moduleReferences.stream() diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/MacroMetaInfo.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/MacroMetaInfo.java similarity index 95% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/MacroMetaInfo.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/MacroMetaInfo.java index 146cd7e..ebf8604 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/MacroMetaInfo.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/MacroMetaInfo.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.metamodel; +package org.dcm4che.typeddicom.parser.metamodel; import java.io.Serializable; @@ -31,7 +31,6 @@ public int hashCode() { return Objects.hash(super.hashCode(), tableId); } - @Override public String implementsBuilderInterfaces() { return StreamSupport.stream(getSubDataElementMetaInfos().spliterator(), false) .map(dataElementMetaInfo -> dataElementMetaInfo.getKeyword() + ".Builder") diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ModuleMetaInfo.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ModuleMetaInfo.java similarity index 70% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ModuleMetaInfo.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ModuleMetaInfo.java index 60641a4..9e42195 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/metamodel/ModuleMetaInfo.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ModuleMetaInfo.java @@ -1,6 +1,6 @@ -package org.dcm4che.typeddicom.metamodel; +package org.dcm4che.typeddicom.parser.metamodel; -import org.dcm4che.typeddicom.table.ModuleTable; +import org.dcm4che.typeddicom.parser.table.ModuleTable; import java.util.Objects; import java.util.stream.Collectors; @@ -13,10 +13,10 @@ public class ModuleMetaInfo extends DataElementMetaInfoContainer { private final String href; public ModuleMetaInfo(ModuleTable moduleTable) { - this.sectionId = moduleTable.getSectionId(); - this.name = moduleTable.getName(); - this.keyword = moduleTable.getKeyword(); - this.href = moduleTable.getHref(); + this(moduleTable.getSectionId(), + moduleTable.getName(), + moduleTable.getKeyword(), + moduleTable.getHref()); } public ModuleMetaInfo(String sectionId, String name, String keyword, String href) { @@ -56,10 +56,4 @@ public int hashCode() { return Objects.hash(super.hashCode(), sectionId, name, keyword, href); } - @Override - public String implementsBuilderInterfaces() { - return StreamSupport.stream(getSubDataElementMetaInfos().spliterator(), false) - .map(dataElementMetaInfo -> dataElementMetaInfo.getKeyword() + ".Builder") - .collect(Collectors.joining(", ")); - } } diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/SOPClass.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/SOPClass.java new file mode 100644 index 0000000..e0d00b2 --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/SOPClass.java @@ -0,0 +1,43 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import java.util.Objects; + +public final class SOPClass { + private final String name; + private final String uid; + + public SOPClass(String name, String uid) { + this.name = name; + this.uid = uid; + } + + public String name() { + return name; + } + + public String uid() { + return uid; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (SOPClass) obj; + return Objects.equals(this.name, that.name) && + Objects.equals(this.uid, that.uid); + } + + @Override + public int hashCode() { + return Objects.hash(name, uid); + } + + @Override + public String toString() { + return "SOPClass[" + + "name=" + name + ", " + + "uid=" + uid + ']'; + } + +} diff --git a/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ValueRepresentationMetaInfo.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ValueRepresentationMetaInfo.java new file mode 100644 index 0000000..75ebbde --- /dev/null +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/metamodel/ValueRepresentationMetaInfo.java @@ -0,0 +1,94 @@ +package org.dcm4che.typeddicom.parser.metamodel; + +import java.util.Objects; +import java.util.Set; + +public final class ValueRepresentationMetaInfo { + private final String tag; + private final String name; + private final String keyword; + private final String definition; + private final String characterRepertoire; + private final String lengthOfValue; + private final String href; + private final Set dataTypes; + + public ValueRepresentationMetaInfo(String tag, String name, String keyword, String definition, + String characterRepertoire, String lengthOfValue, + String href, Set dataTypes) { + this.tag = tag; + this.name = name; + this.keyword = keyword; + this.definition = definition; + this.characterRepertoire = characterRepertoire; + this.lengthOfValue = lengthOfValue; + this.href = href; + this.dataTypes = dataTypes; + } + + public String tag() { + return tag; + } + + public String name() { + return name; + } + + public String keyword() { + return keyword; + } + + public String definition() { + return definition; + } + + public String characterRepertoire() { + return characterRepertoire; + } + + public String lengthOfValue() { + return lengthOfValue; + } + + public String href() { + return href; + } + + public Set dataTypes() { + return dataTypes; + } + + @Override + public boolean equals(Object obj) { + if (obj == this) return true; + if (obj == null || obj.getClass() != this.getClass()) return false; + var that = (ValueRepresentationMetaInfo) obj; + return Objects.equals(this.tag, that.tag) && + Objects.equals(this.name, that.name) && + Objects.equals(this.keyword, that.keyword) && + Objects.equals(this.definition, that.definition) && + Objects.equals(this.characterRepertoire, that.characterRepertoire) && + Objects.equals(this.lengthOfValue, that.lengthOfValue) && + Objects.equals(this.href, that.href) && + Objects.equals(this.dataTypes, that.dataTypes); + } + + @Override + public int hashCode() { + return Objects.hash(tag, name, keyword, definition, characterRepertoire, lengthOfValue, href, dataTypes); + } + + @Override + public String toString() { + return "ValueRepresentationMetaInfo[" + + "tag=" + tag + ", " + + "name=" + name + ", " + + "keyword=" + keyword + ", " + + "definition=" + definition + ", " + + "characterRepertoire=" + characterRepertoire + ", " + + "lengthOfValue=" + lengthOfValue + ", " + + "href=" + href + ", " + + "dataTypes=" + dataTypes + ']'; + } + +} diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/AttributeTableEntry.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/AttributeTableEntry.java similarity index 97% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/AttributeTableEntry.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/AttributeTableEntry.java index e325e68..c89a475 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/AttributeTableEntry.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/AttributeTableEntry.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.util.Objects; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/MacroTable.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/MacroTable.java similarity index 96% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/MacroTable.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/MacroTable.java index a8de2ba..4038a6f 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/MacroTable.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/MacroTable.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.util.ArrayList; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/MacroTableEntry.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/MacroTableEntry.java similarity index 95% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/MacroTableEntry.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/MacroTableEntry.java index f4b8b56..01757a2 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/MacroTableEntry.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/MacroTableEntry.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.util.Objects; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/ModuleTable.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/ModuleTable.java similarity index 86% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/ModuleTable.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/ModuleTable.java index 83e61d9..6d75b1e 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/ModuleTable.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/ModuleTable.java @@ -1,10 +1,10 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.util.ArrayList; import java.util.List; -import static org.dcm4che.typeddicom.utils.KeywordUtils.sanitizeAsJavaIdentifier; +import static org.dcm4che.typeddicom.parser.utils.KeywordUtils.sanitizeAsJavaIdentifier; public class ModuleTable { private final String sectionId; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/Table.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/Table.java similarity index 98% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/Table.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/Table.java index a134270..6c5fd4f 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/Table.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/Table.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.util.ArrayList; import java.util.Collection; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/TableCell.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/TableCell.java similarity index 95% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/TableCell.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/TableCell.java index 88b8248..6b1b904 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/TableCell.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/TableCell.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.util.Objects; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/TableEntry.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/TableEntry.java similarity index 91% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/table/TableEntry.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/TableEntry.java index b9917d8..e3411af 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/table/TableEntry.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/table/TableEntry.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.table; +package org.dcm4che.typeddicom.parser.table; import java.io.Serializable; import java.util.ArrayList; diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/utils/InvalidClassNameException.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/utils/InvalidClassNameException.java similarity index 77% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/utils/InvalidClassNameException.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/utils/InvalidClassNameException.java index 4c40959..2bd89bb 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/utils/InvalidClassNameException.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/utils/InvalidClassNameException.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.utils; +package org.dcm4che.typeddicom.parser.utils; public class InvalidClassNameException extends RuntimeException { public InvalidClassNameException(String message) { diff --git a/buildSrc/src/main/java/org/dcm4che/typeddicom/utils/KeywordUtils.java b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/utils/KeywordUtils.java similarity index 91% rename from buildSrc/src/main/java/org/dcm4che/typeddicom/utils/KeywordUtils.java rename to dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/utils/KeywordUtils.java index f9c4372..a4c2749 100644 --- a/buildSrc/src/main/java/org/dcm4che/typeddicom/utils/KeywordUtils.java +++ b/dcm4che-typeddicom-parser/dcm4che-typeddicom-parser-javalib/src/main/java/org/dcm4che/typeddicom/parser/utils/KeywordUtils.java @@ -1,4 +1,4 @@ -package org.dcm4che.typeddicom.utils; +package org.dcm4che.typeddicom.parser.utils; import java.text.DecimalFormat; import java.util.regex.Pattern; @@ -153,12 +153,19 @@ public static String convert(long number) { } result = result + tradMillions; - String tradHundredThousands = switch (hundredThousands) { - case 0 -> ""; - case 1 -> "one thousand "; - default -> convertLessThanOneThousand(hundredThousands) - + " thousand "; - }; + String tradHundredThousands; + switch (hundredThousands) { + case 0: + tradHundredThousands = ""; + break; + case 1: + tradHundredThousands = "one thousand "; + break; + default: + tradHundredThousands = convertLessThanOneThousand(hundredThousands) + + " thousand "; + break; + } result = result + tradHundredThousands; String tradThousand; diff --git a/dcm4che-typeddicom-parser/settings.gradle.kts b/dcm4che-typeddicom-parser/settings.gradle.kts new file mode 100644 index 0000000..9645a28 --- /dev/null +++ b/dcm4che-typeddicom-parser/settings.gradle.kts @@ -0,0 +1,16 @@ +import org.gradle.internal.impldep.org.apache.ivy.core.IvyPatternHelper.substitute + +pluginManagement { + repositories { + mavenLocal() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } + gradlePluginPortal() + } +} + +rootProject.name = "dcm4che-typeddicom-parser" +include("dcm4che-typeddicom-parser-dtos") +include("dcm4che-typeddicom-parser-javalib") +include("dcm4che-typeddicom-parser-gradleplugin") diff --git a/dcm4che-typeddicom-publisher/build.gradle.kts b/dcm4che-typeddicom-publisher/build.gradle.kts new file mode 100644 index 0000000..bf57d05 --- /dev/null +++ b/dcm4che-typeddicom-publisher/build.gradle.kts @@ -0,0 +1,25 @@ +plugins { + `java-gradle-plugin` +} + +gradlePlugin { + plugins { + create("typeddicomPublisher") { + id = "org.dcm4che.typeddicom-publisher" + implementationClass = "org.dcm4che.typeddicom.publisher.TypeddicomPublisherPlugin" + } + } +} + +repositories { + mavenCentral() +} + +dependencies { + testImplementation(platform("org.junit:junit-bom:5.9.1")) + testImplementation("org.junit.jupiter:junit-jupiter") +} + +tasks.test { + useJUnitPlatform() +} diff --git a/dcm4che-typeddicom-publisher/src/main/java/org/dcm4che/typeddicom/publisher/TypeddicomPublisherPlugin.java b/dcm4che-typeddicom-publisher/src/main/java/org/dcm4che/typeddicom/publisher/TypeddicomPublisherPlugin.java new file mode 100644 index 0000000..6c9c476 --- /dev/null +++ b/dcm4che-typeddicom-publisher/src/main/java/org/dcm4che/typeddicom/publisher/TypeddicomPublisherPlugin.java @@ -0,0 +1,127 @@ +package org.dcm4che.typeddicom.publisher; + +import org.gradle.api.Plugin; +import org.gradle.api.Project; +import org.gradle.api.credentials.PasswordCredentials; +import org.gradle.api.plugins.JavaPluginExtension; +import org.gradle.api.publish.PublishingExtension; +import org.gradle.api.publish.maven.MavenPublication; +import org.gradle.api.publish.maven.plugins.MavenPublishPlugin; +import org.gradle.api.tasks.bundling.Jar; +import org.gradle.plugins.signing.SigningExtension; +import org.gradle.plugins.signing.SigningPlugin; +import org.jetbrains.annotations.NotNull; + +import java.util.Map; +import java.util.Objects; + +public class TypeddicomPublisherPlugin implements Plugin { + private static final String TYPEDDICOM_GROUP = "org.dcm4che"; + private static final String TYPEDDICOM_VERSION = "0.5.0"; + + private static final String STANDARD_PUBLICATION_NAME = "mavenJava"; + private static final String GRADLE_PLUGIN_PUBLICATION_NAME = "pluginMaven"; + private TypeddicomPublisherPluginExtension extension; + + @Override + public void apply(@NotNull Project project) { + project.setGroup(TYPEDDICOM_GROUP); + project.setVersion(TYPEDDICOM_VERSION); + + this.extension = project.getExtensions().create("typeddicomPublisher", TypeddicomPublisherPluginExtension.class); + + project.getPluginManager().apply(MavenPublishPlugin.class); + + addJavadocAndSourcesJarToJavaPluginExtension(project); + + addVersionInfoToJarManifest(project); + + project.getGradle().projectsEvaluated(gradle -> { + if (project.getPluginManager().hasPlugin("java-gradle-plugin")) { + configurePublishingAndSigningExtension(project, GRADLE_PLUGIN_PUBLICATION_NAME); + } else { + configurePublishingAndSigningExtension(project, STANDARD_PUBLICATION_NAME); + } + }); + } + + private static void addJavadocAndSourcesJarToJavaPluginExtension(@NotNull Project project) { + JavaPluginExtension javaPluginExtension = project.getExtensions().getByType(JavaPluginExtension.class); + javaPluginExtension.withJavadocJar(); + javaPluginExtension.withSourcesJar(); + } + + private static void addVersionInfoToJarManifest(Project project) { + project.getTasks().withType(Jar.class, jar -> { + jar.getManifest().attributes(Map.of( + "Implementation-Title", project.getName(), + "Implementation-Version", TYPEDDICOM_VERSION + )); + }); + } + + private void configurePublishingAndSigningExtension(Project project, String publicationName) { + MavenPublication mavenPublication = configurePublishingExtensionAndReturnMavenPublication(project, publicationName); + applyAndConfigureSigningPluginIfSigningKeyIsAvailable(project, mavenPublication); + } + + @NotNull + private MavenPublication configurePublishingExtensionAndReturnMavenPublication(Project project, String publicationName) { + PublishingExtension publishing = project.getExtensions().getByType(PublishingExtension.class); + MavenPublication publication = publishing.getPublications().maybeCreate(publicationName, MavenPublication.class); + + publication.setArtifactId(project.getName()); + + if (!Objects.equals(publicationName, GRADLE_PLUGIN_PUBLICATION_NAME)) { + publication.from(project.getComponents().getByName("java")); + } + + publication.pom(pom -> { + pom.getName().set(extension.getPomName()); + pom.getDescription().set(extension.getPomDescription()); + pom.getName().set("dcm4che-typeddicom-java-generator-gradleplugin"); + pom.getDescription().set("This gradle plugin provides a Task to generate Java code which provides the " + + "classes which are specified in the DICOM standard. The classes can be extended with custom " + + "tags by providing a yaml file containing the changes."); + pom.getUrl().set("https://github.com/dcm4che/dcm4che-typeddicom"); + pom.getProperties().put("project.build.sourceEncoding", "UTF-8"); + pom.licenses(licenses -> licenses.license(license -> { + license.getName().set("Mozilla Public License Version 2.0"); + license.getUrl().set("https://www.mozilla.org/en-US/MPL/2.0/"); + })); + pom.developers(developers -> developers.developer(developer -> { + developer.getId().set("Nirostar"); + developer.getName().set("Niklas Roth"); + developer.getEmail().set("36939232+nirostar@users.noreply.github.com"); + })); + pom.scm(scm -> { + scm.getConnection().set("scm:git:git://github.com/dcm4che/dcm4che-typeddicom.git"); + scm.getDeveloperConnection().set("scm:git:git@github.com:dcm4che/dcm4che-typeddicom.git"); + scm.getUrl().set("https://github.com/dcm4che/dcm4che-typeddicom"); + }); + pom.issueManagement(issueManagement -> + issueManagement.getUrl().set("https://github.com/dcm4che/dcm4che-typeddicom/issues") + ); + }); + + publishing.getRepositories().maven(repo -> { + repo.setName("dcm4cheMaven"); + repo.setUrl("sftp://dcm4che.org:22/home/maven2"); + repo.credentials(PasswordCredentials.class); + }); + + return publication; + } + + private static void applyAndConfigureSigningPluginIfSigningKeyIsAvailable(Project project, MavenPublication mavenPublication) { + if (project.hasProperty("signingKey") && project.hasProperty("signingPassword")) { + project.getPluginManager().apply(SigningPlugin.class); + SigningExtension signing = project.getExtensions().getByType(SigningExtension.class); + signing.useInMemoryPgpKeys( + Objects.requireNonNull(project.property("signingKey")).toString(), + Objects.requireNonNull(project.property("signingPassword")).toString() + ); + signing.sign(mavenPublication); + } + } +} diff --git a/dcm4che-typeddicom-publisher/src/main/java/org/dcm4che/typeddicom/publisher/TypeddicomPublisherPluginExtension.java b/dcm4che-typeddicom-publisher/src/main/java/org/dcm4che/typeddicom/publisher/TypeddicomPublisherPluginExtension.java new file mode 100644 index 0000000..430c833 --- /dev/null +++ b/dcm4che-typeddicom-publisher/src/main/java/org/dcm4che/typeddicom/publisher/TypeddicomPublisherPluginExtension.java @@ -0,0 +1,8 @@ +package org.dcm4che.typeddicom.publisher; + +import org.gradle.api.provider.Property; + +public interface TypeddicomPublisherPluginExtension { + Property getPomName(); + Property getPomDescription(); +} diff --git a/dcm4che-typeddicom-skeleton/build.gradle.kts b/dcm4che-typeddicom-skeleton/build.gradle.kts new file mode 100644 index 0000000..b820404 --- /dev/null +++ b/dcm4che-typeddicom-skeleton/build.gradle.kts @@ -0,0 +1,34 @@ +plugins { + id("java-library") + id("org.dcm4che.typeddicom-publisher") +} + +typeddicomPublisher { + pomName.set("dcm4che-typeddicom-skeleton") + pomDescription.set("This contains the skeleton implementation of the Java classes for typeddicom libraries. It " + + "isn't very useful on it's own. (see dcm4che-typeddicom-lib-std for a full fledged implementation of the " + + "DICOM standard."); +} + +repositories { + mavenCentral() + maven { + url = uri("https://www.dcm4che.org/maven2/") + } +} + +dependencies { + implementation("org.dcm4che:dcm4che-core:5.29.0") + + testImplementation("org.junit.jupiter:junit-jupiter-api:5.8.1") + testRuntimeOnly("org.junit.jupiter:junit-jupiter-engine:5.8.1") +} + +tasks.getByName("test") { + useJUnitPlatform() +} + +java { + sourceCompatibility = JavaVersion.VERSION_11 + targetCompatibility = JavaVersion.VERSION_11 +} diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractAttributesWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractAttributesWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractAttributesWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractAttributesWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractInformationObjectDefinition.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractInformationObjectDefinition.java similarity index 84% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractInformationObjectDefinition.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractInformationObjectDefinition.java index 28a9015..47a3e34 100644 --- a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractInformationObjectDefinition.java +++ b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractInformationObjectDefinition.java @@ -1,9 +1,7 @@ package org.dcm4che.typeddicom; -import org.dcm4che.typeddicom.dataelements.SOPClassUID; import org.dcm4che3.data.Attributes; -import java.util.Map; import java.util.Set; public abstract class AbstractInformationObjectDefinition extends AbstractAttributesWrapper { @@ -21,7 +19,7 @@ public AbstractInformationObjectDefinition() { * @return The SOP Classes defined in * Part 4 - Section B.5 of the DICOM * Standard not the one contained in the wrapped attributes. To get that one use - * {@link SOPClassUID.Holder#getSOPClassUID()}. + * SOPClassUID.Holder#getSOPClassUID(). */ public abstract Set getStandardSOPClasses(); } diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractSequenceItemWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractSequenceItemWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractSequenceItemWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractSequenceItemWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractSetter.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractSetter.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AbstractSetter.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AbstractSetter.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AttributesWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AttributesWrapper.java similarity index 89% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AttributesWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AttributesWrapper.java index 10c4134..545fc30 100644 --- a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/AttributesWrapper.java +++ b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/AttributesWrapper.java @@ -26,9 +26,10 @@ static T wrap(Attributes attributes, Class wrap /** * Returns a new Attributes wrapper instance which wraps a copy of the attributes contained in this * Attributes wrapper. (see {@link Attributes#Attributes(Attributes)} - * - * @param wrapperClass The class to wrap the new Attributes object in. - * @return a new instance of an Attributes wrapper implementation which wraps a copy of the attributes contained in + * + * @param the Type of the class to wrap new Attributes object in. + * @param wrapperClass the class to wrap the new Attributes object in. + * @return a new instance of an Attributes wrapper implementation which wraps a copy of the attributes contained in * this Attributes wrapper. */ default T copy(Class wrapperClass) { diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/Builder.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/Builder.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/Builder.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/Builder.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/ConstructorNotImplementedException.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/ConstructorNotImplementedException.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/ConstructorNotImplementedException.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/ConstructorNotImplementedException.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/DataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/DataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/DataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/DataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/SOPClass.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/SOPClass.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/SOPClass.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/SOPClass.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/SequenceWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/SequenceWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/SequenceWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/SequenceWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/Setter.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/Setter.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/Setter.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/Setter.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/StringUtils.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/StringUtils.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/StringUtils.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/StringUtils.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/UniversalAttributesWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/UniversalAttributesWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/UniversalAttributesWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/UniversalAttributesWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/BytesDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/BytesDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/BytesDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/BytesDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementMultiWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementMultiWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementMultiWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementMultiWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DateDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementMultiWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementMultiWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementMultiWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementMultiWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/DoubleDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementMultiWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementMultiWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementMultiWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementMultiWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/FloatDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementMultiWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementMultiWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementMultiWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementMultiWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/IntDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementMultiWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementMultiWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementMultiWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementMultiWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/StringDataElementWrapper.java diff --git a/dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/UniversalDataElementWrapper.java b/dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/UniversalDataElementWrapper.java similarity index 100% rename from dcm4che-typeddicom-lib/src/main/java/org/dcm4che/typeddicom/valuerepresentations/UniversalDataElementWrapper.java rename to dcm4che-typeddicom-skeleton/src/main/java/org/dcm4che/typeddicom/valuerepresentations/UniversalDataElementWrapper.java diff --git a/gradle.properties b/gradle.properties index e549c34..718e0d4 100644 --- a/gradle.properties +++ b/gradle.properties @@ -1,3 +1,2 @@ -version=0.4.3 org.gradle.jvmargs=-Xmx4096m -org.gradle.caching=true +org.gradle.parallel=true diff --git a/gradle/wrapper/gradle-wrapper.properties b/gradle/wrapper/gradle-wrapper.properties index ae04661..e1bef7e 100644 --- a/gradle/wrapper/gradle-wrapper.properties +++ b/gradle/wrapper/gradle-wrapper.properties @@ -1,5 +1,5 @@ distributionBase=GRADLE_USER_HOME distributionPath=wrapper/dists -distributionUrl=https\://services.gradle.org/distributions/gradle-7.5.1-bin.zip +distributionUrl=https\://services.gradle.org/distributions/gradle-8.0.2-bin.zip zipStoreBase=GRADLE_USER_HOME zipStorePath=wrapper/dists diff --git a/settings.gradle b/settings.gradle deleted file mode 100644 index 3c8428b..0000000 --- a/settings.gradle +++ /dev/null @@ -1,2 +0,0 @@ -rootProject.name = 'dcm4che-typeddicom' -include 'dcm4che-typeddicom-lib' diff --git a/settings.gradle.kts b/settings.gradle.kts new file mode 100644 index 0000000..c31a385 --- /dev/null +++ b/settings.gradle.kts @@ -0,0 +1,7 @@ +rootProject.name = "dcm4che-typeddicom" + +includeBuild("dcm4che-typeddicom-publisher") +includeBuild("dcm4che-typeddicom-parser") +includeBuild("dcm4che-typeddicom-generator") +includeBuild("dcm4che-typeddicom-lib") +includeBuild("dcm4che-typeddicom-skeleton")