Mercurial > hg > orthanc-book
comparison Sphinx/source/dicom-guide.rst @ 412:969d50e63b17 c-get
first info about c-get
author | Alain Mazy <alain@mazy.be> |
---|---|
date | Tue, 12 May 2020 07:38:15 +0200 |
parents | d217af5e6cb3 |
children | 3ec4d890912e |
comparison
equal
deleted
inserted
replaced
411:b4cc2b6a9f13 | 412:969d50e63b17 |
---|---|
569 | 569 |
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.4.1, C-Get is not supported yet (but work is in | 575 that has been introduced in Orthanc 1.7.0 (see below). |
576 progress). | 576 |
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 |
581 the :ref:`negotiation of a presentation context | 581 the :ref:`negotiation of a presentation context |
587 compression, the JPEG 2000 image that is received by Orthanc might be | 587 compression, the JPEG 2000 image that is received by Orthanc might be |
588 unusable by such software. You might therefore have to **disable | 588 unusable by such software. You might therefore have to **disable |
589 transfer syntaxes** by setting the ``*TransferSyntaxAccepted`` options | 589 transfer syntaxes** by setting the ``*TransferSyntaxAccepted`` options |
590 to ``false`` in the :ref:`configuration file of Orthanc | 590 to ``false`` in the :ref:`configuration file of Orthanc |
591 <configuration>` (by default, all the transfer syntaxes are enabled). | 591 <configuration>` (by default, all the transfer syntaxes are enabled). |
592 | |
593 | |
594 .. _dicom-get: | |
595 | |
596 C-Get: retrieve | |
597 ^^^^^^^^^^^^^^^ | |
598 | |
599 Once you know that a DICOM resource is available on a particular | |
600 DICOM node, you may retrieve it directly without performing a C-Find | |
601 before. This can be done once you know one ore more of the unique | |
602 key attributes (``PatientID``, ``StudyInstanceUID``, ``SeriesInstanceUID`` | |
603 or ``SOPInstanceUID``). | |
604 | |
605 As of Orthanc 1.7.0, Orthanc implements C-Get as a service provider (SCP) | |
606 but not as a service user (SCU). One way to use the C-Get against an | |
607 Orthanc is by using the `DCMTK <https://support.dcmtk.org/docs/dcmconv.html>`__ toolkit:: | |
608 | |
609 $ getscu -v localhost 4242 -aec ORTHANC -k "000d,0020=1.2...." -k "0008,0052=STUDY" | |
610 | |
611 | |
592 | 612 |
593 | 613 |
594 | 614 |
595 Using HTTP instead of the DICOM protocol | 615 Using HTTP instead of the DICOM protocol |
596 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | 616 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |