Sonoline G20..

Siemens Medical Solutions USA, Inc.
Ultrasound Division
SONOLINE G20 Product Platform DICOM Conformance

Statement
Revision Data
Revision Description Submit Date Effective Date
01 DICOM Conformance Statement for G20 1.0 19-Mar-2004

Release
02 Updated for 2.0 Release. 23-Nov-2004
03 Final Revision for 2.0 Release 17-Jan-2005
Page 1 of 58 REV 03
Siemens Medical Solutions USA, Inc. Ultrasound Division
Page 2 of 58 REV 03
2.0 Scope 5
3.0 Definitions 6
4.0 Implementation Model 8
4.1 Application Data Flow Diagram .................................................................. 8

4.1.1 Verification .................................................................................. 10
4.1.2 DICOM Store .............................................................................. 10
4.1.3 Storage Commitment .................................................................. 11
4.1.4 DICOM Print ............................................................................... 11
4.1.5 Patient Registration using Worklist ............................................. 12
4.1.6 Modality Performed Procedure Step ........................................... 15
4.1.7 Removable Media Storage ......................................................... 16
4.2 AE Functional Definition ............................................................................. 16

4.2.1 Verification Real-World Activities ................................................ 16
4.2.2 Store Real-World Activities ......................................................... 16
4.2.3 Storage Commitment Push Model Real-World Activities ............ 16
4.2.4 Print Real-World Activities .......................................................... 17
4.3 Modality Worklist Real-World Activities ...................................................... 17
4.4 Modality Performed Procedure Step Real-World Activities ........................ 17
4.5 Removable Media Storage Real-World Activities ...................................... 17
4.6 Sequencing of Real-World Activities .......................................................... 17
5.0 AE Specifications 19
5.1 SONOLINE G20 AE Specification .............................................................. 19

5.1.1 Association Establishment Policies ............................................ 19
5.1.2 Association Initiation by Real-World Activities ............................ 20
6.0 Removable Media Interchange Specifications 49
6.1 Supported Application Profiles ................................................................... 49
6.2 Supported SOP Classes ............................................................................ 49

6.2.1 Supported SOP Classes and Transfer Syntaxes ........................ 49
Page 3 of 58 REV 03
6.3 Information Object Definition and DICOMDIR Keys .................................. 49

6.3.1 DICOM File Meta Information ..................................................... 49
6.3.2 Basic Directory Information Object Definitions - File-set Identification
Module 51
6.3.3 Basic Directory Information Object Definitions - Directory Identification
Module 51
6.3.4 Physical Storage Media and Media Formats .............................. 51
7.0 Communication Profiles 52
7.1 TCP/IP Stack Supported ............................................................................ 52

7.1.1 Physical Media Supported .......................................................... 52
7.1.2 Chapter Extensions/Specializations/Privatizations ..................... 52
8.0 Configuration 53
8.1 General System Configuration ................................................................... 53

8.1.1 Hospital Name ............................................................................ 53
8.2 DICOM Network Configuration .................................................................. 53

8.2.1 Local ........................................................................................... 53
8.2.2 Remote ....................................................................................... 54
8.3 DICOM Store Configuration ....................................................................... 54
8.4 DICOM Storage Commitment Configuration .............................................. 54
8.5 DICOM Modality Worklist Configuration ..................................................... 54
8.6 DICOM Modality Performed Procedure Step Configuration ....................... 54

8.6.1 DICOM Print Configuration ......................................................... 56
8.7 External Equipment Configuration ............................................................. 57
8.8 Support of Extended Character Sets ......................................................... 57
9.0 Security 58
9.1 Security Profiles ......................................................................................... 58
9.2 Association Level Security ......................................................................... 58
9.3 Application Level Security .......................................................................... 58
9.4 Virus Protection .......................................................................................... 58
Page 4 of 58 REV 03
1.0 Purpose
This document describes the conformance to the ACR-NEMA DICOM 3.0
Standard by the SONOLINE G20 ultrasound system software version 2.0
from Siemens Medical Solutions USA, Inc. Ultrasound Division. It shall
establish the conformance specifications for this system only, and does not
apply to other products offered by Siemens Medical Solutions USA, Inc., or
its affiliates.
The SONOLINE G20 system is a device that generates ultrasound images
that can be sent using DICOM standard protocols and definitions to other
DICOM compliant devices that support SOP classes as defined in Table 2
on page 19 in this document.
2.0 Scope
The DICOM standard provides a well-defined set of structures and proto-
cols that allow inter-operability to a wide variety of medical imaging devices.
When configured with the DICOM option, the SONOLINE G20 system pro-
vides support for essential services related to ultrasound scanning and con-
nectivity to DICOM compliant devices. The SONOLINE G20 system prod-
ucts will not support all features supported by the DICOM standard. This
document clearly states the DICOM services and data classes that are sup-
ported by the applications included with the SONOLINE G20. The intent of
this document is to allow users and other vendors who also conform to the
DICOM standard to exchange information within the specific context of
those elements of the DICOM standard that the SONOLINE G20 system
supports.
This document is written with respect to the adopted portions of the DICOM
standard, Revision 3. The following sections of this document follow the
1
outline specified in the DICOM Standard NEMA publication PS3.2.
1 Second part of the DICOM standard: NEMA Standards Publication PS 3.2-2004,

Digital Imaging and Communications in Medicine (DICOM), Part 2: Conformance
Page 5 of 58 REV 03
3.0 Definitions
The following table provides a list of terms, their acronyms (if applicable),
and their descriptions.
Table 1 Terms, Acronyms, and Descriptions.
Term Acronym Description
American College of ACR- The American College of Radiology (ACR) and the
Radiology - National NEMA National Electrical Manufacturers Association
Electrical Manufacturer's (NEMA) formed a joint committee to develop a
Association standard for Digital Imaging and Communications
in Medicine (DICOM).
Application Entity AE An application that supports DICOM

communication with other DICOM applications.
DICOM Conformance DCS A formal statement associated with a specific

Statement implementation of the DICOM Standard. It
specifies the Service Classes, Information
Objects, Communications Protocols and Media
Storage Application Profiles supported by the
implementation.
DICOM Message Service DIMSE Defines an Application Service Element (both the
Element service and protocol) used by peer DICOM
Application Entities for the purpose of exchanging
medical images and related information.
Digital Imaging and DICOM A well-defined set of structures and protocols that
Communications in 3.0 allow inter-operability to a wide variety of medical
Medicine, Version 3.0 imaging devices.
Ethernet - Network methodology devised in 1976 by Digital

Equipment Corporation, Intel and Xerox which is
the most common in practice today. Ethernet is the
IEEE standard 802.3
Information Object IOD A data abstraction of a class of similar Real-World

Definition Objects which defines the nature and attributes
relevant to the class of Real-World objects
represented.
Integrating the Healthcare IHE An initiative sponsored by the Radiological Society

Enterprise of North America (RSNA) to document and
demonstrate standards-based methods of sharing
information in support of optimal patient care. For
additional information see www.rsna.org/ihe.
Picture Archiving and PACS A DICOM server that accepts medical images from
Communications Systems another DICOM system and stores the images for
later retrieval.
Protocol Data Unit PDU The PDUs are message formats exchanged
between peer entities within a layer. A PDU shall
consist of protocol control information and user
data.
Page 6 of 58 REV 03
Table 1 Terms, Acronyms, and Descriptions. (Continued)
Term Acronym Description
Real-World Activity RWA That which exists in the real world which pertains
to specific area of information processing within
the area of interest of the DICOM Standard. Such
a Real-World Activity may be represented by one
or more computer information metaphors called
SOP Classes.
Request RQ A request from one DICOM AE for service from

another DICOM AE
Response RSP A response from one DICOM AE to the request for

service from another DICOM AE
Service Class Provider SCP The role played by a DICOM Application Entity
(DIMSE-Service-User) which performs operations
and invokes notifications on a specific Association.
Service Class User SCU The role played by a DICOM Application Entity
(DIMSE-Service-User) which invokes notifications
and performs operations on a specific Association.
Service-Object Pairs SOP The union of a specific set of DIMSE Services and
one related Information Object Definition which
completely defines a precise context for
communication.
Structured Report SR Also called Procedure Report. A DICOM object

which contains measurement, calculations,
diagnoses, image references and other
information concerning a patient exam.
Unique identifier UID A series of digits and periods (.) used to uniquely
identify an object such as an Ultrasound image in
DICOM.
VA Hospital Information VISTA DICOM requirements document of the US

System Technology Department of Veteran’s Affairs (VA) Hospital
Architecture DICOM Information System Technology Architecture. For
Conformance additional information see www.va.gov/imaging.
Requirements
Page 7 of 58 REV 03
4.0 Implementation Model

SONOLINE G20 system users can store images and other data directly on
the SONOLINE G20 system hard disk. Images can be exported to a
DICOM archive server or workstation on a network. In the following sec-
tions, SONOLINE G20 system Real World Activities are indicated by “Real
World Activity” name while “G20 AE” indicates the invoked Application
Entity. Similarly, the activities associated with service providers are indi-
cated as “Real World Service Activity.”
4.1 Application Data Flow Diagram

Figure 1 illustrates the SONOLINE G20 system’s Application Entity (AE),
which is shown in the box. Relationships between user invoked activities (in
the circles at the left of the AE) and the associated real-world activities pro-
vided by DICOM service providers (in the circles on the right side of the dia-
gram) are shown.
Page 8 of 58 REV 03
Figure 1 Implementation Model
SONOLINE G20 Local Processes
Verify SCU Verify SCP
Verify SCP Verify SCU
Store SCU Store SCP
SONOLINE G20
B/W Print AE B/W Print
SCU SCP
Modality Worklist
Worklist SCU SCP
MPPS MPPS
SCU SCP
Storage Storage
Commit Commit
SCU SCP
DICOM Standard Interface
Page 9 of 58 REV 03
4.1.1 Verification
Verification is a part of the DICOM configuration located on the ‘DICOM’
page of the System Presets. Verification can be used to send a DICOM Ver-
ification request to a remote Application Entity (AE) and listen for a
response.
When used as a diagnostic tool, Verification returns the following messages
to the user:
If the verification succeeds: “DICOM - Successfully contacted
system”
If the verification fails: “DICOM - Unable to communicate with

