Материал: part02

Внимание! Если размещение файла нарушает Ваши авторские права, то обязательно сообщите нам

Page 136​

DICOM PS3.2 2020a - Conformance​

Modality Worklist​

Image IOD​

MPPS IOD​

Requested Procedure ID​

>Requested Procedure ID​

>Requested Procedure ID​

Requested Procedure Description​

 

>Requested Procedure Description​

Scheduled Procedure Step ID​

>Scheduled Procedure Step ID​

>Scheduled Procedure Step ID​

ScheduledProcedureStepDescription​>Scheduled Procedure Step Description​

>Scheduled Procedure Step Description​

Scheduled Protocol Code Sequence​>Scheduled Protocol Code Sequence​

----​

----​

Performed Protocol Code Sequence​

Performed Protocol Code Sequence​

----​

Study ID​

Study ID​

----​

Performed Procedure Step ID​

Performed Procedure Step ID​

----​

Performed Procedure Step Start Date​

Performed Procedure Step Start Date​

----​

Performed Procedure Step Start Time​

Performed Procedure Step Start Time​

----​

Performed Procedure Step Description​

Performed Procedure Step Description​

----​

Comments on the Performed Procedure Step​CommentsonthePerformedProcedureStep​

----​

----​

Performed Series Sequence​

Scheduled Performing Physician's​

Performing Physician's Name​

>Performing Physician's Name​

Name​

 

 

RequestedProcedureCodeSequence​----​

Procedure Code Sequence​

----​

Referenced Study Component Sequence​

----​

----​

>Referenced SOP Class UID​

SOP Class UID​

----​

>Referenced SOP Instance UID​

SOP Instance UID​

----​

Protocol Name​

Protocol Name​

B.8.1.4 Coerced/Modified Fields​

The Modality Worklist AE will truncate attribute values received in the response to a Modality Worklist Query if the value length is​ longer than the maximum length permitted by the attribute's VR.​

B.8.2 Data Dictionary of Private Attributes​

The Private Attributes added to created SOP Instances are listed in the Table below. EXAMPLE-INTEGRATED-MODALITY reserves​ blocks of private attributes in groups 0009, 0019 and 0029. Further details on usage of these private attributes are contained in Sec-​ tion B.8.1.​

Table B.8.2-1. Data Dictionary of Private Attributes​

Tag​

Attribute Name​

VR​

VM​

Attribute​

 

 

 

 

Description​

(0009,00xx)​

Private Creator​

LO​

1​

EXINTMODMAKER​

(0009,xx01)​

Equipment UID​

UI​

1​

 

(0009,xx02)​

Service UID​

UI​

1​

 

(0019,00xx)​

Private Creator​

LO​

1​

EXINTMODMAKER​

(0019,xx10)​

Edge Enhancement Percent​

IS​

1​

 

(0019,xx20)​

Landmark​

IS​

1​

 

(0019,xx30)​

Pixel Shift Horizontal​

DS​

1​

 

(0019,xx40)​

Pixel Shift Vertical​

DS​

1​

 

(0029,00xx)​

Private Creator​

LO​

1​

EXINTMODMAKER​

(0029,xx40)​

Application Header Sequence​

SQ​

1​

 

- Standard -​

 

DICOM PS3.2 2020a - Conformance​

 

Page 137​

Tag​

Attribute Name​

VR​

VM​

Attribute​

 

 

 

 

Description​

(0029,xx41)​

Application Header Type​

CS​

1​

 

(0029,xx42)​

Application Header ID​

LO​

1​

 

(0029,xx43)​

Application Header Version​

LO​

1​

 

(0029,xx44)​

Application Header Data​

OB​

1​

 

(0029,xx50)​

Workflow Control Flags​

LO​

8​

 

(0029,xx51)​

Archive Management Flag - Keep Online​

CS​

1​

 

(0029,xx52)​

Archive Management Flag - Do Not Archive​

CS​

1​

 

B.8.3 Coded Terminology and Templates​

The Workflow AE is capable of supporting arbitrary coding schemes for Procedure and Protocol Codes. The contents of Requested​ Procedure Code Sequence (0032,1064) and Scheduled Protocol Code Sequence (0040,0008) supplied in Worklist Items will be​ mapped to Image IOD and MPPS attributes as described in Table B.8.1-31. During installation, a service technician will establish a​ mapping between the site-specific codes and the Protocol Names used internally to identify acquisition protocols.​

The contents of Anatomic Region Sequence (0008,2218) in generated images will be filled with an anatomic code selected by the​ user from a catalog. The default catalog of anatomic codes corresponds to CID 4009 “DX Anatomy Imaged” but can be extended​ using the Service/Installation Tool.​

The contents of Performed Procedure Step Discontinuation Reason Code Sequence (0040,0281) for a discontinued MPPS will be​ filled with a code selected by the user from a fixed list corresponding to CID 9300 “Procedure Discontinuation Reasons”.​

B.8.4 Grayscale Image Consistency​

