HdBe-Problem

Profile	Status	URL
HdBe-Problem	draft	https://fhir.healthdata.be/StructureDefinition/LogicalModel/HdBe-Problem

problem		problem	There are no (further) constraints on this element Element Id problem Short description Problem Definition Root concept of the Problem information model. A problem describes a situation with regard to an individual’s health and/or welfare. This situation can be described by the patient himselve (in the form of a complaint) or by their healthprofessional (in the form of a diagnosis, for example). Data Type problem
problem_type	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element Id problem.problem_type Short description ProblemType Definition The type of problem; see the concept description. Data Type CodeableConcept Binding ProblemType codes ProbleemType (extensible)
problem_name	1..1	CodeableConceptBinding	There are no (further) constraints on this element Element Id problem.problem_name Short description ProblemName Definition The problem name defines the problem. Depending on the setting, different code systems can be used. The ProblemNameCodelist provides an overview of the possible code systems. Data Type CodeableConcept Binding ProblemName codes ProbleemNaam (required)
further_specification_problem_name	0..1	string	There are no (further) constraints on this element Element Id problem.further_specification_problem_name Short description FurtherSpecificationProblemName Definition Further specification of problem name when it is recorded via a thesaurus or code system in which the required level of detail is not (yet) available. Data Type string
problem_anatomical_location	0..1	BackboneElement	There are no (further) constraints on this element Element Id problem.problem_anatomical_location Short description ProblemAnatomicalLocation Definition Anatomical location which is the focus of the problem. Data Type BackboneElement
location	0..1	CodeableConcept	There are no (further) constraints on this element Element Id problem.problem_anatomical_location.location Short description Location Definition Localisation on/in the body. Data Type CodeableConcept
laterality	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element Id problem.problem_anatomical_location.laterality Short description Laterality Definition Laterality adds information about body site to the anatomic location, e.g. left. Data Type CodeableConcept Binding Laterality codes Lateraliteit (required)
problem_start_date	0..1	dateTime	There are no (further) constraints on this element Element Id problem.problem_start_date Short description ProblemStartDate Definition Onset of the symptom, complaint, functional limitation, complication or date of diagnosis. A ‘vague’ date, such as only the year or the month and the year, is permitted. Data Type dateTime
problem_end_date	0..1	dateTime	There are no (further) constraints on this element Element Id problem.problem_end_date Short description ProblemEndDate Definition Date on which the disorder to which the problem applies, is considered not to be present anymore.This datum needs not to be the same as the date of the change in problem status. A ‘vague’ date, such as only the year or the month and the year, is permitted. Data Type dateTime
problem_status	1..1	CodeableConceptBinding	There are no (further) constraints on this element Element Id problem.problem_status Short description ProblemStatus Definition The problem status describes the condition of the problem: Active problems are problems of which the patient experiences symptoms or for which evidence exists. Problems with the status 'Inactive' refer to problems that don't affect the patient anymore or that of which there is no evidence of existence anymore. Data Type CodeableConcept Binding ProblemStatus codes ProbleemStatus (required)
verification_status	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element Id problem.verification_status Short description VerificationStatus Definition Clinical status of the problem or the diagnosis. Data Type CodeableConcept Binding VerificationStatus codes VerificatieStatus (required)
comment	0..1	string	There are no (further) constraints on this element Element Id problem.comment Short description Comment Definition Comment by the one who determined or updated the Problem. Data Type string

problem		0..*
problem.problem_type	CodeableConcept	0..1
problem.problem_name	CodeableConcept	1..1
problem.further_specification_problem_name	string	0..1
problem.problem_anatomical_location	BackboneElement	0..1
problem.problem_anatomical_location.location	CodeableConcept	0..1
problem.problem_anatomical_location.laterality	CodeableConcept	0..1
problem.problem_start_date	dateTime	0..1
problem.problem_end_date	dateTime	0..1
problem.problem_status	CodeableConcept	1..1
problem.verification_status	CodeableConcept	0..1
problem.comment	string	0..1

problem
Definition	Root concept of the Problem information model. A problem describes a situation with regard to an individual’s health and/or welfare. This situation can be described by the patient himselve (in the form of a complaint) or by their healthprofessional (in the form of a diagnosis, for example).
Cardinality	0...*
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a
problem.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
problem.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
problem.problem_type
Definition	The type of problem; see the concept description.
Cardinality	0...1
Type	CodeableConcept
Binding	ProblemType codes ProbleemType (extensible)
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	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a v2:CE/CNE/CWE rim:CD orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
problem.problem_name
Definition	The problem name defines the problem. Depending on the setting, different code systems can be used. The ProblemNameCodelist provides an overview of the possible code systems.
Cardinality	1...1
Type	CodeableConcept
Binding	ProblemName codes ProbleemNaam (required)
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	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a v2:CE/CNE/CWE rim:CD orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
problem.further_specification_problem_name
Definition	Further specification of problem name when it is recorded via a thesaurus or code system in which the required level of detail is not (yet) available.
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a
problem.problem_anatomical_location
Definition	Anatomical location which is the focus of the problem.
Cardinality	0...1
Type	BackboneElement
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a
problem.problem_anatomical_location.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
problem.problem_anatomical_location.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
problem.problem_anatomical_location.modifierExtension
Definition	May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Cardinality	0...*
Type	Extension
Modifier	True
Summary	True
Alias	extensions, user content, modifiers
Requirements	Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.
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.
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
problem.problem_anatomical_location.location
Definition	Localisation on/in the body.
Cardinality	0...1
Type	CodeableConcept
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	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a v2:CE/CNE/CWE rim:CD orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
problem.problem_anatomical_location.laterality
Definition	Laterality adds information about body site to the anatomic location, e.g. left.
Cardinality	0...1
Type	CodeableConcept
Binding	Laterality codes Lateraliteit (required)
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	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a v2:CE/CNE/CWE rim:CD orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
problem.problem_start_date
Definition	Onset of the symptom, complaint, functional limitation, complication or date of diagnosis. A ‘vague’ date, such as only the year or the month and the year, is permitted.
Cardinality	0...1
Type	dateTime
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a
problem.problem_end_date
Definition	Date on which the disorder to which the problem applies, is considered not to be present anymore.This datum needs not to be the same as the date of the change in problem status. A ‘vague’ date, such as only the year or the month and the year, is permitted.
Cardinality	0...1
Type	dateTime
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a
problem.problem_status
Definition	The problem status describes the condition of the problem: 1. Active problems are problems of which the patient experiences symptoms or for which evidence exists. 1. Problems with the status 'Inactive' refer to problems that don't affect the patient anymore or that of which there is no evidence of existence anymore.
Cardinality	1...1
Type	CodeableConcept
Binding	ProblemStatus codes ProbleemStatus (required)
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	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a v2:CE/CNE/CWE rim:CD orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
problem.verification_status
Definition	Clinical status of the problem or the diagnosis.
Cardinality	0...1
Type	CodeableConcept
Binding	VerificationStatus codes VerificatieStatus (required)
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	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a v2:CE/CNE/CWE rim:CD orim:fhir:CodeableConcept rdfs:subClassOf dt:CD
problem.comment
Definition	Comment by the one who determined or updated the Problem.
Cardinality	0...1
Type	string
Comments	Note that FHIR strings SHALL NOT exceed 1MB in size
Invariants	ele-1:All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())`
Mappings	rim:n/a

Example instances

[CBB name]
[Concept name ]	[example value]

// example of NameInformation

## Example instances

| name_information      |                   |
|----------------------|-------------------|
| first_names | Johanna Petronella Maria   
| initials | J.P.M. 
| given_name | Jo 
| name_usage | Geslachtsnaam partner gevolgd door eigen geslachtsnaam
| last_name.prefix | van
| last_name.last_name | Putten
| last_name_partner.partner_prefix | van der
| last_name_partner.partner_last_name | 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
problem_type	ProbleemType	extensible	https://fhir.healthdata.be/ValueSet/ProbleemType
problem_name	ProbleemNaam	required	https://fhir.healthdata.be/ValueSet/ProbleemNaam
problem_anatomical_location.laterality	Lateraliteit	required	https://fhir.healthdata.be/ValueSet/Lateraliteit
problem_status	ProbleemStatus	required	https://fhir.healthdata.be/ValueSet/ProbleemStatus
verification_status	VerificatieStatus	required	https://fhir.healthdata.be/ValueSet/VerificatieStatus