DICOM PS3.3 2019c - Information Object Definitions

C.4.12 Imaging Service Request Module (Current)
Prev | C.4 Study Modules | Next

### C.4.12 Imaging Service Request Module

Table C.4-12. Imaging Service Request Module Attributes

Attribute Name | Tag | Attribute Description
--- | --- | ---
Imaging Service Request Comments | (0040,2400) | User-defined comments on the Imaging Service Request. ### Note This Attribute is intended to transmit non-structured information, which can be displayed to the operator of the equipment (e.g., Modality).
Requesting Physician | (0032,1032) | Name of the physician who requested the Imaging Service Request.
Requesting Physician Identification Sequence | (0032,1031) | Identification of the physician who requested the Imaging Service Request. Only a single Item shall be included in this Sequence.
>Include Table 10-1 “Person Identification Macro Attributes Description” | ### Note The Person's Telecom Information (0040,1104) Attribute in this Sequence may be treated as equivalent to HL7v2 field ROL-12 associated with the requesting physician identified in ORC-12 or OBR-16.
Referring Physician's Name | (0008,0090) | Name of the Patient's referring physician for this Imaging Service Request.
Referring Physician Identification Sequence | (0008,0096) | Identification of the Patient's referring physician. Only a single Item shall be included in this Sequence.
>Include Table 10-1 “Person Identification Macro Attributes Description” | ### Note The Person's Telecom Information (0040,1104) Attribute in this Sequence may be treated as equivalent to HL7v2 field ROL-12 associated with the referring physician identified in PV1-8.
Requesting Service | (0032,1033) | Institutional department, unit or service where the request initiated. See Note 3.
Requesting Service Code Sequence | (0032,1034) | Institutional department, unit or service where the request initiated. Equivalent to HL7 v2.x ORC-17. See Note 3. Only a single Item shall be included in this Sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes” | DCID 7030 “Institutional Departments, Units and Services”.
Accession Number | (0008,0050) | A departmental IS generated number that identifies the order for the Imaging Service Request.
Issuer of Accession Number Sequence | (0008,0051) | Identifier of the Assigning Authority that issued the Accession Number. Only a single Item shall be included in this Sequence.
>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
Issue Date of Imaging Service Request | (0040,2004) | Date on which the Imaging Service Request was issued by the requester.
Issue Time of Imaging Service Request | (0040,2005) | Time at which the Imaging Service Request was issued by the requester.
Placer Order Number / Imaging Service Request | (0040,2016) | The order number assigned to the Imaging Service Request by the party placing the order.
Order Placer Identifier Sequence | (0040,0026) | Identifier of the Assigning Authority that issued the Placer Order Number. Only a single Item shall be included in this Sequence.
>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
Filler Order Number / Imaging Service Request | (0040,2017) | The order number assigned to the Imaging Service Request by the party filling the order.
Order Filler Identifier Sequence | (0040,0027) | Identifier of the Assigning Authority that issued the Filler Order Number. Only a single Item shall be included in this Sequence.
>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
Order Entered By | (0040,2008) | The person who entered the Imaging Service Request into an Information System. ### Note This Attribute may be treated as equivalent to HL7v2 field ORC-10.
Order Enterer's Location | (0040,2009) | The location at which the Imaging Service Request was entered. ### Note This Attribute may be treated as equivalent to HL7v2 field ORC-13.
Order Callback Phone Number | (0040,2010) | Telephone Number at which additional information can be retrieved.
Order Callback Telecom Information | (0040,2011) | The telecommunication contact information, including telephone, email, or other telecom addresses, at which additional information about the order can be retrieved. ### Note This Attribute may have internal format or structure in accordance with local agreement or profile. It is recommended that this Attribute be treated as equivalent to HL7v2 fields ORC-12 and OBR-17, and be formatted in accordance with the HL7v2 XTN data type (without escapes for HL7 message structure reserved characters).
Admission ID | (0038,0010) | Identification number of the Visit as assigned by the healthcare provider ### Note Visit and Admission are used interchangeably here. In the broader sense, an admission is a type of visit at an institution where there is an admission process for patients.
Issuer of Admission ID Sequence | (0038,0014) | Identifier of the Assigning Authority that issued the Admission ID. Only a single Item shall be included in this Sequence.
>Include Table 10-17 “HL7v2 Hierarchic Designator Macro Attributes” |
Reason for Visit | (0032,1066) | Reason(s) for this visit by the patient to the facility or provider.
Reason for Visit Code Sequence | (0032,1067) | Coded reason(s) for this visit by the patient to the facility or provider. ### Note If an HL7 message is available with a PV2 segment corresponding to this visit, potential codes may be found in Admit Reason PV2-3. One or more Items are permitted in this Sequence.
>Include Table 8.8-1 “Code Sequence Macro Attributes” | No Baseline CID is defined.

### Note

1. Attributes (0040,2016) and (0040,2017) Placer Order Number and Filler Order Number/Imaging Service Request are intended to convey the corresponding order numbers as defined in HL7, in the case where interoperability with an HL7 environment is the objective.

2. Attributes (0040,2001), (0040,2006) and (0040,2007) were previously defined in DICOM. They are now retired (see PS3.3-1998).

3. Both Requesting Service (0032,1033) and Requesting Service Code Sequence (0032,1034) are defined in this table; the latter is preferred, but the former may be copied from an HL7 message whether or not there is also the ability to map it to a coded form (e.g., with only ORC-17 component 1 valued).

Prev | Up | Next
C.4.11 Requested Procedure Module | Home | C.4.13 Performed Procedure Step Relationship

DICOM PS3.3 2019c - Information Object Definitions