Galileo System

Operator Manual

OPEN DATABASE
Galileo NT connection to HIS

CONNECTION SPECIFICATION
SECTION

B8300030511
Rev. A
(BOOKLET)

EDITION:

July 2004

EBNeuro
-FLORENCE-
ITALY
 Galileo System

Operator Manual

OPEN DATABASE
Galileo NT connection to HIS

CONNECTION SPECIFICATION
SECTION

B8300030511
Rev. A
(BOOKLET)

EBNeuro
-FLORENCE-
ITALY
OPEN DATABASE Operator Manual

TABLE OF CONTENTS

CHAPTER 1 - WARNING

1.1 INFORMATION ABOUT THE MANUAL 1-1

1.1.1 CONVENTION 1-2
1.2 MANUAL CONTENTS 1-2

CHAPTER 2 - INTRODUCTION

2.1 GALILEO ENVIRONMENT 2-1

2.2 INTERFACING GALILEO TO HIS 2-2

CHAPTER 3 - SPECIFICATION
3.1 GALILEO XML FILE DESCRIPTION 3-1
3.2 IMPORTING SCHEDULED EXAM LIST 3-2
3.3 EXPORTING EXAM 3-4
3.4 SEARCHING PATIENT 3-5

Table of contents i-1

Operator Manual OPEN DATABASE

For your notes:

i-2 Table of contents

OPEN DATABASE Operator Manual

CHAPTER 1 - WARNING

1.1 INFORMATION ABOUT THE MANUAL

This document contains proprietary information. No part of this publication may

be photocopied or reproduced without the prior written permission of EBNeuro.

Information in this document is subject to change and revision without notice.

Issues:

First edition: B8300030511 - Rev. A - July 2004

This manual is to be considered as a component of the equipment. When installing

the equipment for the first time, the user should accurately check the content of
the Manual in order to verify its integrity and completeness.
In the event the Operator Manual should be ruined, incomplete or inadequate,
please contact EBNeuro in order to immediately restore or replace the not
compliant Manual.

The official version of this Operator Manual, of which EBNeuro is directly

responsible, is the English versions. For countries in which languages other than
English are spoken, the official Manual is the English version. EBNeuro does not
undertake any responsibility for any translations in other languages made by
distributors or users.

The observance of the operating procedures and of the warnings described in this
Manual is a basic requirement for the correct working of the equipment and to
guarantee the patient’s and the user’s safety.
The Manual must be read in every part in front of the equipment before using it,
in order to become familiar with the operating procedures, the commands, the
connections to the peripheral instruments, and the precautions for a correct and
safe usage.

The Operator Manual should be kept, complete and readable in every part, in a
safe place, and, at the same time, it should be rapidly accessible to the user when
using the equipment.

Warning 1-1
Operator Manual OPEN DATABASE

1.1.1 CONVENTIONS

NOTE
The notes contain important information to be underlined with respect to the rest
of the text. They generally contain information useful for the user to correctly
perform and use the operating procedures of the equipment.

WARNING
Warning messages appear in the Manual prior to procedures or operations that
should be observed in order to avoid any data losses or damages to the
equipment.

ATTENTION

Attention messages appear in the Manual with reference to the description of

procedures or operations that, if not performed correctly, could cause damages to
the user or the patient.

1.2 MANUAL CONTENTS

This document is intended as a guide to interface the Galileo PMS software to the
Hospital Information System using standard XML file exchange, describing the
operations and the file format required for a correct interface.

The manual presents an introduction of the problem and then a description of the
general Galileo XML format, that is the basic format for all the operation
described in this manual.
Then all the three possible interfacing procedures are described, both from the
operating and the technical specification point of view:
• Scheduled exam management
• Exam export
• Patient search

1-2 Warning
OPEN DATABASE Operator Manual

CHAPTER 2
INTRODUCTION

2.1 GALILEO ENVIRONMENT

GALILEO NT line is a product consisting of some module “specialized” for the

acquisition, storage and on-screen display or off-line printout of biological
signals, and is especially designed for the management of encephalic signals. In
particular, the various “software module” are specialized to operate in the field of
the Electroencephalography (EEG, VIDEOEEG), the Polysomnography (PSG),
the Evoked Potential (EP), Event-Related Potentials (ERP) and the
Electromyography (EMG).

The system employs a new and efficient database, developed in the Borland
Interbase SQL Server 6.0 environment, that is dedicated to store, organize,
manage the data of all patients and exams, considered both as textual information
and as numerical acquired signals. Its points of strength lie in the solidity offered
when accessing/exchanging the data on the network, in its safety in terms of
privacy, in the user-friendliness of its user interface and in the speed with which
queries can be performed within large databases.

The data connected to each patient of the database are generally divided into:

• Traces (or Recordings): a collection of data normally acquired directly by the

system. The data are usually displayed in a set of two-dimensional lines on
screen or paper (traces). A typical example is an EEG recording. It is important
to stress that GALILEO NT is designed to handle several other kinds of
tracings (i.e. an Evoked Potentials recording, and EMG recording…).

• Sub Recordings: A Recording may be “split” in a series of Sub-recordings; for

example an EMG Exam is normally split in a series of Sub-recording each of
which is a particular study (EMG trace, …) which individually correspond a
specific acquired EMG traces (i.e. SNCV, MNCV, EMG…). This division in
Sub-recording may be useful to perform later some “filter” or statistical
elaboration on a particular type of exam.

• Analysis: The Recording data may be elaborate in several ways to obtain

different collection of data called Analysis. For example an EEG Recording
may be elaborate to obtain a Compressed Spectral Array (CSA) representation.
The CSA data file is an Analysis.

• Exams: are collections of data, not acquired directly by GALILEO NT system,

linked to the patient, which are typically (but not exclusively) represented by
images (for example a CT or MRI scan).

• Patient history (or Patient Report): is a “document”, (composed with an

user-selectable word processor) containing all the patient’s facts: history,

Introduction 2-1
Operator Manual OPEN DATABASE

comments, diagnostic deductions and related information that the physician

might need to know.

• Data Report: Recording and Analysis can have a document linked called
“Data Report”. The Data Report is managed in the same way as the Patient
History, but contains diagnostic inferences, and comments which are not
directly related to the patient, who is the “owner” of the tracing, but to the data
(tracing or Analysis) itself. The user is of course free to use either one or the
other, or both the reports according to their requirements.
• Comments. To facilitate the input of short “comments” both at patient level
and data level, GALILEO NT provides a way to “attach” to each patient or
tracing (as well as to any exam or analysis) a few lines of comment, without
the need of using a separate word processor.

2.2 INTERFACING GALILEO TO HIS

The increasing need of integration between Galileo and the Hospital Information
Systems (from now on, HIS) is due to a couple of reasons:
• Reduce error in manual insertion of patient data
• Speed operations that require operator intervention

In order to accomplish these tasks, Galileo provides a basic method to interface a

Hospital Information System: in particular, Galileo support the following 3 basic
functions to exchange information with the HIS:
1. importing scheduled exam list
2. exporting exam result
3. patient search

All the 3 functions are based on the exchange of standard XML files with a
predefined format that will be described below. Moreover, Galileo provides a
more advanced technique managing the calls to a custom software module (a
standard DLL, called WRAPPER) that can be written to send command to the
HIS in order to make it interact with Galileo.

In other words, Galileo can exchange information by XML files with or without
sending command to the HIS.

Let’s show this with a practical example. Let’s suppose that Galileo want to read
the exam list from the HIS. There are 2 possible solutions, accordingly to custom
requirements:
• The HIS exports automatically the scheduled exam list copying a XML file in a
dedicated network disk and Galileo reads this list any time a new exam must be
done

2-2 Introduction
OPEN DATABASE Operator Manual

• Galileo asks the HIS for the scheduled exam list with a call to the custom
software module, the WRAPPER, sending for instance SQL commands and
generating a XML file with the HIS answer

The WRAPPER could be used also to translate other file format (for instance, a
HL7 formatted file) into the internal XML file format.

The same philosophy is used to manage the second function (exporting exam
result) where Galileo export a XML formatted file and optionally can make a call
to a WRAPPER module function in order to translate the file format or to send
commands to HIS, accordingly to custom requirements.

