Mercurial > hg > orthanc-book
comparison Sphinx/source/dicom-guide.rst @ 135:0691978ee3d9
Orthanc 1.3.2
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 18 Apr 2018 15:08:59 +0200 |
parents | 9badd112e8ad |
children | 80b39dfa1e3c |
comparison
equal
deleted
inserted
replaced
134:6a9e5f2b10b2 | 135:0691978ee3d9 |
---|---|
239 *PatientID*. For this reason, you should always browse from the study | 239 *PatientID*. For this reason, you should always browse from the study |
240 level (and not from the patient level) as soon as you deal with an | 240 level (and not from the patient level) as soon as you deal with an |
241 application that handles patients from different hospitals. | 241 application that handles patients from different hospitals. |
242 | 242 |
243 *Note:* The current version of the :ref:`Orthanc Explorer | 243 *Note:* The current version of the :ref:`Orthanc Explorer |
244 <orthanc-explorer>` interface (1.3.1 at the time of writing) is | 244 <orthanc-explorer>` interface (1.3.2 at the time of writing) is |
245 designed for single-hospital scenarios, and thus does not provide | 245 designed for single-hospital scenarios, and thus does not provide |
246 study-level access. But the core engine of Orthanc does support | 246 study-level access. But the core engine of Orthanc does support |
247 study-level access through its :ref:`REST API <rest>`. | 247 study-level access through its :ref:`REST API <rest>`. |
248 | 248 |
249 Finally, the patient module is not always fully meaningful. This is | 249 Finally, the patient module is not always fully meaningful. This is |
570 *Note 1:* Even if C-Move may seem counter-intuitive, this is the most | 570 *Note 1:* Even if C-Move may seem counter-intuitive, this is the most |
571 popular and widespread way to initiate a query/retrieve against a PACS | 571 popular and widespread way to initiate a query/retrieve against a PACS |
572 server. The DICOM standard features an `alternative mechanism called | 572 server. The DICOM standard features an `alternative mechanism called |
573 C-Get | 573 C-Get |
574 <http://dclunie.blogspot.be/2016/05/to-c-move-is-human-to-c-get-divine.html>`_. | 574 <http://dclunie.blogspot.be/2016/05/to-c-move-is-human-to-c-get-divine.html>`_. |
575 As of Orthanc 1.3.1, C-Get is not supported yet (but work is in | 575 As of Orthanc 1.3.2, C-Get is not supported yet (but work is in |
576 progress). | 576 progress). |
577 | 577 |
578 *Note 2:* As :ref:`written above <dicom-pixel-data>`, the Orthanc | 578 *Note 2:* As :ref:`written above <dicom-pixel-data>`, the Orthanc |
579 engine is quite generic and is compatible with virtually any image | 579 engine is quite generic and is compatible with virtually any image |
580 compression algorithm (aka. transfer syntax). In particular, during | 580 compression algorithm (aka. transfer syntax). In particular, during |