plan_executor 1.0.2

data/fixtures/order_response/ordresp-200.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<OrderResponse xmlns="http://hl7.org/fhir">
+  <id value="ordresp-200"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: ordresp-200</p>
+      <p>
+        <b>identifier</b>: FILL = ordresp-200</p>
+      <p>
+        <b>request</b>: 
+        <a href="Order/order-200">Order/order-200</a>
+      </p>
+      <p>
+        <b>date</b>: 12/15/2015 7:36:25 AM</p>
+      <p>
+        <b>who</b>: 
+        <a href="Organization/org-uslab-example3">Acme Labs</a>
+      </p>
+      <p>
+        <b>orderStatus</b>: accepted</p>
+    </div>
+  </text>
+  <identifier>
+    <type>
+      <coding>
+        <code value="http://hl7.org/fhir/identifier-type"/>
+        <display value="FILL"/>
+      </coding>
+    </type>
+    <system value="http://lis.acmelabs.org/identifiers"/>
+    <value value="ordresp-200"/>
+  </identifier>
+  <!--  
+    this should be a response to the example request, 
+	but we don't yet have all the resource types in 
+	place to make this happen
+	
+	So for now, although the Order message referred to 
+	here contains a prescription resource, this example
+	response contains lab reports
+   -->
+  <request>
+    <reference value="Order/order-200"/>
+  </request>
+  <date value="2015-12-15T07:36:25Z"/>
+  <!--  made by the lab  -->
+  <who>
+    <reference value="Organization/org-uslab-example3"/>
+    <display value="Acme Labs"/>
+  </who>
+  <!--  
+    there's a loose relationship between the status of 
+    the order, and status information on the fulfillment
+    resources. For instance, in the case of a lab, it probably
+    wouldn't make sense to claim that the response is anything
+    but completed when the report is marked as "final" (as it is 
+    in this case). However due to the diversity of business 
+    practices in the order/fulfillment cycle, there's no formal
+    rules about what is allowed
+   -->
+  <orderStatus value="accepted"/>
+  <!--  
+    the lab report that the lab provides as a token of its 
+    fulfillment for this order 
+
+    In the case of a lab order, the report is usually the real/only
+    outcome. However in a case such as a medication administration,
+    the actual administration is the fulfillment - the MedicationAdministration
+    resource is only a token of the fulfillment of the order
+   -->
+  <!--<fulfillment>
+		<reference value="DiagnosticReport/101"/>
+	</fulfillment>-->
+</OrderResponse>

data/fixtures/order_response/ordresp-210.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<OrderResponse xmlns="http://hl7.org/fhir">
+  <id value="ordresp-210"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: ordresp-210</p>
+      <p>
+        <b>identifier</b>: FILL = ordresp-210</p>
+      <p>
+        <b>request</b>: 
+        <a href="Order/order-200">Order/order-200</a>
+      </p>
+      <p>
+        <b>date</b>: 12/15/2015 7:36:25 AM</p>
+      <p>
+        <b>who</b>: 
+        <a href="Organization/org-uslab-example3">Acme Labs</a>
+      </p>
+      <p>
+        <b>orderStatus</b>: completed</p>
+    </div>
+  </text>
+  <identifier>
+    <type>
+      <coding>
+        <code value="http://hl7.org/fhir/identifier-type"/>
+        <display value="FILL"/>
+      </coding>
+    </type>
+    <system value="http://lis.acmelabs.org/identifiers"/>
+    <value value="ordresp-210"/>
+  </identifier>
+  <!--  
+    this should be a response to the example request, 
+	but we don't yet have all the resource types in 
+	place to make this happen
+	
+	So for now, although the Order message referred to 
+	here contains a prescription resource, this example
+	response contains lab reports
+   -->
+  <request>
+    <reference value="Order/order-200"/>
+  </request>
+  <date value="2015-12-15T07:36:25Z"/>
+  <!--  made by the lab  -->
+  <who>
+    <reference value="Organization/org-uslab-example3"/>
+    <display value="Acme Labs"/>
+  </who>
+  <!--  
+    there's a loose relationship between the status of 
+    the order, and status information on the fulfillment
+    resources. For instance, in the case of a lab, it probably
+    wouldn't make sense to claim that the response is anything
+    but completed when the report is marked as "final" (as it is 
+    in this case). However due to the diversity of business 
+    practices in the order/fulfillment cycle, there's no formal
+    rules about what is allowed
+   -->
+  <orderStatus value="completed"/>
+  <!--  
+    the lab report that the lab provides as a token of its 
+    fulfillment for this order 
+
+    In the case of a lab order, the report is usually the real/only
+    outcome. However in a case such as a medication administration,
+    the actual administration is the fulfillment - the MedicationAdministration
+    resource is only a token of the fulfillment of the order
+   -->
+  <!--<fulfillment>
+		<reference value="DiagnosticReport/101"/>
+	</fulfillment>-->
+</OrderResponse>

data/fixtures/order_response/ordresp-300.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<OrderResponse xmlns="http://hl7.org/fhir">
+  <id value="ordresp-300"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: ordresp-300</p>
+      <p>
+        <b>identifier</b>: FILL = ordresp-300</p>
+      <p>
+        <b>request</b>: 
+        <a href="Order/order-300">Order/order-300</a>
+      </p>
+      <p>
+        <b>date</b>: 12/15/2015 7:36:25 AM</p>
+      <p>
+        <b>who</b>: 
+        <a href="Organization/org-uslab-example3">Acme Labs</a>
+      </p>
+      <p>
+        <b>orderStatus</b>: accepted</p>
+    </div>
+  </text>
+  <identifier>
+    <type>
+      <coding>
+        <code value="http://hl7.org/fhir/identifier-type"/>
+        <display value="FILL"/>
+      </coding>
+    </type>
+    <system value="http://lis.acmelabs.org/identifiers"/>
+    <value value="ordresp-300"/>
+  </identifier>
+  <!--  
+    this should be a response to the example request, 
+	but we don't yet have all the resource types in 
+	place to make this happen
+	
+	So for now, although the Order message referred to 
+	here contains a prescription resource, this example
+	response contains lab reports
+   -->
+  <request>
+    <reference value="Order/order-300"/>
+  </request>
+  <date value="2015-12-15T07:36:25Z"/>
+  <!--  made by the lab  -->
+  <who>
+    <reference value="Organization/org-uslab-example3"/>
+    <display value="Acme Labs"/>
+  </who>
+  <!--  
+    there's a loose relationship between the status of 
+    the order, and status information on the fulfillment
+    resources. For instance, in the case of a lab, it probably
+    wouldn't make sense to claim that the response is anything
+    but completed when the report is marked as "final" (as it is 
+    in this case). However due to the diversity of business 
+    practices in the order/fulfillment cycle, there's no formal
+    rules about what is allowed
+   -->
+  <orderStatus value="accepted"/>
+  <!--  
+    the lab report that the lab provides as a token of its 
+    fulfillment for this order 
+
+    In the case of a lab order, the report is usually the real/only
+    outcome. However in a case such as a medication administration,
+    the actual administration is the fulfillment - the MedicationAdministration
+    resource is only a token of the fulfillment of the order
+   -->
+  <!--<fulfillment>
+		<reference value="DiagnosticReport/101"/>
+	</fulfillment>-->
+</OrderResponse>

