UUID not present in WADO API searches

[GoogleCodeExporter]

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?

JSON response with ObjectID and also UUID for DICOM objects.

What version of the product are you using? On what operating system?

0.7.3

Please provide any additional information below.
From the REST API there seems to be a missing link getting the UUID from a WADO 
search. The JSON response is missing the UUID via the WADO calls.   I'm was 
able to launch 2 instances of Orthanc on port 4242 and port 2000 ; however to 
view the actual images with the explorer.js  script I need the UUID and not the 
ObjectID.

Can you provide me with some details that would allow me to perform a patient 
search via WADO and then locate the UUID to fetch the actual images.

Original issue reported on code.google.com by aashton2...@gmail.com on 13 Mar 2014 at 1:31

[GoogleCodeExporter]

Issue 12 has been merged into this issue.

Original comment by s.jodo...@gmail.com on 13 Mar 2014 at 2:07

[GoogleCodeExporter]

Hello,

If other people are reading this answer, please let me first put Antroy 
Ashton's question into perspective. The following FAQ entry indicates how to 
ease WADO querying thanks to Orthanc, from the patient level to the instance 
level:
https://code.google.com/p/orthanc/wiki/FAQ#Using_Orthanc_to_Ease_WADO_Querying

Here is a sample output of the last call to the "find-instance" URI:

>>>>>
[
   ...
   {
      ...
      "PatientID" : "0555643F",
      "QueryRetrieveLevel" : "INSTANCE",
      "SOPInstanceUID" : "1.3.46.670589.28.2.15.2200939417.3.13491.0.1239199522",
      "SeriesInstanceUID" : "1.3.46.670589.28.2.7.2200939417.2.13493.0.1239199523",
      "StudyInstanceUID" : "1.2.840.113704.1.111.2768.1239195678.57"
   }
]
<<<<<

If I correctly understand, the question is the following: How can I compute the 
"Orthanc UID" that Orthanc would associate to this instance, if it gets 
imported into Orthanc? The above output indeed only lists the "DICOM UIDs" 
information (PatientID/StudyInstanceUID/SeriesInstanceUID/SOPInstanceUID for, 
respectively, the patient/study/series/instance levels).

The way Orthanc associates an "Orthanc ID" to a set of "DICOM UIDs" is 
explained in this other FAQ entry:
https://code.google.com/p/orthanc/wiki/FAQ#Orthanc_Fails_to_Store_a_DICOM_File,_
Complaining_About_an_"

You will find attached to this comment a sample, independent Python script that 
automatically computes this association, provided the result of the REST calls. 
Sample calls are given at the top of the script.

Does this script solves your problem?

HTH,
Sébastien-

Original comment by s.jodo...@gmail.com on 24 Mar 2014 at 10:25

Attachments:

• DicomToOrthancUID.py

[GoogleCodeExporter]

Antroy has confirmed by mail that this answer indeed solves this problem.

Original comment by s.jodo...@gmail.com on 24 Mar 2014 at 8:04

• Changed state: Done