Function Description Software
Function Description Software
tE
u
lo
a
c
d
M
s
n
m
ie
S
MAGNETOM
MR
Function Description
System
Software
MAGNETOM ESSENZA
10130587
© Siemens 2006
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.
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 autho-
rized 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 proce-
dures.
General. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Host software overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
MARS software overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Task cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Patient menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Transfer menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
System menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3 _______ DICOM________________________________________________________ 39
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
DICOM Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
DICOM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DICOM test tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4 _______ Database______________________________________________________ 49
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Databases on MRC and MRSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Database repair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Database access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Backup & Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Function. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Other Function Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
TuneUp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Shim . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Magnet & Cooling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Installation protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Quality Assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Test Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
DICOM Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
File & Image Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Auto Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Standard SRS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Optional SRS Services - Enhanced Productivity Services . . . . . . . . . . . . . . . . . . . . . . . 88
Connections to SRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Authentication and Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Demilitarized Zone (DMZ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
SRS <> Modality Port Connects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
This chapter focuses on the software used on the MAGNETOM ESSENZA System.
Derived from the Avanto System, the syngo MR software for hosts (including MRS, MRSC)
is still based on Windows XP Professional.The introduction of MARS (Measurement And
Reconstruction System) has lead to a new development for the image calculation and
sequence running control system.
Overview 1.1
tem, which enables us to run the entire measurement and FIRE (Fast Image Reconstruc-
tion Environment) on one computer. The Linux system is downloaded from the MRC Host
to MARS during the system booting up.
Peripheral unit part
Most of the other components or peripheral units of the MAGNETOM ESSENZA system,
such as Gradients,RFIS_60, or Patient Table, contain microprocessors running software as
well. The programs for these microprocessors are stored in PROMs, EEPROMs, or
FlashEPROMS respectively, or these programs are downloaded while booting the whole
system.
The MRC Host and the MARS communicate with one another via a 1 GBit Ethernet con-
nection.
In order to run measurements, software and parameters are supplied to the MARS and via
the MARS to all other MAGNETOM components. As a result of the measurement, the MR
signal data are transferred to the MARS for image reconstruction. Instead of the RAID hard
disks arrangement, one hard disk is needed in MARS to store the intermediate image cal-
culation data.
For long-term archiving, images are stored on CD-ROM or DVD via a CD-R or a DVD
recorder connected to the Host, a hard copy camera is connected via customer LAN or an
archive server, e.g. SIENET Magic Store is also connected via the hospital network.
Function 0
Generally speaking , the host is the domain of syngo tasks and user interfaces. In addition,
MR control-related services are also found there.
The host software includes:
• Microsoft OS (Windows XP Professional 64-bit) which also hosts the MRIR boot
loader, kernel, and file systems, and runs under the IP address: 192.168.2.1
• syngo is a software platform developed especially for medical systems and applica-
tions, and provides the basis for modality-specific control and applications, as well as
applications for a wide range of post-processing and other radiological work-
flow-related functions. syngo has a modular structure and can be divided into the fol-
lowing major functional blocks:
- syngo platform:
The syngo platform utilizes a Common Software Architecture (CSA) that provides
fundamental functionalities such as the basic image processing tool, DICOM data
model, image database, and networking capabilities.
- syngo Applications:
The common syngo applications include viewing, filming, and 3D processing, which
are the same for all syngo implementations across all modalities. In addition, special
applications developed for MR system include: EXAM, BOLD, ARGUS, and so on.
- syngo User Interface
syngo provides a user-friendly graphical interface, a common interface across all
modalities, workstations, and radiological and clinical information systems imple-
menting the syngo software.
Function 0
In the MAGNETOM ESSENZA system, the hardware upgrade for the new software archi-
tecture enables the traditional MRIR to act as a client to the host. For MARS, all required
software resides on the host and is booted via the network. After download and installation,
the MARS runs under IP address: 192.168.2.3
syngo is a software platform developed especially for medical systems and applications,
and provides the basis for modality specific control and applications as well as applications
for a wide range of post-processing and other radiological workflow -related functions.
Function 0
In the following pages, some of the important menus as well as some of the important func-
tionalities are explained.
A special user interface is called Patient Browser. It also contains main menus, sometimes
identical, sometimes very similar to the main menus of the task cards listed in the table
above.
Tab. 2 Patient Browser menus
Function 0
Patient Browser
The Patient Browser is used for administration, editing, and archiving of patient and exam-
ination data. There are several ways to open the Patient Browser. For example, use the
main menu "Patient" and select "Browser" available on the Exam task card and all other
task cards displayed at the console. The Patient Browse" uses a hierarchical structure to
show all patient and examination data in the databases and on external data media.
The Patient Browser can be customized in different ways to display or hide patient informa-
tion using different filters and views.
The Patient Browser supports a Transfer menu to import, export, send, and archive data.
The explanation of how to use these functions is given later on.
Configure Browser
The Patient Browser can also be configured in many different ways for the tree view, for list
views or single views , and for the general information available at the Patient Browser.
The work status flags are shown as a tree or list view in the Patient Browser, depending on
the checkboxes clicked or not clicked in the Patient Browser configuration tool. Here, the
customer also finds checkboxes defining permissions for deleting images. This means that
pop-up windows appear that have to be confirmed first before images can be deleted.
Function 0
General
The different functions are discussed in the following sections and shown in the figure
below.
Transfer import
Using the menu "Transfer / Import", you can import patient and examination data archived
or exported to a CD-ROM or DVD data medium in DICOM format into your system (into the
local database) if a drive such as the DVD-ROM has been configured appropriately.
Transfer archive to
You can archive data at computer systems configured as an archive node in the network
on your system. Select the menu "Transfer / Archive To" to open the dialog box with the list
of available archive nodes.
The "Transfer / Archive To" menu is also used to archive data on a CD-ROM via CD-R or
DVD-Recorder drive, if this CD-R or DVD-Recorder drive is configured as an archive
device.
Transfer send to
If your system is connected to a hospital network, you can send images via DICOM storage
to other network nodes directly from the task cards or from the "Patient Browser" using the
menu "Transfer / Send To".
Transfer export to
The "Transfer / Export To" menu is used to burn data in DICOM format on a CD-ROM or
DVD via CD-R or DVD-Recorder drive, if this CD-R or DVD-Recorder drive is not configured
as an archive device, but rather as a simple offline device.
Function 0
Exam Explorer
Protocol management
You may transfer regions, exams, and programs from the Siemens tree to your User tree
by copying them. You can also use the copy function to reorganize the program instruc-
tions, scan programs, examinations, and examination regions in your User tree.
Select the entry you want to copy in the navigation or content area. Select "Edit / Copy"
from the main menu of the Exam Explorer. Select the Region, the examination, or the mea-
surement program to which you want to append a copied or cut entry. Select "Edit / Paste"
from the main menu of the Exam Explorer.
If a "Region", "Exam" or "Program" name already exists, the new entry will get the exten-
sion 001 etc.
• Restoring
After the software re-installation (this means no change in the software version), all pro-
tocols in the backup package will be copied to the User tree.
If the software version or hardware configuration has changed, during the restoration
process only protocols with a set archive flag are converted and restored. Standard pro-
tocols without a set archive flag are not restored if these protocols are included in the
new version. In addition, those protocols having the same name in new and old soft-
ware versions will be duplicated, with the extension “001“ in the name.
Function 0
System Manager
The system status information of the main hardware for Host, Imager (Image Reconstruc-
tion System) and MR scanner (peripheral units) can be seen on the different cards in the
System Manager located under the "System / Control" menu. The Tools card can show the
log file of the MR version check software. It also starts the MR savelog mechanism.
Host card
The system status information of the main software is shown in the "Host" card. The Exam
task, Viewingtask, Filmingtask and 3Dtask are normally running (green arrow up). Optional
tasks such as the Argustask, Boldtask, etc. are normally not running (red arrow down) and
have to be started manually.
You may sometimes find that one or more applications no longer respond, i.e. your com-
mands are not accepted. If this happens, you may close these applications separately and
start them again without having to shut down syngo MR or the Operating System.
Periphery card
The “Periphery“ card displays the system status information of the main hardware compo-
nents for the MR peripheral units.
This card displays the current status of individual components of the MR scanner. All the
components of the MR scanner are listed in five groups: CAN, PCIStar, DSP, PMU, and
MCIR. The current status of the components (ok or not ok) is shown in the State column.
The list is updated automatically. The periphery units are not always online, for example,
while rebooting. Therefore, it is not possible to display the status of scanner components
during booting. During this time, the Scanner Control window shows the message "The
Scanner is not online". Normally, the following is shown: "MR scanner is ready". Customers
can check the “Helium Fill Level“ in the “Periphery“ card.
Tools card
The "Tools" card is used to acquire diagnostic information or check important system files.
If a software error occurs during scanning, it is recommended to immediately create a
"MrSaveLog" file. It contains valuable diagnostic information. Click the "Save System
Log-Files" button and the "MrSaveLog" file is created. It contains all diagnostic information
valid at the time the error occurred. It is stored in the "C:\MedCom\MriDiagnostic" folder as
a ZIP file.
The MrConsistency Checker checks the system files for changes every time the system
boots. The result is saved in a log file. You can view the content of this file in the "Support
& Diagnostic Tools" window by clicking the "View Consistency Log" button. Never install
additional software on the system. That installation could replace existing system files and
corrupt the scanner software.
Function 0
Options configuration
Patient Browser
In "Options / Configuration / Patient Browser", you'll find the Patient Browser configuration
tool that was discussed previously.
Regional Settings
Options service
Local service
In menu "Options / Service / Local Service" you start the service software.
Function 0
Help info
syngo MR also displays information about your scanner system. This includes information
regarding memory capacity as well as the memory that is still available. Select the menu
"Help / Info".
General card
By selecting the “Help/Info/General“ card, customers can get the information such as the
serial number of the system and the software version.
System card
The "System" card provides further information about your measurement system. Here,
you will find information about hardware and software options as well as the coils which can
be used at this specific system. The coils are displayed here if they are configured (refer to
Service Software Configuration) and if the QA for these coils was completed successfully.
Select "Help / Info and" go to the "System" card. All of the software options and most of the
hardware options require licenses, i.e., here we see the licenses and their expiration dates.
Disk/database card
The "Disk/Database" card under "Help / Info" displays the drives and hard disks currently
connected, including information about the capacity and free space that are still available.
It also displays how much space is available in terms of images.
The Disk list displays all physical (e.g. CD-ROM) and logical (e.g. network drives) drives.
The capacity and free space still available are listed next to them. The following information
about these drives is displayed:
All local databases are listed under Database. You are also informed about how many
images can still be stored for each matrix. The following information is displayed:
Network card
If the console or the satellite console is connected to a network, customers may view net-
work-specific information on the network card, such as node names (computer name) and
IP addresses.
Patents card
The Patents card lists all the patents used by Syngo MR.
For detailed information about DICOM, check the Intranet or attend additional DICOM train-
ing. Here only MR-relevant facts are mentioned. There are so-called "DICOM Conform-
ance Statements" including information about the DICOM data model, DICOM
implementation, the implemented DICOM services, and some configuration hints. Use the
Siemens Medical Intranet (for example:"https://intranet.med.siemens.com"), click "DICOM
Conformance Statements" and select "Magnetic Resonance" to find the DICOM Conform-
ance Statement for e.g. MAGNETOM Avanto or syngo MR 2004V.
Function 0
Implemented services
The software versions for Tim systems (e.g. syngo MR 2004V for MAGNETOM Avanto or
syngo MR 2005E for MAGNETOM Espree) include the following DICOM services as
shown in the corresponding "DICOM conformance statement" and the corresponding fig-
ure:
• DICOM service Storage
• DICOM service Storage Commitment
• DICOM service Query/Retrieve
• DICOM service Basic Print
• DICOM service Basic Worklist
• DICOM service Modality Performed Procedure Step
Function 0
Overview
The DICOM configuration is, of course, part of the service software configuration tool, but
it is discussed here to keep it close to the DICOM part of the description.
When you open the service software, enter the Configuration area and look at the DICOM
part you see: "General", "Character Set", "Offline Devices", "Network Nodes", "Print
Devices", "HC Overview" ,"LUT Files" and "HIS/RIS Nodes". These DICOM configuration
pages are discussed in syngo classes, but sometimes some questions also come up in the
Avanto classes, so we are presenting some of this information again.
General
In "DICOM General" the local application entity titles for one particular Host are defined.
Character set
In "DICOM Character Set", the characters for patient registration only are set up. This char-
acter set is not identical to the Windows XP Professional character set. Currently three
sets are available.
• ISO-IR6: 7 Bit ASCII, e.g., for the US
• ISO-IR100: 8 Bit ASCII, e.g., Latin1 with special characters such as the German ,,,
• ISO-IR13: Japanese character set
Look at the online "Help" for the selection of "multiple character sets". The selected char-
acter set will be written in the image header as DICOM attribute 0008, 0005.
If a Radiological Information System (RIS) or Hospital Information System (HIS) uses a dif-
ferent character set for patient registration, the characters of the RIS or HIS system are
used at the MAGNETOM; in this case the DICOM character set configured at the MAGNE-
TOM is ignored. This behavior is true for patient registration only. The MAGNETOM can dis-
play all characters of an image text if images are received from another modality, because
all character sets are always available to be displayed.
Network nodes
Go to the "DICOM Network Nodes" on your own Host and enter the data of all other hosts
you want to communicate with via DICOM services storage, storage commitment, and
query / retrieve. In the syngo MR software, these communication partners are called net-
work nodes. Of course, it is also possible to set up DICOM communication with non-syngo
based systems, such as NUMARIS 3.5.
Function 0
Because the DICOM test tools are explained in syngo classes, we will not go into detail
here.
The following tests are available in the current version of syngo MR software:
• Verify Network
• Storage
• Basic Print
• Storage commitment
• Query/Retrieve
• Basic Worklist
• Performed Procedure Steps (Modality Performed Procedure Steps)
• Additional information is found in the online help for DICOM test tools.
In a standard configuration, the patient database is located on the MRC Host. It contains
patient information in the DICOM image headers and pointers to the pixel information of
the corresponding images. If there is an MRSC available, the standard configuration uses
a shared database. Lets discuss the MRC database first.
The MRC database system actually uses four databases:
• The local database
• The scheduler store database
• The archive store database
• The exchange board database
At the MRC we use three hard disk drives, one CD-R or DVD-Recorder drive, and one
DVD-ROM drive:
• Drive "C" (disk 0) is used as a system software disk
• Drive "D" (disk 1) is used for the databases: Local database, scheduler store, archive
store, and exchange board
• Drive "E" (disk 2) is used to store pixel data only
• Drive "S" (CD-R or DVD-Recorder) is used to store patient data on CD-ROMs or DVDs,
and
• Drive "R" (DVD-ROM) is used to import patient data into the database.
The MRSC uses two hard disks only, but also a CD-R or DVD-Recorder drive and a
DVD-ROM drive:
• Drive "C" (disk 0) is used as the system software disk
• Drive "D" (disk 1) is used for the databases. In this case, only the archive store and
exchange board databases are available
• Drive "S" (CD-R or DVD-Recorder) is used to store patient data on CD-ROMs or DVDs,
and
• Drive "R" (DVD-ROM) is used to import patient data into the database.
Function 0
MRC database
There are four database directories on the database drive "D" :
• D:\Database\Local
• D:\Database\SchedulerStore
• D:\Database\ArchiveStore
• D:\Database\Exchangeboard
The local database (D:\Database\Local) is the main database and contains the DICOM
headers of the images that are selected for display in the Patient Browser. The DICOM
image header includes information such as patient name, institution name, modality type,
image matrix size, modality-specific parameters, etc. Each DICOM header points to a file
including the pixel information. The pixel information is the actual image stored on drive "E"
in the Image directory.
The entries in the scheduler store database (D:\Database\SchedulerStore) are created
during pre-registration or are polled via the DICOM Worklist from a HIS or RIS station. For
preregistered patients there are no images available. For this reason there are no pointers
to drive "E".
The archive store database (D:\Database\ArchiveStore) is used to store images on
CD-ROMs. The selected images will be written first to the archive store database. These
entries are pointers to the local database only. The archive procedure takes the DICOM
image headers from the local database, combines them with the corresponding pixel data,
and writes these data as DICOM files to a CD-ROM via the CD-R or to a DVD via
DVD-Recorder. When the procedure is finished, the entries in the archive store database
are deleted. The archive store database is also used when a CD-ROM or DVD including
DICOM image files is inserted into the DVD-ROM drive. The DVD-ROM drive will be
mounted, and the DICOM data on the CD-ROM or DVD are copied to the archive store
database. With the main menu "Transfer / Import", the image headers can be imported to
the local database and the pixel data are imported to pixel drive "E". Of course a pointer
between the header and the pixel information is calculated and stored in the local database
to find the corresponding pixels later on again.
The exchange board database (D:\Database\Exchangeboard) is used for networking. To
transfer images via the main menu "Transfer / Sent To", the header information and the
pixel information are put together in one DICOM file in the exchange board database and
from there sent to the network. In addition the filming jobs are stored in the exchange board
database. After a film job is finished, the last (approximately 5) film jobs are kept in the job
list. This allows you to restart a job in case of film jams. When images are displayed for
evaluation, the relevant information of manipulations is stored in the exchange board data-
base as well.
NOTE Ensure that the host name is part of the image information in
the local database. Therefore all images have to be archived
and deleted on the local database before the host name is
changed.
You will find files with the following structure in the directory E:\Image:
• 7.0. Pixel file
- The filename is an ID created by the database called LOID (Logical Object IDenti-
fier). The reference to the patient can only be seen with developer tools. The file size
indicates 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, etc. .
• 10 kB for a series
• 6 kB for raw data
• 3 kB for an image (depending on DB config.)
MRSC database
Shared database
We have discussed the databases running at an MRC, but how does a database run if
there is an MRSCas well?
There are two different ways to configure the database on an MRSC. The first is shown in
the figure below. Here we share the database of the MRC to allow access from the MRSC.
At the MRC Host you always find the four databases:
• Local database (D:\Database\Local)
• Scheduler store database (D:\Database\SchedulerStore)
• Archive store database (D:\Database\ArchiveStore)
• Exchange board database (D:\Database\Exchangeboard)
With a shared database , you will find only two databases running on the MRSC host:
• Archive store database (D:\Database\ArchiveStore)
• Exchange board database (D:\Database\Exchangeboard)
The MRSC accesses the local database and the scheduler store database of the main con-
sole MRC via network. The network access to the local database is used e.g. to display or
evaluate images on the MRSC or to print and transfer images from the MRSC.
At the MRC you use the service software configuration tool and define your Host as a main
console. Database configuration is performed automatically.
At the MRSC you use the service software configuration tool and select "Remote Data-
base". You have to configure a database index value of e.g. 100.
It is absolutely necessary to use different database index values for the MRC and MRSC.
Stand-alone database
The second way to set up a database is to configure the MRSC similar to a LEONARDO
viewing station. This means configuring a complete database running at the MRSC. In this
case, you will find the four databases at the MRSC as well:
• Local database (D:\Database\Local)
• Scheduler store database (D:\Database\SchedulerStore)
• Archive store database (D:\Database\ArchiveStore)
• Exchange board database (D:\Database\Exchangeboard)
This means that you use the service software configuration at the MRSC and select "Local
Database." The software will then automatically set the database index to zero and runs
the MRSC like an MRC from a database point of view.
Function 0
The DICOM header and the pixels of images are stored on separate disks; therefore, the
information cannot be restored if one of these two disks is missing. In other words, data
recovery is impossible if the database is corrupted or a disk is broken, refer to the TSG.
A tool which tries to repair the database is planned for future syngo versions . In other
words, there is no database repair tool available at the moment.
There are dependencies between the Local Database and the Scheduler Store. If one of
these databases must be deleted and recreated, you'll have to do this for both databases.
Function 0
Data protection
In order to prevent unintentional deletion of patient images, there is a built-in protection
mechanism. The work status flags "Printed", "Archived", "Sent", and "Received" are set by
the software automatically. The flags "Completed", "Read", and "Verified" can be set by the
operator. Icons for doing this can be configured to be available in the tool bar of the Patient
Browser.
The work status flags are automatically shown in the tree view of the Patient Browser. Addi-
tionally, which of the flags are displayed in the tree view as well as the list view of the Patient
Browser can be configured.
The Patient Browser configuration tool also allows a warning message to be displayed in
case of operations that cannot be performed without confirmation.
Database
As an alternative to starting the service software via remote or locally, select "Utilities / Source / Escape to OS", type in the command "dblist",
and click Go .
These functionalities are available at the MRC and MRSC.
09.07
M4-060.850.11.01.02
Page 63 of 96
CS SD MR
MAGNETOM
63
64 Service Software
5-
Overview
5Service Software
After selecting "Local Service" in the menu "Options / Service" and typing in the required
password, the following window is displayed.
from remote, functions such as the test tools can be used which would normally interfere
with normal system operation, e.g. patient examinations. One additional limitation for safety
reasons is blocking patient table movement via remote control.
A number of details can be seen in the following figures.
If No Access is selected in the menu "Options / Service / Remote Service" the access via
remote is blocked completely.
Function 0
In order to understand the different possibilities that can be selected in the "Event Log", the
following overview should be helpful. Note that there are three sources for messages. All
of these messages are written to the same "Event Log". An exception are the messages
from the application. There is an additional filter in the CSA Status. In the service software
configuration, the selection of a checkbox determines whether all messages are written to
the "Event Log" or only the first one as well as service-relevant messages. The idea is that
the messages caused by a previous problem (already reported) will be suppressed and
thus no unnecessary ones fill the "Event Log" and confuse the CSE. With the filter Domain,
the source of the information can be selected for display. Display of Facility Service
depends on the service configuration parameter "Display Service Messages", which deter-
mines whether service-relevant developer messages are displayed or not.
Further information is located in the online "Help" for the "Event Log"!
Reports 5.2
Function 0
Documentation 5.3
Function 0
Help 5.4
Function 0
The service software online Help functionality is explained in the syngo classes. Aside from
that it is a good idea to look at the new information in the online Help every time a new
software version is released.
Configuration 5.5
Function 0
Local Host
Site Info
In the "Site Info" configuration you'll find two screens.
The first one specifies the customer data, such as name and address information.
The second screen is used to specify the time settings for the Host computer, such as time
zone, date, time, and daylight saving time.
TCP/IP LAN
There are two networks used at a syngo MR system, the network configuration is more
complex compared to a standard syngo system.
The IP addresses of the internal syngo MR network should be 192.168.2.x (as they are the
default). 192.168.2.1 is used by the Host, 192.168.2.3 is used by the MARS. The internal
syngo MR IP addresses have to be changed only if these network IP addresses are used
in the hospital LAN.
The next figure shows the default network addresses and net mask for the internal syngo
MR network to communicate between the Host and MARS.
DICOM
For the DICOM configuration, refer to the corresponding section.
Measurement
Here you set up the MR-specific measurement configuration.
In the first screen the system type of the MAGNETOM scanner has to be selected. In this
case only MAGNETOM ESSENZA is available.
The second screen configures the number of receiver channels, the gradient coil, the gra-
dient power amplifier, etc.
The third screen configures the coils available at your system to afterward show these coils
in the QA platform.
System utilization
In the MrStatistic screen you set up the region, the type of institution, and some additional
criteria. Afterward you activate utilization with the System Utilization Activated checkbox.
Function 0
Numaris4
A restore of Numaris4 should be used after software re-installation or software update only.
All protocols from the User tree with and without archive flag are backed up. Restoring
Numaris4 after software re-installation means that all protocols are available again. After a
software update, protocols without an archive flag are deleted. In addition to the protocols,
other parts of the software will be restored, e.g., registry entries.
Customer protocols
A restore of a customer protocols archive file should be used only if all user protocols
included in an older backup should be restored.
ExamDB
The customer can import and export protocols through the Exam Explorer and therefore
this backup package is no longer needed.
TuneUp 0
Function
The details for the service software functionality TuneUp are discussed in the chapter
Tune-up / QA.
Shim 0
Function
The details for the service software functionality Shim are discussed in chapter Magnet.
Function
The details for the service software functionality Magnet & Cooling are discussed in chap-
ter Magnet.
Installation protocol 0
Function
Using the Installation Protocol is described in the service software online Help for the
Installation Protocol.
Quality Assurance 0
Function
The details for the service software functionality Quality Assurance are discussed in
chapter Tune-up / QA.
Test Tools 0
Function
The details for the service software functionality Test Tools are discussed in the different
hardware chapters.
DICOM Tests 0
Function
The functionality DICOM Tests is discussed in section DICOM.
Function
File & Image Tools is a general syngo functionality which was already discussed in your
syngo class.
Auto Report 0
Function
Auto Report is a general syngo functionality which was already discussed in your syngo
class.
Utilities 0
Function
The menu Utilities contains general syngo functionalities that were already discussed in
your syngo class.
Siemens Remote Services, or SRS, provide several remote services which translate into
clear advantages for our customers - we can help avoid system failures and resulting
down-time and even reduce repair times.
The remote technology also makes future-oriented services such as online application sup-
port or optimization of system usage through Utilization Management possible.
In addition, it allows our service organization to attain higher efficiency in service delivery
through avoidance of on-site service calls as well as attaining better planning, instruction,
and pre-clarification.
The SRS solution has implemented the necessary technical and organizational mecha-
nisms for protecting patient and system data. This includes preventing unauthorized
access (fire walls, passwords), protecting data during transmission (encryption), and the
logging of all remote activities (who, what, where, and when).
The following core services are currently integrated in the standard service agreements:
• Diagnosis and Repair - in case of an unforeseen system malfunction, the responsible
support engineer can dial into the system and clarify the type of error to speed up the
repair. Often, software errors can be corrected immediately online. Should our cus-
tomer require an engineer on site, remote diagnosis allows identification of defective
parts and accelerates their delivery, thereby keeping repair times to a minimum.
• Event Monitoring - proactively screens the performance of our customer's system. If a
parameter deviates from a predefined value, a status message is automatically sent to
our UPTIME Service Center, where service engineers evaluate the status message at
periodic intervals and initiate appropriate actions. For example, if the Helium Level of a
magnet has fallen unexpectedly to a critical value, an immediate refill can be sched-
uled.
• Software Updates - this service provides our customer's system with the latest recom-
mended updates on a continuous basis - everything takes place online.
• LifeNet Uptime Services - up-to-the-minute system and application-related informa-
tion directly at the user console of their imaging system
In addition to the standard SRS services the following optional, so-called Enhanced Pro-
ductivity Services (EPS) are currently offered to customers:
• Siemens Guardian Program♠ - guarantees our customers the highest level of sys-
tem availability possible - by proactively monitoring their system's performance on an
ongoing real-time basis for possible deviations from standard preset norms. In the
event of a system malfunction, a predefined high-speed escalation process is trig-
gered. Clearly designated reaction and repair times, improved spare parts availability,
as well as expert advice guide our customers through the first critical phase in getting
their system back online fast.
• Siemens Virus Protection - a safeguard for our customers' medical systems and clini-
cal networks against viruses of every kind. Contributes to increased patient safety, sys-
tem availability, and smoother clinical operations.
• Siemens Utilization Management - provides customers with detailed utilization analy-
ses and anonymous benchmark information on an ongoing basis to enable users to
realize their system's full efficiency potential.
• Application Training and Support - the use of SRS makes it much easier for our
applications experts to answer specific questions and give valuable advice. For exam-
ple, if an image quality problem has occurred the images can be transferred online - and
the application expert can advise our customers effectively and quickly.
Connections between the medical modalities and the SRS servers are made using routers.
Routers are intelligent devices providing Level 3 (IP address) network communications and
can be programmed to allow or block certain IP addresses or ranges from passing through
the device. For this reason, they offer much more security than MODEMS or other simple
point-to-point communication types. Routers also often include a built-in firewall, so even
Level 4 protection (TCP ports) is possible.
Routers, like switches, have the added advantage that several systems can be connected
to a single router, the number only being limited by the size of the router. Routers used for
remote connections come in different versions for use over the various communications
infrastructures available today.
They are:
• POTS (plain old telephone service) - a format that is available throughout the world. Its
bandwidth, however is very limited - from 36.6 to 56kbits/s.
• ISDN a fully digital communication format found mainly in Europe, but also in other
countries. The maximum transmit speed is 64kbits/s.
• DSL (digital subscriber line) - a relatively (2002) new communication format that is fully
digital and has high bandwidth. Max transmit rates are higher than 1Mbit/s.
• VPN (virtual private network) - a communication format that is used over internet con-
nections. It enjoys the highest security and its speed is only limited by the connection
speed to the provider.
The routers have to be configured by the Siemens Medical router specialists, who work
together with the network administrators in the hospitals. The router must also be config-
ured on the modality, a procedure described in detail in the Software Installation, under
Remote Connectivity. This is the responsibility of the CSE.
To protect the Siemens intranet - and that of the customer - from reciprocal problems and
attacks, the SRS access server, a LINUX server, is secured through a demilitarized zone
(DMZ). Connections from the Siemens service engineer to the customer system, and vice
versa, are not put through directly. They terminate in the SRS access server using a
reverse proxy function. This means that a connection established from the Siemens intra-
net is terminated in the SRS access server. This server then establishes the connection to
the customers system and mirrors the communication coming from the customer back to
the intranet.
The possibility of a communication between the Siemens intranet and the customers net-
work over not explicitly authorized protocols is thereby prevented. Mirroring occurs for pre-
defined protocols only.
This architecture is designed to prevent:
• Unauthorized access from one network to the other (e.g., hackers)
• Access from a third-party network (e.g., the Internet)
• Transmission of viruses or similar harmful programs from one network to the other. In
addition, we do not store any critical data in the DMZ, in particular, customer access
data.
The next Figure (Fig. 45 / p. 93) shows an overview of the protocols used for the various
SRS functionalities such as File & Image Tools, Autoreporting, System Utilization, and
other Value Added Services. How to test the ftp connection to the SRS Server is shown in
the document Installation Software, section Remote Connectivity: TestFTP login to the
Remote server.
The Figure (Fig. 45 / p. 93) also shows an overview of the SRS mail connection. How to
test the mail connection to the SRS Server is shown in the document Installation Software,
section Remote Connectivity.: Testing connectivity from system to RDIAG server.
The software installation for the MAGNETOM ESSENZA is simpler compared to the previ-
ous system. It includes one BIOS CD and one software DVD, which contains everything for
the Host and MARS software.
For the MARS, it only downloads the Linux kernel and runs it in the RAM. After the mount-
ing process finished , the MARS can perform its functions via the mounted paths:
• C:\MedCom\MCIR\Med
• C:\MedCom\MCIR\usr
• C:\MedCom\MCIR\var