Skip to content

Retain Safe Private Attributes #2

@rickardcronholm

Description

@rickardcronholm

The current implementation of anonymization profiles in slicebox pulls from the DICOM standard through part15.xml. My understanding of the Safe Pricate Attributes listed in Table E.3.10-1 is that it is incomplete. Nema has the following note

A sample list of Private Attributes thought to be safe is provided here. Vendors do not guarantee them to be safe, and do not commit to sending them in any particular software version (including future products).

One of the key words being sample. I suggest a functionality for defining (or amending) Safe Private Attributes either in the config or as a modifiable anonymization profile. This might be seen as controversial, since indiscretion could lead to sharing of actual private data. This should, however, not be worse than relying on the sample list which also are not guaranteed to be safe by the vendors according to Nema. Moving Private tags to the config at least makes it an active choice for the user.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions