Important: This is a draft IG for trial use. Click here to give feedback.

HdBe-InformationContact

CBB	Concept	Status
HdBe-ContactInformation	Les informations de contact comprennent les numéros de téléphone et les adresses e-mail d'une personne.Il s'agit d'un modèle d'information partiel. Purpose Les informations de contact sont utilisées pour contacter une personne.	active

CBB

Concept

Status

HdBe-ContactInformation

Les informations de contact comprennent les numéros de téléphone et les adresses e-mail d'une personne.Il s'agit d'un modèle d'information partiel.

Purpose

Les informations de contact sont utilisées pour contacter une personne.

active

ContactInformation			ContactInformation	Element id ContactInformation Short description InformationContact Definition Concept root du modèle d'information partiel InformationContact. Ce concept root contient tous les éléments de données du modèle d'information partiel InformationContact. Data type ContactInformation Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id ContactInformation.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id ContactInformation.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) Extensions are always sliced by (at least) url 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
Type		0..1	CodeableConceptBinding	Element id ContactInformation.Type Short description Type Definition The type of contact information. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Formulaire de télécommunications pour point de contact. ContactPointSystem (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
Value		1..1	string	Element id ContactInformation.Value Short description Value Definition The actual contact information details. Comments Note that FHIR strings SHALL NOT exceed 1MB in size 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
Use		0..1	CodeableConceptBinding	Element id ContactInformation.Use Short description Use Definition Purpose or use of the contact information. For example whether it is a private or business telephone number. Comments Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Data type CodeableConcept Binding Utilisation de point de contact. ContactPointUse (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
Comment		0..1	string	Element id ContactInformation.Comment Short description Comment Definition Explanation about the contact information and how to use it. It can be indicated, for example, that a telephone number concerns a department number (for healthcare professionals) or that availability by phone is only possible during a specified part of the day. Comments Note that FHIR strings SHALL NOT exceed 1MB in size 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

ContactInformation		0..*
ContactInformation.Type	CodeableConcept	0..1
ContactInformation.Value	string	1..1
ContactInformation.Use	CodeableConcept	0..1
ContactInformation.Comment	string	0..1

ContactInformation
Definition	Root concept of the ContactInformation partial information model. This root concept contains all data elements of the ContactInformation partial information model.
Cardinality	0...*
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
ContactInformation.id
Definition	Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality	0...1
Type	string
Mappings	rim: n/a
ContactInformation.extension
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.
Cardinality	0...*
Type	Extension
Alias	extensions, user content
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.
Slicing	Unordered, Open, by url(Value)
Invariants	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
ContactInformation.Type
Definition	The type of contact information.
Cardinality	0...1
Type	CodeableConcept
Binding	Telecommunications form for contact point. ContactPointSystem (required)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
ContactInformation.Value
Definition	The actual contact information details.
Cardinality	1...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a
ContactInformation.Use
Definition	Purpose or use of the contact information. For example whether it is a private or business telephone number.
Cardinality	0...1
Type	CodeableConcept
Binding	Use of contact point. ContactPointUse (required)
Comments	Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
ContactInformation.Comment
Definition	Explanation about the contact information and how to use it. It can be indicated, for example, that a telephone number concerns a department number (for healthcare professionals) or that availability by phone is only possible during a specified part of the day.
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim: n/a

Example instances

ContactInformation
Type	phone - Phone (code by ContactPointSystem)
Value	+3247458497
Use	mobile - Mobile (code by ContactPointUse)
Comment	Only during work hours

ContactInformation
Type	email - Email (code by ContactPointSystem)
Value	BelleUlijn@mail.Be
Use	work - Work (code by ContactPointUse)
Comment

zib ContactInformation-v1.2 difference

This CBB differs significantly from the zib because the zib model is deemed overly complex, too Dutch-specific, and contains unsuited terminology. Mapping the zib model to the FHIR standard is also far from trivial and results in a far too complex mapping. Therefore, the CBB is wholly redesigned based on what is implemented internationally and in Belgium by looking at the FHIR datatype and eHealth core profiles. The new model replaces the containers for phone numbers and email addresses with elements on the root that can capture both. As a result, the cardinality of this partial model in CBBs that includes contact information is widened from 0..1 to 0..* to ensure that all contact information can be captured.

Concept	Category	Description
`TelephoneNumbers`	element	Removed container to simplify CBB and align contactInformation into one generic model.
`EmailAddresses`	element	Removed container to simplify CBB and align contactInformation into one generic model.
`Type`	element	Renamed element `TelecomType` to `type` to make CBB more generic.
`Type`	terminology	Replaced ValueSet NumberType with FHIR ValueSet contact-point-system to make the CBB more generic.
`Value`	element	Replaced elements `TelephoneNumber` and `EmailAddress` with this element to make the CBB more generic.
`Use`	element	Replaced element `NumberType` and `EmailAddressType` with this element to make the CBB more generic.
`Use`	terminology	As in the original `NumberType` and `EmailAddressType`, two different ValueSet are used, we replaced both ValueSets with the FHIR ValueSet contact-point-use.
`Comment`	textual	Removed spelling mistake (Professionnels to Professionals) (zib ticket 1807).

Terminology Bindings

Path	Name	Strength	URL
Type	contact-point-system	required	http://hl7.org/fhir/ValueSet/contact-point-system
Use	contact-point-use	required	http://hl7.org/fhir/ValueSet/contact-point-use