Admin Manual

User Manual:

Open the PDF directly: View PDF .
Page Count: 58

Download
Open PDF In Browser	View PDF

Administrator’s Guide

Open Hospital
An

product

Table of Contents
1

Abstract

4

2

Introduction

5

3

Installation

6

3.1

OpenHospital

3.1.1
3.1.2
3.1.3
3.1.4

3.2

4

5

Java Runtime Environment
MySQL Server and OpenHospital DB
Configure OpenHospital
Run OpenHospital

Portable OpenHospital

Folders

6
6
7
9
10

10

12

4.1

Foldertree in OpenHospital

13

4.2

Foldertree in Portable OpenHospital for Linux

13

4.3

Foldertree in Portable OpenHospital for Windows

14

Configuration Files
5.1

generalData.properties

5.1.1
5.1.2
5.1.3
5.1.4
5.1.5
5.1.6
5.1.7
5.1.8
5.1.9
5.1.10
5.1.11
5.1.12
5.1.13
5.1.14
5.1.15
5.1.16
5.1.17
5.1.18
5.1.19
5.1.20
5.1.21
5.1.22
5.1.23
5.1.24
5.1.25
5.1.26
5.1.27
5.1.28
5.1.29
5.1.30
5.1.31

LANGUAGE
SINGLEUSER
AUTOMATICLOT
LOTWITHCOST
PATIENTSHEET
OPDCHART
ADMCHART
DISCHART
PATIENTBILL
BILLSREPORT
BILLSREPORTMONTH
PHARMACEUTICALORDER
PHARMACEUTICALSTOCK
PATIENTEXTENDED
OPDEXTENDED
MATERNITYRESTARTINJUNE
LABEXTENDED
LABMULTIPLEINSERT
INTERNALPHARMACIES
MERGEFUNCTION
INTERNALVIEWER
SMSENABLED
MAINMENUALWAYSONTOP
RECEIPTPRINTER
VIDEOMODULEENABLED
PATIENTVACCINEEXTENDED
ENHANCEDSEARCH
XMPPMODULEENABLED
DICOMMODULEENABLED
DICOMMODULEENABLED
DEBUG

15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
45
46

5.2

database.properties

47

5.3

dicom.properties

48

5.4

examination.properties

49

5.5

log4j.properties

51

5.6
5.6.1
5.6.2

53

GSM.properties
Skebby.properties

53
54

5.7

txtPrinter.properties

55

5.8

xmpp.properties

56

5.9

Bundles

57

5.9.1

6

sms.properties

New Translations

Reports

57

58

6.1

Compatibility: iReport® 3.0.0

58

6.2

Links

58

1 Abstract
This application is the first of a set of software products that ISF1has developed to support the
management and the activities of the St. Luke Hospital in Angal (Uganda). After that mission, the
St. Luke Hospital has become only the first one of a long list of hospitals that found this software
useful.
All the work was realized as an open-source2 project using only open-source development
software.
This application software consists of the following parts:












Pharmacy management
Laboratory management
OPD management
Patient admission and discharge management
Pregnancy management
Malnutrition control management
Vaccines database
Patient billing support
Therapy management
Internal communication
Statistics and printing

This document describes how to install the application and how to configure it in your
environment, enabling and disabling functionalities as well as manage users.
The reader will not find in this manual the information he needs for the use of the application
software; to have such information you should consult our User’s Guide, supplied with the
application software.

1
2

InformaticiSenzaFrontiere = Computer scientists without frontiers
Open-source = software for which the original source code is made available to anyone free of charge.

Rel. 1.8.0 (December 2014)

2 Introduction
The aim of this program is to manage, in the simplest manner, the hospital administrative operations
like registering patients and laboratory analysis, and to produce statistics for the health ministry. In
the following chapters the users will find all the information they need in order to use properly the
program.

Pag. 5

Rel. 1.8.0 (December 2014)

3 Installation
3.1 OpenHospital
OpenHospital is a stand-alone Java software that not require installation. The .zip file can be copied
and moved everywhere in your system, whether it is Windows or Linux.
It acts like a client application. The server part is carried out by the DBMS (Database Management
System) that is, from its first version, the free and open-source MySQL.
The real part of the installation it concerns the JRE installation, the MySQL Server and the creation
of the DB, which is done through the execution of a script in the folder mysql/ within the .zip file
folders.
The classic installation schema in a regular wired LAN network is shown in the follow figure:

The Administrator/Installer tasks are hereby listed:
 Install the Java Runtime Environment 1.6 or higher
 Install the MySQL server on a computer that will act as the OH-Server
 Copy the OpenHospital application on every client (it may be copied on the server too)
 Configure each OpenHospital copy to point the OH-Server
For Java Runtime Environment installation refer to next chapter 3.1.1 Java Runtime Environment
and to online documentation.
For MySQL installation and DB creation refer to chapter 3.1.1 MySQL Server and OH DB and to
online documentation.
For OpenHospital installation on every client, as told, is enough to copy and extract the zip file.
For OpenHospital configuration refer to chapter 5 Configuration files.

3.1.1 Java Runtime Environment
Depending on the operating system you have, there are different ways to install a Java Virtual
Machine and the Java Runtime Environment.

Pag. 6

Rel. 1.8.0 (December 2014)

For instance on a Microsoft Windows® system you have to download and execute a setup file,
while in Linux based systems you have to type only one command in a terminal.
OpenHospital require a JRE 1.6 or higher to work properly. Anyway, at the time of reading this
document, many changes could have been made at the Java platform-depending installation, so we
invite you to refer to online documentation.

3.1.2 MySQL Server and OpenHospital DB
Depending on the operating system you have, there are several software to download to install and
manage a MySQL server. In any case it will be a normal installation of the software, with some
aspects to pay attention.
For instance on a Microsoft Windows® system you will have MySQL Workbench® as a client,
while in Linux based systems you may have MySQL Administrator and MySQL Query Browser to
perform the same tasks or still MySQL Workbench on new distros.
Anyway the best approach for installation is to use the command-line mysql client which come up
with essentially same commands and syntax for every platform.
3.1.2.1 MySQL Server installation
For the download and installation of a MySQL Server on your server machine we invite you to refer
to latest online documentation at the moment of reading this document.
Anyway, the main aspects the Administrator have to pay attention are:
 on a Linux machine: during the installation it will asked for a “root” password; very important
to choose it carefully and to keep it safely in an installation document. If the password is not
asked during installation an empty password will be automatically set for the root user.
 on a Windows machine: during the installation it will asked for several configuration options;
