3 Definitions

3 Definitions (Current)
Prev		Next

3.1 Reference Model Definitions

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

Application Entity: See [ISO 7498-1].
Service: See [ISO 7498-1].
Application Entity Title (AET): See [ISO 7498-1].

3.2 Service Conventions Definitions

This Part of the Standard makes use of the following terms defined in [ISO/TR 8509]:

Primitive: See [ISO/TR 8509].

3.3 DICOM Introduction and Overview Definitions

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

Attribute: See Attribute in PS3.1 .
Command: See Command in PS3.1 .
Data Dictionary: See Data Dictionary in PS3.1 .
Information Object: See Information Object in PS3.1 .
Message: See Message in PS3.1 .
Service-Object Pair Class (SOP Class): See Service-Object Pair Class in PS3.1 .

3.4 DICOM Upper Layer Service Definitions

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

DICOM Upper Layer Service: See DICOM Upper Layer Service in PS3.8 .

3.5 DICOM Message Exchange Definitions

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

DICOM Message Service Element (DIMSE): See DICOM Message Service Element in PS3.7 .
DIMSE-N Services: See DIMSE-N Services in PS3.7 .
DIMSE-C Services: See DIMSE-C Services in PS3.7 .
DIMSE Service Group (DSG): See DIMSE Service Group in PS3.7 .

3.6 DICOM Information Object Definitions

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

Attribute Tag: See Attribute Tag in PS3.3 .
Composite IOD: See Composite IOD in PS3.3 .
DICOM Application Model: See DICOM Application Model in PS3.3 .
DICOM Information Model: See DICOM Information Model in PS3.3 .
Information Object Definition (IOD): See Information Object Definition in PS3.3 .
Module: See Module in PS3.3 .
Normalized IOD: See Normalized IOD in PS3.3 .
Functional Group: See Functional Group in PS3.3 .

3.7 DICOM Conformance

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

Conformance Statement: See Conformance Statement in PS3.2 .
Standard SOP Class: See Standard SOP Class in PS3.2 .
Specialized SOP Class: See Specialized SOP Class in PS3.2 .
Standard Extended SOP Class: See Standard Extended SOP Class in PS3.2 .
Private SOP Class: See Private SOP Class in PS3.2 .
Standard Attribute: See Standard Attribute in PS3.2 .
Private Attribute: See Private Attribute in PS3.2 .

3.8 DICOM Data Structures and Encoding

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

Data Element: See Data Element in PS3.5 .
Data Set: See Data Set in PS3.5 .
Default Character Repertoire: See Default Character Repertoire in PS3.5 .
Unique Identifier (UID): See Unique Identifier in PS3.5 .

3.9 DICOM Service Class Definitions

The following definitions are commonly used in this Part of the DICOM Standard:

Classic Image Storage SOP Class: An Image Storage SOP Class that is defined by an IOD that stores a single frame and defines the majority of the Attributes in the top-level Data Set.
Combined Print Image: A pixel matrix created by superimposing an image and an overlay, the size of which is defined by the smallest rectangle enclosing the superimposed image and overlay.
Enhanced Image Storage SOP Class: An Image Storage SOP Class that is defined by an IOD that stores multiple frames and defines the majority of the Attributes in Functional Group Sequences.
Legacy Converted Enhanced Image Storage SOP Class: A modality-specific Enhanced Image Storage SOP Class that is defined by an IOD that defines only generic Functional Group Sequences, which does not require information that is not present in Classic Image Storage SOP Class Instances, and is intended for storage of converted Classic Image Storage SOP Class Instances when there is insufficient information to use a True Enhanced Image Storage SOP Class.
Meta Service-Object Pair Class (Meta SOP Class): A pre-defined set of SOP Classes that may be associated under a single SOP for the purpose of negotiating the use of the set with a single item.
Non-Patient Object: A SOP Instance that adheres to a Composite Instance IOD Information Model specified in PS3.3, but does not have the Patient Information Entity as its root. Non-Patient Object SOP Instances may still contain patient-related identifiable information, e.g., Inventory SOP Instances
Performed Procedure Step SOP Class: Any SOP Class that encodes the details about the performance of a procedure step.
Performed Procedure Step SOP Instance: An instance of a Performed Procedure Step SOP Class. Note that all UPS instances are instances of the UPS Push SOP Class, which is capable of encoding details about the performance of a procedure step (in addition to details about the scheduled procedure step) and thus qualify as an instance of a Performed Procedure Step SOP Class.
Preformatted Grayscale Image: An image where all annotation, graphics, and grayscale transformations (up to and including the VOI LUT) expected in the printed image have been burnt in or applied before being sent to the SCP. It is a displayable image where the polarity of the intended display is specified by Photometric Interpretation (0028,0004).
Preformatted Color Image: An image where all annotation, graphics, and color transformations expected in the printed image have been burnt in or applied before being sent to the SCP.
Real-World Activity: That which exists in the real world that pertains to specific area of information processing within the area of interest of the DICOM Standard. Such a Real-World Activity may be represented by one or more computer information metaphors called SOP Classes.
Real-World Object: That which exists in the real world upon which operations may be performed that are within the area of interest of the DICOM Standard. Such a Real-World Object may be represented through a computer information metaphor called a SOP Instance.
Related General SOP Class: A SOP Class that is related to another SOP Class as being more generalized in terms of behavior defined in the Standard, and that may be used to identically encode an instance with the same Attributes and values, other than the SOP Class UID. In particular, this may be the SOP Class from which a Specialized SOP Class (see PS3.2) is derived.
Service Class User (SCU): The role played by a DICOM Application Entity (DIMSE-Service-User) that invokes operations and performs notifications on a specific Association.
Service Class Provider (SCP): The role played by a DICOM Application Entity (DIMSE-Service-User) that performs operations and invokes notifications on a specific Association.
Service Class: A collection of SOP Classes and/or Meta SOP Classes that are related in that they are described together to accomplish a single application.
Service-Object Pair Instance (SOP Instance): A concrete occurrence of an Information Object that is managed by a DICOM Application Entity and may be operated upon in a communication context defined by a specific set of DIMSE Services (on a network or interchange media). A SOP Instance is persistent beyond the context of its communication.
True Enhanced Image Storage SOP Class: A modality-specific Enhanced Image Storage SOP Class that is defined by an IOD that defines modality-specific Functional Group Sequences, Attributes and sets of values, and is intended for creation by acquisition devices.

3.10 Device Independent Pixel Values

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

P-Value: See P-Value in PS3.3 .
Profile Connection Space Value (PCS-Value): See Profile Connection Space Value in PS3.3 .

3.11 HTTP Definitions

This Part of the Standard makes use of the following terms defined in [RFC7230]:

origin server: See [RFC7230].
user agent: See [RFC7230].

3.12 Structured Report Definitions

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

Content Item: See Content Item in PS3.3 .
Content Tree: See Content Tree in PS3.3 .

Prev		Next
2 Normative References	Home	4 Symbols and Abbreviations