I am cursed with having to work with DICOM modalities and their view on how DICOM (the protocol) should work. It’s truly impressive how many different quirks and out-of-spec behaviors you encounter with different vendors…
Our DICOM-to-DicomWeb proxy must have the most special-case/lines-of-code ratio in the whole institute.
I remember when a developer at a previous job (dealing with DICOM images) discovered that little Bobby Tables could do his work in our product as well. It was an exciting and scary day. :-)
I remember the first time I got some DICOM files (my knees being shot it was an MRI or bone scan of them). The software that came on the DVD was terrible, and I was all “how complicated can this format be? It’s basically just a bitmap right?”. After a few hours trying to find correct format docs and discovering the myriad random extensions I took the “screw this” path :)
I am cursed with having to work with DICOM modalities and their view on how DICOM (the protocol) should work. It’s truly impressive how many different quirks and out-of-spec behaviors you encounter with different vendors…
Our DICOM-to-DicomWeb proxy must have the most special-case/lines-of-code ratio in the whole institute.
I remember when a developer at a previous job (dealing with DICOM images) discovered that little Bobby Tables could do his work in our product as well. It was an exciting and scary day. :-)
Oof, I’m sorry.
I remember the first time I got some DICOM files (my knees being shot it was an MRI or bone scan of them). The software that came on the DVD was terrible, and I was all “how complicated can this format be? It’s basically just a bitmap right?”. After a few hours trying to find correct format docs and discovering the myriad random extensions I took the “screw this” path :)
I guarantee you that software is still as bad as it was back then. :-) If you’re on macOS, OsiriX1 is one of the best viewers available.
Oh yeah I know, but I still don’t hate it enough to write my own viewer :)