V.6 SOP Class Definitions
Prev | V Substance Administration Query Service Class (Normative) | Next

## V.6 SOP Class Definitions

### V.6.1 Product Characteristics Query SOP Class

#### V.6.1.1 Product Characteristics Query SOP Class Overview

The Product Characteristics Query SOP class defines an application-level class of service that facilitates the communication of detailed information about drugs, contrast agents, or devices identified by a bar code or similar identifier. The detailed information is intended to be used both for automated processing and for presentation to a system operator.

The Product Characteristics Query SOP class supports the following example use cases:

- Obtain the active ingredient, concentration, or other parameters of a contrast agent for inclusion in the image SOP Instances created during use of the agent, or for setting up image acquisition parameters (e.g., ultrasound transducer frequency)

- Obtain the size parameters of a device (e.g., a catheter) for use in calibrating images that show that device

- Obtain a network reference for an online copy of the "product label" (regulated prescribing and use data) for a drug, contrast agent, or device.

#### V.6.1.2 Product Characteristics Query Information Model

##### V.6.1.2.1 E/R Model

The Product Characteristics Query Information Model is represented by the Entity Relationship diagram shown in figure Section V.6 -1.

Figure V.6-1. Product Characteristics E-R Diagram

There is only one Information Entity in the model, which is the Product. The Attributes of a Product can be found in the following Module in PS3.3.

- Product Characteristics Module

##### V.6.1.2.2 Product Characteristics Query Attributes

Table V.6-1 defines the Attributes of the Product Characteristics Query Information Model:

Table V.6-1. Attributes for the Product Characteristics Query Information Model

Description / Module | Tag | Matching Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | ---
Product Package Identifier | (0044,0001) | R | 1 | Shall be retrieved with Single Value Matching only.
Product Type Code Sequence | (0044,0007) | - | 1 |
>Code Value | (0008,0100) | - | 1 |
>Coding Scheme Designator | (0008,0102) | - | 1 |
>Code Meaning | (0008,0104) | - | 1 |
Product Name | (0044,0008) | - | 1 |
Product Expiration DateTime | (0044,000B) | - | 2 |
Product Parameter Sequence | (0044,0013) | - | 2 |
>Value Type | (0040,A040) | - | 1 |
>Concept Name Code Sequence | (0040,A043) | - | 1 |
>>Code Value | (0008,0100) | - | 1 |
>>Coding Scheme Designator | (0008,0102) | - | 1 |
>>Code Meaning | (0008,0104) | - | 1 |
>All other Attributes of Product Parameter Sequence |  | - | 1C | Conditional on value of Value Type (0040,A040); See PS3.3 Content Item Macro.
All other Attributes of Product Characteristics Module |  | - | 3 |

The Product Package Identifier (0044,0001) might not be globally unique and might conflict with other identifiers used within the scope of the institution.

### Note

The package identifiers are typically unique within the scope of the substance administration management systems. This is a warning that they are not UIDs.

#### V.6.1.3 Conformance Requirements

An implementation may conform to the Product Characteristics Query SOP Class as an SCU or an SCP. The Conformance Statement shall be in the format defined in PS3.2.

##### V.6.1.3.1 SCU Conformance

An implementation that conforms to the Product Characteristics Query SOP Class shall support queries against the Information Model described in Section V.6.1.2 using the baseline C-FIND SCU Behavior described in Section V.4.1.2.

An implementation that conforms to the Product Characteristics Query SOP Class as an SCU shall state in its Conformance Statement the Return Key Attributes it requests, and how those Attributes are used in the application.

An implementation that conforms to the Product Characteristics Query SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.

##### V.6.1.3.2 SCP Conformance

An implementation that conforms to the Product Characteristics Query SOP Class shall support queries against the Product Characteristics Query Information Model described in Section V.6.1.2 using the C-FIND SCP Behavior described in Section V.4.1.3.

An implementation that conforms to the Product Characteristics Query SOP Class as an SCP shall state in its Conformance Statement the Return Key Attributes that it supports.

An implementation that conforms to the Product Characteristics Query SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding responses.

#### V.6.1.4 SOP Class

The Product Characteristics Query SOP Class in the Substance Administration Service Class identifies the Product Characteristics Query Information Model, and the DIMSE-C operations supported. The following Standard SOP Class is identified:

Table V.6.1.4-1. Product Characteristics Query SOP Classes

SOP Class Name | SOP Class UID
--- | ---
Product Characteristics Query Information Model - FIND | 1.2.840.10008.5.1.4.41

### V.6.2 Substance Approval Query SOP Class

#### V.6.2.1 Substance Approval Query SOP Class Overview

The Substance Approval Query SOP Class defines an application-level class of service that allows a device at the point of care to obtain verification of the appropriateness of contrast agents and other drugs administered during a procedure, based on the substance label barcode and the patient ID. The response is an authorization to proceed, or a warning, or a contra-indication for presentation to the system operator.

The Substance Approval Query SOP class supports the following example use cases:

- Obtain verification that administration of a specific drug or contrast agent for an image acquisition is appropriate for the patient

- Obtain verification that the implantation of a specific device under imaging guidance is appropriate for the patient

The Substance Approval Query SOP Class does not specify the mechanism used by the SCP to verify such appropriateness of administration (e.g., by comparison to allergy information in the patient's electronic health record). The duration of validity of an approval beyond the time of the response is not defined by the Standard.

#### V.6.2.2 Substance Approval Query Information Model

##### V.6.2.2.1 E/R Model

The Substance Approval Query Information Model is represented by the Entity Relationship diagram shown in Figure V.6-2.

Figure V.6-2. Substance Approval E-R Diagram

Figure V.6-2

The Attributes of the Information Entities can be found in the following Modules in PS3.3.

- Patient Identification Module

- Patient Demographics Module

- Visit Identification Module

- Substance Administration Module

- Substance Approval Module

- Product Characteristics Module

Only selected Attributes of these Modules are used in the Substance Approval Query Information Model.

The Information Model is used in a bottom-up manner in the query; i.e., given a Product and a Patient, or alternatively a Product and a Visit, for a proposed Substance Administration act at the current time, find the Approval.

The Visit IE is included in the Information Model to support those institutions that identify patients (e.g., on a bar coded wristband) by Admission ID (i.e., the ID of the Visit), rather than Patient ID. This allows automation of query construction using a scan of the Admission ID. The Admission ID can be mapped to the Patient ID by the SCP for the purpose of the performing the query matching.

### Note

1. The Visit is identified by the Admission ID (0038,0010) Attribute, but in the "Model of the Real World for the Purpose of Modality-IS Interface" (see PS3.3), the Visit is subsidiary to the Patient; hence the Admission ID may only be unique within the context of the patient, not within the context of the institution. The use of the Admission ID Attribute to identify the Visit (and hence the Patient) is only effective if the Admission ID is unique within the context of the institution.

2. Certain institutions, e.g., ambulatory imaging centers that do not "admit" patients, may use the Imaging Service Request Identifier, or Accession Number, as an equivalent of the Admission ID. The SCU of this Query Service does not need to know the true origin or nature of the identifier, only that it is passed in the Query in the Admission ID (0038,0010) Attribute.

3. There is conceptually a datetime of administration Attribute of the Substance Administration act, which is implicitly assumed to be approximately the time of the query in this SOP Class.

4. There is conceptually a dose Attribute of the Product entity, which is the entire product identified by the bar code, and the request is for approval of administration of the entire product.

##### V.6.2.2.2 Substance Approval Query Attributes

Table V.6-2 defines the Attributes of the Substance Approval Query Information Model.

Table V.6-2. Attributes for the Substance Approval Query Information Model

Description / Module | Tag | Matching Key Type | Return Key Type | Remark/Matching Type
--- | --- | --- | --- | ---
Patient
Patient's Name | (0010,0010) | O | 2 |
Patient ID | (0010,0020) | R | 1 | Shall be retrieved with Single Value Matching only. One or both of Patient ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching Key in the Query
Issuer of Patient ID | (0010,0021) | O | 2 |
Issuer of Patient ID Qualifiers Sequence | (0010,0024) | O | 3 |
>All Attributes of the Issuer of Patient ID Qualifiers Sequence |  | O | 3 |
Patient's Birth Date | (0010,0030) | - | 2 |
Patient's Sex | (0010,0040) | - | 2 |
Visit
Admission ID | (0038,0010) | R | 2 | Shall be retrieved with Single Value Matching only. One or both of Patient ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching Key in the Query
Issuer of Admission ID Sequence | (0038,0014) | O | 3 |
>Local Namespace Entity ID | (0040,0031) | O | 1C | Required if Universal Entity ID (0040,0032) is not present; may be present otherwise
>Universal Entity ID | (0040,0032) | O | 1C | Required if Local Namespace Entity ID (0040,0031) is not present; may be present otherwise.
>Universal Entity ID Type | (0040,0033) | O | 1C | Required if Universal Entity ID (0040,0032) is present.
Product
Product Package Identifier | (0044,0001) | R | 1 | Shall be retrieved with Single Value Matching only. Shall be present as a Matching Key in the Query.
Substance Administration
Administration Route Code Sequence | (0054,0302) | R | 1 | Shall be present as a Matching Key in the Query.
>Code Value | (0008,0100) | R | 1 |
>Coding Scheme Designator | (0008,0102) | R | 1 |
>Code Meaning | (0008,0104) | - | 1 |
Approval
Substance Administration Approval | (0044,0002) | - | 1 |
Approval Status Further Description | (0044,0003) | - | 2 |
Approval Status DateTime | (0044,0004) | - | 1 |

One or both of Patient ID (0010,0020) and Admission ID (0038,0010) shall be present as a Matching Key in the Query.

Product Package Identifier (0044,0001) shall be present as a Matching Key in the Query. The Product Package Identifier might not be globally unique and might conflict with other identifiers used within the scope of the institution.

### Note

The package identifiers are typically unique within the scope of the substance administration management systems. This is a warning that they are not UIDs.

Administration Route Code Sequence (0054,0302) shall be present as a Matching Key in the Query, and a single Item shall be present in that Sequence with Code Value (0008,0100) and Coding Scheme Designator (0008,0102) as Matching Keys.

##### V.6.2.2.3 Substance Approval Query Responses

A Query response may have a status of Success or Failure (see Section V.4.1.1.4). A Failure Query response carries no semantics about the existence or status of approval of the Substance Administration.

A successful Query response will contain zero or one Pending response items. The case of zero Pending responses carries the semantics of no matching Approval Information Entity found, i.e., that the SCP cannot determine an approval, rather than that the substance administration is approved or disapproved. In this case a decision on substance administration needs to be made by the healthcare provider.

### Note

Zero Pending responses may occur due do inability of the SCP to match the patient ID, product ID or route of administration.

In the case of one Pending response, the matching Approval Information Entity will explicitly convey the Substance Administration Approval (0044,0002) value of APPROVED, WARNING, or CONTRA_INDICATED.

#### V.6.2.3 Conformance Requirements

An implementation may conform to the Substance Approval Query SOP Class as an SCU or an SCP. The Conformance Statement shall be in the format defined in PS3.2.

##### V.6.2.3.1 SCU Conformance

An implementation that conforms to the Substance Approval Query SOP Class shall support queries against the Information Model described in Section V.6.2.2 using the baseline C-FIND SCU Behavior described in Section V.4.1.2.

An implementation that conforms to the Substance Approval Query SOP Class as an SCU shall state in its Conformance Statement how the Query Attributes are used in the application, and how the application displays the returned Attributes, in particular the values of Substance Administration Approval (0044,0002) and Approval Status Further Description (0044,0003). It shall state how it indicates a Query response with zero Pending items, or a Failure status.

An implementation that conforms to the Substance Approval Query SOP Class as an SCU shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when encoding queries and interpreting responses.

##### V.6.2.3.2 SCP Conformance

An implementation that conforms to the Substance Approval Query SOP Class shall support queries against the Substance Approval Query Information Model described in Section V.6.2.2 using the C-FIND SCP Behavior described in Section V.4.1.3. It shall support all of the Attributes specified in the Information Model.

An implementation that conforms to the Substance Approval Query SOP Class as an SCP shall state in its Conformance Statement how it processes Required and Optional Matching Key Attributes. It shall state how it obtains the values for the Return Key Attributes.

An implementation that conforms to the Substance Approval Query SOP Class as an SCP shall state in its Conformance Statement how it makes use of Specific Character Set (0008,0005) when interpreting queries, performing matching and encoding responses.

#### V.6.2.4 SOP Class

The Substance Approval Query SOP Class in the Substance Administration Service Class identifies the Substance Approval Query Information Model, and the DIMSE-C operations supported. The following Standard SOP Class is identified:

Table V.6.2.4-1. Substance Approval Query SOP Classes

SOP Class Name | SOP Class UID
--- | ---
Substance Approval Query Information Model - FIND | 1.2.840.10008.5.1.4.42

Prev | Up | Next
V.5 Association Negotiation | Home | W Color Palette Storage Service Class