As concerns the third function (patient search), the simple XML solution is a little
bit more complicated than the previous two because it would require a good
synchronization of the two systems. In particular, it requires the following steps:
1. Galileo writes the XML with the name of the patient to search for and waits
for the answer
2. the HIS waits for such a file; when it find the file, process the search and then
writes the answer in an other XML file

when Galileo finds the XML with the answer, reads it and shows the results,
allowing patient insertion.

Of course this approach requires some minimal system/software work in the HIS
side, because the Hospital system must be able to read and write XML file in the
Galileo format. In case this is not possible, a WRAPPER module can be
developed by EBNeuro, in order to send query directly to the HIS database
engine.

Introduction 2-3
Operator Manual OPEN DATABASE

FOR YOUR NOTES:

2-4 Introduction
OPEN DATABASE Operator Manual

CHAPTER 3
SPECIFICATION

In this sections first of all the standard Galileo XML format will be described, then
the 3 different functions will be described in detail, providing examples and
explanation of all the information and procedures. For all cases, only the simple
XML exchange method will be described, because the usage of the WRAPPER
module requires some programming skill that is not in the purpose of this
document. The exchange files for all functions has the same Galileo XML format
with the fields as described in the next section, however, in each case some of the
fields are not necessary as will be said in the correspondent table.

3.1 GALILEO XML FILE DESCRIPTION

The Galileo XML file is a standard XML file that can store almost all Galileo
database information organized in a similar way as the database itself do. In other
words, the file contains a list of patients and each of them can have none, one or
more exams, as in the Galileo database. The following table lists all the field and
their meaning in the general Galileo XML file, where in each file more than one
patient can be found, and each patient may have more than one exam:

Field name Description

GALILEO_NT Field enclosing all Galileo data
Patient Groups all patient data; Patient Key is a unique string key (optional)
Pid Unique numeric patient ID in the XML file (max 2^31)
FirstName Patient first name (max 32 chars)
LastName Patient last name (max 32 chars)
Birthdates Patient birth day
Birthplace Patient birth place (max 32 chars)
Usurped General patient ID (social security number, health ID, etc, max 24 chars)
Gender Patient sex (M, F or empty, 1 char)
Street Address street (max 32 chars)
City Address city (max 32 chars)
Zip Address ZIP code (max 8 chars)
Country Address country (max 32 chars)
Phone Patient phone number (max 20 chars)
Comment Optional textual notes added to the patient
PatientReport Text of Patient report
PatientStatistic Optional additional custom patient field; Code is the name of the field
Trace Start key for all exam info; Trace Key is a unique string key (optional)

Specification 3-1
Operator Manual OPEN DATABASE

Tid Unique numeric exam ID in the XML file (max 2^31)

Status Status of scheduled exams (not yet used)
RecCreationDate Date of recording (completed or scheduled)
StandardType Exam type (must be translated between the two systems, max 18 chars)
StandardSubType Exam subtype (max 12 chars)
FileSize Exam file size
UserTid Common exam ID in the HIS and Galileo (max 16 chars)
RecordingDuration Duration of recording expressed in seconds
Comment Optional textual notes added to the patient
TraceReport Text of exam report
TraceStatistic Optional additional custom exam field; Code is the name to the field

3.2 IMPORTING SCHEDULED EXAM LIST

Using simple XML file requires that the HIS writes a XML file formatted as above
in a predefined shared disk before Galileo starts recording exams. The file for
scheduled exams is equal to the generic Galileo XML file with some little
differences:
• The recording date (RecCreationDate) is the time and date when the exam has
been scheduled
• Recording duration (RecordingDuration) and trace report are ignored

To configure the import path, use Galileo configuration program GalntCfg4NT,

page Import/Export, and set Prenotation Path (and Prenotation File if different from
*.xml). With this setting, anytime the user runs the acquisition wizard, a XML file
is searched in the import path and the list of exam scheduled is read. Finally, the list
of scheduled exam is shown and the user chooses the exam to perform.

3-2 Specification
OPEN DATABASE Operator Manual

If the patient already exists in the archive, the new exam is attached to that patient,
if he/she is a new patient, the new patient is inserted in the archive than the exam is
attached to him/her. Moreover, the field StandardType must match one of the
recording type managed by Galileo.

An example of a scheduled exam file is shown:

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>

<!--GALILEO NT exchange file-->
<GALILEO_NT command=ScheduleList>
<Patient PatientKey="XML0">
<Pid>0</Pid>
<FirstName>MARIO</FirstName>
<LastName>ALBERO</LastName>
<Birthdate>20/11/1918</Birthdate>
<UserPid>#000alb</UserPid>
<Gender>M</Gender>
<Street>Via di Forlimpopoli, 35</Street>
<City>Verona</City>
<Zip>40109</Zip>
<Country>Italia</Country>
<Phone>045-981302</Phone>
<BirthPlace>VICENZA</BirthPlace>
<Trace TraceKey="XML0">
<Tid>0</Tid>
<Status>deleted</Status>
<RecCreationDate>27/06/2004 10.02.03</RecCreationDate>
<StandardType>EEG GALNT</StandardType>
<UserTid>123456alb</UserTid>
<TraceStatistic code="Exam type">EEG STANDARD</TraceStatistic>
</Trace>
</Patient>
</GALILEO_NT>

The minimum field set required to insert a scheduled exam into the list are Patient,
with FirstName, LastName, Birthdate, UserPid, and a Trace, with
RecCreationDate, StandardType, UserTid. Any additional field is found in the file
is inserted in the new record created in the archive. For instance, if a TraceStatistic
field is found, a correspondent couple CODE and VALUE is added to the new
exam (see Galileo PMS manual)

The UserTid field is very important to be unique in both HIS and Galileo systems;
it is the one that will be used to link the information of a specific exam in Galileo
with the exam information in the HIS. For instance, after closing the report, the
exam can be exported back to the HIS and the exam report is added to the patient
file in the HIS.

Specification 3-3
Operator Manual OPEN DATABASE

3.3 EXPORTING EXAM

Galileo PMS export exams to the HIS when the exam report is first closed. Closing
exam report makes the exam itself read-only, and the exam is not exported unless it
is reopened and closed again. Exporting exam with XML to the HIS writes a XML
file formatted as above in a predefined shared disk where the HIS should poll
periodically to search for it. The file for scheduled exams is equal to the generic
Galileo XML file and can contain all the listed fields: the Galileo fills all the
available information.

To configure the export path, use Galileo configuration program GalntCfg4NT,

page Import/Export, and set File export path. With this setting, any time the user
close a trace report, Galileo PMS exports a file named as export_XXX.xml, where
XXX is the first free integer, in order to avoid to overwrite files. Moreover, a copy
of the original exam report file (WORD or RTF) is made in the same path. This file
is named Tnnn.doc, where nnn is the value of the Tid field in the XML file.

An example of an exported exam file is shown:

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>

<!--GALILEO NT exchange file-->
<GALILEO_NT>
<Patient PatientKey="XML103">
<Pid>103</Pid>
<FirstName>MARIOTTE</FirstName>
<LastName>ALBRIGHT</LastName>
<Birthdate>20/11/1918</Birthdate>
<Gender>F</Gender>
<PatientReport>
Patient Report
General Hospital
Neurophysiology Department

ANAGRAFICA PAZIENTE:#003

Nome MARIOTTE
Cognome ALBRIGHT
Data di nascita 20/11/1918
Luogo di nascita
Residenza
Telefono
Sesso M
Provenienza Neurologia

</PatientReport>
<PatientStatistic Code="PATOLOGIA">EPILESSIA</PatientStatistic>
<PatientStatistic Code="PROVENIENZA">NEUROLOGIA</PatientStatistic>
<PatientStatistic Code="TICKET">ESENTE</PatientStatistic>
<Trace TraceKey="XML213">
<Tid>213</Tid>

3-4 Specification
OPEN DATABASE Operator Manual

<RecCreationDate>20/11/1998</RecCreationDate>
<StandardType>EEG GALNT</StandardType>
<RecordingDuration>1360</RecordingDuration>
<FileSize>8538</FileSize>
<Status> </Status>
<TraceReport>
General Hospital
Neurophysiology Department

Patient: MARIOTTE ALBRIGHT

BirthDate: 20/11/1918
PID: #003

Patient code list:

Recording type: EEG GALNT
Recording date: 20/11/1998
Recording duration: 00:22:40

Trace code EEG Standard

</TraceReport>
<TraceStatistic Code="STAZIONE DI REGISTRAZIONE">SIRIO A</TraceStatistic>
<TraceStatistic Code="TECNICO">SIG. PAOLO</TraceStatistic>
<TraceStatistic Code="TIPO DI REGISTRAZIONE">EEG STANDARD</TraceStatistic>
</Trace>
</Patient>
</GALILEO_NT>

In this case, a Word document named T213.doc has been copied in the same path as the XML file.

3.4 SEARCHING PATIENT

As said before, the patient search procedure is a little bit more complicated as the
previous two, as it requires a double exchange of XML files, one from Galileo to
the HIS and one back from the HIS to Galileo, both in a predefined shared disk.
First in Galileo, from menu Patients ⇒ Search patients on other archives, the user
can insert some data of the patient to search (for instance, lastname, firstname and
birthdate or just lastname, as in the example):

Specification 3-5
Operator Manual OPEN DATABASE

On confirmation, Galileo writes in the defined network path a XML files named
QUERY.XML with just the data of the patient to look for, then Galileo waits a
number of seconds for the answer from the HIS. In the meantime, the HIS finds the
XML file from Galileo, processes the search and writes the result of the search in a
XML file named ANSWER.XML. If no patient matching the query is found, the HIS
may write no file or write a file with no patient.

If Galileo finds the answer file with some patients that match the query, a list of the
found patients is shown and the user can select one of them, look at detailed patient
data and insert him/her in the archive if desired:

To configure the exchange path, use Galileo configuration program GalntCfg4NT,

page Import/Export, and set Patient query path. This will be the path where Galileo
will write the query file and will look for the answer file. The defaul time that
Galileo will wait for the answer file is 30 seconds; if a different value is needed,
edit configuration file DBGALNT.INI in Windows directory, setting
SecWaitForSearch in section [HISConnection] to the desired value:
[HISConnection]
SecWaitForSearch=60

3-6 Specification
OPEN DATABASE Operator Manual

The above example of a patient search is shown:

QUERY.XML

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>

<!--GALILEO NT exchange file-->
<GALILEO_NT>
<Patient PatientKey="SIOExchange0">
<Pid>0</Pid>
<LastName>VALLI</LastName>
</Patient>
</GALILEO_NT>

ANSWER.XML

<?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>

<!--GALILEO NT exchange file-->
<GALILEO_NT>
<Patient PatientKey="XML0">
<Pid>0</Pid>
<FirstName>MARIO</FirstName>
<LastName>VALLI</LastName>
<Birthdate>20/11/1918</Birthdate>
<UserPid>#000alb</UserPid>
<Gender>M</Gender>
<Street>Via di Forlimpopoli, 35 </Street>
<City>Verona</City>
<Zip>40109</Zip>
<Country>Italia</Country>
<Phone>045-981302</Phone>
<BirthPlace>VICENZA</BirthPlace>
</Patient>
<Patient PatientKey="XML1">
<Pid>1</Pid>
<FirstName>EDOARDO</FirstName>
<LastName>VALLI</LastName>
<Birthdate>10/04/1968</Birthdate>
<UserPid>#00omos</UserPid>
<Gender>M</Gender>
<Street>Via di Ripoli, 35 </Street>
<City>Firenze</City>
<Zip>50129</Zip>
<Country>Italia</Country>
<Phone>055-182352</Phone>
<BirthPlace>FIRENZE</BirthPlace>
</Patient>
<Patient PatientKey="XML2">
<Pid>2</Pid>
<FirstName>ALIDA</FirstName>
<LastName>VALLI</LastName>
<Birthdate>10/09/1928</Birthdate>
<UserPid>#00oos</UserPid>
<Gender>F</Gender>
<Street>Via di Ripoli, 35 </Street>
<City>Firenze</City>
<Zip>50129</Zip>
<Country>Italia</Country>
<Phone>055-182352</Phone>
<BirthPlace>FIRENZE</BirthPlace>
</Patient>
</GALILEO_NT>

Specification 3-7
Operator Manual OPEN DATABASE

For your notes:

3-8 Specification