Dicomizer - json structure for dataset.json file

Google Groups archive
1

I am trying to create DICOM images from WSI-tif files for upload into orthanc. Since the sample json-config file does not all items I would like to include in the DICOM file, I tried editing the sample_dataset.json file. Unfortunately, I cannot figure out the correct format - no matter what I do,
the parsing of the modified json file always fails.
Is there a place/document that explains how to add items to the default file (what are the allowed keywords and sequence structures)?
Thank you very much - Jack

2

Hello,

Is there a place/document that explains how to add items to the
default file (what are the allowed keywords and sequence structures)?

Good question, I don't think so actually.

If you can read C++, the parser is here[1] and more specifically
there[2]. If not then you should file a request on the issue tracker
for someone to synthesize its behavior.

You may also send your dataset, we might try to take a look at it
specifically to see what's wrong.

[1] https://bitbucket.org/sjodogne/orthanc-wsi/src/42dcf14389434478bd8e
4471e6fbe8770a966674/Applications/Dicomizer.cpp?at=default&fileviewer=f
ile-view-default#Dicomizer.cpp-203
[2] https://bitbucket.org/sjodogne/orthanc-wsi/src/42dcf14389434478bd8e
4471e6fbe8770a966674/Resources/Orthanc/OrthancServer/FromDcmtkBridge.cp
p?at=default&fileviewer=file-view-default#FromDcmtkBridge.cpp-1657

3

Dear Jack,

The “dataset.json” format to be used with the “–dataset” command-line argument is really simple: Just add all the tags you want to be included in the output DICOM files into the root associative JSON array. Check out the related documentation:
http://book.orthanc-server.com/plugins/wsi.html#specifying-a-dicom-dataset

A sample JSON file can found at the following location (it is the sample dataset that is generated by adding the “–sample-dataset” flag when invoking “OrthancWSIDicomizer”):
https://bitbucket.org/sjodogne/orthanc-wsi/src/default/Resources/SampleDataset.json

The tags can be specified either with their symbolic tag name, or with their hexadecimal identifier. For instance:

{
“PatientID” : “C123456789”,
“0010,0010” : “PATIENT^NAME”
}

Please share a buggy JSON dataset so as further help can be provided.

Regards,
Sébastien-

4

Sébastien, Thank you very much for you comments, in particular the possibility of using Byte-codes "0040, 0052", etc. That made things much easier. The original problem was caused by putting an element in the wrong sequence - my mistake.
Thank you very much,
Jack