Revision Date Changes
11 April 2017 New revision for mRay 5.0.
12 July 2017 Updated for mRay 5.2.
13 March 2018 Updated for mRay 5.3.
14 June 2018 Updated for mRay 5.4.

Manufacturer and contact

mbits imaging GmbH

Bergheimer Straße 147

D-69115 Heidelberg

E-Mail: support@mbits.info

Telefon: (+49) 6221-6734 883

Internet: www.mbits.info

mRay 5.4

Radiological image viewer for mobile devices with image processing functions

Release-Date: June 2018

© 2018 mbits imaging GmbH

0123

Intended purpose

mRay allows medical professionals to view and evaluate radiological images. Main users are physicians. The patient group, for which mRay can be used, includes all patients from whom radiological image data has been created for the purpose of diagnosis or treatment.

mRay can be operated in hospitals, medical practices, on the go or at home. The software is dedicated for mobile devicesfor fast and immediate access to radiologic images for informational purposes. Whenusing mRay for diagnostic purposes, national regulations within the European Union must be considered and an appropriate display must be used.

mRay allows the display of images and data types that are defined by the Digital Imaging and Communications in Medicine (DICOM) standard (e.g. computed tomography (CT), magnetic resonance imaging (MRI), positron emission tomography (PET), fluoroscopy (XA), digitalx-ray (CR), ultrasound (US)). The software offers common radiological softwaretools (e.g. windowing, measurements, thick slices and annotations).

Introduction

In order to manage and configure the mRay server application, there are three software tools:

  • The mRay server application to start or restart the server, install a service, to set the port of the server through which clients communicate with the server and to install the license file.
  • The mRay configuration application to configure the server and to manage data access, users and groups.
  • The mRay gateway application allows to setup external access points for an mRay server without opening or forwarding ports in the internal network.

The following sections describe the individual functions of these applications.

Installation, update and uninstall

Initial installation

This paragraph applies only to the Windows-installation.

Run the downloaded setup routine (named, for example, 'mRayServer-5.3-win64.exe').

First Administrator rights are requested. Please note that the installation routine only needs those rights in order to install in the default folder 'C:\Program Files\mRay Server'. Please accept the dialog, no other modifications will be made to the system.

In the rest of the process, please follow the instructions of the installer program. During installation, the Visual Studio runtimes need to be installed, i.e. also on a newly installed server system all you have to install is contained in our installer package.

At the end of the installation the server application is automatically started and installed as a service.

Update

1. Update of mRay 4.1 and older to mRay 5.3

Notice

With version 4.1 the product activation and licensing process has been changed. That is, if you are still running mRay 4.0, your current running license needs to be generated and activated again since the old license model is incompatible with the current one. Concerning this, please contact your contractor.

Information

New features require an update of your license file in order to be activated. Please consult the support of the installation.

For the update of mRay 4.1 and older to mRay 5.3 a database migration must be done. This is done automatically when you start the new version, as long as the old application data are still available. Please proceed as follows:

  1. Close the running server application, that you want to update (4.1 or older), and possibly the Configuration application as well.
  2. Backup the application data as described in the FAQ, bullet point 2.
  3. Install the new version 'mRay 5.3'.
  4. Start 'mRay 5.3'.
  5. Ensure that all configuration data has been restored (port, pools, users ...). If not, please contact the mbits support.
  6. Make sure that mRay 5.3 starts automatically at system startup. You can verify that by connecting with the configuration application to the server.

2. Reinstallation / Future updates

In case of an update or a new installation, you can simply run the installer package (again). This will first try to uninstall the existing version (Figure 1). Afterwards, a normal installation is performed as described above. Note, however, that the uninstall process can delete existing data when requested. Please read the following subsection carefully.

Figure 1

1. Update of mRay 5.0 to mRay 5.3

If you already have activated the LDAP user synchronisation with mRay 5.0 make sure you are aware of the following: The binding to an external user directory (LDAP) e.g. Active Directory now supports the login to mRay with the user ID and password from the directory. If the user is logging in for the first time a PIN will be required. The PIN will be sent via Email. Therefore the mRay server needs to be configured by adding an email account for sending the PINs to the users (see manual). No additional changes to your LDAP settings in mRay server are needed. You can specify in the server configuration how long a PIN will be valid. After the specified time a PIN can no longer be used. A new login request triggers a new email with a new PIN.

