Ensure PHI/PII is checking for DeviceSerialNumber

[hoodriverheather]

@nutjob4life I may have missed this in the PHI/PII reporting, but I didn't see any rows indicating (0018,1000) Device Serial Number was found with values.

However, when you ran the example set for me (many months ago), many of the sites had a value in that tag. Checkout the EDRN Draft DICOM Header Tags sheet. Draft DICOM Tags with Values Tab. Row 286.

I just wanted to make sure we are checking for this.

[nutjob4life]

@hoodriverheather yes, this tag is being checked. See the source code:

    # These tend to have less identifiable information
    _medium_tags = {
        (0x0010, 0x0020),  # PatientID
        (0x0010, 0x2160),  # EthnicGroup
        (0x0010, 0x2180),  # Occupation
        (0x0010, 0x1040),  # PatientAddress
        (0x0010, 0x0035),  # PatientBirthName
        (0x0010, 0x1060),  # PatientMotherBirthName
        (0x0018, 0x1000),  # DeviceSerialNumber
    }

If you are finding a DICOM file with a value for DeviceSerialNumber that is being missed, please let me know the file name (and if possible, collection, dataset, sub-dataset, etc.) that I can test with. Thanks in advance

[hoodriverheather]

@nutjob4life I will check when you run the next PHI report, but I do see it in the example set you ran for me a long time ago from multiple sites, so i just wanted to double check. Look at Row 286.

[nutjob4life]

@hoodriverheather I see it but I don't know how to read it.

On row 286 I see empty cell, "(0018,1000)", "Device Serial Number", empty cell, "Ye␤s", "remove/anony␤mize/replace", two empty cells, and then ⬛️, –, –, –, ⬛️, ⬛️, –, 0, ⬛️, ⬛️, –, ⬛️, "Value Anonymized", ⬛️, ⬛️, ⬛️, and two empty cells.

Meanwhile I'm continuing to rewrite the software for #31, but until that's ready—and if you want—we can generate fresh reports for all of Lung_Team_Project_2 and Prostate_MRI based on the closed issues so far.

[hoodriverheather]

@nutjob4life I think it is OK to wait until rewrite is done. Here's what i see in an older version, looking back at revision history:

Sorry it's a screenshot.

[nutjob4life]

@hoodriverheather I'm not sure how to interpret the screenshot either. Is one of those values an event ID? Are there column headings?

If you could determine the file name (and if possible, collection, dataset, sub-dataset, etc.), that would help test to see if it's working as intended.

If that's not possible, we could move DeviceSerialNumber from "medium risk tags" to "strict tags" to see what the effect may be after running a new set of reports.