Sup 219 JSON SR

[darcymason]

Posted by David Clunie on the comp.protocols.dicom
(https://groups.google.com/d/msg/comp.protocols.dicom/4OyeLP-0QN0/3Q9oykUxAQAJ)

Last week DICOM WG 6 approved the release of Sup 219 as a Trial Use Draft:

ftp://medical.nema.org/medical/dicom/supps/Frozen/sup219_fz_JSONSR.pdf
ftp://medical.nema.org/medical/dicom/supps/Frozen/sup219_fz_JSONSR.xml

Posting an issue here as a placeholder -- something to keep an eye on at least -- related to both stuctured reports and JSON. If anyone wants to read through, please comment on if/how this might affect developments in pydicom.

[mrbean-bremen]

I had a quick look, and as far as I can see, this fits quite well into pydicom. The basic JSON encoding/decoding is already there, the only difference I have seen is the use of arrays to preserve the sort order - which makes sense, but currently is always handled as multi-valued entries.

The main work seems to be the keyword lookup. Standard DICOM keyword lookup and UID name lookup is already in pydicom, so adding this to the JSON code should be trivial. Adding the SR-specific lookup will be some work, and I'm not clear yet how to handle the business names JSON (e.g. where to get them), though I'm sure I just missed that.

[darcymason]

I'm not clear yet how to handle the business names JSON (e.g. where to get them)

There was a couple of links given in [this comment] (#824 (comment)) from #824 - I think I glanced at it at the time but don't remember now what is in those. I think there was another comment/source as well about importing the names but can't find it just now.

[darcymason]

Closing this issue, as I think it is well behind the pydicom developments now. New related issues could be opened of course.