"Id","Path","Slice Name","Alias(s)","Label","Min","Max","Must Support?","Is Modifier?","Is Summary?","Type(s)","Short","Definition","Comments","Requirements","Default Value","Meaning When Missing","Fixed Value","Pattern","Example","Minimum Value","Maximum Value","Maximum Length","Binding Strength","Binding Description","Binding Value Set","Code","Slicing Discriminator","Slicing Description","Slicing Ordered","Slicing Rules","Base Path","Base Min","Base Max","Condition(s)","Constraint(s)","Mapping: HCIM HealthProfessional-v3.2(2017EN)","Mapping: HCIM ContactInformation-v1.0(2017EN)","Mapping: HCIM BasicElements-v1.0(2017EN)","Mapping: HCIM HealthProfessional-v3.0(2016EN)","Mapping: HCIM Patient-v3.0(2016EN)","Mapping: HCIM Patient-v2.0.1(2015EN)","Mapping: HCIM HealthProfessional-v1.2.1(2015EN)"
"Practitioner","Practitioner","","Zorgverlener
","",0,*,"","","","null {[]} {[]}
","HealthProfessional","A person who is directly or indirectly involved in the provisioning of healthcare.","Note that a cab driver no longer fits the bill. You probably would be interested in the organization rather than the individual?","","","","","","","","",,,,,"",,,,"Resource",0,*,"","dom-2:If the resource is contained in another resource, it SHALL NOT contain nested Resources {contained.contained.empty()}
dom-1:If the resource is contained in another resource, it SHALL NOT contain any narrative {contained.text.empty()}dom-4:If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated {contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()}dom-3:If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource {contained.where(('#'+id in %resource.descendants().reference).not()).empty()}zv-pra-3:Either Practitioner BIG or AGB-Z identifier SHALL be present. {identifier.where(system='http://fhir.nl/fhir/NamingSystem/agb-z') or identifier.where(system='http://fhir.nl/fhir/NamingSystem/big')}","NL-CM:17.1.1","NL-CM:0.0.4","NL-CM:0.0.9","NL-CM:17.1.1","NL-CM:17.1.1"
"Practitioner.id","Practitioner.id","","","",0,1,"","","Y","id {[]} {[]}
","Logical id of this artifact","The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.","The only time that a resource does not have an id is when it is being submitted to the server using a create operation.","","","","","","","","",,,,,"",,,,"Resource.id",0,1,"",""
"Practitioner.meta","Practitioner.meta","","","",0,1,"","","Y","Meta {[]} {[]}
","Metadata about the resource","The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.","","","","","","","","","",,,,,"",,,,"Resource.meta",0,1,"",""
"Practitioner.implicitRules","Practitioner.implicitRules","","","",0,1,"","Y","Y","uri {[]} {[]}
","A set of rules under which this content was created","A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.","Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. 

This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.","","","","","","","","",,,,,"",,,,"Resource.implicitRules",0,1,"",""
"Practitioner.language","Practitioner.language","","","",0,1,"","","","code {[]} {[]}
","Language of the resource content","The base language in which the resource is written.","Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource  Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).","","","","","","","","",,"extensible","A human language.","http://hl7.org/fhir/ValueSet/languages","",,,,"Resource.language",0,1,"",""
"Practitioner.text","Practitioner.text","","narrative
htmlxhtmldisplay","",0,1,"","","","Narrative {[]} {[]}
","Text summary of the resource, for human interpretation","A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it ""clinically safe"" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.","Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a ""text blob"" or where text is additionally entered raw or narrated and encoded in formation is added later.","","","","","","","","",,,,,"",,,,"DomainResource.text",0,1,"dom-1
",""
"Practitioner.contained","Practitioner.contained","","inline resources
anonymous resourcescontained resources","",0,*,"","","","Resource {[]} {[]}
","Contained, inline Resources","These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.","This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.","","","","","","","","",,,,,"",,,,"DomainResource.contained",0,*,"",""
"Practitioner.extension","Practitioner.extension","","extensions
user content","",0,*,"","","","Extension {[]} {[]}
","Additional Content defined by implementations","May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"",,,,"DomainResource.extension",0,*,"",""
"Practitioner.modifierExtension","Practitioner.modifierExtension","","extensions
user content","",0,*,"","Y","","Extension {[]} {[]}
","Extensions that cannot be ignored","May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"",,,,"DomainResource.modifierExtension",0,*,"",""
"Practitioner.identifier","Practitioner.identifier","","ZorgverlenerIdentificatieNummer
","",1,*,"","","Y","Identifier {[]} {[]}
","HealthProfessionalIdentificationNumber","The health professional identification number is a number that uniquely identifies the health professional.  

The following numbers are used in the Netherlands:
1. UZI Health Professionals. Identification of health professionals (people) in the Dutch healthcare industry.
2. VEKTIS AGB-Z. Identifies health professionals and healthcare organizations.
3. BIG-ID. The ID of the health professional listed in the BIG Register.

This information is not readily available for foreign health professionals.","","Often, specific identities are assigned for the agent.","","","","","","","",,,,,"","value:system}
","",,"open","Practitioner.identifier",0,*,"","","NL-CM:17.1.2","NL-CM:0.0.6","NL-CM:17.1.2","NL-CM:17.1.2"
"Practitioner.identifier:UZI","Practitioner.identifier","UZI","UZI
","",0,1,"","","Y","Identifier {[]} {[]}
","UZI","Unieke Zorgverlener Identificatie (Dutch physician identification number)","","Often, specific identities are assigned for the agent.","","","","","","","",,,,,"",,,,"Practitioner.identifier",0,*,"",""
"Practitioner.identifier:UZI.id","Practitioner.identifier.id","","","",0,1,"","","","string {[]} {[]}
","xml:id (or equivalent in JSON)","unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.","","","","","","","","","",,,,,"",,,,"Element.id",0,1,"",""
"Practitioner.identifier:UZI.extension","Practitioner.identifier.extension","","extensions
user content","",0,*,"","","","Extension {[]} {[]}
","Additional Content defined by implementations","May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"","value:url}
","Extensions are always sliced by (at least) url",,"open","Element.extension",0,*,"",""
"Practitioner.identifier:UZI.use","Practitioner.identifier.use","","","",0,1,"","Y","Y","code {[]} {[]}
","usual | official | temp | secondary (If known)","The purpose of this identifier.","This is labeled as ""Is Modifier"" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.","Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.","","","","","","","",,"required","Identifies the purpose for this identifier, if known .","http://hl7.org/fhir/ValueSet/identifier-use","",,,,"Identifier.use",0,1,"",""
"Practitioner.identifier:UZI.type","Practitioner.identifier.type","","","",0,1,"","","Y","CodeableConcept {[]} {[]}
","Description of identifier","A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.","This element deals only with general categories of identifiers.  It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. 

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.","Allows users to make use of identifiers when the identifier system is not known.","","","","","","","",,"extensible","A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.","http://hl7.org/fhir/ValueSet/identifier-type","",,,,"Identifier.type",0,1,"",""
"Practitioner.identifier:UZI.system","Practitioner.identifier.system","","","",1,1,"","","Y","uri {[]} {[]}
","The namespace for the identifier value","Establishes the namespace for the value - that is, a URL that describes a set values that are unique.","","There are many sets  of identifiers.  To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.","","","<valueUri xmlns=""http://hl7.org/fhir"" value=""http://fhir.nl/fhir/NamingSystem/uzi-nr-pers""/>","","<valueUri xmlns=""http://hl7.org/fhir"" value=""http://www.acme.com/identifiers/patient""/>","","",,,,,"",,,,"Identifier.system",0,1,"",""
"Practitioner.identifier:UZI.value","Practitioner.identifier.value","","","",1,1,"","","Y","string {[]} {[]}
","The value that is unique","The portion of the identifier typically relevant to the user and which is unique within the context of the system.","If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.  The value's primary purpose is computational mapping.  As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.)  A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/STU3/extension-rendered-value.html).","","","","","","<valueString xmlns=""http://hl7.org/fhir"" value=""123456""/>","","",,,,,"",,,,"Identifier.value",0,1,"",""
"Practitioner.identifier:UZI.period","Practitioner.identifier.period","","","",0,1,"","","Y","Period {[]} {[]}
","Time period when id is/was valid for use","Time period during which identifier is/was valid for use.","","","","","","","","","",,,,,"",,,,"Identifier.period",0,1,"",""
"Practitioner.identifier:UZI.assigner","Practitioner.identifier.assigner","","","",0,1,"","","Y","Reference {[]} {[CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization]]}
","Organization that issued id (may be just text)","Organization that issued/manages the identifier.","The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.","","","","","","","","",,,,,"",,,,"Identifier.assigner",0,1,"",""
"Practitioner.identifier:AGB","Practitioner.identifier","AGB","AGB
","",0,1,"Y","","Y","Identifier {[]} {[]}
","AGB","An identifier that applies to this person in this role.","","Often, specific identities are assigned for the agent.","","","","","","","",,,,,"",,,,"Practitioner.identifier",0,*,"",""
"Practitioner.identifier:AGB.id","Practitioner.identifier.id","","","",0,1,"","","","string {[]} {[]}
","xml:id (or equivalent in JSON)","unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.","","","","","","","","","",,,,,"",,,,"Element.id",0,1,"",""
"Practitioner.identifier:AGB.extension","Practitioner.identifier.extension","","extensions
user content","",0,*,"","","","Extension {[]} {[]}
","Additional Content defined by implementations","May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"","value:url}
","Extensions are always sliced by (at least) url",,"open","Element.extension",0,*,"",""
"Practitioner.identifier:AGB.use","Practitioner.identifier.use","","","",0,1,"","Y","Y","code {[]} {[]}
","usual | official | temp | secondary (If known)","The purpose of this identifier.","This is labeled as ""Is Modifier"" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.","Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.","","","","","","","",,"required","Identifies the purpose for this identifier, if known .","http://hl7.org/fhir/ValueSet/identifier-use","",,,,"Identifier.use",0,1,"",""
"Practitioner.identifier:AGB.type","Practitioner.identifier.type","","","",0,1,"","","Y","CodeableConcept {[]} {[]}
","Description of identifier","A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.","This element deals only with general categories of identifiers.  It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. 

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.","Allows users to make use of identifiers when the identifier system is not known.","","","","","","","",,"extensible","A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.","http://hl7.org/fhir/ValueSet/identifier-type","",,,,"Identifier.type",0,1,"",""
"Practitioner.identifier:AGB.system","Practitioner.identifier.system","","","",1,1,"","","Y","uri {[]} {[]}
","The namespace for the identifier value","Establishes the namespace for the value - that is, a URL that describes a set values that are unique.","","There are many sets  of identifiers.  To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.","","","<valueUri xmlns=""http://hl7.org/fhir"" value=""http://fhir.nl/fhir/NamingSystem/agb-z""/>","","<valueUri xmlns=""http://hl7.org/fhir"" value=""http://www.acme.com/identifiers/patient""/>","","",,,,,"",,,,"Identifier.system",0,1,"",""
"Practitioner.identifier:AGB.value","Practitioner.identifier.value","","","",1,1,"","","Y","string {[]} {[]}
","The value that is unique","The portion of the identifier typically relevant to the user and which is unique within the context of the system.","If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.  The value's primary purpose is computational mapping.  As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.)  A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/STU3/extension-rendered-value.html).","","","","","","<valueString xmlns=""http://hl7.org/fhir"" value=""123456""/>","","",,,,,"",,,,"Identifier.value",0,1,"",""
"Practitioner.identifier:AGB.period","Practitioner.identifier.period","","","",0,1,"","","Y","Period {[]} {[]}
","Time period when id is/was valid for use","Time period during which identifier is/was valid for use.","","","","","","","","","",,,,,"",,,,"Identifier.period",0,1,"",""
"Practitioner.identifier:AGB.assigner","Practitioner.identifier.assigner","","","",0,1,"","","Y","Reference {[]} {[CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization]]}
","Organization that issued id (may be just text)","Organization that issued/manages the identifier.","The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.","","","","","","","","",,,,,"",,,,"Identifier.assigner",0,1,"",""
"Practitioner.identifier:BIG","Practitioner.identifier","BIG","BIG
","",0,1,"Y","","Y","Identifier {[]} {[]}
","BIG","An identifier that applies to this person in this role.","","Often, specific identities are assigned for the agent.","","","","","","","",,,,,"",,,,"Practitioner.identifier",0,*,"",""
"Practitioner.identifier:BIG.id","Practitioner.identifier.id","","","",0,1,"","","","string {[]} {[]}
","xml:id (or equivalent in JSON)","unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.","","","","","","","","","",,,,,"",,,,"Element.id",0,1,"",""
"Practitioner.identifier:BIG.extension","Practitioner.identifier.extension","","extensions
user content","",0,*,"","","","Extension {[]} {[]}
","Additional Content defined by implementations","May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"","value:url}
","Extensions are always sliced by (at least) url",,"open","Element.extension",0,*,"",""
"Practitioner.identifier:BIG.use","Practitioner.identifier.use","","","",0,1,"","Y","Y","code {[]} {[]}
","usual | official | temp | secondary (If known)","The purpose of this identifier.","This is labeled as ""Is Modifier"" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.","Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.","","","","","","","",,"required","Identifies the purpose for this identifier, if known .","http://hl7.org/fhir/ValueSet/identifier-use","",,,,"Identifier.use",0,1,"",""
"Practitioner.identifier:BIG.type","Practitioner.identifier.type","","","",0,1,"","","Y","CodeableConcept {[]} {[]}
","Description of identifier","A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.","This element deals only with general categories of identifiers.  It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. 

Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.","Allows users to make use of identifiers when the identifier system is not known.","","","","","","","",,"extensible","A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.","http://hl7.org/fhir/ValueSet/identifier-type","",,,,"Identifier.type",0,1,"",""
"Practitioner.identifier:BIG.system","Practitioner.identifier.system","","","",1,1,"","","Y","uri {[]} {[]}
","The namespace for the identifier value","Establishes the namespace for the value - that is, a URL that describes a set values that are unique.","","There are many sets  of identifiers.  To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.","","","<valueUri xmlns=""http://hl7.org/fhir"" value=""http://fhir.nl/fhir/NamingSystem/big""/>","","<valueUri xmlns=""http://hl7.org/fhir"" value=""http://www.acme.com/identifiers/patient""/>","","",,,,,"",,,,"Identifier.system",0,1,"",""
"Practitioner.identifier:BIG.value","Practitioner.identifier.value","","","",1,1,"","","Y","string {[]} {[]}
","The value that is unique","The portion of the identifier typically relevant to the user and which is unique within the context of the system.","If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986.  The value's primary purpose is computational mapping.  As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.)  A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/STU3/extension-rendered-value.html).","","","","","","<valueString xmlns=""http://hl7.org/fhir"" value=""123456""/>","","",,,,,"",,,,"Identifier.value",0,1,"",""
"Practitioner.identifier:BIG.period","Practitioner.identifier.period","","","",0,1,"","","Y","Period {[]} {[]}
","Time period when id is/was valid for use","Time period during which identifier is/was valid for use.","","","","","","","","","",,,,,"",,,,"Identifier.period",0,1,"",""
"Practitioner.identifier:BIG.assigner","Practitioner.identifier.assigner","","","",0,1,"","","Y","Reference {[]} {[CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization]]}
","Organization that issued id (may be just text)","Organization that issued/manages the identifier.","The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.","","","","","","","","",,,,,"",,,,"Identifier.assigner",0,1,"",""
"Practitioner.active","Practitioner.active","","","",0,1,"","","Y","boolean {[]} {[]}
","Whether this practitioner's record is in active use","Whether this practitioner's record is in active use.","Default is true. 

If the practitioner is not in use by one organization, then it should mark the period on the PractitonerRole with an end date (even if they are active) as they may be active in another role.","Need to be able to mark a practitioner record as not to be used because it was created in error.","<valueBoolean xmlns=""http://hl7.org/fhir"" value=""true""/>","","","","","","",,,,,"",,,,"Practitioner.active",0,1,"",""
"Practitioner.name","Practitioner.name","","Naamgegevens
","",1,*,"Y","","Y","HumanName {[CanonicalType[http://fhir.nl/fhir/StructureDefinition/nl-core-humanname]]} {[]}
","NameInformation","Health professional’s full name. If a health professional identification number is entered, it will be the name as listed in UZI, AGB or by the healthcare center.","Dutch names require that certain name parts are separately communicable. For this reason, extensions are added onto the base HumanName element to mark the meaning of each part. A Dutch HumanName is still a proper FHIR HumanName; however, there might be an incompatibilty with the default FHIR mechanism for communicating given names. See the compatibility note below for more information.

The extension elements cover birth name (NL: eigennaam / geslachtsnaam) 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.

**Incompatibility note**: It has come to light that this specification deviates from the way that the HumanName datatype is normally used. This will be fixed in a future release. However, current implementations should be aware of the special considerations regarding the use of this specification. 

The issue at hand is the way alternative representations of a name, like initials or a nickname, are communicated. Normally this is done using multiple HumanName instances, which are differentiated using the `.use` element. However, this specification allows for including all alternative representations in the _same_ HumanName instance, with the expectation that the extensions provide enough information for receiving systems to differentiate them. However, this means that contrary to the normal usage of this datatype, repetitions of `.given` names cannot be concatenated to get the full list of given names; the list might be a mix of full names, nicknames and initials.

Since multiple implementations are based on this specification, sending systems are advised (but not required) to keep the approach with one HumanName instance, while receiving systems should be able to handle this one-instance approach. More specifically:

* Sending and receiving systems SHOULD always use the specified extensions when using this datatype.
* Sending systems are encouraged to populate the `.text` element to unambigiously communicate the person's name.
* Sending systems are encouraged to send either the full given names or the initials, but not both. This alleviates the duplication of names in `.given`.
* When a sending system uses the current one-instance approach for communicating multiple representations, `.use` MAY NOT be populated. After all, it is not possible to select a single `.use` when the instance contains different representations.
* When a receiving system interprets the instance as the single-instance-multiple-representations approach, the `.given` names marked as initials SHOULD be interpreted as alternatives to the full given names. Note the underlying HCIM expects both the _list_ of full names and _list_ of initials to be a single string; there's no match for an initial to a full name. The instance SHOULD be regarded as using this approach when:
  * They encounter a single instance
  * And the `.use` element is absent
  * And all the name parts are differentiated using the specified extensions
* In any other circumstance, receiving systems SHOULD interpret the usage as the normal use.

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

* `.family` = ""XXX_Helleman-de Haas""
* `.given` = ""Irma"" (with `.given:iso21090EnQualifier` = _BR_)
* `.family:humannameOwnName` = ""XXX_Helleman""
* `.family:humannamePartnerPrefix` = ""de ""
* `.family:humannamePartnerName` = ""Haas""","The name(s) that a Practitioner is known by. Where there are multiple, the name that the practitioner is usually known as should be used in the display.","","","","","<valueHumanName xmlns=""http://hl7.org/fhir"">
  <extension url=""http://hl7.org/fhir/StructureDefinition/humanname-assembly-order"">
    <valueCode value=""NL4""/>
  </extension>
  <text value=""Irma XXX_Helleman-de Haas""/>
  <family value=""XXX_Helleman-de Haas"">
    <extension url=""http://hl7.org/fhir/StructureDefinition/humanname-own-name"">
      <valueString value=""XXX_Helleman""/>
    </extension>
    <extension url=""http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix"">
      <valueString value=""de""/>
    </extension>
    <extension url=""http://hl7.org/fhir/StructureDefinition/humanname-partner-name"">
      <valueString value=""Haas""/>
    </extension>
  </family>
  <given value=""Irma"">
    <extension url=""http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier"">
      <valueCode value=""CL""/>
    </extension>
  </given>
</valueHumanName>","","",,,,,"",,,,"Practitioner.name",0,*,"ele-1
","ele-1:All FHIR elements must have a @value or children {hasValue() | (children().count() > id.count())}
nl-core-humanname-1:if you specify a prefix for an own name then an own name is also expected {name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-own-name').empty().not()}nl-core-humanname-2:if you specify a voorvoegsel for a partner name then a partner name is also expected {name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-prefix').empty().not() implies name.family.extension('http://hl7.org/fhir/StructureDefinition/humanname-partner-name').empty().not()}zv-pra-1:Either Practitioner.name.given and/or Practitioner.name.family and/or Practitioner.name.text SHALL be present. {(family.exists() or given.exists() or text.exists())}zv-pra-2:To be usable for a wide range of internationally available applications, the Patient.name.text SHOULD be present. {text.exists()}","NL-CM:17.1.3","NL-CM:17.1.3","NL-CM:17.1.3"
"Practitioner.telecom","Practitioner.telecom","","Contactgegevens
","",0,*,"","","Y","ContactPoint {[CanonicalType[http://fhir.nl/fhir/StructureDefinition/nl-core-contactpoint]]} {[]}
","ContactInformation","Contact information includes a person's telephone numbers and email addresses. This datatype defines a common basis for expressing all contact information around the world, but adds extensions to express Dutch contacts specifically, according to the HCIM ContactInformation (v1.0, 2017). A Dutch ContactPoint still is a proper FHIR ContactPoint, which means that systems that cannot interpret the extensions will still be able to render and work with this datatype. The table below explains how the HCIM concepts are mapped to the various FHIR elements. The HCIM code itself should also be included using the TelecomType extension.

| HCIM                                               | `.ext:TelecomType` | `.system` | `.use`   |
|----------------------------------------------------|:------------------:|:---------:|:--------:|
| Primary Home Land Line                             | _LL_               | _phone_   | _home_   |
| Temporary Land Line                                | _LL_               | _phone_   | _temp_   |
| Primary Work Land Line                             | _LL_               | _phone_   | _work_   |
|                                                    |                    |           |          |
| Primary Home Fax                                   | _FAX_              | _fax_     | _home_   |
| Temporary Fax                                      | _FAX_              | _fax_     | _temp_   |
| Primary Work Fax                                   | _FAX_              | _fax_     | _work_   |
|                                                    |                    |           |          |
| Primary Home Mobile Phone                          | _MC_               | _phone_   | _home_   |
| Temporary Mobile Phone                             | _MC_               | _phone_   | _temp_   |
| Primary Work Mobile Phone                          | _MC_               | _phone_   | _work_   |
|                                                    |                    |           |          |
| Primary Home Pager                                 | _PG_               | _pager_   | _home_   |
| Temporary Pager                                    | _PG_               | _pager_   | _temp_   |
| Primary Work Pager                                 | _PG_               | _pager_   | _work_   |
|                                                    |                    |           |          |
| Private email address                              |                    | _email_   | _home_   |
| Work email address                                 |                    | _email_   | _work_   |
|                                                    |                    |           |          |
| Mobile phone number undetermined private/business  |                    | _phone_   | _mobile_ |","Person may have multiple ways to be contacted with different uses or applicable periods.  May need to have options for contacting the person urgently, and also to help with identification

These typically will have home numbers, or mobile numbers that are not role specific.","Need to know how to reach a practitioner independent to any roles the practitioner may have.","","","","","<valueContactPoint xmlns=""http://hl7.org/fhir"">
  <system value=""phone""/>
  <value value=""+31611234567""/>
  <use value=""work""/>
</valueContactPoint>","","",,,,,"",,,,"Practitioner.telecom",0,*,"ele-1
","ele-1:All FHIR elements must have a @value or children {hasValue() | (children().count() > id.count())}
cpt-2:A system is required if a value is provided. {value.empty() or system.exists()}","NL-CM:17.1.8","NL-CM:20.6.1","NL-CM:17.1.8","NL-CM:0.1.5","NL-CM:0.1.5","NL-CM:17.1.8"
"Practitioner.address","Practitioner.address","","AdresInformatie
Adresgegevens","",0,*,"","","Y","Address {[CanonicalType[http://fhir.nl/fhir/StructureDefinition/nl-core-address]]} {[]}
","AddressInformation","This datatype defines a common basis for expressing all addresses around the world, but adds extensions to express Dutch addresses specifically, according to the HCIM AddressInformation (v1.0, 2017). A Dutch Address still is a proper FHIR Address, 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 Address parts as intended. To have addresses work for Dutch context, the implementer SHOULD in addition use the extension elements.

**Separate address parts**

The first addition is that Dutch addresses make certain address parts separately communicable. These parts are required for use in true Dutch systems when dealing with Dutch addresses, but may not have value for international systems when information gets sent abroad.

**Custom address types**

The second addition is that the HCIM defines its own ValueSet for address types, which can only be partially expressed using the FHIR Address datatype and requires a mapping to multiple elements. The table below explains how the HCIM concepts are mapped to the various FHIR elements (see the ConceptMaps <http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressUse> and <http://nictiz.nl/fhir/ConceptMap/AdresSoortCodelijst-to-AddressType> as well). The HCIM code itself should also be included using the AddressType extension.

| HCIM                              |` .ext:AddressType` | `.ext:official` | `.use` | `.type`    |
|-----------------------------------|:------------------:|:---------------:|:------:|:----------:|
| Postal Address/Postadres          | _PST_              |                 |        | _postal_   |
| Primary Home/Officieel adres      | _HP_               | true            | _home_ |            |
| Visit Address/Woon-/verblijfadres | _PHYS_             |                 | _home_ | _physical_ |
| Temporary Address/Tijdelijk adres | _TMP_              |                 | _temp_ |            |
| Work Place/Werkadres              | _WP_               |                 | _work_ |            |
| Vacation Home/Vakantie adres      | _HV_               |                 | _temp_ |            |

 If Address.type is _both_ then this is to be understood as a dual purpose address (postal and physical). Systems that support importing it like this are encouraged to do so, otherwise they may need to import this as two separate addresses.

NOTE: FHIR core defines the AD-use extension to further specify the postal address type. However, the ValueSet used in that extension doesn't completely match the HCIM ValueSet. Therefore, a custom extension has been made. This doesn't preclude the use of the AD-use extension.","Note: address is for postal addresses, not physical locations.","The home/mailing address of the practitioner is often required for employee administration purposes, and also for some rostering services where the start point (practitioners home) can be used in calculations.","","","","","<valueAddress xmlns=""http://hl7.org/fhir"">
  <extension url=""http://nictiz.nl/fhir/StructureDefinition/zib-AddressInformation-AddressType"">
    <valueCodeableConcept>
      <coding>
        <system value=""http://hl7.org/fhir/v3/AddressUse""/>
        <code value=""HV""/>
        <display value=""Vakantie adres""/>
      </coding>
    </valueCodeableConcept>
  </extension>
  <use value=""temp""/>
  <line value=""Binnenkant 12A Hoog"">
    <extension url=""http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName"">
      <valueString value=""Binnenkant""/>
    </extension>
    <extension url=""http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber"">
      <valueString value=""12""/>
    </extension>
    <extension url=""http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix"">
      <valueString value=""A""/>
    </extension>
    <extension url=""http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-unitID"">
      <valueString value=""Hoog""/>
    </extension>
  </line>
  <city value=""Amsterdam""/>
  <state value=""NH""/>
  <postalCode value=""1000AA""/>
  <country value=""NLD""/>
</valueAddress>","","",,,,,"",,,,"Practitioner.address",0,*,"ele-1
nl-streetname-if-official-and-other-line-parts","ele-1:All FHIR elements must have a @value or children {hasValue() | (children().count() > id.count())}
nl-streetname-if-official-and-other-line-parts:Address.streetName in an official address SHALL have a value if one of houseNumber|buildingNumberSuffix|additionalLocator has a value {(extension.where(url = 'http://fhir.nl/fhir/StructureDefinition/nl-core-address-official').where(value = true)).empty() or (line.extension.where(url = 'http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-streetName').empty().not() and (line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-houseNumber').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-buildingNumberSuffix').empty().not() or line.extension.where(url='http://hl7.org/fhir/StructureDefinition/iso21090-ADXP-additionalLocator').empty().not()))}","NL-CM:17.1.7","NL-CM:17.1.7","NL-CM:17.1.7"
"Practitioner.gender","Practitioner.gender","","","",0,1,"","","Y","code {[]} {[]}
","male | female | other | unknown","Administrative Gender - the gender that the person is considered to have for administration and record keeping purposes.","","Needed to address the person correctly.","","","","","","","",,"required","The gender of a person used for administrative purposes.","http://hl7.org/fhir/ValueSet/administrative-gender","",,,,"Practitioner.gender",0,1,"",""
"Practitioner.birthDate","Practitioner.birthDate","","","",0,1,"","","Y","date {[]} {[]}
","The date  on which the practitioner was born","The date of birth for the practitioner.","","Needed for identification.","","","","","","","",,,,,"",,,,"Practitioner.birthDate",0,1,"",""
"Practitioner.photo","Practitioner.photo","","","",0,*,"","","","Attachment {[]} {[]}
","Image of the person","Image of the person.","","Many EHR systems have the capability to capture an image of patients and personnel. Fits with newer social media usage too.","","","","","","","",,,,,"",,,,"Practitioner.photo",0,*,"",""
"Practitioner.qualification","Practitioner.qualification","","","",0,*,"Y","","","BackboneElement {[]} {[]}
","Qualifications obtained by training and certification","Qualifications obtained by training and certification.","","","","","","","","","",,,,,"",,,,"Practitioner.qualification",0,*,"","ele-1:All FHIR elements must have a @value or children {hasValue() | (children().count() > id.count())}
zv-pra-4:A SNOMED CT (beroep) code SHOULD be present. {code.coding.where(system='http://snomed.info/sct')}"
"Practitioner.qualification.id","Practitioner.qualification.id","","","",0,1,"","","","string {[]} {[]}
","xml:id (or equivalent in JSON)","unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.","","","","","","","","","",,,,,"",,,,"Element.id",0,1,"",""
"Practitioner.qualification.extension","Practitioner.qualification.extension","","extensions
user content","",0,*,"","","","Extension {[]} {[]}
","Additional Content defined by implementations","May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance  applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"",,,,"Element.extension",0,*,"",""
"Practitioner.qualification.modifierExtension","Practitioner.qualification.modifierExtension","","extensions
user contentmodifiers","",0,*,"","Y","Y","Extension {[]} {[]}
","Extensions that cannot be ignored","May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.","There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions.  The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.","","","","","","","","",,,,,"",,,,"BackboneElement.modifierExtension",0,*,"",""
"Practitioner.qualification.identifier","Practitioner.qualification.identifier","","","",0,*,"","","","Identifier {[]} {[]}
","An identifier for this qualification for the practitioner","An identifier that applies to this person's qualification in this role.","","Often, specific identities are assigned for the qualification.","","","","","","","",,,,,"",,,,"Practitioner.qualification.identifier",0,*,"",""
"Practitioner.qualification.code","Practitioner.qualification.code","","","",1,1,"","","","CodeableConcept {[]} {[]}
","Coded representation of the qualification","Coded representation of the qualification.","","","","","","","","","",,"example","Specific qualification the practitioner has to provide a service","http://hl7.org/fhir/ValueSet/v2-2.7-0360","",,,,"Practitioner.qualification.code",1,1,"",""
"Practitioner.qualification.period","Practitioner.qualification.period","","","",0,1,"","","","Period {[]} {[]}
","Period during which the qualification is valid","Period during which the qualification is valid.","","Qualifications are often for a limited period of time, and can be revoked.","","","","","","","",,,,,"",,,,"Practitioner.qualification.period",0,1,"",""
"Practitioner.qualification.issuer","Practitioner.qualification.issuer","","","",0,1,"","","","Reference {[]} {[CanonicalType[http://hl7.org/fhir/StructureDefinition/Organization]]}
","Organization that regulates and issues the qualification","Organization that regulates and issues the qualification.","","","","","","","","","",,,,,"",,,,"Practitioner.qualification.issuer",0,1,"",""
"Practitioner.communication","Practitioner.communication","","","",0,*,"","","","CodeableConcept {[]} {[]}
","A language the practitioner is able to use in patient communication","A language the practitioner is able to use in patient communication.","The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems actually code this but instead have it as free text. Hence CodeableConcept instead of code as the data type.","Knowing which language a practitioner speaks can help in facilitating communication with patients.","","","","","","","",,"extensible","A human language.","http://hl7.org/fhir/ValueSet/languages","",,,,"Practitioner.communication",0,*,"",""
