Q.4.3 Relevant Patient Information Model SOP Classes
Prev | Q.4 DIMSE-C C-FIND Service | Next

### Q.4.3 Relevant Patient Information Model SOP Classes

#### Q.4.3.1 Relevant Patient Information Model

In order to serve as a Service Class Provider (SCP) of one or more Relevant Patient Information Model SOP Classes, a DICOM Application Entity (AE) possesses relevant information about patients. This information is organized into a Relevant Patient Information Model.

The SOP Classes are composed of both the Information Model and a DIMSE-C Service Group.

##### Q.4.3.1.1 E/R Model

The E/R Model consists of Patient and Structured Information, with no relationship to other Information Entities in the DICOM Information model.

Figure Q.4-1. Relevant Patient Information E/R Model

The Patient IE includes the Attributes of the Patient Identification and Patient Demographics Modules.

The Structured Information IE includes Attributes that are not inherently related to a real-world entity, but are interpreted through their coded content. This includes the Attributes of the Structured Document Content Module, which in the case of the Relevant Patient Information Query Service has its content constrained by specified templates to convey patient related information. Also included in the Structured Information IE are Attributes of the SOP Common and Common Instance Reference Modules that support the interpretation of coded data, or support access to referenced information objects identified in the coded data.

##### Q.4.3.1.2 Relevant Patient Information Attributes

Table Q.4-1 defines the Attributes of the Relevant Patient Information Model:

Table Q.4-1. Attributes for the Relevant Patient Information Model

Description / Module | Tag | Matching Key Type | Return Key Type | Remark / Matching Type
--- | --- | --- | --- | ---
Patient
Patient's Name | (0010,0010) | - | 1 |
Patient ID | (0010,0020) | R | 1 | Shall be present in the Request Identifier. Shall be retrieved with Single Value Matching. ### Note Since only one response is expected, this is a unique key.
Issuer of Patient ID | (0010,0021) | R | 2 | Shall be retrieved with Single Value Matching. In situations where there are multiple issuers, this key constrains matching of Patient ID (0010,0020) to a domain in which the Patient ID (0010,0020) is unique.
Patient's Birth Date | (0010,0030) | - | 2 |
Patient's Sex | (0010,0040) | - | 2 |
All other Attributes of the Patient Identification Module |  | - | 3 |
All other Attributes of the Patient Demographic Module |  | - | 3 |
Structured Information (SR Document Content Module)
Observation DateTime | (0040,A032) | - | 1 |
Value Type | (0040,A040) | - | 1 | See Section Q.4.3.1.2.1.
Concept Name Code Sequence | (0040,A043) | - | 1 | See Section Q.4.3.1.2.1.
>Code Value | (0008,0100) | - | 1 |
>Coding Scheme Designator | (0008,0102) | - | 1 |
>Coding Scheme Version | (0008,0103) | - | 1C | Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously.
>Code Meaning | (0008,0104) | - | 1 |
>All other Attributes of the Concept Name Code Sequence |  |  |  |
Content Sequence | (0040,A730) | - | 2 | See Section Q.4.3.1.2.1.
>All Attributes of the Content Sequence |  | - | - | Content Items as provided by the SCP. Requirements on Content Item Attribute Types shall be in accordance with the definitions in the SR Document Content Module.
HL7 Structured Document Reference Sequence | (0040,A390) | - | 1C |
>Referenced SOP Class UID | (0008,1150) | - | 1 |
>Referenced SOP Instance UID | (0008,1155) | - | 1 |
>HL7 Instance Identifier | (0040,E001) | - | 1 |
>Retrieve URI | (0040,E010) | - | 3 |
Structured Information (Common Instance Reference Module)
Studies Containing Other Referenced Instances Sequence | (0008,1200) | - | 1C | Required if Content Sequence (0040,A390) includes Content Items that reference SOP Instances that use the Patient/Study/Series/Instance information model.
>Referenced Series Sequence | (0008,1115) | - | 1 |
>>Series Instance UID | (0020,000E) | - | 1 |
>>Referenced Instance Sequence | (0008,114A) | - | 1 |
>>>Referenced SOP Class UID | (0008,1150) | - | 1 |
>>>Referenced SOP Instance UID | (0008,1155) | - | 1 |

The Attributes in Table Q.4-2 are not part of the Information Model; their inclusion in the C-FIND request and response identifier are governed by rules in sections Section Q.2.1.1.3.1 and Section Q.2.1.1.3.2, respectively.

Table Q.4-2. Additional C-FIND Identifier Attributes

Attribute Name | Tag | Type in Request Identifier | Type in Response Identifier | Remark
--- | --- | --- | --- | ---
Content Template Sequence | (0040,A504) | 1 | 1 |
>Mapping Resource | (0008,0105) | 1 | 1 |
>Template Identifier | (0040,DB00) | 1 | 1 |
Specific Character Set | (0008,0005) | 1C | 1C | Required if expanded or replacement character sets are used. See Section Q.2.1.1.3,

##### Q.4.3.1.2.1 Relevant Patient Information Attribute Descriptions

Concept Name Code Sequence (0040,A043) in a C-FIND Response shall have one sequence item that identifies the Root node concept of the returned structure. This shall be the same as the Concept Name of the first row of the template identified in the Content Template Sequence (0040,A504) in the Identifier. The Concept Name Code Sequence (0040,A043) shall always be sent zero length in the Request Identifier.

The Value Type (0040,A040) applies to the Concept Name Code Sequence (0040,A043), and shall be the same as the Value Type (0040,A040) of the first row of the template identified in the Content Template Sequence (0040,A504) in the Identifier.

The Content Sequence (0040,A730) is a potentially recursively nested Sequence of Items, as described in PS3.3, SR Document Content Module. The Content Sequence shall always be sent zero length in the Request Identifier. The Content Sequence in the data set of the Response shall contain the content items of the requested template.

Prev | Up | Next
Q.4.2 Service Definition | Home | Q.4.3.2 Conformance Requirements