Orthanc Explorer is not user-friendly enough for my use

Orthanc is designed as a lightweight service for medical imaging, where the word service must be understood in the sense of service-oriented architectures. As a consequence, Orthanc is conceived as a robust back-end server (command-line) that aims to provide the most simple and generic support of DICOM. To state it differently, the primary focus of the Orthanc project is not on the user interface.

However, Orthanc comes out-of-the-box with Orthanc Explorer, its default Web user interface. Orthanc Explorer is designed for development, low-level purpose. It is also used by the development team to test the features of Orthanc as they get introduced in the REST API. Orthanc Explorer is mainly targeted towards an English-speaking technical audience (notably system/network engineers, PACS managers, medical physicists, and researchers).

Non-technical audience (physicists, patients, administrative staff...) might expect an user interface that is more user-friendly than Orthanc Explorer, and/or that integrates more features (such as language translations, sorting resources, access control lists, tagging images, beautiful layout, tunable anonymization, modification of instances, paging if many patients, handling of timeouts, login/logout, Web diffusion to patients/physicians, calendar to chose dates...). If you need such a more advanced user experience so that Orthanc better fits your clinical workflow, you will have to develop a separate, custom Web interface on the top of the REST API of Orthanc, maybe as a plugin. Any front-end Web developer could take care of this task using well-known JavaScript frameworks (such as Angular, Vue.js...).

Note

Since May 2022, a new Orthanc Explorer 2 plugin is available to provide a more user-friendly, more configurable and evolutive UI for Orthanc.

Finally, you may also have a look to the following related projects: