HdBe-ContactPerson
Profile | Description | Status | URL |
---|---|---|---|
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. | draft | https://fhir.healthdata.be/StructureDefinition/HdBe-ContactPerson |
Instructions |
---|
Whereas the CBB ContactPerson includes all (non-healthcare professional) persons that are involved in the care for a patient, FHIR distinguishes two use cases for these persons:
If a person is both a related person and a contact person, then some data duplication is inevitable. |
RelatedPerson | I | RelatedPerson | Element IdRelatedPerson Contact Alternate namesContactpersoon DefinitionInformation about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. Whereas the CBB ContactPerson includes all (non-healthcare professional) persons that are involved in the care for a patient, FHIR distinguishes two use cases for these persons:
If a person is both a related person and a contact person, then some data duplication is inevitable.
| |
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element IdRelatedPerson.identifier A human identifier for this person DefinitionIdentifier for a person within a particular scope. People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.
|
active | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element IdRelatedPerson.active Whether this related person's record is in active use DefinitionWhether this related person record is in active use. Need to be able to mark a related person record as not to be used, such as if it was created in error. This element is labeled as a modifier because it may be used to mark that the resource was created in error.
|
patient | Σ I | 1..1 | Reference(Patient | HdBe Patient) | Element IdRelatedPerson.patient The patient this person is related to DefinitionThe patient this person is related to. We need to know which patient this RelatedPerson is related to. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | HdBe Patient) Constraints
|
relationship | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship The nature of the relationship DefinitionThe nature of the relationship between a patient and the related person. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. Unordered, Open, by $this(Value) BindingThe nature of the relationship between a patient and the related person. PatientRelationshipType (preferred)Constraints
|
role | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship:role Role Alternate namesRol DefinitionDefines the role of the contact person in relation to the patient. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. RolCodelijst Role (required)Constraints
|
relationship | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship:relationship Relationship Alternate namesRelatie DefinitionDefines the contact person’s familial relationship to the patient. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. RelatieCodelijst Relationship (required)Constraints
|
name | Σ | 0..* | HumanName | Element IdRelatedPerson.name NameInformation Alternate namesNaamgegevens DefinitionFull name of the contact. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. Unordered, Open, by use(Value) Constraints
|
nameInformation | Σ I | 0..2 | HdBe NameInformation | Element IdRelatedPerson.name:nameInformation NameInformation Alternate namesNaamgegevens DefinitionThis slice represents the person's official name information, including given names, last name and possibly the partner's last name. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. This Note 1: The CBB cannot be represented straightforward in FHIR. Especially note the guidance on Note 2: This element should only contain a person's official names. The GivenName concept is represented in another Note 3: The examples illustrate how the CBB is mapped to FHIR.
|
nameInformation-GivenName | Σ | 0..* | HdBe NameInformation.GivenName | Element IdRelatedPerson.name:nameInformation-GivenName Name of a human - parts and usage DefinitionThis slice represents the name information normally used to address the person. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. This Note 1: This element should only contain a person's unofficial name. The official names are represented in one or more other Note 2: The examples illustrate how the CBB is mapped to FHIR. HdBe NameInformation.GivenName Constraints
|
telecom | Σ I | 0..* | HdBe ContactInformation | Element IdRelatedPerson.telecom ContactInformation Alternate namesContactpunten, Contactgegevens DefinitionThe contact person’s telephone number and/or e-mail address. People have (primary) ways to contact them in some way such as phone, email. Implementation of the CBB ContactInformation. Please note that this profile differs significantly from the zib ContactInformation because the zib model is deemed overly complex, too Dutch-specific, and contains unsuited terminology. The mapping from zib to FHIR is not trivial and results in too complex mapping. Therefore, the CBB is redesigned based on what is implemented internationally and in Belgium by looking at the FHIR data type 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. Therefore, no need for two profiles, slicing in the host profiles and no ConceptMaps.
|
gender | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdRelatedPerson.gender male | female | other | unknown DefinitionAdministrative Gender - the gender that the person is considered to have for administration and record keeping purposes. Needed for identification of the person, in combination with (at least) name and birth date. Note that FHIR strings SHALL NOT exceed 1MB in size The gender of a person used for administrative purposes. AdministrativeGender (required)Constraints
|
birthDate | Σ | 0..1 | date | There are no (further) constraints on this element Element IdRelatedPerson.birthDate The date on which the related person was born DefinitionThe date on which the related person was born.
|
address | Σ | 0..* | HdBe AddressInformation | Element IdRelatedPerson.address AddressInformation Alternate namesAdresgegevens DefinitionContact person’s address information. Need to keep track where the related person can be contacted per postal mail or visited. Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
|
photo | I | 0..* | Attachment | There are no (further) constraints on this element Element IdRelatedPerson.photo Image of the person DefinitionImage of the person. Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too. When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
|
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdRelatedPerson.period Period of time that this relationship is considered valid DefinitionThe period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown. 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.
|
communication | 0..* | BackboneElement | There are no (further) constraints on this element Element IdRelatedPerson.communication A language which may be used to communicate with about the patient's health DefinitionA language which may be used to communicate with about the patient's health. If a related person does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest. If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
| |
language | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdRelatedPerson.communication.language The language which can be used to communicate with the patient about his or her health DefinitionThe ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. 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. A human language. CommonLanguages (preferred)Constraints
| |
preferred | 0..1 | boolean | There are no (further) constraints on this element Element IdRelatedPerson.communication.preferred Language preference indicator DefinitionIndicates whether or not the patient prefers this language (over other languages he masters up a certain level). People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. This language is specifically identified for communicating healthcare information.
|
RelatedPerson | I | RelatedPerson | Element IdRelatedPerson Contact Alternate namesContactpersoon DefinitionInformation about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. Whereas the CBB ContactPerson includes all (non-healthcare professional) persons that are involved in the care for a patient, FHIR distinguishes two use cases for these persons:
If a person is both a related person and a contact person, then some data duplication is inevitable.
| |
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element IdRelatedPerson.identifier A human identifier for this person DefinitionIdentifier for a person within a particular scope. People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.
|
active | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element IdRelatedPerson.active Whether this related person's record is in active use DefinitionWhether this related person record is in active use. Need to be able to mark a related person record as not to be used, such as if it was created in error. This element is labeled as a modifier because it may be used to mark that the resource was created in error.
|
patient | Σ I | 1..1 | Reference(Patient | HdBe Patient) | Element IdRelatedPerson.patient The patient this person is related to DefinitionThe patient this person is related to. We need to know which patient this RelatedPerson is related to. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | HdBe Patient) Constraints
|
relationship | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship The nature of the relationship DefinitionThe nature of the relationship between a patient and the related person. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. Unordered, Open, by $this(Value) BindingThe nature of the relationship between a patient and the related person. PatientRelationshipType (preferred)Constraints
|
role | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship:role Role Alternate namesRol DefinitionDefines the role of the contact person in relation to the patient. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. RolCodelijst Role (required)Constraints
|
relationship | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship:relationship Relationship Alternate namesRelatie DefinitionDefines the contact person’s familial relationship to the patient. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. RelatieCodelijst Relationship (required)Constraints
|
name | Σ | 0..* | HumanName | Element IdRelatedPerson.name NameInformation Alternate namesNaamgegevens DefinitionFull name of the contact. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. Unordered, Open, by use(Value) Constraints
|
nameInformation | Σ I | 0..2 | HdBe NameInformation | Element IdRelatedPerson.name:nameInformation NameInformation Alternate namesNaamgegevens DefinitionThis slice represents the person's official name information, including given names, last name and possibly the partner's last name. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. This Note 1: The CBB cannot be represented straightforward in FHIR. Especially note the guidance on Note 2: This element should only contain a person's official names. The GivenName concept is represented in another Note 3: The examples illustrate how the CBB is mapped to FHIR.
|
nameInformation-GivenName | Σ | 0..* | HdBe NameInformation.GivenName | Element IdRelatedPerson.name:nameInformation-GivenName Name of a human - parts and usage DefinitionThis slice represents the name information normally used to address the person. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. This Note 1: This element should only contain a person's unofficial name. The official names are represented in one or more other Note 2: The examples illustrate how the CBB is mapped to FHIR. HdBe NameInformation.GivenName Constraints
|
telecom | Σ I | 0..* | HdBe ContactInformation | Element IdRelatedPerson.telecom ContactInformation Alternate namesContactpunten, Contactgegevens DefinitionThe contact person’s telephone number and/or e-mail address. People have (primary) ways to contact them in some way such as phone, email. Implementation of the CBB ContactInformation. Please note that this profile differs significantly from the zib ContactInformation because the zib model is deemed overly complex, too Dutch-specific, and contains unsuited terminology. The mapping from zib to FHIR is not trivial and results in too complex mapping. Therefore, the CBB is redesigned based on what is implemented internationally and in Belgium by looking at the FHIR data type 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. Therefore, no need for two profiles, slicing in the host profiles and no ConceptMaps.
|
gender | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdRelatedPerson.gender male | female | other | unknown DefinitionAdministrative Gender - the gender that the person is considered to have for administration and record keeping purposes. Needed for identification of the person, in combination with (at least) name and birth date. Note that FHIR strings SHALL NOT exceed 1MB in size The gender of a person used for administrative purposes. AdministrativeGender (required)Constraints
|
birthDate | Σ | 0..1 | date | There are no (further) constraints on this element Element IdRelatedPerson.birthDate The date on which the related person was born DefinitionThe date on which the related person was born.
|
address | Σ | 0..* | HdBe AddressInformation | Element IdRelatedPerson.address AddressInformation Alternate namesAdresgegevens DefinitionContact person’s address information. Need to keep track where the related person can be contacted per postal mail or visited. Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
|
photo | I | 0..* | Attachment | There are no (further) constraints on this element Element IdRelatedPerson.photo Image of the person DefinitionImage of the person. Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too. When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
|
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdRelatedPerson.period Period of time that this relationship is considered valid DefinitionThe period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown. 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.
|
communication | 0..* | BackboneElement | There are no (further) constraints on this element Element IdRelatedPerson.communication A language which may be used to communicate with about the patient's health DefinitionA language which may be used to communicate with about the patient's health. If a related person does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest. If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
| |
language | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdRelatedPerson.communication.language The language which can be used to communicate with the patient about his or her health DefinitionThe ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. 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. A human language. CommonLanguages (preferred)Constraints
| |
preferred | 0..1 | boolean | There are no (further) constraints on this element Element IdRelatedPerson.communication.preferred Language preference indicator DefinitionIndicates whether or not the patient prefers this language (over other languages he masters up a certain level). People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. This language is specifically identified for communicating healthcare information.
|
RelatedPerson | I | RelatedPerson | Element IdRelatedPerson Contact Alternate namesContactpersoon DefinitionInformation about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process. Whereas the CBB ContactPerson includes all (non-healthcare professional) persons that are involved in the care for a patient, FHIR distinguishes two use cases for these persons:
If a person is both a related person and a contact person, then some data duplication is inevitable.
| |
identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element IdRelatedPerson.identifier A human identifier for this person DefinitionIdentifier for a person within a particular scope. People are known by a variety of ids. Some institutions maintain several, and most collect identifiers for exchange with other organizations concerning the patient. Examples are national person identifier and local identifier.
|
active | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element IdRelatedPerson.active Whether this related person's record is in active use DefinitionWhether this related person record is in active use. Need to be able to mark a related person record as not to be used, such as if it was created in error. This element is labeled as a modifier because it may be used to mark that the resource was created in error.
|
patient | Σ I | 1..1 | Reference(Patient | HdBe Patient) | Element IdRelatedPerson.patient The patient this person is related to DefinitionThe patient this person is related to. We need to know which patient this RelatedPerson is related to. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | HdBe Patient) Constraints
|
relationship | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship The nature of the relationship DefinitionThe nature of the relationship between a patient and the related person. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. Unordered, Open, by $this(Value) BindingThe nature of the relationship between a patient and the related person. PatientRelationshipType (preferred)Constraints
|
role | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship:role Role Alternate namesRol DefinitionDefines the role of the contact person in relation to the patient. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. RolCodelijst Role (required)Constraints
|
relationship | Σ | 0..* | CodeableConceptBinding | Element IdRelatedPerson.relationship:relationship Relationship Alternate namesRelatie DefinitionDefines the contact person’s familial relationship to the patient. We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. 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. RelatieCodelijst Relationship (required)Constraints
|
name | Σ | 0..* | HumanName | Element IdRelatedPerson.name NameInformation Alternate namesNaamgegevens DefinitionFull name of the contact. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. Names may be changed, or repudiated, or people may have different names in different contexts. Names may be divided into parts of different type that have variable significance depending on context, though the division into parts does not always matter. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems must care about name parts around the world varies widely. Unordered, Open, by use(Value) Constraints
|
nameInformation | Σ I | 0..2 | HdBe NameInformation | Element IdRelatedPerson.name:nameInformation NameInformation Alternate namesNaamgegevens DefinitionThis slice represents the person's official name information, including given names, last name and possibly the partner's last name. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. This Note 1: The CBB cannot be represented straightforward in FHIR. Especially note the guidance on Note 2: This element should only contain a person's official names. The GivenName concept is represented in another Note 3: The examples illustrate how the CBB is mapped to FHIR.
|
nameInformation-GivenName | Σ | 0..* | HdBe NameInformation.GivenName | Element IdRelatedPerson.name:nameInformation-GivenName Name of a human - parts and usage DefinitionThis slice represents the name information normally used to address the person. Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. This Note 1: This element should only contain a person's unofficial name. The official names are represented in one or more other Note 2: The examples illustrate how the CBB is mapped to FHIR. HdBe NameInformation.GivenName Constraints
|
telecom | Σ I | 0..* | HdBe ContactInformation | Element IdRelatedPerson.telecom ContactInformation Alternate namesContactpunten, Contactgegevens DefinitionThe contact person’s telephone number and/or e-mail address. People have (primary) ways to contact them in some way such as phone, email. Implementation of the CBB ContactInformation. Please note that this profile differs significantly from the zib ContactInformation because the zib model is deemed overly complex, too Dutch-specific, and contains unsuited terminology. The mapping from zib to FHIR is not trivial and results in too complex mapping. Therefore, the CBB is redesigned based on what is implemented internationally and in Belgium by looking at the FHIR data type 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. Therefore, no need for two profiles, slicing in the host profiles and no ConceptMaps.
|
gender | Σ | 0..1 | codeBinding | There are no (further) constraints on this element Element IdRelatedPerson.gender male | female | other | unknown DefinitionAdministrative Gender - the gender that the person is considered to have for administration and record keeping purposes. Needed for identification of the person, in combination with (at least) name and birth date. Note that FHIR strings SHALL NOT exceed 1MB in size The gender of a person used for administrative purposes. AdministrativeGender (required)Constraints
|
birthDate | Σ | 0..1 | date | There are no (further) constraints on this element Element IdRelatedPerson.birthDate The date on which the related person was born DefinitionThe date on which the related person was born.
|
address | Σ | 0..* | HdBe AddressInformation | Element IdRelatedPerson.address AddressInformation Alternate namesAdresgegevens DefinitionContact person’s address information. Need to keep track where the related person can be contacted per postal mail or visited. Note: address is intended to describe postal addresses for administrative purposes, not to describe absolute geographical coordinates. Postal addresses are often used as proxies for physical locations (also see the Location resource).
|
photo | I | 0..* | Attachment | There are no (further) constraints on this element Element IdRelatedPerson.photo Image of the person DefinitionImage of the person. Many EHR systems have the capability to capture an image of persons. Fits with newer social media usage too. When providing a summary view (for example with Observation.value[x]) Attachment should be represented with a brief display text such as "Signed Procedure Consent".
|
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdRelatedPerson.period Period of time that this relationship is considered valid DefinitionThe period of time during which this relationship is or was active. If there are no dates defined, then the interval is unknown. 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.
|
communication | 0..* | BackboneElement | There are no (further) constraints on this element Element IdRelatedPerson.communication A language which may be used to communicate with about the patient's health DefinitionA language which may be used to communicate with about the patient's health. If a related person does not speak the local language, interpreters may be required, so languages spoken and proficiency is an important things to keep track of both for patient and other persons of interest. If no language is specified, this implies that the default local language is spoken. If you need to convey proficiency for multiple modes, then you need multiple RelatedPerson.Communication associations. If the RelatedPerson does not speak the default local language, then the Interpreter Required Standard can be used to explicitly declare that an interpreter is required.
| |
language | 1..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdRelatedPerson.communication.language The language which can be used to communicate with the patient about his or her health DefinitionThe ISO-639-1 alpha 2 code in lower case for the language, optionally followed by a hyphen and the ISO-3166-1 alpha 2 code for the region in upper case; e.g. "en" for English, or "en-US" for American English versus "en-EN" for England English. Most systems in multilingual countries will want to convey language. Not all systems actually need the regional dialect. 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. A human language. CommonLanguages (preferred)Constraints
| |
preferred | 0..1 | boolean | There are no (further) constraints on this element Element IdRelatedPerson.communication.preferred Language preference indicator DefinitionIndicates whether or not the patient prefers this language (over other languages he masters up a certain level). People that master multiple languages up to certain level may prefer one or more, i.e. feel more confident in communicating in a particular language making other languages sort of a fall back method. This language is specifically identified for communicating healthcare information.
|
Mapping FHIR profile to CBB
Path | map | CBB |
---|---|---|
RelatedPerson.name | NameInformation | HdBe-ContactInformation |
RelatedPerson.address | AddressInformation | HdBe-ContactInformation |
RelatedPerson | ContactPerson | HdBe-ContactPerson |
RelatedPerson.relationship:role | ContactPerson.Role | HdBe-ContactPerson |
RelatedPerson.relationship:relationship | ContactPerson.Relationship | HdBe-ContactPerson |
RelatedPerson.telecom | ContactPerson.ContactInformation | HdBe-ContactPerson |
zib ContactPerson difference
Concept | Category | Description |
---|---|---|
... | textual | Replaced the term contact with the term contact person at several locations (zib ticket #1738). |
telecom |
reference | Added reference to HdBe-ContactInformation profile, which replaces the two separate HdBe-ContactInformation profiles. |
telecom |
slicing | Removed slicing as the two HdBe-ContactInformation profiles are replaced with one general HdBe-ContactInformation profile, which makes slicing unnecessary. |
relationship.role |
terminology | Replaced Role valueset values to a SNOMED descendent-of 125676002 (Person). |
relationship.relationship |
terminology | Replaced Relationship valueset values to a SNOMED descendent-of 303071001 (Person in the family). |
Terminology Bindings
Path | Name | Strength | URL | ConceptMap |
---|---|---|---|---|
RelatedPerson.relationship | Role | required | https://fhir.healthdata.be/ValueSet/Role | No bound ConceptMap |
RelatedPerson.relationship | Relationship | required | https://fhir.healthdata.be/ValueSet/Relationship | No bound ConceptMap |