The settings tab allows an admin to configure some of the global settings for the FlexView account. The setting tab is not visible for general users.
General Viewer Settings
Organization name was set during signup for your account. You can edit that name here.
Subscription Details
Adjusting your subscription in FlexView is easy. Simply enter the number of additional people you’d like, and we’ll adjust your plan automatically. If you add or remove users in the middle of your billing cycle, your account will be prorated for the number of days your seats were active that month. You will see the adjustment on your next billing cycle.
If you you reduce the number of seats, you may need to set one or more users to inactive on the User tab.
Data Sources
This section allows you to add or edit the data sources for your viewer. For more details about configuration, see Configuring Image Data Sources
Authentication
This secret will apply to any connected data source that you configure to use JWT authentication.
Advance Settings
Performance
FlexView allows advance users to adjust the number of web workers. Web workers are used to speed up image processing. We do not recommend changing the default value unless you are experimenting performance issues on weak machines. Larger numbers of web workers increase the distribution of imaging rendering processing and may improve performance; however, keep in mind that each web-worker has a cost in CPU and eventually there will be a diminishing return into adding more of them. At some point as you increase the number of web workers, you will actually see decreased performance.
By default, this is set to 3.
Global Hotkeys
Advanced users can edit the hotkey JSON file to set hotkeys for all users in their organization. A hotkey definition should have the following properties:
commandName
: name of the registered commandcommandOptions
: extra arguments to the commandskeys
: an array defining the key to get bound to the commandlabel
: label to be shown in the hotkeys preference panel
By default the following hotkeys are set as:
hotkeys: [{ commandName: 'incrementActiveViewport', label: 'Next Viewport', keys: ['right'], }, { commandName: 'decrementActiveViewport', label: 'Previous Viewport', keys: ['left'], }, { commandName: 'rotateViewportCW', label: 'Rotate Right', keys: ['r'] }, { commandName: 'rotateViewportCCW', label: 'Rotate Left', keys: ['l'] }, { commandName: 'invertViewport', label: 'Invert', keys: ['i'] }, { commandName: 'flipViewportHorizontal', label: 'Flip Horizontally', keys: ['h'], }, { commandName: 'flipViewportVertical', label: 'Flip Vertically', keys: ['v'], }, { commandName: 'scaleUpViewport', label: 'Zoom In', keys: ['+'] }, { commandName: 'scaleDownViewport', label: 'Zoom Out', keys: ['-'] }, { commandName: 'fitViewportToWindow', label: 'Zoom to Fit', keys: ['='] }, { commandName: 'resetViewport', label: 'Reset', keys: ['space'] }, { commandName: 'nextImage', label: 'Next Image', keys: ['down'] }, { commandName: 'previousImage', label: 'Previous Image', keys: ['up'] }, // { // commandName: 'previousViewportDisplaySet', // label: 'Previous Series', // keys: ['pagedown'], // }, // { // commandName: 'nextViewportDisplaySet', // label: 'Next Series', // keys: ['pageup'], // }, { commandName: 'setZoomTool', label: 'Zoom', keys: ['z'] }, // ~ Window level presets { commandName: 'windowLevelPreset1', label: 'W/L Preset 1', keys: ['1'], }, { commandName: 'windowLevelPreset2', label: 'W/L Preset 2', keys: ['2'], }, { commandName: 'windowLevelPreset3', label: 'W/L Preset 3', keys: ['3'], }, { commandName: 'windowLevelPreset4', label: 'W/L Preset 4', keys: ['4'], }, { commandName: 'windowLevelPreset5', label: 'W/L Preset 5', keys: ['5'], }, { commandName: 'windowLevelPreset6', label: 'W/L Preset 6', keys: ['6'], }, { commandName: 'windowLevelPreset7', label: 'W/L Preset 7', keys: ['7'], }, { commandName: 'windowLevelPreset8', label: 'W/L Preset 8', keys: ['8'], }, { commandName: 'windowLevelPreset9', label: 'W/L Preset 9', keys: ['9'], }, ],
JSON Editor for Viewer Settings
Advanced users can edit the JSON configuration file for FlexView. Please be sure to include the viewer configuration key viewerConfig
and the Static WADO key staticWadoConfig
. If either of these are not set, your save will fail.
If you have questions about JSON configuration, contact FlexView technical support.
JSON Editor for Runtime Extensions
FlexView adds to OHIF’s extensibility model by introducing the ability to deploy plugins at runtime. This is crucial to enable the addition of new features dynamically, such as AI-based tools, without causing disruptions or system down-time.
The runtime configuration JSON represents an object with two main properties, "extensions" and "modes," each containing an array of objects. Here's a description of the structure:
1. extensions
(Array):
-
- An array containing objects representing extensions.
- In this JSON, there's one extension object in the array.
id
(String):- A unique identifier for the extension.
- In the example below, the
id
is "flexview-runtime-extension-tmtv."
url
(String):- A URL pointing to the location of the extension's JavaScript file.
- The URL in the example is "https://www.unpkg.com/flexview-runtime-extension-tmtv@0.1.2/dist/umd/flexview-runtime-extension-tmtv/index.umd.js. "
2. modes
(Array):
-
- An array containing objects representing modes.
- In this JSON, there's one mode object in the array.
id
(String):- A unique identifier for the mode.
- In the example below, the
id
is "flexview-runtime-mode-tmtv."
url
(String):- A URL pointing to the location of the mode's JavaScript file.
- The URL in this example is "https://www.unpkg.com/flexview-runtime-mode-tmtv@0.0.3/dist/umd/flexview-runtime-mode-tmtv/index.umd.js. "