the best configuration will be (it could differs a bit):
o Custom Installation
o Install all components except Developer ones
o Select Detailed Configuration
o Select Server Machine
o Select Multifunctional Database
o Set a minimum of concurrent connection as the number of clients multiplied by two
o Select Enable TCP/IP Networking and write down the Port Number in an installation
document
o Select UTF8 as default charset for Best Support For Multilingualism
o Select Install As Window Service
o Select Include Bin Directory In Windows PATH
o Select Modify Security Settings, choose the root password and write it down in an
installation document
Once the installation has been completed we are ready for the OpenHospital DB creation. To check
if the server is active and running we can open a terminal window (command prompt) and type the
following command:
# mysql –u root -p
Enter password: ****

The terminal should reply with the MySQL client command line prompt:
Pag. 7

Rel. 1.8.0 (December 2014)

mysql>

that means that we successfully connected to MySQL Server just installed with the root user and it
is waiting for our commands.

3.1.2.1.1 Networking
On Linux systems, MySQL server must be configured to be enabled in networking; this can be
achieved by changing its config file “my.cnf” and commenting out this parameter:
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address
= 127.0.0.1

to
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
#bind-address
= 127.0.0.1

3.1.2.1.2 Performances
More performance in production environment can be achieved by changing following parameters
in MySQL config file “my.cnf”:
#
# Query Cache Configuration
#
query_cache_limit = 1M
query_cache_size = 16M

to
#
# Query Cache Configuration
#
query_cache_limit = 12M
query_cache_size = 256M

3.1.2.2 OpenHospital DB
In order to create the OpenHospital database everything we need is the set of SQL script files
contained in the OpenHospital zip file in the folder mysql/.
If we specified to Include Bin Directory In Windows PATH during the installation process (in
Linux is always true) we can run the MySQL client everywhere in our system.
Open a terminal in the folder mysql/db/ and run the following commands:
# mysql –u root -p
Enter password: ****

Pag. 8

Rel. 1.8.0 (December 2014)

The terminal should reply with the MySQL client command line prompt:
mysql>

We launch the main script “create_all.sql” with the command:
mysql> source create_all.sql

NB:Since version 1.8.0 you may install with different languages data sets by using the related
”create_all_xx.sql” file, or with demo data using the ”create_all_demo.sql” file (only English)
The server starts to process our scripts and after some instants it will be ready again for new
prompt. The DB has been created and we can check it with command:
mysql> show databases;
+--------------------+
| Database
|
+--------------------+
| information_schema |
| mysql
|
| oh
|
| performance_schema |
+--------------------+

The script has created the structure of the DB, populated with some default data and created the
“isf” user with password “isf123”.
The isf user is the one that OpenHospital will use to connect to the DB and its password can be
changed any time with the command:
mysql>SET PASSWORD FOR isf'@'%' = PASSWORD('new-password-here');
Query OK, 1 row affected (0.00 sec)
Rows matched: 1 Changed: 1 Warnings: 0

And then:
mysql>FLUSH PRIVILEGES;
Query OK, 0 rows affected (0.00 sec)

When we are through we exit the MySQL client command line with the command:
mysql>quit;

3.1.3 Configure OpenHospital
OpenHospital comes with several configuration files called “properties files”. The one we need to
modify in order to let OpenHospital to find its database is the database.propertiesand
log4j.propertiesfiles, located in the “resource” folder rsc/.
We have to specify:
 the IP address of the machine where the MySQL Server has been installed and containing the
OpenHospital database
 the “isf” user password, if changed from “isf123”
 the MySQL Server Port Number, if changed from “3306”
NB: These settings have to be put on every OpenHospital copy, it’s to say, on every client.
More informations in chapter 5.2 database.propertiesand5.3 log4j.properties.

Pag. 9

Rel. 1.8.0 (December 2014)

3.1.4 Run OpenHospital
We are ready now to run the OpenHospital software by executing the proper launcher:
 on a Linux machine: openhospital.sh
 on a Windows machine: openhospital.cmd
If everything is ok you should see the OpenHospital main splash screen:

And then the main Menu:

You may create a shortcut (link) to the executable script on the Desktop, the Programs Menu or
wherever you need by using the provided icon “oh.ico” that you find in the package.

3.2 Portable OpenHospital
OpenHospital, since version 1.2.0, has been distributed in a portable format.

Pag. 10

Rel. 1.8.0 (December 2014)

Since OpenHospital is a java software is portable by definition. With the term “portable” here we
refer to the possibility to have a copy self-contained of the software that includes JRE, MySQL
Server and the DB, that can so be copied and run everywhere carrying together all the inserted data.
Since JRE and MySQL are not platform-independent but comes with several version depending on
the platform, we have so:
 Portable OpenHospital for Linux platforms
 Portable OpenHosptial for Windows platforms
Once downloaded the needed version you may start it by launching the related script inside the
package:
 oh.shin the Linux version
 autorun.batin the Windows version
No others configurations are needed.
NB: if you want to use a Portable OpenHospital for Linux from a USB key you need to make sure
that the file permissions in the archive remain unchanged once extracted, otherwise you will not be
able to start the launcher or use the application in an appropriate manner.
NB: is important to understand that portable versions are meant to have a look to the software and
maybe use it in a very little facility (like a dispensary) with only one computer involved. If the
facility need a network architecture the full installation is the best solution.

Pag. 11

Rel. 1.8.0 (December 2014)

4 Folders
OpenHospital has an internal folder tree hereby briefly explained:
 bin – contains the Java binaries (compiled software)
 lib – contains the Java libraries needed to run the software
 rsc – contains the resources of OpenHospital, like configuration files and other stuff
 rsc/icons – contains the icons used in OpenHospital for windows and buttons
 rsc/images – contains the images used in OpenHospital
 rpt – contains the JasperReports® reports used in OpenHospital
 rpt/PDF – contains the reports generated by OpenHospital in PDF format
 bundle – contains the language files
 doc – contains documents like version changelogs and manuals
 log – contains the log files useful for debugging
 mysql – contains the scripts and configurations for MySQL DB
 scr – contains the OpenHospital source code
These folders are organized differently depending on the version.

Pag. 12

Rel. 1.8.0 (December 2014)

4.1 Foldertree in OpenHospital
In OpenHospital zip file you will find the following folder tree structure in the downloaded archive,
where  is replaced with the current OpenHospital version:


OpenHospital_/
 bin
 bundle
 doc
 lib
 mysql
 rpt
 rsc
 startup.cmd  Launcher for Windows
 startup.sh  Launcher for Linux
 SetupGSM.cmd  Utility for Windows
 SetupGSM.sh  Utility for Linux
 oh.ico

4.2 Foldertree in Portable OpenHospital for Linux
In Portable OpenHospital for Linux you will find the following folder tree structure in the
downloaded archive, where  is replaced with the current OpenHospital version:


poh-linux-0.0.2-core-/
 etc/
 jdk1.6.0_04/
 mysql-5.0.51a-linux-i686/
 oh-/
 bin
 bundle
 doc
 lib
 rpt
 rsc
 tmp/
 var/
 oh.sh Launcher for Linux
 SetupGSM.sh  Utility for Linux

Pag. 13

Rel. 1.8.0 (December 2014)

4.3 Foldertree in Portable OpenHospital for Windows
In Portable OpenHospital for Windows you will find the following folder tree structure in the
downloaded archive, where  is replaced with the current OpenHospital version:


poh-win32-0.0.4-core-/
 openhospital/
 jvm
 modified
 mysql
 oh
 bin
 bundle
 doc
 lib
 rpt
 rsc
 tmp
 english.bat
 french.bat
 german.bat
 swahili.bat
 italian.bat
 spanish.bat
 oh.ico
 SetupGSM.cmd  Utility for Windows
 autorun.bat  Launcher for Windows
 autorun.inf

Pag. 14

Rel. 1.8.0 (December 2014)

5 Configuration Files
Some behaviors of OpenHospital depend by settings set in some text files called “properties files”.
OpenHospital 1.8 comes with 6 main properties files:
 database.properties – for OpenHospital database connection
 generalData.properties – for OpenHospital configuration options
 log4j.properties – for the logging system
 txtPrinter– for the text printing system
 xmpp.properties – for the Xmpp Server
 dicom.properties – for the DICOM viewer module
 sms.properties – for SMS Manager module
Furthermore there are other configurations files that are not meant to be modified by the user:
 resolutions.xml – for store locally the informations about webcams
 version.properties – that contains the current OpenHospital version
Every configuration file works only locally and is meant to pilot only a single instance of
OpenHospital application.
This means that if we have many clients running OpenHospital they may run differently according
to their own configuration files.
NB: every change to these files need an application restart in order to see the modifications applied
In following chapters we will see all these properties files and all their feature in details.

Pag. 15

Rel. 1.8.0 (December 2014)

5.1 generalData.properties
OpenHospital 1.7 comes with the generalData.properties file set as follow by default:
# This file contains OpenHospital settings
LANGUAGE=en
SINGLEUSER=yes
AUTOMATICLOT=no
LOTWITHCOST=yes
PATIENTSHEET=patient_clinical_sheet_ver2
OPDCHART=patient_opd_chart
ADMCHART=patient_adm_chart
DISCHART=patient_dis_chart
PATIENTBILL=PatientBill
BILLSREPORT=BillsReport
BILLSREPORTMONTH=BillsReportMonth
PHARMACEUTICALORDER=PharmaceuticalOrder
PHARMACEUTICALSTOCK=PharmaceuticalStock
PATIENTEXTENDED=yes
OPDEXTENDED=yes
MATERNITYRESTARTINJUNE=no
LABEXTENDED=yes
LABMULTIPLEINSERT=yes
INTERNALPHARMACIES=yes
MERGEFUNCTION=yes
SMSENABLED=no
INTERNALVIEWER=yes
MAINMENUALWAYSONTOP=no
RECEIPTPRINTER=no
VIDEOMODULEENABLED=no
PATIENTVACCINEEXTENDED=yes
ENHANCEDSEARCH=no
XMPPMODULEENABLED=no
DICOMMODULEENABLED=yes
DEBUG=no

Every line is composed by key (capitalized) and a value (in blue) as follow:
key = value
Furthermore values can be:
o Boolean: yes | no or true | false
o String: usually a filename or a countrycode
In following chapters we will see the meaning of each of them.

Pag. 16

Rel. 1.8.0 (December 2014)

5.1.1 LANGUAGE
The following table shows the default value and the allowed ones:
key

default value

LANGUAGE en

allowed values
ar, en, it, fr, es, de, sw

OpenHospital 1.8 comes with seven translations, identified by the international country code:
o en – English
o it – Italian
o fr – French
o es – Spanish
o de–German
o sw– Swahili
o ar– Arabic
You can change the language used in the application simply by editing generalData.properties and
setting this key. If a not allowed value is set, the local computer language will be applied.
NB: An application restart is required in order to see the modification applied.

Pag. 17

Rel. 1.8.0 (December 2014)

5.1.2 SINGLEUSER
The following table shows the default value and the allowed ones:
key

default value allowed values

SINGLEUSER yes

yes, no

OpenHospital, since its first version, allow a multi-user usage. It means that is possible to define
different users, arrange them by group and set different rights in application usage; for instance, a
user “receptionist” may be able to register a new patient but not to prescribe a therapy.
OpenHospital has a predefined user called “admin” that have all rights to access all functionality in
the application. When SINGLEUSER is set to YES (default) the program start with this user and all the
functionalities are available.
If SINGLEUSERis set to NO the following login window will appear when start the program:

The default password for “admin” user is “admin”. By typing his password in the white field and by
pressing Submit, you will see the main Menu with all functionalities enabled.
Once you’re logged in as “admin” user you can define users and group (see Users and Groups
(Users)), or just stay with only that as a simple form of data protection.
NB: despite this setting works only locally the users and groups defined will work for every client
connected to the server; anyway is possible to avoid login simply by acting on this parameter.
Disclaimer: data security must never be left solely to application but it must be ensured by a proper
network architecture and by a rigid configuration of the clients.

Pag. 18

Rel. 1.8.0 (December 2014)

5.1.3 AUTOMATICLOT
The following table shows the default value and the allowed ones:
key

default value allowed values

AUTOMATICLOT no

yes, no

OpenHospital, since its first version, allow an automatic management of lots in the main pharmacy.
It means that is possible to work in the pharmacy without taking care about lot definitions in
loading the store and just specify preparation and expiring date for each charging movement (see
6.2.2.2Insert stock movement in the User’s Guide).
For discharging movement, the lot is automatically calculated according to the nearest expiring date
of lots. If the quantity to discharge is higher than the quantity of the first selected lot, more than one
discharging operation can be generated.
By default AUTOMATICLOT is set to NO. Anyway is possible to set it anytime to YES to enable it.
NB: An application restart is required in order to see the modification applied.

Pag. 19

Rel. 1.8.0 (December 2014)

5.1.4 LOTWITHCOST
The following table shows the default value and the allowed ones:
key

default value allowed values

LOTWITHCOST yes

yes, no

OpenHospital, since version 1.8, allows managing the cost of medicals in the main pharmacy. (see
6.2.2.2 Insert stock charging movement in the User’s Guide).
NB: An application restart is required in order to see the modification applied.

Pag. 20

Rel. 1.8.0 (December 2014)

5.1.5 PATIENTSHEET
The following table shows the default value and the allowed ones:
key

