CP-1743 Update Conformance Statement example to be consistent with IHE Scheduled Workflow Status Letter Ballot Date of Last Update 2018/01/23 Person Assigned David Clunie Submitter Name Vladimir Kharam Submission Date 2017/08/23 Correction Number CP-1743 Log Summary: Update Conformance Statement example to be consistent with IHE Scheduled Workflow Name of Standard PS3.2 Rationale for Correction: IHE SWF specifies that Requested Procedure Code be mapped from OBR-44, not OBR-4. The example in PS3.2 Annex C uses OBR-4. Also CPT-4 is mentioned as the codes to use, and this is inappropriate, since it is a billing not ordering scheme. Suggest LOINC instead (which is harmonized withg RadLex and the preferred wire encoding). See also the IHE Code Mapping WP . Correction Wording: <informaltable rules="all" frame="box"> <tr> <td> <para><emphasis role="italic">Amend DICOM PS3.2 as follows (changes to existing text are bold and <emphasis role="bold"><emphasis role="underline">underlined</emphasis></emphasis> for additions and <emphasis role="bold"><emphasis role="strikethrough">struckthrough</emphasis></emphasis> for removals):</emphasis></para> </td> </tr> </informaltable> <section label="C.4.2.1.4.1" xml:id="sect_C.4.2.1.4.1"> <title>Activity - Configured AE Requests MWL Query
Description and Sequencing of Activities When Modality Worklist SCUs query DICOMSRV the queries run against the Scheduled Procedure Step Worklist (referred to hereafter as the 'SPS Worklist' or 'Worklist') in the DICOMRis database. There is a configurable mapping between the Universal Service ID contained in the HL7 Order messages (see ) and one or more Requested Procedures within the DICOMRis database. A Requested Procedure may, in turn, map to 1 or more Scheduled Procedure Steps though the relation is usually 1-to-1. This mapping is also site-configurable. The relation between Accession Number (0008,0050) and Requested Procedure ID (0040,1001) is 1-to-1 within DICOMRis and these attributes have the same value in all MWL responses. Scheduled Procedure Step entries are added and removed from the Worklist as follows:
Annexes
IOD Contents
Attribute Mapping The mapping between attributes received via HL7 from the HIS and those supplied in Modality Worklist is configurable. The default mapping is contained in the table below. Empty cells indicate that there is no mapping for the specific attribute
HL7/Modality Worklist Attribute Mapping
DICOM Attribute DICOM Tag HL7 Attribute Name HL7 Segment Notes
... ... ...
Requested Procedure Code Sequence (0032,1064)
>Code Value (0008,0100) Universal Service Id ORM OBR:44 The value in the HL7 attribute is mapped to one or more procedure codes in the DICOMRis database. The mapping is configurable
>Coding Scheme Designator (0008,0102) Universal Service Id ORM OBR:44 Maps to a site-defined Coding Scheme, the CPTLOINC Coding Scheme or the DICOMRis internal Coding Scheme
>Code Meaning (0008,0008) DICOMRis generated
... ... ...
Coded Terminology and Templates DICOMRis's usage of Coding Schemes is specified in the table below. This table lists the Coding Schemes used by DICOMRis for attributes it originates. Usage of Controlled Terminology by Applications sending IODs to DICOMRis is discussed in the relevant SOP Specific Conformance sections above. The Procedure and Protocol Codes in the DICOMRis database can be exported to files and transferred across the network using the Configuration Utility. This allows Modalities to access and incorporate these codes if so desired.
DICOMRis Controlled Terminology Usage
SOP Class/Service Attribute Name Tag Baseline Context ID Coding Scheme Remarks
Scheduled Procedure Step Module
MWL/ C-FIND >Scheduled Protocol Code Sequence (0040,0008) None CPT-4LOINC, DICOMRis Procedure, site-supplied procedure codes or site-supplied protocol codes At the option of the site, DICOMRis may be configured to associate CPT-4LOINC, DICOMRis Internal codes or site-supplied procedure codes with the various procedures represented in their Item master file. The configured procedure code will be passed in this attribute unless the site has supplied and configured protocol codes to be associated with the respective procedures in addition to procedure codes. In this case the configured protocol code will be passed
Requested Procedure Module
Requested Procedure Code Sequence (0032,1064) None CPT-4LOINC, DICOMRis Procedure, site-supplied procedure codes See remarks for Scheduled Protocol Code Sequence (0040,0040). The difference is that a procedure code is always passed in this attribute rather than a protocol code