F

g
n
a
h
Z

MAGNETOM C!
MR

Function Description
System

Software

08106705

© Siemens AG 2005
The reproduction, transmission or use
of this document or its contents is not
permitted without express written
authority. Offenders will be liable for
damages. All rights, including rights
created by patent grant or registration
of a utility model or design, are
reserved.

Print No.: M4-030.850.11.01.02 English

Replaces: M4-030.850.01.02.02 Doc. Gen. Date: 09.06
2 Revision / Disclaimer
1Revision / Disclaimer

Document revision level

The document corresponds to the version/revision level effective at the time of system
delivery. Revisions to hardcopy documentation are not automatically distributed.
Please contact your local Siemens office to order current revision levels.

Disclaimer
The installation and service of equipment described herein is to be performed by qualified
personnel who are employed by Siemens or one of its affiliates or who are otherwise
authorized by Siemens or one of its affiliates to provide such services.
Assemblers and other persons who are not employed by or otherwise directly affiliated
with or authorized by Siemens or one of its affiliates are directed to contact one of the
local offices of Siemens or one of its affiliates before attempting installation or service pro-
cedures.

MAGNETOM C! M4-030.850.11.01.02 Page 2 of 80 Siemens AG

09.06 SMMR Medical Solutions
Table of Contents 3
1- 0Table of Contents

1 _______ Software _______________________________________________________ 4

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Country Specific Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Image Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Exam Protocols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Export / Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Pixel Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Repair Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Database Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Main/Satellite Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Delete Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
DICOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Implemented Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Main and Satellite Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DICOM Character Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Service Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Service Access Manager (SAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Siemens Remote Services (SRS). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

2 _______ Index _________________________________________________________ 79

Siemens AG M4-030.850.11.01.02 Page 3 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
4 Software
2-
1Software

The Software for syngo MR (NUMARIS/4) is based on Windows XP and uses syngo as
user interface and for display, evaluation and archiving tasks. Spectroscopy and other
features are supported.

MAGNETOM C! M4-030.850.11.01.02 Page 4 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 5

Introduction 0

Overview 0

syngo MR
syngo MR consists of hardware and software.
The main hardware components controlled directly by software are:
• Host (MRC/MRSC)
• Image Processor (MRIR)
• Control Unit (MMC)
Most other components of the MAGNETOM C! contain microprocessors. The programs of
these “micros“ are stored in PROMs or EEPROMs respectively. The necessary parame-
ters will be supplied from the Host via the MMC.
For the hardware description of Host and MRIR, refer to (M4-030.850.12 / Host/Imager
(MRIR)).
The software of the MAGNETOM C! contains all information required to let the hardware
components do their tasks.
The necessary software will be booted / downloaded from the system disk into the work-
ing memory of the appropriate unit.
While Windows xp is the operating system, the application software splits into the two
main parts:
• syngo, software which is common with other Siemens modalities like CT and AX for
viewing, filming, networking (DICOM), RDIAG, patient registration, error logging and
common service tools;
• NUMARIS/4, which is the MR specific software for measurements, image reconstruc-
tion, MR specific evaluation and service functions.

Siemens AG M4-030.850.11.01.02 Page 5 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
6 Software
Syngo MR
Fig. 1:
MAGNETOM C! M4-030.850.11.01.02 Page 6 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 7

User Interface
In (Fig. 4 / p. 9) you can see the syngo parts (which are not described in this document)
and NUMARIS/4 parts.
syngo Parts
• Viewing
• Filming
• 3D (option)
NUMARIS/4 parts
• Exam
• Options
- Argus
- Bold
- Mean Curve
- Perfusion (MR)
- Spectroscopy
- 3D Vessel View
The licenses available can be seen in “Help / info“ see (Fig. 2 / p. 7)
A system status of the main hardware status (Host, Imager, MMC) can be seen in “Sys-
tem / Control”, see (Fig. 3 / p. 8)

Fig. 2: Licenses

Siemens AG M4-030.850.11.01.02 Page 7 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
8 Software

Fig. 3: Software Structure

MAGNETOM C! M4-030.850.11.01.02 Page 8 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 9
Syngo MR User Interface
Fig. 4:
Siemens AG M4-030.850.11.01.02 Page 9 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
10 Software

Fig. 5: Software Structure

The software in the MAGNETOM C can be divided into four major blocks:
• BIOS setting
• Operating System (Windows XP)
• Application Software (Syngo and NUMARIS/4)
• Service Software

Operating System
The operating system is Windows XP.

MAGNETOM C! M4-030.850.11.01.02 Page 10 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 11

On the operating system level, the following programs are absolutely necessary to run the
hardware:
• the system kernel
• device drivers are used to handle hardware components (via the kernel), such as disk
drives, keyboard, monitor, serial and parallel interfaces, network interfaces etc.
• the command interpreter (shell), a translation program to transfer alpha-numeric com-
mand strings (entered by the user) into a sequence of operation instructions which are
processed then by the hardware (the machine code).
• libraries which are data sets used for the generation and execution of programs

Application Software
The software for the MAGNETOM is called NUMARIS/4 (NUclear MAgnetic Resonance
Imaging System). NUMARIS/4 uses Windows xp as the operating system and window
manager to display windows as user interfaces for dialog and messages (syngo).
NUMARIS/4 has programs and data required to run the MAGNETOM for:
• Image display and evaluation. Therefore only the Host and operator console (MRC) is
required. For a satellite console (MRSC) a similar configuration is required a second
time.
• In order to run measurements, software and parameters are supplied to the MMC and
via the MMC to all other MAGNETOM components. The measurement data, as a result
of a measurement, are transferred to the image processor MRIR for image reconstruc-
tion. The hard disk is used to store the image data for evaluation.
• For long time archiving the images are stored onto
- CD-R (connected at the Host)
- hard copy camera (connected at the DICOM network), or an
- archive server e.g. SIENET Magic Store.

MRSC
On the satellite console the same software as on the MRC is installed. Nevertheless the
functions at the MRSC are limited to evaluation and archiving. Measurements cannot be
started from the MRSC, neither tests on the system hardware (gradients, RF, etc.) per-
formed.

Country Specific Settings 0

There are different settings to adapt hard and software to specific country environments.

Siemens AG M4-030.850.11.01.02 Page 11 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
12 Software
Country Specific Settings
Fig. 6:
MAGNETOM C! M4-030.850.11.01.02 Page 12 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 13

1) Time zone and time

