accuvix v10 / sonoace x8 - alpha medtech...sonoace x8 implements the necessary dicom services to...

SON OACE X8 DICOM Conformance MEDISON

ACCUVIX V10 / SONOACE X8

DICOM Conformance Statement

Rev 1.0SonoAce Deutschland GmbH

SON OACE X8 DICOM Conformance 2

0 COVER PAGE

Company Name: MEDISON CO., LTD

Produce Name: ACCUVIX V10 / SONOACE X8

Version: 1.0

Internal Document Number:

Date:

1 CONFORMANCE STATEMENT OVERVIEW

SONOACE X8 implements the necessary DICOM services to download worklists from information systems, save

acquired US images and Structured Reports to a network storage device, CD or DVD, print to a networked

hardcopy device and inform the information system about the work actually done.

Table 1-1 provides an overview of the network services supported by ACCUVIX V10 / SONOACE X8.

Table 1-1

NETWORK SERVICES

SOP Classes User of Service (SCU) Provider of Service (SCP)

Transfer

Ultrasound Image Storage Yes No

Ultrasound Multi-frame Image Storage Yes No

Comprehensive SR Yes No

Workflow Management

Modality Worklist Yes No

Storage Commitment Push Model Yes No

Modality Performed Procedure Step Yes No

Print Management

Basic Grayscale Print Management Yes No

Basic Color Print Management Yes No

Table 1-2 provides an overview of the Media Storage Application Profiles supported by SONOACE X8.

Table 1-2

MEDIA SERVICES

Media Storage Application Profile Write Files (FSC or FSU) Read Files (FSR)

DVD – Rewritable

STD-US-SC-MF-DVD Yes No

SON OACE X8 DICOM Conformance 3

SONOACE X8 DICOM Conformance 4

2 TABLE OF CONTENTS

0 COVER PAGE........................................................................................................................................................................2

1 CONFORMANCE STATEMENT OVERVIEW..................................................................................................................3

2 TABLE OF CONTENTS........................................................................................................................................................4

3 INTRODUCTION ..................................................................................................................................................................8

3.1 REVISION HISTORY........................................................................................................................................................8

3.2 AUDIENCE ........................................................................................................................................................................8

3.3 REMARKS .........................................................................................................................................................................8

3.4 DEFINITIONS, TERMS AND ABBREVIATIONS ...........................................................................................................9

3.5 REFERENCES ...................................................................................................................................................................9

4 NETWORKING................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ....10

4.1 IMPLEMENTATION MODEL................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ......... 10

4.1.1 Application Data Flow .........................................................................................................................................10

4.1.2 Functional Definition of AE’s .............................................................................................................................................................................................11

4.1.2.1 Functional Definition of Storage Application Entity................................................................................................................11

4.1.2.2 Functional Definition of Workflow Application Entity ...........................................................................................................11

4.1.2.3 Functional Definition of Hardcopy Application Entity ............................................................................................................................... 12

4.1.3 Sequencing of Real-World Activities .......................................................................................................................................................... 13

4.2 AE SPECIFICATIONS................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ .... 15

4.2.1 Storage Application Entity Specification..............................................................................................................15

4.2.1.1 SOP Classes...................................................................................................................................................................................................................................15

4.2.1.2 Association Policies...................................................................................................................................................................................................................15

4.2.1.2.1 General......................................................................................................................................................................................................................................................................................................................................................................................................... 15

4.2.1.2.2 Number of Associations................................................................................................................................................................................................................................................................................................................................................ 15

4.2.1.2.3 Asynchronous Nature........................................................................................................................................................................................................................................................................................................................................................ 16

4.2.1.2.4 Implementation Identifying Information........................................................................................................................................................................................................................................................................................ 16

4.2.1.3 Association Initiation Policy .................................................................................................................................................... 16

4.2.1.3.1 Activity – Send Images and Structured Reports and Requests Commitment .............................................................................................................................................................. 16

4.2.1.4 Association Acceptance Policy.................................................................................................................................................23

4.2.1.4.1 Activity – Receive Storage Commitment Response.................................................................................................................................................................................................................................................. 23

4.2.2 Workflow Application Entity Specification ....................................................................................................... 25

4.2.2.1 SOP Classes ..............................................................................................................................................................................25

4.2.2.2 Association Establishment Policy.............................................................................................................................................26


4.2.2.2.1 General .................................................................................................................................................................................... 26

4.2.2.2.2 Number of Associations ......................................................................................................................................................... 26

4.2.2.2.3 Asynchronous Nature ............................................................................................................................................................. 26

4.2.2.2.4 Implementation Identifying Information................................................................................................................................ 26

4.2.2.3 Association Initiation Policy .................................................................................................................................................. 27

4.2.2.3.1 Activity – Worklist Update..................................................................................................................................................... 27

4.2.2.3.2 Activity – Acquire Images...................................................................................................................................................... 31

4.2.2.4 Association Acceptance Policy .............................................................................................................................................. 36

4.2.3 Hardcopy Application Entity Specification ......................................................................................................... 37

4.2.3.1 SOP Classes............................................................................................................................................................................ 37

4.2.3.2 Association Policies................................................................................................................................................................ 37

4.2.3.2.1 General .................................................................................................................................................................................... 37

4.2.3.2.2 Number of Association ........................................................................................................................................................... 37

4.2.3.2.3 Asynchronous Nature ............................................................................................................................................................. 37

4.2.3.2.4 Implementation Identifying Information................................................................................................................................ 38

4.2.3.3 Association Initiation Policy .................................................................................................................................................. 38

4.2.3.3.1 Activity – Film Images ........................................................................................................................................................... 38

4.2.3.4 Association Acceptance Policy .............................................................................................................................................. 46

4.3 NETWORK INTERFACE................................................................................................................................................ 47

4.3.1 Physical Network Interface.................................................................................................................................. 47

4.4 CONFIGURATION.......................................................................................................................................................... 47

4.4.1 AE Title/Presentation Address Mapping.............................................................................................................. 47

4.4.1.1 Local AE Titles....................................................................................................................................................................... 47

4.4.1.2 Remote AE Title/Presentation Address Mapping.................................................................................................................. 47

4.4.1.2.1 Storage .................................................................................................................................................................................... 47

4.4.1.2.2 Workflow ................................................................................................................................................................................ 48

4.4.1.2.3 Hardcopy................................................................................................................................................................................. 48

4.4.2 Parameters........................................................................................................................................................... 48

5 MEDIA INTERCHANGE ................................................................................................................................................... 50

5.1 IMPLEMENTATION MODEL........................................................................................................................................ 50

5.1.1 Application Data Flow ........................................................................................................................................ 50

5.1.2 Functional Definition of AEs............................................................................................................................... 50

5.1.2.1 Functional Definition of Offline-Media Application Entity.................................................................................................. 50

5.1.3 Sequencing of Real-World Activities .................................................................................................................. 50

5.1.4 File Meta Information Options ............................................................................................................................ 50

5.2 AE SPECIFICATIONS .................................................................................................................................................... 51


5.2.1 Offline-Media Application Entity Specification................................................................................................. 51

5.2.1.1 File Meta Information for the Application Entity.................................................................................................................. 51

5.2.1.2 Real-World Activitiesdynamix0 ............................................................................................................................................ 51

5.2.1.2.1 Activity – Export to DVD ..................................................................................................................................................... 51

6 SUPPORT OF CHARACTER SETS...................................................................................................................................53

7 SECURITY ...........................................................................................................................................................................54

8 ANNEXES.............................................................................................................................................................................55

8.1 IOD CONTENTS..............................................................................................................................................................55

8.1.1 Created SOP Instances ....................................................................................................................................... 55

8.1.1.1 US or US Multiframe Image IOD .......................................................................................................................................... 55

8.1.1.2 Comprehensive Structured Report IOD ................................................................................................................................. 56

8.1.1.3 Common Modules .................................................................................................................................................................. 56

8.1.1.4 US or US Multiframe Image Module..................................................................................................................................... 60

8.1.1.5 Comprehensive Structured Report Modules .......................................................................................................................... 64

8.1.2 Used Fields in received IOD by application ....................................................................................................... 67

8.1.3 Attribute mapping .............................................................................................................................................. 67

8.1.4 Coerced/Modified Fields.................................................................................................................................... 68

8.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES......................................................................................................69

8.3 CODED TERMINOLOGY AND TEMPLATES ..............................................................................................................69

8.4 GRAYSCALE IMAGE CONSISTENCY .........................................................................................................................69

8.5 STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES ......................................................................69

8.5.1 US OR US MULTIFRAME IMAGE STORAGE SOP CLASS......................................................................... 69

8.6 PRIVATE TRANSFER SYNTAXES ...............................................................................................................................69

9 STRUCTURED REPORT TEMPLATES...........................................................................................................................70

9.1 TEMPLATES USED IN SONOACE X8 .............................................................................................................................70

9.1.1 OB-GYN STRUCTURED REPORT TEMPLATE............................................................................................ 71

9.1.1.1 OB-GYN Ultrasound Procedure Report (TID 5000)............................................................................................................. 71

9.1.1.2 Observation Context (TID 1001) ........................................................................................................................................... 72

9.1.1.3 Patient Characteristics (TID 5001)......................................................................................................................................... 73

9.1.1.4 OB-GYN Procedure Summary Section (TID 5002) .............................................................................................................. 75

9.1.1.5 Fetal Biometry Ratio Section (TID 5004).............................................................................................................................. 78

9.1.1.6 Fetal Biometry Section (TID 5005) ....................................................................................................................................... 79

9.1.1.7 Long Bones Section (TID 5006) ............................................................................................................................................ 83

9.1.1.8 Fetal Cranium Section (TID 5007)......................................................................................................................................... 85


9.1.1.9 Fetal Biophysical Profile Section (TID 5009) ........................................................................................................................87

9.1.1.10 Early Gestation Section (TID 5011) .......................................................................................................................................88

9.1.1.11 Amniotic Sac Section (TID 5010)...........................................................................................................................................91

9.1.1.12 Pelvis and Uterus Section (TID 5015) ....................................................................................................................................92

9.1.1.13 Ovaries Section (TID 5012) ....................................................................................................................................................94

9.1.1.14 Follicles Section - Left (TID 5013).........................................................................................................................................96

9.1.1.15 Follicles Section – Right (TID 5013)......................................................................................................................................97

9.2 DCMR CONTEXT GROUPS USED IN SONOACE X8............................................................................................................ 99

9.2.1 Gestational Age Equations and Tables (Context Group 12013) ........................................................................... 99

9.2.2 OB Fetal Body Weight Equations and Tables (Context ID 12014) .................................................................... 100

9.2.3 Fetal Growth Equations and Tables (Context ID 12015) ................................................................................... 101

9.2.4 Estimated Fetal Weight Percentile Equations and Tables (Context ID 12016)................................................... 102


3 INTRODUCTION

3.1 REVISION HISTORY

Document Version Date of Issue Author Description

1.0 Draft March 20, 2007 MEDISON Draft Versoin1.0 Draft Check May 3, 2007 MEDISON Checking Version of the

draft

1.0 Trial-Use Draft May 3, 2007 MEDISON

3.2 AUDIENCE

This document is intended for hospital staff, health system integrators, software designers or implementers. It is

assumed that the reader has a working understanding of DICOM.

3.3 REMARKS

DICOM, by itself, does not guarantee interoperability. However, the Conformance Statement facilitates a first-level

validation for interoperability between different applications supporting the same DICOM functionality.

This Conformance Statement is not intended to replace validation with other DICOM equipment to ensure proper

exchange of information intended.

The scope of this Conformance Statement is to facilitate communication with MEDISON and other vendor’s

Medical equipment. The Conformance Statement should be read and understood in conjunction with the DICOM

Standard [DICOM]. However, it is not guaranteed to ensure by itself the desired interoperability and a successful

interconnectivity.

The user should be aware of the following important issues:

The comparison of different conformance statements is the first step towards assessing interconnectivity between

MEDISON and non – MEDISON equipment.

Test procedures should be defined to validate the desired level of connectivity.

The DICOM Standard will evolve to meet the users’ future requirements. MEDISON is activity involved in

developing the standard further and therefore reserves the right to make changes to its products or to discontinue

their delivery.


3.4 DEFINITIONS, TERMS AND ABBREVIATIONS

Definitions, terms and abbreviations used in this document are defined within the different parts of the DICOM

Standard.

Abbreviations and terms are as follows:

AE DICOM Application Entity

AET Application Entity Title

ASCE Association Control Service Element

CD-R Compact Disk Recordable

FSC File-Set Creator

FSU File-Set Updater

FSR File-Set Reader

IOD (DICOM) Information Object Definition

ISO International Standard Organization

MPPS Modality Performed Procedure Step

MSPS Modality Scheduled Procedure Step

R Required Key Attribute

O Optional Key Attribute

PDU DICOM Protocol Data Unit

SCU DICOM Service Class User (DICOM client)

SCP DICOM Service Class Provider (DICOM server)

SOP DICOM Service-Object Pair

U Unique Key Attribute

3.5 REFERENCES

[DICOM] Digital Imaging and Communications in Medicine (DICOM), NEMA PS 3.1–3.18, 2007


4.1 IMPLEMENTATION MODEL

4.1.1 Application Data Flow

DICOM Standard Interface

Figure 4.1-1

APPLICATION DATA FLOW DIAGRAM

- The Storage Application Entity sends images, Structured Reports and requests Storage Commitment to a

remote AE. It is associated with the local real-world activities “Send Images & Reports” and “Request

Commitments”. Methods to send images depend on user configuration, “Batch”, “Send As You Go” or

4 NETWORKING

StorageApplication

Entity

RemoteApplication EntityReceives Images

& Reports

RemoteApplication Entity

ConfirmsCommitments

WorkflowApplication

Entity

RemoteApplication EntityProvides Worklist

Items

RemoteApplication EntityReceives MPPSCreate/Update

HardcopyApplication

Entity

RemoteApplication EntityPrints Film Sheets

Film Images

Send Images& reports

RequestCommitments

UpdateWorklist

AcquireImages


“Manual”. “Manual” mode is performed upon user request for each study or for specific images selected.

“Batch” mode starts to send images at End Exam for each study. “Send As You Go” mode starts when

the first image is acquired for each study and images are transferred immediately after acquisition.

Structured Reports are only sent at End Exam for each study.

If the remote AE is configured as an archive device, the Storage AE will request Storage Commitment and if

a commitment is successfully obtained, it will record this information in the local database and displayed it

in the Exam List.

- The Workflow Application Entity receives Worklist information from and sends MPPS information to a

remote AE. It is associated with the local real-world activities “Update Worklist” and “Acquire Images”.

When the “Update Worklist” local real-world activity is performed, the Workflow Application Entity queries a

remote AE for worklist items and provides the set of worklist items matching the query request. “Update

Worklist” is performed as a result of an operator request or can be performed automatically at specific time

intervals. When the “Acquire Images” local real-world activity is performed, the Workflow Application

Entity creates and updates Modality Performed Procedure Step instances managed by a remote AE.

Acquisition of images will result in automated creation of an MPPS Instance. Completion of the MPPS is

performed at End Exam for each study.

- The Hardcopy Application Entity prints images on a remote AE (Printer). It is associated with the local

real-world activity “Film Images”. Methods to film Images depend on user configuration and are equal to

the Sending images’ of the Storage Application Entity.

4.1.2 Functional Definition of AE’s

4.1.2.1 Functional Definition of Storage Application Entity

The existence of a send-job with associated network destination will activate the Storage AE. An association

request is sent to the destination AEs and upon successful negotiation of a Presentation Context, the image

transfer is started. If the association cannot be opened, the related send-job is set to an error state and can be

restarted by the user via DICOM manager interface or automatically. An automatic retry (retry interval, retry count)

can be configured using the Setup/DICOM Menu.

4.1.2.2 Functional Definition of Workflow Application Entity

Worklist Update attempts to download a Worklist from a remote node. If the Workflow AE establishes an

association to a remote AE, it will transfer all matching worklist items via the open Association. By default,


