Conformance #695
open
Check whether Non-Patient Object Storage SOP Classes should be treated differently
60%
Description
In the last couple of years, the DICOM standard introduced various "Non-Patient Object Storage SOP Classes", e.g. Generic Implant Template Storage, Implant Assembly Template Storage, Implant Template Group Storage and only recently CT Defined Procedure Protocol Storage (see PS 3.4 Annex GG). These SOP Classes are currently treated the same as the Standard Patient Objects Storage SOP Class (see Table B.5-1 in PS 3.4).
It should be checked whether this is correct or whether a difference should be made regarding the network storage and query/retrieve service (library and tools).
Updated by Jörg Riesmeier over 8 years ago
- Assignee set to Jörg Riesmeier
- % Done changed from 0 to 10
The first two commits in this regard are 1093ead and a2bf7a6.
Of course, there is more work to be done, e.g. dcmIsaStorageSOPClassUID() currently only checks for patient DICOM objects so that DcmStorageSCU::checkSOPInstance() reports a warning to the DEBUG logger ("unknown storage SOP class (with standard UID prefix): ..."). Other tools might even deny to send such non-patient objects, even thought the Storage Service is defined for them.
Updated by Jörg Riesmeier over 8 years ago
- % Done changed from 10 to 60
See Commit d8dcde0 (Allow for sending non-patient DICOM objects).
Updated by Jörg Riesmeier over 8 years ago
- Target version changed from 3.6.2 to 3.6.3
Most important changes have already been done. Further evaluation could therefore take place after the upcoming release.
Updated by Jan Schlamelcher over 7 years ago
- Target version changed from 3.6.3 to 3.6.6
Updated by