This must be configured via user “Administrator“.
Daylight saving (automatic switching between summer and winter time) can be enabled.
For checking the day when the time changes see:
Start > Run > tzedit ↵

2) Language for User Interface

Currently four languages are available for the user interface inc. the MRease online help.

3) Keyboard setting
The country specific keyboard layout can be selected.
This does not allow to use all characters for patient registration (DICOM Character
Set / p. 42)

Image Transfer 0

There are several possibilities of transfering images from the local system to a remote
system.
1. Most commonly the transfer is performed via DICOM configuration and “Send to...“.
2. The images can be also archived to a CD-R via “Archive to CD-R“ or “Export to“, and
thus “Imported“ on the remote system. For more details, refer to (CD-R as Single or
Multi session / p. 13) below.
3. If the other station does not have a CD-ROM drive and is not able to handle DICOM
transfer via network, there is the possibility of “Export to Off-line“. This creates a DI-
COM file in the Windows file system (locally or to a mapped remote station). The re-
mote station can then “Import from Off-line“ into the database.
“Import“ is also the procedure to make the test images for monitor and camera
available.

CD-R as Single or Multi session

The mode to write the images onto CD-R depends on the type of Host used. After SW
installation the default mode will be:
• Celsius --> multi session
On the Celsius host, the mode can be changed in Local Service, Utilities, Escape to
OS: cdrcfg.bat -s (for single session) or -m (for multi session).
A reboot is required.

Siemens AG M4-030.850.11.01.02 Page 13 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
14 Software
Image Transfer
Fig. 7:
MAGNETOM C! M4-030.850.11.01.02 Page 14 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 15

Exam Protocols 0

There are different situations where Exam Protocols have to be backed-up/restored or

copied.
• Restore after software re-installation
• Restore after software update
• Copy protocols from one system onto another one
Therefore it is important to understand some facts.
The idea of the procedures is as shown in (Fig. 9 / p. 17)
• All Siemens protocols will be available in the User tree on a new system. It will be the
same result after a SW re-installation if no backup is available.
• Application specialist and customer will modify and save protocols.This will automati-
cally set an archive flag at the Program level see (Fig. 11 / p. 22). The backup will con-
tain all User protocols. All protocols of the User tree (with and without archive flag) will
be restored after a SW re-installation, so that the customer has the same protocols as
before.
• With a new software version there are new protocols. Old protocols and sequences
might be modified in order to achieve better image quality. Therefore the old protocols
have to be converted. Old protocols without archive flag (standard protocols) will not be
restored, since the new ones should be better. If a customer wants to keep the old stan-
dard protocols anyway, the archive flag has to be manually set in each program before
the backup is done.

Siemens AG M4-030.850.11.01.02 Page 15 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
16 Software

Fig. 8: Exam Explorer

MAGNETOM C! M4-030.850.11.01.02 Page 16 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 17
Exam Protocols
Fig. 9:
Siemens AG M4-030.850.11.01.02 Page 17 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
18 Software

