Mercurial > hg > orthanc-book
comparison Sphinx/source/dicom-guide.rst @ 166:3b80f348cc6b
Orthanc 1.4.2
| author | Sebastien Jodogne <s.jodogne@gmail.com> |
|---|---|
| date | Thu, 20 Sep 2018 15:00:49 +0200 |
| parents | 07dc35042826 |
| children | a363714813b2 |
comparison
equal
deleted
inserted
replaced
| 165:b879a6274065 | 166:3b80f348cc6b |
|---|---|
| 238 different patients imaged in different hospitals might share the same | 238 different patients imaged in different hospitals might share the same |
| 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:* Note that since Orthanc 1.4.0, the :ref:`Orthanc Explorer |
| 244 <orthanc-explorer>` interface (1.4.1 at the time of writing) is | 244 <orthanc-explorer>` interface provides a new tab entitled "Studies" |
| 245 designed for single-hospital scenarios, and thus does not provide | 245 for study-level access. |
| 246 study-level access. But the core engine of Orthanc does support | |
| 247 study-level access through its :ref:`REST API <rest>`. | |
| 248 | 246 |
| 249 Finally, the patient module is not always fully meaningful. This is | 247 Finally, the patient module is not always fully meaningful. This is |
| 250 for instance the case in emergency imaging, where the `radiology | 248 for instance the case in emergency imaging, where the `radiology |
| 251 information system | 249 information system |
| 252 <https://en.wikipedia.org/wiki/Radiology_information_system>`__ might | 250 <https://en.wikipedia.org/wiki/Radiology_information_system>`__ might |