HdBe-ContactPerson
CBB | Description | Status |
---|---|---|
HdBe-ContactPerson | A contact person is a person not being a healthcare professional who is involved in the patient’s care, such as family members, caregivers, mental caretakers, guardians and legal representatives. In addition to identification information such as the name, address and contact information can also be entered. The relationship to the patient and the role this person has can be entered as well. PurposeRecording the relevant data for identification of contacts and other persons involved in the patient's care. | active |
ContactPerson | ContactPerson | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
NameInformation | 0..1 | HdBe-NameInformation | |
ContactInformation | 0..* | HdBe-ContactInformation | |
AddressInformation | 0..* | HdBe-AddressInformation | |
Role | 0..* | CodeableConceptBinding | |
Relationship | 0..* | CodeableConceptBinding |
ContactPerson | 0..* | |
ContactPerson.NameInformation | HdBe-NameInformation | 0..1 |
ContactPerson.ContactInformation | HdBe-ContactInformation | 0..* |
ContactPerson.AddressInformation | HdBe-AddressInformation | 0..* |
ContactPerson.Role | CodeableConcept | 0..* |
ContactPerson.Relationship | CodeableConcept | 0..* |
ContactPerson | |
Definition | Root concept of the ContactPerson information model. This root concept contains all data elements of the ContactPerson information model. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
ContactPerson.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 |
|
ContactPerson.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 |
|
ContactPerson.NameInformation | |
Definition | Full name of the contact person. |
Cardinality | 0...1 |
Type | HdBe-NameInformation |
Invariants |
|
Mappings |
|
ContactPerson.ContactInformation | |
Definition | The contact person’s telephone number and/or e-mail address. |
Cardinality | 0...* |
Type | HdBe-ContactInformation |
Invariants |
|
Mappings |
|
ContactPerson.AddressInformation | |
Definition | Contact person’s address information. |
Cardinality | 0...* |
Type | HdBe-AddressInformation |
Invariants |
|
Mappings |
|
ContactPerson.Role | |
Definition | Defines the role of the contact person in relation to the patient. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Role codes |
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 |
|
ContactPerson.Relationship | |
Definition | Defines the contact person’s familial relationship to the patient. |
Cardinality | 0...* |
Type | CodeableConcept |
Binding | Relationship codes |
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 |
|
Example instances
ContactPerson | |
---|---|
NameInformation | reference to NameInformation (Berend Ulijn) |
AddressInformation | reference to AddressInformation (Rue de Boneffe 422) |
ContactInformation | reference to ContactInformation (+3246258140; BerendUlijn@mail.Be) |
Role | 70862002 - Contact person (code by SNOMED CT) |
Relationship | 127849001 - Husband (code by SNOMED CT) |
zib ContactPerson-v3.4 difference
Concept | Category | Description |
---|---|---|
ContactPerson |
naming | Replaced the root conceptname from contact to contactPerson, as the use is not consistent (zib ticket #1738). |
... | textual | Replaced the term contact with the term contact person at several locations (zib ticket #1738). |
ContactInformation |
cardinality | Loosened cardinality from 0..1 to 0..* based on the changes made to the CBB ConctactInformation. Widening the cardinality here allows for capturing all contact information necessary. |
Role |
terminology | Replaced Role valueset values to a SNOMED descendent-of 125676002 (Person). Also included CodeSystem-Role into the valueset. |
Relationship |
terminology | Replaced Relationship valueset values to a SNOMED descendent-of 303071001 (Person in the family). Also included CodeSystem-Relationship into the valueset. |
Terminology Bindings
Path | Name | Strength | URL |
---|---|---|---|
Role | Role | extensible | https://fhir.healthdata.be/ValueSet/Role |
Relationship | Relationship | extensible | https://fhir.healthdata.be/ValueSet/Relationship |