|
20
|
1 .. _improving-interface:
|
|
|
2
|
|
0
|
3 Orthanc Explorer is not user-friendly enough for my use
|
|
|
4 =======================================================
|
|
|
5
|
|
|
6 Orthanc is designed as a lightweight service for medical imaging,
|
|
|
7 where the word *service* must be understood in the sense of
|
|
|
8 `service-oriented architectures
|
|
|
9 <https://en.wikipedia.org/wiki/Service-oriented_architecture>`__. As
|
|
|
10 a consequence, Orthanc is conceived as a robust back-end server
|
|
|
11 (command-line) that aims to provide the most simple and generic
|
|
|
12 support of DICOM. To state it differently, **the primary focus of the
|
|
|
13 Orthanc project is not on the user interface**.
|
|
|
14
|
|
|
15 However, Orthanc comes out-of-the-box with :ref:`Orthanc Explorer
|
|
|
16 <orthanc-explorer>`, its default Web user interface. **Orthanc
|
|
|
17 Explorer is designed for administrative, low-level purpose.** It is
|
|
|
18 also used by the development team to test the features of Orthanc as
|
|
|
19 they get introduced in the REST API. Orthanc Explorer is mainly
|
|
68
|
20 targeted towards an English-speaking technical audience (notably
|
|
|
21 system/network engineers, `PACS
|
|
0
|
22 <https://en.wikipedia.org/wiki/Picture_archiving_and_communication_system>`__
|
|
|
23 managers, medical physicists, and researchers).
|
|
|
24
|
|
|
25 **Non-technical audience** (physicists, patients, administrative
|
|
|
26 staff...) **might expect an user interface that is more user-friendly
|
|
|
27 than Orthanc Explorer**, and/or that integrates more features (such as
|
|
68
|
28 language translations, sorting resources, access control lists,
|
|
|
29 tagging images, beautiful layout, tunable anonymization, modification
|
|
134
|
30 of instances, paging if many patients, handling of timeouts,
|
|
281
|
31 login/logout, Web diffusion to patients/physicians...). If you need
|
|
|
32 such a more advanced `user experience
|
|
0
|
33 <https://en.wikipedia.org/wiki/User_experience>`__ so that Orthanc
|
|
|
34 better fits your clinical workflow, you will have to develop a
|
|
|
35 separate, custom Web interface on the top of the :ref:`rest`, maybe as
|
|
|
36 a `plugin
|
|
|
37 <https://github.com/jodogne/OrthancContributed/tree/master/Plugins>`__. Any
|
|
|
38 front-end Web developer could take care of this task using well-known
|
|
|
39 JavaScript frameworks (such as Meteor, AngularJS, Ember.js...).
|
|
|
40
|
|
|
41 It is possible that an official plugin that provides a more advanced
|
|
|
42 user interface will be developed in the future (provided we find
|
|
|
43 funding for this development). In the meantime, you can also contact a
|
|
|
44 company that provides **commercial support on the top of Orthanc** and
|
|
|
45 that might have developed an advanced user interface. Currently,
|
|
|
46 `Osimis <http://osimis.io/>`_ is the only company ensuring such
|
|
|
47 corporate services, but others might show up in the future. A `contact
|
|
|
48 form <http://www.orthanc-server.com/orthanc-pro.php>`_ is available on
|
|
|
49 the official Web page of Orthanc.
|
|
117
|
50
|
|
|
51 **Update (2017-10-03):** A team of Master students from `ULiège
|
|
|
52 <https://www.uliege.be/>`__ is currently working on creating a
|
|
|
53 revamped version of Orthanc Explorer. You can get in touch with them
|
|
|
54 on the `public discussion forum
|
|
|
55 <https://groups.google.com/d/msg/orthanc-users/oOyKTmfs-J0/B6eyBJcvCAAJ>`__.
|