default value

allowed values

PATIENTSHEET patient_clinical_sheet any kind of .jasper file name
OpenHospital, since its first version, allows to produce a report about the clinical history of a
patient (see 10.9 Clinical Sheet in the User’s Guide).
By default PATIENTSHEET is set to patient_clinical_sheetthat is the filename of the related
report to use for the Clinical Sheet functionality. Anyway is possible to use a different report by
installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 21

Rel. 1.8.0 (December 2014)

5.1.6 OPDCHART
The following table shows the default value and the allowed ones:
key

default value

allowed values

OPDCHART patient_opd_chart any kind of .jasper file name
OpenHospital, since its version 1.8, allows to produce a report about the OPD chart of a patient (see
10.9 Clinical Sheet in the User’s Guide).
By default OPDCHART is set to patient_opd_chart that is the filename of the related report to use
for the Clinical Sheet functionality OPD Chart. Anyway is possible to use a different report by
installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 22

Rel. 1.8.0 (December 2014)

5.1.7 ADMCHART
The following table shows the default value and the allowed ones:
key

default value

allowed values

ADMCHART patient_adm_chart any kind of .jasper file name
OpenHospital, since its version 1.8, allows to produce a report about the Admission of a patient (see
10.9 Clinical Sheet in the User’s Guide).
By default ADMCHART is set to patient_adm_chart that is the filename of the related report to
use for the Clinical Sheet functionality Admission Chart. Anyway is possible to use a different
report by installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 23

Rel. 1.8.0 (December 2014)

5.1.8 DISCHART
The following table shows the default value and the allowed ones:
key

default value

allowed values

DISCHART patient_dis_chart any kind of .jasper file name
OpenHospital, since its version 1.8, allows to produce a report about the Discharge of a patient (see
10.9 Clinical Sheet in the User’s Guide).
By default DISCHART is set to patient_dis_chart that is the filename of the related report to use
for the Clinical Sheet functionality Discharge Chart. Anyway is possible to use a different report
by installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 24

Rel. 1.8.0 (December 2014)

5.1.9 PATIENTBILL
The following table shows the default value and the allowed ones:
key

default value

allowed values

PATIENTBILL PatientBill any kind of .jasper file name
OpenHospital, since version 1.6.0, allows to manage patient bills and to produce an A4 format
breakdown with his/her items and payments (see 8.2 Functions of Accounting in the User’s Guide)
By default PATIENTBILL is set to PatientBill that is the filename of the related report to use for the
bill printing functionality. Anyway is possible to use a different report by installing it in the report
folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 25

Rel. 1.8.0 (December 2014)

5.1.10 BILLSREPORT
The following table shows the default value and the allowed ones:
key

default value

allowed values

BILLSREPORT BillsReport any kind of .jasper file name
OpenHospital, since version 1.6.0, allows to manage patient bills and to produce a report about all
bills paid (or not paid) within a span of time (see 8.2 Functions of Accounting in the User’s Guide)
By default BILLSREPORT is set to BillsReport that is the filename of the related report to use for
the account printing functionality. Anyway is possible to use a different report by installing it in the
report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 26

Rel. 1.8.0 (December 2014)

5.1.11 BILLSREPORTMONTH
The following table shows the default value and the allowed ones:
key

default value

allowed values

BILLSREPORTMONTH BillsReportMonth any kind of .jasper file name
OpenHospital, since version 1.6.0, allows to manage patient bills and to produce a report about all
bills paid (or not paid) monthly (see8.2 Functions of Accounting in the User’s Guide).
By default BILLSREPORTMONTHis set to BillsReportMonththat is the filename of the related
report to use for the account printing functionality. Anyway is possible to use a different report by
installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 27

Rel. 1.8.0 (December 2014)

5.1.12 PHARMACEUTICALORDER
The following table shows the default value and the allowed ones:
key

default value

allowed values

PHARMACEUTICALORDER PharmaceuticalOrder any kind of .jasper file name
OpenHospital, since version 1.7.0, allows to produce a report for the Pharmacy Stock critical levels,
that help to know which pharmaceuticals are going to end and which ones need to be ordered (see
6.1 Pharmaceuticals in the User’s Guide).
By default PHARMACEUTICALORDER is set to PharmaceuticalOrder that is the filename of the
related report to use for the pharmacy printing functionality. Anyway is possible to use a different
report by installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 28

Rel. 1.8.0 (December 2014)

5.1.13 PHARMACEUTICALSTOCK
The following table shows the default value and the allowed ones:
key

default value

allowed values

PHARMACEUTICALSTOCK PharmaceuticalStock any kind of .jasper file name
OpenHospital, since version 1.7.0, allows to produce a report for the Pharmacy Stock Status, that
help to know which pharmaceuticals are currently stored (see 6.1 Pharmaceuticals in the User’s
Guide).
By default PHARMACEUTICALSTOCK is set to PharmaceuticalStock that is the filename of the
related report to use for the pharmacy printing functionality. Anyway is possible to use a different
report by installing it in the report folder (see Reports) and by changing this parameter.
NB: An application restart is required in order to see the modification applied.

Pag. 29

Rel. 1.8.0 (December 2014)

5.1.14 PATIENTEXTENDED
The following table shows the default value and the allowed ones:
key

default value allowed values

PATIENTEXTENDED yes

yes, no

OpenHospital, since version 1.3.1, allows register patient with a big set of information. This set of
information are meant to “extend” the ones collected since version 1.2.1 (see 10.4Insert a new
Patient Extendedin the User’s Guide).
By default PATIENTEXTENDED is set to yes. Anyway is possible to set it to no in order to reduce the
amount of data to be collected and so reduce the workload for the staff involved in data entry.
NB: An application restart is required in order to see the modification applied.

Pag. 30

Rel. 1.8.0 (December 2014)

5.1.15 OPDEXTENDED
The following table shows the default value and the allowed ones:
key

default value allowed values

OPDEXTENDED yes

yes, no

OpenHospital, since version 1.3.1, allows to link every OPD visit to a registered patient in order to
have a comprehensive clinical history. For each visit the user will be asked to select a registered
patient or to register a new one, so from that moment the visit will be attached to his/her history
(see 5.3 OPD Extended and 10.9 Clinical Sheetin the User’s Guide).
By default OPDEXTENDEDis set to yes. Anyway is possible to set it to no in order to reduce the
amount of data to be collected (only age and sex, no patient registration) and so reduce the
workload for the staff involved in data entry.
NB: An application restart is required in order to see the modification applied.

Pag. 31

Rel. 1.8.0 (December 2014)

5.1.16 MATERNITYRESTARTINJUNE
The following table shows the default value and the allowed ones:
key

default value allowed values

MATERNITYRESTARTINJUNE no

yes, no

OpenHospital, since version 1.3.1, allows to change the way the admissions in Maternity ward are
counted within the year; in OpenHospital the first admission of the year for every ward has
progressive number 1 (one) and it increments itself automatically up to the end of the year; in some
facilities this is partially true and the progressive numbering starts from June only for the Maternity
ward. With this option we obtain exactly this behavior.
By default MATERNITYRESTARTINJUNEis set to no.
NB: An application restart is required in order to see the modification applied.

Pag. 32

Rel. 1.8.0 (December 2014)

5.1.17 LABEXTENDED
The following table shows the default value and the allowed ones:
key

default value allowed values

LABEXTENDED yes

yes, no

OpenHospital, since version 1.4.1, allows to force every laboratory exam to be linked to a registered
patient, in order to have a comprehensive clinical history. For each exam the user will be asked to
select a registered patient so from that moment the exam will be attached to his/her history (see
7.3.2 New Laboratory Exam in the User’s Guide).
By default LABEXTENDED is set to yes.Anyway is possible to set it to no in order to reduce the
amount of data to be collected (only name, age and sex, no patient registration) and so reduce the
workload for the staff involved in data entry.
NB: An application restart is required in order to see the modification applied.

Pag. 33

Rel. 1.8.0 (December 2014)

5.1.18 LABMULTIPLEINSERT
The following table shows the default value and the allowed ones:
key

default value allowed values

LABMULTIPLEINSERT yes

yes, no

OpenHospital, since version 1.4.1, allows to insert multiple laboratory tests per patient at a time in
order to avoid the repetitive operation of selecting a patient or writing his/her name; the
LABEXTENDED option must be set to yes too(see 7.3.3 Laboratory Multiple Insert in the User’s
Guide).
By default LABMULTIPLEINSERT is set to yes, but if LABEXTENDED is set to no it will be just
ignored.
NB: An application restart is required in order to see the modification applied.

Pag. 34

Rel. 1.8.0 (December 2014)

5.1.19 INTERNALPHARMACIES
The following table shows the default value and the allowed ones:
key

default value allowed values

INTERNALPHARMACIES yes

yes, no

OpenHospital, since version 1.4.1, allows to register all giving to patients within a ward. Activating
this option the Pharmaceutical Stock Ward functionality will be available in the application (see 6.3
Pharmaceuticals Stock Ward in the User’s Guide)
By default INTERNALPHARMACIES is set to yes.
NB: An application restart is required in order to see the modification applied.

Pag. 35

Rel. 1.8.0 (December 2014)

5.1.20 MERGEFUNCTION
The following table shows the default value and the allowed ones:
key

default value allowed values

MERGEFUNCTION no

yes, no

OpenHospital, since version 1.4.1, allows to merge two patients history in only one. This is
particularly useful in case of double registration that have collected different informations during
the time. Activating this option the Merge functionality will be available in the Admission/Patient
module (see 10.11 Merge function in the User’s Guide).
By default MERGEFUNCTIONis set to no.
NB: An application restart is required in order to see the modification applied.

Pag. 36

Rel. 1.8.0 (December 2014)

5.1.21 INTERNALVIEWER
The following table shows the default value and the allowed ones:
key

default value

INTERNALVIEWER yes

allowed values
yes,

any executable filename in the path or with absolute path

OpenHospital, since version 1.4.1, allows to use a different PDF reader for generated reports. If this
parameter is set to yes, the Jasper PDF Viewer will be used (see 11.2 Report Launcher in the
User’s Guide). If we want to use an external PDF viewer we may put its executable filename but we
must be sure that it is available in the desktop environment.
Example in Windows:
INTERNALVIEWER=AcroRd32.exe
INTERNALVIEWER= C:\\Program Files (x86)\\Adobe\\Reader 10.0\\Reader\\AcroRd32.exe

NB: Please note the double file & folder separator “\\”.
Example in Linux:
INTERNALVIEWER=evince

By default INTERNALVIEWER is set to yes.
NB: An application restart is required in order to see the modification applied.

Pag. 37

Rel. 1.8.0 (December 2014)

5.1.22 SMSENABLED
The following table shows the default value and the allowed ones:
key

default value allowed values

SMSENABLED no

yes, no

OpenHospital, since version 1.5, allows to set this parameter that will be used to set some
information ready for SMS notification to the patients. Enabling or disabling this option will only
affect the possibility to set or not a therapy as notifiable (see 10.10.7 Notify & SMS in the User’s
Guide)
By default SMSENABLED is set to no.
5.1.22.1 Configuration
In order to setup a GSM device, you must set as GSM mode in the related sms.properties file (see
sms.properties) and then set up the related GSM.properties file (see GSM.properties).
The settings in the GSM.properties file should work with the majority of GSM devices (like phones,
smartphones, usb modems, etc…) and only the PORT parameter should be changed accordingly
with the SERIAL port used by your system to address the device once plugged in the system.
If you’re sure the PORT is correct but still OpenHospital is not communicating with the device (we
suggest to switch to DEBUG log level – or lower - during this setup – see log4j.properties) you
might use the SetupGSM utility in your OpenHospital root folder (see Folders)
5.1.22.2 SetupGSM
In order to use the SetupGSM utility just follow these instructions:
1. plug your device in your system and be sure the system recognize it, load a proper driver for
it and assign a serial port (COM)
2. Launch the utility: the utility will scan all plugged devices and will try to recognize the
modem (or phone) within them
3. If the device is recognized as modem you will be prompted for a confirm message as the
follow

4. If the name of the device is the one meant to be used with the system then just click “yes”,
otherwise click “no” and the scan will continue
5. Once you click “yes” the GSM.properties file will be automatically modified by the utility

Pag. 38

Rel. 1.8.0 (December 2014)

5.1.23 MAINMENUALWAYSONTOP
The following table shows the default value and the allowed ones:
key

default value allowed values

MAINMENUALWAYSONTOP no

yes, no

OpenHospital, since version 1.5, allows to keep the main menu always on top so it cannot be
overlapped by other windows.
By default MAINMENUALWAYSONTOPis set to no.
NB: An application restart is required in order to see the modification applied.

Pag. 39

Rel. 1.8.0 (December 2014)

5.1.24 RECEIPTPRINTER
The following table shows the default value and the allowed ones:
key

default value allowed values

RECEIPTPRINTER no

yes, no

OpenHospital, since version 1.5, allows to drive text or ZPL printers with aim of printing simple
receipts in Accounting module (see 8.2.1.10 Print receipt function in User’s Guide). Once this
option has been activated, some parameters have to be set in txtPrinterproperty file in order to
adjust the output with the printer connected to the system (see txtPrinter.properties in this
document).
By default RECEIPTPRINTER is set to no.
NB: The text printer must be set as default printer.
NB: An application restart is required in order to see the modification applied.

