Gegenereerde narrative: StructureDefinition logical-problem Naam Markeringen Kard. Type Omschrijving & constraints logical-problem 0..* Element Logical Model: Problem Elementen gedefinieerd in ancestors:@id, <a href="http://hl7.org/fhir/R4/datatypes.html#Element" title="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.">extension #xD; sourceProfile 0..1 uri source Profile #xD; targetProfile 0..1 uri target Profile #xD; identifier 0..* Identifier Problem identifiers. #xD; clinicalStatus 0..1 CodeableConcept Clinical status of the condition. #xD; verificationStatus 0..1 CodeableConcept Verification status of the asserted problem. #xD; category 0..* CodeableConcept Problem categories. #xD; problemType 0..1 CodeableConcept Dutch problem type semantics represented from the profiled category slice. #xD; severity 0..1 CodeableConcept Severity of the problem. #xD; code 0..1 CodeableConcept Problem or diagnosis code. #xD; furtherSpecificationProblemName 0..1 CodeableConcept Dutch further specification of the problem name when carried by the dedicated extension. #xD; bodySite 0..* logical-problem-body-site Affected body site details, including laterality when supplied. #xD; subject 0..1 Reference(Patient) Subject of the problem. #xD; encounter 0..1 Reference(Encounter) Encounter context in which the problem was recorded or discussed. #xD; onsetDateTime 0..1 dateTime Recorded onset date or time. #xD; onsetAge 0..1 Age Age at onset when recorded as an age. #xD; onsetPeriod 0..1 Period Onset period when recorded as a date range. #xD; onsetRange 0..1 Range Onset range when recorded as an estimated range. #xD; onsetString 0..1 string Narrative onset expression. #xD; abatementDateTime 0..1 dateTime Recorded abatement date or time. #xD; abatementAge 0..1 Age Age at abatement when recorded as an age. #xD; abatementPeriod 0..1 Period Abatement period when recorded as a date range. #xD; abatementRange 0..1 Range Abatement range when recorded as an estimated range. #xD; abatementString 0..1 string Narrative abatement expression. #xD; assertedDate 0..1 dateTime Date the condition assertion was made when populated through the eu-base asserted-date extension. #xD; relatedArtifact 0..* RelatedArtifact Related artifacts associated with the problem in the eu-base layer. #xD; recordedDate 0..1 dateTime Date the problem was first recorded. #xD; recorder 0..1 Reference() Who recorded the problem. #xD; asserter 0..1 Reference() Who asserted the problem. #xD; stage 0..* logical-problem-stage Staging details associated with the problem. #xD; evidence 0..* logical-problem-evidence Evidence supporting the problem or diagnosis. #xD; note 0..* Annotation Narrative notes. #xD; Documentatie voor dit formaat
Canonical intermediate logical model for Problem to Condition translation. It is shaped to the full Condition core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core problem semantics using future-oriented normalized field names.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Source profile used to populate this logical model.
Target profile intended for this logical model instance.
Verification status of the asserted problem.
Dutch problem type semantics represented from the profiled category slice.
Dutch further specification of the problem name when carried by the dedicated extension.
Affected body site details, including laterality when supplied.
Encounter context in which the problem was recorded or discussed.
Onset period when recorded as a date range.
Onset range when recorded as an estimated range.
Age at abatement when recorded as an age.
Abatement period when recorded as a date range.
Abatement range when recorded as an estimated range.
Date the condition assertion was made when populated through the eu-base asserted-date extension.
Related artifacts associated with the problem in the eu-base layer.
Staging details associated with the problem.
Evidence supporting the problem or diagnosis.