EN

technical manual
The manufacturer, assembler and importer are responsible for the safety, reliability and
performance of the unit only if:
- installation, calibration, modification and repairs are carried out by qualified
authorised personnel
- electrical installations are carried out according to the appropriate requirements such
as IEC 60364
- equipment is used according to the operating instructions.
Planmeca pursues a policy of continual product development. Although every effort
is made to produce up-to-date product documentation this publication should not be
regarded as an infallible guide to current specifications. We reserve the right to make
changes without prior notice.
COPYRIGHT PLANMECA
Publication number 30024964 Revision 13
Released 19 September 2023
Table of contents

1 Introduction................................................................................................................................................. 1
1.1 Associated documentation............................................................................................................... 1
1.2 Indications for use............................................................................................................................ 2
1.2.1 Reporting serious incidents..............................................................................................3
2 System requirements..................................................................................................................................4
3 Data backup and life cycle management....................................................................................................7
3.1 Data decommissioning..................................................................................................................... 8
4 Security hardening......................................................................................................................................9
5 Installing Romexis on Windows................................................................................................................ 12
5.1 Romexis software components...................................................................................................... 12
5.2 Requirements (Windows)............................................................................................................... 14
5.2.1 System requirements..................................................................................................... 14
5.2.2 Network requirements.................................................................................................... 14
5.2.3 Requirements for user account...................................................................................... 14
5.3 Installing Romexis on Windows......................................................................................................14
5.4 Installing Romexis license on Windows..........................................................................................20
5.4.1 Installing license in Romexis client.................................................................................21
5.4.2 Installing license in Romexis server only installation..................................................... 21
5.5 Activating Romexis license.............................................................................................................23
5.5.1 Manual activation........................................................................................................... 25
5.5.2 Installing license.............................................................................................................25
5.5.3 Updating license.............................................................................................................26
5.5.4 Managing license........................................................................................................... 27
5.5.5 Transferring license to another installation.................................................................... 29
5.6 Upgrading Romexis........................................................................................................................ 29
5.7 Romexis silent installation.............................................................................................................. 32
5.8 Post-installation configurations on Windows.................................................................................. 32
5.8.1 DIDAPI configuration......................................................................................................33
5.8.2 TWAIN interface configuration....................................................................................... 33
5.8.3 PMBridge interface configuration................................................................................... 36
5.8.3.1 Windows registry additions........................................................................ 37
5.8.3.2 Users......................................................................................................... 38
5.8.3.3 Enabling PMBridge connection..................................................................38
5.8.3.4 PMBridge with dynamic ports.................................................................... 38
5.8.4 DICOM interface configuration.......................................................................................39
5.8.5 Installing Romexis implant library...................................................................................39
5.8.6 Database operations...................................................................................................... 42
5.8.6.1 Installing MS SQL Server Management Studio......................................... 42
5.8.6.2 Setting up MS SQL Server Express backup..............................................42
5.8.6.3 Transferring and merging databases.........................................................44
5.8.6.4 Exporting source database........................................................................ 44
5.8.6.5 Importing data to target database..............................................................46
5.8.7 Configuring Romexis client and server settings............................................................. 48
5.9 Uninstalling Romexis...................................................................................................................... 48
5.10 Troubleshooting..............................................................................................................................49

Technical manual Romexis

Table of contents

5.10.1 Broken font in Korean language Romexis on Windows 10............................................ 49

5.10.2 Romexis client connection to Romexis server fails........................................................ 49
6 Installing Romexis on macOS...................................................................................................................50
6.1 Requirements (macOS)..................................................................................................................50
6.1.1 System requirements..................................................................................................... 50
6.1.2 User requirements..........................................................................................................50
6.1.3 Known issues................................................................................................................. 50
6.1.4 Device support............................................................................................................... 51
6.2 Installing/upgrading Romexis on macOS....................................................................................... 51
6.3 Installing Romexis license on macOS............................................................................................ 54
6.4 Activating Romexis license.............................................................................................................55
6.5 Configuring Romexis client.............................................................................................................55
6.6 Configuring Romexis server........................................................................................................... 57
6.7 DIDAPI configuration...................................................................................................................... 57
6.8 Starting Romexis server................................................................................................................. 57
6.9 Setting up Romexis backup............................................................................................................57
6.10 Database operations...................................................................................................................... 58
6.10.1 Squirrel SQL Database client.........................................................................................58
6.10.2 Transferring and merging databases............................................................................. 59
6.10.3 Exporting files from one database to another................................................................ 59
6.10.4 Importing database from one location to the other.........................................................60
6.11 Installing Romexis implant library................................................................................................... 63
6.12 Setting Romexis client to start at login........................................................................................... 64
6.13 Configuring intraoral camera support............................................................................................. 64
6.14 Configuring Romexis client and server settings............................................................................. 64
6.15 Troubleshooting..............................................................................................................................65
6.15.1 Romexis client connection to Romexis serverfails......................................................... 65
7 Admin module tasks and settings............................................................................................................. 66
7.1 Starting Admin module................................................................................................................... 66
7.2 Connect.......................................................................................................................................... 67
7.2.1 Configuring application launch....................................................................................... 70
7.3 Local Settings................................................................................................................................. 71
7.3.1 2D Imaging.....................................................................................................................72
7.3.2 3D Imaging.....................................................................................................................74
7.3.3 Automatic Image Import................................................................................................. 75
7.3.4 CAD/CAM.......................................................................................................................76
7.3.5 CD-Recording Device.................................................................................................... 76
7.3.6 Dental Unit..................................................................................................................... 77
7.3.7 DICOM........................................................................................................................... 78
7.4 User Management.......................................................................................................................... 78
7.4.1 Adding/updating group................................................................................................... 78
7.4.2 Adding/updating user..................................................................................................... 79
7.4.3 Setting Romexis Cloud user account............................................................................. 81
7.4.4 Setting DDX user account..............................................................................................83
7.5 Patient Merge................................................................................................................................. 83
7.5.1 Patient Search................................................................................................................84
7.5.2 Patient Merge.................................................................................................................84
7.6 DICOM............................................................................................................................................85
7.6.1 Applications....................................................................................................................86
7.6.1.1 Adding or editing DICOM application entity (AE).......................................86
7.6.1.2 Modifying Default Storage AE setup..........................................................88
7.6.1.3 Modifying Default Printer AE setup............................................................91
7.6.1.4 Modifying Default Worklist AE setup..........................................................92

Romexis Technical manual

 Table of contents

7.6.1.5 Modifying Default MPPS AE setup............................................................ 93

7.6.1.6 Modifying Default Q/R (Query/Retrieve SCU) AE setup............................94
7.6.1.7 Modifying Default Auto Storage AEs setup................................................95
7.6.1.8 Configuring Romexis server as DICOM Storage SCP (PACS)................. 96
7.6.1.9 Configuring Romexis server as DICOM Query/Retrieve SCP................... 96
7.6.2 Romexis Server..............................................................................................................96
7.6.3 Access Control............................................................................................................... 97
7.6.4 Modality Performed Procedure...................................................................................... 97
7.6.5 Radiation Dose Structured Report................................................................................. 97
7.6.6 Query/Retrieve/Storage SCP......................................................................................... 98
7.6.7 Default Specific Character Set....................................................................................... 98
7.6.8 Patient merge on DICOM Storage................................................................................. 98
7.6.9 DICOM logging...............................................................................................................99
7.6.10 DICOM/HL7 RxBroker Control..................................................................................... 101
7.7 Security.........................................................................................................................................101
7.8 Templates.....................................................................................................................................102
7.8.1 Creating new template................................................................................................. 103
7.8.2 Editing existing template.............................................................................................. 104
7.9 Device Alerts................................................................................................................................ 105
7.9.1 Configuring device alerts..............................................................................................105
7.9.2 Configuring usage data alerts...................................................................................... 106
8 Romexis configuration............................................................................................................................ 107
8.1 Starting Romexis Configuration tool............................................................................................. 107
8.2 Changing password......................................................................................................................108
8.3 Restarting Romexis service..........................................................................................................108
8.4 Modifying Romexis logging...........................................................................................................109
9 Romexis Configuration tool parameters and settings............................................................................. 112
9.1 Resources.................................................................................................................................... 112
9.1.1 General........................................................................................................................ 112
9.1.2 Person..........................................................................................................................113
9.1.3 Regional....................................................................................................................... 115
9.2 Imaging.........................................................................................................................................115
9.2.1 General........................................................................................................................ 116
9.2.2 Panoramic.................................................................................................................... 117
9.2.3 Cephalometric.............................................................................................................. 119
9.2.4 Intraoral........................................................................................................................ 121
9.2.5 ProScanner.................................................................................................................. 123
9.2.6 ProScanner 2.0 / ProXam iP........................................................................................ 124
9.2.7 Twain Intraoral............................................................................................................. 126
9.2.8 CBCT........................................................................................................................... 127
9.2.9 Defining custom preprocessing settings...................................................................... 128
9.3 Export Font Sizes......................................................................................................................... 129
9.4 Print.............................................................................................................................................. 130
9.5 Cloud............................................................................................................................................ 130
9.6 DDX Dental...................................................................................................................................131
9.7 Usage Data Tracking....................................................................................................................133
9.8 Clinic Management.......................................................................................................................133
9.8.1 PlanLink & Diagnostics................................................................................................ 134
9.8.2 Unit Connections..........................................................................................................136
9.8.3 Solanna Vision............................................................................................................. 137
9.8.4 Floor names................................................................................................................. 138
9.8.5 Integrated communication............................................................................................139
9.8.6 DDS Communication....................................................................................................140

Technical manual Romexis

Table of contents

9.9 Security.........................................................................................................................................140
9.9.1 Client............................................................................................................................ 141
9.9.2 Server...........................................................................................................................144
9.10 Image & Data Management..........................................................................................................145
9.10.1 Data folders..................................................................................................................145
9.10.2 Trash............................................................................................................................ 146
9.11 Start-up.........................................................................................................................................146
9.11.1 Client parameters.........................................................................................................146
9.11.2 Romexis Service.......................................................................................................... 148
9.12 Server Parameters....................................................................................................................... 149
9.12.1 Server...........................................................................................................................149
9.12.2 Database......................................................................................................................152
9.12.3 External Communication.............................................................................................. 154
10 Romexis server and unit connection configuration................................................................................. 156
10.1 Before you start Romexis server and unit connection configuration............................................ 156
10.2 Configuring Romexis server settings............................................................................................156
10.3 Configuring Romexis unit connections......................................................................................... 158
10.3.1 Configuring Sovereign Classic connection...................................................................159
10.3.2 Configuring Compact i5 connection............................................................................. 161
10.3.3 Configuring Compact i3 connection............................................................................. 164
10.3.4 Configuring Compact i v2 (touch panel) connection.................................................... 168
10.3.5 Configuring Compact i v2 (keyboard) connection........................................................ 171
10.3.6 Configuring ProSensor HD connection........................................................................ 173
10.3.7 Configuring ProMax X-ray unit connection...................................................................175
10.3.8 Configuring ProOne X-ray unit connection...................................................................176
10.3.9 Configuring ProX connections......................................................................................178
10.3.10 Configuring PlanMill 40 S milling unit connection........................................................ 179
10.3.11 Configuring Creo C5 connection.................................................................................. 180
10.4 Configuring intraoral camera........................................................................................................ 181
10.5 Configuring PlanScan scanner..................................................................................................... 182
10.6 Configuring Emerald scanner....................................................................................................... 184
10.7 Configuring dental unit touchpad functionality..............................................................................185
10.8 Configuring Solanna Vision.......................................................................................................... 185
11 Clinic Management configuration........................................................................................................... 190
11.1 Before you start Clinic Management configuration.......................................................................190
11.2 Configuring Clinic Management general settings......................................................................... 190
11.3 Creating floor plans...................................................................................................................... 192
11.4 Adding units to Clinic Management layout................................................................................... 194
11.5 Configuring service contact details sending from Romexis to dental units...................................195
11.6 Creating device groups.................................................................................................................195
11.7 Updating unit Guides content....................................................................................................... 196
11.8 Maintenance scheduling...............................................................................................................196
11.9 Maintenance demands................................................................................................................. 197
11.10 Configuring Sovereign Classic user settings storing.................................................................... 198
11.11 Configuring automatic login to Sovereign Classic with Romexis client login................................198
11.12 Configuring Compact i dental unit manual user settings storing and transfer.............................. 199
11.13 Configuring Compact i dental unit automatic user settings storing and transfer.......................... 199
11.14 Configuring of sending device alert e-mails..................................................................................200
11.15 Starting Romexis Virtual Clinic..................................................................................................... 200
11.16 Viewing logs................................................................................................................................. 201
11.17 Creating service entry record....................................................................................................... 202

Appendix A: Romexis language abbreviations................................................................................................. 205

Romexis Technical manual

 Table of contents

Appendix B: Configuring Romexis user's manual.............................................................................................206

Appendix C: X-ray device Ethernet configuration in terminal server environment............................................207
Appendix D: Romexis client startup parameters...............................................................................................208
Appendix E: Specification of USB connected RFID readers.............................................................................210

Technical manual Romexis

Table of contents

Romexis Technical manual

 1 Introduction

1 Introduction
This manual describes how to install, setup, configure and administer
Romexis imaging software.

NOTE
This manual is valid for the Romexis software version 6.4.4 or later.

NOTE
The Romexis configuration and service tasks should be performed only by
qualified personnel, trained by manufacturer or approved dealers.

NOTE
All field maintenance actions and upgrades need to be verified by device
testing.

NOTE
Introducing and using Romexis in the organisation's IT-network could result
unidentified risks to patients, users or third parties; it is up to the responsible
organisation to identify, analyse, evaluate and control these risks.
Any subsequent changes to the IT-network could introduce new risks and
require additional analysis from the responsible organisation.

NOTE
Changes in the IT-network, not instructed in Romexis manuals, could result
unidentified risks to patients, users or third parties.
The IT-network changes include the following:
• changes in the network configuration
• addition or removal of items (hardware and/or software platforms or
software applications)
• update of hardware and/or software platforms or software applications
• upgrade of hardware and/or software platforms or software applications.

Manufacturer
Planmeca Oy, Asentajankatu 6, FIN-00880, Helsinki, Finland
Phone: +358 20 7795 500, Fax: +358 20 7795 555, http://
www.planmeca.com

1.1 Associated documentation

Romexis is delivered with the following manuals:
• Romexis user's manual
• Romexis technical manual
• Romexis quick installation guide
The manuals are delivered with the Romexis software and can be found
from the following folders:
• Installation package
• Windows:
Planmeca_Romexis_<version>_Win\doc

Technical manual Romexis 1

1 Introduction

Planmeca_Romexis_<version>_Win\Romexis Quick
Installation Guide.pdf
• macOS:
Planmeca_Romexis_<version>_Mac_OS/doc
Planmeca_Romexis_<version>_Mac_OS/Romexis Quick
Installation Guide.pdf
• Installation folder (default installation)
• Windows:
C:\Program Files\Planmeca\Romexis\manuals
• macOS:
/Applications/Planmeca/Romexis/manuals
The Romexis manuals are also delivered with separate USB memory sticks
together with the devices (e.g. X-ray and dental units) to be used in
conjunction with Romexis. The environmental requirements for these USB
memory sticks are the same as defined for the devices they are delivered
with.

NOTE
Between the Romexis software releases updates to the manuals may be
published.
The latest versions of the user’s manuals are available on the Material Bank:
https://materialbank.planmeca.com/
The latest version of the technical manual as well as the Romexis software
are available on the Planmeca One (access only for approved dealers):
https://one.planmeca.com/

The original language of the manuals is English.

1.2 Indications for use

Planmeca Romexis is a medical imaging software intended for use in
dental and medical care as a tool for displaying and visualizing dental and
medical 2D and 3D image files from imaging devices, such as projection
radiography and CBCT. It is intended for use by radiologists, clinicians,
referring physicians and other qualified individuals to retrieve, process,
render, diagnose, review, store, print, and distribute images of both adult
and pediatric patients.
Planmeca Romexis is also a preoperative software used for dental implant
planning. Based on the planned implant position a model of a surgical guide
for a guided implant surgery can be designed. The designed objects can be
exported to manufacture a separate physical product.
Planmeca Romexis is also a preoperative software for simulating /
evaluating surgical treatment options. Based on the simulation, models,
guides and splints can be designed for use in maxillofacial surgery. The
designed objects can be exported to manufacture a separate physical
product.
Planmeca Romexis is also intended to be used for monitoring, recording,
storing and displaying mandibular jaw positions and movements relative to
the maxilla.
Additionally, Planmeca Romexis includes monitoring features for Planmeca
devices for maintenance purposes. The software is designed to work as a

2 Romexis Technical manual

 1 Introduction

stand-alone or as an accessory to Planmeca imaging and Planmeca dental

unit products in standard PC.
The software is for use by authorized healthcare professionals. Use of
the software for implant planning requires that the user has the necessary
medical training in implantology and surgical dentistry. Use of the software
for surgical treatment planning requires that the user has the necessary
medical training in maxillofacial surgery.
Indications of the dental implants do not change with guided surgery
compared to conventional surgery.

1.2.1 Reporting serious incidents

Serious incidents that have occurred in relation to the device must be
reported to the manufacturer and the local competent authority.

Technical manual Romexis 3

2 System requirements

2 System requirements
The following tables list the system recommendations and requirements for
installing the Romexis software on both Windows and macOS operating
systems.
System requirements are impacted by the scope of the installation
environment as well as the number and activity level of users. The following
requirements apply to an environment with 1-5 Romexis client users.

NOTE
The following system requirements are recommendations. Not meeting them
may lead to degraded performance.

NOTE
If dozens of dental units are connected under the same Romexis server it is
recommended to double the server resources.

NOTE
If plenty of other software/applications are installed and used in the same
workstation with Romexis, it may degrade Romexis performance.

NOTE
Check the latest up-to-date system recommendations from the following
www-page:
https://www.planmeca.com/software/specifications/system-requirements/

2D imaging system recommendations

Romexis client Romexis server

Processor Minimum: Intel Core i3 (6th Minimum: Intel Core i3 (6th
generation or later) or equivalent generation or later) or equivalent
RAM 4 GB 8 GB
8 GB when working with large
colour photos
Graphics card Any (integrated or dedicated) Any
Hard disk *** 80 GB 2 x 500 GB (RAID1 mirroring)
Supported operating • Windows 10 Pro • Windows 2019 Server
system * • Windows 11 Pro • Windows 10 Pro
• macOS 12 ** • Windows 11 Pro
• macOS 13 ** • macOS 12
• macOS 13
* Only 64-bit operating systems supported
** Romexis Cephalometric Analysis module is not supported on
macOS.
*** The required hard disk size depends on the number of exposures
taken, the image format used, and how long the hard disk space is
assumed to be sufficient.

4 Romexis Technical manual

 2 System requirements

3D imaging system recommendations

Romexis client Romexis server

Processor Minimum: Intel Core i5 (6th generation or later) or Minimum: Intel Core i3
equivalent (6th generation or later)
or equivalent
Recommended: Intel Core i7 Desktop (6th
generation or later) or equivalent
RAM * 3D viewing workstation 3D acquisition
workstation
ProMax 3D s: 8 GB ProMax 3D s: 8 GB
ProMax 3D Classic: 8 GB ProMax 3D Classic: 8 GB
ProMax 3D Plus: 8 GB ProMax 3D Plus: 16 GB
ProMax 3D Mid: 16 GB ProMax 3D Mid: 16 GB 16 GB
ProMax 3D Max: 16 GB ProMax 3D Max: 16 GB
Viso G5: 16 GB Viso G5: 16 GB
Viso G7: 20 GB Viso G7: 32 GB
ProXam 3D: 8 GB ProXam 3D: 8 GB
ProXam 3DQ: 16 GB ProXam 3DQ: 16 GB
Graphics card NVIDIA or AMD (dedicated GPU) ** Any
Hard disk ***** 120 GB 2 x 1 TB (RAID1
mirroring) recommended
Supported • Windows 10 Pro • Windows 2019
operating system • Server
Windows 11 Pro
*** • Windows 10 Pro
• macOS 12 ****
• Windows 11 Pro
• macOS 13 ****
• macOS 12
• macOS 13
* - 24 GB RAM recommended for workstations using the Implant
Guide, 4D Jaw Motion and/or Superimpose features.
- 32 GB RAM recommended if working with large high resolution
volumes and/or Surgery features.
- Working with large volumes, for example captured with
Planmeca Viso, ProMax 3D Mid, ProMax 3D Max, ProXam 3DQ,
or having large environments with several simultaneous users,
requires more memory allocated to the server than the default
Max Heap Size of 3000. For more information on configuring
Romexis memory allocations, see section "Romexis Service" on
page 148 .
** NVIDIA GeForce GT-GTX 10 Series (or highest) with 2 GB (or
highest) recommended for Romexis 3D Ortho Studio.
*** Only 64-bit operating systems supported
**** Romexis Cephalometric Analysis module and Romexis 3D Ortho
Studio module are not supported on macOS.
***** The required hard disk size depends on the number of
exposures taken, the image format used, and how long the hard
disk space is assumed to be sufficient.

Technical manual Romexis 5

2 System requirements

CAD/CAM system recommendations

Romexis client Romexis server

Computer Laptop PC or desktop PC -
Processor Intel i7, 11th generation or better Minimum: Intel Core i3 (6th
generation or later) or equivalent
RAM 32 GB 8 GB
Hard disk 512 GB SSD 2 x 1 TB (RAID1 mirroring)
recommended
Graphics card NVIDIA RTX A3000 or better Any
Cable interface USB 3.0 -
Display Full HD resolution -
Supported operating Windows 10 (64bit) Pro • Windows 2019 Server
system * • Windows 10 Pro
• Windows 11 Pro
• macOS 12
• macOS 13
* Only 64-bit operating systems supported

Common minimum requirements

Romexis client Romexis server

Display Full HD 1920 x 1080 1280 x 1024
Backup medium None required DAT or equivalent

NOTE
Manufacturer claims no responsibility
for end user backup.
Database None • MS SQL 2012, Service Pack 4
(minimum requirement)
• MS SQL 2016 Server/Server
Express
• MS SQL 2019 Server/Server
Express
• MS SQL 2022 Server/Server
Express
• Firebird (macOS)

6 Romexis Technical manual

 3 Data backup and life cycle management

3 Data backup and life cycle management

NOTE
Manufacturer claims no responsibility for the end users’ data security or for
any malfunction in the computer system that may lead to loss of data.

Image backup
Romexis image data is stored into the file system as individual files. The
image data in the file systems must be backed up and stored securely.
The image data can be secured by backing up the following folder (if default
image data folders are used).
• Windows:
C:/romexis_images
• macOS:
/Applications/Plameca/Romexis/database/Romexis_images
The location of the image data folder can be modified, either during Romexis
installation, or with Romexis Configuration tool, see section "Data folders" on
page 145.
In addition to the image data, the data in the following folders is
recommended to backup:
• Clinic management data stored in the following folder.
Windows:
C:/romexis_ergodata
macOS:
/Applications/Plameca/Romexis/database/
Romexis_ergodata
• Thumbnail images stored in the following folder:
Windows:
C:/romexis_cache
macOS:
• /Applications/Plameca/Romexis/database/Romexis_cache
For more information on configuring backups, see sections "Setting up MS
SQL Server Express backup" on page 42 (Windows) and "Setting up
Romexis backup" on page 57 (macOS).

Database backup
Romexis uses a database system for storing patient data and image
metadata. The database must be backed up and stored securely.
Secure the patient database using backup tools of the respective database
engine. It is recommended to regularly verify the integrity of backed up files.

NOTE
The storage and backup media containing database and image should be
appropriately encrypted either on the device or the file level, to protect them
from unauthorised access during storage or in case of theft.

If backing up database by using a copied file of the database, shut down the
service for the respective database engine before proceeding. Microsoft SQL

Technical manual Romexis 7

3 Data backup and life cycle management

also supports Volume Shadow Copy Service (VSS) applications for backing
up a live database.

Keystore backup
Romexis needs access to various installation specific secrets such as
database password and encryption keys.
These secrets are stored at Romexis server side in a Key Vault,
which contains of a password protected keyvault.p12 file, located in
the C:\ProgramData\Planmeca\Romexis\sconfig (Windows) and /
Applications/Planmeca/Romexis/sconfig (macOS) folder.

Configuration backups
The following Romexis related configurations are recommended to include to
the backup routine (if default installation folder is used).
• All contents of the general configuration folder, this includes also the
keyvault.p12 file, as well as report and print templates.
Windows:
C:\Program Files\Planmeca\Romexis\sconfig
macOS:
/Applications/Planmeca/Romexis/sconfig
• If Romexis Cephalometric Analysis module (Windows only) is in use, its
configuration folder.
C:\Program Files\Planmeca\Romexis\client\cephmodule
• If Romexis 3D Orthostudio (Windows only) is in use, its configuration
folder.
C:\Program Files\Planmeca\Romexis\client\orthostudio

Adding disk space

A local hard drive is the most common option for storing the images in
Romexis. If needed, disk space can be increased by adding a new hard
drive and pointing the Romexis data folders to the new drive using Romexis
Configuration tool, see section "Data folders" on page 145.
In large group practices where amount of data is large, it is recommended to
use Storage Area Network (SAN) for image data storage where disk space
can be added transparently.

3.1 Data decommissioning

The patient information database and actual patient images are stored in
different locations. Depending on the setup used they can also be on
different server computers. The database location is dependent on which
database system is in use.
To remove the images, delete the Romexis_images folder.
To remove patient data, delete the database. For more information, see the
technical documentation for the relevant database system.
It is also recommended to properly erase data before disposing of a hard
drive that has been used for storing images or patient data. For more
information, refer to your local legislation.

8 Romexis Technical manual

 4 Security hardening

4 Security hardening
Good computer and network security must be followed in any environment
where Romexis is installed and used. It is recommeneded to install industry
standard firewall and virus protection on both Romexis server and client(s).
All operating systems, as well as firewall and virus protection software,
should be kept up to date. All security patches should be installed. For more
information, see the technical documentation for the relevant software.

Default users, services and ports

The following users are created by the setup software and their passwords
must be changed after installation:
• Database admin user
• Database user romexis
• Romexis default user sysadm
• Romexis integration user pmbridge

NOTE
The clachuah user is no longer added during new installations from Romexis
version 5.2.0.R. In update installations, the inactivation of the clachuah user
is recommended after update if the user is not in use.

NOTE
To prevent unauthorised access to patient data, set appropriate user
permissions and use the operating system automatic timed workstation lock
feature.

Minimum required services/ports:

• MSSQL Server Browser (port 1434 with dynamic ports)
• Romexis server Java RMI (port 1099 with dynamic ports)
• Romexis server configuration (port 2099)

NOTE
All default ports can be changed using the Romexis Configuration tool.

Recommended security capabilities requiring configuration at install time

Pay attention to the security capabilities when installing and configuring
Romexis, see the following table.

Access management
Person Authentication

Technical manual Romexis 9

4 Security hardening

Per user logins

Own username for each user, or using MS Active Directory (AD).
Change default admin passwords
See section "Changing password" on page 108.
Strong user password requirements
See section "Client" on page 141.
Authorization
Proper user group permissions
See section "User Management" on page 78.
Automatic log off
See section "Client" on page 141.
Health data storage confidentiality
Database encryption using MS SQL transparent date encryption (TDE)
feature
See appropriate MS SQL documentation.
Operating system provided disk encryption
See appropriate operating system (OS) documentation.
Data backup and disaster recovery
Ensure that Romexis related data is backed up as recommended.
See section "Data backup and life cycle management" on page 7.
Virus and malware protection
Installation of industry standard firewall and virus protection on both
Romexis server and client(s).
Security patching
All security patches should be installed.
Application hardening
Application hardening by enabling only necessary Romexis services to
minimize number of open ports.
See section "Server Parameters" on page 149.

Additional security capabilities

• Protecting secrets (DB password etc.) using Keystore.
See sections "Security" on page 140.
• Health data transmission confidentiality and integrity using TLS
encryption.
• Server-Client encryption is enabled by default
See section "Server" on page 149.
• Database encryption is enabled by default (only on Windows, not in
macOS)
See section "Database" on page 152.
• Audit Controls: User activity reporting in Report module
See Romexis user's manual.

10 Romexis Technical manual

 4 Security hardening

• Optional: Authenticating server and clients using certificates (Node

Authentication).
Default server & client certificates are used and are adequate to most
users. Additional hardening is possible.
See sections "Security" on page 140 and "Server Parameters" on page
149.

Technical manual Romexis 11

5 Installing Romexis on Windows

5 Installing Romexis on Windows

This chapter includes instructions on how to install, upgrade and uninstall
Romexis software on Windows operating system (OS). In addition, other
installation related instructions are available in this chapter.
The installation includes the following main components:
• Romexis software
• Necessary Java components
• MS SQL 2022 Server Express data management system software
In addition, depending on the system setup, several optional components
can be selected to be installed.

NOTE
When upgrading Romexis from a few releases older version (4.6.2 or older)
it is recommended to upgrade first to the version 5.3.5 before upgrading to
6.x.x release.

5.1 Romexis software components

The Romexis software consists of several components. The components
can be selected in the beginning of the installation procedure.
Before starting the actual installation, study and plan carefully which of the
components are needed in the current case.

NOTE
It is recommended to take a backup of the current Romexis database before
performing the upgrade.

Server components
• Server Program
Romexis program for the server installation.
• MS SQL Server
The default data management system installed.
If another data management system is required, some configuration is
necessary to enable integration.
• Romexis Database
Romexis database MS SQL instance.

Client components
• Client Program
Romexis program for the client.
• VDDS
Required for integration with most of the German practice management
systems.
• Dental unit serial communication
Required if Planmeca Compact i v1 and/or Planmeca Compact i Classic
v1 are connected with Clinic Management.
• Enable Active Directory SSO

12 Romexis Technical manual

 5 Installing Romexis on Windows

This enables Romexis application to access the Kerberos Session Key

for Single Sign-on to work correctly. It modifies the registry value:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\L
sa\Kerberos\Parameters value allowtgtsessionkey=1
This option also modifies Romexis.bat used with PmBridge installation
so it does not contain PmBridge user login details.

Imaging software package

The following installations also require imaging software package to be
installed and run:
• DIDAPI
Didapi X-ray device driver is required on image capturing workstations.
In addition, the DIDAPI component includes subfeatures:
• DIDAPI and device drivers
DIDAPI interface and device drivers for X-ray units.
• DIDAPI UI Support for Integrators
DIDAPI user interface for integrating other DIDAPI users.
• TWAIN Source Capture
TWAIN interface.
• ProSensor/ProXam iS USB Driver
ProSensor/ProXam iS USB driver.
• Device Tool(s)
Required for imaging system device calibrations.
• ProScanner/ProXam iP
Required on ProScanner/ProXam iP workstations.
If Romexis installation media does not contain imaging software package,
the following notification displays:

For more information on downloading and installing imaging software

package, see the Imaging System Updater manuals.

NOTE
The imaging software package also includes Planmeca ProSensor,
ProScanner and ProScanner 2.0, plus KaVo ProXam iP and iS drivers.

Cephalometric Analysis module

Romexis Cephalometric Analysis module.

CAD/CAM module scanning software

Includes software components for using intraoral scanners in Romexis
CAD/CAM module.

Technical manual Romexis 13

5 Installing Romexis on Windows

5.2 Requirements (Windows)

Before you start the actual software upgrade or installation, check carefully
all the preconditions, pre-settings and recommendations listed in this
section, and make all necessary changes to the target system.
If the requirements described in this chapter are not met, the installation fails
or software does not start or function properly after upgrade or installation.

NOTE
Consult your local dealer for detailed information on device support for
different platforms.

5.2.1 System requirements

Check that the system requirements, listed in section "System requirements"
on page 4, are met.

5.2.2 Network requirements

The following network related requirements are set:
• The server client communication is based on Java RMI over TCP/IP,
thus support for TCP/IP protocol is required.
• Network bandwidth requirements are dominated by digital imaging
requirements:
• Viewing digital 2D image requires a transfer of roughly 5 MB of data
over network.
• Viewing 3D volume requires a transfer of 250 MB - 2 GB of data over
network, depending on the volume size and resolution.
• It is recommended that for 3D capture and viewing, a gigabit Ethernet
connection should be used.
• If a firewall is in use, Java RMI protocol requires Romexis to have full
access to all ports between the defined range:
• For more information on defining ports, see section "Server" on page
149.
• If a range of ports is not defined, the default setting is ports above
and including port 1024.

5.2.3 Requirements for user account

The following requirements are set for the user account used during the
upgrade and installation:
• Required user account during the installation is Administrator.
• The user account which starts Romexis Service on a 64-bit operating
system must have a valid password set (not null).

5.3 Installing Romexis on Windows

Before you begin

NOTE
Before starting the installation, check that all requirements are met and
needed planning is made, as described in section "System requirements" on
page 4.

14 Romexis Technical manual

 5 Installing Romexis on Windows

NOTE
Run the installation program as an admin user.

About this task

The following procedure instructs how to make a new installation of Romexis
software.

Steps
1. Locate the Romexis setup program (either on the delivered USB flash
drive or on the downloaded and extracted zip-file contents) and start the
upgrade by double-clicking.
\Romexis\setup.exe
The InstallShield Wizard window appears. Click Next to start the
installation.

2. In the License Agreement screen, read the license and select I accept
the terms of the license agreement option and click Next to continue.

Technical manual Romexis 15

5 Installing Romexis on Windows

3. Select either Standard or Custom installation.

• Select the Standard installation to install the following components.

Server components:
Romexis Server Program
MS SQL Server Express
Romexis Database
Client components:
Romexis Client Program
Continue these instructions from Step 7.
• Select the Custom installation, if you want to manually select the
components to be installed and to modify the image storage paths,
and continue these instructions from the Step 4.
For more information on Romexis components, see section "Romexis
software components" on page 12.
When selected, click Next.

16 Romexis Technical manual

 5 Installing Romexis on Windows

4. Select installation folder.

The default folder (C:\Program Files\Planmeca\Romexis) is

recommended to be used.
When selected, click Next.
5. Select the components to be installed.
Server components:

Client components:

For more information on Romexis components, see section "Romexis

software components" on page 12.
When selected, click Next.

Technical manual Romexis 17

5 Installing Romexis on Windows

6. Set the Romexis server IP address.

Set the IP address as follows:

Server installation: localhost
Client installation: <Romexis server IP address>
Server & client installation: localhost
When set, click Next.
7. If needed, modify the image storage paths (note, this selection is
available only on custom installation mode).
To modify the default image storage paths, activate the selection by
checking the Change Romexis Images folder path and use the Browse
buttons to select the desired location for the image storage folders.

18 Romexis Technical manual

 5 Installing Romexis on Windows

8. Select the language for software and click Next.

Note, you can change the language later in the Romexis Configuration
tool.
9. Select the Romexis default country.

10. Check the installation summary.

Browse through the summary and verify that you have selected all
wanted components.
Click Back if you want to change some selections.
When the correct components are selected, click Next.

Technical manual Romexis 19

5 Installing Romexis on Windows

11. Click Install to start the installation.

The installation starts. Depending on the component selections, several

different installation progress windows will appear on the screen.
In here, only those that need some action are described. Otherwise, click
Next, Install or Finish buttons when appropriate.
12. Click Finish to complete the installation.

13. Restart Windows, select Yes and click OK.

Wait until Windows restarts.

What to do next
Continue to install license, see section "Installing Romexis license on
Windows" on page 20.

5.4 Installing Romexis license on Windows

Depending on the installation type (client/client and server or server only
installation) install the Romexis license, as described in the following
sections.

20 Romexis Technical manual

 5 Installing Romexis on Windows

5.4.1 Installing license in Romexis client

About this task

To install license for client/client and server installation, perform the following
steps during Romexis client start-up.
If Romexis does not detect an installed license, a 30 day trial period is
provided.

Steps
1. Click Install license in the dialog.

To continue using Romexis without a license, click the Continue Trial

button.
2. Browse to and select the license file.
The license is separately provided when purchasing Romexis.

3. Click Open.
4. When License installed successfully! window appears, click OK button.
5. Restart Romexis client.

What to do next
After the license is installed, you must activate it. For more information, see
section "Activating Romexis license" on page 23.

5.4.2 Installing license in Romexis server only installation

About this task

To install the license for server only installation, perform the following steps.

Technical manual Romexis 21

5 Installing Romexis on Windows

Steps
1. To start the License Installer in Windows, select Start > Planmeca >
Install Romexis License.

2. Select the folder in which the license file (romexis.lic) can be found,
and choose Next.
The License Installer requires the location of the license file which is
separately provided when purchasing Romexis.

3. Start installing the licence, click Install.

4. Restart Romexis Service.

4.a. In Windows Start menu, select Planmeca > Start Romexis
Service.

4.b. Click Stop Service and wait for a couple of seconds.

22 Romexis Technical manual

 5 Installing Romexis on Windows

4.c. Click Start Service.

4.d. Click OK to acknowledge the restart.
4.e. Click Done to close the window.
5. After the licence is installed, click Finish.

What to do next
After the license is installed, you must activate it. For more information, see
section "Activating Romexis license" on page 23.

5.5 Activating Romexis license

The functions in the Romexis application are controlled by license and user
rights. In order to use the application, the license must be activated.

NOTE
Depending on the installed license and user rights the functions described in
this manual can vary.

When Romexis Client is started (until activated) after new and updated
Romexis server installations a dialog requesting for activation will pop up.
A period of 30 days is given to activate the Romexis license.
When connected to the Internet, activate the license by filling in username
and email address.

Technical manual Romexis 23

5 Installing Romexis on Windows

24 Romexis Technical manual

 5 Installing Romexis on Windows

5.5.1 Manual activation

When there is no fixed Internet connection available the license can be
manually activated using a mobile phone, for example. If manual activation
is selected the following dialog appears. Follow the instructions in the dialog
and web page.

NOTE
Use the end customer details, not the dealer’s.

5.5.2 Installing license

About this task

Follow these steps to install a license.

Steps
1. Click the Install License button.

2. A license installation dialogue opens and asks for the license file
romexis.lic.

Technical manual Romexis 25

5 Installing Romexis on Windows

3. Browse to the license file and click Open.

When the license has been successfully installed the following message
appears.

4. Click OK.

5.5.3 Updating license

About this task

Follow these steps to update a license.

26 Romexis Technical manual

 5 Installing Romexis on Windows

Steps
1. From the File menu select Update License.

2. Click Install License button and browse to the .lic file.

When the license has been successfully installed the following message
appears.

3. Click OK.

5.5.4 Managing license

About this task

Follow these instructions to manage license.

Technical manual Romexis 27

5 Installing Romexis on Windows

NOTE
Only users with administrator rights have access to license management.

Steps
1. Select License management from the File menu.

The License management window opens.

28 Romexis Technical manual

 5 Installing Romexis on Windows

In the window you can view:

• the number of Romexis clients currently using the license
• expiry dates
• list of current users:
To remove users from the list, select the user you want to remove
and click Drop Client.

• the software modules and features included in the license

5.5.5 Transferring license to another installation

If you are transferring license from one Romexis server installation to
another it must first be released from the current workstation by selecting
Release license.

5.6 Upgrading Romexis

Before you begin

NOTE
Before starting the upgrade, check that all requirements are met and needed
planning is made, as described in section "System requirements" on page 4.

Technical manual Romexis 29

5 Installing Romexis on Windows

NOTE
It is recommended to take a backup of the current Romexis database before
performing the upgrade.

NOTE
Run the installation program as an admin user.

About this task

The following procedure instructs how to upgrade an existing Romexis
software.

Steps
1. Locate the Romexis software and start upgrade by double-clicking the
setup program.
\Romexis\setup.exe
The installation window appears.

2. Select the Modify Installation option and click Next.

3. Accept the Licence Agreement and click Next.
4. From the Component Selection window, select the components installed
in the original installation, and click Next.

NOTE
Make sure to select all Romexis components that are installed on the
workstation. If you deselect a component that is already installed it will
be removed from the workstation during the upgrade.

Additionally, you can also select new components, for more information
on Romexis components, see section "Romexis software components"
on page 12.

30 Romexis Technical manual

 5 Installing Romexis on Windows

Server components:

If you are updating a server installation, remember to select Romexis

Database from the Server Components. This applies only to MS SQL
Server databases.
In case of other database, deselect the options MS SQL Server and
Romexis Database from Server Components and run the database
update scripts manually.
Client components:

5. Select the used language and click Next.

6. When ready, click Finish to complete the installation.
7. Restart Windows, select Yes and click OK.

Wait until the Windows restarts.

Technical manual Romexis 31

5 Installing Romexis on Windows

5.7 Romexis silent installation

About this task

Identical Romexis software installations can be performed to several
Windows workstations using the silent installation option. Carry out the
following steps for silent installation.

Steps
1. Start windows command prompt with administrator privileges.
2. To record your installation, run Romexis setup executable from
installation media with the following command (enter the whole
command to the same line).
E:\Romexis\setup.exe /r
/f1"<PATH_TO_RECORD_FILE>\romexis_installation.iss"
Replace <RECORD_FILE_PATH> with a file path name you wish to save
the result record file.
If the f1 parameter is not set, the record file will be saved by default to
folder and with filename:
C:\Windows\setup.iss
3. Perform the installation following the installation dialogs normally.
Follow the installation instructions given earlier in this manual.
4. After successful installation, copy the romexis_installation.iss
record file to another workstation or a portable drive.
5. To perform the installation with exact the same configurations on another
workstation, enter the following command via command prompt with
administrator privileges.
Enter the whole command to the same line.
E:\Romexis\setup.exe /s /SMS
/f1"<RECORD_FILE_PATH>romexis_installation.iss"
Replace the <RECORD_FILE_PATH> with the path you saved the record
file.
The installation starts silently. You can monitor when the installation is
finished with Windows Task Manager. If any InstallShield processes are
running, the installation is still running.

NOTE
Make sure that all the workstations on which you are installing Romexis
meet the requirements set in the beginning of this manual (e.g.
required .NET frameworks etc.).

NOTE
Additional dialogs may appear if previous Romexis installations in the
workstation differ from the workstation the recording was made. Dialogs
may also appear if device drivers are included in to the installation.

5.8 Post-installation configurations on Windows

In this chapter, instructions how to set up and configure different Romexis
system components, features and interfaces (such as DIDAPI, TWAIN

32 Romexis Technical manual

 5 Installing Romexis on Windows

interface, PMBRIDGE interface, DICOM interface etc.) after installing

Romexis on Windows operating system (OS).

5.8.1 DIDAPI configuration

For more information on DIDAPI configuration, see the Didapi configuration
tool manual.

5.8.2 TWAIN interface configuration

TWAIN interface
TWAIN is a cross-platform interface for acquiring images captured by
scanners, digital cameras or frame grabbers. The manufacturer of the
TWAIN device must provide a Source Manager and TWAIN Data source
for your device to work with the Romexis.
Romexis supports the current TWAIN_32 standard. Refer to your
device manufacturer’s documentation for information on the availability of
TWAIN_32 source interfaces.

NOTE
TWAIN Capture is supported only on Windows operating systems.

The settings for the used TWAIN sources must be defined in TWAIN Setup.
If several TWAIN sources are used, the TWAIN setup must be performed
once for each source.

Modifying TWAIN Setup settings

To configure the TWAIN Setup settings, follow the steps below.
1. Select a patient in the Romexis Patients module.
2. Start the 2D module.
3. Select File > Capture > TWAIN Setup.
4. Select the TWAIN source to be configured from the drop-down list.
5. Modify the TWAIN settings in the appearing window, see description of
the settings below.
6. When ready, click OK.

Technical manual Romexis 33

5 Installing Romexis on Windows

In the following, the TWAIN Settings are described.

TWAIN Settings

• Twain Launcher Settings

• Show Twain Launcher button in toolbar
A separate button can be assigned to the TWAIN source by selecting
this option.
If the check box is not selected, the TWAIN source will use the
general TWAIN Capture button.
• Text and Tooltip
Enter the name and tool tip text of the button in the fields
respectively.
• Icon
By clicking the button, you can select the icon for the Twain launcher
button.
• Default TWAIN Source Settings
• Wait for TWAIN driver Close
Specifies whether a Close command is expected from the TWAIN
driver to signal the end of scanning session. If disabled, only single
scan is expected to be received. When enabled, multiple scans can
be made in one session which are all returned in one batch when
the scanning dialogue is closed. If the scanner software is capable

34 Romexis Technical manual

 5 Installing Romexis on Windows

of scanning multiple images in one session this setting should be

enabled.
• Prefer Memory Transfer
Enables Memory Transfer instead of Native Transfer mode. Refer
to your scanner documentation for more information on supported
and/or preferred mode. For scanning colour images this option
should be enabled.
• Show TWAIN Launch Dialog
If this option is selected, a dialogue is shown when the scanner
software has been launched via TWAIN. On some lower end
systems showing the dialogue can take some time during which it
may be useful to notify the user of the process. Some virus scanning
software is also known to slow down the TWAIN launch.
• Show Import Dialog
Specify whether the Romexis image import dialogue should be
shown for each imported image. The image import dialogue allows to
choose image modality, specify tooth numbers, and crop or reorient
the image. If disabled each scan is imported with default settings and
modality is defined by the Default Image Type setting below.
• Use Study Selection
This option enables the imaging with Romexis Twain client straight to
a study. If this option is selected, the TWAIN imaging is started with
template selection window (see example below).

• Default Image Type

Specifies the default modality for scanned images.
• Default Orientation
Specifies the default orientation for scanned images.
• Default TWAIN Auto Import Settings
In some cases you need to configure TWAIN Auto Import Settings
to enable automatic import of images as part of the TWAIN capture.
Generally this is not required and you can safely ignore these settings.

TWAIN image preprocessing

TWAIN scans can be preprocessed using respective auto enhancement
settings in Romexis Configuration tool, see more in section "Twain Intraoral"
on page 126 .

TWAIN auto recovery

If the scanned images cannot be correctly imported to Romexis due to
a technical or a user error during the process, the Romexis will try to

Technical manual Romexis 35

5 Installing Romexis on Windows

recover the images in the beginning of the next scanning session. If scanned
images are available in the temporary folder (usually %temp% on Windows
computers) the Romexis will match the images with the patient for which
they were originally scanned to and ask the user how to proceed.
• If the patient currently open is the same as the patient to whom the
images were acquired a prompt with the following example text is shown
and the Romexis will proceed with importing the images to the patient.
TWAIN Capture
Previously scanned (3) image(s) that have not been
imported to Romexis found for this patient.
Images are imported now. After that please start
TWAIN scanning again!
• If a different patient is open Romexis informs the user of unprocessed
TWAIN scans and indicates to which patient ID the scans belong to. You
can continue working normally with the current patient. Once the correct
patient has been opened after and all images have been successfully
imported to the patient the prompt will stop appearing.
TWAIN Capture
Previously scanned (3) image(s) that have not been
imported to Romexis found for other patient(s) having
following external ID:
"2"
You may continue with this patient!

Removing TWAIN source configuration

To remove a TWAIN Setup settings for a configured TWAIN data source or
device, follow the steps below.
1. Select a patient in the Romexis Patients module.
2. Start the 2D module.
3. Select File > Capture > TWAIN Setup.
4. Select the TWAIN source to be configured from the drop-down list.
5. Click the Remove settings button to erase the settings for the selected
TWAIN source.
6. When ready, click OK.

NOTE
If a separate button has been assigned to the TWAIN source, the Romexis
Client must be restarted for the change to take effect.

5.8.3 PMBridge interface configuration

To support 3rd party software and their developers to integrate their
software, Romexis includes Practice Management (PMBridge) interface
standards and libraries.
PMBridge interface provides a simple way of data transfer between Romexis
and practice management software of another company. PMBridge functions
as a "bridge" and passes necessary patient information to Romexis and
images from Romexis to the third party software.
For integrators who do not need image transition from Romexis to practice
management software a lighter solution called DxStart is also available.

36 Romexis Technical manual

 5 Installing Romexis on Windows

The PMBridge configuration file PmBridge.ini is located in the Romexis

installation path:
\Planmeca\Romexis\pmbridge\Program

NOTE
For troubleshooting: A PMBridge log file is saved in the %programdata%/
Planmeca/Logs folder. In normal mode, patient information is not visible in
the log file.
Enable the debug mode in the PmBridge.ini file by adding
DEBUG_LOG=1. This displays the patient information in the log and should
be used only for troubleshooting purposes.
Note that the PMBridge logs are not removed automatically but should be
removed manually after troubleshooting the system.

1 User
2 Practice management software
3 Patient & practice database
4 PmBridge (data transfer)
5 Imaging software Romexis
6 Database (images)

5.8.3.1 Windows registry additions

The following path is added as following Windows registry entities' values:
C:\Program Files\Planmeca\Romexis\pmbridge
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVer
sion\App Paths\Dimaxis.exe (Value Name: Path)
HKEY_LOCAL_MACHINE\SOFTWARE\Planmeca\Romexis (Value Name:
pmbridge)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Window
s\CurrentV ersion\App Paths\Dimaxis.exe (Value Name: Path)
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Planmeca\Romexis
(Value Name: pmbridge)

NOTE
According to PMBridge SDK instructions, practice management software has
to add the folder 'Program' to the path obtained from registry. That is why the
complete path is not found from the registry.

Technical manual Romexis 37

5 Installing Romexis on Windows

5.8.3.2 Users
PMBridge user group permissions can be altered to PMBridge user needs in
Romexis Admin Module. For more information see section "Adding/updating
group" on page 78.
Romexis installer creates a user group PMBridge Users and a user
PMBridge to Romexis database. When starting Romexis via PMBridge, the
respected user is automatically selected (Romexis.bat file's parameters
uid (user id) and pwd (password) found from the PMBridge installation
folder).

5.8.3.3 Enabling PMBridge connection

Steps
1. Start Romexis and click Admin button in the Romexis module tree.
2. Click the Connect.
3. On the PM Bridge icon, tick the Active chekbox, and fill in the appearing
PM Bridge configuration parameters.
Check that the PMBRIDGE Enabled option is enabled.
The default port number is 1501.

5.8.3.4 PMBridge with dynamic ports

To see a list of users connected using dynamic ports, go to File > License
Management > Port Info using credentials with administrator rights.

Clicking Clear ports button you can clear the list of used ports. Romexis
server also periodically cleans up the used port list automatically. Clean-up
is performed by comparing the active users list with the port info list.

If PMBridge initialisation fails due to a port problem, the next port is tried
once. The text ***RESERVED displays in the port list in such cases.
A message box displays in Romexis client if the reservation of both ports
fails and/or the initialisation of PMBridge fails. When the user clears the
message, Romexis client opens but PMBridge connection does not work.

38 Romexis Technical manual

 5 Installing Romexis on Windows

5.8.4 DICOM interface configuration

The DICOM interface can be configured in Romexis Admin module. For
more information, see section "DICOM" on page 85.

5.8.5 Installing Romexis implant library

Before you begin

Instead of installing the whole Romexis implant library package, it is
recommended to download and install selected implants and surgical kits
to the Romexis from the Romexis implant library, see more information in:
https://www.planmeca.com/software/software-modules/planmeca-
romexis-3d-implantology/implant-library/

About this task

This section describes the installation of Romexis implant library package
(from USB or downloaded zip-file) on Windows operating system.
The Romexis implant library currently contains implant data from over 120
manufacturers.

NOTE
The Romexis implant library installer Read Me file contains the most up-to-
date list of the implant manufacturers.

Steps
1. Locate Romexis Implant Library setup program (either on the delivered
USB flash drive or on the downloaded and extracted zip-file contents)
and start the upgrade by double-clicking.
Planmeca_Romexis_Implant_Library_<version>_Win\Win\se
tup.exe

2. Click Next.

Technical manual Romexis 39

5 Installing Romexis on Windows

3. In the License Agreement window, select the I accept the terms of the
license agreement and click Next.

4. You can browse the implant library Read Me file and to continue click
Next.

5. Select the implant libraries to be installed by checking appropriate boxes

and click Next.

40 Romexis Technical manual

 5 Installing Romexis on Windows

6. Check the boxes next to the databases to which you want to install the
new Implant Library.

The list of databases may vary depending on your setup.

NOTE
If the database in use does not appear on the list (e.g. solidDB), leave
the selection(s) unticked, and click Next > Install.
Separate SQL scripts for manual database update are in the Romexis
folder, to update the database manually see instruction in the end of this
section (What to do next part).
7. Click Next and Install.
8. You can open installation log file and/or the implant library Read Me file,
to quit the installation, click Finish.

Results
After the installation, verify that the installed implants can be seen in the
Romexis.
To check the list of implants, open Romexis 3D Module and click on the
Implant tab, then select Implant Library.

What to do next
If Romexis Implant Library setup did not include the database in use (it did
not appear on the list in Step 6), follow the steps below update the database
manually.
1. After installing the Implant Library (as described above), browse to
Romexis installation folder (C:\Program Files\Planmeca\Romexis
by default).
2. Scripts for manual installation are located in the folder corresponding
each supported SQL database type:
• sql (solidDB)
• sql.hsqldb (HSQLDB)
• sql.sqlsrv (SQLSRV)
3. Run the batch file all_implants.bat under the
sql.<database>\implants folder matching your database setup.
For example, in case of HSQLDB database, run the following bat-file.

Technical manual Romexis 41

5 Installing Romexis on Windows

C:\Program
Files\Planmeca\Romexis\sql.hsqldb\implant\all_implant
s.bat
4. After the installation, verify that the implants can be seen in Romexis
software.
To check the list of implants open Romexis 3D Module and click on the
Implant tab, then select Implant Library.

5.8.6 Database operations

5.8.6.1 Installing MS SQL Server Management Studio

The SQL Server Management Studio, a graphical tool for managing SQL
Server, is provided with Romexis delivery and can be separately installed, if
needed.

1. Insert Romexis software USB flash drive.

2. Browse to folder:
\Tools\SQL Server Management Studio
3. Start installation program.
SQLManagementStudio_x64_ENU.exe
4. Follow the instructions.

5.8.6.2 Setting up MS SQL Server Express backup

The following sections describe how to set up backups for Romexis MS SQL
Express by means of a scheduled execution of a Stored Procedure using a
batch file and Windows Scheduled Tasks service.
For backups on other database engines refer to their respective
documentation.

Configuration
When the Romexis installer deploys MS SQL Server onto the server
computer, it also creates a Stored Procedure in the Romexis instance
that provides a facility to make backups from the Romexis database, and
transaction logs.
To call the Stored Procedure a set of two SQL scripts and a batch file is
provided on the Romexis installation media in the \Tools\backup\ folder.
1. Copy the contents of the folder to an appropriate location such as:

42 Romexis Technical manual

 5 Installing Romexis on Windows

C:\Program Files\Planmeca\Romexis\backup\
2. Modify the following file as instructed in the inline comments:
romexis_db_backup.sql (to configure database backup settings)
The following settings are provided in the file and should be adjusted to
fit the local backup needs. “1” denotes true while “0” denotes false:
• @backupfldr = ’c:\romexis_images’
Folder to write backup to, a subfolder 'romexis_db' is automatically
created and used. This must be changed to point to a safe location
that is available for tape backup.
• @reportfldr = 'c:\romexis_cache’
As above but defines location for writing reports of the backup
process.
• @checkattrib = 1
Defines if new backups should have their archive bit set. The Stored
Procedure will automatically delete backups older than defined by
dbretainunit UNLESS the files have their archive bit set to true. If this
is left at “1”, the old backups should have their archive bit set to false
when they are backed up to another media to prevent the file system
from being filled with backups.
• @dbretainunit = 'months'
Defines the period for which the backups should be preserved before
automatic deletion. Can be: minutes | hours | days | weeks | months |
copies.
• @dbretainval = 2
Specifies how many dbretain units to keep old backups.
• @rptretainunit = 'copies'
Defines the period for which to retain reports for. Can be: minutes |
hours | days | weeks | months | copies.
• @rptretainval = 30
Specifies how many rptretainunits to keep reports.
• @report = 1
Flag to indicate whether to generate reports or not.

Setting up scheduled backup

NOTE
Remember to test the backup functionality after creating the task.

Use the Windows Scheduled Tasks service to setup a daily backup event as
follows.
1. Open Control Panel.
2. Select System and Security > Administrative Tools.
3. Browse and open Task Scheduler.
4. From the Actions, click the Create Basic Task....
Proceed with the Scheduled Task Wizard and choose Browse to select
the program.
5. Enter basic information for the task.

Technical manual Romexis 43

5 Installing Romexis on Windows

6. From the Trigger options select Daily.

7. Specify a convenient start time to run the backups, such as after
midnight when there is no other activity.
8. In Action phase, select Start a program.
9. To the Program/script field browse the run_romexis_backups.bat
file. E.g.:
C:\Program
Files\Planmeca\Romexis\backup\run_romexis_backups.bat
10. Click Finish.
11. Test the created task carefully before taking into use.

5.8.6.3 Transferring and merging databases

Romexis Database tool can be used for transferring or merging database
from one location to another. For example, in case the client wants to
change database from MS SQL to Firebird or vice versa, or merge two
different databases.
If the database is moved to a new location with the same database
management system as previously used, there is no need to use Database
tool. In such case there are other ways to move the database and images to
the new location.

NOTE
The source and destination databases need to be updated to the same
Romexis software version.

NOTE
Create a backup of the original database and the keyvault.p12 file before
using the Database tool.

NOTE
If the Implant Library has been installed to either of the databases (source or
target) install the newest Implant Library to the target database after merging
the source database into an existing database.

5.8.6.4 Exporting source database

1. Ensure that Romexis Service is NOT running.

NOTE
Before shutting down Romexis Service, it is recommended to shut down
other processes and executable files not needed, to ensure the database
tool has sufficient amount of free memory.
2. Go to Romexis installation media folder:
/tools/database_tool/
3. Start Romexis Service for Database tool by launching the following script
as administrator user.
start_romexis_server_for_database_tool.bat

44 Romexis Technical manual

 5 Installing Romexis on Windows

TIP
The default memory setting is -xmx5000m. If transferring a large
database it might be necessary to increase the amount by editing the
bat-file.
4. Start the Database tool for export, launch the following script:
export_romexis_database.bat
The Database tool checks if all the image paths are the same, and
displays prompt pop-ups.

Click OK.

NOTE
If the paths are not the same, the Database tool raises a warning.

The Database tool export window opens.

• Choose the media/folder where to export the database files to the

Export database tables to a folder field.
• Optionally, select the media/folder where to save the log file in Log
file path field. If left empty no log file is created.
5. Start export by clicking Export files.
When export is completed the following message appears:
Tables were serialised to file X.
6. Close Database tool.
7. Copy the output folder containing the *.serial files to the media that
will be used to move the database to another system (if the folder is not
there already).

Technical manual Romexis 45

5 Installing Romexis on Windows

8. Copy the Romexis image file folders into the same folder with the
*.serial files:
c:\romexis_cache
c:\romexis_ergodata
c:\romexis_images

NOTE
The database transfer tool renames imported duplicate usernames and
device names.

NOTE
A statistics window is shown at the end of a merge/import and an export.
This page shows the amount of exported or imported lines in each table.
Also renamed duplicate user names and duplicate device names are listed.

5.8.6.5 Importing data to target database

Before importing the data, make a new Romexis installation under the same
version that was in use when exporting the data.

NOTE
If merging two databases together, start from the Step 5 below.

1. Ensure that Romexis Service is NOT running.

2. Attach the source database export media to the target system.
3. Go to Romexis installation media folder:
/tools/database_tool/
4. If transferring, i.e. not merging databases, remove all lines from each
table in the target database and reset the tables’ indexing to zero by
running the following script.

NOTE
Do not run the script if merging two databases together! The script will
empty the target database.
\clear_target_database.bat

NOTE
This script can be run only once. If it is ran twice the database indexes
get corrupted and have to be re-installed.
5. Start Romexis server for Database tool by launching the following script
as administrator user.
start_romexis_server_for_database_tool.bat

46 Romexis Technical manual

 5 Installing Romexis on Windows

6. Start the Database tool for import, launch the following script:
import_romexis_database.bat

1. Choose the location of serialised (*.serial) files in the Import

tables from folder to database field.
2. Select which database you are importing to.
The available selections are MS SQL, Firebird or Other.
3. In the Do you want to inspect the target tables primary key indexes
for gaps? field, you can choose to identify and fix issues with
database sequences before importing.
The options are Inspect indexes, Inspect and try to fix indexes (Only
with MS SQL or Firebird) and Ignore indexes. The results are printed
in the log file.
4. Choose the parent location for the romexis_images and
romexis_cache in the local system.
This field is predefined if the path is found from the local Romexis
database.
5. Choose the parent location for the romexis_images and
romexis_cache in the original system.
This field is predefined when the location of the files to be imported is
selected.
6. Select the Merge duplicate patients (Person table) option to enable
patient merging.
Patient merging is done using external ID of the patient. Inactivated
patient images will also be taken into account.
Important: Only use the Merge duplicate patients (Person table)
option if you are certain the merged databases do not contain
identical external_id data for different patients. If two databases
use the patients’ unique social security numbers as external_id,
for example, the function should be safe to use.
7. Optionally, select the media/folder where to save the log file in Log
file path field. The log file path is predefined according to the Import
tables from folder to database field. If left empty no log file is created.

Technical manual Romexis 47

5 Installing Romexis on Windows

7. Start the import by clicking the Import files button.

NOTE
This may take from few minutes to few hours depending on the size of
the imported database.

When the serialisation is completed the following message appears:

Files were de-serialized to database
8. Open Romexis client and verify that the database has been successfully
moved to the new computer.
9. If the implant library has been installed to either of the databases (source
or target) install the newest Implant Library to the target database after
merging the source database into an existing database, see section
"Installing Romexis implant library" on page 39.

NOTE
As an alternative to the Merge duplicate patients (Person table) option, use
the Romexis patient merge module after the database merge procedure. For
more information, see section "Patient Merge" on page 83.

5.8.7 Configuring Romexis client and server settings

There are quite a few additional configurations to be made to the Romexis
client and server settings. In here some of them are listed.
• Configure the Romexis server/client settings e.g. to enable image
capturing with the devices to be used with the Romexis client.
See section "Local Settings" on page 71.
• Configure Romexis server and unit connections.
See section "Romexis server and unit connection configuration" on page
156.
• Configure Clinic Management module (optional) configuration.
See section "Clinic Management configuration" on page 190.

5.9 Uninstalling Romexis

The uninstall of Romexis removes Romexis server and client applications
and related short-cuts and folders. External components that are installed
during the installation, such as MS SQL Server etc., are not removed as well
as he Romexis Database and image files are not removed.

NOTE
It is recommended that you uninstall Romexis only if Romexis is no longer
used on the respective workstation.

The uninstall can be started from Windows Settings > Apps, by selecting
Romexis components from the Apps & features list, and clicking Uninstall.
Depending on the Romexis installation type/options, remove the following
components (if existing):
• Design Center
• Design Center Tooth Library
• Planmeca VDDS Interface
• Romexis

48 Romexis Technical manual

 5 Installing Romexis on Windows

• Romexis 3D Ortho Studio

• Romexis Cephalometric Analysis Module

5.10 Troubleshooting
After installation, start Romexis and test that the installation has succeeded.
In the following, possible problems are described and instructions to correct
the problem are given.

5.10.1 Broken font in Korean language Romexis on Windows 10

When installing Romexis with Korean language option on Windows 10
operating system, texts/font in Romexis might be corrupted, that is,
displayed e.g. with boxes or questions marks.
If this is the case, set the region and language setting on Windows as
follows:
1. Go to Settings > Time & language > Language.
2. Select Add a language.
3. Select the language from the list, then choose which region's version you
want to use.
Your download will begin immediately.
4. After installation, test that the font in Romexis shows correctly.

5.10.2 Romexis client connection to Romexis server fails

If Romexis client (Windows) does not connect to the Romexis server
on macOS, check that the external IP address of the Romexis
server is configured to the parameter SERVER_RMI_HOSTNAME of
the file romexis_server.properties in the folder C:\Program
Files\Planmeca\Romexis\sconfig.

Technical manual Romexis 49

6 Installing Romexis on macOS

6 Installing Romexis on macOS

This chapter includes instructions on how to install, upgrade and uninstall
Romexis software on macOS operating system. In addition, the chapter
contains instructions how to set up and configure different Romexis system
components on macOS.

NOTE
When upgrading Romexis from release 4.6.2 or older, it is recommended to
upgrade first to the version 5.3.5 before upgrading to 6.x.x release.

6.1 Requirements (macOS)

6.1.1 System requirements

Check that the system requirements, listed in section "System requirements"
on page 4, are met.

6.1.2 User requirements

The required user account type during installation is Administrator. Change if
needed, according to the following steps.

Changing user account type to Administrator

1. Start System Preferences from Dock and open Accounts section from
the bottom of the window.
2. Click on the lock in the lower left corner of the Accounts window to make
changes, and give password if asked.

3. From My Account list select the user to use Romexis software and tick
the Allow user to administer this computer box.
4. Click Click the lock to prevent further changes icon in the lower
left corner of the window to prevent any future changes without
authentication.

6.1.3 Known issues

Some MacBook Pro graphic cards might experience problems with Romexis
3D X-Ray Rendering. In such situation Romexis Surface Rendering should
be used, see more information from Romexis user’s manual.

50 Romexis Technical manual

 6 Installing Romexis on macOS

6.1.4 Device support

The following components are NOT currently supported on macOS:
• Dental unit serial communication
• Dimax Tool
• TWAIN
• Quick Launch
• DxExport / DxLoader

6.2 Installing/upgrading Romexis on macOS

About this task

Romexis installation package for macOS does not install any software from
the imaging system release package, e.g. DidapiKit or Device Tool(s). To
install or update imaging system software, see the instructions in Imaging
System Updater manual.

Steps
1. Locate Romexis installation package (either on the delivered USB flash
drive or on the downloaded and extracted zip-file contents).

2. Start the install/upgrade by double-clicking the Planmeca

Romexis.pkg and click Continue.

Technical manual Romexis 51

6 Installing Romexis on macOS

3. Read the Software License Agreement and to continue, click Continue.

Additionally, you can Print or Save the agreement for later use.
4. Click Agree to continue (or Disagree to cancel).

5. Select the language and country.

NOTE
The Country selection is not shown when upgrading the Romexis
software.

52 Romexis Technical manual

 6 Installing Romexis on macOS

6. Select Romexis components to be installed and click Continue.

The options listed below the figure.

• Romexis stand-alone installation (inc. server and client):

• Romexis Server
• Romexis Database
• Romexis Client
• Romexis server installation:
• Romexis Server
• Romexis Database
• Romexis client installation:
• Romexis Client
7. Click Install.

Technical manual Romexis 53

6 Installing Romexis on macOS

8. Type the Name and the Password and click Install Software.

NOTE
Administrator authentication is needed to start the installation.

9. After successful installation, click Close.

6.3 Installing Romexis license on macOS

About this task

To install the license, perform the following steps during Romexis start-up.
If Romexis does not detect an installed license, a 30 day trial period is
provided.

Steps
1. Click Install license button in the dialog.

To continue using Romexis without a license, press the Continue Trial

button.

54 Romexis Technical manual

 6 Installing Romexis on macOS

2. Browse to and select the license file.

The license is separately provided when purchasing Romexis.

3. Click Open.
4. Click OK.

5. Restart Romexis.

What to do next
Once the license is installed, you must activate it. For more information, see
section "Activating Romexis license" on page 55.

6.4 Activating Romexis license

The functions in Romexis application are controlled by license and user
rights. In order to use the application the license must be activated. See
instructions in section "Activating Romexis license" on page 23.

6.5 Configuring Romexis client

After installing Romexis software as a client, check and modify few settings
in the client installation.
1. Browse to folder:
/Applications/Planmeca/Romexis/

Technical manual Romexis 55

6 Installing Romexis on macOS

2. Click on the file Romexis.app at the same time pressing down the CTRL
button (alternatively you can click the right mouse button), and select
Show Package Contents.

3. The application packet contents will be displayed in Finder as folder

structure.
4. Browse to folder:
Contents/MacOS
5. Open the Romexis file for editing.

NOTE
The file might open with different program depending on the installed
applications in the computer.
6. Edit the following settings in the file:
• Change the host parameter value to localhost or to the Romexis
server IP address. For example:
host=localhost
• Check and modify (if necessary) the -Xmx parameter according
to the computer’s system memory. Check the relevant Romexis
software technical bulletin for the suggested -Xmx amounts.
7. After completing the modifications, save the changes (File Menu > Save)
and Exit.
8. Start Romexis by double-clicking the Romexis.app application packet.

56 Romexis Technical manual

 6 Installing Romexis on macOS

6.6 Configuring Romexis server

After installing Romexis software as a server, check and modify a few
settings in the client installation.
1. A default Romexis server installation is single client standalone system
(RMI Server Host: 127.0.0.1).
If networked clients are required, configure the RMI Server Host in
Romexis Configuration tool to match the Romexis server workstation IP
address.
For more information, see section "Server" on page 149.
2. To change the amount of memory allocated to the Romexis server
application, edit the parameter -Xmx in the file:
/Applications/Planmeca/Romexis/server
/Romexis/Server.sh

6.7 DIDAPI configuration

For more information on DIDAPI configuration, see Didapi configuration tool
manual.

6.8 Starting Romexis server

1. Browse to the folder:
/Applications/Planmeca
2. Start Romexis server by double-clicking on the file Start Romexis
Server.app.

NOTE
Starting Romexis server requires Administrator user account. For more
information, see section "User requirements" on page 50.
3. Type your username and password and click OK.

Romexis Server is started as a service, which means that it is started

automatically at every boot. The server can be stopped by double-clicking
the file Stop Romexis Server.app.

6.9 Setting up Romexis backup

To backup database file and image files, organize a backup of the following
folder and its sub-folders at the Romexis server computer:
/Applications/Planmeca/Romexis/database
Shut down Romexis server before copying database files or initiating macOs
Time Machine backup, to prevent possible database corruption. The Firebird
database does not support Volume Shadow Copy technology.
To make a full backup of Romexis software, organize a backup of the
following folder and its sub-folders of the Romexis server computer:

Technical manual Romexis 57

6 Installing Romexis on macOS

/Applications/Planmeca
To backup DIDAPI configurations, make a backup of the following folder:
/Library/Preferences/DIDAPI

NOTE
If the image folders' locations have been changed manually in Romexis
Configuration tool, backup the new folders and their subfolders in addition to
the default ones.

6.10 Database operations

6.10.1 Squirrel SQL Database client

The Squirrel SQL Database client can be used to run queries to Romexis
database.

Installation
The installation packet is located in Romexis installation media, in folder:
/tools/database/Squirrel SQL Client/
with the jdbc driver jaybird-full-2.1.6.jar file for the database.
1. Install the software by double-clicking on the installation package.
2. During the installation, select Optional Plugin for Firebird.

Configuration
1. Copy the jdbc driver for Firebird from Romexis installation media to the
workstation, e.g. to the folder:
/Applications/Planmeca
2. Launch the Squirrel by double clicking on the SQuirreLSQL application
packet in the folder:
/Applications
3. In the Drivers tab, double-click the Firebird Jaybird on the driver list.
4. Set Example URL to:
jdbc:firebirdsql://localhost//Applications/Planmeca/
Romexis/ database/romexis.fdb
5. Go to Extra Class Path.
6. Select Add, browse and select the jdbc driver file you just saved and
click Choose.
7. In the Class Name field, enter:
org.firebirdsql.jdbc.FBDriver
8. Go to Aliases tab and select Create New Alias.
9. Add a name for the connection, e.g. Romexis Database.
10. Select Firebird Jaybird driver from the driver list.
11. Set sysdba as the user and pwr0mex! as the password.
12. Connect to the database.

58 Romexis Technical manual

 6 Installing Romexis on macOS

6.10.2 Transferring and merging databases

Romexis Database tool can be used for transferring or merging database
from one location to another. For example, in case the client wants to
change database from MS SQL to Firebird or vice versa, or merge two
different databases.
If the database is moved to a new location with the same database
management system as previously used, there is no need to use Database
tool. In such case there are other ways to move the database and images to
the new location.
Patient merging is done using external ID of the patient. Also inactivated
patients’ images will be taken into account.

NOTE
When merging databases together, identical patients in different databases
are not merged together by database tool.

NOTE
The source and destination databases need to be updated to same Romexis
version.

NOTE
Create a backup of the original database and the keyvault.p12 file before
using the Database tool.

NOTE
If realistic implants, crowns or STL imports have been added to the source
database's images, the folder /Planmeca/Romexis/geometries and all
its subfolders have to be copied to the target server computer.

6.10.3 Exporting files from one database to another

NOTE
A statistics window is shown in the end of a merge/import and an export.
This page shows the amount of exported or imported lines in each table.
Also renamed duplicate user names and duplicate device names are listed.

NOTE
Before starting shut down Romexis server.

NOTE
It is recommended to shut down other processes and executable files not
needed to ensure the database tool has sufficient amount of free memory.

1. Go to Romexis installation media, folder:

/tools/database_tool/
2. Start Romexis Service for Database tool by launching the following
script:
start_romexis_server_for_database_tool
Start the Database tool for export, launch the following script:
export_romexis_database

Technical manual Romexis 59

6 Installing Romexis on macOS

The Database tool checks if all the image paths are the same, and
displays prompt pop-ups.

Click OK.

NOTE
If the paths are not the same, the Database tool raises a warning.

The Database tool export window opens.

• Choose the media/folder where to export the database files to the

Export database tables to a folder field.
• Optionally, select the media/folder where to save the log file in Log
file path field. If left empty no log file is created.
3. Start export by clicking Export files.
When export is completed the following message appears:
Tables were serialised to file X.
4. Close Database Tool.
5. Copy the output folder containing the *.serial files to the media that
will be used to move the database to another system (if the folder is not
there already).
6. Copy the Romexis image file folders into the same folder with the
*.serial files:
/Application/Planmeca/Romexis/database/romexis_cache
/Application/Planmeca/Romexis/database/
romexis_ergodata
/Application/Planmeca/Romexis/database/romexis_images

6.10.4 Importing database from one location to the other

NOTE
An Admin user account is required.

60 Romexis Technical manual

 6 Installing Romexis on macOS

NOTE
The database transfer tool renames imported duplicate usernames and
device names.

NOTE
If merging two databases together start from Step 4 below.

Moving an old database to a new computer with empty database

Make a new Romexis installation under the same version that was in use
when exporting the data.

NOTE
Before starting make sure Romexis server is NOT running.

NOTE
Do not run the script if merging two databases together! The script will empty
the target database.

1. Go to Romexis installation media folder:

/tools/database_tool
2. Remove all lines from each table in the target database and reset the
tables’ indexing to zero by running the following script by double-clicking
it:
clear_target_database
3. Enter admin user password.

NOTE
This script can be run only once. If it is run twice the database indexes
get corrupted and have to be re-installed.
4. Stop Romexis service.
5. Start Romexis server for Database tool by launching the following script:
start_romexis_server_for_database_tool

Technical manual Romexis 61

6 Installing Romexis on macOS

6. Start the Database tool for import, launch the following script:
import_romexis_database

1. Choose the location of serialised (*.serial) files in the Import

tables from folder to database field.
2. Select which database you are importing to.
The available selections are MS SQL, Firebird or Other.
3. In the Do you want to inspect the target tables primary key indexes
for gaps? field, you can choose to identify and fix issues with
database sequences before importing.
The options are Inspect indexes, Inspect and try to fix indexes (Only
with MS SQL or Firebird) and Ignore indexes. The results are printed
in the log file.
4. Choose the parent location for the romexis_images and
romexis_cache in the local system.
This field is predefined if the path is found from the local Romexis
database.
5. Choose the parent location for the romexis_images and
romexis_cache in the original system.
This field is predefined when the location of the files to be imported is
selected.
6. Select Merge duplicate patients (Person table) option to enable
patient merging. Patient merging is done using external ID of the
patient. Inactivated patient images will also be taken into account.
7. Optionally, select the media/folder where to save the log file in Log
file path field. The log file path is predefined according to the Import
tables from folder to database field. If left empty no log file is created.
7. Start the import by clicking Import files.

NOTE
This may take between a few minutes and a few hours depending on the
size of the imported database.

When the serialisation is completed the following message appears:

62 Romexis Technical manual

 6 Installing Romexis on macOS

Files were de-serialized to database

8. Close Database Tool.
9. Open Romexis client and verify that the database has been successfully
moved to the new computer.

NOTE
As an alternative to the Merge duplicate patients (Person table) option, use
Romexis patient merge module after the database merge procedure. For
more information, see section "Patient Merge" on page 83.

Merging source database into an existing database

Go through the steps from Step 5 to Step 9 in the previous procedure.
If the implant library has been installed to either of the databases (source or
target) install the newest Implant Library to the target database after merging
the source database into an existing database.

6.11 Installing Romexis implant library

Before you begin

Instead of installing the whole Romexis implant library package, it is
recommended to download and install selected implants and surgical kits
to the Romexis from the Romexis implant library, see more information in:
https://www.planmeca.com/software/software-modules/planmeca-
romexis-3d-implantology/implant-library/

About this task

This section describes the installation of Romexis implant library package
(from USB or downloaded zip-file) on macOS operating system.
The Romexis implant library currently contains implant data from over 120
manufacturers.

NOTE
The Romexis implant library installer Read Me file contains the most up-to-
date list of the implant manufacturers.

Steps
1. Locate Romexis Implant Library installation package (either on the
delivered USB flash drive or on the downloaded and extracted zip-file
contents).
2. Double-click on the installation package Planmeca Romexis Implant
Library.pkg to start the installation.
3. Proceed through the installation steps and give the Administrator
password when requested.

Results
After the installation, verify that the realistic implants can be seen in the
Romexis.
To check the list of implants, open the Romexis 3D Module and click on the
Implant tab, then select Implant Library.

Technical manual Romexis 63

6 Installing Romexis on macOS

In order to uninstall Romexis Implant Library implants, double-click

on the application file Uninstall Planmeca Romexis Implant
Library.app, which is located in the installation root folder next to
the .pkg.

6.12 Setting Romexis client to start at login

About this task

To set Romexis client to start every time someone logs into the computer,
follow the steps below.

Steps
1. Create a shortcut to Romexis application into the Dock.
Drag the Romexis.app application icon from the folder /
Applications/Planmeca to the Dock.

2. Place the mouse cursor on top of the Romexis shortcut icon in the Dock.
3. Press and (hold down) the right mouse button.
From the appearing Options menu select Open at Login.

6.13 Configuring intraoral camera support

In order to control the intraoral camera with foot pedal Planmeca Sovereign,
Planmeca Sovereign Classic and Planmeca Compact i V2 dental units need
to be connected to the Romexis server using a local Ethernet network.
For more information on configuring intraoral camera for foot pedal use, see
section "Configuring intraoral camera" on page 181.

6.14 Configuring Romexis client and server settings

There are quite a few additional configurations to be made to the Romexis
client and server settings. In here some of them are listed.
• Configure the Romexis server/client settings e.g. to enable image
capturing with the devices to be used with the Romexis client.
See section "Local Settings" on page 71.
• Configure Romexis server and unit connections.

64 Romexis Technical manual

 6 Installing Romexis on macOS

See section "Romexis server and unit connection configuration" on page

156.
• Configure Clinic Management module (optional) configuration.
See section "Clinic Management configuration" on page 190.

6.15 Troubleshooting

6.15.1 Romexis client connection to Romexis serverfails

If Romexis client (macOS) does not connect to the Romexis server on
macOS, check that the external IP address of the Romexis server is
configured to the parameter RMI Server Host in the Romexis Configuration
tool Server tab.

Technical manual Romexis 65

7 Admin module tasks and settings

7 Admin module tasks and settings

7.1 Starting Admin module

About this task

The Admin module contains a set of settings for Romexis application system
administration.

Steps
1. Start the Romexis.
In Windows Start menu, select Planmeca > Romexis.
2. Click the Admin button in the Romexis module tree.

The Admin module is divided into the following categories:

• Connect
• Settings
• Local Settings
• 2D Imaging
• 3D Imaging
• Automatic Image Import
• CAD/CAM
• CD-Recording Device
• Dental Unit
• DICOM
• User management
• Users
• Groups
• Patient Merge
• DICOM
• Security
• Templates
• Device Alerts

66 Romexis Technical manual

 7 Admin module tasks and settings

7.2 Connect
In the Admin module Connect view you can select which connections/launch
buttons are available in the Romexis.

By clicking the category buttons on top of the Connect view, the list of
application icons can be narrowed to contain only the application of the
selected category (based in which Romexis module the button is visible if
activated).
• 2D - 2D module
• 3D - 3D module
• CAD/CAM - CAD/CAM module
• File - File module
To activate a connection/launch button select the appropriate Active
checkbox.
Some connections/launch buttons have separately configurable parameters,
on those icons there is Configure button.

NOTE
To enable the changes in the Connect view, restart the Romexis.

In the following, the connections/launch buttons are briefly described and

references to the activation and configuration are given.

Applications and connections

• Romexis Cloud
The Romexis Cloud image transfer service allows Romexis software
users to share images and expertise with patients and colleagues.
To enable the button in the Romexis, tick the Active chekbox. For more
information on creating the Romexis Cloud connections, see section
"Cloud" on page 130.

Technical manual Romexis 67

7 Admin module tasks and settings

• DDX Cloud
The DDX Cloud allows sending images and scans from Romexis directly
to DDX Cloud portal. A new case can be created to DDX Cloud. Images
can also be added to existing/open DDX cases. There is also possibility
to Import cases from DDX to Romexis.
To enable the button in the Romexis, tick the Active chekbox. For more
information on creating the DDX Cloud connections, see section "DDX
Dental" on page 131.
• PM Bridge
PMBridge in an integration library to
• Pass patient information to Romexis and have Romexis create or
update the patient in its database.
• Orchestrate Romexis client to show on top etc.
• Retrieve image thumbnails and full image files.
To enable the PMBridge, tick the Active chekbox. For more information
on setting the application parameters, see section "PMBridge interface
configuration" on page 36.
• Generic 2D launch
Allows creating button to 2D module which launches 3rd party 2D
application with patient data and exported image(s).
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• Generic 3D launch
Allows creating button to 3D module which launches 3rd party 3D
application with patient data and exported the image(s).
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• Romexis OrthoStudio
The button opens OrthoStudio software and exports automatically
patient information and intraoral scans from Romexis.
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• 3D Diagnostix service
Allows Romexis users order radiology reports and surgical guide
directly from 3D module. Hardcoded order form and CBCT images are
automatically sent to 3D Diagnostix ftp-server.
To enable the button in the Romexis, tick the Active chekbox.
• Dolphin launch
The button opens Dolphin software, exports automatically patient
information and CBCT (with ProFace and STL mapped).
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• 360 Imaging service

68 Romexis Technical manual

 7 Admin module tasks and settings

Allows Romexis users order radiology reports and surgical guide directly
from 3D module. Hardcoded order form in Romexis and CBCT images
are automatically send to 360 imaging ftp -server.
To enable the button in the Romexis, tick the Active chekbox.
• Nobel Clinician launch
The button opens NobelClinician software, exports automatically patient
information and CBCT image from Romexis.
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• coDiagnostiX launch
The button opens CD software, exports automatically patient information
and CBCT image from Romexis.
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• PlanCAD Premium launch
The button opens PlanCAD Premium software, exports automatically
patient information and scans from Romexis.
To enable the button in the Romexis, tick the Active chekbox. For
more information on setting the application parameters, see "Configuring
application launch" on page 70.
• PlanCAD Premium export
To enable the button in the Romexis, tick the Active chekbox.
• HeySmile export
The button exports the selected case and opens the HeySmile online
platform.
To enable the button in the Romexis, tick the Active chekbox.
• exocad export
The button enables the export in ExoCad format.
To enable the button in the Romexis, tick the Active chekbox.
• Sim to Care export
The button allows sending scans from ModelAnalyser module directly to
the SIMtoCARE server.
To enable the button in the Romexis, tick the Active chekbox, and fill in
the API entry point for the application.

• 3Shape export
The button enables the export in 3Shape format.
To enable the button in the Romexis, tick the Active chekbox.
• Generic Lab portal

Technical manual Romexis 69

7 Admin module tasks and settings

Add the application as described in section "Configuring application

launch" on page 70 and fill in the necessary properties.
• TruAbutment Cloud
Allows user to send scans to TruAbutment and order custom abutments.
TruAbutment send button uses Romexis Cloud service with customised
Romexis dialog.
To enable the button in the Romexis, tick the Active chekbox.

7.2.1 Configuring application launch

Steps
1. Start the Admin module.
See section "Starting Admin module" on page 66.
2. Click the Connect tab.
3. Click the Configure button on Generic 3D launch icon.
4. Tick the Active chekbox of Generic 2D launch or Generic 3D launch.
5. If the Select Application ... list already includes a predefined settings for
the application, select the option, if not, click the Add button.
6. Click the (…) button to browse and select the appropriate executable.
7. Set the application properties and parameters.

• Name
Descriptive tool tip for Launch icon shown in Romexis user interface.
It is possible to configure multiple launch targets for user to choose
from.
• Command Line (write to the field or click Add Item button)
The following command line values or data to be passed to the
called executable:
%P Patient ID, internal non-continuous automatic ID used by some
customers
%E External ID, as provided by the customer organisation
%I Other ID, additional secondary ID usually via migration or
integration
%F First Name of patient
%L Last Name of patient
%D Date of Birth, localised

70 Romexis Technical manual

 7 Admin module tasks and settings

%U Date of Birth Unformatted, YYYYMMDD

%O Output Filename, path to a temp file
%S List of Output files
%T Dolphin Quick Launch /FACESCAN AND /*_ARCH, datasets in
predefined format.
• 3D Export (visible only for 3D related applications)
Specify how objects should be exported.
For quick launch with CBCT only, select option:
• Export Volume in Multi Frame Format
For quick launch with CBCT and ProFace image, select options:
• Export Volume in Multi Frame Format
• Include ProFace (.OBJ)
For quick launch with CBCT, ProFace image and upper/lower
intraoral scan STL files, select options:
• Export Volume in Multi Frame Format
• Include ProFace (.OBJ)
• Include IO-Scan fitted to Volume

NOTE
The launch feature requires that the receiving software is capable of
receiving file and patient information via the command line. For more
information, see the 3rd party documentation for correct parameters.
8. Click the OK button.
9. Make sure the created application is selected and click the OK button.
10. Restart Romexis.

7.3 Local Settings

In the Local Settings tab you can set various settings and parameters for the
Romexis.
The settings are divided into the following categories:
• 2D imaging
• 3D imaging
• Automatic Image Import
• CAD/CAM
• CD-Recording Device
• Dental Unit
• DICOM
The Local Settings has the following buttons.
• Restore
Restores the settings to the previously saved values.
• Set As Global Defaults
To specify the settings made on the current workstation as global default
values on all new workstations that log in to the same Romexis server
click the Set as Global Defaults button.

Technical manual Romexis 71

7 Admin module tasks and settings

The settings of those workstations that have already logged into

Romexis server at some point are not affected. Only the settings
modified by the user are affected. This feature is especially useful e.g.
for settings 3D Module Enabled on This Workstation and Image Capture
(DIDAPI) Enabled.
A confirmation dialogue is displayed before global defaults are applied.
• Save
Saves the changes made to the settings.

7.3.1 2D Imaging

• Image Capture (DIDAPI) Enabled

Enables the image capturing through the DIDAPI interface. Enabling this
setting requires that the DIDAPI is installed.
The setting is applied after restarting Romexis.
• Viso Image Capture (2D/3D) Enabled
Enables the image capturing with Planmeca Viso X-ray unit.
The setting is applied after restarting Romexis.
• ProScanner Capture Enabled
This setting enables captures with Planmeca ProScanner.
The setting is applied after restarting Romexis.
• ProScanner Application Folder
Defines the ProScanner application folder.
• ProScanner 2.0 / ProXam iP Capture Enabled
This setting enables captures with Planmeca ProScanner 2.0 and KaVo
ProXam iP imaging plate scanners.
The setting is applied after restarting Romexis.
• Image Reprocessing Enabled
This setting enables reprocessing of the exposures in certain modalities.
Reprocessing allows easy exploration of different DIDAPI pre-processing
settings and is therefore well suited for identifying optimal settings
during initial configuration of a X-ray device. A single exposure can
be processed multiple times with different DIDAPI configuration values

72 Romexis Technical manual

 7 Admin module tasks and settings

applied and returned to the Romexis each time as if it was a new

exposure.
The following images can be reprocessed.
• DIMAX3: pan, bw, sinus
• DIMAX4: all
• SmartPan *
• ProCeph
• ProSensor
*) To reprocess Planmeca Viso SmartPan images, disable the Viso
Image Capture (2D/3D) Enabled setting (as described earlier in this
section).
Check the required software versions from each device's own manual.
When the image reprocessing is enabled and panoramic exposure
is started, a DIDAPI ReProcessing dialogue is shown. The following
choices are available:
• ReProcess Latest Image
Returns the most recent real exposure as a new image with current
DIDAPI configuration applied.
• Choose Image to ReProcess
Select an existing image in Romexis for Reprocessing, apply current
DIDAPI configuration on it, and return the result as a new image.
• Launch DIDAPI Config
Launches DIDAPI Configuration tool for changing DIDAPI
preprocessing settings.
• Turn ReProcessing OFF
Turns OFF the Image Reprocessing Enabled setting in Admin / Local
Settings.
Reprocessing is usually used as follows:
1. Check DIDAPI Configuration that preprocessing settings are
enabled.
2. Expose an image of a patient or a test target.
3. Enable the Image Reprocessing in Admin > Local Settings.
4. Evaluate image and use DIDAPI Configuration to adjust
preprocessing to better match customer's preferences.
5. Start new exposure and choose Reprocess Latest Image.
The original image is returned with new preprocessing settings and
verify image quality. Repeat steps 4. and 5. until desired image
quality is achieved.
6. Turn Reprocessing off.
The setting is applied immediately, no need for restarting the Romexis.
• Rejecting Exposures is allowed
Allows user to cancel exposures during the exposure time.
• Intra Cam Image Import Enabled
Checking/unchecking this option determines whether the videos saved in
the shared folder are immediately retrieved and automatically saved as

Technical manual Romexis 73

7 Admin module tasks and settings

attachments to the currently open patient when intraoral camera capture

window is closed.
After closing the capture window, the captured intraoral video and
potentially other videos saved in the shared folder are added as
attachments to the patient and removed from the shared folder.
The supported video formats are mp4, avi, and mpg.
The setting is applied immediately, no need for restarting the Romexis.
• Import Intra Cam Folder
Defines the default shared folder where the intraoral camera videos
are saved and from where the videos are retrieved and saved as
attachments to the patient.
• Use External Video Application
By enabling this setting, the intracam activation button starts the external
application defined with the Generic 2D launch (see section "Connect"
on page 67).
The above explained Intra Cam Image Import Enabled and Import
Intra Cam Folder parameters can be used together with this external
application, to enable Romexis automatically retrieve the captured
images after closing the external application.
• Use Email app via RomexisClient.ini
Enables using an e-mail application defined in the
RomexisClient.ini file.
• ProX / ProXam iX Twain exposure values enabled
Enables ProX and ProXam iX Twain exposure values.
• Export All Default Folder
The default export folder is used when the option Export all images is
selected in the image browser of the Imaging module.
Export all images option can be selected in the Image Browser when
selecting the Image list browsing mode.
For more information, see Romexis user’s manual.

7.3.2 3D Imaging

• 3D Module Enabled on This Workstation

This setting enables the organisation to allow/deny access to the 3D
module per workstation.
• 3D Rendering Enabled
Enabling this function generates 3D rendered view in 3D module but
consumes more memory. This function should be disabled in image
capturing workstations.
• 3D Rendering Quality

74 Romexis Technical manual

 7 Admin module tasks and settings

This settings affects to the quality of the 3D rendered view (but not 2D
slices) by changing the size of which the 3D rendering is made.
Depending on the amount of CPU and display size, test and select
optimal value for the setting. The more quality is set, the more CPU is
required for smooth screen updates.
• Low
Max. size 256 x 256, lowest quality, recommended for low end
systems.
• Normal
Max. size 512 x 512, average quality.
• High
Max. size 768 x 768, high quality.
• Very High
Max. size 1024 x 1024, recommended only for high end systems.
• Use Low Quality Preview
When enabled the previews of 2D and 3D views are shown in low quality
when the views are manipulated.
• Reconstruction Server
The 3D reconstruction PC’s (Reco PC) Host Name (IP address) and Port
Number are defined here.

NOTE
In case of Planmeca Viso X-ray unit, it is possible to take exposures
even without defining the Reco PC IP-address in the Romexis
configuration, but for using Redo 3D Reconstruction or Artefact removal
functions the Reco PC IP-address must be defined.

7.3.3 Automatic Image Import

• Enable automatic image import

Enabling the automatic image import, the Romexis imports all images
found from the defined folder as photos for the currently opened patient.
You can either write the folder path or use the Browse button to select
the folder.
The following image formats can be imported: png, jpg, jpeg, tiff, jfif.
• Image directory
Defines the folder where the images are imported.
• Import notification
Defines if notification of the image import is displayed, options are:
• Do not show anything
No any notification is shown.

Technical manual Romexis 75

7 Admin module tasks and settings

• Show import window

Opens Romexis image import editor. In the editor, user can change
image type, rotate image or crop it before importing. If user selects
Cancel in the editor, the image will not be imported.
• Show notification window
A small notification dialog shows how many images were imported
and closes automatically in a short period.
• Delete images after import
By enabling this option, after a successful import the image file is deleted
from the folder.
• When patient is not selected, import images to next selected patient.
By enabling this option, if not patient is selected, the images are
imported to the next selected patient.
To activate changes in these settings, restart the Romexis client.

7.3.4 CAD/CAM

• 3D Printer Export Folder

Defines the folder where the STL model bases are exported when using
the 3D Print in the Model Analyser module.

7.3.5 CD-Recording Device

• Device Bus
Specify device bus where the CD recording device is located. Modify this
setting only if the AUTOMATIC setting doesn’t work.
• Log CD-burn
If enabled, system writes a log of the CD-writing process for
troubleshooting purposes.

76 Romexis Technical manual

 7 Admin module tasks and settings

7.3.6 Dental Unit

• Paired unit
• Connect to Dental Unit at Startup
Defines if the dental unit connection is made during the Romexis
startup.
• Select Dental Unit
Select the dental unit from the drop-down menu.
• PlanScan Control
• Port Number
Defines the port number.
• Remote TouchPad and Keyboard control
• Enable remote control
Enables the Remote TouchPad and Keyboard control option.
• Port Number
Defines the port number.
• Solanna Vision
• Select Device
From the drop-down menu, the used Solanna Vision device on the
Romexis client can be selected. That is necessary if Solanna Vision
is used in a standalone mode, without a supporting dental unit.
With Automatically option (default) the Solanna Vision device is
selected automatically based on which dental unit the Romexis client
is connected.
• Port Number
Defines the port number.
• Self Check Port
Defines the self check port.
• Intra Cam Serial Connection (CamComm)

Technical manual Romexis 77

7 Admin module tasks and settings

• CamComm Enabled
Enable this setting to enable intraoral video camera activation and
foot pedal automation in Romexis using standard Serial Connection.
• Com Port
This port needs to be specified correctly and is in most cases COM1.
Note that this requires the use of Planmeca Compact dental unit.

7.3.7 DICOM

These settings define the workstation specific DICOM identifiers.

• AE Title for this workstation
• Station Name
• Institution Name
• Institution Department Name

7.4 User Management

In the User Management > Users / Groups tab you can create user groups
and define user names, passwords and clinic names etc.
The Groups and Users tabs have the following buttons:
• Add
Click the Add button to add a new user or a group, see sections:
"Adding/updating group" on page 78
"Adding/updating user" on page 79
• Update
Select the group or user from the list and click the Update button to
modify of an existing user or a group data, see sections:
"Adding/updating group" on page 78
"Adding/updating user" on page 79
• Inactivate
Select the group or user from the list and click the Inactivate button to
inactivate the group or user.
• Refresh
Use the Refresh button to refresh the tab view.

7.4.1 Adding/updating group

About this task

Follow the steps below to add a new group or to update an existing group’s
settings.
Note that some of the settings cannot be modified when updating an existing
group’s settings (e.g. group name).

78 Romexis Technical manual

 7 Admin module tasks and settings

Steps
1. Select the User Management > Groups tab in the Admin module.
The existing groups are listed in the Groups tab.
2. Click the Add button to create a new group, or select an existing group
from the list and click the Update button to modify existing group’s data.

3. When adding a group, enter the name and description for the new group.
4. Define the permissions for the group by selecting the permission(s) and
clicking the Add / Remove buttons.
5. Select the Toolbars tab.

6. Select the tools visible for the user group.

6.a. Select the toolbar category to be edited from the Select Toolbar to
Edit list.
6.b. Move the toolbar items between the Visible and Hidden fields by
clicking the Add > and < Remove buttons.
7. To create the group and save the group's settings, click the OK button.

7.4.2 Adding/updating user

Before you begin

If you are using the Planmeca PlanID system, make sure that you have
created a user group for PlanID Users. Set the group to include all of the
Clinic Management permissions.

Technical manual Romexis 79

7 Admin module tasks and settings

For more information on group creation, see section "Adding/updating group"

on page 78.

About this task

Follow the steps below to add a new user or to update of an existing user’s
data.
Note that some of the settings cannot be modified when updating an existing
user's settings (e.g. username).

Steps
1. Select the User Management > Users tab in the Admin module.
The existing users are listed in the Users tab.
2. Click the Add button to create a new user, or select an existing user from
the list and click the Update button to modify existing user’s data.
In the dialogue that displays, fill in or select the necessary information.

3. Fill in or update the user's information in the User, Personal and Contact
tabs.
4. If Romexis Cloud service is used, configure the settings in the Cloud tab,
see section "Setting Romexis Cloud user account" on page 81.
5. If DDX Dental cloud service is used, configure the settings in the DDX
tab, see section "Setting DDX user account" on page 83 .
6. Select the Clinic tab and fill in or update the necessary fields.

• Listens device alerts

80 Romexis Technical manual

 7 Admin module tasks and settings

• Add user to list

Enable this option for those users to which the device alerts are
to be sent.
• Planmeca PlanID
Shows the RFID tag assigned for the user.
• RFID button
The RFID button allows the user to assign the RFID tag by using
a separate RFID reader connected to the computer USB port.
• Allow reassign from dental unit
The Allow reassign from dental unit option allows the user
to reassign the existing RFID tag for a new user. For more
information, see the PlanID quick guide.

NOTE
The assigning of Romexis user to RFID tag can be performed
using a compatible dental unit or in Romexis directly, with a USB
connected RFID Reader. The latter approach is recommended
if there is a large number of users. For more information, see
"Specification of USB connected RFID readers" on page 210.
• Device maintenance
• Share user contact details to a device group
Select this option to enable sending user contact details from
Romexis to dental units and select the created device group from
the drop down menu.
• Patient identification
• Require patient identification
Enables requiring the patient identification.
7. To create the user and save the user's settings, click the OK button.

What to do next
If you want to display a user image on the unit’s user interface and the
Romexis clinic management floorplan, update the user data (Update button)
and add the image to the user information in the Photo tab.

7.4.3 Setting Romexis Cloud user account

About this task

To start using the Romexis Cloud service for sending and receiving cases
you need a user account. The user account identifies each user globally
when sending and receiving cases. It is also used to establish a secure
private-public key encryption for all data transferred through the cloud. An
additional fee based service subscription may be required to use certain
features such as sending new cases.
The Romexis Cloud account is linked to a user account, so no need for
export/import keys if the same user account is used. But if different user
accounts want to use the same Romexis Cloud login, then export/import
keys is needed to link the same cloud account to various user accounts
whether in the same server or different servers.

Technical manual Romexis 81

7 Admin module tasks and settings

Steps
1. Select the User Management > Users tab in the Admin module, and
either create a new user or update an existing user’s data.
For more information on creating a new user or updating an existing user
data, see section "Adding/updating user" on page 79.
2. Select Cloud tab.

3. If not yet created, to create a cloud account, click Sign up link.

Follow the instructions given in the web page.
4. Enter your Email and Password in the respective fields.
When successfully logged into the cloud for the first time, your private
keys will be created in the Romexis database.
To access the cloud from another workstation you need to move your
private key to that workstation using the Export Keys and Import Keys
buttons (under the Advanced Option) before logging into the cloud.
If for some reason you have lost access to the private keys click the
Generate new Keys. A new private key will be generated in the Romexis
database.

NOTE
Generating new keys will invalidate all previously received cases as the
private key information required to decrypt them no longer exists.

NOTE
To prevent any unauthorised person from accessing your cases in the
cloud make sure to protect the private key after it has been exported.

NOTE
For more information on how to configure the Romexis Cloud application
see section "Cloud" on page 130.
5. Click OK to save the user data or continue user data creation in other
tabs.

82 Romexis Technical manual

 7 Admin module tasks and settings

7.4.4 Setting DDX user account

About this task

Follow the steps below to add a new user or to update of an existing user to
use DDX user account.

Steps
1. Select the User Management > Users tab in the Admin module, and
either create a new user or update an existing user’s data.
For more information on creating a new user or updating an existing user
data, see section "Adding/updating user" on page 79.
2. Select the DDX tab.

3. Fill in the Register Romexis Application fields

• DDX Account Name
• App Public Key
• App Private Key
4. Configure the DDX Dental cloud service provider settings, see
instructions in section "DDX Dental" on page 131.
5. Click the OK button save the user data or continue user data creation in
other tabs.

7.5 Patient Merge

The Patient Merge tab consists of two search panels in the upper half of the
screen and a search result panel in the lower half.
On the upper left side there is the Searh for groups of patient with matching
attributes search panel.

Technical manual Romexis 83

7 Admin module tasks and settings

On the upper right side there is the Searh for patients with specific attributes
search panel.

In the lower half there is the search result panel.

7.5.1 Patient Search

Search for matching patients in the following ways:
• Search for patients with matching attributes in the left side search panel
Select from a list of attributes including, for example, surname and
date of birth. Patient Merge groups together the patients with matching
attributes and displays them in the result panel.
Groups are distinguished based on the background colour of the result
list.
• Search for patients with specific attributes in the right side search panel
Use the wildcard character '*' in search fields, excluding date of birth and
gender fields.
The panel contains 2 columns of search fields so that 2 individual
searches can be performed at the same time.

NOTE
You cannot combine search results from the matching attributes and specific
attributes search methods.
After a successful search, select patients for merging by selecting the
relevant patient checkboxes.

7.5.2 Patient Merge

The target patient must also be selected - this marks the patient that other
patients are merged into. When using "search by matching attributes" mode
you can select / deselect the whole group with double click. In this case the
user that was modified last will be the target for merging.
Merging process is irreversible and can be reverted only by restoring
database backup. Patient Merge merges the following patient information:
• Patient info: For example, name and date of birth are set according to
target patient

84 Romexis Technical manual

 7 Admin module tasks and settings

• Address: If target already has assigned address, this is used; otherwise,

the most recently modified address is assigned to merged patient
• Person Attributes: Patient, provider, user, physician etc. are merged to
target person
• User information: All user entries point to target patient after merging

NOTE
The patient in question can be a Romexis user.
• Images and studies: All images and studies are merged to target person
• Dental Session info: All entries are merged for target person
• Assignments: All entries are merged for target person
• Medical History: All entries are merged for target person
• Treatment plans: All entries are merged for target person

NOTE
Persons other than the target are set as inactive according to other Admin
tabs.

7.6 DICOM
In the DICOM tab, the following settings for DICOM related configuration are
available.

Technical manual Romexis 85

7 Admin module tasks and settings

7.6.1 Applications
In the Applications section all the default DICOM application entities are
defined.

In the following sections, the DICOM application entities handling for

different type of entities are described.

7.6.1.1 Adding or editing DICOM application entity (AE)

About this task

An Application Entity (AE) is a functional component in a system that is a
user and/or provider (SCU/SCP) of one or more DICOM services. Each AE
uses a unique AE Title to identify itself. Devices often have a different AE
for each DICOM service, e.g. to send DICOM images to an external PACS
image database.
In order to configure application entity for DICOM destinations, the following
information is needed from the local network administrator:
• Network configuration information for Romexis workstation
• Port numbers for DICOM configurations
• IP addresses of DICOM services
• AE titles, port numbers and IP addresses for the needed DICOM
services.

NOTE
If there are several Romexis workstations in the network configured under
local settings the workstations should have unique AE titles, for example
ROMEXIS_1, ROMEXIS_2 etc., unless the Communicate through server
option is enabled.

86 Romexis Technical manual

 7 Admin module tasks and settings

Steps
1. Select the application you want to create an AE.

2. Click Add.
3. Fill and select the options for the application entity.

• Define the AE Title, Host Name and Port Number for the AE.
• If needed, select the desired Supported Transfer Syntax options to
be used. With these you can limit certain transfer syntax options to
increase compatibility.
• In the TLS Settings section, with the Enable TLS option you can
enable the Transport Layer Security (TLS) to be used with the AE. If
enabled, select the used certificate from the drop-down menu below.
In addition, with the Ignore peer certificate option it is possible
to ignore the peer certificate with the connection. If enabled, any
certificate presented by the SCP are accepted.

Technical manual Romexis 87

7 Admin module tasks and settings

• With the buttons in the DICOM Verification (C_ECHO) field, you can
make the AE verification through the client or server.
4. When all settings are ready, click OK.

7.6.1.2 Modifying Default Storage AE setup

Steps
1. Create an application entity (AE) for the DICOM Default Storage (if not
yet exist).
For more information, see section "Adding or editing DICOM application
entity (AE)" on page 86.
2. Click Select of the Default Storage AE, and from the appearing list,
select the application entity to be used with the DICOM Default Storage,
and click OK.
3. Click Setup of the Default Storage AE and select the options to be used
with the DICOM Default Storage.
4. Enable or disable the Communicate through server.
The setting defines if all the DICOM communication is routed from
Romexis clients to DICOM services via Romexis server. The SCU AE
Title will be used instead of Client AE Title.
5. Modify the setting in the General tab (click the tab if not yet selected).

The setup contains the following settings:

• Reuse association for Singleframe CT images
Specifies whether a single storage association is reused for all
frames in a Singleframe CT images. If disabled a new association
will be opened for each frame.
• Supports Enhanced (Multiframe) CT images
3D volumes will be sent to DICOM Storage in multiframe format. See
your DICOM Storage server documentation for more information.
• Send Images with rotation and mirroring applied
The image is sent to DICOM storage rotated or mirrored if rotation or
mirroring is applied to it.
• Send Images with processing applied

88 Romexis Technical manual

 7 Admin module tasks and settings

All image enhancements made in Romexis are merged into the

image sent to DICOM storage.
• Send Images with annotations applied
Annotations added in Romexis are merged into the images sent to
DICOM storage.
• Send grayscale images with LUT
The Lookup Table (LUT) is included with images sent to DICOM
Storage. In Romexis the following applies to LUT values:
If a gamma correction value unequal to 1.00 is set in Romexis
Configuration Imaging > Panoramic > Auto-enhancements > Gamma
correction, only that value will be used as LUT. If the value equal to
1.00 is set in the first Adjust Levels operation gamma and min/max
values will be used as LUT.
In general only the first adjustment in the Adjust Levels will be used
as LUT whereas the next adjustments will be ignored.
6. Modify the setting in Modality tab (click the tab).

The Force Modalities option allows forcing of specific modality to be

used for each image category. By default Romexis selects the best
suitable modality for each image. Forcing of modality is usually not
required but may be useful e.g. to maximize compatibility with different
PACS systems (for example if the system doesn’t support PX dental
modality).

Technical manual Romexis 89

7 Admin module tasks and settings

7. Modify the setting in the SOP Class tab (click the tab).

The Force SOP Classes option allows forcing of a specific SOP Class
to be used for each image category in Romexis. By default Romexis
selects the correct SOP Class for each image. Forcing of SOP Class
is usually not required but may be useful in some cases to maximize
compatibility with different PACS systems. The first class item in each
drop down list is the default value.
8. Modify the setting in the Storage Commitment tab (click the tab).

• Storage Commitment Enabled

Storage commitments will be shown in Image properties once
received.
• Use separate commitment threads
Threads Storage Commitment into maximum 10 parallel processes
improving Storage throughput in cases where PACS Storage
Commitment processing time is long.
• Two association mode for commitment
When two association mode is enabled, a dedicated association
socket will be opened for establishing Storage Commitment.

90 Romexis Technical manual

 7 Admin module tasks and settings

Otherwise the original Storage association socket is reused to

establish Storage Commitment.

NOTE
Two association mode for commitment cannot be used with server
autostorage.

• Listening port for commitment

Specifies the port where Romexis server listens to Storage
Commitments when Two Association mode is used.
• Client listening port for commitment
Specifies the port where Romexis client listens to Storage
Commitments when Two Association mode is used.
• Timeout for commitment(s)
Specifies the timeout (in Romexis server) for receiving Storage
Commitment when Two Association mode is used.
9. When all settings are ready, click OK.

7.6.1.3 Modifying Default Printer AE setup

Steps
1. Create an application entity (AE) for the DICOM Default Printer (if not yet
exist).
For more information, see section "Adding or editing DICOM application
entity (AE)" on page 86.
2. Click Select of the Default Printer AE, and from the appearing list, select
the application entity to be used with the DICOM Default Printer, and
click OK.
3. Click Setup of the Default Printer AE and select the options to be used
with the DICOM Default Printer.

The setup contains the following settings:

Technical manual Romexis 91

7 Admin module tasks and settings

• Orientation
With Default the printer automatically selects the page orientation
while Portrait or Landscape forces the selected orientation.
• Film Size
This setting allows forcing the printer to use a certain film size.
• Magnification Type
Default will use the default magnification type of the printer while the
others can be used to overrule.
• Smoothing Type
For more information, see your DICOM printer manual for more
information on this setting.
• Magnification Factor
The multiplier to magnify prints. Set this to a value larger than 0 to
scale images up or down. 0.5 will yield 50% size, 1 yields 100%
while 1.5 yields 150% scaling. Leave empty to let the printer fit the
image on the film.
• Header Text Height
Text height for text in header. Values between 20-50 are usually
good. Leaving this empty will cause no header to be printed. Note
that if a magnification is applied in printing the text sizes will also be
scaled accordingly.
• Footer Text Height
Text height for text in footer. Values between 20-50 are usually good.
Leaving this empty will cause no footer to be printed.
• Annotation Text Height
Text height for annotation. Values between 20-50 are usually good.
Leaving this empty will cause no annotations to be printed.
4. When all settings are ready, click OK.

7.6.1.4 Modifying Default Worklist AE setup

Steps
1. Create an application entity (AE) for the DICOM Default Worklist (if not
yet exist).
For more information, see section "Adding or editing DICOM application
entity (AE)" on page 86.
2. Click Select of the Default Worklist AE, and from the appearing list,
select the application entity to be used with the DICOM Default Worklist,
and click OK.

92 Romexis Technical manual

 7 Admin module tasks and settings

3. Click Setup of the Default Worklist AE and select the options to be used
with the DICOM Default Worklist.

• Communicate through server

Enable this option to route all DICOM communication from Romexis
clients to DICOM services via Romexis server. If enabled Romexis
server SCU AE Title will be used instead of Romexis client AE Title.
• Select and update closes matching patient automatically
Enable the setting to have Romexis select and update closes
matching patient automatically when a patient is opened from
DICOM Worklist and a patient with similar information already exists
in Romexis database. Normally Romexis will ask the user to make a
selection between updating or creating a new patient.
• Default Modality
The setting specifies the default value for the modality in the DICOM
Worklist screen in the Patient module.
4. When all settings are ready, click OK.

7.6.1.5 Modifying Default MPPS AE setup

Steps
1. Create an application entity (AE) for the DICOM Default Modality
Performed Procedure Step (MPPS) (if not yet exist).
For more information, see section "Adding or editing DICOM application
entity (AE)" on page 86.
2. Click Select of the Default MPPS AE, and from the appearing list, select
the application entity to be used with the DICOM Default MPPS, and
click OK.

NOTE
For the Default Modality Performed Procedure Step (MPPS) AE there is
no separate setup, only the AE selection available.
3. When the AE selected, click OK.

Technical manual Romexis 93

7 Admin module tasks and settings

7.6.1.6 Modifying Default Q/R (Query/Retrieve SCU) AE setup

Steps
1. Create an application entity (AE) for the DICOM Default Q/R (Query/
Retrieve) (if not yet exist).
For more information, see section "Adding or editing DICOM application
entity (AE)" on page 86.
2. Click Select of the Default Q/R AE, and from the appearing list, select
the application entity to be used with the DICOM Default Q/R, and click
OK.
3. Click Setup of the Default Q/R AE and select the options to be used with
the DICOM Default Q/R (Query/Retrieve).

• Use Romexis server AE title

Use Romexis server SCU title in Query mode as calling AE title
instead of using Romexis client AE title.
• Allow only for current patient
Limits DICOM Query Retrieve queries to the currently selected
patient only.
• Automatic for PMBRIDGE patient
Automatically execute Query/Retrieve for current patient when new
patient is selected using PMBRIDGE.
With the Disabled if last Retrieve less than (h) parameter you can
define a delay for the automatic Q/R if during the time set images
has been received for the patient.
For example, if the parameter is set to 24 h, the automatic Q/R is
NOT executed if images has received for the patient during the last
24 hours.
• Delete retrieved images after n days
Auto delete images requested and received from DICOM Q/R after n
days.
4. When all settings are ready, click OK.

94 Romexis Technical manual

 7 Admin module tasks and settings

7.6.1.7 Modifying Default Auto Storage AEs setup

Steps
1. Create an application entity (AE) for the DICOM Default Auto Storage (if
not yet exist).
For more information, see section "Adding or editing DICOM application
entity (AE)" on page 86.
2. Click Select of the Default Auto Storage AEs, and from the appearing
list, select the application entity to be used with the DICOM Default Auto
Storage, and click OK.
3. Click Setup of the Default Auto Storage AEs and select the options to be
used with the DICOM Default Printer.

The setup contains the following settings:

• Store new images automatically
This enables the storing of selected image types to the selected
archives.
• Retry storage for failed commitment
Defines the number of retries of storing images after failed
commitment.
• Delete image with successful commitment after
Defines a time period in days after which the image is deleted from
the Romexis side after successful commitment of storing the image
to the archive.
4. Add the application entities (AEs) to be used for auto storage.
4.a. Select the application entity from the AE drop-down list.
4.b. Click Add AE to add the AE.
To remove an AE from the list, click Remove of the AE.
5. Select the image types to be sent to the each AEs.
For each AE you can select the image types:
• 2D Pan storage
Selects the 2D panoramic images to be sent to the AE.
• 2D Ceph storage
Selects the 2D cephalostat images to be sent to the AE.
• 2D intra storage
Selects the 2D intraoral images to be sent to the AE.

Technical manual Romexis 95

7 Admin module tasks and settings

• 2D photo storage
Selects the 2D photos to be sent to the AE.
• 2D Cbct storage
Selects the 2D CBCT images to be sent to the AE.
• 3D storage
Selects the 3D images to be sent to the AE.
• Surface storage
Selects the surface model files to be sent to the AE.

NOTE
This option includes also the STL model files.
6. When all settings are ready, click OK.

7.6.1.8 Configuring Romexis server as DICOM Storage SCP (PACS)

Note the following issues when configuring the Romexis server as DICOM
Storage SCP (PACS).
• Use license with Romexis PACS included.
• Use the Romexis Server AE Title (SCP) as the Storage AE title in the
sending software.
• If Restrict DICOM AEs is in use, list allowed IP addresses or AE Titles.
• Set Query/Retrieve Listening port to the port value where you want
Romexis PACS to listen for incoming storage requests.
• Set Patient merge on DICOM Storage setting to desired value.

7.6.1.9 Configuring Romexis server as DICOM Query/Retrieve SCP

Romexis DICOM Query/Retrieve SCP supports PatientRoot queries
PATIENT, STUDY and INSTANCE and StudyRoot queries STUDY and
INSTANCE. Both DICOM C-MOVE and C-GET operations are supported.
Note the following issues when configuring the Romexis server as DICOM
Query/Retrieve SCP:
• Use license with Romexis Query/Retrieve SCP included.
• Define AE title for Romexis server DICOM settings (SCP).
• Set up the retrieving target AE title and port in the Romexis Default
Storage AE settings. The AE title of Q/R SCU only needs to be listed
here.
• Set Query/Retrieve Listening port to the port value where you want
Romexis Q/R SCP.
• Setup Access Control settings as desired.

7.6.2 Romexis Server

In the Romexis Server section the AE title for workstation (default AE_title is
ROMEXIS_1) and Romexis server SCU and SCP are defined.

96 Romexis Technical manual

 7 Admin module tasks and settings

7.6.3 Access Control

In the Access Control section, you can restrict access only from specific
SCU when Romexis works as an SCP (requires a specific Romexis DICOM
PACS license).

• Restrict DICOM AEs

Activates the restricting access from specific Application Entity titles (AE)
or IP addresses.
• Accepted Storage SCU IP Addresses
The accepted IP addresses are separated by a comma.
• Accepted Storage SCU AE Titles
The accepted AE titles are separated by a comma.

NOTE
If the Restrict DICOM AEs is activated but no IP addresses or AE titles
are listed, all IPs and AEs are blocked.
• Enable TLS
Enables the Transport Layer Security (TLS).
From the drop-down menu below the used key store certification can be
selected. The key store certificates are added in the Security tab, see
more in section "Security" on page 101.
• Enable Two-Way Authentication
Enables the two-way authentication.

7.6.4 Modality Performed Procedure

DICOM MPPS SCU service is used together with DICOM Modality Worklist
SCU service. If Romexis MPPS service is configured, the ID, status and
dates of studies as well as patient name will be sent to PACS when starting
the exposure. Dates and compete list of images including X-ray parameters
will be sent to the HIS/RIS server after closing exposure task.
To connect to HIS/RIS MPPS the provider service Default MPPS AE should
be enabled.
For sending messages select Default MPPS AE (see section "Applications"
on page 86) and tick the box Allow sending messages.

7.6.5 Radiation Dose Structured Report

In the Radiation Dose Structured Report section sending of RDSR after an
outgoing DICOM storage is enabled/disabled.

Technical manual Romexis 97

7 Admin module tasks and settings

• Send RDSR after an outgoing DICOM storage

Enables sending an Radiation Dose Structured Report (RDSR) after
an outgoing DICOM storage (CT). CTDIvol and collimation values are
left empty in the RDSR message when using devices manufactured by
Planmeca.
RDSR does not support sending a separate Storage Commitment
message. If both RDSR and Storage Commitment are enabled, the
Storage Commitment message will only be sent for the storage of the
study.

7.6.6 Query/Retrieve/Storage SCP

In the Query/Retrieve section the DICOM Query/Retrieve/Storage SCP listen
port is defined.

• Listening port
Defines the port number where DICOM Query/Retrieve/Storage SCP
results should be expected. Default port is 104.

7.6.7 Default Specific Character Set

In the Default Specific Character Set section the default specific character
set is defined.

To support patient names and information in different languages and

character sets, this setting allows a specific character set to be defined for
saving DICOM files.
Set this option according to your local requirements to allow any DICOM
compatible application to correctly read and display patient information as
you have entered it.

7.6.8 Patient merge on DICOM Storage

In the Patient merge on DICOM Storage section it is possible to set some
options for storing patients to the Romexis database when Romexis works
as an storage SCP, to avoid duplicate patients.
If the same ID is not found, the Romexis tries to find the same patient with
the name (first name + surname) and with the date of birth (DOB). With the
Matching type it is possible to loosen the matching criteria of the search.

• Exact matching
Only an exact matches with the patient name (first name + surname) and
with the date of birth (DOB) is stored under the existing patient ID.
• Loose matching
When this option is selected, the upper/lower case characters, white
spaces and some other special characters with the patient name (first
name + surname) and with the date of birth (DOB) are matched to an
existing patient ID.

98 Romexis Technical manual

 7 Admin module tasks and settings

For example, "SMITH" and "Smith" are stored under the same patient ID.

7.6.9 DICOM logging

In the DICOM logging section you can enable/disable and configure the
saving DICOM activities/messages to database, and view the activity and
logs.

• Save DICOM activities to database

Enables or disables the saving of DICOM activities to database.
• Write to DICOM Message LOG for severities:
• Debug
• Informal
• Warning
• Error
Enables or disables the saving of DICOM messages to database of the
selected severities.
• Store DICOM activities for
Defines the time period (days, default: 14) for which the activities are
stored to database.
If the value is negative, the activities will never be removed from the
database.
• Store Message Log Entries
Defines the time period (days, default: 30) for which the messages are
stored to database.
Message logging can also be configured by message severity by
checking the individual checkboxes.
Note, if none are selected, nothing will be logged.

View Activity
By clicking View Activity, the DICOM Activity Dialog opens. The dialog
consists of two views: DICOM Activity view and Message Log view.

DICOM Activity view

Technical manual Romexis 99

7 Admin module tasks and settings

• The DICOM Activity shows all DICOM transactions in a table with the
following information:
Activity ID, Transaction start and end time, Duration, DICOM Command
(C-STORE, C-FIND, C-MOVE...), Calling and Called AET, Calling and
Called URI, Transfer Status (Queued, Active, Failed, Success), Study
Instance UID, Accession Number, Patient ID (external ID), Image ID
(database ID), Image ModalityStorage, Retry Count.
The table is sortable by any column. Some columns may be empty for
some DICOM activities since all the data is not always available.
• Filters
The results can be filtered using the following filters:
• Start date and time
• End date and time
• Status
• Direction (Outbound, Inbound)
The start and end date can be set using a date picker, by clicking the
appropriate date field. The start and end time can be set with the up/
down arrows, or by typing.
If no dates are set, activities with any date will be shown in the table.
One or more status values can be selected for filtering. If none are
selected, activities with any status will be shown in the table.
Activity direction is always Outbound when using any Romexis SCU and
Inbound when using any Romexis SCP.
Filters can be reset by clicking Clear.
• Show log messages for selected row button
Show log messages for a selected DICOM activity. Message log
contains detailed information about the DICOM communication.
When a DICOM activity is selected, the Show log messages for selected
row button can be pressed to open the Message Log view filtered
automatically to show the log messages for the given DICOM activity.
The Message Log view filters according to the Activity ID unless it is null
for the log entry. For all log entries that have a null Activity ID, the query
tries to match their Study Instance UIDs to the Study Instance UID of the
selected activity.
• Resend selected C-STORE button
An outgoing C-STORE message can be resent by first selecting the
message in the activity view and then clicking Resend selected C-
STORE.
Message Log view
• The Message Log shows DICOM related log messages in a table with
the following information:
Time, Study Instance UID, Linked DICOM Activity ID, Severity (Debug,
Informal, Warning, Error), Message.
Some columns may be empty for some DICOM activities since all the
data is not always available.
• Filters
The results can be filtered using the following filters:
• Start date and time

100 Romexis Technical manual

 7 Admin module tasks and settings

• End date and time

• Severity
• Study Instance UID
• Activity ID
The start and end date can be set using a date picker, by clicking the
appropriate date field. The start and end time can be set with the up/
down arrows, or by typing.
If no dates are set, activities with any date will be shown in the table.
One or more status values can be selected for filtering. If none are
selected, activities with any status will be shown in the table.
Filters can be reset by clicking Clear.

7.6.10 DICOM/HL7 RxBroker Control

NOTE
The DICOM/HL7 RxBroker is supported only on Windows operating
systems.

In the DICOM/HL7 RxBroker Control section you can set DICOM RxBroker
related settings.

NOTE
The HL7 RxBroker is not supported.

• Start DICOM SCP in RxBroker

Enables DICOM SCP start in RxBroker.
• Update Status button
By clicking the button, you can update the Last status field.
• Start, Stop and Restart buttons
Control buttons for starting, stopping and restarting the RxBroker
process.

7.7 Security
In the Security tab, the security certificates are handled.

Technical manual Romexis 101

7 Admin module tasks and settings

• Certificates
• Truststore Certificates
Click Add to add and Remove to remove truststore certificate files.
• Keystore Certificates
Click Add to add and Remove to remove keystore certificate files.
• Each certificate must have a unique alias which separate them
from each other. Before a certificate can be stored to the
database, a dialog asking for alias is shown. Uniqueness check
is case insensitive, for example, aliases 'my certificate' and 'My
Certificate' are considered to be equal.
• The keystore certificates are only supported for:
-Storage SCU/SCP
-Storage commitment (not with two association mode)
-DICOM Query/Retrieve SCU/SCP
-Worklist SCU.
• The supported certificate formats are .p12 and .jks.
• When adding certificate, if the certificate is password protected, a
password prompt is shown.
The following limitations apply:
• Private key algorithm must be RSA.
• Private key must be encoded as per PKCS #8 standard.
• Certificates must be of type X.509.
Changes made with these configurations requires the restart of the Romexis
service, see section "Restarting Romexis service" on page 108.

7.8 Templates
The templates are used for capturing multiple images to a certain predefined
layout.
A template can contain intraoral, panoramic and cephalometric X-ray images
and photos. The print layout and the alignment for the images in it can also
be defined in the template.

102 Romexis Technical manual

 7 Admin module tasks and settings

The list of existing image templates is shown in Templates tab.

To prevent using a certain template for new studies, select the template and
click Inactivate.

NOTE
Inactivation does not affect the existing studies based on the template.

7.8.1 Creating new template

Steps
1. Select Templates tab in the Admin module.
2. Click New.
3. Enter a name for the new template in the appearing dialog and click OK.
4. In Template Editor, click Layout.
5. Select a pre-defined layout or define a custom layout in Choose Layout
window.
You can customise the number of images per row or per column. The
last option allows you to create complex templates such as FMX 20.

6. Back in the Template Editor, double-click the image slot which properties
you want to modify.
Select the image type, sensor orientation, horizontal and vertical
alignment of the images in the study, exposure order, send order and
tooth numbers.

NOTE
The Alignment X and Alignment Y are also used to position images
into a print layout. Appropriate alignment allows printing images in larger
scale with less white space in between.

Technical manual Romexis 103

7 Admin module tasks and settings

7. After you have defined all necessary information for all the slots click OK.

Results
The template is saved into the database. It can now be used in the Imaging
module and in radiology approval process in the Clinic module.

7.8.2 Editing existing template

Steps
1. Select Templates tab in the Admin module.
2. Select the template from the list and click Update.
3. Enter a name for the new template in the appearing dialog and click OK.
4. If you want to change the layout, click Layout in the Template Editor.
5. Choose a pre-defined layout or define a custom layout in the Choose
Layout window.
You can customise the number of images per row or per column. The
last option allows you to create complex templates such as FMX 20.

6. Back in the Template Editor, double-click the image slot which properties
you want to modify.
Select the image type, sensor orientation, horizontal and vertical
alignment of the images in the study, exposure order, send order and
tooth numbers.

NOTE
The Alignment X and Alignment Y are also used to position images
into a print layout. Appropriate alignment allows printing images in larger
scale with less white space in between.
7. After you have defined all necessary information for all the slots click OK.

104 Romexis Technical manual

 7 Admin module tasks and settings

Results
The template is saved into the database. It can now be used in the Imaging
module and in radiology approval process in the Clinic module.

7.9 Device Alerts

The Device Alerts tab allows configuration of device alert (error messages)
forwarding to user e-mails, and defining usage data alerts.

7.9.1 Configuring device alerts

Before you begin

In order to see the user in the Configure Device Alerts / Name list, the
Listens device alerts / Add user to list option in the user data Clinic tab must
be enabled and the Work Email in the Contact tab must be defined as the
alerts are sent to that address.
See more in section "Adding/updating user" on page 79.

Steps
1. Select Configure Device Alerts tab in the Admin module.

2. From the left panel, select the user to which the device alerts is to be
sent.
3. Click Configure and select the specific error and help events to be
forwarded to a selected user’s e-mail.

4. Click OK.

Technical manual Romexis 105

7 Admin module tasks and settings

5. Click the Activate / deactivate to enable the device alert sending to the
user.

7.9.2 Configuring usage data alerts

Steps
1. Select Configure Usage Data Alerts tab in the Admin module.

2. Click New to create a new usage data alert.

3. Enter Name and Message, and select Type for the alert.
4. Select Instrument from the drop-down menu.
5. Configure triggers that allow custom events on.
• Used more than
Unit component mileage limits (hours) for preventive maintenance.
• Selected more than or Activated more than
Unit instrument selection or activation frequency to track
inappropriate use.
6. Click Save Settings.
To modify an existing alert definition, select the alert from the left panel
and change the settings and click Save Settings.
To remove an alert definition, select the alert from the left panel and click
Remove.

106 Romexis Technical manual

 8 Romexis configuration

8 Romexis configuration
8.1 Starting Romexis Configuration tool

Before you begin

Romexis Configuration tool is accessible only for users with administrator
rights. The access is defined by the user group permissions, see more in
section "User Management" on page 78.

About this task

Romexis Configuration tool is a password-protected facility for adjusting
various system-wide Romexis settings. The parameters and setting available
in the Romexis Configuration tool are described in section "Romexis
Configuration tool parameters and settings" on page 112.
Romexis Configuration tool general buttons
• Show Help >>
To display an interactive help explaining the options in each window,
click the Show Help button.
• Set Defaults
Some of the Romexis Configuration tool views includes Set Defaults
button, by clicking the button the default settings are set for the settings
in the current view.
To start Romexis Configuration tool, follow the steps below.

Steps
1. Start Romexis Configuration tool.
• In Windows Start menu, select Planmeca > Romexis Configuration.
or
• Browse to C:/Program files/Planmeca/Romexis/admin
folder, and double-click RomexisConfig.bat file.
2. Log into Romexis Configuration tool by entering your user name and
password in the respective fields and click OK.

The default username and password are:

• Username: sysadm
• Password: promax

Technical manual Romexis 107

8 Romexis configuration

8.2 Changing password

Steps
1. Start Romexis Configuration tool.
For instructions, see section "Starting Romexis Configuration tool" on
page 107.
2. Enter your user name to the Username field.

3. Click the Change password button.

4. Enter the current password, and the new password twice.

5. Click the OK button.

8.3 Restarting Romexis service

Before you begin

Restarting Romexis service requires administration rights, either login to
the Romexis server as an administrator user or run Start Romexis Service
application as an administrator.

About this task

Usually when changing Romexis settings in Romexis Configuration tool, to
activate the changes Romexis service must be restarted.
Follow the steps below to restart Romexis service.

Steps
1. In Windows Start menu, select Planmeca > Start Romexis Service.

2. Click Stop Service and wait for a couple of seconds.

3. Click Start Service.
4. Click OK to acknowledge the restart.

108 Romexis Technical manual

 8 Romexis configuration

5. Click Done to close the window.

8.4 Modifying Romexis logging

Before you begin

Normally, there is no need to modify the Romexis logging properties.
However, for troubleshooting purposes, it can be useful to get more detailed
and longer period of logging data.

About this task

The Romexis writes log files for the Romexis subsystems listed in the
following table. In the table, the configuration file for each log file and the
default folders for the generated log files are listed.
In the configuration file you can modify log file settings, such as the log level,
log file name, log file size, how many old log files to keep and where the log
files are saved.

Subsystem Configuration file Log file folder Log file names

Romexis server
\Romexis\Server\ \ProgramData\Planmeca
Windows
log4j2_server.xml \Logs \Romexis\Server RomexisServer_<computer
/Romexis/Server/ /Library/Logs/Planmeca/ name>.log
macOS
log4j2_server.xml Romexis/Server
DICOM/HL7 RxBroker
\Romexis\broker\ \ProgramData\Planmeca
Windows RomexisBroker.log
log4j2_rxbroker.xml \Logs \Romexis\Server
macOS The DICOM/HL7 RxBroker is supported only on Windows operating systems.
Romexis client
\Romexis\client\ \ProgramData\Planmeca
Windows
log4j2_client.xml \Logs \Romexis\Client RomexisClient_<computer
/Romexis/client/ /Library/Logs/Planmeca/ name>.log
macOS
log4j2_client.xml Romexis/Client
Romexis configuration
\Romexis\admin\ \ProgramData\Planmeca
Windows
log4j2_rxconfig.xml \Logs\Romexis\Admin
RomexisGeneral.log
/Romexis/admin/ /Library/Logs/Planmeca/
macOS
log4j2_rxconfig.xml Romexis/Admin
DxLoader
\Romexis\tools\ \ProgramData\Planmeca
Windows
log4j2_dxloader.xml \Logs \Romexis\General
RomexisDxLoader.log
/Romexis/tools/ /Library/Logs/Planmeca/
macOS
log4j2_dxloader.xml Romexis/General
Intracam
\Romexis\client\ \ProgramData\Planmeca
Windows
log4j2_intracam.xml \Logs \Romexis\Client
Intracam.log
/Romexis/client/ /Library/Logs/Planmeca/
macOS
log4j2_intracam.xml Romexis/Client

Technical manual Romexis 109

8 Romexis configuration

Subsystem Configuration file Log file folder Log file names

Solanna Vision
\Romexis\client\ \ProgramData\Planmeca
Windows
log4j2_streamapp.xml \Logs \Romexis\Client
SolannaVisionStreamApp.log
/Romexis/client/ /Library/Logs/Planmeca/
macOS
log4j2_streamapp.xml Romexis/Client
\Romexis\Server\ \ProgramData\Planmeca
Windows
log4j2_controlserver.xml \Logs \Romexis\Server
SolannaVisionControlServer.log
/Romexis/Server/ /Library/Logs/Planmeca/
macOS
log4j2_controlserver.xml Romexis/Server
Romexis Viewer
\Romexis\viewer\ \ProgramData\Planmeca
Windows
log4j2_viewer.xml \Logs \Romexis\Client
RomexisViewer.log
/Romexis/viewer/ /Library/Logs/Planmeca/
macOS
log4j2_viewer.xml Romexis/Client
PMBridge
Windows See section "PMBridge interface configuration" on page 36.

Follow the steps below to modify the Romexis logging properties.

Steps
1. Open the log file configuration file for editing.
Check the configuration file location and file name from the table above.
2. Modifying the logging level.
The logging level of each logging entity is by default set to 'info'. To
add more information to the log files, for example for troubleshooting
purposes, the logging level can be set to 'debug' level. This can be
applied separately for each logging entity.
2.a. Browse the file to the <Loggers> section.
2.b. Select the desired logging entity from the section and modify the
value of level parameter.
For example, if more detailed logging is needed for Romexis
server, set the level to debug as follows.
<Logger name="ROMEXIS_SERVER" level="debug"
includeLocation="true" additivity="false">

NOTE
The 'debug' level logging enlarges the log file sizes, thus it might be
good to modify the logging storage size settings, see the next step.
3. Modifying the logging storage size.
3.a. Browse the file to the <RollingFile> section of the desired
logging entity.
3.b. Modify the SizeBasedTriggeringPolicy size parameter
value to correspond the needed file size.
For example, if more logging data is needed for Romexis server,
set the file size e.g. to 20 MB as follows.
<SizeBasedTriggeringPolicy size="20 MB" />

110 Romexis Technical manual

 8 Romexis configuration

Once this amount of logging data is reached, older archives will be

deleted on subsequent rollovers.

NOTE
Make sure there are enough disk space for the log files.
4. Modifying the log storage folders.
If needed, it is possible to modify the folders where to the log files are
stored.
4.a. Browse the file to the <Properties> section.
4.b. The main folder path for the log files can be defined with the
romexisLogPath variable.
For example, to define the C:\projects\Romexis_logs
(Windows) for the Romexis log files, set the variable as follows.
<Property
name="romexisLogPath">\projects\Romexis_logs</
Property>
4.c. The subfolders are defined with the following settings accordingly.
<Property name="programDataClient">$
{sys:romexisLogPath}/Client</Property>
<Property name="programDataServer">$
{sys:romexisLogPath}/Server</Property>
<Property name="programDataAdmin">$
{sys:romexisLogPath}/Admin</Property>
<Property name="programDataGeneral">$
{sys:romexisLogPath}/General</Property>

NOTE
The defined logging folder(s) must exist with sufficient write permission.
5. Save and close the file.
6. Restart the Romexis to enable the changes.

NOTE
If the logging level (info/debug) of the Romexis server is changed, the
Romexis service must be restarted for the change to take effect.

What to do next

NOTE
When the Romexis software is updated, the logging configuration files
(log4j2_*.xml) are replaced, so if permanent changes are made to these
files, remake the changes after Romexis update. Or alternatively make a
backup copies of the configuration files and replace them after Romexis
update.

Technical manual Romexis 111

9 Romexis Configuration tool parameters and settings

9 Romexis Configuration tool parameters and settings

The sections below lists and describes the parameters and settings in the
Romexis Configuration tool.

9.1 Resources

9.1.1 General

• Show Instance Name in Client’s title bar

By checking/unchecking this option you can define whether the instance
name that is defined in the Instance Name field (see below) is shown in
the Romexis title bar.
• Show Username in Client’s title bar
By checking/unchecking this option you can define whether the
username that is defined in the Instance Name field is shown in the
Romexis title bar.
• Allow more than one client instance on one workstation
With this options selected multiple Romexis clients can be started on the
same computer.
• Synchronize Ceph Module Analysis Types between server and clients
With this option Romexis Cephalometric Analysis types are synchronised
between server and clients.
• Instance Name
Enter the instance name (e.g. clinic name) into the Romexis title bar. All
Romexis clients that are connected to the same server have the same
instance name.
• Use KaVo webpage link for tutorial videos
If this option is enabled, the Romexis tutorial video links will be directed
to the KaVo website instead of the Planmeca website.

112 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

9.1.2 Person

• Name formatting
The Name Formatting selection affects the formatting of name display on
the screen.
• Don’t format
The names are displayed as they were entered into the database.
• Capitalize first letter
The first letter of each name is capitalised and the rest remain in
lower case.
• Capitalize all
Capitalises all letters in a name.
Name Formatting affects the processing of searches for names so that
when Don't Format is used, searches are case sensitive, while Capitalize
First Letter/Capitalize ALL make searches case insensitive.
• Name display order
In Name Display Order you can decide which name, family name or first
name, is displayed first in the Romexis.
• Patient identification
Patient Identification defines which Patient ID is used to refer to patients.
The same ID is also used in patient search. Romexis can maintain three
different Patient IDs at a time.
• Custom ID
Refers to an ID typed into Romexis at patient creation, or an ID
generated by e.g. Axium.

Technical manual Romexis 113

9 Romexis Configuration tool parameters and settings

• Other ID
Refers to an ID imported from another software, where this usually
administrative ID has been assigned to patients manually (may e.g.
refer to a patient’s old paper file).
• Autonumber
Instructs Romexis to automatically assign a Patient ID to the created
patient and to use this unique identifier. This is viable only in cases
where Romexis is used as the master patient management software.
• Patient ID Sorting
The following options are available when patient list is sorted by the
Patient ID column:
• Insertion order
Sorting in the order the patients were entered into the database.
• Alphabetical
Alphabetical sorting: 001, 1111, 22, aaa, aab, aba
• Numerical
Numerical sorting ignoring leading zeros: 001, 22, 1111, aaa, aab
• Prefix alphabetically
Sorting first by leading alphabets and then numerically: A22, A1111,
B01
• Patient
• Access reason is required when accessing patients
If this option is enabled the reason for accessing the patient is
required when opening patient. This request can be set optional in
the Romexis Configuration tool.
• Give warning for Selecting all patients
Warns the user when all patients are searched at the same time from
the database in the Patient module.
• Export files using patient name
Specifies the patient’s name to be used as the default filename
for exports. The suggested filename can still be changed. When
disabled the filename field shows empty by default.
• Show Patient ID in Patient Drop-Down List
When disabled, no patients ID are shown in the patient drop-down
list.
• Auto Find Patients
Enabled by default. When disabled, no patients are shown in the
search list until a patient search is performed.
• Enable adding and editing of PlanID
When disabled, adding and editing PlanID is not allowed.
For more information on using the PlanID with users, see section
"Adding/updating user" on page 79.
• Maximum No of Patient Query Results to Return
Limit for maximum number of records to return in patient search queries.
• Patient List Name Formatting

114 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

• Use Global Formatting Setting Above

This option uses the settings defined in the fields above.
• First Name and Last Name Initial
This option displays the entire first name and only the first letter of
the last name of the patient in the search results.
• Initials Only
This option displays only the patient’s initials in the search results.

9.1.3 Regional

• Tooth identification system

• FDI/ISO
This option refers to the two-digit FDI World Dental Notation.
• ADA
Universal Numbering System adopted by the American Dental
Association.
• Regional settings
These settings specify default values and available settings in the
Patient Demographics.
• Country
Defines the default country for demographics.
• Language
Defines the default language for demographics.
• Show State / State Prompt
Enables showing an input field for patients home state or similar, and
a freely configurable prompt text.
• Show PIN / PIN prompt
Enables showing an input field for patients personal identification
number or similar, and a freely configurable prompt text.
• ProModel Price List
Specify the HTTP address location of the regional ProModel price
list.

9.2 Imaging

Technical manual Romexis 115

9 Romexis Configuration tool parameters and settings

9.2.1 General

General Settings
• Images Decoded/Decompressed on Server
This setting is disabled by default and 2D images are transferred
in compressed format from server to client where the image is
decompressed before viewing.
Since Romexis 5.2.0 release, this option also affects 3D volume data
when the Use Dicom JPEGLosslessV1 Compression option is in use.
• Allow Delayed Image Writes
If enabled, the saving of image from Romexis client to the file server is
performed in the background. Delayed image writes improve workflow
for slow networks when client and server are in different locations.
The user cannot close the Romexis client as long as the transfer is in
progress.
Also affects image import. Option is disabled by default.
• Use Dicom JPEGLosslessV1 Compression
By checking/unchecking this option you can define whether the DICOM
images are stored in lossless compression format in the Romexis image
data folder.
Having the compression/decompression performed on client side (with
the Images decoded / decompressed on server option disabled) can
reduce file transfer times over slow networks.

Locking
• Automatically Lock 2D Images and Studies
2D images and studies can be optionally locked after a defined delay (in
hours) so that they can only be opened in read only mode (no changes
made are stored) and they can't be inactivated or moved.
Locking applies also to 2D module studies so that study can't be
modified if it is locked (no images can be added or removed).
To enable locking, tick the checkbox.
• Lock After (Hours)

116 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Defines the delay in hours after which the 2D images and studies are
locked.

Burn Data on an Exported Image

The following items can be selected to be burned to exported images.
• Patient ID
• Name
• Date of Birth
• Age
• Exposure Date
• Voltage (kV)
• Current (mA)
• Exposure Time (s)
• DAP (mGy x cm2)
• Image Capturer

9.2.2 Panoramic
In the Panoramic tab you can make adjustments to the image quality
settings of panoramic images.

The Resolution, Bits Per Pixel and Image Format define how the images are
stored in the database after the image has been taken.
• Resolution
See the pixel sizes for Normal, Enhanced and High resolution in the
X-ray unit’s user’s manual.

Technical manual Romexis 117

9 Romexis Configuration tool parameters and settings

NOTE
The size of the image is much larger and the handling of the image
slower when the pixel size is smaller.

NOTE
The resolution selected in the Romexis configuration panoramic settings
depends on which X-ray unit and sensor type is in use. Other Romexis
Configuration settings (BitsPerPixel, ImageFormat, Gamma, Sharpening,
Median) are the same as the settings for other 2D images acquired with
Dimax sensor.
• Bits per pixel
This field defines whether the images are captured as 8 bit or 16 bit. The
best dynamic contrast range is reached by using 16 bit per pixel, but the
images will be twice the size of 8 bit images.
• Image format
The format in which the images are stored in the database. The options
are TIFF and JPEG.
• JPEG quality
The JPEG Quality can be set to Low, Medium, High or Maximum.
• Auto Enhancements
The Auto Enhancements group includes settings that affect the
visualization of the images in the Romexis. They do not affect the
original images in the database.
• Use Normal Preprocessing
Auto enhancement are automatically performed on all new images If
the automatic adjustments are not satisfactory, it can be undone by
clicking the Undo button in the Imaging module, and the adjustments
can be done manually using the Adjust Levels.
• Gamma Correction
Adjusts the gamma curve of the image. By adjusting the gamma
value, the image can be made to look more like a conventional
X-ray image.
• Sharpen
The image can be sharpened with a specific filter and strength
(Low, Medium or High).
• Despecle
A specific filter can be used to remove noise from the image by
selecting Despecle.
• Use Custom Preprocessing
The custom preprocessing in the Romexis allows defining custom
preprocessing settings for 2D exposures/images. The custom
preprocessing settings can be defined per image type in the 2D
Imaging module.
There are two types of preprocessing settings, global and local. The
global type is available on all Romexis clients connected to the same
Romexis server, and the local type is available only on the Romexis
client/workstation they are defined on.
From the drop-down menu, you can check if there are any, global or
local, custom preprocessing settings defined. Option No Workstation

118 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Settings indicates that there is no local preprocessing settings

defined.
By enabling the Use Custom Preprocessing the defined
preprocessing settings are used instead of the settings defined
under the Use Normal Preprocessing. If both types of
preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing
settings.

NOTE
All preprocessing settings are defined and modified in the Romexis
2D Imaging module whereas the current settings can be viewed in
the Romexis Configuration tool.

For more information on defining the custom preprocessing settings,

see section "Defining custom preprocessing settings" on page 128.
For more information on image processing and archiving see the
Romexis user’s manual.
• Bitewing auto enhancements
The Bitewing Auto Enhancements group includes dedicated settings
that affect exposures taken with the bitewing programs available in the
selected X-ray units. They will not affect exposures taken with intraoral
sensors. The same values as for the Auto Enhancements for panoramic
images above apply.
• Save Auto Focus Images
Enables saving the autofocus images as normal exposures among other
X-ray images in the Romexis.
The setting is available only with Dimax sensor, as Autofocus is not
available with SmartPan.

9.2.3 Cephalometric
In the Cephalometric tab you can adjust cephalometric image quality
settings.

The Resolution and the Image Format settings define how the images are
stored in the database.
• Resolution
See the pixel sizes for Normal and Enhanced resolution from X-ray unit’s
user’s manual.

Technical manual Romexis 119

9 Romexis Configuration tool parameters and settings

NOTE
The size of the image is much larger and the handling of the image is
slower when the resolution of the image is higher.
• Image Format
The format in which the images are stored in the database. The options
are TIFF, JPEG and DICOM.
The JPEG Quality can be set to be Low, Medium, High or Maximum.
• Auto Enhancements
The Auto Enhancements group includes settings that affect the
visualization of the images in the Romexis. They do not affect the
original images in the database.
• Use Normal Preprocessing
When a new image is captured, the Adjust Levels operation is
automatically performed to the image with the Auto Enhancement
group settings. If the automatic adjustment is not satisfactory, it can
be undone by clicking the Undo button in the Imaging module, and
the adjustments can be done manually in Romexis using the Adjust
Levels function.
• Gamma correction
Adjusts the gamma curve of the image. By adjusting the gamma
value, the image can be made to look more like a conventional
X-ray image.
• Sharpen
The image can be sharpened with a specific filter and strength
(Low, Medium or High).
• Despecle
A specific filter can be used to remove noise from the image by
selecting the option.
• Use Custom Preprocessing
The custom preprocessing in the Romexis allows defining custom
preprocessing settings for 2D exposures/images. The custom
preprocessing settings can be defined per image type in the 2D
Imaging module.
There are two types of preprocessing settings, global and local. The
global type is available on all Romexis clients connected to the same
Romexis server, and the local type is available only on the Romexis
client/workstation they are defined on.
From the drop-down menu, you can check if there are any, global or
local, custom preprocessing settings defined. Option No Workstation
Settings indicates that there is no local preprocessing settings
defined.
By enabling the Use Custom Preprocessing the defined
preprocessing settings are used instead of the settings defined
under the Use Normal Preprocessing. If both types of
preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing
settings.

120 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

NOTE
All preprocessing settings are defined and modified in the Romexis
2D Imaging module whereas the current settings can be viewed in
the Romexis Configuration tool.

For more information on defining the custom preprocessing settings,

see section "Defining custom preprocessing settings" on page 128.
For more information on image processing and archiving see the
Romexis user’s manual.

9.2.4 Intraoral
In the Intraoral tab you can make adjustments to the image quality settings
for the intraoral images.

The Resolution, Bits Per Pixel and Image Format settings define how the
images are stored in the database.
• Resolution
See the pixel sizes for Normal and High resolution in the X-ray unit’s
user’s manual.

NOTE
The size of the image is much larger and the handling of the image is
slower when the resolution is higher.
• Bits Per Pixel
In the Bits Per Pixel group you can select whether the images are stored
as 8 bit or 16 bit images. The best dynamic contrast range is reached
by using 16 bit per pixel, but the images will be twice the size of 8 bit
images.
• Image Format
The format in which the images are stored in the database. The options
are TIFF, JPEG and DICOM.
The JPEG Quality can be set to be Low, Medium, High or Maximum.
• Auto Enhancements
The Auto Enhancements group includes settings that affect the
visualization of the images in Romexis. They do not affect the original
images in the database.
• Use Normal Preprocessing

Technical manual Romexis 121

9 Romexis Configuration tool parameters and settings

When a new image is captured, the Adjust Levels operation is

automatically performed to the image with the Auto Enhancement
group settings. If the automatic adjustment is not satisfactory, it can
be undone by clicking the Undo button in the Imaging module and
the adjustments can be done manually in Romexis with the Adjust
Levels function.
• Gamma correction
Adjusts the gamma curve of the image. By adjusting the gamma
value, the image can be made to look more like a conventional
x-ray image.
• Sharpen
The image can be sharpened with a specific filter and strength
(Low, Medium or High).
• Despecle
A specific filter can be used to remove noise from the image by
selecting the Despecle.
• Use Custom Preprocessing
The custom preprocessing in the Romexis allows defining custom
preprocessing settings for 2D exposures/images. The custom
preprocessing settings can be defined per image type in the 2D
Imaging module.
There are two types of preprocessing settings, global and local. The
global type is available on all Romexis clients connected to the same
Romexis server, and the local type is available only on the Romexis
client/workstation they are defined on.
From the drop-down menu, you can check if there are any, global or
local, custom preprocessing settings defined. Option No Workstation
Settings indicates that there is no local preprocessing settings
defined.
By enabling the Use Custom Preprocessing the defined
preprocessing settings are used instead of the settings defined
under the Use Normal Preprocessing. If both types of
preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing
settings.

NOTE
All preprocessing settings are defined and modified in the Romexis
2D Imaging module whereas the current settings can be viewed in
the Romexis Configuration tool.

For more information on defining the custom preprocessing settings,

see section "Defining custom preprocessing settings" on page 128.
For more information on image processing and archiving see the
Romexis user’s manual.

122 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

9.2.5 ProScanner
In the ProScanner tab you can make adjustments to the image quality
settings for Planmeca ProScanner images.

The Image Format defines how the images are stored in the database after
the image has been taken.
• Image Format
The format in which the images are stored in the database. The options
are TIFF, JPEG and DICOM.
The JPEG Quality can be set to be Low, Medium, High or Maximum.
• Auto Enhancements
The Auto Enhancements group includes settings that affect the
visualization of the images in Romexis. They do not affect the original
images in the database.
• Use Normal Preprocessing
When a new image is captured, the Adjust Levels operation is
automatically performed to the image with the Auto Enhancement
group settings. If the automatic adjustment is not satisfactory, it
can be undone by clicking the Undo button in the Imaging module
and the adjustments can be done manually in Romexis through the
Adjust Levels function.
• Gamma correction
Adjusts the gamma curve of the image. By adjusting the gamma
value, the image can be made to look more like a conventional
X-ray image.
• Sharpen
The image can be sharpened with a specific filter and strength
(Low, Medium or High).
• Despecle
A specific filter can be used to remove noise from the image by
selecting the Despecle.
• Use Custom Preprocessing
The custom preprocessing in Romexis allows defining custom
preprocessing settings for 2D exposures/images. The custom
preprocessing settings can be defined per image type in the 2D
Imaging module.
There are two types of preprocessing settings, global and local. The
global type is available on all Romexis clients connected to the same
Romexis server, and the local type is available only on the Romexis
client/workstation they are defined on.

Technical manual Romexis 123

9 Romexis Configuration tool parameters and settings

From the drop-down menu, you can check if there are any, global or
local, custom preprocessing settings defined. Option No Workstation
Settings indicates that there is no local preprocessing settings
defined.
By enabling the Use Custom Preprocessing the defined
preprocessing settings are used instead of the settings defined
under the Use Normal Preprocessing. If both types of
preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing
settings.

NOTE
All preprocessing settings are defined and modified in the Romexis
2D Imaging module whereas the current settings can be viewed in
the Romexis Configuration tool.

For more information on defining the custom preprocessing settings,

see section "Defining custom preprocessing settings" on page 128.
For more information on image processing and archiving see the
Romexis user’s manual.

9.2.6 ProScanner 2.0 / ProXam iP

In the ProScanner 2.0 / ProXam iP tab you can make adjustments to the
image quality settings for Planmeca ProScanner 2.0 and KaVo ProXam iP
images.

The Image Format defines how the images are stored in the database after
the image has been taken.
• Image Format
The format in which the images are stored in the database. The options
are TIFF, JPEG and DICOM.
The JPEG Quality can be set to be Low, Medium, High or Maximum.
The images are stored as 16 bit images.
• Auto Enhancements
The Auto Enhancements group includes settings that affect the
visualization of the images in Romexis. They do not affect the original
images in the database.
• Use Normal Preprocessing
When a new image is captured, the Adjust Levels operation is
automatically performed to the image with the Auto Enhancement
group settings. If the automatic adjustment is not satisfactory, it can
be undone by clicking the Undo button in the Imaging module and

124 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

the adjustments can be done manually in Romexis with the Adjust

Levels function.
• Gamma correction
Adjusts the gamma curve of the image. By adjusting the gamma
value, the image can be made to look more like a conventional
X-ray image.
• Sharpen
The image can be sharpened with a specific filter and strength
(Low, Medium or High).
• Despecle
A specific filter can be used to remove noise from the image by
selecting the Despecle.
• Use Custom Preprocessing
The custom preprocessing in Romexis allows defining custom
preprocessing settings for 2D exposures/images. The custom
preprocessing settings can be defined per image type in the 2D
Imaging module.
There are two types of preprocessing settings, global and local. The
global type is available on all Romexis clients connected to the same
Romexis server, and the local type is available only on the Romexis
client/workstation they are defined on.
From the drop-down menu, you can check if there are any, global or
local, custom preprocessing settings defined. Option No Workstation
Settings indicates that there is no local preprocessing settings
defined.
By enabling the Use Custom Preprocessing the defined
preprocessing settings are used instead of the settings defined
under the Use Normal Preprocessing. If both types of
preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing
settings.

NOTE
All preprocessing settings are defined and modified in the Romexis
2D Imaging module whereas the current settings can be viewed in
the Romexis Configuration tool.

For more information on defining the custom preprocessing settings,

see section "Defining custom preprocessing settings" on page 128.
For more information on image processing and archiving see the
Romexis user’s manual.

Technical manual Romexis 125

9 Romexis Configuration tool parameters and settings

9.2.7 Twain Intraoral

In the Twain Intraoral tab you can make adjustments to the image quality
settings for TWAIN intraoral images.

The Image Format defines how the images are stored in the database after
the image has been taken.
• Image Format
The format in which the images are stored in the database. The options
are TIFF, JPEG and DICOM.
The JPEG Quality can be set to be Low, Medium, High or Maximum.
• Auto Enhancements
The Auto Enhancements group includes settings that affect the
visualization of the images in Romexis. They do not affect the original
images in the database.
• Use Normal Preprocessing
When a new image is captured, the Adjust Levels operation is
automatically performed to the image with the Auto Enhancement
group settings. If the automatic adjustment is not satisfactory, it can
be undone by clicking the Undo button in the Imaging module and
the adjustments can be done manually in Romexis with the Adjust
Levels function.
• Gamma correction
Adjusts the gamma curve of the image. By adjusting the gamma
value, the image can be made to look more like a conventional
x-ray image.
• Sharpen
The image can be sharpened with a specific filter and strength
(Low, Medium or High).
• Despecle
A specific filter can be used to remove noise from the image by
selecting the Despecle.
• Use Custom Preprocessing
The custom preprocessing in Romexis allows defining custom
preprocessing settings for 2D exposures/images. The custom
preprocessing settings can be defined per image type in the 2D
Imaging module.
There are two types of preprocessing settings, global and local. The
global type is available on all Romexis clients connected to the same
Romexis server, and the local type is available only on the Romexis
client/workstation they are defined on.

126 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

From the drop-down menu, you can check if there are any, global or
local, custom preprocessing settings defined. Option No Workstation
Settings indicates that there is no local preprocessing settings
defined.
By enabling the Use Custom Preprocessing the defined
preprocessing settings are used instead of the settings defined
under the Use Normal Preprocessing. If both types of
preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing
settings.

NOTE
All preprocessing settings are defined and modified in the Romexis
2D Imaging module whereas the current settings can be viewed in
the Romexis Configuration tool.

For more information on defining the custom preprocessing settings,

see section "Defining custom preprocessing settings" on page 128.
For more information on image processing and archiving see the
Romexis user’s manual.

9.2.8 CBCT
In the CBCT tab you can make adjustments to the image quality settings for
the CBCT images.
Default Settings and Auto Enhancements affect the visualisation of the
CBCT images when they are opened in Romexis.

• Default Settings
• Show Live Frame Preview
• Default Artefact Removal
Sets the default Artefact removal level that is selected in the 3D
Exposure dialogue. The default setting can be overridden by the user
per exposure.
• BitDepth
Specifies the bit depth at which 3D exposures are stored in Romexis
image database. The default value is 12bit. When 15bit is used 3D
volumes can be exported optionally in 12 or 15 bit depth. 15bit
setting should be used only in cases where 15bit exports to other
systems are a requirement.

Technical manual Romexis 127

9 Romexis Configuration tool parameters and settings

• Window
Defines the default range of gray scale values displayed for new
exposures. The window range is 0 - 4095 shades of gray and it is
typically set to 2000.
• Level
Defines the midpoint for the shades of gray (0 - 4095). If level is
set to 2000 and window is 2000, the shades of gray that are in use
include values from 1000 to 3000.
• Auto Enhancements
• Gamma correction
Defines the default gamma value for the Auto Enhancement.
• Auto Levels Min Pct(%)
Defines the percentage of cumulative shades of gray that is left out
of the contrast range from the lower end of the contrast range.
• Auto Levels Max Pct(%)
Defines the percentage of the cumulative shades of gray that is left
out of the contrast range from the upper end of the histogram.

9.2.9 Defining custom preprocessing settings

About this task

It is possible to define default preprocessing settings for 2D images (e.g.
panoramic, bitewing, cephalometric, intraoral and ProScanner images).
There are two types of preprocessing settings, global and local. The global
type is available on all Romexis clients connected to the same Romexis
server, and the local type is available only on the Romexis client/workstation
they are defined on.
If both types of preprocessing settings are defined, the local (i.e. workstation
specific) preprocessing settings override the global preprocessing settings.

Steps
1. Open a 2D image in Romexis.
2. Use the image specific toolbar to adjust levels or sharpen the image until
acceptable image quality is achieved.
3. Check that the correct enhancements are listed in the Image Operations
field.

TIP
Applying the same enhancements several times on the image will slow
down opening of image preprocessing, so it is better to try to minimize
the number of enhancements if possible.

128 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

4. From the File menu select the Capture > Save Image Enhancements
as Default Enhancements to set the current settings in the Image
Operations list as default enhancements for the current image type.

5. Select the image preprocessing type, Local or Global.

The global type is available on all Romexis clients connected to the
same Romexis server, and the local type is available only on the
Romexis client/workstation they are defined on.

6. Enable the defined preprocessing settings in the Romexis Configuration

tool.
6.a. Start the Romexis Configuration tool.
See section "Starting Romexis Configuration tool" on page 107.
6.b. Under the Imaging, select the 2D imaging type.
6.c. Select the Use Custom Preprocessing option.
6.d. From the drop-down menu, view the defined preprocessing
settings.
In the drop-down menu, you can view the defined global and/or
local custom preprocessing settings. All local settings with the
workstation name are separately visible. Option No Workstation
Settings indicates that there is no local preprocessing settings
defined. The local (i.e. workstation specific) preprocessing settings
override the global preprocessing settings.

6.e. Click the OK button.

7. Restart the Romexis to enable the changes.

9.3 Export Font Sizes

• Font sizes for exporting and printing

• Image Annotation Font Size
Defines the font size for the image annotations.
• Image Measurement Font Size

Technical manual Romexis 129

9 Romexis Configuration tool parameters and settings

Defines the font size for the measurements made on the images.

9.4 Print

• Update Print Logo Files

• Client Logo
Shown in the top left corner of the printed paper.
• Romexis Logo
Shown in the top right corner of the printed paper. By default it is
Romexis logo.
• Footer Logo
Shown in the bottom left corner of the printed paper. The image
which will replace a logo must be in Portable Network Graphics file
format (.png). The height of all logos is limited to 1.0 inches.
By clicking the Browse button the user can browse for desired image
and by clicking the Update button the image is updated to Romexis
database.
• Show Logos in Printouts
The logos showing in printouts can be selected here.
• Printer Settings
• Send Printout in Stripes
• Default Print DPI
Defines the default DPI for printing.
• Default DICOM Print DPI
Defines the default DPI for DICOM printing.

9.5 Cloud

• Servers

130 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Configure the cloud server settings as follows:

• Cloud Server Address: eu.online.planmeca.com
• Port: 443
In cases where Romexis client workstation is behind a firewall that
blocks outgoing connections, a firewall proxy server IP and port should
be configured as follows:
• Client Proxy Address: the IP address of the proxy server that proxies
HTTPS connections
• Proxy Port: the port of the proxy server that proxies HTTPS
connections
• Settings
• Use Cloud Id Prefix for Incoming Patients
If selected, the sender’s prefix (pmcn_) is added to Cloud patients
IDs when imported to Romexis.
• Require login for each Cloud sending
If selected, Cloud credentials are requested each time the Cloud
sending dialogue is opened.
• Download cloud cases in background (on Server)
If selected, cloud cases are downloaded automatically from cloud to
server.
• Pseudonymise patient name in Cloud sending
If selected, removes patient name from exported Cloud data so
name is not visible on receiver's end. Also anonymises DICOM
header and content.txt data file. Patient ID is still readable.

NOTE
See also section "Setting Romexis Cloud user account" on page 81.

9.6 DDX Dental

• DDX Site

Technical manual Romexis 131

9 Romexis Configuration tool parameters and settings

• Server Address
The host address of th DDX Dental cloud service provider. The
default address is:
http://www.ddxdental.com
• Client Proxy Address
Internet proxy address used in the practice, if any.
• Proxy Port
Port of the proxy address if proxy address is used.
• Register Romexis Application
• Client(s) using App Name
The application name the practice uses when communicating with
DDX cloud server. Security keys will be registered for the application
using this name.
• DDX Account Name
The DDX Dental account name used. This account name is used if
not defined for each user separately.
• App Public Key
The security public key registered for App Name. The keys are
created and shown in the web browser when registering the
application using the (Re-)Register button. Both keys must be
manually copy-pasted from the web browser display.
• App Private Key
Security private key.
• Test of DDX Link
• Test: Get Practice Info -button
If the practice is registered as a DDX client and the application
is successfully registered, the practice info is successfully found
and shown. If the test is passed, the registration and settings are
correctly executed.
• Test: Get Accounts Info -button
Gets and shows all labs registered for this practice.
• Laboratory Role Registration for Importing Case(s)
• Add New Lab Name (return)
To add new laboratory name, write the name to the field and press
return.
• Edit Lab Client Name
To select and/or edit the laboratory client name.
• Lab Public Key
The security public key registered for Lab Name. The keys are
created and shown in the web browser when registering the
application using the (Re-)Register button.
• Lab Private Key
Security private key.
• Save & Test Lab Keys
Click the Validate Lab Keys button to save and test the lab keys.

132 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

NOTE
See also section "Setting DDX user account" on page 83.

9.7 Usage Data Tracking

Romexis collects anonymous user interface interactions such as button

clicks, see below in more detail.
• Data being tracked
• System profile (operating system, available memory, license type
and content)
• Current location (country and city)
• Data about your interaction with the software (e.g. actions you
perform).
• Data NOT being tracked
• Personal or patient data (name, email address, file names,
workstation name, IP etc.)
• Any user activity outside of the Romexis application.
Usage of data tracking can be disabled/enabled in Romexis configuration, to
decide when to share anonymous data.
• Allow Usage Data Tracking
Enable or disable the anonymous user interface interaction tracking.
For more information on data processing, see Planmeca Romexis Software
Licence Terms.

9.8 Clinic Management

Technical manual Romexis 133

9 Romexis Configuration tool parameters and settings

9.8.1 PlanLink & Diagnostics

• Clinic Overview and Log Refresh-rate

Sets the refresh rate for the clinic status overview and log screens. The
high refresh rate may be useful for troubleshooting.
By enabling Show large icons setting, the unit icons in the clinic layout
are in bigger format. E.g. if there are only few units and the floor plan
figures are spacious, this can be enabled.
• PlanLink – Compact Unit Lock
Specifies whether the dental unit should be locked when PlanLink proxy
service is not available to collect diagnostic information. If locking is
enabled, the dental unit will be inoperable when the connected PC
running PlanLink proxy is shut down or otherwise connection cannot
be established between the PC and the dental unit. When connection is
re-established the dental unit will again become operable after a power
cycle.
• Save Diagnostic Events to Database
Specifies whether the diagnostic events and messages collected from
the dental unit should be save into the database. The default setting is
recommended.
• Export Ergodata-files
• Export to Zip -button

134 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Use this function to export all recorded diagnostic data (ergodata)

from dental units to a zip file for troubleshooting purposes.
• Dental Unit User Settings
• Send Service Modes
Enable this setting to include dental unit service mode settings when
dental unit settings are stored to database and restored back to
dental units. In normal operation this should be left disabled but can
be useful at dental unit installations if numerous new dental units
must be configured identically.
• E-mail notification server (SMTP)
The Romexis server can be configured to send alert e-mails when
specific diagnostic events take place in dental units. Romexis sends
the e-mails to the SMTP server configured with these settings. The
device alerts triggering the e-mails are configured in the Romexis Admin
module.
Note that the Romexis server software does not include the SMTP
server but the service must externally be available.
• Server Host Name
Defines the SMTP Server host.
• Server Port
Defines the SMTP server port.
• User Name and Password
Credentials used for connecting to the SMTP server. This is required
only with encrypted SMTP servers.
• Sender Address
Defines a custom sender address.
• Encryption
Choose from the following encryption method options:
• No Encryption
• STARTTLS
Encryption methods negotiated with SMTP server.
• SSL/TLS
Both SSL and TLS encryptions are required.

NOTE
The encryption method used must be supported by the e-mail server
used.
• E-mail notification settings
• Notification period (mins)
Defines the delay in minutes after which an error is considered to be
important enough to be reported in an e-mail. If an error is negated
by itself or fixed by a user within this time limit, then no error will be
reported. The error will still be shown in the dental unit event log.
• Don't e-mail for same error in (mins)
Defines the time limit during which a persistent error will not be
reported again.

Technical manual Romexis 135

9 Romexis Configuration tool parameters and settings

9.8.2 Unit Connections

Unit connections tab

Lists the configured unit connections.

Planmeca Compact Ethernet adapter service tab

Lists the Compact i dental units connected to the Clinic management. Use
the Search, Add, Update and Remove buttons to modify the list.
• Romexis Server Settings
• Enable Communication Service
Select to enable the communication to the unit.
• Enable Log (Troubleshooting only)
Because of performance issues, enable this setting only for
troubleshooting purposes.
• Service Control Port
Define port number for the service control port in the field.

136 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

• Max Heap Size (MB)

Set to 0 to automatically calculate used memory based on device
count. Heap size change should be approximately 24 MB per device.
• Java VM Parameters

• Service Control

9.8.3 Solanna Vision

• Solanna Vision Control Server

• Enabled
Enables the Planmeca Solanna Vision discovery in the network.
• Network Interface (optional)
If Romexis server workstation has many network interfaces, it may
be necessary to manually select which one is used for Planmeca
Solanna Vision discovery. Check the hints under the Network
Interface field and, if necessary, enter a value like eth0.
• Authentication and hi-res photos
When enabled, this Romexis server takes ownership of the
discovered Planmeca Solanna Vision devices and sets the
authentication credentials in them. This also allows high resolution
photos to be taken.
• Service Control Port
Defines the port number for the service control port number.
• Self Check Port
Defines the self check port number.
• Java VM Parameters
Solanna Vision has configurable parameters both on the server and
client side.
Normally it is not necessary to set these parameters at all. They may
be applicable in some network configurations or special situations.
In this field, the Romexis server parameters can be defined.
• Solanna Vision on Romexis Client
• Java VM Parameters

Technical manual Romexis 137

9 Romexis Configuration tool parameters and settings

In this field, the Romexis client parameters can be defined.

The parameters in this field will be applied on all Romexis clients
connecting to this Romexis server.
• Solanna Vision automatic credentials
In this field, the Planmeca Solanna Vision automatic credentials are
listed, and can be viewed.
• Update
Updates the selected credential(s).
• Export...
Allows exporting Solanna Vision configurations to a 3rd party
applications for viewing Planmeca Solanna Vision video streams
outside Romexis.
For more information on configuring the Planmeca Solanna Vision with
Romexis, see section "Configuring Solanna Vision" on page 185 and the
Planmeca Solanna & Planmeca Solanna Vision installation and technical
manual.

9.8.4 Floor names

Lists the defined floor names in the clinic management layout. Use the
Update and Clear buttons to modify the list.

138 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

9.8.5 Integrated communication

• DTS server
• Server Host Name
Fill out the field according to the Representational state transfer
(REST) web service data provided.
• User Name
Fill out the field according to the Representational state transfer
(REST) web service data provided.
• Password
Fill out the field according to the Representational state transfer
(REST) web service data provided.
• Enabled
Uncheck the box to temporarily disable the DTS service without
having to clear the data.
• Romexis Insights
• Disable
Check the option to disable the Romexis Insights.
• AMQPS
To enable the Romexis Insights, enable the AMQPS traffic from the
Romexis server to the cloud portal. Port 5671 is used for AMQPS
protocol over TCP/UDP.
• AMQPS HTTPS (websocket)
It is also possible to select AMQPS HTTPS (port 443).
• Service Control
After enabling the Romexis Insights communication, start the Romexis
Insights by pressing the Start Service button or by restarting the
Romexis server.

Technical manual Romexis 139

9 Romexis Configuration tool parameters and settings

9.8.6 DDS Communication

• Enabled
If selected, the DDS communication is enabled.
Enable the DDS communication if connecting the Planmeca ProX X-ray
unit (via ProX connector box) to Romexis Clinic Management.
• DDS domain
Defines the DDS domain identifier.
This value must match with the ProX connector box Network ID setting
to enable the communication between the Romexis and the Planmeca
ProX X-ray unit.
• NodeID
Defines a suffix for the used node ID, the final node ID is created as
follows:
CM_[SERVER|CLIENT]_<NodeID>
To activate the changes in these parameters, restart the Romexis service.

9.9 Security

140 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

9.9.1 Client

The Login and Approval settings affect the information requested from users
when logging into Romexis or when granting approvals. This allows for the
facilities to adjust the security measures in Romexis according to their local
policies.
• Login Username and Password
• User name and Password are required
When logging in to Romexis both user name and password are
required.
• Username required
Only user name is required when logging in.
• Username is not required
Username and password are not required when logging in.
• Login only with Swipe Card
When additionally selecting this option, the user can log in only with
a swipe card.

Technical manual Romexis 141

9 Romexis Configuration tool parameters and settings

• Automatic logout
By activating this option, the Romexis user is automatically logged
out from Romexis if not actively using the application. The logout
timer resets with mouse clicking.

NOTE
The logout does not take place during patient imaging.
• Automatic logout time in minutes
Defines the time in minutes after which the user is logged out, if no
actively using Romexis.
• Approval Username and Password
• Username and Password are required
When granting approvals e.g. for image acquisition requests,
Romexis asks for both username and password.
• User name required
Only user name is required.
• Approval only with Swipe Card
When selected the approval can only be made with swipe card.
• Password
• Maximum password age (days) (0 = never expires)
Set the value as days, or set to 0 for password that never expires.
• Minimum password length
Sets the required minimum length for the password.
• Maximum number of wrong password
Set the number of allowed wrong entries, or by setting to 0 (default)
wrong entries are not calculated).
• At least one digit required
At minimum one number is required in the password. This setting is
disabled by default.
• At least one special char required
At least one non-alphanumeric character (e.g. @,#,!,%,&,?) required
in the password. This setting is disabled by default.
• Swipe Card Userid
When swiping the card, the card produces an output text string that
contains the user ID and password.
• Track No in Swipe Card
Indicates the row in the text output from which the password string is
read. Assume e.g. the following typical Swipe Card output:
: %testusera6yz8cat?
;0000948721?
;20060101=20070101?
The User ID test user is located on the first track (0), starting from
the second column (1) and ending in the eight column (7).
• Start Column in Swipe Card

142 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Indicates the column in the text output where the password string
starts.
• End Column in Swipe Card
Indicates the column in the text output where the password string
ends.
• Swipe Card Password
See the description of the Swipe Card Userid above.
• Active Directory
Romexis can be configured to use Active Directory for user
authentication and permission management. Each Romexis user group
must be mapped to an Active Directory group in the Admin module.
• Allow login with AD username without AD server connection
Enables login with AD username without AD server connection. The
AD username for the Romexis user is defined in the Admin module/
Resource management with AD logon name parameter, see more in
section "Adding/updating user" on page 79.
If this option is used the AD server authentication is disabled and
vice versa.
• Use AD Authentication
Authentication of Romexis users against Active Directory.
• Use Nested Groups for user
Uses nested groups for user.
• Use SSL Encryption
Require SSL encryption during authentication.
• New Domain
Type the DNS domain you want to add to the list here, and press
Add. The domain is listed in the Dns Domain field below.
• Dns Domain
List of domains added. The Server Address field below corresponds
to the selected domain. To remove a domain, remove the text in this
box and press Enter.
This will also remove the Server Addresses linked to the domain.
• New Server
Type the server address you want to add to the list here, and press
Add. The server is listed in the Server Address field below.
• Server Address
List of server addresses added to the selected domain. To remove a
server, remove the text in this box and press Enter.
• Test SSO Auth
Tests the configuration against the Active Directory server.

NOTE
Additional configuration of the Windows client environments may be
required to enable Single Sign On authentication.
• Manage KeyVault Password and Encryption Keys

Technical manual Romexis 143

9 Romexis Configuration tool parameters and settings

NOTE
Before changing the KeyVault password or encryption keys, it is
strongly recommended to take backup of the Romexis database and the
KeyVault as if for some unexpected reason the changing of password or
encryption keys fails, some of the data in the database may irreversibly
become unavailable.

• Change Encryption Keys button

By clicking the button it is possible to change the KeyVault
encryption keys.
• Change Password button
To change the KeyVault password, enter first the old password to the
Old password field and the new password to the New password and
Re-enter new password fields, and click Change Password button.
• Manage Server Side Permission Checking
• Permission token expiry in minutes
Sets the token expiry period in minutes.

9.9.2 Server

• Require client approval

If enabled, the Romexis clients must be manually accepted to enable the
connection. To accept or reject a Romexis client, use the buttons in the
Clients list.
• Refresh list button
By clicking the button, the Clients list is refreshed.
• Regenerate All Certificates button
Click the button to revoke and recreate all existing certificates.
Note that all Romexis clients will lose connection until the new
certificates are installed.
• Export server certificates button
By clicking the button, you can export the Romexis server certificate as
a .pem file to a local folder to manually move it to the Romexis client.
The exported certificate is copied to the client folder of the Romexis
client installation.
• Clients
Lists all clients connected to the Romexis server and their information
and status.
If the Require client approval option is enabled, the clients can be
selected from the list and either the client connection can be accepted
(by clicking Accept button) or rejected (by clicking Reject button).

144 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

9.10 Image & Data Management

9.10.1 Data folders

• Romexis Data Folders

The Romexis Data Folders settings allows re-configuration of the
Romexis image and ergodata (dental unit diagnostic data) storage paths
can be re-configured and all existing data can be relocated to a new
folder.
• Set Path button
Use the Set Path button to specify a new root folder for
Romexis data folders. E.g. if the root folder is specified as
R:\romexis_data\ then romexis_images, romexis_cache
and romexis_ergodata folders will be automatically created under
it. After the Romexis service is restarted all new images will be
stored to the new location.
• Move data button
To move all existing data files to a new location and update all
database references to point to the moved files click the Move Data
button
It is possible to change the path to point to a new location and have
new files stored there while keeping existing files in the old location.
• Progress
In the field progress data of the data folder actions are shown.

NOTE
Romexis service must be restarted after changing the root path or moving
images for the changes to activate the modifications.

Technical manual Romexis 145

9 Romexis Configuration tool parameters and settings

9.10.2 Trash

• Reactivate and Empty Trash

To search for inactivated patients, images and devices select the
suitable alternative from the Fetch drop-down menu.
To reactivate patients, images or devices select the appropriate
alternative from the list and click the Reactivate button. The selected
items are restored to Romexis.
To permanently delete patients, images, attachments or devices from
Romexis database, click the Empty Trash button.

9.11 Start-up

NOTE
Start-up tabs are available only on Romexis server on Windows.

9.11.1 Client parameters

NOTE
This tab can be used to configure only the Client that is installed on this
current workstation.

146 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

• Connection to Romexis Server

• Server Address and Server Port
Define the Romexis server address into which the Romexis client
connects to. Host address can be either IP or DNS name.
• User ID and Password
Optional login information for the Romexis client.
• Java VM Parameters
• JVM Path
Set the Java Virtual Machine to be used by Romexis client.
• Enable the use of Direct3D pipeline

• Stack Size (kB)

Defines the amount of stack memory in use. This parameter is
optional, and needs to be configured only if certain TWAIN devices
are used.
• Max Heap Size (MB)
Defines the maximum amount of memory which Romexis client has
in use.
This can be also set by modifying the parameter's -Xmx value in the
Romexis.bat file on each client computer. The default value of the
parameter is set based on the amount of the memory installed.
• 3D Rendering
Defines the rendering method for 3D images.
• User Interface
• Language
Defines the language file used with Romexis client.

Technical manual Romexis 147

9 Romexis Configuration tool parameters and settings

• Main Window Size X and Main Window Size Y

These parameters can be used to force the client's main window to a
certain size.
• Default Monitor

9.11.2 Romexis Service

Romexis service is a Windows program that starts the Romexis server every
time Windows is started. In this tab all the settings for the Romexis service
can be configured.

NOTE
Changes to these parameters take effect only after you restart Romexis
service.

• Romexis Service
• Windows Service Name
Defines the name of the Romexis service in the Windows services
list.
• Executable Name
The name of the wrapper executable to be used as Romexis service.
• Startup Delay (min)
Defines the Romexis service startup delay in minutes.
• Java VM Parameters
These parameters affect the way the Romexis server is launched.
• JVM path
Defines the path to the Java Virtual Machine in use.
• Classpath
Defines the files that the Virtual Machine uses.
• Main Class
Defines the Main Class inside RomexisServer.jar file.
• Optional App Args
Allows passing optional configuration parameters to the Romexis
server, normally specified in romexis_server.properties file.
• Optional JVM Args

148 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Allows passing optional configuration parameters to the

Romexis server’s Java Virtual Machine. Normally specified in
RomexisService.ini file.
• Max Heap Size
Defines the maximum amount of memory which the Romexis server
has in use. The default value is 3000.
Note, working with large volumes, for example captured with
Planmeca Viso, ProMax 3D Mid, ProMax 3D Max, or having
large environments with several simultaneous users, requires more
memory allocated to the server than the default 3000.
• Service Control
• Start Service -button
Starts the Romexis service.
• Stop Service -button
Stops the service.
• Remove Service -button
Stops the service and removes it from the Windows services list.
• Show Log -button
Opens the Romexis service Log.

9.12 Server Parameters

9.12.1 Server

RMI - Server/Client Communication

• RMI Server Host

Technical manual Romexis 149

9 Romexis Configuration tool parameters and settings

The Romexis server IP or DNS name is configured here.

• RMI Server Port
Defines the port for the Romexis server-client communication.
• Configuration Port
Defines the port that is used when the Romexis client acquires the
settings listed below from the server. If this port is changed, a port must
be defined on each client Romexis.bat file.
• Port range begin, Port range end
You can define a port range for RMI communication between the
Romexis client and the server.
If port range is defined as Port range begin = 0 and Port range end = 0
(the default), random free ports will be used.
It is recommended to use a range covering as much ports as possible for
better performance.
• RMI SSL encryption
Enable or disable SSL encryption over client-server communication.
Enabled by default.
• Server notifications
Enable or disable notifications for new images to clients. Notifications are
sent to inform other clients that new images are available for the current
patient.

Mobile Server
• mRomexis Server Enabled and mRomexis Server Port
Enables communication with mRomexis clients and allows configuration
of the port where incoming mRomexis client communications are
listened to (default 8093). This setting is enabled is by default in new
installations.

NOTE
Also configure your firewall to allow access the following executable:
C:\Program
Files\Planmeca\Romexis\server\RomexisService64.exe
• Max concurrent xray sessions
Defines the limit of how many mRomexis applications can
simultaneously acquire x- ray images.
Default value is 0. The mRomexis uses Romexis server for capturing
images. When this value is 1 or more, the Romexis client collects
DIDAPI configuration settings and calibration files from the client
computers and sends them to the server.

DICOM/HL7 RxBroker Service

NOTE
The DICOM/HL7 RxBroker is supported only on Windows operating
systems.

If enabled the RxBroker process is started automatically in Romexis server

startup. Enable this option if the DICOM RxBroker service is in use.

150 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

NOTE
The HL7 RxBroker is not supported in the current Romexis software.

Server Log
Click the Show Log button to view the log.

Clinic Management
• Control Module
The Start Module button loads and starts the Clinic management module
(RxServerClinic.jar).
The Stop Module button stops and unloads the Clinic management
module from the running Romexis server. It can be restarted by pressing
Start Module button.
• Version
Shows the current version of the running Romexis Clinic Management
instance.
• Unit Communication (PlanLink)
• Enable communication
Enables the Romexis server to accept the unit connection requests
from Planmeca units. If disabled all unit connections are disabled.
• Communication port
Defines the port number in the Romexis server which is used by the
Planmeca units for connecting to the server.
• Enable unit time sync for Compact i
If enabled, the time in the Compact I dental units connected to the
Clinic Management is synchronised by the Romexis server.
• Save log only if patient is selected
Saves the log only if the patient is selected.
• Enable debugging log
When enabled, starts the logging of the diagnostic communication.
• Unit Monitoring / Controlling
• Port range begin
Sets the smallest port number included to the range of unit
monitoring.
• Port range end
Sets the biggest port number included to the range of unit
monitoring.
• File Server (Class Server)
• File server enabled
File server provides several files for the Romexis clients, including
dental unit quick guides, maintenance and infection control
instructions and dental unit control panel.
In addition, if this option is selected, the Romexis server provides the
latest Romexis connection classes to Romexis connection proxies
which communicate with the dental units. This is needed only in
special cases, e.g. valid for Planmeca Compact i Chairside PC
connections.

Technical manual Romexis 151

9 Romexis Configuration tool parameters and settings

• File server port

This is the port the server listens to.
• VNC Server (Unit control panel)
Defines the VNC server port.

9.12.2 Database

• Connection Pool
• Use Connection Pool

• Database Connection
The Database Connection field displays a list of alternative databases for
use with Romexis.
• Solid
• Oracle
• SQL server (jTDS)
• Firebird
• SQL Server (MS)
• HSQLDB (embedded)
The database options above, when selected, display the following fields:
• JDBC connect URL
Romexis uses JDBC driver to connect to the database. If you use a
different database than the one provided in Romexis installation, you
must acquire JDBC driver for the alternative database.
JDBC Connect URL is the connection string which JDBC driver uses
to locate the data source. An example URL can be seen beside the
database names, but because it is defined by the provider of the
driver, it can differ from the example URL. In such case contact the
provider of the JDBC driver.

152 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

• User ID and Password

The login information to enter Romexis Database.
• Test Connection -button
To test the database connection, click this button.
The SQL Server (MS) option, when selected, displays the following fields
in addition to listed above:
• Use SSL encryption
Enable SSL encryption for communication between Romexis server
and database. This option is enabled by default on new installations.
• Trust Server Certificate
Encryption uses a self-signed certificate generated by SQL Server by
default. If you plan to use a third party certificate you should export
the certificate into a trustStore and deselect this option.
The following options are also available if the SQL Server (MS) option is
selected, but are disabled if the Trust Server Certificate option check box
(above) is checked:
• Path to the certificate trustStore
Determines the path to the trustStore where the server
authentication certificate is imported.
• TrustStore password
Defines the used password to trustStore.
• Host name in certificate
Type the hostname that is defined in your certificate. This is used to
validate the certificate.
The Complete URL shows you the URL that is used when Romexis
connects to the database.

Technical manual Romexis 153

9 Romexis Configuration tool parameters and settings

9.12.3 External Communication

• Datagate - External Patient Management System

Romexis can connect to an external patient management system
through a data gate. The data gate is a connection to the database from
which Romexis polls for new external information.
• Datagate Enabled
Enables or disables the data gate connection.
• Database settings
The connection settings for the data gate are similar as the general
Romexis database settings, see description in section "Database" on
page 152.
• Active from (24h Clock, HHMM)
Defines the starting hour of the day for the automatic data gate
polling.
• Active to (24h Clock, HHMM)
Defines the last hour of the day until which the data gate polling is
on.
• Poll Interval (min)
Defines the time interval between consecutive queries into the
database.
• DICOM
• DICOM SCP Enabled

154 Romexis Technical manual

 9 Romexis Configuration tool parameters and settings

Enables Romexis to retrieve DICOM images (DICOM Storage or

DICOM Q/R).
This setting is enabled by default.
• DICOM SCU Enabled
Enables Romexis automatically send the DICOM images to an
external PACS image archive after acquisition.
Romexis polls for new DICOM images from the Romexis database
according to the polling setting below.
• Active from (24h Clock, HHMM)
Defines the starting hour of the day for automatic DICOM polling.
• Active to (24h Clock, HHMM)
Defines the last hour of the day until when the DICOM polling is
on.
• Poll interval (min)
Defines the time interval (in minutes) between consecutive
queries into image database.

Technical manual Romexis 155

10 Romexis server and unit connection configuration

10 Romexis server and unit connection configuration

NOTE
The configurations in this chapter are mainly relevant when configuring the
optional Romexis Clinic Management module.

10.1 Before you start Romexis server and unit connection configuration
Before setting up and configuring the network for Romexis server/client(s),
plan carefully the following issues:
• Plan for IP addresses and port numbers used in the network.
• Take care that there are no software firewall settings in the Romexis
server or client workstations, and no hardware firewalls in the network,
blocking the ports used for device communication.

NOTE
If several Romexis instances are installed to the same workstation, be extra
careful with the port numbers given to the different server/services running
on the workstation, each of them must have an unique port number.

10.2 Configuring Romexis server settings

Steps
1. Start the Romexis Configuration tool.
For instructions, see section "Starting Romexis Configuration tool" on
page 107.

156 Romexis Technical manual

 10 Romexis server and unit connection configuration

2. From the directory tree on the left side, under Server Parameters, click
Server.
Related parameters appears to the right panel.

3. Check and/or set the values for the following parameters, listed in the
table below.

Parameter Description
RMI - Server/Client Communication
RMI Server Host Defines the Romexis server IP address or
DNS name.
RMI Server Port Defines the port for Romexis server-
client-communication.
The default value is normally valid.
Change only in some special cases,
e.g. there are more than one instance
of Romexis installed to the same
workstation.
File Server (Class Server)
File server enabled File server provides several files for the
Romexis clients, including dental unit
quick guide, maintenance and infection
control instructions and dental unit control
panel.
Enable this setting (by default this is
disabled).

Technical manual Romexis 157

10 Romexis server and unit connection configuration

Parameter Description
File server port This is the port the server listens to.
The default value is normally valid.
Change only in some special cases,
e.g. there are more than one instance
of Romexis installed to the same
workstation.
Unit Communication (PlanLink)
Enable communication Enables the Romexis server to accept the
unit connection requests from the units. If
disabled all unit connections are disabled.
This must be enabled (by default this is
disabled).
Communication port Defines the port number in the Romexis
server which is used by the units for
connecting to the server.
The default value is normally valid.
Change only in some special cases,
e.g. there are more than one instance
of Romexis installed to the same
workstation.
Enable unit time sync If enabled, the time in the dental units
connected to the Clinic Management is
synchronised by the Romexis server.
By default enabled, keep enabled.
Unit Monitoring / Controlling
Port range begin Sets the smallest port number included to
the range of unit monitoring. Default value
is 6000.
Port range end Sets the biggest port number included to
the range of unit monitoring. Default value
is 6700.
For example, with default values, unit
monitoring port number range is 6000 -
6700.
Usually the default values are sufficient,
only if there is a huge number of units to
be connected to the Clinic Management,
the range must be extended.
Leave default values for the rest of the parameters in the panel.
4. Click the OK button to save the changes and exit the Romexis
Configuration tool.
5. Restart the Romexis service to activate changes.
For instructions, see section "Restarting Romexis service" on page 108.

10.3 Configuring Romexis unit connections

In the following sections, instructions for configuring and enabling the
connection between Romexis and different dental, X-ray and milling unit.

158 Romexis Technical manual

 10 Romexis server and unit connection configuration

Select appropriate section and follow the instructions given for the unit/
model to be connected.
You can test your configuration with the Romexis Clinic Management -
Virtual Clinic tool. For more information, see section "Starting Romexis
Virtual Clinic" on page 200.

10.3.1 Configuring Sovereign Classic connection

Before you begin

It is assumed that during the Planmeca Sovereign Classic dental unit
installation, the Ethernet cable from the dental unit is connected and routed
to the local area network (LAN).

1 Ethernet cable
2 Local area network (LAN)
3 Romexis server

Steps
1. Touch the Program and About this unit buttons.

The following information is displayed in the About this unit window (the
figure below is an example only).

Technical manual Romexis 159

10 Romexis server and unit connection configuration

2. Touch the Network settings arrow (>) to open the network settings menu.

In the menu, you can scroll the list either from the list itself, from the
scroll bar to the right, or by using the Up and Down buttons. Press the
Edit or Arrow button next to the setting to edit the value.
When modifying these settings, you will be prompted to enter the PIN-
code 1701.
3. Edit the following settings in the Network settings menu.
• Name
The name of the dental unit shown in the Romexis. The unit name
must be unique and it has to be changed before connecting the unit
to the Romexis.
• IP address
The dental unit’s IP address. The IP address must be unique.
• Network mask
Subnet mask. The default is 255.255.255.0.
• Gateway
Default gateway. The default is 0.0.0.0.
• Romexis server IP address
IP address of the Romexis server, as defined in Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis server port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change the this setting only if you have
changed the default port 6812 to some other port in Romexis
configuration (in section "Configuring Romexis server settings" on
page 156.
• Romexis connection

NOTE
Do not enable the Romexis connection before all the above dental
unit’s network settings are correctly set.

Enable Romexis connection, toggle the arrow button and select

Romexis and local users option.

160 Romexis Technical manual

 10 Romexis server and unit connection configuration

4. Press OK button to save the changes.

5. Restart the dental unit.

Results
When the connection to Romexis is enabled and the connection is on, the
Romexis symbol on the touch panel is visible.
When the connection is disabled or off, or if the dental unit configuration
does not include the Romexis Clinic Management module, the symbol is
grey.

What to do next
You can add the dental unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.2 Configuring Compact i5 connection

Steps
1. Connect the dental unit to the clinic network (if not yet done).
An example installation of the physical LAN connection is shown on the
figure below.

1 Ethernet interface
2 Ethernet cable
3 Local area network (LAN)
4 Romexis server
1.a. Switch off the dental unit.
1.a. Open the cuspidor door and remove the electronics control box
cover.
See the dental unit's technical manual for more detailed
instructions.

Technical manual Romexis 161

10 Romexis server and unit connection configuration

1.b. Connect the Ethernet cable to the connector located on the right
upper corner of the Main PCB.

1.c. Route the Ethernet cable from the cuspidor to local area network
(LAN).
2. Switch on the dental unit.
3. Touch Program.

4. Touch About this unit.

The following information is displayed in the About this unit window (the
figure below is an example only).

162 Romexis Technical manual

 10 Romexis server and unit connection configuration

5. Touch the Network settings arrow (>) to open the network settings menu.
Note, the following is an example only and does not necessarily portray
the actual situation.

You can scroll the list either from the list itself, from the scroll bar to the
right, or by using the Up and Down buttons.
6. Edit the following settings in the Network settings menu.
• Name
The name of the dental unit shown in Romexis. The unit name must
be unique and it has to be changed before connecting the unit to
Romexis.
• DHCP
When DHCP is enabled, the dental unit’s IP address is assigned by
a DHCP server.
From the Romexis connection point of view, the DHCP can be
enabled or disabled.
• IP address
The dental unit’s IP address. The default is 10.0.0.1
The IP address must be unique.
• Network mask
Subnet mask. The default is 255.255.255.0
• Gateway
Default gateway. The default is 0.0.0.0
• Romexis server IP address
IP address of the Romexis server, as defined in Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis server port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in Romexis configuration (in
section "Configuring Romexis server settings" on page 156).

Technical manual Romexis 163

10 Romexis server and unit connection configuration

• Romexis connection

NOTE
Do not enable the Romexis connection before all the above dental
unit’s network settings are correctly set.

Toggle the arrow button to enable the connection to Romexis.

7. Touch OK to save the changes.

8. Restart the dental unit.

Results
When the connection to Romexis is enabled and the connection is on, the
Romexis symbol on the touch panel is visible.
When the connection is disabled or off, or if the dental unit configuration
does not include the Romexis Clinic Management module, the symbol is
grey.

What to do next
You can add the dental unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.3 Configuring Compact i3 connection

Steps
1. Connect the dental unit to the clinic network (if not yet done).
An example installation of the physical LAN connection is shown on the
figure below.

1 Dental unit
2 Ethernet interface
3 Ethernet cable
4 Local area network (LAN)
5 Romexis server
1.a. Switch off the dental unit.

164 Romexis Technical manual

 10 Romexis server and unit connection configuration

1.b. Remove the junction box cover.

See the dental unit's technical manual for more detailed
instructions.
1.c. Connect the Ethernet cable to the connector located on the left
upper corner of the Main control PCB.

1.d. Route the Ethernet cable from the cuspidor to local area network
(LAN).
2. Switch on the dental unit.
3. Touch Program.

Technical manual Romexis 165

10 Romexis server and unit connection configuration

4. Touch About this unit.

The following information is displayed in the About this unit window (the
figure below is an example only).

5. Touch the Network settings arrow (>) to open the network settings menu.
Note, the following is an example only and does not necessarily portray
the actual situation.

You can scroll the list either from the list itself, from the scroll bar to the
right, or by using the Up and Down buttons.
6. Edit the following settings in the Network settings menu.
• Name
The name of the dental unit shown in Romexis. The unit name must
be unique and it has to be changed before connecting the unit to
Romexis.
• DHCP
When DHCP is enabled, the dental unit’s IP address is assigned by
a DHCP server.
From the Romexis connection point of view, the DHCP can be
enabled or disabled.
• IP address

166 Romexis Technical manual

 10 Romexis server and unit connection configuration

The dental unit’s IP address. The default is 10.0.0.1

The IP address must be unique.
• Network mask
Subnet mask. The default is 255.255.255.0
• Gateway
Default gateway. The default is 0.0.0.0
• Romexis server IP address
IP address of the Romexis server, as defined in Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis server port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in Romexis configuration (in
section "Configuring Romexis server settings" on page 156).
• Romexis connection

NOTE
Do not enable the Romexis connection before all the above dental
unit’s network settings are correctly set.

Toggle the arrow button to enable the connection to Romexis.

7. Touch OK to save the changes.

8. Restart the dental unit.

Results
When the connection to Romexis is enabled and the connection is on,
Romexis symbol on the touch panel is visible.
When the connection is disabled or off, or if the dental unit configuration
does not include the Romexis Clinic Management module, the symbol is
grey.

What to do next
You can add the dental unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

Technical manual Romexis 167

10 Romexis server and unit connection configuration

10.3.4 Configuring Compact i v2 (touch panel) connection

About this task

An example of the physical LAN connection of the system is shown on the
figure below.

1 Ethernet interface
2 Ethernet cable
3 Local area network (LAN)
4 Romexis server

Steps
1. Open the cuspidor door and remove the electronics control box cover.
2. Connect the Ethernet cable to the connector located on the right upper
corner of the Main control PCB.

3. Route the Ethernet cable from the cuspidor to local area network (LAN).

168 Romexis Technical manual

 10 Romexis server and unit connection configuration

4. Touch the Program and About this unit button.

The following information is displayed in the About this unit window (the
figure below is an example only).

5. Touch Network settings arrow (>) to open the network settings menu.

In the menu, you can scroll the list either from the list itself, from the
scroll bar to the right, or by using the Up and Down buttons. Press the
Edit or Arrow button next to the setting to edit the value.
When modifying these settings, you will be prompted to enter the PIN-
code 1701.
6. Edit the following settings in the Network settings menu.
• Name
The name of the dental unit shown in the Romexis. The unit name
must be unique and it has to be changed before connecting the unit
to the Romexis.
• IP address
The dental unit’s IP address. The IP address must be unique.
• Network mask
Subnet mask. The default is 255.255.255.0.
• Gateway
Default gateway. The default is 0.0.0.0.
• Romexis server IP address

Technical manual Romexis 169

10 Romexis server and unit connection configuration

IP address of the Romexis server, as defined in Romexis

Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis server port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in Romexis configuration (in
section "Configuring Romexis server settings" on page 156).
• Romexis connection

NOTE
Do not enable the Romexis connection before all the above dental
unit’s network settings are correctly set.

Enable Romexis connection, toggle the arrow button and select

Romexis and local users option.
7. Press OK to save the changes.
8. Restart the dental unit.

Results
When the connection to Romexis is enabled and the connection is on, the
Romexis symbol on the touch panel is visible.
When the connection is disabled or off, or if the dental unit configuration
does not include the Romexis Clinic Management module, the symbol is
grey.

What to do next
You can add the dental unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

170 Romexis Technical manual

 10 Romexis server and unit connection configuration

10.3.5 Configuring Compact i v2 (keyboard) connection

About this task

An example of physical LAN connection of the system is shown on the figure
below.

1 Ethernet interface
2 Ethernet cable
3 Local area network (LAN)
4 Romexis server

Steps
1. Open the cuspidor door and remove the electronics control box cover.
2. Connect the Ethernet cable to the connector located on the right upper
corner of the Main PCB.

3. Connect the other end of the Ethernet cable (connected in the previous
step) to a workstation which is configured to a 10.0.0.x subnet.
The dental unit default IP address is 10.0.0.1. This must be changed to
the clients IP network configuration.
4. Open a web browser in the computer connected to the Ethernet cable
and enter 10.0.0.1 to the address field.
A PIN code dialogue appears.

Technical manual Romexis 171

10 Romexis server and unit connection configuration

5. Enter the PIN code 1701 and click Login button.

The unit configuration interface opens to the browser, an example figure
below.

6. Modify the values under Change settings: title as described below.

• Unit name
Defines the dental unit name, visible in the Clinic Management. Set
according to the device naming plan. The name must be unique.
• Inet addr.
Defines dental unit own IP address. Set (if not yet modified during
the installation) according to the IP network plan. The IP address
must be unique.
• Mask
Defines subnet mask. The default value is 255.255.255.0.
• Gateway
Defines default gateway. The default value is 0.0.0.0.

172 Romexis Technical manual

 10 Romexis server and unit connection configuration

• Romexis addr.
IP address of the Romexis server, as defined in the Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in Romexis configuration (in
section "Configuring Romexis server settings" on page 156).
• Mode (SM210)
Set this to value 1 or 2.
7. Click Save button.
8. Exit the browser.
9. Restart the dental unit.
10. Route the Ethernet cable from the cuspidor to the local area network
(LAN).

What to do next
You can add the dental unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.6 Configuring ProSensor HD connection

Before you begin

NOTE
Planmeca ProSensor HD Clinic Management support is only available for
the Ethernet box setup, not for the USB version.

NOTE
ProSensor HD Clinic Management support is available for ProSensor
(Ethernet) software version 2.5.8 onwards.

Technical manual Romexis 173

10 Romexis server and unit connection configuration

An example of the physical LAN connection of the system is shown on the

figure below.

1 Sensor with cable

2 ProSensor device (Ethernet)
3 Power over Ethernet (PoE) port
4 Local area network (LAN)
5 Romexis server

NOTE
The adapter box is necessary to the system installation. The ProSensor HD
will not function if you connect the Ethernet cable directly from the Romexis
server through the local area network (LAN) to the ProSensor device.

Steps
1. Login to the ProSensor main page.
Use a internet browser and use www-address below to access the
ProSensor main page.
http://172.26.150.150/index.html

NOTE
The 172.26.150.150 is the default IP address, if changed or the DHCP
is used, see more instructions on how to configure the in device's
installation manual.
2. Click Network Configuration.

174 Romexis Technical manual

 10 Romexis server and unit connection configuration

3. Fill in the following fields.

• Device Name
Enter the name for the device that appears in the Romexis Clinic
Management module.
• CM-IPAddress
Enter the IP address of the Romexis server.
• CM port
Enter the Romexis Clinic Management port.
4. Click the Send box.
A yellow LED switches to flashing green state, then the box restarts.
For more information on the Ethernet interface setup, see device's
installation manual.

10.3.7 Configuring ProMax X-ray unit connection

Before you begin

It is assumed that the X-ray unit and reconstruction PC (Reco PC) are
installed and connected to the Romexis workstation, according to the
instructions given in the X-ray unit’s installation manual.

Steps
1. Switch on the X-ray unit.

Technical manual Romexis 175

10 Romexis server and unit connection configuration

2. In the control panel, touch the service spanner at the top left corner
of the main view to open the settings menu and select 1600 Clinic
Management.

3. Set the following values to the appearing parameters.

• Romexis Server IP
IP address of the Romexis server, as defined in the Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis Port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in Romexis configuration (in
section "Configuring Romexis server settings" on page 156).
• Device Number
Enter an unique number for the X-ray unit.
• PlanLink Communication
Set the switch to ON position.
4. Save the changes, touch the green check mark button.
5. Restart the X-ray unit.

What to do next
You can add the X-ray unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.8 Configuring ProOne X-ray unit connection

Before you begin

It is assumed that the X-ray unit is installed and connected to the Romexis
workstation, according to the instructions given in the X-ray unit’s installation
manual.

Steps
1. Switch on the X-ray unit.

176 Romexis Technical manual

 10 Romexis server and unit connection configuration

2. In the control panel, touch the service spanner at the top right corner
of the main view to open the User settings menu and select Clinic
Management (U1600).

3. Set the following values to the appearing parameters.

• PlanLink Communication
Set the switch to On to enable the Clinic Management
communication.
• Romexis Server IP
IP address of the Romexis server, as defined in the Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Romexis Server Port
Romexis communication port number, as defined in Romexis
Configuration tool (Server Parameters > Server > Communication
port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in Romexis configuration (in
section "Configuring Romexis server settings" on page 156).
• Device Number
Enter an unique number for the X-ray unit.
4. Save the changes, touch the green check mark button.
5. Restart the X-ray unit.

Technical manual Romexis 177

10 Romexis server and unit connection configuration

What to do next
You can add the X-ray unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.9 Configuring ProX connections

Before you begin

It is assumed that the Planmeca ProX X-ray unit with ProX connector box
are installed and configured according to the instructions given in their own
manuals, and are physically connected to the same local area network with
the Romexis server.

NOTE
The Clinic Management support is only available if the X-ray unit is equipped
with ProX connector box.

About this task

An example of the physical LAN connection of the system is shown on the
figure below.

1 X-ray unit
2 ProX connector box
3 Local area network (LAN)
4 Romexis server

Steps
1. Start and login to the Romexis Configuration tool.
See section "Starting Romexis Configuration tool" on page 107.
2. From the directory tree on the left side, under the Clinic Management,
click the DDS Communication.
3. Configure the settings as follows.
• Tick the Enabled checkbox to enable the DDS communication with
the X-ray unit.
• Set the DDS domain value to match the value defined in the ProX
connector box Network ID setting (note, in both the default value is
9).

178 Romexis Technical manual

 10 Romexis server and unit connection configuration

• Optionally, enter NodeID. The defined ID is used as a suffix

for the used node ID (created with formula: CM_[SERVER|
CLIENT]_<NodeID>).
Note, the NodeID is not the unit name used in the Clinic
Management module.
4. Click OK button.
5. Restart the Romexis service to activate the changes.
See section "Restarting Romexis service" on page 108.

What to do next
You can add the X-ray unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.10 Configuring PlanMill 40 S milling unit connection

Before you begin

It is assumed that the Planmeca PlanMill 40 S milling unit is installed
according to the milling unit's installation manual.
The Romexis server must have network connection with the milling unit, for
example, as shown in the following figure.

1 Milling unit
2 Router
3 Local area network (LAN)
4 Romexis server

NOTE
The milling unit uses a static IP addresses for all system components. Check
all IP addresses within the network to avoid conflicts in the network.

About this task

Check the service configuration settings in the milling unit and modify if
necessary, follow the steps below.

Steps
1. Set up a connection between Romexis and the milling unit.
For more information on setting up the connection, see milling unit's
installation manual.

Technical manual Romexis 179

10 Romexis server and unit connection configuration

2. In the milling unit user interface, browse to C:\Program

Files (x86)\Planmeca\Planmeca PlanMill 40 S Clinic
Management Service\ folder.
3. Open the ClinicMgmtService.exe.config file.
4. In the file, check and edit if necessary, the Romexis server network
settings in the following lines.
• Edit the line below to contain the Romexis server IP address, as
defined in the Romexis Configuration tool (Server Parameters >
Server > RMI Server Host setting).
<add key="RomexisServerAddress" value="10.11.12.11"/>
• Edit line below to contain the Romexis communication port number,
as defined in Romexis Configuration tool (Server Parameters >
Server > Communication port setting).
<add key="RomexisServerPort" value="6812"/>
• Edit the line below to contain the milling unit’s own IP address.
<add key="DevicePublicAddress" value="10.11.12.15"/>
• Edit the line below to contain the milling unit’s own port number.
<add key="DevicePublicPort" value="6811"/>
5. Save the file.
6. Restart the milling unit if any changes to the file were made.

What to do next
You can add the milling unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.3.11 Configuring Creo C5 connection

Before you begin

It is assumed that the Planmeca Creo C5 printer is installed according to the
device's quick installation guide.
The Romexis server must have network connection with the printer, for
example as shown in the figure below.

1 Printer
2 Local area network (LAN)
3 Romexis server

180 Romexis Technical manual

 10 Romexis server and unit connection configuration

NOTE
The Romexis Clinic Management support is available for the printer in
release 1.1.0 or later.

Steps
1. Switch on the printer.
2. From the printer's control panel main screen, touch the Settings button.

3. In the Settings menu, touch the Romexis option.

4. In the Romexis settings menu, fill the Romexis server network settings.
• Server address
The IP address of the Romexis server, as defined in the Romexis
Configuration tool (Server Parameters > Server > RMI Server Host
setting).
• Server port
The Romexis communication port number, as defined in the
Romexis Configuration tool (Server Parameters > Server >
Communication port setting).
The default is 6812. Change this setting only if you have changed
the default port 6812 to some other port in the Romexis configuration
(in section "Configuring Romexis server settings" on page 156).
5. Enable the connection by touching the Romexis enabled button to
enabled-position.
6. To save the changed settings, touch the OK button.

7. Restart the printer.

Results
When the connection to Romexis is enabled and the connection is on, the
Romexis symbol on the touch panel is visible.
When the connection is disabled or off, or if the dental unit configuration
does not include Romexis Clinic Management module, the symbol is grey.

What to do next
You can add the printer unit to the Clinic Management module, see more
instructions in section "Clinic Management configuration" on page 190.

10.4 Configuring intraoral camera

About this task

Carry out these steps for the dental units equipped with intraoral camera.

Technical manual Romexis 181

10 Romexis server and unit connection configuration

Steps
1. Install intraoral camera and connect cables.
For more instructions, see intraoral documentation and the figure below.

1 Romexis server
2 Local area network (LAN)
3 Intraoral USB cable
4 Display cable
5 Romexis client
2. Configure Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
3. Configure dental unit network connection and settings and enable
Romexis connection in the dental unit (if not yet done).
See section "Configuring Romexis unit connections" on page 158.
4. Start dental unit’s Romexis client workstation.
5. Start Romexis.
6. Click Admin button and selet Local Settings > Dental Unit.
7. Enable Connect to Dental Unit at Startup setting and select the dental
unit in question from the drop-down menu.

8. To activate changes, restart Romexis client and dental unit.

10.5 Configuring PlanScan scanner

Before you begin

It is assumed that the Planmeca PlanScan scanner is installed to the dental
unit and connected to the Romexis client/server.

182 Romexis Technical manual

 10 Romexis server and unit connection configuration

The following figure shows an example network configuration with Planmeca

PlanScan scanner.

1 Romexis server
2 Local area network (LAN)
3 PlanScan FireWire cable
4 Display cable
5 Romexis client

About this task

Carry out these steps for the dental units equipped with PlanScan scanner.

Steps
1. Configure Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable
Romexis connection in the dental unit (if not yet done).
See section "Configuring Romexis unit connections" on page 158.
3. Start the dental unit’s Romexis client workstation.
4. Start the Romexis.
5. Click Admin button and select Local Settings > Dental Unit.
6. Enable the Connect to Dental Unit at Startup setting and select the
dental unit in question from the drop-down menu.

7. Check that Port Number under the PlanScan Control is not in any other
use.
8. To activate changes, restart Romexis client and the dental unit.

Technical manual Romexis 183

10 Romexis server and unit connection configuration

10.6 Configuring Emerald scanner

Before you begin

It is assumed that the Planmeca Emerald scanner is installed to the dental
unit and connected to the Romexis client/server.
The following figure shows an example network configuration with the
scanner.

1 Romexis server
2 Local area network (LAN)
3 Emerald scanner USB 3.0 cable
4 Display cable
5 Romexis client

About this task

Carry out these steps for the dental units equipped with scanner.

Steps
1. Configure the Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable
Romexis connection in the dental unit (if not yet done).
See section "Configuring Romexis unit connections" on page 158.
3. Start the dental unit’s Romexis client workstation.
4. Start Romexis.
5. Click Admin button and select Local Settings > Dental Unit.
6. Enable Connect to Dental Unit at Startup setting and select the dental
unit in question from the drop-down menu.

184 Romexis Technical manual

 10 Romexis server and unit connection configuration

7. To activate changes, restart Romexis client and the dental unit.

10.7 Configuring dental unit touchpad functionality

About this task

Carry out these steps to enable the remote touchpad functionality in the
dental unit.

Steps
1. Configure Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable
Romexis connection in the dental unit (if not yet done).
See section "Configuring Romexis unit connections" on page 158.
3. Start the dental unit’s Romexis client workstation.
4. Start Romexis.
5. Click Admin button and select Local Settings > Dental unit.
6. Enable the Connect to Dental Unit at Startup setting and select the
dental unit in question from the drop-down menu.

7. Enable Enable remote control setting under the Remote TouchPad and
Keyboard control.

8. Check that Port Number is not in any other use.

9. To activate changes, restart Romexis client and the dental unit.

10.8 Configuring Solanna Vision

Before you begin

There are few options for configuring the Planmeca Solanna Vision with the
Romexis, before starting, see the Planmeca Solanna & Planmeca Solanna
Vision installation and technical manual for more information.

Steps
1. Configure Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable
Romexis connection in the dental unit (if not yet done).
See section "Configuring Romexis unit connections" on page 158.

Technical manual Romexis 185

10 Romexis server and unit connection configuration

3. Connect the Solanna Vision network cable.

The following figure shows an example network configuration with
Solanna Vision.

1 Dental unit
2 Dental unit's Ethernet cable
3 Solanna Vision's Ethernet cable
4 Local area network (LAN)
5 Romexis server
6 Romexis client
4. Configure network settings in the dental unit.
4.a. Switch on the dental unit.
4.b. Touch the Program button.

4.c. Touch the About this unit button.

4.d. Touch the Solanna Vision tab.

186 Romexis Technical manual

 10 Romexis server and unit connection configuration

4.e. Modify the Solanna Vision network settings.

• If the Dynamic Host Configuration Protocol (DHCP) is used in

the network:
Toggle the DHCP button to enable the DHCP. A blue button
means that DHCP is enabled.
When DHCP is enabled, Solanna Vision's IP address is
assigned by a DHCP server. DHCP is enabled by default.
• If static IP address(es) is used in the network, disable the
DHCP setting above, and enter the following settings:
• IP address
The IP address must be unique.
• Netmask
Defines the subnet mask. The value default is:
255.255.255.0
• Gateway
Defines the default gateway. The default value is: 0.0.0.0
4.f. Touch the OK button to save the changes.

4.g. Restart the dental unit.

5. Enable the Solanna Vision discovery in the Romexis server.
5.a. Start the Romexis Configuration tool in the Romexis server.
See section "Starting Romexis Configuration tool" on page 107.
5.b. From the directory tree on the left side, under the Clinic
Management, click Solanna Vision.
5.c. Activate the Enabled option.

Technical manual Romexis 187

10 Romexis server and unit connection configuration

If the Romexis server workstation has many network interfaces,

it may be necessary to manually select which one is used for
Solanna Vision discovery. Check the hints under the Network
Interface field and, if necessary, enter a value like eth2.
5.d. Click the OK button to save the settings.
5.e. Restart the Romexis server to activate the changes.
6. Pair the dental unit in the Romexis client.
6.a. Start the Romexis.
6.b. Click the Admin button in the Romexis module tree.

6.c. Select Local Settings > Dental Unit and set the pairing.

• In the Paired unit, enable the Connect to Dental Unit at Startup

option.
• Select the dental unit from the Select Dental Unit drop-down
menu.

NOTE
In case of Planmeca Sovereign Classic dental unit, enable also
the Enable remote control setting under the Remote TouchPad
and Keyboard control.

6.d. To save the changes, click the Save button.

6.e. To activate the changes, restart the Romexis client.

Results
The Solanna Vision video stream should be available in the Romexis 2D
module window.
For more information, see the device's user's manual.

188 Romexis Technical manual

 10 Romexis server and unit connection configuration

What to do next
You can add the Solanna Vision to the Clinic Management module
(optional), for more instructions, see section "Clinic Management
configuration" on page 190.

Technical manual Romexis 189

11 Clinic Management configuration

11 Clinic Management configuration

The following section describes how to set up Romexis Clinic Management
module.
You can test your configuration with Romexis Clinic Management - Virtual
Clinic tool. For more information, see section "Starting Romexis Virtual
Clinic" on page 200.

11.1 Before you start Clinic Management configuration

Before setting up and configuring the Clinic Management configuration,
carefully plan the following issues:
• Plan for naming the devices connected to the Clinic Management, i.e.
the names given for the dental units, the client workstations connected to
the dental units, the X-ray devices, etc.
• Plan for clinic layout including floor plan picture files, naming rooms/
working areas, etc.
• When planning, keep in mind possible new devices added later to the
Clinic Management module.
• Get acquainted with Clinic Management and its functions, see Romexis
User’s manual.

NOTE
The Clinic Management module is optional, the license used with
the Romexis installation must include the license for using the Clinic
Management module.

NOTE
When restarting the Romexis service or units connected to it, it takes a while
before the units are again visible in the Clinic Management views.

11.2 Configuring Clinic Management general settings

Steps
1. Start Romexis Configuration tool.
For instructions, see section "Starting Romexis Configuration tool" on
page 107.
2. From the directory tree on the left side, under the Clinic Management,
select PlanLink & Diagnostics.
Related parameters appears to the right panel.
3. Check and/or set the values for the following parameters, listed in the
table below.

Parameter/setting Description
Clinic overview and Log Refresh-rate

190 Romexis Technical manual

 11 Clinic Management configuration

Parameter/setting Description
Show large icons By enabling this setting, the unit icons in
the clinic layout are in bigger format. By
default this is disabled.
E.g. if there are only few units and the
floor plan figures are spacious, this can be
enabled.
Note, you can change this setting later
when adding units to the clinic layout,
if it seems that bigger icons are more
appropriate.
Dental Unit User Settings
Send Service Modes By enabling this setting, it is possible to
modify dental unit service mode settings
remotely from Romexis server.
In normal operation this should be left
disabled but can be useful at dental unit
installations if numerous new dental units
must be configured identically.

NOTE
If enabled temporarily for installing
purposes, remember to disable this setting
after completing the installations.
Email notification server (SMTP)
Romexis server can be configured to send alert e-mails when specific
diagnostic events take place in dental units. Romexis sends the e-mails
to the SMTP server configured with these settings. The device alerts
triggering the e-mails are configured in the Romexis Admin module.
Note that Romexis server software does not include the SMTP server
but the service must externally be available.
If e-mail notifications is not taken into use, leave these parameters as
defaults.
Server Host Name Defines the SMTP server host.
Server Port Defines the SMTP server port.
Email notification settings
Notification period (mins) Defines the delay in minutes after which
an error is considered to be important
enough to be reported in an e-mail. If an
error is negated by itself or fixed by a user
within this time limit, then no error will be
reported. The error will still be shown in
the dental unit event log.
Don't e-mail for same error Defines the time limit in minutes during
in (mins) which a persistent error will not be
reported again.
For the rest of the parameters, leave the default values.

Technical manual Romexis 191

11 Clinic Management configuration

4. From the directory tree on the left side, under the Image & Data
Management, click Data Folders.
The Romexis Data Folders settings sheet allows re-configuration of
the Romexis image, cache and ergodata (dental unit diagnostic data)
storage paths.
For more information on data folders, see section "Data folders" on page
145.
For more information on the needed disk space, see section "System
requirements" on page 4.
To change the data folder location, follow the sub-steps below:
4.a. Click Set Path.
4.b. Browse or enter the new storage path.
4.c. Click Yes to confirm to create new storage folders.
If the given path is valid, the romexis_images, romexis_cache
andromexis_ergodata folders are automatically created under
it.
After Romexis server restart, the all-new Romexis image, cache
and ergodata are stored to the new locations.
5. Click OK to save the changes and exit Romexis Configuration tool.
6. Restart Romexis service to activate changes.
For instructions, see section "Restarting Romexis service" on page 108.

11.3 Creating floor plans

Before you begin

Carry out these steps in the Romexis server.

About this task

Follow the steps below to create a floor plan.

Steps
1. Create a PNG format graphic file from the floor plan of the Clinic
Management area.
• For multi-floor, multi-clinic or other complex layouts you can create
multiple floor plans. Up to nine custom floor plans can be specified
for the clinic view.
• Each floor plan graphic must be in PNG format, with a recommended
maximum size of 1100 x 800 pixels.
• Name the files floorplan1.png, floorplan2.png, up to
floorplan9.png, depending on how many floors/areas are
needed.

192 Romexis Technical manual

 11 Clinic Management configuration

As an example, the figure below is the default floor plan file included in
the Romexis installation package.

2. Create another smaller image from each floor plan image to be shown in
the Clinic floor plan list as a thumbnail image.
• Each floor plan thumbnail graphic must be in PNG format and
approx. 300 x 180 pixels in size.
• Name the files floorplanthumbnail1.png,
floorplanthumbnail2.png, up to
floorplanthumbnail9.png, depending on for how many floors/
areas are defined.
An example of a floor plan thumbnail graphic is given below.

3. Save the floor plan files and thumbnail graphic files to the Romexis
installation path, in the folder /Romexis/sconfig, replacing any
previous floorplan*.png files.
4. To name or rename the floor plans, follow the sub-steps below.
4.a. Start Romexis Configuration tool.
For instructions, see section "Starting Romexis Configuration tool"
on page 107.
4.b. From the directory tree on the left side, select Clinic Management
> Floor names.
4.c. Select the floorplanX from the list and click the Update button and
enter the name for the floor plan and click the OK button.
4.d. After naming the floor plans, click OK to save the changes.
5. Exit Romexis Configuration tool.
6. Restart Romexis service to activate changes.
For instructions, see section "Restarting Romexis service" on page 108.

Technical manual Romexis 193

11 Clinic Management configuration

11.4 Adding units to Clinic Management layout

Before you begin

Carry out these steps in the Romexis server.

NOTE
All units to be added to the Clinic Management, must be connected,
configured and switched on, as described in section "Configuring Romexis
unit connections" on page 158.

About this task

Follow the steps below to add units to Clinic Management layout.

Steps
1. Start Romexis.
2. Click Clinic button.

3. Activate Floorplan view by clicking the layout.

4. Click Configure Layout button.

A list of operatories, chairside workstations, dental units, X-ray units,

milling units etc. are shown in the panel at the bottom of the Floorplan
view.
The unit becomes available in the list once it has connected to the
Romexis server. If a unit is not on the list, verify that the unit connection
has been configured and that the unit has been connected to the
Romexis server.
5. Select an operatory (you can choose between vertical or horizontal
operatories) and drag and drop it into the layout.
6. Enter the name of the operatory (the operatories can be named e.g. to
match the names of the actual operatories in the clinic) and click OK
button.
The operatory appears in the layout.
7. Add a corresponding unit pair into the layout by drag drop it to the layout.
8. In the same way add all other units to the layout.
9. Close Romexis.

Results
On the next Romexis startup all added units are visible in the clinic layout, in
the Romexis server as well as in any Romexis client installation.

194 Romexis Technical manual

 11 Clinic Management configuration

11.5 Configuring service contact details sending from Romexis to dental

units

Before you begin

NOTE
This is an optional feature, the license used with the Romexis, must include
the license for using the Clinic Management module.

About this task

Follow the steps below to enable the sending service contact details from
Romexis to dental units.

Steps
1. Configure the Romexis server settings (if not yet done), see section
"Configuring Romexis server settings" on page 156.
2. Configure the dental unit network connection and settings and enable
the Romexis connection with the dental unit (if not yet done), see section
"Configuring Romexis unit connections" on page 158.
3. Start the dental unit’s Romexis client workstation.
4. Start the Romexis.
5. Create a device group containing the dental units to which the service
contact details are sent.
For more information, see section "Creating device groups" on page 195.
6. Update (or create if not yet existing) a Romexis user whose contact
information is to be sent to the dental units.
• In the Clinic tab, enable the Share user contact details to a device
group option and select the created device group from the drop down
menu.
• Among the mandatory fields, fill in the First Name, Last Name, Work
Phone and Work Email fields for the user (those are the information
sent and visible in the dental unit).
• For more information how to add/update user data, see Romexis
technical manual.
7. To activate changes, restart the Romexis client and the dental unit.

11.6 Creating device groups

Steps
1. Start the Romexis.
2. Click the Clinic button and

3. Activate the Floorplan view by clicking the layout.

4. Click the Configure Groups button.

5. Click the New Group button, enter name for the group and click the OK
button.

Technical manual Romexis 195

11 Clinic Management configuration

6. Select the units to be added to the group from the Units list and click the
Add to selected group button.
7. When all units are selected, click OK button twice.

11.7 Updating unit Guides content

Before you begin

Carry out these steps in the Romexis server.

About this task

Always after the dental unit software upgrade, the dental unit quick guides,
maintenance and infection control instructions and the dental unit control
panel (GUI) should be updated in the Romexis server for the Clinic
Management.
Follow the steps below to update the dental unit data.

Steps
1. Insert the USB flash drive including the Planmeca dental unit software
update to the Romexis server computer USB port.
2. Open the USB flash drive folder.
3. Run the romexisGUI_update.bat script (located in the root folder of
the USB flash drive) as an admin user.
Wait until the script has copied all files to the Clinic Management
module.
4. Start the Romexis.
5. Click the Clinic button and

6. Check from the Guides and Monitoring views that the instructions and
Touch panels have been successfully updated.

11.8 Maintenance scheduling

Before you begin

NOTE
Romexis Clinic Management’s maintenance scheduling feature is available
for use with the Planmeca Sovereign Classic 1.7.0.234.R and 1.7.1.6.R.

Before you can use the feature, you must create a device group for the
dental units that require regular scheduled upkeep. For more information on
the device group setup, see section "Creating device groups" on page 195.

About this task

The maintenance scheduling feature allows you to plan regular upkeep and
cleaning operations for the devices in your clinic.

Steps
1. Start Romexis.

196 Romexis Technical manual

 11 Clinic Management configuration

2. Click Clinic.

3. Activate Floorplan view by clicking the layout.

4. Click Maintenance Scheduling button.

5. Select the group.

6. Set the maintenance schedule.
You can add new scheduled upkeep operations, with the time of day and
duration of each operation.
You can select from the following operations for the device group:
• Short instrument flushing
• Long instrument flushing
• Suction cleaning
• Waterline cleaning
You can also set the device into low power (standby) mode for a set
period. For more information, see the Romexis user’s manual.

NOTE
The schedule controls and assists in the automation of different
procedures and is intended for use by dental clinic technicians. For
more detailed technical service and parts replacement operations, see
the dental unit's technical manual.

11.9 Maintenance demands

Before you begin

NOTE
Romexis Clinic Management’s maintenance demands feature is available for
use with the Planmeca Sovereign Classic 1.8.0.746.R.

Before you can use the feature, you must create a device group for the
dental units that require regular scheduled upkeep. For more information on
the device group setup, see section "Creating device groups" on page 195.

About this task

The maintenance Demands feature enables you to set selected groups
of Planmeca Sovereign Classic units with a designated number of suction
cleaning and instrument flushing procedures per day.
If the set demands are not met, Romexis displays a notification and/or
prohibits the further use of water and suction.
If selected, the notifications are visible in the Romexis Clinic Management
floorplan view, as well as the Planmeca Sovereign Classic user interface.

Steps
1. Start Romexis.
2. Click Clinic.

Technical manual Romexis 197

11 Clinic Management configuration

3. Activate Floorplan view by clicking the layout.

4. Click Maintenance Scheduling.

5. Select the group.

6. Set the maintenance demand options.

11.10 Configuring Sovereign Classic user settings storing

About this task

Follow the steps below to enable user settings storage to Romexis with
Planmeca Sovereign Classic dental units.

Steps
1. Configure Romexis server settings (if not yet done), see section
"Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable the
Romexis connection with the dental unit (if not yet done), see section
"Configuring Sovereign Classic connection" on page 159.
3. To activate changes, restart the Romexis client and the dental unit.

Results
The user setting are stored to the C:\Program
Files\Planmeca\Romexis\server\resources\settings\user
folder.

NOTE
The user in the dental unit must be connected to the Romexis user, for more
information, see dental unit’s technical manual.

11.11 Configuring automatic login to Sovereign Classic with Romexis client

login

About this task

Follow the steps below to enable the automatic login to the Planmeca
Sovereign Classic when the user is logged in to the Romexis client.

Steps
1. Configure Romexis server settings (if not yet done), see section
"Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable the
Romexis connection with the dental unit (if not yet done), see section
"Configuring Sovereign Classic connection" on page 159.
3. Start the dental unit’s Romexis client workstation.
4. Start Romexis.
5. Click Admin button and select Local Settings > Dental Unit.

198 Romexis Technical manual

 11 Clinic Management configuration

6. Enable Connect to Dental Unit at Startup setting under the Paired unit
title and select the dental unit in question from drop-down menu.

7. To activate changes, restart the Romexis client and the dental unit.

11.12 Configuring Compact i dental unit manual user settings storing and
transfer

Before you begin

To use this feature, Romexis license must include the license for using the
Clinic Management module.

About this task

Carry out these steps to enable the manual user setting storing and transfer
to Romexis with Planmeca Compact i dental units.

Steps
1. Configure Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable the
Romexis connection with the dental unit (if not yet done).
For instructions, see the appropriate section:
• "Configuring Compact i v2 (touch panel) connection" on page 168
• "Configuring Compact i v2 (keyboard) connection" on page 171
3. To activate changes, restart Romexis client and the dental unit.

11.13 Configuring Compact i dental unit automatic user settings storing and
transfer

Before you begin

To use this feature, the Romexis license must include the license for using
the Clinic Management module.

About this task

Follow the steps below to enable the automatic user setting storing and
transfer to Romexis with Planmeca Compact i dental units.
The user settings are transferred to the unit when the user logs in to
Romexis.

Steps
1. Configure Romexis server settings (if not yet done), see section
"Configuring Romexis server settings" on page 156.
2. Configure dental unit network connection and settings and enable the
Romexis connection with the dental unit (if not yet done).
For instructions, see the appropriate section:
• "Configuring Compact i v2 (touch panel) connection" on page 168

Technical manual Romexis 199

11 Clinic Management configuration

• "Configuring Compact i v2 (keyboard) connection" on page 171

3. Start the dental unit’s Romexis client workstation.
4. Start Romexis.
5. Click Admin button and select Local Settings > Dental Unit.
6. Enable Connect to Dental Unit at Startup setting under the Paired unit
title and select the dental unit in question from drop-down menu.

7. To activate changes, restart the Romexis client and the dental unit.

11.14 Configuring of sending device alert e-mails

Before you begin

To use this feature, Romexis license must include the license for using the
Clinic Management module.

About this task

Follow the steps below to enable the sending of device alert e-mails.

Steps
1. Configure Romexis server settings (if not yet done).
See section "Configuring Romexis server settings" on page 156.
2. Configure the dental unit network connection and settings and enable
the Romexis connection with the dental unit (if not yet done).
See section "Configuring Romexis unit connections" on page 158.
3. Update the Romexis users’ data for those users to which the device
alerts are to sent.
In the Clinic tab, enable the Listens device alerts / Add user to list option,
see more instructions in section "Adding/updating user" on page 79.
4. Configure the device alerts for the user, see section "Configuring device
alerts" on page 105.
5. To activate changes, restart Romexis client and the dental unit.

11.15 Starting Romexis Virtual Clinic

About this task

Romexis Virtual Clinic allows you to perform demos and test simulations of
your clinic setup without requiring the physical devices to be connected to
the system, or for the devices to run.

Steps
1. Start Romexis.

200 Romexis Technical manual

 11 Clinic Management configuration

2. Select File > Virtual clinic.

For more information on the Virtual Clinic feature, see the following
manuals:
• Romexis user's manual
• Romexis Clinic Management, Virtual Clinic quick guide

11.16 Viewing logs

Steps
1. Start Romexis.
2. Click Clinic button.

3. Activate Floorplan view by clicking the layout.

Technical manual Romexis 201

11 Clinic Management configuration

4. Select Logs tab.

5. Filtering, sorting and handling the log data.

• You can filter the log events with the following criteria:
• Device
• Event Type
• From/Until Date
• You can copy all or selected log items to clipboard by clicking Copy
to Clipboard button.
• Depending on the event type, you can show graphical or detailed
view of the selected event by clicking Show Event in Graph button or
by double-clicking the event.
• You can sort the events by columns by clicking the column title field.
For more information on the logging feature, see the Romexis user’s
manual.

11.17 Creating service entry record

Steps
1. Start Romexis.
2. Click Clinic button.

3. Activate Floorplan view by clicking the layout.

4. Select Summary tab.
5. Select Service History tab.
The Service History tab shows a list of recent maintenance procedures
and a form for entering new maintenance records or for reviewing the
previous records.

202 Romexis Technical manual

 11 Clinic Management configuration

6. To record a new entry, click New entry button.

7. The following information is recorded from a service visit.
• Entry ID (for quick reference)
• Date
• Entry reason (the reason for visit)
• Service visit
A scheduled visit such as yearly maintenance.
• Unscheduled service visit
A non-scheduled visit that may have caused unscheduled
downtime. Possibly caused by an unexpected lamp failure or
similar.
• User guidance visit
A visit is required to instruct the user in proper use or
maintenance of the unit.
• Remote service
Recorded when a technical problem can be solved without
visiting the clinic, for example by adjusting service modes
remotely.
• Remote user guidance
Used for example when the user can be remotely instructed
on the phone on the proper use of the unit by referring to the
recorded history information.
• Yearly maintenance
Shows the confirmed yearly maintenance operations and other
recorded service visits.
• User name
The name of the person who provided the service (automatically
records the currently logged in user)
• Comments
To provide more details and to assist in later maintenance visits.
• Error codes
Error events that the service entry negates can be selected from the
list of all errors.
Click Add and Remove buttons to modify the list. Once negated the
errors no longer show in Diagnostic Log.

• Elapsed time
For recording the time consumed on the service operation.
• Spare parts

Technical manual Romexis 203

11 Clinic Management configuration

A list of components used. Part number, part name and quantity

can be recorded as listed in Planmeca’s spare part manuals, for
example.
• Comments
For explaining, for example, the steps taken during the maintenance.
• Reset Values
Set a service point to reset the unit’s summary counter values. Use
these options after servicing a part or the unit. The options can be
changed at a later point in case an erroneous recording was made.
These settings only affect the display of summary values and they
do not affect the data stored into the database, which remains fully
available for reporting.
• Unit
Resets the unit counter when, for example, annual maintenance is
done.
• Operating light
Resets the operating light counter when the lamp is changed.
To view the existing entries select them from Service History list, which
automatically updates the recorded values onto the form.
To edit an existing record, click Edit.
8. Click Save to add and store the record.

204 Romexis Technical manual

 Appendix A: Romexis language abbreviations

Appendix A: Romexis language abbreviations

Abbreviation Language
cn Simplified Chinese
cs Czech
da Danish
de German
en English
es Spanish
et Estonian
fi Finnish
fr French
hu Hungarian
jp Japanese
ko Korean
nl Dutch
no Norwegian
pl Polish
pt Portuguese
ru Russian
sk Slovak
sv Swedish
th Thai
tr Turkish
vi Vietnamese
zh Traditional Chinese

Technical manual Romexis 205

Appendix B: Configuring Romexis user's manual

Appendix B: Configuring Romexis user's manual

The Romexis user’s manual can be configured to be used with Romexis.

NOTE
This option is available only with Romexis installed on Windows operating
system.

The Romexis installer detects Adobe Acrobat and Adobe Reader

installations and configures Romexis to open the Romexis user’s manual
(PDF format) with the relevant software.
1. To configure the PDF reader manually after the installation
of the Romexis, open the file /Planmeca/Romexis/sconfig/
manual_config.xml file for editing.
2. Make sure the key application default-path contains the path to
the executable file of Adobe Acrobat or Adobe Reader.
3. Check the following line for the language in use:
<locale language="en" doc-file="Romexis_um.pdf"/>
Make sure that the line contains the name of the user’s manual to be
used with the relevant language, and that is found in the /manuals
folder of the Romexis folder structure.

206 Romexis Technical manual

 Appendix C: X-ray device Ethernet configuration in terminal server environment

Appendix C: X-ray device Ethernet configuration in

terminal server environment
To configure a separate device for each Terminal Server client workstation
follow the instructions below.
X-ray device ethernet configurations are made in the ethernet configuration
files, located in the C:\Program Files\Planmeca\Didapi folder. The
file names are:
• ProSensorEthernetConfig.txt
• PromaxEthernetConfig.txt
• ProOneEthernetConfig.txt

NOTE
In older installations DIDAPI files are located in the Dimaxis folder:
C:\ProgramFiles\Planmeca\Dimaxis\Program

Edit the Ethernet configuration file of the respective X-ray device in order to
map X-ray devices to Terminal Server client workstations.
As a terminal server client workstation name one can use either
computername or clientname of the client workstation.
Computername and/or clientname can be seen in Windows command line:
Start > Run and type in cmd. In the command line, type in "set".
X-ray devices are mapped with their IP addresses.
For example, a Terminal Server environment with three ProSensors
(ip-addesses: 192.168.0.1, 192.168.0.2, 192.168.0.3) and three Terminal
Server clients (clientnames: xpprosensor1, xpprosensor2, xpprosensor3)
would be mapped to each other the following way in the
ProSensorEthernetConfig.txt file.
xpprosensor1=192.168.0.1 xpprosensor2=192.168.0.2
xpprosensor3=192.168.0.3

NOTE
Each terminal server client must have access to the DIDAPI folder and a
working network connection to the X-ray devices.

Technical manual Romexis 207

Appendix D: Romexis client startup parameters

Appendix D: Romexis client startup parameters

Romexis client is started with specific startup parameters. On Microsoft
Windows operating system, most of the parameters are defined in the
Romexis Configuration tool. See section "Client parameters" on page 146
for information on configuring Romexis client parameters using the Romexis
Configuration tool.
For the parameters not available in the Romexis Configuration
tool, you need to edit the in the Romexis.bat file located
in Romexis client installation folder, by default C:\Program
Files\Planmeca\Romexis\client folder.
You can access the file by right clicking on the Romexis desktop icon and
select Edit. Note that modifying the Romexis.bat file requires administrator
rights.
In the following table, the parameters are listed and described.
For information on how to edit startup parameters on or macOS operating
system, follow the instruction in section "Configuring Romexis client" on
page 55.

NOTE
The installation of the Romexis update may overwrite your own changes
to the Romexis.bat file. It is recommended to take a backup of the
Romexis.bat file containing your edits.

Parameter Description
-Xmx Amount of memory allocated for Java
process, e.g.:
–Xmx=4000m
See Romexis technical bulletin for
recommended values.
xsize Specify a fixed size for Romexis window
when opened, e.g.:
ysixe
xsize=1920 ysize=1080
host Romexis server IP address, e.g:
host=192.168.10.100
port Port used for Java RMI connection to
Romexis server, e.g.: port=1099
romexis_config_port Tells the client which port number to use to
fetch settings from the server.
language Language for Romexis interface, e.g.:
language=en
monitor If multiple monitors used, you can define
to which monitor Romexis will first open at,
e.g.:
monitor=2
uid Username defined for login.
pwd Password defined for login.

208 Romexis Technical manual

 Appendix D: Romexis client startup parameters

Parameter Description
-nofades Turns off some fade effects and animations
in user interface to conserve bandwidth
and CPU for example with Remote Desktop
Connection and Citrix.
This parameter is not editable in Romexis
Configuration tool.
-no3d Disables 3D rendering. Can be used to start
software when usable GPU is not available.
This parameter is not editable in Romexis
Configuration tool.
-windowed Does not open Romexis Client in full screen
mode on macOS by default at startup.
This parameter is not editable in Romexis
Configuration tool.
-vison Enables image capturing with Planmeca
Viso X-ray unit.
This can also be enabled in Admin module
> Local Settings with 'Viso Image Capture
(2D/3D) Enabled' option.
-version Show Romexis version on command line.
-nosurface Disable surface rendering (ProFace tab).
This parameter is not editable in Romexis
Configuration tool.
/PMBRIDGE Only used with PmBridge. Starts as
minimized and listens to PmBridge calls.
Added as last parameter.
This parameter is not editable in Romexis
Configuration tool.
/PMBRIDGE_MAXIMIZED Only used with PmBridge. Starts normally
(not minimised) and listens to PmBridge
calls. Added as last parameter.
This parameter is not editable in Romexis
Configuration tool.

Technical manual Romexis 209

Appendix E: Specification of USB connected RFID readers

Appendix E: Specification of USB connected RFID

readers
Working principle
USB RFID Reader is used with Romexis. The USB RFID Reader acts like a
HID device, displaying the NFC card's ID number in an active document field
when the RFID card is read.
The following picture shows example output from a reader.

Reader specifications
• USB keyboard emulator device
• Works on Windows or macOS operating systems in conjunction with
Romexis installation.
• Reader must support standard ISO/IEC 14443 and all Mifare cards The
PlanID card type is Mifare Classic EV1 4k, 7 byte UID.
• Displays ID number LSB first in hexadecimal format (no spaces or
special control characters between ID characters); reader must append
CR (carriage return).

210 Romexis Technical manual

1.015.1955

Planmeca Oy | Asentajankatu 6 | 00880 Helsinki | Finland

tel. +358 20 7795 500 | fax +358 20 7795 555 | [email protected] | www.planmeca.com