Pag. 40

Rel. 1.8.0 (December 2014)

5.1.25 VIDEOMODULEENABLED
The following table shows the default value and the allowed ones:
key

default value allowed values

VIDEOMODULEENABLED no

yes, no

OpenHospital, since version 1.5, allows to drive any webcam with the aim of shooting patients
passports in Admission/Patient module (see 10.4.3 Patient Photo function in User’s Guide). Once
this option has been activated the related button New Photo in New Patient Extended window will
be available to start and use the webcam.
By default VIDEOMODULEENABLED is set to no.
NB: An application restart is required in order to see the modification applied.

Pag. 41

Rel. 1.8.0 (December 2014)

5.1.26 PATIENTVACCINEEXTENDED
The following table shows the default value and the allowed ones:
key

default value allowed values

PATIENTVACCINEEXTENDED yes

yes, no

OpenHospital, since version 1.6, allows to register vaccines given to patients (see 9 Vaccines in the
User’s Guide). This option allow to toggle the patient’s fullname in the Patient vaccines browsing
window.
By default PATIENTVACCINEEXTENDEDis set to yes.
NB: An application restart is required in order to see the modification applied.

Pag. 42

Rel. 1.8.0 (December 2014)

5.1.27 ENHANCEDSEARCH
The following table shows the default value and the allowed ones:
key

default value allowed values

ENHANCEDSEARCH no

yes, no

OpenHospital, since version 1.6, allows to optimize memory usage when the number of registered
patients becomes huge (see 10.2.2 Search patient Enhanced in the User’s Guide). With the
enhanced search only the patient matching a search criteria will be loaded in the memory, otherwise
all patients registered in the system will be loaded in the Patients browser window.
By default ENHANCEDSEARCHis set to no. Anyway is possible to toggle this option anytime to
reduce the amount of memory needed by the computer or the server.
NB: An application restart is required in order to see the modification applied.

Pag. 43

Rel. 1.8.0 (December 2014)

5.1.28 XMPPMODULEENABLED
The following table shows the default value and the allowed ones:
key

default value allowed values

XMPPMODULEENABLED no

yes, no

OpenHospital, since version 1.7, embeds a new technology that allow user’s logged in the
application to chat and share informations related to the hospital activities (see 13 Communication
in the User’s Guide); the SINGLEUSER option must be set to no too. If this option is active,
OpenHospital will look for an XMPP Server at startup time. The xmpp.properties will be used to
point the server that must be installed on the computer or on the OH Server by the System
Administrator (see xmpp.properties in this document).
By default XMPPMODULEENABLED is set to no, but if SINGLEUSER is set to yes it will be just
ignored.
NB: An application restart is required in order to see the modification applied.

Pag. 44

Rel. 1.8.0 (December 2014)

5.1.29 DICOMMODULEENABLED
The following table shows the default value and the allowed ones:
key

default value allowed values

5.1.30 DICOMMODULEENABLED

no

yes, no

OpenHospital, since version 1.8, embeds a new feature that allows to attach DICOM files to
patient’s clinical sheet. When this option is enabled, a button DICOM appears in the patient
Clinical sheet module.
By default DICOMMODULEENABLED is set to no.
NB: An application restart is required in order to see the modification applied.

Pag. 45

Rel. 1.8.0 (December 2014)

5.1.31 DEBUG
The following table shows the default value and the allowed ones:
key

default value allowed values

DEBUG no

yes, no

OpenHospital, since version 1.7, allows to run itself in debug mode that could be useful to
understand what is happening behind the user graphical interface. At the moment this option will
affect only the video module, that means that in place of the normal New Patient Extended
window (see 10.4.3 Patient Photo function in User’s Guide), it will open the new special window
showed below:

From this window is possible to have more information about webcams connected to the system
and try different resolutions in order to find the best one or more information about a problem.
Once produced a photo, OpenHospital will remember the last setting used in the future.
By default DEBUGis set to no.
NB: An application restart is required in order to see the modification applied.

Pag. 46

Rel. 1.8.0 (December 2014)

5.2 database.properties
OpenHospital 1.7 and above comes with the database.properties file set as follow by default:
# This file contains MySQL Server informations
jdbc.drivers=com.mysql.jdbc.Driver
jdbc.url=jdbc:mysql:
jdbc.server=localhost
jdbc.db=oh
jdbc.username=isf
jdbc.password=isf123
# jdbc.port=3306

First two parameters are not meant to be modified by the User, neither by the Administrator:
 jdbc.drivers: the java library used to connect to a MySQL Server
 jdbc.url: the address to point a MySQL Server
Then we have five parameters which may need to be set according to your network settings instead:
 jdbc.server: the IP address of the server where the MySQL Server is installed; localhost means
the same computer where this file is located; others values can be:
127.0.0.1 – loopback network
192.168.0.100 – an example of private IP address (LAN)
217.147.110.117 – an example of public IP address (WAN)





jdbc.db: the name of the OpenHospital database
jdbc.username: the MySQL user allowed to connect and operate on the database
jdbc.password: the user password
jdbc.port: the TCP port where the MySQL Server is listening; by default this port is 3306 but
can be changed if needed; anyway must reflect the MySQL Server settings

The full address for the db will then result as:
jdbc:mysql://localhost/oh

NB: An application restart is required in order to see the modification applied.

Pag. 47

Rel. 1.8.0 (December 2014)

5.3 dicom.properties
OpenHospital 1.8 comes with the dicom.properties file set as follow by default:
#dicom.manager.impl=org.isf.dicom.manager.FileSystemDicomManager
#dicom.manager.impl=org.isf.dicom.manager.HybernateDicomManager
dicom.manager.impl=org.isf.dicom.manager.HybernateDicomManager
dicom.storage.filesystem=E\:\\ISF\\DICOM\\OH_storage





for filesystem
for database

dicom.manager.impl: the java class that implement org.isf.dicom.manager.DicomManagerIntf
and that will manage the DICOM persistence operation. This property can take two values
org.isf.dicom.HybernateDicomManager : The dicom File is stored in the database
org.isf.dicom.FileSystemDicomManager : The dicom file is stored in the file system
dicom.storage.filesystem: is the value of the first parameter is
org.isf.dicom.FileSystemDicomManager, this property tell OpenHospital about the path where
the DICOM files will be stored.

Pag. 48

Rel. 1.8.0 (December 2014)

