PS-2020a / part04

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.​

FF.2.4 Additional Volumetric Considerations​

FF.2.4.1 Annotations in Volumetric Presentations States​

The Volumetric Presentation States provide two ways for annotating views:​

•​Annotations on the Volumetric Presentation View​

•​Annotationsdescribedby coordinatesin theVolumetricPresentationStateReferenceCoordinateSystem(VPS-RCS)withoptional​ references to Structured Reports providing context.​

Annotations on the view provide the application of free unformatted text or vector graphics as described in the Section C.10.5​ “Graphic Annotation Module” in PS3.3. 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 Section​ C.18.9.1.2 “Graphic Type” in PS3.3, 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​ maybeemployedtoensurethatVolumetricGraphicAnnotationsaresufficientlyvisible,evenifthelocationinthevolumeisnotvisible​ inthecurrentview.E.g.foraGraphicTypePOINTadisplayapplicationmightrenderacrosshairatthespecifiedpositioninthevolume​ 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,annotationscanbegroupedintoGraphicLayersanditissuggestedthatapplicationsprovidemechanismstodefinerendering​ styles per Graphic Layer.​

SeeSectionXXX.3.4“ReplacingSetofDerivedImagesWithSingleVPSUsingCrosscurveAnimation”inPS3.17andSectionXXX.3.5​ “Volumetric Annotations (example: Trajectory Planning)” in PS3.17 for examples of Volumetric Graphic Annotations.​

FF.2.4.2 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.​

FF.2.4.2.1 Input Sequence Animation​

A Presentation Animation Style (0070,1A01) value of INPUT_SEQ indicates that Input Sequence Animation is being specified. In this​ animationstyle,asingleVolumetricPresentationStateisdefinedwhichincludesinputitemsintheVolumetricPresentationStateInput​ Sequence(0070,1201)withdifferentvaluesofInputSequencePositionIndex(0070,1203).Theanimatedpresentationviewisproduced​ 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 Figure FF.3.2-1.​

Note​

For example, a set of inputs could be temporally related volumes of a moving anatomical structure like the heart.​

- Standard -​

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.​

Note​

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.​

Volumetric Presentation State Input Sequence (0070,1201) item

Input Sequence Position Index (0070,1203) = n

Volumetric Presentation State Input Sequence (0070,1201) item

Input Sequence Position Index (0070,1203) = n

...

...

Volumetric Presentation State Input Sequence (0070,1201) item

Input Sequence Position Index (0070,1203) = 2

Volumetric Presentation State Input Sequence (0070,1201) item

Input Sequence Position Index (0070,1203) = 2

Volumetric Presentation State Input Sequence (0070,1201) item

Input Sequence Position Index (0070,1203) = 1

Volumetric Presentation State Input Sequence (0070,1201) item

Input Sequence Position Index (0070,1203) = 1

Figure FF.3.2-1. Input Sequence Animation​

FF.2.4.2.2 Presentation Sequence Animation​

APresentationAnimationStyle(0070,1A01)valueofPRESENTATION_SEQindicatesthatPresentationSequenceAnimationisbeing​ specified. In this animation style, a set of Volumetric Presentation States are applied sequentially. See Figure FF.3.2-2.​

Note​

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).TheorderofapplicationofthesePresentationStatesisdeterminedbythevalueofPresentationSequencePositionIndex​ (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.​

- Standard -​

Figure FF.3.2-2. Presentation Sequence Animation​

FF.2.4.2.3 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 Fig-​ ure FF.3.2-3.​

Note​

A typical application of this animation style is motion along a curve centered within the colon or a blood vessel.​

Curve described by Animation Curve Sequence (0070,1A04)

MPR Top Left Hand Corner (0070,1505)

Figure FF.3.2-3. Crosscurve Animation​

FF.2.4.2.4 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 Figure FF.2.4.2.4-1.​

- Standard -​

Figure FF.2.4.2.4-1. Flythrough Animation​

FF.2.4.2.5 Swivel Animation​

A Presentation Animation Style (0070,1A01) value of SWIVEL indicates that Swivel Animation is being specified. In this animation​ style,aPresentationStatedefinesaninitialvolumerenderedusingViewpointPosition(0070,1603),ViewpointLookAtPoint(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​ isdefinedbySwivelRange(0070,1A06)andthemaximumrateofrotationisspecifiedbyRecommendedAnimationRate(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.​

FF.2.5 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​

•​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​

•​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 Annex XXX “Volumetric Presentation States (Informative)” in PS3.17.​

FF.3 Behavior of An SCP​

In addition to the behavior for the Storage Service Class specified in Section B.2.2 “Behavior of an SCP”, the following additional re-​ quirements are specified for the Volumetric Presentation State Storage SOP Classes:​

- Standard -​

•​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 a Volume Rendering Volumetric Presentation State Storage SOP Class shall perform an un-​ shaded 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 any of the Volumetric Presentation State Storage SOP Classes is not required to support​ Structured Reporting Storage SOP Classes.​

FF.4 Conformance​

In addition to the Conformance Statement requirements for the Storage Service Class specified in Section B.4.3 “Conformance​ Statement Requirements”, the following additional requirements are specified for the Volumetric Presentation State Storage SOP​ Classes:​

FF.4.1 Conformance Statement For An SCU​

The following behavior shall be documented in the Conformance Statement of any implementation claiming conformance to a Volu-​ metric 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 Class, the manner in​ whichpresentationrelatedattributesarederivedfromadisplayedimage,operatorinterventionordefaults,andhowtheyareincluded​ 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.​

FF.4.2 Conformance Statement For An SCP​

The following behavior shall be documented in the Conformance Statement of any implementation claiming conformance to a Volu-​ metric 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 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, 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.​

•​ForanSCPofaVolumetricPresentationStateStorageSOPClass,whetherreferencestoStructuredReportinstancesaresupported,​ and if not supported, any notifications or lack of notifications to the user that the context information is not displayed.​

- Standard -​

- Standard -​

GGNon-PatientObjectStorageServiceClass​

GG.1 Overview​

GG.1.1 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-related information object to another DICOM AE.​

GG.1.2 Service Definition​

TheNon-PatientObjectStorageServiceClassincludesseveralSOPClasses,eachusinganIODdefinedinPS3.3(seeSectionGG.3).​ The Non-Patient Object Storage Service Class uses the C-STORE DIMSE Service specified in PS3.7. 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.​

•​The transferred information is stored in some medium.​

•​For some time frame, the stored information may be accessed.​

Note​

1.​SupportfortheNon-PatientObjectStorageServiceClassdoesnotimplysupportforanyrelatedQuery/RetrieveService​ Classes.​

2.​The duration of the storage is also implementation dependent, but is described in the Conformance Statement of the​ SCP.​

3.​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.​

GG.2 Association Negotiation​

The Association negotiation rules as defined in PS3.7 apply to the SOP Classes of this Service Class. No SOP Class specific applic-​ ation information (extended negotiation) is used.​

GG.3 SOP Classes​

Theapplication-levelservicesaddressedbytheNon-PatientObjectStorageServiceClassdefinitionarespecifiedintheSOPClasses​ specified in Table GG.3-1.​

Table GG.3-1. Standard SOP Classes​

- Standard -​

GG.4 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 PS3.7.​

In addition to the behaviors specified in this section, there may be SOP Class specific behavior requirements, as described in Sec-​ tion GG.6.​

GG.4.1 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.​

TheSCUshallrecognizethestatusoftheC-STOREserviceandtakeappropriateactionbasedonthesuccessorfailureoftheservice.​ 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.​

GG.4.2 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.​

Note​

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. Table GG.4-1 defines​ thespecificresponsestatuscodevaluesthatmightbereturnedinaC-STOREresponse.Generalstatuscodevaluesandfieldsrelated​ to status code values are defined for C-STORE DIMSE Service in PS3.7.​

Table GG.4-1. C-STORE Response Status Values​

Note​

Status Codes are returned in DIMSE response messages (see PS3.7). The code values stated in column "Status Codes"​ are returned in Status Command Element (0000,0900).​

- Standard -​

GG.5 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 PS3.2.​

GG.5.1 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:​

•​Whether the implementation is a SOP Instance creator for the SOP Class.​

Note​

TheremaybeSOPClassspecificConformanceStatementrequirementsforcreatorsofSOPInstances.SeeSectionGG.6.​

•​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.​

GG.5.2 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:​

•​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.​

Note​

There may be SOP Class specific Conformance Statement requirements for applications that interpret the SOP Instances​ for display or further processing. See Section GG.6.​

GG.6 Application Behavior for Standard SOP Classes​

This section specifies SOP Class specific behaviors for conformant applications.​

GG.6.1 Hanging Protocol SOP Class​

GG.6.1.1 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:​

•​The manner in which the values of the Hanging Protocol IOD Attributes are derived from displayed images, layouts, operator inter-​ vention or defaults.​

•​Any Private Attributes that are used as the value of Selector Attribute (0072,0026) in the Image Set Selector Sequence, Filter Op-​ erations Sequence or Sorting Operations Sequence.​

•​The optional Attributes that may be included in a Hanging Protocol SOP Instance.​

GG.6.1.2 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:​

- Standard -​

•​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.​

•​DescriptionofapplicationbehaviorwhenthevalueofPartialDataDisplayHandling(0072,0208)isADAPT_LAYOUTorzerolength.​

•​DescriptionofapplicationbehaviorwhenthedisplayenvironmentoftheHangingProtocolInstancediffersfromthedisplayenvironment​ 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.​

GG.6.2 Color Palette Storage SOP Class​

GG.6.2.1 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:​

•​The optional Attributes that may be included in a Color Palette SOP Instance.​

GG.6.2.2 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:​

•​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​

GG.6.3 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:​

•​Generic Implant Template Description Module​

•​Generic Implant Template 2D Drawings Module​

•​Generic Implant Template 3D Models Module​

•​Generic Implant Template Mating Features Module​

•​Generic Implant Template Planning Landmarks Module​

•​Implant Assembly Template Module​

•​Implant Template Group Module​

•​Surface Mesh Module​

Referential integrity between sets of related SOP instances shall be maintained.​

- Standard -​