-
Notifications
You must be signed in to change notification settings - Fork 13
/
No_Known_Problems_Section_20140226.xml
82 lines (81 loc) · 5 KB
/
No_Known_Problems_Section_20140226.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
<?xml version="1.0" encoding="UTF-8"?>
<!-- Problem Section -->
<component>
<section>
<templateId root="2.16.840.1.113883.10.20.22.2.5.1"/> <!-- Problem Section with Coded Entries Required -->
<code code="11450-4" codeSystem="2.16.840.1.113883.6.1" codeSystemName="LOINC" displayName="Problem List"/>
<title>PROBLEMS</title>
<text ID="Concern_1">
Problem Concern:<br/>
Concern Tracker Start Date: 06/07/2013 16:05:06<br/>
Concern Tracker End Date: <br/>
Concern Status: Active<br/>
<content ID="problems1">No known <content ID="problemType1">problems.</content></content>
</text>
<entry typeCode="DRIV">
<!-- Problem Concern Act -->
<act classCode="ACT" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.22.4.3"/>
<id root="36e3e930-7b14-11db-9fe1-0800200c9a66"/>
<!-- SDWG supports 48765-2 or CONC in the code element -->
<code code="CONC" codeSystem="2.16.840.1.113883.5.6"/>
<text><reference value="#Concern_1"></reference></text>
<statusCode code="active"/> <!-- The concern is not active, in terms of there being an active condition to be managed.-->
<effectiveTime>
<low value="20130607160506"/> <!-- Time at which THIS “concern” began being tracked.-->
</effectiveTime> <!-- status is active so high is not applicable. If high is present it should have nullFlavor of NA-->
<!-- Optional Author Element-->
<author>
<time value="20130607160506"/>
<assignedAuthor>
<id extension="66666" root="2.16.840.1.113883.4.6"/>
<code code="207RC0000X" codeSystem="2.16.840.1.113883.6.101" codeSystemName="NUCC"
displayName="Cardiovascular Disease"/>
<addr>
<streetAddressLine>6666 StreetName St.</streetAddressLine>
<city>Silver Spring</city><state>MD</state><postalCode>20901</postalCode>
<country>US</country>
</addr>
<telecom value="tel:+1(301)666-6666" use="WP"/>
<assignedPerson>
<name>
<given>Heartly</given>
<family>Sixer</family>
<suffix>MD</suffix>
</name>
</assignedPerson>
</assignedAuthor>
</author>
<entryRelationship typeCode="SUBJ">
<observation classCode="OBS" moodCode="EVN" negationInd="true">
<!-- Model of Meaning for No Problems -->
<!-- This is more consistent with how we did no known allergies. -->
<!-- The use of negationInd corresponds with the newer Observation.ValueNegationInd -->
<!-- The negationInd = true negates the value element. -->
<!-- problem observation template -->
<templateId root="2.16.840.1.113883.10.20.22.4.4"/>
<id root="4adc1021-7b14-11db-9fe1-0800200c9a67"/>
<code code="ASSERTION" codeSystem="2.16.840.1.113883.5.4"/>
<text><reference value="#problems1"></reference></text>
<statusCode code="completed"/>
<effectiveTime>
<low value="20130607160506"/>
</effectiveTime>
<!-- The time when this was biologically relevant ie True for the patient. -->
<!-- As a minimum time interval over which this is true, populate the effectiveTime/low with the current time. -->
<!-- It would be equally valid to have a longer range of time over which this statement was represented as being true. -->
<!-- As a maximum, you would never indicate an effectiveTime/high that was greater than the current point in time. -->
<!-- This idea assumes that the value element could come from the Problem value set, or-->
<!-- when negationInd was true, is could also come from the ProblemType value set (and code would be ASSERTION). -->
<value xsi:type="CD" code="55607006"
displayName="Problem"
codeSystem="2.16.840.1.113883.6.96"
codeSystemName="SNOMED CT">
<originalText><reference value="#problemType1"></reference></originalText>
</value>
</observation>
</entryRelationship>
</act>
</entry>
</section>
</component>