Details
-
Change Request
-
Resolution: Persuasive
-
Medium
-
FHIR Core (FHIR)
-
DSTU2
-
Modeling & Methodology
-
Datatypes
-
-
Josh Mandel / Eric Haas : 10-0-0
-
Enhancement
-
Non-compatible
-
DSTU2
Description
HumanName as structured, with ISO 21090 extensions, is not working for nl/de/es people. After extensive discussions - see https://chat.fhir.org/#narrow/stream/implementers/subject/http.3A.2F.2Fhl7.2Eorg.2Ffhir.2FStructureDefinition.2Fiso21090-EN-qualifie - we cam up with this proposal at 2016 DevDays.
1. change family name cardinality to 0..1
Add note that you always fill out the family name with correct display
2. add extensions to core for HumanName.family based on v2:
Own Family name Prefix
Own Family name
Family name Prefix from Partner/Spouse
Family name from Partner/Spouse
Mother's Family Name (not based on v2, but for es)
Father's Family Name
2a. add extension to HumanName:
Name Assembly Order per v2, wtih v2 and Dutch codes. Dutch codes are:
NL0 unknown
NL1 maiden name
NL2 partner name
NL3 name partner followed by maiden name
NL4 maiden name followed by partner name
3. Add a note that when searching on family name, search on all the parts (delimited by spaces, dashes or other separator characters), but national profiles may make more specific rules about which parts are considered in search