Mercurial > hg > orthanc-book
annotate Sphinx/source/users/rest.rst @ 674:5ec581c7e610
Warning about using cURL from the Windows prompt
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Thu, 06 May 2021 14:52:56 +0200 |
parents | bc8fa2bf4cf7 |
children | aba6dac03d16 |
rev | line source |
---|---|
0 | 1 .. _rest: |
2 | |
3 REST API of Orthanc | |
4 =================== | |
5 | |
6 .. contents:: | |
7 :depth: 3 | |
8 | |
9 One of the major strengths of Orthanc lies in its built-in `RESTful | |
10 API | |
11 <https://en.wikipedia.org/wiki/Representational_state_transfer>`__, | |
12 that can be used to drive Orthanc from external applications, | |
13 independently of the programming language that is used to develop | |
14 these applications. The REST API of Orthanc gives a full programmatic | |
15 access to all the core features of Orthanc. | |
16 | |
17 Importantly, Orthanc Explorer (the embedded administrative interface | |
18 of Orthanc) entirely resorts to this REST API for all its features. | |
19 This implies that anything that can be done through Orthanc Explorer, | |
20 can also be done through REST queries. | |
21 | |
22 *Note:* All the examples are illustrated with the `cURL command-line | |
25 | 23 tool <https://curl.haxx.se/>`__, but equivalent calls can be readily |
0 | 24 transposed to any programming language that supports both HTTP and |
25 JSON. | |
26 | |
27 | |
674
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
28 .. _curl-windows: |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
29 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
30 Warning about using cURL from the Windows prompt |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
31 ------------------------------------------------ |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
32 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
33 The examples on this page assume that the user is running a bash shell |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
34 on some GNU/Linux distribution. Such a shell has the major advantage |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
35 of having the possibility to use either single-quote or double-quotes |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
36 characters in order to group a set of characters (including spaces) as |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
37 a whole string. |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
38 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
39 .. highlight:: bash |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
40 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
41 Unfortunately, the default command-line prompt of Microsoft Windows |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
42 **doesn't support single-quote characters**. If you execute a cURL |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
43 command-line from this page that mixes single-quote and double-quotes, |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
44 you'll have to replace single-quotes by double-quotes, and prefix the |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
45 double-quotes by a backslash character. For instance, consider the |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
46 following command line that works fine on GNU/Linux:: |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
47 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
48 $ curl -v -X PUT http://localhost:8042/modalities/sample \ |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
49 -d '{"AET" : "ORTHANCC", "Host": "127.0.0.1", "Port": 2002}' |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
50 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
51 This call will **not** work on the Microsoft Windows prompt as it |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
52 contains single-quotes. You should adapt this command line as follows |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
53 to run it on Windows:: |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
54 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
55 $ curl -v -X PUT http://localhost:8042/modalities/sample \ |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
56 -d "{\"AET\" : \"ORTHANCC\", \"Host\": \"127.0.0.1\", \"Port\": 2002}" |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
57 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
58 As an alternative, consider using a different Windows shell, for |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
59 instance `Windows PowerShell |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
60 <https://fr.wikipedia.org/wiki/Windows_PowerShell>`__ (some examples |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
61 of PowerShell can be found below on this page). |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
62 |
5ec581c7e610
Warning about using cURL from the Windows prompt
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
671
diff
changeset
|
63 |
114 | 64 .. _sending-dicom-images: |
65 | |
0 | 66 Sending DICOM images |
67 -------------------- | |
68 | |
69 .. highlight:: bash | |
70 | |
71 The upload of DICOM files is possible by querying the REST API using | |
72 the following syntax:: | |
73 | |
74 $ curl -X POST http://localhost:8042/instances --data-binary @CT.X.1.2.276.0.7230010.dcm | |
75 | |
76 .. highlight:: json | |
77 | |
78 Orthanc will respond with a JSON file that contain information about | |
79 the location of the stored instance, such as:: | |
80 | |
81 { | |
82 "ID" : "e87da270-c52b-4f2a-b8c6-bae25928d0b0", | |
83 "Path" : "/instances/e87da270-c52b-4f2a-b8c6-bae25928d0b0", | |
84 "Status" : "Success" | |
85 } | |
86 | |
87 .. highlight:: bash | |
88 | |
89 Note that in the case of curl, setting the ``Expect`` HTTP Header will | |
90 significantly `reduce the execution time of POST requests | |
358
011b01ccf52d
fixing external hyperlinks
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
331
diff
changeset
|
91 <https://stackoverflow.com/questions/463144/php-http-post-fails-when-curl-data-1024/463277#463277>`__:: |
0 | 92 |
93 $ curl -X POST -H "Expect:" http://localhost:8042/instances --data-binary @CT.X.1.2.276.0.7230010.dcm | |
94 | |
95 The code distribution of Orthanc contains a `sample Python script | |
449 | 96 <https://hg.orthanc-server.com/orthanc/file/default/OrthancServer/Resources/Samples/ImportDicomFiles/ImportDicomFiles.py>`__ |
0 | 97 that recursively upload the content of some folder into Orthanc using |
98 the REST API:: | |
99 | |
100 $ python ImportDicomFiles.py localhost 8042 ~/DICOM/ | |
101 | |
102 | |
297
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
103 .. highlight:: perl |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
104 |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
105 If you are using Powershell (>= 3.0), you can use the following to send a single |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
106 Dicom instance to Orthanc:: |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
107 |
376 | 108 # disabling the progress bar makes the Invoke-RestMethod call MUCH faster |
297
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
109 $ProgressPreference = 'SilentlyContinue' |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
110 |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
111 # upload it to Orthanc |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
112 $reply = Invoke-RestMethod http://localhost:8042/instances -Method POST -InFile CT.X.1.2.276.0.7230010.dcm |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
113 |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
114 # display the result |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
115 Write-Host "The instance can be retrieved at http://localhost:8042$($reply.Path)" |
64d1ddab8246
Improved PDF creation Pwsh snippet + added Dicom instance upload example with
Benjamin Golinvaux <bgo@osimis.io>
parents:
294
diff
changeset
|
116 |
0 | 117 .. _rest-access: |
118 | |
119 Accessing the content of Orthanc | |
120 -------------------------------- | |
121 | |
122 Orthanc structures the stored DICOM resources using the "Patient, | |
123 Study, Series, Instance" model of the DICOM standard. Each DICOM | |
124 resource is associated with an :ref:`unique identifier <orthanc-ids>`. | |
125 | |
126 List all the DICOM resources | |
127 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
128 | |
129 Here is how you would list all the DICOM resources that are stored in | |
130 your local Orthanc instance:: | |
131 | |
132 $ curl http://localhost:8042/patients | |
133 $ curl http://localhost:8042/studies | |
134 $ curl http://localhost:8042/series | |
135 $ curl http://localhost:8042/instances | |
136 | |
137 Note that the result of this command is a `JSON file | |
25 | 138 <https://en.wikipedia.org/wiki/Json>`__ that contains an array of |
0 | 139 resource identifiers. The JSON file format is lightweight and can be |
140 parsed from almost any computer language. | |
141 | |
142 Accessing a patient | |
143 ^^^^^^^^^^^^^^^^^^^ | |
144 | |
145 .. highlight:: bash | |
146 | |
147 To access a single resource, add its identifier to the `URI | |
25 | 148 <https://en.wikipedia.org/wiki/Uniform_resource_identifier>`__. You |
0 | 149 would for instance retrieve the main information about one patient as |
150 follows:: | |
151 | |
152 $ curl http://localhost:8042/patients/dc65762c-f476e8b9-898834f4-2f8a5014-2599bc94 | |
153 | |
154 .. highlight:: json | |
155 | |
156 Here is a possible answer from Orthanc:: | |
157 | |
158 { | |
159 "ID" : "07a6ec1c-1be5920b-18ef5358-d24441f3-10e926ea", | |
160 "MainDicomTags" : { | |
161 "OtherPatientIDs" : "(null)", | |
162 "PatientBirthDate" : "0", | |
163 "PatientID" : "000000185", | |
164 "PatientName" : "Anonymous^Unknown", | |
165 "PatientSex" : "O" | |
166 }, | |
167 "Studies" : [ "9ad2b0da-a406c43c-6e0df76d-1204b86f-78d12c15" ], | |
168 "Type" : "Patient" | |
169 } | |
170 | |
171 This is once again a JSON file. Note how Orthanc gives you a summary | |
172 of the main DICOM tags that correspond to the patient level. | |
173 | |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
174 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
175 .. _browsing-hierarchy: |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
176 |
0 | 177 Browsing from the patient down to the instance |
178 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
179 | |
180 .. highlight:: bash | |
181 | |
182 The field ``Studies`` list all the DICOM studies that are associated | |
183 with the patient. So, considering the patient above, we would go down | |
184 in her DICOM hierarchy as follows:: | |
185 | |
186 $ curl http://localhost:8042/studies/9ad2b0da-a406c43c-6e0df76d-1204b86f-78d12c15 | |
187 | |
188 .. highlight:: json | |
189 | |
190 And Orthanc could answer:: | |
191 | |
192 { | |
193 "ID" : "9ad2b0da-a406c43c-6e0df76d-1204b86f-78d12c15", | |
194 "MainDicomTags" : { | |
195 "AccessionNumber" : "(null)", | |
196 "StudyDate" : "20120716", | |
197 "StudyDescription" : "TestSUVce-TF", | |
198 "StudyID" : "23848", | |
199 "StudyInstanceUID" : "1.2.840.113704.1.111.7016.1342451220.40", | |
200 "StudyTime" : "170728" | |
201 }, | |
202 "ParentPatient" : "07a6ec1c-1be5920b-18ef5358-d24441f3-10e926ea", | |
203 "Series" : [ | |
204 "6821d761-31fb55a9-031ebecb-ba7f9aae-ffe4ddc0", | |
205 "2cc6336f-2d4ae733-537b3ca3-e98184b1-ba494b35", | |
206 "7384c47e-6398f2a8-901846ef-da1e2e0b-6c50d598" | |
207 ], | |
208 "Type" : "Study" | |
209 } | |
210 | |
211 .. highlight:: bash | |
212 | |
213 The main DICOM tags are now those that are related to the study | |
214 level. It is possible to retrieve the identifier of the patient in the | |
215 ``ParentPatient`` field, which can be used to go upward the DICOM | |
216 hierarchy. But let us rather go down to the series level by using the | |
217 ``Series`` array. The next command would return information about one | |
218 of the three series that have just been reported:: | |
219 | |
220 $ curl http://localhost:8042/series/2cc6336f-2d4ae733-537b3ca3-e98184b1-ba494b35 | |
221 | |
222 .. highlight:: json | |
223 | |
224 Here is a possible answer:: | |
225 | |
226 { | |
227 "ExpectedNumberOfInstances" : 45, | |
228 "ID" : "2cc6336f-2d4ae733-537b3ca3-e98184b1-ba494b35", | |
229 "Instances" : [ | |
230 "41bc3f74-360f9d10-6ae9ffa4-01ea2045-cbd457dd", | |
231 "1d3de868-6c4f0494-709fd140-7ccc4c94-a6daa3a8", | |
232 <...> | |
233 "1010f80b-161b71c0-897ec01b-c85cd206-e669a3ea", | |
234 "e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4" | |
235 ], | |
236 "MainDicomTags" : { | |
237 "Manufacturer" : "Philips Medical Systems", | |
238 "Modality" : "PT", | |
239 "NumberOfSlices" : "45", | |
240 "ProtocolName" : "CHU/Body_PET/CT___50", | |
241 "SeriesDate" : "20120716", | |
242 "SeriesDescription" : "[WB_CTAC] Body", | |
243 "SeriesInstanceUID" : "1.3.46.670589.28.2.12.30.26407.37145.2.2516.0.1342458737", | |
244 "SeriesNumber" : "587370", | |
245 "SeriesTime" : "171121", | |
246 "StationName" : "r054-svr" | |
247 }, | |
248 "ParentStudy" : "9ad2b0da-a406c43c-6e0df76d-1204b86f-78d12c15", | |
249 "Status" : "Complete", | |
250 "Type" : "Series" | |
251 } | |
252 | |
253 It can be seen that this series comes from a PET modality. Orthanc has | |
254 computed that this series should contain 45 instances. | |
255 | |
256 .. highlight:: bash | |
257 | |
258 So far, we have navigated from the patient level, to the study level, | |
259 and finally to the series level. There only remains the instance | |
260 level. Let us dump the content of one of the instances:: | |
261 | |
262 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4 | |
263 | |
264 .. highlight:: json | |
265 | |
266 The instance contains the following information:: | |
267 | |
268 { | |
269 "FileSize" : 70356, | |
270 "FileUuid" : "3fd265f0-c2b6-41a2-ace8-ae332db63e06", | |
271 "ID" : "e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4", | |
272 "IndexInSeries" : 6, | |
273 "MainDicomTags" : { | |
274 "ImageIndex" : "6", | |
275 "InstanceCreationDate" : "20120716", | |
276 "InstanceCreationTime" : "171344", | |
277 "InstanceNumber" : "6", | |
278 "SOPInstanceUID" : "1.3.46.670589.28.2.15.30.26407.37145.3.2116.39.1342458737" | |
279 }, | |
280 "ParentSeries" : "2cc6336f-2d4ae733-537b3ca3-e98184b1-ba494b35", | |
281 "Type" : "Instance" | |
282 } | |
283 | |
284 .. highlight:: bash | |
285 | |
286 The instance has the index 6 in the parent series. The instance is | |
287 stored as a raw DICOM file of 70356 bytes. You would download this | |
288 DICOM file using the following command:: | |
289 | |
290 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4/file > Instance.dcm | |
291 | |
292 | |
293 Accessing the DICOM fields of an instance as a JSON file | |
294 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
295 | |
296 .. highlight:: bash | |
297 | |
298 When one gets to the instance level, you can retrieve the hierarchy of | |
299 all the DICOM tags of this instance as a JSON file:: | |
300 | |
301 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4/simplified-tags | |
302 | |
303 .. highlight:: json | |
304 | |
305 Here is a excerpt of the Orthanc answer:: | |
306 | |
307 { | |
308 "ACR_NEMA_2C_VariablePixelDataGroupLength" : "57130", | |
309 "AccessionNumber" : null, | |
310 "AcquisitionDate" : "20120716", | |
311 "AcquisitionDateTime" : "20120716171219", | |
312 "AcquisitionTime" : "171219", | |
313 "ActualFrameDuration" : "3597793", | |
314 "AttenuationCorrectionMethod" : "CTAC-SG", | |
315 <...> | |
316 "PatientID" : "000000185", | |
317 "PatientName" : "Anonymous^Unknown", | |
318 "PatientOrientationCodeSequence" : [ | |
319 { | |
320 "CodeMeaning" : "recumbent", | |
321 "CodeValue" : "F-10450", | |
322 "CodingSchemeDesignator" : "99SDM", | |
323 "PatientOrientationModifierCodeSequence" : [ | |
324 { | |
325 "CodeMeaning" : "supine", | |
326 "CodeValue" : "F-10340", | |
327 "CodingSchemeDesignator" : "99SDM" | |
328 } | |
329 ] | |
330 } | |
331 ], | |
332 <...> | |
333 "StudyDescription" : "TestSUVce-TF", | |
334 "StudyID" : "23848", | |
335 "StudyInstanceUID" : "1.2.840.113704.1.111.7016.1342451220.40", | |
336 "StudyTime" : "171117", | |
337 "TypeOfDetectorMotion" : "NONE", | |
338 "Units" : "BQML", | |
339 "Unknown" : null, | |
340 "WindowCenter" : "1.496995e+04", | |
341 "WindowWidth" : "2.993990e+04" | |
342 } | |
343 | |
344 .. highlight:: bash | |
345 | |
346 If you need more detailed information about the type of the variables | |
347 or if you wish to use the hexadecimal indexes of DICOM tags, you are | |
348 free to use the following URL:: | |
349 | |
350 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4/tags | |
351 | |
352 Accessing the raw DICOM fields of an instance | |
353 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
354 | |
355 .. highlight:: bash | |
356 | |
357 You also have the opportunity to access the raw value of the DICOM | |
358 tags of an instance, without going through a JSON file. Here is how | |
359 you would find the Patient Name of the instance:: | |
360 | |
361 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4/content/0010-0010 | |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
362 Anonymous^Unknown |
0 | 363 |
364 The list of all the available tags for this instance can also be retrieved easily:: | |
365 | |
366 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4/content | |
367 | |
368 It is also possible to recursively explore the sequences of tags:: | |
369 | |
370 $ curl http://localhost:8042/instances/e668dcbf-8829a100-c0bd203b-41e404d9-c533f3d4/content/0008-1250/0/0040-a170/0/0008-0104 | |
371 For Attenuation Correction | |
372 | |
373 The command above has opened the "0008-1250" tag that is a DICOM | |
374 sequence, taken its first child, opened its "0040-a170" tag that is | |
375 also a sequence, taken the first child of this child, and returned the | |
376 "0008-0104" DICOM tag. | |
377 | |
378 Downloading images | |
379 ^^^^^^^^^^^^^^^^^^ | |
380 | |
381 .. highlight:: bash | |
382 | |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
383 As :ref:`explained above <browsing-hierarchy>`, the raw DICOM file |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
384 corresponding to a single instance can be retrieved as follows:: |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
385 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
386 $ curl http://localhost:8042/instances/609665c0-c5198aa2-8632476b-a00e0de0-e9075d94/file > Instance.dcm |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
387 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
388 It is also possible to download a preview PNG image that corresponds |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
389 to some DICOM instance:: |
0 | 390 |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
391 $ curl http://localhost:8042/instances/609665c0-c5198aa2-8632476b-a00e0de0-e9075d94/preview > Preview.png |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
392 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
393 The resulting image will be a standard graylevel PNG image (with 8 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
394 bits per pixel) that can be opened by any painting software. The |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
395 dynamic range of the pixel data is stretched to the [0..255] range. |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
396 An equivalent JPEG image can be downloaded by setting the `HTTP header |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
397 <https://en.wikipedia.org/wiki/List_of_HTTP_header_fields>`__ |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
398 ``Accept`` to ``image/jpeg``:: |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
399 |
169 | 400 $ curl -H 'Accept: image/jpeg' http://localhost:8042/instances/609665c0-c5198aa2-8632476b-a00e0de0-e9075d94/preview > Preview.jpg |
0 | 401 |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
402 If you don't want to stretch the dynamic range, and create a 8bpp or |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
403 16bpp PNG image, you can use the following URIs:: |
0 | 404 |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
405 $ curl http://localhost:8042/instances/609665c0-c5198aa2-8632476b-a00e0de0-e9075d94/image-uint8 > full-8.png |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
406 $ curl http://localhost:8042/instances/609665c0-c5198aa2-8632476b-a00e0de0-e9075d94/image-uint16 > full-16.png |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
407 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
408 In these images, the values are cropped to the maximal value that can |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
409 be encoded by the target image format. The |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
410 ``/instances/{...}/image-int16`` is available as well to download |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
411 signed DICOM pixel data. |
0 | 412 |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
413 Since Orthanc 1.4.2, it is also possible to download such images in |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
414 the generic `PAM format |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
415 <https://en.wikipedia.org/wiki/Netpbm#PAM_graphics_format>`__:: |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
416 |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
417 $ curl -H 'Accept: image/x-portable-arbitrarymap' http://localhost:8042/instances/609665c0-c5198aa2-8632476b-a00e0de0-e9075d94/image-uint16 > full-16.pam |
0 | 418 |
168
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
419 Users of Matlab or Octave can find related information :ref:`in the |
86e92d0cc53e
information about images
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
155
diff
changeset
|
420 dedicated section <matlab>`. |
0 | 421 |
380 | 422 Downloading studies |
411 | 423 ^^^^^^^^^^^^^^^^^^^ |
380 | 424 |
425 .. highlight:: bash | |
426 | |
427 All instances of a study can be retrieved as a zip file as follows:: | |
428 | |
429 $ curl http://localhost:8042/studies/6b9e19d9-62094390-5f9ddb01-4a191ae7-9766b715/archive > Study.zip | |
430 | |
431 It is also possible to download a zipped DICOMDIR through:: | |
432 | |
381 | 433 $ curl http://localhost:8042/studies/6b9e19d9-62094390-5f9ddb01-4a191ae7-9766b715/media > Study.zip |
380 | 434 |
218 | 435 |
436 .. _peering: | |
437 | |
216 | 438 Sending resources to remote Orthanc over HTTP/HTTPS (through Orthanc peering) |
224
02399e86f046
starting documentation of jobs
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
223
diff
changeset
|
439 ----------------------------------------------------------------------------- |
216 | 440 |
428
943515b68158
documented transcoding
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
411
diff
changeset
|
441 Orthanc can send its DICOM instances to remote Orthanc servers over |
943515b68158
documented transcoding
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
411
diff
changeset
|
442 HTTP/HTTPS. Such servers are referred to as :ref:`Orthanc peers |
943515b68158
documented transcoding
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
411
diff
changeset
|
443 <peers>`. This process can be triggered by the REST API, which is |
943515b68158
documented transcoding
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
411
diff
changeset
|
444 described in this section. |
216 | 445 |
446 Configuration | |
447 ^^^^^^^^^^^^^ | |
448 | |
449 .. highlight:: json | |
450 | |
314
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
451 You first have to declare the Url of the remote orthanc inside the |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
452 :ref:`configuration file <configuration>`. For instance, here is how |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
453 to declare a remote orthanc peer:: |
216 | 454 |
455 ... | |
494 | 456 "OrthancPeers" : { |
216 | 457 "sample" : [ "http://localhost:8043" ], // short version |
458 "sample2" : { // long version | |
459 "Url" : "http://localhost:8044", | |
460 "Username" : "alice", // optional | |
461 "Password" : "alicePassword", // optional | |
462 "HttpHeaders" : { "Token" : "Hello world" }, // optional | |
463 "CertificateFile" : "client.crt", // optional (only if using client certificate authentication) | |
464 "CertificateKeyFile" : "client.key", // optional (only if using client certificate authentication) | |
465 "CertificateKeyPassword" : "certpass" // optional (only if using client certificate authentication) | |
466 }, | |
467 ... | |
468 | |
469 .. highlight:: bash | |
470 | |
471 Such a configuration would enable Orthanc to connect to two other | |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
472 Orthanc instances that listens on the localhost on the ports 8043 |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
473 and 8044. The peers that are known to Orthanc can be queried:: |
216 | 474 |
475 $ curl http://localhost:8042/peers?expand | |
476 | |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
477 Instead of using the configuration file, peers can be created or |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
478 updated through the REST API using the ``PUT`` method of HTTP:: |
216 | 479 |
480 $ curl -v -X PUT http://localhost:8042/peers/sample -d '{"Url" : "http://127.0.0.1:8043"}' | |
481 | |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
482 One peer can also be removed using the ``DELETE`` method as follows:: |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
483 |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
484 $ curl -v -X DELETE http://localhost:8042/peers/sample |
216 | 485 |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
486 Note that, by default, peers are read from the Orthanc configuration |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
487 files and are updated in Orthanc memory only. If you want your |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
488 modifications to be persistent, you should configure Orthanc to store |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
489 its peers in the database. This is done through this configuration:: |
0 | 490 |
216 | 491 ... |
492 "OrthancPeersInDatabase" : true, | |
493 ... | |
494 | |
495 Sending One Resource | |
496 ^^^^^^^^^^^^^^^^^^^^ | |
497 | |
498 .. highlight:: bash | |
499 | |
500 Once you have identified the Orthanc identifier of the DICOM resource | |
501 that would like to send :ref:`as explained above <rest-access>`, you | |
502 would use the following command to send it:: | |
503 | |
504 $ curl -X POST http://localhost:8042/peers/sample/store -d c4ec7f68-9b162055-2c8c5888-5bf5752f-155ab19f | |
505 | |
506 The ``/sample/`` component of the URI corresponds to the identifier of | |
507 the remote modality, as specified above in the configuration file. | |
508 | |
509 Note that you can send isolated DICOM instances with this command, but | |
510 also entire patients, studies or series. It is possible to send multiple instances with a single POST | |
511 request:: | |
512 | |
513 $ curl -X POST http://localhost:8042/peers/sample/store -d '["d4b46c8e-74b16992-b0f5ca11-f04a60fa-8eb13a88","d5604121-7d613ce6-c315a5-a77b3cf3-9c253b23","cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e"]' | |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
514 |
216 | 515 Note that the list of resources to be sent can include the |
516 :ref:`Orthanc identifiers <orthanc-ids>` of entire patients, | |
517 studies or series as well. | |
518 | |
633
06bea33cb7d0
metadata and attachments are not transferred between peers
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
609
diff
changeset
|
519 **Important remark:** Neither the :ref:`metadata <metadata>`, nor the |
06bea33cb7d0
metadata and attachments are not transferred between peers
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
609
diff
changeset
|
520 :ref:`attachments <attachments>` are transferred between the Orthanc |
06bea33cb7d0
metadata and attachments are not transferred between peers
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
609
diff
changeset
|
521 peers. This is because metadata and attachments are considered as |
06bea33cb7d0
metadata and attachments are not transferred between peers
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
609
diff
changeset
|
522 local to one Orthanc server. |
06bea33cb7d0
metadata and attachments are not transferred between peers
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
609
diff
changeset
|
523 |
06bea33cb7d0
metadata and attachments are not transferred between peers
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
609
diff
changeset
|
524 |
294 | 525 Testing connectivity with a remote peer |
526 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
527 | |
528 .. highlight:: bash | |
529 | |
530 In version 1.5.9+, we have introduced a route to retrieve the ``/system`` info from | |
531 a remote peer. This route can also be used to test the connectivity with that peer | |
532 without actually sending a DICOM resource.:: | |
533 | |
534 $ curl http://localhost:8042/peers/sample/system | |
535 | |
536 | |
216 | 537 Using HTTPS |
538 ^^^^^^^^^^^ | |
539 | |
609
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
540 If you're transfering medical data over internet, it is mandatory to |
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
541 use HTTPS. |
216 | 542 |
609
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
543 On the server side, we recommend to put Orthanc behind an :ref:`HTTPS |
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
544 server that will take care of the TLS <https>`. |
216 | 545 |
609
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
546 On the client side, in order for the client Orthanc to recognize the |
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
547 server certificate, you'll have to provide a path to the CA |
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
548 (certification authority) certificates. This is done in the |
0dde82745e0d
documentation of DICOM TLS
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
577
diff
changeset
|
549 configuration file through this configurationg:: |
216 | 550 |
551 ... | |
552 "HttpsCACertificates" : "/etc/ssl/certs/ca-certificates.crt, | |
553 ... | |
554 | |
223 | 555 If you want your server to accept incoming connections for known hosts only, you can either: |
216 | 556 |
557 - configure a firewall to accept incoming connections from known IP addresses | |
558 - configure your client Orthanc to use a client certificate to authenticate at the Server. This is done through the ``CertificateFile``, ``CertificateKeyFile`` and ``CertificateKeyPassword`` entries in the configuration file. | |
559 | |
560 | |
561 | |
562 | |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
563 Sending resources to remote modalities (through DICOM C-Store) |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
564 -------------------------------------------------------------- |
0 | 565 |
566 Orthanc can send its DICOM instances to remote DICOM modalities (C-Store SCU). This process | |
567 can be triggered by the REST API. | |
568 | |
569 Configuration | |
570 ^^^^^^^^^^^^^ | |
571 | |
572 .. highlight:: json | |
573 | |
574 You first have to declare the AET, the IP address and the port number | |
575 of the remote modality inside the :ref:`configuration file | |
576 <configuration>`. For instance, here is how to declare a remote | |
577 modality:: | |
578 | |
579 ... | |
580 "DicomModalities" : { | |
212 | 581 "sample" : [ "ORTHANCA", "127.0.0.1", 2000 ], // short version |
582 "sample2" : { // long version | |
583 "AET" : "ORTHANCB", | |
584 "Port" : 2001, | |
585 "Host" : "127.0.0.1", | |
586 "Manufacturer" : "Generic", | |
587 "AllowEcho" : true, | |
588 "AllowFind" : true, | |
589 "AllowMove" : true, | |
590 "AllowStore" : true | |
591 } | |
0 | 592 }, |
593 ... | |
594 | |
595 .. highlight:: bash | |
596 | |
212 | 597 Such a configuration would enable Orthanc to connect to two DICOM |
598 stores (for instance, other Orthanc instances) that listens on the | |
599 localhost on the port 2000 & 2001. The modalities that are known to Orthanc | |
0 | 600 can be queried:: |
601 | |
212 | 602 $ curl http://localhost:8042/modalities?expand |
603 | |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
604 Instead of using the configuration file, modalities can be created or |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
605 updated through the REST API using the ``PUT`` method of HTTP:: |
212 | 606 |
607 $ curl -v -X PUT http://localhost:8042/modalities/sample -d '{"AET" : "ORTHANCC", "Host": "127.0.0.1", "Port": 2002}' | |
608 | |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
609 One modality can also be removed using the ``DELETE`` method as follows:: |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
610 |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
611 $ curl -v -X DELETE http://localhost:8042/modalities/sample |
0 | 612 |
667
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
613 Note that, by default, modalities are read from the Orthanc |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
614 configuration files and are updated in Orthanc memory only. If you |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
615 want your modifications to be persistent, you should configure Orthanc |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
616 to store the modalities in the database. This is done through this |
be71b56c90ab
example to delete peer/modality using rest
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
662
diff
changeset
|
617 configuration:: |
212 | 618 |
619 ... | |
620 "DicomModalitiesInDatabase" : true, | |
621 ... | |
0 | 622 |
331
48673b8abae3
documentation of storage commitment scu
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
314
diff
changeset
|
623 |
48673b8abae3
documentation of storage commitment scu
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
314
diff
changeset
|
624 .. _rest-store-scu: |
48673b8abae3
documentation of storage commitment scu
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
314
diff
changeset
|
625 |
0 | 626 Sending One Resource |
627 ^^^^^^^^^^^^^^^^^^^^ | |
628 | |
629 .. highlight:: bash | |
630 | |
631 Once you have identified the Orthanc identifier of the DICOM resource | |
632 that would like to send :ref:`as explained above <rest-access>`, you | |
633 would use the following command to send it:: | |
634 | |
635 $ curl -X POST http://localhost:8042/modalities/sample/store -d c4ec7f68-9b162055-2c8c5888-5bf5752f-155ab19f | |
636 | |
637 The ``/sample/`` component of the URI corresponds to the identifier of | |
638 the remote modality, as specified above in the configuration file. | |
639 | |
173
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
640 Note that you can send isolated DICOM instances with this command, but |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
641 also entire patients, studies or series. |
0 | 642 |
407 | 643 Various optional fields are also available. i.e, if you need to |
644 monitor the state of a transfer, you can start the transfer in :ref:`asynchronous mode | |
645 <jobs>`, which will provide you with the identifier of the Orthanc job:: | |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
646 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
647 $ curl -X POST http://localhost:8042/modalities/sample/store \ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
648 --data '{ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
649 "Resources" : ["d4b46c8e-74b16992-b0f5ca11-f04a60fa-8eb13a88"], |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
650 "Synchronous" : false, |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
651 "LocalAet" : "ORTHANC", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
652 "MoveOriginatorAet": "ORTHANC", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
653 "MoveOriginatorID": 1234, |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
654 "Timeout": 10, |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
655 "StorageCommitment": false |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
656 }' |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
657 |
403 | 658 |
0 | 659 Bulk Store SCU |
660 ^^^^^^^^^^^^^^ | |
661 | |
662 .. highlight:: bash | |
663 | |
664 Each time a POST request is made to ``/modalities/.../store``, a new | |
173
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
665 DICOM association is possibly established. This may lead to a large |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
666 communication overhead if sending multiple isolated instances by |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
667 making one REST call for each of these instances. |
0 | 668 |
669 To circumvent this problem, you have 2 possibilities: | |
670 | |
671 1. Set the ``DicomAssociationCloseDelay`` option in the | |
672 :ref:`configuration file <configuration>` to a non-zero value. This | |
673 will keep the DICOM connection open for a certain amount of time, | |
173
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
674 waiting for new instances to be routed. This is useful if |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
675 autorouting images :ref:`using Lua <lua-auto-routing>`. |
0 | 676 |
173
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
677 2. It is possible to send multiple instances with a single POST |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
678 request (so-called "Bulk Store SCU", available from Orthanc |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
679 0.5.2):: |
0 | 680 |
681 $ curl -X POST http://localhost:8042/modalities/sample/store -d '["d4b46c8e-74b16992-b0f5ca11-f04a60fa-8eb13a88","d5604121-7d613ce6-c315a5-a77b3cf3-9c253b23","cb855110-5f4da420-ec9dc9cb-2af6a9bb-dcbd180e"]' | |
682 | |
683 The list of the resources to be sent are given as a JSON array. In | |
684 this case, a single DICOM connection is used. `Sample code is | |
685 available | |
449 | 686 <https://hg.orthanc-server.com/orthanc/file/default/OrthancServer/Resources/Samples/Python/HighPerformanceAutoRouting.py>`__. |
0 | 687 |
173
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
688 Note that the list of resources to be sent can include the |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
689 :ref:`Orthanc identifiers <orthanc-ids>` of entire patients, |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
690 studies or series as well. |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
691 |
901bc7b2dbab
improved bulk store scu section
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
169
diff
changeset
|
692 |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
693 Performing C-Echo |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
694 ----------------- |
0 | 695 |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
696 To validate the DICOM connectivity between Orthanc and a remote modality, |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
697 you can perform a C-ECHO:: |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
698 |
557
3af5dda67520
fix sample for c-echo in rest api
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
494
diff
changeset
|
699 $ curl -X POST http://localhost:8042/modalities/sample/echo -d '{}' |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
700 |
557
3af5dda67520
fix sample for c-echo in rest api
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
494
diff
changeset
|
701 From Orthanc 1.7.0, you can include an extra ``Timeout`` field:: |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
702 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
703 $ curl -X POST http://localhost:8042/modalities/sample/echo -d '{ "Timeout": 10 }' |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
704 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
705 If no ``Timeout`` parameter is specified, the value of the ``DicomScuTimeout`` |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
706 configuration is used as a default. If ``Timeout`` is set to zero, this means |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
707 no timeout. |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
708 |
557
3af5dda67520
fix sample for c-echo in rest api
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
494
diff
changeset
|
709 NB: A body containing a valid JSON object is needed by |
3af5dda67520
fix sample for c-echo in rest api
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
494
diff
changeset
|
710 ``/modalities/{id}/echo`` since Orthanc 1.7.0. |
3af5dda67520
fix sample for c-echo in rest api
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
494
diff
changeset
|
711 |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
712 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
713 Performing C-Move |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
714 ----------------- |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
715 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
716 .. highlight:: bash |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
717 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
718 You can perform a DICOM C-Move to move a specific study from one modality |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
719 to another (including Orthanc itself if you don't specify the ``TargetAet`` |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
720 field). |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
721 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
722 I.e. to move a study whose you know the ``StudyInstanceUID`` from |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
723 the modality ``sample`` to another Orthanc whose AET is ``ORTHANCB``:: |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
724 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
725 $ curl --request POST --url http://localhost:8042/modalities/samples/move \ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
726 --data '{ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
727 "Level" : "Study", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
728 "Resources" : [ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
729 { |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
730 "StudyInstanceUID": "1.2.840.113543.6.6.4.7.64067529866380271256212683512383713111129" |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
731 } |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
732 ], |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
733 "TargetAet": "ORTHANCB", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
734 "Timeout": 60 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
735 }' |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
736 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
737 |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
738 Performing Query/Retrieve (C-Find) and Find with REST |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
739 ----------------------------------------------------- |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
740 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
741 *Section contributed by Bryan Dearlove* |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
742 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
743 Orthanc can be used to perform queries on the local Orthanc instance, |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
744 or on remote modalities through the REST API. |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
745 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
746 To perform a query of a remote modality you must define the modality |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
747 within the :ref:`configuration file <configuration>` (See |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
748 Configuration section under Sending resources to remote modalities). |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
749 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
750 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
751 Performing Queries on Modalities |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
752 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
753 |
138 | 754 .. highlight:: bash |
755 | |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
756 To initiate a query you perform a POST command against the Modality |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
757 with the identifiers you are looking for. The the example below we are |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
758 performing a study level query against the modality sample for any |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
759 study descriptions with the word chest within it. This search is case |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
760 insensitive unless configured otherwise within the Orthanc |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
761 configuration file:: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
762 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
763 $ curl --request POST \ |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
764 --url http://localhost:8042/modalities/sample/query \ |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
765 --data '{ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
766 "Level" : "Study", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
767 "Query" : { |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
768 "PatientID" : "", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
769 "StudyDescription" : "*Chest*", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
770 "PatientName" : "" |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
771 } |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
772 }' |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
773 |
314
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
774 You might be interested in including the ``Normalize`` option to bypass |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
775 the normalization of the outgoing C-FIND queries. For instance, for |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
776 the ``InstitutionName`` to be included at the ``Study`` level, one would |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
777 run:: |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
778 |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
779 $ curl -v http://localhost:8042/modalities/sample/query -X POST -d \ |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
780 '{"Level":"Study","Query":{"InstitutionName":"a"},"Normalize":false}' |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
781 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
782 .. highlight:: json |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
783 |
138 | 784 You will receive back an ID which can be used to retrieve more |
785 information with GET commands or C-Move requests with a POST Command:: | |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
786 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
787 { |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
788 "ID": "5af318ac-78fb-47ff-b0b0-0df18b0588e0", |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
789 "Path": "/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0" |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
790 } |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
791 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
792 |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
793 Additional Options |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
794 ^^^^^^^^^^^^^^^^^^ |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
795 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
796 .. highlight:: json |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
797 |
314
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
798 You can use patient identifiers by including the ``*`` within your |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
799 search. For example if you were searching for a name beginning with |
314
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
800 ``Jones`` you can do:: |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
801 |
139 | 802 "PatientName":"Jones*" |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
803 |
314
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
804 If you wanted to search for a name with the words ``Jo`` anywhere |
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
805 within it you can do:: |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
806 |
139 | 807 "PatientName":"*Jo*" |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
808 |
138 | 809 To perform date searches you can specify within StudyDate a starting |
810 date and/or a before date. For example ``"StudyDate":"20180323-"`` | |
811 would search for all study dates after the specified date to | |
812 now. Doing ``"StudyDate":"20180323-20180325"`` would search for all | |
813 study dates between the specified date. | |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
814 |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
815 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
816 Reviewing Level |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
817 ^^^^^^^^^^^^^^^ |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
818 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
819 .. highlight:: bash |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
820 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
821 :: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
822 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
823 $ curl --request GET --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/level |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
824 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
825 Will retrieve the level with which the query was performed, Study, |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
826 Series or Instance. |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
827 |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
828 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
829 Reviewing Modality |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
830 ^^^^^^^^^^^^^^^^^^ |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
831 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
832 .. highlight:: bash |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
833 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
834 :: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
835 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
836 $ curl --request GET --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/modality |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
837 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
838 Will provide the modality name which the original query was performed against. |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
839 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
840 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
841 Reviewing Query |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
842 ^^^^^^^^^^^^^^^ |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
843 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
844 .. highlight:: bash |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
845 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
846 To retrieve information on what identifiers the query was originally |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
847 performed using you can use the query filter:: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
848 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
849 $ curl --request GET --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/query |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
850 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
851 |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
852 Reviewing Query Answers |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
853 ^^^^^^^^^^^^^^^^^^^^^^^ |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
854 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
855 .. highlight:: bash |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
856 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
857 You are able to individually review each answer returned by performing |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
858 a GET with the answers parameter:: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
859 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
860 $ curl --request GET --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/answers |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
861 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
862 You will get a JSON back with numbered identifiers for each answer you |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
863 received back. For example because we performed a Study level query we |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
864 received back 5 studies answers back. We are able to query each answer |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
865 for content details:: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
866 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
867 $ curl --request GET --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/answers/0/content |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
868 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
869 If there are content items missing, you may add them by adding that |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
870 identifier to the original query. For example if we wanted Modalities |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
871 listed in this JSON answer in the initial query we would add to the |
314
5f0cd51d97c0
Normalize option in /modalities/.../query
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
313
diff
changeset
|
872 POST body: ``"ModalitiesInStudy":""`` |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
873 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
874 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
875 Performing Retrieve (C-Move) |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
876 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
877 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
878 .. highlight:: bash |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
879 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
880 You can perform a C-Move to retrieve all studies within the original |
205
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
881 query using a post command and identifying the Modality (named in this |
207 | 882 example ``Orthanc``), to be one to in the POST contents:: |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
883 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
884 $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/retrieve --data Orthanc |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
885 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
886 You are also able to perform individual C-Moves for a content item by |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
887 specifying that individual content item:: |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
888 |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
889 $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/answers/0/retrieve --data Orthanc |
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
890 |
207 | 891 If C-Moves take too long (for example, performing a C-Move of a big |
671
bc8fa2bf4cf7
asynchronous c-move
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
667
diff
changeset
|
892 study), you may run the request in :ref:`asynchronous mode <jobs>`, |
bc8fa2bf4cf7
asynchronous c-move
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
667
diff
changeset
|
893 which will create a job in Orthanc:: |
205
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
894 |
207 | 895 $ curl --request POST --url http://localhost:8042/queries/5af318ac-78fb-47ff-b0b0-0df18b0588e0/retrieve \ |
896 --data '{"TargetAet":"Orthanc","Synchronous":false}' | |
897 | |
205
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
898 |
207 | 899 .. highlight:: bash |
900 | |
671
bc8fa2bf4cf7
asynchronous c-move
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
667
diff
changeset
|
901 The answer of this POST request is the job ID taking care of the |
bc8fa2bf4cf7
asynchronous c-move
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
667
diff
changeset
|
902 C-Move command, :ref:`whose status can be monitored <jobs-monitoring>` |
bc8fa2bf4cf7
asynchronous c-move
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
667
diff
changeset
|
903 in order to detect failure or completion:: |
205
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
904 |
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
905 { |
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
906 "ID" : "11541b16-e368-41cf-a8e9-3acf4061d238", |
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
907 "Path" : "/jobs/11541b16-e368-41cf-a8e9-3acf4061d238" |
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
908 } |
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
909 |
7213bef30604
rest.rst edited online with Bitbucket.
Diego Fernández Slezak <dfslezak@gmail.com>
parents:
173
diff
changeset
|
910 |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
911 |
378
16dc3561b41e
Filtering and returning metadata using Python
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
912 .. _rest-find: |
16dc3561b41e
Filtering and returning metadata using Python
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
360
diff
changeset
|
913 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
914 Performing Finds within Orthanc |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
915 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
916 .. highlight:: bash |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
917 |
662
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
918 Performing a find within the local database of Orthanc is very similar |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
919 to using Queries against DICOM modalities and the additional options |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
920 listed above work with find also. When performing a find, you will |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
921 receive the Orthanc ID's of all the matched items within your |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
922 find. For example if you perform a study level find and 5 Studies |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
923 match you will receive 5 study level Orthanc ID's in JSON format as a |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
924 response:: |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
925 |
404
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
926 $ curl --request POST --url http://localhost:8042/tools/find \ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
927 --data '{ |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
928 "Level" : "Instance", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
929 "Query" : { |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
930 "Modality" : "CR", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
931 "StudyDate" : "20180323-", |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
932 "PatientID" : "*" |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
933 } |
7469b6c5618b
DICOM commands: Timeout + improved existing doc
Alain Mazy <alain@mazy.be>
parents:
381
diff
changeset
|
934 }' |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
935 |
312
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
936 Setting the ``Expand`` field to ``true`` in the POST body of the |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
937 query will automatically report details about each study:: |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
938 |
313 | 939 $ curl https://demo.orthanc-server.com/tools/find -d '{"Level":"Study","Query":{"PatientName":"KNIX"}}' |
940 [ | |
941 "b9c08539-26f93bde-c81ab0d7-bffaf2cb-a4d0bdd0" | |
942 ] | |
312
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
943 $ curl https://demo.orthanc-server.com/tools/find -d '{"Level":"Study","Query":{"PatientName":"KNIX"},"Expand":true}' |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
944 [ |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
945 { |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
946 "ID" : "b9c08539-26f93bde-c81ab0d7-bffaf2cb-a4d0bdd0", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
947 "IsStable" : true, |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
948 "LastUpdate" : "20180414T091528", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
949 "MainDicomTags" : { |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
950 "InstitutionName" : "0ECJ52puWpVIjTuhnBA0um", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
951 "ReferringPhysicianName" : "1", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
952 "StudyDate" : "20070101", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
953 "StudyDescription" : "Knee (R)", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
954 "StudyID" : "1", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
955 "StudyInstanceUID" : "1.2.840.113619.2.176.2025.1499492.7391.1171285944.390", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
956 "StudyTime" : "120000.000000" |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
957 }, |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
958 "ParentPatient" : "6816cb19-844d5aee-85245eba-28e841e6-2414fae2", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
959 "PatientMainDicomTags" : { |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
960 "PatientID" : "ozp00SjY2xG", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
961 "PatientName" : "KNIX" |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
962 }, |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
963 "Series" : [ |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
964 "20b9d0c2-97d85e07-f4dbf4d2-f09e7e6a-0c19062e", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
965 "edbfa0a9-fa2641d7-29514b1c-45881d0b-46c374bd", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
966 "f2635388-f01d497a-15f7c06b-ad7dba06-c4c599fe", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
967 "4d04593b-953ced51-87e93f11-ae4cf03c-25defdcd", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
968 "5e343c3e-3633c396-03aefde8-ba0e08c7-9c8208d3", |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
969 "8ea120d7-5057d919-837dfbcc-ccd04e0f-7f3a94aa" |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
970 ], |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
971 "Type" : "Study" |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
972 } |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
973 ] |
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
974 |
662
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
975 Here is a sample REST API call to find the Orthanc identifiers of all |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
976 the DICOM series generated by an imaging modality whose "Device Serial |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
977 Number (0018,1000)" DICOM tag is equal to "123":: |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
978 |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
979 $ curl -X POST http://localhost:8042/tools/find -d '{"Level":"Series","Query":{"DeviceSerialNumber":"123"},"Expand":true}' |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
980 |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
981 If you are interested by a **list of several items** (in this case, in |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
982 a list of serial numbers), just separate them with backslashes as |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
983 would do with DICOM C-FIND:: |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
984 |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
985 $ curl -X POST http://localhost:8042/tools/find -d '{"Level":"Series","Query":{"DeviceSerialNumber":"123\\abc"},"Expand":true}' |
88503c6e549f
list of items in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
633
diff
changeset
|
986 |
312
b19b892977a2
expand in /tools/find
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
297
diff
changeset
|
987 |
138 | 988 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
989 Additional Options |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
990 ^^^^^^^^^^^^^^^^^^ |
138 | 991 .. highlight:: json |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
992 |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
993 You also have the ability to limit the responses by specifying a limit within the body of the POST message. For example:: |
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
994 |
138 | 995 "Limit":4 |
136
8e08909ab69b
Added find information to: Performing Query/Retrieve and Find with REST
Bryan Dearlove <bdearlove@gmail.com>
parents:
132
diff
changeset
|
996 |
132
55a2ee3c462d
Performing Query/Retrieve with REST
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
114
diff
changeset
|
997 |
216 | 998 .. _changes: |
999 | |
0 | 1000 Tracking changes |
1001 ---------------- | |
1002 | |
1003 .. highlight:: bash | |
1004 | |
1005 Whenever Orthanc receives a new DICOM instance, this event is recorded | |
1006 in the so-called "Changes Log". This enables remote scripts to react | |
1007 to the arrival of new DICOM resources. A typical application is | |
1008 **auto-routing**, where an external script waits for a new DICOM | |
1009 instance to arrive into Orthanc, then forward this instance to another | |
1010 modality. | |
1011 | |
1012 The Changes Log can be accessed by the following command:: | |
1013 | |
1014 $ curl http://localhost:8042/changes | |
1015 | |
1016 .. highlight:: json | |
1017 | |
1018 Here is a typical output:: | |
1019 | |
1020 { | |
1021 "Changes" : [ | |
1022 { | |
1023 "ChangeType" : "NewInstance", | |
1024 "Date" : "20130507T143902", | |
1025 "ID" : "8e289db9-0e1437e1-3ecf395f-d8aae463-f4bb49fe", | |
1026 "Path" : "/instances/8e289db9-0e1437e1-3ecf395f-d8aae463-f4bb49fe", | |
1027 "ResourceType" : "Instance", | |
1028 "Seq" : 921 | |
1029 }, | |
1030 { | |
1031 "ChangeType" : "NewSeries", | |
1032 "Date" : "20130507T143902", | |
1033 "ID" : "cceb768f-e0f8df71-511b0277-07e55743-9ef8890d", | |
1034 "Path" : "/series/cceb768f-e0f8df71-511b0277-07e55743-9ef8890d", | |
1035 "ResourceType" : "Series", | |
1036 "Seq" : 922 | |
1037 }, | |
1038 { | |
1039 "ChangeType" : "NewStudy", | |
1040 "Date" : "20130507T143902", | |
1041 "ID" : "c4ec7f68-9b162055-2c8c5888-5bf5752f-155ab19f", | |
1042 "Path" : "/studies/c4ec7f68-9b162055-2c8c5888-5bf5752f-155ab19f", | |
1043 "ResourceType" : "Study", | |
1044 "Seq" : 923 | |
1045 }, | |
1046 { | |
1047 "ChangeType" : "NewPatient", | |
1048 "Date" : "20130507T143902", | |
1049 "ID" : "dc65762c-f476e8b9-898834f4-2f8a5014-2599bc94", | |
1050 "Path" : "/patients/dc65762c-f476e8b9-898834f4-2f8a5014-2599bc94", | |
1051 "ResourceType" : "Patient", | |
1052 "Seq" : 924 | |
1053 } | |
1054 ], | |
1055 "Done" : true, | |
1056 "Last" : 924 | |
1057 } | |
1058 | |
1059 This output corresponds to the receiving of one single DICOM instance | |
1060 by Orthanc. It records that a new instance, a new series, a new study | |
1061 and a new patient has been created inside Orthanc. Note that each | |
1062 changes is labeled by a ``ChangeType``, a ``Date`` (in the `ISO format | |
25 | 1063 <https://en.wikipedia.org/wiki/ISO_8601>`__), the location of the |
0 | 1064 resource inside Orthanc, and a sequence number (``Seq``). |
1065 | |
1066 Note that this call is non-blocking. It is up to the calling program | |
1067 to wait for the occurrence of a new event (by implementing a polling | |
1068 loop). | |
1069 | |
1070 .. highlight:: bash | |
1071 | |
1072 This call only returns a fixed number of events, that can be changed | |
1073 by using the ``limit`` option:: | |
1074 | |
1075 $ curl http://localhost:8042/changes?limit=100 | |
1076 | |
1077 The flag ``Last`` records the sequence number of the lastly returned | |
1078 event. The flag ``Done`` is set to ``true`` if no further event has | |
1079 occurred after this lastly returned event. If ``Done`` is set to | |
1080 ``false``, further events are available and can be retrieved. This is | |
1081 done by setting the ``since`` option that specifies from which | |
1082 sequence number the changes must be returned:: | |
1083 | |
1084 $ curl 'http://localhost:8042/changes?limit=100&since=922' | |
1085 | |
1086 A `sample code in the source distribution | |
449 | 1087 <https://hg.orthanc-server.com/orthanc/file/default/OrthancServer/Resources/Samples/Python/ChangesLoop.py>`__ |
0 | 1088 shows how to use this Changes API to implement a polling loop. |
1089 | |
1090 | |
1091 Deleting resources from Orthanc | |
1092 ------------------------------- | |
1093 | |
1094 .. highlight:: bash | |
1095 | |
1096 Deleting patients, studies, series or instances | |
1097 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | |
1098 | |
1099 Deleting DICOM resources (i.e. patients, studies, series or instances) | |
1100 from Orthanc is as simple as using a HTTP DELETE on the URI of this | |
1101 resource. | |
1102 | |
1103 Concretely, you would first explore the resources that are stored in | |
1104 Orthanc :ref:`as explained above <rest-access>`:: | |
1105 | |
1106 $ curl http://localhost:8042/patients | |
1107 $ curl http://localhost:8042/studies | |
1108 $ curl http://localhost:8042/series | |
1109 $ curl http://localhost:8042/instances | |
1110 | |
1111 Secondly, once you have spotted the resources to be removed, you would | |
1112 use the following command-line syntax to delete them:: | |
1113 | |
1114 $ curl -X DELETE http://localhost:8042/patients/dc65762c-f476e8b9-898834f4-2f8a5014-2599bc94 | |
1115 $ curl -X DELETE http://localhost:8042/studies/c4ec7f68-9b162055-2c8c5888-5bf5752f-155ab19f | |
1116 $ curl -X DELETE http://localhost:8042/series/cceb768f-e0f8df71-511b0277-07e55743-9ef8890d | |
1117 $ curl -X DELETE http://localhost:8042/instances/8e289db9-0e1437e1-3ecf395f-d8aae463-f4bb49fe | |
1118 | |
1119 | |
1120 Clearing log of changes | |
1121 ^^^^^^^^^^^^^^^^^^^^^^^ | |
1122 | |
1123 :ref:`As described above <changes>`, Orthanc keeps track of all the | |
1124 changes that occur in the DICOM store. This so-called "Changes Log" | |
1125 is accessible at the following URI:: | |
1126 | |
1127 $ curl http://localhost:8042/changes | |
1128 | |
1129 To clear the content of the Changes Log, simply DELETE this URI:: | |
1130 | |
1131 $ curl -X DELETE http://localhost:8042/changes | |
1132 | |
1133 | |
155 | 1134 Log of exported resources |
1135 ^^^^^^^^^^^^^^^^^^^^^^^^^ | |
1136 | |
1137 For medical traceability, Orthanc can be configured to store a log of | |
1138 all the resources that have been exported to remote modalities:: | |
0 | 1139 |
1140 $ curl http://localhost:8042/exports | |
1141 | |
1142 In auto-routing scenarios, it is important to prevent this log to grow | |
1143 indefinitely as incoming instances are routed. You can either disable | |
1144 this logging by setting the option ``LogExportedResources`` to ``false`` | |
1145 in the :ref:`configuration file <configuration>`, or periodically | |
1146 clear this log by DELETE-ing this URI:: | |
1147 | |
1148 $ curl -X DELETE http://localhost:8042/exports | |
1149 | |
155 | 1150 NB: Starting with Orthanc 1.4.0, the ``LogExportedResources`` is set |
1151 to ``false`` by default. If the logging is desired, set this option to | |
1152 ``true``. | |
1153 | |
0 | 1154 |
1155 Anonymization and modification | |
1156 ------------------------------ | |
1157 | |
1158 The process of anonymizing and modifying DICOM resources is | |
1159 :ref:`documented in a separate page <anonymization>`. | |
1160 | |
1161 | |
1162 Further reading | |
1163 --------------- | |
1164 | |
1165 The examples above have shown you the basic principles for driving an | |
1166 instance of Orthanc through its REST API. All the possibilities of the | |
35
5737f51ff94e
How does Orthanc stores its database
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
25
diff
changeset
|
1167 API have not been described: |
5737f51ff94e
How does Orthanc stores its database
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
25
diff
changeset
|
1168 |
224
02399e86f046
starting documentation of jobs
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
223
diff
changeset
|
1169 * Advanced features of the REST API can be found on :ref:`another page |
02399e86f046
starting documentation of jobs
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
223
diff
changeset
|
1170 <rest-advanced>`. |
35
5737f51ff94e
How does Orthanc stores its database
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
25
diff
changeset
|
1171 * A :ref:`FAQ entry <rest-samples>` lists where you can find more |
5737f51ff94e
How does Orthanc stores its database
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
25
diff
changeset
|
1172 advanced samples of the REST API of Orthanc. |
577
7d27154e70f9
cheatsheet and full openapi
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
557
diff
changeset
|
1173 * A :ref:`short reference of the REST API of Orthanc <cheatsheet>` is |
7d27154e70f9
cheatsheet and full openapi
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
557
diff
changeset
|
1174 part of the Orthanc Book. |
7d27154e70f9
cheatsheet and full openapi
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
557
diff
changeset
|
1175 * The full documentation of the REST API in the OpenAPI/Swagger format |
7d27154e70f9
cheatsheet and full openapi
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
557
diff
changeset
|
1176 is `available online <https://api.orthanc-server.com/>`__. This |
7d27154e70f9
cheatsheet and full openapi
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
557
diff
changeset
|
1177 reference is automatically generated from the source code of |
7d27154e70f9
cheatsheet and full openapi
Sebastien Jodogne <s.jodogne@gmail.com>
parents:
557
diff
changeset
|
1178 Orthanc. |