plan_executor 1.0.2

data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/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/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/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/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/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/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/OrderResponse/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/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/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/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Patient/patient-uslab-example1.xml

@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?><Patient xmlns="http://hl7.org/fhir">
+  <id value="patient-uslab-example1"/>
+  <text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: patient-uslab-example1</p><p><b>identifier</b>: 18547545 (USUAL)</p><p><b>name</b>: Todd G. Lerr (OFFICIAL)</p><p><b>gender</b>: male</p><p><b>birthDate</b>: Jun 7, 2012</p><p><b>deceased</b>: false</p><p><b>address</b>: 123 North 102nd Street Apt 4d Harrisburg PA 17102 USA (HOME)</p></div></text><extension url="http://hl7.org/fhir/StructureDefinition/us-core-race">
+    <valueCodeableConcept>
+      <coding>
+        <code value="2106-3"/>
+      </coding>
+    </valueCodeableConcept>
+  </extension>
+  <extension url="http://hl7.org/fhir/StructureDefinition/us-core-ethnicity">
+    <valueCodeableConcept>
+      <coding>
+        <code value="2135-2"/>
+      </coding>
+    </valueCodeableConcept>
+  </extension>
+<!--    EH: limit to single identifier that orderer can match to patient system can be URL    -->
+  <identifier>
+    <use value="usual"/>
+    <system value="urn:oid:2.16.840.1.113883.3.72.5.30.2"/>
+    <value value="18547545"/>
+  </identifier>
+<!--   name use limited to official and anonymous   -->
+  <name>
+    <use value="official"/>
+    <family value="Lerr"/>
+    <given value="Todd"/>
+    <given value="G."/>
+    <suffix value="Jr"/>
+  </name>
+<!--    use FHIR code system for male / female    -->
+  <gender value="male"/>
+  <birthDate value="2012-06-07"/>
+  <deceasedBoolean value="false"/>
+  <address>
+    <use value="home"/>
+    <line value="123 North 102nd Street"/>
+    <line value="Apt 4d"/>
+    <city value="Harrisburg"/>
+    <state value="PA"/>
+    <postalCode value="17102"/>
+    <country value="USA"/>
+  </address>
+</Patient>

data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Practitioner/pract-uslab-example1.xml

@@ -0,0 +1,18 @@
+<?xml version="1.0" encoding="UTF-8"?><Practitioner xmlns="http://hl7.org/fhir">
+	<id value="pract-uslab-example1"/>
+		<text><status value="generated"/><div xmlns="http://www.w3.org/1999/xhtml"><p><b>Generated Narrative with Details</b></p><p><b>id</b>: pract-uslab-example1</p><p><b>identifier</b>: 4444444445 (OFFICIAL)</p><p><b>name</b>: Leanard T Bloodraw </p><p><b>telecom</b>: ph: (555)7771234 ext.11</p></div></text><identifier>
+		<use value="official"/>
+		<system value="http://hl7.org/fhir/sid/us-npi"/> <!--   NPI  -->
+		<value value="4444444445"/>
+		</identifier>
+	<name>
+		<family value="Bloodraw"/>
+		<given value="Leanard"/>
+		<given value="T"/>
+		<suffix value="Jr"/>
+	</name>
+	<telecom>
+		<system value="phone"/>
+		<value value="(555)7771234 ext.11"/>
+	</telecom>
+</Practitioner>

data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Practitioner/pract-uslab-example3.xml

@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Practitioner xmlns="http://hl7.org/fhir">
+  <id value="pract-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>: pract-uslab-example3</p>
+      <p>
+        <b>identifier</b>: 1234567893 (official)</p>
+      <p>
+        <b>name</b>: Gregory F House </p>
+      <p>
+        <b>telecom</b>: ph: 555 777 1234 11</p>
+    </div>
+  </text>
+  <identifier>
+    <use value="official"/>
+    <system value="http://hl7.org/fhir/sid/us-npi"/>
+    <!--   NPI  -->
+    <value value="1234567893"/>
+  </identifier>
+  <name>
+    <family value="House"/>
+    <given value="Gregory"/>
+    <given value="F"/>
+    <suffix value="PhD"/>
+  </name>
+  <telecom>
+    <system value="phone"/>
+    <value value="555 777 1234 11"/>
+  </telecom>
+</Practitioner>

data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Specimen/spec-100.xml