system”
C-ECHO-RQ
G20 DICOM DICOM

Presets Verification SCU Verification SCP
Menu
C-ECHO-RSP
Figure 2 Verification Model.
4.1.2 DICOM Store

When requested the SONOLINE G20 sends images to the preconfigured
DICOM Storage server.
DICOM Store can be seen as two sub-operations:
queueing images for transfer
transferring images to the storage server.
Queueing images for transfer:
The SONOLINE G20 can be configured to automatically queue up images

for transfer as they are being created. “AutoStore to DICOM” option in
DICOM presets has to be set for this.
Alternatively, user can select exams manually queue them up from Review
mode. When an exam is selected for DICOM store all images will be
queued.
Transfer of images to the storage server:
Further, when “AutoStore to DICOM” option is selected once images are

queued they may be immediately transferred or delayed until the end of
study using the transfer storage configuration.
Page 10 of 58 REV 03
The SONOLINE G20 supports two storage configurations when “AutoStore

to DICOM” option is selected: “Store At End of Exam” and “Store During
Exam”.
If the storage configuration is set to “Store At End of Exam” transfer
attempts begin when the user selects “Close Study” or “New Patient”.
If the storage configuration is set to “Store During Exam”, transfer attempts
to destination devices begin immediately after they are queued.
For both “Store At End of Exam” and “Store During Exam” settings, image
transfer will be delayed if the SONOLINE G20 is busy performing another
DICOM Store operation.
C-STORE-RQ
G20 DICOM DICOM

STORE STORE SCU STORE SCP
C-STORE-RSP
Figure 3 Store Model.
4.1.3 Storage Commitment

The user can exercise the Storage Commitment option by configuring and
selecting a Storage Commitment server from the DICOM Presets menu.
The SONOLINE G20 system requests commitment of stored images and
upon successful acknowledgment from the Storage Commitment server
marks the study on the system hard drive as ‘Archived’.
Figure 4 Storage Commitment Model
N-ACTION-RQ
DICOM N-ACTION-RSP DICOM
G20 STORAGE STORAGE
STORE COMMITMENT N-EVENT-RQ COMMITMENT
SCU N-EVENT-RSP SCP
4.1.4 DICOM Print

The SONOLINE G20 system is capable of grayscale (B/W) printing.
When requested, single frame images will be printed to a pre-configured
DICOM network printer.
DICOM Print can be seen as two sub-operations:
preparing image pages for transfer
transferring pages to printer
Preparing image pages for transfer:
The SONOLINE G20 can be configured to automatically queue up images

to be printed on B/W Printer as they are being created. Alternatively, user
can select exams or individual images and manually queue them up from
Review mode for print.
Every image queued up is added into a page in the printer layout (DICOM
B/W Printer Layout). The SONOLINE G20 does not allow images from
more than one study to be printed on a single page.
Transfer of pages to the Printer:
Further, pages may be immediately transferred to the printer or delayed

until the end of study based on the transfer configuration.
The SONOLINE G20 supports two configurations: “Print At End of Exam”
and “Print When Page Full”.
If the configuration is set to “Print At End of Exam,” transfer attempts of all
pages to the destination DICOM printer begin as a batch when the user
ends the exam.
If the configuration is set to “Print When Page Full”, transfer attempt of a
page to the destination DICOM printer begins as soon as it becomes full.
For both “Print At End of Exam” and “Print when page full” settings, page
transfer will be delayed if the SONOLINE G20 is busy performing another
DICOM Print operation.
N-SET-RQ
N-ACTION-RQ
N-CREATE-RQ
N-DELETE-RQ
G20 DICOM DICOM
PRINT PRINT SCU PRINT SCP
N-SET-RSP
N-ACTION-RSP
N-CREATE-RSP
N-DELETE-RSP
Figure 5 Print Model.
4.1.5 Patient Registration using Worklist

Patient registration can be automated by using the 'Worklist' Real World
Activity. Pressing the 'New Patient' key on the keyboard initiates the patient
data registration process and closes the previous active study. Pressing the
'Worklist' button on the patient data display screen invokes the Worklist
query screen. The Worklist query screen can also can be initiated from the
Study screen.
Pressing the 'Search' button will attempt to find all matching patient data
using the information entered on the Worklist Query screen. Patient name
fields that are partially filled or empty will be treated as though an implicit
wildcard was appended at the end of each field. Patient ID, Requested Pro-
cedure ID and Accession number will be exact match only. If no matches
are found, a message will be presented to the operator indicating so. If
more that one matching patient is found, a pick list of patient procedures will
be presented to the user to select from. Each of the fields will be sortable in
ascending and descending order.
The pick list of patient procedures will be limited to a number of preset
entries. If more than this number of matching records are found in the query,
the search will terminate and the user will be notified. The search list criteria
will contain:
Patient name
Patient ID
Accession number
Exam start date/time range
Requested Procedure ID
US/All modalities
Scheduled station AE title
Scheduled Performing Physician’s Name
C-FIND-RQ
G20
New Patient
C-FIND-RSP
Figure 6 Modality Worklist Model
Once a Worklist query is initiated, a “Retrieving worklist, please wait ...” dia-
log will be presented to the user. The user will only have one option, “Can-
cel,” which will abort the query operation.
The following data fields in Modality Worklist Screen are initially populated
from the New Patient Screen, if filled in, and can be used for query:
Attribute Name Tag
Patient’s Full Name (0010,0010)

Patient ID (0010,0020)
Accession Number (0008,0050)
The following data fields will be populated on the worklist screen for each
return:
Attribute Name Tag
Patient’s Full Name (0010,0010)

Accession Number (0008,0050)
Exam Start Date/Time (0040,0002), (0040,0003)
Scheduled Procedure Step Sequence (0040,0100)*
>Scheduled Procedure Step Description (0040,0007)
>Scheduled Protocol Code Sequence (0040,0008)
>>Code Value (0008,0100)
Requested Procedure Description (0032,1060)
Exam Type (0008,1030)**
*<code1>, …,<codeN>: <sched1>,…,<schedn>

where:
code<i> = Sequence item code value(0008,0100)
for a given sequence or value multiplicity
sched<i> = Scheduled procedure step(0040,0007)
for a given sequence or value multiplicity
**if a value exists for (0008,1030). Otherwise, Exam
Type is set to value of Scheduled Procedure Step
(0040,0007). If (0040,0007) is also empty, Exam
Type is set to Requested Procedure Description
(0032,1060) if it exists.
The first procedure step is highlighted initially. The user can highlight a dif-
ferent procedure step, if desired, and select the highlighted patient proce-
dure step or cancel the operation. Selection of a procedure step from the list
will cause demographic information for the patient to be loaded in to the
patient data fields. Additional information from the procedure step will be
used to populate attributes in any images and MPPS messages generated
during the procedure step.
If the Worklist Server provides one or more of the attributes in the following
table with the procedure step, the data provided will be displayed to the
user.
Attribute Name Tag
Patient State (0038,0500)

Pregnancy Status (0010,21C0)
Attribute Name Tag
Medical Alerts (0010,2000)

Contrast Allergies (0010,2110)
Special Needs (0038,0050)
The following data fields will be populated on the patient data screen:
Attribute Name Tag
Patient Name (first,middle,last) (0010,0010)

Accession number (0008,0050)
Exam start date/time (0040,0002), (0040,0003)
DOB (0010,0030)
Sex (0010,0040)
Weight (0010,1030)
Height (0010,1020)
Physician (0008,0090)
Indication (0080,1080)
LMP (0010,21D0)
4.1.6 Modality Performed Procedure Step

The SONOLINE G20 System supports reporting of Modality Performed
Procedure Step (MPPS) orders when the patient registration process uti-
lizes the ‘Worklist’ Real World Activity. Procedure steps are presented to
the operator after successful query of a server that supports the MPPS
option. A detail window allows the operator access to individual scheduled
procedure steps. Pressing the ‘Procedures’ push button on the Review
Screen actualizes the detail window when multiple procedure steps are
listed for the patient.
N-CREATE-RQ
N-SET-RQ
G20 DICOM DICOM
New Modality Performed Modality Performed
Procedure Step Procedure Step
Patient SCU N-CREATE-RSP SCP
N-SET-RSP
Figure 7 MPPS Model
4.1.7 Removable Media Storage

The SONOLINE G20 can perform DICOM operations to its standard on-
board 120mm CD disk drive.
The SONOLINE G20 performs only the File Set Creator Role for CD disks.
A DICOM 3.0 conforming CD media is created when the user saves studies
in DICOM format to the CD. A DICOM 3.0 conforming DICOMDIR file is cre-
ated together with the directory structures and image files.
4.2 AE Functional Definition
4.2.1 Verification Real-World Activities

The SONOLINE G20 application entity performs Verification Service Class
as an SCU and SCP allowing the operator to verify the ability of an applica-
tion on a remote device to receive DICOM messages and allowing the oper-
ator of a remote DICOM device to verify the SONOLINE G20 system’s abil-
ity to receive DICOM messages. (C-ECHO DIMSE)
4.2.2 Store Real-World Activities

The SONOLINE G20 Application Entity (AE) performs all of the functions to
transmit ultrasound images and associated data to network servers or
workstations. The SONOLINE G20 AE supports the Ultrasound Image,
Ultrasound Multi-Frame Image, Ultrasound Image (Retired), Ultrasound
Multi-Frame (Retired) and Secondary Capture storage SOP classes as an
SCU.
The SONOLINE G20 AE initiates an association for C-STORE Requests to
store providers when the user invokes “DICOM Store”. The association may
be used to store multiple images and clips and is closed when no images or
clips are available to be stored to the remote device for five seconds.
4.2.3 Storage Commitment Push Model Real-World Activities

