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

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. Purpose Life stance may have implications for treatment and care, such as in instructions for treatment, diet, or mental care.	draft

CBB

Description

Status

HdBe-LifeStance

Patient’s life stance and/or religion.

Purpose

Life stance may have implications for treatment and care, such as in instructions for treatment, diet, or mental care.

draft

LifeStanceRc

LifeStance

1..1

CodeableConceptBinding

Comment

0..1

string

LifeStanceRc		0..*
LifeStanceRc.LifeStance	CodeableConcept	1..1
LifeStanceRc.Comment	string	0..1

LifeStance
Definition	Base definition for all elements in a resource.
Cardinality	0...*
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a
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	System.String
Mappings	rim:n/a
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	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
LifeStance.LifeStanceRc
Definition	Root concept of the LifeStance information model. This root concept contains all data elements of the LifeStance information model.
Cardinality	0...*

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	Levensovertuiging	extensible	https://fhir.healthdata.be/ValueSet/Levensovertuiging