A) Protocol conversion

Software re-installation / SW update

The general idea is that the operator will get his old protocols. If there were none (new
installation), he will get all Siemens protocols.
The first check during the first start of meduser is to see if protocols have been restored
(see (Fig. 10 / p. 19)).
• If NO (new installation), all Siemens protocols will also be installed in the User tree.
• If YES, it will be checked if the restored protocols are from a system with different soft-
ware version or hardware configuration.
- if NO, (SW re-installation) the operator will have the same protocols as before.
- if YES, all protocols without an archive flag will be deleted and the remaining proto-
cols will be converted. If the operator wants the Siemens protocols, he can copy them
into the User tree using the Exam Explorer or the CSE can start InstallProtocols.bat
(see (Copy inside the Exam Explorer / p. 20)).

Restore Customer Protocols via Service Software

All previous protocols in the User tree will be deleted before restoring the protocols. After
a restart medcom, the procedure is as described before.

Import Protocols via Exam Explorer

Here the existing protocols will be kept and the new one added. Programs from other SW
version or HW configuration will be proposed for conversion. They can only be imported
after successful conversion.

MAGNETOM C! M4-030.850.11.01.02 Page 18 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 19
Fig. 10: Protocol Backup Flow
Siemens AG M4-030.850.11.01.02 Page 19 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
20 Software

B) Backup/Restore Handling
In the Backup window of the Service software there are three possibilities of backing up
protocols:
• Numaris 4 (Group N4Customer)
Restore of NUMARIS4 should be used only after SW re-installation or SW update.
All protocols from the user tree will be backed up, with and without archive flag (see
(Fig. 11 / p. 22)).
When restoring Numaris 4 (after software re-installation) all protocols will be available.
After a software update the protocols without Archive flag will be deleted.
In addition to the protocols other SW parts will be restored e.g. registry entries.
• Customer Protocols
Restore of Customer Protocols should be used only if all User protocols should be
restored to the condition at the time they where backed up.

NOTE All previous User protocols will be deleted !

• Exam DB
This procedure is described in the syngo User guide.
The operator can export and import package (region, exam, program) from the Exam
Explorer directly onto/from any device (except CD-R) without assistance by a CSE (see
(Fig. 12 / p. 23)). After export there will be a file .edx (e.g. 50kB). In case the checkbox
“Export sequences“ is selected, a directory with the required sequences will be
generated (e.g.30MB). These are only required if they are user generated, since the
Siemens sequences are identical on all NUMARIS/4 systems.
The CSE can backup the exported packages if it has been exported from the Exam
Explorer into the directory C:\ExamDbBackup, because this package backs up (and
restores) the files from (to) there ! The same way in the opposite direction is used for
restore.

NOTE The files in the directory C:\ExamDbBackup will be deleted during

the next restart MedCom!

Copy inside the Exam Explorer

If a region/exam/program name already exists, the new file will get the extension 001 etc.:

MAGNETOM C! M4-030.850.11.01.02 Page 20 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 21
Tab. 1 Different ways to copy User Protocols

Exam Explorer region

copy/paste a region from Siemens to exam
User program
region 001
exam
program
InstallProtocols.bat Region
copies all regions from Siemens to exam
User program
program001

NOTE The Windows Explorer should not be used to copy protocols !

Siemens AG M4-030.850.11.01.02 Page 21 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
22 Software
Fig. 11: Protocol Backup NUM4
MAGNETOM C! M4-030.850.11.01.02 Page 22 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 23
Fig. 12: Protocol Backup Exam DB
Siemens AG M4-030.850.11.01.02 Page 23 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
24 Software

Database 0

The patient database is located on the MRC. It contains patient information (image
header) and a pointer to the location where the pixel information of the images are stored
(E:\image).
The MRC has three disks, where
• “C“ is used for system software,
• “D“ is used for the database,
• “E“ for pixel data.
The MRSC has two disks, where
• “C“ is used for system software,
• “D“ is used for the part of the database which is used only here for display and ar-
chiving.
All pixel data is stored on the MRC disk “E“ .

NOTE The information of each patient image is split into the parts Head-
er (on disk D ) and Pixel (on disk E ).
This makes it impossible to retrieve the patient images when the
database is deleted and a new one created (e.g. when a disk has
been replaced).
The pixel data may be still available, but no information about the
patient to whom it belongs.

MAGNETOM C! M4-030.850.11.01.02 Page 24 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 25
Fig. 13: Database_0
Siemens AG M4-030.850.11.01.02 Page 25 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
26 Software
Fig. 14: Database_1
MAGNETOM C! M4-030.850.11.01.02 Page 26 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 27

Export / Import 0

Before we discuss the different parts of the database in section , let us take a look at the
data structure of the patient images.
The internal patient image splits up into the two main parts:
• Header (part of database)
• Pixel (on partition E )
Whenever images are transferred via network (DICOM) or exported, pixel and header
have to be combined to an image file.
For received images (or imported from offline) it is just the other way around. An import is
necessary e.g. in order to display images from CD or to display and film the camera test
images (stored on drive “C“ ).

Pixel Disk 0

Image
In the directory E:\Image you will find files with the following structure:
• 7.0. Pixel file
- the filename is an ID created by the database called LOID (Logical Object IDentifier).
The reference to the patient can only be seen with developer tools.The file size indi-
cates the matrix size
e.g.
128 kB --> 256 matrix image
512 kB --> 512 matrix image
• BitmapFrameBlob-7.0....
- Overlays for images
• PixelData-7.0....
- DICOM attribute 7FE0
• Datainfo....
Shadow attributes contain e.g. image evaluation graphics, -labels,...
• 10kB for a series
• 6kB for a raw data
• 3kB for an image (depending on DB config.)

Repair Database 0

Since header and pixel of the images are stored on separate disks, it is obvious, that the
information cannot be restored if one of these two parts is missing. In other words, data
recovery often is impossible if the database is corrupted or a disk is broken, see TSG
Software (Database) and Host (Replacing hard disk).
A tool which tries to repair the database is planned for future syngo versions

Siemens AG M4-030.850.11.01.02 Page 27 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
28 Software

There are dependencies between Local DB and Scheduler Store. If one of these must be
deleted (and created again) it is required to do this for both DBs.
This also explains why the DBs on both consoles (MRC and MRSC) have to be recreated
together (see later).
Also the host name is part of the image information in the DB. Therefore all images have
to be archived and deleted before changing the host name!

MAGNETOM C! M4-030.850.11.01.02 Page 28 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 29
Fig. 15: Database_3
Siemens AG M4-030.850.11.01.02 Page 29 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
30 Software

Database Structure 0

There are four sections of the patient database. The first three will be indicated as Global
DB (gdbs) during boot and shutdown.

Local DB
The Local database is the main database and contains the headers of the images which
are selected in the browser for display (see (Fig. 13 / p. 25)). Included in the header is
such information as patient name, institution, modality type, image matrix size, modality
specific parameters, etc.
Each DB entry points to the file with the pixel information (the actual image) on drive “E“ .

Scheduler Store
The entries in the Scheduler Store are created from pre-registration or polled via DICOM
Worklist from a HIS/RIS station.
Since there are no images yet, there are no pointers to the pixel disk “E“.

Archive Store
If images should be written onto a CD-R, the selected images will be written first into the
Archive Store. These entries are pointed to the Local DB only.
The archive procedure takes the headers from the local DB, combines it with the corre-
sponding pixel data (evtl. compresses), and writes these files as DICOM files onto the
CD-R.
If the procedure is finished, the entries will be deleted.
In addition the Archive Store is used if a DVD-ROM with images is inserted into the drive.
Automatically the DVD-ROM will be mounted and the directory will be copied into the
Archive Store.
With “Import“ the image headers will be copied into the “Local DB“ and the pixel data will
be copied onto drive “E“.

Exchange Board
If images are displayed for evaluation the relevant information of manipulations are stored
in the exchange board.
In addition the filming jobs are stored in the exchange board. After a film job is finished the
last (approx. 5) film jobs will be still kept in the job list. This allows to restart a job in the
event of film jams.

MAGNETOM C! M4-030.850.11.01.02 Page 30 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 31
Fig. 16: Database_2
Siemens AG M4-030.850.11.01.02 Page 31 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
32 Software

Main/Satellite Console 0

Since the satellite console shares the patient data on the main console, it refers via a dif-
ferent DBID index to the main console.

NOTE The database will be destroyed if both consoles use the same
DBID index !

MAGNETOM C! M4-030.850.11.01.02 Page 32 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 33
Fig. 17: Database_4
Siemens AG M4-030.850.11.01.02 Page 33 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
34 Software

Information about the contents of the separate database parts are reflected partially in the
patient browser and can also be seen in the following windows (MRC is shown left and
MRSC is right):
• Help -> info see (Fig. 18 / p. 35)
• Local service -> Utilities -> dblist ↵ see (Fig. 19 / p. 36)

MAGNETOM C! M4-030.850.11.01.02 Page 34 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 35
Fig. 18: Database Status 1
Siemens AG M4-030.850.11.01.02 Page 35 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
36 Software
Fig. 19: Database Status 2
MAGNETOM C! M4-030.850.11.01.02 Page 36 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 37