Worklist Update use “US” for Modality, current date for Scheduled Procedure Step Start Date and blank for

Scheduled Station AE-Title as query parameters. The results will be displayed in a separate list, which will be

cleared with the next Worklist Update.

The Workflow AE performs the creation of an MPPS Instance automatically whenever the first image is acquired for

each study. The MPPS “Complete” states can only be set by “End Exam” for each study.

4.1.2.3 Functional Definition of Hardcopy Application Entity

The existence of a print-job will activate the Hardcopy AE. An association is established with the printers and the

printer’s status determined. If the printer is operating normally, the film sheets described within the print-job will be

printed. If the printer is not operating normally, the print-job will set to an error state and can be restarted by the

user via DICOM manager interface or automatically. An automatic retry (retry interval, retry count) can be

configured using the Setup/DICOM Menu.


4.1.3 Sequencing of Real-World Activities


Image ManagerStorage Hardcopy Workflow Department Scheduler Printer

4. Start Exam

9. End Exam10. Complete Acquisition (Finalize MPPS)

12. Commit Acquired Images & SR Documents

3. Select Workitem

6. Acquire Image

5. Start Acquisition (Create MPPS)

13. Receive Commitment Result

2. Receive Worklist

8. Print Acquired Image

1. Query Worklist

9. Store Acquired Images

11. Store SR Documents


Figure 4.1-2

SEQUENCING CONTRAINTS – SEND AS YOU GO


Figure 4.1-3

SEQUENCING CONSTRAINTS – BATCH MODE

Under normal scheduled workflow conditions, the sequencing constraints are illustrated in Figure 4.1-2 and Figure

4.1-3.

Image ManagerStorage Hardcopy Workflow Department Scheduler Printer

4. Start Exam

7. End Exam8. Complete Acquisition (Finalize MPPS)

12. Commit Acquired Images & SR Documents

3. Select Workitem

6. Acquire Image

5. Start Acquisition (Create MPPS)

13. Receive Commitment Result

11. Print Acquired Images

2. Receive Worklist

1. Query Worklist

9. Store Acquired Images

11.Store SR Documents


Other workflow situations (e.g. unscheduled procedure steps) will have other sequencing constraints. Printing could

equally take place after the images acquired have been stored. Printing could be omitted completely if no printer is

connected or hardcopies are not required.

4.2 AE SPECIFICATIONS

4.2.1 Storage Application Entity Specification

4.2.1.1 SOP Classes

SONOACE X8 provides Standard Conformance to the following SOP Classes:

Table 4.2-1

SOP CLASSES FOR AE STORAGE

SOP Classes SOP Class UID SCU SCP

Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Yes No

Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 Yes No

Comprehensive Structured Report Storage 1 .2.840.10008.5.1 .4.1 .1 .88.33 Yes No

Storage Commitment Push Model 1.2.840.10008.1.20.1 Yes No

Verification 1 .2.840.10008.1 .1 Yes Yes

4.2.1.2 Association Policies

4.2.1.2.1 General

The DICOM Standard application context name for DICOM 3.0 is always proposed:

Table 4.2-2

DICOM APPLICATION CONTEXT FOR AE STORAGE

Application Context Name 1 .2.840.10008.3.1 .1 .1

4.2.1.2.2 Number of Associations

SONOACE X8 can initiate one or more Associations at a time for each destination to which a transfer request is

being processed in the active job queue list.

Table 4.2-3


NUMBER OF ASSOCIATIONS INITIATED FOR AE STORAGE

Maximum number of simultaneous Associations Unlimited

SONOACE X8 accepts Associations to receive N-EVENT_REPORT notifications for the Storage Commitment Push

Model SOP Class.

Table 4.2-4

NUMBER OF ASSOCIATIONS ACCEPTED FOR AE STORAGE

Maximum number of simultaneous Associations Unlimited

4.2.1.2.3 Asynchronous Nature

SONOACE X8 does not support asynchronous communications (multiple outstanding transactions over a single

Association).

Table 4.2-5

ASYNCHRONOUS NATURE AS A SCU FOR AE STORAGE

Maximum number of outstanding asynchronous transactions 1

4.2.1.2.4 Implementation Identifying Information

The implementation information for this Application Entity is:

Table 4.2-6

DICOM IMPLEMENTATION CLASS AND VERSION FOR AE STORAGE

Implementation Class UID 1 .2.410.200001 .1 .0001

Implementation Version Name P6A1_0

4.2.1.3 Association Initiation Policy

4.2.1.3.1 Activity – Send Images and Structured Reports and Requests Commitment

4.2.1.3.1.1 Description and Sequencing of Activities

A user can select exams or images and request them to be sent to some destination. Each request is forwarded

to the job queue and processed individually. When the “Batch” or “Send As You Go” option is active, Stored

images and reports will be forwarded to the network job queue for a pre-configured auto-send target destination


automatically. For “Batch” and “Manual” configuration, the system opens an association, sends all images in the

study, and closes the association. If “Send As You Go” is selected, the system handles the association with the

Storage SCP Server using the following method.

a. Open an Association when the first image is acquired, and keep association open until the study is

closed.

b. If an error occurs while sending an image to the server because there is no longer an open association

(server timed-out), attempt to re-establish the association.

c. When the study is closed, close the open association after images remained in that study are sent.

Structured Reports are only sent over a separate association at End Exam For.

If the remote AE is configured as an archive device, the Storage AE will, after all images and reports have been

sent, transmit Storage Commitment request (N-ACTION) over a separate Association. The Storage AE can only

receive an N-EVENT-REPORT request in a subsequent association initiated by the SCP.


Image ManagerStorage AE

1. Open Association

2. C-STORE (Images)

3. Close Association

4. Open Association

5. C-STORE (SR Documents)


7. Open Association

8. N-ACTION (Storage Commitment Request for Images & SR Documents


10. Open Association

11. N-EVENT-REPORT (Storage Commitment Response)


Figure 4.2-1

SEQUENCING OF ACTIVITY - SEND IMAGES

A possible sequence of interactions between the Storage AE and an Image Manager (e.g. a storage or archive

device supporting the Storage and Storage Commitment SOP Classes as an SCP) is illustrated in the figure above.

NOTE: The N-EVENT-REPORT must be sent over a separate association initiated by the Image Manager.

(See Section 4.2.1.4)


4.2.1.3.1.2 Proposed Presentation Contexts

SONOACE X8 is capable of proposing the Presentation Contexts shown in the following table.

Table 4.2-7

PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY SEND IMAGES

Presentation Context Table

Abstract Syntax Transfer Syntax Role Ext.

Name UID Name List UID List Neg.

Ultrasound Image 1.2.840.10008.5. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Storage 1.4.1.1.6.1

Ultrasound Multi-frame 1.2.840.10008.5. JPEG Lossy Baseline 1.2.840.10008.1.2.4 SCU None

Image Storage 1.4.1.1.3.1 .50

Comprehensive 1.2.840.10008.5. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Structured Report 1.4.1.1.88.33

Storage

Storage Commitment 1.2.840.10008.1. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Push Model 20.1 Explicit VR Little Endian 1.2.840.10008.1.2.1

Verification 1.2.840.10008.1. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None1 Explicit VR Little Endian 1.2.840.10008.1.2.1

Presentation Contexts for Ultrasound Image Storage and Ultrasound Multi-frame Image Storage will be proposed

for the “Storage” device configured in Setup/DICOM.

A Presentation Context for Comprehensive Structured Report Storage will be proposed for the “Storage SR” device

configured in Setup/DICOM.

A Presentation Context for Storage Commitment Push Model will be proposed for the “SC” device configured in

Setup/DICOM.

A Presentation Context for Verification will be proposed when a user press the “Test” button for a configured device.


4.2.1.3.1.3 SOP Specific Conformance Image & Comprehensive Structured Report Storage SOP

Classes

All Image & Structured Report Storage SOP Classes supported by the Storage AE exhibit the same behavior,

except where stated, and are described together in this section.

Table 4.2-8

STORAGE C-STORE RESPONSE STATUS HANDLING BEHAVIOR

Service

Status

Further Meaning Error Code Behavior

Success Success 0000The SCP has successfully stored the SOP Instance. If all

SOP Instances succeed, the job is marked as complete.

Refused Out of Resources A700-A7FFThe association is aborted using A-ABORT and the send job

is marked as failed. The status is logged.

ErrorData Set does not

match SOP ClassA900-A9FF Same as "Refused" above.

ErrorCannot

UnderstandC000-CFFF Same as "Refused" above.

Warning Coercion of Data

ElementsB000

Image transmission is considered successful.

Warning Data Set does not

match SOP ClassB007

Same as "Warning" above.

Warning Elements Discards B006 Same as "Warning" above.* * Any other status

code.Same as "Refused" above.

The Behavior of Storage AE during communication failure is summarized in the Table below:

Table 4.2-9

STORAGE COMMUNICATION FAILURE BEHAVIOR

Exception BehaviorTimeout The Association is aborted using A-ABORT

and the send job is marked as failed.

Association aborted by the SCP or network layers The Send job is marked as failed.

A failed send job can be restarted by user interaction. The system can be configured to automatically resend failed


jobs if a transient status code is received. The delay between resending failed jobs and the number of retries is also

configurable.

4.2.1.3.1.4 SOP Specific Conformance for Storage Commitment SOP Class

4.2.1.3.1.4.1 Storage Commitment Operations (N-ACTION)

The Storage AE will request storage commitment for the configured device for instances of the Ultrasound Image,

Ultrasound Multi-frame Image and Structured Report Storage SOP Classes.

The Storage AE will consider Storage Commitment failed if no N-EVENT-REPORT is received for a Transaction

UID within a configurable time period after receiving a successful N-ACTION response (duration of applicability for

a Transaction U ID).

The Storage AE does not send the optional Storage Media FileSet ID & UID Attributes or the Referenced Study

Component Sequence Attribute in the N-ACTION

The Behavior of Storage AE when encountering status codes in an N-ACTION response is summarized in the Table

below:

Table 4.2-10

STORAGE COMMITMENT N-ACTION RESPONSE STATUS HANDLING BEHAVIOR

Service

Status

Further

Meaning

Error Code Behavior

Success Success 0000

The request for storage comment is considered successfully

sent. The system waits for the association of the N-Event-

Report.

* *Any other status

code.

The Association is aborted using A-Abort and the request for

storage comment is marked as failed

The behavior of Storage AE during communication failure is summarized in the Table below:

Table 4.2-11

STORAGE COMMITMENT COMMUNICATION FAILURE BEHAVIOR

Exception BehaviorTimeout The Association is aborted using A-ABORT and

the storage commitment job is marked as failed.

Association aborted by the SCP or network layers The storage commitment job is marked as

failed.


4.2.1.3.1.4.2 Storage Commitment Notification (N-EVENT-REPORT)

The Storage AE is capable of receiving an N-EVENT-REPORT notification if it has successfully negotiated a

Presentation Context for the Storage Commitment Push Model.

Upon receipt of an N-EVENT-REPORT the timer associated with the Transaction UID will be cancelled.

The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is summarized in the Table

below.

Table 4.2-12

STORAGE COMMITMENT N-EVENT-REPORT BEHAVIOR

Event Type Name Event Type

ID

Behavior

Storage Commitment

Request Successful

1 The commit status is set to “Y” for each exam in the exam list.

Auto deletion for committed exam is not supported.

Storage Commitment

Request Complete –

Failures Exists

2 The commit status is set to “N” for each exam in the exam list.

The Referenced SOP Instances under Failed SOP Sequence

(0008, 1198) are logged. A send job that failed storage commitment

will not be automatically restarted but can be restarted by user

interaction.

The reasons for returning specific status codes in an N-EVENT-REPORT response are summarized in the Table

below.

Table 4.2-13

STORAGE COMMITMENT N-EVENT-REPORT RESPONSE STATUS REASONS

Service

Status

Further Meaning Error

Code

Behavior

Success Success 0000The Storage commitment result has been successfully

received.

FailureUnrecognized

Operation0211H

The Transaction UID in the N_EVENT_REPORT request is not

(was never issued within an N_ACTION request)

FailureNo Such Event Type

01 13HAn invalid Event Type ID was supplied in the


N_EVENT_REPORT request

Failure Processing Failure 01 10HAn internal error occurred during processing of the

N_EVENT_REPORT

4.2.1.3.1.5 SOP Specific Conformance for Verification

The Behavior when encountering status codes in a C-ECHO response is summarized in the Table below:

Table 4.2-14

VERIFICATION C-ECHO RESPONSE STATUS HANDLING BEHAVIOR

Service

Status

Further

Meaning

Error Code Behavior

Success Success 0000 Verification Status is set to ‘Normal’

* * Any other status code Verification Status is set to ‘Failed’

The Behavior of Storage AE during communication failure is summarized in the Table below:

Table 4.2-15

VERIFICATION COMMUNICATION FAILURE BEHAVIOR


the verification job is marked as failed.

Association aborted by the SCP or network layers The verification job is marked as failed.

4.2.1.4 Association Acceptance Policy

4.2.1.4.1 Activity – Receive Storage Commitment Response

4.2.1.4.1.1 Description and Sequence of Activities

The Storage AE will accept associations in order to receive responses to a Storage Commitment Request.


Image ManagerStorage AE

1. Open Association

2. N-EVENT-REPORT (Storage Commitment Response)


Figure 4.2-2

SEQUENCING OF ACTIVITY - RECEIVE STORAGE COMMITMENT RESPONSE

A possible sequence of interactions between the Storage AE and an Image Manager (e.g. a storage or archive

device supporting Storage Commitment SOP Classes as an SCP) is illustrated in the Figure above:

1. The Image Manager opens a new association with the Storage AE.

2. The Image Manager sends an N-EVENT-REPORT request notifying the Storage AE of the status of a

previous Storage Commitment Request. The Storage AE replies with an N-EVENT-REPORT response

confirming receipt.

3. The Image Manager closes the association with the Storage AE.

4.2.1.4.1.2 Accepted Presentation Contexts

The Storage AE will accept Presentation Contexts as shown in the Table below.

Table 4.2-16

ACCEPTABLE PRESENTATION CONTEXTS FOR ACTIVITY

RECEIVE STORAGE COMMITMENT RESPONSE


Abstract Syntax Transfer Syntax

Name UID Name List UID List

Role Ext.

Neg.


Storage 1.2.840.10008.1. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Commitment 20.1 Explicit VR Little Endian 1.2.840.10008.1.2.1

Push Model

Verification 1.2.840.10008.1. Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

1 Explicit VR Little Endian 1.2.840.10008.1.2.1

4.2.1.4.1.3 SOP Specific Conformance for Storage Commitment SOP Class

4.2.1.4.1.3.1 Storage Commitment Notifications (N-EVENT-REPORT)

Upon receipt of an N-EVENT-REPORT the timer associated with the Transaction UID will be cancelled.

The behavior of Storage AE when receiving Event Types within the N-EVENT_REPORT is summarized in Table

4.2-12.

The reasons for returning specific status codes in an N-EVENT-REPORT response are summarized in Table 4.2-13.

4.2.1.4.1.4 SOP Specific Conformance for Verification SOP Class

The Storage AE provides standard conformance to the Verification SOP Class as an SCP. If the C-ECHO request

was successfully received, a 0000 (Success) status code will be returned in the C-ECHO response.

4.2.2 Workflow Application Entity Specification

4.2.2.1 SOP Classes


Table 4.2-17

SOP CLASSES FOR AE WORKFLOW


Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No

Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No


4.2.2.2 Association Establishment Policy

4.2.2.2.1 General

The DICOM standard application context name for DICOM 3.0 is always proposed.

Table 4.2-18

DICOM APPLICATION CONTEXT FOR AE WORKFLOW

Application Context Name 1.2.840.10008.3.1.1.1

4.2.2.2.2 Number of Associations

SONOACE X8 initiates one Association at a time for a Worklist request.

Table 4.2-19

NUMBER OF ASSOCIATIONS INITIATED FOR AE WORKFLOW

Maximum number of simultaneous Associations 1



Association)

