Материал: part17

- Standard -​

- Standard -​

J Handling of Identifying Parameters​ (Informative)​

ThisAnnexwasformerlylocatedinAnnexM“HandlingofIdentifyingParameters(Informative)”inPS3.4inthe2003andearlierrevisions​

of the Standard.​

J.1 Purpose of This Annex​

TheDICOMStandardwaspublishedin1993andaddressesmedicalimagescommunicationbetweenmedicalmodalities,workstations​ and other medical devices as well as data exchange between medical devices and the Information System (IS). DICOM defines SOP​ Instances with Patient, Visit and Study information managed by the Information System and allows to communicate the Attribute​ values of these objects.​

Since the publication of the DICOM Standard great effort has been made to harmonize the Information Model of the DICOM Standard​ with the models of other relevant standards, especially with the HL7 model and the CEN TC 251 WG3 PT 022 model. The result of​ these effort is a better understanding of the various practical situations in hospitals and an adaptation of the model to these situations.​ In the discussion of models, the definition of Information Entities and their Identifying Parameters play a very important role.​

The purpose of this Informative Annex is to show which identifying parameters may be included in Image SOP Instances and their​ related Modality Performed Procedure Step (MPPS) SOP Instance. Different scenarios are elucidated to describe varying levels of​ integration of the Modality with the Information System, as well as situations in which a connection is temporarily unavailable.​

Note​

In this Annex, "Image SOP Instance" is used as a collective term for all Composite Image Storage SOP Instances.​

The scenarios described here are informative and do not constitute a normative section of the DICOM Standard.​

J.2 Integrated Environment​

"Integrated" means in this context that the Acquisition Modality is connected to an Information System or Systems that may be an​ SCP of the Modality Worklist SOP Class or an SCP of the Modality Performed Procedure Step SOP Class or both. In the following​ description only the behavior of "Modalities" is mentioned, it goes without saying that the IS must conform to the same SOP Classes.​

TheModalityreceivesidentifyingparametersbyqueryingtheModalityWorklistSCPandgeneratesotherAttributevaluesduringimage​ generation. It is desirable that these identifying parameters be included in the Image SOP Instances as well as in the MPPS object​ in a consistent manner. In the case of a Modality that is integrated but unable to receive or send identifying parameters, e.g., link​ down, emergency case, the Modality may behave as if it were not integrated.​

The Study Instance UID is a crucial Attribute that is used to relate Image SOP Instances (whose Study is identified by their Study In-​ stance UID), the Modality PPS SOP Instance that contains it as a reference, and the actual or conceptual Requested Procedure (i.e.,​ Study) and related Imaging Service Request in the IS. An IS that manages an actual or conceptual Detached Study Management​ entity is expected to be able to relate this Study Instance UID to the SOP Instance UID of the Detached Study Management SOP In-​ stance, whether or not the Study Instance UID is provided by the IS or generated by the modality.​

For a detailed description of an integrated environment see the IHE Radiology Technical Framework. This document can be obtained​ at http://www.ihe.net/​

J.2.1 Modality Conforms to Modality Worklist and MPPS SOP Classes​

The modality may:​

•​N-CREATEaMPPSSOPInstanceandincludeitsSOPInstanceUIDintheImageSOPInstanceswithintheReferencedPerformed​ Procedure Step Sequence Attribute.​

•​Copy the following Attribute values from the Modality Worklist information into the Image SOP Instances and into the related MPPS​ SOP Instance:​

- Standard -​

•​Study Instance UID​

•​Referenced Study Sequence​

•​Accession Number​

•​Requested Procedure ID​

•​Scheduled Procedure Step ID​

•​Scheduled Procedure Step Description​

•​Scheduled Protocol Code Sequence​

•​Create the following Attribute value and include it into the Image SOP Instances and the related MPPS SOP Instance:​

•​Performed Procedure Step ID​

•​Include the following Attribute values that may be generated during image acquisition, if supported, into the Image SOP Instances​ and the related MPPS SOP Instance:​

•​Performed Procedure Step Start Date​

•​Performed Procedure Step Start Time​

•​Performed Procedure Step Description​

•​Study ID​

J.2.2 Modality Conforms Only to The Modality Worklist SOP Class​

The modality may:​

•​In the absence of the ability to N-CREATE a MPPS SOP Instance, generate a MPPS SOP Instance UID and include it into the​ Referenced Performed Procedure Step Sequence Attribute of the Image SOP Instances. A system that later N-CREATEs a MPPS​ SOP Instance may use this UID extracted from the related Image SOP Instances.​

•​Copy the following Attribute values from the Modality Worklist information into the Image SOP Instances:​

•​Study Instance UID​

•​Referenced Study Sequence​

•​Accession Number​

•​Requested Procedure ID​

•​Scheduled Procedure Step ID​

•​Scheduled Procedure Step Description​

•​Scheduled Protocol Code Sequence​

•​Create the following Attribute value and include it into the Image SOP Instances:​

•​Performed Procedure Step ID​

A system that later N-CREATEs a MPPS SOP Instance may use this Attribute value extracted from the related Image SOP Instances.​

•​Include the following Attribute values that may be generated during image acquisition, if supported, into the Image SOP Instances:​

•​Performed Procedure Step Start Date​

•​Performed Procedure Step Start Time​

- Standard -​

•​Performed Procedure Step Description​

•​Study ID​

AsystemthatlaterN-CREATEsaMPPSSOPInstancemayusetheseAttributevaluesextractedfromtherelatedImageSOPInstances.​

J.2.3 Modality Conforms Only to The MPPS SOP Class​

The modality may:​

•​N-CREATEaMPPSSOPInstanceandincludeitsSOPInstanceUIDintheImageSOPInstanceswithintheReferencedPerformed​ Procedure Step Sequence Attribute.​

•​Create the following Attribute values and include them in the Image SOP Instances and the related MPPS SOP Instance:​

•​Study Instance UID​

•​Performed Procedure Step ID​

•​Copy the following Attribute values, if available to the Modality, into the Image SOP Instances and into the related MPPS SOP In-​ stance:​

•​Accession Number​

•​Patient ID​

•​Patient's Name​

•​Patient's Birth Date​

•​Patient's Sex​

If sufficient identifying information is included, it will allow the Image SOP Instances and the MPPS SOP Instance to be later related​ to the Requested Procedure and the actual or conceptual Detached Study Management entity.​

•​Include the following Attribute values that may be generated during image acquisition, if supported, into the Image SOP Instances​ and the related MPPS SOP Instance:​

•​Performed Procedure Step Start Date​

•​Performed Procedure Step Start Time​

•​Performed Procedure Step Description​

•​Study ID​

J.3 Non-integrated Environment​

"Non-Integrated" means in this context that the Acquisition Modality is not connected to an Information System Systems, does not​ receiveAttributevaluesfromanSCPoftheModalityWorklistSOPClass,andcannotcreateaPerformedProcedureStepSOPInstance.​

The modality may:​

•​In the absence of the ability to N-CREATE a MPPS SOP Instance, generate a MPPS SOP Instance UID and include it into the​ Referenced Performed Procedure Step Sequence Attribute of the Image SOP Instances. A system that later N-CREATEs a MPPS​ SOP Instance may use this UID extracted from the related Image SOP Instances.​

•​Create the following Attribute values and include them in the Image SOP Instances:​

•​Study Instance UID​

•​Performed Procedure Step ID​

- Standard -​