Delete Protection 0

In order to prevent unintentional deletion of patient images there is a built-in protection

mechanism.
The flags Printed, Archived, Sent and Received will be set by the software automatically.
The flags Completed, Read and Verified can be set by the operator himself. Icons can be
configured to be available in the toolbar of the Patient Browser.
In addition it can be configured which of the flags will be displayed in the Work Status.
Furthermore it can be configured which of the flags will display a warning message, in
case the operator wants to delete images, and a required operation has not been per-
formed.

Siemens AG M4-030.850.11.01.02 Page 37 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
38 Software
Fig. 20: Delete Protection
MAGNETOM C! M4-030.850.11.01.02 Page 38 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 39

DICOM 0

For detailed information about DICOM, check the Intranet or attend extra DICOM training.
Here, only a few MR relevant facts will be mentioned.

Implemented Services 0

In the current version of syngo MR / NUMARIS4 (VA26A) the following DICOM services
are implemented (see also DICOM conformance statement).
• Storage
• Storage Commitment
• Query/Retrieve
• Basic Print
• Basic Worklist
• MPPS

Print
All required processing of the virtual filmsheet incl. LUT takes place on the local Host.

Main and Satellite Console 0

In contrast to NUMARIS/3 and 3.5 systems, both consoles are independent from the view
of DICOM configuration, archiving and handling.

Siemens AG M4-030.850.11.01.02 Page 39 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
40 Software

Fig. 21: DICOM Services

MAGNETOM C! M4-030.850.11.01.02 Page 40 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 41
Fig. 22: DICOM Configuration
Siemens AG M4-030.850.11.01.02 Page 41 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
42 Software

DICOM Character Set 0

The character set for patient registration is not identical with the Windows character set!
The allowed character sets are selectable in the service configuration. Currently two sets
are available.

ISO-IR6 7Bit ASCII e.g. for the US

ISO-IR100 8Bit ASCII e.g. Latin1 with special characters like German words
ISO-IR13 Japanese character set

For the selection of “allow multiple character sets“, refer to the online help.
The kind of character set will be written in the image header as DICOM attribute 0008,
0005.
In the event, that the RIS has a different character set configured as the modality, the
character set of the RIS will be taken, the other one ignored.
The character set of received images can be displayed, since all character sets are avail-
able for display.

MAGNETOM C! M4-030.850.11.01.02 Page 42 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 43
Fig. 23: DICOM Character Set
Siemens AG M4-030.850.11.01.02 Page 43 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
44 Software

Network 0

Since there are two networks in a NUMARIS/4 system, the network configuration is more
complex compared to a standard syngo system.
The IP addresses of the internal network should be 192.168.2.x (as they are default). Only
in the event that this network is used in the hospital, this address should be changed, pref-
erably to 10.168.2.x.
Shows the default network addresses and netmask for the internal network to the MMC
and Imager (MRIR).

MAGNETOM C! M4-030.850.11.01.02 Page 44 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 45

Fig. 24: Network Configuration

Siemens AG M4-030.850.11.01.02 Page 45 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
46 Software

Service Software 0

After selecting Local Service in the options menu and typing the required password, the
following window will be displayed.

Fig. 25: Service UI

Service Access Manager (SAM) 0

In order to prevent unauthorized access to the MR system and especially to the service
tools, a large number of protections have been implemented.
There are different service levels (1 to 7) which allows grouping access of the available
features to certain persons only.
The first level is accessible without password to the operator.
• Here the configuration parameters can be displayed only.
• In addition this level is used automatically if the operator selects the Event Log in the
Options submenu.
Furthermore we have to distinguish between local access and remote access.
• For Local Access there is only the service password which allows access to the ser-
vice UI without further limitations, since the CSE is at the system and has full control
over the system anyway.

MAGNETOM C! M4-030.850.11.01.02 Page 46 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 47

• For Remote Access it is obvious that it depends on the situation.

- If the operator wants to use the system and enables only Limited Access, the CSE
can only perform non-destructive functions e.g. reading the Event Log, transfer imag-
es files etc.
- If the operator grants Full Access , he himself cannot use the system anymore, but
from remote, functions such as tests can be performed which would interfere with
normal system operation, e.g. patient examination.
Additional limitations for safety reasons include starting X-ray (AX and CT) or table
movement, (CT, MR) etc.
- Some details can be seen in (Fig. 26 / p. 48)
• For No Access, the access from remote will be blocked.
If remote access is enabled, the router can be configured so that certain users (IP) have
accessonly. It is therefore safer than a modem where anybody could reach the system.

Siemens AG M4-030.850.11.01.02 Page 47 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
48 Software
Fig. 26: Service Access Manager 1
MAGNETOM C! M4-030.850.11.01.02 Page 48 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 49

