The. Worklist is persisted to non-volatile memory so that it can be accessed during portable exams. Both manual and automatic queries are supported. Automatic ...
Both manual and automatic queries are supported. ... Table 3-27 specifies the Matching Key attributes used by Automatic Worklist C-FIND requests and manual Update Worklist...
· 21919 30th Dr. SE, Bothell, WA 98021-3904 USA · Telephone 1.425.951.1200 · Facsimile 1.425.951.1201 · www.sonosite.com
Document Number: Revision: Title:
D25306
B
SonoSite PX DICOM Conformance Statement
CHANGE HISTORY: Revision B A
Description of Change Remove references to Ultrasound (Retired) SOP Class Initial release.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 1 of 48
TABLE OF CONTENTS
1 INTRODUCTION .............................................................................................................................................. 7 1.1 DICOM BACKGROUND........................................................................................................................................7 1.2 DEFINITIONS ...................................................................................................................................................... 7 1.3 REFERENCE DOCUMENTS ...................................................................................................................................... 8
2 IMPLEMENTATION MODEL............................................................................................................................. 9 2.1 APPLICATION DATA FLOW DIAGRAM .................................................................................................................... 10 2.2 FUNCTIONAL DEFINITIONS OF AES .......................................................................................................................11 2.3 SEQUENCING OF REAL-WORLD ACTIVITIES ............................................................................................................ 13
3 AE SPECIFICATIONS ...................................................................................................................................... 15 3.1 STORE AE - SPECIFICATION ............................................................................................................................... 15 3.1.1 Association Establishment Policies ......................................................................................................15 3.1.1.1 General............................................................................................................................................................. 15 3.1.1.2 Number of Associations ................................................................................................................................... 15 3.1.1.3 Asynchronous Nature....................................................................................................................................... 15 3.1.1.4 Implementation Identifying Information ......................................................................................................... 15 3.1.2 Association Initiation by Real-World Activity.......................................................................................15 3.1.2.1 Association Initiation by: Archive Exam ........................................................................................................... 16 3.1.2.2 Association Initiation By: Image Acquisition .................................................................................................... 16 3.1.2.3 Association Initiation by: Review Archive......................................................................................................... 16 3.1.2.4 Association Initiation by: Get Status ................................................................................................................ 16 3.1.3 Proposed Presentation Contexts to an Archiver ..................................................................................17 3.1.3.1 Verification SOP Class....................................................................................................................................... 18 3.1.3.2 Ultrasound Image Storage SOP Class ............................................................................................................... 18 3.1.3.3 Ultrasound Multi-Frame Image Storage SOP Class........................................................................................... 19 3.1.3.4 Secondary Capture Image Storage SOP Class ................................................................................................... 19 3.1.3.5 Basic Text SR Storage SOP Class ....................................................................................................................... 20 3.1.3.6 Comprehensive SR Storage SOP Class .............................................................................................................. 20 3.1.4 Common Composite Image IOD Module..............................................................................................21 3.1.4.1 Patient Module ................................................................................................................................................ 21 3.1.4.2 General Study Module ..................................................................................................................................... 22 3.1.4.3 Patient Study Module....................................................................................................................................... 22 3.1.4.4 General Series Module ..................................................................................................................................... 23 3.1.4.5 General Equipment Module ............................................................................................................................. 23 3.1.4.6 SC Equipment Module...................................................................................................................................... 24 3.1.4.7 General Image Module..................................................................................................................................... 24 3.1.4.8 Image Pixel Module.......................................................................................................................................... 25 3.1.4.9 Cine Module ..................................................................................................................................................... 25 3.1.4.10 Multi-frame Module......................................................................................................................................... 25 3.1.4.11 US Region Calibration Module ......................................................................................................................... 25 3.1.4.12 US Image Module ............................................................................................................................................. 26 3.1.4.13 VOI LUT Module ............................................................................................................................................... 27 3.1.4.14 SOP Common Module ...................................................................................................................................... 27 3.1.4.15 SR Document Series Module ............................................................................................................................ 27 3.1.4.16 SR Document General Module ......................................................................................................................... 27 3.1.4.17 SR Document Content Module......................................................................................................................... 28 3.1.5 Store AE Behavior to C-Store Status.....................................................................................................28 3.2 STORAGE COMMITMENT AE SPECIFICATION........................................................................................................28 3.2.1 Association Establishment Policies ......................................................................................................29 3.2.1.1 General............................................................................................................................................................. 29 3.2.1.2 Number of Associations ................................................................................................................................... 29 3.2.1.3 Asynchronous Nature....................................................................................................................................... 29 3.2.1.4 Implementation Identifying Information ......................................................................................................... 29 3.2.1.5 SCU Behavior.................................................................................................................................................... 29 3.2.2 Proposed Presentation Contexts to a Storage Commitment Server ....................................................30
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 2 of 48
3.2.2.1 Storage Commitment Push Model SOP Class .................................................................................................. 30 3.2.2.2 Verification SOP Class....................................................................................................................................... 30 3.2.3 Storage Commitment Attributes..........................................................................................................30 3.3 MODALITY WORKLIST AE SPECIFICATION ........................................................................................................... 31 3.3.1 Association Establishment Policies ......................................................................................................31 3.3.1.1 General............................................................................................................................................................. 31 3.3.1.2 Number of Associations ................................................................................................................................... 32 3.3.1.3 Asynchronous Nature....................................................................................................................................... 32 3.3.1.4 Implementation Identifying Information ......................................................................................................... 32 3.3.2 Association Initiation by Real-World Activity.......................................................................................32 3.3.2.1 Association Initiation by: Update Worklist ....................................................................................................... 32 3.3.2.2 Association Initiation by: Worklist Query ......................................................................................................... 32 3.3.2.3 Association Initiation by: Automatic Worklist Query ....................................................................................... 32 3.3.2.4 Association Initiation by: Get Status ................................................................................................................ 32 3.3.3 Proposed Presentation Contexts to a Worklist Server .........................................................................33 3.3.3.1 Modality Worklist Information Model FIND SOP Class.................................................................................. 33 3.3.3.2 Verification SOP Class....................................................................................................................................... 33 3.3.4 Modality Worklist Attributes ...............................................................................................................33 3.3.4.1 Broad Worklist Query Matching Key Attributes ............................................................................................... 33 3.3.4.2 Patient Based Query Matching Key Attributes ................................................................................................. 33 3.3.4.3 Return Key Attributes....................................................................................................................................... 34 3.3.5 Worklist AE Behavior to C-FIND Status ................................................................................................35 3.4 MODALITY PERFORMED PROCEDURE STEP (MPPS) AE SPECIFICATION .................................................................... 35 3.4.1 Association Establishment Policies ......................................................................................................35 3.4.1.1 General............................................................................................................................................................. 36 3.4.1.2 Number of Associations ................................................................................................................................... 36 3.4.1.3 Asynchronous Nature....................................................................................................................................... 36 3.4.1.4 Implementation Identifying Information ......................................................................................................... 36 3.4.2 Proposed Presentation Contexts to an MPPS Server ...........................................................................36 3.4.2.1 MPPS SOP Class ............................................................................................................................................... 36 3.4.2.2 Verification SOP Class....................................................................................................................................... 36 3.4.3 MPPS Information Model Attributes....................................................................................................36 3.5 MEDIA EXPORT AE SPECIFICATION....................................................................................................................38 3.5.1 Introduction .........................................................................................................................................38 3.5.2 Implementation Model ........................................................................................................................38 3.5.2.1 Application Data Flow ...................................................................................................................................... 39 3.5.2.2 Functional Definition of the AE ........................................................................................................................ 39 3.5.2.3 Sequencing of Real-World Activiities ............................................................................................................... 39 3.5.2.4 File Meta Information Options (see PS 3.10) ................................................................................................... 39 3.5.3 AE Specifications ..................................................................................................................................40 3.5.3.1 File Meta Information for the Application Entity ............................................................................................. 40 3.5.3.2 Real-World Activities........................................................................................................................................ 40 3.5.4 Augmented and Private Application Profiles .......................................................................................40 3.5.5 Media Configuration ............................................................................................................................41 3.5.6 Media Storage SOP Class .....................................................................................................................41 3.5.7 Information Module Definitions...........................................................................................................41 3.5.7.1 File-set Identification Module .......................................................................................................................... 42 3.5.7.2 Directory Information Module ......................................................................................................................... 42
4 COMMUNICATION PROFILES ........................................................................................................................ 44 4.1 TCP/IP STACK .................................................................................................................................................44
5 EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS ........................................................................................ 45 5.1 PRIVATE TRANSFER SYNTAXES ............................................................................................................................. 45
6 CONFIGURATION.......................................................................................................................................... 46 6.1 AE TITLE/PRESENTATION ADDRESS MAPPING........................................................................................................46 6.2 CONFIGURABLE PARAMETERS..............................................................................................................................46
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 3 of 48
6.2.1 6.2.2 6.2.3
Sonosite PX Configurable Parameters per Network Location ..............................................................46 Configurable Parameters per Remote Device Instance........................................................................46 Other Configurable Parameters ...........................................................................................................47
7 SUPPORT OF EXTENDED CHARACTER SETS ................................................................................................... 48
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 4 of 48
Figure 2-1 Figure 2-2 Figure 2-3 Figure 3-1 Figure 3-2
LIST OF FIGURES
Implementation Model........................................................................................................................10 Sequencing Constraints - "During the Exam" Configuration................................................................13 Sequencing Constraints - "End of Exam" Configuration ......................................................................14 Media Export Data Flow ......................................................................................................................39 Sonosite PX Directory Entity Relationship Diagram.............................................................................41
LIST OF TABLES
Table 1-1 NETWORKING SERVICES ................................................................................................................................6 Table 3-1 Store AE SOP Class Support .........................................................................................................................15 Table 3-2 Store AE Proposed Presentation Contexts to an Archiver ...........................................................................17 Table 3-3 US Image IOD Modules ................................................................................................................................18 Table 3-4 US Multi-Frame Image IOD Modules ...........................................................................................................19 Table 3-5 SC Image IOD Modules.................................................................................................................................19 Table 3-6 Patient Module Attributes ...........................................................................................................................21 Table 3-7 General Study Module Attributes ................................................................................................................22 Table 3-8 Patient Study Module Attributes .................................................................................................................22 Table 3-9 General Series Module Attributes................................................................................................................23 Table 3-10 General Equipment Module Attributes .....................................................................................................24 Table 3-11 SC Equipment Module Attributes ..............................................................................................................24 Table 3-12 General Image Module Attributes .............................................................................................................24 Table 3-13 Image Pixel Module Attributes ..................................................................................................................25 Table 3-14 Cine Module Attributes..............................................................................................................................25 Table 3-15 Multi-frame Module Attributes .................................................................................................................25 Table 3-16 US Region Calibration Attributes ...............................................................................................................26 Table 3-17 US Image Module Attributes......................................................................................................................26 Table 3-18 VOI LUT Module Attributes........................................................................................................................27 Table 3-19 SOP Common Module Attributes...............................................................................................................27 Table 3-20 Store AE Behavior to C-Store Status ..........................................................................................................28 Table 3-21 Storage Commitment AE SOP Class Support..............................................................................................28 Table 3-22 Storage Commitment AE Proposed Presentation Contexts.......................................................................30 Table 3-23 Storage Commitment Request - Action Information .................................................................................30 Table 3-24 Storage Commitment Result Event Information.....................................................................................31 Table 3-25 Modality Worklist AE SOP Class Support ...................................................................................................31 Table 3-26 Modality Worklist AE Proposed Presentation Contexts to a Worklist Server............................................33 Table 3-27 Broad Worklist Query Matching Key Attributes .......................................................................................33 Table 3-28 Patient Based Query Matching Key Attributes ..........................................................................................33 Table 3-29 Return Key Attributes ................................................................................................................................34 Table 3-30 Worklist AE Behavior to C-FIND Status ......................................................................................................35 Table 3-31 MPPS AE SOP Class Support.......................................................................................................................35 Table 3-32 MPPS AE Proposed Presentation Contexts ................................................................................................36 Table 3-33 MPPS SOP Class N-CREATE and N-SET Attributes ......................................................................................36 Table 3-34 SOP Classes and Transfer Syntaxes for Media Export ................................................................................40 Table 3-35 Basic Directory IOD Modules .....................................................................................................................41 Table 3-36 File-Set Identification Module....................................................................................................................42 Table 3-37 Directory Information Module...................................................................................................................42 Table 3-38 PATIENT KEYS.............................................................................................................................................42 Table 3-39 STUDY KEYS ................................................................................................................................................43 Table 3-40 SERIES KEYS................................................................................................................................................43 Table 3-41 IMAGE KEYS ...............................................................................................................................................43
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 5 of 48
Conformance Statement Overview
The Sonosite PX Ultrasound System implements the necessary DICOM services to download work lists from an information system, save acquired images to a network storage device and request storage commitment for them, print to a networked hardcopy device, inform an information system of exam status via MPPS, and store DICOM files onto removable media.
Table 1-1 provides an overview of the network services supported by the Sonosite PX Ultrasound System.
Table 1-1 NETWORKING SERVICES
NETWORKING SOP CLASSES
Ultrasound Image Storage Ultrasound Multi-frame Image Storage Secondary Capture Image Storage Comprehensive SR Storage Basic Text SR Storage
Modality Worklist Storage Commitment Modality Performed Procedure Step
Basic Grayscale Print Management Basic Color Print Management
Verification
USER OF SERVICE (SCU)
TRANSFER
Yes Yes Yes Yes Yes
WORKFLOW MANAGEMENT
Yes Yes Yes
PRINT MANAGEMENT
Yes Yes
GENERAL
Yes
PROVIDER OF SERVICE (SCP)
No No No No No
No No No
No No
Yes
Table 1.1-2 provides an overview of the media storage services supported by the Sonosite PX Ultrasound System.
Table 1.1-2
MEDIA STORAGE SERVICES
SOP CLASSES
ROLE
Media Storage Directory Stroage
FSC
Ultrasound Image Storage
FSC
Ultrasound Multi-frame Image Storage
FSC
Comprehensive SR Storage
FSC
Basic Text SR Storage
FSC
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 6 of 48
1 INTRODUCTION
This document describes the Sonosite PX® Ultrasound System's conformance to the ACR-NEMA DICOM (Digital Imaging and Communications in Medicine) standard and satisfies the DICOM requirement for a vendor conformance specification.
The Sonosite PX system is an ultrasound imaging device. The DICOM options of the Sonosite PX system provide a means to query the Information System for scheduled procedures using Modality Worklist, send procedure status messages to RIS via MPPS, send images to storage servers and removable USB media, and request Storage Commitment for images stored to PACS.
Throughout this document DICOM storage servers will be referred to as archivers. For a device to be classified as an archiver it must be capable of receiving DICOM store commands. Archivers are primarily comprised of PACS.
This document is written with respect to ACR-NEMA DICOM version number 3.1 - 2007.
1.1 DICOM BACKGROUND
The DICOM information exchange specification provides a definitive structure of commands and information that allow for the inter-communication of medical imaging devices. Developed by the American College of Radiology (ACR) and the National Electrical Manufacturers Association (NEMA), the DICOM standard strives to promote communication of image information through the use of a standardized set of command classes and information semantics.
The DICOM standard defines classes of information that are common to many modalities of medical imaging. However, to meet the specific needs of information content for such a diverse range of information, the DICOM specification defines structures for a multitude of medical data. To alleviate the need for applications to implement every aspect of the DICOM specification, a list of conformance tables for every modality was created to define the minimum set of information necessary for data exchanges. A requirement of the DICOM specification is to maintain a compliance document that outlines a subset of DICOM services and data classes that are supported by a device. The purpose of this document is to define a subset of DICOM for the exchange of information with the Sonosite PX via its DICOM feature.
1.2 DEFINITIONS
AE ANSI CDA CW DICOM DIMSE FSC HIS IE IOD kHz LUT MPPS
Application Entity American National Standards Institute Clinical Document Architecture Continuous Wave Digital Imaging and Communications in Medicine DICOM Message Service Element File Set Creator Hospital Information System Information Entity Information Object Definition Kilohertz Look Up Table Modality Performed Procedure Step
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 7 of 48
PACS PW PDU PPS RGB RIS SC SCU SCP SOP SPS SR TCP/IP UID US USB UTC VOI VR
Picture Archive and Communication System Pulsed Wave Protocol Data Unit Performed Procedure Step Red, Green, Blue Radiology Information System Secondary Capture Service Class User (Client) Service Class Provider (Server) Service Object Pair Scheduled Procedure Step Structured Report Transmission Control Protocol/Internet Protocol Unique Identifier Ultrasound Universal Serial Bus Coordinated Universal Time Value Of Interest Value Representation
1.3 REFERENCE DOCUMENTS
ACR-NEMA DICOM Standard Version 3.1 2019
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 8 of 48
2 IMPLEMENTATION MODEL
The Sonosite PX DICOM feature incorporates the DICOM 3.1 standard for image storage, MPPS, Storage Commitment, and Modality Worklist functions. Scheduled Procedures are queried from the HIS/RIS Worklist SCP and presented to the operator for selection. At the beginning and end of a procedure, MPPS messages are sent to the information system relaying the exam status. Performed Procedures1 are transferred from the Sonosite PX ultrasound system using standard network connections to be stored on a DICOM compatible archiver. Upon completion of image transfer, Storage Commitment is requested for transferred images.
The behavior of how images are sent depends on which Transfer Images setting is selected during DICOM setup of locations. Two selections are offered, "During the exam" (in-progress transfer mode) or "End of exam" (batch transfer mode).
For batch transfer mode, Sonosite PX allows up to four archivers and one Worklist server to be selected at any given time. The devices are selected using DICOM Setup mode with all selected archive devices being placed into a destination list.
For in-progress transfer mode, Sonosite PX allows only one archive device and one Worklist server to be selected at any given time. Like batch transfer mode, the devices are selected using DICOM Setup mode with all selected devices annotated in the destination list.
A maximum of 200 Scheduled Procedures Steps may be queried from the selected Modality Worklist SCP. The Worklist is persisted to non-volatile memory so that it can be accessed during portable exams. Both manual and automatic queries are supported. Automatic queries are user configurable and are performed in the background at periodic intervals.
During an exam all saved images are written to internal storage. For batch transfer mode, when the exam completes all images associated with it are marked as Archive Pending for transfer to each device in the current destination list. If a network connection is present then transfer begins immediately.
Performed Procedures are Archived to devices in the destination list sequentially, starting with the first selected archiver and ending with the last selected archiver. Exam images are sent to each destination device in batch transfer mode; an association is opened, all exam images are transferred in acquisition order, and the association is closed. Once an exam is successfully transferred to a device then all images in the exam are marked as Archive Complete to that destination and Storage Commitment is requested for the images. Archiving then continues with the next device in the destination list. Once all devices in the destination list have successfully received each exam image then the Exam Archive is complete.
If an archiver is configured to receive Basic Text Structured Reports or Comprehensive Structured Reports, those documents are transferred at the end of each exam.
For in-progress transfer mode, images are transferred immediately after acquisition, followed by request for Storage Commitment, provided there is a network connection present.
When a Get Status is performed the current destination list is used in the same manner as with Exam Archive. For batch transfer mode, the devices are accessed sequentially, starting with the first selected archiver and ending with the last selected Storage Commitment server. For each device an association is opened, status is returned, and the association is closed. Status is obtained from archiver, MPPS, Storage Commitment and Worklist devices using DICOM Verify (C-Echo). Once status is successfully returned from all devices in the destination list then Get Status is complete.
1 Performed Procedures may consist of single or multi-frame images, or reports.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 9 of 48
When a Get Status is performed during in-progress transfer mode, the archive device association is opened if closed, a C-Echo Request is issued and the C-Echo response status is reported. The association remains open while in DICOM Setup mode. Once DICOM Setup mode is exited the rules used for image acquisition apply to closing the association. This behavior allows an in-progress transfer with an open association to remain open through the Get Status process and allows subsequent image acquisition to be sent on the same association when acquisition constraints are met.
One or more completed exams may be selected from the exam list to have their images saved as DICOM files to the selected USB medium.
The user may choose to "Append" a completed exam. On the Sonosite PX system, this is treated as a new Series in the same Study as the original exam. The appended exam shows up as a separate line item in the Patient List form.
2.1 APPLICATION DATA FLOW DIAGRAM
The diagram in Figure 2-1 represents the relationship between the ultrasound system's real-world activities (circles on the left), the local AEs built into Sonosite PX (boxes in the center), and the remote AEs built into the devices Sonosite PX communicates with using DICOM (boxes on the right).
Figure 2-1
Implementation Model
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 10 of 48
The following are the conditions that invoke real-world activities associated with AEs.
Exam Archive For batch transfer mode, End Exam with one or more images saved on internal storage. Exam end occurs when End Study is pressed or when Patient setup mode is entered and any of the patient fields are changed and the changes are committed. For in-progress transfer mode after an image acquisition is complete. Image acquisition occurs after Save is pressed for single images or Save Clip is pressed for clips. System startup with one or more images flagged as Archive Pending. Upon completion of image transfer, Storage Commitment is requested for transferred images and reports.
Get Status Operator Verify command in DICOM Setup mode.
Procedure Status User starts a new procedure, thereby setting the procedure step to IN PROGRESS. Upon procedure completion status is set to COMPLETE or DISCONTINUED.
Patient User enters Patient Setup screen, enters search criteria, and presses Query or user enters Worklist screen and presses Update. The Worklist screen is entered and a list of matching Scheduled Procedures Steps are returned and displayed.
Exam Export User selects one or more completed exams from the exam list and the images and reports for those exams are written to the selected removable media.
2.2 FUNCTIONAL DEFINITIONS OF AES
Store This AE handles sending ultrasound images and reports to an archiver using the DICOM store SCU services. Steps taken to Get Archiver Status:
A-ASSOCIATE C-ECHO command A-RELEASE
Steps taken to Send Exam to Archiver, batch transfer mode: A-ASSOCIATE for each exam image or report { C-STORE Image SOP Instance } A-RELEASE
Steps taken to Send Exam to Archiver, in progress transfer mode: A-ASSOCIATE for each image or clip acquired that has not been transferred yet { C-STORE Image SOP Instance } A-RELEASE
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 11 of 48
Storage Commitment This AE handles the requesting of storage commitment for objects sent to an archiver using the DICOM Storage Commitment (Push Model) SCU services.
Steps taken to get Storage Commitment SCP Status: A-ASSOCIATE C-ECHO command A-RELEASE
Steps taken to send list of SOP Instances for commitment request: A-ASSOCIATE N-ACTION commitment request A-RELEASE
Steps taken to receive list of committed SOP Instances (role reversal): A-ASSOCIATE N-EVENT-REPORT commitment response A-RELEASE
Worklist This AE handles querying a Worklist SCP for a list of scheduled procedures using the DICOM Modality Worklist SCU services.
Steps taken to Get Worklist Status: A-ASSOCIATE C-ECHO command A-RELEASE
Steps taken to Query a Worklist SCP: A-ASSOCIATE SEND C-FIND Request command { RECEIVE C-FIND Response } While C-FIND status == pending AND responses <= 200
A-RELEASE
Modality Performed Procedure Step This AE handles sending procedure status to an MPPS SCP using the DICOM MPPS SCU services.
Steps taken to get MPPS SCP Status: A-ASSOCIATE C-ECHO command A-RELEASE
Steps taken to send IN PROGRESS status at start of procedure: A-ASSOCIATE N-CREATE MPPS SOP Instance A-RELEASE
Steps taken to send COMPLETE or DISCONTINUED at end of procedure: A-ASSOCIATE N-SET MPPS SOP Instance status update A-RELEASE
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 12 of 48
2.3 SEQUENCING OF REAL-WORLD ACTIVITIES
All real world activities that initiate communication to remote AEs operate asynchronously with respect to each other and Workflow activities.
Figure 2-2
Sequencing Constraints - "During the Exam" Configuration
Under normal scheduled workflow conditions the sequencing constraints illustrated apply: 1. Worklist Query is initiated. 2. List of Scheduled Procedure Steps (SPS) are returned. 3. SPS item is selected from the Worklist and the Exam begins. 4. MPPS IN PROGRESS message sent. 5. Image or Clip is acquired. 6. Association is opened with the Image Manager and the acquired image is stored. 7. Storage Commitment is requested for sent objects. 8. MPPS COMPLETED (or DISCONTINUED) message sent.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 13 of 48
Figure 2-3
Sequencing Constraints - "End of Exam" Configuration
Under normal scheduled workflow conditions the sequencing constraints illustrated apply: 1. Worklist Query is initiated. 2. List of Scheduled Procedure Steps (SPS) are returned. 3. SPS item is selected from the Worklist and the Exam begins. 4. MPPS IN PROGRESS message sent. 5. Images and Clips are acquired. 6. Exam is ended. 7. SOP instances acquired during the exam are stored to the Image Manager. 8. Storage Commitment request is made for stored objects. 9. MPPS COMPLETE (or DISCONTINUED) message sent.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 14 of 48
3 AE SPECIFICATIONS
3.1 STORE AE - SPECIFICATION
The Store AE provides conformance to the following DICOM V3.1 SOP Classes as an SCU:
Table 3-1 Store AE SOP Class Support
SOP Class Name Verification Ultrasound Image Storage Ultrasound Multi-frame Image Storage Secondary Capture Image Storage Basic Text SR Storage
SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.1.1.6.1 1.2.840.10008.5.1.4.1.1.3.1 1.2.840.10008.5.1.4.1.1.7 1.2.840.10008.5.1.4.1.1.88.11
Conformance Level Standard Standard Standard Standard Standard
3.1.1 ASSOCIATION ESTABLISHMENT POLICIES
The Store AE will initiate an association to a device in response to the following real-world activities; Archive Exam or Image Acquisition, Review Archive, and Get Status.
3.1.1.1 GENERAL
Maximum PDU size offered to SCP:
131,072 bytes
This is the maximum PDU size the Store AE can receive and is the value offered for the maximum PDU size in the
Association Request command. Once the Association is open if the Store AE receives a PDU that is larger than this
value then the Association will be aborted.
Minimum PDU size accepted from SCP:
4,096 bytes
This is the minimum PDU size the Store AE can be configured to send. If the Store AE receives a maximum PDU size
in the Association Accept response that is smaller than this value then the Association will be aborted immediately.
Maximum PDU size sent by SCU:
131,072 bytes
This is the maximum PDU size the Store AE can be configured to send. The maximum PDU size sent on any Store
AE Association will be the smaller of the configured value and the maximum PDU size received in the Association
Accept response.
3.1.1.2 NUMBER OF ASSOCIATIONS
Number of simultaneous associations for the Store AE:
1
3.1.1.3 ASYNCHRONOUS NATURE
The Store AE will not use asynchronous operations.
3.1.1.4 IMPLEMENTATION IDENTIFYING INFORMATION
Implementation Class UID: Implementation Version name:
"1.2.276.0.7230010.3.0.3.6.4" "OFFIS_DCMTK_364"
3.1.2 ASSOCIATION INITIATION BY REAL-WORLD ACTIVITY
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 15 of 48
The Store AE will open associations to the storage devices listed in the current destination list in response to the following real-world activities; Archive Exam or Image Acquisition, Review Archive, and Get Status.
3.1.2.1 ASSOCIATION INITIATION BY: ARCHIVE EXAM
The Archive Exam real-world activity if configured for batch transfer mode will cause the Store AE to open associations to each storage device listed in the current destination list.
3.1.2.2 ASSOCIATION INITIATION BY: IMAGE ACQUISITION
The Image Acquisition real-world activity if configured for in-progress transfer mode will cause the Store AE to open an association to the selected storage device .
3.1.2.3 ASSOCIATION INITIATION BY: REVIEW ARCHIVE
The Archive command real-world activity while in Review mode will cause the Store AE to open associations to each storage device listed in the current destination list.
3.1.2.4 ASSOCIATION INITIATION BY: GET STATUS
The Get Status real-world activity will cause the Store AE to open associations to each archiver listed in the current destination list.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 16 of 48
3.1.3 PROPOSED PRESENTATION CONTEXTS TO AN ARCHIVER
Table 3-2 Store AE Proposed Presentation Contexts to an Archiver
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Name List
UID List
Role Extended Negotiation
Verification 1.2.840.10008.1.1
Implicit VR Little Endian 1.2.840.10008.1.2
SCU None
Ultrasound Image Storage
Implicit VR Little Endian 1.2.840.10008.1.2
1.2.840.10008.5.1.4.1.1.6.1 Explicit VR Little Endian 1.2.840.10008.1.2.1 JPEG Baseline (Process 1) 1 1.2.840.10008.1.2.4.50
SCU
Ultrasound
Multi-frame 1.2.840.10008.5.1.4.1.1.3.1 JPEG Baseline (Process 1) 1.2.840.10008.1.2.4.50 SCU
Image Storage
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7 Storage
Implicit VR Little Endian Explicit VR Little Endian
1.2.840.10008.1.2 1.2.840.10008.1.2.1
SCU
Basic Text SR 1.2.840.10008.5.1.4.1.1.88. Implicit VR Little Endian 1.2.840.10008.1.2
Storage
11
Explicit VR Little Endian 1.2.840.10008.1.2.1
SCU
Comprehensive 1.2.840.10008.5.1.4.1.1.88. Implicit VR Little Endian 1.2.840.10008.1.2
R Storage
33
Explicit VR Little Endian 1.2.840.10008.1.2.1
SCU
None None None None None
1 This Transfer Syntax is the only one proposed if JPEG Compression is configured.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 17 of 48
3.1.3.1 VERIFICATION SOP CLASS
The Store AE provides standard conformance to the Verification SOP Class as an SCU. The remote SCP must support Verification in the same association as the Store Command (C-Store).
3.1.3.2 ULTRASOUND IMAGE STORAGE SOP CLASS
The Ultrasound Image Storage SOP Class uses the Common Composite Image IOD Modules as shown in Table 3-3
Table 3-3 US Image IOD Modules
IE Patient Study Series Frame Of Reference Equipment
Image
Module
Patient Clinical Trial Subject General Study Patient Study Clinical Trial Study General Series Clinical Trial Series Frame Of Reference Synchronization General Equipment General Image Image Pixel Contrast/Bolus Palette Color Lookup Table US Region Calibration US Image Overlay Plane VOI LUT SOP Common
Reference 3.1.4.1 Not Used 3.1.4.2 3.1.4.3 Not Used 3.1.4.4 Not Used Not Used Not Used 3.1.4.5 3.1.4.7 3.1.4.8 Not Used
Not Used
3.1.4.11 3.1.4.12 Not Used 3.1.4.13 3.1.4.14
Usage M U M U U M U U U M M M C
C
U M U U M
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 18 of 48
3.1.3.3 ULTRASOUND MULTI-FRAME IMAGE STORAGE SOP CLASS
The Ultrasound Multi-Frame Image Storage SOP Class uses the Common Composite Image IOD Modules as shown in Table 3-4.
Table 3-4 US Multi-Frame Image IOD Modules
IE Patient Study Series Frame Of Reference Equipment
Image
Module
Patient Clinical Trial Subject General Study Patient Study Clinical Trial Study General Series Clinical Trial Series Frame Of Reference Synchronization General Equipment General Image Image Pixel Contrast/Bolus Cine Multi-Frame Frame Pointers Palette Color Lookup Table US Region Calibration US Image VOI LUT SOP Common
Reference
3.1.4.1 Not Used 3.1.4.2 3.1.4.3 Not Used 3.1.4.4 Not Used Not Used Not Used 3.1.4.5 3.1.4.7 3.1.4.8 Not Used 3.1.4.9 3.1.4.10 Not Used Not Used 3.1.4.11 3.1.4.12 3.1.4.13 3.1.4.14
Usage
M U M U U M U U U M M M C M M U C U M U M
3.1.3.4 SECONDARY CAPTURE IMAGE STORAGE SOP CLASS
The Secondary Capture Image Storage SOP Class uses the Common Composite Image IOD Modules as shown in Table 3-5.
Table 3-5 SC Image IOD Modules
IE Patient Study Series Equipment
Image
Module
Patient Clinical Trial Subject General Study Patient Study Clinical Trial Study General Series Clinical Trial Series General Equipment SC Equipment General Image Image Pixel SC Image Overlay Plane Modality LUT VOI LUT SOP Common
Reference
3.1.4.1 Not Used 3.1.4.2 3.1.4.3 Not Used 3.1.4.4 Not Used 3.1.4.5 3.1.4.6 3.1.4.7 3.1.4.8 Not Used Not Used Not Used 3.1.4.13 3.1.4.14
Usage
M U M U U M U U M M M M U U U M
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 19 of 48
3.1.3.5 BASIC TEXT SR STORAGE SOP CLASS
The Basic Text SR Storage SOP Class uses the IOD Modules as shown in Table 3-4.
Table 3-22 Basic Text SR IOD Modules
IE Patient
Study
Series Equipment Document
Module
Patient Clinical Trial Subject General Study Patient Study Clinical Trial Study SR Document Series Clinical Trial Series General Equipment SR Document General SR Document Content SOP Common
Reference
3.1.4.1 Not Used 3.1.4.2 3.1.4.3 Not Used 3.2.4.16 Not Used 3.1.4.5 3.2.4.17 3.2.4.18 3.1.4.14
3.1.3.6 COMPREHENSIVE SR STORAGE SOP CLASS
The Comprehensive SR Storage SOP Class uses the IOD Modules as shown in Table 3-4.
Table 3-22 Basic Text SR IOD Modules
IE Patient
Study
Series Equipment Document
Module
Patient Clinical Trial Subject General Study Patient Study Clinical Trial Study SR Document Series Clinical Trial Series General Equipment SR Document General SR Document Content SOP Common
Reference
3.1.4.1 Not Used 3.1.4.2 3.1.4.3 Not Used 3.2.4.16 Not Used 3.1.4.5 3.2.4.17 3.2.4.18 3.1.4.14
Usage M U M U U M U M M M M
Usage M U M U U M U M M M M
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 20 of 48
3.1.4 COMMON COMPOSITE IMAGE IOD MODULE
The section defines the Modules that are common to the Ultrasound, and Secondary Capture Storage SOP Classes.
3.1.4.1 PATIENT MODULE
Table 3-6 specifies the attributes used from the Patient Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame, and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Table 3-6 Patient Module Attributes
Attribute Name
Tag
Type
Attribute Description
From Worklist or manually entered on Patient Setup
Patient's Name 1
(0010,0010)
2
screen (Last and First fields). All 5 Person Name Components are preserved when name comes from
Worklist.
Patient ID 1
(0010,0020)
2
From Worklist or manually entered on Patient Setup screen (MRN field)
Patient's Birth Date 1
(0010,0030)
2
From Worklist or manually entered on Patient Setup screen (Date of birth fields)
Patient's Sex 1
(0010,0040)
2
From Worklist or manually entered on Patient Setup screen (Gender pick list)
Other Patient IDs
(0010,1000) 3 From Worklist
Manually entered on Patient Setup screen. Not
Ethnic Group
(0010,2160) 3 applicable to all Sonosite PX software versions. Only
sent for IMT Exam Types.
1 This attribute cannot be modified by the user when coming from DICOM Worklist.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 21 of 48
3.1.4.2 GENERAL STUDY MODULE
Table 3-7 specifies the attributes used from the General Study Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame, and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Table 3-7 General Study Module Attributes
Attribute Name
Tag
Type
Attribute Description
Study Instance UID
(0020,000D) 1 From Worklist or automatically generated
Study Date
(0008,0020) 2 Procedure start date
Study Time
(0008,0030) 2 Procedure start time
From Worklist or manually entered on Patient Setup
Referring Physician's Name
(0008,0090)
2
screen (Referring field) Note: Manually entered values will be sent using only
the last name component.
From Worklist (mapped from Requested Procedure
ID attribute) or manually entered for unscheduled
Study ID
(0020,0010) 2 procedures. If no value is provided via worklist or
manual entry, then a value will be automatically
generated.
Accession Number 2 Study Description
(0008,0050)
2
From Worklist or manually entered on Patient Setup screen (Accession field)
(0008,1030)
3
From Worklist 1 or selected manually on Patient Setup screen (Procedure Type pick list)
Referenced Study Sequence
(0008,1110)
3
From Worklist. Not sent if procedure was unscheduled.
>Referenced SOP Class UID
(0008,1150) 1C
>Referenced SOP Instance UID
(0008,1155) 1C
Mapped from Worklist Requested Procedure Code
Procedure Code Sequence
(0008,1032) 3 Sequence, if performed.
Not sent if procedure was unscheduled.
>Code Value
(0008,0100) 1C
>Coding Scheme Designator
(0008,0102) 1C
>Code Meaning
(0008,0104) 1C
Name of Physician(s) Reading Study
Entered on Patient Setup screen. (Reading field) (0008,1060) 3 Note: Manually entered values will be sent using only
the last name component.
1 Mapped from Scheduled Procedure Step Description (0040,0007) if it exists. Otherwise, Study Description is set to value of Requested Procedure Description (0032,1060) if it exists. If Requested Procedure Description (0032,1060) is also empty, Study Description is set to Requested Procedure Code Sequence (0032,1064) Code Meaning (0008,0104). 2 This attribute cannot be modified by the user when coming from DICOM Worklist.
3.1.4.3 PATIENT STUDY MODULE
Table 3-8 defines attributes used from the Patient Study Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame, and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Attribute Name Additional Patient's History
Table 3-8 Patient Study Module Attributes
Tag (0010,21B0)
Type 3
Attribute Description
From Worklist of manually entered on Patient Setup screen (Indications field).
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 22 of 48
3.1.4.4 GENERAL SERIES MODULE
Table 3-9 specifies the attributes used from the General Series Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Attribute Name Modality Series Instance UID Series Number Laterality Series Date Series Time Protocol Name Series Description
Operator's Name
Request Attributes Sequence
>Requested Procedure ID >Scheduled Procedure Step ID >Scheduled Procedure Step Description >Scheduled Protocol Code Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning
Performed Procedure Step ID
Performed Procedure Step Start Date Performed Procedure Step Start Time
Performed Procedure Step Description
Performed Protocol Code Sequence
>Code Value >Coding Scheme Designator >Code Meaning
Table 3-9 General Series Module Attributes
Tag (0008,0060) (0020,000E) (0020,0011) (0020,0060) (0008,0021) (0008,0031) (0018,1030) (0008,103E)
(0008,1070)
(0040,0275)
(0040,1001) (0040,0009)
Type 1 1 2 2C 3 3 3 3
3
3
1C 1C
Attribute Description
"US" Automatically generated "1" Zero Length Procedure start date Procedure start time Zero length Same as Performed Procedure Step Description Entered on Patient Setup screen (Performing field). The value is transmitted in the last name component Only sent if the procedure originated from a Worklist Scheduled Procedure Step From Worklist From Worklist
(0040,0007)
3
From Worklist
(0040,0008)
3
From Worklist
(0008,0100) 1C
(0008,0102) 1C
(0008,0104) 1C
(0040,0253)
3
From Worklist (mapped from Scheduled Procedure Step ID) or Generated by Sonosite PX
(0040,0244)
3
Procedure start date
(0040,0245)
3
Procedure start time
Mapped from Worklist SPS description, if
(0040,0254)
3
performed, or selected manually on Patient Setup
screen (Procedure Type pick list)
Mapped From Worklist Scheduled Protocol Code
(0040,0260)
3
sequence, if performed.
Otherwise sent as zero length sequence.
(0008,0100) 1C
(0008,0102) 1C
(0008,0104) 1C
3.1.4.5 GENERAL EQUIPMENT MODULE
Table 3-10 specifies the attributes used from the General Equipment Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 23 of 48
Table 3-10 General Equipment Module Attributes
Attribute Name
Manufacturer Institution Name Station Name Institutional Department Name Manufacturer's Model Name Software Versions FUJIFILM USA Sonosite Private Tag
Tag (0008,0070) (0008,0080) (0008,1010) (0008,1040) (0008,1090) (0018,1020)
(0019,1110)
Type 2 3 3 3 3 3
2
Attribute Description "SonoSite, Inc." Entered on Patient Setup screen (Institution) Host Name for current location
Model name (maps to product line) System Firmware Version
Worksheet Data in JSON Formatted Text
3.1.4.6 SC EQUIPMENT MODULE
Table 3-11 describes the attributes used from the SC Equipment Module. These attributes are used by the Secondary Capture Image Storage SOP Class. Attributes not listed are not used.
Table 3-11 SC Equipment Module Attributes
Attribute Name Modality
Tag
Type
(0008,0060) 3 "US"
Attribute Description
3.1.4.7 GENERAL IMAGE MODULE
Table 3-12 specifies the attributes used from the General Image Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Attribute Name Instance Number Patient Orientation Content Date Content Time
Derivation Description
Lossy Image Compression
Lossy Image Compression Ratio
Table 3-12 General Image Module Attributes
Tag (0020,0013) (0020,0020) (0008,0023) (0008,0033)
(0008,2111)
(0028,2110)
(0028,2112)
Type 2 2C 2C 2C
3
3
3
Attribute Description
A number that identifies this image Zero Length Image acquisition date Image acquisition time "RGB to MONOCHROME2 conversion" - Sent for MONOCHROME2 images "RGB to JPEG Baseline 1 conversion" Sent for JPEG Lossy compressed images. 01=Lossy Compressed - Only sent for MONOCHROME2 and JPEG Lossy Compressed images. Set to 3 for MONOCHROME2 images. The approximate compression ratio is sent for JPEG Lossy Compressed images.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 24 of 48
3.1.4.8 IMAGE PIXEL MODULE
Table 3-13 specifies the attributes used from the Image Pixel Module. These attributes are used by the Ultrasound, Ultrasound Multi-frame and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Attribute Name Samples per Pixel
Photometric Interpretation
Rows Columns Bits Allocated Bits Stored High Bit Pixel Representation Pixel Data
Planar Configuration
Table 3-13 Image Pixel Module Attributes
Tag (0028,0002)
(0028,0004)
(0028,0010) (0028,0011) (0028,0100) (0028,0101) (0028,0102) (0028,0103) (7FE0,0010)
(0028,0006)
Type 1
1
1 1 1 1 1 1 1
1C
Attribute Description
MONOCHROME2=1, RGB=3, YBR_FULL_422 = 3 Configurable in DICOM Setup mode. Valid settings defined by archiver type and Transfer Syntax being used. MONOCHROME2, RGB or YBR_FULL_422 1050 1400 8 8 7 0 Used Basic Offset Table is set to zero length for encapsulated multi-frame images. 0=Color-by-pixel - Only sent for RGB and YBR_FULL_422 images
3.1.4.9 CINE MODULE
Table 3-14 specifies the attributes used from the Cine module. The Ultrasound Multi-Frame Image IOD uses these attributes. Attributes not listed are not used.
Table 3-14 Cine Module Attributes
Attribute Name Frame Time
Tag
Type
Attribute Description
(0018,1063) 1C Nominal time (in msec) per individual frame.
3.1.4.10 MULTI-FRAME MODULE
Table 3-15 specifies the attributes used from the Cine module. The Ultrasound Multi-Frame Image IOD uses these attributes.
Table 3-15 Multi-frame Module Attributes
Attribute Name Number of Frames Frame Increment Pointer
Tag (0028,0008) (0028,0009)
Type 1 1
Attribute Description Number of frames in a Multi-frame Image. Always set to 00181063H (Frame Time).
3.1.4.11 US REGION CALIBRATION MODULE
Table 3-16 specifies the attributes used from the US Region Calibration Module. These attributes are used by Ultrasound and Ultrasound Multi-frame Image Storage SOP instances created by the Sonosite PX system. Attributes not listed are not used.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 25 of 48
Table 3-16 US Region Calibration Attributes
Attribute Name
Sequence of Ultrasound Regions >Region Location Min x0 >Region Location Min y0 >Region Location Max x1 >Region Location Max y1 >Physical Units X Direction >Physical Units Y Direction >Physical Delta X >Physical Delta Y >Reference Pixel x0 >Reference Pixel y0 >Ref. Pixel Physical Value X >Ref. Pixel Physical Value Y >Region Spatial Format >Region Data Type >Region Flags
Tag
(0018,6011) (0018,6018) (0018,601A) (0018,601C) (0018,601E) (0018,6024) (0018,6026) (0018,602C) (0018,602E) (0018,6020) (0018,6022) (0018,6028) (0018,602A) (0018,6012) (0018,6014) (0018,6016)
Type
1 1 1 1 1 1 1 1 1 3 3 3 3 1 1 1
Attribute Description Used Automatically generated Automatically generated Automatically generated Automatically generated
Automatically generated Automatically generated Automatically generated Only sent in Spectral Doppler regions. Only sent in Spectral Doppler regions. Only sent in Spectral Doppler regions. Only sent in Spectral Doppler regions. Automatically generated Automatically generated Automatically generated
3.1.4.12 US IMAGE MODULE
Table 3-17 specifies the attributes used from the US Image Module. These attributes are used by Ultrasound and Ultrasound Multi-frame Image Storage SOP instances created by the Sonosite PX system. Attributes not listed are not sent.
Table 3-17 US Image Module Attributes
Attribute Name Samples Per Pixel
Photometric Interpretation
Bits Allocated Bits Stored High Bit Planar Configuration Pixel Representation
Tag (0028,0002)
(0028,0004)
(0028,0100) (0028,0101) (0028,0102) (0028,0006) (0028,0103)
Type 1
1
1 1 1 1C 1
Attribute Description
MONOCHROME2=1, RGB=3, YBR_FULL_422 = 3 Configurable in DICOM Setup mode Valid settings defined by archiver type and Transfer Syntax being used. MONOCHROME2, RGB or YBR_FULL_422 8 8 7 0=Color-by-pixel - Only sent for RGB and YBR_FULL_422 images 0 RGB = "ORIGINAL\PRIMARY\<ExamType>\nnnn"
YBR_FULL_422 or MONOCHROME2 = "DERIVED\PRIMARY\<ExamType>\nnnn"
Image Type
Lossy Image Compression
\
D25306
Rev: B
(0008,0008) (0028,2110)
Value for <ExamType>is determined by the exam type
selected by the user.
2
nnnn=bit map designating the image mode:
0001 =
2D Imaging
0002 =
M-Mode
0004 =
CW Doppler
0008 =
PW Doppler
0010 =
Color Doppler
0100 =
Color Power Mode
1C
01=Lossy Compressed - Only sent for MONOCHROME2 and JPEG Lossy Compressed images.
SonoSite PX DICOM Conformance Statement
Page: 26 of 48
Attribute Name
Ultrasound Color Data Present Heart Rate Transducer Data
Tag
(0028,0014) (0018,1088) (0018,5010)
Type
3 3 3
Attribute Description
00=Color data not present in image 01=Color data is present in image
3.1.4.13 VOI LUT MODULE
Table 3-18 specifies the attributes used from the VOI LUT module. These attributes are used by the Ultrasound, Ultrasound Multi-frame and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Attribute Name Window Center Window Width
Table 3-18 VOI LUT Module Attributes
Tag (0028,1050) (0028,1051)
Type 3 1C
Attribute Description 128 - Only sent with Monochrome2 256 - Only sent with Monochrome2
3.1.4.14 SOP COMMON MODULE
Table 3-19 specifies the attributes used from the SOP Common module. These attributes are used by the Ultrasound, Ultrasound Multi-frame and Secondary Capture Image Storage SOP Classes. Attributes not listed are not used.
Attribute Name
SOP Class UID SOP Instance UID Specific Character Set Instance Number
Table 3-19 SOP Common Module Attributes
Tag
(0008,0016) (0008,0018) (0008,0005) (0020,0013)
Type
1 1 1C 3
Attribute Description
Automatically generated Automatically generated ISO_IR 100 A number that identifies this image
3.1.4.15 SR DOCUMENT SERIES MODULE
Table 3-10 specifies the attributes used from the SR Document Series Module. These attributes are used by the SR Document Storage SOP Classes. Attributes not listed are not used.
Attribute Name
Modality Series Instance UID Series Number Referenced Performed Procedure Step Sequence
Table 99-05 SR Document Series Module Attributes
Tag (0008,0060) (0020,000E) (0020,0011)
Type 1 "SR" 1 1
Attribute Description
(0008,1111) 2
3.1.4.16 SR DOCUMENT GENERAL MODULE
Table 3-10 specifies the attributes used from the SR Document General Module. These attributes are used by the SR Storage SOP Classes. Attributes not listed are not used.
Table 99-05 SR Document General Module Attributes
Attribute Name Instance Number
\
D25306
Rev: B
Tag
Type
(0020,0013) 1
Attribute Description
SonoSite PX DICOM Conformance Statement
Page: 27 of 48
Attribute Name
Completion Flag Verification Flag Content Date Content Time Performed Procedure Code Sequence
Tag (0040,A491) (0040,A493) (0008,0023) (0008,0033)
(0040,A372)
Type 1 1 1 1
2
Attribute Description
3.1.4.17 SR DOCUMENT CONTENT MODULE
Table 3-10 specifies the attributes used from the SR Document Content Module. These attributes are used by the SR Storage SOP Classes. Attributes not listed are not used.
Table 99-05 SR Document Content Module Attributes
Attribute Name
Value Type Concept Name Code Sequence Text Value Observation Date Time Content Sequence >Relationship Type >Referenced Content Item Identifier
Tag (0040,A040) (0040,A043) (0040,A160) (0040,A032) (0040,A730) (0040,A010)
(0040,DB73)
Type 1 1C 1C 1C 1C 1
1C
Attribute Description
3.1.5 STORE AE BEHAVIOR TO C-STORE STATUS
Table 3-20describes the behavior for C-Store response status returned from the Storage SCP. All image SOP classes supported by the Store AE exhibit the same behavior.
Service Status Success Refused Error
Warning
Table 3-20 Store AE Behavior to C-Store Status
Further Meaning
Out of Resources Data Set does not match SOP Class Cannot understand Coercion of data elements Data set does not match SOP class Elements discarded
Status Codes
0000 A7xx A9xx Cxxx B000 B007 B006
Store AE Behavior
Continue without user notification Association terminated. User notified. Association terminated. User notified. Association terminated. User notified. Ignored - Message logged. Ignored - Message logged. Ignored - Message logged.
3.2 STORAGE COMMITMENT AE SPECIFICATION
The Storage Commitment AE provides conformance to the following DICOM V3.1 SOP Classes as an SCU:
Table 3-21 Storage Commitment AE SOP Class Support
SOP Class Name Verification Storage Commitment Push Model
SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.1.20.1
Conformance Level Standard Standard
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 28 of 48
3.2.1 ASSOCIATION ESTABLISHMENT POLICIES
The Storage Commitment AE will initiate an association to a device in response to the following real-world activities:
1. All images have been transferred for an exam (batch mode transfer). 2. An image has been transferred for an exam (in-progress mode transfer). 3. The user manually selects to (re) issue commitment request for a particular exam. 4. After system startup, archived but un-committed images exist. In all cases a N-ACTION command is issued to the Storage Commitment server. After the request has been made, the association is left open for 30 seconds to receive a reply (in case the storage commit server is configured to reply on the same association). After 30 seconds the association is closed.
The Storage Commitment AE will respond to an association request from a device in response to the following realworld activities:
1. Storage Commitment SCP responds to commitment request with N-EVENT-REPORT.
3.2.1.1 GENERAL
Maximum PDU size offered to SCP:
131,072 bytes
This is the maximum PDU size the Store AE can receive and is the value offered for the maximum PDU size in the
Association Request command. Once the Association is open if the Store AE receives a PDU that is larger than this
value then the Association will be aborted.
Minimum PDU size accepted from SCP:
4,096 bytes
This is the minimum PDU size the Store AE can be configured to send. If the Store AE receives a maximum PDU size
in the Association Accept response that is smaller than this value then the Association will be aborted immediately.
Maximum PDU size sent by SCU:
131,072 bytes
This is the maximum PDU size the Store AE can be configured to send. The maximum PDU size sent on any Store
AE Association will be the smaller of the configured value and the maximum PDU size received in the Association
Accept response.
3.2.1.2 NUMBER OF ASSOCIATIONS
Number of simultaneous associations for the Storage Commitment AE: 1
3.2.1.3 ASYNCHRONOUS NATURE
The Storage Commitment AE will not use asynchronous operations.
3.2.1.4 IMPLEMENTATION IDENTIFYING INFORMATION
Implementation Class UID: Implementation Version name:
"1.2.276.0.7230010.3.0.3.6.4" "OFFIS_DCMTK_364"
3.2.1.5 SCU BEHAVIOR
The Sonosite PX system accepts N-EVENT-REPORTS the N-ACTION association or on separate associations. The Sonosite PX system provides visual indication of successful Storage Commitment.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 29 of 48
3.2.2 PROPOSED PRESENTATION CONTEXTS TO A STORAGE COMMITMENT SERVER
Table 3-22 Storage Commitment AE Proposed Presentation Contexts
Abstract Syntax
Name
UID
Verification SOP Class
1.2.840.10008.1.1
Presentation Context Table Transfer Syntax
Name List
UID List
Implicit VR Little Endian
1.2.840.10008.1.2
Role Extended Negotiation
SCU None
Storage Commitment Push Model
1.2.840.10008.1.20.1 Implicit VR Little Endian
1.2.840.10008.1.2 SCU None
3.2.2.1 STORAGE COMMITMENT PUSH MODEL SOP CLASS
The Storage Commitment AE provides standard conformance to the Storage Commitment Push Model SOP Class as an SCU.
3.2.2.2 VERIFICATION SOP CLASS
The Storage Commitment AE provides standard conformance to the Verification SOP Class as both SCU and SCP.
3.2.3 STORAGE COMMITMENT ATTRIBUTES
Table 3-23 Storage Commitment Request - Action Information
Action Type Name
Request Storage Commitment
Action Type ID
1
Attribute
Transaction UID
Referenced SOP Sequence >Referenced SOP Class UID >Referenced SOP Instance UID
Tag
(0008,1195)
(0008,1199) (0008,1150) (0008,1155)
Notes
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 30 of 48
Event Type Name Storage Commitment Request Successful
Storage Commitment Request Complete Failures Exist
Table 3-24 Storage Commitment Result Event Information
Event Type ID
Attribute
1
Transaction UID
Tag (0008,1195)
Referenced SOP Sequence
(0008,1199)
>Referenced SOP Class UID
(0008,1150)
>Referenced SOP Instance UID (0008,1155)
2
Transaction UID
(0008,1195)
Referenced SOP Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Failed SOP Sequence >Referenced SOP Class UID >Referenced SOP Instance UID >Failure Reason
(0008,1199) (0008,1150) (0008,1155) (0008,1198) (0008,1150) (0008,1155) (0008,1197)
Notes
3.3 MODALITY WORKLIST AE SPECIFICATION
The Modality Worklist AE provides conformance to the following DICOM V3.1 SOP Classes as an SCU:
Table 3-25 Modality Worklist AE SOP Class Support
SOP Class Name Verification Modality Worklist Information Model - FIND
SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.4.31
Conformance Level Standard Standard
3.3.1 ASSOCIATION ESTABLISHMENT POLICIES
The Modality Worklist AE will initiate an association to a device in response to the following real-world activities; 1. The user initiates a manual Update Worklist (Broad Query). 2. The user initiates a specific Worklist Query (Patient Based Query). 3. The system initiates an Automatic Worklist Query (Broad Query).
In all cases a C-FIND command is issued to the Modality Worklist server. After the requested data is returned, the association is closed.
3.3.1.1 GENERAL
Maximum PDU size offered to SCP: 131,072 bytes This is the maximum PDU size the Modality Worklist AE can receive and is the value offered for the maximum PDU size in the Association Request command. Once the Association is open if the Modality Worklist AE receives a PDU that is larger than this value then the Association will be aborted.
Minimum PDU size accepted from SCP:
4,096 bytes
This is the minimum PDU size the Modality Worklist AE can be configured to send. If the Modality Worklist AE
receives a maximum PDU size in the Association Accept response that is smaller than this value then the
Association will be aborted immediately.
Maximum PDU size offered to SCI: 131,072 bytes
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 31 of 48
This is the maximum PDU size the Modality Worklist AE can be configured to send. The maximum PDU size sent on any Modality Worklist AE Association will be the smaller of the configured value and the maximum PDU size received in the Association Accept response.
3.3.1.2 NUMBER OF ASSOCIATIONS
Number of simultaneous associations for the Modality Worklist AE: 1
3.3.1.3 ASYNCHRONOUS NATURE
The Modality Worklist AE will not use asynchronous operations.
3.3.1.4 IMPLEMENTATION IDENTIFYING INFORMATION
Implementation Class UID: Implementation Version name:
"1.2.276.0.7230010.3.0.3.6.4" "OFFIS_DCMTK_364"
ASSOCIATION INITIATION BY REAL-WORLD ACTIVITY
The Modality Worklist AE will open associations to the configured Worklist SCP in response to the following realworld activities; Update Worklist, Query Worklist, Automatic Worklist Query, and Get Status.
3.3.1.5 ASSOCIATION INITIATION BY: UPDATE WORKLIST
The Update Worklist real-world activity initiated in Worklist screen will cause the Modality Worklist AE to open an association with the Worklist SCP, configured in the current Location.
3.3.1.6 ASSOCIATION INITIATION BY: WORKLIST QUERY
The Query Worklist command real-world activity initiated in Patient Setup screen will cause the Modality Worklist AE to open an association with the Worklist SCP, configured in the current Location.
3.3.1.7 ASSOCIATION INITIATION BY: AUTOMATIC WORKLIST QUERY
The Automatic Worklist Query real-world activity initiated by the system at periodic intervals will cause the Modality Worklist AE to open an association with the Worklist SCP, configured in the current Location.
3.3.1.8 ASSOCIATION INITIATION BY: GET STATUS
The Get Status real-world activity will cause the Modality Worklist AE to open an association to the Modality Worklist SCP configured in the current Location.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 32 of 48
3.3.2 PROPOSED PRESENTATION CONTEXTS TO A WORKLIST SERVER
Table 3-26 Modality Worklist AE Proposed Presentation Contexts to a Worklist Server
Abstract Syntax
Name
UID
Verification SOP Class
1.2.840.10008.1.1
Presentation Context Table Transfer Syntax
Name List
UID List
Implicit VR Little Endian
1.2.840.10008.1.2
Role Extended Negotiation
SCU None
Modality Worklist Information Model - FIND
1.2.840.10008.5.1.4.31 Implicit VR Little Endian
1.2.840.10008.1.2 SCU None
3.3.2.1 MODALITY WORKLIST INFORMATION MODEL FIND SOP CLASS
The Modality Worklist AE provides standard conformance to the Modality Worklist Information Model - FIND SOP Class as an SCU.
3.3.2.2 VERIFICATION SOP CLASS
The Modality Worklist AE provides standard conformance to the Verification SOP Class as an SCU.
3.3.3 MODALITY WORKLIST ATTRIBUTES
3.3.3.1 BROAD WORKLIST QUERY MATCHING KEY ATTRIBUTES
Table 3-27 specifies the Matching Key attributes used by Automatic Worklist C-FIND requests and manual Update Worklist C-FIND requests for Broad queries initiated by the user from the Worklist screen.
Table 3-27 Broad Worklist Query Matching Key Attributes
Attribute Name Modality Scheduled Station AE-Title
Scheduled Procedure Step Start Date
Tag (0008,0060) (0040,0001)
(0040,0002)
Type R R
R
Notes
Selectable from list provided by User Interface Configurable Sent as either ;
1) Sonosite PX's AE Title 2) Universal Matching. Configurable Sent as either; 1) Today's date 2) Yesterday, Today and Tomorrow date range 3) Universal Matching
3.3.3.2 PATIENT BASED QUERY MATCHING KEY ATTRIBUTES
Table 3-28 specifies the Matching Key attributes used for Worklist C-FIND requests for Patient Based queries initiated by the user from the Patient Setup screen.
Table 3-28 Patient Based Query Matching Key Attributes
Attribute Name Modality
Scheduled Station AE-Title
Scheduled Procedure Step Start Date
Tag (0008,0060) (0040,0001)
(0040,0002)
Type R R
R
Notes
Selectable from list provided by User Interface
Configurable Sent as either ; 1) Sonosite PX's AE Title 2) Universal Matching.
Configurable Sent as either; 1) Today's date 2) Yesterday, Today and Tomorrow date range 3) Universal Matching
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 33 of 48
Attribute Name Patient's Name
Patient ID Accession Number Requested Procedure ID
Tag (0010,0010)
(0010,0020) (0008,0050) (0040,1001)
Type R
R O O
Notes
Entered on Patient Setup screen. A wild card is appended to Last and First name component. Entered on Patient Setup screen. Single value matching only. Entered on Patient Setup screen. Entered on Patient Setup screen.
3.3.3.3 RETURN KEY ATTRIBUTES
Table 3-29 specifies the Return Key attributes that are included in all Worklist C-FIND requests.
Table 3-29 Return Key Attributes
Attribute Name
Tag
Type Notes
Study Instance UID
(0020,000D) 1
Accession Number4
(0008,0050) 2 Displayed on Patient Setup screen
Referring Physician's Name
(0008,0090) 2 Displayed on Patient Setup screen
Displayed on Patient Setup screen. All 5 name
Patient's Name4
(0010,0010) 1 components are preserved but only Last, First and
Middle name components are displayed.
Patient ID4
(0010,0020) 1 Displayed on Patient Setup screen
Patients Birth Date
(0010,0030) 2 Displayed on Patient Setup screen
Patient's Sex
(0010,0040) 2 Displayed on Patient Setup screen
Other Patient IDs
(0010,1000) 3
Additional Patient History
(0010,21B0) 3 Displayed on Patient Setup screen as Indications
Admitting Diagnoses Description (0008,1080)
3
Displayed on Patient Setup screen as Indications if Additional Patient History is not returned.
Last Menstrual Date
(0010,21D0) 2 Displayed on Patient Setup screen.
Scheduled Procedure Step Sequence
(0040,0100) 1
>Modality
(0008,0060) 1
>Scheduled Station AE Title
(0040,0001) 1
>Scheduled Procedure Step Start Date
(0040,0002) 1
>Scheduled Procedure Step Start Time
(0040,0003) 1
>Scheduled Procedure Step Description4
(0040,0007) 1C
>Scheduled Protocol Code Sequence
(0040,0008) 1C
>>Code Value
(0008,0100) 1C
>>Coding Scheme Designator
(0008,0102) 1C
>>Code Meaning
(0008,0104) 3
>Scheduled Procedure Step ID (0040,0009) 1
Requested Procedure ID4
(0040,1001) 1 Displayed on Patient Setup screen.
Requested Procedure Description4
(0032,1060) 1C
Requested Procedure Code Sequence
(0032,1064) 1C
>Code Value
(0008,0100) 1C
>Coding Scheme Designator
(0008,0102) 1C
>Code Meaning4
(0008,0104) 3
Referenced Study Sequence
(0008,1110) 2
>Referenced SOP Class UID
(0008,1150) 1C
>Referenced SOP Instance UID (0008,1155) 1C
\
D25306 Rev: B SonoSite PX DICOM Conformance Statement
Page: 34 of 48
4 This attribute from Worklist may be truncated when displayed in the Sonosite PX User Interface. However, the value contained in the attribute is preserved in full fidelity.
3.3.4 WORKLIST AE BEHAVIOR TO C-FIND STATUS
Table 3-30 specifies the response status codes, which an SCP may return following the SCU's C-FIND request, along with the Worklist AEs associated behavior. Only those status responses that indicate some form of error condition are presented to the user. Related fields are not used.
Service Status Refused Failed Cancel Success
Pending
Table 3-30 Worklist AE Behavior to C-FIND Status
Further Meaning Out of resources Identifier does not match SOP Class
Status Codes
A700
A900
Unable to process
Matching terminated due to Cancel request Matching is complete - No final Identifier is supplied. Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier.
Cxxx FE00 0000 FF00
FF01
Worklist AE Behavior
The association is terminated. The user is notified of the failure. The association is terminated. The user is notified of the failure. The association is terminated. The user is notified of the failure. The association is terminated. The user is notified that the query was incomplete. The Modality Worklist AE will continue operation without user notification.
The Modality Worklist AE will continue operation without user notification.
The Modality Worklist AE will continue operation without user notification.
3.4 MODALITY PERFORMED PROCEDURE STEP (MPPS) AE SPECIFICATION
The MPPS AE provides conformance to the following DICOM V3.1 SOP Classes as an SCU:
Table 3-31 MPPS AE SOP Class Support
SOP Class Name Verification Modality Peformed Procedure Step
SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.3.1.2.3.3
Conformance Level Standard Standard
3.4.1 ASSOCIATION ESTABLISHMENT POLICIES
The MPPS AE will initiate an association to a device in response to the following real-world activities:
1. The user begins a new procedure.
2. The user completes (or discontinues) a procedure.
3. The system has queued up procedures whose status has not yet been transmitted to the MPPS
SCP.
In the case of beginning a procedure an N-CREATE command is issued to the MPPS SCP. In the case of
completing/discontinuing a procedure, an N-SET is issued to the MPPS SCP. After the message has been made, the
association is closed.
\
D25306 Rev: B SonoSite PX DICOM Conformance Statement
Page: 35 of 48
3.4.1.1 GENERAL
Maximum PDU size offered to SCP: 131,072 bytes This is the maximum PDU size the MPPS AE can receive and is the value offered for the maximum PDU size in the Association Request command. Once the Association is open if the MPPS AE receives a PDU that is larger than this value then the Association will be aborted.
Minimum PDU size accepted from SCP: 4,096 bytes This is the minimum PDU size the MPPS AE can be configured to send. If the MPPS AE receives a maximum PDU size in the Association Accept response that is smaller than this value then the Association will be aborted immediately.
Maximum PDU size offered to SCI: 131,072 bytes This is the maximum PDU size the MPPS AE can be configured to send. The maximum PDU size sent on any MPPS AE Association will be the smaller of the configured value and the maximum PDU size received in the Association Accept response.
3.4.1.2 NUMBER OF ASSOCIATIONS
Number of simultaneous associations for the MPPS AE:
1
3.4.1.3 ASYNCHRONOUS NATURE
The MPPS AE will not use asynchronous operations.
3.4.1.4 IMPLEMENTATION IDENTIFYING INFORMATION
Implementation Class UID: Implementation Version name:
"1.2.276.0.7230010.3.0.3.6.4" "OFFIS_DCMTK_364"
3.4.2 PROPOSED PRESENTATION CONTEXTS TO AN MPPS SERVER
Table 3-32 MPPS AE Proposed Presentation Contexts
Abstract Syntax
Name
UID
Verification SOP Class
1.2.840.10008.1.1
Presentation Context Table Transfer Syntax
Name List
UID List
Implicit VR Little Endian
1.2.840.10008.1.2
Modality Performed Procedure Step
1.2.840.10008.3.1.2.3.3 Implicit VR Little Endian
1.2.840.10008.1.2
Role Extended Negotiation
SCU None
SCU None
3.4.2.1 MPPS SOP CLASS
The MPPS AE provides standard conformance to the Modality Performed Procedure Step SOP Class as an SCU.
3.4.2.2 VERIFICATION SOP CLASS
The MPPS AE provides standard conformance to the Verification SOP Class as an SCU.
3.4.3 MPPS INFORMATION MODEL ATTRIBUTES
\
D25306
Table 3-33 MPPS SOP Class N-CREATE and N-SET Attributes Rev: B SonoSite PX DICOM Conformance Statement
Page: 36 of 48
Attribute Name
Scheduled Step Attribute Sequence
Tag (0040,0270)
Req. Type N-CREATE
1
Req. Type N-SET
Not allowed
>Study Instance UID
(0020,000D)
1
Not allowed
>Referenced Study Sequence (0008,1110)
2
Not allowed
>>Referenced SOP Class UID (0008,1150)
1
Not allowed
>>Referenced SOP Instance UID
(0008,1155)
1
Not allowed
>Accession Number
(0008,0050)
2
Not allowed
>Requested Procedure ID
(0040,1001)
2
Not allowed
>Requested Procedure Code Sequence
(0032,1064)
3
Not allowed
>>Code Value
(0008,0100)
1
Not allowed
>>Coding Scheme Designator (0008,0102)
1
Not allowed
>>Code Meaning
(0008,0104)
1
Not allowed
>Requested Procedure Description
(0032,1060)
2
Not allowed
>Scheduled Procedure Step ID
(0040,0009)
2
Not allowed
>Scheduled Procedure Step Description
(0040,0007)
2
Not allowed
>Scheduled Protocol Code Sequence
(0040,0008)
2
Not allowed
>>Code Value
(0008,0100)
1
Not allowed
>>Coding Scheme designator (0008,0102)
1
Not allowed
>>Code Meaning
(0008,0104)
3
Not allowed
Patient's Name
(0010,0010)
2
Not allowed
Patient ID
(0010,0020)
2
Not allowed
Patient's Birth Date
(0010,0030)
2
Not allowed
Patient's Sex
(0010,0040)
2
Not allowed
Referenced Patient Sequence
(0008,1120)
2
Not allowed
Performed Procedure Step ID
(0040,0253)
1
Not allowed
Performed Station AE Title
(0040,0241)
1
Not allowed
Performed Station Name
(0040,0242)
2
Not allowed
Performed Location
(0040,0243)
2
Not allowed
Performed Procedure Step Start Date
(0040,0244)
1
Not allowed
Performed Procedure Step Start Time
(0040,0245)
1
Not allowed
Performed Procedure Step
(0040,0252)
1
3
Status
Performed Procedure Step
(0040,0254)
2
3
Description
Performed Procedure Type
(0040,0255)
2
3
Description
\
D25306 Rev: B SonoSite PX DICOM Conformance Statement
Notes From Worklist From Worklist
From Worklist
Empty Internally Generated "SONOPPSxxxxxxx"
N-CREATE only N-CREATE only
Page: 37 of 48
Procedure Code Sequence >Code Value >Coding Scheme Designator >Code Meaning Performed Procedure Step End Date Performed Procedure Step End Time Modality Study ID Performed Protocol Code Sequence >Code Value >Coding Scheme Designator >Code Meaning Performed Series Sequence >Performing Physician's Name >Protocol Name
>Operators' Name >Series Instance UID >Series Description >Retrieve AE Title >Referenced Image Sequence >>Referenced SOP Class UID >>Referenced SOP Instance UID >Referenced Non-Image Composite SOP Instance Sequence >>Referenced SOP Class UID >>Referenced SOP Instance UID
(0008,1032) (0008,0100) (0008,0102) (0008,0104) (0040,0250)
(0040,0251)
(0008,0060) (0020,0010) (0040,0260)
(0008,0100) (0008,0102) (0008,0104) (0040,0340) (0008,1050)
(0018,1030)
(0008,1070) (0020,000E) (0008,103E) (0008,0054) (0008,1140)
(0008,1150) (0008,1155)
(0040,0220)
(0008,1150) (0008,1155)
2
3
N-CREATE only
1
1
1
1
3
3
2
3
2
3
1
Not allowed
"US"
2
Not allowed
2
3
N-CREATE only
1
1
1
1
3
3
2
3
2
2
1
1
Internally Generated
"SONOPPSxxxxxxx"
2
2
1
1
2
2
2
2
2
2
1
1
1
1
2
2
1
1
1
1
3.5 MEDIA EXPORT AE SPECIFICATION
3.5.1 INTRODUCTION
This section of the conformance statement specifies the Sonosite PX compliance to DICOM Media Storage. It details the roles supported by this product.
Sonosite PX is able to export DICOM images and reports to removable USB media stick memory. Any reference to USB in this document refers to "USB media stick memory".
3.5.2 IMPLEMENTATION MODEL
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 38 of 48
The Media Export AE saves single and multi-frame US images and reports to a USB storage device. It is associated with the local real-world activity "Export to USB". "Export to USB" is performed upon user request for selected patient series.
3.5.2.1 APPLICATION DATA FLOW
Export to USB
Media Export AE
FSC
USB Storage Medium
Figure 3-1
Media Export Data Flow
3.5.2.2 FUNCTIONAL DEFINITION OF THE AE
Sonosite PX can perform the following functions: Create a new DICOM file-set on the USB medium Add to an existing DICOM file-set previously created by the Sonosite PX system
3.5.2.3 SEQUENCING OF REAL-WORLD ACTIVIITIES
Not applicable.
3.5.2.4 FILE META INFORMATION OPTIONS (SEE PS 3.10)
The implementation information written to the File Meta Header in each file is:
Implementation Class UID: Implementation Version name:
"1.2.276.0.7230010.3.0.3.6.4" "OFFIS_DCMTK_364"
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 39 of 48
3.5.3 AE SPECIFICATIONS
3.5.3.1 FILE META INFORMATION FOR THE APPLICATION ENTITY
The Source Application Entity Title included in the file header is configurable. The default value set in the File Meta Information for this AE is: "DICOM Media".
3.5.3.2 REAL-WORLD ACTIVITIES
3.5.3.2.1
REAL-WORLD ACTIVITY "EXPORT TO USB"
"Export to USB" saves the selected DICOM SOP instances to the USB medium and creates a DICOM File Set. If a DICOM File Set created by the Sonosite PX exists on the medium, any new files selected for export will be added to the existing files. The Media Export AE acts as a File Set Creator when requested to export SOP instances from the internal storage to a USB medium. If there is insufficient space on the medium, the user will be prompted with an informative message.
Limitations: The user cannot review or manipulate DICOM files written to the USB medium on the system.
3.5.3.2.1.1 Media Storage Application Profile for the real-world activity "Export to USB"
Not applicable [FUTURE]
3.5.3.2.1.1.1 Options This Application Entity supports the SOP Classes and Transfer Syntaxes listed below in Table 3-34:
Table 3-34 SOP Classes and Transfer Syntaxes for Media Export
Abstract Syntax
Name
UID
Media Storage Directory Storage
1.2.840.10008.1.3.10
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1
Comprehensive SR Storage Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.33 1.2.840.10008.5.1.4.1.1.88.11
Transfer Syntax
Name List
UID List
Explicit VR Little Endian
1.2.840.10008.1.2.1
Explicit VR Little
Endian
1.2.840.10008.1.2.1
JPEG Baseline (Process 1.2.840.10008.1.2.4.50
1)
Explicit VR Little
Endian
1.2.840.10008.1.2.1
JPEG Baseline (Process 1.2.840.10008.1.2.4.50
1)
Explicit VR Little Endian
1.2.840.10008.1.2.1
Explicit VR Little Endian
1.2.840.10008.1.2.1
Sec. 3.2.4 Common Composite Image IOD Module describes image module usage by Sonosite PX.
3.5.4 AUGMENTED AND PRIVATE APPLICATION PROFILES
Not applicable.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 40 of 48
3.5.5 MEDIA CONFIGURATION
The Application Entity Titles configurable for Media Services are listed below:
Application Entity: "Media Export"
Default AE Title: "DICOM Media"
3.5.6 MEDIA STORAGE SOP CLASS
The following diagram illustrates the relationship between directory entities in the Basic Directory module produced by Sonosite PX. It is based on the basic DICOM entity relationship model.
Root Directory Entity
1 includes
1-n Patient DR
1 references
1-n Study DR
1 references
1-n Series DR
1 references
1-n Image DR
Figure 3-2
Sonosite PX Directory Entity Relationship Diagram
The Media Storage SOP Class uses the Basic Directory IOD Modules as shown in Table 3-35.
Table 3-35 Basic Directory IOD Modules
Module File-set Identification Directory Information
Reference 3.1.4.1 3.4.7.2
Usage M U
3.5.7 INFORMATION MODULE DEFINITIONS
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 41 of 48
3.5.7.1 FILE-SET IDENTIFICATION MODULE
Table 3-36 specifies the attributes used from the File-set Identification Module. Table 3-36 File-Set Identification Module
Attribute Name
File-set ID File-set Descriptor ID Specific Character Set of File-set Descriptor File
Tag (0004,1130) (0004,1141)
(0004,1142)
Type 2 3
1C
Attribute Description "SONO_EXPORT" Not Used
Not Used
3.5.7.2 DIRECTORY INFORMATION MODULE
Table 3-37 specifies the attributes used from the Directory Information Module. Table 3-37 Directory Information Module
Attribute Name Offset of the First Directory Record of the Root Directory Entity Offset of the Last Directory Record of the Root Directory Entity File-set Consistency Flag Directory Record Sequence >Offset of the Next Directory Record >Record In-use Flag >Offset of Referenced LowerLevel Directory Entity
>Directory Record Type
>Referenced File ID >Referenced SOP Class UID in File >Referenced SOP Instance UID in File >Referenced Transfer Syntax in UID in File
Tag
(0004,1200)
(0004,1202) (0004,1212) (0004,1220) (0004,1400) (0004,1410) (0004,1420) (0004,1430) (0004,1500) (0004,1510) (0004,1511) (0004,1512)
Type 1 See PS 3.3
Attribute Description
1 See PS 3.3
1 See PS 3.3 2 See PS 3.3
1C See PS 3.3
1C Sonosite PX sets all created records to 0xFFFF
1C See PS 3.3
1C
Sonosite PX Supported Values: PATIENT, STUDY, SERIES, IMAGE
1C See PS 3.3
1C See PS 3.3
1C See S 3.3
1C See PS 3.3
3.5.7.2.1 PATIENT KEYS Table 3-38 specifies the additional keys used for directory records of type PATIENT.
Table 3-38 PATIENT KEYS
Attribute Name Patient's Name Patient ID
Tag (0010,0010) (0010,0020)
Type 2 1
Attribute Description Reference 3.2.4.1 Reference 3.2.4.1
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 42 of 48
3.5.7.2.2 STUDY KEYS Table 3-39 specifies the additional keys used for directory records of type STUDY.
Table 3-39 STUDY KEYS
Attribute Name
Study Date Study Time Study Description Study Instance UID Study ID Accession Number
Tag
(0008,0020) (0008,0030) (0008,1030) (0020,000D) (0020,0010) (0008,0050)
Type
1 1 2 1C 1 2
Attribute Description
Reference 3.2.4.2 Reference 3.2.4.2 Reference 3.2.4.2 Reference 3.2.4.2 Reference 3.2.4.2 Reference 3.2.4.2
3.5.7.2.3 SERIES KEYS Table 3-40 specifies the additional keys used for directory records of type SERIES.
Table 3-40 SERIES KEYS
Attribute Name Modality Series Instance UID Series Number
Tag (0008,0060) (0020,000E) (0020,0011)
Type 1 1 1
Attribute Description Reference 3.2.4.4 Reference 3.2.4.4 Reference 3.2.4.4
3.5.7.2.4 IMAGE KEYS Table 3-41 specifies the additional keys used for directory records of type IMAGE.
Table 3-41 IMAGE KEYS
Attribute Name Instance Number
Tag
Type
Attribute Description
(0020,0013) 1 Reference 3.2.4.7
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 43 of 48
4.1 TCP/IP STACK
The TCP/IP protocol is used.
4 COMMUNICATION PROFILES
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 44 of 48
5 EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS
5.1 PRIVATE TRANSFER SYNTAXES
None
5.2 PRIVATE TAGS
(0019,1110)[UT] Private Tag Contains Synchronicity Worksheet Data
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 45 of 48
CONFIGURATION
5.3 AE TITLE/PRESENTATION ADDRESS MAPPING
The Sonosite PX AE Title and Sonosite PX networking parameters are configurable in DICOM Setup Mode. Port number 104 is the default used for DICOM communication with the Sonosite PX.
5.4 CONFIGURABLE PARAMETERS
5.4.1 SONOSITE PX CONFIGURABLE PARAMETERS PER NETWORK LOCATION
The Sonosite PX system can be configured to operate in multiple network locations. The Sonosite PX local device settings and remote device settings (e.g. Archivers/Worklist/MPPS/Storage Commitment) can be configured for each location. These parameters are intended to be configured by a network/DICOM administrator.
Configurable Sonosite PX Networking and DICOM parameters: DHCP DICOM AE Title IPv4: o IP Address (disabled if DHCP is selected) o Subnet Mask (disabled if DHCP is selected) o Default Gateway (disabled if DHCP is selected) o DNS Address (disabled if DHCP is selected) IPv6: o IP Address (disabled if SLAAC is selected) o Subnet Mask (disabled if SLAAC is selected) o Default Gateway (disabled if SLAAC is selected) o DNS Address (disabled if SLAAC is selected) Transfer Images (End of exam, During the exam) JPEG Compression level Port (default = 104) Wireless properties (see Sonosite PX User Guide for detailed configuration information)
5.4.2 CONFIGURABLE PARAMETERS PER REMOTE DEVICE INSTANCE
Every archiver, storage commit, MPPS, and modality worklist device that Sonosite PX is setup to communicate with has a set of parameters that are configurable in Setup mode. These parameters are intended to be configured by a network/DICOM administrator.
Configurable parameters for each device instance:
DICOM AE Title
IP Address
Port Number
Use DIMSE TLS
(On/Off, see Sonosite PX User Guide for detailed configuration
information)
TLS Client Certificate
(Optional, used for authentication if desired)
TLS Private Key
(Optional, used for authentication if desired)
TLS Private Key Password
(Optional, used for authentication if desired)
TLS Certification Authority
(Optional, used for authentication if desired)
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 46 of 48
Configurable parameters for each Archiver device instance:
SOP Class
Ultrasound Multi-frame (enable/disable)
Photometric Interpretation Monochrome2 / RGB / YBR_FULL_422 (used for JPEG Baseline)
Transfer Syntax
ELE/ILE or JPEG Baseline (applies to US and US-MF images only)
Send Images Only
Selection
Include Basic Txt SR
Selection
Include Comprehensive SR
Selection
Configurable parameters for the Worklist SCP device instance:
Automatic Query Enable
On/Off
Automatic Query Interval
Selection = 30 minutes, 1, 2, 4 , 8, 12, 24 hours
Automatic Query Start Time Selection = 0:00 to 23:00 hours
Modality
Specified in user interface
Scheduled Station AE Title
This Sonosite PX system only or universal matching (used for Broad &
Patient Based Queries)
SPS Date
Today; "Yesterday, Today & Tomorrow"; or universal matching
(Used for Broad & Patient Based Queries)
5.4.3 OTHER CONFIGURABLE PARAMETERS
These settings apply independent of network configuration:
Photometric Interpretation (removable media)
Monochrome2 / RGB / YBR_FULL_422
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 47 of 48
6 SUPPORT OF EXTENDED CHARACTER SETS
The Sonosite PX system supports the ISO 8859 Latin 1 (ISO-IR 100) character set family.
The Specific Character Set key attribute (0008,0005), a type 1C attribute, may be returned by an SCP if that device supports any character set encodings beyond the ISO_IR 6. If the tag is not present in the Worklist query result, the default (i.e. ISO_IR 6, i.e. ASCII) is assumed. If the tag is present, only ISO_IR 6 (ASCII), or ISO_IR 100 (Latin Alphabet # 1) are supported by the Sonosite PX system. All other character set encodings are unsupported and will cause the system to issue a C-Find Cancel. All query results data acquired up to the first detection of an unsupported character set encoding are retained and presented to the user.
\
D25306
Rev: B SonoSite PX DICOM Conformance Statement
Page: 48 of 48
Microsoft Word 2013