@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Specimen xmlns="http://hl7.org/fhir">
+	<id value="spec-100"/>
+	<text>
+		<status value="generated"/>
+		<div xmlns="http://www.w3.org/1999/xhtml">
+			<p>
+				<b>Generated Narrative with Details</b>
+			</p>
+			<p>
+				<b>id</b>: spec-100</p>
+			<p>
+				<b>type</b>: Platelet-free plasma 
+        <span style="background: LightGoldenRodYellow ">(Details : {SNOMED CT code "708048008" := "708048008", given as "Plasma specimen with citrate"}; {http://ehr.goodhealthclinic.org/specimens/type code "PFP" := "PFP", given as "Platelet Free Plasma"})</span>
+			</p>
+			<p>
+				<b>subject</b>: 
+        <a href="Patient/patient-uslab-example1">Todd Lerr</a>
+			</p>
+			<p>
+				<b>accessionIdentifier</b>: spec-100 (official)</p>
+		</div>
+	</text>
+	<!--Assume no specimen placer ID  for now	<identifier>		<use value="official"/>		<system value="http://ehr.goodhealthclinic.org/identifiers/specimen"/>		<value value="spec-100"/>	</identifier>-->
+	<!--Filler ID moved to accsession number-->
+	<!--     Type is a loosely defined field because there is such a lot of variation in how it is used.   The principal variation is how much information that could be represented elsewhere is also   represented here. For instance, here's some possible types:     lithium heparin plasma   (+ .container.additive) (e.g. SNOMED CT 446272009)     transfusion bag of blood (+ container.type)     Peritoneal lavage        (+ collection.bodySite)   If the type includes other fields, it would be normal not to populate the other fields   Note that this practice is so widespread that it's pointless to try and stop it  :(   -->
+	<!--  choice of SNOMED CT concept code...  -->
+	<type>
+		<coding>
+			<system value="http://snomed.info/sct"/>
+			<!--  EH: Note to balloters  - lots of choices for whole blood I chose this.  -->
+			<code value="708048008"/>
+			<display value="Plasma specimen with citrate"/>
+		</coding>
+		<!--   and or local code  -->
+		<coding>
+			<system value="http://ehr.goodhealthclinic.org/specimens/type"/>
+			<code value="PFP"/>
+			<display value="Platelet Free Plasma"/>
+		</coding>
+		<text value="Platelet-free plasma"/>
+	</type>
+	<!--  Patient is required from core   -->
+	<subject>
+		<reference value="Patient/patient-uslab-example1"/>
+		<display value="Todd Lerr"/>
+	</subject>
+	<!--   accession identifier - e.g. assigned by the labaratory when it is received.     This is common, unlike specimen identifier   -->
+	<accessionIdentifier>
+		<use value="official"/>
+		<system value="http://lis.acmelabs.org/identifiers/accession"/>
+		<value value="spec-100"/>
+	</accessionIdentifier>
+	<collection>
+		<!--   the time of collection is required. Usually a point in time, but can be a period      (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine)   Should be same a effective times in obs and dr-->
+		<collectedDateTime value="2014-12-05"/>
+		<!--	<bodySite>-->
+		<!--  choice of SNOMED CT concept code...  -->
+		<!--<coding>				<system value="http://snomed.info/sct"/>-->
+		<!--  EH: Note to balloters  -  this is to demonstrate use of source for body site not really needed for blood draw.  -->
+		<!--<code value="53120007"/>				<display value="Arm"/>			</coding>-->
+		<!--   and or local code  -->
+		<!--<coding>				<system value="http://ehr.goodhealthclinic.org"/>				<code value="ARM"/>				<display value="Arm"/>			</coding>			<text value="Drawn from Arm"/>		</bodySite>-->
+	</collection>
+</Specimen>

data/lib/tests/testscripts/xml/Connectathon11/Track7-LabOrderLabReport/_reference/resources/Specimen/spec-400.xml

@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Specimen xmlns="http://hl7.org/fhir">
+  <id value="spec-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>: spec-400</p>
+      <p>
+        <b>type</b>: Stool specimen 
+        <span style="background: LightGoldenRodYellow ">(Details : {SNOMED CT code "119339001" := "119339001", given as "Stool specimen"})</span>
+      </p>
+      <p>
+        <b>subject</b>: 
+        <a href="Patient/patient-uslab-example1">Todd Lerr</a>
+      </p>
+      <p>
+        <b>accessionIdentifier</b>: 21041205000001 (official)</p>
+    </div>
+  </text>
+  <!--   a specimen identifier - e.g. assigned when the specimen was taken by the orderer/placer  use the accession number for the filling lab   -->
+  <!--  Placer ID  -->
+  <!--  Filler ID moved to accsession number
+	<identifier>
+		<use value="official"></use>
+		<label  value="Filler Specimen ID"></label>
+		<system value="http://lis.acmelabs.org/identifiers/specimen"/>
+		<value value="SID456"/>
+	</identifier>
+  -->
+  <!--  
+   Type is a loosely defined field because there is such a lot of variation in how it is used.
+   The principal variation is how much information that could be represented elsewhere is also
+   represented here. For instance, here's some possible types:
+     lithium heparin plasma   (+ .container.additive) (e.g. SNOMED CT 446272009)
+     transfusion bag of blood (+ container.type)
+     Peritoneal lavage        (+ collection.bodySite)
+   If the type includes other fields, it would be normal not to populate the other fields
+
+   Note that this practice is so widespread that it's pointless to try and stop it  :(   -->
+  <!--  choice of SNOMED CT concept code...  -->
+  <type>
+    <coding>
+      <system value="http://snomed.info/sct"/>
+      <code value="119339001"/>
+      <display value="Stool specimen"/>
+    </coding>
+    <text value="Stool specimen"/>
+  </type>
+  <!--  Patient is required from core   -->
+  <subject>
+    <reference value="Patient/patient-uslab-example1"/>
+    <display value="Todd Lerr"/>
+  </subject>
+  <!--   accession identifier - e.g. assigned by the labaratory when it is received.
+     This is common, unlike specimen identifier   -->
+  <accessionIdentifier>
+    <use value="official"/>
+    <system value="http://lis.acmelabs.org/identifiers/accession"/>
+    <value value="21041205000001"/>
+  </accessionIdentifier>
+  <collection>
+    <!--   the time of collection is required. Usually a point in time, but can be a period
+      (collectedPeriod) if it's a timed collection (e.g. a 24 hour urine)   -->
+    <collectedDateTime value="2014-12-05"/>
+  </collection>
+</Specimen>