The SONOLINE G20 AE supports Storage Commitment Push Model SOP
class to inform servers when all the store operations for a study have been
completed. The Storage Commitment SCU uses the N-ACTION primitive to
request safekeeping of a set of SOP Instances. The Storage Commitment
SCU also processes the N-EVENT-REPORT primitives that are received
from the SCP indicating ‘successful’ or ‘non-successful’ commitment sta-
tus. The N-EVENT-REPORT information is used to mark a study as being
successfully archived to a DICOM Storage SCP.
4.2.4 Print Real-World Activities

The SONOLINE G20 AE provides all aspects of the Print Management
SCU. The SONOLINE G20 AE initiates an association to the printer when
the user invokes “DICOM Print”. The association may be used to print mul-
tiple pages and is closed when no pages are available to be printed to the
remote device for five seconds.
4.3 Modality Worklist Real-World Activities

The SONOLINE G20 AE supports the DICOM Basic Worklist Management
Service as an SCU. The AE initiates an association to the active Worklist
server when a Worklist query is selected. The association is closed upon
the completion of each query. A preset maximum number of matching
results is accepted, at which point the SONOLINE G20 AE issues a C-CAN-
CEL-RQ request.
4.4 Modality Performed Procedure Step Real-World

Activities
The SONOLINE G20 AE supports Modality Performed Procedure Step
(MPPS) in the role of SCU. The SONOLINE G20 is capable of displaying
scheduled procedure steps via the User Interface (UI) for Modality Per-
formed Procedure Step. The operator can select a single PPS. The opera-
tor can notify the MPPS server that a MPPS is ‘In Progress’, ‘Discontinued’
or ‘Completed’.
4.5 Removable Media Storage Real-World Activities

The SONOLINE G20 AE provides standard implementation of DICOM
Store to CD. The SONOLINE G20 AE selects one or more studies and
exports the same to CD. The SONOLINE G20 AE creates a DICOM File
Format Image File for every image and clip in each of the selected studies.
A DICOMDIR file is created along with the files.
4.6 Sequencing of Real-World Activities

Print, Store, Echo, Worklist, Storage Commit and MPPS commands can be
transmitted simultaneously within the limits described below.
Storage Commit
The Storage Commitment (if enabled) command is sent in the following sit-
uations:
a. On series close, when all images have previously stored successfully.
b. The series is closed before all images are stored successfully, all previ-
ous stores have succeeded and the last image stores successfully.
c. The series is closed before all images are stored successfully, at least
one store has succeeded, at least one store has failed and the last store
with non-zero retry count fails or succeeds.
d. A series has been partially committed as in c. Later, due to "Retry Job”
button press on the Store Status UI screen the store jobs are retried.
Another Storage Commit is sent when at least one store has succeeded
and the last store with non-zero retry count fails or succeeds.
MPPS
The MPPS (if enabled) command is sent in the following situations:
a. N-CREATE command is sent whenever a new procedure step is
selected. The state of the MPPS command is set to “In-Progress”.
b. N-SET command is sent when the Procedure Step is closed by the user
pressing either the Completed or Discontinued button on the Close Proce-
dure dialog. The state of the MPPS command is set, according to the state
(Completed or Discontinued) set by the user.
5.0 AE Specifications
The following specifications apply to the SONOLINE G20 AE as depicted in
Figure 1.
5.1 SONOLINE G20 AE Specification

The SONOLINE G20 AE provides conformance to the following DICOM
Service SOP Classes as an SCU.
Table 2 Supported SOP Classes.
Service SOP Class Name SOP Class UID
Verification 1.2.840.10008.1.1
Ultrasound Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.6
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1
Ultrasound Multi-Frame Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.3
Ultrasound Multi-Frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Storage Commitment - Push Model 1.2.840.10008.1.20.1
Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4
Printer SOP Class 1.2.840.10008.5.1.1.16
Modality Worklist Information Model C- FIND 1.2.840.10008.5.1.4.31
Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3
5.1.1 Association Establishment Policies
5.1.1.1 General
The SONOLINE G20 system utilizes TCP/IP. The Maximum Length PDU
negotiation is included in all association establishment requests. The max-
imum length PDU offered for an association initiated by the SONOLINE
G20 is:
Maximum PDU Offered: 28672
5.1.1.2 Association Establishment Order
The SONOLINE G20 initiates each C-Store Request one at a time, one for
each transfer request being processed.
Image format on the SONOLINE G20 can be set to one of “Automatic”, “Old
Ultrasound” or “Secondary Capture”.
For the “Automatic” setting, the SONOLINE G20 proposes Ultrasound,

Ultrasound retired and Secondary Capture sequentially for static images.
For clips the SONOLINE G20 proposes Ultrasound Multi-Frame and Ultra-
sound Multi-Frame retired sequentially.
For the “Old Ultrasound” setting, the SONOLINE G20 proposes Ultrasound
retired and Secondary Capture sequentially for static images. Only Ultra-
sound Multi-Frame retired is proposed for clips.
For the “Secondary Capture” setting, the SONOLINE G20 proposes only
Secondary Capture for static images. Clips are not supported with this set-
ting.
5.1.1.3 Asynchronous Nature
All associations use the default synchronous mode of operation. Asynchro-

nous Operations Window negotiations are not supported.
5.1.1.4 Implementation Identifying Information
Implementation Class UID: “1.3.12.2.1107.5.5.5” (See below).

Implementation Version Name: “MergeCOM3_330”
Siemens has provided registration for all Siemens Medical Solutions
Groups. This unique Class UID is defined as:
“1.3.12.2.1107.5.5.product”
Where the interpretation is:
1. = International Standards Organization (ISO)
3. = International branch of ISO
12.2.1107.5. = Assigned to Siemens-UB MED
5. = Ultrasound Modality (SMS-UG)
Product = 5 - DICOM implementation for SONOLINE G20, G50, G60 S and
Acuson CV70
5.1.2 Association Initiation by Real-World Activities
5.1.2.1 Real World Activity – Verification
The SONOLINE G20 is capable of supporting Verification service class as

SCU or SCP. Verification can be initiated as a singular event from the Sys-
tems Presets menu to any configured SCP that supports Verification.
Proposed Presentation Contexts – Verification

The SONOLINE G20 will propose Presentation contexts as shown in Table
3.
Table 3 Verification Presentation Context.
Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 Implicit VR Little 1.2.840.10008.1.2 SCU/ None

Endian SCP
Verification 1.2.840.10008.1.1 Explicit VR Little 1.2.840.10008.1.2.1 SCU/ None
Endian SCP
Verification 1.2.840.10008.1.1 Explicit VR Big 1.2.840.10008.1.2.2 SCU/ None
Endian SCP
5.1.2.2 Real World Activity – Store
The SONOLINE G20 facilitates users to store images as they are being cre-
ated or later in review mode.
Queueing images during acquisition:
“Autostore to DICOM” option in DICOM presets has to be set. One or more

of “Digital Store 1”, “Digital Store 2” and “Print/Store” keys on the control
panel can be configured for Store (Disk Store, D.Store, Clip capture). When
the user presses one of the configured keys, an image or clip is acquired,
stored on the hard disk and queued up to be transferred to the storage
server.
Queueing images in Review mode:
User can select one or more closed studies and queue them up for Storage.
The DICOM Store button is available in Review screen for this operation. All
images are stored.
Transfer of images to the storage server:
See Section "4.1.2 DICOM Store" (page 10).
Associated Real World Activities

When images are transferred from the hard disk to a DICOM Store SCP, the
system establishes an association between the SONOLINE G20 AE and
the configured DICOM device. The association may be used to store multi-
ple images and is closed when no images are available to be stored to the
remote device for five seconds.
Proposed Presentation Context

The following Presentation Contexts are presented to the SCP in an A-
ASSOCIATE-RQ for DIMSE C-STORE storage services. The storage ser-
vices utilize C-STORE services, as defined by the DICOM Standard. Table
4 represents all “Store” presentation contexts.
Table 4 Store Presentation Context.
Abstract Syntax Transfer Syntax

Extended
Role
Negotiation
Ultrasound Multi- 1.2.840.10008.5.1.4.1.1.3.1 Lossy JPEG 8 Bit 1.2.840.10008.1.2.4.50 SCU None

Frame Image Image
Storage Compression
Ultrasound Multi- 1.2.840.10008.5.1.4.1.1.3.1 DICOM Explicit 1.2.840.10008.1.2.1 SCU None
Frame Image VR Little Endian
Storage
Ultrasound Multi- 1.2.840.10008.5.1.4.1.1.3.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
Storage
Ultrasound Multi- 1.2.840.10008.5.1.4.1.1.3 DICOM Explicit 1.2.840.10008.1.2.1 SCU None
Storage (Retired)
Ultrasound Multi- 1.2.840.10008.5.1.4.1.1.3 DICOM Implicit 1.2.840.10008.1.2 SCU None
Storage (Retired)
Ultrasound Image 1.2.840.10008.5.1.4.1.1.6.1 DICOM Explicit 1.2.840.10008.1.2.1 SCU None
Storage VR Little Endian
Ultrasound Image 1.2.840.10008.5.1.4.1.1.6.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
Storage VR Little Endian
Ultrasound Image 1.2.840.10008.5.1.4.1.1.6 DICOM Explicit 1.2.840.10008.1.2.1 SCU None
Storage (Retired) VR Little Endian
Ultrasound Image 1.2.840.10008.5.1.4.1.1.6 DICOM Implicit 1.2.840.10008.1.2 SCU None
Storage (Retired) VR Little Endian
Secondary Capture 1.2.840.10008.5.1.4.1.1.7 DICOM Explicit 1.2.840.10008.1.2.1 SCU None
Image Storage VR Little Endian
Secondary Capture 1.2.840.10008.5.1.4.1.1.7 DICOM Implicit 1.2.840.10008.1.2 SCU None
Image Storage VR Little Endian
The SONOLINE G20 system always acts as an SCU for store and is the cli-
ent in a client-server model.
SOP Specific Conformance to Storage Service SOP Classes

