DICOM PS3.2 2019a - Conformance

3 Definitions (Current)
Prev |  | Next

# 3 Definitions

For the purposes of this Standard the following definitions apply.

## 3.1 Reference Model Definitions

This Part makes use of the following terms defined in [ISO 7498-1]:

Application Entity (AE)

  See [ISO 7498-1].

Application Entity Title

  See [ISO 7498-1].

Protocol Data Unit

  See [ISO 7498-1].

Transfer Syntax

  See [ISO 7498-1].

## 3.2 ACSE Service Definitions

This Part makes use of the following terms defined in [ISO 8649]:

Association

  See [ISO 8649].

Association Initiator

  See [ISO 8649].

## 3.3 Presentation Service Definitions

This Part makes use of the following terms defined in [ISO 8822]:

Abstract Syntax

  See [ISO 8822].

Abstract Syntax Name

  See [ISO 8822].

Presentation Context

  See [ISO 8822].

Transfer Syntax Name

  See [ISO 8822].

## 3.4 DICOM Introduction and Overview Definitions

This Part makes use of the following terms defined in PS3.1:

Conformance Statement

  Conformance Statement.

Information Object

  Information Object.

Service-Object Pair Class (SOP Class)

  Service-Object Pair Class (SOP Class).

## 3.5 DICOM Information Object Definitions

This Part makes use of the following terms defined in PS3.3:

Information Object Definition (IOD)

  Information Object Definition.

## 3.6 DICOM Service Class Specification Definitions

This Part makes use of the following terms defined in PS3.4:

Real-World Activity

  Real-World Activity.

Service Class

  Service Class.

Service Class User (SCU)

  Service Class User (SCU).

Service Class Provider (SCP)

  Service Class Provider (SCP).

Meta Service-Object Pair Class (Meta SOP Class)

  Meta Service-Object Pair Class (Meta SOP Class).

## 3.7 DICOM Data Structure and Encoding Definitions

This Part makes use of the following terms defined in PS3.5:

Data Set

  Data Set.

DICOM Transfer Syntax

  DICOM Transfer Syntax.

Unique Identifier (UID)

  Unique Identifier (UID).

## 3.8 DICOM Message Exchange Definitions

This Part makes use of the following terms defined in PS3.7:

Extended Negotiation

  Extended Negotiation.

Implementation Class UID

  Implementation Class UID.

## 3.9 DICOM Upper Layer Service Definitions

This Part makes use of the following terms defined in PS3.8:

DICOM Upper Layer Service

  DICOM Upper Layer Service.

Presentation Address

  Presentation Address.

## 3.10 Media Storage and File Format for Data Interchange

This Part makes use of the following terms defined in PS3.10:

File-set

  File-set.

File-set Creator (FSC)

  File-set Creator.

File-set Reader (FSR)

  File-set Reader.

File-set Updater (FSU)

  File-set Updater.

Application Profile

  Application Profile.

## 3.11 DICOM Conformance

This Part uses the following definitions:

Standard SOP Class

  A SOP Class defined in the DICOM Standard that is used in an implementation with no modifications.

Standard Extended SOP Class

  A SOP Class defined in the DICOM Standard extended in an implementation with additional Type 3 Attributes. The additional Attributes may either be drawn from the Data Dictionary in PS3.6, or may be Private Attributes. The semantics of the related Standard SOP Class shall not be modified by the additional Type 3 Attributes when absent. Therefore, the Standard Extended SOP Class utilizes the same UID as the related Standard SOP Class.

  ### Note

  IODs from a Standard Extended SOP Class may be freely exchanged between DICOM implementations since implementations unfamiliar with the additional Type 3 Attributes would simply ignore them.

Specialized SOP Class

  A SOP Class derived from a Standard SOP Class that has been specialized in an implementation by additional Type 1, 1C, 2, 2C, or 3 Attributes, by enumeration of specific permitted values for Attributes, or by enumeration of specific permitted Templates. The additional Attributes may either be drawn from the Data Dictionary in PS3.6, or may be Private Attributes. The enumeration of permitted Attribute values or Templates shall be a subset of those permitted in the related Standard SOP Class. Since the semantics of the related Standard SOP Class may be modified by the additional Attributes, a Specialized SOP Class utilizes a Privately Defined UID that differs from the UID for the related Standard SOP Class.

  ### Note

  1. Since a Specialized SOP Class has a different UID than a Standard or Standard Extended SOP Class, other DICOM implementations may not recognize the Specialized SOP Class. Because of this limitation, a Specialized SOP Class should only be used when a Standard or Standard Extended SOP Class would not be appropriate. Before different implementations can exchange Instances in a Specialized SOP Class, the implementations must agree on the UID, content (in particular the additional Type 1, 1C, 2, and 2C Attributes), and semantics of the Specialized SOP Class. A Specialized SOP Class may be used to create a new or experimental SOP Class that is closely related to a Standard SOP Class.

  2. The Association Negotiation for a Specialized SOP Class may include a SOP Class Common Extended Negotiation Sub-Item (as defined in PS3.7) for identification of the Service Class and of the Related General SOP Class from which it was specialized. This may allow a receiving application, without prior agreement on the Specialized SOP Class IOD, to process Instances of that class as if they were instances of a Related General SOP Class.

Private SOP Class

  A SOP Class that is not defined in the DICOM Standard, but is published in an implementation's Conformance Statement.

  ### Note

  Since a Private SOP Class is not defined in the DICOM Standard, other DICOM implementations may not recognize the Private SOP Class. Because of this limitation, a Private SOP Class should only be used when a Standard or Standard Extended SOP Class would not be appropriate. In order for different implementations to exchange Instances in a Private SOP Class, the implementations must agree on the UID, content (in particular the Type 1, 1C, 2, and 2C Attributes), and semantics of the Private SOP Class. A Private SOP class may be used to create a totally new or experimental SOP Class.

Standard Attribute

  An Attribute defined in the Data Dictionary in PS3.6.

Private Attribute

  An Attribute that is not defined in the DICOM Standard.

Standard Application Profile

  An Application Profile defined in the DICOM Standard that is used in an implementation with no modifications.

Augmented Application Profile

  An Application Profile derived from a Standard Application Profile by incorporating support for additional Standard or Standard Extended SOP Classes.

Private Application Profile

  An Application Profile that is not defined in the DICOM Standard, but is published in an implementation's Conformance Statement.

Security Profile

  A mechanism for selecting an appropriate set of choices from the Parts of the DICOM Standard along with corresponding security mechanisms (e.g., encryption algorithms) for the support of security facilities.

Transformation of DICOM SR to CDA

  A mechanism for mapping and transforming DICOM SR objects to HL7 CDA documents.

Prev |  | Next
2 Normative References | Home | 4 Symbols and Abbreviations

DICOM PS3.2 2019a - Conformance