Rebranding & Security

Watch the technical training’s video recording:

TECHNICAL TRAINING video: MedDream rebranding & security. 2022-09-20

Agenda of the technical training:

Different rebranding types;
Changing logotypes, theme color, and About box information;
Viewport API rebranding;
Secure MedDream DICOM Viewer installation;
Permissions and restrictions for MedDream DICOM Viewer;
MedDream DICOM Viewer configuration using SSL;
MedDream DICOM Viewer configuration using iFrame;
Secure integration of MedDream DICOM Viewer;
Q&A.

Speakers:

Speaker: Marius Šadauskas, System Integrator at Softneta.

Moderator: Renata Kalniūnienė, Marketing Project Manager at Softneta.

During the webinar, these questions from the attendees were answered:

– Please touch a fair bit on the modality worklist.
– Recommendation for SSL terminated reverse Proxy:
1. Are SSL-terminate reverse proxies supported?
2. Do you have software recommendations? For example NGINX, Apache.
3. Do you have any important or critical configuration tips?
– Probably covered in the manual or by testing it out, but I am using the opportunity: Questions about generating Softneta Token V2 with Token Service no Accounts in use. Now generating tokens without Permission Tag works. Does it grant authorization.defaultHisPermissions permission to those tokens? Would setting the Permission per Token limit the access? Should you set permissions per Token?
– Partnership / agent fee.
– What about documentation sources for rebranding the help files / user documents?
– Alongside windows – please do share information on Linux platform as well when you share details / recording later.
– Instead of “hard coded” branding colors, could you support adding the color as a hex value? That way I could set the color to match our own branding guidelines.
– Can the new 8.0.0 version be installed over a 7.9.0 version by the customer without direct support from Softneta without risking losing the 7.9.0 settings?
– How can the permissions be configured for different users? For example one group of doctors should not have access to the patient history, but others should have it.
– Is it possible to redirect user automatically from HTTP to HTTPS?
– Does the token integration also work with patient ID’s instead of studies?
– For SSL is it possible to use wildcard certificate?
– In the standalone MedDream application: s it possible to deactivate a user for a certain time after a few failed logins in order to counter possible hacking attempts?
– We just upgraded to version 8.0.0, works great but just one question on the worklist we used to tell which studies are viewed and which are not but now everything is the same (before it used to be shaded and unshaded ), is there any setting that I need to enable? (Answer: This functionality was in version 7.1 in combination with MedDream PACS. It was cancelled because other PACSes do not have this feature.)