Table 4.2-20

ASYNCHRONOUS NATURE AS A SCU FOR AE WORKFLOW




Table 4.2-21

DICOM IMPLEMENTATION CLASS AND VERSION FOR AE WORKFLOW

Implementation Class UI D 1.2.410.200001.1.0001

Implementation Version Name P6A1 _0



4.2.2.3.1 Activity – Worklist Update


The request for a Worklist Update is initiated by user interaction or automatically at specific time intervals,

configurable by the user.

The interactive Worklist Query will display a dialog for entering data as search criteria. When the Query is started

on your request, only the data from the dialog will be inserted as matching keys into the query.

With automated worklist queries the SONOACE X8 always requests all items for a Scheduled Procedure Step Start

Date (actual date), Modality (US) and Scheduled Station AE Title.

Upon initiation of the request, the SONOACE X8 will build an Identifier for the C-FIND request, will initiate an

Association to send the request and will wait for Worklist responses. After retrieval of all responses, SONOACE X8

will access the local database to add patient demographic data. The results will be displayed in a separate list,

which will be cleared with the next worklist update.

SONOACE X8 will initiate an Association in order to issue a C-FIND request according to the Modality Worklist

Information Model.


Department SchedulerWorkflow AE


1. Open Association

2. C-FIND Request (Worklist Query)

3. C-FIND Response (Worklist Item) - Status=Pending

4. C-FIND Response (Worklist Item) - Status=Pending

5. C-FIND Response - Status=Success6. Close Association

7. Select Worklist Item


Figure 4.2-3

SEQUENCING OF ACTIVITY - WORKLIST UPDATE

A possible sequence of interactions between the Workflow AE and a Departmental Scheduler (e.g. a device such

as a RIS or HIS which supports the Modality Worklist SOP Class as an SCP) is illustrated in the figure above:


SONOACE X8 will propose Presentation Contexts as shown in the following table:

Table 4.2-22

PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY WORKLIST UPDATE




Role Ext.

Neg.

Modality Worklist

Information

Model - FIND

1.2.840.10008.

5.1.4.31

Implicit VR Little Endian

Explicit VR Little Endian

1.2.840.10008.1.2

1.2.840.10008. 1.2.1

SCU None


4.2.2.3.1.3 SOP Specific Conformance for Modality Worklist

The behavior of SONOACE X8 when encountering status codes in a Modality Worklist C-FIND response is

summarized in the Table below. If any other SCP response status than “Success” or “Pending” is received by

SONOACE X8, a message ”Query failed” will appear on the user interface.

Table 4.2-23

MODALITY WORKLIST C-FIND RESPONSE STATUS HANDLING BEHAVIOR

Service

Status


Code

Behavior

SuccessMatching is complete

0000The SCP has Completed the operation

successfully.

Pending Matches are continuing FF00 Continue.

Pending

Matches are continuing -

Warning that one or more

Optional Keys were not

supported

FF01 Continue.

* *

Any other

status

code.

The Association is aborted using A-Abort and the

Worklist is marked as failed

The behavior of SONOACE X8 during communication failure is summarized in the Table below.

Table 4.2-24

MODALITY WORKLIST COMMUNICATION FAILURE BEHAVIOR


the worklist query is marked as failed.

Association aborted by the SCP or network layers The Worklist query is marked as failed.

Acquired images will always use the Study Instance UID specified for the Scheduled Procedure Step (if available).

If an acquisition is unscheduled, a Study Instance UID will be generated locally.

The Table below provides a description of the SON OACE X8 Worklist Request Identifier and specifies the attributes

that are copied into the images. Unexpected attributes returned in a C-FIND response are ignored.


Requested return attributes not supported by the SCP are set to have no value. Non-matching responses returned

by the SCP due to unsupported optional matching keys are ignored. No attempt is made to filter out possible

duplicate entries.

Table 4.2-25

WORKLIST REQUEST IDENTIFIER

Module Name

Attribute Name

Tag

VR M R Q D IOD

Scheduled Procedure Step

Scheduled Procedure Step Sequence 0040,0100 SQ x

> Scheduled Station AET 0040,0001 AE (S) x x

> Scheduled Procedure Step Start Date 0040,0002 DA S,R x x x

> Scheduled Procedure Step Start Time 0040,0003 TM x x

> Modality 0008,0060 CS S x x

> Scheduled Performing Physician's Name 0040,0006 PN x

> Scheduled Procedure Step Description 0040,0007 LO x x x

> Scheduled Station Name 0040,0010 SH x

> Scheduled Procedure Step Location 0040,0011 SH x

> Scheduled Protocol Code Sequence 0040,0008 SQ x x

> Scheduled Procedure Step ID 0040,0009 SH x x

Requested Procedure

Requested Procedure ID 0040,1001 SH x x x

Requested Procedure Description 0032,1060 LO x

Study Instance UID 0020,000D UI x x

Referenced Study Sequence 0008,1110 SQ x x

Requested Procedure Code Sequence 0032,1064 SQ x x

Imaging Service Request

Accession Number 0008,0050 SH x x x

Requesting Physician 0032,1032 PN x

Referring Physician's Name 0008,0090 PN x x

Visit Status

Current Patient Location 0038,0300 LO x

Patient Identification

Patient’s Name 0010.0010 PN x x x

Patient ID 0010,0020 LO x x x

Patient Demographic


Patient's Birth Date 0010,0030 DA x x x

Patient's Sex 0010,0040 CS x x x

Patient’s Size 0010,1020 DS x x x

Patient's Weight 0010,1030 DS x x x

The above table should read as follows:

Module Name: The Name of the associated module for supported worklist attributes.

Attribute Name: Attributes supported to build an SONOACE X8 Worklist Request Identifier.

Tag: DICOM tag for this attribute.

VR: DICOM VR for this attribute.

M: Matching keys for (automatic) Worklist Update. An “S” indicates that SONOACE X8 supplies an

attribute value for Single Value Matching or additional specific tags indicated by “(S)”; an “R”

will indicate Range Matching.

R: Return keys. An ”X” will indicate that SONOACE X8 will supply this attribute as Return Key with

zero length for Universal Matching.

Q: Interactive Query Key. An “X” will indicate that SONOACE X8 will supply this attribute as

matching key, if entered in the Setup Dialog.

D: Displayed keys. An “X” indicates that this worklist attribute is displayed to the user during a

patient registration dialog.

IOD: An “X” indicates that this Worklist attribute is included into all Object Instances created during

performance of the related Procedure Step.

4.2.2.3.2 Activity – Acquire Images


An Association to the configured MPPS SCP system is established immediately after the first image is acquired to

send the MPPS N-Create message.

The “End Exam” button causes a “COMPLETED” message. An exam for which an MPPS instance is sent with a

state of “COMPLETED” can no longer be updated.

The SONOACE X8 will support creation of “unscheduled cases” by allowing MPPS Instances to be communicated

for locally registered Patients.

The SONOACE X8 only supports a 1-to-1 relationship between Scheduled and Performed Procedure Steps.

SONOACE X8 will initiate an Association to issue an:


N-CREATE request according to the CREATE Modality Performed Procedure Step SOP Instance

operation, or an:

N-SET request to update the contents and state of the MPPS according to the SET Modality Performed

Procedure Step Information operation.

Figure 4.2-4

SEQUENCING OF ACTIVITY - ACQUIRE IMAGES

A possible sequence of interactions between the Workflow AE and a Departmental Scheduler (e.g. a device such

as a RIS or HIS which supports the MPPS SOP Class as an SCP) is illustrated in the figure above:

Workflow AE Department Scheduler

5. Acquire Images

1. Start Exam

6. End Exam

3. N-CREATE (MPPS) - IN PROGRESS

8. N-SET (MPPS) - COMPLETED



2. Open Association

7. Open Association



SONOACE X8 will propose Presentation Contexts as shown in the following table:

Table 4.2-26

PROPOSED PRESENTATION CONTEXTS FOR REAL-WORLD ACTIVITY ACQUIRE IMAGES




Role Ext.

Neg.

Modality Performed

Procedure Step

1.2.840.10008.

3.1.2.3.3



1.2.840.10008.1.2

1.2.840.10008. 1.2.1

SCU None

4.2.2.3.2.3 SOP Specific Conformance for MPPS

The behavior of SONOACE X8 when encountering status codes in an MPPS N-CREATE or N-SET response is

summarized in the Table below. If any other SCP response status than “Success” or “Warning” is received by

SONOACE X8, a message “MPPS failed” will appear on the user interface.

Table 4.2-27

MPPS N-CREATE / N-SET RESPONSE STATUS HANDLING BEHAVIOR

Service

Status

Further Meaning Error Code Behavior

Success Success 0000The SCP has Completed the operation

successfully.

WarningAttribute Value Out of

Range01 16H The MPPS Operation is considered successful.

* * Any other status

code.

The Association is aborted using A-Abort and the

MPPS is marked as failed

The behavior of SONOACE X8 during communication failure is summarized in the table below:

Table 4.2-28


MPPS COMMUNICATION FAILURE BEHAVIOR


the MPPS job is marked as failed.

Association aborted by the SCP or network layers The MPPS job is marked as failed.

Table 4.2-29 provides a description of the MPPS N-CREATE and N-SET request identifiers send by SONOACE X8.

Empty cells in the N-CREATE and N-SET columns indicate that the attribute is not sent.

Table 4.2-29

MPPS N-CREATE / N-SET REQUEST IDENTIFIER

Attribute Name Tag VR N-CREATE N-SET

Specific Character Set 0008,0005 CS "ISO_IR 100"

Performed Procedure Step Relationship

Scheduled Step Attribute

Sequence0040,0270 SQ

> Study Instance UID 0020,000D UIFrom MWL or generated

by device

> Referenced Study Sequence 0008,1110 SQ From MWL

>> Referenced SOP Class UID 0008.1150 UI From MWL

>> Referenced SOP Instance

UID

0008,1155UI From MWL

> Accession Number 0008,0050 SH From MWL or user input

> Requested Procedure ID 0040,1001 SH From MWL

> Requested Procedure

Description0032,1060 LO From MWL

> Scheduled Procedure Step

ID

0040,0009SH From MWL

> Scheduled Procedure Step

Description

0040,0007LO From MWL

> Scheduled Protocol Code

Sequence

0040,0008SQ From MWL

>> Code Value 0008,0100 SH From MWL

>> Coding Scheme Designator 0008,0102 SH From MWL

>> Coding Scheme Version 0008,0103 SH From MWL


>> Code Meaning 0008,0104 LO From MWL

Patient's Name 0010,0010 PN From MWL or user input

Patient ID 0010,0020 LO From MWL or user input

Patient's Birth Date 0010,0030 DA From MWL or user input

Patient's Sex 0010,0040 CS From MWL or user input

Referenced Patient Sequence 0008,1120 SQ Zero length

> Referenced SOP Class UID 0008,1150 UI Zero length> Referenced Instance UID

0008,1155

UI Zero length

Performed Procedure Step Information

Performed Procedure Step ID 0040,0253 SH

Generated by device

(Study Date + Study

Time)

Performed Station AE Title 0040,0241 AE From Modality Setup

Performed Station Name 0040,0242 SH Zero length

Performed Location 0040,0243 SH

Performed Procedure Step

Start Date0040,0244 DA

Zero length

Actual Start Date


Start Time0040,0245 TM Actual Start Time


Status0040,0252 CS "IN PROGRESS"

"DISCONTINUED" or

"COMPLETED"


Description0040,0254 LO

From MWL or user input

(Same as Study

Description)

From MWL or user input

(Same as Study

Description)

Performed Procedure Type

Description0040,0255 LO Zero length Zero length

Procedure Code Sequence 0008,1032 SQ From MWL From MWL

> Code Value 0008,0100 SH From MWL From MWL

> Coding Scheme Designator 0008,0102 SH From MWL From MWL

> Coding Scheme Version 0008,0103 SH From MWL From MWL

> Code Meaning 0008,0104 LO From MWL From MWL

Performed Procedure Step End

Date0040,0250 DA Zero length Actual End Date


Performed Procedure Step End

Time

0040,0251

TM

Zero length

Actual End Time

Image Acquisition Results

Modality 0008,0060 CS "US"

Study ID 0020,0010 SH

generated by device

(Study Date + Study

Time)

Performed Protocol Code

Sequence0040,0260 SQ Zero length

Performed Series Sequence 0040,0340 SQ Zero length One or more items

> Performed Physician's Name 0008,1050 PN From MWL

> Protocol Name 0018,1030 LO

"FreeForm" or staged

protocol name (In case

of Stress echo)

> Operator's Name 0008,1070 PN From user input

> Series Instance UID 0020,000E UI generated by device

> Series Description 0008,1 03E LO Zero length

> Retrieve AE Title 0008,0054 AE Zero length

> Referenced Image Sequence 0008,1140 SQ From Modality

>> Referenced SOP Class UID 0008,1150 UI From Modality


UID

0008,1155UI

From Modality

> Referenced Non-Image

Composite SOP Instance

Sequence

0040,0220 SQ From Modality

>> Referenced SOP Class UID 0008,1150 UI From Modality


UID0008,1155 UI From Modality


The Workflow Application Entity does not accept Associations.


4.2.3 Hardcopy Application Entity Specification

4.2.3.1 SOP Classes


Table 4.2-30

SOP CLASSES FOR AE HARDCOPY


Basic Grayscale Print Management Meta 1.2.840.10008.5.1.1.9 Yes No

Basic Color Print Management Meta 1.2.840.10008.5.1.1.18 Yes No

4.2.3.2 Association Policies

4.2.3.2.1 General

The DICOM standard application context name for DICOM 3.0 is always proposed:

Table 4.2-31

DICOM APPLICATION CONTEXT FOR AE HARDCOPY

Application Context Name 1.2.840.10008.3.1.1.1

4.2.3.2.2 Number of Association

SONOACE X8 can initiate one or more Associations at a time for each destination to which a transfer request is

being processed in the active job queue list.

Table 4.2-32

NUMBER OF ASSOCIATIONS INITIATED FOR AE HARDCOPY

Maximum number of simultaneous Associations Unlimited (number of configured

hardcopy devices)



Association)

Table 4.2-33

ASYNCHRONOUS NATURE AS A SCU FOR AE HARDCOPY





Table 4.2-34

DICOM IMPLEMENTATION CLASS AND VERSION FOR AE HARDCOPY




4.2.3.3.1 Activity – Film Images


A user composes images onto film sheets and requests them to be sent to a specific hardcopy device. The user

can select the desired film format and number of copies. Each print-job is forwarded to the job queue and

processed individually.

Hardcpoy AE Printer

1. Open Association

2. N-CREATE (Film Session)

3. N-CREATE (Film Box)

4. N-SET (Image Box)

5. N-ACTION (Film Box)

6. Print film sheets

7. N-DELETE (Film Session)


Figure 4.2-5


SEQUENCING OF ACTIVITY - FILM IMAGES

A typical sequence of DIMSE messages sent over an association between Hardcopy AE and a Printer is illustrated

in the Figure above:

Association Initiation Policies for “Batch”, “Send As You Go” and “Manual” Mode are equal to the Sending images’ of

the Storage Application Entity. (See 4.2.1.3.1 .1)

Status of the print-job is reported through the job control interface. One or more job can be active at a time for each

separate hardcopy device. If any response from the remote Application contains a status other than Success or

Warning, the Association is aborted and the related job is switched to a failed state. It can be restarted any time by

user interaction or, if configured, by automated retry.


SONOACE X8 is capable of proposing the Presentation Contexts shown in the Table below:

Table 4.2-35

PROPOSED PRESENTATION CONTEXTS FOR ACTIVITY FILM IMAGES




Role Ext.

Neg.

Basic Grayscale Print

Management Meta

1.2.840.10008.

5.1.1.9



1.2.840.10008.1.2

1.2.840.10008.1.2.1

SCU None

Basic Color Print

Management Meta

1.2.840.10008.

5.1.1.18



1.2.840.10008.1.2

1.2.840.10008.1.2.1

SCU None

4.2.3.3.1.3 Common SOP Specific Conformance for all Print SOP Classes

The general behavior of Hardcopy AE during communication failure is summarized in the table below. This behavior

is common for all SOP Classes supported by Hardcopy AE.

Table 4.2-36

HARDCOPY COMMUNICATION FAILURE BEHAVIOR


the print job is marked as failed.


Association aborted by the SCP or network layers The print job is marked as failed.

4.2.3.3.1.4 SOP Specific Conformance for the Film Session SOP Class

Hardcopy AE supports the following DIMSE operations for the Film Session SOP Class:

N-CREATE

N-DELETE

Details of the supported attributes and status handling behavior are described in the following subsections.

4.2.3.3.1.4.1 Film Session SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the Table below:

Table 4.2-37

FILM SESSION SOP CLASS N-CREATE REQUEST ATTRIBUTES

Attribute Name Tag VR Value Presence

of Value

Source

Number of Copies 2000,0010 IS 1..99 ALWAYS USER

Print Priority 2000,0020 CS HIGH, MED or LOW ALWAYS USER

Medium Type 2000,0030 CS

PAPER, CLEAR FILM, BLUE

FILM, MAMMO CLEAR FILM

or MAMMO BLUE FILM

ALWAYS USER

Film Destination 2000,0040 CS MAGAZINE or PROCESSOR ALWAYS USER

The Behavior of Hardcopy AE when encountering status codes in an N-CREATE response is summarized in the

table below:

Table 4.2-38

FILM SESSION SOP CLASS N-CREATE RESPONSE STATUS HANDLING BEHAVIOR

Service

Status

Further

Meaning

Error

Code

Behavior

Success Success 0000The SCP has Completed the operation successfully.

WarningAttribute

Value Out011 6H System continues operations.


of Range

Warning Attribute

List Error0107H Same as above

* * Any other

status

code.

The Association is aborted using A-Abort and the print-job

is marked as failed

4.2.3.3.1.4.2 Film Session SOP Class Operations (N-DELETE)

The behavior of Hardcopy AE when encountering status codes in an N-DELETE response is summarized in the

Table below:

Table 4.2-39

PRINTER SOP CLASS N-DELETE RESONSE STATUS HANDLING BEHAVIOR

Service

Status

Further

Meaning

Error

Code

Success Success 0000 The SCP has Completed the operation successfully.

* *

Any other

status

code.


is marked as failed

4.2.3.3.1.5 SOP Specific Conformance for the Film Box SOP Class

Hardcopy AE supports the following DIMSE operations for the Film Box SOP Class:

N-CREATE

N-ACTION


4.2.3.3.1.5.1 Film Box SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the table below:

Table 4.2-40


FILM BOX SOP CLASS N-CREATE REQUEST ATTRIBUTES


of Value

Source

Image Display

Format

2010,0010 ST

"STAN DARD\1, 1" ,

"STAN DARD\1, 2" ,

"STAN DARD\2, 2" ,

"STAN DARD\2, 3" ,

"STAN DARD\3, 3" ,

"STAN DARD\3, 4" ,

"STAN DARD\3, 5" ,

"STAN DARD\4, 4" ,

"STAN DARD\4, 5" or

"STAN DARD\4, 6"

ALWAYS USER

Referenced Film

S e s s i o n

Sequence

2010.0500 SQ ALWAYS AUTO

> Referenced

SOP Class UID0008,1150 UI 1.2.840.10008.5.1.1.1 ALWAYS AUTO

> Referenced

SOP Instance

UID

0008,1155 UIFrom created Film Session

SOP InstanceALWAYS AUTO

Film Orientation 2010,0040 CS PORTRAIT or LANDSCAPE ALWAYS USER

Film Size ID 2010,0050 CS

8INX10IN, 8_5INX11IN,

10INX12IN, 10INX14IN,



24CMX24CM, 24CMX30CM,

A4, A3

ALWAYS USER

Magnification

Type2010,0060 CS

REPLICATE, BILINEAR,

CUBIC, NONEALWAYS USER

Max Density 2010,0130 US 0 ~ ANAP USER

Configuration

Information2010,0150 ST

Values are defined in Print

Conformance StatementANAP USER

Smoothing Type 2010,0080 CSValues are defined in Print

Conformance StatementANAP USER


Border Density 2010,0100CS BLACK or WHITE ALWAYS USER

Empty Image

Density

2010,0110CS BLACK or WHITE ALWAYS USER

Min Density 2010,0120 US 0 ~ ANAP USER

The behavior of Hardcopy AE when encountering status codes in an N-CREATE responses is summarized in the

table below:

Table 4.2-41

FILM BOX SOP CLASS N-CREATE RESPONSE STATUS HANDLING BEHAVIOR

Service

Status


Code

Behavior

Success Success 0000The SCP has Completed the operation

successfully.

WarningAttribute Value Out of

Range01 16H System continues operations.

Warning Attribute List Error 0107H Same as above

Warning

Requested Min Density or

Max Density outside of

printer's operating range

B605H Same as above

* * Any

other

status

code.

The Association is aborted using A-Abort and

the print-job is marked as failed

4.2.3.3.1.5.2 Film Box SOP Class Operations (N-ACTION)

An N-ACTION Request is issued to instruct the Print SCP to print the contents of the Film Box.

The behavior of Hardcopy AE when encountering status codes in an N-ACTION responses is summarized in the

table below:

Table 4.2-42

FILM BOX CLASS N-ACTION RESPONSE STATUS HANDLING BEHAVIOR


Service

Status

Further

Meaning

Error

Code

Behavior


* *

Any other

status

code.


is marked as failed

4.2.3.3.1.6 SOP Specific Conformance for the Film Box SOP Class

Hardcopy AE supports the following DIMSE operations for the Image Box SOP Class:

- N-SET


4.2.3.3.1.6.1 Image Box SOP Class Operations (N-SET)

The attributes supplied in an N-SET Request are listed in the Table below:

Table 4.2-43

BASIC GRAYSCALE IMAGE BOX SOP CLASS N-SET REQUEST ATTRIBUTES


of Value

Source

Image Position 2020,0010 US1 .. N (N = Row * Column of

Film Box)ALWAYS AUTO

Basic Grayscale

Image Sequence2020,0110 SQ ALWAYS AUTO

> Samples Per Pixel 0028,0002 US 1 ALWAYS AUTO

> Photometric

Interpretation0028,0004 CS MONOCHROME2 ALWAYS AUTO

> Rows 0028,0010 US Number of Row Pixels of Image ALWAYS AUTO

> Columns0028,0011

USNumber of Column Pixels of

ImageALWAYS AUTO

> Bits Allocated 0028,0100 US 8 ALWAYS AUTO

> Bits Stored 0028,0101 US 8 ALWAYS AUTO


> High Bit 0028,0102 US 7 ALWAYS AUTO

> Pixel

Representation0028,0103 US 0 ALWAYS AUTO

> Pixel Data 7FE0,0010 OB Pixels of Image ALWAYS AUTO

Table 4.2-44

BASIC COLOR IMAGE BOX SOP CLASS N-SET REQUEST ATTRIBUTESAttribute Name Tag VR Value Presence

of Value

Source

Image Position 2020,0010 US1 .. N (N = Row * Column of

Film Box)ALWAYS AUTO

> Samples Per Pixel 0028,0002 US 3 ALWAYS AUTO

> Photometric

Interpretation0028,0004 CS RGB ALWAYS AUTO

> Planar

Configuration0028,0006 US 1 ALWAYS AUTO

> Rows 0028,0010 US Number of Row Pixels of Image ALWAYS AUTO

> Columns 0028,0011 USNumber of Column Pixels of

ImageALWAYS AUTO

> Bits Allocated 0028,0100 US 8 ALWAYS AUTO

> Bits Stored 0028,0101 US 8 ALWAYS AUTO

> High Bit 0028,01 02US 7 ALWAYS AUTO

> Pixel Representation 0028,01 03US 0 ALWAYS AUTO

> Pixel Data 7FE0,0010 OB Pixels of Image ALWAYS AUTO

The behavior of Hardcopy AE when encountering status codes in an N-SET response is summarized in the table

below:

Table 4.2-45

IMAGE BOX SOP CLASS N-SET RESPONSE STATUS HANDLING BEHAVIOR

Service

Status

Further

Meaning

Error

Code

Behavior



* *

Any other

status

code.


is marked as failed


The Hardcopy Application Entity does not accept Associations.


4.3 NETWORK INTERFACE

4.3.1 Physical Network Interface

SONOACE X8 supports a single network interface. One of the following physical network interfaces will be

available depending on hardware options installed:

Table 4.3-1

SUPPORTED PHYSICAL NETWORK INTERFACES

Ethernet 1 00baseT

Ethernet 1 0baseT

4.4 CONFIGURATION

4.4.1 AE Title/Presentation Address Mapping

4.4.1.1 Local AE Titles

All local applications use the AE Titles and TCP/IP Ports configured via the Setup/DICOM Menu. All local DICOM

services use the same AE Title. The system listens for Verification requests and Commitment reports on the

configured Port.

4.4.1.2 Remote AE Title/Presentation Address Mapping

The AE Title, host names and port numbers of remote applications are configured using the SONOACE X8

Setup/DICOM Menu.

4.4.1.2.1 Storage

The Add button on the SONOACE X8 Setup/DICOM Menu must be used to set the AE Titles, port-numbers, IP

addresses and capabilities for the remote Image Storage SCPs. Multiple remote Image Storage SCPs can be

defined.


addresses and capabilities for the remote Structured Report Storage SCP. Only a single remote Structured Report


Storage SCP can be defined.


addresses and capabilities for the remote Storage Commitment SCP. Only a single remote Storage Commitment

SCP can be defined and only one Image Storage SCP can be assigned for Storage Commitment.

4.4.1.2.2 Workflow


addresses and capabilities for the remote Modality Worklist SCP. Only a single remote Modality Worklist SCP can

be defined.


addresses and capabilities for the remote MPPS SCP. Only a single remote MPPS SCP can be defined.

4.4.1.2.3 Hardcopy


addresses and capabilities for the remote Print SCPs. Multiple remote Print SCPs can be defined.

4.4.2 Parameters

A number of parameters related to acquisition and general operation can be configured using the Setup/DICOM

Menu. The Table below only shows those configuration parameters relevant to DICOM communications. See the

SONOACE X8 Manual for details on general configuration capabilities.

Table 4.4-1

CONFIGURATION PARAMETERS TABLE

Parameter Configurable

(Yes/No)

Default Value

Local System Parameters

AE Title (Local System AE Title) Yes “Set AE Title”

Station Name Yes “Set Station Name”

Port No. (Local Port Number) Yes 104


Service Common Parameters

Retry Interval Yes 30 Sec.

Connect Timeout Yes 15 Sec.

Maximum Retires Yes 1

Storage Parameters

Transfer Mode Yes “Batch”

Include 3D Volume Yes Checked

Window Center (VOI LUT) Yes 128

Window Width (VOI LUT) Yes 256

Storage Commitment Parameters

Associated Storage Server Yes None

Worklist Modality Parameters

Delay between automatic Worklist Updates Yes 5 Min.

Query Worklist for specific Scheduled Station AE Title Yes Any

Query Worklist for specific Scheduled Modality Value No. “US” fixed

Query Worklist for Specific Start Date Yes Today

Print Parameters

Transfer Mode Yes “Batch”

Color Yes “Grayscale”

Medium Type Yes “PAPER”

Format Yes 1x1

Film Size Yes 8 IN X 10 IN

Orientation Yes “PORTRAIT”

Destination Yes “MAGAZINE”

Magnification Yes “REPLICATE”

Smoothing Type Yes Blank

Border Density Yes “BLACK”

Empty Density Yes “BLACK”

Priority Yes “HIGH”

Min Density Yes Blank

Max Density Yes Blank

Copies Yes 1

Configuration Info Yes Blank


5 MEDIA INTERCHANGE

5.1 IMPLEMENTATION MODEL

5.1.1 Application Data Flow

Figure 5.1-1

APPLICATION DATA FLOW DIAGRAM FOR MEDIA STORAGE

- The Offline-Media Application Entity exports images and Structured Report to a DVD Storage medium. It is

associated with the local real-world activity “Export to DVD RW”, “Export to DVD RW” is performed upon user

request for selected studies.

5.1.2 Functional Definition of AEs

5.1.2.1 Functional Definition of Offline-Media Application Entity

Activation of the “Export to DVD RW” menu entry will pass the currently selected studies to the Offline-Media

Application Entity. The SOP Instances associated with the selection will be collected into one or more export jobs.

The contents of each export job will be written to a single DVD media.

5.1.3 Sequencing of Real-World Activities

At least one study must exist and be selected before the Offline-Media Application Entity can be invoked. The

operator can insert a new DVD media at any time before or after invocation of the Offline-Media Application Entity. If

no DVD media is available the export job can be cancelled immediately.

5.1.4 File Meta Information Options

The implementation written to the File Meta Header in each file is:

Table 5.1-1

DICOM IMPLEMENTATION CLASS AND VERSION FOR MEDIA STORAGE

Offline-MediaApplication

EntityDVD Storage

Media

Export toDVD RW




5.2 AE SPECIFICATIONS

5.2.1 Offline-Media Application Entity Specification

The Offline-Media Application Entity provides standard conformance to the Media Storage Service Class. The

Application Profiles and roles are listed below:

Table 5.2-1

APPLICATION PROFILES, ACTIVITIES AND ROLES FOR OFFLINE-MEDIA

Application Profiles Supported Real World Activity RoleSTD-US-SC-MF-DVD Export To DVD FSC, FSU

5.2.1.1 File Meta Information for the Application Entity

The File-Set Identifier included in the File Meta Header is “MEDISON P6A”.

The Source Application Entity Title included in the File Meta Header is configurable using the Setup/DICOM Menu.

5.2.1.2 Real-World Activitiesdynamix0

5.2.1.2.1 Activity – Export to DVD

The Offline-Media Application Entity acts as an FSC and FSU when requested to export SOP Instances from the

local database to a DVD medium.

If the contents of the current selection do not fit on a single media, a separation into multiple export jobs which can

be adapted by the user will be suggested.

The user will be prompted to insert a DVD for each export job. The contents of the export job will be written

together with a corresponding DICOMDIR to a DVD. Writing in multi-session mode is supported.

5.2.1.2.1.1 Media Storage Application Profiles

The Offline-Media Application Entity supports the STD-US-SC-MF-DVD Application Profile.


5.2.1.2.1.1.1 Options

The Media Application Entity supports the SOP Classes and Transfer Syntaxes listed in the table below:

Table 5.2-2

IODS, SOP CLASSES AND TRANSFER SYNTAXES FOR OFFLINE MEDIA

Information Object

Definition

SOP Class UID Transfer Syntax Transfer Syntax UID

Media Storage Directory

Storage

1.2.840.10008.1.3.10 Explicit VR Little Endian 1.2.840.10008.1.2.1

US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Explicit VR Little Endian 1.2.840.10008.1.2.1

US Multiframe Image

Storage

1.2.840.10008.5.1.4.1.1.3.1 JPEG Baseline Lossy

Compression

1.2.840.10008.1.2.4.50

Comprehensive Structured

Report Storage

1.2.840.10008.5.1.4.1.1.88.3

3

Explicit VR Little Endian 1.2.840.10008.1.2.1


6 SUPPORT OF CHARACTER SETS

All SONOACE X8 DICOM applications support the

ISO_IR 100 (ISO 8859-1:1987 Latin Alphabet No. 1 supplementary set)


7 SECURITY

SONOACE X8 does not support any specific security measures.

It is assumed that SONOACE X8 is used within a secured environment. It is assumed that a secured environment

includes as minimum:

a. Firewall or router protections to ensure that only approved external hosts have network access to SON OACE X8.

b. Firewall or router protections to ensure that SONOACE X8 has only network access to approved external hosts

and services.

c. Any communication with external hosts and services outside the locally secured environment use appropriately

secure network channels (e.g. such as a Virtual Private Network (VPN).

Other