Feature #943
Updated by Jörg Riesmeier about 5 years ago
Currently, adding (minimal) support for a new SOP Class to the DCMTK is quite cumbersome since - depending on the type of SOP Class - changes to various files are needed (see e.g. "this Howto":https://support.dcmtk.org/redmine/projects/dcmtk/wiki/Howto_AddSOPClass).
In order to facilitate the work of adding new SOP Classes and of maintaining the definitions, it would be helpful to have a central place where all SOP Classes (Storage and others) are defined with their UID, Name and Features (e.g. for Storage SOP Classes, a classification like Image, SR, Waveform, etc., Patient vs. Non-Patient and so on). The current API, e.g. dcmIsaStorageSOPClassUID() or dcmIsImageStorageSOPClassUID(), should probably stay for a while. Maybe, also other UIDs such as for Transfer Syntaxes or Well-known Frame of References, should be added to this new data structure.
It would probably also be useful to think about a new naming scheme for the modality-specific (SOP class) filename prefix defined as part of the DcmModalityTable structure, since it is becoming more and more difficult to find unused but still intuitive combinations of 2 or 3 three letters.