StructureDefinition-2.16.840.1.113883.10.20.22.4.3

Sourcehl7.cda.us.ccdar2dot2#current:Consolidated CDA Release 2.1 StructureDefinition Publication (v5.0.0)
resourceTypeStructureDefinition
id2.16.840.1.113883.10.20.22.4.3
canonicalhttp://hl7.org/fhir/cda/ccda/StructureDefinition/2.16.840.1.113883.10.20.22.4.3
version2.2
statusactive
publisherHealth Level Seven
nameProblemConcernAct
titleProblem Concern Act
date2021-11-24T17:43:01+00:00
descriptionThis template reflects an ongoing concern on behalf of the provider that placed the concern on a patients problem list. So long as the underlying condition is of concern to the provider (i.e., as long as the condition, whether active or resolved, is of ongoing concern and interest to the provider), the statusCode is active. Only when the underlying condition is no longer of concern is the statusCode set to completed. The effectiveTime reflects the time that the underlying condition was felt to be a concern; it may or may not correspond to the effectiveTime of the condition (e.g., even five years later, the clinician may remain concerned about a prior heart attack). The statusCode of the Problem Concern Act is the definitive indication of the status of the concern, whereas the effectiveTime of the nested Problem Observation is the definitive indication of whether or not the underlying condition is resolved. The effectiveTime/low of the Problem Concern Act asserts when the concern became active. The effectiveTime/high asserts when the concern was completed (e.g., when the clinician deemed there is no longer any need to track the underlying condition). A Problem Concern Act can contain many Problem Observations (templateId 2.16.840.1.113883.10.20.22.4.4). Each Problem Observation is a discrete observation of a condition, and therefore will have a statusCode of completed. The many Problem Observations nested under a Problem Concern Act reflect the change in the clinical understanding of a condition over time. For instance, a Concern may initially contain a Problem Observation of chest pain: - Problem Concern 1 --- Problem Observation: Chest Pain Later, a new Problem Observation of esophagitis will be added, reflecting a better understanding of the nature of the chest pain. The later problem observation will have a more recent author time stamp. - Problem Concern 1 --- Problem Observation (author/time Jan 3, 2012): Chest Pain --- Problem Observation (author/time Jan 6, 2012): Esophagitis Many systems display the nested Problem Observation with the most recent author time stamp, and provide a mechanism for viewing prior observations.
jurisdictionsus
fhirVersion4.0.1
kindresource
abstractfalse
sdTtypeAct
derivationconstraint
basehttp://hl7.org/fhir/cda/StructureDefinition/Act
Usages
Name Flags Card. Type Description & Constraints doco
. . Act
. . . classCode 1..1 Required Pattern: ACT
. . . moodCode 1..1 Required Pattern: EVN
. . . Slices for templateId Slice: Unordered, Open by value:extension, value:root
. . . . templateId:primary 1..1
. . . . . root 1..1 Required Pattern: 2.16.840.1.113883.10.20.22.4.3
. . . . . extension 1..1 Required Pattern: 2015-08-01
. . . id 1..*
. . . code 1..1
. . . . code 1..1 Required Pattern: CONC
. . . . codeSystem 1..1 Required Pattern: 2.16.840.1.113883.5.6
. . . statusCode 1..1 The statusCode of the Problem Concern Act is the definitive indication of the status of the concern, whereas the effectiveTime of the nested Problem Observation is the definitive indication of whether or not the underlying condition is resolved.
. . . . code 1..1 The statusCode of the Problem Concern Act is the definitive indication of the status of the concern, whereas the effectiveTime of the nested Problem Observation is the definitive indication of whether or not the underlying condition is resolved.
Binding: ProblemAct statusCode ( required )
. . . effectiveTime 1..1
. . . . low 1..1 The effectiveTime/low of the Problem Concern Act asserts when the concern became active.
. . . . high 0..1 The effectiveTime/high asserts when the concern was completed (e.g., when the clinician deemed there is no longer any need to track the underlying condition).
. . . author 0..* http://hl7.org/fhir/cda/StructureDefinition/Author
. . . Slices for entryRelationship The following entryRelationship represents the importance of the concern to a provider.
Slice: Unordered, Open by profile:observation
. . . . entryRelationship:problem 1..*
. . . . . typeCode 1..1 Required Pattern: SUBJ
. . . . . observation 1..1 http://hl7.org/fhir/cda/StructureDefinition/Observation
. . . . entryRelationship:priority 0..*
. . . . . typeCode 1..1 Required Pattern: REFR
. . . . . observation 1..1 http://hl7.org/fhir/cda/StructureDefinition/Observation

doco Documentation for this format

Produced 08 Sep 2023