when I’m in ohif exoplorer when I click the back logo you can’t go back to explorer2 and not to ohif’s “Study List”
go to this address: …ui/app/#/ and not …ohif/
// Defines the order in which the viewer icons should appear in the interface
// OHIF viewers modes that are not listed here, won't appear in the interface.
"ViewersOrdering" : [
"osimis-web-viewer",
"stone-webviewer",
"ohif",
"ohif-vr",
"ohif-tmtv",
"ohif-seg",
// "ohif-micro", // currently disabled, this is still experimental in OHIF
"meddream",
"volview",
"wsi"
],
I’m not sure this is possible (but we are not OHIF experts). However, it seems there is a showStudyList option in the OHIF configuration file that can be set to false to remove the back button.
We are also working with OHIF and Orthanc and I think I might give you a solution for the “back” button.
As @alainmazy said, you can set showStudyList: false in the OHIF configuration to remove this button. You can also set whiteLabeling alongside it to customize the logo (it does remove the OHIF logo though). Here is the doc.
You could do something like so:
whiteLabeling: {
createLogoComponentFn(React, props) {
// Create a button (to be customized)
return React.createElement(
"button",
{ // props
onClick: () => history.back() // go to the previous page
},
[] // children
)
}
}
yessss.when I can understand if the system can be right for us, I will definitely make the donationI’m understanding what the best configuration is for a small medical practice, with doctors who upload the dicoms remotely.
orthanc only for administrator and then connect clients like horos?
or ortanch and ohif? but in this case can everyone also delete their studies?
also for safety reasons, which configuration should you choose?
Yes, indeed. However, they, technically, still have access to the whole API and can therefore delete other doctor’s studies.
This can be handled by a small Lua script.
eh what is that script for? how do you use it? what does it do? does it create accounts that can write and delete?
I tried to configure the HOROS client, but how does that work too? does the doctor upload the dicoms to the local and then upload them to the server if he wants? same to see those on the server… does he have to download them to see them?
isn’t there something that keeps the HOROS client synchronized with the server without the doctor having to upload and download manually?
As explained in the documentation I pointed before, you must create a separate ohif.js JSON file that contains the options to configure OHIF. Then, set UserConfiguration to ohif.js.