Add presentation address to file meta information for DULP and Web Services Status Letter Ballot Date of Last Update 2019/09/12 Person Assigned David Clunie Submitter Name David Clunie Submission Date 2019/02/18 Correction Number CP-1895 Log Summary: Add presentation address to file meta information for DULP and Web Services Name of Standard PS3.6, PS3.10, PS3.18 2019d Rationale for Correction: The file meta information contains attributes to describe the source, sending and receiving AE titles. These are supposed to be unique (per PS3.8 Section C.2) in the sense that different systems do not share the same AET, however in practice duplications are not infrequently observed. This makes use of the AETs in the file meta information unreliable. Accordingly, add presentation address attributes to increase the specificity of the information recorded. Also, the web services allow transfer of PS3.10 files but do not specify the appropriate handling of the meta information. Add optional coercion behavior description. Separate action will be taken to register "dicom:" as a scheme name per BCP 35. Correction Wording:

DICOM File Meta Information

Attribute Name	Tag	Type	Attribute Description
Source Application Entity Title	(0002,0016)	3	The DICOM Application Entity (AE) Title of the AE that wrote this file's content (or last updated it). If used, it allows the tracing of the source of errors in the event of media interchange problems. The policies associated with AE Titles are the same as those defined in . If the Data Set was created de novo by the application writing the file, its AE Title, if it has one, may be used. If the Data Set was received over the network, there is potential ambiguity as to whether the value is the same as Sending Application Entity Title (0002,0017) or Receiving Application Entity Title (0002,0018) or some other value.
Sending Application Entity Title	(0002,0017)	3	The DICOM Application Entity (AE) Title of the AE that sent this file's content over a network. This is the AE that was the sender (source) of the content (the Data Set), in the case of a Data Set sent over the network (i.e., the Calling AET of the SCU for a C-STORE operation). If the Data Set was instead created de novo by the application writing the file, it should not be present.
Receiving Application Entity Title	(0002,0018)	3	The DICOM Application Entity (AE) Title of the AE that received this file's content over a network. This is the AE that was the recipient (destination) of the content (the Data Set), in the case of a Data Set received over the network (i.e., the Called AET of the SCP for a C-STORE operation). If the Data Set was instead created de novo by the application writing the file, it should not be present.
Source Presentation Address	(0002,nnn6)	3	The DICOM Presentation Address corresponding to the Source Application Entity Title (0002,0016). See .
Sending Presentation Address	(0002,nnn7)	3	The DICOM Presentation Address corresponding to the Sending Application Entity Title (0002,0017). See .
Receiving Presentation Address	(0002,nnn8)	3	The DICOM Presentation Address corresponding to the Receiving Application Entity Title (0002,0018). See .
Private Information Creator UID	(0002,0100)	3	The UID of the creator of the private information (0002,0102).
Private Information	(0002,0102)	1C	Contains Private Information placed in the File Meta Information. The creator shall be identified in (0002,0100). Required if Private Information Creator UID (0002,0100) is present.

...

The encoding of the presentation address depends on the network transport protocol. For objects exchanged using the PS3.8 DICOM Upper Layer Protocol for TCP/IP, the presentation address shall be encoded as a URI consisting of the scheme "dicom" followed by a colon, then either the fully qualified host name or IP address, followed by a colon and then the port number. E.g., "dicom:127.0.0.1:104", "dicom:myhost.mydomain.com:104". For objects exchanged using the PS3.18 Web Services, the presentation address shall be encoded as the absolute URL of the endpoint of the base of the resource or service, sufficient to identify the system. E.g., "http://myhost.mydomain.com:80/wado-rs/". The presentation address is not expected to be the complete address of the resource. The scheme shall be "http", regardless of whether secure transport was actually used or not. For security reasons, care should be taken to assure that no access credentials such as usernames, passwords or authentication token parameters are encoded in the presentation address.

Amend DICOM PS3.6 as follows (changes to existing text are bold and underlined for additions and struckthrough for removals):

This section specifies the File Meta Elements needed to support the formatting of the File Meta Information of the DICOM File Format (see ).

Registry of DICOM File Meta Elements

Tag	Name	Keyword	VR	VM
(0002,0000)	File Meta Information Group Length	File​Meta​Information​Group​Length	UL	1
(0002,0001)	File Meta Information Version	File​Meta​Information​Version	OB	1
(0002,0002)	Media Storage SOP Class UID	Media​Storage​SOP​Class​UID	UI	1
(0002,0003)	Media Storage SOP Instance UID	Media​Storage​SOP​Instance​UID	UI	1
(0002,0010)	Transfer Syntax UID	Transfer​Syntax​UID	UI	1
(0002,0012)	Implementation Class UID	Implementation​Class​UID	UI	1
(0002,0013)	Implementation Version Name	Implementation​Version​Name	SH	1
(0002,0016)	Source Application Entity Title	Source​Application​Entity​Title	AE	1
(0002,0017)	Sending Application Entity Title	Sending​Application​Entity​Title	AE	1
(0002,0018)	Receiving Application Entity Title	Receiving​Application​Entity​Title	AE	1
(0002,nnn6)	Source Presentation Address	Source​Presentation​Address	UR	1
(0002,nnn7)	Sending Presentation Address	Sending​Presentation​Address	UR	1
(0002,nnn8)	Receiving Presentation Address	Receiving​Presentation​Address	UR	1
(0002,0100)	Private Information Creator UID	Private​Information​Creator​UID	UI	1
(0002,0102)	Private Information	Private​Information	OB	1

Amend DICOM PS3.18 as follows (changes to existing text are bold and underlined for additions and struckthrough for removals):

Content-Type: multipart/related; type=application/dicom; boundary={MessageBoundary} The entire multipart response contains every instance for the specified Study that can be converted to one of the requested Transfer Syntaxes. Each part in the multipart response represents a DICOM SOP Instance with the following http headers: Content-Type: application/dicom [dcm-parameters] See . The origin server may populate the PS3.10 File Meta Information with the identification of the Source, Sending and Receiving AE Titles and Presentation Addresses as described in PS3.10 Section 7.1, or these Attributes may have been left unaltered from when the origin server received the objects. The user agent storing the objects received in the response may populate or coerce these Attributes based on its own knowledge of the endpoints involved in the transaction, so that they accurately identify the most recent storage transaction.

Content-Type: multipart/related; type=application/dicom; boundary={MessageBoundary} The entire multipart response contains every instance for the specified Series that can be converted to one of the requested Transfer Syntaxes. Each part in the multipart response represents a DICOM SOP Instance with the following http headers: Content-Type: application/dicom [dcm-parameters] See . The origin server may populate the PS3.10 File Meta Information with the identification of the Source, Sending and Receiving AE Titles and Presentation Addresses as described in PS3.10 Section 7.1, or these Attributes may have been left unaltered from when the origin server received the objects. The user agent storing the objects received in the response may populate or coerce these Attributes based on its own knowledge of the endpoints involved in the transaction, so that they accurately identify the most recent storage transaction.

Content-Type: multipart/related; type="application/dicom"; boundary={MessageBoundary} The multipart response contains a single part representing the specified DICOM SOP Instance with the following http headers: Content-Type: application/dicom [dcm-parameters] See . The origin server may populate the PS3.10 File Meta Information with the identification of the Source, Sending and Receiving AE Titles and Presentation Addresses as described in PS3.10 Section 7.1, or these Attributes may have been left unaltered from when the origin server received the objects. The user agent storing the objects received in the response may populate or coerce these Attributes based on its own knowledge of the endpoints involved in the transaction, so that they accurately identify the most recent storage transaction.