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

HdBe-Problème

CBB	Concept	Status
HdBe-Problem	Un problème décrit une situation concernant la santé et/ou le bien-être d'une personne. Cette situation peut être décrite par la personne concernée elle-même (le patient) (sous la forme d'une plainte) ou par son professionnel de la santé (sous la forme d'un diagnostic, par exemple). La situation peut amener à une politique diagnostique ou thérapeutique. Un problème comprend toutes sortes de renseignements médicaux ou infirmiers qui représentent un problème de santé. Un problème peut représenter divers types de problèmes de santé: Une plainte, constatation faite par le patient : une perception subjective, ressentie comme négative, de sa santé par le patient. Exemples : maux d'estomac, amnésie. Un symptôme : une perception par le patient ou à son sujet susceptible d'indiquer une certaine maladie. Exemples : fièvre, sang dans les selles, taches blanches au niveau du palais. Un diagnostic : interprétation médicale des plaintes et constatations. Exemples : Diabète sucré de type II, pneumonie, syndrome hémolytique urémique. Une limitation fonctionnelle : une réduction des possibilités fonctionnelles. Exemples : mobilité réduite, aide requise pour s'habiller. Une complication : tout diagnostic considéré par le professionnel de la santé comme un résultat imprévu et non désiré de l'action médicale. Exemples : infections postopératoires des plaies, perte d'audition due à l'utilisation d'antibiotiques. Purpose Une vue d'ensemble des problèmes de santé d'un patient a pour but d'informer tous les professionnels de la santé impliqués dans les soins du patient de l'état de santé actuel et passé du patient. Elle fournit des informations sur les problèmes qui nécessitent une action médicale, ceux qui sont sous contrôle et ceux qui ne sont plus d'actualité. La vue d'ensemble des problèmes fournit également directement le contexte médical de la médication administrée et des procédures suivies. La vue d'ensemble favorise une poursuite efficace et ciblée des soins du patient. Une liste complète des problèmes est importante pour l'aide à la décision automatisée et la détermination des contre-indications.	active

CBB

Concept

Status

HdBe-Problem

Un problème décrit une situation concernant la santé et/ou le bien-être d'une personne. Cette situation peut être décrite par la personne concernée elle-même (le patient) (sous la forme d'une plainte) ou par son professionnel de la santé (sous la forme d'un diagnostic, par exemple). La situation peut amener à une politique diagnostique ou thérapeutique. Un problème comprend toutes sortes de renseignements médicaux ou infirmiers qui représentent un problème de santé. Un problème peut représenter divers types de problèmes de santé:

Une plainte, constatation faite par le patient : une perception subjective, ressentie comme négative, de sa santé par le patient. Exemples : maux d'estomac, amnésie.
Un symptôme : une perception par le patient ou à son sujet susceptible d'indiquer une certaine maladie. Exemples : fièvre, sang dans les selles, taches blanches au niveau du palais.
Un diagnostic : interprétation médicale des plaintes et constatations. Exemples : Diabète sucré de type II, pneumonie, syndrome hémolytique urémique.
Une limitation fonctionnelle : une réduction des possibilités fonctionnelles. Exemples : mobilité réduite, aide requise pour s'habiller.
Une complication : tout diagnostic considéré par le professionnel de la santé comme un résultat imprévu et non désiré de l'action médicale. Exemples : infections postopératoires des plaies, perte d'audition due à l'utilisation d'antibiotiques.

Purpose

Une vue d'ensemble des problèmes de santé d'un patient a pour but d'informer tous les professionnels de la santé impliqués dans les soins du patient de l'état de santé actuel et passé du patient. Elle fournit des informations sur les problèmes qui nécessitent une action médicale, ceux qui sont sous contrôle et ceux qui ne sont plus d'actualité. La vue d'ensemble des problèmes fournit également directement le contexte médical de la médication administrée et des procédures suivies. La vue d'ensemble favorise une poursuite efficace et ciblée des soins du patient. Une liste complète des problèmes est importante pour l'aide à la décision automatisée et la détermination des contre-indications.

active

Problem			Problem	Element id Problem Short description Problème Definition Concept root du modèle d'information Problème.Un problème décrit une situation concernant la santé et/ou le bien-être d'une personne. Cette situation peut être décrite par le patient lui-même (sous la forme d'une plainte) ou par son professionnel de la santé (sous la forme d'un diagnostic par exemple). Data type Problem Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Problem.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Problem.extension Short description Additional content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
ProblemType		0..1	CodeableConceptBinding	Element id Problem.ProblemType Short description TypeProblème Definition Le type de problème ; voir la description du concept. 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. Data type CodeableConcept Binding Codes TypeProblème ProblemType (extensible) Constraints 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
ProblemName		1..1	CodeableConceptBinding	Element id Problem.ProblemName Short description NomProblème Definition Le nom du problème définit le problème. 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. Data type CodeableConcept Binding Codes NomProblème ProblemName (extensible) Constraints 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
FurtherSpecificationProblemName		0..1	string	Element id Problem.FurtherSpecificationProblemName Short description NomProblèmeSpécificationSupplémentaire Definition Spécification supplémentaire du nom du problème lorsqu'il est enregistré via un thésaurus ou un système de code dans lequel le niveau de détail requis n'est pas (encore) disponible. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ProblemAnatomicalLocation		0..1	BackboneElement	Element id Problem.ProblemAnatomicalLocation Short description LocalisationAnatomiqueProblème Definition La localisation anatomique qui est au centre du problème. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id Problem.ProblemAnatomicalLocation.id Short description Unique id for inter-element referencing Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Data type string Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id Problem.ProblemAnatomicalLocation.extension Short description Additional content defined by implementations Alternate names extensions, user content 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. 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. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints 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
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id Problem.ProblemAnatomicalLocation.modifierExtension Short description Extensions that cannot be ignored even if unrecognized Alternate names extensions, user content, modifiers 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). 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. Data type Extension Constraints 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
Location		0..1	CodeableConceptBinding	Element id Problem.ProblemAnatomicalLocation.Location Short description Localisation Definition Localisation sur/dans le corps. 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. Data type CodeableConcept Binding Codes Localisation Location (required) Constraints 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
Laterality		0..1	CodeableConceptBinding	Element id Problem.ProblemAnatomicalLocation.Laterality Short description Latéralité Definition La latéralité ajoute à la localisation anatomique des informations concernant le site physique, par ex. à gauche. 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. Data type CodeableConcept Binding Codes Latéralité Laterality (required) Constraints 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
ProblemStartDate		0..1	dateTime	Element id Problem.ProblemStartDate Short description DateDébutProblème Definition Apparition du symptôme, de la plainte, de la limitation fonctionnelle, de la complication ou date du diagnostic. Une date ‘vague’, telle que l'année uniquement ou le mois et l'année, est autorisée. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ProblemEndDate		0..1	dateTime	Element id Problem.ProblemEndDate Short description DateFinProblème Definition La date à laquelle le trouble auquel s'applique le problème est considéré comme n'étant plus présent. Cette date ne doit pas être identique à la date du changement de statut du problème. Une date ‘vague’, telle que l'année uniquement ou le mois et l'année, est autorisée. Data type dateTime Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a
ProblemStatus		0..1	CodeableConceptBinding	Element id Problem.ProblemStatus Short description StatutProblème Definition Le statut du problème décrit l'état du problème : Les problèmes actifs sont des problèmes dont le patient présente des symptômes ou pour lesquels des preuves existent. Les problèmes ayant le statut ‘Inactif’ font référence à des problèmes qui n'affectent plus le patient ou dont il n'existe plus de preuve d'existence. 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. Data type CodeableConcept Binding Codes StatutProblème ProblemStatus (required) Constraints 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
VerificationStatus		0..1	CodeableConceptBinding	Element id Problem.VerificationStatus Short description StatutVérification Definition Statut clinique du problème ou diagnostic. 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. Data type CodeableConcept Binding Codes StatutVérification VerificationStatus (required) Constraints 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
Comment		0..1	string	Element id Problem.Comment Short description Commentaire Definition Commentaire de celui qui a déterminé ou mis à jour le problème. Comments Note that FHIR strings SHALL NOT exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() or (children().count() > id.count())` Mappings rim: n/a

Problem		0..*
Problem.ProblemType	CodeableConcept	0..1
Problem.ProblemName	CodeableConcept	1..1
Problem.FurtherSpecificationProblemName	string	0..1
Problem.ProblemAnatomicalLocation	BackboneElement	0..1
Problem.ProblemAnatomicalLocation.Location	CodeableConcept	0..1
Problem.ProblemAnatomicalLocation.Laterality	CodeableConcept	0..1
Problem.ProblemStartDate	dateTime	0..1
Problem.ProblemEndDate	dateTime	0..1
Problem.ProblemStatus	CodeableConcept	0..1
Problem.VerificationStatus	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 themselves (in the form of a complaint) or by their health professional (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	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.ProblemType
Definition	The type of problem; see the concept description.
Cardinality	0...1
Type	CodeableConcept
Binding	ProblemType codes ProblemType (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.ProblemName
Definition	The problem name defines the problem.
Cardinality	1...1
Type	CodeableConcept
Binding	ProblemName codes ProblemName (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.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.
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.ProblemAnatomicalLocation
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.ProblemAnatomicalLocation.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	rim: n/a
Problem.ProblemAnatomicalLocation.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.ProblemAnatomicalLocation.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.ProblemAnatomicalLocation.Location
Definition	Location on/in the body.
Cardinality	0...1
Type	CodeableConcept
Binding	Location codes Location (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.ProblemAnatomicalLocation.Laterality
Definition	Laterality adds information about body site to the anatomic location, e.g. left.
Cardinality	0...1
Type	CodeableConcept
Binding	Laterality codes Laterality (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.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.
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.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.
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.ProblemStatus
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	0...1
Type	CodeableConcept
Binding	ProblemStatus codes ProblemStatus (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.VerificationStatus
Definition	Clinical status of the problem or the diagnosis.
Cardinality	0...1
Type	CodeableConcept
Binding	VerificationStatus codes VerificationStatus (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

problem
ProblemType	282291009 - Diagnosis interpretation (code by SNOMED CT)
ProblemName	4241002 - Listeriosis (code by SNOMED CT)
FurtherSpecificationProblemName
ProblemAnatomicalLocation	---
ProblemAnatomicalLocation.Location
ProblemAnatomicalLocation.Laterality
ProblemStartDate	2022-05-03T12:00:00
ProblemEndDate
ProblemStatus	55561003 - Active (code by SNOMED CT)
VerificationStatus	410605003 - Confirmed present (code by SNOMED CT)
Comment

zib Problem-v4.4 difference

Concept	Category	Description
`ProblemType`	terminology	Changed SNOMED code 116223007 (Complication) with 263718001 (Complication) because 116223007 is not included in the International Edition of SNOMED.
`ProblemName`	terminology	Removed all CodeSystems execpt SNOMED CT and changed binding strenght from required to extensible.
`ProblemStatus`	cardinality	Relaxed cardinality from 1..1 to 0..1 because it is very likely that the status is not always known. Also, the FHIR spec does not make a status mandatory.
`VerificationStatus`	terminology	Replaced NullFlavor Unknown code with SNOMED CT Unknown code.
`Problem`	textual	Replaced 'himself' by 'themselves'.
description.concept	textual	Put a period after 'Examples: stomach ache, amnesia'.
description.concept	textual	Put a period after 'roof of the mouth'.

Terminology Bindings

Path	Name	Strength	URL
ProblemType	ProblemType	extensible	https://fhir.healthdata.be/ValueSet/ProblemType
ProblemName	ProblemName	extensible	https://fhir.healthdata.be/ValueSet/ProblemName
ProblemAnatomicalLocation.Location	Location	required	https://fhir.healthdata.be/ValueSet/Location
ProblemAnatomicalLocation.Laterality	Laterality	required	https://fhir.healthdata.be/ValueSet/Laterality
ProblemStatus	ProblemStatus	required	https://fhir.healthdata.be/ValueSet/ProblemStatus
VerificationStatus	VerificationStatus	required	https://fhir.healthdata.be/ValueSet/VerificationStatus