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