This Application Profile is based on the Media Storage Service Class (see PS 3.4).
SOP Classes and corresponding Transfer Syntaxes supported by this Application Profile are specified in the Table A.3-1.
Table A.3-1STD-XABC-CD SOP CLASSES AND TRANSFER SYNTAXES
|Information Object Definition||Service Object Pair Class UID||Transfer Syntax and UID||FSC Requirement||FSR Requirement||FSU Requirement|
|Basic Directory||1.2.840.10008.1.3.10||Explicit VR Little Endian Uncompressed 1.2.840.10008.1.2.1||Mandatory||Mandatory||Mandatory|
|X-Ray Angiographic Image||1.2.840.10008.5.1.4.18.104.22.168||JPEG Lossless Process 14 (selection value 1) 1.2.840.10008.1.2.4.70||Mandatory||Mandatory||Optional|
Notes: 1. This application profile does not allow the use of the X-Ray Angiographic Bi-Plane Image Object. Biplane acquisitions must therefore be transferred as two single plane SOP instances. A future Application Profile that permits X-Ray Angiographic Bi-Plane Image Object transfer is under development.
2. This Applicaton Profile includes only the XA Image SOP Instances. It does not include Standalone Curve, Modality LUT, VOI LUT, or Overlay SOP Instances.
Basic Cardiac Application Profiles in the STD-XABC class require the 120 mm CD-R physical media with the ISO/IEC 9660 Media Format, as defined in PS 3.12.
Conformant Application Entities shall include in the DICOMDIR File a Basic Directory IOD containing Directory Records at the Patient and subsidiary levels appropriate to the SOP Classes in the File-set.
Note: DICOMDIRs with no directory information are not allowed by this Application Profile.
Table A.3-2 specifies the type of Directory Records that shall be supported and the additional associated keys. Refer to the Basic Directory IOD in PS 3.3.
Table A.3-2STD-XABC-CD ADDITIONAL DICOMDIR KEYS
|Key Attribute||Tag||Directory Record Type||Type||Notes|
|Patient’s Birth Date||(0010,0030)||PATIENT||2|
|Performing Physicians’ Name||(0008,1050)||SERIES||2|
|Icon Image Sequence||(0088,0200)||IMAGE||1|
|Referenced Image Sequence||(0008,1140)||IMAGE||1C||Required if the SOP Instance referenced by the Directory Record has an Image Type (0008,0008) of BIPLANE A or BIPLANE B.|
|>Referenced SOP Class UID||(0008,1150)||IMAGE||1C||Required if Referenced Image Sequence (0008,1140) is present|
|>Referenced SOP Instance UID||(0008,1155)||IMAGE||1C||Required if Referenced Image Sequence (0008,1140) is present|
Directory Records of type IMAGE shall include Icon Images. The icon pixel data shall be supported with Bits Allocated (0028,0100) equal to 8 and Row (0028,0010) and Column (0028,0011) attribute values of 128.
Notes: 1. This icon size is larger than that recommended in PS 3.10 because the 64x64 icon would not be clinically useful for identifying and selecting x-ray angiographic images.
2. For multi-frame images, it is recommended that the icon image be derived from the frame identified in the Representative Frame Number attribute (0028,6010), if defined for the image SOP Instance. If the Representative Frame Number is not present, a frame approximately one-third of the way through the multi-frame image should be selected. The process to reduce a 512x512 image to a 128x128 image is beyond the scope of this standard.
This section defines other parameters common to all specific Application Profiles in the STD-XABC class that need to be specified in order to ensure interoperable media interchange.
The attributes listed in Table A.3-3 used within the X-Ray Angiographic Image files shall take the values specified.
Table A.3-3STD-XABC-CD- REQUIRED IMAGE ATTRIBUTE VALUES
|Rows||(0028,0010)||512 (see below)|
|Columns||(0028,0011)||512 (see below)|
When creating or updating a File-set, Rows or Columns shall not exceed a value of 512. When reading a File-set, an FSR or FSU shall accept a value of at least 512 for Rows or Columns.
Overlay data, if present, shall be encoded in Overlay Data (60XX,3000).
Retired. See PS 3.11 2004.
Note: The retired Detached Patient Management SOP Class was previously suggested to allow patient identification and demographic information to be updated without changing the composite Image IOD files. This usage is now retired.