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
Høringssvar:
There is a risk that this will require development in it-systems to support name and address protection for related persons. Since the text says "should be labeled" this is not expected to be a hard requirement.
Besluttet:
Vi tilføjer en indledende sætning til afsnittet som beskriver, at hvis man i en given implementering skal understøtte navne- og adressebeskyttelse, så anbefaler vi, at det gøres på følgende måde. Denne formulering skal både inkluderes i dokumentationen for RelatedPerson og Patient.
The text was updated successfully, but these errors were encountered:
* Updated scope and usage section according to #136
* Updated scope and usage section according to #135
* added to relationship value set and code system supplement to account for #135 and #134
* Handled issues from consultation
#140, #139, #137
* Update StructureDefinition-dk-core-patient-intro.md
#138
* Updated after review
* Update release-notes.md
---------
Co-authored-by: Christian Gasser <[email protected]>
Co-authored-by: kirstinerosenbeck <[email protected]>
Co-authored-by: Jens Kristian Villadsen <[email protected]>
Høringssvar:
There is a risk that this will require development in it-systems to support name and address protection for related persons. Since the text says "should be labeled" this is not expected to be a hard requirement.
Besluttet:
Vi tilføjer en indledende sætning til afsnittet som beskriver, at hvis man i en given implementering skal understøtte navne- og adressebeskyttelse, så anbefaler vi, at det gøres på følgende måde. Denne formulering skal både inkluderes i dokumentationen for RelatedPerson og Patient.
The text was updated successfully, but these errors were encountered: