HdBe-NameInformation

ProfileDescriptionStatusURL
HdBe-NameInformation

Name information includes a person's given names, nickname, last name and possibly the partner's last name.

drafthttps://fhir.healthdata.be/StructureDefinition/HdBe-NameInformation
Instructions

This datatype defines a common basis for expressing all name information around the world, but adds extensions to express names specifically, according to the CBB NameInformation. A CBB NameInformation name still is a proper FHIR HumanName, which means that systems that cannot interpret the extensions will still be able to render and work with this datatype.

To have true compatibility an implementer SHOULD use the core HumanName parts as intended. The implementer SHOULD in addition use the extension elements. Furthermore, it is encouraged to provide a representation of the full name in the HumanName.text element.

Separate name parts The extension elements cover birth name (NL: achternaam) and partner/spouse name. Both may have a prefix (NL: voorvoegsel). When a person marries, he or she may keep their own name, assume the partner name, append the partner name to their own name, or the other way around. For this reason, there are extensions for marking each part for what it is.

Example: miss Irma Jongeneel marries mister de Haas and assumes the name Irma Jongeneel-de Haas.

  • family = "Jongeneel-de Haas"
  • given = "Irma"
  • family.extension:lastName = "Jongeneel"
  • family.extension:partnerPrefix = "de "
  • family.extension:partnerLastName = "Haas"

The HumanName.use element

The use of element HumanName.use is discouraged because the CBB model does not contain a corresponding concept. If .use is populated, its value SHALL match the semantics of the other elements. To illustrate: if .use is set to official, it is not expected that the zib concept 'GivenName' (NL: roepnaam) is populated because this is not part of an official name.

If the .use element is populated, it is likely that a full name can only be communicated using multiple instances of this profile, one for each purpose of .use. Receiving systems SHOULD be able to handle multiple instances of this datatype profile in an instance.

The CBB concept 'titles'

The CBB concept 'titles' for noble and scientific titles cannot be fully mapped to FHIR. Sending systems should make an effort to provide title information in the best way possible using the .prefix and .suffix elements conform the definition of FHIR. However, if it is not possible to break down the titles properly, it can be communicated as-is using the .prefix element . Receiving systems should be resilient for a broader range of information in the .prefix element than stated by its definition. See the guidance on the .prefix and .suffix elements for more information.


url1..1System.StringFixed Value
valueCodecode
useΣ ?!0..1codeBinding
textΣ0..1string
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueCodecode
url1..1System.StringFixed Value
valueCodecode
url1..1System.StringFixed Value
valueCodecode
prefixΣ0..*string
suffixΣ0..*string
periodΣ I0..1Period

url1..1System.StringFixed Value
valueCodecode
useΣ ?!0..1codeBinding
textΣ0..1string
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueCodecode
url1..1System.StringFixed Value
valueCodecode
url1..1System.StringFixed Value
valueCodecode
prefixΣ0..*string
suffixΣ0..*string
periodΣ I0..1Period

url1..1System.StringFixed Value
valueCodecode
useΣ ?!0..1codeBinding
textΣ0..1string
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueStringstring
url1..1System.StringFixed Value
valueCodecode
url1..1System.StringFixed Value
valueCodecode
url1..1System.StringFixed Value
valueCodecode
prefixΣ0..*string
suffixΣ0..*string
periodΣ I0..1Period

Mapping FHIR profile to CBB

Pathmap
HumanNamename_information
HumanName.extension:humannameAssemblyOrder.value[x]name_usage
HumanName.family.extension:prefix.value[x]last_name.prefix
HumanName.family.extension:lastName.value[x]last_name.last_name
HumanName.family.extension:partnerPrefix.value[x]last_name_partner.partner_prefix
HumanName.family.extension:partnerLastName.value[x]last_name_partner.partner_last_name
HumanName.given:firstNamesfirst_names
HumanName.given:initialsinitials
HumanName.given:givenNamegiven_name
HumanName.prefixtitles
HumanName.suffixtitles

HdBe-NameInformation is a datatype profile and can therefore not have an example of its own. Rather, an example is provided within the example of the HdBe-profile(s) that use this datatype profile.

zib-NameInformation difference

Concept Category Description
HumanName textual Made the implementation guidance in the comment more generic and removed Dutch context.
family.extension:lastName.value[x] textual Added textual guidance that it is allowed to include prefix in the lastName for systems that do not record the prefix sperately, which is common in Belgium.
family.extension:lastName.value[x] textual Added textual guidance that it is allowed to include partnerPrefix in the partnerLastName for systems that do not record the prefix sperately, which is common in Belgium.



Terminology Bindings

PathNameStrengthURLConceptMap
HumanName.extension.value[x]name-assembly-order|4.0.1requiredhttp://hl7.org/fhir/ValueSet/name-assembly-order|4.0.1https://fhir.healthdata.be/ConceptMap/NameUsage-to-HumanNameAssemblyOrder