Feature iops 3702 withheld data items#235
Open
vickyjaiswal0308 wants to merge 5 commits into
Open
Conversation
Collaborator
|
Keeping the PR for @omarisgreat contribution. |
Contributor
|
I like the approach but is there any possibility we could align to DS4P extensions/codes, if appropriate? https://build.fhir.org/ig/HL7/fhir-security-label-ds4p/inline_security_labels.html e.g. use the DS4P extension for the inline label and possibly use something like a core confidentiality code (e.g. using ActCode#TBOO, REDACT or NOPAT) for coding whether the information should be withheld. If not, we might need to take this to DA first to get agreement. No inline label can then be the default, e.g. allowing patient disclosure |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Marking Data Items as Withheld
Where a data item is required for clinical interpretation but must not be disclosed to the patient (e.g. sex assigned at birth used for interpretation of results or genomic analysis), it SHALL NOT be replaced with a placeholder value such as “unknown” or “not stated”.
Instead, the original value SHALL be retained in the FHIR resource for clinical use.
Implementations MAY use security labels or element-level visibility annotations to support classification of such data items. Exclusion from patient-facing views SHALL be performed through implementation-defined disclosure rules applied at the time of data presentation.