5.4 examination.properties
OpenHospital 1.8 comes with the examination.properties file used in the examination module. The
file is set as follow by default:
# This file contains PatientExamination module settings
LIST_SIZE = 10
HEIGHT_UNIT = cm
HEIGHT_MIN = 0
HEIGHT_MAX = 250
HEIGHT_INIT = 0
WEIGHT_UNIT = Kg
WEIGHT_MIN = 0
WEIGHT_MAX = 200
WEIGHT_INIT = 0
WEIGHT_STEP = 0.1
AP_UNIT = mmHg
AP_MIN = 80
AP_MAX = 120
HR_UNIT = bpm
HR_MIN = 0
HR_MAX = 240
HR_INIT = 60
TEMP_UNIT = °C
TEMP_INIT = 0
TEMP_MIN = 0
TEMP_MAX = 50
TEMP_STEP = 0.1
SAT_INIT = 90
SAT_MIN = 50
SAT_MAX = 100
SAT_STEP = 0.1




















LIST_SIZE: the maximum number of examination that can be view in the history. Must be less
than or equal to 10.
HEIGHT_UNIT: the Height unit
HEIGHT_MIN: the height minimum value, use to initialize the height slider in the
Examination window.
HEIGHT_MAX: the height maximum value, use to initialize the height slider in the
Examination window.
HEIGHT_INIT: the height initial value.
WEIGHT_UNIT: the Weight unit
WEIGHT _MIN: the Weight minimum value, use to initialize the Weight slider in the
Examination window.
WEIGHT _MAX: the Weight maximum value, use to initialize the Weight slider in the
Examination window.
WEIGHT _INIT: the Weight initial value.
WEIGHT _STEP: the step used when moving the weight slider
AP_UNIT: the Arterial pressure unit
AP _MIN: the Arterial pressure minimum value
AP _MAX: the Arterial pressure maximum value
HR_UNIT: the Heart rate unit
HR _MIN: the Heart rate minimum value
HR _MAX: the Heart rate maximum value
HR _INIT: the Heart rate initial value
TEMP_UNIT: the temperature unit
Pag. 49

Rel. 1.8.0 (December 2014)










TEMP _INIT: the temperature initial value
TEMP _MIN: the temperature minimum value
TEMP _MAX: the temperature maximum value
TEMP _STEP: the temperature step used when moving the slider
SAT _INIT: the saturation initial value
SAT _MIN: the saturation minimum value
SAT _MAX: the saturation maximum value
SAT _STEP: the saturation step used when moving the slider

Pag. 50

Rel. 1.8.0 (December 2014)

5.5 log4j.properties
OpenHospital 1.7 and above comes with the log4j.properties file set as follow by default:
# logging di default su file, livello FINEST (debug++)
log4j.rootCategory=FINEST
#log4j.rootLogger=R
# StdOut Appender (with classes) (not used)
log4j.appender.StdOut = org.apache.log4j.ConsoleAppender
log4j.appender.StdOut.layout=org.apache.log4j.PatternLayout
log4j.appender.StdOut.layout.ConversionPattern=[%d{dd/MMM/yyyy HH:mm:ss}]
[%X{OHUserGroup}:%X{OHUser}] %-p - %m%n
# File Appender (with classes), daily rotation
log4j.appender.RollingFile = org.apache.log4j.DailyRollingFileAppender
log4j.appender.RollingFile.DatePattern='.'yyyy-MM-dd
log4j.appender.RollingFile.File=logs/openhospital.log
log4j.appender.RollingFile.layout=org.apache.log4j.PatternLayout
log4j.appender.RollingFile.layout.ConversionPattern=[%d{dd/MMM/yyyy HH:mm:ss}]
[%X{OHUserGroup}:%X{OHUser}] %-p - %m (%l)%n
# DB Appender (table columns)
log4j.appender.DB=org.apache.log4j.jdbc.JDBCAppender
log4j.appender.DB.URL=jdbc:mysql://localhost:3306/oh?autoReconnect=true
log4j.appender.DB.user=isf
log4j.appender.DB.password=isf123
log4j.appender.DB.sql=INSERT INTO LOG (LOG_TYPE, LOG_CLASS, LOG_METHOD,
LOG_TIME, LOG_MESS, LOG_USER) VALUES (1, '%C', '%M', '%d{yyyy-MM-dd HH:mm:ss}',
LEFT('%m', 1024), '%X{OHUser}')
log4j.appender.DB.layout=org.apache.log4j.PatternLayout
# Assigning appenders to packages
log4j.category.org.isf=DEBUG,RollingFile,DB
log4j.additivity.org.isf = false

This file is not meant to be modified by the User.
Once the system is up and running, the log levelcan be reduced from "DEBUG" to "INFO", so the
size of the log files and the tables are significantly reduced:
log4j.category.org.isf=INFO,RollingFile,DB

On the contrary, in case of malfunctions of the application, the log level can be increased to
"TRACE", in this way will be shown more details on the operation of the application:
log4j.category.org.isf=TRACE,RollingFile,DB

You can even disable the log file or the log DB, by deleting the respective appender if not needed:
log4j.category.org.isf=INFO,DB

or
log4j.category.org.isf=INFO,RollingFile

Pag. 51

Rel. 1.8.0 (December 2014)

You can also decide to log only in the standard output (the console window) with:
log4j.category.org.isf=INFO,StdOut

The DB appender configuration must be set properly, according with database.properties (see 5.2
database.properties), by editing the following lines (in red the most important parameters):
# DB Appender (table columns)
log4j.appender.DB=org.apache.log4j.jdbc.JDBCAppender
log4j.appender.DB.URL=jdbc:mysql://localhost:3306/oh?autoReconnect=true
log4j.appender.DB.user=isf
log4j.appender.DB.password=isf123

NB: An application restart is required in order to see the modification applied.

Pag. 52

Rel. 1.8.0 (December 2014)

5.6 sms.properties
OpenHospital 1.8 comes with the sms.properties file set as follow by default:
# Configuration file for SMS Sender
# MODE = GSM (COM PORT) or HTTP (PROVIDER)
# GATEWAY = Skebby or empty
# TIMEOUT = Timeout for the HTTP request
# LOOP = loop time in seconds
# ICC = International Calling Code
MODE = GSM
GATEWAY = Skebby
TIMEOUT = 3000
LOOP = 15
ICC = +39








MODE: the SMS sender mode. Can take two values:
o GSM: need a GSM modem connected to a COM port. The administrator should
configure the SMSGateway/GSM.properties file to set the suitable PORT
o HTTP: need a HTTP API provider. .
GATEWAY: HTTP gateway to use. Required when the MODE is set to GSM.
TIMEOUT: timeout for the HTTP request. Required when MODE is set to HTTP.
LOOP: Delay used by the sender to fetch new SMS operations to proceed. The value is in
second.
ICC: the International Country Code that nedd to be added to the phone numbers that require
it..

5.6.1 GSM.properties
OpenHospital 1.8 comes with the GSM.properties file set as follow by default:
# Configuration file for SMS Sender GSM
# PORT = COMx (Windows) or /dev/ttyUSBx (Linux)
#Mon Dec 01 02:38:30 CET 2014
CMGS=AT+CMGS\="
GMM=AT+GMM\r\n
CMGF=AT+CMGF\=1\r
CSMP=AT+CSMP\=17,167,0,0\r
PORT=COM20
DRIVERNAME=com.sun.comm.Win32Driver

Only the PORT property needs to be modified.
 PORT: COM port where the modem is connected.

Pag. 53

Rel. 1.8.0 (December 2014)

5.6.2 Skebby.properties
OpenHospital 1.8 comes with the Skebby.properties file set as follow by default:
# Configuration file for Skebby Provider
URL = http://gateway.skebby.it/api/send/smseasy/advanced/http.php
USR =
PWD =
TYPE = send_sms_classic
SENDER_NUMBER =
SENDER_STRING =

This serve for the implementation of the Skebby HTTP Api for sending SMS.








URL: Url of the Skebby http api.
USR: the username need for the authentification on the skebby server
PWD: password for the authentification on the skebby server
TYPE: SMS type, require by skebby. You can just leave the default value.
SENDER_NUMBER: Sender number.
SENDER_STRING: Sender string, that will replace the sender number in the phone of the
recipient.

Pag. 54

Rel. 1.8.0 (December 2014)

5.7 txtPrinter.properties
OpenHospital 1.7 and above comes with the txtPrinter.properties file set as follow by default:
# This file contains text printing informations
PRINT_AS_PAID=yes
PRINT_WITHOUT_ASK=no
PAGE_HEIGHT=50
PAGE_WIDTH=47
ZPL=yes
ZPL_FONT_TYPE=0
ZPL_ROW_HEIGHT=25

This file will be used only if the RECEIPTPRINTER flag is enabled (see 5.1.20 RECEIPTPRINTER in
this document)
This file has seven parameters, hereby explained:
 PRINT_AS_PAID: it will affect the behavior when a Bill is set to PAID in the Accounting
module (see 8.2.1.10 Print receipt function in User’s Guide).
If it is set to yesOpenHospital will try to print a receipt for the Bill in text format in a page
of size PAGE_HEIGHT and PAGE_WIDTH.
A confirmation window will appear:

Otherwise you must do it after, by press Edit Bill button on the already closed (“C”) bill





PRINT_WITHOUT_ASK: if set to yesOpenHospital will try to print the receipt without
confirmation window
ZPL:if set to yes we are specifying that the text printer connected to the system works with
ZPL language (an EPL evolution for Zebra Label Printer)
ZPL_FONT_TYPE: a 0 (zero) value stands for standard character; you may change this value
with “A”, “B”, “C”, etc... according with the device datasheet, in order to obtain a better
look
ZPL_FONT_SIZE: an integer value to adjust the character size in order to obtain a better look

The best way to set these parameters according with your device is to set them one by one and
check the different results until you reach the best fit.
NB: An application restart is required in order to see the modification applied.

Pag. 55

Rel. 1.8.0 (December 2014)

5.8 xmpp.properties
OpenHospital 1.7 and above comes with the xmpp.properties file set as follow by default:
# This file contains Xmpp Server informations
DOMAIN=127.0.0.1
PORT=5222

This file will be used only if the XMPPMODULEENABLED flag is enabled (see 5.1.24
XMPPMODULEENABLED in this document)
In order to use the Communication module (see 13 Communication in the User’s Guide) you must
install an XMPP Server separately on the OH Server, let’s say side by side with MySQL Server.
The most common XMPP Server is the free and open-source project Ignite Openfire®
(http://www.igniterealtime.org/projects/openfire/) available for Linux, Windows and Mac.
Once the XMPP Server is installed, active and running we may set the two parameters in the
xmpp.properties file as follow:
 DOMAIN – the IP address of the XMPP server (it could be the same of MySQL Server)
 PORT – 5222 or another if set differently
NB: An application restart is required in order to see the modification applied.

Pag. 56

Rel. 1.8.0 (December 2014)

5.9 Bundles
Bundles are the language (or translation) files provided with OpenHospital. As told in 5.1.1
LANGUAGE chapter, OpenHospital 1.7 comes with different available languages in folder
bundles/ within the package file:
language_XY.properties
where XY is an international country code.
Since they are property files, every language file is made by hundreds of key = value couple too.
Special characters are coded in the UNICODE coding system with 4 bytes, like:
U+00E1 = \u00E1 = á
U+00E8 = \u00E8 = è
U+00F6 = \u00F6 = ö
…

5.9.1 New Translations
In order to create a new translation or to fix some labels in the OpenHospital is enough to create a
copy of the English one, rename it with the new country code in place of the “XY” in the filename,
and start translating with a simple text editor.
For instance, if you want to create an Arab translation, you may create a new bundle from the
English one:
language_en.propertieslanguage_ar.properties
Then you can edit the Arab file and set the LANGUAGE parameter to ar to start testing your
translation.

Pag. 57

Rel. 1.8.0 (December 2014)

6 Reports
Reports in OpenHospital are produced with JasperReports® technology that allow to design a
report in a WYSIWYG (What You See Is What You Get) way, connect it to a datasource (DB), test
it, modify it and then compile it to use it in the application software.
OpenHospital reports are all contained in reports rpt/ folder (see Folders in this document). Each
report consists of two files:
a .jrxml file: JasperReport XML file, that can be modified with a proper editor
a .jasper file: Jasper file, that is the compiled version that can be run in OpenHospital; this file is
produced on the jrxml base
The Jasper editor to create and modify Jasper reports is iReport®, a free and open-source software.
With iReport® is possible to edit OpenHospital reports and re-compile them in order to be used in
OpenHospital application.

6.1 Compatibility: iReport® 3.0.0
In order to have compliant and fully-working reports for OpenHospital we suggest to use iReport®
version 3.0.0.

6.2 Links
JasperReports® - http://www.jaspersoft.com/
iReport® - http://community.jaspersoft.com/project/ireport-designer
iReport® 3.0.0 - http://sourceforge.net/projects/ireport/files/iReport%20(classic)/

Pag. 58



---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : No
Page Count                      : 58
Language                        : it-IT
Tagged PDF                      : Yes
Title                           : Title
Author                          : bob
Creator                         : Microsoft® Word 2010
Create Date                     : 2015:01:23 09:31:31+01:00
Modify Date                     : 2015:01:23 09:31:31+01:00
Producer                        : Microsoft® Word 2010

EXIF Metadata provided by EXIF.tools