The high resolution display monitor attached to EXAMPLEINTEGRATED-MODALITY can be calibrated according to the Grayscale​ Standard Display Function (GSDF). The Service/Installation Tool is used together with a luminance meter to measure the Character-​ istic Curve of the display system and the current ambient light. See the EXAMPLE-INTEGRATED-MODALITY Service Manual for​ detailsonthecalibrationprocedureandsupportedcalibrationhardware.TheresultofthecalibrationprocedureisaMonitorCorrection​ LUT that will be active within the display subsystem after a system reboot.​

B.8.5 Standard Extended / Specialized / Private SOP Classes​

No Specialized or Private SOP Classes are supported.​

B.8.5.1 X-Ray Radiofluoroscopic Image Storage SOP Class​

The X-Ray Radiofluoroscopic Image Storage SOP Class is extended to create a Standard Extended SOP Class by addition of​ standard and private attributes to the created SOP Instances as documented in Section B.8.1.​

B.8.6 Private Transfer Syntaxes​

No Private Transfer Syntaxes are supported.​

- Standard -​

Page 138​

DICOM PS3.2 2020a - Conformance​

- Standard -​

DICOM PS3.2 2020a - Conformance​

Page 139​

CConformanceStatementSampleDICOMRis​

Interface (Informative)​

Disclaimer:​

ThisdocumentisanexampleDICOMConformanceStatementforaproductthatsupportsDICOMSOPClassesfrequentlyassociated​ withaRadiologyInformationSystemorRIS.Theproductwhoseconformanceisbeingdocumented,DICOMRis,andthemanufacturer,​ Hospital Systems, are fictional.​

As stated in the annex title, this document is truly informative, and not normative. A conformance statement of an actual product might​ implement additional services and options as appropriate for its specific purpose. In addition, an actual product might implement the​ servicesdescribedinadifferentmannerand,forexample,withdifferentcharacteristicsand/orsequencingofactivities.Inotherwords,​ this conformance statement example does not intend to standardize a particular manner that a product might implement DICOM​ functionality.​

C.0 Cover Page​

Company Name: EXAMPLE RIS Products.​

Product Name: SAMPLE DICOMRis Interface​

Version: 1.0-rev. A.1​

Internal document number: 4226-xxx-yyy-zzz rev 1​

Date: YYYYMMDD​

C.1 Conformance Statement Overview​

Hospital Systems' DICOMRis is a suite of applications that implement a full-featured Radiology Information System (RIS). DICOMRis​ includes features typically associated with a RIS, including interfaces to various Hospital Information Systems, Patient Tracking,​ ResultsReporting,FilmTracking,ManagementReporting,PACSIntegration,etc.TheDICOMRisGUI-basedclientapplication,RisView,​ runs on a Windows 95/98/NT platform; the server platform is Digital Unix.​

As part of PACS Integration DICOMRis supports several DICOM Service Classes, using DICOMTool's DICOM Toolkit, to provide the​ following capabilities:​

Allowing Modalities to query for worklists of procedures to be performed and for patient and procedure demographics. DICOMRis​ processes these queries by directly accessing the DICOMRis database, which is automatically updated with appropriate data through​ the normal operations of the RIS.​

Updating the DICOMRis database in response to Procedure Step transactions initiated by Modalities as they perform examinations.​ Relevant data contained in these transactions may be viewed using RisView.​

Table C.1-1. Network Services​

SOP Classes​

User of Service (SCU)​

Provider of Service (SCP)​

Workflow Management​

 

 

Modality Worklist​

No​

Yes​

Modality Performed Procedure Step​

No​

Yes​

C.2 Table of Contents​

A table of contents shall be provided to assist readers in easily finding the needed information.​

- Standard -​

Page 140​

DICOM PS3.2 2020a - Conformance​

C.3 Introduction​

C.3.1 Revision History​

Table C.3.1-1. Revision History​

Document Version​

Revision Date​

Revision Author​

Revision Description​

1.1​

October 30, 2003​

WG 6​

Version for Final Text​

1.2​

August 30, 2007​

WG 6​

Revised Introduction​

C.3.2 Audience, Remarks, Terms and Definitions, Basics of DICOM Communication, Abbrevi-​ ations, References​

See example text in Section A.3.​

C.3.3 Additional References for This Example​

IHE Radiology Technical Framework, Revision 7.0, ACC/HIMSS/RSNA, 2006.​

Logical Observation Identifier Names and Codes (LOINC). Regenstrief Institute. Indianapolis. 2018.http://loinc.org/​

C.3.4 Additional Remarks and Definitions for This Example​

ThisdocumentisasampleDICOMConformanceStatementcreatedforDICOMPS3.2.Itistobeusedsolelyasanexampletoillustrate​ how to create a DICOM Conformance Statement for a departmental information system supporting DICOM Modality Worklist and​ Modality Performed Procedure Step Services. The subject of the document, DICOMRis, is a fictional product.​

DICOMRis Database The database that indexes procedures, orders and patients​

DICOMSRV DICOM MWL and MPPS application​

RisView DICOMRis' GUI-based application providing views into the DICOMRis' Database, reporting function, etc.​

- Standard -​