I’ve recently been reading about the hard to understand HTML and the ‘fine line’ there is to producing HTML output that all (enough?) web browsers understand. To all web developers I say quit you’re whining, try following the DICOM standard. Although I haven’t read enough standards to say that DICOM is the worst standard ever, I can say that it can be a tad confusing at times.
- The standard is long. The PDF version of HTML4 is nice and light at a single 389 page document, the 2008 DICOM standard has 18 parts, part 3 alone is 1097 pages. ( OK, this is a bit of comparing apples to oranges since DICOM covers communication protocols in addition to the syntax…)
- The standard is old. The ARC/NEMA standard dates back to the mid-eighties. There’s nothing wrong with this per say, but it does carry around a lot of baggage (like transfer protocols that so far as I can tell, no one uses anymore). Life would be so much easier if implicit little endian would just go away *sigh*.
- The standard is ambiguous. There’s lots that’s unclear or unspecified. What’s the correct window/level (brightness/contrast if you’re not familiar with DICOM). You’d better look outside the standard to figure it out.
- The standard is confusing. What’s the pixel spacing in an x-ray image? Try reading figuring out what this means.
- Major vendors don’t comply to the standard. It’s not enough to comply with the standard, like web browsers you’ve got to be bug compatible with common vendor formats. Unlike Web browsers, there’s not just a handful, there’s dozens of them, and you may not have their data. This is what David Clunie calls the “we know what the standard says but we are going to ignore it and do what we have been doing for almost a decade regardless” CR vendor bug.
That said, at least there is a standard. When I first started working a Merge (formerly Cedara Software) there was a SIF (Scanner InterFace) team who’s job it was to read the proprietary formats from older scanner and read them in. We still sell boxes that connect to old ultrasound machines to allow them to produce DICOM outputs. Despite being old, the standard is still extensible (though it’s going a little too far IMHO). Finally, DICOM also has a pretty good domain model for radiology. I don’t know what came first, the domain model or DICOM, but structuring your application around the DICOM model has worked very well for me.