You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a user of deidentified FHIR resources, it might be important to know which paths were removed (deidentified) by the deidentification process. Unless this information is not encoded as part of a deidentified resource, it is impossible for a user to know whether a particular data point is simply missing in the original resource or was removed by the deidentification process.
This enhancement could be implemented as either
an Extension that lists all deidentified paths or
Tags (searchable!) that encode the deidentified paths
The text was updated successfully, but these errors were encountered:
One drawback I can think about is that this information might expose an additional "attack surface" for re-identification of a patient. Therefore, this should be an optional feature, that is disabled by default.
For a user of deidentified FHIR resources, it might be important to know which paths were removed (deidentified) by the deidentification process. Unless this information is not encoded as part of a deidentified resource, it is impossible for a user to know whether a particular data point is simply missing in the original resource or was removed by the deidentification process.
This enhancement could be implemented as either
The text was updated successfully, but these errors were encountered: