Annex A Basic Cardiac X-ray Angiographic Application Profile(Normative)

A.1 Class and profile identification

This Annex defines an Application Profile Class for Basic Cardiac X-ray Angiographic clinical applications.

The identifier for this class shall be STD-XABC. This annex is concerned only with cardiac

angiography.

The specific Application Profile in this class is shown in the Table A.1-1.

NOTE: This table contains only a single Application Profile. It is expected that additional Application Profiles may be added to PS 3.11.

Table A.1-1BASIC CARDIAC XA PROFILE

Application Profile Identifier Description
Basic Cardiac X-Ray Angiographic Studies on CD-R Media STD-XABC-CD It handles single frame or multi-frame digital images up to 512x512x8 bits; biplane acquisitions are encoded as two single plane information objects.

A.2 Clinical context

This Application Profile Class facilitates the interchange of primary digital X-ray cine runs, typically acquired as part of cardiac catheterization procedures. Typical media interchanges would be from in-lab acquisition equipment to either a display workstation or to a data archive system, or between a display workstation and a data archive system (in both directions). This context is shown in figure A.2-1 below.

[pic]

Figure A.2-1CLINICAL CONTEXT DIAGRAM

The operational use of media interchange is potentially both intra-institutional and inter-institutional.

A.2.1 Roles and service class options

This Application Profile Class uses the Media Storage Service Class defined in PS 3.4.

The Application Entity shall support one or more of the roles of File-set Creator, File-set Reader, and File-set Updater, defined in PS 3.10.

A.2.1.1 FILE SET CREATOR

The Application entity acting as a File-Set Creator generates a File Set under the STD-XABC Application Profile Class. Typical entities using this role would include X-ray angiographic lab equipment, and archive systems that generate a patient record for transfer to another institution. File Set Creators shall be able to generate the Basic Directory SOP Class in the DICOMDIR File with all types of Directory Records related to the SOP Classes stored in the File-set.

FSC shall offer the ability to either finalize the disc at the completion of the most recent write session (no additional information can be subsequently added to the disc) or to allow multi-session (additional information may be subsequently added to the disk).

NOTE : A multiple volume (a logical volume that can cross multiple physical media) is not supported by this Application Profile Class. If a set of Files, e.g., a Study, cannot be written entirely on one CD-R, the FSC will create multiple independent DICOM File-sets such that each File-set can reside on a single CD-R media controlled by its individual DICOMDIR file. The user of the FSC can opt to use written labels on the discs to indicate that there is more than one disc for this set of files (e.g., a study).

A.2.1.2 FILE SET READER

The role of File Set Reader is used by Application Entities that receive a transferred File Set. Typical entities using this role would include display workstations, and archive systems that receive a patient record transferred from another institution. File Set Readers shall be able to read all the SOP Classes defined for the specific Application Profile for which a Conformance Statement is made, using all the defined Transfer Syntaxes.

A.2.1.3 FILE SET UPDATER

The role of File Set Updater is used by Application Entities that receive a transferred File Set and update it by the addition of information. Typical entities using this role would include analytic workstations, which, for instance, may add to the File-set an information object containing a processed (e.g., edge-enhanced) image. Stations that update patient information objects would also use this role. File-set Updaters do not have to read the images. File-set Updaters shall be able to generate one or more of the SOP Instances defined for the specific Application Profile for which a conformance statement is made, and to read and update the DICOMDIR file.

FSU shall offer the ability to either finalize the disc at the completion of the most recent write session (no additional information can be subsequently added to the disc) or to allow multi-session (additional information may be subsequently added to the disk).

NOTE : If the disc has not been closed out, the File-set Updater shall be able to update information assuming there is enough space on the disc to write a new DICOMDIR file, the information, and the fundamental CD-R control structures. CD-R control structures are the structures that are inherent to the CD-R standards, see PS 3.12.

A.3 STD-XABC-CD basic cardiac profile

A.3.1 SOP classes and transfer syntaxes

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

A.3.2 Physical media and media formats

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.

A.3.3 Directory information in DICOMDIR

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.

A.3.3.1 ADDITIONAL KEYS

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
Patient’s Sex (0010,0040) PATIENT 2
Institution Name (0008,0080) SERIES 2
Institution Address (0008,0081) SERIES 2
Performing Physicians’ Name (0008,1050) SERIES 2
Icon Image Sequence (0088,0200) IMAGE 1
Image Type (0008,0008) IMAGE 1
Calibration Image (0050,0004) IMAGE 2
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

A.3.3.2 ICON IMAGES

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.

A.3.4 Other parameters

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.

A.3.4.1 IMAGE ATTRIBUTE VALUES

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

Attribute Tag Value
Modality (0008,0060) XA
Rows (0028,0010) 512 (see below)
Columns (0028,0011) 512 (see below)
Bits Allocated (0028,0100) 8
Bits Stored (0028,0101) 8

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

A.3.4.1.1 ATTRIBUTE VALUE PRECEDENCE

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.