Id1.2.276.0.76.10.4074
ref
hl7de-
Gültigkeit ab2015‑12‑06
Statusdraft EntwurfVersions-Label
NameProblemConcernActBezeichnungProblem Concern Act
Beschreibung
en-US This template reflects an ongoing concern on behalf of the provider that placed the concern on a patient’s 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. This equates to the time the concern was authored in the patient's chart. 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.
KontextElternknoten des Template-Element mit Id 1.2.276.0.76.10.4074
KlassifikationCDA Entry Level Template
Offen/GeschlossenOffen (auch andere als die definierten Elemente sind erlaubt)
Benutzt von / Benutzt
Benutzt von 3 Transactions und 7 Templates, Benutzt 3 Templates
Benutzt von als NameVersion
2.16.840.1.113883.3.1937.777.54.4.2Transaktiondraft CDA-Dokument Einweisungsbrief2020‑07‑10 20:14:25
2.16.840.1.113883.2.6.60.12.4.4Transaktiondraft Erzeugung-Überleitungsdokument2017‑03‑09 12:24:04
2.16.840.1.113883.2.6.60.10.41Transaktiondraft CDA-Dokument Arztbrief Plus2017‑02‑01
1.2.276.0.76.10.1020linkdraft Arztbrief Plus (v3.00)2017‑02‑01
1.2.276.0.76.10.1023linkdraft Überleitungs-CDA Dokument2017‑03‑14
1.2.276.0.76.10.1034linkdraft eEinweisungsbrief (v1.0)2020‑06‑18
1.2.276.0.76.10.3023Containmentdraft Frühere Erkrankungen2017‑04‑09
1.2.276.0.76.10.3079Containmentdraft Gesundheitsprobleme2017‑03‑01
1.2.276.0.76.10.3098Containmentdraft Grund für die Einweisung2017‑05‑26
2.16.840.1.113883.2.6.60.12.10.113linkdraft Überleitungs-CDA (ambulant-stationär)2018‑04‑04 17:10:48
Benutzt als NameVersion
1.2.276.0.76.10.4075Containmentdraft Problem ObservationDYNAMIC
1.2.276.0.76.10.4076Containmentdraft Priorität PräferenzDYNAMIC
1.2.276.0.76.10.90025Inklusiondraft Author (Body)DYNAMIC
BeziehungSpezialisierung: Template 2.16.840.1.113883.10.12.301 CDA Act (2005‑09‑07)
ref
ad1bbr-

Adaptation: Template 2.16.840.1.113883.10.20.22.4.3 (2015‑08‑01)
ref
hl7de-
Beispiel
Beispiel
<act classCode="ACT" moodCode="EVN">
  <templateId root="1.2.276.0.76.10.4074"/>  <id root="ec8a6ff8-ed4b-4f7e-82c3-e98e58b45de7"/>  <code code="CONC" codeSystem="2.16.840.1.113883.5.6" displayName="Concern"/>  <!-- Der statusCode besagt, dass das Problem noch besteht (aktuell/aktiv) und verfolgt werden muss -->
  <statusCode code="active"/>  <effectiveTime>
    <!-- Das low Element gibt an, wann das Problem zum ersten Male dokumentiert worden ist -->
    <low value="201307061145-0800"/>  </effectiveTime>
  <author typeCode="AUT">
    <!-- dasselbe wie Concern effectiveTime/low -->
    <time value="201307061145-0800"/>    <assignedAuthor>
      <!-- Autor des Problems mit id und code -->
    </assignedAuthor>
  </author>
  <entryRelationship typeCode="SUBJ">
    <observation classCode="OBS" moodCode="EVN">
      <!-- Problem Observation 1.2.276.0.76.10.4076 -->
    </observation>
  </entryRelationship>
</act>
ItemDTKardKonfBeschreibungLabel
hl7:act
ProbdotsnAct
@classCode
cs1 … 1FACT
@moodCode
cs1 … 1FEVN
hl7:templateId
1 … 1MProbdotsnAct
@root
uid1 … 1F1.2.276.0.76.10.4074
hl7:id
1 … *ProbdotsnAct
hl7:code
1 … 1MProbdotsnAct
@code
CONF1 … 1FCONC
@codeSystem
1 … 1F2.16.840.1.113883.5.6
hl7:statusCode
1 … 1MProbdotsnAct
hl7:effectiveTime
1 … 1MProbdotsnAct
hl7:low
1 … 1MProbdotsnAct
hl7:high
0 … 1ProbdotsnAct
hl7:author
0 … *RProbdotsnAct
Eingefügt von 1.2.276.0.76.10.90025 Author (Body) (DYNAMIC)
@typeCode
cs0 … 1FAUT
@contextControlCode
cs0 … 1FOP
hl7:functionCode
CE0 … 1AuthdotsBody
 CONF
Der Wert von @code muss gewählt werden aus dem Value Set 2.16.840.1.113883.1.11.10267 ParticipationFunction (DYNAMIC)
hl7:time
TS1 … 1RAuthdotsBody
hl7:assignedAuthor
1 … 1RAuthdotsBody
@classCode
cs0 … 1FASSIGNED
hl7:id
II1 … *RAuthdotsBody
hl7:code
CE0 … 1AuthdotsBody
@codeSystem
CONF0 … 1F2.16.840.1.113883.5.111
hl7:addr
AD0 … *AuthdotsBody
hl7:telecom
TEL0 … *AuthdotsBody
hl7:assignedPerson
0 … 1AuthdotsBody
Eingefügt von 1.2.276.0.76.10.90010 CDA Person Elements (DYNAMIC)
@classCode
cs0 … 1FPSN
@determinerCode
cs0 … 1FINSTANCE
hl7:name
PN1 … 1MPersdotsents
hl7:representedOrganization
0 … 1AuthdotsBody
Eingefügt von 1.2.276.0.76.10.90011 CDA Organization Elements (DYNAMIC)
@classCode
cs0 … 1FORG
@determinerCode
cs0 … 1FINSTANCE
hl7:id
II0 … *Orgadotsents
hl7:name
ON1 … 1MOrgadotsents
hl7:telecom
TEL0 … *Orgadotsents
hl7:addr
AD0 … 1Orgadotsents
hl7:entryRelationship
1 … *MListe der Probleme
Beinhaltet 1.2.276.0.76.10.4075 Problem Observation (DYNAMIC)
ProbdotsnAct
@typeCode
cs1 … 1FSUBJ
hl7:entryRelationship
0 … *Priorität des Problem laut Einschätzung des Gesundheitsdienstleisters
Beinhaltet 1.2.276.0.76.10.4076 Priorität Präferenz (DYNAMIC)
ProbdotsnAct
@typeCode
cs1 … 1FREFR