HdBe-LifeStance
WARNING This page contains a draft CBB, as raw output from the zib export and automatic conversion to CBB. It requires thorough review and adaption to the Belgian realm. This CBB is merely added for informative use.
CBB | Description | Status |
---|---|---|
HdBe-LifeStance | Patient’s life stance and/or religion. PurposeLife stance may have implications for treatment and care, such as in instructions for treatment, diet, or mental care. | draft |
LifeStance | LifeStance | ||
id | 0..1 | string | |
extension | I | 0..* | Extension |
LifeStance | 1..1 | CodeableConceptBinding | |
Comment | 0..1 | string |
LifeStance | |
Definition | Root concept of the LifeStance information model. This root concept contains all data elements of the LifeStance information model. |
Cardinality | 0...* |
Invariants |
|
Mappings |
|
LifeStance.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 |
|
LifeStance.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 |
|
LifeStance.LifeStance | |
Definition | Patient’s life stance and/or religion. |
Cardinality | 1...1 |
Type | CodeableConcept |
Binding | LifeStance 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 |
|
LifeStance.Comment | |
Definition | Explanation that reflects the importance of religion or life stance for the patient, for example how much value the patient attaches to rituals and the like. |
Cardinality | 0...1 |
Type | string |
Comments | Note that FHIR strings SHALL NOT exceed 1MB in size |
Invariants |
|
Mappings |
|
Example instances
[CBB name] | |
---|---|
[Concept name ] | [example value] |
// example of NameInformation
## Example instances
| NameInformation | |
|----------------------|-------------------|
| FirstNames | Johanna Petronella Maria
| Initials | J.P.M.
| GivenName | Jo
| NameUsage | Geslachtsnaam partner gevolgd door eigen geslachtsnaam
| LastName.Prefix | van
| LastName.LastName | Putten
| LastNamePartner.PartnerPrefix | van der
| LastNamePartner.PartnerLastName | Giessen
| Titles |
zib [zib name + version](https://zibs.nl/wiki/[zib name + version(release)]) difference
Concept | Category | Description |
---|---|---|
[element.path] |
[category of change] | [Description of change]([Reference to ticket/issue/zulip chat using MarkDown link]) |
Terminology Bindings
Path | Name | Strength | URL |
---|---|---|---|
LifeStance | LifeStance | extensible | https://fhir.healthdata.be/ValueSet/LifeStance |