Event Log 0

In order to understand the different possibilities that can be selected in the Event Log, the
following overview should be helpful.

NOTE There are three source where messages are coming from.
All are written into the same Event Log.

An exception are the messages from the application. Here is an additional filter in the
“CSA Status“.
In the service configuration, the selection of a checkbox determines whether all messages
are written into the Event Log or only the first one and service relevant ones. The idea is
that the messages caused by a previous problem (already reported) will be suppressed
and thus will not unnecessarily fill the Event Log and confuse the CSE.
With the option “Domain“ ,the source of the information can be selected for display.
For the display facility “Service“, it depends on the service configuration parameter “Dis-
play Service Messages“ whether or not service relevant Developer messages are dis-
played.
For additional information, refer to the online help.

Fig. 27: Event Log 1

Siemens AG M4-030.850.11.01.02 Page 49 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
50 Software
Fig. 28: Event Log 2
MAGNETOM C! M4-030.850.11.01.02 Page 50 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 51

Siemens Remote Services (SRS) 0

The following section will discuss the questions:

• “Why SRS?“ refer to (Why SRS / p. 51)

• “System Management Center (SMC)“ refer to (System Management Center
(SMC) / p. 53)
• “Services“ refer to (Services / p. 55)
• “Who can use RDIAG?“ refer to (Who can use RDIAG / p. 57)
• “How can I handle it?“ refer to (How can I handle it / p. 59)
• “What has to be configured?“ refer to (What has to be configured / p. 61)
• “How can I configure?“ refer to (How can I configure / p. 62)
• “How can it be tested?“ refer to (How can it be tested? / p. 67)

SRS is the process of Siemens Medical to provide online support via WAN communica-
tion between support centers and customer sites and thus speeding up service and
increase system uptime.

Why SRS
A) Proactive service
• By getting automatic warning about upcoming problems e.g.
- MR systems: magnet monitoring for Helium level and Shield temperature data.
(Siemens Intranet, https://cti.med.siemens.de/sites/mr_quality/mr/format/)
- Tube exchange at CT systems.
• Get performance and quality information from the installed systems.
B) Support for on site CSE from the USC, TSC, HSC
• Utilization Management (UM) can give the customer statistics about the system perfor-
mance.
C) Reactive Service (Remote Diagnostics - RDIAG), avoid unnecessary service trips
by getting remotely:
• error information
• patient image display or raw data viewing applet
• perform tests and get test results
• information about required spare parts

Siemens AG M4-030.850.11.01.02 Page 51 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
52 Software

Fig. 29: Why RDIAG? (1)

MAGNETOM C! M4-030.850.11.01.02 Page 52 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 53

System Management Center (SMC)

SMC
The SMC provides the resources:
• Database of SRS users and the installed systems
• DB for evaluation of site data (HW and SW configuration and performance)
• SW to present the results to service support centers and customer

Portal
There are two equal portals using the same DB
• Portal1 Erlangen
• Portal2 Newark

Backend Server in DMZ

For each geographical region (timezone) one Server cluster is provided
• North and South America
• Europe and Africa
• Asia and Australia (RDIAG Server only)
Each DMZ provides:
• The servers installed between two firewalls -Demilitarized Zone (DMZ).
• ISDN and VPN (Virtual Private Node) Servers for WAN connections allow secure data
transfer via telephone line or Internet.

Siemens AG M4-030.850.11.01.02 Page 53 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
54 Software
Fig. 30: Server Park
MAGNETOM C! M4-030.850.11.01.02 Page 54 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 55

Services
The SMC provides the services for the following tasks:
• Event Management (Event Monitoring) is used to monitor SIEMENS Medical applica-
tions running on medical devices at customer sites. That means sending events (e.g.
critical ones) to one of the defined DMZ’s, if the log agent monitors a defined parame-
ter, for example certain error code, which was written to a logfile of the application.
• Asset Management is used to collect asset information (i.e. regarding HW, OS, SW)
from connected medical devices.
• SW-Distribution is used to deliver the agent configuration sets to the medical devices
and is further used also to do software updates for SIEMENS Medical applications.
More tasks are planned.

Siemens AG M4-030.850.11.01.02 Page 55 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
56 Software
Fig. 31: System Management Support
MAGNETOM C! M4-030.850.11.01.02 Page 56 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 57

Who can use RDIAG

RDIAG will be mainly used by the support centers USC, TSC, HSC and finally by the busi-
ness unit (BU).
The responsible engineers will use the available RDIAG servers, where the medical sys-
tems can be accessed via a preconfigured site list.
Each user requires access permission via username and password.

