HdBe-ContactInformation
CBB | Description | Status |
---|---|---|
HdBe-ContactInformation | Contact information includes a person's telephone numbers and e-mail addresses. This is a partial information model. PurposeContact information is used to contact a person. | active |
ContactInformation | ContactInformation | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
Type | 0..1 | CodeableConceptBinding | |
Value | 1..1 | string | |
Use | 0..1 | CodeableConceptBinding | |
Comment | 0..1 | string |
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 |
|
Mappings |
|
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 |
|
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 |
|
Mappings |
|
ContactInformation.Type | |
Definition | The type of contact information. |
Cardinality | 0...1 |
Type | CodeableConcept |
Binding | Telecommunications form for contact point. |
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 |
|
Mappings |
|
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 |
|
Mappings |
|
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. |
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 |
|
Mappings |
|
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 |
|
Mappings |
|
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 |