data/fixtures/order_response/ordresp-310.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<OrderResponse xmlns="http://hl7.org/fhir">
+  <id value="ordresp-310"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: ordresp-310</p>
+      <p>
+        <b>identifier</b>: FILL = ordresp-310</p>
+      <p>
+        <b>request</b>: 
+        <a href="Order/order-300">Order/order-300</a>
+      </p>
+      <p>
+        <b>date</b>: 12/15/2015 7:36:25 AM</p>
+      <p>
+        <b>who</b>: 
+        <a href="Organization/org-uslab-example3">Acme Labs</a>
+      </p>
+      <p>
+        <b>orderStatus</b>: completed</p>
+    </div>
+  </text>
+  <identifier>
+    <type>
+      <coding>
+        <code value="http://hl7.org/fhir/identifier-type"/>
+        <display value="FILL"/>
+      </coding>
+    </type>
+    <system value="http://lis.acmelabs.org/identifiers"/>
+    <value value="ordresp-310"/>
+  </identifier>
+  <!--  
+    this should be a response to the example request, 
+	but we don't yet have all the resource types in 
+	place to make this happen
+	
+	So for now, although the Order message referred to 
+	here contains a prescription resource, this example
+	response contains lab reports
+   -->
+  <request>
+    <reference value="Order/order-300"/>
+  </request>
+  <date value="2015-12-15T07:36:25Z"/>
+  <!--  made by the lab  -->
+  <who>
+    <reference value="Organization/org-uslab-example3"/>
+    <display value="Acme Labs"/>
+  </who>
+  <!--  
+    there's a loose relationship between the status of 
+    the order, and status information on the fulfillment
+    resources. For instance, in the case of a lab, it probably
+    wouldn't make sense to claim that the response is anything
+    but completed when the report is marked as "final" (as it is 
+    in this case). However due to the diversity of business 
+    practices in the order/fulfillment cycle, there's no formal
+    rules about what is allowed
+   -->
+  <orderStatus value="completed"/>
+  <!--  
+    the lab report that the lab provides as a token of its 
+    fulfillment for this order 
+
+    In the case of a lab order, the report is usually the real/only
+    outcome. However in a case such as a medication administration,
+    the actual administration is the fulfillment - the MedicationAdministration
+    resource is only a token of the fulfillment of the order
+   -->
+  <!--<fulfillment>
+		<reference value="DiagnosticReport/101"/>
+	</fulfillment>-->
+</OrderResponse>

data/fixtures/order_response/ordresp-400.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<OrderResponse xmlns="http://hl7.org/fhir">
+  <id value="ordresp-400"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: ordresp-400</p>
+      <p>
+        <b>identifier</b>: FILL = ordresp-400</p>
+      <p>
+        <b>request</b>: 
+        <a href="Order/order-400">Order/order-400</a>
+      </p>
+      <p>
+        <b>date</b>: 12/15/2015 7:36:25 AM</p>
+      <p>
+        <b>who</b>: 
+        <a href="Organization/org-uslab-example3">Acme Labs</a>
+      </p>
+      <p>
+        <b>orderStatus</b>: accepted</p>
+    </div>
+  </text>
+  <identifier>
+    <type>
+      <coding>
+        <code value="http://hl7.org/fhir/identifier-type"/>
+        <display value="FILL"/>
+      </coding>
+    </type>
+    <system value="http://lis.acmelabs.org/identifiers"/>
+    <value value="ordresp-400"/>
+  </identifier>
+  <!--  
+    this should be a response to the example request, 
+	but we don't yet have all the resource types in 
+	place to make this happen
+	
+	So for now, although the Order message referred to 
+	here contains a prescription resource, this example
+	response contains lab reports
+   -->
+  <request>
+    <reference value="Order/order-400"/>
+  </request>
+  <date value="2015-12-15T07:36:25Z"/>
+  <!--  made by the lab  -->
+  <who>
+    <reference value="Organization/org-uslab-example3"/>
+    <display value="Acme Labs"/>
+  </who>
+  <!--  
+    there's a loose relationship between the status of 
+    the order, and status information on the fulfillment
+    resources. For instance, in the case of a lab, it probably
+    wouldn't make sense to claim that the response is anything
+    but completed when the report is marked as "final" (as it is 
+    in this case). However due to the diversity of business 
+    practices in the order/fulfillment cycle, there's no formal
+    rules about what is allowed
+   -->
+  <orderStatus value="accepted"/>
+  <!--  
+    the lab report that the lab provides as a token of its 
+    fulfillment for this order 
+
+    In the case of a lab order, the report is usually the real/only
+    outcome. However in a case such as a medication administration,
+    the actual administration is the fulfillment - the MedicationAdministration
+    resource is only a token of the fulfillment of the order
+   -->
+  <!--<fulfillment>
+		<reference value="DiagnosticReport/101"/>
+	</fulfillment>-->
+</OrderResponse>

data/fixtures/order_response/ordresp-410.xml

@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<OrderResponse xmlns="http://hl7.org/fhir">
+  <id value="ordresp-410"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: ordresp-410</p>
+      <p>
+        <b>identifier</b>: FILL = ordresp-410</p>
+      <p>
+        <b>request</b>: 
+        <a href="Order/order-400">Order/order-400</a>
+      </p>
+      <p>
+        <b>date</b>: 12/15/2015 7:36:25 AM</p>
+      <p>
+        <b>who</b>: 
+        <a href="Organization/org-uslab-example3">Acme Labs</a>
+      </p>
+      <p>
+        <b>orderStatus</b>: completed</p>
+    </div>
+  </text>
+  <identifier>
+    <type>
+      <coding>
+        <code value="http://hl7.org/fhir/identifier-type"/>
+        <display value="FILL"/>
+      </coding>
+    </type>
+    <system value="http://lis.acmelabs.org/identifiers"/>
+    <value value="ordresp-410"/>
+  </identifier>
+  <!--  
+    this should be a response to the example request, 
+	but we don't yet have all the resource types in 
+	place to make this happen
+	
+	So for now, although the Order message referred to 
+	here contains a prescription resource, this example
+	response contains lab reports
+   -->
+  <request>
+    <reference value="Order/order-400"/>
+  </request>
+  <date value="2015-12-15T07:36:25Z"/>
+  <!--  made by the lab  -->
+  <who>
+    <reference value="Organization/org-uslab-example3"/>
+    <display value="Acme Labs"/>
+  </who>
+  <!--  
+    there's a loose relationship between the status of 
+    the order, and status information on the fulfillment
+    resources. For instance, in the case of a lab, it probably
+    wouldn't make sense to claim that the response is anything
+    but completed when the report is marked as "final" (as it is 
+    in this case). However due to the diversity of business 
+    practices in the order/fulfillment cycle, there's no formal
+    rules about what is allowed
+   -->
+  <orderStatus value="completed"/>
+  <!--  
+    the lab report that the lab provides as a token of its 
+    fulfillment for this order 
+
+    In the case of a lab order, the report is usually the real/only
+    outcome. However in a case such as a medication administration,
+    the actual administration is the fulfillment - the MedicationAdministration
+    resource is only a token of the fulfillment of the order
+   -->
+  <!--<fulfillment>
+		<reference value="DiagnosticReport/101"/>
+	</fulfillment>-->
+</OrderResponse>

data/fixtures/organization/org-uslab-example3.xml

@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Organization xmlns="http://hl7.org/fhir">
+  <id value="org-uslab-example3"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      <p>
+        <b>Generated Narrative with Details</b>
+      </p>
+      <p>
+        <b>id</b>: org-uslab-example3</p>
+      <p>
+        <b>identifier</b>: 01D1111111 (official)</p>
+      <p>
+        <b>name</b>: Acme Labs</p>
+      <p>
+        <b>address</b>: Firstcare Way Building 2 Harrisburg PA 42043 USA (work)</p>
+    </div>
+  </text>
+  <identifier>
+    <use value="official"/>
+    <system value="http://www.cms.gov/Regulations-and-Guidance/Legislation/CLIA/index.html"/>
+    <!--    CLIA    -->
+    <value value="01D1111111"/>
+  </identifier>
+  <name value="Acme Labs"/>
+  <address>
+    <!--    EH extension for us county    -->
+    <extension url="http://hl7.org/fhir/StructureDefinition/us-core-county">
+      <valueString value="42043"/>
+    </extension>
+    <use value="work"/>
+    <line value="Firstcare Way"/>
+    <line value="Building 2"/>
+    <city value="Harrisburg"/>
+    <state value="PA"/>
+    <postalCode value="42043"/>
+    <country value="USA"/>
+  </address>
+  <contact>
+    <name>
+      <family value="House"/>
+      <given value="Gregory"/>
+      <given value="F"/>
+      <prefix value="Dr"/>
+      <suffix value="PhD"/>
+    </name>
+  </contact>
+</Organization>

data/fixtures/patient/patient-example-updated.xml

@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="UTF-8"?><Patient xmlns="http://hl7.org/fhir">
+  <id value="example"/>
+  <text>
+    <status value="generated"/>
+    <div xmlns="http://www.w3.org/1999/xhtml">
+      
+      <table>
+        
+        <tbody>
+          
+          <tr>
+            
+            <td>Name</td>
+            
+            <td>Peter James 
+              <b>Chalmers</b> (&quot;Jim&quot;)
+            </td>
+          
+          </tr>
+          
+          <tr>
+            
+            <td>Address</td>
+            
+            <td>534 Erewhon, Pleasantville, Vic, 3999</td>
+          
+          </tr>
+          
+          <tr>
+            
+            <td>Contacts</td>
+            
+            <td>Home: unknown. Work: (03) 5555 6473</td>
+          
+          </tr>
+          
+          <tr>
+            
+            <td>Id</td>
+            
+            <td>MRN: 12345 (Acme Healthcare)</td>
+          
+          </tr>
+        
+        </tbody>
+      
+      </table>    
+    
+    </div>
+  </text>
+<!--   MRN assigned by ACME healthcare on 6-May 2001   -->
+  <identifier>
+    <use value="usual"/>
+    <type>
+      <coding>
+        <system value="http://hl7.org/fhir/v2/0203"/>
+        <code value="MR"/>
+      </coding>
+    </type>
+    <system value="urn:oid:1.2.36.146.595.217.0.1"/>
+    <value value="12345"/>
+    <period>
+      <start value="2001-05-06"/>
+    </period>
+    <assigner>
+      <display value="Acme Healthcare"/>
+    </assigner>
+  </identifier>
+  <active value="true"/>
+<!--   Peter James Chalmers, but called "Jim"   -->
+  <name>
+    <use value="official"/>
+    <family value="Chalmers"/>
+    <given value="Peter"/>
+    <given value="James"/>
+  </name>
+  <name>
+    <use value="usual"/>
+    <given value="Jim"/>
+  </name>
+  <telecom>
+    <use value="home"/>
+  <!--   home communication details aren't known   -->
+  </telecom>
+  <telecom>
+    <system value="phone"/>
+    <value value="(03) 5555 6473"/>
+    <use value="work"/>
+  </telecom>
+    <!-- additional telecom -->
+  <telecom>
+    <system value="email"/>
+    <value value="foo@example.com"/>
+  </telecom>
+<!--   use FHIR code system for male / female   -->
+  <gender value="male"/>
+  <birthDate value="1974-12-25">
+    <extension url="http://hl7.org/fhir/StructureDefinition/patient-birthTime">
+      <valueDateTime value="1974-12-25T14:35:45-05:00"/>
+    </extension>
+  </birthDate>
+  <deceasedBoolean value="false"/>
+  <address>
+    <use value="home"/>
+    <line value="534 Erewhon St"/>
+    <city value="PleasantVille"/>
+    <state value="Vic"/>
+    <postalCode value="3999"/>
+  </address>
+  <contact>
+    <relationship>
+      <coding>
+        <system value="http://hl7.org/fhir/patient-contact-relationship"/>
+        <code value="partner"/>
+      </coding>
+    </relationship>
+    <name>
+      <family value="du">
+      <!--   the "du" part is a family name prefix (VV in iso 21090)   -->
+        <extension url="http://hl7.org/fhir/StructureDefinition/iso21090-EN-qualifier">
+          <valueCode value="VV"/>
+        </extension>
+      </family>
+      <family value="Marché"/>
+      <given value="Bénédicte"/>
+    </name>
+    <telecom>
+      <system value="phone"/>
+      <value value="+33 (237) 998327"/>
+    </telecom>
+    <gender value="female"/>
+    <period>
+    <!--   The contact relationship started in 2012   -->
+      <start value="2012"/>
+    </period>
+  </contact>
+  <managingOrganization>
+    <reference value="Organization/1"/>
+  </managingOrganization>
+</Patient>