In our application, while working on managing missing patient information, we noticed inconsistencies between CTK and 3D Slicer default values.
The default value in 3D slicer will be:
Patient name : “No name”
Patient ID : "Patient- + study instance UID
Whereas for CTK :
Patient name : empty
Patient ID : study instance UID
The inconsistency is noticeable if you import in the DICOM database dicoms without a patient name and ID. Then if you load a volume, the name and ID in the subject hierachy tree are different from the DICOM database list of imported files.
Would it be possible to homogenize the patient information default values between CTK and 3D Slicer?
My opinion would be to modify the default value in CTK because the missing patient name generates a blank in the DICOM database list of imported files (not obvious for the user).
Slicer uses CTK, too. If you want your code to behave the same way as Slicer then you can have a look at Slicer’s source code and do exactly the same.
Thank you for your reply!
In our application (Certis Solution), we use both CTK and Slicer 3D. Certis Solution already behaves like slicer for default values in case of missing information. The only difference noticeable is while importing files in the DICOM database and it is made through CTK which have different default values as Slicer or Certis Solution.
The difference is noticeable in Slicer and consequently in our application. For example, if you import DICOM with missing patient name/ID, the patient name line will be blank in the DICOM database (see screen shots taken from Slicer-5.2.2). This blank line gives the feeling that the import failed if the user does not pay attention…
The other application that uses CTK can be updated to not just use the default behavior but use the CTK DICOM classes the same way as Slicer does.