DICOM PS3.20 2019b - Imaging Reports using HL7 Clinical Document Architecture

8.2.3 inFulfillmentOf/Order and @ID (Current)
Prev | 8.2 Imaging Header | Next

### 8.2.3 inFulfillmentOf/Order and @ID

An inFulfillmentOf element represents the Placer Order. There may be more than one inFulfillmentOf element in the case where a single report is fulfilling multiple orders. There SHALL be one inFulfillmentOf/order for each distinct Order associated with the report.

In each inFulfillmentOf/order there SHALL be one order/id for the Placer Order Number (0040,2016). There SHALL be one order/ps3-20:accessionNumber for the DICOM Accession Number (0008,0050) associated with the order. The ps3-20:accessionNumber SHALL be Data Type II; it SHALL have a UID root attribute identifying its assigning authority, and the DICOM Accession Number SHALL be in the extension attribute.

Example 8.2.3-1. inFulfillmentOf example

    <xs:schema ...
        xmlns:ps3-20="urn:dicom-org:ps3-20"
        ...
    </xs:schema>
    <inFulfillmentOf>
        <order>
            <id extension="089-927851" root="2.16.840.1.113883.19.4.33"/>
            <!-- {extension} =
              Placer Order Number/Imaging Service Request (0040,2016) {root} =
              Order Placer Identifier Sequence (0040,0026) > Universal Entity ID (0040,0032) -->
            <ps3-20:accessionNumber extension="10523475" root="2.16.840.1.113883.19.4.27" />
            <!-- {extension}=
              Accession Number (0008,0050) {root} =
              Issuer of Accession Number Sequence (0008,0051) > Universal Entity ID (0040,0032) -->
            <code code="RPID24"
                displayName="CT HEAD WITH IV CONTRAST"
                codeSystem="2.16.840.1.113883.6.256"
                codeSystemName="RadLex Playbook">
            <!-- Ordered Procedure Code is
              Requested Procedure Code Sequence (0032,1064) -->
        </order>
    </inFulfillmentOf>

Prev | Up | Next
8.2.2 Physician of Record Participant | Home | 8.2.4 documentationOf/serviceEvent

DICOM PS3.20 2019b - Imaging Reports using HL7 Clinical Document Architecture