Sha256: a177bf854f5158c9b01f735f1165e42db784dad0adb453e2ff10988b980e0bd5
Contents?: true
Size: 1.96 KB
Versions: 10
Compression:
Stored size: 1.96 KB
Contents
<?xml version="1.0" encoding="UTF-8"?>
<List xmlns="http://hl7.org/fhir">
<id value="med-list"/>
<meta>
<security>
<system value="http://terminology.hl7.org/CodeSystem/v3-ActReason"/>
<code value="HTEST"/>
<display value="test health data"/>
</security>
</meta>
<status value="current"/>
<mode value="changes"/>
<code>
<coding>
<system value="http://snomed.info/sct"/>
<code value="182836005"/>
<display value="Review of medication"/>
</coding>
<text value="Medication Review"/>
</code>
<date value="2013-11-20T23:10:23+11:00"/>
<source>
<reference value="Patient/example"/>
</source>
<!--
in a real medications list, we'd actually have medication resources.
but this an example to demonstrate a changes list, so we'll just use
display -->
<entry>
<!-- patient was prescribed hydroxocobalamin. the flag marks this
as a prescription. Note that healthcare workers will now get into
a long debate the exact implication of "prescribed". That's why the
spec doesn't fix the flag values -->
<flag>
<coding>
<system value="http://nehta.gov.au/codes/medications/changetype"/>
<code value="01"/>
<display value="Prescribed"/>
</coding>
</flag>
<item>
<display value="hydroxocobalamin"/>
</item>
</entry>
<!--
on this one, we record that the patient was taken off morphine sulfate.
because not every system knows the flags, and the ensure there's no confusion,
if the flag implies that something was removed from the list, then the
deleted element must also be set
-->
<entry>
<flag>
<coding>
<system value="http://nehta.gov.au/codes/medications/changetype"/>
<code value="02"/>
<display value="Cancelled"/>
</coding>
</flag>
<deleted value="true"/>
<item>
<display value="Morphine Sulfate"/>
</item>
</entry>
</List>
Version data entries
10 entries across 10 versions & 1 rubygems