The Store Real World Activity provides standard extended conformance as
an SCU for the following standard Storage Service Class SOP:
Table 5 Supported SOP Classes.
Service SOP Class Name SOP Class UID Conformance Level
Ultrasound Multi-Frame 1.2.840.10008.5.1.4.1.1.3.1 Standard Extended

Image Storage
Ultrasound Multi-Frame 1.2.840.10008.5.1.4.1.1.3 Standard Extended
Image Storage (Retired)
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Standard Extended
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6 Standard Extended
(Retired)
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7 Standard Extended
Storage
This is accomplished using the DIMSE C-STORE Service. The SCU issues
a service request with a SOP instance that meets the requirements of the
desired ultrasound or secondary capture IOD.
The following table denotes the attributes included in the Ultrasound Image
Object as implemented on the SONOLINE G20. Attributes not listed are not
used.
Table 6 Ultrasound Image and Ultrasound Retired Image IOD Attributes
Module Attribute Tag Notes
Specific Character (0008,0005) Always set to “ISO_IR 100”

Set
Patient Patient's Name (0010,0010) G20 Patient Data Screen – Last
Identification Name, First & Middle fields.
Populated from Modality Worklist if
used.
Patient ID (0010,0020) G20 Patient Data Screen –
ID field. Default is today’s date &
time (e.g., 03_04_2003_17_54_43
= Apr. 3, 2003 at 5:54:43 PM).
used.
Patient Patient's Birth Date (0010,0030) G20 Patient Data Screen –
Demographic DOB field. Default is a zero length
attribute. Populated from Modality
Worklist if used.
Patient's Sex (0010,0040) G20 Patient Data Screen –
Gender field. M = male
F = female. O = Other
Default is a zero length attribute.
used.
Patient’s Age (0010,1010) Calculated from Patient Data

Screen DOB field.
Patient’s Size (0010,1020) G20 Patient Data Screen –
Height field. Populated from
Modality Worklist if used.
Patient’s Weight (0010,1030) G20 Patient Data Screen –
Weight field. Populated from
Patient Study Admitting (0008,1080) G20 Patient Data Screen –
Diagnosis Indication field. Populated from
Description Modality Worklist if used.
General Study Study Instance UID (0020,000D) Populated from Modality Worklist if
used; generated by G20 otherwise
Study Date (0008,0020) Date the exam started.
Study Time (0008,0030) Time the exam started.
Referring (0008,0090) G20 Patient Data Screen –
Physician's Name Physician field. Populated from
Study ID (0020,0010) Populated with Requested
Procedure ID (0040,1001) from
Modality Worklist if available;
otherwise generated by G20
Accession Number (0008,0050) G20 Patient Data Screen –
Accession Number field. Populated
from Modality Worklist if used.
Study Description (0008,1030) Populated with the first attribute
from Modality Worklist in this list
that contains a valid value: Study
Description (0008,1030),
Scheduled Procedure Step
Description (0040,0007),
Requested Procedure Description
(0032,1060). If Modality Worklist
was not used or none of the
attributes contains a valid value
G20 Patient Data Screen –
Indication field is used.
General Series Modality (0008,0060) Always set to “US”
Series Instance (0020,000E) Generated by G20
UID
Series Number (0020,0011) Series Number in study (1-n).
Laterality (0020,0060) Always sent as 0 length attribute
(b)
Series Date (0008,0021) Date the series started.
(b)
Series Time (0008,0031) Time the series started.
(b)
Series (0008,103E) Populated with Scheduled
Description Procedure Step Description if a
value was provided by Modality
Worklist.
(b)
Protocol Name (0018,1030) The exam type of the most recent
image stored in a particular series.
If no images are stored for a series
then the value is set to
“Ultrasound”.
(b)
Request (0040,0275) Populated with Scheduled
Attributes Procedure Step Sequence
Sequence (0040,0100) if provided by Modality
Worklist.
>(b)Scheduled (0040,0007) Populated with Scheduled

Procedure Step Procedure Step Description
Description (0040,0007) from Scheduled
Procedure Step Sequence
(0040,0100) if provided by Modality
Worklist.
(b)
> Scheduled (0040,0008) Populated with Scheduled Protocol
Protocol Code Code Sequence (0040,0008) from
Sequence Scheduled Procedure Step
Sequence (0040,0100) if provided
by Modality Worklist.

Procedure Step ID Procedure Step ID (0040,0009)
from Scheduled Procedure Step
(b)
> Requested (0040,1001) Populated with Requested
Procedure ID Procedure ID (0040,1001) from
(b)
Performed (0040,0244) Date the Performed Procedure Step
Procedure Step was started.
Start Date
(b)
Performed (0040,0245) Time the Performed Procedure
Procedure Step Step was started.
Start Time
(b)
Performed (0040,0253) Populated with Scheduled
Procedure Step ID Procedure Step ID (0040,0009) if
provided by Modality Worklist.
(b)
Description (0040,0007) if provided by Modality
Worklist.
(b)
Performed (0040,0260) Populated with Scheduled Protocol
Procedure Protocol Code Sequence (0040,0008) if
Code Sequence provided by Modality Worklist.
(b)
Comments on (0040,0280) Populated with Comments on the
the Performed Scheduled Procedure Step
Procedure Step (0040,0400) if provided by Modality
Worklist.
General Manufacturer (0008,0070) Set to “Siemens Ultrasound”

Equipment
Institution Name (0008,0080) G20 System Presets –
Organization Name field.
Software Versions (0018,1020) Set to the DICOM Software Version
Manufacturer’s (0008,1090) Set to “G20”
Model Name
General Image Instance Number (0020,0013) Image number in study (1 – n)
Patient Orientation (0020,0020) Always sent as 0 length attribute
Image Pixel Samples per Pixel (0028,0002) Always set to 1
Photometric (0028,0004) Always set to “MONOCHROME2“
Interpretation
Rows (0028,0010) Always set to 480
Columns (0028,0011) Always set to 640
Bits Allocated (0028,0100) Set to 8.
Bits Stored (0028,0101) Set to 8.
High Bit (0028,0102) Set to 7.
Pixel (0028,0103) Set to 0
Representation
Pixel Data (7FE0, 0010)
US Image Image Type (0008,0008) Always sent as a 0 length attribute.
Lossy Image (0028,2110) “00”
Compression
SOP Common SOP Class UID (0008,0016) 1.2.840.10008.5.1.4.1.1.6.1 or
1.2.840.10008.5.1.4.1.1.6
SOP Instance UID (0008,0018) Generated by G20
Image Plane Pixel Spacing (0028,0030) Pixel Spacing information is only
provided for single, full screen, 2D
image types (2D image types are B-
mode).
Region (c)
Sequence of (0018,6011)
Calibration Ultrasound
Regions
(c)
> Region Spatial (0018,6012) B-Mode = 0001H
Format M-Mode = 0002H
(c)
> Region Data (0018,6014) B-Mode, M-Mode = 0001H (Tissue)
Type
(c)
> Region Flags (0018,6016) 1st Bit (LSB) = 1 (All images
acquired are transparent)
2nd Bit = 1 (All images acquired are
automatically scaled)
The value of the 3rd bit is undefined
4th Bit is Reserved and value is
always 0
(c)
> Region Location (0018,6018)
Min X0
>(c)Region Location (0018,601A)

Min Y0
>(c)Region Location (0018,601C)

Max X1
(c)
> Region Location (0018,601E)
Max Y1
(c)
> Physical Units X (0018,6024) B-Mode = 0003H (cm)
direction M-Mode = 0004H (seconds)
(c)
> Physical Units Y (0018,6026) B-Mode = 0003H (cm)
direction M-Mode = 0003H (cm)
(c)
> Physical Delta (0018,602C)
X
(c)
> Physical Delta (0018,602E)
Y
(b)
The Attribute is only provided if the procedure step is queried
from the MWL server.
(c)
Region Calibration is provided only for 2D (B-Mode) and M-
Mode Regions. Region Calibration is not supported on Ultra-
sound Retired, Secondary Capture images and Screen Cap-
tures.
Table 7 Ultrasound MultiFrame and Ultrasound MultiFrame Retired Image IOD Attributes

Set
used.
time (e.g., 03_04_2003_17_54_43
= Apr. 3, 2003 at 5:54:43 PM).
used.
Worklist if used.
F = female. O= Other
used.
Screen DOB field.
used; generated by G20 otherwise.

Description (0008,1030), Scheduled
Procedure Step Description
(0040,0007), Requested Procedure
Description (0032,1060). If Modality
Worklist was not used or none of
the attributes contains a valid value
UID
(b)
(b)
(b)
Worklist.
(b)
then the value is set to “Ultrasound”.
(b)
Worklist.
(b)
> Scheduled (0040,0007) Populated with Scheduled
Worklist.
(b)
> Scheduled (0040,0008) Populated with Scheduled Protocol

(b)
> Requested (0040,1001) Populated with Requested
(b)
Start Date
(b)
Performed (0040,0245) Time the Performed Procedure Step
Start Time
(b)
(b)
Worklist.
(b)
(b)
Worklist.

Equipment
Institution Name (0008,0080) G20 System Presets – Organization
Name field.
Manufacturer’s (0008,1090) Set to “G20”.
Model Name
General Image Instance Number (0020,0013) Image number in study (1 - n)
Patient Orientation (0020,0020) Always sent as 0 length attribute
Image Pixel Samples per Pixel (0028,0002) Set to 1 for MONOCHROME2
images, 3 for YBR_FULL_422 clips.
Photometric (0028,0004) “YBR_FULL_422” if sent
Interpretation compressed, “MONOCHROME2“
if sent uncompressed.
Planar (0028,0006) Color-by-pixel. Set to 0 for
Configuration YBR_FULL_422 clips, not provided
for MONOCHROME2 images.
Bits Allocated (0028,0100) Set to 8
Bits Stored (0028,0101) Set to 8

