Hello,
We have recently implemented conversion from any character set to ISO_IR 192 while pulling worklist cases for nicer display of characters in our application. Unfortunately, this causes the logging to show patient information.
We have moved the logging to an encrypted space, but are seeing numerous problems as the logs grow (with debug level logging). I think this is caused by our encryption engine, but unable to change it at this time.
Is there a way to suppress the patient information or the conversion data while maintaining the ability to convert character sets?
Thank you.
Stop displaying conversion info in logs.
Moderator: Moderator Team
-
- DCMTK Developer
- Posts: 2512
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
Re: Stop displaying conversion info in logs.
If you don't want to disable the debug and trace logger of the dcmdata module completely, it would probably be the best approach to introduce a new (sub-)logger (e.g. "dcmtk.dcmdata.protected") for the information concerned. You could then disable (or redirect) only this logger. Maybe, this approach would also make sense for other DCMTK modules where DICOM element values or even complete DICOM datasets are written to the logger.
Of course, this would require changes to the DCMTK source code, e.g. in class DcmSpecificCharacterSet. See logger "dcmtk.dcmqrdb.progress" or "dcmtk.dcmnet.responses" for an example on how this could work.
Of course, this would require changes to the DCMTK source code, e.g. in class DcmSpecificCharacterSet. See logger "dcmtk.dcmqrdb.progress" or "dcmtk.dcmnet.responses" for an example on how this could work.
Re: Stop displaying conversion info in logs.
Thank you for the direction!
-
- DCMTK Developer
- Posts: 2512
- Joined: Tue, 2011-05-03, 14:38
- Location: Oldenburg, Germany
- Contact:
Re: Stop displaying conversion info in logs.
After discussing it with the team, I've created an entry in the DCMTK issue tracker: https://support.dcmtk.org/redmine/issues/1046
Who is online
Users browsing this forum: Bing [Bot], Google [Bot], Semrush [Bot] and 1 guest