-
Notifications
You must be signed in to change notification settings - Fork 14
/
Copy pathPROBLEM_Resolved_Problem.xml
71 lines (70 loc) · 3.21 KB
/
PROBLEM_Resolved_Problem.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
<section>
<templateId root="2.16.840.1.113883.10.20.22.2.5.1"/>
<code code="11450-4" codeSystem="2.16.840.1.113883.6.1" displayName="Problem List"/>
<title>Problem List</title>
<text>
<table>
<thead>
<tr>
<th>Name</th>
<th>Dates</th>
<th>Status</th>
</tr>
</thead>
<tbody>
<tr ID="Problem1">
<td ID="ProblemDescription1">Acute pharyngitis</td>
<td>
<content>Onset: Apr 2 2014</content>
<br />
<content>Resolution: Apr 5 2014</content>
</td>
<td>Resolved</td>
</tr>
</tbody>
</table>
</text>
<entry>
<act classCode="ACT" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.22.4.3" />
<id root="e5fbc288-659f-4aeb-a5e1-eb7cc8fcdfaf" />
<code code="CONC" codeSystem="2.16.840.1.113883.5.6" />
<!-- Since this is a resolved problem, the concern status has been changed to completed. -->
<!-- While clinicians can track resolved problems, generally active problems will have active concern status and resolved concerns will be completed -->
<statusCode code="completed" />
<effectiveTime>
<!-- This represents the time that the clinician began tracking the concern. This may frequently be an EHR timestamp-->
<low value="20140403124536+0500" />
<!-- This represents the time that the clinician stopped actively the concern. This may frequently be an EHR timestamp-->
<high value="20140407102516+0500" />
</effectiveTime>
<entryRelationship typeCode="SUBJ">
<observation classCode="OBS" moodCode="EVN">
<templateId root="2.16.840.1.113883.10.20.22.4.4" />
<id extension="10241108" root="1.3.6.1.4.1.22812.4.111.0.4.1.2.1" />
<code codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" code="55607006" displayName="Problem" />
<text>
<reference value="#Problem1" />
</text>
<statusCode code="completed" />
<effectiveTime>
<!-- This represents the date of biological onset. This can be before the patient vistited the clinician, as illustrated in this example-->
<low value="20140402" />
<!-- This represents the date of resolution. Since this a boundary condition, if you wish to include the full day, the boundary should be padded or be the start of next day -->
<!-- This reflects a common confusion point since people often consider dates to include the day at the boundary, but this ia RIM-related boundary constraint-->
<high value="20140405235959+0500"/>
</effectiveTime>
<!-- This is a SNOMED code as the primary vocabulary for problem lists-->
<value xsi:type="CD" code="363746003" codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED CT" displayName="Acute pharyngitis">
<originalText>
<reference value="#ProblemDescription1" />
</originalText>
<!-- These are common translations of the SNOMED code, ICd-9 and ICd-10 are often used in billing-->
<translation xsi:type="CD" code="462" codeSystem="2.16.840.1.113883.6.103" codeSystemName="ICD-9" displayName="Acute pharyngitis" />
<translation xsi:type="CD" code="J02.9" codeSystem="2.16.840.1.113883.6.90" codeSystemName="ICD-10" displayName="Acute pharyngitis" />
</value>
</observation>
</entryRelationship>
</act>
</entry>
</section>