Omda uses the client server (C/S) model, with FileMaker Pro as client application and FileMaker Server as application and data server. This model gives the user the best user experience, as a full featured client application is used. FileMaker Pro can be used on both Windows and Macintosh computers.

Communication between the client application and the server uses port 5003 and 443. The communication can be encrypted with a certificate installed at the server. FileMaker Server is to be installed on a Windows server. A virtual server can be used.

FileMaker Server handles the distribution of the Omda application to FileMaker Pro clients. An upgrade of Omda is installed in the FileMaker Server application. No upgrade is needed of the FileMaker Pro clients, unless stated in the release notes.

To handle tasks that are not managed by FileMaker Server, a Java based software deployed in Apache Tomcat is an essential part of the solution. The software is named ivfServices and is installed in the same server as FileMaker Server.  A main task for ivfServices is to manage audit logging. The log data is stored in an SQL database, Frontbase.

FileMaker Pro clients call ivfServices for certain tasks and is also visible in the user interface in some areas. FileMaker Pro clients and ivfServices use port 8080 for communication. Internally in the server, ivfServices accesses databases in FileMaker Server via JDBC.

Integration to other systems is handled by multiple methods, where Mirth Connect is the main component. Mirth Connect is a Java based software with its strength in healthcare integration. Development of integration capabilities is a continuous task. With use of Mirth Connect, all types of integrations can be developed.

The recommended standard configuration of physical disks for the server are:

• C: Operating system and software. Installation of FileMaker Server, Apache Tomcat/ivfServices and Mirth Connect applications.
• D: Data. Database part of FileMaker Server and other live databases and files.
• E: Backup. Primary backup of databases and other files in at least three generations.

Secondary backup of this disk, performed by another part (IT or clinic staff), is mandatory.

The size of the different disks depends of the types of data stored, the number of backup generations to be saved, and the type and number of integration used. If pictures, scanned documents or other digital data is used, this can be stored outside the database, in encrypted format. Disk D: or other storage can be used for this type of data and the backup strategy for media data can differ from main data backup strategy.

See more regarding backup procedures here

Set up and installation of software at the server is done by Omda Support, via VPN connection or other method, to give Omda support staff access to server. The same connection is used to install upgrades of Omda and other software components.

Secondary backup to tape or other media, stored in a physical separate area from the server, is to be set up and maintained by the IT department. Surveillance of the server regarding disk usage, process load and patches of operating system, is handled by the IT department. Installation and upgrades of FileMaker Pro is done by the IT department.