High Bit (0028,0102) Set to 7
Pixel (0028,0103) Set to 0
Representation
Pixel Data (7FE0, 0010)
US Image Image Type (0008,0008) Sent as a 0 length attribute.
Lossy Image (0028,2110) Always set to “01”
Compression
SOP Common SOP Class UID (0008,0016) 1.2.840.10008.5.1.4.1.1.3.1 or
1.2.840.10008.5.1.4.1.1.3
Image Plane Pixel Spacing (0028,0030) Pixel Spacing information is only
provided for single, full screen, 2D
image types (2D image types are B-
Mode).
Cine Frame Time (0018,1063)
Multi-Frame Number of Frames (0028,0008)
Frame Increment (0028,0009) 00181063H
Pointer
Region (c)
Sequence of (0018,6011)
Calibration Ultrasound
Regions
>(c)Region Spatial (0018,6012) B-Mode = 0001H

Format M-Mode = 0002H
>(c)Region Data (0018,6014) B-Mode, M-Mode = 0001H (Tissue)

Type
(c)
> Region Flags (0018,6016) 1st Bit (LSB) = 1 (All images
acquired are transparent)
2nd Bit = 1 (All images acquired are
automatically scaled)
The value of the 3rd bit is undefined
4th Bit is Reserved and value is
always 0
(c)
> Region Location (0018,6018)
Min X0
(c)
> Region Location (0018,601A)
Min Y0
(c)
> Region Location (0018,601C)
Max X1
(c)
> Region Location (0018,601E)
Max Y1
(c)
> Physical Units X (0018,6024) B-Mode = 0003H (cm)
direction M-Mode = 0004H (seconds)
(c)
> Physical Units Y (0018,6026) B-Mode = 0003H (cm)
direction M-Mode = 0003H (cm)
>(c)Physical Delta (0018,602C)

X
>(c)Physical Delta (0018,602E)

Y
(b)
(c)
Region Calibration is provided only for 2D (B-Mode) and M-
Mode Regions. Region Calibration is not supported on Ultra-
sound Retired images and Screen Captures.
Table 8 Secondary Capture Image IOD Attributes

Set
used.
time (e.g., 03_04_2003_17_54_43
= Apr. 3, 2003 at 5:54:43 PM).
used.
Worklist if used.
F = female. O= Other
used.
Screen DOB field.

used; generated by G20 otherwise.
Description (0008,1030), Scheduled
Procedure Step Description
(0040,0007), Requested Procedure
Description (0032,1060). If Modality
Worklist was not used or none of
the attributes contains a valid value
UID
(b)
(b)
(b)
Worklist.
(b)
then the value is set to “Ultrasound”.
(b)
Worklist.
(b)
Worklist.
>(b)Scheduled (0040,0008) Populated with Scheduled Protocol

(b)
>(b)Requested (0040,1001) Populated with Requested

(b)
Start Date
(b)
Performed (0040,0245) Time the Performed Procedure Step
Start Time
(b)
(b)
Worklist.
(b)
(b)
Worklist.
SC Equipment Conversion Type (0008,0064) Always set to “WSD”

Module

Equipment
Institution Name (0008,0080) G20 System Presets – Organization
Name field.
Manufacturer’s (0008,1090) Set to “G20”.
Model Name
General Image Instance Number (0020,0013) Image number in study (1 – n)
Patient Orientation (0020,0020) Always sent as 0 length attribute.
Image Pixel Samples per Pixel (0028,0002) Always set to 1
Photometric (0028,0004) “MONOCHROME2“
Interpretation
Bits Allocated (0028,0100) Set to 8.
Bits Stored (0028,0101) Set to 8.
High Bit (0028,0102) Set to 7.
Pixel (0028,0103) Set to 0.
Representation
Pixel Data (7FE0,0010)
SOP Common SOP Class UID (0008,0016) 1.2.840.10008.5.1.4.1.1.7
(b)
Error Handling
The following table indicates the response status codes that are handled by
the SONOLINE G20 AE, which an SCP may return following the SCU’s C-
STORE-RSP command.
A successful C-STORE operation will allow the SONOLINE G20 AE to con-

tinue to the next action desired by the user.
Table 9 C-STORE Status Responses.
Service Status Further Meaning Protocol Codes Related Fields
Refused Out of resources. A7xx None

Error Data set does not A9xx None
match SOP Class.
Cannot understand. Cxxx
Warning Coercion of data B000 None
Elements.
Data set does not B007
match SOP Class.
Elements discarded. B006
Success 0000 None
If the C-STORE operation is not successful, the image(s) are spooled on

the SONOLINE G20 hard drive. A user-configured number of additional
attempts are made to store the image(s). If these attempts fail, the user
must select the job and press “Retry Job” on the Store Status page to com-
plete the C-STORE operation.
All image storage on the SONOLINE G20 system hard drive is temporary in
nature. If an attempt is made to store images on a full SONOLINE G20 sys-
tem hard drive, the system will attempt to delete studies archived to CD or
DICOM. If no deleteable data exists, a “DISK FULL” message is displayed
on the SONOLINE G20 system display. The user must then delete studies
not archived in order to store additional images.
5.1.2.3 Real-World Activity Storage Commitment
This operation allows the AE to create an instance of the Storage Commit-

ment SOP Class and to provide information about a specific Real World
Activity that is under the control of the SCU. The AE invokes a request for
safekeeping of images by the N-ACTION REQUEST. Referenced in the N-
ACTION Request are the SOP class UID(s) and SOP instance UID(s) for all
STORE Class objects requesting commitment by the SCU.
Storage Commit
The Storage Commitment (if enabled) command is sent in the following sit-
uations:
a. On series close, when all images have previously stored successfully.
b. The series was previously closed, all previous stores have succeeded
and the last image stores successfully.
c. The series was previously closed, at least one store has succeeded, at
least one store has failed and the last store with non-zero retry count fails or
succeeds.
d. A series has been partially committed as in c. Later, due to "Retry Job”

button press on the Store Status UI screen the store jobs are retried.
Another Storage Commit is sent when at least one store has succeeded
and the last store with non-zero retry count fails or succeeds.
The SONOLINE G20 waits for the return of a successful N-ACTION
RESPONSE Status Code applicable for the associated request indicating
whether the commitment request was successful or a failure.
The SONOLINE G20 waits for the N-EVENT REPORT from the SCP for at
most 48 hours. The SONOLINE G20 is capable of accepting the N-EVENT
REPORT on the association initiated for the N-ACTION REQUEST or an
association initiated by the SCP. The N-EVENT REPORT notification con-
tains the status of the imbedded SOP instances referenced in the N-
ACTION REQUEST. Studies with all SOP instances marked as ‘successful’
will be eligible for deletion from the system hard drive.
The SONOLINE G20 allows the user to configure a Storage Commitment
Server which may be different from the Storage Server. Thus, the Storage
Commitment SCP must wait for an appropriate time for the stored images
to arrive from the Storage server.
Image-By-Image and Batch Storage Commitment are supported as speci-
fied in the US Department of Veteran’s Affairs “VISTA DICOM Conformance
Requirements for Image Modalities in radiology, Cardiology, Dental, Oph-
thalmology and other specialities” (Version 2.3).
Abstract Syntax Transfer Syntax Role Extended

Negotiation
Storage 1.2.840.10008. Implicit VR 1.2.840.10008. SCU None
Commitment Push 1.20.1 Little 1.2
Model Endian
Table 10 Storage Commitment Presentation Context Table
The SONOLINE G20 system will act as an SCU in the ‘Push Model” Stor-
age Commitment SOP Class.
SOP Specific Conformance to Storage Commitment SOP Class
The Storage Commitment AE provides conformance to the following
DICOM Service SOP Class as an SCU at a standard level of conformance.
Supported SOP Class SOP Class UID Conformance Level

Name
Storage Commitment Push 1.2.840.10008.1.20.1 Standard
Model
Storage Commitment to Storage Media (CD) is not supported.

Table 11 Supported SOP Class
The following table provides the list of attributes supported by the AE in the
implementation of Storage Commitment SOP Class:
Table 12 Storage Commitment Request Attributes in N-ACTION REQUEST
Attribute Tag Notes
Transaction UID (0008,1195) Generated by G20

Referenced SOP (0008,1199)
Sequence
>Referenced SOP (0008,1150) SOP Classes are listed in Table 5 on
Class UID page 23
>Referenced SOP (0008,1155) SOP Instance UIDs of the images the
Instance UID G20 is requesting commitment of.
5.1.2.4 Error Handling
If the storage commitment operation is not successful, a user-configured

number of additional attempts are made. If these attempts fail, the user
must select the job and press “Retry Job” on the DICOM Store Queue page
to complete the storage commitment operation.
5.1.2.5 Real World Activity - Print
The SONOLINE G20 facilitates printing of images as they are being created
or later in review mode.
Preparing image pages during acquisition
The “Print/Store 1” and “Print/Store 2” keys on the control panel can be con-
figured for Print (DICOM B/W Print). When the user presses the configured
key on the control panel, the image is acquired, stored on the hard disk and
placed in a page under the printer layout (DICOM B/W Printer Layout).
Preparing image pages in Review mode
The user can select either individual images from open or closed studies, or
one or more entire closed studies and queue them up for print. A DICOM B/
W Printer button is available in Review screen for this operation. When a
study is selected for print, all single-frame images belonging to the study
will be printed.
Transfer of pages to the Printer
Pages may be immediately transferred or delayed until the end of study
using the transfer configuration. The SONOLINE G20 supports two config-
urations: “Print At End of Exam” and “Print When Page Is Full”.
If the configuration is set to “Print At End of Exam”, all pages queued to des-
tination devices will be transferred as a batch when the user selects “Close
Study” or “New Patient”. If the configuration is set to “Print When Page Is
Full”, a page is transferred to destination devices immediately after it is full.
For both “Print At End of Exam”, and “Print When Page Is Full” settings,
image transfer will be delayed if the SONOLINE G20 is busy performing
another DICOM Print Command.
Associated Real World Activities
An association is established when the user initiates a “B/W Print” opera-
tion. Individual images or entire exams can be transferred to the selected
DICOM Print device. The association is closed when no pages are avail-
able to be printed for five seconds. An association may also be opened after
a network outage or when the system is powered-on if images are queued
to be printed.
Proposed Presentation Context to a Grayscale Print Server
Table 13 Grayscale Print Presentation Context.
Abstract Syntax Transfer Syntax