Safety aspects
Since the usage of RDIAG can
• access patient data
• conflict with user actions
• modify the system software (e.g. configuration)
Safety features are implemented which limit the access permission and give the operator
full control over any remote activity.

Siemens AG M4-030.850.11.01.02 Page 57 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
58 Software
Fig. 32: Who can use RDIAG? (2)
MAGNETOM C! M4-030.850.11.01.02 Page 58 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 59

How can I handle it

A) The user interface on the RDIAG server can be accessed by registered users
with their password
The customer has to be asked to enable the remote access (see below).
A specific site can be selected out of the database entries.
This entry contains the necessary site parameters to establish a connection (see (What
has to be configured / p. 61)).
B) After typing the six characters of the service key and login, the service UI will be
displayed the same way as at the system itself
The available functions are restricted depending on the access level enabled by the oper-
ator (see (Service Access Manager (SAM) / p. 46)).
C) Enable remote access
The operator can enable / disable or restrict the access to a certain level:
• Full Access
Features like local service UI are available (except x-ray).
• Remote Application Support
The complete user interface of syngo MR can be mirrored to a remote station e.g. in
order to help the operator with system handling (future use).
• Limited Access Permanent
Same as Limited access, but no automatic disable.
• Limited Access
Non destructive functions only, e.g reading Event Log. The connection will be disabled
if there was no connection for more than two hours.
• No Access

Siemens AG M4-030.850.11.01.02 Page 59 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
60 Software

Fig. 33: How can I handle it? (3)

MAGNETOM C! M4-030.850.11.01.02 Page 60 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 61

What has to be configured

The situation in the hospital can be quite complex. Shows an example with different sys-
tems in a network.
At the system a VPN - connection to the Internet or a router is required.
The router can be connected to an ISDN line or (via an optional serial-interface and
modem) to a POTS (plain old telephone service) line.
For our system the RDIAG server and System Management servers are just nodes in a
different network. The router has to find the way to the server.
Different targets can be configured at the system e.g.
• USC for customer email and error messages
• HSC for statistical data (quality database)
• CSE email account (inside the Siemens intranet)

Siemens AG M4-030.850.11.01.02 Page 61 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
62 Software

Fig. 34: What has to be configured? (4)

How can I configure

Before RDIAG can be used, some configuration is necessary.
Configuration has to be done “At the system“ and “At the RDIAG Server“:
At the System:

MAGNETOM C! M4-030.850.11.01.02 Page 62 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 63

Here the principle will be explained, for detailed instruction see software Installation and
Configuration Instruction .
Several parameters have to be determined at the site and reported to the USC. Especially
the passwords have to be coordinated between the CSE and the RDIAG Server adminis-
tration.
After configuration all functions should be tested, since a malfunction is likely if one of the
several parameters is misspelled.
IP Reservation Tool
For a small network administered by Siemens, all network addresses can be determined
with the “IP Reservation Tool“ in the Intranet see (Fig. 35 / p. 63)
(The URL in the Intranet, http://tdi-s3.med.siemens.de/applicationdb/Silver-
Stream/Pages/ip_start.html)
For a RAS connection at syngo-based systems the IP address will be mostly configured
with addresses from the “IP Reservation Tool“.

Fig. 35: IP Reservation Tool

Siemens AG M4-030.850.11.01.02 Page 63 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
64 Software
Fig. 36: RDIAG System config (7)
MAGNETOM C! M4-030.850.11.01.02 Page 64 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 65

At the RDIAG Server:

The administrator of the RDIAG Server has the permission to ADD or MODIFY system
entries.

Siemens AG M4-030.850.11.01.02 Page 65 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
66 Software
Fig. 37: RDIAG Server Config
MAGNETOM C! M4-030.850.11.01.02 Page 66 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 67

How can it be tested?

RDIAG Server to system see (Fig. 38 / p. 69)
Select the appropriate entry in the RDIAG Server, then a connection will be established
by:
1. Dialing the correct phone no. of the system (ISDN-router)
2. The destination ISDN-router checks the Chap password and calls back
3. Connecting to the system (remote must be enabled)
4. Establish a transparent IP connection (IP address)
5. The Service login UI is displayed
After typing the six missing password characters the real Service UI will be displayed.
System to RDIAG Server see (Fig. 39 / p. 70)
This can also be tested from remote.
• Writing an Email from user UI Options -> Service -> Remote Service -> Mail
• Autoreport with or without attachment (after setup and triggered by the conditions)
A connection will be established by:
1. Dialing the correct phone no. of the RDIAG Server (via router)
2. Connecting to the RDIAG Server
3. Establish a transparent IP connection (IP address)
4. Transfering the E-mail via SMTP (to configured E-mail address)
5. Disconnecting
The E-mail attachments will not use the FTP account, but files selected as separate file
via: File & Image transfer.
1. Select an image to be transferred in batch mode.
2. End the service session.
After app. 3hrs. the system will establish a connection by:
1. Dialing the correct phone no. of the RDIAG Server (via router)
2. Connecting to the RDIAG Server
3. Logging in as user “rdiagftp” (with configured password)
4. Establish a transparent IP connection (IP address)
5. Transfering the image file via FTP (to a data pool)
6. Disconnecting
The account and password for FTP is identical for all systems. The image files will be
sorted into a directory e.g. “mr22002” named by the sending modality. The filename will
be called e.g. mr22002_xxxx.img.
The modality is determined by the configuration parameter “System type” (fixed for MR).
Before the transfer of the image file, some parameters like patient name and patient id are
anonymized.
Connect status and history see (Fig. 40 / p. 71)

Siemens AG M4-030.850.11.01.02 Page 67 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
68 Software

At the system the connect status (and history) can be seen

• as Icon on the user UI bottom line
• in the Options -> Remote Service UI (see (Fig. 33 / p. 60))
• in the Event log, Domain Customer
• in Utilities -> Session List

MAGNETOM C! M4-030.850.11.01.02 Page 68 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 69
Fig. 38: Connect flow 1
Siemens AG M4-030.850.11.01.02 Page 69 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
70 Software
Fig. 39: Connect flow 2
MAGNETOM C! M4-030.850.11.01.02 Page 70 of 80 Siemens AG
09.06 SMMR Medical Solutions
Software 71

Fig. 40: Connect Status and History

Siemens AG M4-030.850.11.01.02 Page 71 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
72 Software

Software Installation 0

For software installation, the following media are available:

1. DVD-ROM “syngo MR“ 1-3/6(WinXP, syngo, NUMARIS) for Host and MRSC
2. DVD-ROM “syngo MR“ 4/6(WinXP, syngo, NUMARIS) for Imager .

MAGNETOM C! M4-030.850.11.01.02 Page 72 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 73
Fig. 41: Software Installation 1
Siemens AG M4-030.850.11.01.02 Page 73 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
74 Software

Installation Procedure 0

The number in brackets refers to the chapter in the installation instructions.

The system is delivered from factory with pre-installed software. Therefore only steps (2),
(6) and (5) are required.
For a complete software re-installation however, most of the following steps have to be
performed.
(2) All necessary parameters should be collected and noted in the Configuration Pages
e.g. system configuration, network addresses, remote nodes, etc.
(3) After the BIOS setting (3.1), Windows XP and syngo will be installed onto the MRC
system disk (3.2).
Next the NUMARIS4 sw will be installed onto the system disk (3.3).
The Service key (password) must be available for configuration or restore.
If a backup is available, it can be restored e.g. from CD-R (3.4).
Otherwise, (and this is true for a new system installation) the software has to be config-
ured (6).
Part of the configuration is the installation of the license file (6.7), which enables the
options, protocols and sequences. The license is calculated for the Dongle ID!
For the first installation, tune-up has to be performed as well and site-specific data have to
backed up, e.g. on CD-R (5.1).

MAGNETOM C! M4-030.850.11.01.02 Page 74 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 75
Fig. 42: Software Installation 2
Siemens AG M4-030.850.11.01.02 Page 75 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
76 Software

MRIR
The MRIR requires software and configuration only for updates or for sw reinstallation.
Therefore monitor, keyboard and mouse have to temporarily be taken from the MRC or
MRSC.

Configuration 0

In the first window the required options have to be selected and will be displayed in the
second window. The options marked as Standard will always be available.
For details, refer to the SW installation instructions.

MAGNETOM C! M4-030.850.11.01.02 Page 76 of 80 Siemens AG

09.06 SMMR Medical Solutions
Software 77
Fig. 43: Software Configuration
Siemens AG M4-030.850.11.01.02 Page 77 of 80 MAGNETOM C!
Medical Solutions 09.06 SMMR
78 Software

Backup 0

Refer to the SW installation instructions for details..

MAGNETOM C! M4-030.850.11.01.02 Page 78 of 80 Siemens AG

09.06 SMMR Medical Solutions
Index 79
3-
D
2Index

Database . . . . . . . . . . . . . . . . . . . . . . .24

N Network . . . . . . . . . . . . . . . . . . . . . . . .44

Siemens AG M4-030.850.11.01.02 Page 79 of 80 MAGNETOM C!

Medical Solutions 09.06 SMMR
80 Index

MAGNETOM C! M4-030.850.11.01.02 Page 80 of 80 Siemens AG

09.06 SMMR Medical Solutions