Uninstall

The uninstaller removes the currently installed version of the software. You may be asked if you want to delete existing data (Figure 2) if you are uninstalling a version older than 5.2. By default, 'No' is selected. Please be nevertheless careful that you do not accidentally delete the existing data in this step unless you explicitly want to do so.

Figure 2

The mRay server application

The application mRay Server starts or stops the server process. In addition, a port can be set to under which the server is available. The server can be started as an ordinary application or automatically via a Windows service. We recommend to start the server via a service. This ensures that your server is restarted automatically in case of an unexpected system restart. Addtionally, no logon is required to restart the server. In a separate chapter 'Server Execution Models' you can learn more about the service installation process.The application can be seen in Figure 3:

Figure 3

  1. Checkbox for starting or stopping the server process.
  2. Configures the server communication port.
  3. Starts the mRay Configuration application.
  4. Opens the Admin Manual.
  5. Shows the server version, the intended use and license terms.
  6. You can switch between two different server execution models (application and service) over this button (more about that in chapter 'Server Execution Models').

(Re-)installation of a license

To use mRay Server without any restrictions you need to obtain a license and activate it via the mRay server configuration. You can get a license by contacting your contractor. The following steps are required to do an activation:

Figure 4a

Figure 4b

  • Run the newly installed mRay server application.
  • A popup appears (see figure 4a) which prompts you to install a license. It also shows you additional information such as:
    • License status: Displays how long your license is valid.
    • Registration key: This key needs to be submitted to your contractor to obtain an activation key.
  • Now it is time to get in contact with your contractor and to send him your registration key. After he has received your key, he will send you back an activation key.
  • Now go back to the mRay Server application window and click the' Configuration' button.
  • The mRay Server configuration opens. Now log on to the server with the "admin" account via the configuration. Please note the server text field, which specifies the target address of the server to which you want to connect and install the license. In the case of a remote license installation, this field may need to be edited.
  • After successful login please click on the "About this mRay server" button, which opens a dialog with the title bar "About mRay". This allows you to install a license (see figure 4b).
  • With the reception of your activation key you are ready to activate the server by installing it via the 'Select license file' button. When you click on the button a file explorer opens which prompts you to input the path to your license file.
  • If the license file is valid you can now proceed to start and configure your server. If not, the mRay server application automatically closes and you will be prompted again to install a license after you restarted the mRay server application.

The same procedure is valid for a reactivation of your license which is needed in case of a license prolongation or a booking of additional modules. Since you are not prompted automatically again to activate your server, you need to open the reactivation dialog manually. You can access it via the "About" dialog of the mRay Server configuration. To do this, click on the "About" button after you have logged in as "admin" via the configuration on the server. Please click on the button labeled 'Change license'. Now, the activation dialog explained previously opens again. From there you can proceed with the steps described in the last section.

Server execution models

There are two different execution models of the server. The first one is to execute the server as an ordinary application. To run the server in this mode two requirements need to be met: You need to keep the mRay server application window open and the checkbox 'start on port' must be checked. A disadvantage of this execution model is that the server will get and be kept deactivated if the mRay server application is closed accidentally or the system restarts unexpectedly unless the server is restarted again manually.

The second execution model is to install the server as a service. With this model you do not need to keep the mRay server application window open and the server restarts automatically if the system restarts. Furthermore a login at the logon screen is not required.

To switch between both modes you can to click on the button labeled 'Install as service' or 'Uninstall service' within the mRay server application. 'Install as service' installs the service as a service application (second mode) whereas 'Uninstall service' runs the server as an ordinary application (first mode). The button labeling is alternating.

Notice

A service is not allowed to access a network drive unless the affected host system (computer name) is listed in the ACL (access control list) of the network drive. An alternative is to run the service under a different account as opposed to the LocalSystem account which is authorized to access the network drive. Please ensure that the account has full access to the application data of mRay (C:\ProgramData\MBITS\mRayServer) and to all of the registered folders in the configuration.

Gateway installation

The mRay gateway offers a connection forwarding for mRay clients to a mRay server where the clients may have no direct access to the mRay server itself e.g. if you are running your mRay server in a closed network.

In order to install the gateway application, run the 'mRayGateway-5.3-win64.exe' and follow the install programs instructions.Wait until the installation process has completed and run the gateway application.

Figure 5

The gateway launcher offers a small user interface to configure the application.

  1. Run gateway: Toggle to run or stop the gateway process.
  2. Client port: The port used by mRay clients to connect to the gateway.
  3. Server port: The port used by the mRay server to connect to the gateway.
  4. Install as service: Installs the mRay gateway as a Windows service.

To connect your mRay server to the gateway installation, enter the address of the gateway with the port of the gateway in the mRay configuration like it is shown in General Settings Figure 12.

The mRay configuration application

The mRay Configuration application is used to manage the server system (Figure 6). You can change general settings, pool, users, groups and monitor the server process. Please log in with an administrator user in order to make adjustments.

Figure 6

Connection window

The connection window (Figure 7) is used to connect to the server:

Figure 7

  1. The network address including the port of the server you want to connect to
  2. Enter your administrator login name (default name is 'admin' ) here.
  3. Specify the administrator password that you received by your mbits contact. The password should be changed after the first login.
  4. If everything is correct, you can connect to the server using the Connect button.

Configuration window

The Home screen (Figure 8) contains the general configuration tabs, which are explained in the following sections:

Figure 8

  1. Status: Displays the current status of the server and other internal information.
  2. Settings: Make general, globally applicable settings to the server.
  3. E-mail SMTP: Here you can set up an outgoing e-mail server (SMTP) to send important messages via e-mail from mRay Server (e. g. PIN messages, expiring licenses, etc.).
  4. Pools: A Pool corresponds to a DICOM node on the network. Pools contain user access rights for different data sources.
  5. Users: Create, manage and delete users.
  6. Groups: Create user access and chat groups.
  7. Log: Displays the server log.
  8. Advanced: You can adjust advanced settings here.

Status tab

The Status tab (Figure 9) shows license information, free space on the server and other internal information:

Abbildung 9

  1. Activating the checkbox displays additional internal information of the server process.
  2. Activating the checkbox pauses the information pane to be updated continuously.
  3. Shows the users PIN's if LDAP is active.
  4. Opens the About dialog for the connected server that displays information about the manufacturer, used licenses, certification, etc. for the product and allows you to install updates or a license.

General settings

This tab can be used to change various global settings (Figure 10).

Figure 10

  1. If checked the server can also be configured from a remote computer. Note: If your server is reachable from the internet, choosing this option will enable server configuration from any computer. Pay attention to provide a strong administrator password (min. 8 characters with uppercase and lowercase characters and numbers).
  2. This checkbox activates the automatic deletion of the oldest records if the free memory falls under the provided limit on the installation disk. This ensures that the server is always ready for use. Please note that no data will be deleted from the PACS or similar, only the cached and encrypted DICOM data of the mRay server will be removed.
  3. Specifies the desired free space in gigabytes if automatic deletion is activated.
  4. If checked, the server uses an alternate working mRay path to store data like the cached and encrypted DICOM files there.
  5. Set the alternate working folder. If enabled, the application data of newly created pools are stored within that path.
  6. Choose which devices of a user do instantly get access without permission of the administrator.
  7. If checked the server will connect to the gateway URL given in the input field. Input field: Set the address of the mRay Gateway installation the mRay Server should connect to. Make sure that the specified URL includes the port of the gateway. If you want your mRay Server to connect to multiple gateways you can specify their addresses by using a semicolon as a separator. For example: demo.mray.info:35000 or heidelberg.mbits.info:34999;test.mray.info:35001
  8. If enabled, set the settings for the LDAP connection.
  9. Fill in your IP address or server URL in this input field. If the server needs to be contacted via a special port you need to append a colon followed by the port. For example: ad.mbits.info:40000 bzw. 192.168.1.100:40000
  10. Fill in the domain which contains the users and groups. This input field is optional. If it is empty, the domain will be requested from the LDAP server. By setting the option "LDAP - Domain is DN" unequal 0 in the advanced options the fully qualified domain needs to be specified (e.g. dc=ad,dc=example,dc=com).
  11. Insert your username here (optional in case of an anonymous login). By setting the options "LDAP - Username is DN" and/or "LDAP - Domain is DN" unequal 0 in the advanced options the fully qualified username needs to be specified. (e.g. cn=ldapuser,dc=ad,dc=example,dc=com).
  12. Insert your password here.
  13. Here you can input the time interval to synchronize with the LDAP server.
  14. Press this button to synchronize the LDAP server immediately. Please note that all changes within the settings will be applied.
  15. Shows the current synchronization state.
  16. Here you can choose, which groups and their users will be stored in the user and groups directory of the mRay server.
  17. With this input field you can search for special groups.
  18. Apply the changed settings. Note: Changes to the fields 1-7 must always be confirmed with this button.
  19. Revert the changed settings.

Notice

For the integration scenario 'mRay server with worldwide access' you can configure the server worldwide with the mRay configuration and internet access. Please be cautious to use a strong administrator password (at least 8 characters, upper/lower case and digits).

Notice

Please note that if you have activated the LDAP synchronization (see point 8), you must also configure an existing sender e-mail account (see chapter "E-Mail SMTP"). This is required to send an automatic PIN notification to an mRay LDAP user to be authenticated if requested. A new PIN request is usually made in the case of a first authentication or a password change.

Notice

The expire time of a PIN that is requested by an LDAP user can be manually set using the advanced options (see the Advanced options section) using the 'LDAP - Time after PIN expires' setting.

Info

Changes need to be confirmed before they are applied.

Pool management

The Pool Tab (Figure 11) lets you create, edit and delete „pools“:

Figure 11

  1. Adds a new pool.
  2. „Edit“ or double clicking a pool will open the edit dialog.
  3. Deletes the selected pool.
  4. Filter the pool list using free text.
  5. This button will only be shown if your license includes the PACS upload feature. This features enables structured reports, presentation states and photos to be stored in a PACS. Push this button to open the PACS Upload Pool settings. You can enter your PACS address, port and AET in the dialog. Note that you may need to enter the upload pool as a DICOM send entity in your PACS (depending on the PACS software).
  6. Press this button to edit the share pool settings. This pool is used to host shared data. If your license doesn't include the PACS upoad feature then all datasets created on client devices (i.e. structured reports, presentation states and photos) will be stored in this pool. Otherwise only internally shared presentation states will be stored in the share pool.

There are three different types of pools: Network Nodes, Query/Retrieve pools and External DICOM Folders.

Network node pool

A Network node pool is equivalent to a regular DICOM node (Figure 12).

Abbildung 12

  1. Select which type of pool you want to create:
    • Network node: Represents an ordinary PACS node to which you can send data from a PACS.
    • Query/Retrieve: Represents a pool with which you can send search queries to a PACS.
    • External DICOM folder: Access to an abitrary folder.
  2. Specify a name for the pool. The checkbox lets you activate or deactivate the pool (without deleting it).
  3. If activated, a different working path for the new pool can be specified where all data is stored. This will overwrite the general setting on the working path (if set). Please note, however, that the settings concerning free space and limits will apply to that path.
  4. Enables a DICOM C-Store SCP listener through which you can send DICOM data from your PACS to your pool. A TCP input port and an application entity title (AET) for the DICOM C-Store SCP listener must be set for this pool.
    1. Please note: You have to add the specified AET and port of the mRay server to your PACS configuration. Otherwise you will not be able to send images to mRay.
    2. A possible connection error while sending image data from a PACS workstation to the mRay server, cannot be detected by mRay.
  5. Activates the temporary storage of already retrieved or transmitted datasets, which speeds up a later search for these datasets. When this option is activated, new incoming datasets are not automatically placed in the user's inbox, but must first be moved to the inbox via the search tab.
  6. Let’s you specify a limit of datasets that this pool can contain. Use this option to limit the entries that will displayed to the users within the client application.
  7. Delete incoming datasets from the server after the specified number of days. You can also enter floating-point numbers (e.g. „2.5“).
  8. „Zero Footprint Mode“ enforces a deletion of data immediately after viewing it on the client. Choosing this option will disable functions 8 and 9.
  9. Let’s you specify how long local data on the client app will be available.
  10. Activates/deactivates the “auto download” feature. If enabled here and in the client app, incoming datasets will automatically be downloaded to the client app.
  11. Activates/ deactivates JPEG Compression for this pool.
  12. The mRay server can optionally remove patient information from incoming image data (“Pseudonymization”).

Warning

Burned-in information cannot be removed. Please ensure, that there is no personal information directly encoded in your images when using this feature.

Warning

JPEG compression is only supported for images with maximum 12 bits and lossless compression is only supported for images with maximum 16 bits.

Query/Retrieve pool

A Query/Retrieve Pool is created to search a PACS from within the client app (Figure 13).

Figure 13

Any function already described in 'Network Node Pool' will not be explained. These are the different form fields to consider:

  1. Specify first the local port and the AET for the mRay server (i.e. the AET which will receive answers from your PACS). On the second line specify the connection details of your PACS.
  2. Status field containing potential errors.
  3. Creates the pool.
  4. Abort Creation of the pool.

Notice

You have to add the specified AET and port of the mRay server to your PACS configuration. Otherwise the connection will not be accepted by your PACS.

External DICOM folder pool

An external DICOM folder (Figure 14) imports dicom data from a local directory.

Figure 14

All other fields are explained in chapter 'Network node pool'.

  1. Specify the external directory containing DICOM data here.

Info

The external DICOM folder pool also supports non DICOM file types i.e. PDF, PNG, JPG, TIFF, TGA and BMP

User management

The Users tab lets you add, edit and delete users (Figure 15).

Figure 15

  1. Add a new user.
  2. Edit the selected user. Or double click the user item in the list.
  3. Delete the selected user.
  4. Filter the users list using free text.

Create and edit users

After clicking “add” or “edit” the user dialog will come up (Manual users: figure 16a, LDAP synchronized users: figure 16b).

1

2

3

4

5

6

7

8

9

10

11

12

13

14

14

15

Abbildung 16a

1

2

19

18

17

16

4

5

6

7

8

9

10

11

13

14

14

15

Abbildung 16b

  1. Specify the login name.
  2. Complete name of the user (will be shown to others in chat-rooms).
  3. Enter and confirm the password for the user.
  4. These entries will appear depending on your server license modules.
  5. Enable PACS upload: enables the automatic upload of DICOM datasets for this user. This effects the creation of Structured Reports and Key Images. Sharing of KeyImages in messenger will not be effected.
  6. Enable photo capturing: enables the capturing of photos as a DICOM series (wounddocumentation) for this user. This effects the photo button in the inbox.
  7. Choose whether this user is allowed to use the messaging feature.
  8. Allows a user to share a dataset with other users who have no access to the related pool.
  9. The devices list cannot be edited by hand. It lists all device IDs with which the user has been registered. By selecting/deselecting the checkbox of a device ID access can be allowed/prohibited a user's device.
  10. Deletes a selected device.
  11. Check all pools the user should have access to.
  12. Error messages.
  13. Applies the changes.
  14. Cancel changes.
  15. Enables or disables the user (Disabled users can not connect to the server).
  16. Alternate e-mail address(es). Will be preferred against LDAP mail (see item 18) in case of e-mail notifications. You can use the semicolon separator (;) to specify multiple e-mail addresses.
  17. DN (short: distinguished name), i.e. unique identifier within the LDAP directory, of the synchronized LDAP user.
  18. LDAP synchronized e-mail address of an LDAP user. Is used for the automatic dispatch of important e-mail notifications from mRay. Can be overwritten by an alternative e-mail address (see item 16).
  19. Triggers a new PIN request for a user, so that the most recent LDAP password is queried again (for example, in case of password change).

Notice

Please take care of the characters used for the password as they might not be available on the keyboard of a mobile device.

Info

Manual users can still be maintained and used alongside LDAP synchronized users.

Group management

The Groups tab (Figure 17) lets you manage user groups. You can grant access to certain pools for a group of users at the same time. Furthermore, a group also represents a chat-room within the client app (if enabled).

Figure 17

  1. Adds a group.
  2. Edit the selected group. Alternatively double click on the group item in the list.
  3. Delete the selected group.
  4. Search the group list using free text.

Add or edit groups

The group dialog (Figure 18) will show up after clicking add/edit in the groups tab.

Figure 18a

Figure 18b

  1. Provide a name for the group. Please note that this will also be the name of the chat-room.
  2. Enable PACS upload: enables the automatic upload of DICOM datasets for this user. This effects the creation of Structured Reports and Key Images. Sharing of KeyImages in messenger will not be effected.
  3. Enable photo capturing: enables the capturing of photos as a DICOM series (wounddocumentation) for this user. This effects the photo button in the inbox.
  4. Enable photo documentation: enables the photo documentation feature for this user. This effects the photo button in the inbox.
  5. Enable/disable messaging for the group. If disabled no chat-room will be created.
  6. Enable access rights of the group for one or several pools.
  7. Add users to the group or remove them.
  8. Enables or disables the Group. (Disabled groups are not connected to the server).
  9. Apply changes.
  10. Abort changes.

Server log

The Log tab displays the last lines of the server log (Figure 19). The log is the most important tool for tracing errors. To get access to the complete server log use the 'Export server log' button.

Figure 19

  1. Export the protocol to a file.
  2. Export an extended log file for your mbits support.
  3. Filter log entries using free text.

Email SMTP

In the "E-Mail SMTP" tab you can store an e-mail account and a corresponding mail outgoing server. This is used to send e-mail notifications to users of mRay. An example is the automatic PIN notification with activated / licensed LDAP user synchronization.

Abbildung 20

  1. IP or name of the outgoing mail server to which the mails are forwarded for dispatch.
  2. Port of the outgoing mail server (optional). This can vary depending on the security setting of the connection (see point 3).
  3. Security setting / encryption regarding the communication link between mRay and the outgoing mail server. The following options are available: None = Unsecured connection (default ports: 25, 587), SSL / TLS = Secure connection (default port: 465), STARTTLS = Unsecured connection with upgrade to a secure connection (default ports: 25, 587).
  4. E-mail address of the sender via which the notifications or e-mails are sent.
  5. Username of the sender's e-mail account for logging on to the outgoing mail server.
  6. Password of the sender's e-mail account for logging on to the outgoing mail server.
  7. Checks the connection and logon data against the outgoing mail server.
  8. Optional e-mail addresses of the administrators who are to receive important notifications regarding the operation of mRay (e.g., reporting on outgoing PIN notifications to users). Using the semicolon separator (;), you can specify several e-mail addresses.

Remote Auto-Update

Since version 5.3, you can also use the "About" dialog of the configuration to install server updates via a remote computer. To do this, go to the Update tab of the configuration "About" dialog.

1

2

3

Abbildung 21

  1. Shows the currently uploaded mRay Server Installer version. This is only displayed if it is a valid and supported installer.
  2. Uploads the preselected mRay Server Installer.
  3. Starts the currently uploaded mRay Server Installer to update the server.

Advanced options

In addition to the default settings that you make through the graphical interface of the mRay Configuration application, there is an advanced options tab which allows to customize server and client behaviour.

Figure 22

  1. Title: Shows a human readable name of the option.
  2. Value: Shows the Value of the option.
  3. Value: values displayed in black are default values, the green ones are customized.
  4. Filter: Use free text to find an option.
  5. Restart Server: Restarts the server automatically.

Notice

Any change in the advanced options tab reqires a restart of the server application to be applied.

In order to edit an option, double cklick on its row to open the edit window.

Figure 23

  1. Description of the option.
  2. Default value (can change between mRay versions).
  3. Current value (grey means empty/default).
  4. Reset the value to its default.
  5. Apply the value and close the window.
  6. Do not change the value and close the window.

Photo Documentation

The photo documentation feature is expressly not permitted to be used for diagnosis or treatment decisions. The feature is only available for evaluation purposes. To take part in the evaluation and use the photo documentation feature please contact the mbits support team. You may need an mRay server license that has the feature enabled and the following settings to be configured properly:

Advanced Options Tab:

  1. "PhotoDoc-Tagging Entries Specification": Entered in advanced tab and specifies a tagging model in the JSON format that will be displayed on the client side
  2. "PhotoDoc - Export path": Specifies a folder that will be used by the server to export completed orders. Those orders are then picked picked up by the backend.

User/Group-Options:

  1. Enable photo capturing: Must be enabled so the photo capturing feature is available for the given user or group.

FAQ

Server application

  1. Why do all datasets except the last 20-30 disappear from the server? Please check the free space on your server. See section General settings.
  2. Which files should be backed up regularly?
    • On Windows the important files are saved in the folder C:\ProgramData\MBITS\mRayServer. You should backup these files.
      • config.ini (saves basic server options like port number, etc.)
      • mraydb.mes (main database, saves everything concernig users, pools, etc.)
      • mraydb.mes-wal (if available)
      • license.ini (license which has been installed for the server activation)
      • options.ini (advanced options)
    • Please notice that received image datasets might be located at a different place on the drive according to the settings made in the configuration. By default, the location described above is used. These can be backed up as well. In case of a reinstallation it is meaninful to resend the data from the PACS again where it is stored normally.
    • mRay features a built-in backup mechanism that saves the fundamental settings of the server. This process is triggered e.g. before an LDAP synch.

The installation package contains a backup script 'mRayServerBackup.bat' which copies those files into a folder on the desktop.

Client application

  1. Why do some datasets have the red tag „resolution reduced by xy%“? The application supports pictures up to 4096*4096*4096 pixels. Larger datasets will be resized. The percentage value describes the compression ratio.
  2. Why do some datasets have the green tag „JPEG”? Those datasets are transferred by employing JPEG compression (according to the Konsensius-Conference [Loose et al. 2009]).
  3. The patient list does not show all datasets. Why? Please ensure that the search field is empty.
  4. Why are no results shown after performing a query search to my PACS, although the patient is listed in my PACS? Some PACS distributers require a case sensitive search. Searching for “smith” will not lead to a result list as searching for “Smith” does.

Known issues

The list of known issues leads to problems identified after the release of the latest version of mRay. These problems, however, were classified as non-critical, so that an unrestricted working with the application is possible.

  1. Pseudonymization of images is not applied to the burned- in pixel data information. Please communicate this fact to the users to ensure that the data is sent only to pools for which Pseudonymization is turned off.
  2. Form fields for floating point numbers within the configuration application only accept values in english format, i.e. with a point as a delimiter.
  3. The auto-download setting Wifi/Mobile is not applicable for the Windows version of mRay client app.
  4. The image retrieve status information can sometimes hang at 100% until the image is finally retrieved.
  5. Multi touch gestures might trigger a button press event if they end above a button. This will happen altough the gesture is recognized as intended.
  6. With Android 6.0.1 and higher it is possible, that the application crashes in some infrequent cases if it is running in background mode. The application then shows a black screen and can not be operated anymore. It will be usable again as soon as it is terminated and restarted, which means you need to remove it from the overview of the running apps.
  7. The Windows desktop client application may show a blank icon in the taskbar for a short time.
  8. Creating DICOM Structured Reports does not work with non DICOM files.
  9. In rare cases it takes a little more time as usual to log in, if the device was just approved by the administrator.
  10. The new Android 7 splitscreen mode will lead the application to crash, if it is displayed in a splitscreen.
  11. The camera on a MED-TAB v2 does not focus correctly.
  12. Emojis in text fields can behave unexpectedly.
  13. A global cache path to a network drive can cause problems (concerns mRay server only) 
  14. A MED-TAB v1 shows artifacts in overlay images when hardware-side DICOM mode is enabled.
  15. .The initial layout of a photo in the chat can be wrong
  16. Automatic memory management on the mobile device may be incorrect if several mRay accounts are used on the device. Although the data is no longer accessible, they are not deleted under certain circumstances.

Information

  • The DICOM conformance statement can be consulted at the following address.
  • To avoid operating delays in your medical office or station in case of a failure of your main device by e.g. a hardware defect, operating system failure, overheating or similar please make sure that you always keep a functional backup device ready.
  • If JPEG compression is selected for a pool it is not guaranteed that all datasets are compressed using jpeg encoding. Please note the information in Pool-Management about supported number of bits. The decision between lossless and jpeg compression is also based on the resulting size of a dataset.
  • If anti-virus software is used please make sure that the configuration prevents possible data losses for directories containing patient data.