Closed sls19050 closed 4 hours ago
Thank you for the clear and concise bug report. This seems to be an actual bug. I will investigate
The code in _public_dicom.py is generated based on webscraping of http://dicom.nema.org/medical/dicom/current/output/chtml/part15/chapter_E.html
I assumed table E.1-1
on this webpage was static but this assumption seems to be false. But I have noticed before that it is actually updated from time to time and you have found another update.
I need to update the scraping tool and re-generate _public_dicom.py
This will probably be early next week
Thank you so much! Really appreciate your quick response! :-D
Fixed now for idiscore 1.2.0. All tags in your example are now removed.
pip install idiscore==1.2.0
should fix the issue for you.
The underlying problem was that idiscore was out of date with dicom.nema.org table E.1-1. This is being picked up in #138 Hope this helps!
Description
use scenario: I applied the basic profile and realized that the Instance Creation Date and Time , a.k.a (0008,0012) and (0008,0013), remained the same in the redacted DICOM. I was expecting some action performed to those date and time.
I also looked at the https://github.com/sjoerdk/idiscore/blob/master/idiscore/_public_dicom.py, and realize that the (0008,0012) and (0008,0013) was never mentioned there. Why are they not part of any of the profiles/options?
Expectation as per the Basic Prof. column in Table E.1-1. Application Level Confidentiality Profile Attributes: https://dicom.nema.org/medical/dicom/current/output/chtml/part15/chapter_E.html
What I Did
output: