HdBe-ContactInformation

Profile	Description	Status	URL
HdBe-ContactInformation-EmailAddresses	Contact information that includes a person's e-mail addresses.	draft	https://fhir.healthdata.be/StructureDefinition/HdBe-ContactInformation-EmailAddresses
HdBe-ContactInformation-TelephoneNumbers	Contact information that includes a person's telephone numbers.	draft	https://fhir.healthdata.be/StructureDefinition/HdBe-ContactInformation-TelephoneNumbers

HdBe-ContactInformation-EmailAddresses

Instructions
The "EmailAddresses" concept of CBB ContactInformation.

ContactPoint	I		ContactPoint	Element Id ContactPoint Short description EmailAddresses Alternate names EmailAdressen Definition Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. Comments The "EmailAddresses" concept of CBB ContactInformation. Data Type ContactPoint Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2:A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim:n/a v2:XTN rim:TEL servd:ContactPoint zib-contactinformation-v1.2-2020EN:NL-CM:20.6.3 HdBe-ContactInformation:email_addresses
system	Σ I	1..1	codeBindingFixed Value	Element Id ContactPoint.system Short description email Definition Telecommunications form for contact point - what communications system is required to make use of the contact. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data Type code Binding Telecommunications form for contact point. ContactPointSystem (required) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed Value email Mappings rim:n/a v2:XTN.3 rim:./scheme servd:./ContactPointType
value	Σ	0..1	string	Element Id ContactPoint.value Short description EmailAddress Alternate names EmailAdres Definition The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data Type string Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.1 (or XTN.12) rim:./url servd:./Value zib-contactinformation-v1.2-2020EN:NL-CM:20.6.7 HdBe-ContactInformation:email_address
use	Σ ?!	0..1	codeBinding	Element Id ContactPoint.use Short description EmailAddressType Alternate names EmailSoort Definition Identifies the purpose for the contact point. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data Type code Binding Use ConceptMap EmailAddressType-to-ContactInformation-EmailAddressesUse to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-EmailAddressesUse. ContactInformation-EmailAddressesUse (required) Permitted Values EmailAddressType_to_ContactInformation_EmailAddressesUse Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.2 - but often indicated by field rim:unique(./use) servd:./ContactPointPurpose zib-contactinformation-v1.2-2020EN:NL-CM:20.6.8 HdBe-ContactInformation:email_address_type
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element Id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data Type positiveInt Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:n/a
period	Σ I	0..1	Period	There are no (further) constraints on this element Element Id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data Type Period Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1:If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim:n/a v2:DR rim:IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2:N/A rim:./usablePeriod[type="IVL<TS>"] servd:./StartDate and ./EndDate

ContactPoint	I		ContactPoint	Element Id ContactPoint Short description EmailAddresses Alternate names EmailAdressen Definition Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. Comments The "EmailAddresses" concept of CBB ContactInformation. Data Type ContactPoint Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2:A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim:n/a v2:XTN rim:TEL servd:ContactPoint zib-contactinformation-v1.2-2020EN:NL-CM:20.6.3 HdBe-ContactInformation:email_addresses
system	Σ I	1..1	codeBindingFixed Value	Element Id ContactPoint.system Short description email Definition Telecommunications form for contact point - what communications system is required to make use of the contact. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data Type code Binding Telecommunications form for contact point. ContactPointSystem (required) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed Value email Mappings rim:n/a v2:XTN.3 rim:./scheme servd:./ContactPointType
value	Σ	0..1	string	Element Id ContactPoint.value Short description EmailAddress Alternate names EmailAdres Definition The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data Type string Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.1 (or XTN.12) rim:./url servd:./Value zib-contactinformation-v1.2-2020EN:NL-CM:20.6.7 HdBe-ContactInformation:email_address
use	Σ ?!	0..1	codeBinding	Element Id ContactPoint.use Short description EmailAddressType Alternate names EmailSoort Definition Identifies the purpose for the contact point. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data Type code Binding Use ConceptMap EmailAddressType-to-ContactInformation-EmailAddressesUse to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-EmailAddressesUse. ContactInformation-EmailAddressesUse (required) Permitted Values EmailAddressType_to_ContactInformation_EmailAddressesUse Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.2 - but often indicated by field rim:unique(./use) servd:./ContactPointPurpose zib-contactinformation-v1.2-2020EN:NL-CM:20.6.8 HdBe-ContactInformation:email_address_type
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element Id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data Type positiveInt Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:n/a
period	Σ I	0..1	Period	There are no (further) constraints on this element Element Id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data Type Period Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1:If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim:n/a v2:DR rim:IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2:N/A rim:./usablePeriod[type="IVL<TS>"] servd:./StartDate and ./EndDate

ContactPoint	I		ContactPoint	Element Id ContactPoint Short description EmailAddresses Alternate names EmailAdressen Definition Details for all kinds of technology mediated contact points for a person or organization, including telephone, email, etc. Comments The "EmailAddresses" concept of CBB ContactInformation. Data Type ContactPoint Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2:A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim:n/a v2:XTN rim:TEL servd:ContactPoint zib-contactinformation-v1.2-2020EN:NL-CM:20.6.3 HdBe-ContactInformation:email_addresses
system	Σ I	1..1	codeBindingFixed Value	Element Id ContactPoint.system Short description email Definition Telecommunications form for contact point - what communications system is required to make use of the contact. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data Type code Binding Telecommunications form for contact point. ContactPointSystem (required) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Fixed Value email Mappings rim:n/a v2:XTN.3 rim:./scheme servd:./ContactPointType
value	Σ	0..1	string	Element Id ContactPoint.value Short description EmailAddress Alternate names EmailAdres Definition The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data Type string Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.1 (or XTN.12) rim:./url servd:./Value zib-contactinformation-v1.2-2020EN:NL-CM:20.6.7 HdBe-ContactInformation:email_address
use	Σ ?!	0..1	codeBinding	Element Id ContactPoint.use Short description EmailAddressType Alternate names EmailSoort Definition Identifies the purpose for the contact point. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data Type code Binding Use ConceptMap EmailAddressType-to-ContactInformation-EmailAddressesUse to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-EmailAddressesUse. ContactInformation-EmailAddressesUse (required) Permitted Values EmailAddressType_to_ContactInformation_EmailAddressesUse Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.2 - but often indicated by field rim:unique(./use) servd:./ContactPointPurpose zib-contactinformation-v1.2-2020EN:NL-CM:20.6.8 HdBe-ContactInformation:email_address_type
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element Id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data Type positiveInt Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:n/a
period	Σ I	0..1	Period	There are no (further) constraints on this element Element Id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data Type Period Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1:If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim:n/a v2:DR rim:IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2:N/A rim:./usablePeriod[type="IVL<TS>"] servd:./StartDate and ./EndDate

Mapping FHIR profile to CBB

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 ContactInformation-EmailAddresses difference

Concept	Category	Description
`ContactPoint`	textual	Removed zib context in the comment.
`use`	terminology	Changed the conceptmap NumberType-to-ContactInformation-EmailAddressesUse to EmailAddressType-to-ContactInformation-EmailAddressesUse Nictiz ticket #231

HdBe-ContactInformation-TelephoneNumbers

Instructions

Instructions
Implementation of the "TelephoneNumbers" concept of CBB ContactInformation. Please note that, although the concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts `ContactPoint.system` and `ContactPoint.use` respectively, a mismatch occurs on the concept of mobile phone numbers; the CBB uses the first concept and FHIR the second. For this reason, the ValueSet on `ContactPoint.system` is too narrow and the CBB code will need to be communicated using the codeSpecification extension.

Implementation of the "TelephoneNumbers" concept of CBB ContactInformation.

Please note that, although the concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts ContactPoint.system and ContactPoint.use respectively, a mismatch occurs on the concept of mobile phone numbers; the CBB uses the first concept and FHIR the second. For this reason, the ValueSet on ContactPoint.system is too narrow and the CBB code will need to be communicated using the codeSpecification extension.

ContactPoint	I		ContactPoint	Element Id ContactPoint Short description TelephoneNumbers Alternate names Telefoonnummers Definition Container of the TelephoneNumbers concept. This container contains all data elements of the TelephoneNumbers concept. Comments Implementation of the "TelephoneNumbers" concept of CBB ContactInformation. Please note that, although the concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts `ContactPoint.system` and `ContactPoint.use` respectively, a mismatch occurs on the concept of mobile phone numbers; the CBB uses the first concept and FHIR the second. For this reason, the ValueSet on `ContactPoint.system` is too narrow and the CBB code will need to be communicated using the codeSpecification extension. Data Type ContactPoint Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2:A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim:n/a v2:XTN rim:TEL servd:ContactPoint zib-contactinformation-v1.2-2020EN:NL-CM:20.6.2 HdBe-ContactInformation:telephone_numbers
extension	I	0..*	Extension	Element Id ContactPoint.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments 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. Data Type Extension Sliced: Unordered, Open, by url(Value) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
comment	I	0..1	Extension(string)	Element Id ContactPoint.extension:comment Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments 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. Data Type Extension(string) Extension URL https://fhir.healthdata.be/StructureDefinition/ext-Comment Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
url		1..1	System.StringFixed Value	There are no (further) constraints on this element Element Id ContactPoint.extension:comment.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data Type System.String Fixed Value https://fhir.healthdata.be/StructureDefinition/ext-Comment Mappings rim:N/A
value[x]		0..1		Element Id ContactPoint.extension:comment.value[x] Short description Comment Alternate names Toelichting Definition Explanation about the telephone number and how to use it. It can be indicated, for example, that it is a department number (for healthcare professionals) or that availability by phone is only possible during a specified part of the day. Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a rim:N/A zib-contactinformation-v1.2-2020EN:NL-CM:20.6.9 HdBe-ContactInformation:comment
valueString			string	There are no (further) constraints on this element Data Type string
system	Σ I	1..1	codeBinding	Element Id ContactPoint.system Short description TelecomType Alternate names TelecomType Definition The telecom or device type that the telephone number is connected to. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data Type code Binding Use ConceptMap TelecomType-to-ContactInformation-TelephoneNumbersSystem to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-TelephoneNumbersSystem. ContactInformation-TelephoneNumbersSystem (required) Permitted Values TelecomType_to_ContactInformation_TelephoneNumbersSystem Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.3 rim:./scheme servd:./ContactPointType zib-contactinformation-v1.2-2020EN:NL-CM:20.6.5 HdBe-ContactInformation:telecom_type
extension	I	0..*	Extension	Element Id ContactPoint.system.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments 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. Data Type Extension Sliced: Unordered, Open, by url(Value) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
telecomType	I	0..1	Extension(CodeableConcept)	Element Id ContactPoint.system.extension:telecomType Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments 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. Data Type Extension(CodeableConcept) Extension URL https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
url		1..1	System.StringFixed Value	There are no (further) constraints on this element Element Id ContactPoint.system.extension:telecomType.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data Type System.String Fixed Value https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Mappings rim:N/A
value[x]		0..1	Binding	Element Id ContactPoint.system.extension:telecomType.value[x] Short description TelecomType Alternate names TelecomType Definition The telecom or device type that the telephone number is connected to. Binding TelecomType (required) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a rim:N/A zib-contactinformation-v1.2-2020EN:NL-CM:20.6.5 HdBe-ContactInformation:telecom_type
valueCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data Type CodeableConcept
value	Σ	0..1	string	Element Id ContactPoint.value Short description TelephoneNumber Alternate names Telefoonnummer Definition The person's telephone number. Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data Type string Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.1 (or XTN.12) rim:./url servd:./Value zib-contactinformation-v1.2-2020EN:NL-CM:20.6.4 HdBe-ContactInformation:telecom_number
use	Σ ?!	0..1	codeBinding	Element Id ContactPoint.use Short description NumberType Alternate names NummerSoort Definition NumberType indicates whether the number is a landline, temporary, work telephone number. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data Type code Binding Use ConceptMap NumberType-to-ContactInformation-TelephoneNumbersUse to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-TelephoneNumbersUse. ContactInformation-TelephoneNumbersUse (required) Permitted Values NumberType_to_ContactInformation_TelephoneNumbersUse Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.2 - but often indicated by field rim:unique(./use) servd:./ContactPointPurpose zib-contactinformation-v1.2-2020EN:NL-CM:20.6.6 HdBe-ContactInformation:number_type
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element Id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data Type positiveInt Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:n/a
period	Σ I	0..1	Period	There are no (further) constraints on this element Element Id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data Type Period Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1:If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim:n/a v2:DR rim:IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2:N/A rim:./usablePeriod[type="IVL<TS>"] servd:./StartDate and ./EndDate

ContactPoint	I		ContactPoint	Element Id ContactPoint Short description TelephoneNumbers Alternate names Telefoonnummers Definition Container of the TelephoneNumbers concept. This container contains all data elements of the TelephoneNumbers concept. Comments Implementation of the "TelephoneNumbers" concept of CBB ContactInformation. Please note that, although the concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts `ContactPoint.system` and `ContactPoint.use` respectively, a mismatch occurs on the concept of mobile phone numbers; the CBB uses the first concept and FHIR the second. For this reason, the ValueSet on `ContactPoint.system` is too narrow and the CBB code will need to be communicated using the codeSpecification extension. Data Type ContactPoint Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2:A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim:n/a v2:XTN rim:TEL servd:ContactPoint zib-contactinformation-v1.2-2020EN:NL-CM:20.6.2 HdBe-ContactInformation:telephone_numbers
extension	I	0..*	Extension	Element Id ContactPoint.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments 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. Data Type Extension Sliced: Unordered, Open, by url(Value) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
comment	I	0..1	Extension(string)	Element Id ContactPoint.extension:comment Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments 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. Data Type Extension(string) Extension URL https://fhir.healthdata.be/StructureDefinition/ext-Comment Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
url		1..1	System.StringFixed Value	There are no (further) constraints on this element Element Id ContactPoint.extension:comment.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data Type System.String Fixed Value https://fhir.healthdata.be/StructureDefinition/ext-Comment Mappings rim:N/A
value[x]		0..1		Element Id ContactPoint.extension:comment.value[x] Short description Comment Alternate names Toelichting Definition Explanation about the telephone number and how to use it. It can be indicated, for example, that it is a department number (for healthcare professionals) or that availability by phone is only possible during a specified part of the day. Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a rim:N/A zib-contactinformation-v1.2-2020EN:NL-CM:20.6.9 HdBe-ContactInformation:comment
valueString			string	There are no (further) constraints on this element Data Type string
system	Σ I	1..1	codeBinding	Element Id ContactPoint.system Short description TelecomType Alternate names TelecomType Definition The telecom or device type that the telephone number is connected to. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data Type code Binding Use ConceptMap TelecomType-to-ContactInformation-TelephoneNumbersSystem to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-TelephoneNumbersSystem. ContactInformation-TelephoneNumbersSystem (required) Permitted Values TelecomType_to_ContactInformation_TelephoneNumbersSystem Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.3 rim:./scheme servd:./ContactPointType zib-contactinformation-v1.2-2020EN:NL-CM:20.6.5 HdBe-ContactInformation:telecom_type
extension	I	0..*	Extension	Element Id ContactPoint.system.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments 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. Data Type Extension Sliced: Unordered, Open, by url(Value) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
telecomType	I	0..1	Extension(CodeableConcept)	Element Id ContactPoint.system.extension:telecomType Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments 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. Data Type Extension(CodeableConcept) Extension URL https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
url		1..1	System.StringFixed Value	There are no (further) constraints on this element Element Id ContactPoint.system.extension:telecomType.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data Type System.String Fixed Value https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Mappings rim:N/A
value[x]		0..1	Binding	Element Id ContactPoint.system.extension:telecomType.value[x] Short description TelecomType Alternate names TelecomType Definition The telecom or device type that the telephone number is connected to. Binding TelecomType (required) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a rim:N/A zib-contactinformation-v1.2-2020EN:NL-CM:20.6.5 HdBe-ContactInformation:telecom_type
valueCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data Type CodeableConcept
value	Σ	0..1	string	Element Id ContactPoint.value Short description TelephoneNumber Alternate names Telefoonnummer Definition The person's telephone number. Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data Type string Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.1 (or XTN.12) rim:./url servd:./Value zib-contactinformation-v1.2-2020EN:NL-CM:20.6.4 HdBe-ContactInformation:telecom_number
use	Σ ?!	0..1	codeBinding	Element Id ContactPoint.use Short description NumberType Alternate names NummerSoort Definition NumberType indicates whether the number is a landline, temporary, work telephone number. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data Type code Binding Use ConceptMap NumberType-to-ContactInformation-TelephoneNumbersUse to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-TelephoneNumbersUse. ContactInformation-TelephoneNumbersUse (required) Permitted Values NumberType_to_ContactInformation_TelephoneNumbersUse Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.2 - but often indicated by field rim:unique(./use) servd:./ContactPointPurpose zib-contactinformation-v1.2-2020EN:NL-CM:20.6.6 HdBe-ContactInformation:number_type
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element Id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data Type positiveInt Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:n/a
period	Σ I	0..1	Period	There are no (further) constraints on this element Element Id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data Type Period Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1:If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim:n/a v2:DR rim:IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2:N/A rim:./usablePeriod[type="IVL<TS>"] servd:./StartDate and ./EndDate

ContactPoint	I		ContactPoint	Element Id ContactPoint Short description TelephoneNumbers Alternate names Telefoonnummers Definition Container of the TelephoneNumbers concept. This container contains all data elements of the TelephoneNumbers concept. Comments Implementation of the "TelephoneNumbers" concept of CBB ContactInformation. Please note that, although the concepts TelecomType and NumberType are functionally equivalent to the FHIR concepts `ContactPoint.system` and `ContactPoint.use` respectively, a mismatch occurs on the concept of mobile phone numbers; the CBB uses the first concept and FHIR the second. For this reason, the ValueSet on `ContactPoint.system` is too narrow and the CBB code will need to be communicated using the codeSpecification extension. Data Type ContactPoint Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` cpt-2:A system is required if a value is provided. `value.empty() or system.exists()` Mappings rim:n/a v2:XTN rim:TEL servd:ContactPoint zib-contactinformation-v1.2-2020EN:NL-CM:20.6.2 HdBe-ContactInformation:telephone_numbers
extension	I	0..*	Extension	Element Id ContactPoint.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments 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. Data Type Extension Sliced: Unordered, Open, by url(Value) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
comment	I	0..1	Extension(string)	Element Id ContactPoint.extension:comment Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments 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. Data Type Extension(string) Extension URL https://fhir.healthdata.be/StructureDefinition/ext-Comment Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
url		1..1	System.StringFixed Value	There are no (further) constraints on this element Element Id ContactPoint.extension:comment.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data Type System.String Fixed Value https://fhir.healthdata.be/StructureDefinition/ext-Comment Mappings rim:N/A
value[x]		0..1		Element Id ContactPoint.extension:comment.value[x] Short description Comment Alternate names Toelichting Definition Explanation about the telephone number and how to use it. It can be indicated, for example, that it is a department number (for healthcare professionals) or that availability by phone is only possible during a specified part of the day. Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a rim:N/A zib-contactinformation-v1.2-2020EN:NL-CM:20.6.9 HdBe-ContactInformation:comment
valueString			string	There are no (further) constraints on this element Data Type string
system	Σ I	1..1	codeBinding	Element Id ContactPoint.system Short description TelecomType Alternate names TelecomType Definition The telecom or device type that the telephone number is connected to. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data Type code Binding Use ConceptMap TelecomType-to-ContactInformation-TelephoneNumbersSystem to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-TelephoneNumbersSystem. ContactInformation-TelephoneNumbersSystem (required) Permitted Values TelecomType_to_ContactInformation_TelephoneNumbersSystem Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.3 rim:./scheme servd:./ContactPointType zib-contactinformation-v1.2-2020EN:NL-CM:20.6.5 HdBe-ContactInformation:telecom_type
extension	I	0..*	Extension	Element Id ContactPoint.system.extension Short description Additional content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments 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. Data Type Extension Sliced: Unordered, Open, by url(Value) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
telecomType	I	0..1	Extension(CodeableConcept)	Element Id ContactPoint.system.extension:telecomType Short description Optional Extensions Element Alternate names extensions, user content Definition Optional Extension Element - found in all resources. Comments 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. Data Type Extension(CodeableConcept) Extension URL https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` ext-1:Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim:n/a rim:N/A
url		1..1	System.StringFixed Value	There are no (further) constraints on this element Element Id ContactPoint.system.extension:telecomType.url Short description identifies the meaning of the extension Definition Source of the definition for the extension code - a logical name or a URL. Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. Data Type System.String Fixed Value https://fhir.healthdata.be/StructureDefinition/ext-CodeSpecification Mappings rim:N/A
value[x]		0..1	Binding	Element Id ContactPoint.system.extension:telecomType.value[x] Short description TelecomType Alternate names TelecomType Definition The telecom or device type that the telephone number is connected to. Binding TelecomType (required) Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a rim:N/A zib-contactinformation-v1.2-2020EN:NL-CM:20.6.5 HdBe-ContactInformation:telecom_type
valueCodeableConcept			CodeableConcept	There are no (further) constraints on this element Data Type CodeableConcept
value	Σ	0..1	string	Element Id ContactPoint.value Short description TelephoneNumber Alternate names Telefoonnummer Definition The person's telephone number. Requirements Need to support legacy numbers that are not in a tightly controlled format. Comments Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. Data Type string Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.1 (or XTN.12) rim:./url servd:./Value zib-contactinformation-v1.2-2020EN:NL-CM:20.6.4 HdBe-ContactInformation:telecom_number
use	Σ ?!	0..1	codeBinding	Element Id ContactPoint.use Short description NumberType Alternate names NummerSoort Definition NumberType indicates whether the number is a landline, temporary, work telephone number. Requirements Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. Comments Applications can assume that a contact is current unless it explicitly says that it is temporary or old. Data Type code Binding Use ConceptMap NumberType-to-ContactInformation-TelephoneNumbersUse to translate terminology from the functional model to profile terminology in ValueSet ContactInformation-TelephoneNumbersUse. ContactInformation-TelephoneNumbersUse (required) Permitted Values NumberType_to_ContactInformation_TelephoneNumbersUse Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:XTN.2 - but often indicated by field rim:unique(./use) servd:./ContactPointPurpose zib-contactinformation-v1.2-2020EN:NL-CM:20.6.6 HdBe-ContactInformation:number_type
rank	Σ	0..1	positiveInt	There are no (further) constraints on this element Element Id ContactPoint.rank Short description Specify preferred order of use (1 = highest) Definition Specifies a preferred order in which to use a set of contacts. ContactPoints with lower rank values are more preferred than those with higher rank values. Comments Note that rank does not necessarily follow the order in which the contacts are represented in the instance. Data Type positiveInt Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim:n/a v2:n/a
period	Σ I	0..1	Period	There are no (further) constraints on this element Element Id ContactPoint.period Short description Time period when the contact point was/is in use Definition Time period when the contact point was/is in use. Comments A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration. Data Type Period Constraints ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` per-1:If present, start SHALL have a lower value than end `start.hasValue().not() or end.hasValue().not() or (start <= end)` Mappings rim:n/a v2:DR rim:IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2:N/A rim:./usablePeriod[type="IVL<TS>"] servd:./StartDate and ./EndDate

Mapping FHIR profile to CBB

HdBe-ContactInformation-TelephoneNumbers 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 ContactInformation-TelephoneNumbers difference

Concept	Category	Description
`ContactPoint`	textual	Removed zib context in the comment.

Terminology Bindings

Path	Name	Strength	URL	ConceptMap
ContactPoint.use	ContactInformation-EmailAddressesUse	required	https://fhir.healthdata.be/ValueSet/ContactInformation-EmailAddressesUse	https://fhir.healthdata.be/ConceptMap/EmailAddressType-to-ContactInformation-EmailAddressesUse
ContactPoint.system	ContactInformation-TelephoneNumbersSystem	required	https://fhir.healthdata.be/ValueSet/ContactInformation-TelephoneNumbersSystem	https://fhir.healthdata.be/ConceptMap/TelecomType-to-ContactInformation-TelephoneNumbersSystem
ContactPoint.system.extension.value[x]	TelecomType	required	https://fhir.healthdata.be/ValueSet/TelecomType	No bound ConceptMap
ContactPoint.use	ContactInformation-TelephoneNumbersUse	required	https://fhir.healthdata.be/ValueSet/ContactInformation-TelephoneNumbersUse	https://fhir.healthdata.be/ConceptMap/NumberType-to-ContactInformation-TelephoneNumbersUse