Extended
Role
Negotiation
Basic Grayscale 1.2.840.10008.5.1.1.9 DICOM Explicit 1.2.840.10008.1.2.1 SCU None

Print Management VR Little Endian
Meta SOP Class
Basic Grayscale 1.2.840.10008.5.1.1.9 DICOM Implicit 1.2.840.10008.1.2 SCU None
Print Management VR Little Endian
Meta SOP Class
SOP Specific Conformance to Basic Grayscale Print Management

Meta SOP Class
The SONOLINE G20 AE provides standard conformance of the Grayscale
Meta SOP classes as an SCU. Specifically, with respect to the Basic Gray-
scale Print Management Meta SOP Class this means conformance to the
underlying SOP classes:
Table 14 Conformance to Grayscale Print Meta SOP Class.
SOP Class Name SOP Class UID Conformance Level
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Standard

Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Standard
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Standard
Printer SOP Class 1.2.840.10008.5.1.1.16 Standard
All mandatory elements of these classes are supported.
Specific Conformance to Basic Film Session SOP Class

DICOM specified usage - M = Mandatory; U = User Option
Table 15 Supported DIMSE Services for Basic Film Session SOP Class.
Name Usage Description
N-Create M Creates the Film Session.

N-Set U Not used.
N-Delete U Deletes the Film Session.
N-Action U Not used.
SOP Specific Conformance to Basic Film Box SOP Class

Table 16 Supported DIMSE Services for Basic Film Box SOP Class.
N-Create M Creates the Film Box.

N-Set U Not used.
N-Delete U Deletes the Film Box. Issued after each film is printed.
N-Action M Sent after each Film Box is filled, and at the end of the
exam to force a print of partially filled Film Box.
Table 17 Attributes set for the Basic Film Box SOP Class.
Attribute Name Attribute Tag Usage Range Description
Image Display (2010,0010) M STANDARD\ X,Y Where X, Y can be

Format configured/ selected as
1*1, 1*2, 2*2, 2*3, 3*2,
3*3, 3*5, 4*5, 4*6, 5*6
Film Orientation (2010,0040) U PORTRAIT Range may be limited
LANDSCAPE by print server/printer.
Film Size ID (2010,0050) U 8INX10IN Range may be limited
8.5INX11IN by print server/printer.
10INX12IN
10INX14IN
11INX14IN
11INX17IN
14INX14IN
14INX17IN
24CMX24CM
24CMX30CM
A3
A4
Magnification (2010,0060) U REPLICATE
Type BILINEAR
CUBIC
NONE
Min. Density (2010,0120) U 0-99,999,999 Printer specific
Max Density (2010,0130) U 0-99,999,999 Printer specific
Configuration (2010,0150) U Printer specific
Information
Smoothing Type (2010,0080) U Printer specific
Border Density (2010,0100) U BLACK
WHITE
Empty Image (2010,0110) U BLACK
Density WHITE
Trim (2010,0140) U YES
NO
SOP Specific Conformance to Basic Grayscale Image Box SOP Class

Table 18 Supported DIMSE Services for the Basic Grayscale Image Box SOP.
N-Set M The SCP for each potential image of the film box creates an
image box instance. Only those instances, which actually
contain images, will be updated with the N-SET message.
Table 19 Attributes set for the Basic Grayscale Image Box SOP Class.
Name Attribute Range Description
Image (2020,0010) 1-30 Value according to Image Display

Position Format
Polarity (2020,0020) NORMAL, REVERSE Intensity mapping between
display and print
Table 20 Supported DIMSE Services for the Printer SOP.
N-Event-Report M Ignored and not handled.

N-Get U May be issued by this device at any time to get printer status.
Table 21 Supported Printer SOP Class Elements.
Name Usage Range Description
Printer Status U WARNING During a “Failure” the Print job will be

FAILURE displayed as “Failed”
Printer Status U Vendor specific Reported to user if printer status =
Information WARNING or FAILURE.
Error Handling
The SONOLINE G20 Print AE supports the following error codes and
reports failures to the user.
Table 22 Supported Error Codes for Printer Classes.
Service Status Further Meaning Protocol Codes
Success Film accepted for Printing 0000

Warning Film accepted for Printing, one or 107,116,B600,B605
more settings ignored.
Failure Printing not successful C602, C603, C613
If the print operation is not successful, the image(s) are spooled on the
SONOLINE G20 hard drive. A user-configured number of additional
attempts are made to print the image(s). If these attempts fail, the user must
select the job and press “Retry Job” on the Print Status page to complete
the print operation.
5.1.2.6 Real World Activity - Worklist
A separate association is established by the AE for each Worklist query

operation, with only one active query at a time. The association is closed at
completion of the query.
Table 23 Worklist Presentation Context Table

Negotiation
Modality Worklist 1.2.840.10008. Implicit VR 1.2.840.10008. SCU None
Information Model 5.1.4.31 Little 1.2
- FIND Endian
The SONOLINE G20 will always act as an SCU and as the client in a client-
server model.
SOP Specific Conformance to Modality Worklist Service SOP Classes
The Worklist AE provides conformance to the following DICOM Service
SOP Classes as an SCU all at a standard extended level of conformance:
Table 24 Supported SOP Classes

Name
Modality Worklist 1.2.840.10008.5.1.4.31 Standard Extended
Information Model - FIND
The following table provides the list of attributes requested in the Modality
Worklist Query.
Table 25 Modality Worklist Information Model Attributes
Attribute Name Tag
Specific Character Set (0008,0005)

Accession number (0008,0050)*
Referring Physician’s Name (0008,0090)
Study Description (0008,1030)
Admitting Diagnoses Description (0008,1030)
Referenced Study Sequence (0008,1110)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Patient’s Name (0010,0010)*
Patient ID (0010,0020)*
Patient’s Birth Date (0010,0030)
Patient’s Sex (0010,0040)
Patient’s Size (0010,1020)
Patient’s Weight (0010,1030)
Medical Alerts (0010,2000)
Attribute Name Tag
Contrast Allergies (0010,2110)

Pregnancy Status (0010,21C0)
Last Menstrual Date (0010,21D0)
Patient Comments (0010,4000)
Study Instance UID (0020,000D)
Requesting Physician (0032,1032)
Requested Procedure Description (0032,1060)
Requested Procedure Code Sequence (0040,0008)
>Code Value (0008,0100)
>Coding Scheme Designator (0008,0102)
>Coding Scheme Version (0008,0103)
>Code Meaning (0008,0104)
Special Needs (0038,0050)
Patient State (0038,0500)
Scheduled Procedure Step Sequence (0040,0100)
>Modality (0008,0060)
>Scheduled Station AE Title (0040,0001)*
>Scheduled Procedure Step Start Date (0040,0002)
>Scheduled Procedure Step Start Time (0040,0003)
>Scheduled Performing Physician’s Name (0040,0006)
>Scheduled Procedure Step Description (0040,0007)
>Scheduled Protocol Code Sequence (0040,0008)
>>Code Value (0008,0100)
>>Coding Scheme Designator (0008,0102)
>>Coding Scheme Version (0008,0103)
>>Code Meaning (0008,0104)
>Scheduled Procedure Step ID (0040,0009)
>Comments on the Scheduled Procedure Step (0040,0400)
Requested Procedure ID (0040,1001)*
Reason for the Requested Procedure (0040,1002)
*Indicates parameter may be populated for
query.
5.1.2.7 Real World Activity - Modality Performed Procedure Step
This operation allows the AE to create an instance of the Modality Per-

formed Procedure Step SOP Class (MPPS) and provide information about
a specific real world Performed Procedure Step that is under control of the
SCU. This operation is invoked through the DIMSE N-CREATE and N-SET
services.
Only the IHE (refer to IHE Rev 5.5) Simple and Abandoned Cases for the
relationship between Scheduled Procedure Steps and Performed Proce-
dure Steps are supported. Both cases specify that a 1-to-1 relationship
must exist between Scheduled Procedure Step and Performed Procedure
Step. In the Simple Case the Performed Procedure Step is completed suc-
cessfully. In the Abandoned Case the Performed Procedure Step is aban-
doned before being completed.
A list of scheduled procedures and procedure steps will be accessible from
the Worklist and Procedure screens. The Performed Procedure Step User
Interface allows the operator to set the status of the performed procedure
step. The system shall establish an association for N-CREATE and N-SET,
if another N-CREATE or N-SET is available within 5 seconds, it will be sent
using the same association.
Starting a Performed Procedure Step
When the user depresses the ‘OK’ button on the New Patient Screen a per-
formed procedure SOP Class instance will be created using the N-CREATE
DIMSE service for the selected scheduled procedure.
Ending a Performed Procedure Step
When the user selects ‘Completed’ or ‘Discontinued’ from the MPPS User
Interface, the performed procedure step will be closed using the N-SET
DIMSE service.
New Patient Request
If the ‘New Patient’ button is selected and there are opened performed pro-
cedure steps, the user shall be prompted for a closure status for the opened
procedure step by the MPPS User Interface. Any opened procedure steps
must be closed before any ‘new patient’ data can be entered.
System Shutdown
If the user requests ‘System Shutdown’ and there is an open performed pro-
cedure step, the user will be prompted for a closure status for the open pro-
cedure step. All procedure steps should be closed before the system can
be shutdown. Failure to close a procedure step will result in the procedure
step being marked as Discontinued.
Error Handling
If the MPPS operation is not successful, the MPPS command is spooled on
the SONOLINE G20 hard drive. A user-configured number of additional
attempts are made to complete the MPPS Commands. If these attempts
fail, the user must select this job and press “Retry Job” on the Store Status
page to complete the MPPS operation.

Negotiation
Modality 1.2.840.10008. Implicit VR 1.2.840.10008. SCU None
Performed 3.1.2.3.3 Little 1.2
Procedure Step Endian
Table 26 MPPS Presentation Context Table
The SONOLINE G20 system will always act as an SCU and be the client in
a client – server model.
SOP Specific Conformance to Modality Performed Procedure Step
SOP Classes
The Modality Performed Procedure Step AE provides a conforming imple-
mentation of the following DICOM Service SOP Class as an SCU at a stan-
dard extended level of conformance.
Table 27 Supported SOP Class

Name
Modality Performed 1.2.840.10008.3.1.2.3.3 Standard Extended
Procedure Step
The following tables provide the list of attributes supported by the AE in the
implementation of MPPS SOP Class including N-CREATE, N-SET and
Final State attributes. The SONOLINE G20 sends N-SET only at final state.
Table 28 Modality Performed Procedure Step Attributes in N-CREATE
Attribute Tag Notes
Specific Character Set (0008,0005) Always set to “ISO_IR 100”

Scheduled Step Attribute (0040,0270)
Sequence
>Study Instance UID (0020,000D) Value obtained from Modality WorkList;
generated by G20 in some cases
>Referenced Study Sequence (0008,1110) Always empty
>Referenced Patient Sequence (0008,1120) Always empty
>Accession Number (0008,0050) Value obtained from Modality WorkList
>Requested Procedure ID (0040,1001) Value obtained from Modality WorkList
>Requested Procedure (0032,1060) Value obtained from Modality WorkList

Description
>Scheduled Procedure Step ID (0040,0009) Value obtained from Modality WorkList
>Scheduled Procedure Step (0040,0007) Value obtained from Modality WorkList
Description
>Scheduled Protocol Code (0040,0008)
Sequence
Attribute Tag Notes
>>Code Value (0008,0100) Value obtained from Modality WorkList

>>Coding Scheme Designator (0008,0102) Value obtained from Modality WorkList
>>Coding Scheme Version (0008,0103) Value obtained from Modality WorkList
>>Code Meaning (0008,0104) Value obtained from Modality WorkList
Patient’s Name (0010,0010) Value obtained from Modality WorkList
Patient ID (0010,0020) Value obtained from Modality WorkList.
Patient’s Birth Date (0010,0030) Value obtained from Modality WorkList
Patient’s Sex (0010,0040) Value obtained from Modality WorkList
Performed Procedure Step ID (0040,0253) Value obtained from Modality WorkList
Performed Station AE Title (0040,0241) The AE title of the G20 on which the
procedure was performed.
Performed Station Name (0040,0242)
Performed Location (0040,0243)
Performed Procedure Step Start (0040,0244) The start date of the performed
Date procedure step.
Performed Procedure Step Start (0040,0245) The start time of the performed
Time procedure step.
Performed Procedure Step (0040,0252) Always set to “In-Progress”.
Status
Performed Procedure Step (0040,0254) Value obtained from Modality WorkList
Description
Performed Procedure Type (0040,0255) Always sent as 0 length attribute
Description
Procedure Code Sequence (0008,1032) Always empty
Performed Procedure Step End (0040,0250) Always sent as 0 length attribute
Date
Performed Procedure Step End (0040,0251) Always sent as 0 length attribute
Time
Modality (0008,0060) Always set to US
Study ID (0020,0010) Populated from Requested Procedure ID
(0040,1001) if Modality Worklist is used;
created by G20 otherwise
Performed Protocol Code (0040,0260) Always empty
Sequence
Performed Series Sequence (0040,0340) Always empty
Table 29 Modality Performed Procedure Step Attributes in N-SET
Attribute Tag Notes
Performed Procedure (0040,0252) Set to “Discontinued” or “Completed” based

Step Status on user selection.
Performed Procedure (0040,0250) Date the procedure step was completed
Step End Date
Performed Procedure (0040,0251) Time the procedure step was completed
Step End Time
Performed Series (0040,0340) Shall contain only one series
Sequence
>Performing (0008,1050)
Physician’s Name
>Protocol Name (0008,1030) Exam type specified by the operator.
>Operator’s Name (0008,1070)
>Series Instance UID (0020,000E) The Instance UID of the series to which the
procedure belongs.
>Series Description (0008,103E) Always sent as 0 length attribute
>Retrieve AE Title (0008,0054) Always sent as 0 length attribute
>Referenced Image (0008,1140) List of all the images in the series.
Sequence
>>Referenced SOP (0008,1150) The SOP class UID can be one of:
Class UID Ultrasound Multi-Frame Image Storage
1.2.840.10008.5.1.4.1.1.3.1
Ultrasound Multi-Frame Image Storage
(Retired) 1.2.840.10008.5.1.4.1.1.3
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
>>Referenced SOP (0008,1155) The SOP instance UID of the image.
Instance UID
>Referenced Non- (0040,0220) Always empty
Image Composite SOP
Instance Sequence
6.0 Removable Media Interchange Specifications

This implementation supports120mm CD-R medium.
6.1 Supported Application Profiles

The SONOLINE G20 provides standard conformance to the following Ultra-
sound Application Profiles. A DICOM 3.0 conformant DICOMDIR file is cre-
ated together with the directory structures and image files.
Table 30 Application Profiles, Real-World Activities, and Roles
Supported AP Real-World Activity Roles SC Option

STD-US-ID-SF-CDR Create CD-R FSC Interchange
STD-US-ID-MF-CDR Create CD-R FSC Interchange
STD-US-SC-SF-CDR Create CD-R FSC Interchange
STS-US-SC-MF-CDR Create CD-R FSC Interchange
6.2 Supported SOP Classes
6.2.1 Supported SOP Classes and Transfer Syntaxes

This implementation provides standard conformance to the following
DICOM 3.0 SOP Classes.
Table 31 SOP Classes and Transfer Syntaxes for Media Interchange
Service SOP Class Name SOP Class UID Transfer Syntax Name Transfer Syntax UID List
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 DICOM Explicit VR 1.2.840.10008.1.2.1

Little Endian
Ultrasound Multi-Frame Image 1.2.840.10008.5.1.4.1.1.3.1 Lossy JPEG 8 Bit 1.2.840.10008.1.2.4.50
Storage Image Compression
6.3 Information Object Definition and DICOMDIR Keys
6.3.1 DICOM File Meta Information

The following table denotes the attributes included in the Ultrasound Image
Object as implemented on the SONOLINE G20 in addition to the attributes
listed in Table 6 on page 23.
Table 32 US Image Attributes Used (Refer to Table 6 on page 23 for additional attributes used)
Attribute Name Tag Notes
File Preamble No Tag or Length fields All bytes are set to 00H
DICOM Prefix No Tag or Length fields Set to DICOM Prefix “DICM”
Group length (0002,0000)
File Meta Information Version (0002,0001) Always set to 0001H
Media Storage SOP Class UID (0002,0002) Always Ultrasound Image
1.2.840.10008.5.1.4.1.1.6.1
Media Storage SOP Instance UID (0002,0003)
Transfer Syntax UID (0002,0010) Always Explicit VR Little Endian
1.2.840.10008.1.2.1
Implementation Class UID (0002,0012) Always set to 1.3.12.2.1107.5.5.5
Implementation Version Name (0002,0013) Always set to MergeCOM3_330
The following table denotes the attributes included in the Ultrasound Multi-
Frame Image Object as implemented on the SONOLINE G20 in addition to
the attributes listed in Table 7 on page 28.
Table 33 USMF Image Attributes Used (Refer to Table 7 on page 28 for additional attributes used)
Attribute Tag Notes
File Preamble No Tag or Length fields All bytes are set to 0

DICOM Prefix No Tag or Length fields Set to “DICM”
Group length (0002,0000)
File Meta Information Version (0002,0001) Always set to 0001H
Media Storage SOP Class UID (0002,0002) Always Ultrasound Multi-Frame Image
1.2.840.10008.5.1.4.1.1.3.1
Media Storage SOP Instance UID (0002,0003)
Transfer Syntax UID (0002,0010) Always Lossy JPEG 8 Bit Compression
1.2.840.10008.1.2.4.50
Implementation Class UID (0002,0012) Always set to 1.3.12.2.1107.5.5.5
Implementation Version Name (0002,0013) Always set to MergeCOM3_330
6.3.2 Basic Directory Information Object Definitions - File-set

Identification Module
Attribute Tag Notes
File-Set ID (0004,1130) Always Set
6.3.3 Basic Directory Information Object Definitions - Directory

Identification Module
Attribute Tag Notes
Offset of the First Directory Record (0004,1200)

of the Root Directory Entry
Offset of the Last Directory Record (0004,1202)
of the Root Directory Entry
File-set Consistency Flag (0004,1212)
Directory Record Sequence (0004,1220)
>Offset of the Next Directory (0004,1400)
Record
>Record In-use Flag (0004,1410)
>Offset of Referenced Lower-Level (0004,1420)
Directory Entity
>Directory Record Type (0004,1430)
>Referenced File ID (0004,1500)
>Referenced SOP Class UID in (0004,1510)
File
>Referenced SOP Instance UID in (0004,1511)
File
6.3.4 Physical Storage Media and Media Formats

The physical storage media supported is 120mm CD-R Medium.
7.0 Communication Profiles

All SONOLINE G20 system application entities utilize the DICOM 3.0 TCP/
IP communication support as defined in PS3.8 (Part 8) of the DICOM 3.0
Standard.
7.1 TCP/IP Stack Supported

Each process inherits its TCP/IP stack from the SONOLINE G20’s operat-
ing systems TCP/IP stack. The local AE Port number is always set to 104.
7.1.1 Physical Media Supported

Standard representations of IEEE 802.3 10BaseT/100BaseT (“twisted
pair”) are supported
7.1.2 Chapter Extensions/Specializations/Privatizations

Pixel Spacing information is only provided for single, full screen, and 2D
image types (B-mode).
No private attributes are used by the SONOLINE G20 AE.
8.0 Configuration
The SONOLINE G20 Networking and DICOM parameters can be config-
ured through the SONOLINE G20 System Presets Menu screens. The fol-
lowing configuration is supported:
General system
Network (local and remote)
DICOM Store
DICOM Print
DICOM Modality Worklist
DICOM Storage Commitment
DICOM Modality Performed Procedure Step
8.1 General System Configuration

The following system parameter can be configured via the SONOLINE G20
System Presets Basic Menu screens. This parameter is mapped to a
DICOM image attribute:
Hospital Name
8.1.1 Hospital Name

The user can enter the organization (i.e. hospital, clinic, etc.) as a text string
in the Hospital Name field of the System Presets - General menu. The
Organization Name field is transferred to DICOM devices as Institution
Name - DICOM data element (0008, 0080).
8.2 DICOM Network Configuration

DICOM and networking parameters can be configured for both the local
SONOLINE G20 device and remote DICOM service class providers
through the System Presets DICOM Menu.
8.2.1 Local
The SONOLINE G20 local network parameters are configurable. The fol-
lowing network parameters can be configured for a SONOLINE G20
device:
Host Name
IP address
Subnet IP mask
Default Gateway
DICOM Application Entity Title
8.2.2 Remote
Multiple DICOM service class providers can be configured through the sys-
tem presets. The following network parameters can be configured for each
remote device:
DICOM Device Application Entity Title
IP address
Port Number
8.3 DICOM Store Configuration

Several configuration settings are provided in addition to those described in
8.2.2 Remote.
The Image Format setting provides control over the Presentation Contexts
proposed during Association negotiation. This is documented in Section
"5.1.2.2 Real World Activity – Store" (page 21).
8.4 DICOM Storage Commitment Configuration

Configuration of DICOM Storage Commitment remote devices must be per-
formed separately from DICOM Store Configuration. The SONOLINE G20
supports Storage Commitment to the same remote device as Store or to a
different device.
8.5 DICOM Modality Worklist Configuration

The only setting specific to Modality Worklist servers is for the maximum
number of worklist items. This allows the user to set a maximum number of
Scheduled Procedure Steps that are accepted by the SONOLINE G20. If
the maximum is exceeded the additional Scheduled Procedure Steps are
discarded and a cancel is sent.
8.6 DICOM Modality Performed Procedure Step

Configuration
Configuration of DICOM Modality Performed Procedure Step remote
devices must be performed separately from DICOM Modality Worklist Con-
figuration. The SONOLINE G20 supports MPPS to the same remote device
as Modality Worklist or to a different device.
The “Store Image Format” setting controls the Referenced SOP Class UID
(0008,1150) in the Referenced Image Sequence (0008,1140) of the MPPS N-SET

sent by the SONOLINE G20. Due to the SONOLINE G20’s ability to select from
multiple Presentation Contexts during Association Negotiation, it is necessary to
use this setting.
In the majority of installations the “Store Image Format” should be left at the
default setting of “New Ultrasound”. There are two cases when the “Store
Image Format” must be set to “Old Ultrasound” or “Secondary Capture”:
1. When the active Storage Server “Image Format” is set to “Old Ultra-
sound” or “Secondary Capture”.
2. When the active Storage Server “Image Format” is set to “Auto-
matic”, but the Storage Server does not support US Image and US
Multi-frame Image.
In both cases the correct setting can be determined by reviewing the
DICOM Conformance Statement of the Storage Server and following the
instructions below. DICOM Conformance Statements are usually available
on the manufacturer’s Web site.
If at least one of US Image and US Multi-frame Image are listed in the
DICOM Conformance Statement and the active Storage Server “Image For-
mat” is set to “Automatic” then “New Ultrasound” is the correct setting for
“Store Image Format”.
If the above is not true and at least one of US Image (Retired) and US Multi-
frame Image (Retired) are listed in the DICOM Conformance Statement
then “Old Ultrasound” is the correct setting for “Store Image Format”.
If neither of the above are true then “Secondary Capture” is the correct set-
ting for “Store Image Format”.
8.6.1 DICOM Print Configuration

For each DICOM Print server, the following data is configurable by the user
using the System Presets DICOM Print User Interface. The effect of chang-
ing parameters of the DICOM Print server will be seen at the next created
film sheet. The current film sheet is not affected by changing these param-
eters.
Table 34 User-configurable printer parameters.
Parameter Description
Printer Type: Black and White

Film Size Select the size of the film - 8x10 inches, 8.5x11 inches,
10x12 inches, 10x14 inches, 11x14 inches, 11x17 inches,
14x14 inches, 14x17 inches, 24x24 centimeters, 24x30
centimeters, A3, or A4.
Film Orientation Select from Portrait:
or Landscape:
Display Format You must supply the number of rows and columns of
images on the printed sheet.
For example, a 6 on 1 print with Landscape mode should
have 3 columns and 2 rows:
A 6 on 1 with Portrait mode would have 2 columns and 3

rows:
Table 34 User-configurable printer parameters. (Continued)
Parameter Description
Print Priority HIGH, MEDIUM or LOW

Medium Type PAPER, CLEAR FILM, BLUE FILM, TRANSPARENCY or
CURRENT (to use the currently loaded media)
Film Destination MAGAZINE, PROCESSOR or CURRENT
Max. Density Used to define the Black value - printer specific
Min. Density Used to define the White value - printer specific
Smoothing Type Printer specific value
Border Density BLACK or WHITE
Empty Image Density BLACK or WHITE
Trim YES/NO to having a border around each image
Polarity Normal/reverse. Normal means black is printed as black.
Reverse means the grayscale is inverted so that black
comes out as white and white as black.
Configuration Information: Printer Specific values
8.7 External Equipment Configuration

The SONOLINE G20 user can configure “Hard Key” to “Output Device”
mapping through the System Presets - Customize Keys. Print images are
acquired and sent to the assigned device when the user presses the asso-
ciated key. The following key assignments are supported:
Print/Store – This key can be assigned to the configured DICOM
Printer, DICOM Store or OEM printer device.
Digital Store 1 – This key can be assigned to Multi-frame Store
Capture, DICOM Printer, DICOM Store or OEM printer device.
Digital Store 2 – This key can be assigned to Multi-frame Store
Capture, DICOM Printer, DICOM Store or OEM printer device.
8.8 Support of Extended Character Sets

The “ISO-IR 100” Latin Alphabet 1 Extended character set is supported by
the SONOLINE G20 system.
9.0 Security
9.1 Security Profiles

None supported.
9.2 Association Level Security

None supported.
9.3 Application Level Security

None supported.
9.4 Virus Protection

The SONOLINE G20 computer system's networking has been configured to sig-
nificantly reduce the possibility of virus and hacking vulnerabilities. On the G20
computer system, all ingress TCP and UDP ports are closed and/or absent of any
type of server. The only exception to this is due to the necessity of a DICOM
server available at ingress TCP port 104. Additionally, all non-essential computer
services and components are disabled to minimize G20 egress network footprint.
Outside of some minimal network exchanges required by the G20's commercial

computer operating system, the only network connections initiated by the G20 are
for DICOM connectivity and network-share export function.

Sonoline G20..

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Sonoline G20..

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sonoline G20..

Uploaded by

Copyright:

Available Formats

Siemens Medical Solutions USA, Inc.

SONOLINE G20 Product Platform DICOM Conformance

Revision Description Submit Date Effective Date

01 DICOM Conformance Statement for G20 1.0 19-Mar-2004

02 Updated for 2.0 Release. 23-Nov-2004

03 Final Revision for 2.0 Release 17-Jan-2005

4.0 Implementation Model 8

4.1 Application Data Flow Diagram .................................................................. 8

4.2 AE Functional Definition ............................................................................. 16

4.3 Modality Worklist Real-World Activities ...................................................... 17

4.4 Modality Performed Procedure Step Real-World Activities ........................ 17

4.5 Removable Media Storage Real-World Activities ...................................... 17

4.6 Sequencing of Real-World Activities .......................................................... 17

5.1 SONOLINE G20 AE Specification .............................................................. 19

6.0 Removable Media Interchange Specifications 49

6.1 Supported Application Profiles ................................................................... 49

6.2 Supported SOP Classes ............................................................................ 49

6.3 Information Object Definition and DICOMDIR Keys .................................. 49

7.0 Communication Profiles 52

7.1 TCP/IP Stack Supported ............................................................................ 52

8.1 General System Configuration ................................................................... 53

8.2 DICOM Network Configuration .................................................................. 53

8.3 DICOM Store Configuration ....................................................................... 54

8.4 DICOM Storage Commitment Configuration .............................................. 54

8.5 DICOM Modality Worklist Configuration ..................................................... 54

8.6 DICOM Modality Performed Procedure Step Configuration ....................... 54

8.7 External Equipment Configuration ............................................................. 57

8.8 Support of Extended Character Sets ......................................................... 57

9.1 Security Profiles ......................................................................................... 58

9.2 Association Level Security ......................................................................... 58

9.3 Application Level Security .......................................................................... 58

9.4 Virus Protection .......................................................................................... 58

1 Second part of the DICOM standard: NEMA Standards Publication PS 3.2-2004,

Term Acronym Description

Application Entity AE An application that supports DICOM

DICOM Conformance DCS A formal statement associated with a specific

Ethernet - Network methodology devised in 1976 by Digital

Information Object IOD A data abstraction of a class of similar Real-World

Integrating the Healthcare IHE An initiative sponsored by the Radiological Society

Table 1 Terms, Acronyms, and Descriptions. (Continued)

Term Acronym Description

Request RQ A request from one DICOM AE for service from

Response RSP A response from one DICOM AE to the request for

Structured Report SR Also called Procedure Report. A DICOM object

VA Hospital Information VISTA DICOM requirements document of the US

4.0 Implementation Model

4.1 Application Data Flow Diagram

Figure 1 Implementation Model

SONOLINE G20 Local Processes

Verify SCU Verify SCP

Verify SCP Verify SCU

Store SCU Store SCP

DICOM Standard Interface

If the verification fails: “DICOM - Unable to communicate with

G20 DICOM DICOM

Figure 2 Verification Model.

4.1.2 DICOM Store

The SONOLINE G20 can be configured to automatically queue up images

Further, when “AutoStore to DICOM” option is selected once images are